Payment portal for website

A payment portal for your website — checkout and back-office on one API.

topropay's hosted portal drops into the merchant's checkout and the operator's back-office on the same authorisation engine. Cards, wallets, bank rails (including ACH), BNPL, crypto and licensed-iGaming flows — surfaced through one API, routed across the connected acquirer panel, reconciled into one ledger.

Book a portal review Read the API docs
topropay.com/portal/ · operator view
Checkout Refunds Disputes Reconcile

€189.00

Choose a method

  • Card · •••• 4242
  • Apple Payselected
  • iDEAL · ING
  • ACH · routing 0210
Pay €189.00

Routed through topropay · PCI L1 vault

Drop-in
hosted portal in days
300+
methods reachable
Licensed
iGaming and regulated verticals
1 ledger
across every receipt

Key benefits

Why an orchestrated payment portal wins on every vertical

Four outcomes that show up consistently once the portal sits on the orchestration layer rather than per-provider plumbing — including dedicated paths for licensed iGaming operators and US ACH flows.

  1. 01

    One payment portal for website checkouts and back-office flows

    topropay's hosted portal drops into the merchant's website checkout and into the back-office surfaces operators use to issue refunds, manage disputes and run reconciliation. Same authorisation engine on the buyer side and the operator side; one configuration plane behind both.

  2. 02

    Smart routing across the connected acquirer panel

    Every authorisation runs through the routing engine in under 200ms. Soft declines cascade to the next ranked acquirer inside the same request. The portal surfaces a single clean Pay button on the buyer side and a per-transaction analytics view on the operator side.

  3. 03

    Vertical-aware integration — including licensed iGaming

    The portal handles vertical-specific risk policies, dispute templates and method bias — including a fully-licensed iGaming integration path. Operators in permitted jurisdictions inherit the platform's posture; verticals outside the licensed scope are out of scope.

  4. 04

    ACH payment portal for US flows

    An ACH payment portal surfaces alongside card and wallet authorisations through the same API. NACHA mandate evidence, R-code-aware retries and operator-side controls handle the bank-rail lifecycle; one ledger consolidates ACH and card receipts.

How it works

From hosted portal drop-in to a live payment processing iGaming or generic checkout

Five concrete stages between dropping in the hosted portal and a daily reconciliation export. Hosted flows ship in days; embedded flows take weeks.

  1. 01

    Drop in the hosted portal

    The hosted portal lives on a redirect or iframe with a signed session token. Method availability per market and brand styling are dashboard configuration; the merchant's checkout calls one endpoint.

  2. 02

    Switch on methods and routing

    Cards, wallets, bank rails, BNPL and (where licensed) regional gaming-friendly methods light up from the dashboard. Routing policy (approval-, cost- or composite-weighted) is per-segment.

  3. 03

    Authorise across the connected panel

    Every authorisation runs through the routing engine. Soft declines cascade to the next ranked acquirer inside the same request; the buyer sees one clean result.

  4. 04

    Operator portal handles disputes and refunds

    The back-office portal surfaces the unified dispute queue across acquirers, refund operations with reason codes, and audit-friendly action logs. One UI across the connected provider panel.

  5. 05

    Reconcile in one feed

    Settlements, fees, refunds and chargebacks across every connected provider normalise into one ledger keyed off vault tokens; daily exports drop into ERP or warehouse.

iGaming scope

iGaming payment solutions — what's in scope, what isn't

iGaming is supported for licensed operators only. The block below is direct about what the platform underwrites and what it doesn't, so an operator can self-check before booking a review.

In scope
  • Licensed iGaming operators with current operating licences in permitted jurisdictions
  • Full KYC, AML and responsible-gaming controls in place on the operator side
  • iGaming payment methods filtered per jurisdiction — the portal surfaces only what the licence permits
  • iGaming payment gateway integration via the same unified API as any other merchant
  • Operator-specific 3DS / risk policies layered on the standard routing engine
  • Dispute and chargeback queue tuned to iGaming-typical patterns (high refund rate on responsible-gaming triggers, scheme-side fraud rules)
Out of scope
  • Unlicensed gambling and grey-market betting, regardless of integration shape
  • Operators in jurisdictions without a clear regulatory framework for the vertical
  • Adult, illicit substances and other compliance-blocked verticals — out of scope regardless of licensing in some markets
  • Methods or routes not explicitly permitted by the underlying acquirer for the iGaming MCC
  • Cash-out / wallet flows that bypass the operator's KYC and responsible-gaming controls
  • Bonus-abuse patterns that violate scheme programme rules (Visa VAMP / Mastercard ECP)

Main use cases

Where the payment portal earns its keep across verticals

