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.

It is now possible to use Elavon signing capabilities to have your merchant sign your partner documentation at the same time the Elavon documents are being signed. These third-party documents can be dynamically generated at signing time. It is also possible to display non-dynamically generated third-party documents.

To utilize third-party signing, partners must provide document templates in XHTML format and any desired images in JPG or PNG format, as well as indicate where the images should be placed within the document template. 

Third party documents are assigned a document name and cardinal number that are used to identify and retrieve specific documents.

Below are examples of how to create and retrieve third-party documents. In the examples, two third-party documents are included in XHTML format using two cardinal numbers, 1122 and 1213. Each cardinal number represents a specific third-party document template.

Signed document(s) can be generated after the document packet is signed and submitted for boarding.

**/createdocumentpacket** request example:

```
"partnerDocumentData": {
    "1122": {
	          "partnerCustomFieldName1": "sampleValue1",
	          "partnerCustomFieldName2": "sampleValue2"
    },
    "1213": {
		  "partnerCustomFieldName3": "sampleValue3",
		  "partnerCustomFieldName4": "sampleValue4"
    }
},
```

**/createdocumentpacket** response example:

```
{
    "responseId": 0,
	"error": null,
	"documentPacketId": "0bf18d64-b725-4b3b-80ef-10387cfeaea0",
	"signerResponses": [
	    {
                "signerId": "1DAM20220321115",
		"signerUrl": "Sample signerUrl"
	    }
	]
}
```

**/getsignedpacket** request example:

```
{
    "documentPacketId": "0bf18d64-b725-4b3b-80ef-10387cfeaea0"
}
```

**/getsignedpacket** response example:

```
{
	"responseId": 0,
	"error": null,
	"documents": {
		"APPLICATION": "base-64 encoded string",
		"PARTNER_DOCUMENTS": {
			"1122": "base-64 encoded string",
			"1213": "base-64 encoded string"
		},
		"TERMINAL_HIRE_AGREEMENT": "base-64 encoded string"
	}
}
```

## Standalone Third-Party Signing

It is possible to use Elavon signing capabilities to sign partner document(s) without showing Elavon documents or providing unnecessary eBoarding application data.  Building the XHTML template is the same process as described above,  :magic-link[Third-Party Signing]{id="third-party-signing"}.

To set up standalone third-party document signing: 
   - The field, `isThirdPartyStandalone` must be set to “true”
   - The field, `agreementId` is an optional field for the partner’s merchant identification number (MID).  

      **Note:** It only makes sense to provide this field if you want to allow a merchant the ability to upload a document to an existing record. Document upload will only work for an application previously boarded by the eBoarding platform.

Below is an example of initiating standalone third-party signing:

```  
"documentPacketData" : {
   "isThirdPartyStandalone": "true",
   "agreementId" : "8025341440",
      "partnerDocumentData": {
         "100200": {
           "legalName": "Testing Partner Document",
           "dogName": "Dog Name"
         }
      }
}
```

## Linking to Third-Party Static Documents

Partners can provide a link to third-party static documents in the customer UI so that merchants may download and view the document(s). 

To create a link, partners must provide the static document to their Solutions Engineer, so it can be added to the Elavon database and later referenced via a cardinal number.

The link displayed is based on the filename of the static document, which may be in one or more languages. 

PAPI **Managed flow** partners can specify the cardinal number of the document using the the  `createdocumentpacket` PAPI operation. A link to that document is then displayed in the **Additional Documentation** section of the UI when the application is generated.

Third-Party Signing

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

eBoarding Partner API Overview

Integration by flow type

Prerequisites and tools

Boarding process workflows

Main boarding elements

Passing data to board

Principal applicant

Additional shareholders

Contact information

Financial information

Card pricing

Bank account information

Billing

Fees

Payment processing equipment

Dynamic currency conversion (DCC)

Value added services

Third-party signing

Complementary API calls

API reference

Element code tables

Merchant category codes

Boarding timeouts

Push notifications

Best practices

Release notes

2024

2023

2022

2021

2020