Elavon downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalising content, and measuring site performance.

Essential cookies enable core functionality such as page navigation and access to secure areas. The website cannot function properly without these cookies; they can only be disabled by changing your browser preferences.

These are cookies that support site functionality that is visible or advantageous to you or your experience of the site, they enable websites to remember choices and provide a more personalized experience.   Functional cookies help to provide services that you request, such as language preference or layout.

Performance cookies help us to improve our website by collecting and reporting information on its usage (for example, which of our pages are most frequently visited).

These cookies and similar technologies gather information about your browsing habits. They remember that you've visited a website and share this information with other organisations, such as advertisers and platforms on which we advertise. They do this in order to provide you with ads that are more relevant to you and your interests. Although these cookies and similar technologies can track your visits to other websites, they don't usually know who you are. Without these cookies, online advertisements you encounter will be less relevant to you and your interests.

Cookie Settings

U.S. Bank Europe DAC. Registered in Ireland – Number 418442..  Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.
 
U.S. Bank Europe DAC. Registered in Ireland with Companies Registration Office. The liability of the member is limited. United Kingdom branch registered in England and Wales under the number BR022122.
U.S. Bank Europe DAC, trading as Elavon Merchant Services, is a credit institution authorised and regulated by the Central Bank of Ireland.  Authorised by the Prudential Regulation Authority.  Subject to regulation by the Financial Conduct Authority and limited regulation by the Prudential Regulation Authority.  Details about the extent of our regulation by the Prudential Regulation Authority are available from us on request.

Most popular solutions

Additional solutions

Fusebox integration & options

Optional platform features

Documentation

North America

Europe

Regions

Opayo Pi is a level 1 PCI-compliant, full-service payment gateway with 99.99% uptime, which is ideal for e-commerce businesses of all sizes. It offers a variety of integration paths which can be used individually or in conjunction with each other to provide a flexible, friction-free, and secure checkout experience for your customers, all with 24/7 telephone support available.

Features:
- A selection of integration paths – drop-in.js checkout, a restful API, and a customisable hosted payment page.
- 3D Secure, AVS, CV2 and advanced fraud screening tools
- Digital wallet support for Apple Pay, Google Pay, PayPal, and other alternative payment methods
- Dedicated transaction reporting and account administration portal 
- Support for subscription and recurring payments
- Stored card and network tokenisation functionality
- 24/7 telephone support

:::notice{important}
Opayo Pi is only available in the United Kingdom and Ireland.
:::



## Getting Started

### Step 1: Contact the Opayo technical support team

 :magic-link[Our World class support and guidance]{id="support"} will get you up and running as quickly as possible.

### Step 2: Integrate your payment page

Decide which integration method works best for you:
- When you use our :magic-link[drop-in checkout integration]{id="integration-options-byopp"}, your shopper enters their card details into our drop-in UI.
- When you want full control of the checkout experience you can :magic-link[integrate your own form]{id="integration-options-byopp"}. Your shopper enters their card details into a form of your own design.
- If you want a more hands-off approach, you can customise our :magic-link[hosted payment page]{id="integration-guide-hpp"}. This method lets you construct an Opayo-hosted payment page that allows your customers to make payments in a secure, PCI-compliant manner.

We capture the card details and transmit them securely to Opayo using the SagePay.js JavaScript library. We will return a single-use Card Identifier token for you to use in your payment request. :magic-link[You can ask to reuse tokens, too]{id="tokens-reusable-identifiers"}.

### Step 3: Verify your authentication and credentials

All Opayo Pi requests are made using HTTPS and must be authenticated. We use HTTP Basic authentication, which is a simple and secure method of enforcing access controls.

