Live · API access on request

Every agent framework has a tool for web search. None has a tool for paying a real person in a market the card rails don't reach.

Storspay is the payout tool for AI agents: one MCP tool call sends a real payment — same-day, into Africa and Latin America — inside limits a human sets in advance.

Live today. Request access and we'll send keys and docs once your business clears KYB.

Thanks. Your request is in. Keys and docs come to this address once KYB clears.
Hmm, that didn't go through. Try again or email info@storsapp.com.

One all-in rate. Storspay never holds your funds — see Disclosures.

No spam · We email you about your keys, nothing else

Agent payouts · MCP Live

Let an AI agent pay real people.

One MCP tool call sends a payout inside a mandate a human set in advance. For agent builders and AI-native teams.

Try the mandate simulator ↓
Platform & Marketplace API · REST Live

Embed payouts in your own checkout.

Instant payouts for gig, creator and outsourcing platforms. Escrow (hold & release) for marketplaces. Webhooks, sandbox keys, revenue share.

See endpoints & run the checkout simulator ↓
Accounts, Cards & Collections · REST Sandbox

Accounts and cards for the people you pay. Payments in from Africa.

Open a USD account for any seller or worker, issue a card that spends from it, collect from buyers in Africa, and pay in USD, GBP or EUR. Same keys.

See the four surfaces ↓
Live interface · v1
// The agent's toolbelt already has search.
// This adds payouts.
await storspay.createPayout({
  mandate_id: "mnd_...",       // permission a human granted
  recipient_id: "rcp_...",     // must be on the approved list
  amount_usd: 300,
  idempotency_key: "..."       // safe to retry
});
Try it

Set the limits. Then try to break them.

This simulator runs entirely in your browser. Set a mandate on the left, then fire scenarios on the right — the outcomes respond to your settings, because that's the product.

Simulated demo · no real money moves · the live API behaves the same way

Set the agent's limits

Used this month: $0 of $50,000
// Try a scenario →

That refusal is the product.

Every block is logged, every limit is set by a human, and no agent can widen its own permission.

Request API access →
The limits are the product

Why a finance team will actually allow an agent to pay people.

An agent that can move money is only deployable if the money can't move outside lines a human drew. Every payout runs inside a mandate:

01

Approved people only

The agent pays only recipients a human put on an approved list. Anyone else is refused, logged, and left for a human to add.

02

Capped per payment and per month

Hard ceilings on any single payout and on the month's total. When the cap is reached, the agent stops — it cannot raise its own limit.

03

Allowed countries only

Payouts go only into corridors the human switched on. Everything else refuses on corridor, before any money is touched.

04

Big payments wait for a human

Anything above the approval threshold stops and waits. A named person approves it before it moves — no exceptions, no override flag.

05

Instant pause

A human can pause every agent on the account instantly. Paused means paused: pending runs freeze and nothing new executes.

Built on open protocols

No proprietary SDK. Nothing to install.

The interface is built on the standards agent frameworks already speak, so calling Storspay is no different from calling any other tool.

MCP — Model Context Protocol

The tool surface is an MCP server. Every major agent framework supports MCP, so any agent can call Storspay payouts with no custom work on either side.

AP2-style mandates

The mandate structure is modelled on the AP2 intent / cart / payment pattern: the human grants a scoped, signed permission in advance, and every payout is checked against it.

Agent card for discovery

A machine-readable agent card at /.well-known/agent.json describes the capabilities and authorization model, so agents and directories can discover the service.

Why this doesn't exist yet

Agent payments today are about agents buying things.

The agent-payments wave so far is agents buying from merchants — checkout, carts, cards. Almost nobody is building for agents that pay people: the annotators, contributors, sellers and delivery teams that platforms owe money to every week. And the payout rails that do exist stop at a handful of countries. Ours don't — they reach the corridors where this workforce actually is, across Africa and Latin America.

Platform & Marketplace API · REST

