The DigetPay Developer Portal is the single entry point for any partner who
wants to publish a service inside the DigetPay App marketplace.
This documentation guides you through the entire journey: self-registration,
company verification, submitting your marketplace app, configuring how your app
looks to the customer, and getting money flowing through your DigetPay
partnership.
Base URL note — this demo references the staging environment
(https://fin-api.digetpay.com). See §2 Environments & base URLs for the production URL.
1. What is the DigetPay Developer Portal?#
A self-serve onboarding flow — register, complete KYC, and publish a listing.
A credential manager — sandbox API keys plus webhook secrets.
An integration toolkit — listing, offers, panels, orders, and outbound webhooks.
1.1 Who is this for?#
1.
Marketplace service developers — teams building services that live inside
the Super App (top-ups, tickets, gift cards, billers, merchants).
2.
Partner engineering leads — people who own the technical review.
This documentation is reserved for marketplace service developers. Merchant
acquiring and the customer payment API have separate docs and are not
documented here.
2. Environments & base URLs#
All endpoints are prefixed globally with /v1.| Environment | Base URL | Purpose |
|---|
| Staging | https://fin-api.digetpay.com/v1 | Build and test. OTP is dev-visible |
| Production | https://api.digetpay.com/v1 | Live traffic |
3. Integration models#
Every application is created with the EMBEDDED integration model, which
decides how a customer launches your service from the Super App.All new applications use the EMBEDDED flow — the only model available today.
It provides the simplest UX and the highest conversion rates.
4. Quick start#
To get started, you need to prepare some documents, both for the company, and the company's representative, also refered to as the owner.The Representative's Saudi phone (+9665…)
The Representative's email address
Scans of your commercial registration, tax certificate, and a representative ID
Onboarding checklist#
| # | Step | API | Result |
|---|
| 1 | Register company + owner | POST /developer-portal/register | org ONBOARDING |
| 2 | Verify phone with OTP | POST .../register/verify-otp | phone verified |
| 3 | Upload documents (COMMERCIAL_REGISTRATION, TAX_CERTIFICATE, REP_ID) | POST .../company/documents | docs attached |
| 4 | Check readiness | GET .../company/readiness | canSubmitVerification: true |
| 5 | Submit for review | POST .../company/submit | verification SUBMITTED |
| 6 | Admin review | — | org APPROVED (1–2 business days) |
5. Using this Documentation#
This documentation supports several ways to make your integration journey easier.Using an LLM#
Click Copy Page at the top of any page to copy the content in
Markdown/OpenAPI format, which is parsable by LLMs.
Click the MCP button at the top of any API endpoint for a guide on
integrating the docs with your favourite IDE.
Use the LLMS.txt link at the bottom of the page to get a complete,
LLM-parsable sitemap of the docs.
Using API clients like Postman#
This documentation supports sending requests from your browser.
You can also export the collection as an OpenAPI spec "Via the Export button on the bottom of the page" and import it into your
favourite API client (Postman, Bruno, Insomnia, etc.).
6. FAQ#
See also#