Payment intents

Endpoints

Paths are relative to the environment base URL — on the sandbox, https://pay.rsends.io/api/backend. See Environments.

Create an intent

The amount is denominated in the settlement token (e.g. 100 means 100 USDC), not in fiat. Send the token you want to be paid in and, optionally, the destination wallet.

curl -X POST https://pay.rsends.io/api/backend/api/v1/merchant/payment-intent \
  -H "Authorization: Bearer rsend_test_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 100,
    "currency": "USDC",
    "chain": "base_sepolia",
    "recipient": "0xYourDestinationWallet00000000000000000000",
    "expires_in_minutes": 30,
    "metadata": { "order_id": "ORD-1024" }
  }'

Where the money goes

An intent cannot exist without a resolvable on-chain recipient — that is the non-custodial invariant, enforced at creation. The recipient you pass wins; if you omit it, RSends falls back to your organisation's settlement wallet (set in Settings). If neither resolves, creation fails with 422 SETTLEMENT_WALLET_MISSING rather than defaulting to some address. A wallet claimed by more than one organisation fails with 422 SETTLEMENT_WALLET_AMBIGUOUS.

The response

The response echoes the intent plus an onchain object — the exact, non-custodial instructions the payer's wallet executes. There is no deposit address and no custodial key anywhere in it.

{
  "intent_id": "pi_9f1c4a7e2b5d8036c1e94ab7d2508f63",
  "reference_id": "a1b2c3d4e5f6a7b8",
  "onchain_invoice_id": "0x9f…",          // bytes32, derived from reference_id + chain id
  "amount": 100.0,
  "currency": "USDC",
  "chain": "base_sepolia",
  "recipient": "0xyourdestinationwallet00000000000000000000",
  "status": "pending",
  "expires_at": "2026-08-06T12:30:00+00:00",
  "created_at": "2026-08-06T12:00:00+00:00",
  "completed_at": null,
  "tx_hash": null,
  "metadata": { "order_id": "ORD-1024" },
  "onchain": {
    "invoiceId": "0x9f…",
    "merchant":  "0xyourdestinationwallet00000000000000000000",
    "token":     "0x036cbd53842c5426634e7929541ec2318f3dcf7e",
    "amount":    "100000000",             // base units (USDC has 6 decimals) — what YOU receive
    "fee":       "600000",                // 0.60 USDC — read live from the router's quoteFee
    "total":     "100600000",             // amount + fee — what the PAYER parts with
    "maxFee":    "600000",                // payer's ceiling; pay() reverts above it
    "chainId":   84532,
    "router":    "0x2Ec353815F2Cd382628d0D399F8d80959C1758CA",
    "routerVersion": 1,                   // 1 = deployed sandbox router (fee); 2 = fee-less
    "function":  "pay",                   // "pay" (ERC-20) | "payNative" (ETH)
    "decimals":  6,
    "isNative":  false,
    "permitType": "eip2612",              // "eip2612" → permit flow; "none" → approve + pay
    "feeUnavailable": false
  }
}

Hosting the checkout

There is no checkout_url field in the response — you compose the URL from the intent_id:

https://demo.rsends.io/pay/pi_9f1c4a7e2b5d8036c1e94ab7d2508f63

That page re-fetches the intent and its onchain instructions, then drives the payer's wallet — see Hosted checkout.

Fees: what the sandbox does today

Your principal always arrives whole. Nothing is ever deducted from what settles into your wallet — RSends never touches the transfer. What differs between the two routers is whether the payer is charged something on top.

Intent lifecycle

Cancel an intent

Cancel a still-pending intent to stop accepting payment for it. Cancellation is an off-chain state change — there are no funds to return, because none were ever held. Any other state returns 400 INVALID_STATE.

Resolve a held payment

An intent in review (a late payment under late_payment_policy: "review") waits for your decision. Post {"action": "complete"} to accept it — which fires a payment.completed_late webhook — or {"action": "refund"} to mark it refunded for your books. Any other state returns 400 INVALID_STATE. See Refunds.

Errors you should handle

Full table, envelope shapes and rate limits: Errors.