The collection was generated from publicly accessible Confluence documentation and is intended to help developers explore the API, prototype integrations, and validate request and response shapes.

Important: Request bodies and values in this collection are illustrative examples based on documentation snippets. Replace placeholders with your own merchant credentials and production-ready values before using them in a live integration.

Purpose

Use this collection to:

Authenticate and establish session or merchant context where required
Initiate and manage transactions
Query transaction status, logs, and reports
Work with Super Wallet functions where enabled for your account

Intended audience

This collection is intended for:

Merchants and integrators building payment and payout flows
QA and support engineers troubleshooting transactions
Developers validating request formats during onboarding

Before you begin

Before sending requests, ensure that you have:

A valid merchant or company token and any required API credentials
Access to the correct environment for your integration
Any feature enablement required for the services you plan to use, such as Super Wallet or tokenized payments

Some requests in this collection also assume familiarity with the DPO Pay XML request structure and operation-specific fields.

Base URLs

Requests in this collection currently reference multiple hosts.

Most common production base URL

https://secure.3gdirectpay.com/API/v7

Some requests also use:

.../API/v7/index.php
.../API/v7/Auth

If your organisation provides different sandbox or UAT base URLs, update your Postman environment or request variables accordingly.

Collection structure

The collection is organised into the following functional areas:

Super Wallet (v7) – account and wallet-related actions such as creating an account, adding or removing mobile details, and related account operations
Transaction operations (v7) – transaction lifecycle operations including verification, querying, refunds, logs, counts, and reporting
Merchant operations (v7) – merchant authentication and company-level details
Transaction payment options (v7) – tokenised card and mobile payment requests, and related payment option queries

Recommended workflow

Review the relevant documentation for the operation you want to test
Open the Postman collection
Fork or import the collection into your workspace
Replace sample values with your own credentials and request data
Confirm that you are using the correct host for the operation you are testing

Authentication notes

DPO Pay v7 uses merchant credentials and tokens issued by DPO.

This collection includes requests such as Auth and UserAuth that relate to authentication. Exact requirements may vary depending on your account configuration and enabled services, so confirm the correct credential set and required XML fields for your merchant profile before testing.

Notes

This collection was generated from Confluence documentation and may not reflect later changes if the upstream documentation is updated
XML payloads are based on documentation examples and may include placeholders
Some endpoints or features may be restricted by region, merchant profile, or product enablement

Known issues

Non-production hostnames detected

Dev host 3g.rogersm.dev.directpay.online

editReport(V7)
generateReport(V7)
fetchReports(V7)
GetMobilePaymentOptionsByCompanyToken(V7)

Sandbox host secure1.sandbox.directpay.online

createAccount(V7)
addMobile
pullAccount(V7)
chargeTokenCreditCard(V7)
ChargeTokenMobile (V7)

Recommended remediation

Introduce variables such as {{baseUrl}} and optionally {{authBaseUrl}}, then update request URLs accordingly
Confirm which operations should use sandbox versus production hosts, and document this clearly
Replace placeholder requests such as activateAccount (TBC) with final request definitions, or mark them clearly as not implemented

Open the collection in Postman

This Postman collection was generated from publicly accessible Confluence documentation and is intended to help developers explore the API, prototype integrations, and validate request/response shapes.

▶️ Run in Postman