10 things to know before you buy Payment processors

Practical buying checks for payment processors, with the jargon explained.

  1. Model the actual transaction mix Compare costs using card types, values, countries, online versus in-person sales and monthly volume. A low headline percentage can be outweighed by fixed transaction and cross-border fees.

  2. Include every charge Price authorisation, refunds, chargebacks, currency conversion, terminal rental, PCI programmes and minimum monthly fees. PCI refers to the card industry security rules that apply when handling card data.

  3. Check settlement timing Find out when funds reach the bank, whether weekends differ and when reserves can be withheld. Faster settlement may cost extra but can materially improve cash flow.

  4. Understand contract and termination Check minimum terms, notice windows, automatic renewals, price-change clauses and terminal return fees. Merchant acquiring and terminal rental may be separate contracts with different end dates.

  5. Test integration and reconciliation Confirm compatibility with the website, till and accounting system. Settlement reports should let finance staff match gross sales, fees, refunds and net deposits without manual guesswork.

  6. Plan for disputes and fraud Review fraud controls, evidence requirements, chargeback fees and response deadlines. Stronger checks can reduce fraud but may reject genuine customers, so settings need measured adjustment.

  7. Reduce card-data exposure Hosted payment pages and tokenisation, which substitutes a reusable code for card details, can reduce what the business stores. Confirm the supplier explains the remaining PCI responsibilities accurately.

  8. Provide an outage fallback Ask what happens when broadband, the processor or a terminal fails and whether offline transactions create extra risk. A second connection or processor may be justified where every lost hour is costly.

  9. Examine support at trading hours Support should match evenings, weekends or seasonal peaks if that is when payments occur. Test escalation routes and replacement times before relying on a single terminal.

  10. Verify portability before switching Stored-card tokens and recurring payment mandates may not transfer to a new processor. Establish migration options and customer impact before building subscriptions around proprietary credentials.