Sub-MID or direct MID · one API

Merchant account internet on a multi-acquirer orchestration API.

A sub-merchant onboarding for merchants who need to be live in days, plus direct MID integration for merchants ready for their own bank relationship. Same unified API, same PCI L1 vault, same reconciliation feed across the panel.

Option A

Sub-merchant

  • KYB · 2–5 business days
  • No monthly account fee
  • Under topropay master MID
  • PCI L1 posture inherited
Option B

Direct MID

  • Merchant's own acquirer
  • Interchange-plus pricing
  • Weeks to onboard
  • Orchestrated on top
Pick one, run both, or migrate between them over time.
Sub-MID
or direct-MID onboarding
UK · EU
APAC and LATAM connectivity
PCI L1
vault inherited by every merchant
1 API
one integration, many acquirers

Two onboarding paths

How internet merchant account providers usually compare with topropay's shape

Traditional internet-merchant-account providers offer one acquiring relationship. topropay offers a sub-MID or a direct MID plus the routing layer on top — the merchant integrates once and picks the shape that fits their volume and risk.

Sub-merchant model

Fast onboarding, low up-front cost

The merchant sits under topropay's master MID at a licensed partner acquirer. KYB runs on the sub-merchant; onboarding usually clears in a few business days. No merchant-side scheme registrations, no bank facing paperwork. This is the closest thing to a 'free internet merchant account' in the honest sense — no monthly account fee to start, per-transaction pricing only.

Direct-MID model

Merchant's own bank relationship

For merchants with the volume or regulatory need to hold their own MID, topropay integrates directly with the merchant's chosen acquirer. Onboarding is longer (weeks not days) and the acquirer's own KYB / underwriting applies. The routing engine, vault and reconciliation still ride the same platform.

Key benefits

Why merchants pick this shape over a single acquirer

Four properties that show up the moment merchant-account traffic stops running through a single acquirer and starts routing across a panel.

One API across every acquirer relationship

Whether the merchant's traffic clears through a sub-MID or a direct MID, the merchant integrates against the same unified topropay API. Adding a new acquirer relationship is a dashboard change, not a re-integration.

Smart routing across the panel

Per-BIN, per-currency and per-country scoring picks the best acquirer per authorisation. Soft declines cascade to the next ranked lane inside the same auth so the buyer sees one decision, not a retry-and-fail loop.

PCI L1 vault inherited

Card data captures into the platform vault before any acquirer sees it. Sub-merchants inherit the PCI DSS Level 1 posture from day one; SAQ scope shrinks accordingly. PAN never lands in merchant systems.

Regulatory paths for licensed verticals

Licensed FX brokers, regulated financial-services merchants and licensed gaming operators route to acquirers that carry the right scheme-programme registrations for their MCC. topropay does not onboard unlicensed or grey-market operators.

How the acquiring flow works

From KYB to reconciled ledger in five steps

What actually happens between the merchant submitting KYB documents and finance reading a normalised reconciliation row in the general ledger.

  1. 01

    Choose the model

    Sub-merchant for fastest onboarding and lowest up-front cost; direct MID for merchants with volume or regulatory need. Some merchants use both — sub-MID in one geography, direct MID in another.

  2. 02

    KYB & underwriting

    KYB, sanctions screening and volume forecasting run through the dashboard. Documents: incorporation certificate, UBO declaration, licence copies where the vertical requires them (FX / gaming / EMI etc.).

  3. 03

    Integrate the API

    One integration covers card, ACH, SEPA, wallet, BNPL and crypto across every enabled channel. Hosted checkout, embedded hosted fields, or low-level SDK — same back-end for all three.

  4. 04

    Route, cascade & retry

    Each authorisation runs through the top-ranked acquirer; soft declines cascade to the next ranked lane inside the same auth. Nothing leaks back to the buyer as a retry-and-fail loop.

  5. 05

    Settle & reconcile

    Settlement files from every connected acquirer normalise into one ledger. Daily exports tagged by acquirer, MID, currency and routing policy. Finance imports into the merchant's accounting system.

Main use cases

Where an e commerce internet merchant account (or an FX one) earns its keep

