Welcome to DPO Pay by Network — Developer Guide

No card data touches your servers.
DPO handles the payment flow, security, and compliance.

How DPO Works (Big Picture)

flowchart LR
A[Your system] -->|Create Token| B[DPO API]
B -->|Returns Token| A
A -->|Redirect user with token| C[DPO Hosted Checkout]
C -->|Customer pays| D[DPO Gateway]
D -->|BackURL Webhook| A
A -->|Confirm via verifyToken| B

Key Concept: The Token

Every payment starts by calling createToken.

The token represents:

Order reference
Amount & currency
Return/callback URLs
Customer details
Service / product info

Once you have the token:

Redirect shopper to pay
Receive callback / status
(Optional) verify token if callback not received

Quick Start

1) Create a Token

Create a transaction and receive a payment token.

2) Redirect Customer

Send shopper to DPO's hosted checkout page.

3) Handle Callback

Receive the payment result via BackURL Webhook.

4) Verify Token (optional)

Confirm final status if callback was missed.

5) Refund / Void

Manage reversals and refunds.

Response Codes

See all gateway result codes.

API Collection (Postman v6)

Explore the full DPO Pay API Collection (v6) in Postman.

API Collection (Postman v7)

Explore the full DPO Pay API Collection (v7) in Postman.

Why Hosted Checkout?

PCI responsibility shifts to DPO
No storing card data
Faster integration
Built-in support for local African payment types

Perfect for:

E-commerce
Travel bookings
Marketplaces
Invoice / Pay-by-link flows

You're Ready

See the first API call:

Testing these APIs DPO Pay v6 uses a single endpoint (/API/v6/) and XML request payloads. For the best testing experience, use the provided Postman collections on each section page

POST https://secure.3gdirectpay.com/API/v6/
Request: createToken


Content-Type: application/xml; charset=utf-8
Accept: application/xml

▶️ Run in Postman