Skip to main content
lite lets your business accept online and in-person payments in Saudi Arabia. One integration gives you mada, Visa, Mastercard, Apple Pay, and Samsung Pay, with 3D Secure authentication and settlement handled for you. There are four ways to integrate. All of them connect to the same platform and support the same payment methods. What changes between them is how much you build, how much control you have over the checkout experience, and how much PCI DSS compliance work falls on your side.
What is PCI DSS? It is the card industry’s security standard. The more your own systems see or store card details, the more of the standard applies to you. Integrations where lite captures the card details keep your compliance work to a minimum.
Create a payment page from your lite dashboard, copy the link and share it anywhere: WhatsApp, SMS, email, social media. Your customer opens the link, pays on a page hosted by lite, and you are notified of the result. No code and no developer needed. Best for: selling on social media, collecting invoice payments, or taking payments before you have a website.

Hosted checkout

Your website hands the customer over to a secure payment page hosted by lite. The customer pays there and is redirected back to your site with the result. Your developer writes a small amount of server-side code to create a checkout session and handle the redirect. lite keeps the payment page itself up to date, so new payment methods and authentication changes reach your customers without extra work from you. Best for: getting a website live with payments in the shortest time.

Web SDK

Embed lite’s prebuilt payment elements directly inside your own checkout page. The customer never leaves your site, and you control everything around the payment form: layout, branding, and flow. The card fields themselves are rendered and captured by lite, so card details never touch your servers. This gives you a fully native checkout while keeping most of the PCI DSS burden with lite. Expect moderate frontend and backend work. Best for: businesses that want checkout to feel like part of their own product without handling card data.

Direct API

Your systems call lite’s payment APIs directly, and you build the entire checkout experience yourself, including the card form. This gives you total control, but because raw card details pass through your systems, your business must be fully PCI DSS compliant (SAQ D). Choose this only if you already hold that certification or have a firm plan to obtain it. Most businesses get the control they need from the Web SDK instead. Best for: PCI DSS certified businesses building fully custom payment experiences.

Compare the options

Payment LinksHosted checkoutWeb SDKDirect API
Code requiredNoneMinimal, server-side onlyModerate, frontend and backendMost, you build the full checkout
Where the customer payslite page, opened from a linklite page, via redirectYour page, with lite payment fieldsYour page, with your own fields
Checkout customizationlite’s page with your brandinglite’s page with your brandingHigh, you own the pageTotal
PCI DSS scopeMinimalMinimalReduced, card data bypasses your serversFull, SAQ D required

Included with every integration

  • All payment methods through one integration. Enable or disable methods from your dashboard, with no code changes.
  • Automatic 3D Secure. lite triggers authentication whenever it is required, including the mandatory checks for mada e-commerce payments.
  • Webhooks. Your systems are notified of payment events, so your records always reflect the true payment status.
  • A sandbox environment. Test the full flow with test cards before going live.
  • Dashboard, refunds, and reports. Manage payments, issue refunds, and reconcile settlements in one place.