Fraud & Disputes
The fraud-routing blueprint supports allow, step-up, hold, or block decisions on the authorization path. When a cardholder disputes, the disputes blueprint organizes the evidence and the applicable Reg E or Reg Z clock for accountable review.
Authorize
Card and account-to-account authorizations, in flight.
Decide in-flight
Returns allow / step-up / hold / block for a supplied payment, with checks aimed at avoiding unsupported friction.
efficientIn-flight authorization runs on a latency budget as much as a token budget.
Verify
Out-of-band verification when Tripwire requests step-up. Open work. No Cadre blueprint is assigned to this step yet.
Holds and edge cases go to the human queue.
Dispute
Cardholder claims open Reg E / Reg Z investigation clocks.
Separates interim timing obligations from the dispute merits and records each status for review.
frontierDispute merits under Reg E / Reg Z carry the hard reasoning here.
Recover
Network recovery on merchant liability. Open work. No Cadre blueprint is assigned to this step yet.
The walkthrough
- 1
Tripwire illustrates allow / step-up / hold / block routing on the authorization path, with explicit checks against over-blocking.
Open example capture - 2
Friction is a decision too: step-up goes to the customer, holds go to fraud ops.
- 3
When a cardholder disputes, Arbiter records interim action, timeline status, and merits status separately under the applicable Reg E or Reg Z path.
- 4
Cadre does not yet cover network recovery.