White Label

White Label Merchant Management: How PSPs Run a Merchant Portfolio

Oksana Mikhailovskaya
12 min read

White label merchant management is the back-office layer of a white-label payment gateway where you onboard merchants, configure their shops, fees and limits, monitor their risk and calculate their payouts under your brand. This guide is for PSPs, acquiring banks, electronic money institutions (EMIs), independent sales organizations (ISOs) and platforms that run many merchants on one gateway.

What Is White Label Merchant Management?

It is the set of back-office tools you use to run a merchant portfolio on a gateway you license but sell as your own. The vendor builds and hosts the tools. You, or your acquirer in an ISO setup, decide which merchants to accept and when they are paid; you set what they pay and what they may do.

You own the merchant relationship and the duties that come with it: onboarding, risk, support and payouts. That is the difference from reselling white-label merchant services under a referral deal. Merchants see only your brand: your back office, your payment pages and your statements.

Who manages what

Split of merchant management duties on a white-label platform
AreaYou (operator)MerchantVendor
Merchants and shopsCreate them, set and change their statusAsks for new shops, keeps its details currentProvides the hierarchy and the back office
KYC and underwritingDecide, or pass the file to the acquirer in an ISO setupSupplies documents and answers questionsProvides fields for status and limits, not the decision
Fees, limits, reservesSet them per merchant and shopAccepts them in its contractCalculates fees and statements
Payment methods and routingEnable methods, write routing rulesOffers shoppers the methods you enabledBuilds and maintains connectors, the integrations with acquirers and payment methods
Users and accessGrant access to your staff and each merchant’s administratorGrants access to its own employeesEnforces the permissions
Risk monitoringWatch fraud and dispute ratios, act on alertsAnswers chargebacks with evidenceSupplies reports, alerts and signals
PayoutsPay merchants, if you receive their fundsReconciles its statementsProduces statements and payout registers

Who receives the funds decides how much of the payout row is yours. In an ISO setup the acquirer approves the merchant and settles to it directly. As a payment facilitator (PayFac), which signs merchants on the acquirer’s behalf and receives their settlement, you underwrite and pay them yourself. Our guide to white-label credit card processing compares the two, and the payment gateway business model shows how each one earns.

How Is a Merchant Portfolio Structured: PSP, Merchant, Shop?

Most platforms use three levels: you as the PSP at the top, merchants (legal entities) under you, and shops (websites, apps or sales channels) under each merchant. Settings, reports and access follow the same levels, so you can treat two sites of one merchant differently.

You

PSP level

Connectors and acquirer accounts, portfolio-wide routing and anti-fraud rules, your own staff users, and the balance and settlements of the whole portfolio.

The legal entity

Merchant level

The contract, the merchant’s administrator and employees, and its statements and payouts across all of its shops.

One site or app

Shop level

Its own keys, payment methods, currencies, fees, limits and reserve, its permission for direct application programming interface (API) access, and its own daily statement.

On eComCharge, a Smart Routing rule set at PSP level applies to every merchant and shop below it, and you can write separate rules for one merchant or one shop. Our guide to payment routing explains how such rules pick a connector.

Reports use the same structure. Transaction statistics filter by gateway, merchant, shop, payment method, currency, transaction type and status, so one high-risk site is visible apart from the rest of its merchant.

How Do You Onboard a Merchant on a White Label Platform?

You, or your acquirer in an ISO setup, check the application and decide on approval and limits; you then create the merchant and its shops in the back office and issue credentials. The checks, including know your business (KYB) verification, are run by you, your verification provider or your acquirer, depending on your model. The platform records their outcome as a status, limits and access.

  1. Application: the merchant, to you

    The merchant sends company details, its owners and directors, the websites or apps to connect, what it sells and its expected monthly volume.

  2. KYC and underwriting: you, or the acquirer in an ISO setup

    Verify the company and its beneficial owners, review each website and assess the risk. The outcome is a decision plus a risk tier, limits and, where needed, a rolling reserve: a share of each payment held back for a set number of days. The full process is in our merchant onboarding guide; for high-risk verticals, see high-risk onboarding.

  3. Merchant and shop setup: you, in the back office

    Create the merchant, add one shop per site or app, then enable payment methods and currencies and set fees and limits for each shop.

  4. Access: you, then the merchant

    Create the merchant’s administrator user. The administrator then adds its own employees and decides what each of them sees.

  5. Integration: the merchant

    The merchant connects through the hosted payment page, the widget, the API or shopping cart payment modules. Payment links and a virtual terminal, a back-office form for card orders taken by phone or mail, let it integrate merchants without code. Direct host-to-host integration is off by default on eComCharge; you allow it per shop.

  6. Go-live: you

    Run test payments, switch the shop to live and set the date of its first risk review.

