Use cases

Four agents. Four ways the money does not come back.

Each of these roles commits money or moves it. Most approval workflows start with the amount. What matters first is how much of your recovery survives once the instruction has gone out, and the action and its rail decide that.

Reddix is pre-general-availability and works with design partners. The four roles below are the ones it designs its controls around, not case studies, and there are no customer results on this page because there are none to report yet.

Find your agent · There is no universal undo →
Procurement · raising POs

The tier changes under you.

A purchase order passes through three tiers while its amount stays the same.

One purchase order, three tiers A purchase order on the tier scale over its life. As a draft it is Tier 0, freely reversible, and is logged. Once issued it is Tier 1, compensable, and Reddix arms cancellation. When the supplier accepts, the same order steps up to Tier 2, past the point where the gate starts, and an amendment or release against it is held above your threshold. The amount never changes. PROCUREMENT ACCOUNTS PAYABLE TREASURY SUPPORT DRAFT ISSUED AMEND OR RELEASE TIER 0Freely reversible TIER 1Compensable TIER 2Hold before commit TIER 3Irreversible GATE LOGGED CANCELLATION ARMED HELD ABOVE YOUR THRESHOLD SUPPLIER ACCEPTS THE SUPPLIER’S RELIANCE MOVED IT UP THE SCALE. PROCUREMENT PAYABLES TREASURY SUPPORT DRAFT LOGGED TIER 0 TIER 1 TIER 2 TIER 3 ISSUED CANCELLATION ARMED TIER 0 TIER 1 TIER 2 TIER 3 SUPPLIER ACCEPTS AMEND OR RELEASE HELD ABOVE YOUR THRESHOLD TIER 0 TIER 1 TIER 2 TIER 3 THE SUPPLIER’S RELIANCE MOVED IT UP THE SCALE. DASHED AMBER: WHERE THE GATE STARTS.
What Reddix does: classifies the order when it is issued and arms cancellation, which stays yours to make until the supplier accepts. From acceptance, or from the moment the supplier starts acting on it, amending the order or releasing against it is Tier 2, and above your threshold Reddix holds that instruction for a second person.
Accounts payable · paying invoices

The riskiest action moves no money.

Approving an invoice is the obvious exposure. Changing where the vendor is paid is the quieter one.

The change that moves no money A vendor bank-detail change moves nothing on the day it happens. It is Tier 2, hold before commit, and Reddix holds it for maker-checker approval. Every later payment to that vendor inherits the new account, and those payments are where payment approvals look. Once the change is released there is no reversal of the exposure it creates: only correction going forward, plus recovery attempts on payments already misdirected. PROCUREMENT ACCOUNTS PAYABLE TREASURY SUPPORT THE CHANGE VENDOR BANK DETAILS Moves $0 on the day it happens. TIER 0 TIER 1 TIER 2 TIER 3 HELD FOR MAKER-CHECKER EVERY LATER PAYMENT Payment, to the new account Payment, to the new account Payment, to the new account and every one after it WHERE PAYMENT APPROVALS LOOK ONCE RELEASED: NO REVERSAL OF THE EXPOSURE, ONLY CORRECTION GOING FORWARD, PLUS RECOVERY ATTEMPTS ON PAYMENTS ALREADY MISDIRECTED. PROCUREMENT PAYABLES TREASURY SUPPORT THE CHANGE VENDOR BANK DETAILS Moves $0 on the day it happens. TIER 0 TIER 1 TIER 2 TIER 3 HELD FOR MAKER-CHECKER EVERY LATER PAYMENT Payment, to the new account Payment, to the new account Payment, to the new account and every one after it WHERE PAYMENT APPROVALS LOOK ONCE RELEASED: NO REVERSAL OF THE EXPOSURE. ONLY CORRECTION GOING FORWARD, PLUS RECOVERY ATTEMPTS ON PAYMENTS ALREADY MISDIRECTED.
What Reddix does: treats a master-data change (here, the vendor’s bank details) as a financial action in its own right, not only the payments that follow it. It holds the change for maker-checker approval, so whoever releases it is never whoever made it.
Treasury · moving cash

The rail decides, not the instruction.

The same payment instruction gets a different amount of protection on each rail.

