This page is for the classic Hosted Payment Pages (HPP) integration, which has reached end-of-life. This means we are:
- No longer developing the HPP integration.
- Not accepting new HPP integrations.
- Preparing to stop accepting transactions using HPP.
This table lists the fields to be passed in an HPP payment response.
This field is returned for buy now, pay later payment methods in the result URL.
Returns the outcome of the payment. It can take one of the following values:
|String||The reference you assigned to the original payment.|
If you define this field in the payment 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 server-to-server notification. This notification is the recommended way to update the payment status in your back office. The notification system is more reliable in its delivery because the
We recommend setting a fixed
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.
The payment method used in the transaction.
|String||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.|
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:
If no value is specified in the request, the default value
|String||The code that identifies the skin used to process the payment.|