Rule

The legal duty behind onboarding

In the EU, customer due diligence under Article 13 of Directive (EU) 2015/849 covers identifying the customer and its beneficial owner, understanding the purpose of the relationship and ongoing monitoring of its transactions. Regulation (EU) 2024/1624 sets the same duties in Article 20 and applies from 10 July 2027.

Which Settings Do You Configure per Merchant and Shop?

Six groups: payment methods, currencies, routing, limits, fees and security rules. Most of them belong at shop level, because each site or app has its own risk and its own price list. The table shows what each group controls and a typical use.

Per-merchant and per-shop settings
SettingWhat it controlsTypical use
Payment methodsWhich cards, wallets and local methods a shop acceptsEnable only the methods your acquirer approved for that merchant
CurrenciesThe currencies a shop accepts, and conversion through the currency converterShow shoppers local prices while the merchant settles in one currency
RoutingWhich connector handles each payment, on eComCharge using 50+ conditions such as bank identification number (BIN), country, currency, amount, card type and 3-D Secure statusSend a high-risk shop to the acquirer that accepted it
LimitsTotal amount per period, amount per payment, a list of allowed amounts, and the number of payments per card (transaction limits)Cap a new merchant’s monthly volume until it has a history
Fees and reserveBuy rate (what your acquirer or payment method provider charges you) and sell rate (what you charge the merchant) per transaction type, payment method and currency; rolling reserve percentage and hold period in daysPrice each shop’s payments and hold back a reserve for a high-risk shop
SecurityAnti-fraud rules, 3-D Secure rules on the 3DS Server, and permission for direct API accessRequest 3-D Secure on a first payment from an unknown card

The difference between the sell rate and the buy rate is your revenue, and the platform applies both rates to every transaction type, refunds and chargebacks included.

Good to know

Change limits on evidence

Raise a limit after a review of the shop’s volume, refunds and disputes, not because the merchant asks. Record the reason and the next review date with each change.

How Do User Roles and Access Work in the Merchant Back Office?

Two groups share one back office: your staff, who see the portfolio, and each merchant’s staff, who see only their own merchant. Grant access by duty, one section at a time, so a support agent can answer a merchant without seeing store keys, payouts or other merchants’ data.

Your staff

  • Sections such as statistics or payouts enabled per employee.
  • Server transaction logs of requests to acquirers, with access granted at PSP level or for one merchant.
  • Portfolio analytics in FinStatHub, where each user sees only the merchants assigned to them.

Merchant staff

  • On eComCharge, a merchant dashboard with conversion, decline codes, successful payments and daily statistics for up to 90 days.
  • Dashboard access per employee, set by the merchant’s administrator.
  • Store public and secret keys hidden from merchant employees by default.
  • Statements in short form, without your buy rate or your revenue.

Access rules to set on day one

  • One named user per person, no shared logins.
  • Fee and payout sections for finance staff only.
  • Store keys for the merchant’s technical staff only.
  • Leavers removed on their last day. eComCharge also deletes users who have not logged in for more than 180 days, on the first day of each month.
  • Merchant administrator users checked at every periodic merchant review.

How Do You Monitor Merchant Risk: Chargeback and Fraud Ratios?

Track fraud and dispute counts for each shop against the card schemes’ thresholds, and act before your acquirer has to. One high-risk shop can lift the ratio of the acquirer portfolio that all your merchants share, so a portfolio average hides the problem.

Visa’s Visa Acquirer Monitoring Program (VAMP) fact sheet sets one ratio for card-not-present payments: the monthly count of fraud reports and disputes divided by the count of settled transactions. Thresholds are in basis points (bps), hundredths of a percent.

50 bps
an acquirer portfolio becomes Above Standard
70 bps
an acquirer portfolio becomes Excessive
150 bps
an excessive merchant in the EU, US, Canada and Asia-Pacific from 1 April 2026, with at least 1,500 fraud reports and disputes a month

Source: Visa Acquirer Monitoring Program fact sheet, 2025

Illustrative example

