createToken (v6)

The createToken operation is the first step in initiating a payment with DPO Pay by Network. It generates a secure payment token that represents a single checkout session.

You’ll use this token to:

Redirect the customer to the hosted DPO checkout page, or
Continue processing flows such as status checks or refunds.

Legacy note: Some fields and endpoints may still reference 3G Direct Pay (3G). This is the same platform, now branded as DPO Pay by Network.

Endpoint

Method: POST Headers:

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

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

DPO does not provide a separate sandbox. Test credentials are issued on this endpoint and later promoted to live mode.

▶️ Test in Postman

Required XML Fields

Field	Description
`CompanyToken`	Merchant token assigned by DPO
`Request`	Must be `createToken`
`PaymentAmount`	Amount (e.g., `450.00`)
`PaymentCurrency`	ISO currency (e.g., `ZAR`)
`CompanyRef`	Your order reference
`RedirectURL`	Where the customer is sent after payment
`BackURL`	Server callback URL for final status
`ServiceType`	Provided by DPO during merchant onboarding.
`Description`	Payment description

Optional customer fields improve receipts & reporting: customerFirstName, customerLastName, customerEmail

Example Request (XML)

Replace values with your own CompanyToken, URLs, and ServiceType.

<?xml version="1.0" encoding="utf-8"?>
<API3G>
  <CompanyToken>8D3DA73D-9D7F-4E09-96D4-3D44E7A83EA3</CompanyToken>
  <Request>createToken</Request>

  <Transaction>
    <PaymentAmount>450.00</PaymentAmount>
    <PaymentCurrency>ZAR</PaymentCurrency>
    <CompanyRef>49FKEOA</CompanyRef>

    <RedirectURL>https://www.domain.com/payurl.php</RedirectURL>
    <BackURL>https://www.domain.com/backurl.php</BackURL>

    <CompanyRefUnique>0</CompanyRefUnique>
    <PTL>5</PTL>

    <customerFirstName>Alex</customerFirstName>
    <customerLastName>Nkosi</customerLastName>
    <customerEmail>customer@example.com</customerEmail>
  </Transaction>

  <Services>
    <Service>
      <ServiceType>3854</ServiceType>
      <ServiceDescription>Flight from Nairobi to Diani</ServiceDescription>
      <ServiceDate>2025/12/20 19:00</ServiceDate>
    </Service>
  </Services>
</API3G>

📘
PTL refers to the Payment Time Limit in hours (how long the payment token stays active before expiring). Default varies by merchant account.

Example Success Response (XML)

This is a real working response you received — excellent.

<?xml version="1.0" encoding="utf-8"?>
<API3G>
    <Result>000</Result>
    <ResultExplanation>Transaction created</ResultExplanation>
    <TransToken>1B454D71-23EB-42E9-8FE8-FDDC167B5BCD</TransToken>
    <TransRef>R73770389</TransRef>
</API3G>

Field	Meaning
`Result` = `000`	Success
`TransToken`	Token used to redirect customer
`TransRef`	DPO transaction reference

Redirect customer here:

URL https://secure.3gdirectpay.com/pay.asp?ID=1B454D71-23EB-42E9-8FE8-FDDC167B5BCD

Example Error Response

<API3G>
  <Result>904</Result>
  <ResultExplanation>Invalid currency code</ResultExplanation>
</API3G>

See full list: Gateway Response Codes (v6)

Payment Flow Summary

sequenceDiagram
  participant M as Merchant Server
  participant DPO as DPO API
  participant C as Customer

  M->>DPO: POST createToken
  DPO-->>M: TransToken (000)
  M-->>C: Redirect to DPO checkout
  DPO-->>M: BackURL callback with result
  M->>DPO: verifyToken (optional)

Going Live Checklist

Item	Done
Use test credentials issued by DPO	☐
Switch same credentials to live when approved	☐
HTTPS on `RedirectURL` and `BackURL`	☐
Return `HTTP 200 OK` to callbacks	☐
Log `TransToken`, `TransRef`, `CompanyRef`, `Result`	☐

Branding Note: You may still see 3G in examples — internally this is the same platform. Use DPO Pay by Network in your merchant-facing integrations.