Documentation

Read the platform
before you build on it.

This index is generated from the documentation navigation itself, so every link below goes to a page that exists. There are no summaries of pages that were never written, and no reading times, because the docs do not record them.

Start here

The one part of the documentation that is genuinely sequential — pick a region, get credentials, then make a call.

  1. 1Introduction
  2. 2Choosing your region
  3. 3Authentication
  4. 4Quickstart
  5. 5Environments
Pages76 written
Sections16 in the tree
API reference11 resources
Store platforms7 documented
By audience

Who the page is written for.

These three sections appear in every region of the docs. What changes inside them is the market, not the audience.

The global platform

Region-agnostic, front to back.

Accepting a payment, moving it, reconciling it, and the reference for every resource that does so — plus the guides for the people who operate it.

Egypt

The rails that are local.

Egypt has its own documentation tree because it has its own rails, its own settlement cycle and its own regulator.

Badges are printed as the documentation sets them. Roadmap marks a page that describes planned capability — it is written down, but it is not something you can call today. No payment rail is live yet; regulated services will be provided through licensed partners. Treat every other badge as a descriptive label rather than a commitment.

Elsewhere

When the docs are not the answer.