<p>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.</p>


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

<p>U.S. Bank Europe DAC. Registered in Ireland – Number 418442..  Registered Office: Block F1, Cherrywood Business Park, Dublin 18, D18 W2X7, Ireland.</p>
<p>U.S. Bank Europe DAC, trading as Elavon Merchant Services, is regulated by the Central Bank of Ireland.</p>
<p><br>
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.</p>
<p>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.</p>


Most popular solutions

Additional solutions

Fusebox integration & options

Optional platform features

Documentation

North America

Europe

Regions

When submitting a request establish an adequate http timeout value to prepare for delays or connection issues. Elavon recommends setting the timeout value to 60 – 120 seconds.

## Step 1: Session token request

Request a session token :magic-link[/hosted-payments/transaction_token]{id="api-reference#tag/Request-Session-Token"} using x-www-form-urlencoded key/value pairs. The session token response is only valid for 15 minutes and can only be used once. A session token will be returned.  

:::::notice{note}

- Make sure to URL encode the session token so that the special characters and symbols such as `+` and `&` are encoded properly. Failure to URL encode will result in a 401 error message.
:::::

| Objects | Description |
|----------------|----------------------------------------|
| Credentials | API user credentials. :magic-link[Contact us]{id="overview#getting-started"} if you need your user credentials. <br>Required |
| Transaction type | Available :magic-link[payment types]{id="transaction-types"}<br>Required |
| Transaction amount | If no amount is provided, your customer will be prompted to enter the amount |
| Payment token | See :magic-link[credit card tokens]{id="transaction-types#credit-card-tokens"} |
| Invoice number | This value is passed back to the card issuer and provided to the cardholder on their monthly statement to identify the transaction | 
| Customer name | The cardholder’s / customer’s name - prepopulates your payment page |
| Billing address | The cardholder’s / customer’s billing address to prepopulate your payment page |
| Shipping address | The cardholder’s / customer’s shipping address to prepopulate your payment page |
| Doing Business As | How information should appear on a customer's credit card statement. See :magic-link[DBA]{id="dba"}. |
| Language option | HPP integration supports the following language values in the `ssl_language` field:<ul><li>en = US English</li><li>fr = Canadian French</li></ul> | 

## Step 2: Redirect to hosted payment page 

Once the session token is obtained, you should redirect the customer's browser. See sample code below. Ensure you have set your :magic-link[redirect URL]{id="customize-payment-page-hpp-only"} so your customer is redirected to your page when they complete the transaction.  

**Best Practices**
- Your credentials must be kept secure. Elavon strongly recommends passing and storing Converge credentials through server-side code instead of client-side code. 
- Always submit data to Converge through Hyper Text Transfer Protocol Secure (HTTPS) using the POST method. 
- Request parameters should be included in the body of the message.  Do not put request parameters in the request url.

## Sample HPP integration  
### HTML server-side code

```html
<html> 
<head> 
    <meta http-equiv="content-type" content="text/html; charset=UTF-8"> 
    <title>Hosted Payment Page Demo</title> 
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js"></script> 
    <script> 
        function initiateHPP () { 
            var tokenRequest = { 
            ssl_amount: document.getElementById('ssl_amount').value 
            }; 
            $.post("SecureCredentials.php", tokenRequest, function( data ) { 
            document.getElementById('ssl_txn_auth_token').value = data; 
            transactionToken = data; 
            }); 
            return false; 
        } 
    </script> 
</head> 

<body> 
    <form name="getSessionTokenForm"> 
        <p> 
            Transaction Amount: <input type="text" id="ssl_amount" name="ssl_amount" value="100.00"> 
        </p> 
        <p> 
        <button onclick="return initiateHPP();">Initiate Session</button> 
        </p> 
    </form> 
    <p></p> 
    <form action="https://api.demo.convergepay.com/hosted-payments/" method="POST" enctype="application/x-www-form-urlencoded"> 
        <table border="1" width="40%" bordercolorlight="#C0C0C0" cellspacing="1" bordercolordark="#FFFFFF"> 
            <tr> 
                <td colspan="2"><b><font face="Arial Narrow">Redirect Cardholder to Converge HPP - DEMO</font></b></td> 
            </tr> 
            <tr> 
                <td><font face="Arial Narrow">One Time Session Token</font></td> 
                <td><font face="Arial Narrow"> 
                <input id="ssl_txn_auth_token" type="text" name="ssl_txn_auth_token" size="25"></font></td> 
            </tr> 
            <tr> 
                <td colspan="2"> 
                <p align="center"> 
                <font face="Arial Narrow"> 
                <input type="submit" value="Redirect Cardholder to Converge" name="Submit"></font></td> 
            </tr> 
        </table> 
    </form> 
</body> 
</html>
```

### PHP client-side code (SecureCredentials.php)

```php
<?php 

$merchantID = "xxxxxx"; //Virtual Merchant Account ID 
$merchantUserID = "apiuser123"; //Virtual Merchant User ID 
$merchantPinCode = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"; //Converge PIN 
$vendorID = "xxxxxx"; //Vendor ID 

$url = "https://api.demo.convergepay.com/hosted-payments/transaction_token"; // URL to Converge demo session token server 
//$url = "https://api.convergepay.com/hosted-payments/transaction_token"; // URL to Converge production session token server  

// Read the following querystring variables 

$amount= $_POST['ssl_amount']; //Post Tran Amount

$ch = curl_init(); // initialize curl handle 
curl_setopt($ch, CURLOPT_URL,$url); // set url to post to 
curl_setopt($ch, CURLOPT_POST, true); // set POST method 
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); 

// Set up the post fields. If you want to add custom fields, you will add them in Converge and add the field name in the curlopt_postfields string. 
curl_setopt($ch, CURLOPT_POSTFIELDS, 
"ssl_merchant_id=$merchantID". 
"&ssl_user_id=$merchantUserID". 
"&ssl_pin=$merchantPinCode". 
"&ssl_vendor_id=$vendorID". 
// "&ssl_first_name=Samuel". //You can pass in values from your application, and they will appear and pre-populate the HPP form 
// "&ssl_avs_address=7301 Chapman Hwy". //You can pass in values from your application, and they will appear and pre-populate the HPP form 
// "&ssl_avs_zip=37920". //You can pass in values from your application, and they will appear and pre-populate the HPP form 
"&ssl_invoice_number=Inv123".  
//"&ssl_next_payment_date=03/03/2023". //used only if transaction type is ccrecurring 
//"&ssl_billing_cycle=MONTHLY".  //used only if transaction type is ccrecurring 
"&ssl_transaction_type=ccsale". 
"&ssl_verify=N". //set to 'Y' if transaction type is ccgettoken, otherwise not needed 
"&ssl_get_token=Y". //pass with 'Y' if you wish to tokenize the card as part of a ccsale, do not send if transaction type set to ccgettoken 
"&ssl_add_token=Y". // should always be Y if using card manager and either transaction type is set to 'Y' or if ssl_get_token is set to 'Y'. 
"&ssl_amount=$amount" //do not pass amount if using ccgettoken as the transaction type 
); 

curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); 
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false); 
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); 
curl_setopt($ch, CURLOPT_VERBOSE, true);

$result = curl_exec($ch); // run the curl process 
curl_close($ch); // Close cURL

echo $result; //shows the session token. 

?>
```

Take a payment

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

Payment types

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