Connecting a payment gateway looks like a one-day job until you add refunds, subscriptions, and local methods. Here is where the time and money actually go.
Integrating a payment gateway sounds like a one-day job until you read the docs. Plug in an SDK, paste a few keys, and you are taking cards, right? That is true for a simple one-off charge. It stops being true the moment you add refunds, subscriptions, or a second currency.
This post is for founders and product owners trying to budget a payment integration without a developer in the room. It covers what actually takes time and what you should expect to pay.
A single gateway, one currency, one-off payments, and a basic webhook can be done in a few days by someone who has done it before. Most gateways, from Stripe and Adyen to Pix in Brazil and local Chinese channels, have decent SDKs and test sandboxes.
The work gets interesting when you go past that:
These are integration costs paid to a development team. The gateway's own per-transaction fees are separate and usually the bigger number over time.
| Scope | What is included | Typical cost |
|---|---|---|
| Basic | One gateway, card payments, webhooks, test and live | $2,000 to $5,000 |
| Standard | Add refunds, subscriptions, receipt emails, admin view | $5,000 to $12,000 |
| Multi-method | Card plus Pix, boleto, or similar local methods, reconciliation | $12,000 to $30,000 |
The jump from standard to multi-method is mostly testing and reconciliation, not code. Each method has its own status codes, timeouts, and edge cases around chargebacks and disputes.
If card data touches your server at all, PCI DSS applies. The cheapest way to stay out of scope is a hosted page or a tokenized flow where the card number never reaches your code. That is a design decision made early, and changing it later means rework.
For cross-border payments, add KYC and AML checks, currency conversion, and local tax handling. An integration that ignores these will pass testing and then fail a real audit or a real chargeback dispute.
The integration cost is a one-time number. The gateway's fees are forever, and they deserve as much attention.
Card gateways typically charge a percentage plus a fixed amount per transaction, often 2.5 to 3.5 percent for cross-border cards. Local methods are cheaper: Pix in Brazil is often a flat fee per transaction, and boleto has its own schedule. Add a monthly fee for some gateways, a chargeback fee of $15 to $25 per dispute, and a currency conversion markup, and the real cost of taking payments can quietly reach 4 percent.
Before you pick a gateway, ask for the full fee schedule, not the headline rate. The headline rate is the best case, and your real volume will land somewhere worse.
A payment integration is not done when the happy path works. Have your finance team run the odd cases in the sandbox before you go live: a card that expires mid-subscription, a refund on a partial order, a dispute that arrives a month later, a settlement file with a rounding difference. Each one you catch in testing saves a support ticket and a confused customer later.
Our team has built payment flows that include local methods like Pix, so the sandbox-to-live checklist is a routine part of the work rather than a discovery process.
We build payment and financial systems as part of our normal work, and the pattern is always the same. Clients budget for the "connect the gateway" part and get surprised by the "keep the ledger honest" part. It is not a bug in the estimate. It is a scope gap.
The fix is to write down the money flows before any code. Draw every state an order can be in: created, paid, partially refunded, refunded, failed, disputed, expired. Then decide who owns each transition. If you cannot draw it on a whiteboard, the integration will cost more than the estimate, whoever you hire.
We run a China-based team with overlap hours for clients in the Americas, Europe, and Africa, and we have delivered payment work across a few markets, so the timezone and the local-method questions are ones we have already worked through.
GlobeSoft builds custom software, AI applications, SaaS, FinTech and enterprise systems for clients worldwide. Message us on WhatsApp for the fastest answer, or email us — we typically reply within 24 hours.
Keep reading
The code is the fast part. Testing is what decides whether your first week of live traffic is calm or a fire drill. The cases to run before any payment feature ships.
5 min readAdding payments looks small in the project plan and eats two weeks if you get it wrong. The steps, the methods, and the mistakes that cost teams the most.
7 min readHow Pix payment integration works for businesses selling in Brazil: gateway vs direct routes, fees of 0.22% to 0.99%, Pix Cobranca and Automatico, and a build checklist.
13 min readA real payment gateway is infrastructure, not a checkout feature. Here is the architecture, PCI DSS compliance, fraud controls, and what it costs to build one.
7 min readWhat mobile money integration costs, the M-Pesa, MTN MoMo, Flutterwave and Paystack routes, timelines, and the licensing and reconciliation that matter.
5 min readConnecting two systems is easy on the happy path. The real work is in retries, idempotency, rate limits, and data mapping. Here's where the hours go.
