How to choose a payment service provider for a growing startup

Start with requirements, not providers

Most provider selections begin with a shortlist of familiar names. A better starting point is a written description of what your payments need to do over the next two to three years: which markets, currencies and payment methods, which customer types, and what volumes.

Write requirements in business terms first. "Accept card and bank payments from business customers in three European markets, with payouts to suppliers in two currencies" is easier to evaluate against than a list of API features.

• Markets and currencies — now and planned
• Payment methods your customers actually use in each market
• Customer type: consumer, business or both
• Expected volume, average transaction size and seasonality
• Payouts, refunds, disputes and any marketplace or split-payment needs

Understand the total cost, not the headline rate

Headline pricing rarely reflects what you will pay. Total cost includes the mix of payment methods, cross-border and currency conversion fees, dispute and refund fees, payout costs, minimums and the internal effort required to operate the integration.

Ask each provider to price your expected transaction mix, not a generic example. Where pricing is blended, ask how it compares with interchange-plus pricing at your volume, and at what point pricing can be renegotiated.

Evaluate operations as seriously as technology

Integration is a few weeks of work; operating the provider lasts for years. Look closely at reconciliation reports, settlement timing, dispute handling, support quality and how the provider communicates incidents.

Involve finance and customer operations in the evaluation. They will live with the reporting and exception handling long after the engineering project is closed.

• Settlement timing and reconciliation data quality
• Dispute and chargeback workflow
• Account management and support model at your size
• Incident history and status communication

Check compliance responsibilities early

Your integration choice affects your compliance scope. Hosted payment pages and provider-managed card fields typically reduce the card data your systems handle, which can reduce your PCI DSS obligations. Confirm the exact scope with the provider and, where relevant, a qualified assessor.

In the European Economic Area, card payments are subject to Strong Customer Authentication requirements under PSD2. Ask how the provider handles authentication, exemptions and the effect on conversion.

Plan for the provider you'll need next

The right provider for launch may not be the right one at ten times the volume or in a new region. Avoid designs that make switching expensive: keep payment logic behind your own interface where practical, understand how stored payment credentials can be migrated, and review contract terms on notice periods and data portability.

Run the decision as a short, structured project

A focused evaluation usually involves a requirements document, a shortlist of three to four providers, a scored matrix agreed in advance, priced proposals based on your real transaction mix and reference conversations with similar companies. Make the decision with product, engineering, finance and operations in the room.

References

• PCI Security Standards Council — PCI DSS
• Directive (EU) 2015/2366 (PSD2), EUR-Lex