Frequently asked questions
These are the questions payments leaders, finance teams and procurement reviewers ask most often about FeeVerify. Each answer stands on its own and links to the page that covers the subject in full: what FeeVerify checks, how it handles your data, how an engagement runs and is paid for, and what the evidence looks like.
About FeeVerify
What is FeeVerify?
FeeVerify breaks down complex payments billing and validates it. It works out what each fee should be from your agreements and from the scheme fee schedules, side letters and pricing that fill in what a contract leaves out, checks every transaction against that, and traces every variance to its source. It then keeps checking each new month and gives you clear economics for routing and negotiation. It is an independent control layer: it processes and routes nothing. It pairs people who know payments with technology: AI does the high-volume analysis and experienced payments specialists sign off every material finding before it reaches you, so you need no new headcount. You keep the rulebook it builds. Read how FeeVerify works.
Who is FeeVerify for?
FeeVerify works across the payment chain: payment processors, PSPs, payment facilitators, ISOs, payment gateways, issuing banks, acquiring banks and enterprise merchants. The buyer is usually the CFO, Head of Payments, Treasury or Internal Audit at a business that cannot easily check what schemes and providers bill it. It is most useful at a renewal, an audit, or when costs rise without an explanation. See who FeeVerify is for.
Which costs does FeeVerify check?
FeeVerify checks the costs set by your agreements, side letters and scheme fee schedules: interchange, including downgrades, scheme fees, acquirer markup, volume tiers, rebates and incentives, surcharges, FX and tax on fees. Each fee your agreements allow becomes a rule. Where a contract is silent or loose, the term is filled from the scheme schedules and other sources and graded for confidence, and every transaction is checked against the rules that govern it. See what goes into an investigation.
Our processor already reconciles for us. Why would we need FeeVerify?
A processor's reconciliation shows that its invoice matches its own records. It does not test whether those records apply the rates, tiers and exceptions in your contract. FeeVerify processes and routes nothing, so it has no stake in the answer: it reads your agreements independently, recalculates every transaction, and shows where billed cost departs from what you agreed, with the clause and the rows attached. See why costs rise when volumes do not.
Is FeeVerify independent of our providers?
Yes. FeeVerify processes and routes nothing, and sells no acquiring, processing or routing, so its findings carry no commercial agenda. It works as an independent control layer owned by your Finance team, not by a provider, which is why its evidence can be put to an acquirer, processor or scheme and relied on by internal audit. Read how FeeVerify is governed.
Does FeeVerify only look at past bills?
No. The diagnostic starts with one month of past billing, because that is where money already lost can be recovered. Going forward, continuous assurance validates each new month as it lands, so cost changes are caught before they compound. The rulebook also gives you the true cost of each provider and route on one basis, for routing decisions, pricing and your next negotiation. See what happens after the first month.
Does FeeVerify replace our payments or finance team?
No, and it needs no new headcount either. AI does the high-volume reading and re-costing that few teams have the people to do by hand, and your team decides what to do with the results. You approve the data dictionary before any agent runs, experienced payments specialists steer each investigation, and a named reviewer signs off material findings. Decisions about renegotiation or recovery stay with your people. See who does what in an investigation.
Data and governance
Where is our data stored?
Your contracts, invoices and transaction data sit in a ringfenced, per-tenant environment that belongs to your organisation. There is no co-mingling and no shared fine-tuning layer between tenants. Where you need a specific data-residency region, it is agreed with you as part of onboarding, and any transfer outside your region is agreed in advance with safeguards such as standard contractual clauses. Read how FeeVerify handles your data.
Is our data used to train AI models?
No. Your commercial data is never used to train, fine-tune or improve any machine-learning model, whether FeeVerify's or a third party's. Where the platform uses model providers to read documents or reconcile data, it does so under agreements that prohibit training on your content or keeping it beyond what is needed to return a result. Read the privacy policy.
Do you need our customers' card numbers?
No. FeeVerify never asks for card numbers. Every uploaded file is scanned on arrival, and a file containing full card numbers (PANs) is rejected before it lands, so you send masked or tokenised card data only. Card type, issuing region and similar fields are enough to recalculate interchange and scheme fees. See what FeeVerify needs from you.
Who signs off a finding before we act on it?
A named reviewer. Every material output lands in needs review and waits for a named sign-off before it reaches a decision-maker. Before that, every rule is graded High, Medium or Low against named sources, and rules graded Low go to a payments specialist before they are treated as final. Agents read and recalculate; people decide. See the controls around every finding.
What is logged, and can our auditors see it?
Every action, by an agent or a person, is recorded in the worklog with the operator, the source, the output and the status. Each figure in a report links back to the clause or data row it came from, so an auditor can follow a finding from the invoice line to the contract. The worklog belongs to your tenant. Read about the worklog and grading.
What happens to our data when an engagement ends?
Your commercial data is kept only while your tenancy is active or as you instruct. When you delete a tenant, or at the end of an engagement, the associated data is deleted within the period set out in your agreement. Audit-log metadata may be kept for a limited period where the law requires it. Read the retention terms.
The engagement and how FeeVerify is paid
What is the 30-day diagnostic?
The diagnostic is the core of a risk-aligned pilot. Over 30 days from the data arriving, FeeVerify re-costs every transaction or fee line in scope, quantifies each variance and links it to its clause, and reviews the findings with your team. You see verified recoveries before any recurring fee, and you keep the rulebook and the variance map whatever you decide next. Book a discovery call.
What do we need to provide?
Your contracts and agreements, side letters and incentive tiers, pricing, and one month of settlement, clearing, scheme billing or invoice files. The exact list depends on where you sit in the payment chain. Files can arrive as your counterparties send them, including scanned PDFs and contracts in languages other than English, and no integration is needed. See the full data list.
How is FeeVerify paid?
FeeVerify starts with a risk-aligned pilot, so you see verified recoveries before any recurring fee. After the diagnostic it earns a success fee on the value you accept, whether that is money back, cost savings through optimisation or revenue gained from better commercial decisions, with no ongoing commitment, and continuous assurance is optional once the value is proven. Pilot fees and success-fee percentages are subject to contract, and FeeVerify does not publish them. Read about FeeVerify and how it works with clients.
What do we keep if we stop?
You keep the rulebook, the variance map and the reports, from day one. The rulebook is a structured record of every fee your contracts allow, each rule with its clause and confidence grade, so it stays useful in a renegotiation or an audit whether or not you continue with FeeVerify. See what the pilot includes.
What does it mean to become a design partner?
A design partner works with the team building FeeVerify while the product matures. Design partners get preferential terms and a say in the roadmap and the order of work. As with any pilot, a design partner keeps the rulebook and the variance map built on its data. Ask about becoming a design partner.
Which markets does FeeVerify work in?
FeeVerify is proven on real production data from a tier-one cross-border payments business operating across multiple markets (blended and IC++ acquiring), reading contracts in several languages and currencies. It works globally: the method is the same in every market, whatever the language or currency of the contracts. See the markets FeeVerify covers.
Results and evidence
What has FeeVerify found so far?
In an anonymised engagement for a tier-one cross-border payments business operating across multiple markets (blended and IC++ acquiring), FeeVerify re-costed 44M+ transactions from one month of data against 228 expected-fee rules from over 100 contract packages. It tied out 92% of invoice lines to a rule in the first market, wrote 60+ source-linked reports and traced a six-figure recurring variance to a single contract clause, 30 days from data ingestion to diagnostic. Read what the engagement found.
Why is the client not named?
The engagement was confidential, and FeeVerify never names a client without permission. The proof page describes the client as a tier-one cross-border payments business operating across multiple markets (blended and IC++ acquiring), states what the figures cover, and shows the evidence pattern without identifying details. FeeVerify does not publish customer names, logos or testimonials. See the anonymised disclosure.
What does a finding look like?
A finding names the rule, the clause it comes from, the transactions behind it, the amount billed, the amount expected, the difference and a confidence grade. It reads as a claim you could put to the provider or scheme: this clause, these rows, this much. A named reviewer signs it off before it reaches a decision-maker. See how variances are traced to the clause.
How do we know a finding is right?
Every rule carries a confidence grade of High, Medium or Low, set against named sources, and every figure links to its clause or data row so you can check it yourself. Rules graded Low go to a payments specialist first, and material findings wait for a named reviewer. A finding that rests on an interpretation of the contract says so. Read how confidence grades work.
Can we use the findings to recover money?
Yes. Each finding comes with the clause, the rows and the amount, ready for a renegotiation or a recovery claim. Recovery still depends on the counterparty: acquirers told the Reserve Bank of Australia that schemes "did not proactively reimburse" billing errors (RBA, 2025) so a claim needs the clause and the rows behind it. See how scheme fee errors are found.
How often is the check repeated?
The diagnostic covers one month of data. Once the value is proven, optional continuous assurance runs the same rulebook on each new month, so scheme, FX and downgrade changes are caught as they land rather than a quarter later. When a contract changes or a new fee notice arrives, the affected rules are updated and graded again. See how continuous assurance works.
Start with one month of your own data.
A pilot begins with the agreements that protect both sides, then your contracts and one month of settlement data, scoped with a payments specialist on the first call. The 30-day diagnostic re-costs every transaction against them and shows each variance with its clause, before any recurring fee.