Everything about a merchant,
in one profile.
Per-merchant configuration, fee templates, MID assignments and full activity history in one console. Each merchant gets the configuration its business model needs.
Every merchant has different needs
Different verticals, different geographies, different transaction volumes - different configuration. Merchant Management is built around the assumption that no two merchants are the same.
Per-merchant config
Everything that defines a merchant in one profile: their terminals, the fees that apply to them, their risk settings, documents, users and current status, with the history of who changed what.
Fee templates
Each merchant can be routed across a different mix of MIDs. The mix is configurable and can be changed without disruption.
Activity history
Different merchants get different risk profiles - velocity limits, BIN-country rules, refund caps, all configurable per merchant.
Activity history
Full transaction, settlement, chargeback and configuration history per merchant. Searchable, filterable, exportable.
Per-merchant reporting
Run any report scoped to a single merchant - volume, decline reasons, chargeback ratio, fee breakdown.
How merchants are managed
- Configure
On approval, the merchant gets fee templates, MID assignments and risk thresholds applied based on the rules engine.
- Monitor
Track volume, decline patterns, chargeback ratios per merchant. Alerts on threshold breaches.
- Adjust
Update fees, MID assignments or risk thresholds at any time. Changes apply at the next transaction.
Frequently asked questions
Can I bulk-update merchants?
Configuration that is shared can be applied through templates rather than edited merchant by merchant, so a change across a group of merchants is a template change rather than a repetitive afternoon.
How fast does a fee change apply?
Immediately. The next transaction processes against the new fee structure.
Can a merchant see its own configuration?
Yes. A merchant can see its own configuration in its portal, which cuts down the back and forth about which settings are actually in force.
How are merchant suspensions handled?
Suspend at the merchant level (all transactions blocked) or at the MID level (specific routing disabled). Both reversible from the admin console with full audit log.
Can different merchants have different KYC requirements?
Yes. The onboarding rules engine assigns different KYC providers and document requirements based on merchant type, geography or risk score.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.