Continuous sub-merchant monitoring after boarding
A boarding decision is a snapshot. The portfolio risk is what the sub-merchant does next. Here is why monitoring has to continue after boarding, and how to catch drift before it shows up in a ratio or a sponsor-bank review.
The risk is after the decision
You can board a sub-merchant cleanly and still inherit a problem. Chargebacks climb, fraud appears in a new pattern, ownership changes, the business model shifts, or a Mastercard MATCH listing appears that was not there at boarding. Most of those signals never trigger a formal case. They sit in the large share of monitoring output that closes without escalation. But they accumulate, and by the time they surface in your VAMP ratio or in a sponsor-bank request, the cost to the portfolio is already booked.
What continuous monitoring watches
Dispute and fraud drift, new MATCH listings, sanctions and watchlist changes, beneficial-ownership and registered-agent changes, and shifts in processing pattern or MCC. Each is produced by a different tool, and the value is in seeing them together, on the same sub-merchant, over time. A single signal in isolation rarely tells you much; the trend across signals does.
One record per sub-merchant, monitored over time
FinQub is the single source of truth for fintech risk decisions. It sits alongside your fraud, dispute, sanctions, and KYB tools and lands every signal each produces on one record per sub-merchant.
Drift is visible as it happens. Every new signal attaches to the same record, so a sub-merchant trending toward trouble is on the record the day the signal arrives, not in next month's report.
You decide, the record remembers. A vendor score is a signal. Your rulebook or your team decides whether to hold, review, or terminate, and FinQub records the decision, who made it, and the evidence it stood on. If you terminate and add the merchant to MATCH, that disposition is on the record too.
Ready for the request. When a sponsor bank or acquirer asks for monitoring history on a set of sub-merchants, one query produces a signed exam packet per merchant, with the full timeline.
Frequently asked questions
Why isn't boarding enough?
A sub-merchant that looked clean at boarding can drift: chargebacks climb, fraud appears, ownership changes, or the business model shifts. Most of those signals never trigger a formal case, but they accumulate, and by the time they show in your VAMP ratio or in a sponsor-bank review, the damage is done. Monitoring has to continue after the boarding decision.
What should continuous monitoring watch for?
Dispute and fraud drift, new Mastercard MATCH listings, sanctions and watchlist changes, beneficial-ownership and registered-agent changes, and shifts in processing pattern or MCC. Each is a signal about the same sub-merchant, and the value is in seeing them together over time, not in separate vendor consoles.
Does FinQub generate the monitoring alerts?
Your fraud, dispute, and screening vendors generate the signals. FinQub is the record they land on: every new signal attaches to the same sub-merchant record over time, so drift is visible as it happens. The signal is a signal; your rulebook or your team decides whether to act, and FinQub records the decision.
All of it runs on your existing gateway, acquirer, and KYB tools. FinQub is the single source of truth for fintech risk decisions they report into. See how the same record handles VAMP at boarding, or book a short walkthrough below.