Description of _transaction_.csv
All <date in utc>_transaction_*.csv files are built the same way. The date is in UTC format.
The following files will appear on the SFTP server:
YYYYMMDDZ_transaction_failed.consolidated.csv
YYYYMMDDZ_transaction_fundsmissing.consolidated.csv
YYYYMMDDZ_transaction_fundsreceived.consolidated.csv
YYYYMMDDZ_transaction_indoubt.consolidated.csv
YYYYMMDDZ_transaction_pending.consolidated.csv
YYYYMMDDZ_transaction_succeeded.consolidated.csv
For more information regarding different transaction states, check the The transaction process.
Explanation of fields:
| Title | Description | Type |
|---|---|---|
TXID | The PPRO Transaction ID | numeric |
TXSTATE | The transaction state | string |
FAILTYPE | The failtype (if the transaction ever failed) | string` |
FUNDSTATE | The fund state | string |
AMOUNT | The amount of transaction in cents | numeric |
CURRENCY | The currency of the transaction | string |
ACCOUNTHOLDER | The account holder of the transaction | string |
TAG | The name of the channel on which the transaction was processed (livechannel or testchannel) | string |
MERCHANTTXID | Client-generated merchant transaction identifier | string |
COUNTRYCODE | Two-letter country code of the transaction | string |
SELLINGPOINT | Optional field sent in by PSP/Merchant | string |
SOLDSERVICE | Optional field sent in by PSP/Merchant | string |
INITTS | The timestamp of transaction initiation (UTC time) | string |
SUCCEEDEDTS | The timestamp (if) the transaction state changed to succeeded (UTC time) | string |
FAILEDTS | The timestamp (if) the transaction state changed to failed (UTC time) | string |
INDOUBTTS | The timestamp (if) the transaction state changed to indoubt (UTC time) (deprecated, remains for backwards compatibility) | string |
FUNDSRECEIVEDTS | The timestamp (if) the transaction fundstate changed to state received (UTC time) | string |
FUNDSMISSINGTS | The timestamp (if) the transaction fundstate changed to missing (UTC time) | string |
ERRORTEXT | If an error occurred, this is the human-readable error text for the specific transaction | string |
ADD.<additional fields> | If a scheme requires additional input on the transaction API (specin parameters), the information is echoed in an individual ADD field per specin parameter.Example: specin.consumerref appears in the Processing files as ADD.CONSUMERREF. | string |
OUT.<additional fields> | If a scheme emits additional output on the transaction API (SPECOUT parameters), the information is echoed in an individual OUT field per SPECOUT parameter.Example: SPECOUT.SRCIBAN appears in the Processing files as OUT.SRCIBAN. | string |
MCONTRACT | Only appears if using consolidated files. This is the merchant contract ID | string |
Note
The number of
ADDandOUTfields and values can vary, depending on the data emitted by the scheme.
Updated 10 months ago