One payment view, every rail
Authorisations, captures, refunds and chargebacks land in one feed across every connected gateway. No tab-switching between provider consoles to answer a single support question.
PIC payment portal
PIC payment, one merchant portal for every gateway.
topropay is the payment system that puts every connected payment gateway, acquirer and method behind one merchant portal. You see authorisations, routing decisions, settlements and fees in a single payment view, while smart routing keeps approval rates high and gateway processing fast on every transaction.
PIC payment portal at a glance
- 1 portal
- One merchant portal that shows every gateway, acquirer and method in a single payment view.
- 300+ methods
- Cards, wallets, account-to-account and local rails reachable through one integration.
- <150 ms routing
- Per-transaction gateway processing decisions taken inside the same authorisation request.
The short version
A merchant portal that shows every payment, not just one gateway
Most businesses outgrow a single-gateway setup quickly. The first gateway covers one region and a handful of methods; the next market wants a different acquirer, the next product launches a wallet-led checkout, and finance ends up reading three consoles to answer one question. Each new gateway portal looks slightly different, exports its numbers in a slightly different shape, and adds another layer of operational tax to the payment system.
topropay collapses that sprawl into one merchant portal. Authorisations, routing decisions, captures, refunds and chargebacks land in a unified payment view, regardless of the gateway that handled the transaction. Per-authorisation routing picks the best gateway in milliseconds, cascading retries keep approval rates high, and a single normalised ledger replaces the file-per-gateway reconciliation that the finance team usually inherits. The engineering job shrinks to one integration. The operations job shrinks to one screen.
Key benefits
What changes when the payment dashboard is the same place as the gateway
Four outcomes show up first when a unified portal replaces N provider consoles.
Smart gateway processing
Each authorisation is scored and routed to the gateway most likely to approve at the lowest cost. Soft declines cascade to the next ranked route in the same request, transparent to the shopper.
Every method, one integration
Open one connection and reach hundreds of methods — cards, wallets, account-to-account, regional schemes — without standing up a new gateway portal per provider.
Operations without exposure
Role-based access, scoped permissions and a full audit trail give your team the controls they need to run the payment system without ever handling raw card data.
How it works
From integration to a live payment view
Four phases take a merchant from a single integration to a live, fully observable portal — without changing the acquirers or contracts already in place.
-
Connect once
Drop in the unified API or a prebuilt checkout. The merchant portal lights up as soon as the first integration test posts a transaction — no separate dashboard installation, no per-gateway setup.
-
Switch on rails
Pick the gateways, acquirers and methods you want live in each market. Each rail appears in the same payment dashboard view, so the operations team learns one interface instead of a console per provider.
-
Route and observe
Set the routing policy — by cost, currency, approval rate or risk. Every authorisation flows through gateway processing in milliseconds and shows up in the live payment view with its full decision trail.
-
Reconcile and report
Settlements, fees, refunds and chargebacks normalise into one ledger that exports directly to your ERP or warehouse, so finance closes the month against the same numbers operations sees in the portal.
Where it fits
Where a unified gateway portal earns its keep
Different businesses ask the portal slightly different questions. These are the patterns the platform sees most often.
- DTC
Direct-to-consumer brands
One payment view across the storefront, mobile app and a recurring loyalty programme — without a separate gateway portal per channel.
- SaaS
Subscriptions and SaaS
Retry policy, dunning and account-updater logic run inside the same dashboard, so renewal recovery is a configuration choice instead of a per-gateway script.
- Marketplace
Marketplaces and platforms
Split payments and seller payouts are visible alongside the parent transaction, so support cases close in a single screen rather than three.
- PSP
PSPs and resellers
White-label the merchant portal to your own customers and resell multi-gateway capacity through one integration.
- Travel
Travel and high-ticket
Staged captures, partial refunds and currency conversions are visible end-to-end, so finance can investigate a long-tail booking from a single timeline.
Capabilities
What lives inside the payment system
Six capability bands cover the full lifecycle of a transaction, from accepting it on the checkout to closing the books at month-end.
Read the API documentationUnified merchant portal
One web app with role-based access, a normalised payment view, configurable routing rules and audit logs. Every connected gateway, acquirer and method is visible from the same screen, so the team learns one tool instead of N.
Smart routing & cascading
Per-transaction scoring picks the best gateway for each authorisation and cascades to the next route on a soft decline. Routing is rule-driven and editable from the dashboard payment view without a code release.
Payment dashboard analytics
Approval rate, cost per transaction, decline reasons and chargeback flow into a live dashboard. Cohort the data by gateway, scheme, market or BIN and act on what you see — no SQL required for the day-to-day questions.
Tokenisation & vault
Card data is captured into a PCI DSS Level 1 vault; the portal and your services only ever handle tokens. Refunds, retries and recurring all operate on the saved token, so your PCI scope stays at the lightest applicable form.
Webhooks & exports
A signed event stream feeds your SIEM, data warehouse or in-house ops tooling; CSV and Parquet exports cover the cases when a real-time feed is overkill. The portal and the export agree on every number.
Multi-currency settlement
Settlement currency is a policy choice, not a gateway constraint. The platform groups payouts by currency and acquirer so reconciliation does not multiply with every new market you open.
Fees & charges
Gateway fee and charge data, surfaced in the portal
Fee opacity is one of the main reasons teams move to a unified portal. Every payment gateway charge and acquirer fee is captured against the transaction it belongs to, so finance can answer a "what did this cost?" question without leaving the screen.
Each connected gateway's fee model is surfaced in the portal alongside the transaction, so the cost of every authorisation is visible — not buried in a monthly statement.
The payment gateway charge for routing, tokenisation and reporting is included in the platform fee; you do not pay extra to see your own data.
Fees, refunds, chargebacks and forex are normalised in the ledger so finance can reconcile gateway charges back to authorisations one-to-one.
Industry relevance
Regions and methods the merchant portal covers
The same merchant portal opens new markets as configuration, not as fresh integration. These are the regions and method families the platform serves most often, with local rails surfaced alongside cards in the unified payment view.
Europe & UK
Local acquiring, SEPA online payments and SCA-compliant 3DS2 across EU and UK markets. Domestic schemes like iDEAL, Bancontact and Blik sit alongside Visa and Mastercard.
APAC
Local methods and connectivity across major APAC markets. Where a merchant needs a payment gateway Indonesia connection, regional e-wallets and bank transfers are surfaced in the same payment view as card flows.
LATAM
Card, wallet and bank-transfer coverage across the largest LATAM markets, with multi-currency settlement and the same routing policy you run elsewhere.
South Asia & emerging
Selected coverage including an Indian payment gateway connection where merchant onboarding allows; the unified portal lets you operate every supported region from one console.
Where exactly the platform connects in a given country depends on the merchant's vertical and the local licensing environment. The portal is the source of truth: it lists the gateways and methods actually switched on for the account, so the team always works against a live picture rather than a marketing snapshot.
Trust & compliance
Signals your CISO and CFO will recognise
The portal is the operator-facing surface of a payment system that already carries the heavy compliance work. You get the visibility without taking on the regulated card-data surface.
- PCI DSS L1 Service provider posture with annual on-site assessment and quarterly ASV scans.
- PSD2 ready 3DS2 and SCA applied per transaction in markets that require it.
- EU data residency Processing inside the agreed region, with audit-grade event logs available from the portal.
For the deeper compliance posture — vault, scheme attestations, audit-grade exports — see the payment card industry PCI compliance page. For the routing engine that decides which gateway handles each authorisation, see smart routing and cascading. Related guides cover the payment processing process end to end, the credit card payment processor stack, merchant acquiring, and the payment provider overview for PSPs.
Common questions
Frequently asked questions about the merchant portal
What is a PIC payment portal?
PIC payment is shorthand for a 'payment-in-context' portal — a single merchant portal where every gateway, acquirer and method a business uses is visible from one screen. Instead of switching between provider consoles, an operator sees the full payment view for a transaction (gateway, scheme, route, decision, fee, settlement, refund, chargeback) in one place. topropay delivers that as part of its payment system, sitting in front of every connected provider.
How is this different from a single payment gateway?
A standalone payment gateway gives you one route to authorisation and one console to read from. topropay is a payment system above many gateways: a single integration reaches every connected provider, the merchant portal aggregates all of them into one view, and a smart-routing engine picks the best gateway per authorisation. You also keep the option to swap or add gateways without re-integrating downstream tooling.
Do you provide a payment dashboard or a separate dashboard payment tool?
The merchant portal is the payment dashboard — there is no separate dashboard payment product to install. The same web app shows the payment view, the routing rules, the gateway processing decisions and the reconciliation feed; access is role-based so finance, operations and engineering see what they each need.
Can the portal cover an Indian payment gateway connection?
Where merchant onboarding allows, the platform connects to regional providers including an Indian payment gateway. Geographic reach varies by merchant profile and licence requirements, so the supported list is confirmed during onboarding rather than fixed in the marketing material.
Do you support a payment gateway Indonesia connection?
Yes, regional connectivity in APAC includes a payment gateway Indonesia route alongside local e-wallets and bank transfers. As with any market, the exact list of providers depends on the merchant's vertical and configuration — the unified portal surfaces whichever rails are active.
How are gateway fee and payment gateway charge handled?
Each connected gateway's fee schedule is visible inside the portal next to the transactions it processed. The platform fee covers the unified API, routing, tokenisation and reporting; per-gateway costs pass through transparently so the gateway fee on a given authorisation is clear. The portal then groups payment gateway charge entries by acquirer and currency for clean reconciliation.
Do you publish an international payment gateway list?
The platform exposes its currently supported gateways inside the merchant portal — that is the live international payment gateway list each merchant cares about, because it reflects what is actually switched on for their account. We do not publish a fixed marketing list because connectivity evolves and per-merchant entitlements differ.
How does the platform support positive payment system practices?
A positive payment system (also called positive pay) is a control where issued payments are matched against an authorised list before settlement, originally for cheques and now extended to electronic flows. The portal supports the equivalent control for digital payments: every authorisation is recorded against an account-level allow-list, anomalies surface in the live payment view, and the audit log keeps a verifiable record that finance and risk teams can match against expected payouts.
Can I keep my existing gateways and acquirers when adopting topropay?
Yes. topropay is an orchestration layer, not a closed gateway, so the existing gateway portal contracts and acquirer relationships you already hold stay in place. Point them at the unified API; the merchant portal and the routing engine sit on top. You add new providers as configuration, not as fresh engineering projects.
How long does it take to bring a team onto the portal?
A typical migration from a single-gateway console to the topropay portal takes days, not quarters. The integration is one API; the dashboard payment view, the routing rules and the reconciliation feed are wired up as soon as the first transaction lands. Finance and operations teams usually onboard inside a single training session because they learn one interface instead of three.
Talk to a payments engineer
Put your gateways behind one merchant portal.
Book a portal walk-through. We map your current providers, surface every gateway fee and payment gateway charge against real transactions, and show how the unified payment view replaces console-switching for finance and operations.