Integrate once. Every vendor, worker and seller gets paid through your own checkout.

A REST API for platforms and marketplaces that owe money to people in Africa, Latin America and Asia. Create a recipient, create a payout, get a webhook when it lands — 2–5 minutes later, in local currency. Pay out instantly, or hold funds in escrow until delivery is confirmed. Sandbox keys to build, production keys after KYB.

2–5 min
from API call to money in the recipient's bank or mobile wallet
26 corridors
one integration, every country — including Nigeria and Ghana
sk_test_ · sk_live_
sandbox and production keys · Bearer auth · 100 req/min
Earn on volume
revenue share on every payout plus a lifetime rate discount

Three calls. That's the integration.

Everything lives under /api/v1/ and is authenticated with your API key as a Bearer token. Build against sk_test_ keys in the sandbox — nothing moves — then switch the prefix to sk_live_ when KYB clears.

  1. Create a recipient once — name, country, currency and their bank or mobile-money details. You get back a recipientId to reuse forever.
  2. Create a payout in USD with your own reference. The response quotes the fee, the exchange rate and the exact local amount before anything settles.
  3. Listen for the webhook — payout.completed arrives when the money lands, usually within 2–5 minutes.
Gig & freelance platformsAI data-labellingCreator & royalty payoutsOutsourcing & BPOCross-border marketplaces
Request sandbox keys →Run the simulator ↓
POST /api/v1/recipientscurl
curl https://app.storspay.com/api/v1/recipients \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Amara Okafor",
    "email": "amara@example.com",
    "country": "NG",
    "currency": "NGN",
    "bankAccount": { "bankCode": "058", "accountNumber": "0123456789" }
  }'

// 201 Created
{ "recipientId": "rcp_8f2k…", "status": "verified" }
POST /api/v1/payoutsinstant · default
curl https://app.storspay.com/api/v1/payouts \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{ "recipientId": "rcp_8f2k…", "amountUsd": 250,
        "reference": "order_10492" }'

// 201 Created
{ "payoutId": "pay_3n7q…", "status": "processing",
  "fee": 5.00, "exchangeRate": 1329.17,
  "localAmount": 325647.00, "currency": "NGN",
  "estimatedDelivery": "2–5 minutes" }

Instant payouts. Money lands in 2–5 minutes.

The default mode. Your platform calls POST /api/v1/payouts, funds leave your Storspay wallet immediately and arrive in the recipient's bank account or mobile-money wallet in local currency. Same rails as our payroll product — triggered by your code instead of a person.

created
your API call
processing
seconds
completed
2–5 min · webhook

Built for platforms that pay on a schedule or on demand: weekly gig earnings, per-task data-labelling payments, creator revenue, monthly contractor invoices. Batch as many calls as you need — rate limit is 100 requests a minute per key, and every payout carries your own reference so reconciliation is a join, not a hunt.

If a payout fails — a wrong account number, say — funds return to your wallet automatically and you receive payout.failed with the reason. Recipients never open an account, install an app or see anything but local currency.

Request sandbox keys →Try an instant payout ↓
GET /api/v1/payouts/pay_3n7q…status
{
  "payoutId": "pay_3n7q…",
  "reference": "order_10492",
  "status": "completed",
  "amountUsd": 250.00,
  "fee": 5.00,
  "exchangeRate": 1329.17,
  "localAmount": 325647.00,
  "currency": "NGN",
  "recipient": { "recipientId": "rcp_8f2k…", "country": "NG" },
  "createdAt": "2026-09-06T14:02:11Z",
  "completedAt": "2026-09-06T14:05:48Z"
}
GET /api/v1/payouts?status=completed&from=2026-09-01list · filters
{ "data": [ …47 payouts… ], "hasMore": false,
  "totals": { "amountUsd": 11840.00, "fees": 236.80 } }

Escrow. Hold at checkout, release on delivery.

