Feb 2021 Release Notes

The release on February 11, 2021 includes:

Global Experience Updates

  1. Fusion Pay now supports fee type, PCI Basic Fee.

  2. Global Lookup Table
    The following codes have been added to the global lookup table:

    • Desk 1500
    • D5ECA w/PP1500
  3. Multiple e-signers
    When using Managed or Guided API flows, you can now collect one or more business owner signatures.

The Guided flow also supports functionality for both single and grouped (multi-location) applications.

  1. Resolved Issues
    Updates have been made to correct:
    • An intermittent issue with the signing status in Guided flow.
    • CorrelationId failing in WebSphere.
    • An error in the customer e-Sign page.
    • Tiers missing Pricing Control validation.
    • Signing customers with an Extended Legal Name.

North America (NA) Updates

  1. PCI Program Changes


This update was originally required for all non-Scoop NA Partners before April 1, 2021 and is now DELAYED.

Elavon is modifying the PCI Security Program method by adding an additional Security Program option named PCI Plus.

The implementation date and details will be notified in good time to make the required changes.

  1. Updated Partner Source ID (REQUIRED)


The following updates are REQUIRED for all NA eBoarding API Partners.

This advance notice outlines the technical updates required for API changes rescheduled to commence on April 11, 2021.

We will issue a new and unique client ID value to each Partner integrated with our eBoarding API.

The new client ID identifies the applications you submit using the eBoarding API and improves our support capability.

Important Dates

  • You can make the changes immediately.
  • All changes must be completed by March 31, 2021.
  • Implementation is required starting April 1, 2021.


  1. Receive your new and unique client ID.

  2. Replace the existing clientId value (“IDNA”) with your new and unique client ID in each of the following API operations:

    • appendgroupdocumentpacket
    • updatedocumentpacket
    • boardstatus
    • createdocumentpacket
    • board
    • uploadDocuments

    For example, if the issued clientId is, “MYNEWID” then for each operation:

    1. Delete the clientId value, “IDNA”.
    2. Insert the issued clientId value, “MYNEWID”.


For support, please contact your Elavon Relationship Manager.

  1. NA Lookup Tables
    M70PP has been added to the NA lookup table.

  2. Electronic Check Service (ECS) Update

Following this release, EnCircle will no longer be an ECS provider option. If you use the ECS option, then you should ensure you use the PAYA option by setting the EcsInfo serviceProviderType to PAYA.

  1. Resolved Issues
    A fix has been made for uploaded documents not appearing on the NA Group applications status page.

Europe (EU) Updates

  1. Boarding European Non-Domestic Merchants
    Our API now enables Partners operating cross-border and inside Europe to generate and present contractual documentation (in English) for e-signing of merchants who:

    • Operate in non-domestic markets.
    • Use EURO currency.


Successful boarding may rely on additional factors. Consult with your Elavon Relationship Manager when you want to make changes.

Domestic markets include:

  • Denmark
  • Finland
  • Germany
  • Ireland
  • Norway
  • Poland
  • Sweden
  • United Kingdom

Only countries in scope are eligible for EU eBoarding at this time.

Countries in ScopeCountries out of Scope
European non-domestic countries that use EUR as currency:European countries where Elavon doesn’t do business or countries that don’t use EUR currency:
CyprusCzech Republic
LatviaIsle of Man
  1. Mandatory Change Notification: SFTP Document Uploads


For compliance reasons, support for using SFTP to upload documents will stop on April 1, 2021.

All Partners currently using SFTP to upload documents must be ready to instead use eBoarding’s uploadDocuments API by March 31, 2021.

Using the API, the flow is:

  1. /creditCheck
  2. /board
  3. /uploadDocuments

The uploadDocuments request is described in the eBoarding API Reference. Complete instructions have been issued where needed.

For support, please contact your Relationship Manager.