Developers
A transfer API without blockchain concepts
Create a confirmed transfer, receive signed status events and reconcile through stable identifiers. The partner interface does not expose wallets, addresses, chains, gas or private keys.
API principles
Built to be operated, not only called
Seven contracts your engineering team can rely on across versions.
REST endpoints with versioned request and response contracts
Mandatory idempotency keys on writes
Partner client-reference identifiers on every transfer
Amounts represented in minor units with explicit currencies
Signed webhooks with replay protection and per-transfer sequence numbers
Stable machine-readable errors and visible current state
Daily reconciliation and billing reports
POST /v1/transfers Idempotency-Key: <uuid> { "destination_country": "FR", "source_amount_amd": 4318500, "source_currency": "AMD", "confirmed": true, "client_reference_id": "partner-88213" }
201transfer.created
Authenticated documentation carries the full payload, market-specific fields and the complete state model.
Integration sequence
Six steps to production
Scoping fixes the engineering estimate before any commercial commitment is asked of you.
- 1Qualification and technical scopingCorridor fit, licences, volumes and the engineering estimate are established first.
- 2Credentials and API walkthroughYour team receives credentials and the full integration reference.
- 3Transfer and webhook integrationCreate transfers, consume signed events and hold state on your side.
- 4State, refund and reconciliation testingExercise terminal states and the refund path before any customer traffic.
- 5Security and compliance reviewYour security, legal and compliance teams review controls and evidence.
- 6Controlled production launchA closed group of customers, with written success criteria agreed in advance.
Talk to us
Put the endpoint in front of your engineers
Credentials and the full integration reference are shared when a partner conversation opens.