Skip to main content

​
Collect payments with DPO Pay

DPO uses a hosted checkout: Centipid Billing creates a transaction token with DPO, sends the payer to DPO’s payment page, and verifies the token before crediting anything. Offered in the country catalog for Kenya, Uganda, Rwanda, Ghana, Côte d’Ivoire, South Africa, Tanzania, Zambia, Malawi, Senegal, Zimbabwe, and Nigeria.

​
Before you start

  1. Complete DPO merchant onboarding in an account owned by the ISP.
  2. In the DPO dashboard open Settings → Company Token and collect the company token.
  3. Collect the numeric service type for the product you are selling. DPO issues it per service, and a wrong value is rejected at checkout.
  4. Plan the walled garden: the payer’s browser must reach secure.3gdirectpay.com, so a Hotspot subscriber who is not yet online cannot pay unless DPO is reachable pre-authentication.

​
Configure the gateway

1

Open Settings → Payments → DPO Pay

Select DPO Pay from the payment marketplace.
2

Enter the company token

Company token (required, stored as a secret) comes from DPO dashboard → Settings → Company Token.
3

Enter the service type

Service type (required) is the numeric service or product code from your DPO account.
4

Register the redirect and back URLs

See Callback URLs below.
5

Run a controlled test payment

Pay a small amount from the captive portal on an unauthenticated device and confirm the payment reaches the ledger.

​
Credentials

Both gate the switch.

​
Callback URLs

Set both in your DPO account. The redirect is where a completed payment returns; the back URL is where a cancelled or failed one lands.

​
What the payer must provide

Whatever DPO’s payment page asks for — card or mobile money, depending on what DPO has enabled for your account and country. The amount and the currency are fixed before the payer arrives.

​
How a payment completes

1

Create token

Centipid Billing posts an XML request to DPO’s API and receives a transaction token.
2

Payment

The payer is redirected to DPO’s payment page and completes the payment there.
3

Verification

On return, the token is verified against DPO. Only a verified successful result records a payment and applies the package; DPO’s own explanation is stored against the transaction otherwise.

​
Troubleshooting

For every gateway’s fields in one place, see the credential reference.