One instruction, three rails, three tiers One instruction, send 40,000 dollars, forks by the rail it goes out on. On an ACH inside the return window it is Tier 1, compensable: Reddix arms compensation, and undo depends on the window and an accepted reason. On a wire or an instant rail it is Tier 2: held above your threshold, and undo depends on the receiving side's goodwill. Settled on-chain it is Tier 3, irreversible: it is approved first or blocked, and no undo exists. The gate starts between Tier 1 and Tier 2. PROCUREMENT ACCOUNTS PAYABLE TREASURY SUPPORT ONE INSTRUCTION Send $40,000 ACH, in return window Wire or instant rail Settled on-chain TIER 0 Freely reversible TIER 1 Compensable TIER 2 Hold before commit TIER 3 Irreversible GATE COMPENSATION ARMED UNDO: WINDOW & REASON HELD ABOVE YOUR THRESHOLD UNDO: THEIR GOODWILL APPROVE FIRST, OR BLOCK UNDO: NONE EXISTS PROCUREMENT PAYABLES TREASURY SUPPORT ONE INSTRUCTION Send $40,000 ACH, IN RETURN WINDOW COMPENSATION ARMED TIER 0 TIER 1 TIER 2 TIER 3 UNDO: WINDOW & REASON WIRE OR INSTANT RAIL HELD ABOVE YOUR THRESHOLD TIER 0 TIER 1 TIER 2 TIER 3 UNDO: THEIR GOODWILL SETTLED ON-CHAIN APPROVE FIRST, OR BLOCK TIER 0 TIER 1 TIER 2 TIER 3 UNDO: NONE EXISTS
What Reddix does: tiers the instruction by the rail it actually goes out on. The same payment is released with compensation armed on one rail and, above your threshold, held before release on another. Where nothing reverses it, Reddix says so rather than promising an undo.
Support · refunds and credits

Cheap individually, expensive in aggregate.

Each refund is small and compensable. The failure is how many, how fast.

Refunds stay at one tier while the total climbs; a credit moves up when the customer is told A support agent issues refunds one after another, faster and faster. Every refund is Tier 1, compensable, and each on its own is well under your materiality threshold. The running total climbs until it crosses the threshold: velocity raises effective materiality without changing the tier, so compensation is armed and you are notified. Separately, a credit is Tier 1 while it sits in your books and Tier 2 once the customer has been told, where it is held above your threshold. PROCUREMENT ACCOUNTS PAYABLE TREASURY SUPPORT REFUNDS, ONE AFTER ANOTHER TIER 1 Compensable, for every one of them VELOCITY RAISES EFFECTIVE MATERIALITY COMPENSATION ARMED, AND NOTIFY YOUR MATERIALITY THRESHOLD EACH REFUND ON ITS OWN SITS WELL UNDER IT A CREDIT IN YOUR BOOKS TIER 1 TOLD TO THE CUSTOMER TIER 2 HELD ABOVE YOUR THRESHOLD THE REFUNDS NEVER CHANGED TIER. THE TOTAL DID. PROCUREMENT PAYABLES TREASURY SUPPORT REFUNDS, ONE AFTER ANOTHER TIER 1 Compensable, every one VELOCITY RAISES EFFECTIVE MATERIALITY: COMPENSATION ARMED, AND NOTIFY YOUR THRESHOLD EACH REFUND ON ITS OWN SITS WELL UNDER IT A CREDIT IN YOUR BOOKS TIER 1 TOLD TO THE CUSTOMER TIER 2 HELD ABOVE YOUR THRESHOLD THE REFUNDS NEVER CHANGED TIER. THE TOTAL DID.
What Reddix does: treats velocity and first-time payees as signals that raise effective materiality, which is how much scrutiny an action gets, without moving its tier. A run of small refunds can cross a threshold none of them would alone. At Tier 1, high materiality means compensation armed and a notification; nothing is held. A credit granted and told to the customer in one step is Tier 2, and above your threshold Reddix holds it before the message goes out.
Framework §2 The four tiers, and what places an action in one A commitment’s tier depends on contractual formation and counterparty reliance. A movement’s depends on the finality law of its rail: how firmly that rail treats a payment as done. Every tier placement on this page traces to §2’s own lists. Read §2, the reversibility tier model →

Which of these is running in your stack?

The exposure report runs thirty days in shadow mode, read-only, with nothing in your payment path.

Start with the exposure report · See how a held action actually works →