Merchant accounts

Merchant accounts, mainstream and high-risk — one integration in front of every account you run.

topropay's orchestration layer sits in front of the merchant accounts your business uses today and the ones it will add tomorrow. Direct or sub-merchant, standard or licensed high-risk, US or international — every merchant account reachable through one unified API, one routing engine and one reconciliation feed.

Book an accounts review Explore the platform
LATAM Merchant account M-4081 · BRL · PIX APAC Merchant account M-3017 · SGD · cards UK Merchant account M-2204 · GBP · cards + OB EU Merchant account M-1190 · EUR · cards + SEPA
Multiple accounts, one settlement story.
  • Direct

    Merchant holds its own contracts with each acquirer.

  • Sub-merchant

    Merchant rides topropay's MIDs and inherits the platform's posture.

  • Mainstream

    Retail, SaaS, marketplaces, travel and similar standard MCCs.

  • Licensed high-risk

    Subscriptions, cruise, nutraceuticals, regulated gaming and the like, where licensed.

Key benefits

Why running multiple merchant accounts through orchestration changes the maths

Four outcomes show up consistently once topropay sits in front of the merchant accounts a business uses, regardless of whether they're direct or sub-merchant.

  1. 01

    One integration in front of every merchant-account path

    Whether you onboard as a sub-merchant on the platform's MIDs or layer topropay in front of your own direct merchant accounts, you integrate once. The decision can change later without re-platforming.

  2. 02

    Routing across the acquirer panel beneath your accounts

    Each merchant account sits behind an acquirer or a panel of acquirers. The routing engine scores every authorisation across the connected set and cascades through soft declines inside the same request.

  3. 03

    International high risk merchant accounts as a routing question

    International high risk merchant accounts stop being a queue of country-by-country applications when the platform's regional acquirer panel handles the geography mix. New markets become routing-policy changes, not new onboarding cycles.

  4. 04

    One ledger across every account, currency and acquirer

    Settlements, fees, refunds and chargebacks from every merchant account roll into one normalised reconciliation feed. Finance closes the month from a single export rather than a CSV-per-account merge.

How it works

From scoping to live across mainstream and high risk merchant accounts

Five stages. Underwriting is concentrated up-front; operations simplify afterwards. Most merchants reach live integration in weeks, not quarters.

  1. 01

    Scoping

    Map MCCs, geographies, chargeback profile and volume against the available acquirer set. Output: realistic candidate panel and timeline.

  2. 02

    Underwriting

    Underwriting happens once on the platform side under the sub-merchant model, or runs in parallel with direct acquirer applications if you keep your own MIDs.

  3. 03

    Integration

    Drop in the unified API or the hosted checkout. Existing acquirer contracts can stay in place; the platform sits in front of them.

  4. 04

    Activation

    Methods, routing weights and risk thresholds switch on per market. Sandbox parity lets you rehearse cascade and chargeback scenarios before live traffic.

  5. 05

    Operate

    Live authorisations, refunds and disputes flow through one operator portal. Reconciliation drops into your ERP daily.

The three paths

Gateway-only, direct merchant accounts, or sub-merchant — pick once, change later

Three valid shapes for an online merchant. The platform supports all three, and the choice can change as the business scales without re-platforming the integration.

Gateway only

No merchant account on the merchant side

  • Provider holds the account; merchant rides one MID
  • Cheapest to start, hardest to scale beyond one provider
  • No multi-acquirer routing or cascading
  • Reconciliation is per-provider, manual to merge
Direct MIDs

Merchant holds its own merchant accounts

  • Direct contracts with each acquirer
  • Best leverage on pricing once volume is established
  • Multi-acquirer routing if topropay sits in front
  • Reconciliation runs against multiple settlement files
Sub-merchant

Sub-merchant on the platform's MIDs

  • Onboard once with topropay; ride the platform's MIDs
  • Fastest path to live; inherited compliance posture
  • Multi-acquirer routing on day one
  • Reconciliation already normalised into one ledger

Main use cases

Verticals running on the platform's merchant-accounts model

