SADAD Integrations Overview
SADAD provides multiple integration options to support different business models, platforms, and technical requirements.
This page helps you quickly identify which integration is right for you.
Web Integrations
🧾 Web Checkout 2.1
Hosted payment page (Redirect flow)
Best for:
- Websites needing a fast and secure integration
- Minimal PCI scope
- Standard card payments, Apple Pay, Google Pay
Key characteristics:
- Customer is redirected to SADAD checkout
- No card data touches your servers
- Supports callback URL + webhook
👉 Recommended for most merchants
🖼️ Web Checkout 2.2 (iFrame) (Coming Soon)
Embedded checkout experience
Best for:
- Merchants who want checkout embedded in their website
- More control over UI/UX
- Seamless customer experience
Key characteristics:
- Checkout inside an iframe
- Same security model as hosted checkout
- Requires additional UI handling
Status: Planned
API Integrations
🔌 Direct API (Planned)
Server-to-server payment processing
Best for:
- Advanced platforms
- Custom payment flows
- Full control over transaction lifecycle
Key characteristics:
- Direct API calls
- Higher PCI responsibility
- Suitable for large or complex platforms
Status: Planned
Mobile Integrations
📱 Mobile SDKs (Planned)
Platforms:
- Android
- iOS
- Flutter
Best for:
- Native mobile applications
- In-app payments
- Optimized mobile user experience
Key characteristics:
- Native SDKs
- Built-in authentication handling
- Unified transaction status via webhooks
Status: Planned
How to Choose the Right Integration
| Your Requirement | Recommended Integration |
|---|---|
| Fastest go-live | Web Checkout 2.1 |
| Lowest compliance effort | Web Checkout 2.1 |
| Custom UI on web | Web Checkout 2.2 |
| Full backend control | Direct API |
| Mobile apps | Mobile SDKs |
Need Help Choosing?
If you’re unsure which integration fits your use case, contact SADAD Support with a brief description of your business model.
tip
Most merchants should start with Web Checkout 2.1 and migrate to advanced integrations only if needed.