SADAD Web Checkout 2.1
SADAD Web Checkout 2.1 is a hosted payment solution that allows merchants to accept online payments securely without handling sensitive card or wallet data on their own servers.
SADAD hosts and manages the payment interface, authentication, and regulatory requirements, while merchants integrate using a simple server-side form submission.
When Should You Use Web Checkout 2.1?
This integration is recommended if you:
- Want a fast and compliant payment integration
- Do not want to handle card or wallet data
- Prefer a redirect-based checkout flow
- Want SADAD to manage PCI, authentication, and security
Web Checkout 2.1 is suitable for:
- E-commerce websites
- Service-based platforms
- Subscription or one-time payments
- Businesses prioritizing quick go-live
High-Level Integration Flow
At a high level, the integration works as follows:
- Merchant creates an order on their server
- Merchant generates a request signature
- Merchant submits an HTML form to SADAD
- Customer completes payment on SADAD-hosted page
- SADAD notifies merchant via callback and webhook
📘 For a detailed visual flow:
→ Web Checkout Flow
Supported Payment Methods
Depending on your merchant configuration and approval, Web Checkout 2.1 supports:
- Credit & Debit Cards
- SADAD
- Apple Pay
- Google Pay
Available payment methods may vary based on:
- Merchant category
- Bank approval
- Environment (Test or Live)
Sandbox and Live Environments
-
Sandbox Mode
- Used for development and testing
- No real funds are involved
- Enabled by using the Test Secret Key
-
Live Mode
- Used for real transactions
- Real customer payments are processed
- Enabled by using the Live Secret Key
There are no separate endpoints for sandbox or live mode.
📘
→ Environments – Test & Live
Key Integration Components
A complete Web Checkout integration includes:
- Signature Generation (server-side)
- Payment Request Form
- Customer Redirection Handling
- Callback Verification
- Webhook Processing (recommended)
Each component is documented in detail in the following sections.
Common Use Cases
Web Checkout 2.1 is commonly used for:
- One-time product or service payments
- Invoice-based payments
- Simple checkout flows without complex UI requirements
- Merchants who want minimal compliance overhead
What This Guide Covers
This documentation provides:
- Step-by-step integration instructions
- Request and response parameter definitions
- Signature generation logic
- Callback and webhook handling
- Error codes and status handling
- Best practices and common pitfalls
Where to Start
If this is your first integration, begin with:
Then follow the sections in the order shown in the left navigation.
Need Help?
If you are unsure whether Web Checkout 2.1 is the right integration for your business, contact:
Please include a brief description of your use case so the team can guide you appropriately.