Six merchant shapes that share the same orchestration but apply it at different risk and complexity bands. Cruise, continuity, gaming and international cases all belong here.

  • Mainstream

    Retail, SaaS and travel merchants in standard MCCs

    Most merchants in standard MCCs don't need a 'high risk' bucket — they need account-level reliability. The platform's mainstream merchant-accounts path delivers low-friction underwriting and routing across the standard acquirer panel.

  • Subscriptions

    Subscription, SaaS and continuity billing

    Recurring billing on vault tokens with network-token-by-default and scheme account updaters keeps renewals alive without per-account scripting. Renewal failure becomes a routing question, not an engineering one.

  • Cruise

    Cruise line high risk merchant accounts

    Cruise line operators sit in a travel-adjacent high-risk band — long booking windows, complex captures, chargeback windows that extend past sailing. The platform's travel-tuned routing and staged-capture support fit cruise line economics; legitimate, licensed operators are supported.

  • Subs (HR)

    Continuity, nutraceuticals and supplements

    High-risk continuity verticals (nutraceutical and supplement subscriptions) route through chargeback-aware acquirer subsets. Soft-descriptor handling and dispute-evidence templates are configured per vertical.

  • Gaming

    Licensed gaming and sportsbook merchants

    Licensed operators in permitted jurisdictions integrate as sub-merchants. KYC, AML and responsible-gaming controls run alongside the platform's standard posture; unlicensed operators are out of scope.

  • International

    International merchants with multi-region traffic

    Cross-border DTC, marketplaces and OTAs running into multiple regions get a regional acquirer panel rather than a single MID. Settlement currency is a policy choice; FX exposure is a setting, not a default.

Platform features

Capabilities behind every merchant account on the platform

What the platform ships specifically for handling multiple merchant accounts behind one integration — beyond the general orchestration features that apply to every merchant.

  • Unified payments API

    One contract across every connected merchant account and acquirer; SDKs for web, mobile and server.

  • Hosted & embedded checkout

    Drop-in checkout for a fast launch; hosted fields and a low-level SDK for full control.

  • Smart routing engine

    Per-transaction scoring on BIN, scheme, currency, country and risk — ranked routes per authorisation across your accounts.

  • Cascade & retry

    Soft declines fail over to the next ranked acquirer inside the same authorisation. No buyer-facing retry.

  • PCI DSS Level 1 vault

    Card data captures into our vault before it touches any merchant account. Refunds, retries and recurring run on tokens.

  • Network tokens & updaters

    Network-token-by-default tokenisation, plus scheme account updaters that keep saved cards alive across re-issuance.

  • 3DS2 & SCA orchestration

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

  • Dispute & chargeback queue

    One queue across every merchant account; evidence-pack templates per vertical; automated representment for select case types.

  • Unified reconciliation

    Settlements, fees, refunds and chargebacks normalised across every account into one daily ledger export.

  • Operator portal

    One dashboard for authorisations, refunds, disputes and chargebacks across every connected merchant account.

Trust & compliance

Compliance posture inherited across every merchant account

The platform's audited environment wraps every connected account. Sub-merchants inherit the posture rather than re-certifying per account; direct-MID merchants keep their own certifications and ride the platform's surface on top.

  • PCI DSS L1

    Annual on-site assessment; quarterly ASV scans; inherited by sub-merchants.

  • SCA & 3DS2

    Selective challenges keep approval rates high in Europe without skipping the compliance bar.

  • Scheme programmes

    Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP thresholds tracked per acquirer.

  • Licensed only

    Licensed operators in permitted jurisdictions; grey- and black-market verticals are out of scope.

Ready to map your accounts

Stand up the right merchant accounts, in the right regions, behind one API.

A 45-minute accounts review walks through whether the direct-MID, sub-merchant or hybrid path fits, which acquirers underwrite your MCC and geography, and the sandbox you can test against before any commercial commitment.

Book an accounts review Read the API docs

Frequently asked

Buyer questions about merchant accounts on the platform