Built for marketplaces. Create the payout with "escrow": true and the funds are secured from your wallet but not disbursed — the payout sits in held. Your buyer sees "Payment secured". When delivery is confirmed, call POST /api/v1/payouts/:id/release and the vendor is paid in the usual 2–5 minutes.

created
checkout
held
funds secured
released
you confirm delivery
completed
vendor paid
  1. Buyer view: Payment secured → Funds held → Delivered. Vendor view: Payment pending → Payment released → Funds received. Both are yours to render — we send the state changes.
  2. Cancel a held payout any time with POST /api/v1/payouts/:id/cancel — funds return to your wallet instantly and you get payout.refunded.
  3. 14-day safety net: a payout still held after 14 days is refunded to your wallet automatically, with a payout.refunded webhook. No money ever gets stuck.
Physical-goods marketplacesServices marketplacesSourcing & commoditiesMilestone-based freelance work
Request sandbox keys →Try hold & release ↓
POST /api/v1/payoutsescrow
{ "recipientId": "rcp_8f2k…", "amountUsd": 1200,
  "reference": "order_20817", "escrow": true }

// 201 Created — funds secured, nothing disbursed yet
{ "payoutId": "pay_9k2e…", "status": "held",
  "fee": 24.00, "localAmount": 1563103.00, "currency": "NGN",
  "holdExpiresAt": "2026-09-20T14:02:11Z" }
POST /api/v1/payouts/pay_9k2e…/releasedelivery confirmed
// 200 OK — disbursing to the vendor now
{ "payoutId": "pay_9k2e…", "status": "processing",
  "releasedAt": "2026-09-09T09:41:03Z",
  "estimatedDelivery": "2–5 minutes" }
POST /api/v1/payouts/pay_9k2e…/cancelor refund
{ "payoutId": "pay_9k2e…", "status": "refunded",
  "refundedToWallet": 1224.00 }

Webhooks. Every state change, signed and retried.

Register a webhook URL when your partner account is created (or override it per payout with callbackUrl). We POST every payout state change with your reference attached, sign each delivery with HMAC-SHA256 using your webhook secret, and retry failed deliveries three times — after 30 seconds, 2 minutes and 10 minutes.

payout.createdpayout accepted
payout.processingfunds in flight
payout.completedmoney landed
payout.failedreturned to wallet
payout.heldescrow secured
payout.releasedescrow released
payout.refundedcancelled or 14-day timeout

Verify the signature by computing HMAC-SHA256 over the raw body with your secret and comparing it to the Storspay-Signature header. Treat events as idempotent — the same payoutId and status may arrive twice if a retry overlaps.

Request sandbox keys →
POST https://yourplatform.com/webhooks/storspaypayout.completed
Storspay-Signature: t=1757167548,v1=5f1e9a…
Content-Type: application/json

{
  "event": "payout.completed",
  "payoutId": "pay_3n7q…",
  "reference": "order_10492",
  "status": "completed",
  "amountUsd": 250.00,
  "localAmount": 325647.00,
  "currency": "NGN",
  "recipient": { "recipientId": "rcp_8f2k…", "name": "Amara Okafor" },
  "timestamp": "2026-09-06T14:05:48Z"
}
verify · nodeHMAC-SHA256
const sig = crypto.createHmac('sha256', WEBHOOK_SECRET)
  .update(rawBody).digest('hex');
if (sig !== headerV1) return res.status(400).end();
// respond 2xx within 10s — otherwise we retry (30s → 2m → 10m)

Every endpoint, on one screen.

All routes live under https://app.storspay.com/api/v1/, require Authorization: Bearer <key>, return JSON and follow OpenAPI 3.0. Full request/response schemas ship with your keys.

