- 1 Introduction
- 2 Solution Overview
- 3 Merchant e-Commerce Example
- 4 Getting Started with Payeezy Gateway Payment Pages
- 4.1 Configuring the Payeezy Gateway Payment Page
- 4.2 Integration: Two options
- 4.2.1 With Shopping Cart
- 4.2.2 Without a Shopping Cart
- 4.3 Transaction Results and Receipting
- 5 Security
The First Data Payeezy Gateway Payment Pages solution provides merchants with a non-storing, “hands off” solution that complies completely with Payment Card Industry Data Security Standards (PCI-DSS).
This product provides credit card processing through a Payeezy Gateway Payment Page.
Payeezy Gateway Payment Pages eliminate merchant exposure to cardholder data while removing the requirement for SSL certificates. With PCI compliance a critical and mandatory requirement this increases the significance of this facet.
Payeezy Gateway Payment Pages can be customized according to merchant user interface requirements. Colors, logos, and wording can be sent to Payeezy Gateway in HTML format so the cardholder has the same user interface experience during payment as when they are shopping on the merchant site.
Other configuration options available include:
- Receipt notification emails to the cardholder and/or merchant
- Customized messaging for receipt emails
As with all Payeezy Gateway software, Payeezy Gateway Payment Pages include access to all First Data Payeezy Gateway Real-time Payment Manager (RPM) functionality such as Virtual Point of Sale and Reports.
A typical website offering goods for sale is depicted in Figure 1. Customers add items to their shopping cart by pressing the “Add to Cart” button shown in Figure 2.
In Figure 3 the customer clicks the “Checkout” link when ready to pay for their selected items. At this point they are taken to their Payeezy Gateway Payment Page on the Payeezy Gateway servers, shown in Figure 4.
Note from the logo, colours, and font the seamless transition from merchant (Figure 3) to external (Figure 4) site. This external site is where the customer will enter their payment information, isolating the merchant from the sensitive cardholder data.
Displayed is the option for the cardholder to enter their email address for receipt delivery. This an optional offering configured at the merchant’s discretion.
Once the payment has been processed the receipt, or Customer Transaction Record (CTR), appears as in Figure 5.
The first step in setting up Payeezy Gateway Payment Pages is starting the process to obtain a production account with First Data. While registration is in progress merchants can obtain test credentials for their developers to access the demo system and get a head start on the integration.
Once a production account is set up developers can simply configure a live payment page and swap its values with the demo credentials in the code.
To configure a new demo or live Payeezy Gateway Payment Page, Merchant Administrators can log in to Payeezy Gateway Real-time Payment Manager (RPM) (Figure 6) and click on the Payment Pages menu option (Figure 7).
A listing of Payeezy Gateway Payment Pages that are already set up on the account is shown in Figure 8. Merchant Administrators can select one of these links to view or edit its configuration or click the “Create a New Payment Page” link.
There are two basic ways to integrate Payeezy Gateway Payment Pages into a merchant website:
- With a shopping cart
- Without a shopping cart
Integration is fairly straightforward:
- One file in the cart software is renamed
- Two variables from the Payeezy Gateway Payment Page configuration are inserted in the shopping cart configuration
Shopping cart software is not mandatory for Payeezy Gateway Payment Pages as developers can integrate the code directly into an HTML page.
Form code in a variety of languages, including Ruby, Perl, and PHP can be downloaded here.
Note that irrespective of cart or software choice, additional integration is required for merchants that wish to use the Relay Response and Silent Post methods. Please see "Transaction Results Handling" below.
After a transaction is processed, by default the Payeezy Gateway standard transaction receipt is displayed to the customer. There are several options that allow customization of this behavior: Receipt Link, Relay Response, and Silent Post. These options enable a combination of the following:
- Return the transaction results to the merchant site
- Display a transaction receipt generated by the merchant site
- Redirect the customer to the merchant site
|Receipt Link Method||This comes with two options: user-initiated navigation - LINK, GET and POST methods add a link or button on the standard transaction receipt. If the customer clicks the link or button, he/she is taken to the configured URL (usually back to the merchant site), optionally including the transaction results. automatic navigation - AUTO-POST, AUTO-GET and REDI methods automatically take the customer to the configured URL and include the transaction results. These methods are commonly used for custom receipting, where the merchant server processes the returned transaction results and presents a receipt based on them.|
|Relay Response||Sends transaction results to a server specified by the merchant. The response from the merchant server is then passed on to the customer's browser as a receipt for the transaction. It allows the merchant to tailor the receipt page to the individual customer and update their web server in real time (for example, to empty the shopping cart).|
|Silent Post||Similar to Relay Response except that no response is expected from the merchant server, and the customer is shown the standard receipt page. It is typically used as a secondary source of transaction results alongside the Receipt Link or Relay Response methods.|
For additional technical information on the development required for these methods, see the First Data Payeezy Gateway Payment Pages Integration Manual.
Payeezy Gateway Payment Pages are safe and secure. Sophisticated hash calculations are executed on the Payeezy Gateway servers to confirm that only requests from designated merchant sites are accepted. In the case of Relay Response, merchant servers conduct a separate hashing confirmation to verify the authenticity of the response from Payeezy Gateway.