{"title":"Received payment details report","category":"default","creationDate":1776961629,"content":"

The Received payment details report provides more detail on all transactions you processed through Adyen.<\/p>\n

Generating and downloading<\/strong>: Get this report manually<\/a> or automatically<\/a>.<\/p>\n

Time zone<\/strong>: The time zone setting<\/a> of your account.<\/p>\n

Availability<\/strong>: Available for company accounts<\/a> and merchant accounts<\/a>.<\/p>\n

\n

We have migrated to a new technology platform to make report generation faster. You may have to update your data ingestion pipeline if you automatically ingest report data. To determine if you have to take action, check the migration overview<\/a>.<\/p>\n<\/div>\n

Sample report<\/h2>\n

Download a sample Received payment details report<\/a> for examples of the included data.<\/p>\n

Report structure<\/h2>\n

Entries<\/h3>\n

Under the header line, each line in the report is a separate entry.<\/p>\n

Columns<\/h3>\n

Each column shows specific information about the entries.<\/p>\n

Standard columns<\/h4>\n

The table below reflects the standard columns that are included in the report, and the default order after the migration. You can add more columns<\/a>, or change the order of the default columns.<\/p>\n

\n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
#<\/th>\nColumn<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
1<\/td>\nCompany Account<\/td>\nUnicode Text (80-character)<\/td>\nThe name of your company account as registered in the plataforma de pagamentos da Adyen.<\/td>\n<\/tr>\n
2<\/td>\nMerchant Account<\/td>\nUnicode Text (80-character)<\/td>\nThe name of the merchant account that was used to process the original payment request.
The report may contain line items for multiple merchant accounts.<\/td>\n<\/tr>\n
3<\/td>\nPsp Reference<\/td>\nUnicode Text (16-character limit)<\/td>\nAdyen's 16-character unique reference associated with the transaction\/the request.\u00a0This value is globally unique; quote it when communicating with us about this request.<\/td>\n<\/tr>\n
4<\/td>\nMerchant Reference<\/td>\nUnicode Text (80-character)<\/td>\nThe reference that was specified in the payment request.<\/td>\n<\/tr>\n
5<\/td>\nPayment Method<\/td>\nUnicode Text (30-character)<\/td>\nThe payment method used for the transaction.
For example: visa<\/em>, mc<\/em>, mc_applepay<\/em>, amex<\/em>.<\/td>\n<\/tr>\n
6<\/td>\nCreation Date<\/td>\nString<\/td>\nThe timestamp indicating when the payment was created on the plataforma de pagamentos da Adyen.
Format: YYYY-MM-DD HH:MM:SS<\/code>.
For example: 2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n
<\/td>\nCreation Date Time Zone

Before the migration<\/strong>: TimeZone<\/td>\n		Alpha Text (4-character limit)<\/td>\nThe time zone of the Creation Date<\/strong>.
This is the ISO code for your time zone setting<\/a>.<\/td>\n<\/tr>\n
7<\/td>\nCurrency<\/td>\nUnicode Text (3-character limit)<\/td>\nThe three-character ISO currency code<\/a>.<\/td>\n<\/tr>\n
<\/td>\nAmount<\/td>\nNumeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The amount of the payment (authorisation amount). Always a positive value, even if the payment was canceled before being captured.<\/td>\n<\/tr>\n
8<\/td>\nType<\/td>\nUnicode Text (50-character)<\/td>\nThe record type.
For this report, the value is always Payment<\/em>.<\/td>\n<\/tr>\n
9<\/td>\nRisk Scoring<\/td>\nInteger<\/td>\nThe total risk score of the payment.<\/td>\n<\/tr>\n
10<\/td>\nShopper Interaction<\/td>\nAlpha Text (30-character limit)<\/td>\nThe transaction type.
Possible values: Ecommerce<\/em>, ContAuth<\/em>, POS<\/em>, MOTO<\/em>.<\/td>\n<\/tr>\n
11<\/td>\nShopper Name<\/td>\nUnicode Text (80-character)<\/td>\nThe name of the cardholder, as specified in the transaction, if available.<\/td>\n<\/tr>\n
12<\/td>\nShopper PAN<\/td>\nAlphanumeric (80-character)<\/td>\nThe Primary Account Number (PAN<\/a>).
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: IBAN\/BIC<\/code><\/td>\n<\/tr>\n
13<\/td>\nShopper IP<\/td>\nUnicode Text (50-character)<\/td>\nThe IP address (IPV4 or IPV6) of the shopper as specified in the original transaction, if available.<\/td>\n<\/tr>\n
14<\/td>\nShopper Country<\/td>\nAlpha Text (2-character limit)<\/td>\nThe ISO country code of the shopper, if available. If not available, this is computed based on the shopper's IP address.<\/td>\n<\/tr>\n
15<\/td>\nIssuer Name<\/td>\nUnicode Text<\/td>\nThe name of the issuing bank, if available.<\/td>\n<\/tr>\n
16<\/td>\nIssuer Id<\/td>\nAlphanumeric (30-character limit)<\/td>\nThe unique identifier of the issuer.
In case of card payments this will be the issuer BIN (first six digits of the card number).<\/td>\n<\/tr>\n
17<\/td>\nIssuer City<\/td>\nUnicode Text (80-character)<\/td>\nThe city of the issuer, if available.<\/td>\n<\/tr>\n
18<\/td>\nIssuer Country<\/td>\nAlpha Text (2-character limit)<\/td>\nThe ISO country code of the issuer.<\/td>\n<\/tr>\n
19<\/td>\nAcquirer Response

Before the migration<\/strong>: value had a limited length.<\/td>\n		Alphanumeric<\/td>\nThe normalized response from the acquirer. Not necessarily the final status of the payment. When a payment is canceled before being captured, the acquirer response will be Unknown<\/em>.<\/td>\n<\/tr>\n
20<\/td>\nAuthorisation Code<\/td>\nUnicode Text (50-character)<\/td>\nThe authorisation code returned for a successful payment.<\/td>\n<\/tr>\n
21<\/td>\nShopper Email<\/td>\nUnicode Text (256-character)<\/td>\nThe email address of the shopper, as specified in the original transaction, if available.<\/td>\n<\/tr>\n
22<\/td>\nShopper Reference<\/td>\nUnicode Text (256-character)<\/td>\nThe shopper ID or reference that was specified in the original transaction.<\/td>\n<\/tr>\n
23<\/td>\n3D Directory Response<\/td>\nAlpha Text (1-character limit)<\/td>\nFor payments processed with 3D Secure (Secure Code\/Verified by Visa), the 3D Directory response.
Values: Y<\/em>, N<\/em>, U<\/em>, E<\/em><\/td>\n<\/tr>\n
24<\/td>\n3D Authentication Response<\/td>\nAlpha Text (1-character limit)<\/td>\nFor payments processed with 3D Secure (Secure Code\/Verified by Visa), and directory response Y<\/em>, this holds the authentication response.
Values: Y<\/em>, N<\/em>, U<\/em>, A<\/em>, E<\/em><\/td>\n<\/tr>\n
25<\/td>\nCVC2 Response<\/td>\nText field Numeric (1-Character limit)<\/td>\nThe result passed back by the issuer after verifying the CVC2, or CVV2\/CID in case of Visa\/Amex.<\/td>\n<\/tr>\n
26<\/td>\nAVS Response<\/td>\nText field Numeric (2-Character limit)<\/td>\nIf Address Verification (AVS) was performed, the result of the AVS Check.<\/td>\n<\/tr>\n
27<\/td>\nBilling Street<\/td>\nUnicode Text (256-character)<\/td>\nThe street part of the billing address.<\/td>\n<\/tr>\n
28<\/td>\nBilling House Number \/ Name<\/td>\nUnicode Text (256-character)<\/td>\nThe house number or name part of the billing address.<\/td>\n<\/tr>\n
29<\/td>\nBilling City<\/td>\nUnicode Text (256-character)<\/td>\nThe city part of the billing address.<\/td>\n<\/tr>\n
30<\/td>\nBilling Postal Code \/ ZIP<\/td>\nUnicode Text (30-character)<\/td>\nThe ZIP code or postal code part of the billing address.<\/td>\n<\/tr>\n
31<\/td>\nBilling State \/ Province<\/td>\nUnicode Text (256-character)<\/td>\nThe state or province of the billing address.<\/td>\n<\/tr>\n
32<\/td>\nBilling Country<\/td>\nAlpha Text (2-character limit)<\/td>\nThe ISO country code of the billing address.<\/td>\n<\/tr>\n
33<\/td>\nDelivery Street<\/td>\nString<\/td>\nThe street part of the delivery address.<\/td>\n<\/tr>\n
34<\/td>\nDelivery House Number \/ Name<\/td>\nString<\/td>\nThe house number or name part of the billing address.<\/td>\n<\/tr>\n
35<\/td>\nDelivery City<\/td>\nString<\/td>\nThe city part of the delivery address.<\/td>\n<\/tr>\n
36<\/td>\nDelivery Postal Code \/ ZIP<\/td>\nString<\/td>\nThe ZIP code or postal code part of the delivery address.<\/td>\n<\/tr>\n
37<\/td>\nDelivery State \/ Province<\/td>\nString<\/td>\nThe state or province of the delivery address.<\/td>\n<\/tr>\n
38<\/td>\nDelivery Country<\/td>\nString<\/td>\nThe ISO country code of the delivery address.<\/td>\n<\/tr>\n
39<\/td>\nAcquirer Reference<\/td>\nString<\/td>\nThe reference number for the transaction provided by the acquirer.<\/td>\n<\/tr>\n
40<\/td>\nPayment Method Variant<\/td>\nUnicode Text (32-character)<\/td>\nThe payment method sub-brand, or the main payment method if not available (for example mccredit<\/em> or visagold<\/em>).<\/td>\n<\/tr>\n
41<\/td>\nRaw Acquirer Response

Before the migration<\/strong>: Raw acquirer response<\/td>\n		String<\/td>\nThe raw response we receive from the acquirer, where available. When a payment is canceled before being captured, the raw acquirer response will be empty.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

Removed standard columns<\/h4>\n

From November 2023, the following columns have been removed.<\/p>\n

\n \n\n\n\n\n\n\n\n\n\n\n\n
Column<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Reserved 4<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 5<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 6<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 7<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 8<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 9<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 10<\/td>\nString<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

Additional columns<\/h3>\n

You can configure report columns<\/a> to add these to your report:<\/p>\n

\n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Column<\/th>\nData type<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Global Card Brand<\/td>\nString<\/td>\nThe brand of the card used for the payment.<\/td>\n<\/tr>\n
Original Amount

Before the migration<\/strong>: Original amount<\/td>\n		Numeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The original amount of the payment.<\/td>\n<\/tr>\n
Cashback Amount

Before the migration<\/strong>: Cashback amount<\/td>\n		Numeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The additional cashback amount on the payment.<\/td>\n<\/tr>\n
POS Charity Amount<\/td>\nNumeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The additional charity amount on the payment. Applies to point-of-sale transactions.<\/td>\n<\/tr>\n
POS Gratuity Amount<\/td>\nNumeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The additional gratuity amount on the payment. Applies to point-of-sale transactions.<\/td>\n<\/tr>\n
POS Cashback Amount<\/td>\nNumeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The additional cashback amount on the payment. Applies to point-of-sale transactions.<\/td>\n<\/tr>\n
POS Discount Amount<\/td>\nNumeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The additional discount amount on the payment. Applies to point-of-sale transactions.<\/td>\n<\/tr>\n
POS Surcharge Amount

Before the migration<\/strong>: Surcharge Amount<\/td>\n		Numeric

or

String (only in .XLS<\/code> and .XLSX<\/code> report files)<\/td>\n		The surcharge amount on the payment.<\/td>\n<\/tr>\n
POS Payment Device

Before the migration<\/strong>: Payment Device<\/td>\n		String<\/td>\nThe device that was used to make the payment.<\/td>\n<\/tr>\n
Shopper Phone Number<\/td>\nString<\/td>\nThe phone number of the shopper, as specified in the original transaction, if available.<\/td>\n<\/tr>\n
Alternative Acquirer Reference<\/td>\nString<\/td>\nThe alternative acquirer reference of the acquirer that was used for the transaction.<\/td>\n<\/tr>\n
Acquirer<\/td>\nString<\/td>\nName of the acquirer that processed the original payment.<\/td>\n<\/tr>\n
Acquirer Account<\/td>\nString<\/td>\nThe acquirer account that was used for the transaction.<\/td>\n<\/tr>\n
Installments<\/td>\nString<\/td>\nWhere installment transactions are applicable, this field shows the total number of installments requested by the merchant.<\/td>\n<\/tr>\n
DCC<\/td>\nString<\/td>\nIndicates if Dynamic Currency Conversion (DCC) was used during the transaction.
Possible values:
  • DCC accepted<\/em> \u2013 The shopper accepted DCC and completed the transaction in their currency.<\/li>
  • DCC declined<\/em> \u2013 The shopper refused DCC and completed the transaction in the merchant's currency.<\/li>
  • DCC not offered<\/em> \u2013 The shopper and merchant both share the same currency, therefore DCC was not offered.<\/li><\/ul><\/td>\n<\/tr>\n
BCMC IBAN\/BIC<\/td>\nString<\/td>\nThe Bancontact<\/a> IBAN or BIC.<\/td>\n<\/tr>\n
BIN Funding Source<\/td>\nString<\/td>\nThe card funding source.
Possible values:
  • CHARGE<\/li>
  • CREDIT<\/li>
  • DEBIT<\/li>
  • DEFERRED_DEBIT<\/li>
  • PREPAID<\/li>
  • PREPAID_RELOADABLE<\/li>
  • PREPAID_NONRELOADABLE<\/li><\/ul><\/td>\n<\/tr>\n
Device Fingerprint<\/td>\nString<\/td>\nThe device fingerprint<\/a> of the shopper's device, as specified in the original transaction, if available.<\/td>\n<\/tr>\n
Device<\/td>\nString<\/td>\nThe device that was used to make the payment.<\/td>\n<\/tr>\n
Browser<\/td>\nString<\/td>\nThe browser that was used to make the payment.<\/td>\n<\/tr>\n
Merchant Order Reference<\/td>\nString<\/td>\nA reference that allows you to link multiple transactions to each other for reporting purposes. See merchantOrderReference<\/a>.<\/td>\n<\/tr>\n
Payment Requester Type<\/td>\nString<\/td>\nContains the value autorescue<\/code> if there was an auto rescue<\/a> attempt for the payment.<\/td>\n<\/tr>\n
Network Token Used<\/td>\nString<\/td>\nIf true, a network token was used to authorise the payment.<\/td>\n<\/tr>\n
Network Token Available<\/td>\nString<\/td>\nIf true, a network token was available for use for the payment.<\/td>\n<\/tr>\n
Metadata<\/td>\nString<\/td>\nThe contents of the metadata<\/a> object of the payment, in the form of key value pairs.<\/td>\n<\/tr>\n
Airline Data

Before the migration<\/strong>: Airlinedata<\/td>\n		String<\/td>\nAirline data<\/a> related to the payment, if available.<\/td>\n<\/tr>\n
Risk Profile<\/td>\nString<\/td>\nThe name of the risk profile<\/a> that was evaluated during the transaction.<\/td>\n<\/tr>\n
Risk Profile Id

Before the migration<\/strong>: Risk Profile ID<\/td>\n		Numeric<\/td>\nThe ID of the risk profile that was evaluated during the transaction.<\/td>\n<\/tr>\n
Risk Profile Reference<\/td>\nString<\/td>\nThe reference number of the risk profile that was evaluated during the transaction.<\/td>\n<\/tr>\n
POS Transaction Date

Before the migration<\/strong>: milliseconds were included.<\/td>\n		Date<\/td>\nThe transaction date for a point-of-sale transaction.<\/td>\n<\/tr>\n
POS Store

Before the migration<\/strong>: Store<\/td>\n		String<\/td>\nThe identifier assigned to the store in your point-of-sale account.<\/td>\n<\/tr>\n
POS Entry Mode<\/td>\nString<\/td>\nIndicates how card details were entered into the terminal. Common entry modes: MKE<\/em> (Manual Key Entry), MSR<\/em> (PAN auto-entry via magnetic stripe), Chip<\/em> (PAN auto-entry via chip), CTLS MSR<\/em> (Contactless card).
Possible values:
  • Unknown<\/em><\/li>
  • MKE<\/em><\/li>
  • MSR<\/em><\/li>
  • Bar Code Read<\/em><\/li>
  • OCR Coding Read<\/em><\/li>
  • Chip<\/em><\/li>
  • CLTS Chip<\/em><\/li>
  • RFID<\/em><\/li>
  • MSR (transmitted)<\/em><\/li>
  • CTLS MSR<\/em><\/li>
  • Biometrics<\/em><\/li>
  • Chip (CVV unreliable)<\/em><\/li><\/ul><\/td>\n<\/tr>\n
POS CVM Performed

Before the migration<\/strong>: CVM Performed<\/td>\n		String<\/td>\nA two-digit hexadecimal code indicating the type of card verification that was used.<\/td>\n<\/tr>\n
POS Library Implementation

Before the migration<\/strong>: Library Implementation<\/td>\n		String<\/td>\nThe type of library implementation, for example Android<\/em>, iOS<\/em>, C<\/em> or .NET<\/em>.<\/td>\n<\/tr>\n
Library Version<\/td>\nString<\/td>\nVersion number of the library used, or standalone<\/em> if the payment terminal is not integrated with the POS system.<\/td>\n<\/tr>\n
POS Terminal Version

Before the migration<\/strong>:Terminal App Version<\/td>\n		String<\/td>\nThe version of the POS terminal application.<\/td>\n<\/tr>\n
ARes TransStatus<\/td>\nString<\/td>\nThe transaction status of the 3D Secure 2 authentication request. This is the final result of the authentication, unless the value is C<\/em>, which means a challenge flow is initiated.<\/td>\n<\/tr>\n
RReq TransStatus<\/td>\nString<\/td>\nThe 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.<\/td>\n<\/tr>\n
3DS Version<\/td>\nString<\/td>\nThe version of the 3D Secure protocol used for the payment.<\/td>\n<\/tr>\n
Liability Shift<\/td>\nBoolean<\/td>\nIndicates if a liability shift took place for the payment.
Possible values: TRUE<\/em> or FALSE<\/em><\/td>\n<\/tr>\n
Merchant Category Code

Before the migration<\/strong>: MCC<\/td>\n		String<\/td>\nThe Merchant Category Code<\/a>.<\/td>\n<\/tr>\n
Retry Json<\/td>\nString<\/td>\nRetry information about the payment.<\/td>\n<\/tr>\n
POS Store and Forward Indicator

Before the migration<\/strong>: POS Store and Forward indicator<\/td>\n		Boolean<\/td>\nIndicates if this was a store-and-forward<\/a> transaction.
Possible values: TRUE<\/em> or FALSE<\/em><\/td>\n<\/tr>\n
POS Cash Register Name

Before the migration<\/strong>: Cash register name<\/td>\n		String<\/td>\nThe name of the POS system.<\/td>\n<\/tr>\n
POS Tender Reference<\/td>\nString<\/td>\nThe tender reference of the point-of-sale payment.<\/td>\n<\/tr>\n
Split Payment Data<\/td>\nString<\/td>\nSplit payment data for the payment, if applicable.<\/td>\n<\/tr>\n
Real Time Account Updater Status

Before the migration<\/strong>: Realtime account updater status<\/td>\n		String<\/td>\nThe status of the Real Time Account Updater<\/a> request.<\/td>\n<\/tr>\n
Original Card Bin<\/td>\nString<\/td>\nThe card BIN of the card that was used to process the original payment request.<\/td>\n<\/tr>\n
Network Transaction Reference<\/td>\nString<\/td>\nThe network transaction reference of the payment.<\/td>\n<\/tr>\n
Recurring Detail Reference<\/td>\nString<\/td>\nThe recurring detail reference used for the payment.<\/td>\n<\/tr>\n
Card Number<\/td>\nString<\/td>\nObfuscated card number showing the card BIN, an obfuscated section and the last four digits.
For example: 411111****1111<\/em><\/td>\n<\/tr>\n
Reserved 2

November 2023<\/strong>: this column has been removed.<\/td>\n		String<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n
Reserved 3

November 2023<\/strong>: this column has been removed.<\/td>\n		String<\/td>\nReserved for future enhancements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n

Configure report columns<\/h2>\n

If you want to add additional columns or change the order of columns in a report, you can do so in the Customer Area<\/a>. If you have an automated system that uses the report's data, configuring the report columns can affect your automated system.<\/p>\n

To configure report columns, you need to have one of the following user roles<\/a>:<\/p>\n