Skip to content

Payment gateway configuration


Payment gateway is part of order process used for transferring the actual payment to outside provider that is responsible for completing the payment transaction based on given context. Every payment method must be associated with payment gateway and configuration is based on payment gateway that it uses. Virto Commerece comes with many gateways already setup that use iCharge payment integrator module. For more information visit

Supported gateways

The first thing you must do is select one (or more) of the many gateways supported, and set up an account with that gateway vendor. Once you have an account set up with a valid (or test) login Id and password, you can use that configuration and setup payment method in management tool. Below is the list of supported gateway:

Authorize.Net AIM(1)
eProcessing Transparent Databse Engine(3)
GoRealTime (Full-pass) (4)
Intellipay ExpertLink (6)
iTransact RediCharge HTML (8)
NetBilling DirectMode(9)
Verisign PayFlow Pro (10)
USA ePay CGI Transaction Gateway(13)
Plug 'n Pay (14)
Planet Payment iPay(15)
MPCS (16)
RTWare (17)
ECX (18)
Bank of America eStores (Form Post)(19)
Innovative Gateway (PHP)(20)
Merchant Anywhere (Transaction Central) (21)
SkipJack (22)
ECHOnline NVP API(23)
3 Delta Systems (3DSI) EC-Linx(24)
TrustCommerce API(25)
PSIGate XML(26)
PayFuse XML(27)
PayFlowLink (28)
Paymentech Orbital Gateway V4.3(29)
LinkPoint (30)
Moneris eSelect Plus Canada(31)
uSight Gateway Post-Auth(32)
Fast Transact VeloCT (Direct Mode)(33)
NetworkMerchants Direct-Post API(34)
Ogone DirectLink(35)
Concord EFSNet (36) (Depreciated, use LinkPoint)
TransFirst Transaction Central Classic (formerly PRIGate) (37)
Protx (38) (Depreciated, use SagePay (67) instead)
Optimal Payments / FirePay Direct Payment Protocol (39)
Merchant Partners (Transaction Engine) (40)
CyberCash (41)
First Data Global Gateway (Linkpoint) (42)
YourPay (43) (Depreciated, use Linkpoint (42) instead)
ACH Payments AGI (44)
Payments Gateway AGI(45)
Cyber Source SOAP API (46)
eWay XML API (Australia) (47)
goEmerchant XML(48)
TransFirst eLink(50)
Chase Merchant Services (Linkpoint) (51)
PSIGate XML Interface (52)
Thompson Merchant Services NexCommerce (iTransact mode) (53)
WorldPay Select Junior Invisible (54)
TransFirst Transaction Central (55) (This is different from TransFirst eLink, supported above. The TransactionCentral gateway is also used by MerchantAnywhere and PRIGate)
Paygea (56)
Sterling SPOT API (HTTPS POST)(57)
PayJunction Trinity Gateway (58)
SECPay (United Kingdom) API Solution(59)
Payment Express PXPost (60)
Elavon/NOVA/My Virtual Merchant (61)
Sage Payment Solutions (Bankcard HTTPS Post protocol)(62)
SecurePay (Script API/COM Object Interface) (63)
Moneris eSelect Plus USA (64)
Beanstream Process Transaction API(65)
Verifi Direct-Post API(66)
SagePay Direct (Previously Protx) (67)
Merchant E-Solutions Payment Gateway (Trident API)(68)
PayLeap Web Services API (69) (Previously SECPay) API Solution (70)
Worldpay XML (Direct/Invisible) (71)
ProPay Merchant Services API (72)
Intuit QuickBooks Merchant Services (QBMS) (73)
Heartland POS Gateway (74)
Litle Online Gateway (75)
BrainTree DirectPost (Server-to-Server) Gateway (76)
JetPay Gateway (77)
Sterling XML Gateway (78)
Landmark Flat File HTTPS Post (79)
BluePay 2.0 Post (81)
Adyen API Payments (82)
Barclay XML API (83)
PayTrace Payment Gateway (84)
YKC Gateway (85)
Cyberbit Gateway (86)
GoToBilling Gateway (87)
TransNational Bankcard (88)
Netbanx (89)
MIT (90)
DataCash (91)
ACH Federal (92)
Global Iris (HSBC) (93)

Configuring payment method

The tutorial assumes that you already have account to one of the gateway providers. As an example will be used in this tutorial.

To create new payment method do the following steps:

  • Open management tool and login with user that has permissions to manage payments
  • Go to Settings/Payments and click add
  • Fill in Name, description and select the gateway you want for that payment method to use
  • Check Active and click next button

  • Add localizations for payment method display name if needed and continue
  • In the final page you have to configure selected gateway (assuming you have selected Authorize.Net)
  • Fill in Extra security key for Authorize.Net's AIM (3.1) protocol. or leave empty if not configured with
    • This gateway has a unique security feature. To use it, you must add the secret hash value provided by the Authorize.Net merchant web interface.В If no hash secret is supplied in the config method, the hash value returned by the server will NOT be checked.
  • Fill in Merchant's Gateway login (API Login ID) and Merchant's Gateway password (Transaction Key)
  • The field "Default URL for a specific Gateway" should only be changed to override default gateway used by iCharge. For example testing authorize.Net you should provide ""
  • Check "Identifies if transaction is in test mode" only when testing gateway. Otherwise leave it unchecked. In test mode no real transaction are made.

All information for configuring specific gateway can be found here

Last update: June 18, 2020