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

## Test 3D Secure

The following table lists our magic **CardHolder** values. When you test your Opayo Direct transaction request, these simulate 3D-Authenticated transaction responses.

| Magic Value | 3DSecureStatus | 3D Secure Rule | Description |
|---|---|---|---|
| SUCCESSFUL | OK | Passes all rules | Returned for a frictionless flow where authentication is successful. |
| NOTAUTH | NOTAUTHED | Accept 3d auth failure | Returned for a frictionless flow where authentication is unsuccessful. |
| CHALLENGE | Status=3DAUTH  3DSecureStatus=OK | - | Returned for a challenge flow. The cardholder will be re-directed to the ACS to enter two-factor authentication. A CReq, VPSTxId, ACSURL and StatusDetail will also be returned.  Once you re-direct to the ACSURL, entering the correct password displayed on the site will simulate a successful authentication, entering any other password will simulate an unsuccessful authentication. |
| NOTENROLLED | NOAUTH | Accept card not in scheme | Authentication could not be performed |
| PROOFATTEMPT | ATTEMPTONLY | Passes all rules | The cardholder attempted to authenticate themselves, and the process did not complete. A CAVV is returned and this is treated as being successfully authenticated. |
| REJECT | NOTAUTHED | Rejects before rulebase check | Authentication rejected by Issuer. |
| TECHDIFFICULTIES | INCOMPLETE | Accept issuer not in scheme | 3D-Secure authentication was unable to complete. No authentication occurred. |
| ERROR | ERROR | Accept MPI failure | Simulates an error condition where 3D-Authentication cannot be performed due to data errors or service unavailability in one of the parties involved in the check. It can also result if you have not submitted the creq to the ACSURL within thirty seconds, or your customer has not entered 2FA on the ACS’s authentication page within ten minutes. |


## Test 3D Secure Passwords

:::::notice{warning}

**Important**. All other phrases will fail authentication.
:::::


### 3DS2

**3DS2 Secure Password Responses**
| Value | Description |
|---|---|
| **challenge** | Successful authentication. (All other phrases will fail authentication). |

## Test Address Values

To test your failure pages use a Test Card. The test will always return an **OK** response and an Authorisation Code. All other card numbers will be declined.

Test your Rule Base and fraud-specific code by omitting the following codes. The transaction will authorise and you will receive NOTMATCHED messages in the AVS/CV2 checks.

- Billing Address 1: 88
- Billing Post Code: 412

## Test Payment Cards

You can use the following Test Card details using any Expiry date and the CVV: 123 (1234 for Amex cards).

**Available test payment cards for 3D Secure testing**
| Payment Method | Card Number | Card Type |
|---|---|---|
| Visa | 4929000000006 | Visa |
| Visa | 4929000005559 | Visa |
| Visa | 4929000000014 | Visa |
| Visa | 4929000000022 | Visa |
| Visa Corporate | 4484000000002 | Visa |
| Visa Debit | 4462000000000003 | VisaDebit |
| Visa Electron | 4917300000000008 | VisaElectron |
| MasterCard | 5186150660000009 | MasterCard |
| MasterCard | 5186150660000025 | MasterCard |
| MasterCard | 5186150660000108 | MasterCard |
| MasterCard | 5186150660000207 | MasterCard |
| Debit MasterCard | 5185690060000001 | DebitMasterCard |
| Maestro (UK Issued) | 6759000000005 | Maestro |
| Maestro (German Issued) | 6705000000008 | Maestro |
| Maestro (Irish Issued) | 5185570760000008 | Maestro |
| Maestro (Spanish Issued) | 6766000000000 | Maestro |
| American Express | 374200000000004 | AmericanExpress |
| Diners Club / Discover | 36000000000008 | Discover |
| JCB | 3569990000000009 | JCB |

### Apple Pay Testing