:::::notice{warning}
All requests are made using HTTPS to ensure the security of your customers’ sensitive information.
:::::
::::notice{warning}
An SSL handshake occurs when connecting to Opayo's servers. Before going live, we recommend verifying that you have the [latest root certificate from this link](https://www.entrust.com/resources/certificate-solutions/tools/root-certificate-downloads) for Opayo's certificate issuing authority installed on your servers. If you have any issues, you can check out [how to fix SSL Certificate errors](https://blog.hubspot.com/website/fix-ssl-certificate-error). If you need additional help, contact [support@opayo.io](mailto:support@opayo.io?subject=Pi%20-%20SSL%20certification%20help%20required%20).
::::

#### Pi credentials 
You will find your Pi credentials in your account on MyOpayo. If you don't have credentials yet, you can use a :magic-link[sandbox account]{id="test-in-sandbox"} available for our test environment. Credentials are specific to the test or live environments. When you encounter a problem connecting with an environment, check that you are using the correct credentials.

:::notice{warning}
- When you create new credentials, they immediately render all existing credentials invalid.
- You must replace your expired credentials with the new ones in any integration with our REST API, or your calls will not be authorised.
- You must record and save your new credentials securely. - Pi credentials do not work for any legacy or alternative integration methods.
:::

### Retrieve your integration key and password 
Before integrating with Pi or accessing our [TEST environment](https://sandbox.opayo.eu.elavon.com/mysagepay/login.msp "Opens in a new browser window or tab") or [LIVE environment](https://live.opayo.eu.elavon.com/mysagepay/login.msp "Opens in a new browser window or tab"), you must follow these steps to retrieve your **Integration Key** (username) and **Integration Password**: 
1. Sign in to your MyOpayo Administrator account. Use the credentials provided during your account setup.
2. On the **Administrator** tab, in the **Password** details section, check the disclaimer box.

:::notice{info}
**Note:** You are agreeing that by creating new credentials, your existing Opayo API implementations may not function before you replace your legacy credentials in them with the new credentials.
:::
3. Click **Create API credentials**. 
4. Record, save, and secure the: - **Environment.** This is the Test or Live environment the credentials apply to. - **Vendor Name**. The **vendorname** for the account. - **Integration Key**. The value for the Integration key (your **username**). - **Integration Password**. The value for the Integration password.

### Step 4: Test and certify your integration

Once you have integrated your payment solution with Opayo, we recommend that you test the integration.

Only use Elavon-approved card numbers to test your integration. Refer to the :magic-link[Test in sandbox page]{id="test-in-sandbox"} for more information.

### Step 5: Go live

- Replace the demo endpoints with the production endpoints when you finish testing your integration.
- Activate your production account by contacting Elavon support.

## Additional information and restrictions

For all integrations you must:
- Create a Session Key to authenticate your calls from the browser.
- Enable the Opayo JavaScript library to Tokenise card details as the unique Card Identifier used to submit payments from your server.

Overview

Alliance Offers

Data as a Service

Invitation to Apply

Bank Holidays

Card Activation

Card Controls

Challenge-Widget

Commercial Credit Cards

Commercial Statements

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Balance Transfers

Credit Card Disputes

Credit Card Payments

Credit Card Qualified Offers

Credit Card Statements

Credit Card Transactions

Data Sharing for Marketing Purposes

Digital Wallets

Incoming Webhooks

Make a Payment - Coming Soon

Rewards Accelerator

Rewards Automatic Redemption

Rewards: Balance Summary

Rewards: Dashboard

Rewards Redemption Accounts

Rewards Redemptions

Rewards Transactions: Earned and Redeemed

Travel Notifications

User Profile

3DSecure2

CheckoutJs

Commerce SDK

Converge

Disputes Management

Dynamic Currency Conversion

eBoarding

Elavon Cloud Payments Interface

Elavon Payment Gateway

Fusebox

Hosted Payment Page

In Person Payments on Opayo

Leads

Lightbox payment modal

Online Payments on Opayo

Opayo

Opayo Direct

Opayo Forms

Opayo Reporting API

Opayo Server

Opayo Shared API

Payment Method Gateway

Payments Core 365

Simplify

viaconex

XML API

Card as a Service API

Core Banking API

Money Movement API

Reference API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Avvance Connect

Avvance Express

Avvance Flex

Bank Information

Card as a Service

Check Payables

Corporate Account Information

Corporate Account Information 3LO

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Debit Card Phone Number Lookup

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Foreign Exchange

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

RTP® - Real-Time Payments

Tokenized Payments

Treasury Builder

U.S. Bank FBO Account

Virtual Account Reporting

Virtual Card Payments

Voyager Accounts

Voyager Cards

Voyager Drivers

Voyager Transactions

Voyager Vehicles

Wire Transfers

Build your own payment page

API reference

Integration options

Transaction types

Additional options

PayPal integration

Apple Pay

Apple Pay (Opayo managed certificate)

Apple Pay (Merchant managed certificate)

Google Pay

Alternative payment methods

3D Secure authentication

SCA exemptions

Tokens (reusable identifiers)

Credential on file

Hosted payment page

Integration guide

Tokens

Test in Sandbox

Support

Compliance information

Change Log