Sub-merchant · direct MID · licensed high-risk
Start on topropay's aggregator model and go live in days. Migrate to a direct MID with a connected acquirer once volume and dispute posture support it. Same integration, same dashboard, same reconciliation feed across the transition.
Account model
Two lanes sit behind the same gateway. Pick the one that matches where the business is today; migrate as volume and dispute posture prove out.
Sub-merchant (aggregator model)
Fastest path to live · no direct acquiring contract
topropay's onboarding puts the merchant onto the platform's aggregator MID. KYB is lighter, the go-live window is measured in days rather than weeks, and the merchant inherits the platform's PCI L1 posture. Settlement lands on topropay's operating account and pays out to the merchant on the agreed schedule.
Direct MID (per-merchant acquiring contract)
Best for volume · lower blended fees · direct settlement
The merchant holds a direct acquiring contract with the connected licensed acquirer. Interchange-plus visibility is cleaner, chargeback exposure is direct, and settlement pays out from the acquirer to the merchant. topropay's orchestration, vault, routing and reconciliation still ride on top.
Key benefits
Four properties that matter to merchants picking between fast-onboarding aggregator models and per-merchant direct acquiring.
New merchants live on the aggregator MID within days. Once volume, verticals and dispute posture prove out, the merchant can migrate to a direct MID with the connected acquirer — same integration, same dashboard, same reconciliation feed.
Whether the merchant is on the sub-merchant model or a direct MID, authorisations route across the connected acquiring panel. Soft declines cascade inside the same authorisation; nothing leaks back to the buyer.
US, UK, EU, APAC and LATAM sit behind the same platform. The right acquiring lane per country pair and per BIN is selected by the routing engine, not by which merchant account was opened first.
Licensed high-risk verticals (subscriptions, travel, ticketing, licensed gaming, regulated nutraceuticals) have dedicated routing weights and chargeback-programme monitoring. Grey and black-market verticals are out of scope regardless of channel.
How it works
What happens between the merchant hitting the underwriting queue and the first live authorisation clearing on the connected acquirer.
Company documents, beneficial ownership, vertical, expected volume, ticket size and target geographies land in the underwriting queue via the dashboard.
Underwriting recommends the aggregator model for fast go-live or the direct-MID model where the merchant's volume, vertical and dispute posture justify it.
The commercial contract is issued; the platform vault is provisioned; API credentials and dashboard access are delivered.
The merchant integrates against topropay's unified API — hosted checkout, embedded fields or low-level SDK. Sandbox covers the full connected panel end to end.
First live authorisations start; the routing engine tunes weights against the merchant's actual BIN mix and volume distribution over the first few weeks.
Main use cases
Six recurring merchant shapes — DTC, SaaS, marketplaces, travel, licensed gaming and PSP resellers.
Start on the aggregator MID to reach EU and UK buyers immediately; migrate to a direct EU MID once volume in the region justifies the acquiring relationship.
Aggregator MID covers early growth; direct MID once monthly recurring volume clears the threshold where interchange-plus visibility matters.
The marketplace holds the direct MID; individual sellers ride the platform's sub-merchant onboarding underneath. Reconciliation rolls up per-seller and per-acquirer.
Chargeback-aware routing across acquirers experienced in travel MCCs. Delayed capture, auth-only bookings and refund-on-cancellation all supported on the same MID.
Where the merchant holds the operating licence, dedicated routing weights per jurisdiction, plus scheme-programme (VDMP / VAMP / VFMP / ECP / EFMP) monitoring per acquirer.
PSPs and resellers inherit the aggregator MID as a downstream product; individual sub-merchants roll up under the reseller's contract and reporting.
Platform features
Twelve capabilities the platform ships once and reuses across every merchant account — sub-merchant, direct-MID, hybrid.
Fast KYB, inherited PCI posture, ride the platform's aggregator MID; go live in days.
Direct acquiring contract with a connected licensed acquirer; interchange-plus visibility; direct settlement.
Per-BIN, per-currency, per-country scoring across the connected acquiring panel.
Soft declines cascade to the next ranked lane inside the same authorisation; nothing leaks back to the buyer.
Card data captures into the platform vault before any acquirer sees it; vault tokens drive refunds, retries and recurring.
VTS and MDES network tokens by default; scheme account updaters keep saved cards alive across re-issuance.
Selective challenges on the authorisation path — PSD2 SCA-compliant in Europe without breaking conversion.
Chargebacks and disputes from every connected acquirer in one queue; evidence-pack templates per vertical.
Sanctions screening at KYB; AML monitoring tuned per vertical, volume and country mix.
Settlements, interchange, fees, refunds and chargebacks normalised into one ledger regardless of sub-merchant / direct-MID mix.
Refunds require operator justification; every refund event logged with actor identity, reason and timestamp.
Same merchant can run some traffic on the aggregator model and other traffic on a direct MID — reconciliation stays unified.
Regional coverage
Three regional slices — US, UK, and the broader EU / APAC / LATAM panel — each with their own acquiring lanes and vertical availability.
US-side coverage runs through licensed US acquirers connected to the platform. Visa, Mastercard, Amex, Discover, ACH (NACHA-compliant), Apple Pay, Google Pay and Click to Pay are exposed via the same unified API. Sub-merchant onboarding for fast go-live; direct MID with a US acquirer once volume warrants it.
UK-side coverage runs through licensed UK acquirers. High-risk online merchant account uk lanes (licensed gaming, travel, subscription and other regulated verticals) are supported where the merchant holds the required operating licences. Chargeback-programme monitoring per acquirer is surfaced in the dashboard.
EU card connectivity, SEPA Direct Debit, iDEAL, Bancontact, PIX (BR), OXXO and Boleto (LATAM, via partners), plus APAC card and wallet coverage all sit under one merchant-account layer. Regional acquiring is added as connections rather than as separate merchant records.
Trust & compliance
One audited environment plus per-acquirer scheme-programme monitoring. Sub-merchants inherit the posture on the aggregator model; direct-MID merchants ride it via the platform layer.
Ready to open the account
A 30-minute underwriting review confirms which account model fits, which acquirers cover your target geographies and verticals, and a sandbox you can test against before any commercial commitment.
Frequently asked
Sub-merchant vs direct MID, underwriting timelines, chargeback exposure, licensed high-risk verticals and the practicalities of migrating between account models.
An online merchant account on topropay is the commercial record under which the merchant accepts card and non-card payments. It can be an aggregator sub-merchant record (riding the platform's MID) or a direct MID (a per-merchant acquiring contract with a connected licensed acquirer). Both ride the same unified API, vault and reconciliation feed.
The payment gateway online merchant account pattern on topropay is: the merchant integrates once against the unified gateway API; behind the gateway sits the merchant-account layer (aggregator or direct MID) and the connected acquiring panel. The merchant doesn't pick one gateway per acquirer — the gateway is one, the acquirers are many.
Yes, for licensed high-risk verticals. High risk online payment processing on the platform runs across acquirers experienced in the merchant's vertical; chargeback-programme monitoring (VDMP / VAMP / VFMP / ECP / EFMP) is surfaced per acquirer; routing weights rotate around at-risk lanes. Adult content, unlicensed gambling and other grey / black verticals are out of scope.
Yes. online merchant account usa coverage runs through licensed US acquirers connected to the platform. Sub-merchant onboarding for fast go-live; direct MID with a US acquirer once volume, vertical and dispute posture support it. Visa, Mastercard, Amex, Discover, ACH, Apple Pay, Google Pay and Click to Pay all sit under the same account.
Yes — a high risk online merchant account on topropay pairs sub-merchant or direct-MID structure with acquirers experienced in the merchant's vertical. Chargeback-aware routing weights, dispute-queue templates per vertical and per-acquirer scheme-programme monitoring are wired in by default. Licensed operators only.
high risk online merchant account uk lanes are supported through licensed UK acquirers with capacity for the merchant's vertical. The UK vertical mix typically covers licensed gaming, subscription, travel and other regulated categories. The operating-licence bar applies as it does everywhere — grey / black verticals are out of scope.
Yes. High risk online merchant services around the account cover chargeback-aware routing, unified dispute queue with evidence-pack templates per vertical, operator-side refund controls, per-acquirer scheme-programme monitoring, and AML / sanctions monitoring tuned to the merchant's profile. Those services ride on top of the account layer.
The 'high risk online payment gateway' framing on topropay isn't a separate product — it's the same unified gateway API with high-risk-aware routing weights, dispute tooling and monitoring layered on. The merchant integrates once; the platform handles the per-vertical behaviour behind the API.
Aggregator sub-merchant approval typically runs 2–5 business days for clean documentation on low-risk verticals; longer for licensed high-risk verticals where operating-licence checks and volume forecasts extend underwriting. Direct-MID approval depends on the connected acquirer's own underwriting timeline — typically 2–6 weeks.
Yes — that migration path is common and supported. The merchant record stays; the acquiring contract shifts. Existing vault tokens carry across; the API surface and dashboard don't change. Reconciliation history stays queryable through the same feed.
On the aggregator model, settlement lands on topropay's operating account and pays out to the merchant on the agreed schedule. On direct MID, settlement pays out directly from the connected acquirer to the merchant. In both cases, the platform's reconciliation feed exposes the settlement rows tagged per acquirer, per currency and per net-of-fees amount.
Yes. For licensed high-risk verticals (gaming, regulated financial services, licensed nutraceuticals in some jurisdictions, adult-industry-adjacent verticals like dating in some jurisdictions), the merchant must hold the operating licence in every jurisdiction they accept from. The platform's underwriting confirms this at KYB.
On the aggregator model, chargeback exposure sits with topropay as the merchant of record, with contractual pass-through to the sub-merchant per scheme rules. On direct MID, chargeback exposure sits with the merchant directly with the connected acquirer. In both cases, the unified dispute queue and evidence-pack templates apply.
topropay accepts applications from merchants operating across EU, UK, APAC and LATAM as a baseline, with US and other geographies added via connected licensed acquirers. Country availability depends on the merchant's vertical, licensing posture and the coverage of the connected acquirer panel in that country.
Yes. PSPs and resellers inherit the aggregator sub-merchant model as a downstream product. Individual sub-merchants roll up under the PSP's contract; per-sub-merchant reporting and routing policies are supported in the dashboard so the reseller can manage the portfolio.
Related