Crypto Payout - ON RAMP by Mesadepagos

The Crypto Payout module sends funds from a wallet created in ON RAMP to an external wallet provided by the partner. The v3 endpoint uses the same request and response contract as v2. Get a token with POST /v3/auth/login. Retrieve the source wallet and its configured assets through Wallets v3.

Endpoint

POST /v3/transactions/payouts/crypto

Headers

Header	Required	Description
`Authorization`	Yes	`Bearer <token>` JWT session
`Content-Type`	Yes	`application/json`

Create a Crypto Payout

Use this endpoint to request a crypto payout from an internal wallet to a destination address.

Request

{
  "walletId": "550e8400-e29b-41d4-a716-446655440000",
  "destinationWallet": "0x0000000000000000000000000000000000000000",
  "amount": "100",
  "asset": "USDC",
  "blockchain": "Polygon",
  "externalReference": "9dd9614e-5059-4cb5-826c-ef092fd99cb9"
}

Fields

Field	Type	Required	Description
`walletId`	string	Yes	UUID v4 of the internal wallet funding the payout.
`destinationWallet`	string	Yes	Address of the external wallet receiving the payout.
`amount`	string	Yes	Positive crypto amount as a string, with up to 8 decimal places.
`asset`	string	Yes	Asset to send, such as `USDC` or `USDT`.
`blockchain`	string	Yes	Asset blockchain, such as `Polygon` or `Ethereum`.
`externalReference`	string	Yes	Unique partner reference used for reconciliation.

Test in Sandbox

Use these parameters as a starting point for a sandbox test:

Parameter	Test value	Notes
`baseUrl`	`https://sandbox-rampa.mesadepagos.com/api`	Sandbox base URL.
`token`	`<TOKEN>`	Replace with the JWT obtained at login.
`walletId`	`550e8400-e29b-41d4-a716-446655440000`	Replace with an actual tenant wallet.
`destinationWallet`	`0x0000000000000000000000000000000000000000`	External destination wallet.
`amount`	`100`	Crypto amount to send.
`asset`	`USDC`	`USDT` is also supported.
`blockchain`	`Polygon`	`Ethereum` is also supported.
`externalReference`	`9dd9614e-5059-4cb5-826c-ef092fd99cb9`	Must be unique per operation.

curl --request POST 'https://sandbox-rampa.mesadepagos.com/api/v3/transactions/payouts/crypto' \
  --header 'Authorization: Bearer <TOKEN>' \
  --header 'Content-Type: application/json' \
  --data '{
    "walletId": "550e8400-e29b-41d4-a716-446655440000",
    "destinationWallet": "0x0000000000000000000000000000000000000000",
    "amount": "100",
    "asset": "USDC",
    "blockchain": "Polygon",
    "externalReference": "9dd9614e-5059-4cb5-826c-ef092fd99cb9"
  }'

Response

{
  "transactionId": "550e8400-e29b-41d4-a716-446655440001",
  "walletId": "550e8400-e29b-41d4-a716-446655440000",
  "destinationWallet": "0x0000000000000000000000000000000000000000",
  "amount": "100",
  "asset": "USDC",
  "blockchain": "Polygon",
  "externalReference": "9dd9614e-5059-4cb5-826c-ef092fd99cb9",
  "status": "pending_transaction",
  "message": "Payout crypto created"
}

Considerations

walletId must belong to an existing wallet of the authenticated partner.
destinationWallet must use the same blockchain sent in the request.
Use a unique externalReference per operation for reconciliation.

The destination must be a valid EVM address (0x followed by 40 hexadecimal characters). The source wallet must be active and have the selected asset configured on the requested blockchain. Replace the sample wallet identifiers and address with actual values for your environment. A successful request returns HTTP 201 with status: "pending_transaction"; this does not confirm settlement. Final status changes arrive through a withdrawal_crypto notification. See crypto transaction webhooks and the Crypto Payout API reference.

​Endpoint

​Headers

​Create a Crypto Payout

​Request

​Fields

​Test in Sandbox

​Response

​Considerations