{"title":"Received payment details report","category":"default","creationDate":1788346618,"content":"<p>The Received payment details report provides details about all authorized and refused payments you processed through Adyen, including shopper interaction, risk score, and acquirer response.<\/p>\n<h2>Requirements<\/h2>\n<p>Before you begin, take into account the following requirements and preparations.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Requirement<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Integration type<\/strong><\/td>\n<td style=\"text-align: left;\">You must be onboarded as a franchisee by your franchisor. For more information, see <a href=\"\/franchisees\/onboarding\">Onboarding<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><a href=\"\/franchisees\/users#roles\">\n  <strong>Customer Area roles<\/strong>\n<\/a><\/td>\n<td style=\"text-align: left;\">To download the report, you must have the following role:<br> <strong>Generate key financial reports<\/strong>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"notices yellow\">\n<p>This report contains personal shopper data such as card numbers, email addresses, and billing addresses. If you access unmasked shopper data, it can affect your PCI DSS compliance level. To download unmasked data, your user must have the <strong>Merchant View PII<\/strong> <a href=\"\/franchisees\/users#roles\">role<\/a>.<\/p>\n<\/div>\n<h2 id=\"get-the-report\">Get the report<\/h2>\n<p>To generate and download the report:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-live.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li>\n<li>Go to <strong>Reports<\/strong> &gt; <strong>Reports overview<\/strong>.<\/li>\n<li>Select <strong>Received payment details<\/strong> report. You see a list of all generated Received payment details reports.<\/li>\n<li>Select <strong>Generate report<\/strong> to generate the report manually, or select <strong>Modify automatic generation<\/strong> to set up automatic generation.<\/li>\n<\/ol>\n<h2 id=\"report-structure\">Report structure<\/h2>\n<h3 id=\"entries\">Entries<\/h3>\n<p>Under the header line, each line in the report is a separate entry.<\/p>\n<h3 id=\"standard-columns\">Standard columns<\/h3>\n<div class=\"sticky-table-container\">\n    \n<table>\n<thead>\n<tr>\n<th>#<\/th>\n<th>Column<\/th>\n<th>Data type<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1<\/td>\n<td>Company Account<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The name of your company account as registered in the Adyen payments platform.<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Merchant Account<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The name of the merchant account that was used to process the original payment request. <br>The report may contain line items for multiple merchant accounts.<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Psp Reference<\/td>\n<td>Unicode Text (16-character limit)<\/td>\n<td>Adyen'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<tr>\n<td>4<\/td>\n<td>Merchant Reference<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The reference that was specified in the payment request.<\/td>\n<\/tr>\n<tr>\n<td>5<\/td>\n<td>Payment Method<\/td>\n<td>Unicode Text (30-character)<\/td>\n<td>The payment method used for the transaction. <br>For example: <em>visa<\/em>, <em>mc<\/em>, <em>mc_applepay<\/em>, <em>amex<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>6<\/td>\n<td>Creation Date<\/td>\n<td>String<\/td>\n<td>The timestamp indicating when the payment was created on the Adyen payments platform.<br>Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br>For example: <em>2012-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td><\/td>\n<td>Creation Date Time Zone<\/td>\n<td>Alpha Text (4-character limit)<\/td>\n<td>The time zone of the <strong>Creation Date<\/strong>. <br>This is the ISO code for your time zone setting.<\/td>\n<\/tr>\n<tr>\n<td>7<\/td>\n<td>Currency<\/td>\n<td>Unicode Text (3-character limit)<\/td>\n<td>The three-character <a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_4217\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">ISO currency code<\/a>.<\/td>\n<\/tr>\n<tr>\n<td><\/td>\n<td>Amount<\/td>\n<td>Numeric <br><br>or<br><br> String (only in <code>.XLS<\/code> and <code>.XLSX<\/code> report files)<\/td>\n<td>The amount of the payment (authorization amount). Always a positive value, even if the payment was canceled before being captured.<\/td>\n<\/tr>\n<tr>\n<td>8<\/td>\n<td>Type<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The record type. <br>For this report, the value is always <em>Payment<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>9<\/td>\n<td>Risk Scoring<\/td>\n<td>Integer<\/td>\n<td>The total risk score of the payment.<\/td>\n<\/tr>\n<tr>\n<td>10<\/td>\n<td>Shopper Interaction<\/td>\n<td>Alpha Text (30-character limit)<\/td>\n<td>The transaction type.<br>Possible values: <em>Ecommerce<\/em>, <em>ContAuth<\/em>, <em>POS<\/em>, <em>MOTO<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>11<\/td>\n<td>Shopper Name<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The name of the cardholder, as specified in the transaction, if available.<\/td>\n<\/tr>\n<tr>\n<td>12<\/td>\n<td>Shopper PAN<\/td>\n<td>Alphanumeric (80-character)<\/td>\n<td>The Primary Account Number (<a href=\"\/get-started-with-adyen\/adyen-glossary\/#card-number-pan\">PAN<\/a>). <br>In case of card payments, the last four digits of the card number.<br>For SEPA, this field shows the IBAN and BIC in the following format: <code>IBAN\/BIC<\/code><\/td>\n<\/tr>\n<tr>\n<td>13<\/td>\n<td>Shopper IP<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The IP address (IPV4 or IPV6) of the shopper as specified in the original transaction, if available.<\/td>\n<\/tr>\n<tr>\n<td>14<\/td>\n<td>Shopper Country<\/td>\n<td>Alpha Text (2-character limit)<\/td>\n<td>The 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<tr>\n<td>15<\/td>\n<td>Issuer Name<\/td>\n<td>Unicode Text<\/td>\n<td>The name of the issuing bank, if available.<\/td>\n<\/tr>\n<tr>\n<td>16<\/td>\n<td>Issuer Id<\/td>\n<td>Alphanumeric (30-character limit)<\/td>\n<td>The unique identifier of the issuer.<br>In case of card payments this will be the issuer BIN (first six digits of the card number).<\/td>\n<\/tr>\n<tr>\n<td>17<\/td>\n<td>Issuer City<\/td>\n<td>Unicode Text (80-character)<\/td>\n<td>The city of the issuer, if available.<\/td>\n<\/tr>\n<tr>\n<td>18<\/td>\n<td>Issuer Country<\/td>\n<td>Alpha Text (2-character limit)<\/td>\n<td>The ISO country code of the issuer.<\/td>\n<\/tr>\n<tr>\n<td>19<\/td>\n<td>Acquirer Response<\/td>\n<td>Alphanumeric<\/td>\n<td>The normalized response from the acquirer. Not necessarily the final status of the payment. When a payment is canceled before being captured, the acquirer response is <em>Unknown<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>20<\/td>\n<td>Authorisation Code<\/td>\n<td>Unicode Text (50-character)<\/td>\n<td>The authorisation code returned for a successful payment.<\/td>\n<\/tr>\n<tr>\n<td>21<\/td>\n<td>Shopper Email<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The email address of the shopper, as specified in the original transaction, if available.<\/td>\n<\/tr>\n<tr>\n<td>22<\/td>\n<td>Shopper Reference<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The shopper ID or reference that was specified in the original transaction.<\/td>\n<\/tr>\n<tr>\n<td>23<\/td>\n<td>3D Directory Response<\/td>\n<td>Alpha Text (1-character limit)<\/td>\n<td>For payments processed with 3D Secure (Secure Code\/Verified by Visa), the 3D Directory response. <br>Values: <em>Y<\/em>, <em>N<\/em>, <em>U<\/em>, <em>E<\/em><\/td>\n<\/tr>\n<tr>\n<td>24<\/td>\n<td>3D Authentication Response<\/td>\n<td>Alpha Text (1-character limit)<\/td>\n<td>For payments processed with 3D Secure (Secure Code\/Verified by Visa), and directory response <em>Y<\/em>, this holds the authentication response. <br>Values: <em>Y<\/em>, <em>N<\/em>, <em>U<\/em>, <em>A<\/em>, <em>E<\/em><\/td>\n<\/tr>\n<tr>\n<td>25<\/td>\n<td>CVC2 Response<\/td>\n<td>Text field Numeric (1-Character limit)<\/td>\n<td>The result passed back by the issuer after verifying the CVC2, or CVV2\/CID in case of Visa\/Amex.<\/td>\n<\/tr>\n<tr>\n<td>26<\/td>\n<td>AVS Response<\/td>\n<td>Text field Numeric (2-Character limit)<\/td>\n<td>If Address Verification (AVS) was performed, the result of the AVS Check.<\/td>\n<\/tr>\n<tr>\n<td>27<\/td>\n<td>Billing Street<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The street part of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>28<\/td>\n<td>Billing House Number \/ Name<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The house number or name part of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>29<\/td>\n<td>Billing City<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The city part of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>30<\/td>\n<td>Billing Postal Code \/ ZIP<\/td>\n<td>Unicode Text (30-character)<\/td>\n<td>The ZIP code or postal code part of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>31<\/td>\n<td>Billing State \/ Province<\/td>\n<td>Unicode Text (256-character)<\/td>\n<td>The state or province of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>32<\/td>\n<td>Billing Country<\/td>\n<td>Alpha Text (2-character limit)<\/td>\n<td>The ISO country code of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>33<\/td>\n<td>Delivery Street<\/td>\n<td>String<\/td>\n<td>The street part of the delivery address.<\/td>\n<\/tr>\n<tr>\n<td>34<\/td>\n<td>Delivery House Number \/ Name<\/td>\n<td>String<\/td>\n<td>The house number or name part of the billing address.<\/td>\n<\/tr>\n<tr>\n<td>35<\/td>\n<td>Delivery City<\/td>\n<td>String<\/td>\n<td>The city part of the delivery address.<\/td>\n<\/tr>\n<tr>\n<td>36<\/td>\n<td>Delivery Postal Code \/ ZIP<\/td>\n<td>String<\/td>\n<td>The ZIP code or postal code part of the delivery address.<\/td>\n<\/tr>\n<tr>\n<td>37<\/td>\n<td>Delivery State \/ Province<\/td>\n<td>String<\/td>\n<td>The state or province of the delivery address.<\/td>\n<\/tr>\n<tr>\n<td>38<\/td>\n<td>Delivery Country<\/td>\n<td>String<\/td>\n<td>The ISO country code of the delivery address.<\/td>\n<\/tr>\n<tr>\n<td>39<\/td>\n<td>Acquirer Reference<\/td>\n<td>String<\/td>\n<td>The reference number for the transaction provided by the acquirer.<\/td>\n<\/tr>\n<tr>\n<td>40<\/td>\n<td>Payment Method Variant<\/td>\n<td>Unicode Text (32-character)<\/td>\n<td>The payment method sub-brand, or the main payment method if not available (for example <em>mccredit<\/em> or <em>visagold<\/em>).<\/td>\n<\/tr>\n<tr>\n<td>41<\/td>\n<td>Raw Acquirer Response<\/td>\n<td>String<\/td>\n<td>The raw response received from the acquirer, where available. When a payment is canceled before being captured, the raw acquirer response is empty.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/franchisees\/settlement-details-report\"\n                        target=\"_self\"\n                        >\n                    Settlement details report\n                <\/a><\/li><li><a href=\"\/franchisees\/payment-accounting-report\"\n                        target=\"_self\"\n                        >\n                    Payment accounting report\n                <\/a><\/li><li><a href=\"\/franchisees\/payments-lifecycle\"\n                        target=\"_self\"\n                        >\n                    Payments lifecycle\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/franchisees\/received-payment-details-report","articleFields":{"description":"Get details about authorized and refused payments, including the shopper interaction, risk score, and acquirer response.","feedback_component":true},"algolia":{"url":"https:\/\/docs.adyen.com\/franchisees\/received-payment-details-report","title":"Received payment details report","content":"The Received payment details report provides details about all authorized and refused payments you processed through Adyen, including shopper interaction, risk score, and acquirer response.\nRequirements\nBefore you begin, take into account the following requirements and preparations.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nYou must be onboarded as a franchisee by your franchisor. For more information, see Onboarding.\n\n\n\n  Customer Area roles\n\nTo download the report, you must have the following role: Generate key financial reports.\n\n\n\n\nThis report contains personal shopper data such as card numbers, email addresses, and billing addresses. If you access unmasked shopper data, it can affect your PCI DSS compliance level. To download unmasked data, your user must have the Merchant View PII role.\n\nGet the report\nTo generate and download the report:\n\nLog in to your Customer Area.\nGo to Reports &gt; Reports overview.\nSelect Received payment details report. You see a list of all generated Received payment details reports.\nSelect Generate report to generate the report manually, or select Modify automatic generation to set up automatic generation.\n\nReport structure\nEntries\nUnder the header line, each line in the report is a separate entry.\nStandard columns\n\n    \n\n\n\n#\nColumn\nData type\nDescription\n\n\n\n\n1\nCompany Account\nUnicode Text (80-character)\nThe name of your company account as registered in the Adyen payments platform.\n\n\n2\nMerchant Account\nUnicode Text (80-character)\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.\n\n\n3\nPsp Reference\nUnicode Text (16-character limit)\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.\n\n\n4\nMerchant Reference\nUnicode Text (80-character)\nThe reference that was specified in the payment request.\n\n\n5\nPayment Method\nUnicode Text (30-character)\nThe payment method used for the transaction. For example: visa, mc, mc_applepay, amex.\n\n\n6\nCreation Date\nString\nThe timestamp indicating when the payment was created on the Adyen payments platform.Format: YYYY-MM-DD HH:MM:SS. For example: 2012-07-26 19:58:55.\n\n\n\nCreation Date Time Zone\nAlpha Text (4-character limit)\nThe time zone of the Creation Date. This is the ISO code for your time zone setting.\n\n\n7\nCurrency\nUnicode Text (3-character limit)\nThe three-character ISO currency code.\n\n\n\nAmount\nNumeric or String (only in .XLS and .XLSX report files)\nThe amount of the payment (authorization amount). Always a positive value, even if the payment was canceled before being captured.\n\n\n8\nType\nUnicode Text (50-character)\nThe record type. For this report, the value is always Payment.\n\n\n9\nRisk Scoring\nInteger\nThe total risk score of the payment.\n\n\n10\nShopper Interaction\nAlpha Text (30-character limit)\nThe transaction type.Possible values: Ecommerce, ContAuth, POS, MOTO.\n\n\n11\nShopper Name\nUnicode Text (80-character)\nThe name of the cardholder, as specified in the transaction, if available.\n\n\n12\nShopper PAN\nAlphanumeric (80-character)\nThe Primary Account Number (PAN). 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\n\n\n13\nShopper IP\nUnicode Text (50-character)\nThe IP address (IPV4 or IPV6) of the shopper as specified in the original transaction, if available.\n\n\n14\nShopper Country\nAlpha Text (2-character limit)\nThe ISO country code of the shopper, if available. If not available, this is computed based on the shopper's IP address.\n\n\n15\nIssuer Name\nUnicode Text\nThe name of the issuing bank, if available.\n\n\n16\nIssuer Id\nAlphanumeric (30-character limit)\nThe unique identifier of the issuer.In case of card payments this will be the issuer BIN (first six digits of the card number).\n\n\n17\nIssuer City\nUnicode Text (80-character)\nThe city of the issuer, if available.\n\n\n18\nIssuer Country\nAlpha Text (2-character limit)\nThe ISO country code of the issuer.\n\n\n19\nAcquirer Response\nAlphanumeric\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 is Unknown.\n\n\n20\nAuthorisation Code\nUnicode Text (50-character)\nThe authorisation code returned for a successful payment.\n\n\n21\nShopper Email\nUnicode Text (256-character)\nThe email address of the shopper, as specified in the original transaction, if available.\n\n\n22\nShopper Reference\nUnicode Text (256-character)\nThe shopper ID or reference that was specified in the original transaction.\n\n\n23\n3D Directory Response\nAlpha Text (1-character limit)\nFor payments processed with 3D Secure (Secure Code\/Verified by Visa), the 3D Directory response. Values: Y, N, U, E\n\n\n24\n3D Authentication Response\nAlpha Text (1-character limit)\nFor 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\n\n\n25\nCVC2 Response\nText field Numeric (1-Character limit)\nThe result passed back by the issuer after verifying the CVC2, or CVV2\/CID in case of Visa\/Amex.\n\n\n26\nAVS Response\nText field Numeric (2-Character limit)\nIf Address Verification (AVS) was performed, the result of the AVS Check.\n\n\n27\nBilling Street\nUnicode Text (256-character)\nThe street part of the billing address.\n\n\n28\nBilling House Number \/ Name\nUnicode Text (256-character)\nThe house number or name part of the billing address.\n\n\n29\nBilling City\nUnicode Text (256-character)\nThe city part of the billing address.\n\n\n30\nBilling Postal Code \/ ZIP\nUnicode Text (30-character)\nThe ZIP code or postal code part of the billing address.\n\n\n31\nBilling State \/ Province\nUnicode Text (256-character)\nThe state or province of the billing address.\n\n\n32\nBilling Country\nAlpha Text (2-character limit)\nThe ISO country code of the billing address.\n\n\n33\nDelivery Street\nString\nThe street part of the delivery address.\n\n\n34\nDelivery House Number \/ Name\nString\nThe house number or name part of the billing address.\n\n\n35\nDelivery City\nString\nThe city part of the delivery address.\n\n\n36\nDelivery Postal Code \/ ZIP\nString\nThe ZIP code or postal code part of the delivery address.\n\n\n37\nDelivery State \/ Province\nString\nThe state or province of the delivery address.\n\n\n38\nDelivery Country\nString\nThe ISO country code of the delivery address.\n\n\n39\nAcquirer Reference\nString\nThe reference number for the transaction provided by the acquirer.\n\n\n40\nPayment Method Variant\nUnicode Text (32-character)\nThe payment method sub-brand, or the main payment method if not available (for example mccredit or visagold).\n\n\n41\nRaw Acquirer Response\nString\nThe raw response received from the acquirer, where available. When a payment is canceled before being captured, the raw acquirer response is empty.\n\n\n\n\n\n\nSee also\n\n\n                    Settlement details report\n                \n                    Payment accounting report\n                \n                    Payments lifecycle\n                \n","type":"page","locale":"en","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Franchisees","lvl2":"Received payment details report"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/franchisees","lvl2":"\/franchisees\/received-payment-details-report"},"levels":3,"category":"","category_color":"","tags":["Received","payment","details","report"]}}
