Fiat or crypto in. Global payouts via API.

Pay from fiat balances or convert supported crypto into fiat for local and cross-border payouts. Connect bank transfers, international payments and available e-wallets for supplier payments, business payroll and platform disbursements.

Get started
Read payout API docs
Funding source
Recipient destination

Conversion & payout

You fund

USDT

Recipient gets

USD

Local transfer

Any supported funding asset, subject to your active balance, an available conversion quote and an approved payout route.

Illustration only. No transfer is submitted.

Payouts built around your business.

One funding flow. Different payout needs.

Supplier payments

How this payout works

  1. 01

    Choose your funding

    Use a fiat balance in an eligible account or deposit supported crypto into your DogPay wallet.

  2. 02

    Convert when needed

    DogPay converts crypto into supported fiat. Fiat balances can fund payouts directly on eligible routes, with currency conversion where needed.

  3. 03

    Supplier payments

    Partner banks or payment institutions deliver fiat to recipient accounts. Track the final payout status.

From request to reconciliation.

Prepare recipients and balances, create the instruction, then track the final result. Bank payouts and on-chain withdrawals use separate APIs.

  1. Prepare the destination

    Register the bank recipient or confirm the on-chain address and network.

  2. Check the funding

    Select an eligible balance; prepare bank payout materials or estimate the network fee.

  3. Create and track

    Submit the instruction and reconcile the final result using the documented status flow.

Global Payouts

View bank payout endpoints

API access, required documents and coverage depend on the selected payout channel and account review.

  1. GET/open-api/v1/payout/payee-options
  2. POST/open-api/v1/payout/payee
  3. GET/open-api/v1/payout/accounts
  4. POST/open-api/v2/payout/create
  5. GET/open-api/v1/payout/detail
Read payout API docs

Control every instruction.

Request identity

Use callId for idempotency and keep your entity context explicit.

Completion visibility

Order creation is not delivery. Track the final status through the relevant detail API and webhook.

Review and availability

Recipient checks, KYT, supporting documents and channel rules apply. Fees and timing vary by route.

FinCEN MSBFINTRAC MSBHong Kong TCSP

Entity-specific disclosures, not a bank charter. DogPay is not a bank; see the applicable entities and service scope.

See compliance

Before you integrate

Can crypto fund a bank payout?

Yes, eligible crypto wallet balances can fund bank payouts under the selected route. The receiving bank gets the supported fiat currency; availability and conversion conditions must be confirmed.

Is this the same as Payment-as-a-Service?

Payment-as-a-Service focuses on accepting customer payments. Global Payouts focuses on sending funds to recipients; Global Accounts provides the account infrastructure.

Does one API cover every destination?

No. Bank payouts use Payout V2; external on-chain transfers use the wallet withdrawal API. Supported routes and API permissions must be checked separately.

Are batch payouts or instant arrival guaranteed?

Supplier payments, business payroll and platform disbursements are supported use cases. Share destination countries, recipient count, frequency and amounts so the team can assess channels, processing and expected timing.

Build your payout integration.

Confirm your markets, funding balances and recipient types, then start with the matching API guide.

Read payout API docs