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

Checkout.js uses Converge’s JavaScript library to collect cardholder data from the customer’s browser and send it directly to Converge for processing. Sensitive data won't touch your server, allowing you to avoid the compliance burden for handling payment card information or personally identifying data. The result of the transaction returns to the browser and can display as a response to the customer and update the back-end systems. 

This integration method is ideal for businesses that want: 

- More control over the customization of their payment page. 
- A consistent look and feel throughout your website and payment page. 
- Have PCI Level 1 Service Provider (SAQ A-EP). 

**Restrictions** 

Checkout.js does not currently support the fields required to process lodging transactions. If you are required to provide fields such as **arrival date** or **room number**, :magic-link[Fusebox]{id="/products/fusebox/v1/lodging-transactions"} may be a better solution for you. 

## Workflow

:::image{id="/content/dam/developer-portal-solutions/en-us/elavon/media/images/products/checkoutjs/Checkoutjs_1.svg" alt="Workflow diagram showing the interaction between customer and Elavon through Converge payment gateway"}
:::

## Integration checklist 

**Step 1 - Contact software technical support team/customer service** 

To integrate using Checkout.js, you'll need to contact the Software Technical Support Team or Customer Service at 1-800-377-3962 | Option 2 | Option 2, or by emailing <#sedevportalsupport@elavon.com>. They can help you:

- Register and add the IP address of the server that will send the session token request and the web URL to an allowed list. 
- Set a Converge user ID with an API user status with permission to post a session token request. 
- Provide API credentials. 

**Step 2 - Integrate with Checkout.js** 

To use the Converge JavaScript Library, your server must have the following settings: 

- All pages that use the Converge payment script must use HTTPS protocol. 
- The domain must have a valid SSL certificate. 
- The server must support TLS 1.2 or 1.3 with Perfect Forward Secrecy (PFS). 

Use the following endpoints in our *demo environment.* 

Endpoint: `https://api.demo.convergepay.com/hosted-payments`

- Session token request: :magic-link[/transaction_token]{id="/products/checkout-js/v1/api-reference#tag/Request-Session-Token"} 
- Checkout.js: :magic-link[/checkout.js]{id="/products/checkout-js/v1/api-reference#tag/Checkout.js-Transaction-Request"} 

**Step 3 - Ensure your PCI compliance** 

Elavon requires you and your merchants that use Converge to support customer compliance with the Payment Card Industry–Data Security Standard (PCI-DSS) guidelines. You are required to validate [PCI compliance as a PCI Level 1 Service Provider (SAQ A-EP)](https://www.pcisecuritystandards.org/document_library/?category=saqs#results) annually. This requires the submission of a Report on Compliance (ROC) based on an on-site audit completed by a Qualified Security Assessor (QSA) before processing. 

Card brand registration is also required. PCI validation must be completed, and documentation provided to execute the registration process with each card brand network annually. 

The PCI-DSS are a set of requirements that enhance the security of payment account data. The core principles and requirements of the PCI-DSS are:

- Build and maintain secure networks
- Protect cardholder data
- Maintain a vulnerability management program
- Implement strong access control measures
- Regular network monitoring and testing
- Maintain information security policies

The Payment Application–Data Security Standard (PA–DSS) provides you and your merchants the guidelines to develop secure payment applications that follow the PCI–DSS and don't store sensitive data. The summarized PA–DSS guidelines that payment applications integrating to Converge must comply with are:

1. Non-retention of full magnetic stripe data, card validation code
 (CAV2, CID, CVV2, CVC2), or PIN block data.
2. Protection of stored cardholder data.
3. Availability of secure authentication features.
4. Logging of payment application activities.
5. Protection for wireless transmissions.
6. Facilitation of secure network implementations.
7. Non-collection and storing of cardholder data on an Internet-connected server.
8. Facilitation of secure remote network updates.
9. Facilitation of secure remote access to payment applications.
10. Encryption of sensitive traffic over public networks.
11. Encryption of all non-console administrative access.
12. Maintenance of instructional documentation and training programs for you, your customers, and resellers.

This table lists the PCI-DSS and PA-DSS resources for data security compliance.

| **Resource** | **Description** |
| ----------------------------------------------------------------------------------| ------------------------------------------------ |
| [PCI Security Standards Council](https://www.pcisecuritystandards.org/) | An open global forum for ongoing development, enhancement, storage, dissemination, and implementation of security standards for account data protection. |
| [PCI Security Documents Library](https://www.pcisecuritystandards.org/document_library) | A list of documents covering a range of Payments Card Industry topics. If you need more information on PCI security and compliance, you can probably find some information here. |
| [PIN Transaction Security (PTS) Devices](https://www.pcisecuritystandards.org/security_standards/ped/pedapprovallist.html) | List of approved PTS devices. |
| [PCI Software Security Framework](https://docs-prv.pcisecuritystandards.org/Software%20Security/Standard/PCI-Secure-Software-Standard-v1_2_1.pdf) | Complete list of software requirements and guidance for PCI Software Security Framework. |
| [PA–DSS Program Guide](https://www.pcisecuritystandards.org/pdfs/pci_pa_dss_program_guide.pdf?class=track_link) | PCI’s PA – DSS Program Guide |

**Step 4 - Test and certify your integration** 

Once you have integrated your payment solution with Converge, we recommend that you test the integration. Here are the important links needed for testing your integration before going live: 

- Only use Elavon-approved card numbers to test your integration. Refer to the :magic-link[Test cards]{id="/products/checkout-js/v1/test-cards"} page for more information. 
- If you receive any errors while testing, refer to the :magic-link[Error codes]{id="/products/checkout-js/v1/error-codes"} page for more details. 

To certify your integration, you will be provided with a test script. The type and number of tests you need to run depends on your region, market segment and the transaction types you will accept as defined in your Solution Statement. Contact your solution engineer for more information. 

**Step 5 - Go live** 

- Replace the demo endpoints with the production endpoints when you finish testing your integration: 

 - Session Token Request: `https://api.convergepay.com/hosted-payments/transaction_token`
 - Checkout.js: `https://api.convergepay.com/hosted-payments/Checkout.js` 

- Activate your production account by contacting Elavon support. 
- Use real cards to connect with Elavon's production server.

Overview

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

API reference

Integration guide

Payment types

Take a payment

Transaction management

Additional options

Wallets

Point of sale lending

Fees

Currency Conversion

3D Secure 2

Export scripts

Shopping cart plugins

Billing and invoicing / Hospitality

Authentication

Invoice lifecycle

Managing invoices

Status and error codes

Error codes

Response codes

Supported DCC currency codes

Test cards

Elavon domains and IP addresses

Release notes