{"title":"Payment response","category":"default","creationDate":1776961627,"content":"<div class=\"sc-notice warning\"><div>\n<p><strong>Hosted Payment Pages are no longer available<\/strong><\/p>\n<p>To accept payments through an Adyen-hosted page, use our <a href=\"\/pt\/online-payments\/build-your-integration\/sessions-flow?platform=Web&amp;integration=Hosted%2BCheckout\">Hosted Checkout<\/a>.<\/p>\n<p>This page is for the classic Hosted Payment Pages (HPP) integration, which has reached end-of-life.  We are no longer processing transactions though HPP.<\/p>\n<\/div><\/div>\n<p>This table lists the fields to be passed in an\u00a0HPP payment response.<\/p>\n<table><thead><tr class=\"header\"><th>Field<\/th><th>Type<\/th><th>Required<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td>\n<p><code>additionalData.acquirerReference<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-x-\" alt=\"-x-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/x.png\" \/><\/p>\n<\/td><td>\n<p>This field is returned for buy now, pay later payment methods in the result URL.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>authResult<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/p>\n<\/td><td>\n<p>Returns the outcome of the payment. It can take one of the following values:<ul><li markdown=\"1\"><code>AUTHORISED<\/code>: The payment authorisation was successfully completed.<\/li><li markdown=\"1\"><code>REFUSED<\/code>: The payment was refused. Payment authorisation was unsuccessful.<\/li><li markdown=\"1\"><code>CANCELLED<\/code>: The payment was cancelled by the shopper before completion, or the shopper returned to the merchant's site before completing the transaction.<\/li><li><code>PENDING<\/code>: It is not possible to obtain the final status of the payment.<br><br \/>\nThis can happen if the systems providing final status information for the payment are unavailable, or if the shopper needs to take further action to complete the payment.<\/li><li markdown=\"1\"><code>ERROR<\/code>: An error occurred during the payment processing.<\/li><\/ul><\/p>\n<\/td><\/tr><tr><td>\n<p><code>merchantReference<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/p>\n<\/td><td>\n<p>The reference you assigned to the\u00a0<a href=\"\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-request\">original payment<\/a>.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>merchantReturnData<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-x-\" alt=\"-x-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/x.png\" \/><\/p>\n<\/td><td>\n<p>If you define this field in the\u00a0<a href=\"\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-request\">payment session setup<\/a>, the value is returned as is. This information is useful to build a custom result page, and it integrates seamlessly with the shopper's session on your server.When the payment status is defined, we send you a webhook event. This event is the recommended way to update the payment status in your back office. Webhooks are more reliable in its delivery because the\u00a0<code>resultURL<\/code> parameter relies on the shopper's browser\/computer\/Internet connection, any of which could fail at any time.We recommend setting a fixed\u00a0<code>resultURL<\/code>\u00a0in the skin configuration. However, sometimes it may be preferable to set the result URL on a per-payment basis: to override the\u00a0<code>resultURL<\/code>\u00a0value specified in the skin configuration, you need to set the result URL for the payment session with the <code>resURL<\/code>\u00a0parameter.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>merchantSig<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/p>\n<\/td><td>\n<p>The signature in Base64 encoded format. It is generated by concatenating the values of payment session fields, and by computing the HMAC using the shared secret, as configured in the skin. <br>For more information, refer to <a href=\"\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/hmac-signature-calculation\">HMAC signature calculation<\/a>.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>paymentMethod<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-x-\" alt=\"-x-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/x.png\" \/><\/p>\n<\/td><td>\n<p>The payment method used in the transaction.When\u00a0<code>authResult<\/code>\u00a0equals\u00a0<code>CANCELLED<\/code>, the payment method may not be known \u2013 in this case, it is not included.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>pspReference<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-x-\" alt=\"-x-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/x.png\" \/><\/p>\n<\/td><td>\n<p>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.When\u00a0<code>authResult<\/code> equals <code>PENDING<\/code>,\u00a0<code>ERROR<\/code> or <code>CANCELLED<\/code>, the\u00a0<code>pspReference<\/code> may not yet be known; therefore, it may be empty or not included.<\/p>\n<\/td><\/tr><tr><td>\n<p><code>reason<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-x-\" alt=\"-x-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/x.png\" \/><\/p>\n<\/td><td>\n<p><div class=\"sc-notice note\"><div> Only applicable for iDEAL payment method. <\/div><\/div>If a shopper cancels a payment, this field returns a random number.If the transaction results in an error, this field returns either of the possible following values:<ul><li markdown=\"1\">authentication_error<\/li><li markdown=\"1\">format_error<\/li><li markdown=\"1\">invalid_field<\/li><li markdown=\"1\">invalid_request<\/li><li markdown=\"1\">invalid_amount<\/li><li markdown=\"1\">system_failure<\/li><li markdown=\"1\">unknown_account<\/li><li markdown=\"1\">unknown_error<\/li><li markdown=\"1\">unknown_id<\/li><\/ul><\/p>\n<\/td><\/tr><tr><td>\n<p><code>shopperLocale<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/p>\n<\/td><td>\n<p>The <code>shopperLocale<\/code> value provided in the\u00a0<a href=\"\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-request\">payment request<\/a>.<div class=\"sc-notice info\"><div> If no value is specified in the request, the default value <code>en_GB<\/code> is returned. <\/div><\/div><\/p>\n<\/td><\/tr><tr><td>\n<p><code>skinCode<\/code><\/p>\n<\/td><td>\n<p>String<\/p>\n<\/td><td>\n<p><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/p>\n<\/td><td>\n<p>The code that identifies the\u00a0<a href=\"\/online-payments\/classic-integrations\/hosted-payment-pages\/skin\">skin<\/a>\u00a0used to process the payment.<\/p>\n<\/td><\/tr><\/tbody><\/table>","url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-response-fields","articleFields":{"id":"25144477","type":"page","_expandable":{"operations":""},"status":"current","sitemap":{"priority":0.3},"parameters":{"anchor_new":"<a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/CheckoutService\/latest\/post\/payments__section_resParams\">API Explorer<\/a>","parent_page":"classic Hosted Payment Pages (HPP)","new_desc":"integrating using our Checkout APIs"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-response-fields","title":"Payment response","content":"\nHosted Payment Pages are no longer available\nTo accept payments through an Adyen-hosted page, use our Hosted Checkout.\nThis page is for the classic Hosted Payment Pages (HPP) integration, which has reached end-of-life.  We are no longer processing transactions though HPP.\n\nThis table lists the fields to be passed in an\u00a0HPP payment response.\nFieldTypeRequiredDescription\nadditionalData.acquirerReference\n\nString\n\n\n\nThis field is returned for buy now, pay later payment methods in the result URL.\n\nauthResult\n\nString\n\n\n\nReturns the outcome of the payment. It can take one of the following values:AUTHORISED: The payment authorisation was successfully completed.REFUSED: The payment was refused. Payment authorisation was unsuccessful.CANCELLED: The payment was cancelled by the shopper before completion, or the shopper returned to the merchant's site before completing the transaction.PENDING: It is not possible to obtain the final status of the payment.\nThis can happen if the systems providing final status information for the payment are unavailable, or if the shopper needs to take further action to complete the payment.ERROR: An error occurred during the payment processing.\n\nmerchantReference\n\nString\n\n\n\nThe reference you assigned to the\u00a0original payment.\n\nmerchantReturnData\n\nString\n\n\n\nIf you define this field in the\u00a0payment session setup, the value is returned as is. This information is useful to build a custom result page, and it integrates seamlessly with the shopper's session on your server.When the payment status is defined, we send you a webhook event. This event is the recommended way to update the payment status in your back office. Webhooks are more reliable in its delivery because the\u00a0resultURL parameter relies on the shopper's browser\/computer\/Internet connection, any of which could fail at any time.We recommend setting a fixed\u00a0resultURL\u00a0in the skin configuration. However, sometimes it may be preferable to set the result URL on a per-payment basis: to override the\u00a0resultURL\u00a0value specified in the skin configuration, you need to set the result URL for the payment session with the resURL\u00a0parameter.\n\nmerchantSig\n\nString\n\n\n\nThe signature in Base64 encoded format. It is generated by concatenating the values of payment session fields, and by computing the HMAC using the shared secret, as configured in the skin. For more information, refer to HMAC signature calculation.\n\npaymentMethod\n\nString\n\n\n\nThe payment method used in the transaction.When\u00a0authResult\u00a0equals\u00a0CANCELLED, the payment method may not be known \u2013 in this case, it is not included.\n\npspReference\n\nString\n\n\n\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.When\u00a0authResult equals PENDING,\u00a0ERROR or CANCELLED, the\u00a0pspReference may not yet be known; therefore, it may be empty or not included.\n\nreason\n\nString\n\n\n\n Only applicable for iDEAL payment method. If a shopper cancels a payment, this field returns a random number.If the transaction results in an error, this field returns either of the possible following values:authentication_errorformat_errorinvalid_fieldinvalid_requestinvalid_amountsystem_failureunknown_accountunknown_errorunknown_id\n\nshopperLocale\n\nString\n\n\n\nThe shopperLocale value provided in the\u00a0payment request. If no value is specified in the request, the default value en_GB is returned. \n\nskinCode\n\nString\n\n\n\nThe code that identifies the\u00a0skin\u00a0used to process the payment.\n","type":"page","locale":"pt","boost":15,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Classic integrations for Ecommerce","lvl3":"Hosted Payment Pages","lvl4":"Reference for Hosted Payment Pages","lvl5":"Payment response"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations","lvl3":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages","lvl4":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api","lvl5":"\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/hosted-payment-pages-api\/hpp-payment-response-fields"},"levels":6,"category":"Online Payments","category_color":"green","tags":["Payment","response"]}}
