Collect an on-ramp payment
Collects from a registered counterparty’s mobile-money payment
destination and pays the proceeds into one of your own wallets,
executed asynchronously against a quote from
POST /v1/quotes?type=onramp. The roles are the reverse of an
off-ramp: senderId is the counterparty who pays (a beneficiary
record in your association), paymentDestinationId is the payment
destination the collection debits, and walletId is your wallet the
payout lands in. Pricing is never accepted from the caller; it is
resolved server-side from the quote.
The wallet must be verified (403 otherwise). The counterparty’s
classification must match the corridor the quote was priced for, and
the fields the connector requires must be present on the
counterparty and payment destination; a submission that falls short
returns a 422 with field-level detail. notifyEmail and
notifyWhatsApp notify your own business, at the email or mobile
number on your registered profile. Returns 202.
Authorizations
Access token issued by POST /v1/auth/token.
Application secret (the apiKey issued at registration), required on every request.
Body
Your transaction id. Replaying it returns the original result.
Your own wallet the payout lands in.
The paying counterparty, a beneficiary registered in your association.
The counterparty's payment destination the collection debits.
A quote from POST /v1/quotes?type=onramp.
Purpose of remittance. Discover values via GET /v1/payments/enums.
Optional sender-side transaction reference. When supplied: 1-16 characters, letters, digits, and hyphens only. Omit it or send null for no reference.
16^[A-Za-z0-9-]{1,16}$Optional recipient-side transaction reference. When supplied: 1-16 characters, letters, digits, and hyphens only. Omit it or send null for no reference.
16^[A-Za-z0-9-]{1,16}$The counterparty's source of funds, when the connector requires it.
ISO 3166-1 alpha-2 country that issued the counterparty's ID, when the connector requires it.
Your source of funds, when the connector requires it.
Notify your business by email at the address on your registered profile. Mutually exclusive with notifyWhatsApp.
Notify your business by WhatsApp at the mobile number on your registered profile. Mutually exclusive with notifyEmail.
Response
On-ramp accepted for asynchronous processing.
A 202 means the submission was accepted for asynchronous execution, not that it settled. Track completion with the Transactions routes or webhooks.
The transaction record id, used with GET /v1/transactions/{transactionId}.
Submission status; not a terminal transaction status.
"accepted"
Execution intent id, when present.
True when this response replays a prior submission with the same transactionId.