Off-ramp quickstart

This guide sends 10 USDC to a Kenyan M-Pesa number, then shows what’s different for Nigerian bank accounts. Before you start, you need:

An API key with off-ramp switched on. See getting access.
A wallet you control with some USDC on Base.

Quote the payout

Add the recipient, and we’ll check their account and give you the name it’s registered to, all in the same call.

curl -X POST https://merchant.minisend.xyz/api/offramp/quote \
  -H "Authorization: Bearer ms_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 10,
    "currency": "KES",
    "recipient": {
      "method": "MOBILE",
      "account_name": "Jane Wanjiku",
      "phone": "0712345678",
      "mobile_network": "Safaricom"
    }
  }'

{
  "amount_usdc": 10,
  "currency": "KES",
  "rate": 128.57,
  "amount_local": 1285,
  "fee": 0,
  "recipient_amount": 1285,
  "estimated_total_deposit_usdc": 10.12,
  "deposit_submission_required": false,
  "recipient_name": "JANE WANJIKU",
  "expires_at": "2026-07-05T12:05:00.000Z"
}

recipient_amount is what lands in the recipient’s account. deposit_submission_required tells you which way the order will go. This one is automatic, so nothing comes off the payout and a small sender fee is added to what you send instead. When an order asks you to send and confirm, the quote is a close estimate, fee comes off the payout, and there’s no estimated_total_deposit_usdc.

Create the order

Add an Idempotency-Key header with a value that’s unique to this payout. If your request times out and you send it again, we’ll recognise it and won’t create a second order.

curl -X POST https://merchant.minisend.xyz/api/offramp/orders \
  -H "Authorization: Bearer ms_live_your_key_here" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: payout-8412" \
  -d '{
    "amount": 10,
    "currency": "KES",
    "refund_address": "0xYourWalletAddress0000000000000000000000",
    "reference": "payout-8412",
    "recipient": {
      "method": "MOBILE",
      "account_name": "Jane Wanjiku",
      "phone": "0712345678",
      "mobile_network": "Safaricom"
    }
  }'

{
  "order_id": "9b2f6c1e-...",
  "status": "pending",
  "amount_usdc": 10,
  "total_deposit_usdc": 10.12,
  "sender_fee_usdc": 0.12,
  "transaction_fee_usdc": 0,
  "currency": "KES",
  "rate": 128.57,
  "amount_local": 1285,
  "fee": 0,
  "recipient_amount": 1285,
  "deposit_address": "0x7a3d1c9e5b2f4a6c8e0d1b3f5a7c9e1d3b5f7a9c",
  "deposit_chain": "base",
  "deposit_submission_required": false,
  "expires_at": "2026-07-05T12:05:00.000Z",
  "instructions": "Send exactly 10.12 USDC (Base), shown as total_deposit_usdc (the order amount plus fees), to deposit_address before expires_at. A smaller amount is not credited and is refunded to refund_address. The deposit is detected automatically: do not submit a transaction hash for this order."
}

We check the recipient’s account before creating anything. If the account isn’t valid, you get a 422 and no order is created.

Send USDC on Base

From your own wallet, transfer exactly total_deposit_usdc USDC on Base to deposit_address before expires_at.

Send exactly total_deposit_usdc, in USDC, on Base. On automatic orders, a smaller amount isn’t accepted and goes back to your refund_address. You also only have a few minutes, so create the order when you’re ready to send. When an order asks you to send and confirm, you have 30 minutes.

Confirm your transfer (only if asked)

Skip this step when deposit_submission_required is false, as it is for the order above. We spot the transfer ourselves, and calling this endpoint returns 409.When it’s true, send us the transaction hash (the ID of your transfer, starting with 0x):

curl -X POST https://merchant.minisend.xyz/api/offramp/orders/9b2f6c1e-.../deposit \
  -H "Authorization: Bearer ms_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"transaction_hash": "0x55a572efe1720250e442f38741477a4fc3f7f152e5cd208cc52f8222a1c2a13b"}'

A 200 with "status": "settling" means the payout is on its way. A 422 means we couldn’t find a matching transfer. Check the amount, the network, and the hash, then try the same call again.

Check it's done

Check the order’s status, or wait for the webhook:

curl https://merchant.minisend.xyz/api/offramp/orders/9b2f6c1e-... \
  -H "Authorization: Bearer ms_live_your_key_here"

When the payout lands, status becomes completed, settlement_receipt holds the payout receipt, and an offramp.completed webhook fires. See off-ramp webhooks.

NGN payouts

NGN orders pay out to bank accounts and are always automatic, like the one above. The only difference is how you describe the recipient: a bank institution code and an account_number. See recipients. Get the bank codes from GET /api/offramp/institutions instead of typing them into your code.

curl -X POST https://merchant.minisend.xyz/api/offramp/orders \
  -H "Authorization: Bearer ms_live_your_key_here" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: payout-8413" \
  -d '{
    "amount": 100,
    "currency": "NGN",
    "refund_address": "0xYourWalletAddress0000000000000000000000",
    "recipient": {
      "account_name": "Chidi Okafor",
      "institution": "GTBINGLA",
      "account_number": "0123456789"
    }
  }'

Automatic orders only stay open for a few minutes, because the rate is fixed when you create them. Create the order when you’re ready to send, ideally with the transfer automated. If time runs out, the order expires and you can simply create a new one. If a payout fails after you’ve sent your USDC, it goes back to your refund_address by itself.

Get Started

Dashboard

Payments

Off-ramp API

Onramp API

Wallet API

Webhooks

Help

Off-ramp quickstart

NGN payouts

​NGN payouts

NGN payouts