Accepting online payments with Verifone can be done through multiple integration methods. This page describes what you need to know in order to decide on which integration method is best for you, where to find the essential information like URLs, and how to authenticate with our API.
Online payments can be processed by using our Checkout solution as a Hosted Payments Page (HPP) or an iFrame. Payment modifications can be done directly via the portal, or by using Server-to-Server API calls. A comparison of the different integration methods can be found here:
|Integration method||Description||PCI compliancy|
|Hosted Payments Page (HPP)||Full page redirect to Verifone servers||SAQ A|
|iFrame||Render a Verifone hosted form on your website||SAQ A|
|Pay by Link||Send payment links to your customers manually or automate with an API||SAQ A|
|Server-to-Server API||Perform API calls to capture customer payment information and place orders||SAQ D|
To process transactions through the sandbox and production environments, you will be using different API keys. One key is used for sandbox, and one is used for production. Make sure your API key and secret are never stored on the client’s side, they are only intended for Server-to-Server API calls.
The URL you use determines if you are making calls into the sandbox or production environments. Different URLs, API keys and other variables need to be used in sandbox and production. When setting up your environments, make sure the following variables are configurable:
|API key||Retrieved from Verifone Central|
|User ID||Retrieved from Verifone Central|
|Payment Provider Contracts||Administration > Payment Provider Contracts > [Contract] > Payment Provider Contract ID value|
|3DS Contract||Administration > 3D-Secure Provider Contracts > [Contract] > 3-D Secure Contract ID|
|Entity ID||Administration > Organizations > [Organization] > Organisation ID value|
Organisation ID (Entity ID) in Verifone Central
Sandbox and production URLs