Merchant Signup & KYC
Required business information and documents for DigetPay merchant approval.
DigetPay verifies your business before enabling payment processing. Complete KYC early to avoid delays in receiving staging credentials.
Document list: Requirements may vary by legal entity type (sole proprietorship, LLC, or joint stock). The exact requirements will be confirmed during the onboarding review.
How to apply
- Open the DigetPay Merchant Application Form
- Complete the merchant application form
- Upload the required KYC documents
- Submit your application for compliance review
- Receive portal credentials and staging API keys upon approval
Typical KYC documents
| Document | Purpose | Notes |
|---|---|---|
| Commercial registration (CR) | Legal business identity in KSA | Original or certified copy required |
| National ID / Iqama (authorized signatory) | Identity verification | Must match signatory on application |
| Bank account letter (IBAN) | Settlement account | Issued by your bank on official letterhead |
| Business address proof | Registered location | Utility bill or lease agreement acceptable |
| Website or app URL | Integration context | Must be live and operational |
| Expected volume & MCC | Risk assessment | Annual transaction estimates required |
Marketplace & Sub-Merchant KYC Addendum
This section applies to marketplaces, platforms, aggregators, and other business models that onboard multiple sub-merchants to process payments through DigetPay.
Marketplace / Platform requirements
The marketplace or platform must provide:
| Requirement | Purpose | Notes |
|---|---|---|
| Commercial registration (CR) | Legal entity verification | Must be valid and match the application |
| National ID / Iqama of authorized signatory | Identity verification | Must match the authorized signatory |
| Bank account / IBAN letter | Settlement verification | Must be issued by the bank |
| Business address proof | Address verification | Utility bill or lease agreement may be accepted |
| Website / platform URL | Business model verification | Must be accessible and operational |
| Business model description | Risk and compliance assessment | Describe how the marketplace operates and how sub-merchants are onboarded |
| Expected transaction volume | Risk assessment | Include expected monthly or annual volume |
| Sub-merchant onboarding flow | Compliance review | Describe how merchants are registered and verified |
Sub-Merchant requirements
Each sub-merchant onboarded through the marketplace must provide the applicable KYC information and documents required for merchant onboarding.
| Requirement | Purpose | Notes |
|---|---|---|
| Legal business name | Business identification | Must match the submitted registration documents |
| Commercial registration / applicable business license | Legal verification | Required where applicable |
| National ID / Iqama of authorized signatory | Identity verification | Must match the person authorized to represent the business |
| Bank account / IBAN | Settlement verification | Must belong to the sub-merchant or an approved settlement structure |
| Business address | Address verification | Must match the registered business information where applicable |
| Website / store / platform profile | Business activity verification | Must clearly describe the goods or services offered |
| Business activity / MCC | Risk classification | Must accurately represent the sub-merchant's primary activity |
Beneficial Owner and ownership information
For applicable business entities, DigetPay may require information about the individuals who ultimately own or control the business.
Provide:
- Beneficial owner name and identification details
- Ownership percentage, where applicable
- Authorized signatory details
- Ownership structure for companies with multiple shareholders
- Supporting corporate documents when required
Marketplace onboarding responsibilities
The marketplace is responsible for ensuring that sub-merchant information submitted to DigetPay is complete and accurate.
Before a sub-merchant is activated for payment processing:
- Collect the required sub-merchant information and documents
- Verify that the submitted information is complete and consistent
- Submit the sub-merchant for DigetPay compliance review
- Address any additional information requests
- Wait for approval before enabling payment processing
DigetPay may request additional documents or information based on the sub-merchant's business activity, ownership structure, risk profile, or applicable compliance requirements.
Business information required
| Field | Example | Requirements |
|---|---|---|
| Legal business name | As on CR | Must match commercial registration exactly |
| Trade / brand name | Customer-facing name | Name customers see on receipts/invoices |
| MCC (merchant category) | E-commerce, SaaS, etc. | Select primary business category |
| Website URL | https://yourstore.com | Must be accessible and operational |
| Support email & phone | Customer contact | Active channels for customer inquiries |
| Authorized signatory | Name, role, contact | Person authorized to sign agreements |
Review process
sequenceDiagram
participant Merchant
participant DigetPay as DigetPay Compliance
participant Ops as DigetPay Ops
Merchant->>DigetPay: Submit application + documents
DigetPay->>DigetPay: KYC / AML review (3-5 business days)
alt Approved
DigetPay->>Ops: Provision merchant record
Ops->>Merchant: Portal invite + staging key request
else More info needed
DigetPay->>Merchant: Request additional documents
Merchant->>DigetPay: Submit clarifications
end
After approval
Once your application is approved:
- You will receive an email invitation to access the DigetPay merchant portal
- Generate your staging API keys from the portal dashboard
- Review the integration documentation and sandbox environment setup
- Begin testing payment flows in staging before going live
- Schedule a call with your onboarding manager to discuss production deployment
Timeline expectations
- Initial review: 3–5 business days
- Additional documents (if needed): 2–3 business days after submission
- Final approval: 1–2 business days after compliance clearance
- Portal access: Issued same day as approval
Common issues & troubleshooting
Delayed review: Ensure all documents are clear, legible, and match the information on your application.
Rejected documents: Verify that documents are current (not expired) and issued by official sources.
Missing information: Double-check that all required fields in the application form are completed accurately.
Marketplace / sub-merchant delays: Ensure that the marketplace and each sub-merchant have submitted all applicable KYC information and supporting documents before requesting compliance approval.
Contact your DigetPay account manager only when your case requires additional clarification or documentation that is not covered by the requirements above.
Related
- Business Onboarding Overview
- Integration Planning
- Merchant Portal Guide
- API Reference
Updated about 1 month ago