The full menu · one platform

Payment processing options — the full menu, one platform.

Pick the integration shape, the rails, the provider mix, the MID model and the acceptance channels that fit your business today — and change any of them without re-integrating tomorrow. One API, one vault, one reconciliation feed across every choice.

Book an options review Read the API docs
Integration
hosted · embedded · SDK
Rails
card · ACH · SEPA · wallet · BNPL · crypto
Provider mix
single lane · multi-acquirer panel · full orchestration
Channels
online · POS · pay link · invoice

The menu

Five categories of small business payment processing options and enterprise choices

Every choice a merchant makes with topropay lives inside one of five categories. Pick a combination that fits today; expand later without re-integrating.

  1. 01

    Integration shape

    Pick the surface that matches the PCI-scope preference and the amount of UI control the merchant wants.

    Hosted checkout
    Drop-in redirect or iframe; PCI scope shrinks to SAQ A.
    Embedded (hosted fields)
    Card-number, expiry, CVV iframes inside the merchant's own page; SAQ A-EP.
    Low-level SDK
    Full surface control; vault tokenisation still handled server-side.
  2. 02

    Rails and methods

    The categories the unified API exposes. Merchants pick the subset relevant to their buyer geography and vertical.

    Card
    Visa, Mastercard, Amex, Discover, JCB, RuPay across connected acquirers.
    Bank rail
    ACH (US), SEPA (EU), Bacs and Open Banking (UK), PIX (BR), PayID / OSKO (AU).
    Wallets
    Apple Pay, Google Pay, Click to Pay, Alipay+, WeChat Pay, regional wallets.
    BNPL
    Klarna, Afterpay, Affirm, Clearpay, Atome via the same authorise endpoint.
    Crypto
    Stablecoins, majors and L2 networks via licensed partner gateways.
  3. 03

    Provider mix

    How many acquirers / PSPs sit behind the merchant's traffic. Determines approval-rate ceiling and geographic reach.

    Single provider
    Fastest path to live; ceiling limited by one acquirer's approval and BIN routing.
    Multi-acquirer panel
    Two or more connected acquirers with per-BIN routing; cascade on soft decline.
    Full orchestration
    Broad connected panel with per-BIN, per-currency and per-country routing plus risk-signal scoring.
  4. 04

    Onboarding model

    Two contractual shapes. Both inherit the platform's PCI L1 posture.

    Sub-merchant
    Merchant rides the platform's MIDs; no direct acquiring contract; fastest to live.
    Direct MID
    Merchant holds their own acquiring contract; the platform provides orchestration and reconciliation.
  5. 05

    Acceptance channels

    Where the payment actually happens. All channels share the same vault, tokens and reconciliation feed.

    Online checkout
    Hosted, embedded or SDK checkout on the merchant's website.
    POS / card-present
    Partner-delivered terminal estate plus SoftPOS / Tap-to-Phone.
    Hosted pay links
    Branded per-invoice URLs shared via email, SMS or WhatsApp.
    Invoice-tied receivables
    Hosted pay links tied to invoices with auto-close on settlement.

Key benefits

Why one menu of website payment processing options beats stitching stacks

Four properties that show up the moment a merchant stops running two payment stacks (one online, one in-person; one for cards, one for bank rails) and starts running one menu of options.

One menu, one integration

Every option on the menu — integration shape, rails, provider mix, MID model, channels — sits behind the same unified API. Switching between options is a dashboard / routing-policy change, not a re-integration.

Right-sized for small business, scaled for enterprise

Small business payment processing options default to a smaller connected panel, lighter routing policy and fewer channels enabled. Enterprise merchants unlock the full option surface — same platform, different defaults.

Approval rate follows the option choice

Single-provider ceilings are hard. The multi-acquirer and full-orchestration options lift approval by ranking connected lanes per authorisation and cascading soft declines inside the same auth.

One reconciliation feed across every option

Whichever combination of options the merchant picks, settlements, fees, refunds and chargebacks normalise into one ledger tagged by channel, provider, currency and vertical.

How selection works

From discovery to phased go-live in five steps

How merchants actually navigate the option menu — from an initial 30-minute discovery review to phased go-live with the shortlisted picks.

  1. 01

    Discovery review

    A 30-minute review captures the merchant's geography mix, vertical, buyer profile, existing stack and roadmap — the constraints that narrow the option menu.

  2. 02

    Option shortlist

    topropay proposes an initial shortlist: integration shape, rails per market, provider mix and MID model — with the reasoning behind each pick.

  3. 03

    Sandbox validation

    Merchant tests the shortlisted options in sandbox against representative test cards, mandates and buyer flows — before any commercial commitment.

  4. 04

    Phased go-live

    Merchant migrates traffic in stages, often parallel-running with an existing provider during cutover so approval, cost and dispute outcomes can be measured.

  5. 05

    Tune, expand, repeat

    As traffic grows, new options unlock: extra rails per market, additional acquirers on the panel, new channels (POS, pay links, invoices). Same merchant record throughout.