Six recurring merchant shapes — online retail, SaaS, licensed FX brokers, travel, cross-border sellers and PSPs reselling the panel.

  • Retail

    E commerce internet merchant account for online retail

    DTC brands, marketplaces, subscription boxes — high-volume online retail routes through the connected acquiring panel, with per-market method lists surfaced on the same hosted checkout.

  • SaaS

    SaaS billing on a sub-MID

    Recurring card billing under a sub-MID keeps SaaS merchants live without a bank-side merchant account. Network tokens and account updaters keep renewals alive across card re-issuance.

  • FX

    Licensed forex broker acceptance

    Licensed FX brokers use a forex merchant account with an acquirer that carries the right FX MCC registration. Deposits and withdrawal flows are configured per the broker's risk and compliance profile.

  • Travel

    Travel and ticketing

    Auth-only at booking, capture at fulfilment, refunds on cancellation — all against the same vault token. Delayed capture is a scheme-programme-aware flow on the acquirer side.

  • Intl

    International internet merchant account for cross-border sellers

    Sellers targeting multiple regions route through the geo-optimal acquirer per country pair — an international internet merchant account across EU, UK, APAC and LATAM under one contract.

  • PSP

    PSPs reselling merchant-account internet coverage

    Resellers inherit the connected acquiring panel and configure independent routing policies per downstream merchant. The PSP keeps the merchant relationship; the platform handles the per-merchant provider-side message exchange.

Regional coverage

uk internet merchant account and cross-border acquiring across regions

Three regional slices to anchor the coverage — UK, EU and combined APAC / LATAM.

United Kingdom

internet merchant account uk connectivity through licensed UK partner acquirers — Visa, Mastercard, Amex, Discover, Bacs, Faster Payments and Open Banking under FCA-authorised acquiring. A uk internet merchant account can run as a sub-MID or direct-MID depending on volume.

European Union

SEPA-zone acquiring across the EU under PSD2 and SCA — selective 3DS2 on the online surface, mandate handling for SEPA Direct Debit, and licensed gaming programme registrations where the merchant holds the licence.

APAC & LATAM

APAC and LATAM connectivity via partner acquirers per region — India via licensed partner gateways, Brazil via PIX plus card, Mexico via card plus regional rails. Same unified API, same reconciliation feed.

Platform features

Capabilities across every internet-merchant-account shape

Twelve capabilities the platform ships once and reuses across sub-MID and direct-MID shapes — the primitives that keep the two models feeling like one product.

  • Sub-MID onboarding

    Sub-merchant onboarding under topropay's master MID at licensed partner acquirers — fastest path to live.

  • Direct-MID integration

    Direct integration with the merchant's own MID when volume or regulatory posture requires it.

  • Unified API across models

    Same REST contract regardless of sub-MID or direct-MID; SDKs for web, mobile and server.

  • Smart routing engine

    Per-transaction scoring on BIN, scheme, currency, country pair and risk across every enabled acquirer.

  • Cascade & retry

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

  • PCI DSS Level 1 vault

    Card data in the platform vault; PAN never lands in merchant systems; SAQ scope reduced for sub-merchants.

  • Network tokens & updaters

    VTS / MDES tokens by default; scheme updaters keep saved cards alive across re-issuance.

  • 3DS2 / SCA orchestration

    Selective EMV 3DS2 challenges per PSD2 exemption logic — high approval without skipping the compliance bar.

  • Unified dispute queue

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

  • Sanctions & AML alignment

    Sanctions screening at onboarding; AML monitoring tuned per merchant vertical, volume and geography.

  • One reconciliation feed

    Settlements, fees, refunds and chargebacks from every connected acquirer in one normalised ledger.

  • Per-merchant routing policies

    Independent routing weights per merchant; resellers configure their downstream merchants individually.

Trust & compliance

Compliance posture across every connected acquirer

One audited environment underpins the orchestration layer; per-acquirer scheme programmes surface in the dashboard so the merchant sees where every lane stands.

PCI DSS Level 1
Annual on-site assessment plus quarterly ASV scans; sub-merchants inherit the posture across every connected acquirer.
Scheme programmes
Visa VDMP / VAMP / VFMP and Mastercard ECP / EFMP positions surfaced per connected acquirer; routing weights rotate around at-risk lanes.
SCA & PSD2
Selective 3DS2 keeps approval high in Europe without skipping the SCA bar.
Sanctions & AML alignment
Sanctions screening at onboarding; AML monitoring tuned per merchant vertical, volume and country mix.
FCA-authorised UK acquirers
UK-side connectivity runs through FCA-authorised partner acquirers for uk internet merchant account merchants.
Licensed verticals only
Licensed FX brokers, 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.

Ready to onboard

Get an internet merchant account that scales with you.

A 30-minute onboarding review covers the acquirer(s) relevant to your geography and vertical, sub-MID vs direct-MID trade-offs at your forecast volume, and a sandbox you can test against before any commercial commitment.

Frequently asked

Buyer questions about merchant account internet on topropay

