Every rail
One system
SEPA, SEPA Inst, SWIFT and domestic rails
One ledger underneath every payment flow
built for the rails
Six primitives. Every flow posts to Core
Multi-rail orchestration
SEPA, SEPA Inst, SWIFT and domestic rails
One API surface. One ledger
Real-time settlement
Posted to the ledger the instant the rail confirms. No batch reconciliation
IBAN & BIC routing
Account addressing across SEPA and SWIFT, with BIC lookup and validation
ISO 20022 native
pacs.008, pain.001, camt.054, structured at the wire, not parsed after
Returns & recalls
Reversals modeled as first-class entries, with lineage to the original
Limits & screening
Volume, Frequency and beneficiary checks
live signal
Right now, on the wire
Pulled live from the testnet ledger. New entries land here as the rails confirm
Cleared today
TPS
p99 lat.
Success
in the system
Payments writes here
So does every other module
Payment lifecycle
One payment. End to end
From the API call to the posted entry, seven moments, every one observable
- T+001Submit
- T+34ms02Validate
- T+182ms03Screen
- T+340ms04Route
- T+1.2s05Clear
- T+8.4s06Post
- T+12s07Confirm
POST /v1/payments
Request reaches the API. Idempotency key reserved, payload validated against the schema. Response 202 returned immediately
Get started
Wire one rail today
The system handles the rest
Connect one corridor today. SEPA SCT, SEPA Instant, SWIFT, internal. Every leg posts to Core, settles in the same back office, shows up in the same app.