Redeem cAROUSD

Burn cAROUSD from a custodial wallet and receive public test stablecoin 1:1. Settlement is asynchronous: the transaction moves PENDING → SETTLING → SETTLED, with the payout hash in settlementTxHash. Settlement advances lazily when the transaction is read; poll GET /transactions/{id} until terminal.

POST /redeem

Redeem cAROUSD

cURL

curl --request POST \
  --url https://aropay.aro.media/api/v1/redeem \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "walletId": "ckwlt0001abcd",
  "amount": "10"
}
'

201

{
  "ok": "<unknown>",
  "data": {
    "transaction": {
      "id": "<string>",
      "chainId": 123,
      "amount": "<string>",
      "token": "<string>",
      "txHash": "<string>",
      "settlementTxHash": "<string>",
      "explorerUrl": "<string>",
      "fromAddress": "<string>",
      "toAddress": "<string>",
      "counterparty": "<string>",
      "walletId": "<string>",
      "error": "<string>",
      "metadata": "<unknown>",
      "createdAt": "2023-11-07T05:31:56Z",
      "updatedAt": "2023-11-07T05:31:56Z"
    }
  }
}

Authorizations

apiKeyAuthsessionCookie

Authorization · string · header · default: aro_sk_your_key_here · required

AroPay API key, sent as Authorization: Bearer aro_sk_…. Created in the dashboard under Settings → API keys. Takes precedence over a session cookie when both are present.

Body

application/json

walletId · string · required

amount · string · required

Decimal string in human units.

Response

201

application/json

Redeem transaction (typically SETTLING on return).

ok · any · required

data · object · required

Show child attributes