Get Transactions

Common use: review a customer’s transaction history or reconcile wallet activity across multiple cards.

Endpoint

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

Headers

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

Request

Required Fields

Field	Req	Description
`Request`	Yes	Must be `SuperWalletGetTransactions`
`CompanyToken`	Yes	Token provided by DPO to authorize API operations
`customerUnq`	Yes	Unique token identifying the customer
`customerToken`	No	Token for a specific credit card. If omitted, results include all cards
`numberOfRecords`	No	Maximum number of records to return (default: `100`)
`indexOfRecords`	No	Index of the first record to retrieve (default: `0`)

Example Request (XML)

<?xml version="1.0" encoding="utf-8"?>
<API3G>
  <CompanyToken>68B90B5E-25F6-4146-8AB1-C7A3A0C41A7F</CompanyToken>
  <Request>SuperWalletGetTransactions</Request>
  <customerUnq>9D3D99F7-3FEE-4792-961A-6EFFB5B642BA</customerUnq>
  <indexOfRecords>50</indexOfRecords>
  <numberOfRecords>25</numberOfRecords>
</API3G>

Response

Example Success Response (XML)

<?xml version="1.0" encoding="utf-8"?>
<API3G>
  <Result>000</Result>
  <ResultExplanation>Transactions found</ResultExplanation>
  <TotalTransactions>8</TotalTransactions>
  <transHistory>
    <trans>
      <transRef>49717D0F</transRef>
      <providerName>Direct Pay Online Payment</providerName>
      <transAmount>1.00</transAmount>
      <transCurrency>USD</transCurrency>
      <paymentDate>2018-07-20</paymentDate>
      <transCardType>MASC</transCardType>
      <transCardNum>(4679)</transCardNum>
    </trans>
    <trans>
      <transRef>49711B2E</transRef>
      <providerName>Direct Pay Online Payment</providerName>
      <transAmount>1.00</transAmount>
      <transCurrency>USD</transCurrency>
      <paymentDate>2018-07-20</paymentDate>
      <transCardType>MASC</transCardType>
      <transCardNum>(3215)</transCardNum>
    </trans>
  </transHistory>
</API3G>

Field Reference

Field	Description
`Result`	Response code returned by the server
`ResultExplanation`	Description of the result
`TotalTransactions`	Total number of transactions found
`transHistory`	Array of transaction objects
`transRef`	Transaction reference
`providerName`	Payment provider name
`transAmount`	Transaction amount
`transCurrency`	Currency code (e.g., USD, KES)
`paymentDate`	Date of transaction
`transCardType`	Card type used (e.g., VISA, MASC)
`transCardNum`	Masked card number (last 4 digits)

Typical Usage Flow

sequenceDiagram
  participant M as Merchant
  participant D as DPO API

  M->>D: SuperWalletGetTransactions<br/>(CompanyToken, customerUnq)
  D-->>M: Result + TotalTransactions + transHistory
  M->>M: Display transactions<br/>ordered by payment date (desc)
  Note over M,D: Optionally repeat call<br/>with indexOfRecords for pagination

Notes & Best Practices

Use pagination (numberOfRecords, indexOfRecords) for large result sets.
If customerToken is not provided, all transactions for the customer’s Super Wallet will be returned.
Transactions are listed newest first.
Always handle Result and ResultExplanation codes to confirm success before parsing data.
Store responses securely if used for financial reporting or reconciliation.

Common Result Codes

Code	Meaning	Action
`000`	Transactions found	Success
`801`	Missing `CompanyToken`	Provide valid token
`804`	XML error	Check formatting/encoding
`902`	Data mismatch	Verify `customerUnq` or `customerToken`
`999`	Internal error	Retry or contact support