Skip to main content

Pay out a redemption

Pay a client's redemption out through the bank from the Cash-outs tab of a bank rail connection, including a payout from an escrow.
Open it fromAsset lifecycleBank railCash-outsRoles:Bank rail managerAuditorConsole address: /asset-lifecycle/bank-rail/connectionId/cash-outs

The Cash-outs tab on a Bank rail token page manages client redemptions paid out through the bank in either Booked movements or Supply delegate escrow mode.

The cash-outs table shows one row per cash-out with the “Client”, the “Destination account”, the “Amount”, the “Status”, the “Payout deadline” and “Created”, and the “Record cash-out” button.

Pay out a redemption

In Booked movements mode, the client first locks tokens via Request redemption in the Investor portal (see Booked movements) or POST /api/v2/tokens/{assetId}/features/register-lines/lines, then initiates a cash-out or asks a manager to record it. In Supply delegate mode, the client always initiates the cash-out directly (see Pay out from an escrow).

  1. Open Asset lifecycle → Bank rail, select the reserve token and open Cash-outs.
  2. Select Record cash-out, pick the client, an open redemption request and an active bank account, then confirm Record cash-out.
  3. If the client's rolling 24-hour cash-out total (excluding released rows) stays at or below Redemption approval threshold, approval is automatic. Above it, the row pauses at “Waiting for approval” for a different Bank rail manager to select Approve or Reject (regardless of the Bank rail approval row setting).
  4. Approved cash-outs queue for the bank's next business opening (see Set when the bank takes payments) and send one payment instruction before the payout deadline minus the settlement window.

When the bank confirms settlement, the rail burns the held tokens and marks the row “Paid” (or “Unbooked” with an operations case if the burn fails). Bank rejections, missed deadlines or account restrictions cancel the payout, return tokens and mark the row “Released” with the reason. Owner and Platform admin accounts can select Open escrow in the row menu on Supply delegate links.

If the bank later returns a settled payout (for example, a closed destination account), the row moves through “Returned, re-crediting” to “Returned, credit opened” and links to a new credit on Payments that always requires a second manager's mint approval.

Pay out from an escrow

In Supply delegate mode, one escrow per network controlled by the rail wallet locks client tokens during payout so holders cannot spend them after the bank pays.

Set up the escrow on Settings

On Settings, the Escrow card displays one of four states:

Card state
Meaning and operator step
“No escrow holds tokens for this link yet”
Select Create escrow (requires Escrow manager role) and sign with your wallet.
“Being created”
Deployment is settling on chain (refreshes every five seconds).
“Ready”
Active escrow ready for cash-outs (Owner and Platform admin also see Open escrow).
“More than one escrow matches this token link”
Cash-outs are refused until only one matching escrow remains.

During a rail wallet rotation, the card splits into Current rail wallet (“Contained”, emptied by a custodian) and Next rail wallet (where an Escrow manager selects Create escrow for the staged wallet). The API equivalent is GET/POST /api/v2/bank-rail/connections/{connectionId}/token-links/{tokenLinkId}/escrow (which returns escrow-manager-missing without the role and includes activeRailWallet during rotation).

How a Supply delegate cash-out runs

Record cash-out is disabled in Supply delegate mode because clients initiate payouts from their own wallets:

  1. The client approves the escrow for the exact cash-out amount (one exact approval per cash-out, after any prior cash-out locks).
  2. The client calls POST /api/v2/users/me/bank-cash-outs with an Idempotency-Key, amount and active bank account.
  3. The rail locks the tokens in escrow until the payout deadline (re-locking with a fresh deadline after checker approval if over threshold).
  4. On bank settlement, the rail burns the locked tokens (“Paid”). On rejection, expiry or insufficient allowance, the rail unlocks and returns them (“Releasing” → “Released”), raising an operations case for custodian forced transfer if three return attempts fail.

If a wallet restriction holds the cash-out, tokens stay locked without instructing the bank until the restriction lifts or a compliance checker approves release before the settlement window closes (see Review and release held positions). Integrations should track lock, approval and payout progress via the cash-out stream (see Follow a cash-out).

Was this page helpful?