ProtectPay PMI – Hosted Payment Page


Considerations specific to the Hosted Payment Page
As with all of the ProtectPay Payer Management Interfaces, the HPP is only needed when new payment method information must be collected. To process using an existing ProtectPay token, simply perform a ProtectPay API processing call.

With the Hosted Payment Page, you enjoy slightly less control over a cardholder’s checkout experience than with the Seamless Payment Interface. The HPP, though, satisfies more of the PCI-DSS requirements. Use of the HPP are required to validate using SAQ A.

The look and feel of the Hosted Payment Page can be modified using a CSS URL. That process is not covered on this website, but you can get information about it in the HPP documentation. Links to this documentation can be accessed below.

HPP Processing Configurations
The HPP can be configured to perform various payment method storage and/or processing requests. These options include:
  • Create a Payment Method
  • Create and Authorize a Payment Method for a specified amount
  • Create and Process a Payment Method for a specified amount
  • Authorize a payment method for a specified amount
  • Process a payment method for a specified amount
  • Authorize a payment method for a specified amount and create a PaymentMethodId only if authorization is successful
Summary of Processing
  1. Each HPP instance is created specific to a ProtectPay payer. Create one for new customers, or use an existing payer.
  2. Create an instance of the HPP using the API method [CreateHostedTransactionIdentifier]
  3. Redirect the payer to our HPP, or embed that HPP into an iframe. (Not covered on this website.)
  4. Handle our simple ‘Success’ message, and obtain the details of the transaction by making the API call [GetHostedTransactionResults]
 
Get Started: Create a Payer
 
Just take me to the API docs