E-commerce and payments
Online stores, booking and ticketing, and the payment plumbing behind them: Mada, K-Net, Visa and the gateway your acquirer provides. Built in Arabic and English, tested with real cards before launch.
Payment integration is scoped as its own line, with its own acceptance test in the acquirer’s sandbox.
The checkout is the product
A store can look finished and still lose the sale on the last screen: a 3-D Secure redirect that never returns, a refund that exists in the gateway but not in your accounts, an order confirmation that arrives twice.
We build the storefront and the back office together, because what decides whether the business runs is order state, refunds and reconciliation — not the hero image.
Rasad has shipped commerce, booking and ticketing platforms since 2021: stores that take K-Net and Visa, a delivery marketplace, and two football club platforms selling tickets and merchandise.
What we build
Six parts of a store that holds up
Every build starts from the catalogue and the money, then the screens.
Catalogue and storefront
Products, variants, media and pricing in both languages, with the layout your brand already uses.
Checkout and payments
Mada, K-Net, Visa and the gateway your acquirer provides. Hosted or embedded, with 3-D Secure handled end to end.
Orders and fulfilment
Order state from paid to delivered, shipping APIs, delivery tracking and the exceptions that always appear.
Booking and ticketing
Time slots, seat maps or event passes, with the inventory rules that stop double-selling.
Back office
Refunds, partial refunds, reconciliation against the gateway statement, and an audit trail for finance.
Arabic and English
RTL layout, Arabic product copy, locale-aware currency and tax labels, tested on real phones.
Before launch
Four things we test with real money
A demo checkout proves the button works. These prove the business works.
- 01
A successful payment
A real card, a real amount, through the same gateway and 3-D Secure flow your customers will use.
- 02
A failed payment
Declined, abandoned and timed-out checkouts. The order must not be marked paid, and the customer must be told what to do next.
- 03
A refund
Full and partial, from the back office, reconciled against the gateway statement — not just “the button works”.
- 04
A repeat and a race
The same customer buying twice, and two people buying the last item at the same moment.
Where commerce breaks after launch
Each one has a named owner before go-live.
- Webhooks that never arrive
- The gateway says paid and your system never hears it. We reconcile on a schedule instead of trusting a single callback.
- Refund drift
- Money leaves the gateway but the order stays open. Refunds write back to the order and to the report finance reads.
- Currency and tax labels
- A cart showing the wrong currency or omitting VAT is a support ticket, and in Saudi Arabia a compliance problem.
- Inventory oversell
- Two buyers, one item. Stock is reserved when the payment intent is created, not after the confirmation page.
Commerce already in production
Haute Boutique runs on a custom store with K-Net and Visa payments and a bilingual CMS. PayShip connects payment and shipping APIs in one delivery product. Al Saqr FC and Al Raed FC sell tickets and merchandise through club platforms with a custom CMS and ticketing integration.
- Haute Boutique — custom store, bilingual CMS
- K-Net + Visa
- PayShip — both sides of the order connected
- Payment + shipping
- Al Saqr FC and Al Raed FC — two club platforms
- Ticketing
Each project is listed in the portfolio with the technologies we shipped.
Questions before scoping
Which payment providers do you integrate?
Mada, K-Net and Visa through the gateway your acquirer provides, including HyperPay and Stripe where the merchant already has an account. The gateway is scoped as its own line because its sandbox and approval process set the launch date.
Can you take over an existing store?
Yes, after a paid review of the code, the catalogue and the payment configuration. We do not migrate a live store without reading it first.
Do you build on WordPress?
Yes, when the business fits the platform. Several published projects run on WordPress or a custom CMS. When the catalogue, pricing or fulfilment rules do not fit, a custom build is cheaper than fighting the platform every month.
How long does a store take?
Most stores land in the 12–20 week band; a single-provider catalogue can be shorter. The date comes after the access map, before development starts.
See the published price bandsCan it handle VAT and ZATCA e-invoicing?
Yes. ZATCA Phase 2 e-invoicing is a separate integration with its own acceptance test.
How ZATCA, Nafath, Mada and ERP are deliveredWhat about refunds and reconciliation?
Both are part of the build, not an add-on. A refund writes back to the order, and the monthly statement reconciles against the gateway.
Show us the checkout you have, or the one you want
Send the catalogue size, the payment provider and the fulfilment rules. We will come back with a scope, a dated plan and a price.
30 minutes, no obligation. If an off-the-shelf platform fits, we will say so.
