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.

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

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

Tokenization is a powerful security that allows a merchant to support all of their 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 substantially reduces the liability and costs associated with PCI compliance, and eliminates the risk of storing sensitive data.

Merchants set up for the tokenization service receive responses that include a token, if requested. The generated token is linked to a specific card number and not to a transaction. Furthermore, you can generate a token and save the token with associated information in Card Manager.

Card Manager enables merchants to tokenize and store sensitive payment information on Elavon's secure servers, simplifying their PCI-DSS compliance and payment processing for returning customers. Card Manager allows access to all tokens that have been generated from your integrated application or directly added to the integrated application.

## Code Samples

### CWS 

#### Request

| Property | Description |
| --- | --- |
| parameters JSONObject required | All relevant parameters for tokenization. |
| generateToken boolean optional | Generate Token Indicator Indicates whether to tokenize or not the card number. **Valid values:** - true - false (Default) |
| addToken boolean optional | Store Token Indicator Indicates whether to store or not the token in Card Manager. **Valid values:** - true - false (Default) |


#### Response

| Property | Description |
| --- | --- |
| data JSONObject | Object holding various responses. |
| tokenizedCard boolean | Token Token generated for the card number. |


#### Example

##### Request

```json
{
 "method" : "startPaymentTransaction",
 "requestId" : "355383921",
 "targetType" : "paymentGatewayConverge",
 "version" : "1.0",
 "parameters" : {
 "paymentGatewayId" : "be02a77b-16f4-4bf7-98c3-fca61f9cb564",
 "transactionType" : "SALE",
 "tenderType" : "CARD",
 .....
 "generateToken" : true, 
 "addToken" : true,
 .....
 }
}
```

##### Response