One shop against the merchant threshold

  • Assumed month for an EU shop: 40,000 settled Visa card-not-present transactions, 350 fraud reports and 330 disputes.
  • Ratio: 680 divided by 40,000, or 170 bps.
  • Result: above 150 bps but below 1,500 items, so the shop does not meet both criteria for an excessive merchant. It is still your signal to lower its limits and request 3-D Secure more often.

Warning signs in a merchant’s traffic

  • Refunds and chargebacks rising above the level you set for the shop.
  • Payment amounts that do not match the prices on the shop’s website, a sign of aggregation: accepting payments for a business you did not approve.
  • Many payments in a short time with different cards from one BIN.
  • One email, phone number or Internet Protocol (IP) address behind many different cards.

On eComCharge, anti-fraud tools run rules per merchant, card type and transaction pattern, with refund and chargeback alerts. SmartCheck adds card history, 16 metrics per card over 360 days, as a condition for Smart Routing to request 3-D Secure or reject a payment. Our post on monitoring merchant transactions covers the warning signs in detail.

How Do Payouts and Statements Work per Merchant?

The platform calculates what each merchant is owed; the money moves through your bank or your acquirer, not through the gateway. On eComCharge each shop gets a daily statement at midnight. If merchant funds come to you, your finance team builds a payout register for any period and pays it; if the acquirer settles directly, you only reconcile.

Who pays the merchant
ModelWho settles to the merchantWhat you manage on the platform
Technical PSP or ISOThe acquirer, directlyFees, reports and reconciliation; no payouts
Payment facilitator or licensed aggregatorYou, from funds the acquirer settles to youDaily statements, reserves, payout registers and payments

From daily statement to payout

Steps 3 and 4 apply when merchant funds come to you.

  1. Daily close: the platform

    At midnight it collects the previous day’s transactions for each shop, recalculates the reserve and draws up a statement in each currency the shop accepts.

  2. Statement: the platform

    Each statement shows counts and amounts per transaction type and payment method, the fees from your buy and sell rates, the reserve withheld and released, the amount due to the merchant and your revenue.

  3. Payout register: your finance team

    Choose the first and last day of the pay period. The platform totals the amounts due across all of the merchant’s shops, per currency.

  4. Payment: your finance team and your bank

    Send the money, then mark the register paid. The statements behind it are stamped with the date and time and cannot enter the next calculation.

Note

Rolling reserve and chargeback losses

The rolling reserve goes back to the merchant when its hold period ends. Until then it covers chargebacks a merchant can no longer pay, a loss that otherwise falls on whoever stands behind the merchant under the contract, often you. The financial statements post shows how eComCharge calculates it.

If you run a marketplace that pays many sellers from one payment, you need extra logic; see our post on split payments and vendor payouts.

How Do You Suspend or Offboard a Merchant?

Restrict before you terminate. A graded status stops new payments while refunds and chargebacks still go through, so shoppers are repaid and disputes are answered. Close the merchant only when its disputes, reserve and final payout are settled, and keep its records as the law requires.

Status

No new payments

The shop can no longer accept payments, but it can still refund earlier ones.

Status

Staff-only operations

The merchant cannot run chosen transaction types; your staff still can, for example to refund a shopper.

Status

Read-only login

The merchant logs in to see its statistics and nothing else.

Offboarding checklist

  • Switch every shop of the merchant to no new payments.
  • Keep refunds and chargeback responses open until the dispute period ends.
  • Release the rolling reserve after its hold period, net of chargebacks, or confirm the acquirer has if it holds the funds.
  • Run the final statement; if you pay the merchant, make the final payout and mark it paid.
  • Export transactions and statements as .xlsx or .csv files, or through the API.
  • Remove the merchant’s users, or leave one read-only login if the contract needs it.
  • Keep due diligence documents and transaction records for five years after the relationship ends, under Article 40 of the Directive and, from 10 July 2027, Article 77 of the Regulation.

What Are the Risks, and Who Does Not Need It?

The main risks come from the portfolio, not the software: a merchant you cannot see clearly, access that is too wide, and dependence on a single acquirer or vendor. Each has a control you can set up before your first merchant goes live.

Merchant management risks and how to reduce them
RiskWhat happensHow to reduce it
Weak onboardingA merchant processes for a business you did not approveReview each shop’s site before go-live; use a list of allowed amounts; keep direct API access off
Access too wideStaff or merchant employees see keys, payouts or other merchantsGrant sections by duty; keep store keys hidden by default
One high-risk shopIts disputes lift the ratio of the acquirer portfolio you shareShop-level limits and reserves; a weekly review of fraud and dispute counts
Acquirer shut-offAn acquirer closes a vertical and your shops stopKeep a backup connector with routing rules ready, as part of a multi-acquirer strategy
Vendor lock-inMerchants, tokens and history live on the vendor’s platformAgree data export and token migration terms in the contract
Note

