Platform
Payments & Settlement
The failure this rail is built against is specific: one investor’s subscription money credited to another, discovered months later once tokens have been issued against it.
What it changes
- A reference, or nothingA statement line matches on its reference and on nothing else — not the amount, not the date, not the counterparty name. Matching on “when it’s obvious” is how the wrong subscription gets credited.
- Unidentified credits go to suspenseSomebody sent that money and is entitled to have it applied or returned, so it is recognised as a liability in suspense where it stays visible, rather than left off the books until it is understood.
- Investor money is never revenueIt is carried as a liability from arrival until an allocation settles. Received, screening and cleared render in caution colours rather than green, because an open obligation is not a success.
What it includes
Checksummed referencesHuman-quotable, and distinct from a subscription reference so the two are never confused on a statement.
Statement reconciliationUnder- and overpayments are exceptions for a person, never part-applied.
Clawback holdsCard and pull-rail proceeds are refused inside the chargeback window rather than warned about — a warning at 2am is a warning somebody clicks past.
Two-person settlementSettlement and refund each need a second authoriser, and the approval binds to the amount.
What this deployment does not do
Stated plainly
No payment provider adapter exists. Bank transfers, wires, custody transfers and institutional instructions are operator-recorded and reconciled; card, local rail, stablecoin and crypto report as unavailable with the reason.
See it against something real.
Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.