Payment services

Payment services — one catalogue, one API, one ledger.

topropay exposes card, ACH, crypto (via partner gateways), payment facilitation, subscriber and merchant payment services under a single orchestration layer. Routing, vault and reconciliation are shared; the catalogue is a configuration choice per merchant.

Book a services review Explore the platform
topropay · service catalogue
  • Card payment services
  • ACH payment services
  • Crypto payment services
  • Payment facilitation services
  • Subscriber payment services
  • Merchant payment services
  • E-payment services
  • Business payment services
8 categories · 1 contract · 1 ledger
8
service categories under one API
300+
methods reachable globally
60+
connected acquirers and PSPs
1
operator portal and ledger

Key benefits

Why a catalogue of payment services beats single-purpose tools

Four outcomes that show up consistently once card, ACH, crypto and facilitation services share the same orchestration layer rather than living in separate consoles.

  1. Catalogue

    Every payment-service category under one contract

    Card, ACH, crypto (via partner gateways), payment facilitation, subscriber and merchant payment services all live under the same topropay contract. Adding a new service category becomes a dashboard step, not a fresh integration project.

  2. Routing

    Smart routing inside every service category

    Inside card, inside ACH, inside crypto — every authorisation runs through the routing engine, scored against your own traffic. The cascade absorbs soft declines inside the same request, so each service category lifts on net revenue, not just on coverage.

  3. Posture

    PCI DSS Level 1 and audited posture across services

    Card data captures into the vault before it ever touches merchant origin. Sub-merchants on facilitation services inherit the platform's PCI, SCA and AML posture rather than carrying separate certifications per service category.

  4. Reconciliation

    One ledger across card, ACH, crypto and facilitated flows

    Settlements, fees, refunds and chargebacks across every service category normalise into one reconciliation feed. Finance closes the month from one export — regardless of how many service categories the merchant runs.

Service catalogue

The six payment-service categories in detail

Each category is an independent toggle on the merchant contract — turn on the categories you need, leave the rest off. Underneath, the same routing engine, vault and reconciliation power them all.

  • Card payment services

    Credit card payment services run across the connected acquirer panel — multi-acquirer routing on every authorisation, network tokens, scheme updaters, selective 3DS2 / SCA, and dispute tooling per scheme.

    • Visa / Mastercard / Amex / Discover / JCB / RuPay
    • Network tokens by default
    • Per-BIN routing weights
    • Unified dispute queue

  • ACH payment services

    ACH payment services cover one-off and recurring debits with NACHA mandate handling, R-code retry calendars and operator-side controls — same API surface as card, plus rail-specific metadata.

    • NACHA mandate evidence
    • R-code-aware retries
    • ACH debits and credits
    • Same webhook event model as card

  • Crypto payment services

    Crypto payment services run through licensed partner gateways: stablecoins, majors and L2 networks. Optional conversion-on-receipt keeps treasury fiat-only when that's the merchant's preference.

    • USDC, USDT, BTC, ETH and others
    • Conversion-on-receipt policies
    • Same reconciliation feed as fiat
    • Partner-licensed AML / KYC

  • Payment facilitation services

    Payment facilitation services let a platform onboard sub-merchants under topropay's MIDs, with per-tenant routing policies, split payments and per-tenant reporting. Useful for marketplaces, vertical SaaS and PSPs.

    • Sub-merchant onboarding
    • Split payments and seller payouts
    • Per-tenant routing policies
    • Platform-side underwriting

  • Subscriber payment services

    Subscriber payment services cover recurring authorisations end-to-end: cycle scheduling, smart-retry, network tokens, account updaters and customer-portal cancel flows — across card, ACH and SEPA Direct Debit.

    • Cycle scheduling and retries
    • Network tokens and updaters
    • API / portal / operator cancel
    • Renewal-event webhook stream

  • Merchant & business payment services

    Merchant payment services and broader business payment services cover the surfaces a merchant operates against — onboarding, KYC / KYB, vault, dashboard, reporting — under one platform contract.

    • Single onboarding and KYB
    • Operator dashboard
    • Daily reconciliation exports
    • Webhooks into your SIEM / warehouse

How it works

From service-category selection to a single ledger row

