Use published network rules and your own written account terms when evaluating payment-processing numbers. This guide does not present an original survey, a representative merchant dataset, or verified industry averages.
Keep network monitoring measures separate
Visa’s Acquirer Monitoring Program (VAMP) combines reported fraud and disputes for Visa card-not-present transactions. Mastercard operates separate chargeback and fraud programs. Ask your acquirer which regional rules, transaction counts, reporting periods, and account limits apply; one percentage cannot describe every program.
Read MATCH codes in the current Mastercard manual
- 04: Excessive Chargebacks.
- 05: Excessive Fraud.
- 12: PCI Data Security Standard Noncompliance.
- 14: Identity Theft.
- Repeated application declines do not establish a MATCH listing. Request written confirmation from the acquirer, including the reporting institution and reason code.
Separate processing fees from reserves
Compare transaction charges, monthly fees, gateway costs, and other fees using the same volume and transaction mix. Show reserve withholding separately: it affects when cash is available and is governed by the merchant agreement, including permitted deductions and release conditions. A reserve percentage is not itself a processing fee.
Treat approval estimates as account-specific
Request an estimate after the processor reviews the business model and documentation. Missing records, product eligibility, prior terminations, and the processor’s review can change timing. Cybin helps prepare the file; the processor or acquiring bank decides whether to approve it and on what terms.
Check what a statistic actually measures
- Look for a named source, publication date, population, and sample size.
- Check whether a ratio uses transaction count or dollar value, and which reporting period it covers.
- Distinguish an actual merchant quote from an industry average or a marketing example.
- Do not treat a market-size forecast as evidence that a processor accepts a product.