Submit a deposit

Once you’ve sent the order’s USDC to deposit_address on Base, send us the transaction hash (the ID of your transfer). We check the transfer covers the order and start the payout.

Only for orders where deposit_submission_required is true. Automatic orders (every NGN order, and some KES M-Pesa phone and till orders) don’t need this, because we spot the transfer ourselves. Calling this for one returns 409.

Endpoint

POST https://merchant.minisend.xyz/api/offramp/orders/{order_id}/deposit

Authorization: Bearer ms_live_your_key_here

Requires the offramp scope. Orders you don’t own return 404.

Body

string

required

The ID of the Base transaction where you sent the USDC to deposit_address. It starts with 0x followed by 64 letters and numbers. Each transaction can only pay for one order. Using one twice returns 409.

Example

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"}'

const res = await fetch(
  `https://merchant.minisend.xyz/api/offramp/orders/${orderId}/deposit`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer ms_live_your_key_here',
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ transaction_hash: txHash }),
  }
);

if (res.status === 422) {
  // transfer could not be verified. Check amount/chain/hash and retry
}
const order = await res.json(); // status: "settling" on success

Response (200)

The full order object with status: "settling":

{
  "order_id": "9b2f6c1e-...",
  "status": "settling",
  "amount_usdc": 10,
  "deposit_tx_hash": "0x55a572efe1720250e442f38741477a4fc3f7f152e5cd208cc52f8222a1c2a13b",
  "rate": 129.52,
  "amount_local": 1295,
  "fee": 13,
  "...": "..."
}

The order’s rate, amount_local, and fee now show the actual payout, at the live rate. From here, watch for completed by checking the order or with the offramp.completed webhook. Sending the same hash again after it’s been accepted is harmless. You just get the order back as it is now.

Errors

Status	Meaning
`400`	`transaction_hash` doesn’t look like a transaction ID (`0x` plus 64 letters and numbers)
`404`	We can’t find this order, or it isn’t yours
`409`	The order is automatic (no hash needed), it’s already finished or expired, or this hash was already used for another order
`422`	We couldn’t match the transfer: it was too small, on the wrong network, or sent to the wrong address. The order stays `pending`, so fix it and try again
`429`	You’ve sent more than 20 of these in the last minute. Wait a moment and try again

A 422 means the payout did not start. Check that you sent exactly total_deposit_usdc, in USDC, on Base, to the order’s deposit_address, then send the hash again. If the order expires while you’re sorting it out, send the order_id and hash to support.

Overview

Endpoints

Off-ramp endpoints

Onramp endpoints

Wallet API endpoints

Submit a deposit

Endpoint

Body

Example

Response (200)

Errors

​Endpoint

​Body

​Example

​Response (200)

​Errors

Endpoint

Body

Example

Response (200)

Errors