Four stages between picking categories on the contract and a normalised reconciliation row in tomorrow's finance export. The integration code stays the same as categories grow.

  1. 01

    Pick the service categories you need

    Card, ACH, crypto, facilitation, subscriber — turn the relevant categories on per merchant from the dashboard. Adding a new category later is a configuration change, not an integration project.

  2. 02

    Configure routing and method mix

    Per-category routing policies, method availability per market and risk thresholds are dashboard-level. Engineering integrates the API once; ops tunes the policies afterwards.

  3. 03

    Run live traffic through one API

    Every authorisation — regardless of service category — runs through the same unified API. Vault tokens, signed webhooks and event-model semantics are the same across card, ACH and crypto.

  4. 04

    Reconcile from one feed

    Settlements, fees, refunds and chargebacks from every service category normalise into one reconciliation feed; per-category analytics in the dashboard surface where the next tweak earns its keep.

Small business note

Credit card payment services for small business — and how 'cheap' is defined

The platform is sized for sub-100M-EUR merchants alongside enterprise volume — same integration, no platform retainer, no monthly minimum. Pricing is per-authorisation on top of the underlying acquirer economics.

  • 01

    Credit card payment services for small business with no platform retainer and no monthly minimum — pay per authorisation, interchange-plus pass-through where supported.

  • 02

    Cheap card payment services in the sense that matters: lowest landed cost per BIN, scheme and country pair, picked per transaction by the routing engine.

  • 03

    ACH payment services and SEPA Direct Debit at a flat per-transaction price for low-ticket recurring flows.

  • 04

    No long-form questionnaires up front — onboarding and KYB are designed for sub-100M-EUR merchants alongside enterprise volume.

Platform features

Capabilities shared across every service category

What the platform ships once and reuses across card, ACH, crypto and facilitation — the primitives that make the catalogue feel like one product.

  • Unified payments API

    One REST contract across every service category; SDKs for web, mobile and server.

  • Smart routing engine

    Per-transaction scoring inside every service category — card, ACH, crypto.

  • Vault tokenisation

    PCI DSS Level 1 vault keeps sensitive data out of merchant origin across card and ACH.

  • Network tokens & updaters

    Network tokens by default; scheme updaters keep saved cards alive across re-issuance.

  • 3DS2 & SCA orchestration

    Selective challenges per transaction; PSD2-compliant in Europe without breaking conversion.

  • ACH / SEPA mandate handling

    NACHA / SEPA mandate evidence captured at sign-up; retained per scheme rules.

  • Crypto via partner gateways

    Licensed partner crypto gateways inside the same API surface as fiat.

  • Sub-merchant onboarding

    Payment-facilitation primitives for marketplaces, vertical SaaS and PSPs.

  • Operator portal

    One dashboard for authorisations, refunds, disputes and chargebacks across every service category.

  • Signed webhooks

    Replay-safe, normalised events into SIEM, warehouse or in-house tooling.

  • Unified reconciliation

    One ledger across every service category, with category tags on every row.

  • Sandbox parity

    Sandbox that mirrors production — routing, cascade, retries, updaters and cancel.

Trust & compliance

Compliance posture across the service catalogue

One audited environment underpins every service category. Merchants inherit posture rather than carrying separate certifications per category.

PCI DSS Level 1
Annual on-site assessment, quarterly ASV scans; sub-merchants inherit the posture regardless of service category.
Mandate posture
NACHA authorisations for ACH, SEPA mandate IDs for SEPA Direct Debit; captured and retained per scheme rules.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per vertical, volume and service-category mix.
Scheme programme tracking
Visa VDMP/VAMP/VFMP and Mastercard ECP/EFMP thresholds tracked across the connected acquirer panel.
Audit log
Operator actions, cancel events and refund events logged with actor identity, reason code and timestamp.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported where current operating licences exist. Grey and black-market verticals are out of scope regardless of service category.

Ready to pick categories

Turn on the payment services that fit your business.

A 30-minute services review covers the categories relevant to your traffic — card, ACH, crypto, facilitation, subscriber — the routing policies that fit, and a sandbox to test against before any commercial commitment.

Book a services review Read the API docs

Frequently asked

Buyer questions about the payment-services catalogue

