accountId|transactionCode|transactionDate|transactionId|responseCode|responseMessage|avsResponseCode|token|accountNumberUpdated|accountAccessoryUpdated|tokenUpdated|transactionType|submissionId|originalTransactionId|isRebillEnabled|sequenceNumber|transactionInternalCode|accountTypeUpdated|holderNameUpdated|retryFeeAmount|expectedEffectiveDate|warningCode|amount|accountNumberMasked|accountAccessory|accountType|holderName|aggregateTransactionId|aggregateTransactionCode|aggregateTransactionInternalCode|approvalCode|processedAmount|providerResponseCode|providerResponseMessage|providerAvsResponseCode|originalTransactionCode|originalTransactionDate
Generally we recommend integrators not to rely on the column order and use file headers included in every file. However, for legacy systems, where the only option is rely on column order, the order of columns from the
example of a response header record above can be used.
Please note, that the length of values is not fixed; however, it will not exceed the maximum length indicated in the specification for respective field. All columns will always be present in the file. An empty column is represented by a 'pipe' separator with no spaces or values. It will visually appear as two consecutive pipes, for example:
sale|John Smith||2000
1st column: sale
2nd column: John Smith
3rd column: empty
4th column: 2000
Please be advised that additional columns may be added. You will be notified in advance of such changes if you are subscribed to the specification updates.
