Transactions Extended Data Export

Returns daily transaction data with extended card-type codes and network transaction identifiers in XML format, enabling interchange qualification analysis and cross-referencing with authorization records.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Transactions Extended Data Export

The TransactionsExtendedData export extends the standard transaction file with additional card-level metadata focused on interchange qualification and network tracking. It uses two-character extended card type codes (VS, VD, MC, MD, AM, DS) that provide finer-grained classification than the single-character codes in the base Transactions file. The PS2000TransactionIdentifier in this file is the primary key for linking records to authorizations in the TransAuth file.

Endpoint

GET /download/YYYYMMDD/TransactionsExtendedData

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 performing interchange cost analysis by card product type (e.g. separating Visa Debit from Visa Credit costs), when building cross-reference tables between settled transactions and their authorization records, or when investigating interchange downgrades. The ExtendedCardType field is essential for any analysis that requires distinguishing between credit and debit products of the same network.

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: TransactionsExtendedData > Merchants > Merchant > Batches > Batch > Transactions > Transaction

<Merchant> fields:

FieldTypeDescription
MIDstringMerchant identifier (unique account number)

<Batch> fields:

FieldTypeDescription
BatchIdstringExternal batch identifier
NetDepositAmountintegerNet deposit amount for the batch in cents
TransactionsCountintegerTotal number of transactions in the batch

<Transaction> fields:

FieldTypeDescription
ExtendedCardTypestringTwo-character code for card network and product (see reference below)
PS2000TransactionIdentifierstringUnique network-level transaction reference (Visa: 15-digit numeric; Mastercard: alphanumeric)
AuthorizationCodestringApproval code returned by the card issuer
ValidationCodestringInterchange validation code (empty for Mastercard and some other card types)
TransactionAmountintegerTransaction amount in cents; negative = refund or reversal
TransactionFeedecimalFee applied in dollars; xsi:nil="true" if no fee applies

Extended Card Type Reference:

CodeNetworkProduct Type
VSVisaStandard (credit or debit, general)
VDVisaDebit
VCVisaCredit
MCMastercardStandard (credit or debit, general)
MDMastercardDebit
AMAmerican ExpressStandard
DSDiscoverStandard
<?xml version="1.0" encoding="utf-8"?>
<TransactionsExtendedData xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Merchants>
    <Merchant>
      <MID>9180000000001234</MID>
      <Batches>
        <Batch>
          <BatchId>90001320907</BatchId>
          <NetDepositAmount>1417437</NetDepositAmount>
          <TransactionsCount>3</TransactionsCount>
          <Transactions>
            <Transaction>
              <ExtendedCardType>VD</ExtendedCardType>
              <PS2000TransactionIdentifier>356044817836921</PS2000TransactionIdentifier>
              <AuthorizationCode>076075</AuthorizationCode>
              <ValidationCode>VWLM</ValidationCode>
              <TransactionAmount>257088</TransactionAmount>
              <TransactionFee xsi:nil="true" />
            </Transaction>
            <Transaction>
              <ExtendedCardType>MC</ExtendedCardType>
              <PS2000TransactionIdentifier>MWEMEEHUT0213</PS2000TransactionIdentifier>
              <AuthorizationCode>05938J</AuthorizationCode>
              <ValidationCode />
              <TransactionAmount>-42500</TransactionAmount>
              <TransactionFee xsi:nil="true" />
            </Transaction>
            <Transaction>
              <ExtendedCardType>AM</ExtendedCardType>
              <PS2000TransactionIdentifier>019521283465064</PS2000TransactionIdentifier>
              <AuthorizationCode>858364</AuthorizationCode>
              <ValidationCode>A7KP</ValidationCode>
              <TransactionAmount>189300</TransactionAmount>
              <TransactionFee xsi:nil="true" />
            </Transaction>
          </Transactions>
        </Batch>
      </Batches>
    </Merchant>
  </Merchants>
</TransactionsExtendedData>

Error Codes

CodeWhen it happens
400Malformed date format in URL path
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404No TransactionsExtendedData file found for the specified date
500Internal server error

Common Mistakes

  • Not dividing TransactionAmount by 100 — all amounts are in cents. A value of 257088 = $2,570.88.
  • Treating negative TransactionAmount as an error — negative values are refunds or reversals and are expected in the file.
  • Relying on ValidationCode being populated for all card types — it is empty for Mastercard by design.
  • Not using ExtendedCardType for interchange analysis — VD (Visa Debit) and VC (Visa Credit) qualify at very different interchange rates and must be analyzed separately.
  • Confusing TransactionFee: xsi:nil="true" with zero — nil means no fee information is available; 0 means a fee was assessed but was zero.

Related Endpoints

  • GET /download/YYYYMMDD/Transactions — standard transaction export with more fields per transaction
  • GET /download/YYYYMMDD/TransAuth — authorization records; use PS2000TransactionIdentifier to cross-reference
  • GET /download/YYYYMMDD/MASD1001 — daily fee detail showing interchange costs by program

Example

curl -X GET "https://hq.staging.netevia.dev/download/20260528/TransactionsExtendedData" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/json
merchants