Elavon EPG ACH

Elavon EPG ACH token payments support charging stored ACH bank accounts vaulted against shopper profiles. Transactions are submitted to the Elavon Payment Gateway REST API using stored ACH payment tokens.

Features

✅ Payment Sale Payments are authorized and immediately captured using Token payment methods.

Resources

Configuration

To obtain API credentials, contact Converge Software Support at 1-800-377-3962 and request API credentials for Authvia. Configure an Elavon CRM shopper and tokenize a stored ACH payment before running charges.

This table describes the required or possible attributes needed to configure a merchant product for this type.

Name	Type	Description	Rules
host	string	(required) The Elavon Converge API host. Use the UAT host for testing. Examples: uat.api.converge.eu.elavonaws.com, api.converge.eu.elavonaws.com.
basicAuth	object	(required) API Key and Secret Key used for Basic authentication. Examples: [object Object].

Enabling this Product

Using create-merchant-product API you can add a new product to your merchant record. Below is an example configuration for the payload of that request.

{
  "line": "payments",
  "product": "token",
  "provider": "elavon-epg-ach",
  "config": {
    "host": "api.converge.eu.elavonaws.com",
    "basicAuth": {
        "username": "your_api_key_here",
        "password": "sk_your_secret_key_here"
    }
},
  
}

Data Mapping

The following bullet points outline the mapping of data fields between the Authvia platform and the Elavon EPG ACH system, detailing the correspondence of specific attributes for seamless data integration.

Authvia transaction.references.external maps to Elavon EPG ACH UNMAPPED
Authvia transaction.id maps to Elavon EPG ACH UNMAPPED
Authvia transaction.description maps to Elavon EPG ACH UNMAPPED
Authvia customer.externalIds.elavon-epg maps to Elavon EPG ACH shopper
Authvia transaction.paymentMethod.token maps to Elavon EPG ACH storedAchPayment
Authvia merchant.id maps to Elavon EPG ACH UNMAPPED