Skip to content

Platform modules

Merchant Management System for PSPs and Acquirers

A merchant management system is the software a payment provider uses to run every merchant it serves, from the first application to the last payout. It brings the whole lifecycle, from onboarding and compliance checks to pricing and settlements, into one interface, so your team stops copying data between spreadsheets and separate tools.

We built ours for PSPs and PayFacs, and for the acquiring banks and ISOs that run large merchant books. The goal is simple to state and hard to reach without software: grow the number of merchants without growing the back office at the same rate.

What is a merchant management system?

People often confuse it with a payment gateway, and the two solve different problems. A gateway processes each payment. It carries the card data from the shopper's checkout to the acquirer so that one transaction can be authorized and captured. They aren't the same thing.

The merchant management software runs everything around those payments. It onboards the merchant, checks who owns it, decides what it pays, watches its chargebacks and works out what it's owed.

Put shortly, the gateway moves the money for each payment, and the merchant management platform runs the relationship with the business that sends it, which is why a PSP with a good gateway and no MMS still ends up running its merchants on spreadsheets. We offer both, so one provider can cover the whole flow.

Modules of our merchant management system

Each module replaces a job that otherwise lives in a spreadsheet or in somebody's inbox. Together they cover the full merchant lifecycle.

Module What your team does with it
Onboarding and KYB/KYC Collects applications, verifies the business and its beneficial owners, keeps a compliance trail
Underwriting and risk scoring Scores merchants at onboarding and later, with your own rules for approve, review or decline
Transaction monitoring Flags unusual volumes, suspicious activity and threshold breaches as they happen
Chargebacks and disputes Tracks each case with its status, evidence and deadlines
Pricing and tariffs Sets fees per merchant, group or product, and changes terms without rebuilding the setup
Settlements and reconciliation Calculates settlements, fees and reserves, then reconciles payouts against processed volume
Merchant dashboard Gives each merchant a self-service view of transactions, statements and performance
Portfolio view Segments and filters merchants by status, risk, region or performance
Roles and audit trail Controls who sees and does what, with a full record for audits
APIs and webhooks Connects the system to your gateway, CRM, core banking and reporting tools

The dashboard row deserves a second look. Every question a merchant can answer by itself is a support ticket your team doesn't have to handle.

How merchant onboarding runs

Onboarding is where most merchant operations slow down, so ours runs as a guided workflow with a status at every step:

  1. The merchant fills in a structured application with business details, documents and processing needs.
  2. The system verifies the business, its beneficial owners and the documents against your compliance rules.
  3. Business and ownership checks confirm legitimacy, ownership structure and sanction or watchlist status.
  4. Edge cases go to your team for manual review, with all the context in one place.
  5. You approve, ask for more information or decline, based on clear criteria.
  6. Once approved, the merchant gets its merchant ID, pricing and access, and can start processing.

Nothing stalls in an inbox, because each application always shows what it's waiting for. Our guide to merchant onboarding for PSPs goes deeper into the KYB documents to ask for.

Risk doesn't end at approval

Merchants change. One that looked fine in March can run a different business by June, so the system reassesses merchants as their behavior and volumes change and watches for unusual spikes and threshold breaches in real time.

Chargeback ratios get special attention. You see them climb and can act before they reach the card schemes' penalty thresholds, instead of finding out from an acquirer's letter after the fines have already landed on your account. Merchant category codes stay accurate too, which keeps both risk scoring and pricing honest. For the rules and alerts behind this, see our page on merchant risk monitoring.

Settlements your finance team can trust

Settlement is where accuracy matters most, because every error is somebody's money. Settlements run on the schedules you define for each merchant or group, so a riskier merchant can settle weekly behind a rolling reserve while a steady one settles daily without holdbacks.

Fees and reserves apply automatically, and each payout can be tracked from calculation to completion. Statements and data exports for accounting and audits come out of the same place. Your finance team gets figures it can check instead of reports rebuilt by hand at the end of each month.

Connecting it to the rest of your stack

No PSP runs on one system. Ours connects through open APIs and webhooks to whatever sits around it, from gateways and KYC providers to the CRM and accounting systems your teams already use.

Webhooks keep everything in sync in real time. They fire on merchant status changes, onboarding milestones, risk flags, settlement updates and report exports, so the other systems learn about a change the moment it happens.

Moving an existing portfolio

Switching systems usually means the dreaded re-onboarding of every merchant. Here, existing merchant accounts can be imported straight into the system, so you move a portfolio over and keep operating instead of starting again.

Questions

Is a merchant management system the same as a payment gateway?

No. A gateway processes individual payments, and a merchant management system runs the merchant relationship around them: onboarding, compliance, risk, pricing and settlements.

Who uses merchant management software?

Payment service providers, payment facilitators, acquiring banks and ISOs. Anyone who serves many merchants and has to onboard, price, monitor and settle them uses one.

Can merchants see their own data?

Yes. Each merchant gets a self-service dashboard with its transactions and statements, which cuts the number of support requests your team receives.

Does it work with tools we already use?

It connects through APIs and webhooks to the gateways and back-office tools you already run, KYC providers included. Tell us your stack on the demo and we'll show where each piece plugs in.

See your portfolio in it

Judge a merchant management system by putting one of your real merchants into it.