Six merchant shapes that share the same hosted-portal primitives but stress them differently — DTC, licensed iGaming, ACH-heavy US merchants, B2B invoicing, marketplaces and SaaS subscriptions.

  • DTC

    E-commerce DTC portals

    Hosted checkout on the website plus operator-side refund / dispute portal — same authorisation engine across both, with brand styling for the buyer-side portal.

  • iGaming

    Licensed iGaming payments platform

    An iGaming payments platform for licensed operators — deposit flows, withdrawal flows, KYC handoffs and scheme-programme tracking. Operator-licensing required in every market the merchant serves.

  • ACH

    ACH payment portal for US merchants

    US merchants surface an ACH payment portal alongside cards on the same checkout. NACHA mandate handling, R-code-aware retries and operator-side bulk operations through the same API.

  • B2B

    B2B invoice payment portal

    A B2B invoice-payment portal for cards and bank rails — invoice URLs map to hosted-portal sessions; payments settle into the same reconciliation feed as ecommerce traffic.

  • Marketplace

    Marketplaces with per-seller portals

    Multi-tenant portals where each seller surface inherits the parent merchant's routing and reporting. Split payments and per-seller payouts on one orchestration.

  • SaaS

    Subscriptions and SaaS portals

    Customer portals for plan management, payment-method update and self-service refunds — wired through the same vault tokens and webhook stream as the buy-flow.

Platform features

Capabilities behind the iGaming payments platform and the wider portal

What the platform actually ships — both the generic portal primitives and the iGaming / ACH-specific layers.

  • Hosted payment portal

    Drop-in checkout via redirect or iframe; signed session tokens; brandable surface; localised method ordering per market.

  • Operator back-office portal

    Unified dashboard for authorisations, refunds, disputes and chargebacks across every connected provider.

  • iGaming payment provider integration

    Connected iGaming-friendly acquirers and PSPs in the routing panel; licensed-operator-only access; per-jurisdiction method filtering.

  • iGaming payment processing

    Scheme programme tracking (Visa VAMP / Mastercard ECP) per iGaming relationship; chargeback-aware routing for high-refund verticals.

  • iGaming payment methods

    Cards, bank rails, regional wallets and (where licensed) crypto rails surfaced inside the same operator-facing portal.

  • ACH payment portal

    NACHA mandate evidence, R-code-aware retries, ACH credits and debits surfaced through the same API as card.

  • Smart routing engine

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

  • PCI DSS Level 1 vault

    Card data captures into the vault before it touches the merchant origin; refunds, retries and recurring run on vault tokens.

  • 3DS2 / SCA orchestration

    Selective challenges per transaction across the connected provider panel — PSD2-compliant in Europe without breaking conversion.

  • Signed webhooks

    Replay-safe webhook delivery with HMAC signatures; per-event subscription; SIEM-friendly out of the box.

  • Unified reconciliation

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

  • Sandbox parity

    Per-environment sandbox that mirrors production — routing, cascade, 3DS, ACH R-codes, iGaming dispute scenarios.

Trust & compliance

Compliance posture for licensed iGaming and the wider portal

Every authorisation runs through a single audited environment. Merchants inherit the platform's posture; iGaming operators carry their own licensing on top.

PCI DSS Level 1
Annual on-site assessment and quarterly ASV scans; sub-merchants inherit the posture regardless of vertical.
iGaming licensing posture
iGaming operators must hold current operating licences in permitted jurisdictions, with full KYC / AML / responsible-gaming controls. Onboarding verifies licence scope before any traffic is permitted.
Scheme programme tracking
Visa VAMP / VDMP / VFMP and Mastercard ECP / EFMP thresholds tracked per provider, with dashboard alerts.
ACH / NACHA alignment
NACHA authorisation evidence for ACH, retained per scheme rules; R-code-aware retry calendars built in.
Sanctions & AML
Sanctions screening on onboarding; AML monitoring tuned per vertical and per acquirer's appetite.
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 explicitly out of scope regardless of integration shape.

Ready to drop in the portal

One payment portal for your website — checkout and back-office.

A 30-minute portal review walks through the connected acquirer panel for your vertical (including licensed iGaming where applicable), the methods relevant for your markets, and a sandbox to test against before any commercial commitment.

Book a portal review Read the API docs

Frequently asked

Buyer questions about the payment portal — generic and licensed iGaming

