Skip to main content

Introduction

Payen provides a secure hosted user interface called IP.Frame. This section details how to integrate IP.Frame with your payment processing system.

There are two flavours of IPFrame available that offer different user experiences:

Standard IPFrame is a modal dialog in an iframe that can be embedded in a merchant's website. It can be customised with the merchant's colours and logos, and can be used to accept card and all supported alternative payment methods (APMs).

Simplified IPFrame (SIP) uses full page redirect to APMs that do not allow being activated from within a frame. When using SIP the customer will have no direct interaction with IPFrame, but will be taken from the merchant site to the first page of the APM site where they complete the payment. On completion the customer browser is redirected to the merchant site.

IP.Frame has the ability to recognise customers and store payment methods which can then be re-used making all future payments quicker and easier. IP.Frame also has the ability to make more informed decisions about declined payments giving the cardholder better information about how to proceed and complete the order/payment.

The service significantly reduces the scope of PCI-DSS for merchants. IP.Frame provides a seamless integration for both existing and new merchant websites.

A summary of the features available are as follows:

  • Secure integration method eliminating sensitive data transmission from IP.Frame to merchant via the customer's browser.
  • Each customer is identified by and linked to the merchant customer identification value.
  • Payment methods are stored against each customer for future payments.
  • The ability for customers to add new payment methods, remove existing payment methods and select a default payment method.
  • Helpful and constructive feedback to the customer for declined transactions.
  • Integrated 3D Secure solution.
  • Spending limitations can be applied at a merchant, account, customer or card level.
  • Configurable customer and payment method blocking to safeguard against fraudulent activity.
  • Detailed trail of user actions to identify transaction activity.
  • Support for multiple languages.
  • Customisable look via merchant hosted styles and images.

For more information on any of these features or configuration options, please speak to your Integration Manager.

info

All the server to server requests are in an JSON or XML format for extensibility.

All API calls are performed over standard HTTPS (SSL) POST. The body and HTTP request must be encoded using UTF-8.

The content type should be set as “application/json” or “text/xml” and the digest should always be sent as an HTTP header. For more information on digest calculation, please see the Digest Calculation section.