Payment gateway integration
Payments inside the software you already use: a 3D Secure card payment in your ordering site, school portal or B2B shop. Refunds, reconciliation and receipts are handled by the system, not by hand.
In production I have integrated Garanti BBVA and VakıfBank 3D Secure for school fees, QNB's PayFor 3D Host for a coffee roaster's store, and Multinet, Pluxee and Edenred meal cards for a delivery restaurant. Every bank and provider has its quirks; the work is in getting the edge cases right.
Who it’s for
Any business software that takes money: ordering, booking, school fees and dues, B2B portals and WooCommerce stores.
What it can include
- 3D Secure card payment. Bank virtual POS or payment provider, on the bank's page or inside yours.
- Meal cards. Card, phone number and one-time-code flows of meal-card providers.
- Refunds and cancellations. Full or partial refunds from the admin panel.
- Reconciliation. Every payment matched to an order, an installment or an invoice.
- Receipts. Receipts and payment confirmations by e-mail or SMS.
- Security. No card data on your server; signatures and callbacks are verified.
Related work
Real projects built from the same pieces.
How a project runs
- A short note. What the software should do, who will use it and what exists today. I reply within a working day.
- The list. Together we list the screens, roles and modules. Price and timeline follow from that list.
- Design and code. The interface is designed in Figma and coded by the same person; data model, permissions and deployment are planned together.
- Launch and hosting. It runs on your server or on mine, and I keep it running after launch.
Common questions
Which banks have you integrated?
Garanti BBVA, VakıfBank and QNB (PayFor) virtual POS, and Multinet, Pluxee and Edenred meal cards.
Do you store card numbers?
No. Card details are entered on the bank's or provider's side; the system keeps only the result.
Can you add a provider you haven't used?
Yes, if it has documentation and a test environment. The work follows the same pattern: request, signature, callback and status query.
the problem.hello@rentonhead.dev →