Every ISO you sponsor, every approval, with its evidence.
See each approval the day it happens, on the processors your ISOs already use. Prova never signs a merchant and never competes with your ISOs.
Every ISO you sponsor, in one portal.
These are the bank screens, shown with demo data. Each ISO reports into them on the processor it already uses.
- One row per ISO
- Volume, chargebacks, fraud, network program enrollments, and MATCH filings for every sponsored ISO, on one scorecard.
- Twelve months of the whole portfolio
- Chargeback ratio, fraud ratio, and volume against each ISO's own baseline, so a drift shows up as a bar before it becomes a fine.
- Findings with a date on them
- Last review, next review, and every open finding, kept next to the record it is about.
Bank portal, demo data
Risk, by ISO and by merchant
Every sponsored ISO ranked by chargeback ratio against the network thresholds. Under it, the merchants running at two or three times their usual volume this week.
Bank portal, demo data
Compliance with a clock on it
Brand-risk findings carry their reporting deadline. Terminated merchants wait in the MATCH queue with the reason code attached, next to the merchant record they concern.
Bank portal, demo data
Residuals and reserves, per ISO
Gross volume, interchange, network fees, ISO residual, and bank margin per ISO. Downgrades by reason. Reserves required, funded, held back, and releasable.
Between the bank and its ISOs, never in their place.
- Never a competitor
- Prova never becomes an ISO or an acquirer and never signs a merchant. Visa's rules make that a condition of holding a bank's data. We hold ourselves to it.
- Your data stays in your program
- Merchant files, owners, bank accounts, and KYB results stay with the bank that owns them. No merchant fact crosses from one bank's program to another's.
- Exam-ready as you go
- Each decision keeps its evidence, its sign-off, and the policy it was made under. The file an examiner asks for already exists.
What one file never shows.
An illustration with made-up names.
Swipe sideways to see the whole graph.
- Four merchants, one owner, two ISOs
- Each ISO sees its own two merchants. You see the owner behind all four.
- The same merchant, underwritten twice
- Today the ISO underwrites a file and the bank underwrites it again from the same documents, with neither seeing the other's reasoning. On Prova you read the ISO's decision and its evidence.
- Rings look clean one file at a time
- A ring opens merchants that share owners, accounts, and addresses across ISOs. Each file passes on its own. Across the whole program, the links show.
Agents do the work. People make the calls.
- Agents work inside limits each bank and ISO sets.
- People approve, decline, and sign. An agent never makes the final call on a merchant.
- Every action an agent takes is written to the same record as the decision.
Boarding agents
Take the application, gather what is missing, run identity and business checks once, and bring the file to a person with the evidence attached.
Monitoring agents
Check every merchant against the record and the network thresholds every day. Hold what looks wrong and say why.
Compliance agents
Keep each decision filed under the policy it was made on, with its evidence and its sign-off.
How a pilot runs.
Prove it on your own files before anything changes for your team.
Backtest
Last year's approvals run through the record. You see what it would have caught.
Shadow
Agents work new files beside your team. Your people still make every call.
Readout
Time to decision, rework, and losses, scored against your own baseline.
Nothing gets ripped out.
One ISO goes live
Its merchants board through Prova on the processor it already uses.
You watch the same record
You see every approval the day it happens, with the evidence, instead of a monthly spreadsheet.
Your other ISOs join
Owners and accounts that span ISOs show up for the first time.
Request a backtest.
Tell us about your program. The first call is 30 minutes, there is nothing to install, and we agree together which files a backtest would run on.