Payment Gateway Integration

The pay button is the smallest piece of an online payment setup. What decides whether an integration is correct is what happens seconds after the buyer closes their banking app, because by then the money has moved and your site knows nothing about it.

The first part creates the transaction on the server, with the amount recalculated from database prices instead of read off a form. The second shows the buyer how to pay. The third takes the provider notification, checks its signature, then moves the order. Only the third may call an order paid.

For small and mid sized baskets a QRIS integration wins, because buyers scan the code from whichever bank or e-wallet app is already on their phone, with no numbers to type. Virtual accounts still win on large amounts and with corporate buyers who need a transfer receipt, while retail outlets matter for buyers who pay cash.

Per transaction fees and settlement schedules are set by the provider, not by us, and the gaps are wide enough to move your margin when the average order is small. We usually enable the three or four methods that get used, then add more once data justifies it, because twelve options read as noise on a phone.

The number one mistake in a checkout integration never changes: the order status is updated on the redirect page. That page only loads if the buyer waits for their browser to come back to your site, and most buyers do not wait. Money arrives, the order still reads unpaid, and somebody on your team chases the gap through bank statements every night.

The next failure is more dangerous because it stays invisible until somebody tries it. A notification endpoint with no signature check can be called by anyone who guesses the address, and one forged request is enough to mark an order paid with no money behind it. At one building materials distributor, virtual account orders never changed status because a firewall had blocked the endpoint from day one, and two staff reconciled by hand for months.

The five checks below fit into one afternoon in sandbox mode, and none needs source code access except to fix what it finds. Run them before the ads go live, not after a buyer chases goods your system insists were never paid for.

If one check fails, what is broken is not the look of your checkout but your record of the money, and the gap grows quietly until it shows up in a monthly report.

Providers want company paperwork before they open an account, normally the deed of incorporation, the corporate tax number, the director's ID, and a company bank account for settlement. Verification sits with the provider and its length is outside our control, which makes it the most common reason a store slips its launch date.

The merchant account is opened in your company name, not ours, and settlement moves from the provider straight into your account without passing through anybody. The principle matches the domain rule: anything tied to your money or identity stays yours, so a working relationship can end without your payments dying with it.

At handover you receive the list of endpoints and order states in use, production credentials held in your own account, a daily reconciliation procedure a non technical staff member can follow, and a notification log for tracing orders. Hosting, SSL, the server, the WhatsApp group, and unlimited revisions for a year come with the package, while the domain is bought separately and stays in your name. Our team works from Gunung Putri, Bogor.