Request money
Creates a request-money event from originator to beneficiary.
Authorizations
Path Parameters
User identifier.
Body
Credentials and corridor id for the request.
Partner request money v2 body (request-money-v2/{userToken}): beneficiary, amounts, and destination PM.
Beneficiary phone (and optionally other aliases) the platform will normalize.
Example: +525512345678.
Correlation ID
Partner provided operation identifier.
Recipient amount
Amount to receive
Recipient currency
ISO 4217 format
Destination payout method ID
required if the destinationPaymentMethod parameter is not provided.
ID of the payout method that will receive the money.
You can provide either the payout method ID using this parameter, or the full payout method object using the destinationPaymentMethod parameter.
If both parameters are provided, destinationPaymentMethodId will take precedence and destinationPaymentMethod will be ignored.
Reason
Reason for the request
Destination payout method
required if the destinationPaymentMethodId parameter is not provided.
The full payout method object that will receive the money.
You can provide either the full payout method object using this parameter, or just the payout method ID using the destinationPaymentMethodId parameter.
If both parameters are provided, this object will be ignored and destinationPaymentMethodId will take precedence.
Response
200 — OK. Request-money operation created.
Scenarios for this response:
| Scenario | How to reproduce | Typical code / body |
|---|---|---|
| Happy path | Valid userToken, corridor, destination PM, and payload. | OperationResponsePartner |
See also Full scenario matrix.
User frendly operation code for support purposes
Example: ABC123.
Operation status
Example: Sent, Funding, Funded, Accepted, Rejected, ReadyForPickup, Completed, Failed, OnHold, InTransit, Cancelled.
Indicates if the operation can be cancelled by the funder user.
User ID
ID of the user who performed the operation.
Data about the reason why the operation was ignored by the funder user.
Indicates if the operation was ignored by the funder user.
Attribution link
Link to the operation.
Recipient user information
Sender user information
Estimated exchange rate for the operation.
Destination payment method
Source payment method
Currency code
ISO 4217 format.
Example: USD for United States Dollar, MXN for Mexican Peso.
Reason. Free text.
Example: Hi! I need money.
Operation status details
Correlation ID
Partner provided operation identifier.