Elavon Converge

How to enable Elavon Converge Paze on a merchant.

Elavon Converge supports both card and ACH payments, now including refund capabilities. Key features include account setup without CVV2 requirement, E-commerce Transaction ID setup, and customizable payment fields for specialized transactions.

Features

Refund A paze payment processed with Elavon Converge can be / according to its status. ✅ Payment Authorization Payments can be authorized by customers using Paze. ✅ Payment Capture Payment authorizations made using Paze payment methods can be captured. This step happens automatically with CHARGE transactions.

Resources

Configuration

To obtain your API User credentials, call Software Support at Elavon at 1-800-377-3962 and request API User credentials for Authvia. Alternatively, you can email [email protected] directly to handle your setup needs.

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

NameTypeDescriptionRules
merchant_idstring(required) Merchant Id for the Elavon. Examples: your_merchant_id_here.
user_idstring(required) User Id for the Elavon. Examples: your_user_id_here.
pinstring(required) PIN for the Elavon. Examples: your_pin_here.
clientIdstring(required) Client Id for the Paze.
profileIdstring(required) Profile Id for the Paze. Examples: your_profile_id_here.
namestring(required) Name for the Paze. Examples: your_name_here.

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": "paze",
  "provider": "elavon-converge",
  "config": {
    "merchant_id": "your_merchant_id_here",
    "user_id": "your_user_id_here",
    "pin": "your_pin_here",
    "profileId": "your_profile_id_here",
    "name": "your_name_here"
  }
}

Data Mapping

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

  • Authvia transaction.reference.external maps to Elavon Converge ssl_invoice_number
  • Authvia transaction.id maps to Elavon Converge UNMAPPED
  • Authvia transaction.description maps to Elavon Converge ssl_description
  • Authvia transaction.userId maps to Elavon Converge ssl_customer_code
  • Authvia merchant.id maps to Elavon Converge UNMAPPED