Integration of Stripe, GoPay, PayPal and local payment gateways – including recurring payments, refunds and payment matching. Payment is where caution pays off most: a mistake here is not cosmetic but financial, and often legal too.

What the integration covers

Not just a redirect to the gateway. You have to handle both the customer's return and the asynchronous notifications, cover the case where they close the window mid-payment, process partial and full refunds, and keep the order state consistent even when a notification arrives twice or hours later.

What we build on

  • Idempotent notification handling – a duplicate delivery never writes twice.
  • Signature and origin verification instead of blindly trusting the request.
  • Automatic matching of payments to orders and alerts on unmatched ones.
  • Refunds and credit notes straight from the admin, recording who and when.
  • Recurring payments and subscriptions including failed charges and retries.

Security and data

Sensitive card data is never stored on your side – it stays with the gateway provider certified to hold it. You work with tokens and states, which also makes any security audit considerably simpler.

If you already have a gateway but payments are matched by hand or go missing, the fix is usually in the notification handling rather than in changing provider.

Frequently asked questions

Which payment gateway do you recommend?

It depends on the market and the type of payments. For local customers, support for domestic banks and card payments usually decides; for subscriptions, reliable recurring charging matters more. We compare fees, available methods and documentation quality, and recommend based on your volume.

Can we use several gateways at once?

Yes, and across several markets it is often necessary. The payment layer is designed so the gateway is chosen by country, currency or amount, and adding another provider does not mean rewriting the checkout process.