Start
Quickstart
From first conversation to a tested integration.
An integration has two directions: Speedy calls you, and you call Speedy. This page shows the shape of both. The exact endpoints and keys come in your onboarding pack.
The steps
- Write to partners@speedymoneytransfer.com with your corridors, payout methods and onboarding process.
- We reply with our diligence pack and a technical walkthrough.
- Agree the commercial and compliance terms with us.
- Receive sandbox access and a webhook signing secret through a secure channel.
- Implement the operations below, then run the test scenarios with us.
- Both sides sign off before production access is enabled.
What Speedy calls on your side
| Operation | Purpose |
|---|---|
| List corridors | The currency pairs, countries and payout methods you support. |
Quote | A price for a corridor, method and amount, with an expiry. |
| Create payout | Start a payout. Must be idempotent on our transfer id. |
| Get payout | Read the current status of a payout. |
| Cancel payout | Stop an accepted payout that has not started. May answer too late. |
Statement | What you say you paid out up to a given time. Read-only; used for daily reconciliation. |
What you call on Speedy
One thing: a signed webhook for each payout status change. See Webhooks.
A payout request
{
"idempotencyKey": "trf_8f2c41d0a7b3e955",
"quoteId": "q_demo_000123",
"recipient": {
"method": "bank_account",
"fullName": "Example Recipient",
"account": "0000000000",
"bankCode": "000"
},
"sendAmount": { "amount": "250.00", "currency": "USD" }
}Respond with your own reference and the payout's status. Repeat the same reference if we retry with the same idempotency key.
{
"partnerRef": "pr_demo_7c91d2",
"status": "submitted"
}