ICharge Gateway Setup and Required Properties

This page contains the available methods, properties, and additional setup information for each gateway.

3DSI EC-Linx (gw3DSI)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

MerchantLogin corresponds to the 3DSI field "MerchId" and MerchantPassword corresponds to "Pwd". You will need to add the "UserId" field with the value supplied from 3DSI using AddSpecialField. The TransactionId property is required for all transactions. Captures of previous auth-only transactions must have the same TransactionId as the original authorization. The Credit method is used for both credits and voids, and the TransactionId must be different than the original authorization. (The TransactionId from the original authorization should be passed in the Credit's TransactionId parameter).

5th Dimension Logistics (gw5thDimension)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The MerchantLogin property corresponds to the 5th Dimension field "mkey".

ACH Federal (gwACHFederal)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

ACH Payments (gwACHPayments)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Adyen (gwAdyen)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The MerchantLogin property maps to the Webservice User, and the password is the password given to that user. These values are accessible from the Adyen's online management console (located at https://ca-live.adyen.com/ or https://ca-test.adyen.com/). You must also set the "TerminalId" configuration setting with the name of your merchant account. Note that this gateway does not make a distinction between Sales and Authorization-Only transactions in the API. Instead, the management console has global settings that control when captures are made. (In other words; you can make only sale transactions, or only auth-only transactions. You cannot send both). You may need to set the "CurrencyCode" config depending on your locale.

Authorize.NET AIM (gwAuthorizeNet)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

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 to the "HashSecret" configuration setting (via 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; Config("HashSecret=myhashvalue"). If no hash secret is supplied in the config method, the hash value returned by the server will NOT be checked.

Authorize.NET AIM XML (gwAuthorizeNetXML)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

This gateways implements the Authorize.NET's Advanced Integration Method (AIM) XML API.

Authorize.NET CIM (gwAuthorizeNet)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway performs transactions using customer profiles stored via Authorize.NET's Customer Information Manager (CIM). Therefore ID's will be used instead of payment, billing, and shipping information. The ID's are specified via the following configs: "AuthNetCIMProfileId", "AuthNetCIMPaymentProfileId", and "AuthNetCIMShippingProfileId".

Note: Customer profiles can be managed via the RecurringBilling component.

Bank Of America (gwBankOfAmerica)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The "HashSecret" configuration setting is required by this gateway as an Hmac calculation must be computed and sent in the Authorization header of the request. "HashSecret" must be set to the Hmac Key generated for you by the gateway. Note the component handles the computation of the Hmac.

The FullName is also required to be specified and an exception will be thrown if not set.

AuthCode is used to perform tagged transactions (transactions that do not require the Card data to be specified). The value to specify within AuthCode is the value contained within ApprovalCode after a successful authorization. This transactions are only applicable for Capture, VoidTransaction, and Refund transactions.

Barclay (gwBarclay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The "UserId" configuration setting is required to be set.

Beanstream (gwBeanstream)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount can represented as either cents without a decimal point or dollars and cents with a decimal point. For example, a value of "100" would equate to "$1.00" while a value of "100.00" would equate to "$100.00" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

You must set a "username" and "password" in the merchant interface, and add them to the component via the AddSpecialField method if you wish to use any transaction other than Sale.

Bluefin (gwBluefin)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

BluePay (gwBluePay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

BrainTree (gwBrainTree)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Chase (gwChase)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Your MerchantLogin will be the "Store Number" provided by Linkpoint. This gateway requires a client certificate, which can be set using the SSL Certificate fields. Void transactions with this gateway require a transaction timestamp. This timestamp can be retrieved from the original AuthOnly response through the GetResponseVar; method. Example:

icharge.AuthOnly(); 
String tdate = icharge.GetResponseVar("/root/r_tdate");

This value can be set for the VoidTransaction with the AddSpecialField method. Example:

icharge.AddSpecialField("tdate","YourDate");
icharge.VoidTransaction("TransactionId");

Converge (gwConverge)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

The "ssl_merchant_id" provided by Elavon is your MerchantLogin, and "ssl_merchant_pin" is your MerchantPassword. If provided with an "ssl_user_id", set the "MyVirtualMerchantUserId" configuration setting via the Config method.

Cyber Cash (gwCyberCash)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Cyberbit (gwCyberbit)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

CyberSource (gwCyberSource)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Data Cash (gwDataCash)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

InvoiceNumber is required for all transactions and must be between 6 and 30 digits in length.

DataCash provides two methods of voiding transactions. The default method for voiding a transaction is by calling VoidTransaction using the TransactionId. DataCash also allows you to void transactions based on the InvoiceNumber (note that your account must be set up to use reference based cancellations).

ECX (gwECX)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

This gateway requires the same setup as the Authorize.Net (1) gateway.

eProcessing (gwEprocessing)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Accounts with this gateway may be configured to require an additional shared secret for stronger authentication. This is called the "RestrictKey". If this is configured for your account you may add this value using the AddSpecialField method like so:

retail.AddSpecialField("RestrictKey", "yFqqXJh9Pqnugfr");

Eway (gwEway)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Your MerchantLogin will be the eWay Customer Id, and the MerchantPassword is only required for performing refunds.

ExPay (gwExPay)

Supported Methods:

AuthOnly

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Your MerchantLogin will be the Payee ID Key.

The "HashSecret" configuration setting is required by this gateway as an Hmac calculation must be computed and sent in the request. "HashSecret" must be set to the Payee Secret Key provided by the gateway. Note the component handles the computation of the Hmac.

The "ExPayGetMethods" and "ExPayGetStatus" configuration settings are available to perform additional requests not directly available via the component methods.

In addition to the GetResponseVar; method, the "X***" configuration settings are available to help navigate the JSON response. Below is an example of parsing a "GetMethods" response.

ICharge1.Config("XPath=/json/response/methods");
String count = ICharge1.Config("XChildrenCount"); // Returns the number of methods, i.e. 3
ICharge1.Config("XPath=/json/response/methods/[1]"); // XPath Indexes are 1-based
String name = ICharge1.Config("XChildrenName[0]"); // Array indexes are 0-based.  i.e. name = "id"
String value = ICharge1.Config("XChildrenXText[0]"); // Array indexes are 0-based.  i.e. value = "77"

Fast Transact (gwFastTransact)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

First Atlantic Commerce (gwFirstAtlantic)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires the use of a unique InvoiceNumber. AuthOnly and Sale transactions must have a new unique value. All subsequent transactions (Capture, Refund, or VoidTransaction) must use the same InvoiceNumber used in the initial authorization.

Note: VoidTransaction is used to perform a reversal for this gateway and TransactionAmount is used to specify the reversal amount.

First Data (gwFirstData)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

icharge.AuthOnly(); 
String tdate = icharge.GetResponseVar("/root/r_tdate");

This value can be set for the VoidTransaction with the AddSpecialField method. Example:

icharge.AddSpecialField("tdate","YourDate");
icharge.VoidTransaction("TransactionId");

First Data E4 (gwFirstDataE4)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The "FDMSKeyId" configuration setting is also required by this gateway. This configuration setting is used to specify the Key Id, obtained from FDMS, that corresponds to the HMAC Key (specified via HashSecret) and is sent within the Authorization header of the request.

The FullName is also required to be specified and an exception will be thrown if not set.

First Data PayPoint (gwFirstDataPayPoint)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Global Iris (gwGlobalIris)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The Global Iris gateway does not use a password, but rather requires a SHA-1 hash using a secret key. The secret key assigned to you will be specified via MerchantPassword and the component will compute the SHA-1 hash. Global Iris Refund transactions require a refund password in addition to MerchantPassword. This password can be specified using GlobalIrisRefundPassword.

InvoiceNumber is required for all transactions and must be between 1 and 40 digits in length.

Global Iris only supports the following credit card types: Visa, MasterCard, American Express, and Maestro. Any other card type will be rejected by the server (Setting the card number to a card outside of these ranges will cause an error).

Global Payroll (gwGlobalPayroll)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

A ClientId must also be set for this gateway via the AddSpecialField method.

ICharge1.AddSpecialField("ClientID", "1009");

Our implementation supports Global Payroll Tokenization via the "GlobalPayrollToken" configuration setting (it is not required that you use tokenization). To process a transaction using a token, set "GlobalPayrollToken" configuration setting to the token obtained by calling the "GlobalPayrollCreateToken" action config. Tokenization can not be used to Capture or Refund a transaction.

GoEMerchant (gwGoEMerchant)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

GoToBilling (gwGoToBilling)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Id is a required field.

Heartland (gwHeartland)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires you set the following configuration settings with the values supplied by Heartland: "HeartlandLicenseId", "HeartlandSiteId", and "HeartlandDeviceId". In addition, you may optionally set the "HeartlandSiteTrace", "HeartlandDeveloperId", and "HeartlandVersionNumber" configuration settings for this gateway.

Our implementation supports Heartland's Tokenization implementation via the "HeartlandTokenMapping" and "HeartlandTokenValue" configuration settings (it is not required that you use tokenization). Note: Heartland's Tokenization implementation requires that your merchant account is properly configured to support tokenization. In addition to the account configurations, there are special pricing considerations for merchants in the production environment. Therefore merchants who wish to use tokenization should contact their Relationship Manager for more details and to configure their account appropriately.

HSBC (gwHSBC)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

The user's "Name" maps to MerchantLogin, and "password" maps to MerchantPassword.

Note: The TestMode property can be overridden by using the AddSpecialField method to add the "Mode" field.

ICharge1.AddSpecialField("Mode", "Y");

Innovative (gwInnovative)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Intellipay (gwIntellipay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Intuit Payment Solutions (gwIntuitPaymentSolutions)

(formerly known as ECHOnline)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Refund transactions require two special fields, "original_amount" and "order_number", to be added to the request. "original_amount" is the amount originally authorized transaction that is now being refunded. "order_number" is the order number returned in the response of the original authorization. Below is some sample code demonstrating how to add these special fields:

ICharge1.AddSpecialField("original_amount", "1.00");
ICharge1.AddSpecialField("order_number", ICharge1.GetResponseVar("/ECHOTYPE3/order_number"));

ITransact (gwITransact)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

JetPay XML (gwJetPay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

MerchantLogin must be set to the "TerminalId" JetPay field.

TransactionId is required for Sale, AuthOnly, Credit and Force transactions.

AuthCode is required when performing VoidTransaction transactions.

LinkPoint (gwLinkPoint)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

icharge.AuthOnly(); 
String tdate = icharge.GetResponseVar("/root/r_tdate");

This value can be set for the VoidTransaction with the AddSpecialField method. Example:

icharge.AddSpecialField("tdate","YourDate");
icharge.VoidTransaction("TransactionId");

Litle (gwLitle)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway uses the TransactionDesc property to place transactions in different categories. If TransactionDesc is left blank the transaction will fail.

This gateway also requires you set the "MerchantCode" configuration setting with the Merchant Id supplied to you by Litle.

Merchant Anywhere (gwMerchantAnywhere)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Use the "RegKey" provided by MerchantAnywhere as your MerchantPassword.

Merchant E-Solutions (gwMerchantESolutions)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Merchant Partners (gwMerchantPartners)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Note: To send encrypted card data, the "ValidateCardNumber" configuration setting must be set to 'False' prior to setting the Card data (using either the Number of the MagneticStripe property). You will also need to set the "MerchantPartnersReaderType" configuration setting the value corresponding to the card reader being used.

MIT (gwMIT)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "MXN".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

In addition to your merchant login and password, the MIT Gateway also requires the following configs to be specified: "MerchantCode", "MITCompanyId", "MITBranchId", "MITCountry", and "MITTPOperation".

When performing a Refund transaction, AuthCode is required to be set to the value returned in the ApprovalCode obtained from the response of the original authorization.

Moneris Canada (gwMoneris)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

InvoiceNumber is required for all transactions.

Moneris USA (gwMonerisUSA)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

InvoiceNumber is required for all transactions.

Monetra (gwMonetra)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway implementation is using the test environment URL by default. When moving to production please set the GatewayURL property to point to the production server.

Note: Automatic settlement must be activated on the gateway portal.

MPCS (gwMPCS)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

This gateway requires the same setup as the Authorize.Net (1) gateway.

My Virtual Merchant (gwMyVirtualMerchant)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Netbanx (gwNetbanx)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

In addition to your merchant login and password, the Netbanx Gateway also requires an additional "accountNum" field, which must be added using "NetbanxAccountNumber" config.

InvoiceNumber is required for all transactions.

NetBilling (gwNetBilling)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Network Merchants (gwNetworkMerchants)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

NexCommerce (gwNexCommerce)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Ogone (gwOgone)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The "UserId" configuration setting is required to be set.

Orbital (gwOrbital)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

To configure this gateway please note that your merchant/group Id is your MerchantLogin, and your Bank Id (BIN) will be your MerchantPassword (which specifies to use the Salem or Tampa [PNS] platform). The Terminal Id is defaulted to "001" (but can be changed via in Config).

Pay Direct (gwPayDirect)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires PayDirectSettleMerchantCode to be set as it is used in authorization.

In addition to TransactionAmount the amount details are required to be set using PayDirectConvenienceFee and PayDirectMerchantAmount. If these fields are not set, the component will internally set the fields. Please see the config definitions for further details.

Payeezy Gateway (gwPayeezy)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The FullName is also required to be specified and an exception will be thrown if not set.

Pay Junction (gwPayJunction)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Pay Leap (gwPayLeap)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

This gateway requires the FullName field.

Pay Point (gwPayPoint)

Supported Methods:

Sale

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Rather, this gateway supports the 'test_status' SpecialField which allows values of 'true' (simulate authorized transaction), 'false' (simulated declined transaction), or 'live' (send transaction to the bank for authorization).

This gateway supports the use of the Freedom API via the PayPointFreedomAPI.

The supported methods for the Freedom API are:

For the Capture, Refund, and VoidTransaction methods, you must specify your 'remote_pswd' via a SpecialField.

Note: the AuthOnly transaction performs a deferred transaction in which an authorization takes place and funds in the cardholders account are frozen pending release but the money will not be debited. In order for these frozen funds to be released you will need to call Capture. Alternatively you can call VoidTransaction to mark a deferred transaction as cancelled (this only marks the transaction as cancelled on the PayPoint.net system and doesn't send a request to the bank to remove the authorization).

PayFlow Link (gwPayFlowLink)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

PayFlow Pro (gwPayFlowPro)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

The default "Partner" special field is set to "PayPal". You may be required to change it depending on your account setup. If your User Id and Vendor Id (Merchant Login Id) are different, supply the Vendor Id to MerchantLogin and add the User Id like so: AddSpecialField("USER","User Id Value").

PayFuse (gwPayFuse)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

The user's "Name" maps to MerchantLogin, and "password" maps to MerchantPassword.

Note: The TestMode property can be overridden by using the AddSpecialField method to add the "Mode" field.

ICharge1.AddSpecialField("Mode", "Y");

Payment Express (gwPaymentExpress)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Payment WorkSuite [3DSI] (gwPaymentWorkSuite)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USDollars".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Note: The Payment WorkSuite gateway verifies AVS address and zip code data individually. Therefore the AVSResult will contain both results separated by a '/' (i.e. [AddressAVS]/[ZipCodeAVS]). For example if the address matched but the zip code did not match, AVSResult will return: Matched/NotMatched.

Payments Gateway (gwPaymentsGateway)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Payscape (gwPayscape)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

PayTrace (gwPayTrace)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Payvision (gwPayvision)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires that you set a unique InvoiceNumber for each request made (AuthOnly, Capture, Void, etc.).

After successful authorizations, the "PayvisionTransactionGuid" configuration will be populated along with the response properties. This configuration setting is also required to be specified, using the value obtained from the authorization, when performing subsequent transactions (such as Capture, Refund, Force, and VoidTransaction).

PayWiser (gwPayWiser)

Supported Methods:

MerchantLogin and TransactionDesc are required properties.

MerchantPassword is not applicable.

TerminalID and DynamicDescriptor configuration settings are required for PayWiser Gateway.

BuyerIP and TerminalIP fields are required and must be sent via the AddSpecialField method. For example:

icharge.AddSpecialField("BuyerIP", "1.1.1.1");
icharge.AddSpecialField("TerminalIP", "2.2.2.2");

Other optional fields like Surcharge and CashBack (valid only for Sale) can also be set by calling AddSpecialField.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "EUR".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires the use of a unique TransactionId.

After a successful Sale, the PayWiserReserveReferenceId and PayWiserCaptureReferenceId configuration settings will be populated along with the response properties. If PayWiserTokenizeCard is set to True, PayWiserTokenReferenceId will also be populated after a successful Sale.

A card token or a token reference id can be used to authorize a credit card. A card token can be obtained via the RecurringBilling component by setting the PayWiserRequestType configuration setting to 1.

PhoeniXGate (gwPhoeniXGate)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not available for this gateway.

TestMode is supported and when set to "True", test transactions can be sent using a live account that will not be captured and settled.

Other fields can also be set by calling AddSpecialField.

This Gateway does not have a test URL. Transactions will be processed using the production server.

This gateway performs transactions using customer profiles. Therefore Id's will be used instead of credit card information. To process transactions using customer profiles, "PhoeniXGateProcessRecurringCredit" configuration setting must be set to True. Also "PhoeniXGateCardInfoKey" must be set to the Credit Card Info Key obtained from RecurringBilling component at the time the payment record was created, and "MerchantCode" configuration setting must be set to the Merchant ID which is also known as Merchant Number or RPNum.

Our implementation supports PhoeniXGate Tokenization implementation via the "PhoeniXGateTokenMode" and "PhoeniXGateToken" configuration settings (it is not required that you use tokenization). To process a transaction using a token, set "PhoeniXGateProcessTokenCredit" configuration setting to True. Tokenization can not be used to Capture or Refund a transaction.

Note: A token can be obtained from RecurringBilling component

Planet Payment (gwPlanetPayment)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "840".

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires you to set the "TerminalId" configuration setting. MerchantLogin maps to the company KEY, and MerchantPassword maps to the PIN.

PlugNPay (gwPlugNPay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

PRIGate (gwPRIGate)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Use the "RegKey" provided by PRIGate as your MerchantPassword.

ProPay XML (gwProPay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

PSIGate HTML (gwPSIGate)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

PSIGate XML (gwPSIGateXML)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

Note when performing a VoidTransaction, InvoiceNumber is required to be set to the value returned within ResponseInvoiceNumber of the original transaction that is being voided.

QuickBooks Merchant Services (gwQBMS)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

For the QBMS gateway, your App Login is used for the MerchantLogin, and the Connection Ticket for the MerchantPassword. (Using the Application Id in the MerchantLogin property will cause an error).

TransactionId is required for all transactions.

Repay (gwRepay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not available for this gateway.

TestMode is supported and when set to "True", test transactions can be sent using a live account that will not be captured and settled.

Other fields can also be set by calling AddSpecialField.

This Gateway does not have a test URL. Transactions will be processed using the production server.

This gateway performs transactions using customer profiles. Therefore Id's will be used instead of credit card information. To process transactions using customer profiles, "RepayProcessRecurringCredit" configuration setting must be set to True. Also "RepayCardInfoKey" must be set to the Credit Card Info Key obtained from RecurringBilling component at the time the payment record was created, and "MerchantCode" configuration setting must be set to the Merchant ID which is also known as Merchant Number or RPNum.

Our implementation supports Repay Tokenization implementation via the "RepayTokenMode" and "RepayToken" configuration settings (it is not required that you use tokenization). To process a transaction using a token, set "RepayProcessTokenCredit" configuration setting to True. Tokenization can not be used to Capture or Refund a transaction.

Note: A token can be obtained from RecurringBilling component

RTWare (gwRTWare)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

This gateway requires the same setup as the Authorize.Net (1) gateway.

Sage Payments (gwSagePayments)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

SagePay (gwSagePay)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

"RelatedSecurityKey" and "RelatedVendorTXCode" special fields are required for Refunds. These are parsed out of the original authorization response. "SecurityKey" and AuthCode are required for voids and captures.

SEC Pay (gwSECPay)

Supported Methods:

Sale

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway supports the use of the Freedom API via the PayPointFreedomAPI.

The supported methods for the Freedom API are:

For the Capture, Refund, and VoidTransaction methods, you must specify your 'remote_pswd' via a SpecialField.

Secure Payments (gwSecurePay)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Skipjack (gwSkipjack)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The "CurrencyCode" configuration setting is not applicable.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

This gateway requires you to set the "TerminalId" configuration setting as developer serial number for Void and Refund transactions.

Sterling XML (gwSterling)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

MerchantLogin must be set to the "SECURENETID" field of the Sterling XML gateway.

Additionally, TransactionId is required for all transactions.

Transaction Central (gwTransactionCentral)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Use the "RegKey" provided by Transaction Central as your MerchantPassword.

TransFirst (gwTransFirst)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

TransNational Bankcard (gwTransNationalBankcard)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Trust Commerce (gwTrustCommerce)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is not applicable.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

USAePay (gwUSAePay)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

USight (gwUSight)

This gateway is no longer in service.

Verifi (gwVerifi)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

WorldPay Select Junior (gwWorldPay)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

You may set the "MerchantCode" configuration setting, if you wish to send a merchant code that is different than your merchant login.

WorldPay US Link (gwWorldPayLink)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is available for this gateway. This field is only sent if a value is explicitly specified.

TestMode is not supported and when set to "True" an exception will be thrown by the component.

WorldPay XML (gwWorldPayXML)

Supported Methods:

MerchantLogin and MerchantPassword are required properties.

The TransactionAmount is required to be represented as cents without a decimal point. For example, a dollar value of "1.00" would equate to "100" for this gateway.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

WorldPay requires you to set the "TerminalId" configuration setting with the Installation Id provided to you by Worldpay. In addition, the Customer.Country and TransactionDesc are required fields.

YKC (gwYKC)

Supported Methods:

Sale

MerchantLogin is a required property. MerchantPassword is not applicable.

The "CurrencyCode" configuration setting is available for this gateway. The default value is "USD".

TestMode is not supported and when set to "True" an exception will be thrown by the component.

Note: Most merchants using YKC will need to set the "CurrencyCode" config to "JPY" for Japanese yen.

Your Pay (gwYourPay)

Supported Methods:

MerchantLogin is a required property. MerchantPassword is not applicable.

The TransactionAmount is required to be represented as cents with a decimal point. For example, "1.00".

The "CurrencyCode" configuration setting is not applicable.

This gateway supports sending ThreeDSecure (3DS) verification data by setting the following configs: CAVV, XID, ECI.

TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.

icharge.AuthOnly(); 
String tdate = icharge.GetResponseVar("/root/r_tdate");

This value can be set for the VoidTransaction with the AddSpecialField method. Example:

icharge.AddSpecialField("tdate","YourDate");
icharge.VoidTransaction("TransactionId");