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

Hosted Payment Page supports credit card, electronic check and gift card transactions. 

## Credit card 
Select the transaction type and send it in the :magic-link[session token]{id="take-a-payment"} request. 
| Transaction type | Definition |
|-------------------|-----------------------------------------------------|
| Credit Card Sale `(ccsale)` | Obtains real-time authorization for a credit card sale transaction and enters the transaction into the unsettled batch. Batch settlement can be done [manually](https://support.convergepay.com/s/article/Settle-a-Batch-Manually) or automatically. |
| Credit Card Generate Token (`ccgettoken`) | Generates a :magic-link[token]{id="transaction-types#credit-card-tokens"} from a card number. The token generated can be used in place of a credit card number in any subsequent transactions made in :magic-link[transaction management]{id="transaction-management"}. |
| Credit Card Authorization Only `(ccauthonly)` | Obtains a real-time authorization for a credit card transaction, guarantees that the funds are available on the card, and reduces the cardholder’s limit to buy for only a predetermined period (which is usually 7-10 days based on the credit card’s issuing bank). This transaction does not place the authorization in the settlement batch. To place the `ccauthonly` transaction in the open batch, use :magic-link[cccomplete]{id="transaction-management#credit-card-management"} or log in to Converge under Payments > Auth Only to convert to a sale or pend. |
| Credit Card Verify `(ccverify)` | Verifies the credit card account for AVS and CVV data. :magic-link[AVS]{id="response-codes#avs"} and :magic-link[CVV]{id="response-codes#cvv2cvc2"} are returned to indicate if the AVS and CVV data passed originally were correct and matched the cardholder statement billing address and the CVV value located on the card. |
| Credit Card Add Recurring `(ccaddrecurring)` | Adds a credit card recurring record to the Converge recurring batch. Once added, the transaction will run automatically within the specified billing cycle on the scheduled payment day without the need to send it for authorization. Recurring transactions will run indefinitely, unless suspended by the user. |
| Credit Card Add Installment (`ccaddinstall`) | Adds a credit card installment record to the Converge recurring batch. Once added, the transaction will run automatically within the specified billing cycle on the scheduled payment day without the need to send it for authorization. Installment transactions will run until the number of installments specified is reached. |


## Credit card tokens

Tokenization is a powerful security feature that allows you to support all existing business processes that require card data without the risk of holding card data and without any security implications therefore protecting the customers' confidential information. 

Tokenization eliminates the risk of storing sensitive data, and substantially reduces the liability and costs associated with PCI compliance. 

- Tokens are not unique if the same card is used multiple times. If the same card is added a second time, the same token will be used instead of generating a new one. 
- Tokens are unique for each merchant. For example, the same card will produce a different token for each merchant. 
- Merchants with multiple terminals sharing tokenization domains will receive the same token for a unique card and the token can be used across their stores if they wish to do so. 

**Requirements** 

Tokenization must be enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 

### Generate a card token
Converge provides the following ways to generate tokens: 

**Option 1.** Generate token while taking a payment/authorization request.

With this token generation method, you include the `ssl_get_token` parameter in the :magic-link[session token]{id="take-a-payment"} request of the following transactions:

- Credit Card Sale
- Credit Card Authorization Only
- Credit Card Add Recurring
- Credit Card Add Installment

**Option 2.** Generate a token without taking a payment/authorization.

With this token generation method, you send the transaction to request a token without a payment:

- Credit Card Generate Token 
- Credit Card Verify

Once a token has been generated, you can manage card tokens via :magic-link[transaction management]{id="transaction-management"} or [customer manager](https://support.convergepay.com/s/article/Customer-Manager).

### Store a card token 
There are two options to store tokenized cards:

**Option 1.** Converge managed tokens

Customer manager enables merchants to tokenize and store the customer's sensitive data and associated information on Elavon's secure servers, which simplifies their PCI-DSS compliance and the payment process for returning customers.  

With this token generation method, you include the `ssl_add_token` parameter in the :magic-link[session token]{id="take-a-payment"} request of the following transactions: 

- Credit Card Sale 
- Credit Card Authorization Only 
- Credit Card Add Recurring
- Credit Card Add Installment
- Credit Card Verify
- Credit Card Generate Token 

Converge will store the token and customer details in the Converge database for future transactions. When a token is used, the information stored in the profile will be included when the transaction is being authorized.

If you want to modify token payments via the API in :magic-link[transaction management]{id="transaction-management"}, you will need to retain and include the following in future payments. 
- `ssl_merchant_initiated_unscheduled`
    - `Y` - If the merchant initiated this payment without cardholder consent (cancellation fee) AND this is NOT a recurring/installment transaction.
    - `N` - If the merchant initiated this payment without cardholder consent (subscriptions) AND this is a recurring/installment transaction.
    - `N` - If the cardholder initiated this payment as a one-time transaction.
    - `N` - If the cardholder initiated this payment for recurring/installment.
- `ssl_recurring_flag` (required if payment is recurring/installment)
    - `1` - recurring
    - `2` - installment 

For more information on managing tokenized cards see [customer manager](https://support.convergepay.com/s/article/Customer-Manager) and :magic-link[transaction management]{id="transaction-management"}

**Option 2.** Merchant managed tokens

The token is not stored in Converge but instead in your own database. With this option, additional fields must be retained and included on all future payments.

- `ssl_exp_date` 
- `ssl_token` 
- `ssl_ps2000_data` 
- `ssl_approval_code`  
- `ssl_association_token `  
- `ssl_merchant_initiated_unscheduled`
    - `Y` - If the merchant initiated this payment without cardholder consent (cancellation fee) AND this is NOT a recurring/installment transaction.
    - `N` - If the merchant initiated this payment without cardholder consent (subscriptions) AND this is a recurring/installment transaction.
    - `N` - If the cardholder initiated this payment as a one-time transaction.
    - `N` - If the cardholder initiated this payment for recurring/installment.
- `ssl_recurring_flag` (required if payment is recurring/installment)
    - `1` - recurring
    - `2` - installment 

:::::notice{note}
If you already have a token with expiry date but do not have the `ssl_ps2000_data` or `ssl_approval_code` then you must store this data and include it the next time you use the token for processing. 
:::::

## Electronic check 

Electronic checks use the Automated Clearing House (ACH) to direct debit from a customer's checking account into a merchant's business bank account. 

**Requirements** 

- Electronic check must be enabled. Verify by calling :magic-link[/VirtualMerchantDemo/accountxml.do]{id="api-reference#tag/Terminal-Management"} with transaction type `terminalsetup`. 
- Region set to USA 

:::::notice{note}
 When testing ACH ECheck transactions, use the following test data:
- The routing number used for the demo environment is 490000018.
- The account number can be numeric up to 16 digits.
:::::

Select the transaction type and send it in the :magic-link[session token]{id="take-a-payment"} request of the following transactions: 

| Transaction type | Definition |
|-------------------|-----------------------------------------------------|
| Electronic Check Purchase (`ecspurchase`) | The `ecspurchase` transaction debits the purchase amount from a checking account.  |
| Electronic Check Add Recurring (`ecsaddrecurring`) | The `ecsaddrecurring` transaction adds an ACH ECheck recurring payment to the Converge recurring batch. Once added, the transaction will run automatically within the specified billing cycle on the scheduled payment day without the need to send it for authorization. Recurring transactions will run indefinitely, unless suspended by the user.  |
| Electronic Check Add Installment (`ecsaddinstall`) | The `ecsaddinstall` transaction adds an ACH ECheck installment payment to the Converge recurring batch. Once added, the transaction will run automatically for the number of installments specified within the specified billing cycle on the scheduled payment day without the need to send it for authorization. Once the total number of installments is reached, the payments will stop running.  |

## Gift card 

Converge allows you to offer gift/loyalty cards options to customers within a single or multi-location environment. You can issue cards for any dollar amount. All transactions will be processed in real-time, and you can add or debited the balance from the cards. 

Contact support to create your card design and to order cards.  

Select the transaction type and send it in the :magic-link[session token]{id="take-a-payment"} request. 

| Transaction type | Definition |
|-------------------|-----------------------------------------------------|
| Electronic Gift Card Redemption (`egcsale`) | The `egcsale` transaction deducts the purchase amount from the balance of the gift card account.  |

## Next steps
- :magic-link[How to take a payment]{id="take-a-payment"}
- :magic-link[How to customize your payment page]{id="customize-payment-page-hpp-only"}

Payment types

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

Overview

API reference

Integration guide

Customize payment page

Take a payment

Transaction management

Additional options

Wallets

Point of sale lending

3D Secure 2

Currency conversion

Doing Business As

Export scripts

Fees

Shopping cart plugins

Billing and invoicing / Hospitality

Authentication

Invoice lifecycle

Managing invoices

Status and error codes

Elavon domains and IP addresses

Error codes

Response codes

Supported MCC currency codes

Test cards

Release notes