DEVELOPER PORTAL PRODUCT OVERVIEW
-Hosted Payments Page
-Lightbox
-Checkout.js
-XML
Test Cards
Converge Elavon Test Host Pre-Programmed Responses (see attached file)
B2 EMV Test Cards
Converge Endpoints
Endpoint to post session token request -transaction_token is an endpoint to send POST commands requesting a Session Token (ssl_txn_auth_token). This is done via a server-to-server call in order to keep your API credentials (ssl_merchant_id, ssl_user_id, ssl_pin, ssl_vendor_id, and ssl_partner_app_id) inaccessible to the cardholder.
Demo Endpoint: https://api.demo.convergepay.com/hosted-payments/transaction_token
Production Endpoint: https://api.convergepay.com/hosted-payments/transaction_token
Lightbox - This creates a pop-up screen (payment modal / iFrame), where the cardholder enters their details directly into a screen that Elavon served to the cardholder's browser. It bypasses the merchant's website, which results in lower PCI compliance requirements but has limited customizability for changing the way the payment modal appears.
Demo Endpoint: https://api.demo.convergepay.com/hosted-payments/PayWithConverge.js
Production Endpoint: https://api.convergepay.com/hosted-payments/PayWithConverge.js
Checkout.js -is the source (src) script file for Checkout.js functions. This gets included on your website in order to utilize Elavon's code for directing the card payment data to Elavon's servers (bypassing your own). Highly customizable for how the payment page appears, as you create your own payment page.
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) -similar to Lightbox, except it redierects from the merchants website to Elavon's Converge HPP. Limited customizability and low PCI compliance requirement
Demo Endpoint: https://api.demo.convergepay.com/hosted-payments/
Production Endpoint: https://api.convergepay.com/hosted-payments/
XML API -Server to server call so does not require a session token. This means it is not cardholder facing. Typically this is used for admin functions (void, refunds, etc...) or sales that utilize a card token (ssl_token). As long as you never use card data through this method, then you will have low PCI compliance requirement. If you do see / use full card data, then you will need to provide an AoC.
Demo Endpoint: https://api.demo.convergepay.com/VirtualMerchantDemo/processxml.do
Production Endpoint: https://api.convergepay.com/VirtualMerchant/processxml.do
Converge User Interface Login
Demo User Interface Login
Production / Live Account User Interface Login
Terminal Semi Integration - To release the TSI API specification, we will first need an Elavon signed NDA. Please reach out to us to request this.