National switch connection
An adapter written against an internal contract rather than a protocol, with a simulator that reproduces the awkward cases — a timeout after a financial effect, a contradictory late rejection — before a real connection exists.
Banks, e-money issuers and institutions that need to reach or join a national scheme, and the regulators supervising them.
Part of the platform itself: it is present wherever BitriPay runs.
The problem
Integrations with a scheme are usually written against its protocol. When the profile changes, or a second scheme appears, the business logic has to be rewritten because the protocol leaked into it.
How it works
- Payments are expressed in an internal canonical form that presumes no particular protocol.
- An adapter translates between that form and whatever the scheme actually speaks.
- A simulator reproduces the awkward outcomes, labelled as simulation throughout.
- The certified codec is loaded only for a connection whose certification is recorded.
What you can check
Facts about the running platform rather than adjectives. Each one is visible in the product, the API reference or the ledger.
- The internal contract presumes nothing about the wire format — not ISO 8583, not ISO 20022, not REST — so the protocol never reaches the business logic.
- The simulator reproduces a timeout after a financial effect, a provisional not-found, a duplicate success, a contradictory late rejection, an invalid signature and an acknowledgement without completion.
- Everything the simulator produces is labelled as simulation and it never attests certification.
- A certified adapter is loaded only for a connection whose certification state says so.
- Aggregation fees on switch payments are accrued per completed payment and invoiced per period, never posted onto the payment itself.
What it costs
Scheme and aggregation fees are set in the console and shown on the merchant’s statement as their own line.
Questions
Why build before the profile is published?
Because the hard part is not the wire format — it is the behaviour around it: what happens on a timeout that had a financial effect, or a rejection that contradicts an earlier success. Those can be built and tested now, and the format becomes a codec later.
Does the simulator prove you are certified?
No, and it says so on everything it produces. It proves the behaviour was built and tested. Certification is a separate, recorded state, and the certified adapter loads only for a connection that has it.
How are the switch fees charged?
Accrued per completed payment and invoiced per period and per currency. They are never posted onto the payment itself, so the payment amount is the payment amount and the fee is a separate, visible obligation.
Read next
Smart Route
Routing scored from measured success rates, cost and latency per connector, with a circuit breaker that takes a failing rail out before your customers find it.
Corridor network
A corridor records which phase it is in, under whose licence and with which custody model — as data, so moving from an orchestrator to a licensed issuer changes rows rather than code.
The gateway API
A payments API whose documentation is generated from the same table that serves the requests, so the reference can never describe an endpoint the platform does not have.