Overview
Bitpayway is a stablecoin payment provider designed to be practical and simple to use. With the best fees on the market, our platform offers the best solution for on-chain payments. It was designed so you can integrate easily and start using it right away. Our support is personalized and human (no bots!).
What you can do
- Quick and simple integration with your application, with support for multiple networks.
- Manage payments for each of your businesses separately.
- Receive payments with immediate liquidity (no custody on our side).
- Support for multi-destination payments. Part of the payment goes to your account and part to one of your partners.
- Receive signed webhook notifications when an order status changes.
- Follow orders, values and transaction details in the dashboard.
Supported assets and networks
| Network | Stablecoins | Platform fee |
|---|---|---|
| Ethereum | USDT, USDC | 1% |
| Arbitrum | USDT, USDC | 1% |
Payments must be made with the official token contracts below. Tokens bridged from another network, such as USDC.e on Arbitrum, are not accepted.
| Network | Stablecoin | Token contract | Decimals |
|---|---|---|---|
| Ethereum | USDT | 0xdAC17F958D2ee523a2206206994597C13D831ec7 | 6 |
| Ethereum | USDC | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | 6 |
| Arbitrum | USDT (USD₮0) | 0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9 | 6 |
| Arbitrum | USDC | 0xaf88d065e77c8cC2239327C5EDb3A432268e5831 | 6 |
On Arbitrum, the USDT contract identifies itself as USD₮0, Tether's official
USDT on that network. Wallets and explorers may show either name.
Availability can depend on the stablecoin and network configuration enabled for your business. See how the fees are calculated.
Your first payment in 4 steps
1. Create a business
In the dashboard, enter the name of your business to create its configuration. Each business has its own settings, keys, wallets and orders. Fill in its webhook URL and the redirect URLs for successful and failed payments. See Configuring your account.
2. Create the API and webhook keys and use them in your application
In the business configuration, create an API key and a webhook secret key, and store both on your server:
- The API key authenticates the requests your server sends to the
API, in the
Authorizationheader. Copy it when you create it, because it is not displayed again. - The webhook secret key verifies the signature of the webhook notifications your application receives.
3. Register your wallets and authorize them on the blockchain
For each stablecoin on each network you want to accept, enter the address of the wallet that receives the payments. Then enable it by approving the on-chain transaction with MetaMask. You cannot create orders for a token until its wallet is enabled.
Multi-destination payments use their own wallet registry and need an additional setup.
4. Create orders and collect payment in the checkout
Your server creates a payment order with POST /api/order and redirects the
customer to the gatewayUrl returned in the response. In the
hosted checkout, the customer connects a wallet, pays and
returns to your redirect URL. Your server then receives the webhook with the
paid status.
Use the browser redirect to guide the customer experience, and use the signed webhook to confirm payment status on your server.