TransAuth Authorization Export Data

The TransAuth export file contains the authorization records for every payment transaction attempt processed by each merchant. It captures both approvals and declines, along with the terminal, card, POS condition, and issuer response details. Use this file to audit authorization flows, support dispute representment with authorization evidence, and identify declined transaction patterns.

Endpoint

GET /download/YYYYMMDD/TransAuth

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this file when you need to verify that an authorization was obtained for a specific transaction (critical for chargeback disputes), audit the terminal entry modes and POS condition codes that were sent to the network, or investigate authorization declines by response code. The ApprovalCode field is required when responding to retrieval requests from card networks.

Query Parameters

None. The file is identified by the date path segment (YYYYMMDD) and delivered via SFTP.

Response

200 OK — Returns XML content with the following structure:

XML Hierarchy: Merchant > TransAuths > TransAuth

<Merchant> fields:

<TransAuth> fields:

<Merchant>
  <MID>9180000000001234</MID>
  <TransAuths>
    <TransAuth>
      <TerminalNumber>0001</TerminalNumber>
      <PrimaryAccountNumber>414100xxxxxxxxx0555</PrimaryAccountNumber>
      <CountryCode>840</CountryCode>
      <TransactionDateTime>2026-05-27T14:22:00</TransactionDateTime>
      <PosConditionCode>00</PosConditionCode>
      <CardType>Visa</CardType>
      <AuthorizationResponse>00</AuthorizationResponse>
      <VendorId>Vital</VendorId>
      <AuthorizedAmount>142.50</AuthorizedAmount>
      <CardExpirationDate>0000</CardExpirationDate>
      <ApprovalCode>412649</ApprovalCode>
      <TerminalEntryMode>07</TerminalEntryMode>
    </TransAuth>
    <TransAuth>
      <TerminalNumber>0001</TerminalNumber>
      <PrimaryAccountNumber>536759xxxxxxxxx6473</PrimaryAccountNumber>
      <CountryCode />
      <TransactionDateTime>2026-05-27T15:10:00</TransactionDateTime>
      <PosConditionCode>00</PosConditionCode>
      <CardType>MasterCard</CardType>
      <AuthorizationResponse>00</AuthorizationResponse>
      <VendorId>Vital</VendorId>
      <AuthorizedAmount>225.00</AuthorizedAmount>
      <CardExpirationDate>0000</CardExpirationDate>
      <ApprovalCode>072795</ApprovalCode>
      <TerminalEntryMode>05</TerminalEntryMode>
    </TransAuth>
  </TransAuths>
</Merchant>

Error Codes

Common Mistakes

• Treating AuthorizationResponse: 00 as the only valid outcome — other codes indicate specific decline reasons and should be mapped to the card network's response code table for proper interpretation.
• Assuming AuthorizedAmount equals the final settled amount — the settled amount may differ if a tip was added after authorization, or if a partial capture was used.
• Using CardExpirationDate for cardholder verification — it is always zeroed out (0000) in the export for PCI compliance.
• Overlooking PosConditionCode — an incorrect code can cause interchange downgrades or shift fraud liability; validate that codes in this file match the actual transaction environment.
• Confusing TerminalEntryMode: 01 (manual key entry) performance issues — manual entry carries higher fraud risk and typically incurs higher interchange and chargeback liability.

Related Endpoints

• GET /download/YYYYMMDD/Transactions — settled transaction records; use ApprovalCode to cross-reference
• GET /download/YYYYMMDD/TransactionsExtendedData — extended card type with PS2000TransactionIdentifier
• GET /download/YYYYMMDD/Chargeback — AuthCode in chargeback records maps to ApprovalCode here

Example

curl -X GET "https://hq.staging.netevia.dev/download/20260528/TransAuth" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"