Who does not need it

A merchant that sells only its own goods needs a merchant account and a gateway, not portfolio tools. If you refer merchants to another company’s gateway for a commission, that company manages them. And with a handful of merchants on one acquirer, a hosted gateway account from an existing PSP may be the simpler start.

Merchant Management in eComCharge

eComCharge is a white-label payment gateway for PSPs, acquiring banks, EMIs and platforms that serve online merchants. Merchant management sits in the same branded back office as routing and reporting. You choose software as a service (installation from 1 week) or your own servers (from 3 months).

  • PSP, merchant and shop hierarchy with roles, shops and permissions, managed from one back office.
  • Rates and fees per merchant and shop; the system calculates what each merchant owes, with daily statements and payout registers.
  • Limits, status and verification under your control, and direct API access allowed per shop.
  • Smart Routing with 50+ conditions at PSP, merchant or shop level, and SmartCheck card history.
  • Reports by merchant, method or currency, .xlsx and .csv export, a Report API and real-time webhooks.
  • PCI DSS Level 1, 170+ connectors, and 24/7 technical support for you and your merchants.

eComCharge pricing depends on your specific needs, so contact our sales team for a quote. See white-label processing for PSPs or our white-label payment gateway software.

Frequently asked questions

It is the back office of a white-label payment gateway where you run your merchant portfolio under your own brand: onboarding merchants, configuring their shops, fees and limits, controlling user access, monitoring fraud and disputes, and producing statements and payouts. The vendor supplies and hosts the tools; you make the decisions and own the merchant relationship.

It is the merchant-facing side of the same back office, shown under your brand and domain. Merchants log in to see their payments, dashboards and statements, create payment links and manage their own employees’ access. They see only their own data, and in short form: your buy rate and your revenue stay hidden.

You do, or your acquirer does, depending on your model. In an ISO setup the acquirer approves each merchant; as a payment facilitator you verify and underwrite merchants yourself. The platform does not make the decision. It records the outcome as the merchant’s status, limits, reserve and access.

Yes. On eComCharge a merchant can sell through payment links created in its back office, with a limit and an expiry date per link, or take card details by phone or mail in the virtual terminal. Shopping cart payment modules connect a store without code. Direct host-to-host integration is off by default and enabled by you per shop.

Yes. You create each merchant’s administrator, and the administrator adds employees and decides what they see, such as the dashboard. On eComCharge the store’s public and secret keys are hidden from merchant employees by default, and users who have not logged in for more than 180 days are deleted automatically.

Under Visa’s Acquirer Monitoring Program, a merchant in the EU, the US, Canada or Asia-Pacific is excessive from 1 April 2026 at 150 basis points of fraud reports and disputes over settled card-not-present transactions, with at least 1,500 items a month. Set your own warning level lower and check it per shop. Other schemes run their own programmes.

No, the gateway moves no money. It calculates what each merchant is owed: on eComCharge, a daily statement per shop and a payout register for any period. If the acquirer settles to merchants directly, you only reconcile. If funds come to you, your finance team pays merchants from your bank account and marks the register paid.

On eComCharge merchant management is part of the white-label gateway, not a separate product. eComCharge pricing depends on your specific needs, such as the deployment model, transaction volume, connectors and customisation, so contact our sales team for a quote. Add your own costs for onboarding checks, risk staff and support.


Respectfully, the eComCharge Team

eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.

Request demo

Relevant guides

White Label

High-Risk Merchant Onboarding: Checks, Scheme Rules and What to Automate

How PSPs, acquiring banks and EMIs onboard high-risk merchants: which MCCs count as high risk, the KYB, UBO and sanctions checks EU law requires, underwriting and reserves, Visa registration and monitoring, what to automate and how to keep an evidence trail.

Oksana Mikhailovskaya
Oksana Mikhailovskaya March 3, 2026
White Label

Custom Payment Solutions: What to Customise and How to Scope It

A guide for PSPs, banks and platforms on custom payment solutions: custom build vs off-the-shelf vs white-label, what can be customised, how a connector or payout flow is scoped and delivered, what drives cost and time, and the risks.

Oksana Mikhailovskaya
Oksana Mikhailovskaya July 1, 2025

Set up your payment processing system

in 7 days, not a year
Request demo