MethodPathWhat it does
Recipients
POST/recipientsCreate a recipient — name, email, country, currency, bank or mobile-money details. Optional payoutMethod: local_currency (default), usd_ach, gbp_fp, eur_sepa or storspay_account. Returns recipientId.
GET/recipientsList all recipients for your platform.
GET/recipients/:idFetch one recipient.
Payouts
POST/payoutsCreate a payout: recipientId, amountUsd, reference, optional callbackUrl, optional escrow (default false). Returns payoutId, status, fee, exchangeRate, localAmount, estimatedDelivery.
GET/payouts/:idPayout status and details.
GET/payoutsList payouts — filter by status, date range, recipient.
POST/payouts/:id/releaseRelease an escrowed payout (status held → disbursed in 2–5 min).
POST/payouts/:id/cancelCancel a held payout — funds return to your wallet.
Account & market data
GET/balanceYour current wallet balance.
GET/earningsAccumulated revenue share and pending payout of earnings.
GET/corridorsAll live corridors with current rates, limits and channel availability (bank / mobile money).
GET/rates/:corridorCurrent exchange rate for one corridor.

Auth: Bearer API key (sk_test_ sandbox · sk_live_ production) · Rate limit 100 requests/min per key · Keys are generated, rotated and revoked by Storspay; your platform's admin sees usage stats.

Request sandbox keys →

You integrate once. You earn on every payout.

Platform partners pay the same transparent all-in rate as everyone else — 2% per payout, covering conversion, settlement and local delivery, with no API fee and no monthly minimum. Then two things only API partners get:

Rate
2%
all-in per payout, by corridor. No FX markup, no API fee.
Revenue share
≈0.1–0.2%
of your payout volume, credited to your earnings ledger on every completed payout.
Lifetime discount
Set at signup
a permanent reduction on your rate for integrating — agreed per partner, never expires.

Earnings accrue per payout and are visible any time via GET /api/v1/earnings or your partner dashboard. We pay accumulated earnings out monthly to your bank account or your Storspay wallet.

Talk to us about partner terms →
// worked example · one $1,000 payout · Nigeria fee charged to you $20.00 (2% all-in) your lifetime discount −$2.00 (e.g. 10% off the fee) you pay $18.00 your revenue share +$1.50 (share of our margin) ────────────────────────────────────────── net cost of the payout $16.50 → 1.65% all-in bank wire, same payout ~$60.00 (~6%) + 3–5 days // GET /api/v1/earnings { "totalEarnings": 4218.40, "pendingPayout": 612.75, "lastPayoutAt": "2026-09-01T00:00:00Z" }

Illustrative figures. Your discount and revenue-share percentage are set in your partner agreement.

Try it

Run a marketplace checkout. Watch the money move.

This simulator runs entirely in your browser. Pick instant or escrow, fire the API calls on the right, and watch the buyer and vendor screens on the left update — exactly the states your webhook handler will receive.

Simulated demo · no real money moves · sandbox behaves the same way
Your platform wallet$25,000.00
Buyer seesorder_20817 · $1,200
·
Awaiting checkoutNothing has happened yet
Vendor seesAmara Okafor · Lagos
·
No payment yetWaiting for the platform
Your revenue share this session$0.00
// Start by creating a recipient →

That's the whole vendor-payment flow.

Your checkout calls one endpoint, the vendor is paid in local currency in minutes, and every state change reaches your webhook — signed. Request sandbox keys and build this against real endpoints today.

Request sandbox keys →
Accounts, Cards & Collections API · REST

Same keys, four more surfaces. Accounts, cards, collections, transfers.

Open a USD account (with GBP and EUR details) for any seller, worker or organisation. Issue them a card that spends from it. Collect from buyers in Africa by bank transfer or mobile money. Move money between accounts instantly, with optional escrow. All under /api/v1/, the same Bearer keys, the same webhook envelope. Build against the sandbox today; production follows verification of your business and each account holder.

Accounts
/virtual-accounts · USD account in the holder's name, GBP + EUR details alongside, after hosted verification
Cards
/cards · virtual in seconds, physical by post; spend controls; PAN never returned — 60-second reveal token
Collections
/collections · payment requests from 26 corridors; bank or mobile money; USD credited on arrival
Transfers
/transfers · account-to-account, instant; escrow with release / cancel; cash-out to any destination

