Skip to main content

1. Quick Start (5 Minutes)

Get up and running with SADAD Web Checkout 2.1 in just a few minutes. This guide is designed for developers who want a fast, minimal, and correct integration.

Who is this for?

This quick start is intended for backend developers or technical teams who want to validate the integration end-to-end before moving to production.


What You Will Achieveโ€‹

By the end of this guide, you will be able to:

  • Create a SADAD payment request
  • Generate a valid request signature
  • Redirect a customer to the SADAD payment page
  • Receive the transaction result securely

Prerequisitesโ€‹

Before you begin, ensure that:

  • Your SADAD merchant onboarding is approved
  • You have access to the SADAD Merchant Panel
  • You have generated a Test Secret Key and noted your Merchant ID (MID)

This is a one-time setup.


Step 1: Prepare Order Detailsโ€‹

From your server, prepare the order data you want to send to SADAD:

  • Order ID (unique per transaction)
  • Transaction amount
  • Customer contact details
  • Callback URL

These values must remain unchanged throughout the transaction lifecycle.


Step 2: Generate Signature (Server-Side)โ€‹

Using your Secret Key, generate a SHA256 signature:

  • Sort parameters alphabetically by key
  • Prefix with Secret Key
  • Concatenate values only
  • Hash using SHA256 and convert to uppercase

๐Ÿ‘‰ Refer to:
Signature Generation (Request)

warning

Never generate the signature on the client side.


Step 3: Submit Payment Formโ€‹

Submit an HTML form from your backend or server-rendered page to the SADAD Web Checkout endpoint.

  • Method: POST
  • Target: SADAD Web Checkout URL
  • Include all parameters + generated signature

๐Ÿ‘‰ Refer to:
Payment Form Submission


Step 4: Customer Completes Paymentโ€‹

The customer:

  • Selects a payment method
  • Completes authentication if required (3DS / Apple Pay / Google Pay)
  • Is redirected back to your CALLBACK_URL

No sensitive card data ever touches your servers.


Step 5: Handle Callback & Webhookโ€‹

After payment:

  • Callback URL returns final transaction status (browser-based)
  • Webhook provides reliable server-to-server confirmation

You should validate the signature and update your order status accordingly.

๐Ÿ‘‰ Refer to:


Common Mistakes to Avoidโ€‹

  • Generating signature on frontend
  • Modifying parameters after signature generation
  • Ignoring webhook events
  • Treating callback as the only source of truth

Whatโ€™s Next?โ€‹

Once the quick start flow works successfully:

  • Configure Test & Live environments
  • Review Best Practices
  • Enable Webhooks in production

๐Ÿ‘‰ Continue with:
Merchant Account Setup


tip

If you face any issues, contact SADAD Support with: Merchant ID, Order ID, and Transaction Reference.