How Rein is designed

Who does what

The lender sets rules, funds the line, holds credit risk and decides where a person must sign off. Rein is being built to check payments, explain results and refer the cases its rules require. The borrower spends within the lender's rules. Money never passes through Rein.

The weekly-line design

The earlier design uses four steps: set the mandate, approved payees, categories and caps; fund a weekly spending line; check each payment and record its reason; collect actual spend and start the next cycle. This describes the design, not a claim that a live lender is using it today.

Rules, business and market context

The proposed payment-permit layer covers mandate, payees, categories, per-payment and total caps, stops on new draws and officer approval. The richer verification-agent work considers a borrower's history, business fit, merchant legitimacy and market prices. These are separate layers, not a duplicate-invoice product alone.

Where it fits

Existing lending and factoring are the starting point. A business account, card, invoice-finance process or platform-credit flow can provide the place to check before payment. People and software agents are both possible payment initiators.

How to measure it

Simple before-and-after loss comparisons can mislead when controls tighten at times of higher risk. The research considers threshold comparisons, randomized control strength and staged rollouts. Simulation results are not measured losses on real borrowers.

What you can inspect

The full synthetic report preserves policy profiles, invoice findings, concentration and reconciliation detail. The homepage bakery animation is a separate simple explanation. See the report guide.

Questions