Payment Pages extend the basic Relay Response protocol by allowing the merchant's server to send 302 or 303 HTTP Redirects to the First Data Payeezy Gateway server instead of the usual HTML. The extension consists of passing such HTTP Redirects on to the customer's web browser. The browser will then automatically follow the redirect and load the receipt page directly from the URL specified in the redirect.
Using this extension offers the following advantages:
- The merchant can include sensitive information about the customer in the receipt page which the merchant does not want to share with the First Data Payeezy Gateway Payment Pages server.
- The receipt page will appear under a URL on the merchant's site, and not under https://checkout.gateway.payeezy.com
- When the customer's web browser loads the redirect target page, it will send any cookies that the merchant may have set earlier. If the merchant maintains an internal session for the customer, the session data will be available when producing the receipt page.
- The receipt page can refer to stylesheets, javascript, images, or any other files stored on the merchant's server with relative URLs. The receipt page can follow the natural organization of the merchant's web application.
To enable Relay Response Extensions, go to the Relay Response tab of the Payment Page configuration and select the checkbox: "Pass HTTP Redirects to the Customer's Browser."