What buyers ask before they commit — covering definitions, gateway vs account vs aggregator paths, US-specific high-risk setups, international structures, cruise-line verticals and the bank-side vs acquirer-side distinction.

  • What's the difference between gateway-only and full merchant accounts?

    Gateway-only means the provider holds the merchant account and the merchant rides one MID. Merchant accounts proper are issued in the merchant's own name by an acquirer, with the merchant on the contract. topropay supports both shapes: a sub-merchant model where you ride our MIDs, and an orchestration layer that sits in front of your own direct merchant accounts when you have them.

  • What are internet merchant accounts in this context?

    Internet merchant accounts is the older industry term for merchant accounts that accept card-not-present (online) transactions — as opposed to physical/POS terminals. Every merchant account on topropay is an internet merchant account by design; we are an online-first orchestration platform.

  • Are web merchant accounts handled the same way?

    Web merchant accounts is a synonym for internet merchant accounts — the term emphasises browser-based checkouts. The orchestration shape is the same: one API, one vault, one routing engine and one reconciliation feed across every connected web merchant account.

  • How do high risk merchant accounts work on the platform?

    High risk merchant accounts route through a curated subset of the connected acquirer panel — those acquirers that underwrite the specific MCC, geography and chargeback profile in question. Per-segment routing policies are tuned for chargeback-band-aware acquirer selection, and unified reconciliation works the same way across high-risk and standard accounts.

  • What about high risk merchant accounts us — is US connectivity included?

    High risk merchant accounts us are supported through US-domiciled acquirer relationships in the connected panel. US card BINs route to US acquirers under US risk policies; cross-border traffic from US merchants can route to non-US acquirers when the BIN, scheme and country pair make that the better landing zone.

  • What is a high risk gateway in relation to merchant accounts?

    A high risk gateway is the gateway surface in front of a high-risk-licensed acquirer. topropay aggregates several high risk gateway connections behind one API — your integration speaks to topropay, topropay speaks to the relevant high-risk gateway per authorisation based on the routing policy you've set.

  • What does a high risk gateway merchant account setup look like?

    A high risk gateway merchant account setup pairs one or more high-risk-licensed acquirer accounts with the gateway surface that authorises into them. Through topropay, that's a sub-merchant onboarding once, then routing across the available high-risk acquirers from the dashboard. Existing direct high-risk gateway merchant accounts can stay in place; topropay sits in front of them.

  • Is a high risk gateway merchant accounts us setup any different from a single account?

    A high risk gateway merchant accounts us setup typically pairs more than one US-domiciled high-risk acquirer behind a single integration, so cascade and routing can absorb declines that a single account would simply lose. The contractual underwriting still happens per acquirer; the orchestration layer is what makes the multi-account shape feel like one product.

  • Do you support international high risk merchant accounts for cross-border traffic?

    International high risk merchant accounts are the standard shape for any merchant whose customers span more than one region. The platform's regional acquirer panel — EU, UK, APAC and LATAM — is reachable behind one integration; underwriting for each regional account is platform-side, and routing decides which account runs which authorisation.

  • What are the benefits of high risk merchant accounts when run through orchestration?

    Benefits of high risk merchant accounts orchestrated through the platform: chargeback-aware routing across acquirers so a soft decline on one can be picked up by another; one ledger across acquirers; a unified dispute queue with evidence-pack templates; sub-merchant onboarding that compresses several acquirer applications into one; and routing policies that can be tuned per segment without re-integration.

  • What benefits high risk merchant accounts give over a single account?

    Benefits high risk merchant accounts over a single account: redundancy (a chargeback ratio breach on one acquirer doesn't stop the merchant), routing flexibility (per-BIN and per-currency policies), pricing leverage (commercial reviews are evidence-based across providers) and faster regional rollout (the platform-side acquirer panel covers regions a single account doesn't).

  • How do I pick the best merchant accounts for high risk?

    The best merchant accounts for high risk are a function of MCC, geography mix and chargeback profile — not a fixed top-N list. We map your traffic against the realistic acquirer subset that underwrites your specific shape, then route across that subset rather than picking one. The 'best' becomes a routing policy, not a procurement choice.

  • Do you support cruise line high risk merchant accounts?

    Cruise line high risk merchant accounts are supported for licensed cruise operators. The vertical sits in the travel-adjacent high-risk band because of long booking windows, complex captures and extended chargeback liability; the platform's staged-capture support, evidence-pack templates and travel-tuned routing fit those constraints. Licensed operators only.

  • What are merchant accounts payment gateways in plain terms?

    Merchant accounts payment gateways describes the pair of things needed to accept online cards: the merchant account (which holds the funds and the contract) and the payment gateway (which authorises and captures the transaction). topropay provides the gateway, the routing across multiple connected gateways, and either the sub-merchant accounts or the layer in front of your own merchant accounts.

  • What about high risk accounts in banking versus high-risk merchant accounts?

    High risk accounts in banking is the bank-side classification — a deposit account flagged for elevated AML or compliance attention. High-risk merchant accounts is the acquiring-side classification of a merchant whose MCC, performance or geography puts it in a higher-risk band. They are independent: a merchant can be coded high-risk by the acquirer while holding a standard bank account, and vice versa.

Related

Related on the topropay platform