FeeVerify for payment gateways

A gateway connects merchants to acquirers and charges for every transaction it carries. Many also resell acquiring, bundling interchange, scheme fees and acquirer markup into one merchant price, and every gateway pays providers for services such as 3-D Secure, tokenisation and fraud screening. FeeVerify validates what you pay for each of them against your agreements, checks that merchants are billed what their contracts say, and keeps checking each month as costs change.

What does a gateway pay, and where does the margin leak?

A gateway's own fees are usually simple: a charge per transaction, sometimes a monthly fee. The costs behind them are not. A gateway that resells acquiring pays interchange, scheme fees and an acquirer's markup on every transaction it sells at a bundled price. Every gateway pays service providers per call for 3-D Secure, tokenisation, network tokens, account updating and fraud screening, often under tiered contracts.

The margin leaks when those costs drift from their contracts, when a scheme change lands under a bundled price that does not move, and when merchants are billed less than their contracts say. Each is small per transaction, and a gateway carries a great many transactions.

What you pay or chargeWhere it leaksHow FeeVerify checks it
Acquiring behind bundled pricingAcquirer markup, minimums and tiers that drift from the contractRe-costs each transaction against the acquirer contract for its market
Interchange and scheme feesDowngrades; scheme fees on the wrong region or product; pass-through marked upRecalculates each fee from the scheme schedules and flags downgrades with their cause
Provider services: 3-D Secure, tokens, account updating, fraud screeningPer-call fees above the contracted tier, minimums applied twice, calls billed that never happenedChecks each provider invoice against its contract and your own call and transaction counts
Bundled merchant pricingPrices set once and left while the costs underneath roseSets each merchant's true cost beside its bundled price, month by month
Gateway fees billed to merchantsPer-transaction and monthly fees in the contract never charged, or charged at an old rateChecks each merchant's billing against its contract

Four ways FeeVerify protects a gateway's margin

FeeVerify sits as an independent control layer between what you pay acquirers, schemes and providers and what your merchants pay you. Looking back, it recovers overcharges and finds fees that were never billed. Going forward, it keeps bundled prices above cost and shows the true cost of each acquirer and provider.

Looking back: recover what has leaked

Recover overcharges

Acquirer, scheme and provider billing is broken down and checked against your agreements and the published schedules. Variances come back quantified, sourced and ready to claim.

Bill what merchants owe

Gateway and service fees in merchant contracts that were never charged, or charged at an old rate, are found and quantified.

Going forward: keep bundled prices above cost

Keep pricing in step with cost

Each new month of billing is validated as it lands, so a scheme change or a provider price rise is caught before it erodes the bundled prices that sit on top of it.

Choose acquirers and providers on clear economics

The true cost of each acquirer and service provider sits on one basis, clause-linked and sourced, ready for routing decisions and your next provider negotiation.

None of this needs new headcount. AI does the high-volume analysis, and experienced payments specialists sign off every material finding.

Proof in production

FeeVerify is proven on a tier-one cross-border payments business, anonymised here, that runs blended and IC++ acquiring across multiple markets and had no AI-led billing reconciliation before. The diagnostic ran on one month of its real production data and was delivered within 30 days of the data arriving.

A gateway that resells acquiring carries the same acquirer and scheme costs that engagement checked, and its provider contracts are rules in the same way. FeeVerify builds rules from each agreement and re-costs every transaction against them.

44M+transactions re-costed from one month of data
228expected-fee rules from over 100 contract packages
92%invoice-to-rule tie-out in the first market
60+source-linked reports, every number traceable
6-figurerecurring variance traced to a single contract clause
30 daysfrom data ingestion to a diagnostic on real production data

Figures are from an anonymised engagement; the client is not named. The proof page sets out the method and the disclosure.

Getting started

You start with a 30-day diagnostic on one month of your own data, and you see verified recoveries before any recurring fee. A good first scope is the acquirer or provider with the largest bill, or the bundled price you suspect no longer covers its cost. The first call agrees that scope and the data we need.

  1. Share your data

    Your acquirer, scheme and provider contracts, your merchant pricing, and one month of transaction, settlement and invoice files. No integration is needed to start.

  2. 30-day diagnostic

    Every transaction is re-costed. Variances are quantified and linked to the clause behind them, and the findings are reviewed with your team.

  3. Recover and continue

    FeeVerify's fee is a success fee on the value you accept, with no ongoing commitment. Optional continuous assurance then checks each new month as it lands.

Pilot terms are agreed in the contract. The how it works page covers each step in more detail.

Questions gateways ask

We do not resell acquiring. Is FeeVerify still useful?

Yes, for two things. Your provider costs: per-call fees for 3-D Secure, tokenisation, account updating and fraud screening, checked against each contract and your own call counts. And your revenue: whether each merchant is billed the gateway fees its contract sets.

Can FeeVerify tell us which bundled prices lose money?

Yes. Each merchant's true cost, from interchange and scheme fees through acquirer markup and provider charges, is set beside its bundled price every month. Merchants and segments where the price no longer covers the cost show up before the loss grows.

Do you need card numbers?

No. Files containing full card numbers are rejected at upload, so you send masked or tokenised data. FeeVerify needs the fields your fees depend on, such as card type, region, product and amount. Your data stays in an environment only your organisation can see, and it is never used to train a model. The governance page has the detail.

How is FeeVerify paid?

You see verified recoveries before any recurring fee. After the 30-day diagnostic, FeeVerify's fee is a success fee on the value you accept, whether that is money back, cost savings or revenue gained, and there is no ongoing commitment. Specific pilot fees and percentages are set in the contract.

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.