Operations controls section

Disputes & Ops Controls

Learn how exceptional money movement is handled across crypto payments and stablecoin-powered cards: refunds, underpayments, card transaction holds, clearing mismatches, chargebacks, freezes, AML holds, evidence packs, release decisions, customer-safe status, and daily SLAs.

5 control flows Evidence drives outcomes Ledger impact is explicit

Interactive flow lab

Resolve exceptions without losing audit truth

Switch between crypto exceptions, card transaction controls, card disputes, risk controls, and operations runbooks.

High-level sequence

Dispute and risk hold: review, then release

Freeze fast, investigate, then release funds or post the loss — always with an audit trail.

Customer Ops back-office Risk Card issuer Ledger · Treasury

1

Risk→Ops back-officeevent

A signal auto-opens a case — or the customer files a dispute.
2

Ops back-office→Ledger · Treasuryrequest

Place a hold / freeze on the funds.
3

Ledger · Treasury⇢Ops back-officeresponse

Hold applied.
4

Ops back-office→Riskrequest

Gather evidence, screening, and history.
5

Ops back-office→Card issueroff-platform

Submit dispute evidence (chargeback).
6

Card issuer→Ops back-officeevent

Outcome — won or lost.
7

Ops back-office→Ledger · Treasuryrequest

Release the hold — or post the loss / refund.
8

Ops back-office→Customerevent

Resolution notice, with the full trail.

Endpoint map

Find the operational control point

Filter exception, refund, card transaction control, dispute, ledger adjustment, case, incident, and webhook endpoints.

Concept notes

The control ideas worth remembering

Questions

Check your understanding

Pick an answer and the page will explain the reasoning.