v18

latestOpenAPI 3.1.0raw.githubusercontent.com2026-08-013469188.5 KB

Processing

Refund a failed deposit

Transfer the funds from a failed deposit back to a user-provided address on the same chain. Authenticate with an x-api-key (write scope) or a Bearer platform token; the credential must belong to the client that registered the account.

post/deposits/refund

Headers

x-api-keystring

API key for authentication (omit when sending Authorization)

Example:your-api-key

API key for authentication (omit when sending Authorization)

authorizationstring

Bearer platform token (e.g. forwarded by user-service). Takes precedence over x-api-key when both are present.

Example:Bearer eyJhbGciOi...

Bearer platform token (e.g. forwarded by user-service). Takes precedence over x-api-key when both are present.

Request body

chainstring required

CAIP-2 chain identifier of the deposit (e.g. "eip155:8453")

txHashstring required

Source transaction hash of the stuck deposit

accountstring required

Managed account address that received the deposit (EVM address or Solana public key)

tokenstring required

Source token address. Use the zero address (0x000…000) for native transfers.

recipientstring required

Address to receive the refunded tokens (EVM address or Solana public key)

Example request

{
  "chain": "eip155:8453",
  "txHash": "0xabc123...",
  "account": "0xde0fdf9c06b404cc5e20543cb84cac9067102f19",
  "token": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48",
  "recipient": "0x742d35Cc6634C0532925a3b844Bc9e7595f5bE91"
}

Response

Deposit refunded successfully

messagestring required

transactionHashstring required

amountstring required