To test an Apple Pay (Merchant managed certificate) transaction, use a card number from the Apple Pay [sandbox](https://developer.apple.com/apple-pay/sandbox-testing/) . Configure the test transactions to pass the following **amount** values to get the described result:

| Amount | Expected Result    |
|-------------|-------------------------|
| 106.00  | Successful authorisation. |
| 107.00 | Transaction will soft decline. |
| 108.00 | Successful authorisation, but transaction upgraded to ecommerce type 5. |
| 109.00 | Successful authorisation, but transaction downgraded to ecommerce type 7. |



## PayPal Testing

PayPal is available to the Opayo test environment. You can test without using a live PayPal account.

:::::notice{warning}

**Important:** ONLY test your PayPal integration when your site can correctly send and process the messages exchanged between your site and ours for a standard Opayo Direct transaction.
:::::


### Set Up

1. Sign in to [https://developer.paypal.com. ](https://developer.paypal.com/)
2. Create one or more Sandbox accounts including at least one each of: 
    - Personal (buyer account)
    - Business (merchant account)

:::::notice{info}

**Note:** An Email address is issued for each account you create.
:::::


1. Sign in to your Business (merchant account) and under **API Access**, add the following test-only Third Party Permission Username:  
     **ppdev\_1256915571\_biz\_api1.sagepay.com**
2. You should grant all available permissions.

### Start Testing

1. Sign in to your Test MyOpayo, and then add the Email address for the Business (merchant account) you created.
2. Choose, either a Mark or Express Checkout option, and then send the Transaction Registration post with the **CardType** set to PAYPAL.
3. Our response to your Transaction Registration Post will return a **Status** of PPREDIRECT and provide a simulated **PayPalRedirectURL**.

### Check Results

1. Ensure your code stores the **VPSTxId** and redirects the test customer’s browser to the PayPal Sign In page.
2. Where you have provided them, the **BasketXML** information is shown with your company logo. Sign in using the Personal (buyer account) to complete the transaction process with PayPal
3. Opayo will send a message to your PayPalCallbackURL along with the customer. Ensure your script can handle a **PAYPALOK** Status. You can choose to: 
    - Accept the transaction based on the PayerStatus and or AddressStatus (as the result of these fields can dictate if the transaction is eligible for PayPal Seller Protection)
    - Modify the Amount by +/- 15% of the original value (if the delivery price changes as a result of the address selected

### Complete the Transaction

1. To proceed with the transaction, send a POST to the PayPal Completion URL with a value of YES in the Accept field. This will return a **Status** of OK in the final response to your servers. 
    - When the **AddressStatus** is UNCONFIRMED, and the **PayerStatus** UNVERIFIED, you may not wish to continue.
    - If you do NOT wish to proceed, you must still send a POST to the Opayo servers to complete the transaction. Enter a value of NO in the Accept field to cancel the transaction. This will return a **Status** of NOTAUTHED in the final response to your servers.
2. When you receive this final response from Direct (:magic-link[here]{id="transaction-registration-post-response"}), and depending on the **Status** of the transaction, you should redirect your customer to the relevant completion page on your site.

- A **Status** of OK should redirect the user to a success page.
- An ERROR, NOTAUTHED, REJECTED, MALFORMED or INVALID **Status** should redirect to the relevant error handling page.

:::::notice{warning}

**Important.** Please visit PayPal’s website for localised Seller Protection terms and conditions.
:::::

## Test URLs

**Test URLs by operation**
| Operation | URL |
|---|---|
| REGISTRATION | https://sandbox.opayo.eu.elavon.com/gateway/service/vspdirect-register.vsp |
| 3D-SECURE CALLBACK | https://sandbox.opayo.eu.elavon.com/gateway/service/direct3dcallback.vsp |
| PAYPAL COMPLETION | https://sandbox.opayo.eu.elavon.com/gateway/service/complete.vsp |

## Live URLs

**Live URLs by operation**
| Operation | URL |
|---|---|
| REGISTRATION | https://live.opayo.eu.elavon.com/gateway/service/vspdirect-register.vsp |
| 3D-SECURE CALLBACK | https://live.opayo.eu.elavon.com/gateway/service/direct3dcallback.vsp |
| PAYPAL COMPLETION | https://live.opayo.eu.elavon.com/gateway/service/complete.vsp |
## Support

Email the [Opayo Support team](mailto:support@opayo.com?subject=Opayo%20Direct%20%7C%20Testing) for help with your debugging issues.

Testing

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

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

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

Avvance

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

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

Freight Payment Customer Profiles

Freight Payment Transactions

Incoming Webhooks

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

Opayo Direct Overview

Taking a Payment

1. The customer orders from your site

2. Your server registers the payment with Opayo

3. Opayo replies to your registration POST

4. Opayo submits 3D Secure Authentication

5. You redirect your customer to their Issuing Bank

6. 3D-Authentication and your site called back

7. Your site POSTs the 3D Secure results to Opayo

8. Opayo servers request card authorisation

9. Opayo replies to your POST

10. Opayo sends Settlement Batch Files

Integrating with PayPal

Apple Pay

Integrating with Apple Pay (Opayo managed certificate)

Integrating Apple Pay (merchant managed certificate)

Google Pay

Tokenisation

3D Secure Transactions

Compliance

PCI Compliance

PSD2 Compliance

MCC 6012

Zero Value Authorisation (ZVA)

Additional Transaction Types

DEFERRED Transactions

REPEAT Transactions

AUTHENTICATE and AUTHORISE Transactions

REFUND and VOID Transactions

SCA Exemptions

SCA Exemptions Overview

Soft Declines

Credential on File

API Reference

Transaction registration POST

Transaction Registration POST Response

ThreeDSRequestorAuthenticationInfoXML

ThreeDSRequestorPriorAuthenticationInfoXML

AcctInfoXML

MerchantRiskIndicatorXML

Basket

BasketXML

TRIPS

CustomerXML

Response to Transaction Registration POST (Status=3DAUTH)

3D-Authentication Results POST from your Terminal URL 

Response to Transaction Registration POST (Status=PPREDIRECT)

Callback after PayPal Authentication

Complete a PayPal Transaction 

Protocol 3.00 > 4.00 Migration Guide

Protocol 3.00 > 4.00 Migration Guide overview

Protocol 2.23 > 4.00 Migration Guide

Change Log