About this report
This report is based on the time zone setting of your account.
See Downloading reports.
The Received payment details report provides more detail on a payment, for example, whether the shopper used Dynamic Currency Conversion (DCC).
Download a sample report
To get an idea of the kind of data that you will see in the Received payment details report, you can download a sample report here. Based on your account and settings, your own report might contain additional columns that are not included in the sample report.
The Received payment details report contains the details for all the received transactions in the given date range.
To learn how to add additional columns or change the order of columns, refer to Configure report columns.
|1||Company Account||Unicode Text (80-character)||Name of your company account as registered in the Adyen payments platform.|
|2||Merchant Account||Unicode Text (80-character)||Name of your merchant account that was used to process the original payment request.
The report may contain line items for multiple merchant accounts.
|3||Psp Reference||Unicode Text (16-character limit)||Adyen's 16-character unique reference associated with the transaction/the request. This value is globally unique; quote it when communicating with us about this request.|
|4||Merchant Reference||Unicode Text (80-character)||Reference number that was provided when initiating the payment request.|
|5||Payment Method||Unicode Text (30-character)||Payment method type of the payment which was processed.
For example: visa, mc, amex.
|6||Creation Date||Date field + Time field||Timestamp indicating when the payment was created, as entered in the Adyen payments platform.
For example: 2012-07-26 19:58:55.
|7||TimeZone||Alpha Text (4-character limit)||The time zone of the Creation Date.
This is the ISO code for the time zone which is set up on your company account.
In the Customer Area, go to Account > Company Settings > Time Zone (BST, CET, CEST etc).
|8||Currency||Alpha Text (3-character limit)||The three-character ISO currency code.|
|9||Amount||Text field Numeric (16-Character limit)||The amount of the payment (authorisation amount).|
|10||Type||Unicode Text (50-character)||The record type.
For this report, the corresponding value is always Payment.
|11||Risk Scoring||Integer||The total risk scoring value of the payment.|
|12||Shopper Interaction||Alpha Text (30-character limit)||The transaction type.
Possible values: Ecommerce, ContAuth, POS, MOTO.
|13||Shopper Name||Unicode Text (80-character)||The name of the cardholder, as provided with the transaction, if available.|
|14||Shopper PAN||Alphanumeric (80-character)||The account number of the shopper or consumer.
In case of card payments, the last four digits of the card number.
For SEPA, this field shows the IBAN and BIC in the following format:
|15||Shopper IP||Unicode Text (50-character)||The IP address (IPV4 or IPV6) of the shopper as provided during the original transaction, if available.|
|16||Shopper Country||Alpha Text (2-character limit)||The ISO country code of the shopper, if available. If not available, this is computed based on the shopper's IP address.|
|17||Issuer Name||Unicode Text (256-character)||The name of the issuing bank, if available.|
|18||Issuer Id||Alphanumeric (30-character limit)||The unique identifier of the issuer.
In case of card payments this will be the issuer BIN (first six digits of the card number).
|19||Issuer City||Unicode Text (80-character)||The city of the issuer, if available.|
|20||Issuer Country||Alpha Text (2-character limit)||The ISO country code of the issuer.|
|21||Acquirer Response||Alphanumeric (30-character)||The normalized response from the acquirer. Not necessarily the final status of the payment.|
|22||Raw Acquirer Response||String||The raw response we receive from the acquirer, where available.|
|23||Authorisation Code||Unicode Text (50-character)||Authorisation code returned for a successful payment.|
|24||Shopper Email||Unicode Text (256-character)||The email address of the shopper, as provided during the original transaction, if available.|
|25||Shopper Reference||Unicode Text (256-character)||Shopper ID/reference as supplied in the original transaction.|
|26||3D Directory Response||Alpha Text (1-character limit)||For payments processed with 3D Secure (Secure Code/Verified by Visa), the 3D Directory response.
Values: Y, N, U, E
|27||3D Authentication Response||Alpha Text (1-character limit)||For payments processed with 3D Secure (Secure Code/Verified by Visa), and directory response Y, this holds the authentication response.
Values: Y, N, U, A E
|28||CVC2 Response||Text field Numeric (1-Character limit)||The result passed back by the issuer after verifying the CVC2, or CVV2/CID in case of Visa/Amex.|
|29||AVS Response||Text field Numeric (2-Character limit)||If Address Verification (AVS) was performed, the result of the AVS Check.|
|30||Billing Street||Unicode Text (256-character)||The street part of the billing address.|
|31||Billing House Number / Name||Unicode Text (256-character)||The house number or name part of the billing address.|
|32||Billing City||Unicode Text (256-character)||The city part of the billing address.|
|33||Billing Postal Code / ZIP||Unicode Text (30-character)||The ZIP code or postal code part of the billing address.|
|34||Billing State / Province||Unicode Text (256-character)||The state or province of the billing address.|
|35||Billing Country||Alpha Text (2-character limit)||The ISO country code of the billing address.|
|39||Delivery Street||String||The street part of the delivery address.|
|36||Delivery House Number / Name||String||The house number or name part of the billing address.|
|37||Delivery City||String||The city part of the delivery address.|
|38||Delivery Postal Code / ZIP||String||The ZIP code or postal code part of the delivery address.|
|39||Delivery State / Province||String||The state or province of the delivery address.|
|40||Delivery Country||String||The ISO country code of the delivery address.|
|41||Acquirer Reference||String||Reference number for the transaction provided by the acquirer.|
|42||Payment Method Variant||Unicode Text (32-character)||Payment method sub-brand, or the main payment method if not available (for example mccredit or visagold).|
|43||Reserved 3||String||Reserved for future enhancements.|
|44||Reserved 4||String||Reserved for future enhancements.|
|45||Reserved 5||String||Reserved for future enhancements.|
|46||Reserved 6||String||Reserved for future enhancements.|
|47||Reserved 7||String||Reserved for future enhancements.|
|48||Reserved 8||String||Reserved for future enhancements.|
|49||Reserved 9||String||Reserved for future enhancements.|
|50||Reserved 10||String||Reserved for future enhancements.|
To learn how to add additional columns, refer to Configure report columns.
|3DS Version||String||The version of the 3D Secure protocol used for the payment.|
|Acquirer Account||String||The acquirer account that was used for the transaction.|
|Acquirer||String||Name of the acquirer that processed the original payment.|
|ARes TransStatus||String||The transaction status of the 3D Secure 2 authentication request. This is the final result of the authentication, unless the value is C, which means a challenge flow is initiated.|
|BIN Funding Source||String||The card funding source.
|Cash register name||String||POS Tender Reference.|
|CVM Performed||String||Two-digit hexadecimal code indicating which type of card verification was used.|
|Device Fingerprint||String||The device fingerprint of the shopper's device, as provided during the original transaction, if available.|
|DCC||String||Indicates whether Dynamic Currency Conversion (DCC) was used during the transaction.
|Installments||String||Where installment transactions are applicable, this field will show the total number of installments requested by the merchant.|
|Library Implementation||String||Type of library implementation, for example Android, iOS, C or .NET.|
|Library Version||String||Version number of the library used, or standalone in case the POS terminal is not used in an integrated scenario.|
|Merchant Order Reference||String||Reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference.|
|Metadata||String||Contents from the metadata object related to the payment, in the form of key value pairs.|
|Network Token Used||String||If true, a network token was used to authorise the payment.|
|Network Token Available||String||If true, a network token was available for use for the payment.|
|Payment Requester Type||String||Contains the value
|POS Charity Amount||Numeric||The additional charity amount on the payment. Applies to Point of Sales transactions.|
|POS Cashback Amount||Numeric||The additional cashback amount on the payment. Applies to Point of Sales transactions.|
|POS Discount Amount||Numeric||The additional discount amount on the payment. Applies to Point of Sales transactions.|
|POS Entry Mode||String||Numeric code indicating how card details were entered into the terminal. Common codes:
01: Manual entry
02: PAN auto-entry via magnetic stripe.
05: PAN auto-entry via chip
91: Contactless card
|POS Gratuity Amount||Numeric||The additional gratuity amount on the payment. Applies to Point of Sales transactions.|
|POS Transaction Date||Date||The transaction date for a Point of Sales transaction.|
|POS Store and Forward indicator||Boolean||Indicates whether this was a store-and-forward transaction.
Possible values: TRUE or FALSE
|Real Time Account Updater status||String||The status of the Real Time Account Updater request.|
|Risk Profile||String||The name of the risk profile which was evaluated during the transaction.|
|Risk Profile ID||Numeric||The ID of the risk profile which was evaluated during the transaction.|
|Risk Profile Reference||String||The reference number of the risk profile which was evaluated during the transaction.|
|RReq TransStatus||String||The result of the 3D Secure challenge flow that is sent to the 3D Secure directory server. This is the final result of the authentication. This column can only contain a value when the 3D Secure authentication resulted in a challenge flow.|
|Shopper Phone Number||String||The phone number of the shopper, as provided during the original transaction, if available.|
|Store||String||Store identifier, as configured in Point of Sale.|
|Terminal App Version||String||Version of the POS terminal application.|
Configure report columns
If you want to add additional columns to a report, you can do so in the Customer Area. You can also change the order of columns, for example if this is required by third-party software that you're using.
To configure report columns, you need to have one of the following user roles:
- Merchant admin
- Merchant report role
- Merchant financial
- Merchant POS Report role
To configure report columns:
- Log in to your Customer Area.
- Go to Account > Report columns.
This opens a page with all reports that can be configured. 1
- Find the report that you want to configure and select Configure.
- Select check boxes to indicate which columns should be included in the report.
- Drag the columns into the order you want them to appear in.
- Select Save configuration to save your changes.
1 If you don't see the page, go to the report overview page and toggle Automatic generation on for the report for which you want to configure the columns. You can leave automatic generation on, or turn it off again if you don't want to generate the report automatically.