October 2020 Release (R43)

From October 27, 2020 we’ve improved our eBoarding API experience including:

  1. Registration
  2. eBoarding API URL Fields
  3. Guided Flow Updates
  4. eBoarding API Documentation
  5. e-Sign
  6. Push Notifications
  7. New Fee Code
  8. Postman Examples
  9. Credit Check
  10. Contractual Documentation
Important: This Release Note supersedes all Previews.

1. Registration

We have improved the experience of our eBoarding API registration and sign in UI for individuals making an application. A tooltip is available to guide our customers on our rules for creating a secure password.

Passwords must contain

  • At least 8 characters
  • At least 3 types of character from:
    • 0 to 9 (digits)
    • a to z (lowercase letters)
    • A to Z (uppercase letters)
    • ! # $ & * (special characters)

2. eBoarding API URL Fields

Our URL input fields are increased from 128 characters to 512 characters.

3. Guided Flow Updates

We have improved our Guided Flow including:

  • Simplifying the texts on the Account Creation page.
  • Ability to upload one or more supporting documents.
  • Enabling our Contact Us information to update dynamically:
    • When Sales Agent’s information is included in the createDocumentPacket API call, then Contact Us content includes their contact information.
    • When not, the customer is referred to their Review Application email.

4. eBoarding API Documentation

  • For Self boarding applications, and when eBoarding API applications are completed with our assistance, the generation and retrieval of documents is now unified within FileNet’s Document_Storage table.
  • When using eBoarding API to upload documents, partners now have the option to give them meaningful names.
    • When a custom name is not provided, a default meaningful name is given. For example, merchant_agreement.png.
    • Supporting documents will be named by default as, supporting_document.[MIME TYPE]. For example, supporting_document.jpg.
  • Partners using the eBoarding API can now choose and assign a category to uploaded documents, or leave documents in the default category of ‘Boarding’.
  • In our eBoarding API Managed and Guided flows, our partners can now co-brand the following web-pages by uploading a logo image from the Admin Console:

Table 1. Pages that can be co-branded.

Flow

Pages Available to Brand

Guided Flow
  • Account Creation
  • Login
  • Reset Password
  • App Selector
  • Application Complete Status

Managed Flow
  • Review Agreement
  • Application Complete Status

5. e-Sign

We’ve made a number of minor improvements to our eSign flow including preserving the font-family used for customers’ electronic signatures throughout document processing.

6. Push Notifications

Partners using our eBoarding API can now choose to receive push notifications via OAuth2 authentication.

7. New Fee Code

The following Fee Type Code is now available to the Global eBoarding API lookup tables:

  • KEY: TP2
  • VALUE: TPV MONTHLY FEE 299

8. Postman Examples

Our Partners can now play with our eBoarding API examples using Postman for the:

  • Guided flow
  • Stateful flow

Postman examples will be published here shortly. In the meantime, please ask your Elavon representative for access.

9. Credit Check

For our partners using a Guided or Managed eBoarding API application flow, when re-submitting an application the Credit Check is no longer repeated unless the:

  • Application data has changed or,
  • Credit check token has expired.

10. Contractual Documentation

10.1 Denmark

EU (Denmark) eBoarding API generates the following documents for partners and customers to sign when needed:

  • Merchant Agreement
  • American Express (AMEX) Agreement
  • Poynt Addendum

10.2 Finland

EU (Finland) eBoarding API generates the following documents for partners and customers to sign when needed:

  • Merchant Agreement
  • American Express (AMEX) Agreement
  • Poynt Addendum

10.3 Germany

Our EU eBoarding API now supports the local German debit scheme girocard.

EU (Germany) eBoarding API generates the following documents for partners and customers to sign when needed:

  • Merchant Agreement
  • American Express (AMEX) Agreement
  • Elavon Tokenization Terms of Service (ToS)
  • Poynt Addendum

10.4 Ireland

EU (Ireland) eBoarding API now generates the following documents for partners and customers to sign when needed:

  • Merchant Agreement
  • American Express (AMEX) Agreement
  • Converge Addendum
  • EPG Addendum
  • Poynt Addendum
  • Talech Addendum

10.5 Sweden

EU (Sweden) eBoarding API generates the following documents for partners and customers to sign when needed:

  • Merchant Agreement
  • American Express (AMEX) Agreement
  • Direct Debit Mandate
  • Poynt Addendum

 

Back to Top

 

❮ Back to Release Notes