Skip to main content
Request a demo
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.

One transaction boundaryThree stacked elements — a record, a rule and a ledger posting — enclosed by a single boundary, indicating that all three commit together or not at all.ONE TRANSACTION BOUNDARYRecordwhat is trueRulewhat is permittedPostingwhat it did to the bookscommit together

What it changes

  1. 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.
  2. 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.
  3. 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.
Ask, agree, then actThree steps. One person requests, a different person approves, and only then does the state change. The approval binds to what was requested, so editing it afterwards invalidates the sign-off.Requestone personApprovea different oneActnow it movesThe approval binds to what was asked.Edit it afterwards and the sign-off is void.
Every irreversible act on this platform takes this shape, whatever the subject of the page: one person asks, a different one agrees, and only then does anything move.
The payment railMoney is matched to a subscription by its reference and no other attribute, then screened and settled. Provider adapters for card and crypto rails are not built, and are drawn as an absent component.ReferencechecksummedFunds arrivebank or custodyReconcilereference or nothingScreenAMLSettlesecond authoriserSuspense (2900)unidentified, and visibleNo reference matchProvider adaptersCard, local rail, stablecoinNot built — the registry ships empty
A reference is the only thing that matches money to a payment. Everything else is an exception for a person, and unidentified credits post to suspense where they stay visible.

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.

See it against something real.

Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.

Request Enterprise DemoBack to platform
Your instrument, against this modelAn unspecified asset on the left feeds four stages: structure, compliance policy, the offering book and the register. The asset is drawn as an outline because it is the reader's, not the platform's.Your assetwhatever it isStructurePolicyBookRegister