Core system
Payment & checkout
The part of the build where money actually changes hands — and where most drop-off happens.
What it is
A complete checkout path rather than a payment button: cart, address and delivery, the payment step itself, and a confirmation the customer can act on. Built for Malaysian buyers, which means FPX and DuitNow QR sit alongside cards rather than behind them, and totals are in ringgit throughout.
How we build it
What makes ours work
We design backwards from the order, not forwards from the gateway
A checkout is only as good as the order record it produces. Before any payment UI exists, we define what a complete order must contain — items and variants, the delivery promise made at purchase time, the price actually charged after discounts, and who to contact when something goes wrong. Then the checkout is built as the shortest honest path to producing that record. This is why our checkouts end in a reference number the customer can quote and an order your team can act on, rather than just a payment success screen.
Malaysian rails come first, not as an afterthought
Most checkout templates are built for card-first markets, with local methods bolted on. Malaysian buyers reach for FPX and DuitNow QR first, so the payment step presents them as equals — bank list and QR flow designed with the same care as the card form. Address entry uses real Malaysian states and postcodes, delivery fees are calculated locally, and every total is in ringgit from the first product page to the confirmation. In the Aruva build you can walk this exact flow end to end.
Failure is a first-class path
The unhappy paths are where checkouts quietly lose money: a declined card, stock sold out between cart and payment, a customer who abandons at the delivery step. We re-check availability at the moment of payment rather than trusting the cart, keep the cart intact through a failed attempt so the customer retries instead of restarting, and record enough about abandoned checkouts that you can see where people drop out — because the fix is usually in the step before payment, not payment itself.
Proof
Where we've built this
Every build below contains this system. Open any one and click through it — the fastest way to judge whether we can do what you need.
Questions
Asked about payment & checkout
The questions that come up when we scope this system. Anything else, ask us directly.
Which payment providers do you work with?
We are provider-agnostic. In Malaysia that typically means choosing between gateways like Billplz, senangPay, iPay88, Razer Merchant Services or Stripe, weighed on their fees, settlement time and the methods you need — FPX, DuitNow QR, cards or instalments. We help you choose based on your volumes and cash-flow needs, then build the checkout against that provider’s API. If you already have a merchant account, we build around it.
Can the checkout handle vouchers, discounts and instalments?
Yes — these are checkout logic rather than gateway features, so we build them into the order calculation itself: percentage and fixed vouchers with minimum-spend rules, stacking rules you control, and instalment presentation where the provider supports it. The important part is that the discounted price is computed server-side and recorded on the order, so what the customer saw is always what your records show.
Does it work for services and digital products, not just physical goods?
The same machinery covers all three — what changes is the fulfilment step. Physical goods need delivery fees and address validation; services usually pair checkout with our booking system so payment confirms a time slot; digital products need instant delivery after payment confirmation. We have built all three variations, and the admin side always shows one consistent order list regardless of what was sold.
What does adding a checkout cost?
It depends mostly on what is being sold, not the payment step itself — a single-product checkout is far simpler than a catalogue with variants, stock and delivery zones. Checkout is quoted as part of the build it belongs to rather than as a bolt-on. Tell us what you sell and we will show you the closest existing build, then quote the real version against your catalogue.
Need this in your project?
Tell us what you are building and we will show you the closest thing we have already made — then quote the real version.
Tell us what you need built
We'll put together a free working prototype of your project so you can click through it before paying anything.