Gateway integration
Payment gateway integration, done properly.
Payment integration with hosted card fields, webhooks that update orders, and a checkout that fails safely.
{ "order": "20931",
"amount": 18600,
"token": "tok_sample_7f3a",
"idempotency_key": "ord-20931-1" }
Gateway responseauthorized
Webhook: payment.capturedOrder 20931 set to paid
Hosted fields
Card numbers go to the gateway, not your server.
The card form is served by the gateway. Your system only ever sees a token.
- Customer types card into hosted fieldsServed by the gateway
- Gateway returns a tokentok_sample_7f3a
- Your server charges the tokenNo card number stored
Webhooks
Order status follows the money, not the click.
Orders turn paid when the gateway confirms capture, and each event is processed once.
- checkout.completed14:02:10Pending payment
- payment.captured14:02:13Paid
- payment.captured · repeat14:02:44Ignored · already done
Failing safely
No broken card form, ever.
If the gateway can't start a session, the customer sees another way to pay.
Card sessionGateway timeout
Card formHidden, not half-loaded
Pay by bank offeredOrder still completes
Team alertedWith the error
Questions
Asked on most calls.
- Which gateways do you integrate?
- The one you are approved with. We confirm its API fits your build on the call.
- Does this reduce our PCI scope?
- Hosted fields keep card data off your servers. Your acquirer decides how you validate.
- What are the risks of using a payment gateway?
- Orders marked paid before capture, repeated webhooks, and card forms that fail silently.
- Do you do payment gateway development?
- Payment processing integration, yes. We build on the gateway you are approved with, not a new one.
- What does a build cost?
- Every build is custom, so it is scoped and quoted on the call.
Gateway integration
Show us your checkout flow.
Thirty minutes with the people who build it.