Questions buyers ask before committing — covering the catalogue boundaries, pricing for small business, ACH and crypto specifics, and how categories combine.

  1. 01

    What does topropay mean by payment services?

    Payment services on topropay is the umbrella for every service category exposed through the unified API: card, ACH, crypto (via partner gateways), payment facilitation, subscriber and merchant services. The merchant integrates once and turns the relevant categories on; the platform absorbs the underlying per-category complexity.

  2. 02

    How do e payment services on the platform differ from a generic gateway?

    E payment services on the platform combine the gateway surface (authorise, capture, refund) with routing, cascade, vault, reconciliation and per-category extensions (e.g. NACHA for ACH, mandate handling for SEPA, conversion-on-receipt for crypto). A generic gateway typically ships only the authorisation surface.

  3. 03

    Are ach payment services first-class or bolted on?

    Ach payment services are first-class — the same routing engine, vault, webhooks and reconciliation as card, plus rail-specific NACHA mandate handling and R-code-aware retries. The merchant's billing system doesn't fork by rail; the platform absorbs the per-rail timing differences.

  4. 04

    How does payment services ach payment configuration work?

    Payment services ach payment configuration is dashboard-level: per-policy retry windows (R01 vs R03 vs R04 vs other R-codes), mandate-evidence retention, descriptors, and authorisation-source flags (CIT vs MIT). All of it sits next to the card-side recurring policy, not in a separate console.

  5. 05

    What are typical merchant payment services on the platform?

    Merchant payment services are the surfaces a merchant uses day-to-day: the onboarding flow, KYC / KYB, the operator dashboard, the reconciliation feed, the dispute queue, the API keys and webhook configuration. Everything sits under one platform contract.

  6. 06

    What business payment services does the platform expose beyond cards?

    Business payment services include ACH and SEPA Direct Debit, supplier payouts via bank rail or stablecoin, expense-card issuance integrations (via partner issuers), and B2B invoicing flows that combine card and bank-rail authorisations under one API.

  7. 07

    How are card payment services structured inside the routing engine?

    Card payment services are routed per BIN, scheme, currency and country pair across the connected acquirer panel. Network tokens, scheme updaters and selective 3DS / SCA are wired into every card authorisation; the merchant doesn't manage per-acquirer integrations.

  8. 08

    What do subscriber payment services cover?

    Subscriber payment services cover the full recurring lifecycle: cycle scheduling, smart-retry, network tokens, scheme account updaters, dunning surfaces, and API / portal / operator cancel flows. Card, ACH and SEPA Direct Debit recurring all share the same primitives.

  9. 09

    How do credit card payment services compare to running directly with an acquirer?

    Credit card payment services on topropay collapse many acquirers into one API surface, with per-transaction routing across them. Running directly with a single acquirer ships only that acquirer's appetite and uptime; topropay trades a slightly larger up-front integration for years of optionality across the connected panel.

  10. 10

    Are crypto payment services in-scope for all merchants?

    Crypto payment services are in-scope for licensed and regulated merchants in supported jurisdictions. Crypto rails are delivered through licensed partner gateways with their own VASP / MiCA-relevant authorisations; merchants in unsupported jurisdictions or unsupported verticals are not onboarded onto crypto services regardless of card or ACH appetite.

  11. 11

    Are credit card payment services for small business priced differently from enterprise?

    Credit card payment services for small business carry no platform retainer and no monthly minimum — pricing is per-authorisation on top of the underlying acquirer economics, with interchange-plus pass-through where supported. Enterprise volume earns negotiated improvements on the platform side; the base economics are accessible to sub-100M-EUR merchants.

  12. 12

    How do payment facilitation services work for a marketplace?

    Payment facilitation services let a marketplace onboard sub-merchants under topropay's MIDs with per-tenant routing policies, split payments, seller payouts and per-tenant reporting. The marketplace doesn't need to become a registered facilitator itself — the underlying acquirer relationships sit with the platform.

  13. 13

    What are the cheap card payment services on the platform, and what's the trade-off?

    Cheap card payment services is shorthand for cost-weighted routing: every authorisation runs through the route with the lowest landed cost for that specific BIN, scheme and country pair. The trade-off vs an approval-weighted policy is fractionally lower approval; for many merchant segments cost-weighting still wins on net revenue. The policy is dashboard-configurable.

  14. 14

    Can a merchant run only one or two service categories rather than all of them?

    Yes — service categories are independent toggles. A merchant can run only card payment services, or only card + ACH, or card + crypto + subscriber. Adding a category later is a dashboard step; the integration code does not need to change.

  15. 15

    How does the unified ledger handle the mix of service categories?

    The unified ledger tags every row with a service-category column (card / ACH / crypto / facilitated / etc.) plus the connected acquirer ID and the policy that ran it. Finance can roll up by category, by acquirer, by region or by merchant tenant from the same export.

Related

Related on the topropay platform