Questions buyers ask before committing — covering portal shape, iGaming licensing, ACH integration, dispute handling, payouts and sandbox parity.

  1. 01

    What does topropay mean by payment portal for website?

    Payment portal for website on topropay is the hosted checkout that drops into the merchant's site plus the back-office operator portal that handles refunds, disputes and reconciliation. Both back onto the same authorisation engine, vault and ledger; the merchant integrates once for buyer-side and operator-side together.

  2. 02

    Does the platform support igaming payment solutions for licensed operators?

    Yes. iGaming payment solutions on topropay are available to licensed iGaming operators holding current operating licences in permitted jurisdictions and running full KYC, AML and responsible-gaming controls. Routing, vault tokenisation, dispute tooling and reconciliation behave the same way as for any merchant; operator-specific risk rules layer on top. Unlicensed gambling and grey-market operators are out of scope.

  3. 03

    What about igaming payment — is the integration shape different from generic ecommerce?

    iGaming payment integration uses the same unified API as generic ecommerce — one /v1/payments endpoint, one webhook event model, one vault. The difference is on the back-end: the routing engine routes through iGaming-friendly acquirers in the panel; the dispute queue carries iGaming-specific evidence templates; scheme programme tracking is tighter because the vertical sits in the higher-watch chargeback bands.

  4. 04

    Is topropay an igaming payment provider in the regulatory sense?

    topropay operates as an aggregator / TPPP that integrates with iGaming-friendly acquirers in markets where the platform's licensing supports it. The platform itself is not a direct iGaming-licensed acquirer in every market; iGaming connectivity is delivered through connected providers with the relevant licensing. Operators inherit that posture as sub-merchants.

  5. 05

    How does topropay compare to an igaming solutions provider model?

    An iGaming solutions provider typically bundles checkout, KYC, fraud and bonus management for the iGaming vertical. topropay sits at the payments layer underneath — a licensed iGaming operator can use topropay alongside an iGaming-platform vendor, with topropay handling the unified API in front of the connected acquirer panel and the vendor handling the game-specific surfaces.

  6. 06

    Is there an igaming payment gateway specifically?

    The igaming payment gateway surface on topropay is the same unified gateway as for any other merchant — one REST API, one webhook stream, one vault. iGaming routing policies and method-filtering live on top. From the integration code's perspective, the merchant adds 'method: card' or 'method: bank-transfer' to the request; the platform routes to iGaming-friendly acquirers behind the scenes for operators flagged as iGaming.

  7. 07

    How does igaming payment processing handle chargebacks?

    iGaming payment processing on topropay surfaces the unified chargeback queue with iGaming-tuned evidence templates. Scheme programme thresholds (Visa VAMP, Mastercard ECP) are tracked per acquirer relationship; the dashboard alerts the operator before any threshold is breached. Automated representment is supported for select scheme codes; manual response uses the evidence-template flow.

  8. 08

    What is the igaming payment system shape end-to-end?

    The iGaming payment system shape on topropay is: hosted deposit portal on the operator's site → routing engine picks the best iGaming-friendly acquirer → vault token issued → withdrawal portal initiates a card refund or a bank-rail payout against the same token → unified reconciliation rolls deposits and payouts into one ledger. KYC / AML hand-off integrates with the operator's compliance vendor.

  9. 09

    Which igaming payment methods are typically active?

    iGaming payment methods active on the platform mirror the supported regional method set — cards (where the acquirer underwrites iGaming for that scheme), bank rails (Open Banking in the UK, SEPA in EU, Interac in CA, PIX in BR), select wallets and (where licensed) crypto — filtered per jurisdiction by the operator's licence scope. The portal never surfaces a method not permitted by the operator's licence.

  10. 10

    Are there igaming payment processor connections specifically?

    Yes — connected iGaming payment processors sit in the routing panel alongside generic-vertical acquirers. The routing engine picks among them based on BIN, scheme, currency and per-operator risk policy. The operator's dashboard shows the active iGaming processor panel scoped to their licensed markets.

  11. 11

    What about igaming online payment posture for cross-jurisdiction operators?

    iGaming online payment for cross-jurisdiction operators is supported where the operator holds a current licence in each market it accepts deposits from. The platform tags the licence scope per jurisdiction and never routes a deposit to a market the operator isn't licensed for. Where a jurisdiction loses its regulatory clarity, the platform's posture is to pause that market until clarity returns.

  12. 12

    How is payment processing igaming priced?

    Payment processing iGaming pricing is per-authorisation on top of the underlying acquirer's iGaming-tier rate (which is typically higher than generic-vertical rates because of the chargeback band). topropay's platform fee is a separate line on the invoice; no platform retainer beyond that.

  13. 13

    What igaming payment services include withdrawal / payout flows?

    iGaming payment services on topropay include deposit (authorise) and withdrawal (payout / original-credit / refund) flows through the same vault tokens. Card payouts via OCT where the underlying scheme and acquirer support it; bank-rail payouts via SEPA, Bacs, Faster Payments, Interac and equivalents. Operator-side approval workflows for withdrawals are supported.

  14. 14

    What is an igaming payments platform vs an igaming payment system?

    Industry usage is loose. iGaming payments platform usually means the full surface (checkout + back-office + reconciliation); iGaming payment system is the broader umbrella that may also include the game-side wallet ledger. topropay covers the payments-platform side and integrates with the operator's wallet / game-ledger systems via signed webhooks.

  15. 15

    How does the ACH payment portal work alongside cards?

    The ACH payment portal surfaces ACH as a method tile on the same hosted checkout as cards. NACHA mandate evidence captures at sign-up; the merchant's billing system uses the same authorise endpoint with 'method: ach'. R-code retries follow the platform's retry calendar; operator-side bulk operations (mandate updates, cancellations) work through the same back-office portal.

Related

Related on the topropay platform