Merchant Registeration
Follow the DigetPay merchant journey from registration and KYC verification through technical onboarding, Fin staging tests, production activation, and go-live.
Complete DigetPay merchant onboarding from registration and KYC verification through sandbox testing, production activation, and go-live.
DigetPay completes business verification before technical setup and payment testing. Use the stage guide below to understand the expected timing and the action to take if you cannot proceed.
Start here if you are registering a new merchant account or preparing a merchant to begin integration.
Merchant journey
The merchant journey starts with business onboarding and identity verification, then continues into API access, integration path selection, staging tests, and production activation.
flowchart LR
A[Business Onboarding] --> B[Merchant Signup & KYC]
B --> C[Nafath Identity Verification]
C --> D[Wathq CR Verification]
D --> E[Technical Onboarding]
E --> F[Sandbox Setup]
F --> G[Integration Path Selection]
G --> H[Staging Tests]
H --> I[Production Activation]
I --> J[Go Live]
Stage guide
Timelines vary by merchant type, document completeness, integration scope, and go-live approval. Your onboarding manager shares expected dates after KYC submission.
| Stage | What you do | Expected timing | If you cannot proceed |
|---|---|---|---|
| Register the merchant and provide business information. | Varies by application completeness. | Review the required registration fields and submit complete, current information. |
| Submit the personal and business details required for Know Your Customer (KYC) verification. | Initial review: 3–5 business days. | Check that all application fields are complete and that submitted documents are clear and current. |
| Verify the business owner’s National ID or Iqama through Nafath. | Assessed during KYC; no separate timeframe is published. | Confirm that the ID or Iqama has 10 digits and starts with 1 or 2, then correct the registration details. |
| Validate the merchant’s Commercial Registration (CR) through Wathq. | Assessed during KYC; no separate timeframe is published. | Confirm that the CR is active and uses a valid 10-digit CR number, then correct the registration details. |
| Review the API documentation and prepare the integration. | Begins after business approval; timing depends on integration scope. | Resolve any outstanding KYC or account-access issue before starting technical setup. |
| Obtain Fin staging access and test API credentials. | Portal access is issued on the approval day. | Confirm that the organization is approved, then contact your onboarding manager or DigetPay support if access is unavailable. |
| Select Hosted Checkout, Embedded Integration, Pay by Link, or POS. | During technical onboarding. | Review the integration requirements with your onboarding manager before implementation. |
| Validate payment flows, error handling, and edge cases in Fin staging. | Depends on your implementation and test results. | Fix the failed scenario, retest in Fin staging, and use the error response when contacting support. |
| Complete compliance checks and production readiness tasks. | Begins after staging tests pass and go-live approval is granted. | Complete the outstanding Go-Live Checklist items and request final review. |
| Enable live payment processing and monitor the first transactions. | After production activation and a successful production smoke test. | Pause live traffic if needed and contact DigetPay support for production incidents. |
| Task | Guide |
|---|---|
| Sign up and KYC | Business Onboarding |
| Staging credentials | Sandbox Setup |
| Select an integration path | Choose Integration Path |
| Compare staging and production URLs | Environments Overview |
| Run a first test payment | Quick Start |
| Manage dashboard access and keys | Dashboard User Guide |
| Complete production cutover | Go-Live Checklist |
Merchant registration and KYC
Start onboarding by entering the required personal and business information. DigetPay uses this information to identify the merchant, validate the business, and prepare the account for verification through Nafath and Wathq.
Step 1 — Basic information
Enter the required registration details before identity and business verification begins.
All fields in this section are required to proceed with merchant verification. Ensure all information is accurate and up-to-date.
| Field | Required | Description | Validation |
|---|---|---|---|
| National ID / Iqama | Yes | The business owner’s National ID or Iqama number, used for Nafath identity verification. | Enter 10 digits starting with 1 or 2. |
| Commercial Registration Certificate | Yes | The merchant’s CR number. DigetPay retrieves the official certificate and business details through Wathq; no file upload is required. | Enter a valid, active 10-digit CR number. |
| Mobile Number | Yes | Saudi mobile number used for OTP verification and onboarding updates. | Use the Saudi mobile format: +966 5XXXXXXXX. |
| Email Address | Yes | Business email used for account activation, support, and notifications. | Enter a valid email address. |
| Services Required | Yes | DigetPay services the merchant wants to use. | Select at least one service. |
Verify the CR number and National ID or Iqama before you submit. Incorrect, expired, or incomplete information can require additional documents and delay approval.
If verification needs more information
DigetPay may request additional documents or clarification during compliance review. Submit the requested information promptly; review of additional documents typically takes 2–3 business days after submission. After compliance clearance, final approval typically takes 1–2 business days.
If your documents are rejected, replace them with clear, current documents issued by official sources. If a field fails validation, correct the value in the registration form before resubmitting. Contact your DigetPay onboarding manager for questions about specific requirements or onboarding status.
What happens next
Register the merchant, verify business details, and complete KYC.
Prepare sandbox credentials before building or testing the integration.
Decide whether to use Hosted Checkout, Embedded Integration, Pay by Link, or POS.
Complete production activation tasks before accepting real payments.
Updated about 1 month ago