Definitions, FX / forex scope, UK / EU regional posture, volume thresholds, KYB documents and the practicalities of choosing sub-MID vs direct-MID.

  1. 01

    What does 'merchant account internet' mean on topropay?

    A merchant account internet setup on topropay is the arrangement that lets the merchant accept internet (card-not-present) payments. It's either a sub-MID under topropay's master account at a licensed partner acquirer, or a direct MID the merchant holds themselves with topropay orchestrating on top. Both models expose the same unified API to the merchant's stack.

  2. 02

    Do you offer a forex merchant account?

    topropay onboards licensed FX brokers into a forex merchant account through partner acquirers that carry the right FX / MCC scheme-programme registrations. The broker must hold the relevant regulatory licence (FCA in the UK, CySEC in the EU, ASIC in Australia, etc.). Unlicensed FX and copy-trading affiliate structures without a regulated principal are out of scope.

  3. 03

    How do internet merchant account providers compare against topropay?

    Internet merchant account providers typically deliver one acquiring relationship each. topropay sits one layer above, exposing many connected acquirers behind the same integration. The merchant doesn't pick one provider — the routing engine picks the best acquirer per transaction across the connected panel.

  4. 04

    Can we get an internet merchant account uk with topropay?

    Yes. internet merchant account uk connectivity runs through licensed UK partner acquirers (FCA-authorised). Card scheme acceptance, Bacs, Faster Payments and Open Banking sit behind the same unified API as EU, APAC and LATAM connectivity.

  5. 05

    Is there really a free internet merchant account option?

    There isn't a truly 'free internet merchant account' anywhere — every acceptance model has per-transaction costs (interchange, scheme fees, acquirer margin). What topropay offers as the closest honest equivalent is the sub-merchant model, which typically has no monthly account fee and no bank-facing setup fee. Per-transaction pricing still applies and is confirmed at underwriting.

  6. 06

    How does the uk internet merchant account onboarding work?

    The uk internet merchant account onboarding runs the standard sub-merchant path: KYB and UBO declarations, sanctions screening, volume forecasting, licence copies where the vertical requires them, then activation on the partner acquirer. Most low-risk UK merchants clear in 2-5 business days; regulated verticals take longer per the acquirer's compliance timeline.

  7. 07

    Do you support an e commerce internet merchant account for high-volume retail?

    Yes. An e commerce internet merchant account for high-volume online retail runs through the connected acquiring panel with routing weights tuned to the merchant's BIN mix. Cascade on soft decline lifts approval; per-market method lists surface on the same hosted checkout the merchant integrates once.

  8. 08

    What is an international internet merchant account in practice?

    An international internet merchant account on topropay means the merchant integrates once and sees the geo-optimal acquirer per country pair — EU acquirer for EU buyers, UK acquirer for UK buyers, APAC / LATAM acquirers for their respective regions. Cross-border cases fall back to the acquirer with the widest geographic remit.

  9. 09

    What about a forex merchant account uk specifically?

    A forex merchant account uk arrangement pairs an FCA-authorised FX broker with a UK partner acquirer that carries the FX MCC and the relevant scheme-programme registration. Deposit and withdrawal flows are configured per the broker's risk profile; chargeback and dispute posture is monitored against Visa VAMP / VDMP thresholds.

  10. 10

    Does the merchant's volume matter for the sub-MID vs direct-MID decision?

    Yes. Below the acquirer-specific volume threshold (typically a few million EUR / GBP / USD per year, varying by acquirer and vertical), a sub-MID is usually the right shape. Above it, direct-MID starts to pay off because interchange-plus pricing on a direct account can beat the sub-merchant blended rate. topropay's underwriting team advises based on forecast volume.

  11. 11

    Can we switch from a sub-MID to a direct MID later?

    Yes. The merchant record and API integration don't change — moving from a sub-MID to a direct MID is a dashboard-side change plus the direct-acquirer KYB the merchant has to complete separately. Vault tokens, dispute history and reconciliation continuity carry across.

  12. 12

    What documents does a first-time internet-merchant-account application need?

    First-time application documents typically include: certificate of incorporation, UBO declaration, articles of association, current business bank statement, board resolution or director's mandate, sample invoice or website URL for site inspection, and licence copies where the merchant's vertical requires them (FCA / CySEC / ASIC / gaming commission / EMI licence etc.).

  13. 13

    How are chargebacks handled?

    Chargebacks land in the unified dispute queue with evidence-pack templates pre-filled per vertical. Automated representment fires for select scheme dispute types (Visa Reason Codes 10.4, 13.1, 13.2 etc.); the operator can override. Per-acquirer position against VDMP / VAMP / ECP is surfaced in the dashboard.

  14. 14

    What verticals are out of scope regardless of the acquiring model?

    Adult content, unlicensed gambling, unlicensed FX / copy-trading affiliate structures, cryptocurrency without the relevant VASP / MiCA-adjacent licence, and grey / black-market goods are out of scope regardless of whether the merchant asks for a sub-MID or a direct MID. Underwriting filters these out at onboarding.

  15. 15

    Is topropay itself the merchant of record?

    For sub-merchants, topropay's master MID is the technical merchant of record on the acquirer side, and topropay's compliance perimeter covers the sub-merchant's traffic. For direct-MID merchants, the merchant is their own merchant of record; topropay's role is orchestration and reconciliation only.