A USD account for anyone you pay. One call.

Post the holder — a person, a business or an organisation — and you get back a pending account and a hosted verification link. When they pass, the account activates with a US routing and account number in their name, plus UK sort-code and EUR IBAN details. Deposits arrive by the same webhook path as your platform wallet.

  1. Create the holder with an externalRef from your system — the same ref twice returns the same account, never a duplicate.
  2. Send them the kycUrl — a hosted flow with your name on it. Sandbox holders named "Test Approved" pass instantly.
  3. Settle sales into it with POST /transfers for 0.5% — instant, no rail — or let buyers and employers pay the account details directly.
Marketplace sellersContractors paid from abroadDelegations & organisationsCreators & agencies
Request sandbox keys →What holders can do with it →
POST /api/v1/virtual-accountscurl
curl https://app.storspay.com/api/v1/virtual-accounts \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{
    "holder": { "externalRef": "seller_4471", "type": "individual",
                "displayName": "Amara Okafor", "email": "amara@example.com",
                "phone": "+2348012345678", "country": "NG",
                "dateOfBirth": "1991-04-12" },
    "currency": "USD"
  }'

// 201 Created
{ "virtualAccountId": "va_9k2m…", "holderId": "hld_2f7a…",
  "status": "pending_kyc", "kycUrl": "https://verify.storspay.com/…" }
webhook · virtual_account.kyc_updatedthen GET /virtual-accounts/:id
{ "virtualAccountId": "va_9k2m…", "status": "active",
  "usd": { "routingNumber": "0210…", "accountNumber": "9876…",
           "bankName": "…", "accountHolderName": "Amara Okafor" },
  "gbp": { "sortCode": "04-00-…", "accountNumber": "3310…" },
  "eur": { "iban": "IE…4471", "bic": "…" },
  "balanceUsd": 0.00 }

A card that spends from the balance.

Issue a virtual Storspay Card the moment an account is active, or a physical one shipped to the holder. Every authorisation is checked against the balance in real time and declined in plain language when it can't clear. Controls — per-transaction, daily and monthly caps, allowed countries, blocked merchant categories, ATM and online toggles — are yours, the holder's, or an organisation manager's for delegate cards.

  1. Issue — POST /cards (virtual, instant) or POST /cards/physical (shipped; activated with last-4 + date of birth).
  2. Control — PATCH /cards/:id to freeze, set spend controls, report lost. validFrom / validUntil for trip cards.
  3. Reveal safely — the PAN is never in an API response. POST /cards/:id/reveal-token returns a 60-second single-use token your app exchanges in the holder's own session.

Three active cards per individual, twenty-five per organisation. Virtual cards are free; physical $10. USD purchases carry no fee; other currencies 1.5%.

Request sandbox keys →
POST /api/v1/cardsvirtual · instant
curl https://app.storspay.com/api/v1/cards \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{ "virtualAccountId": "va_9k2m…",
        "cardholderName": "Amara Okafor",
        "spendControls": { "perTxnUsd": 500, "monthlyUsd": 3000,
                           "allowedCountries": ["NG","US","GB"],
                           "atm": false, "online": true } }'

// 201 Created
{ "cardId": "crd_7t3p…", "form": "virtual", "last4": "4471",
  "expiry": "09/29", "status": "active" }
webhook · card.declinedplain-language reason
{ "event": "card.declined", "data": {
    "cardId": "crd_7t3p…", "amountUsd": 640.00,
    "merchant": { "name": "…", "mcc": "5732", "country": "US" },
    "declineReason": "per_transaction_limit",
    "message": "Above this card's $500 per-purchase limit" } }

Payouts, in reverse.

