ECheck Gateway Setup and Required Properties
This page contains the available methods, properties, and additional setup information for each gateway.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, CheckNumber
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".
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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.
Additional check-relevant properties supported are:
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.
This gateway also requires that the "shopperIP" field be added via AddSpecialField method..
You may need to set the "CurrencyCode" config depending on your locale.
Authorize.NET (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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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.
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".
Additional check-relevant properties supported are: CheckNumber
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".
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, TaxId, CheckNumber
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");
CyberSource (gwCyberSource)
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
Fast Transact (gwFastTransact)
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, TaxId
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are:
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 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.
Additional check-relevant properties supported are: CheckNumber
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 Customer's Name or the CompanyName must be set. If not, an error will occur.
Heartland (gwHeartland)
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.
Additional check-relevant properties supported are:
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.
Additional check-relevant properties supported are: CheckNumber
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");
Intuit Payment Solutions (gwIntuitPaymentSolutions)
(formerly known as ECHOnline)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.
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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".
Additional check-relevant properties supported are: CheckNumber
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.
Additional check-relevant properties supported are: CheckNumber
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.
InvoiceNumber is required for all 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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, TaxId, CheckNumber
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");
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.
Additional check-relevant properties supported are: CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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 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".
Additional check-relevant properties supported are: LicenseNumber, TaxId, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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.
BankName and CheckNumber are both required for all transactions.
NetBilling (gwNetBilling)
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId
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 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.
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are: CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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.
Additional check-relevant properties supported are: CheckNumber
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. 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".
Additional check-relevant properties supported are: CheckNumber
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.
Pay Flow 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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseDOB, TaxId, CheckNumber
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.
Additional check-relevant properties supported are: CheckNumber
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");
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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 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.
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are:
TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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.
For Government Checks, set "PhoeniXGateGovernmentCheck" configuration setting to True.
This Gateway does not have a test URL. Transactions will be processed using the production server.
To process Recurring Billing Checks, "PhoeniXGateProcessRecurringCheck" configuration setting must be set to True. Also "PhoeniXGateCheckInfoKey" must be set to the Check 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.
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".
Additional check-relevant properties supported are: CheckNumber
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".
Additional check-relevant properties supported are: CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
For the QBMS gateway, your Application Name 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 Gateway (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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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.
For Government Checks, set "RepayGovernmentCheck" configuration setting to True.
This Gateway does not have a test URL. Transactions will be processed using the production server.
To process Recurring Billing Checks, "RepayProcessRecurringCheck" configuration setting must be set to True. Also "RepayCheckInfoKey" must be set to the Check 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.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, LicenseDOB, TaxId, CheckNumber
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 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.
Additional check-relevant properties supported are:
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.
Additional check-relevant properties supported are:
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, CheckNumber
TestMode is supported and when set to "True" test transactions can be sent using a live account that will not be captured and settled.
Verifi (gwVerifi)
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.
Additional check-relevant properties supported are:
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: LicenseNumber, TaxId, CheckNumber
TestMode is not supported and when set to "True" an exception will be thrown by the component.
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".
Additional check-relevant properties supported are: LicenseNumber, LicenseState, TaxId, CheckNumber
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");