Converge API endpoints, test cards and developer links

On this page

Where is the Elavon developer portal?

Elavon’s developer portal has the full documentation for each product. Start with the developer portal product overview.

• Converge API, which has four integration methods:
  • Hosted Payments Page
  • Lightbox
  • Checkout.js
  • XML
• Commerce SDK (CSDK)
• Fusebox
  • Simplify

What are the Converge API endpoints?

Each Converge API method below has a demo endpoint and a production endpoint.

Session token request (transaction_token)

Send a POST to transaction_token to request a session token (ssl_txn_auth_token). Make this call server to server, so your API credentials (ssl_merchant_id, ssl_user_id, ssl_pin, ssl_vendor_id and ssl_partner_app_id) stay out of the cardholder’s reach.

• Demo endpoint: https://api.demo.convergepay.com/hosted-payments/transaction_token
• Production endpoint: https://api.convergepay.com/hosted-payments/transaction_token

Lightbox

Lightbox opens a payment pop-up (a payment modal / iFrame) that Elavon serves to the cardholder’s browser. The cardholder types their card details into Elavon’s screen, not your website, which lowers your PCI compliance requirements. How the payment pop-up looks can only be customized to a limited extent.

• Demo endpoint: https://api.demo.convergepay.com/hosted-payments/PayWithConverge.js
• Production endpoint: https://api.convergepay.com/hosted-payments/PayWithConverge.js

Checkout.js

Checkout.js is the script (src) file you include on your website. You build your own payment page, and Elavon’s code sends the card data to Elavon’s servers instead of yours. You control how the page looks.

• Demo endpoint: https://api.demo.convergepay.com/hosted-payments/Checkout.js
• Production endpoint: https://api.convergepay.com/hosted-payments/Checkout.js

Hosted Payment Page (HPP)

The HPP works like Lightbox, except the cardholder is redirected from your website to Elavon’s Converge hosted payment page. Customization is limited and the PCI compliance requirement is low.

• Demo endpoint: https://api.demo.convergepay.com/hosted-payments/
• Production endpoint: https://api.convergepay.com/hosted-payments/

XML API

The XML API is a server-to-server call, so it doesn’t need a session token and isn’t cardholder facing. It’s typically used for admin functions (voids, refunds and so on) or for sales that use a card token (ssl_token). If you never send card data through it, your PCI compliance requirement stays low. If you do see or use full card data, you will need to provide an AoC (Attestation of Compliance).

• Demo endpoint: https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do
• Production endpoint: https://api.convergepay.com/VirtualMerchant/processxml.do

Where can I find Converge test cards?

• Converge Test Cards
• Converge Elavon Test Host Pre-Programmed Responses: pre-programmed responses (PDF)
• B2 EMV Test Cards

Where do I log in to Converge?

• Demo User Interface Login
• Production / Live Account User Interface Login

For Converge help articles from Elavon, see the Converge Support Page.

How do I get the Terminal Semi-Integration (TSI) specification?

To release the TSI API specification, we first need an Elavon signed NDA. Reach out to Cartis support to request this: 1-888-712-0770 or support@cartispayments.com.