Typical edits include: amount, description, PTL (expiry), customer details, Redirect/Back URLs, or service info.

You can only update a token that hasn’t been paid or expired.

Endpoint

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

Headers

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

Required / Optional Fields

Field	Type	Required	Description
`Request`	`string`	Yes	Must be `updateToken`.
`CompanyToken`	`string`	Yes	Token provided by 3G to operate this API.
`TransactionToken`	`string`	Yes	Transaction token from the `createToken` operation.
`PaymentAmount`	`number`	No	Transaction amount (up to 2 decimal places).
`CompanyRef`	`string`	No	Company reference number.
`CustomerEmail`	`string`	No	Customer’s email address to send the link.
`CustomerFirstName`	`string`	No	Customer’s first name.
`CustomerLastName`	`string`	No	Customer’s last name.
`CustomerAddress`	`string`	No	Customer’s address.
`CustomerCity`	`string`	No	Customer’s city.
`CustomerCountry`	`string`	No	ISO 3166-1 alpha-2 country code. Reference
`CustomerDialCode`	`string`	No	Country dial code (ISO 3166-1 alpha-2).
`CustomerPhone`	`integer`	No	Customer’s phone number.
`CustomerZip`	`string`	No	Customer’s ZIP/postal code.
`CompanyAccRef`	`string`	No	Internal accounting reference number.
`UserToken`	`string`	No	Identifies the user who created the transaction.

Only include the fields you want to change. Omitted fields remain as originally set.

Example Update Request

<?xml version="1.0" encoding="utf-8"?>
<API3G>
  <CompanyToken>8D3DA73D-9D7F-4E09-96D4-3D44E7A83EA3</CompanyToken>
  <Request>updateToken</Request>
  <TransactionToken>8C7E2A48-859E-4735-8B36-8B3358BAAAFF</TransactionToken>
  <PaymentAmount>44</PaymentAmount>
  <CompanyRef>DPO1212</CompanyRef>
  <CustomerEmail>test@directpay.online</CustomerEmail>
  <CustomerFirstName>Steven</CustomerFirstName>
  <CustomerLastName>Muallem</CustomerLastName>
  <CustomerAddress>Rose Avenue 6</CustomerAddress>
  <CustomerCity>Nairobi</CustomerCity>
  <CustomerCountry>KE</CustomerCountry>
  <CustomerDialCode>KE</CustomerDialCode>
  <CustomerPhone>4433332312</CustomerPhone>
  <CustomerZip>121212</CustomerZip>
  <CompanyAccRef>DPO3232</CompanyAccRef>
 </API3G>

Success Response

<?xml version="1.0" encoding="utf-8"?>
<API3G>
  <Result>000</Result>
  <ResultExplanation>Token been updated</ResultExplanation>
</API3G>

Error Responses (examples)

<API3G>
  <Result>903</Result>
  <ResultExplanation>Payment time limit exceeded (token expired)</ResultExplanation>
</API3G>

<API3G>
  <Result>904</Result>
  <ResultExplanation>Transaction already cancelled or paid</ResultExplanation>
</API3G>

See **Gateway Response Codes ** and Verify Token Response Codes for full tables.

▶️ Test in Postman

Rules & Constraints

Token must be unpaid and not expired (PTL not elapsed).
Currency and amount must be valid for the merchant account.
Some merchants enforce CompanyRef uniqueness; respect your setting.
If the shopper already opened the checkout, refreshing the page will reflect changes.

Typical Flow

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

  M->>D: createToken
  D-->>M: TransToken
  M->>D: updateToken (optional edits)
  M-->>C: Redirect to hosted checkout
  C->>D: Completes payment
  D-->>M: BackURL callback (result)

Implementation Tips

Keep updates idempotent in your system (log every change against the token).
If you extend PTL, communicate it in your UI (the timer changes).
After updating, you do not get a new token — you keep the same TransToken.
If updateToken fails with expiry or paid state, create a new token and restart.