Overview

Use the Daily Transaction Detail Report to reconcile, monitor, and investigate transaction-level payment activity for a reporting day.

The report is the primary source of truth for transaction-level data. It contains one record per transaction event and reflects the status and outcome processed by Aera.

Key Features

Provides full transaction-level granularity.
Covers all supported payment methods and channels.
Includes authorization, sale, and refund events.
Shows the status and outcome for each transaction.
Uses a structured CSV format for integration and processing.

Report Characteristics

Attribute	Description
Granularity	Transaction-level (one row per transaction event)
Frequency	Daily
Format	CSV
Scope	All transactions processed within the reporting day
Currency representation	Minor units (e.g. 10000 = 100.00 NOK)

Use Cases

Reconciliation: Validate transaction completeness against internal systems and settlement details.
Monitoring: Track volumes and approval rates.
Investigation: Analyze failed or disputed transactions.
Support: Retrieve transaction details for customer inquiries.
Data ingestion: Feed data into ERP, BI, or data platforms.

Relationship to Other Reports

The Daily Transaction Detail Report is part of Aera’s broader reporting framework:

Settlement Reports: Provide financial settlement information and bank-facing reconciliation.
Payout Reports: Show how funds are grouped and paid out to the merchant.

In practice

Use the Daily Transaction Detail Report to understand what happened.
Use Settlement and Payout Reports to understand how money moved.

Example flow

Transactions processed → appear in Transaction Report (Transaction ID)
Transactions settled → appear in Settlement Report (Reconciliation ID)
Settlements aggregated → appear in Payout Report (same Reconciliation ID)

Availability

Generated daily.
Covers transactions processed within the defined reporting day.
Becomes available after processing for the day is complete.

Delivery Options

Access the report through one of the following options:

Manually retrieve it in the Aera Portal.
Use automated delivery through a webhook and the Reporting API.

For details, see Get Reports.

Report Structure

Each row in the report represents a single transaction or transaction event.

For each transaction, the report provides merchant information, transaction IDs from different systems, transaction details, payment instrument details, and point-of-interaction information, such as terminal and online channel details.

Depending on the payment type, acquirer, point of interaction, and payment instrument, different data elements may be present for each transaction.

The field groupings shown below are for documentation purposes only; the actual report is delivered as a flat file without these groupings.

Merchant information

Field	Description
Merchant ID (Aera's MID)	Unique identifier assigned to the merchant in Aera
Merchant name	Name of the merchant
Merchant address	Address of the merchant
Group	Merchant group affiliation
Chain	Merchant chain affiliation
Sub-chain	Merchant sub-chain affiliation
<Name of> (Attribute 1)	Custom merchant-defined attribute 1
<Name of> (Attribute 2)	Custom merchant-defined attribute 2
<Name of> (Attribute 3)	Custom merchant-defined attribute 3
Merchant Category Code (MCC)	Merchant category classification code

Transaction Identification

Field	Description
Transaction ID	Unique identifier for the transaction
Original Transaction ID	Reference to the original transaction (used for refunds or reversals)
Merchant reference (order number/id)	Merchant-provided reference
Retrieval Reference Number	Reference used to track the transaction across systems
Exchange ID	Identifier used for tracking transaction exchanges
STAN	System Trace Audit Number assigned to the transaction

Transaction Details

Field	Description
Transaction Date and Time	Date and time when the transaction was processed
Amount	Transaction amount in minor units (e.g. cents)
Currency	Currency of the transaction (ISO 4217)
Transaction type	Type of transaction (e.g. authorization, capture, refund)
Transaction status	Final status of the transaction
Response code	Response code returned by Aera
Response code description	Description of the response code
Acquirer response code	Response code returned by the acquirer
Acquirer response code description	Description of the acquirer response
Acquirer	Name of the acquiring bank or processor
Acquirer Transaction ID	Identifier assigned by the acquirer
Acquirer Session ID	Session identifier assigned by the acquirer
Aera reconciliation ID	Identifier used for reconciliation processes
Issuer Authorisation code	Authorization code provided by the issuer

Payment Instrument Details

Field	Description
Payment instrument ID	Identifier of the payment instrument used
Payment methods	For example, Visa, Mastercard, Maestro, Bankaxept, Bancontact, Aera, or Xtra Seamless
Credit/Debit	Indicates whether the payment method is a credit or debit card
Payment instrument type	Type of payment instrument (e.g. card, wallet)
Card/instrument expiry date	Expiry date of the card or instrument
Issuer BIN	Bank Identification Number of the issuer
Issuer country	Country of the issuing bank (ISO 3166)

Terminal & POS Information

Field Name	Description
Terminal ID	Identifier of the terminal used for the transaction
Terminal type	Type of terminal used
Card entry mode	Method used to enter card details
PIN entry CVM	Cardholder verification method used
PAR	Payment Account Reference associated with the transaction
ECR ticket number	Reference to the POS receipt or ticket
Offline/online	Indicates whether the transaction was processed offline or online