Building payouts into your platform with the Storspay API: recipients, batches, webhooks and the sandbox

The Storspay dashboard and the Storspay API are the same product on the same rails. If your platform pays sellers, drivers, creators, agents or suppliers in any of the 26 corridors, here is how the integration is shaped.

The four objects

1. Recipients. A person or company with a country, a payout method (local bank, mobile money, or USD/GBP/EUR bank) and validated details. Create once, reuse forever. Where the local system supports it, creation returns the verified account name.
2. Payouts. One transfer to one recipient, in USD or local currency. The response includes the rate, the fee, the channel Storspay selected and the number of underlying transfers if the amount was split.
3. Batches. Up to thousands of payouts under one idempotency key, one rate lock per currency and one debit. Batches are what payroll and marketplace settlement should use.
4. Payment requests (Collections API, sandbox). Local account details and a reference your customer in-country pays; a webhook when the USD credit lands.

The webhook you must handle

payout.completed fires only when the recipient's bank or network has confirmed the credit; payout.failed carries a reason code and means the amount is already back in your balance. Never mark a seller as paid on payout.created. Webhooks are signed; verify the signature and use the event ID for idempotency — we retry until you return 2xx.

Sandbox to live

Sandbox keys work today for the Payouts and Platform APIs and the Accounts, Cards & Collections API. Sandbox corridors mirror production caps and channels, with deterministic test recipients that succeed, fail or split. Going live requires business verification (KYB) and a signed platform agreement; production keys are issued from the dashboard.

Agents

If your product is an AI agent that pays people on a business's behalf, the Agent Payouts API adds human-set caps per agent, per recipient and per day, and a machine-readable description at /.well-known/agent.json. It is live.

What we ask of integrators

• Show your users the mid-market rate and the fee separately — do not fold ours into yours silently.
• Show "completed" only on our completed event.
• Do not name our infrastructure partners in your UI; Storspay is the rail.

Start at storspay.com/developers, or write to info@storsapp.com with "API" in the subject for a sandbox walkthrough.

Who this is for — and who it is not for

Storspay is for businesses, and a sole trader counts as one. If you are a freelancer or sole proprietor trading in your own name, you open a business account of the sole-trader type. You can be paid by companies abroad, and you can pay other businesses on Storspay — including other sole traders — for work they have done for you.

What Storspay is not is a personal money-transfer service. We do not open personal accounts, and every payment has to be a business transaction: an invoice, a contract, work delivered. Money to family, gifts and personal transfers are not what this is, and we would rather say so now than at verification.