One vendor for international wires. Another for mobile-wallet disbursements in Africa. A third for push-to-card. A fourth for on-chain. Each with its own API, its own funding model, its own settlement cycle, its own reconciliation file. Treasury's full-time job becomes managing the vendors instead of moving the money.
One API across every destination rail. Fund once from your Pockyt treasury balance; disburse to banks, wallets, cards, or on-chain addresses through the same call. Reconciliation rolls up against the same ledger as the rest of your money movement. The treasury team writes policy, not vendor management.
The default. A single API call moves a defined amount from your Pockyt balance to a specified destination — bank account, wallet, card, or on-chain address. Idempotent, signed, reconciled.
For marketplace seller settlements, affiliate payouts, payroll-adjacent flows: submit a batch as a single API call or CSV upload. Pockyt processes in parallel, reports back per-payout success, and aggregates fees and FX in one statement.
For platforms that want payout policy expressed as code rather than scheduled jobs: define rules in Programmable Logic ("when seller balance > $1,000 USD-equivalent and no holds, pay out via local rail Mondays") and Pockyt executes against them.
# Payout to a customer account via Standard ACH curl https://mapi.pockyt.io/v3/payouts/pay \ -H "Pockyt-Request-ID: 41236589756324879" \ -H "Accept: application/json" \ -H "Content-Type: application/json" \ -d '{ "merchantNo": "202333", "storeNo": "301854", "verifySign": "8b11e8f0d7f2a412f020f266110b57ba", "customerNo": "2000305228292319592008", "accountToken": "2010305228303182765718", "invoiceId": "9aae4c685d824c5da746f97620c59eb5", "amount": "1.0", "currency": "USD", "ipnUrl": "https://example.com/webhooks", "processingChannel": "STANDARD_ACH", "memo": "thank you", "note": "Cold drink", "subject": "Payouts", "merGroupNo": "100001" }'
01
100+ destination countries
Bank rails in every major market, mobile-wallet rails in growth markets, card-push where it's the right rail, on-chain where stablecoin is the right asset.
02
Single or batched
One-shot API calls for individual payouts, or batched submissions for marketplace settlements and bulk disbursements.
03
Cross-currency native
Source from any Pockyt balance, disburse in any of 27 fiat currencies or USDC. FX applied at mid-market with transparent spread.
04
Idempotency built-in
Every payout call takes an Idempotency-Key. Safe to retry. Duplicate payouts are impossible by design.
05
Crypto payouts
Native USDC payouts to on-chain addresses, with the same reporting and reconciliation as fiat payouts. No separate vendor.
06
One ledger, all outbound
Payouts reconcile against the same Pockyt ledger as collections and treasury. One export, one source of truth.
Marketplaces paying sellers in 5+ countries today are usually managing multiple payout vendors and reconciling across them. Consolidating onto Pockyt collapses the vendor count, the operational overhead, and the FX cost in one move.
Recurring batched payouts to large affiliate or partner networks. The combination of batched submission, cross-currency native support, and rule-driven scheduling tends to remove 80%+ of the manual work.
Companies that hold operating reserves in USDC but need to pay vendors, employees, or partners in local fiat. Pockyt handles the conversion and the local-rail disbursement as a single operation.
Talk to our team about consolidating your payout operations onto one programmable layer.