Your EPS account

Sign in to view secure API documentation, update your account details, log support requests and much more.

Your email or password is incorrect. Please try again or reset your password.
If the issue persists please contact your EPS representative.

Forgot password?

Reset your password

Please enter your email address below. We will send password reset instructions to the email associated with your EPS account.

Thank you

An email has been sent to your account email address with further instructions on how to reset your password.

Back to sign in

EPS Checkout

A secure way to collect credit card information for Property Collect and Expedia Collect bookings

Please note that if you wish to integrate with the EPS Checkout API, you will be required to use EPS Rapid Version 2.1 or 2.2

How does it work?

EPS Checkout gives you the ability to handle Property Collect and Expedia Collect bookings without the need to be PCI compliant. This product will allow you to host an EPS credit card information collection iFrame within your booking form. It's a white label solution so you have full control over the way the form looks on your site. However, you will have no access to any of the information that is collected which means you don't need to be PCI compliant. The benefits are a low effort integration and access to a huge range of properties which do not accept online payments.

When a traveler enters their credit card number and CVV/CVC values they are transmitted, validated and encrypted for storage on EPS servers via the iFrame fields. This information is never stored or supplied by your booking page. However, your booking form will collect and supply the cardholder name, expiration date and all other booking details. 

You can find the list of supported credit cards here. 

Making a booking

  1. The partner needs to send API credentials and a customer browser fingerprint to EPS to get a token. This will be known as the "checkout token".
  2. The partner then needs to serve a page and a link to EPS hosted javascript which will create an iFrame on their checkout page.
  3. Within the iFrame EPS will host input fields for credit card information and javascript to validate and send that information to the EPS Checkout API using the checkout token to authenticate.
  4. We will store the credit card information within our encrypted data store using the Checkout token as a key.
  5. When the partner finally submits the checkout form to our checkout page again using the checkout token, we can link the credit card and customer information using the checkout token as a reference and make a booking.

Site and form set up

  • Construct your checkout form to use container elements with unique IDs for the iFrame credit card and CVV fields. EPS provides active validation for values within each iFrame. 
  • Credit card information must always be provided directly via the iFrames. Do not stack with any additional data collection forms of your own - this will break PCI compliance for your integration.
  • You must also provide a location to store the checkout token hash for use by the client-side script (see next section "Token Generation").

Token Generation 

In order for the checkout iFrame fields to operate, you must generate a checkout token value. The checkout token value is used to identify each unique user & associated booking details when you send your booking request.

Base URL

In order to make calls documented below, the base URL for Checkout is https://checkout.ean.com

For example; https://checkout.ean.com/token/rapid