Payout · Global payouts

One call, payouts to any market worldwide

Batch payouts for payroll, suppliers and global payments — including long-tail countries that banking rails serve poorly.

See the API Book a demo

Where it’s used

Global payroll EOR services Supplier settlement Rewards distribution

Trusted by payment companies and proven in production

AlchemyPayTransakInfiniTruBit

01What you get

Built for batch, safe by default

Everything a payout run needs: throughput, address safety and exact-amount delivery.

High-throughput batching

Large payout runs with automatic retries and status tracking.

Smart address management

Address books and whitelists reduce mispayment risk.

Unified fee management

Fee Station prepays network fees: send 5,000 and they receive exactly 5,000.

Fiat at T+1

Compliant payout rails support same-name and third-party transfers.

02Withdrawal controls

Three independent confirmations before money moves

Break any one of them and the money still doesn’t move.

1 · Request verification

Password and 2FA, signed API requests and IP whitelists on every request.

2 · Risk policies

Lists, limits, frequency rules and multi-step approval workflows. Approve anywhere with Cobo Guard.

3 · Your own final check

A callback inside your own network screens every signature — even if every other layer were breached, only you can move funds.

03Developer guide

One request pays the whole batch

Secure by default from the first request, with a sandbox that runs the full flow.

Read the developer guide

payout-batch

// Illustrative shape. Replace from the developer portal.
POST /v2/payments/payouts/batch
{
  items: [
    { recipient: "rcp_41ab", amount: "5000.00", token: "USDT" },
    { recipient: "rcp_77cd", amount: "1250.00", token: "USDT" }
  ]
}

// Fee Station prepays network fees, so a payout of
// 5,000 USDT arrives as exactly 5,000 USDT.

// Events are pushed as they happen. Verify every one.
{
  event:     "payment.confirmed",
  order_ref: "ord_00417",
  status:    "credited",
  screened:  true
}

// Funds that fail screening are never credited.
// They are returned to the sender and recorded for audit.

Endpoint names and payloads are illustrative and get replaced from the developer portal.

04Compliance

Compliance built in, not bolted on

Every transfer is screened before it settles, and funds that fail screening are returned to the sender.

SOC 2 Type I and Type II ISO 27001 Hong Kong TCSP and Trust registration Lithuania crypto license US MSB registration

See the full trust record

05Your questions

Straight answers on payouts

How do recipients receive the exact amount?

Fee Station prepays network fees, so a payout of 5,000 arrives as exactly 5,000. Fees are handled centrally instead of being deducted from each transfer.

What stops a payout going to the wrong address?

Address books and whitelists reduce mispayment risk, and every withdrawal passes three independent confirmations before it moves.

Who approves a payout run?

You define the risk policies: lists, limits, frequency rules and multi-step approval workflows, with approvals from anywhere via Cobo Guard.

Which countries can we pay into?

Any market a stablecoin can reach, including long-tail countries that banking rails serve poorly. Payout channels and pricing vary by region — the Cobo team can confirm specifics for yours.

Ready to run your first payout batch

You get a working test environment within a week and a 45-minute scoping call with our payments lead.

Book a demo Read the Docs