Gateway Property
Gateway to process transactions.
Data Type
EnumerationPossible Values
No Gateway (0)Authorize Net (1)
Eprocessing (2)
Intellipay (3)
ITransact (4)
Net Billing (5)
Pay Flow Pro (6)
USAe Pay (7)
Plug NPay (8)
Planet Payment (9)
MPCS (10)
RTWare (11)
ECX (12)
Bank Of America (13)
Innovative (14)
Merchant Anywhere (15)
Skipjack (16)
Intuit Payment Solutions (17)
3DSI (18)
Trust Commerce (19)
PSIGate (20)
Pay Fuse (21)
Pay Flow Link (22)
Orbital (23)
Link Point (24)
Moneris (25)
USight (26)
Fast Transact (27)
Network Merchants (28)
Ogone (29)
PRIGate (30)
Merchant Partners (31)
Cyber Cash (32)
First Data (33)
Your Pay (34)
ACHPayments (35)
Payments Gateway (36)
Cyber Source (37)
Eway (38)
Go EMerchant (39)
Trans First (40)
Chase (41)
Nex Commerce (42)
World Pay (43)
Transaction Central (44)
Sterling (45)
Pay Junction (46)
SECPay (47)
Payment Express (48)
My Virtual Merchant (49)
Sage Payments (50)
Secure Pay (51)
Moneris USA (52)
Beanstream (53)
Verifi (54)
Sage Pay (55)
Merchant ESolutions (56)
Pay Leap (57)
Pay Point (58)
World Pay XML (59)
Pro Pay (60)
QBMS (61)
Heartland (62)
Litle (63)
Brain Tree (64)
Jet Pay (65)
HSBC (66)
Blue Pay (67)
Adyen (68)
Barclay (69)
Pay Trace (70)
YKC (71)
Cyberbit (72)
Go To Billing (73)
Trans National Bankcard (74)
Netbanx (75)
MIT (76)
Data Cash (77)
ACHFederal (78)
Global Iris (79)
First Data E4 (80)
Default Value
0Remarks
The following table shows the currently supported gateways, as well as the corporate home page for each.
| Gateway | Home page |
| No Gateway | n/a |
| Authorize.Net | http://www.authorize.net |
| DPI Link | This gateway is no longer in service. |
| eProcessing | http://www.eProcessingNetwork.com |
| GoRealTime (Full-pass) | http://www.gorealtime.com |
| IBill Processing Plus | http://www.ibill.com |
| Intellipay ExpertLink | http://www.intellipay.com |
| Iongate | This gateway is no longer in service. |
| iTransact RediCharge HTML | http://www.itransact.com |
| NetBilling | http://www.netbilling.com |
| Verisign PayFlow Pro | http://www.verisign.com |
| Payready Link | This gateway is no longer in service. |
| NOVA's Viaklix | http://www.viaklix.com |
| USA ePay | http://www.usaepay.com |
| Plug 'n Pay | http://www.plugnpay.com |
| Planet Payment | http://planetpayment.com/ |
| MPCS | http://merchantcommerce.net/ |
| RTWare | http://www.rtware.net/ |
| ECX | http://www.ecx.com |
| Bank of America | http://bankofamerica.com/merchantservices |
| Innovative Gateway | http://www.innovativegateway.com |
| Merchant Anywhere (Transaction Central) | http://www.merchantanywhere.com/ |
| SkipJack | http://www.skipjack.com |
| ECHOnline | http://www.echo-inc.com |
| 3 Delta Systems (3DSI) EC-Linx | http://www.3dsi.com |
| TrustCommerce | http://www.trustcommerce.com |
| PSIGate | http://www.psigate.com |
| PayFuse XML | http://www.firstnationalmerchants.com/ |
| PayFlowLink | http://www.verisign.com |
| Paymentech Orbital Gateway | http://www.paymentech.com |
| LinkPoint | http://www.linkpoint.com |
| Moneris eSelect Plus | http://www.moneris.com |
| uSight Gateway | http://gateway.usight.com |
| Fast Transact | http://www.fasttransact.com/ |
| NetworkMerchants | http://www.networkmerchants.com/ |
| Ogone DirectLink | http://www.ogone.be |
| Concord EFSNet | http://www.concordefsnet.com/ |
| Payment Resources International PRIGate | http://www.paymentresource.com/TransactionCentral.asp |
| Protx | http://www.protx.com |
| Optimal Payments / FirePay | http://www.optimalpayments.com/ |
| Merchant Partners | http://www.merchantpartners.com/ |
| CyberCash | http://www.cybercash.net/ |
| FirstData / CardService International | http://www.firstdata.com |
| YourPay | http://www.yourpay.com |
| ACH Payments | http://www.ach-payments.com |
| Payments Gateway | https://www.paymentsgateway.net/ |
| Cyber Source | http://www.cybersource.com |
| eWay (Australia) | http://www.eway.com.au/ |
| goEmerchant XML | http://www.goemerchant.com/ |
| PayStream (Australia) | http://www.paystream.com.au |
| TransFirst eLink | http://www.transfirst.com |
| Chase Merchant Services | http://www.chase.com |
| PSIGate XML Interface | http://www.psigate.com |
| NexCommerce | http://www.thompsonmerchant.com |
| WorldPay Select Junior Invisible | http://www.worldpay.com |
All of the supported gateways have certain properties that must be set in order to successfully complete a transaction. Generally, the following properties must be set for every gateway:
| Number | |
| ExpMonth | |
| ExpYear | |
| Address | |
| City | |
| State | |
| Zip | |
| FirstName | |
| LastName | |
| FullName | |
| MerchantLogin | |
| MerchantPassword (where required) | |
| TransactionAmount |
Please note that some gateways may also support non-AVS transactions, where customer name and address data is not required. However, these transactions are risky and are not recommended for fraud reasons. When a transaction is authorized, the status of the response will be indicated by the TransactionApproved property. For more details as to why a transaction was authorized or declined, it is recommended that the developer check the ResponseCode and ResponseText properties.
Please see the ResponseCode property for a list of specific response codes for each gateway. Please see the TransactionType property for a list of transaction types supported by each gateway.
In addition to the properties listed above, some gateways require that a few more properties be set. These gateways and properties are listed below. Please note that there are several Authorize.Net compatible gateways which are not listed below. Please see the GatewayURL property for more information.
| Gateway | Properties required |
| gwNoGateway (0) | (none) |
| gwAuthorizeNet (1) | This gateway requires special configuration due to the extra security measures implemented in the 3.1 (AIM) protocol. You will need to add your Transaction Key ("x_Tran_Key") value via the SpecialFields property. Note that your API Login ID maps to MerchantLogin. You must also add the secret hash value with the Config method. Both of these values are provided by the Authorize.Net merchant web interface, which is used to set up your account. For example; AddSpecialField("x_Tran_Key", "mytranskey"), and Config("AIMHashSecret=myhashvalue"). If no hash secret is supplied in the config method, the hash value returned by the server will NOT be checked. Note: You may add the special field "X_Test_Request" with the value "True" to send test transactions. |
| gwDPI (2) | This gateway is no longer in service. gwTransFirst replaces the DPI gateway. |
| gwEprocessing (3) | (none) |
| gwGoRealTime (4) | |
| gwIBill (5) | (none) |
| gwIntellipay (6) | InvoiceNumber |
| gwIOnGate (7) | This gateway is no longer in service. |
| gwITransact (8) | Country, Phone, Email |
| gwNetBilling (9) | InvoiceNumber |
| gwPayFlowPro (10) | TransactionId must be unique for each transaction. Note, the default "Partner" special field is set to "VeriSign". You may be required to change it (using SpecialFields) depending on your account setup. |
| gwPayReady (11) | This gateway is no longer in service. |
| gwViaKlix (12) | InvoiceNumber If given an ssl_user_id by ViaKlix/Nova, set it via the SpecialFields property. Please note that ssl_merchant_id maps to the MerchantLogin property and ssl_merchant_pin maps to the MerchantPassword property. Test transactions can be sent by setting the test mode with AddSpecialField ("ssl_test_mode", "true"). |
| gwUSAePay (13) | (none) |
| gwPlugNPay (14) | (none) |
| gwPlanetPayment (15) | This gateway requires the same setup as the Authorize.Net gateway. |
| gwMPCS (16) | This gateway requires the same setup as the Authorize.Net gateway. |
| gwRTWare (17) | This gateway requires the same setup as the Authorize.Net gateway. |
| gwECX (18) | This gateway requires the same setup as the Authorize.Net gateway. |
| gwBankOfAmerica (19) | This gateway requires special configuration. First, you will need to add the name that appears on the credit card via the SpecialFields property. You must also set the HTTP Referer header to one of the URLs that you allow in your Bank of America store security settings. For example, AddSpecialField("ecom_payment_card_name", "John A. Smith"), and Config("referer=http://www.mydomain.com/"). |
| gwInnovative (20) | This gateway supports an optional test flag by adding the special field: adapter.AddSpecialField ("test_override_errors", "true"). TransactionAmount is required for voids, and must match the amount from the original authorization. |
| gwMerchantAnywhere (21) | This gateway requires the same setup as the TransactionCentral gateway. |
| gwSkipjack (22) | Email, Phone |
| gwECHOnline (23) | Phone |
| gw3DSI (24) | TransactionId The TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. |
| gwTrustCommerce (25) | The TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. |
| gwPSIGate (26) | (none) |
| gwPayFuse (27) | The Config setting "MerchantAlias" is required. The TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. The TransactionId property must be explicitly set before the initial authorization, and that value must be used to modify that transaction rather than the value returned in the ResponseTransactionId property. The "PayFuseTestMode" Config setting can be used for testing. |
| gwPayFlowLink (28) | Id, Phone, Email InvoiceNumber |
| gwOrbital (29) | InvoiceNumber. The TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. Also, to configure this gateway please note that your merchant/group Id maps to the MerchantLogin property, and your Bank Id (BIN) maps to the MerchantPassword property. The Terminal Id is defaulted to "001" (but can be changed via Config). |
| gwLinkPoint (30) | The LinkPoint "ConfigFile" maps to the MerchantLogin property; This gateway requires a client certificate, which can be set using the SSLCert property. |
| gwMoneris (31) | The Response Method of the DirectPost configuration must be set to "Displayed as key/value pairs on our server" in the merchant admin. |
| gwUSight (32) | (none) |
| gwFastTransact VeloCT(33) | You may want to set the ValidateCardNumber configuration setting to false if you're using recurring billing and need to send alphanumeric data in the Number property. |
| gwNetworkMerchants (34) | (none) |
| gwOgone (35) | InvoiceNumber The TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. |
| gwEFSNet (36) | InvoiceNumber. |
| gwPRIGate (37) | This gateway requires the same setup as the TransactionCentral gateway. |
| gwProtx (38) | InvoiceNumber. The fields "RelatedSecurityKey", "RelatedVendorTxCode", and "RelatedTxAuthNo" must be added via SpecialFields before using a TransactionType of Credit. After a successful authorization, the value to put in the "RelatedSecurityKey" field should be parsed from the SecurityKey value found in the ResponseData, and the values for RelatedVendorTxCode and RelatedTxAuthNo should be retrieved from the InvoiceNumber and ResponseApprovalCode properties respectively. For a TransactionType of Void or Capture, you must add the fields "SecurityKey","VendorTxCode", and "TxAuthNo" instead. |
| gwOptimal (39) | In addition to the MerchantLogin (your "merchant Id") and MerchantPassword, Optimal also requires you to set an additional "account" property via the SpecialFields property. The fields "settleNumber" and "origMerchantTxn" must be added via the SpecialFields property before using a TransactionType of Credit. "settleNumber" is also required for a TransactionType of Void. The field "origMerchantTxn" corresponds to the InvoiceNumber from the original authorization. The "settleNumber" must be manually parsed from the ResponseData after a successful transaction with TransactionType of Capture. Finally, the TransactionAmount must be submitted as the number of cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway. |
| gwMerchantPartners (40) | (none) |
| gwCyberCash (41) | This gateway requires the same setup as the PayFlowLink gateway. |
| gwFirstData (42) | This gateway requires the same setup as the LinkPoint gateway. |
| gwYourPay (43) | This gateway requires the same setup as the LinkPoint gateway. |
| gwACHPayments (44) | (none) |
| gwPaymentsGateway (45) | This gateway requires the same setup as the ACHPayments gateway. |
| gwCyberSource (46) | Email, InvoiceNumber. AuthCode is required for Force transactions. MerchantPassword should be set to the SOAP API Transaction Key generated for your merchant account. |
| gwEway (47) | See note below. |
| gwGoEMerchant (48) | Country |
| gwPayStream (49) | For this gateway, you will receive a "MerchantID", "CustomerID", "ZoneID", and "Username" from PayStream. The "MerchantID" field corresponds to the MerchantLogin property. The remaining fields must be added to the request via the SpecialFields property. Also, the InvoiceNumber is a required property for this gateway, and must be unique for each transaction. |
| gwTransFirst (50) | InvoiceNumber |
| gwChase (51) | This gateway requires the same setup as the LinkPoint gateway. |
| gwPSIGateXML (52) | Normally none. However AuthCode is required for Force transactions. |
| gwNexCommerce (53) | This gateway requires the same setup as the gwITransact gateway. |
| gwWorldPay (54) | InvoiceNumber and Country are required properties. You may also wish to change the "currency" special field to the currency you support. It is defaulted to "USD" (see the SpecialFields property for more information). If the "testmode" Special Field is added with the value "100", all transactions will be accepted. If set to "101" all transactions will be declined. If no "testmode" is set, the transactions are live. |
| gwTransactionCentral (55) | The MerchantLogin should be set to your MerchantID. The MerchantPassword should be set to the RegKey provided by Transaction Central. InvoiceNumber is required for Sale transactions. See note below. |
| gwPaygea (56) | The MerchantLogin property should contain the Merchant Email address used to identify you to Paygea. Additional required properties include: InvoiceNumber, Id, and Country. In addition, some configurations may require the "sps_ipaddress" special field, which should contain the customer's IP address. Note: The "sps_cardname" special field contains the customer's name as printed on the credit card. "sps_cardname" is not supplied, it will be constructed from the FirstName and LastName properties. |
| gwSterling (57) | InvoiceNumber. Setting the special field "s_test" to "TRUE" will mark the transaction as a test transaction. |
| gwPayJunction (58) | (none) |
| gwSecPay (59) | (none) |
| gwPaymentExpress (60) | (none) Test transactions may be sent to a live account by adding a "TestMode" special field, and setting it to "1". For example, AddSpecialField("TestMode", "1"). Note that the casing is important for this gateway. |
| gwMyVirtualMerchant (61) | InvoiceNumber If given an ssl_user_id by Nova, set it via the SpecialFields property. Please note that ssl_merchant_id maps to the MerchantLogin property and ssl_merchant_pin maps to the MerchantPassword property. Test transactions can be sent by setting the test mode with AddSpecialField ("ssl_test_mode", "true"). Note that Capture transactions require the special field "ssl_approval_code", which should contain the ResponseApprovalCode returned in the original AuthOnly response. Note when attempting to perform authorizations without supplying a value to CVVData you may need to set the special fields "ssl_cvv2cvc2_indicator" and "ssl_cvv2cvc2". A value of 9 for "ssl_cvv2cvc2_indicator" indicates Not Present. For Visa cards you would set "ssl_cvv2cvc2_indicator" to 9 and "ssl_cvv2cvc2" to empty string. This is not done automatically by the component because of differences in the way card types are processed. This gives the developer the option of what to set here. |
| gwSagePayments (62) | (none) |
| gwSecurePay (63) | (none) |
| gwMonerisUSA (64) | The Response Method of the DirectPost configuration must be set to "Displayed as key/value pairs on our server" in the merchant admin. |
Note: The EWay gateway does note support TransactionTypes like the other gateways do. Instead, eWay defines different GatewayURLs for each of the actions they support. The following table shows all of the supported actions for the eWay Gateway.
| GatewayURL | Description |
| https://www.eway.com.au/gateway/xmlpayment.asp | Sale transactions without CVVData. |
| https://www.eway.com.au/gateway_cvn/xmlpayment.asp | Sale transactions with CVVData. |
| https://www.eway.com.au/gateway/xmlstored.asp | Authorization Only transactions without CVVData. |
| https://www.eway.com.au/gateway/xmltest/TestPage.asp | Test transactions without CVVData. |
| https://www.eway.com.au/gateway_cvn/xmltest/TestPage.asp | Test transactions with CVVData |