A collection is a payment request: you say who's paying, from which country, by bank or mobile money, and how much — in their currency or in USD. You get back local payment instructions and a reference to show them. When they pay, the funds convert and credit the account you named — your platform wallet or a holder's account — and collection.credited fires. 2% all-in, mid-market rate on arrival.

  1. Create with creditTo, country, method, amount and the payer's details. Amounts above a channel cap return several references in one collection.
  2. Show the instructions — bank or paybill details rendered as Storspay's, plus the reference and an expiry countdown.
  3. Handle the states — pending → received → converting → credited. Late or mismatched payments are credited and flagged, never lost. Above $25,000 a review state sits before credited.
African buyers → diaspora sellersTuition & medical feesExporters & distributorsRepatriation
Request sandbox keys →See the product →
POST /api/v1/collectionscurl
curl https://app.storspay.com/api/v1/collections \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{ "creditTo": { "virtualAccountId": "va_9k2m…" },
        "country": "KE", "currency": "KES", "amountUsd": 980,
        "method": "bank_transfer",
        "payer": { "name": "Riverside Medical Group",
                   "source": { "accountType": "bank", "accountNumber": "…" } },
        "reference": "inv_2026_0147", "expiresInMinutes": 1440 }'

// 201 Created
{ "collectionId": "col_5r8w…", "status": "pending",
  "quotedRate": 129.44, "amountLocal": 129437, "feeUsd": 20.00,
  "expectedUsd": 980.00, "expiresAt": "2026-09-10T14:02:00Z",
  "paymentInstructions": [{ "reference": "STORS-KE-4K7P2Q",
     "bankName": "…", "accountNumber": "…", "amountLocal": 129437 }] }
webhook · collection.creditedterminal event only
{ "event": "collection.credited", "data": {
    "collectionId": "col_5r8w…", "receivedLocal": 129437,
    "effectiveRate": 129.41, "creditedUsd": 980.22,
    "creditTo": { "virtualAccountId": "va_9k2m…" } } }

Move money between accounts. Or out in USD, GBP, EUR.

POST /transfers moves USD from your platform wallet or a holder's account to another account (instant, free between holders, 0.5% from a platform), or out to any destination — a local bank or mobile wallet through least-cost routing, or a US, UK or European bank account for a flat fee. Escrow works here too: escrow:true holds until you release or cancel, with a 14-day auto-refund.

USD, GBP and EUR payouts are the same shape on /payouts: create the recipient with payoutMethod: usd_ach | gbp_fp | eur_sepa and their bank details (ABA routing, sort code or IBAN — checksum-validated), and the payout delivers the exact amount with no conversion: flat $5, £4 or €4.50. Or payoutMethod: storspay_account to land it instantly in their Storspay Account.

Seller settlementCash-outUSD contractorsUK & EU suppliersOrganisation → delegate
Request sandbox keys →
POST /api/v1/transfersplatform → seller account
curl https://app.storspay.com/api/v1/transfers \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{ "from": { "kind": "partner_wallet" },
        "to": { "virtualAccountId": "va_9k2m…" },
        "amountUsd": 1200, "reference": "order_10492",
        "escrow": false }'

// 201 Created
{ "transferId": "trf_2c9x…", "status": "completed",
  "feeUsd": 6.00, "arrival": "instant" }
POST /api/v1/payoutsUSD · GBP · EUR recipient
curl https://app.storspay.com/api/v1/payouts \
  -H "Authorization: Bearer sk_test_51Hx…" \
  -d '{ "recipientId": "rcp_gbp_71…",   // payoutMethod: gbp_fp
        "amountUsd": 1000, "reference": "inv_884" }'

// 201 Created
{ "payoutId": "pay_8d1k…", "status": "processing",
  "channel": "gbp_fp", "exchangeRate": 0.7385,
  "localAmount": 738.45, "feeGbp": 4.00,
  "estimatedDelivery": "within hours" }

The four surfaces, on one screen.

Same base URL, auth, pagination and error envelope as the Platform API. Resources belonging to another partner return 404, never 403. New error codes: kyc_not_approved, holder_frozen, limit_exceeded, card_limit_reached, balance_not_zero, collections_unavailable.