Main use cases

Which online payment processing options pair with which merchants

Six recurring merchant shapes and the option combinations that fit them.

  • Sole

    Sole traders and freelancers

    Start with SoftPOS on the phone plus hosted pay links. Add online checkout only when the website launches. Fastest path from KYB to first payment.

  • SMB

    Retail SMBs

    Multi-store SMBs pair a partner terminal estate with an online checkout. Same merchant record; head office reads one ledger across stores and web.

  • DTC

    DTC brands going cross-border

    Add SEPA SDD, iDEAL, PIX and BNPL as the brand enters new markets. Each new option is a routing-policy change, not a new integration project.

  • SaaS

    SaaS subscription businesses

    Card recurring on VTS/MDES network tokens plus SEPA Direct Debit for EU customers. Enterprise annual invoicing rides the same platform.

  • B2B

    B2B invoicing operations

    Invoice-tied hosted pay links with card + ACH + SEPA on the same surface. Dunning with smart retries; auto-close on settlement.

  • PSP

    PSPs and platforms

    Resell the full menu downstream. PSP keeps the merchant relationship and pricing; topropay handles the per-merchant provider-side message exchange.

Platform features

Capabilities that back every payment processing option

Twelve capabilities the platform ships once and reuses across every option combination — the primitives that make the menu feel like one product.

  • Unified API across every option

    One REST contract for card, ACH, SEPA, wallet, BNPL and crypto.

  • Hosted, embedded and SDK surfaces

    Three integration shapes share the same back-end — picked per PCI / UI constraints.

  • Multi-acquirer routing engine

    Per-BIN, per-currency and per-country scoring; ranked routes per authorisation across the connected panel.

  • Cascade & retry

    Soft declines cascade to the next ranked provider inside the same authorisation; nothing leaks back to the buyer.

  • PCI DSS Level 1 vault

    Card data captures into the platform vault before any connected provider sees it; PAN never lands in merchant systems.

  • Network tokens & updaters

    VTS and MDES tokens by default for card; scheme updaters keep saved credentials alive.

  • 3DS2 / SCA orchestration

    Selective 3DS2 challenges per authorisation — PSD2-compliant in Europe without breaking conversion.

  • Unified dispute queue

    One queue across providers; evidence-pack templates per vertical; automated representment for select scheme types.

  • POS + SoftPOS + online

    Card-present via partner terminals and SoftPOS unified with the online surface on one merchant record.

  • Hosted pay links + invoices

    Branded per-invoice URLs shared over email, SMS or WhatsApp with auto-close on settlement.

  • One reconciliation feed

    Settlements, fees, refunds and chargebacks across every option normalised into one ledger.

  • Per-merchant routing policies

    Independent routing weights per merchant or per merchant-group; resellers configure downstream merchants individually.

Industry relevance

Payment processing options for licensed EU, UK, APAC and LATAM merchants

topropay's option menu targets licensed merchants operating across Europe, the UK, APAC and LATAM. The same platform serves small businesses on their first payment and enterprise merchants at multi-region scale — the menu of options is common; the configuration differs.

  • Sole traders & small business
  • Retail SMBs
  • DTC brands cross-border
  • SaaS & subscription businesses
  • B2B invoicing operations
  • Marketplaces & platforms
  • PSPs reselling downstream
  • Licensed gaming (where licensed)
  • Adult content · out of scope
  • Unlicensed gambling · out of scope

Trust & compliance

Compliance posture across every option combination

One audited environment underpins the orchestration layer; rail-specific mandate handling and scheme-programme posture sit alongside it. Sub-merchants inherit the posture across every option chosen.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every option chosen.
PCI MPoC for SoftPOS
Partner SoftPOS apps follow the PCI MPoC standard for accepting card-present transactions on commercial off-the-shelf devices.
SCA & PSD2
Selective 3DS2 on the online authorisation path keeps approval high in Europe without skipping the SCA bar.
Bank-rail mandate posture
NACHA authorisations for ACH, SEPA mandate IDs for SEPA Direct Debit; captured and retained per scheme rules.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per connected provider; routing weights can rotate around at-risk lanes.
Sanctions & AML alignment
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical, volume and country mix.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of the option mix.

Ready to pick your combination

Book a 30-minute options review.

The review covers your geography mix, vertical, buyer profile and roadmap — and proposes an option shortlist you can test in sandbox before any commercial commitment.

Book the review Read the API docs

Frequently asked

Buyer questions about payment processing options on topropay

