Payment API integration cost

What drives build cost

Payment flows

One-off, saved card, subscription, refund and split flows each add work.

Authentication handling

Pausing and resuming payments that need customer authentication.

Webhooks

Verified, reliable processing of payment events.

Reconciliation

Matching payouts, fees and refunds to records.

Platforms

Web, apps and invoices each need integration.

Model transaction fees at your expected volumes and payment mix; they often exceed build cost over a few years.

Payment flows and their effort

Comparing provider fees properly

Providers price differently: a percentage plus a fixed amount per payment, different rates for cards from different regions, extra fees for certain payment methods, currency conversion, disputes or instant payouts. Headline rates rarely tell the whole story. Model a typical month using your real mix of payment methods, customer locations and average values, include refunds and disputes, and compare total fees between providers. For larger volumes, ask whether custom pricing is available.

Include the cost of switching providers later, since stored payment methods may not move easily.

Example: invoice payments first

Ongoing costs

Comparing integration quotations

Check whether each quotation includes webhook handling, idempotent retries, authentication flows, refunds, reconciliation and testing of every path. A quote covering only the 'happy path' of a successful payment leaves the costly edge cases for later.

Where the hidden effort sits

The successful payment is the easy part. The effort sits in the cases around it: a customer who closes the page during authentication, a renewal declined because a card has expired, a refund issued from the provider dashboard rather than your system, a webhook that arrives twice or out of order, and a dispute that needs evidence by a deadline. Each needs a defined behaviour and a test. Estimates that list these cases explicitly are more reliable than estimates based on the number of screens.

Ask for the list of payment states your system will recognise, and what happens to the order, invoice or subscription in each.

Why subscriptions cost more

Recurring billing adds plan changes part-way through a period, proration decisions, trials, pauses, cancellations, failed-payment retries and emails prompting customers to update their card. Many providers offer billing features that handle much of this, which can reduce build cost in exchange for using their model of plans and invoices. Building it yourself gives more control but more to maintain. Choose based on how unusual your pricing is.

Phasing to control cost

Start with the flow that removes the most manual work, often invoice payment links, and add saved cards, subscriptions or split payments once the first flow is stable and reconciled. Each phase can then be estimated on evidence from the previous one rather than guesswork.