MethodPathWhat it does
Storspay Accounts
POST/virtual-accountsOpen an account for a holder (or an existing holderId). Returns pending_kyc + kycUrl; activates with USD, GBP and EUR details.
GET/virtual-accounts · /:id · /:id/transactionsList, fetch, and read the ledger — deposits, collections, transfers in/out, card settlements, fees.
POST/virtual-accounts/:id/kyc-linkRegenerate the hosted verification link.
DELETE/virtual-accounts/:idClose an account — balance must be zero.
Storspay Cards
POST/cards · /cards/physicalIssue a virtual card instantly, or a physical card to a shipping address.
GET/cards · /:id · /:id/transactionsList cards, fetch one, read authorisations, settlements, reversals and refunds.
PATCH/cards/:idFreeze / unfreeze, update spendControls, activate a physical card, report lost.
POST/cards/:id/reveal-token60-second, single-use token to show PAN and CVV in the holder's session. Never returned by the API itself.
DELETE/cards/:idCancel a card.
Collections — "Receive payment"
POST/collectionsCreate a payment request: creditTo, country, currency, amountLocal or amountUsd, method, payer, reference, expiresInMinutes. Returns instructions, quoted rate, fee, expected USD.
GET/collections · /:idList and fetch — status pending / received / converting / credited / expired / cancelled / failed.
POST/collections/:id/cancelCancel a pending request.
Transfers
POST/transfersfrom partner wallet or account → to account, @handle, or a payout destination (local, USD·ACH, GBP, EUR). Optional escrow.
GET/transfers · /:idList and fetch; the seven payout statuses reused.
PATCH/transfers/:id{ "action": "release" | "cancel" } for escrowed transfers; 14-day auto-refund otherwise.

Webhooks: virtual_account.*, card.*, collection.*, transfer.* — same envelope and Storspay-Signature as payouts, retried 30 s / 2 min / 10 min. Sandbox: holders named "Test Approved" / "Test Rejected"; simulated deposit, collection-received and card-purchase endpoints.

Request sandbox keys →
Coverage

Africa, Latin America and Asia, live now.

The payout rails under this API are live today, moving B2B cross-border payroll. Twenty-six corridors, added to quarterly.

West & Central Africa

Ten corridors live
🇳🇬 Nigeria
🇬🇭 Ghana
🇨🇮 Côte d'Ivoire
🇸🇳 Senegal
🇨🇲 Cameroon
🇹🇬 Togo
🇧🇯 Benin
🇧🇫 Burkina Faso
🇬🇦 Gabon
🇨🇬 Congo-Brazzaville

East & Southern Africa

Nine corridors live
🇰🇪 Kenya
🇺🇬 Uganda
🇹🇿 Tanzania
🇷🇼 Rwanda
🇿🇲 Zambia
🇲🇼 Malawi
🇪🇹 Ethiopia
🇧🇼 Botswana
🇿🇦 South Africa

Latin America & Asia

Seven corridors live
🇲🇽 Mexico
🇧🇷 Brazil
🇨🇴 Colombia
🇦🇷 Argentina
🇪🇨 Ecuador
Asia
🇰🇭 Cambodia
🇱🇰 Sri Lanka
What it costs

Same pricing as the rest of Storspay. No API fee.

2% all-in per payout, depending on corridor — the same rate as every other way of using Storspay. That one rate covers conversion, settlement and local delivery. No separate API fee, no hidden FX markup, no monthly minimum.

Timeline

Where this is, honestly.

Now · Live

Agent-callable rails + Platform API

The payout rails are live and moving payroll today. The MCP tool for agents and the REST Platform & Marketplace API (instant payouts, escrow, webhooks) both sit on top of them. Verified businesses get keys on request. The Accounts, Cards & Collections surfaces are in sandbox on the same keys; production opens per business after verification.

Framework SDKs