```json
{
 "requestId" : "355383949",
 "statusDetails" : "REQUEST_ACCEPTED",
 "data" : {
 "paymentGatewayCommand" : {
 "completed" : true,
 "eventQueue" : [ ],
 "chanId" : "55b28627-c74f-404f-be38-e883afc44a31",
 "paymentTransactionData" : {
 "result" : "APPROVED",
 "authCode" : "******",
 "resultMessage" : "APPROVED",
 "date" : "Mon Mar 07 11:12:53 MST 2016",
 "cardEntryType" : "SWIPE",
 "cardScheme" : "VISA",
 "amount" : {
 "currencyCode" : "USD",
 "value" : 2400
 },
 "id" : "070316D3A-EC405BF4-B2E5-4BEB-AF3A-58A93F74D85A",
 "transactionType" : "SALE",
 "approved" : "yes",
 "errors" : [ ],
 "maskedPan" : "******",
 "tokenizedCard" : "7643828574404243",
 "gratuityAmount" : {
 "currencyCode" : "USD",
 "value" : 0
 },
 "signatureBitmap" : {
 "data" : "`!*Q ( ! 0 _' _/ _& _& _'___ _&_____^ _'_____^________^_____^_________ _'_________ _'______ _' _/ ) 0 ( ( ( ( ) ( ( ( 0 ( ( ( ( ( ( ( ( _/ ( ( ( ( (p`%(+ _'_ X _'_ Y _'___ _' ( _' ( _' ) _/ ( ( ) ( ( ( ( 1 ( ( ( ) _' )p`'*._ X _/ _' _' _' _' _' _' _' _' _' _' _&___ _' _& _' _& _' _& _'__^ _' _& _' _' _& _' _' _& _' _' _' _' _' _' _' _'p`)%0 _' ! _' ! ( )p`-)0______ _'_ X______ _'_____^ _'___ _' _'___ _' _' _' _' _/ _/ ( _/ 0 ) ( ) ( 1 ) ) ) 1 * ) ) * ! * ! \" ! ! \"_ Y \"_ X_ Y_ Y_ Y_ X_ Y_ X_ X_ X__Wp`1):_ X _'_ X____ X____ X___ _'_ X_________________^___ _' _/ _' _/ _/ 0 ( ( 0 0 ) 0 1 1 0 ) 1 ) 1 * ) ) \" * ) ! \" \" \"_ Y \"_ Z !_ R_ Y_ Y_ Y_ Q_ Y_ Qp",
 "format" : "SIG_BIN_2"
 },
 "tenderType" : "CARD",
 "balanceDue" : {
 "currencyCode" : "UNKNOWN",
 "value" : 0
 }
 }
 }
 }
}
```

### Java 

```java
...
// we want a token to be generated
tender.setGenerateToken(true);

// If we want the token to be available with Card/Customer Manager in the Converge web site, set this to true. 
// Otherwise a token will still be generated and returned but will not be stored on server.
tender.setAddToken(true);
...
account.getTransactionProcessor().processTransaction(transaction, tender, transactionListener);
...
// When your transaction listener gets a transactionCompleted callback, you'll be able to get the token from it like this:
if (outcome instanceof ECLCardTransactionOutcome)
{
 ECLCardTransactionOutcome cardOutcome = (ECLCardTransactionOutcome)outcome;
 if (cardOutcome.getToken() != null && cardOutcome.getToken().length() > 0)
 {
 System.out.println("My cool token: " + cardOutcome.getToken());
 }
}
```

### Objective-C 

The following will show how to enable token generation and saving of token by setting certain properties on the card tender protocol. Using the same code from the Sale transaction with a card tender, the only addition we need to do before processing the transaction is:

```objc
/* If we want commerce to return a token we always have to set this to YES */
token.generateToken = YES;

/* If we want the token to be available with Card/Customer Manager in the Converge web site, you have to set this to YES. If this is NO, token will still be generated and returned but will not be stored on server */
token.addToken = YES;
```

When the transaction succeeds and your `ECLTransctionProcessingDelegate::transactionDidSucceed` method is called, the "outcome" parameter will be an instance of `ECLCardTransactionOutcome` and you can get the token from that.

```objc
if ([outcome isKindOfClass:[ECLCardTransactionOutcome class]]) {
 ECLCardTransactionOutcome *cardOutcome = (ECLCardTransactionOutcome *)outcome;
 NSString *generatedToken = cardOutcome.token;
}
```

### C\# 

#### Request

```c#
PaymentArgs bea = new PaymentArgs();
...
bea.generateToken = true;
bea.addToken = false; /* Set to true if you want the token to be available for use with Card/Customer Manager in the Converge web site */
...
m_CWS.StartPaymentTransaction(bea, MyNotifyCWSEvent, MyPaymentComplete);
```

#### Response

```c#
public void MyPaymentComplete(PaymentTransactionResults ber)
{
 PaymentTransactionData betd = ber.PaymentTransactionData; 
 if (null != betd) 
 {
 if ((null != betd.tokenizedCard) && (0 < betd.tokenizedCard.Length))
 SaveToken(betd.tokenizedCard);

...
```

Token Request

Alliance Offers

Data as a Service

Invitation to Apply

Accounts

Bank Holidays

Card Activation

Card Controls

Commercial Credit Cards

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

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 Redemption Coming Soon

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

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

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Bank Information

Card as a Service

Card as a Service API

Check Payables

Core Banking API

Corporate Account Information

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Disbursements via Zelle

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Instant payments

Investment Accounting

Money Movement API

PaySmart

Payee Choice

Payee Token+

Personal Loans

Positive Pay

Push to Card

Receivables

Reference API

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

Elavon Commerce SDK Overview

Getting Started

Integration Methods

Commerce Web Services

Java (Windows)

Java (Android)

Objective-C (iOS)

System

Get Environment Information

Get Converge Account Information

Validate BMS Credentials

Payment Terminals

Payment Terminals Overview

Ingenico

iCMP

iPP320

iSC250

Lane 3000

Lane 5000

Link 2500

Moby 5500

RP457c

Self 4000

Card Reader Connection

Device Connection Criteria

Card Reader Configuration

Get Card Reader Information

24-Hour Reboot

On-Demand

Get Device Status

Reset Card Reader

Reboot Card Reader

Encrypted Card Read

Cancel Card Read

Prompt PIN Entry

Capture Card Data

Get Customer Input

Phone Number

Volume Control

Set Shutdown Timeout

Signature Capture

Set Time Zone on Card Reader

TMS Update Check Time Window

SSL Certificate Update Process for Card Reader

Printers

Printers Overview

Get Printer Information

Print Receipts

On Demand Print Receipt

Transaction Types

Transactions Overview

Sale

Auth Only

Auth Only Increment

Convert Auth Only to Sale

Auth Only Reversal

Void

Linked Refund

Stand Alone Refund

Debit Balance Inquiry

Post Auth Tip Adjust

Continue Transaction

Cancel Transaction

Transaction Lookup

Processing Options

Processing Options Overview

Address Verification Service

Force Sale

Gratuity

Manual Card Data Entry

Merchant Transaction Reference

Partial Approval

Pay with Token

Retrieve CVM Signature

Invoice Number

Lane Number

OAR-PS2000 Data

Healthcare

Dynamic currency conversion

Credit Surcharge

Credit Surcharge Overview

Surcharge Property Retrieval

Token Transaction for Surcharge

Transaction Outcome Field for Surcharge

Transaction Search Result for Surcharge

Surcharge In-App

Service Fee

Service Fee Overview

Service Fee Property Retrieval

Token Transaction for Service Fee

Transaction Outcome Field for Service Fee

Transaction Search Result for Service Fee

Service Fee In-App