Substrate under every rail
topropay is the substrate underneath every acceptance channel — a PCI DSS Level 1 vault, a unified switch, a per-transaction routing engine and a normalised reconciliation feed. Merchants and PSPs plug into it; they don't rebuild it.
Key benefits
Four properties that show up the moment finance sees one ledger instead of six, and engineering ships one integration instead of one per acquirer.
Card, ACH, SEPA, wallet, BNPL and crypto rails share the same vault, the same routing engine and the same dispute queue. Merchants don't run parallel stacks per rail; PSPs don't ship separate integrations to their downstream merchants.
The routing engine scores authorisations in under 200 ms; the switch handles peak-hour spikes across the connected acquirer panel; horizontal scaling absorbs seasonal surges without merchant-side action.
PSPs and platforms build their own products on top of the same vault, switch and ledger. Merchant-of-record models, marketplace facilitation and per-merchant routing policies are first-class primitives, not bolt-ons.
Stablecoin and major-token acceptance sits on the same platform as fiat rails, delivered through licensed partner crypto gateways with optional conversion-on-receipt into the merchant's treasury currency.
How payment infrastructure platforms work
Capture, route, settle, report — the substrate is the same across every rail the merchant enables.
Card data captures into the PCI DSS Level 1 vault from a hosted checkout, embedded hosted-fields or low-level SDK. Non-card rails capture their scheme-specific credentials (mandate IDs, wallet tokens, on-chain addresses).
The routing engine scores each authorisation on BIN, scheme, currency, country pair and risk signals; ranks the connected acquirers or partner rails; picks the top route for that transaction.
Settlement files from every connected provider land daily; the platform normalises fees, interchange, refunds and chargebacks into rows tagged by acquirer, scheme, currency and routing policy.
Merchant and PSP dashboards read one ledger; accounting connectors push receipts into ERPs; signed webhooks fire on every lifecycle transition.
Main use cases
Six recurring shapes — enterprise consolidations, PSPs reselling downstream, SaaS billing, omnichannel retail, crypto-adding merchants and marketplace platforms.
Enterprise buyers replacing per-region gateway integrations with one common substrate — enterprise payment infrastructure with routing policies per BU and per market, one ledger for group finance.
PSPs and platforms offer merchant-of-record or facilitator products built on the same vault, switch and ledger; per-merchant routing weights and dispute segregation baked in.
Recurring billing on card, ACH and SEPA rides the same vault tokens; account updaters and smart retries run centrally; renewals don't fall off the back of expired credentials.
Card-present terminal estates share the same vault as online checkout; a single vault token covers refund and recurring across channels.
Crypto payment infrastructure via licensed partner gateways plugs into the same API; the merchant gains a stablecoin or major-token option without a separate crypto integration project.
Different seller profiles land on different connected acquirers based on risk, volume and geography; the reconciliation feed rolls up per seller and per acquirer.
Platform features
Twelve primitives the platform ships once and reuses across every acceptance channel — from vault and switch through routing and dispute tooling.
Card data captures into the platform vault before any acquirer sees it; sub-merchants inherit the PCI posture across every acceptance channel.
One switch across every connected acquirer, PSP and partner-delivered rail; scheme-agnostic message routing at sub-200ms.
Per-BIN, per-currency, per-country and per-risk-signal routing scores across the connected panel; ranked routes per authorisation.
Soft declines cascade to the next ranked provider inside the same authorisation; nothing leaks back to the buyer.
VTS and MDES network tokens by default; scheme account updaters keep saved credentials alive across re-issuance.
Selective EMV 3DS2 per PSD2 exemption logic; frictionless flows pass through where issuers allow.
NACHA authorisations for US ACH; SEPA mandate IDs for SEPA Direct Debit; captured and retained per scheme rules.
Stablecoin and major-token acceptance through licensed partner crypto gateways; optional conversion-on-receipt into treasury currency.
One queue across acquirers and rails; evidence-pack templates per vertical; automated representment for select scheme types.
Refund justification, actor-ID logging, per-merchant permission scopes; audit-grade event log across every state transition.
Settlements, interchange, scheme fees, refunds and chargebacks normalised into one ledger; daily exports as CSV or via API.
Signed lifecycle events; connectors for popular ERPs and accounting systems; replay-safe delivery.
Industry relevance
topropay's substrate targets licensed merchants and PSPs operating across Europe, the UK, APAC and LATAM — enterprise buyers consolidating stacks, PSPs reselling downstream, SaaS and marketplace platforms, omnichannel retail, and crypto-inclusive merchants where operating licences permit.
Trust & compliance
One audited environment for the orchestration layer plus rail-specific mandate handling for ACH, SEPA and crypto partner-gateway connectivity.
Ready to consolidate the stack
A 30-minute architecture review covers the connected acquirer panel relevant to your geographies, the vault topology, the routing policy that fits your BIN mix, and a sandbox to test against before any commercial commitment.
Frequently asked
Definitions, competitor comparisons, migration mechanics, crypto substrate integration and the practicalities of running on shared infrastructure.
Payment infrastructure on topropay is the substrate that sits underneath every acceptance channel — the PCI DSS Level 1 vault that holds card credentials, the unified switch that carries the messages, the smart-routing engine that picks the connected acquirer for each authorisation, the unified dispute queue and the normalised reconciliation feed. Merchants and PSPs plug into it; they don't rebuild it.
A single payment gateway is one connection to one acquirer. The payment gateway infrastructure on topropay is one integration in front of many connected acquirers — the platform swaps or adds gateway providers as routing-policy changes rather than integrations, and the vault, switch and reconciliation stay constant regardless of which provider clears the auth.
Enterprise buyers consolidating per-region or per-scheme gateway integrations into one common substrate typically look at enterprise payment infrastructure. The wins are: routing policies per business unit or market, unified dispute posture across the group, one reconciliation feed for consolidated finance, and one PCI DSS assessment scope rather than several.
Payment infrastructure companies typically fall into three shapes: single-provider gateways (locked to their own acquiring), full-stack processors (acquiring + gateway + risk in-house), and orchestration platforms (provider-agnostic layer above many gateways / processors). topropay sits in the orchestration shape — its value is provider-agnosticism, not scheme-owned acquiring.
Payment infrastructure providers in the orchestration category include IXOPAY, Corefy, Spreedly, Basis Theory and Gr4vy alongside topropay; each has a distinct posture on vault topology, routing engine, dispute tooling and PSP-resell primitives. topropay's specific positioning is one contract across mainstream and licensed compliance-bound verticals (where those verticals hold current operating licences), with crypto rails on the same substrate as fiat.
Payment processing infrastructure on topropay scales horizontally: the switch and routing engine run across multiple regions; the connected acquirer panel absorbs volume across its own switches; peak-hour spikes route through the highest-capacity lanes first. The bottleneck is the acquirer's own switch, not the orchestration layer.
Payment infrastructure platforms vary widely on developer experience — some ship only server SDKs, others include client-side hosted-field libraries and idempotency-safe webhook delivery. topropay ships hosted checkout, embedded hosted-fields, low-level SDKs for web / iOS / Android / server, signed webhooks and OpenAPI-driven contracts across the full API surface.
Payment infrastructure solutions that cover both online and card-present under one merchant record are the omnichannel shape topropay serves. Card-present acceptance rides partner terminal estates and SoftPOS / Tap-to-Phone via licensed acquirers; online rides the connected acquirer panel. Both feed the same vault, so refunds and recurring work across channels.
topropay is delivered as payment infrastructure as a service — hosted by the platform, accessed via the unified API. Merchants and PSPs don't install anything on-premise; they integrate against the API and configure their routing policies through the dashboard. Sandbox environments mirror production for testing.
Payment system infrastructure on topropay is multi-currency at the vault, switch and ledger level. Merchants configure their settlement currencies per market; the switch handles currency conversion on the acquirer's side; the ledger tags each row with the transaction currency, the settlement currency and the FX rate applied. Multi-currency merchants read one consolidated feed with per-currency rollups.
Mobile payment infrastructure on topropay covers Apple Pay, Google Pay, Click to Pay and other wallet-tokenised handoffs on the online side, plus SoftPOS / Tap-to-Phone for in-person acceptance through licensed partner acquirers. Both surfaces feed the same vault; the merchant doesn't run separate mobile-only integrations.
To optimize payment infrastructure that's currently spread across providers, the typical first pass is: consolidate vault tokenisation onto one substrate (topropay's PCI L1 vault), point the online checkout at the unified API in parallel with the existing provider, measure per-provider approval and cost, then rotate routing weights toward the highest-EV lanes. This can run without a big-bang migration.
No. Crypto payment infrastructure sits on the same API as card and bank rails. Stablecoin (USDC, USDT, DAI, PYUSD) and major-token (BTC, ETH, SOL) acceptance route through licensed partner crypto gateways; conversion-on-receipt into fiat is optional. The merchant adds crypto as a channel toggle, not a new integration.
Most merchants integrate in 2–6 weeks depending on the PCI scope choice (hosted vs embedded vs SDK), the number of channels being enabled at once, and any KYB and scheme-programme registration timelines with the connected acquirers. Sandbox covers the full API from day one, so implementation runs in parallel with commercial onboarding.
Vault tokens and transaction history are exportable via API and CSV. Merchants can rotate their routing weights toward a specific connected acquirer over time (effectively deprecating the platform's orchestration by piping traffic through one lane), or export historical dispute and reconciliation data for migration into another provider. The platform's contract structure supports orderly wind-down.
Related