Build with the API
Accounts, invoices, receiving addresses, balances, history, transfers, fee estimates and callbacks, all through one versioned REST API.
Explore the APIFind the integration that fits your product. Start with an account, understand the payment flow, and build one clear step at a time.
Accounts, invoices, receiving addresses, balances, history, transfers, fee estimates and callbacks, all through one versioned REST API.
Explore the APICreate an invoice with an amount and a deadline, then share its checkout link or embed it in your website. Follow partial payments and confirmations in the dashboard.
Explore invoicesReceive payment notifications on your server, verify payment state through the API and update the matching order.
Set up callbacksOpen the dashboard and create an account. Save the Account ID and the one-time Transfer Key in a safe place. The ID identifies your account; the key authorizes protected actions such as transfers. They are not interchangeable.
Create an accountChoose Bitcoin, Litecoin, TRX or USDT TRC20, then add a receiving address in the dashboard or with one API request. Use separate addresses for customers or orders when you need to match incoming payments. An address is a destination for a payment, not proof that the payment arrived.
Generate a receiving addressCreate an invoice for an order with an amount, currency and expiry time. Share its hosted payment link or embed checkout in your website. For a custom experience, use receiving addresses and the Account API. Store plugins and configurable widgets are planned.
Bitcoin and Litecoin payments appear in History as Pending when seen in the mempool and become Recorded when included in a block. TRX and USDT TRC20 payments are observed in TRON blocks and become final after solidification. When the current state cannot be verified, the balance is shown as unavailable. Configure a callback URL for notifications and check payment state through the API before fulfilling an order.
Follow a payment from mempool to blockManual Bitcoin and Litecoin transfers support up to 100 recipients. TRX and USDT TRC20 transfers can contain several transaction parts; check the currency-specific limits in the reference. Estimate fees before sending and save the returned payment ID. Use the same Idempotency-Key and request body when retrying a supported transfer request. Without that key, another POST can submit a separate payment intent; check History before retrying an uncertain result.
Read the transfer referenceDedicated addresses and separate balances for every account.