Definitions, small-business vs enterprise defaults, option-change mechanics, high-risk posture and the practicalities of running one merchant record across many option combinations.

  1. 01

    What does topropay mean by payment processing options?

    Payment processing options on topropay covers the full menu the merchant picks from — integration shape (hosted, embedded, SDK), rails and methods (card, ACH, SEPA, wallet, BNPL, crypto), provider mix (single, multi-acquirer, full orchestration), onboarding model (sub-merchant, direct MID) and acceptance channels (online, POS, hosted pay link, invoice-tied). All options sit behind the same unified API.

  2. 02

    What small business payment processing options should I look at first?

    Small business payment processing options typically start with the hosted checkout (SAQ A, fastest to live), a card + wallet default method mix, sub-merchant onboarding to skip direct acquiring underwriting, and online + hosted-pay-link channels. SoftPOS / Tap-to-Phone is added on the in-person side if the business has any offline sales.

  3. 03

    How do payment processing options for small business compare to enterprise?

    Payment processing options for small business use the same platform as enterprise merchants; what differs is the default configuration. Small-business defaults skew to fewer channels enabled at start, a smaller connected panel, lighter routing policy and a compact dashboard. Enterprise defaults enable the full option surface. Tier-up between the two is a routing-policy and channel-enable change.

  4. 04

    What website payment processing options should merchants pick?

    Website payment processing options depend on PCI-scope preference and UI control. Merchants wanting minimum PCI scope pick the hosted checkout (SAQ A). Merchants wanting to render their own checkout UI pick embedded hosted fields (SAQ A-EP). Merchants building a bespoke web checkout pick the low-level SDK. All three share the same back-end.

  5. 05

    What online payment processing options extend beyond card?

    Online payment processing options beyond card include ACH (US, NACHA-compliant), SEPA Direct Debit (EU), Bacs (UK), regional bank rails (iDEAL, Bancontact, PIX), wallets (Apple Pay, Google Pay, Click to Pay), BNPL (Klarna, Afterpay, Clearpay), and crypto (stablecoins, majors, L2 networks via licensed partner gateways).

  6. 06

    Can a merchant change options later without re-integrating?

    Yes. Adding rails, switching from single-provider to multi-acquirer routing, moving from sub-merchant to direct MID, or enabling new channels (POS, pay links, invoices) are all configuration changes on top of the same integration. The merchant's checkout code and API contract stay the same.

  7. 07

    How does the platform decide which option combination is best?

    topropay proposes an option shortlist based on the merchant's geography mix, vertical, buyer profile, existing stack and roadmap. The proposal is validated in sandbox with representative test cards, mandates and buyer flows before any commercial commitment. Phased go-live and parallel-running with an existing provider are supported.

  8. 08

    Is there a single 'best' set of options?

    No — the best set of options depends on the merchant's specific mix of geography, vertical and buyer profile. What's optimal for a UK SaaS is different from what's optimal for a Brazilian DTC brand or a Singapore-based marketplace. topropay's option menu lets the merchant pick without having to re-platform when the mix shifts.

  9. 09

    What options are available for high-risk merchants?

    Licensed high-risk merchants (chargeback-monitored verticals with valid operating licences) get the same option menu with a chargeback-aware acquirer subset, tighter risk-signal scoring, dispute programme (VDMP / ECP) posture surfaced per acquirer, and evidence-pack templates tuned to their vertical. Unlicensed or grey-market operators are out of scope.

  10. 10

    How do options affect settlement timing?

    Settlement timing depends on the rail chosen. Card typically settles T+1 to T+3 depending on scheme and acquirer. ACH settles 1–3 business days (same-day where supported). SEPA Direct Debit follows the SEPA rulebook. Crypto settles in minutes via partner gateways. The option choice determines timing; the reconciliation feed normalises all of them.

  11. 11

    Do payment processing options change what I pay?

    Yes — different options carry different cost structures. Interchange varies by scheme, region and BIN class. Multi-acquirer routing can reduce effective interchange by picking the lowest-cost lane per authorisation. Bank rails have different fee schedules than cards. topropay's pricing is per-merchant and per-vertical; the routing engine minimises effective landed cost within the option constraints.

  12. 12

    What options apply to POS card-present acceptance?

    POS options include partner-delivered terminal estates (countertop, portable, mPOS), SoftPOS / Tap-to-Phone on NFC-equipped devices, and unified reporting with the online side under one merchant record. Contactless (EMV tap, Apple Pay, Google Pay) is default on the partner terminals.

  13. 13

    Are hosted pay links a separate integration?

    No — hosted pay links are one of the acceptance-channel options inside the same platform. Issue a link via API or the dashboard; the buyer opens it and pays through the same hosted-checkout back-end used for the merchant's main online surface. Vault tokens and reconciliation are shared.

  14. 14

    Do options include crypto acceptance?

    Yes. Crypto is one of the rail options — delivered through licensed partner crypto gateways (VASP / MiCA-relevant authorisations). Stablecoins (USDC, USDT, DAI), majors (BTC, ETH, SOL) and L2 networks are supported. Optional conversion-on-receipt keeps the merchant's treasury fiat-only.

  15. 15

    How long does the option-selection process take before going live?

    Most merchants finish option selection, KYB, sandbox validation and phased go-live in 2–6 weeks. Small-business paths with fewer options can compress to 1–2 weeks. Enterprise migrations with multi-region, multi-channel option combinations typically run 6–10 weeks including parallel-running with the incumbent provider.

Related

Related on the topropay platform