Packaged integrations for the agent frameworks people actually use, driven by what the access list tells us they're building.

2027

Self-serve keys

Instant keys after automated KYB, no human in the loop on our side. Until then, a person reviews every access request.

Developer FAQ

The questions you'd type into a search box.

The tool surface is MCP — the Model Context Protocol — which every major agent framework already supports. Any agent that can call an MCP tool can call Storspay payouts with no custom integration work on either side. There is no proprietary SDK and nothing to install.
Every agent operates inside a mandate a human sets in advance: a cap per payment, a cap per month, an approved recipient list, an allowed-country list, and a threshold above which payments stop and wait for human approval. The agent cannot widen any of its own limits, and a human can pause every agent instantly.
No. Recipients receive local currency directly in the bank account or mobile-money wallet they already have. They never sign up for anything, install an app, or touch crypto.
Twenty-six corridors are live today: Nigeria, Ghana, Côte d'Ivoire, Senegal, Cameroon, Togo, Benin, Burkina Faso, Gabon, Congo-Brazzaville, Kenya, Uganda, Tanzania, Rwanda, Zambia, Malawi, Ethiopia, Botswana, South Africa, Mexico, Brazil, Colombia, Argentina, Ecuador, Cambodia and Sri Lanka — local currency delivered the same business day. New corridors are added quarterly.
The API is live. Request access on this page; once your business completes KYB we issue keys and documentation, typically within a few business days.
The same as the rest of Storspay: 2% all-in per payout, with no separate API fee, no hidden FX markup and no monthly minimum. The rate covers conversion, settlement and local delivery.
Same rails, two front doors. The agent payouts API is an MCP tool for AI agents, wrapped in human-set mandate limits. The Platform & Marketplace API is a conventional REST API (/api/v1/, Bearer keys, webhooks) for platforms that want to embed payouts in their own checkout or vendor-payment flow — with instant payouts or escrow.
Create the payout with "escrow": true. Funds are secured from your wallet but not disbursed — the payout sits in "held" and your buyer sees "Payment secured". When delivery is confirmed you call the release endpoint and the vendor is paid in local currency in 2–5 minutes. You can cancel a held payout at any time, and anything still held after 14 days is refunded to your wallet automatically. Every step arrives at your webhook.
Yes. Sandbox keys (prefix sk_test_) let you build and test every endpoint and webhook without moving money. Production keys (sk_live_) are issued once your business clears KYB. Requests are limited to 100 per minute per key.
Yes. Platform partners receive a revenue share on every completed payout — roughly 0.1–0.2% of payout volume, credited to an earnings ledger you can read via GET /api/v1/earnings and paid out monthly — plus a lifetime discount on your rate, agreed at signup.
Yes. POST /virtual-accounts opens a USD account (with GBP and EUR details) in the seller's name after a hosted verification; POST /cards issues a virtual or physical Storspay Card that spends from it. Settle sales into the account with POST /transfers for 0.5%. Your checkout shows "Powered by Storspay" and nothing else.
Yes. POST /collections creates a payment request with local bank or mobile-money instructions and a reference. When the buyer pays, USD is credited to your wallet or the seller's account and collection.credited fires. 2% all-in at the mid-market rate on arrival; large amounts split under local caps automatically.
Yes. Create the recipient with payoutMethod: usd_ach, gbp_fp or eur_sepa and their bank details. The payout delivers the exact amount with no conversion for a flat $5, £4 or €4.50 — in the same batch as your local-currency payouts.

Ready to pay real people — from your platform or your agent?

Request access and tell us what you're building: a marketplace, a payout platform, an AI agent. Sandbox keys, production keys and docs follow KYB, and your answer shapes what we ship next.

Thanks. Your request is in. Keys and docs come to this address once KYB clears.
Hmm, that didn't go through. Try again or email info@storsapp.com.

One all-in rate. Storspay never holds your funds — see Disclosures.

B2B only · KYB required · No personal remittances

Investor? See the investor thesis →