E-Payment Integrator 2022 .NET Edition
Version 22.0 [Build 8593]

ICharge Component

Properties   Methods   Events   Config Settings   Errors  

The ICharge component is used to authorize credit card transactions with any of the supported Internet Payment Gateways.

Syntax

DPayments.InPay.Icharge

Remarks

The ICharge component allows you to use multiple Internet Payment Gateways through one interface and one component. This allows for easy migration from one gateway to another, as well as quick integration into applications or web services.

The ICharge component allows your website to securely perform credit card transactions without the need to redirect to a third-party site. All transactions are accomplished through a secure HTTPS Post to any supported gateway. The secure response is received and then stored in the component's response properties. Any web site on a standard HTTP server or any stand-alone application can process transactions without the need for a secure server or third-party intervention.

The first thing you must do is select one of the many gateways supported by the ICharge component, and set up an account with that gateway vendor. Once you have an account set up with a valid (or test) login Id and password, you can use the ICharge component.

To begin, set the Gateway property to the gateway you wish to use. If this gateway supports an alternate URL to send test transactions to, set the GatewayURL at this time.

Next, set the MerchantLogin (and for some gateways the MerchantPassword). These are supplied by your gateway vendor when you set up an account.

Now you are ready to process transactions. For each transaction, you must set the Number, ExpMonth, ExpYear, and TransactionAmount properties. Most gateways will also require additional properties, such as Address, FirstName, LastName, InvoiceNumber, etc. Any additional required properties are listed in the Gateway property description.

Once these properties are set, you may run validity checks on the card data with the AVSOnly method, or simply authorize the transaction with the Sale method. If your Gateway supports it, you may also Void transactions that have not yet gone to settlement with the VoidTransaction method. Transactions that have already been settled may be refunded with the Credit method. Please note that some gateways use the Credit method for both voids and credits. See the transaction methods for more information.

The following gateways are supported by the ICharge component:

GatewayHome page
No Gateway (0) n/a
Authorize.Net AIM (1)http://www.authorize.net
eProcessing Transparent Database Engine (2)http://www.eProcessingNetwork.com
Intellipay ExpertLink (3)http://www.intellipay.com
iTransact RediCharge HTML (4)http://www.itransact.com
NetBilling DirectMode (5)http://www.netbilling.com
PayFlow Pro (6)https://www.paypal.com/webapps/mpp/payflow-payment-gateway
USA ePay CGI Transaction Gateway (7)http://www.usaepay.com
Plug 'n Pay (8)http://www.plugnpay.com
Planet Payment iPay (9)http://planetpayment.com/
MPCS (10)http://merchantcommerce.net/
RTWare (11)http://www.rtware.net/
ECX (12)http://www.ecx.com
Bank of America (Global Gateway e4) (13)http://bankofamerica.com/merchantservices
Innovative Gateway (PHP) (14)http://www.innovativegateway.com
Merchant Anywhere (Transaction Central Classic) (15)http://www.merchantanywhere.com/
SkipJack (16)http://www.skipjack.com
3 Delta Systems (3DSI) EC-Linx (18)http://www.3dsi.com
TrustCommerce API (19)http://www.trustcommerce.com
PSIGate HTML (20)http://www.psigate.com
PayFuse XML (ClearCommerce Engine) (21)http://www.firstnationalmerchants.com/
PayFlow Link (22)https://www.paypal.com/webapps/mpp/payflow-payment-gateway
Chase Paymentech Orbital Gateway (23)https://merchantservices.chase.com/
LinkPoint (24)http://www.linkpoint.com
Moneris eSelect Plus Canada (25)http://www.moneris.com
uSight Gateway Post-Auth (26)This gateway is no longer in service.
Fast Transact VeloCT (Direct Mode) (27)http://www.fasttransact.com/
NetworkMerchants Direct-Post API (28)http://www.nmi.com/
Ingenico DirectLink / Ogone (29)https://www.ingenico.be/
TransFirst Transaction Central Classic (formerly PRIGate) (30)http://www.transfirst.com
Merchant Partners (Transaction Engine) (31)http://www.merchantpartners.com/
CyberCash (32)https://www.paypal.com/cybercash
First Data Global Gateway (Linkpoint) (33)http://www.firstdata.com
YourPay (Linkpoint) (34) http://www.yourpay.com
ACH Payments AGI (35)http://www.ach-payments.com
Forte AGI / Payments Gateway AGI(36)https://www.forte.net/
Cyber Source SOAP API (37)http://www.cybersource.com
eWay XML API (Australia) (38)http://www.eway.com.au/
goEmerchant XML (39)http://www.goemerchant.com/
TransFirst eLink (40)http://www.transfirst.com
Chase Merchant Services (Linkpoint) (41)http://www.chase.com
Thompson Merchant Services NexCommerce (iTransact mode) (42)http://www.thompsonmerchant.com
WorldPay Select Junior Invisible (43)http://www.worldpay.com
TransFirst Transaction Central Classic (44)http://www.transfirst.com. (This is different from TransFirst eLink, supported above. The TransactionCentral gateway is also used by MerchantAnywhere and PRIGate)
Sterling SPOT XML API (HTTPS POST) (45)http://www.sterlingpayment.com
PayJunction Trinity Gateway (46)http://www.payjunction.com
SECPay (United Kingdom) API Solution(47)http://www.secpay.com
Payment Express PXPost (48)http://www.paymentexpress.com
Elavon/NOVA/My Virtual Merchant (49)https://support.convergepay.com/s/
Sage Payment Solutions (Bankcard HTTPS Post protocol) (50)http://www.sagepayments.com
SecurePay (Script API/COM Object Interface) (51)http://securepay.com
Moneris eSelect Plus USA (52)http://www.moneris.com
Bambora / Beanstream Process Transaction API (53)https://www.bambora.com/en/ca/
Verifi Direct-Post API (54)http://www.verifi.com
SagePay Direct (Previously Protx) (55)https://www.opayo.uk/
Merchant E-Solutions Payment Gateway (Trident API) (56)http://merchante-solutions.com/
PayLeap Web Services API (57)http://www.payleap.com
PayPoint.net (Previously SECPay) API Solution (58)http://paypoint.net
Worldpay XML (Direct/Invisible) (59)http://www.worldpay.com
ProPay Merchant Services API (60)http://www.propay.com
Intuit QuickBooks Merchant Services (QBMS) (61)This gateway is no longer in service. It has been replaced by Quickbooks Payments (113).
Heartland POS Gateway (62)http://www.heartlandpaymentsystems.com/
Litle / Vantiv Online Gateway (63)http://www.litle.com/
BrainTree DirectPost (Server-to-Server Orange) Gateway (64)http://www.braintreepaymentsolutions.com/
JetPay Gateway (65)http://www.jetpay.com/
HSBC XML API (ClearCommerce Engine) (66)https://www.business.hsbc.uk/en-gb/payments/business-card
BluePay 2.0 Post (67)http://www.bluepay.com
Adyen API Payments (68)http://www.adyen.com
Barclay ePDQ (DirectLink) (69)http://www.barclaycard.co.uk/business/
PayTrace Payment Gateway (70)https://www.paytrace.net/
YKC Gateway (71)http://www.ykc-bos.co.jp/
OmniFund HTTP API / GoToBilling(73)http://omnifund.com/
TransNational Bankcard (74)http://www.tnbci.com/
Netbanx (75)http://www.netbanx.com/
MIT (76)http://www.centrodepagos.com.mx
DataCash (77)http://www.datacash.com/
ACH Federal (78)http://www.achfederal.com/
Global Iris (HSBC) (79)https://www.globalpaymentsinc.com/en-gb
First Data Global Gateway E4 (80)http://www.firstdata.com
First Atlantic Commerce (81)http://www.firstatlanticcommerce.com/
Bluefin (82)http://www.bluefin.com/
Payscape (83)http://www.payscape.com
Pay Direct (Link2Gov) (84)https://www.fisglobal.com/solutions/other/government/
Authorize.NET CIM (85)http://www.authorize.net
5th Dimension Logistics (86)http://www.5thdl.com/
WorldPay US Link Gateway (87)https://www.worldpay.com/en-us/index
3DSI Payment WorkSuite (88)http://www.3dsi.com/
PSIGate XML (89)http://www.psigate.com
First Data PayPoint (90)https://www.firstdata.com/en_us/products/financial_institutions.html
ExPay Gateway (91)http://www.expay.asia
Payvision Gateway (92)http://www.payvision.com/
Converge (formerly MyVirtualMerchant) (93)https://support.convergepay.com/s/
Payeezy Gateway (formerly First Data E4) (94)https://developer.payeezy.com/
Monetra Gateway (95)http://www.monetra.com
Authorize.NET XML (96)http://www.authorize.net/
PhoeniXGate Gateway (97)http://www.phoenixmanagednetworks.com/
Repay Gateway (98)https://www.repay.com/
Global Payroll Gateway (99)https://www.gpgway.com/
PayWiser Gateway (100)https://paywiser.eu/
Veritas Gateway (101)http://www.veritaspay.com/
Stripe Gateway (102)http://www.stripe.com/
KartePay Gateway (103)https://www.kartepay.com/
BlueSnap Gateway (104)https://home.bluesnap.com/
American Payment Solutions (105)https://www.apspayments.com/
BASYS Gateway (106)https://basyspro.com/
Worldpay Online (107)https://www.worldpay.com
Square (108)https://www.squareup.com
Priority Payment Systems (109)https://prioritypaymentsystems.com
Nuvei / GlobalOnePay (110)https://nuvei.com/en-us/
CardPointe (111)https://cardconnect.com/cardpointe
Metrobank (112)https://www.metrobankcard.com/
Quickbooks Payments (113)https://quickbooks.intuit.com/payments/
Shift4 (114)https://www.shift4.com/
Square Payments (115)https://squareup.com/us/en
Heartland Portico Gateway (116)http://www.heartlandpaymentsystems.com/
PayTrace Payment Gateway JSON (117)https://www.paytrace.net/

Property List


The following is the full list of the properties of the component with short descriptions. Click on the links for further details.

AuthCodeAuthorization code from a previous transaction.
CardContains the customer's credit card information.
CustomerContains the customer's name, address, and other identifying information.
GatewayGateway to process transactions with.
GatewayURLDefault URL for a specific Gateway .
InvoiceNumberMerchant-generated invoice number.
Level2AggregateThe level 2 aggregate containing the data to be sent in the request.
Level3AggregateThe level 3 aggregate containing the data to be sent in the request.
MerchantLoginMerchant's Gateway login.
MerchantPasswordMerchant's Gateway password.
ProxyThis property includes a set of properties related to proxy access.
ResponseContains the response to the authorization.
ShippingInfoContains the customer's shipping name, address, and other identifying information.
SpecialFieldsA list of additional fields to send in the request.
SSLAcceptServerCertInstructs the component to unconditionally accept the server certificate that matches the supplied certificate.
SSLCertThe certificate to be used during SSL negotiation.
SSLProviderThis specifies the SSL/TLS implementation to use.
SSLServerCertThe server certificate for the last established connection.
TestModeTurns test mode on and off for transactions sent to the current Gateway .
TimeoutA timeout for the component.
TransactionAmountPurchase amount for an authorization transaction.
TransactionDescDescription of goods purchased.
TransactionIdMerchant-generated transaction Id used for all transactions.

Method List


The following is the full list of the methods of the component with short descriptions. Click on the links for further details.

AddSpecialFieldAdds a special field name and the corresponding value.
AuthOnlyInitiates an authorization-only request transaction.
AVSOnlyUsed to check the validity of the card without authorizing funds.
CaptureCaptures a previously authorized transaction.
ConfigSets or retrieves a configuration setting.
CreditCredits a customer's card.
DoEventsProcesses events from the internal message queue.
ForceUsed when authorization cannot be obtained online.
GetResponseVarParses additional information out of the response.
InterruptInterrupts the current action.
RefundRefunds a previously captured transaction.
ResetClears all properties to their default values.
ResetSpecialFieldsResets all special fields to the default settings.
SaleInitiates an Sale transaction (authorization and capture).
VoidTransactionVoids a previously authorized transaction.

Event List


The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.

ErrorInformation about errors during data delivery.
SSLServerAuthenticationFired after the server presents its certificate to the client.
SSLStatusShows the progress of the secure connection.

Config Settings


The following is a list of config settings for the component with short descriptions. Click on the links for further details.

3DSAuthenticationStatusIndicates whether a transaction qualifies as a ThreeDSecure (3DS) authenticated transaction.
3DSCAVVCardholder Authentication Verification Value from a 3D Secure authentication.
3DSDSTransactionIdDirectory server transaction Id from a 3D Secure authentication.
3DSECIElectronic Commerce Indicator.
3DSEnrollmentStatusIndicates whether 3D Secure authentication is available for the cardholder.
3DSXIDTransactionId from a 3D Secure authentication.
AdyenShopperInteractionSpecifies the sales channel the shopper gives their card details through.
AllowPartialAuthsSpecifies whether partial authorizations are allowed.
AmountFormatUsed to set the input format for TransactionAmount.
ApplePayDataThe Base-64 encoded data containing the encrypted payment data from Apple for use when performing Apple Pay transactions.
APSRequestTypeSpecifies the request type to use for the American Payment Solutions gateway.
AuthNetBillToCompanyThe company that should be included with the customer's information for the Authorize.NET XML gateway.
AuthNetCIMPaymentProfileIdThe Payment Profile ID assigned by Authorize.NET CIM gateway.
AuthNetCIMProfileIdThe Profile ID assigned by Authorize.NET CIM gateway.
AuthNetCIMProfileResponseProfile creation response.
AuthNetCIMShippingAddressIdThe Shipping Address ID assigned by Authorize.NET CIM gateway.
AuthNetCreateCIMProfileWhether to create a CIM Profile.
AuthNetCryptogramTokenized credit card cryptogram.
AuthNetCustomerTypeSpecifies the customer type for the Authorize.NET XML gateway.
AuthNetOpaqueDescriptorAn Authorize.Net opaque data descriptor.
AuthNetOpaqueValueAn Authorize.Net opaque data value.
AuthNetShipToCompanyThe name of the company associated with the customer's shipping address.
AuthNetSplitTenderIdAuthorize.Net assigned id for partially authorized transactions.
AuthNetTokenizedCardThe credit card token.
BamboraPasscodeThe API passcode used for authentication with Bambora.
BankNameName of the card issuer.
BarclayKeepTransactionOpenDetermines whether to perform a maintenance transaction that keeps the transaction open for further processing with the Barclay and Ingenico gateways.
BarclayPartialRefundDetermines whether to send a partial or full refund transaction with the Barclay and Ingenico gateways.
BASYSCardInfoKeyBASYS Gateway Credit Card Profile Id.
BASYSProcessRecurringCreditDetermines whether to process the transaction via Credit Card Profile Id.
BASYSProcessTokenCreditDetermines whether to process the transaction using a Credit Card Token.
BASYSTokenBASYS Gateway Credit Card Token.
BASYSTokenModeIndicates the type of token that is being used for the transaction.
BASYSVoidModeIndicates whether to perform a Void or Reversal.
BluefinReversalDetermines which transaction type will be use for VoidTransaction with the Bluefin gateway.
BluePayMasterIdUsed to reference a previous transaction in BluePay.
BluePayUpdateUsed to perform an Update transaction for BluePay.
BlueSnapEnterpriseUdfsUser-Defined Fields (UDFs) to send with a BlueSnap Sale or AuthOnly request.
BlueSnapGetTokenRetrieves a new hosted payment fields token (pfToken) from BlueSnap.
BlueSnapRetrieveTransactionRetrieves a BlueSnap transaction.
BlueSnapTransactionMetaDataTransaction metadata to send with a BlueSnap Sale or AuthOnly request.
CardholderPresentCodeSpecifies the way in which transaction took place.
CardIssueNumberSpecial Issue Number used for Switch and Solo cards.
CardLast4DigitsThe last 4 digits of a credit card.
CardPointeEncryptionHandlerThe encryption handler to use when requesting a token from CardPointe.
CardPointeGetTokenRetrieves an account token from CardPointe.
CardStartMonthUsed for some international cards.
CardStartYearUsed for some international cards.
CardTokenThe credit card token.
CAVVResponseContains CAVV response value returned by the gateway.
COFPermissionIndicates if the customer gave permission to make a Card On File transaction.
ConvenienceFeeThe total convenience fee charged for a transaction.
ConvergeTokenModeUsed to request a token from the Converge gateway.
CurrencyCodeCurrency code for the currency of the transaction.
CurrencyExponentCurrency exponent to be used in conjunction with the Currency code of the transaction.
CustomerProfileIdUsed to send a customer profile Id to a gateway.
CyberSourceAuthTokenThe request token from a previous authorization for the CyberSource gateway.
CyberSourceProfileIdThe Id of a Customer's Profile stored within the CyberSource gateway.
CyberSourceVoidModeIndicates whether to perform a Void or Reversal.
CyberSourceXMLEscapeDetermines whether to XML escape the CyberSource gateway request field values.
DataCash3DSCardholderRegisteredIndicates whether the cardholder was registered for 3D Secure for the DataCash gateway.
DataCashAuthOnlyFinalityIndicates whether an AuthOnly transaction should be treated as final for the DataCash gateway.
DataCashExtendedPolicyAggregateUsed to specify an XML aggregate for Extended Policies within the DataCash gateway.
DynamicDescriptorA merchant defined transaction description which appears on the customer's credit card statement.
EscapeXMLAutomatically escape data within XML tags.
ExPayGetMethodsUsed to send a GetMethods request to the ExPay gateway.
ExPayGetStatusUsed to send a GetStatus request to the ExPay gateway.
ExPayPaymentIdThe payment Id used to retrieve a transaction status for the ExPay gateway.
ExPayServiceIdThe Id of the service to use to perform an authorization for the ExPay gateway.
FDMSCurrentBalanceContains the current card balance value returned in a response for the First Data E4, Payeezy, and Bank Of America gateways.
FDMSGiftCardTransactionTypeSpecifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways.
FDMSKeyIdThe Key Id that corresponds to the HMAC Key for the First Data E4, Payeezy, and Bank Of America gateways.
FDMSProcessGiftCardSpecifies whether the card being processed is a gift card for the First Data E4, Payeezy, and Bank Of America gateways.
FDMSTransArmorTokenThe Transarmor token that replaces a card number and used for transaction processing.
FDMSWalletProviderIdSpecifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways.
GlobalIrisRefundPasswordThe Refund password for the Global Iris gateway.
GlobalPayrollCreateTokenSends a create token request to the Global Payroll gateway.
GlobalPayrollTokenThe token value for a corresponding card when using the Global Payroll gateway.
GoEMerchantUseGatewayIdIndicates whether to send a password or gateway Id for the GoEMerchant gateway.
HashAlgorithmAlgorithm used for hashing.
HashSecretSecurity key used to generate a hash for gateways supporting such functionality.
HeartlandDeveloperIdOptional DeveloperId field used by the Heartland gateway.
HeartlandDeviceIdDeviceId field required by the Heartland gateway.
HeartlandLicenseIdLicenseId field required by the Heartland gateway.
HeartlandReversalAmountThe settlement amount to be used when performing a reversal for the Heartland gateway.
HeartlandSecretAPIKeySpecifies the secret key to be used for authentication with Heartland.
HeartlandShipDayShip day field required by the Heartland gateway e-commerce/direct marketing transactions.
HeartlandShipMonthShip month field required by the Heartland gateway e-commerce/direct marketing transactions.
HeartlandSiteIdSiteId field required by the Heartland gateway.
HeartlandSiteTraceOptional transaction identifier for the Heartland gateway.
HeartlandTokenMappingThe type of token to return when using Tokenization with the Heartland gateway.
HeartlandTokenValueUsed to retrieve or specify a Heartland token value.
HeartlandVersionNumberOptional VersionNumber field used by the Heartland gateway.
LitleAdvancedFraudChecksIdUsed to specify the Id for use in the AdvancedFraudChecks element for the Litle gateway.
LitleCustomBillingAggregateUsed to specify an XML aggregate for Custom Billing support within the Litle gateway.
MerchantAliasAn additional merchant property used to specify an alias for the merchant.
MerchantCodeA gateway-supplied merchant number, code, or Id.
MerchantESolutionsAccountDataSourceSpecifies the source of a customer's data in an authorization request to Merchant e-Solutions.
MerchantESolutionsCardOnFileTells Merchant e-Solutions that you will be storing card information.
MerchantESolutionsMerchantInitiatedTells Merchant e-Solutions that you are performing a Merchant Initiated Transaction.
MerchantESolutionsMotoECommerceIndUsed to tell Merchant e-Solutions if a transaction is Mail Order, Telephone Order, or E-Commerce.
MerchantESolutionsTokenHolds a token representing card information stored by Merchant e-Solutions.
MerchantESolutionsTokenizeCardWhen set, will request a tokenized card from Merchant e-Solutions.
MerchantPartnersLast4DigitsThe last 4 digits of the card number for a transaction processed via the MerchantPartners gateway.
MerchantPartnersProfileIdThe profile Id to be used to process a transaction via the MerchantPartners or WorldPay Link gateways.
MetrobankLocaleSets the locale for a 3-party request to Metrobank.
MetrobankReturnURLSets the URL where a user will be redirected after a 3-party request to Metrobank.
MetrobankThreePartyRequestIndicates that the component should return data for a 3-party request to Metrobank.
MetrobankThreePartyResponseUsed to manually parse a response after a 3-Party request to Metrobank.
MetrobankVoidTypeUsed to type of transaction should be voided in a request to Metrobank.
MITAESSeedIdThe Seed Id used to perform AES encryption for the MIT gateway.
MITBranchIdBranch reference number for the MIT gateway.
MITCompanyIdCompany reference number for the MIT gateway.
MITCountryCountry of operation for the MIT gateway.
MITEncryptionAlgorithmThe Encryption Algorithm to use with the MIT gateway.
MITEncryptionKeyThe Encryption Key to use with the MIT gateway.
MITFlagFor the MIT framework - Used to indicate that a transaction is merchant initiated.
MITPriorTransIdFor the MIT framework - Used to specify a prior transaction id to be referenced in a merchant initiated transaction.
MITRecurringSpecifies whether to perform a recurring transaction request for the MIT gateway.
MITTPOperationThe operation type for the MIT gateway.
MITTypeFor the MIT framework - Indicates the type of transaction being requested in a Merchant-Initiated Transaction (MIT).
MonerisNVPAPIIndicates whether to use the NVP API for the gwMoneris and gwMonerisUSA gateway.
MyVirtualMerchantTransactionTypeUsed to override the transaction type to send in a transaction for the MyVirtualMerchant and Converge gateways.
MyVirtualMerchantUserIdThe MyVirtualMerchant user Id as configured on VirtualMerchant.
NetbanxAccountNumberAccount Number for the Netbanx gateway.
NetBillingVersionThe Version to be sent in the User-Agent heading of a NetBilling gateway request.
OrbitalAuthReversalIndicates whether to perform an authorization reversal when calling VoidTransaction for the Orbital gateway.
OrbitalConnectionPasswordOrbital Connection Password field used by the Orbital gateway.
OrbitalConnectionUsernameOrbital Connection Username field used by the Orbital gateway.
OrbitalCustomerProfileFromOrderIndCustomer Profile Number generation Options for the Orbital gateway.
OrbitalCustomerProfileIdThe Id for a customer profile in the Orbital gateway.
OrbitalCustomerProfileOrderOverrideIndIndicator to specify how the CustomerId is leveraged to populate other data sets for the Orbital gateway.
OrbitalDigitalTokenCryptogramHolds the cryptogram when making a CDPT request with Orbital.
OrbitalDPANIndicatorIndicates the type of a CDPT authorization with Orbital.
OrbitalTxRefIdxIndentifies the unique components of transactions that have been adjusted more than one time for the Orbital gateway.
OrbitalVoidAdjustedAmountSpecifies the amount to void from a previous authoization for the Orbital gateway.
PayDirectConvenienceFeeThe total convenience fee charged when using the PayDirect gateway.
PayDirectMerchantAmountThe MerchantAmount used by the PayDirect gateway.
PayDirectSettleMerchantCodeThe Settle Merchant Code required for authorization when using the PayDirect gateway.
PayerIPThe IP address of the payer.
PayFlowProInquirySubmits an Inquiry transaction to the PayFlowPro gateway.
PayFlowProTokenUsed specify a token to be used instead of card data for the Payflow Pro gateway.
PayFlowProUploadSubmits an Upload transaction to the PayFlowPro gateway.
PayJunctionUpdateAmountIndicates whether the capture method should send an update amount request when using the PayJunction gateway.
PaymentWorkSuiteClientCodeThe 3DSI assigned client code sent in a request to the PaymentWorksuite gateway.
PaymentWorkSuiteLocationCodeThe 3DSI assigned location code sent in a request to the PaymentWorksuite gateway.
PaymentWorkSuiteMerchantCodeThe 3DSI assigned merchant code sent in a request to the PaymentWorksuite gateway.
PayPointFreedomAPIIndicates whether to use the Freedom API for the gwPayPoint and gwSECPay gateways.
PayTraceAddPurchaseCardDataSends a Level3 request for the PayTrace gateway.
PayTraceIntegratorIdUsed to specify the Integrator Id value assigned by the PayTrace gateway.
PayTraceJSONCardTokenThe token value for a corresponding card.
PayTraceJSONEncryptionKeyThe Encryption Key to use with the PayTraceJSON gateway.
PayTraceJSONGetClientKeyTokenRetrieves a new Client Key (PROTECT AUTH TOKEN) from PayTrace.
PayvisionTransactionGuidThe GUID obtained with an authorization for the Payvision gateway.
PayWiserCaptureReferenceIdThe capture reference id returned by PayWiser after doing a Sale transaction.
PayWiserCardTokenThe token value for a corresponding card when using the PayWiser gateway.
PayWiserEMerchantPayDetermines whether to process the transaction via E-Merchant Pay Acquiring Bank.
PayWiserReserveReferenceIdThe reserve reference id returned by PayWiser after doing a Sale transaction.
PayWiserTokenizeCardWhether to generate a Token Reference Id.
PayWiserTokenReferenceIdThe token reference id for a corresponding card when using the PayWiser gateway.
PhoeniXGateCardInfoKeyPhoeniXGate Gateway Credit Card Profile Id.
PhoeniXGateProcessRecurringCreditDetermines whether to process the transaction via Credit Card Profile Id.
PhoeniXGateProcessTokenCreditDetermines whether to process the transaction using a Credit Card Token.
PhoeniXGateTokenPhoeniXGate Gateway Credit Card Token.
PhoeniXGateTokenModeIndicates the type of token that is being used for the transaction.
PhoeniXGateVoidModeIndicates whether to perform a Void or Reversal.
PKPaymentTokenUsed to send an Apple Pay PKPaymentToken to the gateway.
PPSPaymentTokenA Priority Payment Systems payment token.
QBMSMobileWhether or not this transaction is being sent from a mobile device.
QBPaymentsMobileWhether or not this transaction is being sent from a mobile device.
RawRequestReturns the data that was sent to the gateway.
RawResponseReturns the data that was received from the gateway.
RecurringIndicatorMarks a request as a recurring transaction.
RepayCardInfoKeyRepay Gateway Credit Card Profile Id.
RepayProcessRecurringCreditDetermines whether to process the transaction via Credit Card Profile Id.
RepayProcessTokenCreditDetermines whether to process the transaction using a Credit Card Token.
RepayTokenRepay Gateway Credit Card Token.
RepayTokenModeIndicates the type of token that is being used for the transaction.
RepayVoidModeIndicates whether to perform a Void or Reversal.
ResponseCardNumberThe card number as returned in the response from the gateway.
ResponseCardTypeThe card type as returned in the response from the gateway.
SagePayCreateTokenSends a create token request to the SagePay gateway.
SagePayRemoveTokenSends a remove token request to the SagePay gateway.
SagePayRepeatPerforms a Repeat transaction for the SagePay gateway.
SagePayRequestTokenSpecifies whether to request a token when performing an Auth or Sale when using the SagePay gateway.
SagePayStoreTokenSpecifies whether to store a token when using the SagePay gateway.
SagePayTokenThe token value for a corresponding card when using the SagePay gateway.
SagePayUseAbortIndicates whether to use Abort or Void for void transactions.
Shift4AuthTokenSpecifies the Auth Token when making an Access Token request to the Shift4 gateway.
Shift4ClientGuidSpecifies the Client Guid when making an Access Token request to the Shift4 gateway.
Shift4GetAccessTokenPerforms an Access Token Exchange request with the Shift4 gateway.
Shift4InterfaceNameSpecifies the name of the interface for the Shift4 gateway.
Shift4InterfaceVersionSpecifies the version of the interface for the Shift4 gateway.
SquareAdditionalRecipientsAdditional recipients data to send with a Square Sale or AuthOnly request.
SquareApplicationFeeAllows you to specify an application fee as part of the transaction.
SquareCustomerCardIdThe Id of the card saved to a customer profile.
SquareIdempotencyKeyValue that uniquely identifies a Square Sale, AuthOnly, or Refund request.
SquareLocationIdSquare location Id to make the transaction request against.
SquareOrderIdSquare Order Id to associate with a Square Sale or AuthOnly request.
SquareTenderIdSquare Tender Id associated with a Square transaction.
StoreCardOnFileFor the Stored Credentials framework - Used to indicate that the merchant will be storing the customer's card on file (COF).
StripeApplicationFeeA fee in cents that will be applied to the charge.
StripeDestinationAccountId of an existing, connected Stripe account.
StripeDestinationAmountThe amount to transfer to the destination account.
StripeOnBehalfOfThe Stripe account Id that these funds are intended for.
StripeRefundApplicationFeeWhether the application fee should be refunded when refunding the charge.
StripeRefundReasonReason for the refund.
StripeRefundReverseTransferWhether the transfer should be reversed when refunding the charge.
StripeShippingCarrierThe delivery service that shipped a physical product.
StripeShippingTrackingNumberThe tracking number for a physical product.
StripeTransferGroupIdentifies the transaction as part of a group.
StripeVersionDetermines which version of the Stripe API should be used.
SurchargeAmountUsed to specify the amount of the surcharge for the transaction.
TerminalIdTerminal Id value sent in the transaction.
TipAmountUsed to specify the amount of the tip for the transaction.
USAEPayPerformVoidReleaseSpecifies whether to perform a void or void:release transaction.
UseCardOnFileFor the Stored Credentials framework - Used to indicate that the merchant is using stored card on file (COF) information for the request.
UserIdUsed to specify an Id for the API user.
VeritasBankNameName of the card issuer.
VeritasEncryptionKeyEncryption key used to encrypt credit card information.
VeritasEncryptionKeyEncryption key used to encrypt credit card information.
VeritasTokenVeritas token.
VeritasVoidRefundReasonIdVeritas gateway void reason.
WorldpayOnlineTokenWorldpay Online token.
WorldpayOnlineTokenActionUsed to generate, update, or delete a Worldpay Online token.
XChildrenCountThe number of child elements of the current element.
XChildrenName[x]The name of the child element.
XChildrenXText[x]The inner text of the child element.
XElementThe name of the current element.
XPathProvides a way to point to a specific element in the returned XML or JSON response.
XTextThe text of the current element.
AcceptEncodingUsed to tell the server which types of content encodings the client supports.
AllowHTTPCompressionThis property enables HTTP compression for receiving data.
AllowHTTPFallbackWhether HTTP/2 connections are permitted to fallback to HTTP/1.1.
AllowNTLMFallbackWhether to allow fallback from Negotiate to NTLM when authenticating.
AppendWhether to append data to LocalFile.
AuthorizationThe Authorization string to be sent to the server.
BytesTransferredContains the number of bytes transferred in the response data.
ChunkSizeSpecifies the chunk size in bytes when using chunked encoding.
CompressHTTPRequestSet to true to compress the body of a PUT or POST request.
EncodeURLIf set to True the URL will be encoded by the component.
FollowRedirectsDetermines what happens when the server issues a redirect.
GetOn302RedirectIf set to True the component will perform a GET on the new location.
HTTP2HeadersWithoutIndexingHTTP2 headers that should not update the dynamic header table with incremental indexing.
HTTPVersionThe version of HTTP used by the component.
IfModifiedSinceA date determining the maximum age of the desired document.
KeepAliveDetermines whether the HTTP connection is closed after completion of the request.
KerberosSPNThe Service Principal Name for the Kerberos Domain Controller.
LogLevelThe level of detail that is logged.
MaxHeadersInstructs component to save the amount of headers specified that are returned by the server after a Header event has been fired.
MaxHTTPCookiesInstructs component to save the amount of cookies specified that are returned by the server when a SetCookie event is fired.
MaxRedirectAttemptsLimits the number of redirects that are followed in a request.
NegotiatedHTTPVersionThe negotiated HTTP version.
OtherHeadersOther headers as determined by the user (optional).
ProxyAuthorizationThe authorization string to be sent to the proxy server.
ProxyAuthSchemeThe authorization scheme to be used for the proxy.
ProxyPasswordA password if authentication is to be used for the proxy.
ProxyPortPort for the proxy server (default 80).
ProxyServerName or IP address of a proxy server (optional).
ProxyUserA user name if authentication is to be used for the proxy.
SentHeadersThe full set of headers as sent by the client.
StatusLineThe first line of the last response from the server.
TransferredDataThe contents of the last response from the server.
TransferredDataLimitThe maximum number of incoming bytes to be stored by the component.
TransferredHeadersThe full set of headers as received from the server.
TransferredRequestThe full request as sent by the client.
UseChunkedEncodingEnables or Disables HTTP chunked encoding for transfers.
UseIDNsWhether to encode hostnames to internationalized domain names.
UsePlatformDeflateWhether to use the platform implementation to decompress compressed responses.
UsePlatformHTTPClientWhether or not to use the platform HTTP client.
UseProxyAutoConfigURLWhether to use a Proxy auto-config file when attempting a connection.
UserAgentInformation about the user agent (browser).
CloseStreamAfterTransferIf true, the component will close the upload or download stream after the transfer.
ConnectionTimeoutSets a separate timeout value for establishing a connection.
FirewallAutoDetectTells the component whether or not to automatically detect and use firewall system settings, if available.
FirewallHostName or IP address of firewall (optional).
FirewallListenerIf true, the component binds to a SOCKS firewall as a server (TCPClient only).
FirewallPasswordPassword to be used if authentication is to be used when connecting through the firewall.
FirewallPortThe TCP port for the FirewallHost;.
FirewallTypeDetermines the type of firewall to connect through.
FirewallUserA user name if authentication is to be used connecting through a firewall.
KeepAliveIntervalThe retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.
KeepAliveTimeThe inactivity time in milliseconds before a TCP keep-alive packet is sent.
LingerWhen set to True, connections are terminated gracefully.
LingerTimeTime in seconds to have the connection linger.
LocalHostThe name of the local host through which connections are initiated or accepted.
LocalPortThe port in the local host where the component binds.
MaxLineLengthThe maximum amount of data to accumulate when no EOL is found.
MaxTransferRateThe transfer rate limit in bytes per second.
ProxyExceptionsListA semicolon separated list of hosts and IPs to bypass when using a proxy.
TCPKeepAliveDetermines whether or not the keep alive socket option is enabled.
TcpNoDelayWhether or not to delay when sending packets.
UseIPv6Whether to use IPv6.
UseNTLMv2Whether to use NTLM V2.
CACertFilePathsThe paths to CA certificate files when using Mono on Unix/Linux.
LogSSLPacketsControls whether SSL packets are logged when using the internal security API.
ReuseSSLSessionDetermines if the SSL session is reused.
SSLCACertsA newline separated list of CA certificate to use during SSL client authentication.
SSLCheckCRLWhether to check the Certificate Revocation List for the server certificate.
SSLCheckOCSPWhether to use OCSP to check the status of the server certificate.
SSLCipherStrengthThe minimum cipher strength used for bulk encryption.
SSLEnabledCipherSuitesThe cipher suite to be used in an SSL negotiation.
SSLEnabledProtocolsUsed to enable/disable the supported security protocols.
SSLEnableRenegotiationWhether the renegotiation_info SSL extension is supported.
SSLIncludeCertChainWhether the entire certificate chain is included in the SSLServerAuthentication event.
SSLKeyLogFileThe location of a file where per-session secrets are written for debugging purposes.
SSLNegotiatedCipherReturns the negotiated ciphersuite.
SSLNegotiatedCipherStrengthReturns the negotiated ciphersuite strength.
SSLNegotiatedCipherSuiteReturns the negotiated ciphersuite.
SSLNegotiatedKeyExchangeReturns the negotiated key exchange algorithm.
SSLNegotiatedKeyExchangeStrengthReturns the negotiated key exchange algorithm strength.
SSLNegotiatedVersionReturns the negotiated protocol version.
SSLSecurityFlagsFlags that control certificate verification.
SSLServerCACertsA newline separated list of CA certificate to use during SSL server certificate validation.
TLS12SignatureAlgorithmsDefines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal.
TLS12SupportedGroupsThe supported groups for ECC.
TLS13KeyShareGroupsThe groups for which to pregenerate key shares.
TLS13SignatureAlgorithmsThe allowed certificate signature algorithms.
TLS13SupportedGroupsThe supported groups for (EC)DHE key exchange.
AbsoluteTimeoutDetermines whether timeouts are inactivity timeouts or absolute timeouts.
FirewallDataUsed to send extra data to the firewall.
InBufferSizeThe size in bytes of the incoming queue of the socket.
OutBufferSizeThe size in bytes of the outgoing queue of the socket.
BuildInfoInformation about the product's build.
GUIAvailableTells the component whether or not a message loop is available for processing events.
LicenseInfoInformation about the current license.
MaskSensitiveWhether sensitive data is masked in log messages.
UseInternalSecurityAPITells the component whether or not to use the system security libraries or an internal implementation.

AuthCode Property (ICharge Component)

Authorization code from a previous transaction.

Syntax

public string AuthCode { get; set; }
Public Property AuthCode As String

Default Value

""

Remarks

Some gateways require the merchant to include the ApprovalCode from the original transaction in Credit, VoidTransaction, and Capture transactions. You may send the original approval code in this AuthCode property. The gateways which require this are listed below:

  • gwIntellipay (3)
  • gwBankOfAmerica (13)
  • gwInnovative (14)
  • gwACHPAyments (35)
  • gwForte (36)
  • gwSagePay (50)
  • gwDataCash (77)
  • gwFirstDataE4 (80)

Card Property (ICharge Component)

Contains the customer's credit card information.

Syntax

public EPCard Card { get; set; }
Public Property Card As EPCard

Remarks

This must be set to an instance of the EPCard type, which will contain information about the credit card to be charged. This should include a card Number, ExpMonth, and ExpYear, as well as optional CVVData.

This property is not available at design time.

Customer Property (ICharge Component)

Contains the customer's name, address, and other identifying information.

Syntax

public EPCustomer Customer { get; set; }
Public Property Customer As EPCustomer

Remarks

This property must be set to an instance of the EPCustomer type, which will contain information that identifies the customer. This information will be used by the Gateway for fraud checking purposes. See the EPCustomer type for more information.

All gateways require at the minimum the FirstName, LastName, FullName (the customer's name as it appears on the card), Address, City, State, and Zip. The following table shows which gateways require which additional Customer properties:

Gateway Country Email Id Phone
gwGoRealTime (4) X
gwITransact (8) XX X
gwSkipjack (22) X X
gwECHOnline (23) X
gwPayFlowLink (28) XXX
gwCyberCash (41) XXX
gwCyberSource (46) X
gwGoEMerchant (48) X
gwNexCommerce (53) XX X
gwWorldPay (54) X
gwPayGea (56) X X

This property is not available at design time.

Gateway Property (ICharge Component)

Gateway to process transactions with.

Syntax

public IchargeGateways Gateway { get; set; }

enum IchargeGateways { gwNoGateway, gwAuthorizeNet, gwEprocessing, gwIntellipay, gwITransact, gwNetBilling, gwPayFlowPro, gwUSAePay, gwPlugNPay, gwPlanetPayment, gwMPCS, gwRTWare, gwECX, gwBankOfAmerica, gwInnovative, gwMerchantAnywhere, gwSkipjack, gw3DSI, gwTrustCommerce, gwPSIGate, gwPayFuse, gwPayFlowLink, gwOrbital, gwLinkPoint, gwMoneris, gwUSight, gwFastTransact, gwNetworkMerchants, gwIngenico, gwPRIGate, gwMerchantPartners, gwCyberCash, gwFirstData, gwYourPay, gwACHPayments, gwForte, gwCyberSource, gwEway, gwGoEMerchant, gwTransFirst, gwChase, gwNexCommerce, gwWorldPay, gwTransactionCentral, gwSterling, gwPayJunction, gwSECPay, gwPaymentExpress, gwMyVirtualMerchant, gwSagePayments, gwSecurePay, gwMonerisUSA, gwBambora, gwVerifi, gwSagePay, gwMerchantESolutions, gwPayLeap, gwPayPoint, gwWorldPayXML, gwProPay, gwQBMS, gwHeartland, gwLitle, gwBrainTree, gwJetPay, gwHSBC, gwBluePay, gwAdyen, gwBarclay, gwPayTrace, gwYKC, gwOmniFund, gwTransNationalBankcard, gwNetbanx, gwMIT, gwDataCash, gwACHFederal, gwGlobalIris, gwFirstDataE4, gwFirstAtlantic, gwBluefin, gwPayscape, gwPayDirect, gwAuthorizeNetCIM, gw5thDimension, gwWorldPayLink, gwPaymentWorkSuite, gwPSIGateXML, gwFirstDataPayPoint, gwExPay, gwPayvision, gwConverge, gwPayeezy, gwMonetra, gwAuthorizeNetXML, gwPhoeniXGate, gwRepay, gwGlobalPayroll, gwPayWiser, gwVeritas, gwStripe, gwKartePay, gwBlueSnap, gwAmericanPaymentSolutions, gwBASYS, gwWorldpayOnline, gwSquare, gwPriorityPaymentSystems, gwNuvei, gwCardPointe, gwMetrobank, gwQBPayments, gwShift4, gwSquarePayments, gwHeartlandPortico, gwPayTraceJSON }
Public Property Gateway As IchargeGateways

Enum IchargeGateways gwNoGateway gwAuthorizeNet gwEprocessing gwIntellipay gwITransact gwNetBilling gwPayFlowPro gwUSAePay gwPlugNPay gwPlanetPayment gwMPCS gwRTWare gwECX gwBankOfAmerica gwInnovative gwMerchantAnywhere gwSkipjack gw3DSI gwTrustCommerce gwPSIGate gwPayFuse gwPayFlowLink gwOrbital gwLinkPoint gwMoneris gwUSight gwFastTransact gwNetworkMerchants gwIngenico gwPRIGate gwMerchantPartners gwCyberCash gwFirstData gwYourPay gwACHPayments gwForte gwCyberSource gwEway gwGoEMerchant gwTransFirst gwChase gwNexCommerce gwWorldPay gwTransactionCentral gwSterling gwPayJunction gwSECPay gwPaymentExpress gwMyVirtualMerchant gwSagePayments gwSecurePay gwMonerisUSA gwBambora gwVerifi gwSagePay gwMerchantESolutions gwPayLeap gwPayPoint gwWorldPayXML gwProPay gwQBMS gwHeartland gwLitle gwBrainTree gwJetPay gwHSBC gwBluePay gwAdyen gwBarclay gwPayTrace gwYKC gwOmniFund gwTransNationalBankcard gwNetbanx gwMIT gwDataCash gwACHFederal gwGlobalIris gwFirstDataE4 gwFirstAtlantic gwBluefin gwPayscape gwPayDirect gwAuthorizeNetCIM gw5thDimension gwWorldPayLink gwPaymentWorkSuite gwPSIGateXML gwFirstDataPayPoint gwExPay gwPayvision gwConverge gwPayeezy gwMonetra gwAuthorizeNetXML gwPhoeniXGate gwRepay gwGlobalPayroll gwPayWiser gwVeritas gwStripe gwKartePay gwBlueSnap gwAmericanPaymentSolutions gwBASYS gwWorldpayOnline gwSquare gwPriorityPaymentSystems gwNuvei gwCardPointe gwMetrobank gwQBPayments gwShift4 gwSquarePayments gwHeartlandPortico gwPayTraceJSON End Enum

Default Value

0

Remarks

This property is used to select the gateway with which transactions will be processed. Setting the Gateway property will also fill the GatewayURL with the URL to the gateway's processing server, and will also fill the and SpecialFields property with a collection of default names and values for the selected gateway. These are special configuration values that should usually not be changed. The following table shows the currently supported gateways, as well as the corporate home page for each.

GatewayHome page
No Gateway (0) n/a
Authorize.Net AIM (1)http://www.authorize.net
eProcessing Transparent Database Engine (2)http://www.eProcessingNetwork.com
Intellipay ExpertLink (3)http://www.intellipay.com
iTransact RediCharge HTML (4)http://www.itransact.com
NetBilling DirectMode (5)http://www.netbilling.com
PayFlow Pro (6)https://www.paypal.com/webapps/mpp/payflow-payment-gateway
USA ePay CGI Transaction Gateway (7)http://www.usaepay.com
Plug 'n Pay (8)http://www.plugnpay.com
Planet Payment iPay (9)http://planetpayment.com/
MPCS (10)http://merchantcommerce.net/
RTWare (11)http://www.rtware.net/
ECX (12)http://www.ecx.com
Bank of America (Global Gateway e4) (13)http://bankofamerica.com/merchantservices
Innovative Gateway (PHP) (14)http://www.innovativegateway.com
Merchant Anywhere (Transaction Central Classic) (15)http://www.merchantanywhere.com/
SkipJack (16)http://www.skipjack.com
3 Delta Systems (3DSI) EC-Linx (18)http://www.3dsi.com
TrustCommerce API (19)http://www.trustcommerce.com
PSIGate HTML (20)http://www.psigate.com
PayFuse XML (ClearCommerce Engine) (21)http://www.firstnationalmerchants.com/
PayFlow Link (22)https://www.paypal.com/webapps/mpp/payflow-payment-gateway
Chase Paymentech Orbital Gateway (23)https://merchantservices.chase.com/
LinkPoint (24)http://www.linkpoint.com
Moneris eSelect Plus Canada (25)http://www.moneris.com
uSight Gateway Post-Auth (26)This gateway is no longer in service.
Fast Transact VeloCT (Direct Mode) (27)http://www.fasttransact.com/
NetworkMerchants Direct-Post API (28)http://www.nmi.com/
Ingenico DirectLink / Ogone (29)https://www.ingenico.be/
TransFirst Transaction Central Classic (formerly PRIGate) (30)http://www.transfirst.com
Merchant Partners (Transaction Engine) (31)http://www.merchantpartners.com/
CyberCash (32)https://www.paypal.com/cybercash
First Data Global Gateway (Linkpoint) (33)http://www.firstdata.com
YourPay (Linkpoint) (34) http://www.yourpay.com
ACH Payments AGI (35)http://www.ach-payments.com
Forte AGI / Payments Gateway AGI(36)https://www.forte.net/
Cyber Source SOAP API (37)http://www.cybersource.com
eWay XML API (Australia) (38)http://www.eway.com.au/
goEmerchant XML (39)http://www.goemerchant.com/
TransFirst eLink (40)http://www.transfirst.com
Chase Merchant Services (Linkpoint) (41)http://www.chase.com
Thompson Merchant Services NexCommerce (iTransact mode) (42)http://www.thompsonmerchant.com
WorldPay Select Junior Invisible (43)http://www.worldpay.com
TransFirst Transaction Central Classic (44)http://www.transfirst.com. (This is different from TransFirst eLink, supported above. The TransactionCentral gateway is also used by MerchantAnywhere and PRIGate)
Sterling SPOT XML API (HTTPS POST) (45)http://www.sterlingpayment.com
PayJunction Trinity Gateway (46)http://www.payjunction.com
SECPay (United Kingdom) API Solution(47)http://www.secpay.com
Payment Express PXPost (48)http://www.paymentexpress.com
Elavon/NOVA/My Virtual Merchant (49)https://support.convergepay.com/s/
Sage Payment Solutions (Bankcard HTTPS Post protocol) (50)http://www.sagepayments.com
SecurePay (Script API/COM Object Interface) (51)http://securepay.com
Moneris eSelect Plus USA (52)http://www.moneris.com
Bambora / Beanstream Process Transaction API (53)https://www.bambora.com/en/ca/
Verifi Direct-Post API (54)http://www.verifi.com
SagePay Direct (Previously Protx) (55)https://www.opayo.uk/
Merchant E-Solutions Payment Gateway (Trident API) (56)http://merchante-solutions.com/
PayLeap Web Services API (57)http://www.payleap.com
PayPoint.net (Previously SECPay) API Solution (58)http://paypoint.net
Worldpay XML (Direct/Invisible) (59)http://www.worldpay.com
ProPay Merchant Services API (60)http://www.propay.com
Intuit QuickBooks Merchant Services (QBMS) (61)This gateway is no longer in service. It has been replaced by Quickbooks Payments (113).
Heartland POS Gateway (62)http://www.heartlandpaymentsystems.com/
Litle / Vantiv Online Gateway (63)http://www.litle.com/
BrainTree DirectPost (Server-to-Server Orange) Gateway (64)http://www.braintreepaymentsolutions.com/
JetPay Gateway (65)http://www.jetpay.com/
HSBC XML API (ClearCommerce Engine) (66)https://www.business.hsbc.uk/en-gb/payments/business-card
BluePay 2.0 Post (67)http://www.bluepay.com
Adyen API Payments (68)http://www.adyen.com
Barclay ePDQ (DirectLink) (69)http://www.barclaycard.co.uk/business/
PayTrace Payment Gateway (70)https://www.paytrace.net/
YKC Gateway (71)http://www.ykc-bos.co.jp/
OmniFund HTTP API / GoToBilling(73)http://omnifund.com/
TransNational Bankcard (74)http://www.tnbci.com/
Netbanx (75)http://www.netbanx.com/
MIT (76)http://www.centrodepagos.com.mx
DataCash (77)http://www.datacash.com/
ACH Federal (78)http://www.achfederal.com/
Global Iris (HSBC) (79)https://www.globalpaymentsinc.com/en-gb
First Data Global Gateway E4 (80)http://www.firstdata.com
First Atlantic Commerce (81)http://www.firstatlanticcommerce.com/
Bluefin (82)http://www.bluefin.com/
Payscape (83)http://www.payscape.com
Pay Direct (Link2Gov) (84)https://www.fisglobal.com/solutions/other/government/
Authorize.NET CIM (85)http://www.authorize.net
5th Dimension Logistics (86)http://www.5thdl.com/
WorldPay US Link Gateway (87)https://www.worldpay.com/en-us/index
3DSI Payment WorkSuite (88)http://www.3dsi.com/
PSIGate XML (89)http://www.psigate.com
First Data PayPoint (90)https://www.firstdata.com/en_us/products/financial_institutions.html
ExPay Gateway (91)http://www.expay.asia
Payvision Gateway (92)http://www.payvision.com/
Converge (formerly MyVirtualMerchant) (93)https://support.convergepay.com/s/
Payeezy Gateway (formerly First Data E4) (94)https://developer.payeezy.com/
Monetra Gateway (95)http://www.monetra.com
Authorize.NET XML (96)http://www.authorize.net/
PhoeniXGate Gateway (97)http://www.phoenixmanagednetworks.com/
Repay Gateway (98)https://www.repay.com/
Global Payroll Gateway (99)https://www.gpgway.com/
PayWiser Gateway (100)https://paywiser.eu/
Veritas Gateway (101)http://www.veritaspay.com/
Stripe Gateway (102)http://www.stripe.com/
KartePay Gateway (103)https://www.kartepay.com/
BlueSnap Gateway (104)https://home.bluesnap.com/
American Payment Solutions (105)https://www.apspayments.com/
BASYS Gateway (106)https://basyspro.com/
Worldpay Online (107)https://www.worldpay.com
Square (108)https://www.squareup.com
Priority Payment Systems (109)https://prioritypaymentsystems.com
Nuvei / GlobalOnePay (110)https://nuvei.com/en-us/
CardPointe (111)https://cardconnect.com/cardpointe
Metrobank (112)https://www.metrobankcard.com/
Quickbooks Payments (113)https://quickbooks.intuit.com/payments/
Shift4 (114)https://www.shift4.com/
Square Payments (115)https://squareup.com/us/en
Heartland Portico Gateway (116)http://www.heartlandpaymentsystems.com/
PayTrace Payment Gateway JSON (117)https://www.paytrace.net/

GatewayURL Property (ICharge Component)

Default URL for a specific Gateway .

Syntax

public string GatewayURL { get; set; }
Public Property GatewayURL As String

Default Value

""

Remarks

This property is used to change the default URL for a specific Gateway. This is useful for specifying a different URL for testing purposes, or to support additional gateway processors that share a protocol format (such as additional Authorize.net compatible gateways). Please note that the proper "http://" or "https://" formatting must be observed. See "Testing Information" in the Table of Contents for a list of test URLs.

InvoiceNumber Property (ICharge Component)

Merchant-generated invoice number.

Syntax

public string InvoiceNumber { get; set; }
Public Property InvoiceNumber As String

Default Value

""

Remarks

This field contains a merchant-generated invoice number. This number should be unique for each transaction. This property is optional for most gateways, but it is recommended that the merchant use an invoice number to keep track of transactions. See the Gateway property to determine if this is a required or optional field for the gateway you are using.

Level2Aggregate Property (ICharge Component)

The level 2 aggregate containing the data to be sent in the request.

Syntax

public string Level2Aggregate { get; set; }
Public Property Level2Aggregate As String

Default Value

""

Remarks

This property is used to specify the level 2 aggregate obtained from Level2 component. When specified, the component will parse the aggregate and send the specified values within the transaction request to process the transaction as a level 2 transaction.

Level3Aggregate Property (ICharge Component)

The level 3 aggregate containing the data to be sent in the request.

Syntax

public string Level3Aggregate { get; set; }
Public Property Level3Aggregate As String

Default Value

""

Remarks

This property is used to specify the level 3 aggregate obtained from Level3 component. When specified, the component will parse the aggregate and send the specified values within the transaction request to process the transaction as a level 3 transaction.

MerchantLogin Property (ICharge Component)

Merchant's Gateway login.

Syntax

public string MerchantLogin { get; set; }
Public Property MerchantLogin As String

Default Value

""

Remarks

This is the login Id supplied by the Gateway you signed up with to process credit card transactions.

MerchantPassword Property (ICharge Component)

Merchant's Gateway password.

Syntax

public string MerchantPassword { get; set; }
Public Property MerchantPassword As String

Default Value

""

Remarks

This is the password supplied by the Gateway you signed up with to process credit card transactions. Some gateways require passwords only for Credit or Void transactions, some require it for all transactions, and some do not require this field at all.

Proxy Property (ICharge Component)

This property includes a set of properties related to proxy access.

Syntax

public Proxy Proxy { get; set; }
Public Property Proxy As Proxy

Remarks

This property contains fields describing the proxy through which the component will attempt to connect.

Response Property (ICharge Component)

Contains the response to the authorization.

Syntax

public EPResponse Response { get; }
Public ReadOnly Property Response As EPResponse

Remarks

This property will contain the response returned from the Gateway server. It should be inspected (and logged) after a call to AuthOnly, Sale, Capture, Credit, Force, or VoidTransaction. The EPResponse type contains the following fields:

ApprovalCode Contains an authorization code for an approved transaction.
Approved Indicates whether the transaction was successful (True) or unsuccessful (False).
ApprovedAmount The amount approved for the transaction, this is the amount actually charged to the credit card.
AVSResult Contains the Address Verification System result code. Used for fraud detection.
Code Indicates the success or failure of the transaction.
CVVResult Contains the returned CVV result code if it was requested. Used for fraud detection.
Data Contains the raw response from the host.
ErrorCode Additional code returned for declined or failed transactions.
ErrorText Description of the error which occurred.
InvoiceNumber Merchant-generated invoice number echoed back in the response.
ProcessorCode Return code generated by the processor, or additional gateway response code that may contain more information beyond "Approved" or "Declined".
Text Contains a human-readable message explaining the code.
TransactionId Host-generated transaction identifier, used for Captures, Credits, or Voids.

Note that many gateways do not return values in all of these fields. Any field in the Data which has not been parsed into these Response fields may be retrieved with the GetResponseVar method.

This property is read-only and not available at design time.

ShippingInfo Property (ICharge Component)

Contains the customer's shipping name, address, and other identifying information.

Syntax

public EPShipInfo ShippingInfo { get; set; }
Public Property ShippingInfo As EPShipInfo

Remarks

This property must be set to an instance of the EPShipInfo type, which will contain information that specifies the shipping information for the order. See the EPShipInfo type for more information.

This property is not available at design time.

SpecialFields Property (ICharge Component)

A list of additional fields to send in the request.

Syntax

public EPSpecialFieldList SpecialFields { get; }
Public Property SpecialFields As EPSpecialFieldList

Remarks

This property contains a collection of EPSpecialField name/value pair objects. The Gateway may put some special configuration fields into this property which you can edit or add to. This allows you to extend the functionality of the component by adding fields for which there are not currently properties for.

This property is not available at design time.

SSLAcceptServerCert Property (ICharge Component)

Instructs the component to unconditionally accept the server certificate that matches the supplied certificate.

Syntax

public Certificate SSLAcceptServerCert { get; set; }
Public Property SSLAcceptServerCert As Certificate

Remarks

If it finds any issues with the certificate presented by the server, the component will normally terminate the connection with an error.

You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.

Please note that this functionality is provided only for cases where you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.

SSLCert Property (ICharge Component)

The certificate to be used during SSL negotiation.

Syntax

public Certificate SSLCert { get; set; }
Public Property SSLCert As Certificate

Remarks

The digital certificate that the component will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.

SSLProvider Property (ICharge Component)

This specifies the SSL/TLS implementation to use.

Syntax

public IchargeSSLProviders SSLProvider { get; set; }

enum IchargeSSLProviders { sslpAutomatic, sslpPlatform, sslpInternal }
Public Property SSLProvider As IchargeSSLProviders

Enum IchargeSSLProviders sslpAutomatic sslpPlatform sslpInternal End Enum

Default Value

0

Remarks

This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the component will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.

Possible values are:

0 (sslpAutomatic - default)Automatically selects the appropriate implementation.
1 (sslpPlatform) Uses the platform/system implementation.
2 (sslpInternal) Uses the internal implementation.

Additional Notes

In most cases using the default value (Automatic) is recommended. The component will select a provider depending on the current platform.

When Automatic is selected, on Windows the component will use the platform implementation. On Linux/macOS the component will use the internal implementation. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used on all platforms.

The .NET Standard library will always use the internal implementation on all platforms.

SSLServerCert Property (ICharge Component)

The server certificate for the last established connection.

Syntax

public Certificate SSLServerCert { get; }
Public ReadOnly Property SSLServerCert As Certificate

Remarks

SSLServerCert contains the server certificate for the last established connection.

SSLServerCert is reset every time a new connection is attempted.

This property is read-only.

TestMode Property (ICharge Component)

Turns test mode on and off for transactions sent to the current Gateway .

Syntax

public bool TestMode { get; set; }
Public Property TestMode As Boolean

Default Value

False

Remarks

You can use this property to set a test mode flag that will be sent in an authorization request. Not all Gateways support test modes. If you set the TestMode property to True and the current Gateway does not support it, the component will throws an exception.

Timeout Property (ICharge Component)

A timeout for the component.

Syntax

public int Timeout { get; set; }
Public Property Timeout As Integer

Default Value

30

Remarks

If Timeout is set to a positive value, and an operation cannot be completed immediately, the component will retry the operation for a maximum of Timeout seconds.

The default value for Timeout is 30 (seconds).

TransactionAmount Property (ICharge Component)

Purchase amount for an authorization transaction.

Syntax

public string TransactionAmount { get; set; }
Public Property TransactionAmount As String

Default Value

""

Remarks

This field contains the transaction amount to be authorized. Gateways may have differing requirements for how the TransactionAmount should be formatted, so refer to the ICharge Gateway Setup page for details on the gateway you are using.

TransactionDesc Property (ICharge Component)

Description of goods purchased.

Syntax

public string TransactionDesc { get; set; }
Public Property TransactionDesc As String

Default Value

""

Remarks

This field contains a description of the goods or services being purchased. Please see the "ICharge Gateway Setup and Required Properties" page to determine if this is a required or optional field for the gateway you are using.

TransactionId Property (ICharge Component)

Merchant-generated transaction Id used for all transactions.

Syntax

public string TransactionId { get; set; }
Public Property TransactionId As String

Default Value

""

Remarks

This property is used to send a merchant-generated transaction id to the Gateway, if the gateway supports that feature.

AddSpecialField Method (ICharge Component)

Adds a special field name and the corresponding value.

Syntax

public void AddSpecialField(string name, string value);
Public Sub AddSpecialField(ByVal Name As String, ByVal Value As String)

Remarks

Please refer to the Name and Value fields for more information on form variables and how they are managed.

AuthOnly Method (ICharge Component)

Initiates an authorization-only request transaction.

Syntax

public void AuthOnly();
Public Sub AuthOnly()

Remarks

This method sends an authorization-only request to the specified Gateway. This transaction is not added to the current open batch, and must be completed later with the Capture method (you may use the Sale method if you wish to authorize and capture in one step).

Note: If the Gateway does not support this method, the component will throws an exception.

AVSOnly Method (ICharge Component)

Used to check the validity of the card without authorizing funds.

Syntax

public void AVSOnly();
Public Sub AVSOnly()

Remarks

This method can be used if you wish to perform fraud (AVS and CVV) checks on a card, but don't actually wish to charge the customer. This is useful for pre-ordering an item that has not yet been released or is currently back- ordered. The card information is validated by the merchant, and when the item is later in stock and ships to the customer, an Sale transaction can be performed.

Note: If the Gateway does not support this method, the component will throws an exception.

Capture Method (ICharge Component)

Captures a previously authorized transaction.

Syntax

public void Capture(string transactionId, string captureAmount);
Public Sub Capture(ByVal TransactionId As String, ByVal CaptureAmount As String)

Remarks

This method captures a transaction that has been previously authorized with the AuthOnly method. The TransactionId parameter indicates to the Gateway which transaction is to be captured, and should contain the TransactionId from the original transaction. The CaptureAmount parameter is the value to be captured from the customer's credit card, and can be different from the authorized amount.

Please see the gateway information in the table of contents to determine if your gateway supports Capture transactions.

The LinkPoint and PSIGateXML gateways require you send the InvoiceNumber rather than the TransactionId.

The SecurePay gateway does not require the TransactionId for captures. Instead, you must send the ApprovalCode returned from the original response in the AuthCode property.

The MyVirtualMerchant and Converge gateways do not require the TransactionId for captures. Instead, you must send the ApprovalCode returned from the original response in the AuthCode property. Note that there is a new capture transaction type available for these gateways. To use the new transaction type, set the MyVirtualMerchantTransactionType to "CCCOMPLETE" and call Capture like normal. When using this transaction type, TransactionId is required and ApprovalCode is not applicable.

Config Method (ICharge Component)

Sets or retrieves a configuration setting.

Syntax

public string Config(string configurationString);
Public Function Config(ByVal ConfigurationString As String) As String

Remarks

Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

Credit Method (ICharge Component)

Credits a customer's card.

Syntax

public void Credit();
Public Sub Credit()

Remarks

This method credits a customer's card specified via Card. This type of transaction is NOT based on previous transaction. Some gateways refer to these as "Open" or "Blind" Credits.

TransactionAmount is used to specify the amount you wish to return to the customer's card.

Please see the gateway information in the table of contents to determine if your gateway supports Credit transactions.

DoEvents Method (ICharge Component)

Processes events from the internal message queue.

Syntax

public void DoEvents();
Public Sub DoEvents()

Remarks

When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.

Force Method (ICharge Component)

Used when authorization cannot be obtained online.

Syntax

public void Force(string voiceAuthCode);
Public Sub Force(ByVal VoiceAuthCode As String)

Remarks

This method is used when the response to a Sale or AuthOnly request indicates that voice authorization is required. The merchant then telephones the call center and receives a voice authorization code. Calling the Force method with this code in the VoiceAuthCode parameter will complete the transaction.

Note: If the Gateway does not support this method, the component will throws an exception.

GetResponseVar Method (ICharge Component)

Parses additional information out of the response.

Syntax

public string GetResponseVar(string name);
Public Function GetResponseVar(ByVal Name As String) As String

Remarks

Due to the fact that this component supports so many gateways, only the most commonly used response variables are parsed into the Response fields. Any additional response information contained within the Data may be retrieved with this GetResponseVar method. There are three formats for the Data returned by the gateways this component supports: Name/value pairs, delimited list, or XML. The value you pass in the Name parameter changes based on these formats, as detailed below:

If the Data field contains name/value pairs, pass the name in the Name parameter and this method will return the value. For instance, if Data contains "ResponseCode=00&FraudScore=53&ApprovalCode=123456&...", calling GetResponseVar("FraudScore") will return "53".

However, if Data contains a delimited list, pass the index of the field you wish to receive. For instance, if Data contains "00|53|123456|...", calling GetResponseVar("1") will return "53".

Finally, if Data contains XML, pass the xpath to the value you wish to receive. For instance, if Data contains "<Response><Code>00</Code><FraudScore>53</FraudScore><ApprovalCode>123456</ApprovalCode></Response>", calling GetResponseVar("/Response/FraudScore") will return "53".

Interrupt Method (ICharge Component)

Interrupts the current action.

Syntax

public void Interrupt();
Public Sub Interrupt()

Remarks

This method interrupts any processing that the component is currently executing.

Refund Method (ICharge Component)

Refunds a previously captured transaction.

Syntax

public void Refund(string transactionId, string refundAmount);
Public Sub Refund(ByVal TransactionId As String, ByVal RefundAmount As String)

Remarks

This method refunds a transaction that has already been captured, or settled. If the transaction is still outstanding use the VoidTransaction method instead. The TransactionId parameter indicates to the Gateway which transaction is to be refunded, and should contain the TransactionId from the original transaction. The RefundAmount parameter is the value to be refunded back to the customer, and can be all or part of the original TransactionAmount

Please see the gateway information in the table of contents to determine if your gateway supports Refund transactions.

The gw3DSI gateway requires the following additional fields for Refund transactions:

component.AddSpecialField "UserId", "my 3DSI-assigned UserId" '(Different than MerchantLogin) component.MerchantPassword = "my 3DSI-assigned Pwd"

The LinkPoint and PSIGateXML gateways require you send the InvoiceNumber rather than the TransactionId.

Reset Method (ICharge Component)

Clears all properties to their default values.

Syntax

public void Reset();
Public Sub Reset()

Remarks

This method clears all properties to their default values and returns the component to its default state.

ResetSpecialFields Method (ICharge Component)

Resets all special fields to the default settings.

Syntax

public void ResetSpecialFields();
Public Sub ResetSpecialFields()

Remarks

This function resets all special gateway configuration fields to the default settings for the specified Gateway.

Please refer to the SpecialFields property for more information on form variables and how they are managed.

Sale Method (ICharge Component)

Initiates an Sale transaction (authorization and capture).

Syntax

public void Sale();
Public Sub Sale()

Remarks

Sends a basic sale transaction to the Gateway. This transaction decrements the cardholder's open-to-buy funds for the TransactionAmount, and the transaction is automatically added to the current open batch.

VoidTransaction Method (ICharge Component)

Voids a previously authorized transaction.

Syntax

public void VoidTransaction(string transactionId);
Public Sub VoidTransaction(ByVal TransactionId As String)

Remarks

This method voids a transaction that has been previously authorized, but which has not yet gone to settlement, or been "captured". The TransactionId parameter indicates to the Gateway which transaction is to be voided, and should contain the TransactionId from the original transaction.

Please see the gateway information in the table of contents to determine if your gateway supports Void transactions.

To cancel a transaction which has already been captured, use the Credit method.

The LinkPoint gateway requires you send the InvoiceNumber rather than the TransactionId.

For the PSIGateXML gateway, send the TransactionId as normal.

For the Heartland gateway, a reversal transaction will be sent when a TransactionAmount is specified. Otherwise a void transaction will be sent.

Error Event (ICharge Component)

Information about errors during data delivery.

Syntax

public event OnErrorHandler OnError;

public delegate void OnErrorHandler(object sender, IchargeErrorEventArgs e);

public class IchargeErrorEventArgs : EventArgs {
  public int ErrorCode { get; }
  public string Description { get; }
}
Public Event OnError As OnErrorHandler

Public Delegate Sub OnErrorHandler(sender As Object, e As IchargeErrorEventArgs)

Public Class IchargeErrorEventArgs Inherits EventArgs
  Public ReadOnly Property ErrorCode As Integer
  Public ReadOnly Property Description As String
End Class

Remarks

The Error event is fired in case of exceptional conditions during message processing.

ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

SSLServerAuthentication Event (ICharge Component)

Fired after the server presents its certificate to the client.

Syntax

public event OnSSLServerAuthenticationHandler OnSSLServerAuthentication;

public delegate void OnSSLServerAuthenticationHandler(object sender, IchargeSSLServerAuthenticationEventArgs e);

public class IchargeSSLServerAuthenticationEventArgs : EventArgs {
  public string CertEncoded { get; }
public byte[] CertEncodedB { get; } public string CertSubject { get; } public string CertIssuer { get; } public string Status { get; } public bool Accept { get; set; } }
Public Event OnSSLServerAuthentication As OnSSLServerAuthenticationHandler

Public Delegate Sub OnSSLServerAuthenticationHandler(sender As Object, e As IchargeSSLServerAuthenticationEventArgs)

Public Class IchargeSSLServerAuthenticationEventArgs Inherits EventArgs
  Public ReadOnly Property CertEncoded As String
Public ReadOnly Property CertEncodedB As Byte() Public ReadOnly Property CertSubject As String Public ReadOnly Property CertIssuer As String Public ReadOnly Property Status As String Public Property Accept As Boolean End Class

Remarks

This event is where the client can decide whether to continue with the connection process or not. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether to continue or not.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string "OK"). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (ICharge Component)

Shows the progress of the secure connection.

Syntax

public event OnSSLStatusHandler OnSSLStatus;

public delegate void OnSSLStatusHandler(object sender, IchargeSSLStatusEventArgs e);

public class IchargeSSLStatusEventArgs : EventArgs {
  public string Message { get; }
}
Public Event OnSSLStatus As OnSSLStatusHandler

Public Delegate Sub OnSSLStatusHandler(sender As Object, e As IchargeSSLStatusEventArgs)

Public Class IchargeSSLStatusEventArgs Inherits EventArgs
  Public ReadOnly Property Message As String
End Class

Remarks

The event is fired for informational and logging purposes only. Used to track the progress of the connection.

Certificate Type

This is the digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

EffectiveDate
String

This is the date on which this certificate becomes valid. Before this date, it is not valid. The following example illustrates the format of an encoded date:

23-Jan-2000 15:00:00.

Encoded
String

This is the certificate (PEM/base64 encoded). This field is used to assign a specific certificate. The Store and Subject fields also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

EncodedB
Byte []

This is the certificate (PEM/base64 encoded). This field is used to assign a specific certificate. The Store and Subject fields also may be used to specify a certificate.

When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.

ExpirationDate
String

This is the date the certificate expires. After this date, the certificate will no longer be valid. The following example illustrates the format of an encoded date:

23-Jan-2001 15:00:00.

ExtendedKeyUsage
String

This is a comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).

Fingerprint
String

This is the hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02

FingerprintSHA1
String

This is the hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: 30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84

FingerprintSHA256
String

This is the hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: 6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53

Issuer
String

This is the issuer of the certificate. This field contains a string representation of the name of the issuing authority for the certificate.

PrivateKey
String

This is the private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.

Note: The PrivateKey may be available but not exportable. In this case, PrivateKey returns an empty string.

PrivateKeyAvailable
Boolean

This field shows whether a PrivateKey is available for the selected certificate. If PrivateKeyAvailable is True, the certificate may be used for authentication purposes (e.g., server authentication).

PrivateKeyContainer
String

This is the name of the PrivateKey container for the certificate (if available). This functionality is available only on Windows platforms.

PublicKey
String

This is the public key of the certificate. The key is provided as PEM/Base64-encoded data.

PublicKeyAlgorithm
String

This field contains the textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.

PublicKeyLength
Integer

This is the length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.

SerialNumber
String

This is the serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.

SignatureAlgorithm
String

The field contains the text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.

Store
String

This is the name of the certificate store for the client certificate.

The StoreType field denotes the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Store is used in conjunction with the Subject field to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject field for details.

Designations of certificate stores are platform-dependent.

The following are designations of the most common User and Machine certificate stores in Windows:

MYA certificate store holding personal certificates with their associated private keys.
CACertifying authority certificates.
ROOTRoot certificates.

When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).

StoreB
Byte []

This is the name of the certificate store for the client certificate.

The StoreType field denotes the type of the certificate store specified by Store. If the store is password protected, specify the password in StorePassword.

Store is used in conjunction with the Subject field to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the Subject field for details.

Designations of certificate stores are platform-dependent.

The following are designations of the most common User and Machine certificate stores in Windows:

MYA certificate store holding personal certificates with their associated private keys.
CACertifying authority certificates.
ROOTRoot certificates.

When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).

StorePassword
String

If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.

StoreType
CertStoreTypes

This is the type of certificate store for this certificate.

The component supports both public and private keys in a variety of formats. When the cstAuto value is used the component will automatically determine the type. This field can take one of the following values:

0 (cstUser - default)For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note: this store type is not available in Java.
1 (cstMachine)For Windows, this specifies that the certificate store is a machine store. Note: this store type is not available in Java.
2 (cstPFXFile)The certificate store is the name of a PFX (PKCS12) file containing certificates.
3 (cstPFXBlob)The certificate store is a string (binary or base64-encoded) representing a certificate store in PFX (PKCS12) format.
4 (cstJKSFile)The certificate store is the name of a Java Key Store (JKS) file containing certificates. Note: this store type is only available in Java.
5 (cstJKSBlob)The certificate store is a string (binary or base64-encoded) representing a certificate store in Java Key Store (JKS) format. Note: this store type is only available in Java.
6 (cstPEMKeyFile)The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate.
7 (cstPEMKeyBlob)The certificate store is a string (binary or base64-encoded) that contains a private key and an optional certificate.
8 (cstPublicKeyFile)The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate.
9 (cstPublicKeyBlob)The certificate store is a string (binary or base64-encoded) that contains a PEM- or DER-encoded public key certificate.
10 (cstSSHPublicKeyBlob)The certificate store is a string (binary or base64-encoded) that contains an SSH-style public key.
11 (cstP7BFile)The certificate store is the name of a PKCS7 file containing certificates.
12 (cstP7BBlob)The certificate store is a string (binary) representing a certificate store in PKCS7 format.
13 (cstSSHPublicKeyFile)The certificate store is the name of a file that contains an SSH-style public key.
14 (cstPPKFile)The certificate store is the name of a file that contains a PPK (PuTTY Private Key).
15 (cstPPKBlob)The certificate store is a string (binary) that contains a PPK (PuTTY Private Key).
16 (cstXMLFile)The certificate store is the name of a file that contains a certificate in XML format.
17 (cstXMLBlob)The certificate store is a string that contains a certificate in XML format.
18 (cstJWKFile)The certificate store is the name of a file that contains a JWK (JSON Web Key).
19 (cstJWKBlob)The certificate store is a string that contains a JWK (JSON Web Key).
21 (cstBCFKSFile)The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). Note: this store type is only available in Java and .NET.
22 (cstBCFKSBlob)The certificate store is a string (binary or base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. Note: this store type is only available in Java and .NET.
23 (cstPKCS11)The certificate is present on a physical security key accessible via a PKCS11 interface.

To use a security key the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS11 dll. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use.

When using a certificate, pass the previously saved security key information as the Store and set StorePassword to the PIN.

Code Example: SSH Authentication with Security Key certmgr.CertStoreType = CertStoreTypes.cstPKCS11; certmgr.OnCertList += (s, e) => { secKeyBlob = e.CertEncoded; }; certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll"; certmgr.CertStorePassword = "123456"; //PIN certmgr.ListStoreCertificates(); sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*"); sftp.SSHUser = "test"; sftp.SSHLogon("myhost", 22);

99 (cstAuto)The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically.

Subject
String

This is the subject of the certificate used for client authentication.

This field will be populated with the full subject of the loaded certificate. When loading a certificate the subject is used to locate the certificate in the store.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma separated list of distinguished name fields and values. For instance "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are displayed below.

FieldMeaning
CNCommon Name. This is commonly a host name like www.server.com.
OOrganization
OUOrganizational Unit
LLocality
SState
CCountry
EEmail Address

If a field value contains a comma it must be quoted.

SubjectAltNames
String

This field contains comma-separated lists of alternative subject names for the certificate.

ThumbprintMD5
String

This field contains the MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

ThumbprintSHA1
String

This field contains the SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

ThumbprintSHA256
String

This field contains the SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

Usage
String

This field contains the text description of UsageFlags.

This value will be of one or more of the following strings and will be separated by commas:

  • Digital Signatures
  • Key Authentication
  • Key Encryption
  • Data Encryption
  • Key Agreement
  • Certificate Signing
  • Key Signing

If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.

UsageFlags
Integer

This field contains the flags that show intended use for the certificate. The value of UsageFlags is a combination of the following flags:

0x80Digital Signatures
0x40Key Authentication
0x20Key Encryption
0x10Data Encryption
0x08Key Agreement
0x04Certificate Signing
0x02Key Signing

Please see the Usage field for a text representation of UsageFlags.

This functionality currently is not available when the provider is OpenSSL.

Version
String

This field contains the certificate's version number. The possible values are the strings "V1", "V2", and "V3".

Constructors

public Certificate();
Public Certificate()

Creates a Certificate instance whose properties can be set. This is useful for use with CERTMGR when generating new certificates.

public Certificate(string certificateFile);
Public Certificate(ByVal CertificateFile As String)

Opens CertificateFile and reads out the contents as an X509 public key.

public Certificate(byte[] certificateData);
Public Certificate(ByVal CertificateData As Byte())

Parses CertificateData as an X509 public key.

public Certificate(CertStoreTypes certStoreType, string store, string storePassword, string subject);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Subject As String)

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, string store, string storePassword, string subject, string configurationString);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Subject As String, ByVal ConfigurationString As String)

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. ConfigurationString is a newline separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CyrptoAPI option. The default value is True (the key is persisted). "Thumbprint" - a MD5, SHA1, or SHA256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to cstUser, cstMachine, cstPublicKeyFile, and cstPFXFile store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, string store, string storePassword, byte[] encoded);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Encoded As Byte())

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will load Encoded as an X509 certificate and search the opened store for a corresponding private key.

public Certificate(CertStoreTypes certStoreType, byte[] storeBlob, string storePassword, string subject);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal StoreBlob As Byte(), ByVal StorePassword As String, ByVal Subject As String)

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. StoreBlob is a string (binary- or base64-encoded) containing the certificate data. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, byte[] storeBlob, string storePassword, string subject, string configurationString);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal StoreBlob As Byte(), ByVal StorePassword As String, ByVal Subject As String, ByVal ConfigurationString As String)

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. StoreBlob is a string (binary- or base64-encoded) containing the certificate data. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X509 certificate's subject Distinguished Name (DN).

public Certificate(CertStoreTypes certStoreType, byte[] storeBlob, string storePassword, byte[] encoded);
Public Certificate(ByVal CertStoreType As CertStoreTypes, ByVal StoreBlob As Byte(), ByVal StorePassword As String, ByVal Encoded As Byte())

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a string (binary- or base64-encoded) containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the component will load Encoded as an X509 certificate and search the opened store for a corresponding private key.

EPCard Type

Contains the customer's credit card information.

Remarks

This type contains the customer's credit card information.

Example: Setting the fields: EPCard card = new EPCard(); card.Number = "4444333322221111"; card.ExpMonth = 12; card.ExpYear = 2010; card.CVVData = "123"; ICharge1.Card = card; Example: Using the Constructors: ICharge1.Card = new EPCard("4444333322221111", 12, 2010, "123");

Fields

Aggregate
String

This field allows you to get or set an XML aggregate built from all of the fields from this type. "EPCardType" is the root element, and the names of the fields create the tags under the root. For instance: <EPCardType> <Number>4444333322221111</Number> <CVV2Data>996</CVV2Data> <CVVIndicator>cvPresent</CVVIndicator> <ExpMonth>12</ExpMonth> <ExpYear>2010</ExpYear> <CardType>ctVisa</CardType> </EPCardType>

CardType
TCardTypes

Type of credit card being used in this transaction. This field contains the customer's credit card type. This is automatically computed after the Number is set, but it can also be changed manually. A list of valid card types is included below.

ctUnknown (0) Invalid or unknown prefix, card type not known.
ctVisa (1) Visa or Delta Card.
ctMasterCard (2) MasterCard.
ctAMEX (3) American Express Card.
ctDiscover (4) Discover Card.
ctDiners (5) Diners Club or Carte Blanche Card.
ctJCB (6) JCB Card.
ctVisaElectron (7) Visa Electron Card (runs as a Visa for most gateways)
ctMaestro (8) Maestro Card
ctLaser (10) Laser Card (Ireland)

CVVData
String

Three digit security code on back of card (optional).

This alphanumeric field contains the three digit Visa "Card Verification Value" (CVV), MasterCard "Card Verification Code" (CVC), or four-digit American Express "Card Identification Number" (CID). This value appears as additional characters embossed on the card signature line following the credit card account number on the back of the credit card. This is an optional field which can be used to determine if the customer is actually in possession of the credit card.

Even if the CVVData is incorrect, the transaction may still be authorized. It is up to the merchant to examine the ResponseCVVResult field and decide whether to honor the transaction or not.

Note: When set to a non-empty value, CVVPresence will be automatically set to cvpProvided. If set to empty string (""), CVVPresence will be automatically set to cvpNotProvided.

CVVPresence
CCCVVPresences

Indicates the presence of the card verification value.

This field is used to indicate the presence of CVVData.

The component will automatically set this value to cvpProvided when a CVVData value is specified. You can explicitly specify the CVVPresence indicator by setting this property.

Available values are:

  • cvpNotProvided (0)
  • cvpProvided (1)
  • cvpIllegible (2)
  • cvpNotOnCard (3)

ExpMonth
Integer

Expiration month of the credit card specified in Number.

This field contains the expiration date of the customer's credit card, and must be in the range 1 - 12.

ExpYear
Integer

Expiration year of the credit card specified in Number.

This field contains the expiration date of the customer's credit card. This field must be in the range 0 - 99, or 2000 - 2099. Any date before the year 2000 or after 2099 cannot be specified.

IsEncrypted
Boolean

Determines whether data set to the Number property is validated.

By default, when the Number field is set, the value will be validated and normalized. For instance, "4444-33332222 1111" will be normalized as "4444333322221111". However, any other non-numerical data entered will cause an exception to be thrown. It may be useful in some gateways to send other data in the Number field, and this can be accomplished by setting IsEncrypted to true. However, please note that in doing so automatic calculation of the CardType may be affected, and the card number will not be verified.

Number
String

Customer's credit card number for the transaction.

If you're sending the transaction with MagneticStripe data, this field should be left empty.

Constructors

public EPCard();
Public EPCard()
public EPCard(string number, int expMonth, int expYear);
Public EPCard(ByVal Number As String, ByVal ExpMonth As Integer, ByVal ExpYear As Integer)
public EPCard(string number, int expMonth, int expYear, string CVVData);
Public EPCard(ByVal Number As String, ByVal ExpMonth As Integer, ByVal ExpYear As Integer, ByVal CVVData As String)

EPCustomer Type

Contains customer information.

Remarks

This type contains information about the customer which the merchant has collected. At the minimum, this should include the customer's name and address. You may also optionally include a merchant-generated customer Id, the customer's Email address, Phone number, and Fax number. This type is used by both the ICharge and ECheck components.

Example: EPCustomer cust = new EPCustomer(); cust.FirstName = "John" cust.LastName = "Smith" cust.FullName = "John M. Smith" cust.Address = "123 Nowhere Ln." cust.City = "Beverly Hills" cust.State = "CA" cust.Zip = "90210" cust.Country = "USA" cust.Phone = "555-555-5555" cust.Email = "jsmith@fake.com" cust.Id = "123456" ICharge1.Customer = cust;

Fields

Address
String

Customer's street address. This field is used as part of the Address Verification Service (AVS) and contains the customer's street address as it appears on their monthly statement. Only the street number, street name, and apartment number are required in This field. City, state, and zip code are set in the City, State, and Zip fields.

The length of this field varies by gateway. If the customer's address is very long, it is admissible to include only the street number in This field.

NOTE: For the Moneris gateway, this field should contain only the customer's street number. The street name should be added via the AddSpecialField method. For example:

component.Customer = new EPCustomer(); component.Customer.Address = "123"; component.AddSpecialField("avs_street_name, "Nowhere Ln");

Address2
String

A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.).

Aggregate
String

This field allows you to get or set an XML aggregate built from all of the fields from this type. "EPCustomer" is the root element, and the names of the fields create the tags under the root. For instance: <EPCustomer> <Address>123 Nowhere Ln.</Address> <Address2>Apt 3B.</Address2> <City>Beverly Hills</City> ... </EPCustomer>

City
String

Customer's city. This field is used as part of the Address Verification Service (AVS) and contains the customer's city as it appears on their monthly statement. Other AVS fields include Address, State, and Zip.

Country
String

Customer's country. This field contains the country in which the customer is located. Most gateways use a two-letter country code, specified in ISO-3166.

Note: If using this field with the PayFuse gateway, this field should contain the ISO-3166 numeric code instead of the standard two-letter code. For example, the ISO code for the US is "840".

Email
String

Customer's email address. This optional field contains the customer's email address.

Fax
String

Customer's fax number. This optional field contains the customer's fax number.

FirstName
String

Customer's first name. This field contains the customer's first name.

FullName
String

Customer's full name. This field contains the customer's full name as it appears on the credit card or bank account. Many gateways use this field in addition to, or instead of, the FirstName and LastName fields. If a gateway requires a FullName and the field is empty, FullName will be constructed using the contents of FirstName and LastName.

Id
String

Merchant-generated customer Id. This field contains a merchant-generated customer identification number. This number should be unique for each different customer that places an order with the merchant.

LastName
String

Customer's last name. This field contains the customer's last name as it appears on their credit card.

Phone
String

Customer's phone number. This optional field contains the customer's phone number.

State
String

Customer's state. This field is used as part of the Address Verification Service (AVS) and contains the two character postal abbreviation of the customer's state as it appears on their monthly statement. Other AVS fields include Address, City, and Zip.

Zip
String

Customer's zip code (or postal code if outside of the USA). This field is used as part of the Address Verification Service (AVS), and contains the customer's zip code as it appears on their monthly statement. Other AVS fields include Address, City, and State.

Constructors

public EPCustomer();
Public EPCustomer()

EPResponse Type

Contains the response to the authorization.

Remarks

This type contains the results of a transaction made with the ICharge, Retail, and ECheck components. The fields contained by this type are listed below.

Fields

ApprovalCode
String

Contains an authorization code when a transaction has been approved. This field contains an authorization code when a transaction has been approved. If the Code returned indicates that the transaction is not approved, then the contents of this field should be ignored.

Approved
Boolean

Indicates the status of the last transaction. This field will be True if the last transaction was approved. However, you should not rely solely on the value contained in this property. After every transaction, the Code should be inspected and evaluated according to the specifications of the Gateway in use. A list of response codes for each gateway is listed in the table of contents. However, it is recommended that the developer acquire the current list from the Gateway which is being used.

ApprovedAmount
String

The amount approved for the transaction, this is the amount actually charged to the credit card.

This field is primarily used when gateways allow partial authorizations and AllowPartialAuths is 'True'. Thus this field is not used by all gateways and should not alone be used to determine if a transaction was successful (such as in the case that this field is not populated).

AVSResult
String

Contains the Address Verification System result code. This one character field contains the Address Verification Service (AVS) result code. An AVS result code can provide additional information concerning the authentication of a particular transaction for which cardholder address verification was requested. An AVS result code of "0" will be returned in the response message when no address verification has been requested. The value returned should be stored for later retrieval, as it may be required when voiding or refunding a transaction. Valid AVS response codes are listed below, and are identical across all Gateway (note that some gateways do not return an AVS response).

AVSResultDescription
AAddress matches, Zip does not.
EAVS error.
GNon-U.S. issuing bank does not support AVS.
NNo match on Address or CustomerZip.
PAVS not applicable for this transaction.
RRetry - Issuer system unavailable.
SService not supported by issuer.
UAddress information is unavailable.
WNine digit Zip matches, Address does not.
XExact AVS match, nine digit Zip.
YExact AVS match, five digit Zip.
ZFive digit Zip matches, Address does not.

Note: Some gateways use their own response codes instead of those in the above table; those response codes are detailed below for such gateways.

Adyen

For Adyen, this field will contain the following possible values:

0Unknown
1Address matches, postal code doesn't
2Neither postal code nor address match
3AVS unavailable
4AVS not supported for this card type
5No AVS data provided
6Postal code matches, address doesn't match
7Both postal code and address match
8Address not checked, postal code unknown
9Address matches, postal code unknown
10Address doesn't match, postal code unknown
11Postal code not checked, address unknown
12Address matches, postal code not checked
13Address doesn't match, postal code not checked
14Postal code matches, address unknown
15Postal code matches, address not checked
16Postal code doesn't match, address unknown
17Postal code doesn't match, address not checked
18Neither postal code nor address were checked

American Payment Solutions

For American Payment Solutions, this field will contain the following possible values:

XExact match, 9-character numeric ZIP
Y, D, or MExact match, 5-character numeric ZIP
2 or 6Exact match, 5-character numeric ZIP, customer name
A or BAddress match only
3 or 7Address, customer name match only
W9-character numeric ZIP match only
Z, P, or L5-character ZIP match only
1 or 55-character ZIP, customer name match only
N or CNo address or ZIP match only
4 or 8No address or ZIP or customer name match only
UAddress unavailable
G or INon-U.S. issuer does not participate
RIssuer system unavailable
ENot a mail/phone order
SService not supported
0, O, or BAVS not available

Barclay

For Barclay, the field will contain the following possible values:

YYAddress and zip code or postal code match
YNAddress matches only
NYZip code or postal code matches
NNNeither address nor zip code or postal code matches; address is not parsable
UUAddress information is unavailable, service is unavailable, or Error; Unknown
BlankNo AVS performed

BlueSnap

For BlueSnap, the field will contain a 3-character string (if AVS checks were done), which contains the AVS checks for the following fields:

1st CharacterName AVS check
2nd CharacterAddress AVS check
3rd CharacterPostal/Zip Code AVS check

The possible values for each result character are:

MMatches
NDoes not match
UCould not be verified

HSBC

For HSBC, the field will contain the following possible values:

YYAddress and zip code or postal code match
YNAddress matches only
NYZip code or postal code matches
NNNeither address nor zip code or postal code matches; address is not parsable
UUAddress information is unavailable, service is unavailable, or Error; Unknown
FFIssuer does not participate in AVS
BlankNo AVS performed

PayTrace / PayTraceJSON

For PayTrace / PayTraceJSON, the field will contain the following possible values:

Full Exact Match
Address Match Only
Zip Match Only
No Match
Address Unavailable
Non-US Issuer does not participate
Issuer System Unavailable
Not a Mail/Phone Order
Service Not Supported

QBMS

For the QBMS gateway, the AVSResult field will contain the result for the street address, a comma, and then the result for the zip code. The values returned are "Pass", "Fail", and "NotAvailable". Therefore, an AVSResult of "Fail,Pass" means that the street address failed validation, but the zip code passed.

DataCash

For DataCash, the field will contain the following possible values (of which correspond to both AVS and CVV checks):

NO DATA MATCHES
ADDRESS MATCH ONLY
SECURITY CODE MATCH ONLY
ALL MATCH
DATA NOT CHECKED

Stripe

For Stripe, the field will contain the following possible values:

Pass The first address line or zip code provided is correct.
Fail The first address line or zip code provided is incorrect.
Unavailable The customer's bank did not check the first address line or zip code provided.
Unchecked The first address line or zip code was provided but has not yet been checked.

Worldpay

For Worldpay, the field will contain a 4-character string, which contains the AVS checks for the following fields:

1st CharacterCard Verification Value (CVV) check
2nd CharacterPostal/Zip Code AVS check
3rd CharacterAddress AVS check
4th CharacterCountry Comparison check

The possible values for each result character are:

0Not Supported.
1Not Checked.
2Matched.
4No Match.
8Partial Match.

Worldpay Online

For Worldpay Online, the field will contain one of the following:

ValueDescription
APPROVED The supplied street and postal code details fully matched the payment provider's records
PARTIAL APPROVED One of the supplied street or postal code details did not match the payment provider's records
NOT SENT TO ACQUIRER Problem with acquirer - possibly no AVS support
NO RESPONSE FROM ACQUIRERProblem with acquirer - possibly no AVS support
NOT CHECKED BY ACQUIRER The acquirer did not check the address details
NOT SUPPLIED BY SHOPPER Missing, incomplete or invalid address details in the order prevented the address from being checked
FAILED Both street and postal code details did not match the payment provider's records

Code
String

Indicates the status of the authorization request. This field contains the actual response code as returned by the Gateway. Unlike the Approved field, this Code field may provide more details about why a transaction was declined. Therefore, it is recommended that developers check the Code as well as the Approved field. The Point of Sale system should evaluate this response code and NOT the Text to determine nature of a response message. The current (at the time of this release) response codes for the supported Gateways are listed in the table of contents to your left.

CVVResult
String

Contains the returned CVV2 result code if it was requested. This field contains the host returned CVV2 result code (if CVV data was sent in the request). The following is a list of current result codes:

MCVV2 Match.
NCVV2 No Match.
PNot Processed.
SMerchant has indicated that CVV2 is not present on card.
UIssuer not certified and/or has not provided Visa encryption keys.

A gateway may also support custom codes or human-readable response messages in this field. Please consult your gateway documentation to determine if CVV2 codes are supported.

Note: Some gateways use their own response codes instead of those in the above table; those response codes are detailed below for such gateways.

HSBC

For HSBC, the field will contain:

0Card type does not support CVM
1CVM match
2CVM did not match issuer value
3CVM was not processed
4CVM should be on the card but cardholder indicated otherwise
5CVM not supported by issuer
6Not valid
7No response from server

Adyen

For Adyen, the field will contain:

0Unknown
1Matches
2Does not match
3Not checked
4No CVC/CVV provided, but was required
5Issuer not certified for CVC/CVV
6No CVC/CVV provided

Barclay

For Barclay, the field will contain:

0,1CVM was not processed
2CVM match
4CVM does not match issuer value
UnknownCVM invalid or missing
BlankNo response from server

BlueSnap

For BlueSnap, the field will contain:

MAMatch
NCIssuer is not certified for CVV2/CVC2/CID
NDCheck was not done
NMNo match
NPCVV2/CVC2/CID should be on the card but is not present
NRCVV check not requested

(Note: There are some scenarios in which the field will be empty instead, refer to BlueSnap's documentation for more details.)

DataCash

For DataCash, the field will contain the following possible values (of which correspond to both AVS and CVV checks):

NO DATA MATCHES
ADDRESS MATCH ONLY
SECURITY CODE MATCH ONLY
ALL MATCH
DATA NOT CHECKED

Stripe

For Stripe, the field will contain the following possible values:

Pass The CVC provided is correct.
Fail The CVC provided is incorrect.
Unavailable The customer's bank did not check the CVC provided.
Unchecked The CVC was provided but has not yet been checked.

Worldpay Online

For Worldpay Online, the field will contain one of the following:

ValueDescription
APPROVED The supplied CVC details matched the payment provider's records
NOT SENT TO ACQUIRER Problem with acquirer - possibly no CVC support
NO RESPONSE FROM ACQUIRERProblem with acquirer - possibly no CVC support
NOT CHECKED BY ACQUIRER The acquirer did not check the CVC details
NOT SUPPLIED BY SHOPPER Missing, or invalid CVC in the payment details prevented the CVC from being checked
FAILED The supplied CVC did not match the payment provider's records

Data
String

The entire response returned from the gateway processor. This field contains the entire response returned from the gateway processor. You may use this to parse additional information that is not returned in the standard response fields.

ErrorCode
String

Additional error code returned by some gateways. If a gateway returns it, this field will contain an additional code that may explain why the transaction was declined. You may also wish to inspect ErrorText for a human-readable description of this ErrorCode.

ErrorText
String

Additional error description returned by some gateways. If a gateway returns it, this field will contain a human-readable description of the error which occurred (if any). You may also wish to inspect ErrorCode for an accompanying code which may be parsed and used by your application.

InvoiceNumber
String

Invoice number submitted in authorization request (if applicable). This field contains the Invoice Number submitted in the original transaction, echoed back by the Gateway host.

ProcessorCode
String

Response code from the underlying processor. Often times a Gateway will return a Code that indicates only whether the transaction is approved or declined. Many of these also include a secondary code that provides more details as to why the transaction was declined.

Note, for the PayFlowPro Gateway this field will contain a "1" if the transaction was a duplicate, a "-1" if duplicate checking service is unavailable, and will be blank for a successfully authorized transaction.

Text
String

Text information that describes each response code. This field contains a response or display text message. This message can be used by the terminal to display the authorization result. The display text must not be used to determine the nature of a response message. A Gateway may translate the response according to the language indicated in the merchant account setup (if applicable).

TransactionId
String

Contains the Visa Transaction Identifier or MasterCard Reference Number. This field contains a transaction identifier or reference number. The Point of Sale (POS) device should not attempt to interpret the meaning of any data appearing in this field. Data returned in this field (if any) should be recorded and used to submit a modification of this transaction at a later time (such as voiding the transaction or capturing an authorization-only transaction, if applicable).

Constructors

public EPResponse();
Public EPResponse()

EPShipInfo Type

Contains shipping information.

Remarks

This type contains the shipping information which the merchant has collected. Shipping information is typically optional data. This type is used by the ICharge components.

Example: EPShipInfo shipInfo = new EPShipInfo(); shipInfo.FirstName = "John" shipInfo.LastName = "Smith" shipInfo.Address = "123 Nowhere Ln." shipInfo.City = "Beverly Hills" shipInfo.State = "CA" shipInfo.Zip = "90210" shipInfo.Country = "USA" shipInfo.Phone = "555-555-5555" ICharge1.ShippingInfo = shipInfo;

Fields

Address
String

Customer's shipping street address.

Address2
String

A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.).

City
String

Customer's shipping city.

Country
String

Customer's shipping country. This field contains the country in which the customer is located. Most gateways use a two-letter country code, specified in ISO-3166.

Email
String

Customer's email address.

FirstName
String

Customer's first name.

LastName
String

Customer's last name.

Phone
String

Customer's phone number.

State
String

Customer's shipping state.

Zip
String

Customer's shipping zip code (or postal code if outside of the USA).

Constructors

public EPShipInfo();
Public EPShipInfo()

EPSpecialField Type

Additional name/value pairs which can be added to a transaction.

Remarks

This type contains a Name and Value which may contain any additional information you wish to send to your gateway that this component does not currently send. You must know the field name in the gateway integration guide available from your gateway. For instance, the code below shows how to add a customer IP Address for the Authorize.Net gateway:

ICharge1.SpecialFields.add(new EPSpecialField("x_customer_ip", "255.123.456.78"));

Fields

Name
String

Name of special configuration field to submit in this transaction. The Name and Value fields can be used to send special gateway configuration and transaction fields for each transaction. These fields can also be used to extend the functionality of this component by submitting additional information to the gateway.

This field is not applicable for the LinkPoint, FirstData, YourPay, PayFuse, or Orbital gateways.

Value
String

Value of special configuration field to submit in this transaction. The Name and Value fields can be used to send special gateway configuration and transaction fields for each transaction. These fields can also be used to extend the functionality of this component by submitting additional information to the gateway.

Note: This field is not applicable for the LinkPoint, FirstData, YourPay, PayFuse, or Orbital gateways.

Constructors

public EPSpecialField();
Public EPSpecialField()
public EPSpecialField(string name, string value);
Public EPSpecialField(ByVal Name As String, ByVal Value As String)

Proxy Type

This is the proxy the component will connect to.

Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the Server and the AuthScheme.

Fields

AuthScheme
ProxyAuthSchemes

This field is used to tell the component which type of authorization to perform when connecting to the proxy. This is used only when the User and Password fields are set.

AuthScheme should be set to authNone (3) when no authentication is expected.

By default, AuthScheme is authBasic (0), and if the User and Password fields are set, the component will attempt basic authentication.

If AuthScheme is set to authDigest (1), digest authentication will be attempted instead.

If AuthScheme is set to authProprietary (2), then the authorization token will not be generated by the component. Look at the configuration file for the component being used to find more information about manually setting this token.

If AuthScheme is set to authNtlm (4), NTLM authentication will be used.

For security reasons, setting this field will clear the values of User and Password.

AutoDetect
Boolean

This field tells the component whether or not to automatically detect and use proxy system settings, if available. The default value is false.

Password
String

This field contains a password if authentication is to be used for the proxy.

If AuthScheme is set to Basic Authentication, the User and Password are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].

If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.

If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.

Port
Integer

This field contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80). See the description of the Server field for details.

Server
String

If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.

If the Server field is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the Server field is set to the corresponding address. If the search is not successful, an error is returned.

SSL
ProxySSLTypes

This field determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. The applicable values are as follows:

psAutomatic (0)Default setting. If the URL is an https URL, the component will use the psTunnel option. If the URL is an http URL, the component will use the psNever option.
psAlways (1)The connection is always SSL enabled.
psNever (2)The connection is not SSL enabled.
psTunnel (3)The connection is made through a tunneling (HTTP) proxy.

User
String

This field contains a user name, if authentication is to be used for the proxy.

If AuthScheme is set to Basic Authentication, the User and Password are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].

If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.

If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.

Constructors

public Proxy();
Public Proxy()
public Proxy(string server, int port);
Public Proxy(ByVal Server As String, ByVal Port As Integer)
public Proxy(string server, int port, string user, string password);
Public Proxy(ByVal Server As String, ByVal Port As Integer, ByVal User As String, ByVal Password As String)

Config Settings (ICharge Component)

The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

iCharge Config Settings

3DSAuthenticationStatus:   Indicates whether a transaction qualifies as a ThreeDSecure (3DS) authenticated transaction.

This setting is used to pass the 3D Secure authentication status on to the transaction server. This component may be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. Other values necessary for passing 3D Secure data include 3DSCAVV, 3DSXID and 3DSECI. This setting is only valid for E-Commerce transactions. Applicable values are:

YThe customer was successfully authenticated.
NThe customer failed authentication, and the transaction is denied.
UAuthentication could not be performed due to technical or other problems.
AAuthentication was not available, but functionality was available (through the issuer, Visa, or a third party) to generate a proof of authentication attempt.

3DSCAVV:   Cardholder Authentication Verification Value from a 3D Secure authentication.

This setting is used to pass 3D Secure CAVV data on to the transaction server. This field must be formatted as a 28-byte Base-64 encoded value. This component may be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. Other values necessary for passing 3D Secure data include 3DSXID and 3DSECI. This setting is only valid for E-Commerce transactions.

3DSDSTransactionId:   Directory server transaction Id from a 3D Secure authentication.

This setting is used to pass the directory server transaction Id to the gateway for 3DS 2.0. This component may be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. This setting is only valid for E-Commerce transactions. This setting is currently only supported when the Gateway property is set to gwNetbanx.

3DSECI:   Electronic Commerce Indicator.

This contains a 1-character transaction indicator identifying the type of transaction being authorized. Supported values vary between gateways, so please consult gateway documentation for more information. Note: Other values necessary for passing 3D Secure data are 3DSXID and 3DSCAVV. This setting is only valid for E-Commerce transactions.

3DSEnrollmentStatus:   Indicates whether 3D Secure authentication is available for the cardholder.

This setting is used to pass the cardholder's 3D Secure enrollment status to the gateway for 3D Secure 1.0.2. This component may be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. This setting is only valid for E-Commerce transactions. This setting is currently only supported when the Gateway property is set to gwNetbanx.

3DSXID:   TransactionId from a 3D Secure authentication.

This setting is used to pass the 3D Secure TransactionId (XID) data on to the gateway. This setting must be formatted as a 20-byte plaintext value, or a 28-byte Base-64 encoded value. This component may be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. For example: Other settings necessary for passing 3D Secure data are 3DSCAVV and 3DSECI. This setting is only valid for E-Commerce transactions.

AdyenShopperInteraction:   Specifies the sales channel the shopper gives their card details through.

This configuration setting is used to specify the sales channel the shopper gives their card details through and whether the shopper is a returning customer. Default value is 0.

Available values are:

Value Description
0 E-Commerce
1 ContAuth
2 POS
3 Moto

AllowPartialAuths:   Specifies whether partial authorizations are allowed.

When set to 'True', partial authorizations will be allowed and must be handled accordingly. A partial authorization occurs when a customer's available funds for a specific card can only meet a portion of the total TransactionAmount. Therefore a second means of payment must be used to pay for the remaining amount. When such a case occurs, the partially approved amount will be made available via ApprovedAmount. When set to 'False', if a customer's card does not have funds the available to account for the entire TransactionAmount the transaction will be declined. The default value is 'True'.

AmountFormat:   Used to set the input format for TransactionAmount.

This configuration setting can be used to specify a single input format for the TransactionAmount property. When set to a value other than 0, the component will automatically convert the amount from the specified format to the format expected by the gateway. Valid values are:

Value Format
0 Unspecified (default)
1 Dollars (1.00)
2 Cents (100)

Note that this setting is only designed for use with currencies that have two digits after the decimal point, like US dollars.

ApplePayData:   The Base-64 encoded data containing the encrypted payment data from Apple for use when performing Apple Pay transactions.

This setting specifies the Base-64 encoded data containing the encrypted payment data received from Apple. The encrypted payment data must be retrieved in a separate process by communicating with the Apple Passbook app. Once the encrypted payment data is received from Apple set this configuration setting, which takes the place of Card, and perform either an AuthOnly or Sale transaction to process the payment.

This setting is applicable to the following gateways:

  • Authorize.NET (gwAuthorizeNet)
  • BlueSnap (gwBlueSnap)

APSRequestType:   Specifies the request type to use for the American Payment Solutions gateway.

This config is used to specify the type of request which will occur when the Sale method is called. By default it is set to Normal (0), in which case the component will send a normal transaction sale request.

The other options are used to instruct the component to send the appropriate type of request needed to query, create, update, or delete a customer vault record when Sale is called.

Possible values for this setting are:

  • 0 - Normal (default)
  • 1 - Add Customer Vault Record
  • 2 - Update Customer Vault Record
  • 3 - Delete Customer Vault Record
  • 4 - Query Customer Vault Record

Please see the gateway setup information for American Payment Solutions for more details on how to use the ICharge component to work with customer vault records. Refer to American Payment Solutions' documentation for more information about the customer vault in general.

AuthNetBillToCompany:   The company that should be included with the customer's information for the Authorize.NET XML gateway.

This configuration setting is used to specify the company in the billing information for the customer.

Note that this is only valid when the Gateway property is set to gwAuthorizeNetXML.

AuthNetCIMPaymentProfileId:   The Payment Profile ID assigned by Authorize.NET CIM gateway.

This config is used to specify the ID of a payment profile to be used to perform a transaction. A payment profile is tied to a AuthNetCIMProfileId and is used to identify the payment option to charge. With the Authorize.NET CIM gateway, transactions are performed using profiles to access customer information stored on their Customer Information Manager (CIM) instead of sending raw card and billing data with the transaction. Therefore this property is required. Note: The RecurringBilling component can be used to manage payment profiles.

AuthNetCIMProfileId:   The Profile ID assigned by Authorize.NET CIM gateway.

This config is used to specify the ID of a profile to be used to perform a transaction. A profile is used to identify the customer initiating the transaction. With the Authorize.NET CIM gateway, transactions are performed using profiles to access customer information stored on their Customer Information Manager (CIM) instead of sending raw customer data with the transaction. Therefore this property is required. Note: The RecurringBilling component can be used to manage profiles.

AuthNetCIMProfileResponse:   Profile creation response.

When requesting a CIM profile to be created by setting the AuthNetCreateCIMProfile configuration setting to True, this configuration setting will contain the response. For Example: icharge.Config("AuthNetCreateCIMProfile=True"); icharge.Sale(); Console.WriteLine(icharge.Config("AuthNetCIMProfileResponse"));

Note that this is read-only and only valid when Gateway property is set to gwAuthorizeNetXML.

AuthNetCIMShippingAddressId:   The Shipping Address ID assigned by Authorize.NET CIM gateway.

This config is used to specify the ID of a shipping address profile to be used to perform a transaction. A shipping address profile is tied to a AuthNetCIMProfileId and is used to identify the shipping location of the item purchased in the current transaction. With the Authorize.NET CIM gateway, transactions are performed using profiles to access shipping information stored on their Customer Information Manager (CIM) instead of sending raw shipping data with the transaction. This property is optional. If an shipping address ID is not specified, shipping information will not be included with the transaction. Note: The RecurringBilling component can be used to manage shipping address profiles.

AuthNetCreateCIMProfile:   Whether to create a CIM Profile.

Whether to create a CIM profile for the customer during a Sale or AuthOnly transaction. By default this configuration setting is set to False. When set to True, the response for the profile creation will be returned in the AuthNetCIMProfileResponse configuration setting. For Example: icharge.Config("AuthNetCreateCIMProfile=True"); icharge.Sale(); Console.WriteLine(icharge.Config("AuthNetCIMProfileResponse"));

Note that this is only valid when the Gateway property is set to gwAuthorizeNetXML.

AuthNetCryptogram:   Tokenized credit card cryptogram.

This configuration setting is used to specify the value of the cryptogram received from the token provider. This configuration setting is required when AuthNetTokenizedCard configuration setting is set.

Note that this is only valid when calling Sale method and the Gateway property is set to gwAuthorizeNetXML.

AuthNetCustomerType:   Specifies the customer type for the Authorize.NET XML gateway.

This configuration setting is used to specify the customer type to send during a request to the Authorize.NET XML gateway. Default value is 0.

Available values are:

Value Description
0 Not sent (Default)
1 Individual
2 Business

AuthNetOpaqueDescriptor:   An Authorize.Net opaque data descriptor.

This setting can be set to an Authorize.Net opaque data descriptor in order to use it in place of explicit card or bank account information. AuthNetOpaqueValue must also be set.

This setting is only valid with the gwAuthorizeNetXML and gwAuthorizeNetCIM gateways, it cannot be used with the gwAuthorizeNet gateway.

AuthNetOpaqueValue:   An Authorize.Net opaque data value.

This setting can be set to an Authorize.Net opaque data value in order to use it in place of explicit card or bank account information. AuthNetOpaqueDescriptor must also be set.

This setting is only valid with the gwAuthorizeNetXML and gwAuthorizeNetCIM gateways, it cannot be used with the gwAuthorizeNet gateway.

AuthNetShipToCompany:   The name of the company associated with the customer's shipping address.

This configuration setting can be used to set the company associated with the shipping address of the customer.

AuthNetSplitTenderId:   Authorize.Net assigned id for partially authorized transactions.

When AllowPartialAuths configuration setting is set to true and there are not enough funds to cover the full transaction amount set using the TransactionAmount property, Authorize.NET will return a Split Tender Id that can be later used, to link to the original partially authorized transaction, to charge the full amount, void, or capture.

AuthNetTokenizedCard:   The credit card token.

This configuration setting is used to specify the credit card token to perform a Sale transaction.

Note that this is only valid when calling Sale method and the Gateway property is set to gwAuthorizeNetXML.

BamboraPasscode:   The API passcode used for authentication with Bambora.

This configuration setting is used to set the API passcode when using the passcode option for authentication with Bambora.

BankName:   Name of the card issuer.

This configuration setting is required for some merchants when calling the Sale method, and must be set to the name of the card issuer. For example: icharge.Config("BankName=Wells Fargo"); icharge.Sale();

BarclayKeepTransactionOpen:   Determines whether to perform a maintenance transaction that keeps the transaction open for further processing with the Barclay and Ingenico gateways.

By default (value of 'False'), all maintenance transactions (such as Capture, Refund, and VoidTransaction) will close the transaction after the operation is performed. When set to 'True', the operation will be performed and the transaction will be left open for further processing. This config works in conjunction with the following methods:

AuthOnly

BarclayKeepTransactionOpen Transaction Type
False RES: request for authorization
True REN: renewal of authorization, if the original authorization is no longer valid.

Capture

BarclayKeepTransactionOpen Transaction Type
False SAS: (last) partial or full data capture (payment), closing the transaction (for further data captures) after this data capture.
True SAL: partial data capture (payment), leaving the transaction open for a possible other data capture.

Refund

BarclayKeepTransactionOpen Transaction Type
False RFS: (last) partial or full refund (on a paid order), closing the transaction after this refund.
True RFD: partial refund (on a paid order), leaving the transaction open for a possible other refund.

VoidTransaction

BarclayKeepTransactionOpen Transaction Type
False DES: delete authorization, closing the transaction after this operation.
True DEL: delete authorization, leaving the transaction open for possible further maintenance operations.

BarclayPartialRefund:   Determines whether to send a partial or full refund transaction with the Barclay and Ingenico gateways.

By default (value of 'False'), the Refund method will send a partial or full refund which closes the transaction. When this setting is set to 'True', a partial refund transaction will be sent and the transaction will be left open for another potential refund.

BASYSCardInfoKey:   BASYS Gateway Credit Card Profile Id.

If BASYSProcessRecurringCredit is set to True this must be set to the credit card profile id value assigned to the payment method when it was added to the system.

Note: BASYSCardInfoKey can be obtained via the RecurringBilling component.

BASYSProcessRecurringCredit:   Determines whether to process the transaction via Credit Card Profile Id.

Determines whether to process the transaction via customer's Credit Card profile. By default this configuration setting is set to False. If set to True, BASYSCardInfoKey and MerchantCode configuration settings must also be set. For instance: icharge.Config("MerchantCode=YourBASYSMerchantKey"); icharge.Config("BASYSProcessRecurringCredit=True"); icharge.Config("BASYSCardInfoKey=YourBASYSCardInfoKey"); icharge.TransactionAmount = "1.00"; icharge.Sale();

BASYSProcessTokenCredit:   Determines whether to process the transaction using a Credit Card Token.

Determines whether to process the transaction using a Credit Card Token provided by BASYS Gateway. By default this configuration setting is set to False. If set to True, BASYSTokenMode and BASYSToken must also be set. For Instance: icharge.Config("BASYSProcessTokenCredit=True"); icharge.Config("BASYSToken=YourToken"); icharge.TransactionAmount = "1.00"; icharge.Sale();

BASYSToken:   BASYS Gateway Credit Card Token.

If BASYSProcessTokenCredit is set to True, this must be set to the token value assigned to the payment method when it was added to the system.

Note: BASYSToken can be obtained via the RecurringBilling component.

BASYSTokenMode:   Indicates the type of token that is being used for the transaction.

Indicates the type of token that is being used for the transaction. If BASYSProcessTokenCredit is set to True this must be set to one of the following values.

Possible values:

Value Description
0 Default (BASYS Gateway Default Format).
1 Card Format.

BASYSVoidMode:   Indicates whether to perform a Void or Reversal.

If BASYSVoidMode is set to "0" (default), VoidTransaction sends a void to undo an unsettled transaction. If BASYSVoidMode is set to "1" (Reversal), this ensures the transaction is unsettled and also removes the authorization from the issuing bank.

Possible values:

Value Description
0 Void (Default).
1 Reversal.

BluefinReversal:   Determines which transaction type will be use for VoidTransaction with the Bluefin gateway.

By default, when VoidTransaction is called with gwBluefin selected the request will use the REFUND transaction type, which is used to void an unsettled Sale transaction. Set this configuration setting to True to use the REVERSAL transaction type instead, which will void an uncaptured authorization. Note that the REVERSAL transaction type may or may not be allowed depending on the payment processor for the account.

BluePayMasterId:   Used to reference a previous transaction in BluePay.

This setting takes a previous transaction's TransactionId. For any parameters that are not set, BluePay will use values from the referenced transaction.

BluePayUpdate:   Used to perform an Update transaction for BluePay.

When set to true, the component will update a prevous transaction when the Sale method is called. BluePayMasterId must be set to the TransactionId of the previous request, and the transaction can only be updated before it has been settled by BluePay.

BlueSnapEnterpriseUdfs:   User-Defined Fields (UDFs) to send with a BlueSnap Sale or AuthOnly request.

This setting can be set to a JSON object like the following one in order to send Enterprise UDFs when calling Sale or AuthOnly: {"udf": [ { "udfValue": "aaa", "udfName": "ENT_UDF1" }, { "udfValue": "bbb", "udfName": "ENT_UDF2" } ]} Note: Content set using this setting will be used as the value of the transactionFraudInfo.enterpriseUdfs JSON field in the request body; it is not validated or manipulated first, it is used "as-is".

BlueSnapGetToken:   Retrieves a new hosted payment fields token (pfToken) from BlueSnap.

Each time this setting is queried, it will retrieve a new pfToken from BlueSnap. This token can then be passed to BlueSnap's hosted payment fields libraries, and then later passed in the transaction request using the special field pfToken or securityCodePfToken. Refer to BlueSnap's documentation for more information about hosted payment fields.

BlueSnapRetrieveTransaction:   Retrieves a BlueSnap transaction.

Setting this to a card transaction ID (or querying it with the TransactionId property set) will cause the component to retrieve the associated transaction and populate its fields accordingly. Please refer to the BlueSnap section of the "ICharge Gateway Setup and Required Properties" page for more information on how the component's fields map to BlueSnap's fields.

BlueSnapTransactionMetaData:   Transaction metadata to send with a BlueSnap Sale or AuthOnly request.

This setting can be set to a JSON object like the following one in order to send Enterprise UDFs when calling Sale or AuthOnly: {"metaData": [ { "metaValue": 20, "metaKey": "stateTaxAmount", "metaDescription": "State Tax Amount" }, { "metaValue": 20, "metaKey": "cityTaxAmount", "metaDescription": "City Tax Amount" }, { "metaValue": 10, "metaKey": "shippingAmount", "metaDescription": "Shipping Amount" } ]} Note: Content set using this setting will be used as the value of the transactionMetaData JSON field in the request body; it is not validated or manipulated first, it is used "as-is".

CardholderPresentCode:   Specifies the way in which transaction took place.

This config allows you to specify the way in which the transaction took place. This config is applicable to the Barclay, HSBC, and PayFuse gateways.

Applicable values are:

Value Description
1 Cardholder present (Default value sent by the Retail component when MagneticStripe data specified)
2 Cardholder present, signature obtained
3 Cardholder not present, unspecified/unknown
4 Cardholder not present, mail/fax order
5 Cardholder not present, telephone
6 Cardholder not present, standing authorization (installment)
7 Cardholder not present, electronic transaction (Default value sent by the ICharge component)
8 Cardholder not present, recurring billing
9 Address used for Id
10 Card not present (installment)
11 Card not present (SET, with Merchant and cardholder certificate)
12 Card not present (SET with Merchant certificate only)
13 Card not present, but payer authentication was used
14 Cardholder present, but card information manually keyed (Default value sent by the Retail component when card is manually entered)

CardIssueNumber:   Special Issue Number used for Switch and Solo cards.

This field is used for the gateways the support International card types. Supported gateways include: Adyen, Barclay, CyberSource, FastTransact, HSBC, NetBanx, NetBilling, Orbital, PayFuse, PaymentExpress, PayPoint, PlugNPay, SagePay, SECPay, and WorldPayXML. Switch, Solo, and some Maestro cards have a 1 or 2 digit Issue number printed on the front of the card, directly following the card number. If that issue number is present, it should be set with this config setting.

CardLast4Digits:   The last 4 digits of a credit card.

This configuration setting is used to specify the last 4 digits of the credit card in certain scenarios.

CardPointeEncryptionHandler:   The encryption handler to use when requesting a token from CardPointe.

This configuration setting is used to specify the encryption handler when requesting a token from CardPointe (gwCardPointe). This should be set to "RSA" if using a private key provided by CardPointe to encrypt the account value before sending. If the account value in the token request is not encrypted, this setting is not necessary.

CardPointeGetToken:   Retrieves an account token from CardPointe.

This configuration setting is used to request a token from CardPointe (gwCardPointe). If CardToken is set, it will be used for the account in the request. If not, Number will be used instead.

CardStartMonth:   Used for some international cards.

If there is a Start Date present on the card, set the month here and the year in CardStartYear.

CardStartYear:   Used for some international cards.

If there is a Start Date on present on the card, set the year here and the month in CardStartMonth.

CardToken:   The credit card token.

This configuration setting is used to specify the credit card token (sometimes called a "nonce") to perform a transaction.

Note that this is only valid when the Gateway property is set to gwConverge, gwMoneris, gwNuvei, gwSquare, gwSquarePayments, gwStripe, or gwQBPayments.

CAVVResponse:   Contains CAVV response value returned by the gateway.

This property will contain the CAVV response value to the authorization and will be populated along with Response. Values vary between gateways, so please consult gateway documentation for more information.

COFPermission:   Indicates if the customer gave permission to make a Card On File transaction.

When true, this setting indicates that the customer gave the merchant permission to perform a Card On File (COF) transaction. Currently only used by CardPointe (gwCardPointe).

ConvenienceFee:   The total convenience fee charged for a transaction.

This field is used to specify the total convenience fee charged for the transaction. This field is applicable to the FirstDataPayPoint and Litle / Vantiv gateway.

ConvergeTokenMode:   Used to request a token from the Converge gateway.

This configuration setting is used to request a token when making a request to gwConverge. If this is set to 1 or 2 before calling Sale or AuthOnly, Converge will return a token in the response, which will be available through the CardToken configuration setting.

Possible values for this setting are:

  • 0 - Don't request a token (default)
  • 1 - Generate a token and return it in the response.
  • 2 - Generate a token, add it to Converge's Card Manager, and return it in the response.

CurrencyCode:   Currency code for the currency of the transaction.

This config is used to specify the currency code to be used in the transaction. Default values and codes vary based on the gateway. This config will be populated with the default value for the gateway when Gateway is set.

For more information on these currency code values, please refer to the ISO 4217 standard as well as the gateway specification.

CurrencyExponent:   Currency exponent to be used in conjunction with the Currency code of the transaction.

If not set, "2" is sent by default. Currently only supported in the Orbital and WorldPayXML gateways.

CustomerProfileId:   Used to send a customer profile Id to a gateway.

This configuration setting is used to specify a customer profile Id when performing a transaction.

Note that this is only valid when the Gateway property is set to gwCardPointe.

CyberSourceAuthToken:   The request token from a previous authorization for the CyberSource gateway.

This config is used to specify a request token for authorization update transactions (such as captures, credits, voids, and reversals). This is only applicable when using the Atos interface.

CyberSourceProfileId:   The Id of a Customer's Profile stored within the CyberSource gateway.

This config allows you to specify a customer Profile Id to process a transaction using the customer's information stored within CyberSource's systems (this is known as Payment Tokenization). When specified, the ProfileId will be sent instead of the card data (when performing an AuthOnly or Sale) and thus the stored card in the customer's profile will be charged. Additionally you can Credit a card on a customer's profile by specifying a Profile Id and a TransactionId of "" (empty string). Please note that the component does NOT support creating, modifying, or deleting customer profiles. These will need to be created using the RecurringBilling component or by other means such as within CyberSource's Business Center.

CyberSourceVoidMode:   Indicates whether to perform a Void or Reversal.

If CyberSourceVoidMode is set to "Void" (default), VoidTransaction sends a void transaction to cancel a Capture or Credit request. Note a transaction can only be voided if CyberSource has not already submitted the capture or credit request to the processor (this is usually done once a day). If CyberSourceVoidMode is set to "Reverse", a full authorization reversal transaction is sent to reverse a previous authorization (i.e. after performing an AuthOnly transaction). Note in a reversal, it is required that TransactionAmount be set to the full amount authorized (as you cannot partially reverse an authorization).

CyberSourceXMLEscape:   Determines whether to XML escape the CyberSource gateway request field values.

If this setting is set to "True", the request field values will be XML escaped prior to being sent to the CyberSource gateway. If this setting is set to "False" (default), the component does not perform any XML escaping and the values are sent exactly as specified. The default value is "False".

DataCash3DSCardholderRegistered:   Indicates whether the cardholder was registered for 3D Secure for the DataCash gateway.

This config is used when sending 3D Secure data to the DataCash gateway. It indicates whether the cardholder was registered for 3D Secure and the PARes or VERes status. Available values are:

Value Description
yes Cardholder registered
no Cardholder not registered
attempted Enrolled, PARes status 'A'
ch_enrolled_u VERes status 'U'
tx_status_u Enrolled, PARes status 'U'

DataCashAuthOnlyFinality:   Indicates whether an AuthOnly transaction should be treated as final for the DataCash gateway.

This config is used to specify whether an AuthOnly transaction should be treated as final. If the final settlement amount is not known, this config should be set to 'False' to indicate that the settlement amount will likely be changed prior to settlement. When set to 'True' or '' (empty string) (default value) the transaction will be treated as final. Note that with '' (empty string) the transaction will be treated as final unless the merchant configuration has been set up or there is a risk of reversal. MasterCard Europe and Maestro have created this mandate to improve the management of cardholder 'open to buy' limits.

DataCashExtendedPolicyAggregate:   Used to specify an XML aggregate for Extended Policies within the DataCash gateway.

The specified aggregate will be contained within the "ExtendedPolicy" element of the request.

The three available policies (elements) that can be specified are: "cv2_policy", "postcode_policy", and "address_policy". Each of these elements have five available attributes, "notprovided", "notchecked", "matched", "notmatched", "partialmatch", of which have the following available values: "accept" and "reject".

Below is a sample XML aggregate: <cv2_policy notprovided="reject" notchecked="accept" matched="accept" notmatched="reject" partialmatch="reject"/> <postcode_policy notprovided="reject" notchecked="accept" matched="accept" notmatched="reject" partialmatch="accept"/> <address_policy notprovided="reject" notchecked="accept" matched="accept" notmatched="reject" partialmatch="accept"/>

DynamicDescriptor:   A merchant defined transaction description which appears on the customer's credit card statement.

This field is used to specify a dynamic descriptor (sometimes called a soft descriptor) for the transaction. Typically this value is used to specify transaction specific details which will be displayed on the customer's credit card statement.

The following gateways currently support this functionality: Heartland.

EscapeXML:   Automatically escape data within XML tags.

When set to true, this config will cause the component to automatically escape the XML data in the request. The default value is false. This is currently only supported in the Authorize.Net XML gateway.

ExPayGetMethods:   Used to send a GetMethods request to the ExPay gateway.

This is an action config that will send a GetMethods request to the ExPay gateway. Method information returned in the response can be parsed via the GetResponseVar method or the X*** configuration settings.

ExPayGetStatus:   Used to send a GetStatus request to the ExPay gateway.

This is an action config that will send a GetStatus request to the ExPay gateway. TransactionId or ExPayPaymentId is required (specifying both will result in an error). Status information returned in the response can be parsed via the GetResponseVar method or the X*** configuration settings.

ExPayPaymentId:   The payment Id used to retrieve a transaction status for the ExPay gateway.

This config is used to specify a payment Id to retrieve a transaction status for via ExPayGetStatus.

ExPayServiceId:   The Id of the service to use to perform an authorization for the ExPay gateway.

This config is used to specify the Id of the service (retrieved via a ExPayGetMethods call) and is required to perform an authorization via an AuthOnly call.

FDMSCurrentBalance:   Contains the current card balance value returned in a response for the First Data E4, Payeezy, and Bank Of America gateways.

When returned in the response, this field will be populated with the current balance on the card used to process the transaction.

FDMSGiftCardTransactionType:   Specifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways.

This field is used to specify the gift card transaction type you wish to perform. All gift card transactions are performed by setting the type via this config and calling the Sale method. When the transaction type is set to '0', the Sale, VoidTransaction and Refund methods can be called to perform their respective transactions. Note to process a gift card transaction, FDMSProcessGiftCard must be set to 'True'.

Applicable values are:

Value Description
0 (Default) Regular transaction (based on method called).
1 ValueLink Activation
2 Balance Inquiry
3 Reload
4 CashOut
5 ValueLink Deactivation

FDMSKeyId:   The Key Id that corresponds to the HMAC Key for the First Data E4, Payeezy, and Bank Of America gateways.

This config 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.

FDMSProcessGiftCard:   Specifies whether the card being processed is a gift card for the First Data E4, Payeezy, and Bank Of America gateways.

When set to 'True', the current transaction will be run as a gift card transaction. The default value 'False', will perform a regular credit card transaction.

FDMSTransArmorToken:   The Transarmor token that replaces a card number and used for transaction processing.

This config is used to both retrieve and specify a Transarmor Token for the First Data E4, Payeezy, and Bank Of America gateways. If your account is configured for Transarmor tokens, a token will be created by the server and returned via this config when performing a transaction using a Card data. Additionally, you can set this config to a previously retrieved token value and the token will be sent in the request rather than the Card data. This increases security as raw card data is no longer needed. Note when sending an FDMSTransArmorToken value, the CardType, ExpMonth, and ExpYear are required.

FDMSWalletProviderId:   Specifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways.

This field is used to specify a wallet provider when using a digital wallet like Apple Pay or Android Pay. By default this field is not sent, and no wallet provider is used.

Applicable values are:

Value Description
1 No wallet provider
2 Visa Checkout
3 MasterPass
4 Apple Pay
5 Samsung Pay
6 Android Pay

GlobalIrisRefundPassword:   The Refund password for the Global Iris gateway.

This config is used to specify the refund password provided to you by Global Iris. When a refund is performed, the component will use the specified password to generate and send a 'refundhash' in the request. This value is required when performing a Refund transaction.

GlobalPayrollCreateToken:   Sends a create token request to the Global Payroll gateway.

This is an action config which when called will send a create token request to the Global Payroll gateway. A successful response will contain the GlobalPayrollToken for the specified Number.

GlobalPayrollToken:   The token value for a corresponding card when using the Global Payroll gateway.

This field is used to retrieve or specify a token value. This field will be populated after a call to GlobalPayrollCreateToken This field should be specified prior to performing a transaction using a token value instead of Card.

GoEMerchantUseGatewayId:   Indicates whether to send a password or gateway Id for the GoEMerchant gateway.

By default, the Password property is sent as the "password" field in all requests. If the GoEMerchantUseGatewayId configuration setting is set to True, the component will instead treat the password as the "gateway_id" field in all requests.

HashAlgorithm:   Algorithm used for hashing.

Certain gateways allow the request to be hashed as an additional authentication mechanism. This configuration setting controls which algorithm is used for hashing. Valid values are:

Value Algorithm
0 MD5 (default)
1 SHA-1

HashSecret:   Security key used to generate a hash for gateways supporting such functionality.

Some gateways allow for the generation of a hash for added security. The following gateways support this config.

Authorize.Net: The newest version of the protocol includes an optional Hash Secret, which may be used to verify that a server response is actually from an Authorize.Net server. The hash secret is concatenated with the MerchantLogin, TransactionId, and TransactionAmount. This value is then hashed with the MD5 algorithm and compared to the value returned by the server. If they do not match, the component throws an exception. If the AIMHashSecret is left blank, this check will not be performed. The Server's Hash Secret may be set using the Authorize.Net online merchant interface, located at https://secure.authorize.net/.

Bank of America: This value will be the HMAC Key generated for you by the gateway. This value is required and an exception will be thrown if not specified.

BarClay and Ingenico: This value is optional and when specified 'SHASIGN' parameter will be computed and sent.

Bambora/Beanstream: If hash validation is required then set this to your hash key. HashAlgorithm will also need to be set accordingly.

Nuvei: This value is required in all transactions. The value is unique to each terminal and can be set through the online interface at "https://testpayments.nuvei.com/merchant/selfcare/".

USAePay: This value is optional and when a 'Pin' value is specified, the 'UMhash' parameter will be computed and sent.

HeartlandDeveloperId:   Optional DeveloperId field used by the Heartland gateway.

If HeartlandDeveloperId is set, the HeartlandVersionNumber should also be set. If set, this field must be exactly 6 characters in length.

HeartlandDeviceId:   DeviceId field required by the Heartland gateway.

This is issued by Heartland during registration.

HeartlandLicenseId:   LicenseId field required by the Heartland gateway.

This is issued by a Heartland Payment Systems Administrator during registration.

HeartlandReversalAmount:   The settlement amount to be used when performing a reversal for the Heartland gateway.

The Heartland gateway supports reversals of credit card transactions. To perform a reversal, TransactionAmount can be set and the VoidTransaction can be called. When performing a reversal, TransactionAmount must be set to the original authorized amount of the transaction you are performing the reversal on. This field should then be set to the settlement amount of the transaction (or the final authorized amount after the reversal is performed).

HeartlandSecretAPIKey:   Specifies the secret key to be used for authentication with Heartland.

If Heartland provides a secret key for use with their API, this property can be used to send it to the gateway. When this key is set, the HeartlandLicenseId, HeartlandSiteId, HeartlandDeviceId, MerchantLogin and MerchantPassword are not required, and will not be sent to the gateway.

HeartlandShipDay:   Ship day field required by the Heartland gateway e-commerce/direct marketing transactions.

The ship day for the Heartland transaction. Valid values are 1 - 31.

HeartlandShipMonth:   Ship month field required by the Heartland gateway e-commerce/direct marketing transactions.

The ship month for the Heartland transaction. Valid values are 1 - 12.

HeartlandSiteId:   SiteId field required by the Heartland gateway.

This is issued by Heartland during registration.

HeartlandSiteTrace:   Optional transaction identifier for the Heartland gateway.

Heartland supplies an additional way to trace the transaction, beyond the InvoiceNumber and TransactionId.

HeartlandTokenMapping:   The type of token to return when using Tokenization with the Heartland gateway.

The field is used to specify the type of token that should be returned when using the Heartland gateway. By setting this field to a value other than 0 (None), a Token will be requested and returned in the response via HeartlandTokenValue (provided one can be generated). Please see the "ICharge Gateway Setup and Required Properties" page for more details about using tokenization, as there are special merchant account configurations required.

The available mapping values are:

0 None: Tokenization is not requested. This is the default value.
1 Unique: This setting instructs the tokenization system to return a new, unique token value for the specified card number. The returned token value is unique within the merchant's token group.
2 Constant: This setting instructs the tokenization system to return a constant token value for the specified card number. The returned token value is unique within the merchant's token group, but the same token is always returned for a particular card number.

HeartlandTokenValue:   Used to retrieve or specify a Heartland token value.

This field is used to retrieve a Heartland Token value when using Heartland Tokenization (which is accomplished by setting HeartlandTokenMapping to a value greater than 0). A token replaces the card number in all subsequent transactions thus increasing security. This field can also be used to specify a previously retrieved token value. When set, the specified token value will be sent in the request instead of the card number.

HeartlandVersionNumber:   Optional VersionNumber field used by the Heartland gateway.

If HeartlandVersionNumber is set, the HeartlandDeveloperId should also be set. If set, this field must be exactly 4 characters in length.

LitleAdvancedFraudChecksId:   Used to specify the Id for use in the AdvancedFraudChecks element for the Litle gateway.

This field is used to specify the Id for the AdvancedFraudChecks element for the Litle gateway. Custom attributes can also be included by using the AddSpecialField method with the name "CustomAttributeX", where X is a number from 1 to 5. For example: icharge.Config("LitleAdvancedFraudChecksId=ASDFG-AXXXXAB999"); icharge.AddSpecialField("CustomAttribute1", "One"); icharge.AddSpecialField("CustomAttribute2", "Two");

LitleCustomBillingAggregate:   Used to specify an XML aggregate for Custom Billing support within the Litle gateway.

This field is used to specify an XML aggregate for Custom Billing support within the Litle gateway. When specifying custom billing, you can use either the phone or url child.

Below is a sample XML aggregate for the phone child: <phone>555-555-5555</phone> <descriptor>Billing Descriptor</descriptor>

Below is a sample XML aggregate for the url child: <url>retail.url</url> <descriptor>www.retail.com</descriptor>

MerchantAlias:   An additional merchant property used to specify an alias for the merchant.

The HSBC and PayFuse gateway both allow for a merchant alias to be specified (and in some cases it may be required). This field allows you to specify the alias.

MerchantCode:   A gateway-supplied merchant number, code, or Id.

For the CardPointe gateway, this configuration setting is required, and should contain your Merchant Id.

For the Litle gateway, this configuration setting is required, and should contain your Merchant Id.

For the MIT gateway, this configuration setting is required, and should contain your Merchant Number (Contado).

For the Priority Payment Systems gateway, this configuration setting is required, and should contain your Merchant Id.

For the WorldPayXML gateway, this configuration setting is optional; it is only needed if you require that the "merchantCode" sent in the request be different from your MerchantLogin (e.g., when processing AMEX transactions, or when supporting multiple currencies).

MerchantESolutionsAccountDataSource:   Specifies the source of a customer's data in an authorization request to Merchant e-Solutions.

This configuration setting is used to specify the source of a customer's data in an authorization request. For a "Card on File" request when the merchant is using data that they stored themselves, this value should be set to "Y". As per Merchant e-Solutions' documentation, valid values are:

Value Description
D Full magnetic stripe read and transmit, Track two
G Chip Card Read Data (EMV)
H Full magnetic stripe read and transmit, Track one
P Manually keyed, Chip Card read capable terminal
Q Proximity payment device using track data rules (Track 2 Only)
R Proximity payment device using VSDC or M/Chip data rules (Track 2 Only)
S Full magnetic stripe read (Track 2 only), Chip Card capable terminal
T Manually keyed, Track two capable
X Manually keyed, Track one capable
Y Subsequent Card on File
@ Manually keyed, terminal has no card reading capability

MerchantESolutionsCardOnFile:   Tells Merchant e-Solutions that you will be storing card information.

This configuration setting is used to inform Merchant e-Solutions that the merchant will be storing a customer's credit card data. For the initial request, after which the customer's data will be stored, this should be set to true.

MerchantESolutionsMerchantInitiated:   Tells Merchant e-Solutions that you are performing a Merchant Initiated Transaction.

This configuration setting is used to inform Merchant e-Solutions that a transaction was initiated by the merchant and not by the cardholder.

MerchantESolutionsMotoECommerceInd:   Used to tell Merchant e-Solutions if a transaction is Mail Order, Telephone Order, or E-Commerce.

This configuration setting is used to tell Merchant e-Solutions if a given transaction is Mail Order, Telephone Order, E-Commerce, or in person. As per Merchant e-Solutions' documentation, valid values are:

Value Description
Z In person.
1 One time Mail/Telephone Order.
2 Recurring Mail/Telephone Order.
3 Prepayment or installment payment.
4 E-commerce Order (Online).

MerchantESolutionsToken:   Holds a token representing card information stored by Merchant e-Solutions.

If this configuration setting contains a token during a request to MerchantESolutions, the token will be sent as part of the request. After a successful Sale, AuthOnly, or AVSOnly request with MerchantESolutionsTokenizeCard set, the token representing the card used in the request will be available by querying this configuration setting.

MerchantESolutionsTokenizeCard:   When set, will request a tokenized card from Merchant e-Solutions.

This configuration setting is used to request a tokenized card from Merchant e-Solutions. If it is set to true during a successful Sale, AuthOnly, or AVSOnly request, the response will include a token representing the card used in the transaction. Note that a token will not be requested if a token is already set in MerchantESolutionsToken.

MerchantPartnersLast4Digits:   The last 4 digits of the card number for a transaction processed via the MerchantPartners gateway.

The last 4 digits of the card number are required to process transactions using a stored profile Id (via MerchantPartnersProfileId) for the MerchantPartners or WorldPay Link gateways.

MerchantPartnersProfileId:   The profile Id to be used to process a transaction via the MerchantPartners or WorldPay Link gateways.

This field is used to specify the Profile Id of a stored profile and is used to process a transaction instead of specifying the card data. A profile is created via the RecurringBilling component and the SubscriptionId response field is used to obtain the profile Id to be set in this field. MerchantPartnersLast4Digits is a required field when using a stored profile. Note this config is only applicable to Sale and Credit transactions processed via the MerchantPartners or WorldPay Link gateways.

MetrobankLocale:   Sets the locale for a 3-party request to Metrobank.

This configuration setting is used when setting the Locale for a 3-party request with Metrobank. Controls the language that will appear on the payment page where the user is redirected.

MetrobankReturnURL:   Sets the URL where a user will be redirected after a 3-party request to Metrobank.

This configuration setting is used when setting the URL where a user will be redirected after a 3-party request with Metrobank. There must be a server listening at that URL to receive the transaction response.

MetrobankThreePartyRequest:   Indicates that the component should return data for a 3-party request to Metrobank.

When sending a 3-party request to Metrobank, this configuration setting should be used to skip sending the request and output it directly to the RawRequest configuration setting instead. It can then be included in the POST request through which the user is redirected.

MetrobankThreePartyResponse:   Used to manually parse a response after a 3-Party request to Metrobank.

After sending a 3-party request to Metrobank and receiving the response, this configuration setting can be used to manually enter the response data into the ICharge component to parse the response.

MetrobankVoidType:   Used to type of transaction should be voided in a request to Metrobank.

Metrobank allows a merchant to void Purchase, Capture, or Refund transactions, but the request must indicate which type of transaction to void. Valid values are:

Value Description
0 Void a purchase (Default).
1 Void a capture.
2 Void a refund.

MITAESSeedId:   The Seed Id used to perform AES encryption for the MIT gateway.

This field is used to specify the Seed Id used to perform AES encryption. This field is provided by MIT and is required when performing AES encryption.

MITBranchId:   Branch reference number for the MIT gateway.

This field is used to specify the branch reference number for the MIT gateway (Required).

MITCompanyId:   Company reference number for the MIT gateway.

This field is used to specify the company reference number for the MIT gateway (Required).

MITCountry:   Country of operation for the MIT gateway.

This field is used to specify the country of operation for the MIT gateway (Required).

MITEncryptionAlgorithm:   The Encryption Algorithm to use with the MIT gateway.

This field is used to specify the encryption algorithm to use for the MIT gateway. Encryption will only be performed if an encryption key is specified via MITEncryptionKey. Note when perform AES (1) encryption, you must also set MITAESSeedId.

Applicable values are:

Value Encryption Type
0 (Default) RC4 - The password, cardholder name, card number, expiration month, expiration year, and CVV data will be encrypted.
1 AES - The entire request XML will be encrypted.

MITEncryptionKey:   The Encryption Key to use with the MIT gateway.

This field is used to specify the encryption key for the MIT gateway. When set, the specified key will be used to perform the encryption specified via MITEncryptionAlgorithm.

MITFlag:   For the MIT framework - Used to indicate that a transaction is merchant initiated.

When making a Merchant Initiated Transaction (MIT), this configuration setting should be set to true to indicate to the payment gateway that the transaction is merchant initiated. Used by the Orbital payment gateway.

MITPriorTransId:   For the MIT framework - Used to specify a prior transaction id to be referenced in a merchant initiated transaction.

When making a Merchant Initiated Transaction (MIT), this configuration setting can be used to specify the transaction Id of a previously successful authorization. Used by the Orbital and CyberSource payment gateways.

MITRecurring:   Specifies whether to perform a recurring transaction request for the MIT gateway.

When this field is set to 'True', the component will perform a recurring transaction request when Sale is called. The fields required for a Recurring charge transaction are the same as a Sale transaction. The default value is 'False'.

MITTPOperation:   The operation type for the MIT gateway.

This field is used to specify the operation type for the MIT gateway (Required). This value will be provided to you by MIT.

MITType:   For the MIT framework - Indicates the type of transaction being requested in a Merchant-Initiated Transaction (MIT).

When making a Merchant Initiated Transaction (MIT), this configuration setting is used to specify the type or reason for the merchant initiated transaction. The possible values and formats for this field vary by gateway, so check the gateway's documentation for the associated values and their meanings.

MonerisNVPAPI:   Indicates whether to use the NVP API for the gwMoneris and gwMonerisUSA gateway.

The field is used to indicate whether to use the NVP API for either the gwMoneris or gwMonerisUSA gateway. When set to true, the NVP API will be used instead of the XML specification. Note that you must set Gateway to either gwMoneris or gwMonerisUSA prior to setting this field. Additionally, if you decide to use the NVP API, this field must be set directly after setting Gateway (as GatewayURL will be updated). Note: The Response Method of the DirectPost configuration must be set to "Displayed as key/value pairs on our server" in the merchant admin console when using the NVP API.

MyVirtualMerchantTransactionType:   Used to override the transaction type to send in a transaction for the MyVirtualMerchant and Converge gateways.

This field is used to override the default transaction type for the MyVirtualMerchant gateway. By default, the component will set the transaction type based on the method called. However this field can be set to override the default value and is particularly useful for creating recurring or installment billing transactions. Below is a list of some of the available transaction types. Note that these additional transaction types require special fields to be added via AddSpecialField. Please consult the Virtual Merchant specifications for details about the required fields.

  • CCCOMPLETE
  • CCADDINSTALL
  • CCADDRECURRING
  • CCINSTALLSALE
  • CCRECURRINGSALE
MyVirtualMerchantUserId:   The MyVirtualMerchant user Id as configured on VirtualMerchant.

This field is used to specify your MyVirtualMerchant user Id which is required (along with MerchantLogin and MerchantPassword) as part of the user authentication.

NetbanxAccountNumber:   Account Number for the Netbanx gateway.

This field is used to specify an account number for the Netbanx gateway which is used in addition to the MerchantLogin and MerchantPassword properties.

NetBillingVersion:   The Version to be sent in the User-Agent heading of a NetBilling gateway request.

The Version portion of the User-Agent HTTP header is required by NetBilling. The default value is "1".

OrbitalAuthReversal:   Indicates whether to perform an authorization reversal when calling VoidTransaction for the Orbital gateway.

This config is used to specify whether VoidTransaction should perform an authorization reversal or void transaction. When this config is set to 'True' and VoidTransaction is called, an authorization reversal transaction will be sent to reverse a previously authorized transaction. The default value is 'False' which sends a void transaction.

OrbitalConnectionPassword:   Orbital Connection Password field used by the Orbital gateway.

If OrbitalConnectionPassword is set, the OrbitalConnectionUsername should also be set. This field is case-sensitive.

OrbitalConnectionUsername:   Orbital Connection Username field used by the Orbital gateway.

If OrbitalConnectionUsername is set, the OrbitalConnectionPassword should also be set.

OrbitalCustomerProfileFromOrderInd:   Customer Profile Number generation Options for the Orbital gateway.

"A" Auto Generate the CustomerRefNum (Id)
"S" Use CustomerRefNum (Id) sent in the request.
"0" Use OrderID (InvoiceNumber) sent in the request.
"D" Use Comments (TransactionDesc) sent in the request.

OrbitalCustomerProfileId:   The Id for a customer profile in the Orbital gateway.

This configuration setting can be used to specify a customer profile to use during a request to the Orbital gateway. Additionally, after a request in which OrbitalCustomerProfileFromOrderInd is set it will contain the customer profile Id returned in the response.

OrbitalCustomerProfileOrderOverrideInd:   Indicator to specify how the CustomerId is leveraged to populate other data sets for the Orbital gateway.

"NO" No mapping to order data.
"OI" Pre-populate OrderId (InvoiceNumber) with the Customer Reference Number (Id).
"OD" Pre-populate the Comments field (TransactionDesc) with the Customer Reference Number (Id).
"OA" Pre-populate the OrderId (InvoiceNumber) and Comments (TransactionDesc) fields with the Customer Reference Number (Id).

Note: This field is auto-populated to "NO" when OrbitalCustomerProfileFromOrderInd is set.

OrbitalDigitalTokenCryptogram:   Holds the cryptogram when making a CDPT request with Orbital.

When making a CDPT request with Orbital, this configuration setting can be used to specify the cryptogram corresponding to the CDPT token. The CDPT token itself should be supplied through the card's Number field.

OrbitalDPANIndicator:   Indicates the type of a CDPT authorization with Orbital.

The DPANIndicator is used to specify the type of authorization when making a CDPT request with Orbital. It should be set to "Y" for the original authorization and "S" for any subsequent related authorizations.

OrbitalTxRefIdx:   Indentifies the unique components of transactions that have been adjusted more than one time for the Orbital gateway.

This field is used when performing a VoidTransaction to identify unique components of transactions adjusted more than one time. The default value ("NULL") should be submitted when voiding a transaction which has not been adjusted more than once or if the un-captured remainder of a split transaction (partial capture) should be voided. To void a specific partial capture, this field should be set to the value returned in the response for the partial capture. Note that this field will also be populated with the TxRefIdx value returned in a response.

OrbitalVoidAdjustedAmount:   Specifies the amount to void from a previous authoization for the Orbital gateway.

This field is used to specify an amount to adjust a previous authorization when performing a VoidTransaction. Thus the specified amount will be voided (assuming that the amount is not greater than the transaction amount remaining) and the total amount minus the adjusted amount will be the new authorized amount. When a value is not specified, the full amount of will be voided.

PayDirectConvenienceFee:   The total convenience fee charged when using the PayDirect gateway.

This field is used to specify the total convenience fee charged for the transaction when using the PayDirect gateway. This field is always required when using the PayDirect gateway. The sum of this field plus PayDirectMerchantAmount must always equal the value in TransactionAmount. If no values are set for either of these two configs, the component will set PayDirectMerchantAmount to the value specified in TransactionAmount and PayDirectConvenienceFee to "0.00".

PayDirectMerchantAmount:   The MerchantAmount used by the PayDirect gateway.

This field is used to specify the total amount of goods and services for the external client when using the PayDirect gateway. This field is always required when using the PayDirect gateway. The sum of this field plus PayDirectConvenienceFee must always equal the value in TransactionAmount. If no values are set for either of these two configs, the component will set PayDirectMerchantAmount to the value specified in TransactionAmount and PayDirectConvenienceFee to "0.00".

PayDirectSettleMerchantCode:   The Settle Merchant Code required for authorization when using the PayDirect gateway.

This field is used to set Settle Merchant Code assigned by Link2Gov for the Reconciliation of funds. This field is always required when using the PayDirect gateway.

PayerIP:   The IP address of the payer.

This config is used to specify the IP address of the payer, which is required by some gateways.

PayFlowProInquiry:   Submits an Inquiry transaction to the PayFlowPro gateway.

Set this config to the TransactionId from the transaction you wish to retrieve. You may also call PFPInquiry without setting it to anything. In this case the Id field is required, and the PayFlow Pro gateway will return the most recent transaction for the specified Id.

PayFlowProToken:   Used specify a token to be used instead of card data for the Payflow Pro gateway.

This field is used to specify a token value to perform additional authorizations (via Sale or AuthOnly) and Credits (via Credit) without sending card data again. For the Payflow Pro gateway, token values are the same as the TransactionId value returned from an authorization. Below is a code example of how this config can be used (note the code starts after the initial Sale or AuthOnly transaction has been performed):

ICharge.Config("PayFlowProToken=" + ICharge.Response.TransactionId); ICharge.TransactionId = "2"; ICharge.TransactionAmount = "10.00"; ICharge.Sale();

PayFlowProUpload:   Submits an Upload transaction to the PayFlowPro gateway.

This is an actionable config which when called will send an upload transaction to the Payflow Pro gateway. An upload transaction is used to store credit card information on the gateway server. Note that billing and shipping information can be saved as well. After a successful upload, TransactionId will contain the token value that corresponds to the credit card data stored. This token value can then be used to process transactions via PayFlowProToken.

PayJunctionUpdateAmount:   Indicates whether the capture method should send an update amount request when using the PayJunction gateway.

This field allows you to specify whether Capture will send an update amount or a capture request. By default, this value is 'False', which sends a capture request to mark an AuthOnly transaction for capture. This particular function does not allow you to alter the amount but instead just marks the authorized amount (from the AuthOnly transaction) for capture. When this field is set to 'True', the Capture method will send an update amount request allowing you to alter the amount that will be captured. This method can be used after AuthOnly and Sale transactions.

PaymentWorkSuiteClientCode:   The 3DSI assigned client code sent in a request to the PaymentWorksuite gateway.

This field is used to specify the client code that is assigned by 3DSI. This code uniquely identifies your organization for the purpose of accessing and authenticating to the Payment WorkSuite.

PaymentWorkSuiteLocationCode:   The 3DSI assigned location code sent in a request to the PaymentWorksuite gateway.

This field is used to specify the location code that uniquely identifies a specific location that is associated with the merchant identified by the specified PaymentWorkSuiteMerchantCode.

PaymentWorkSuiteMerchantCode:   The 3DSI assigned merchant code sent in a request to the PaymentWorksuite gateway.

This field is used to specify the merchant code that uniquely identifies a specific merchant within the Payment WorkSuite.

PayPointFreedomAPI:   Indicates whether to use the Freedom API for the gwPayPoint and gwSECPay gateways.

The field is used to indicate whether to use the Freedom API for either the gwPayPoint and gwSECPay gateway. When set to true, the Freedom API will be used instead of the XML Hosted specification. Note that you must set Gateway to either gwPayPoint or gwSECPay prior to setting this field. Additionally, if you decide to use the Freedom API, this field must be set directly after setting Gateway (as GatewayURL will be updated).

PayTraceAddPurchaseCardData:   Sends a Level3 request for the PayTrace gateway.

This config is used to add Purchase Card (Level2 and Level3) Data to an existing sale transaction for the PayTrace gateway. The Level2Aggregate and Level3Aggregate fields can be set to specify the purchase card data you wish to add prior to calling this config. A TransactionId, from the response of the original sale, is required to be specified when calling this config; i.e.: ICharge.Config("PayTraceAddPurchaseCardData=123456789");

PayTraceIntegratorId:   Used to specify the Integrator Id value assigned by the PayTrace gateway.

This value is assigned by PayTrace and is used for validation and tracking purposes. The default value is: "90000035NSFT".

PayTraceJSONCardToken:   The token value for a corresponding card.

This field is used to specify card token value that you retrieved from Protect.js (see PayTrace documentation for details). This field must be set prior to performing a transaction using a token value instead of a Card.

Note that this is only valid when calling Sale or AuthOnly methods and the Gateway property is set to gwPayTraceJSON (117)

PayTraceJSONEncryptionKey:   The Encryption Key to use with the PayTraceJSON gateway.

This field is used to specify the encryption key that you retrieved from Protect.js (see PayTrace documentation for details).

Note that this is only valid when calling Sale or AuthOnly methods and the Gateway property is set to gwPayTraceJSON (117)

PayTraceJSONGetClientKeyToken:   Retrieves a new Client Key (PROTECT AUTH TOKEN) from PayTrace.

This is an Action config. Getting this config will cause the component to obtain a Client Key (PROTECT AUTH TOKEN) from PayTrace. The Client Key will be used to authorize your application to use Protect.js to retrieve Card Token (hpf token) and Encryption Key (enc key). Please see PayTrace documentation for details. This key is valid for 20 minutes. icharge = new Icharge(); icharge.Gateway = IchargeGateways.gwPayTraceJSON; icharge.GatewayURL = "https://api.paytrace.com"; icharge.MerchantLogin = bearerToken; string clientKeyToken = component.Config("PayTraceJSONGetClientKeyToken"); //use this key to obtain "hpf_token" and "enc_key" from Protect.js

PayvisionTransactionGuid:   The GUID obtained with an authorization for the Payvision gateway.

This config is used to retrieve the Transaction GUID returned in an authorization response for the Payvision gateway. This setting is also used to specify the Transaction GUID from a previous authorization, when performing a followup transaction (such as a Capture, Refund, or VoidTransaction).

PayWiserCaptureReferenceId:   The capture reference id returned by PayWiser after doing a Sale transaction.

This configuration setting is populated after calling the Sale method.

PayWiserCardToken:   The token value for a corresponding card when using the PayWiser gateway.

This field is used to specify a token value. This field should be specified prior to performing a transaction using a token value instead of Card.

Note: PayWiserCardToken can be obtained via the RecurringBilling component by setting the PayWiserRequestType configuration setting to 1.

PayWiserEMerchantPay:   Determines whether to process the transaction via E-Merchant Pay Acquiring Bank.

Determines whether to process the transaction via E-Merchant Pay Acquiring Bank. When this configuration setting is set to True, ThreeDSuccessURL and ThreeDFailURL fields must also be sent using the AddSpecialField method. For example: icharge.Config("PayWiserEMerchantPay=True"); icharge.AddSpecialField("ThreeDSuccessURL", "SuccessURL"); icharge.AddSpecialField("ThreeDFailURL", "FailURL"); icharge.AuthOnly();

By default this configuration setting is set to False.

PayWiserReserveReferenceId:   The reserve reference id returned by PayWiser after doing a Sale transaction.

This configuration setting is populated after calling the Sale method. The value returned by this configuration setting should be used when calling the Refund method.

Note: If the AuthOnly method is called, the Reserve Reference Id can be obtained via the Response property.

PayWiserTokenizeCard:   Whether to generate a Token Reference Id.

Whether to generate a Token Reference Id based on the Credit Card information. This configuration setting can only be set when calling the Sale method.

By default this configuration setting is set to False. If set to True, a Token Reference Id will be returned in PayWiserTokenReferenceId configuration setting.

PayWiserTokenReferenceId:   The token reference id for a corresponding card when using the PayWiser gateway.

This configuration setting is populated at the time the Token Reference Id is created by calling the Sale method and setting PayWiserTokenizeCard configuration setting to True. This field should be specified prior to performing a transaction using a Token Reference Id instead of Card.

PhoeniXGateCardInfoKey:   PhoeniXGate Gateway Credit Card Profile Id.

If PhoeniXGateProcessRecurringCredit is set to True this must be set to the credit card profile id value assigned to the payment method when it was added to the system.

Note: PhoeniXGateCardInfoKey can be obtained via the RecurringBilling component.

PhoeniXGateProcessRecurringCredit:   Determines whether to process the transaction via Credit Card Profile Id.

Determines whether to process the transaction via customer's Credit Card profile. By default this configuration setting is set to False. If set to True, PhoeniXGateCardInfoKey and MerchantCode configuration settings must also be set. For instance: icharge.Config("MerchantCode=YourPhoeniXGateMerchantKey"); icharge.Config("PhoeniXGateProcessRecurringCredit=True"); icharge.Config("PhoenixGateCardInfoKey=YourPhoeniXGateCardInfoKey"); icharge.TransactionAmount = "1.00"; icharge.Sale();

PhoeniXGateProcessTokenCredit:   Determines whether to process the transaction using a Credit Card Token.

Determines whether to process the transaction using a Credit Card Token provided by PhoeniXGate Gateway. By default this configuration setting is set to False. If set to True, PhoeniXGateTokenMode and PhoeniXGateToken must also be set. For Instance: icharge.Config("PhoeniXGateProcessTokenCredit=True"); icharge.Config("PhoeniXGateToken=YourToken"); icharge.TransactionAmount = "1.00"; icharge.Sale();

PhoeniXGateToken:   PhoeniXGate Gateway Credit Card Token.

If PhoeniXGateProcessTokenCredit is set to True, this must be set to the token value assigned to the payment method when it was added to the system.

Note: PhoeniXGateToken can be obtained via the RecurringBilling component.

PhoeniXGateTokenMode:   Indicates the type of token that is being used for the transaction.

Indicates the type of token that is being used for the transaction. If PhoeniXGateProcessTokenCredit is set to True this must be set to one of the following values.

Possible values:

Value Description
0 Default (PhoeniXGate Gateway Default Format).
1 Card Format.

PhoeniXGateVoidMode:   Indicates whether to perform a Void or Reversal.

If PhoeniXGateVoidMode is set to "0" (default), VoidTransaction sends a void to undo an unsettled transaction. If PhoeniXGateVoidMode is set to "1" (Reversal), this ensures the transaction is unsettled and also removes the authorization from the issuing bank.

Possible values:

Value Description
0 Void (Default).
1 Reversal.

PKPaymentToken:   Used to send an Apple Pay PKPaymentToken to the gateway.

This configuration setting is used to send an Apple Pay PKPaymentToken containing a user's credentials to a gateway. The setting should be set to the full JSON contents of the PKPaymentToken, like: icharge.Config("PKPaymentToken={\"version\":\"EC_v1\",\"data\":\"...\",\"signature\":\"...\",\"header\":{\"applicationData\":\"...\",\"transactionId\":\"...\",\"ephemeralPublicKey\":\"...\",\"publicKeyHash\":\"...\"}}"); PKPaymentToken is currently only supported in gwLitle.

PPSPaymentToken:   A Priority Payment Systems payment token.

This configuration setting is used to hold a payment token for use with the Priority Payment Systems gateway. This setting is automatically populated after calling AuthOnly, Sale, or Credit for the Priority Payment Systems gateway.

For the Priority Payment Systems gateway, a payment token is used when calling Capture to specify what previously-authorized transaction should be captured. This setting must be set before calling Capture (the Capture method's TransactionId parameter is ignored).

(Note that Priority Payment Systems still uses a standard transaction Id for the VoidTransaction and Refund methods, only the Capture method uses a payment token instead.)

QBMSMobile:   Whether or not this transaction is being sent from a mobile device.

When using the QBMS gateway, this setting specified whether a transaction is being sent from a mobile device ("True") or not ("False"). The default value is "False".

QBPaymentsMobile:   Whether or not this transaction is being sent from a mobile device.

When using the QBPayments gateway, this setting specified whether a transaction is being sent from a mobile device ("True") or not ("False"). The default value is "False".

RawRequest:   Returns the data that was sent to the gateway.

This may be queried after a call to any method that sends data to the gateway. This will return the request data that was sent to the gateway which may be useful for troubleshooting purposes. For instance: component.Sale() MyString = component.Config("RawRequest")

RawResponse:   Returns the data that was received from the gateway.

This may be queried after a call to any method that sends data to the gateway. This will return the response that was received to the gateway which may be useful for troubleshooting purposes. For instance: component.Sale() MyString = component.Config("RawResponse")

RecurringIndicator:   Marks a request as a recurring transaction.

This configuration setting can be set to indicate that a request is a recurring transaction. For a list of supported values for a gateway, please see the "ICharge Gateway Setup and Required Properties" page. This configuration setting is used by the QBPayments gateway.

RepayCardInfoKey:   Repay Gateway Credit Card Profile Id.

If RepayProcessRecurringCredit is set to True this must be set to the credit card profile id value assigned to the payment method when it was added to the system.

Note: RepayCardInfoKey can be obtained via the RecurringBilling component.

RepayProcessRecurringCredit:   Determines whether to process the transaction via Credit Card Profile Id.

Determines whether to process the transaction via customer's Credit Card profile. By default this configuration setting is set to False. If set to True, RepayCardInfoKey and MerchantCode configuration settings must also be set. For instance: icharge.Config("MerchantCode=YourRepayMerchantKey"); icharge.Config("RepayProcessRecurringCredit=True"); icharge.Config("RepayCardInfoKey=YourRepayCardInfoKey"); icharge.TransactionAmount = "1.00"; icharge.Sale();

RepayProcessTokenCredit:   Determines whether to process the transaction using a Credit Card Token.

Determines whether to process the transaction using a Credit Card Token provided by Repay Gateway. By default this configuration setting is set to False. If set to True, RepayTokenMode and RepayToken must also be set. For Instance: icharge.Config("RepayProcessTokenCredit=True"); icharge.Config("RepayToken=YourToken"); icharge.TransactionAmount = "1.00"; icharge.Sale();

RepayToken:   Repay Gateway Credit Card Token.

If RepayProcessTokenCredit is set to True, this must be set to the token value assigned to the payment method when it was added to the system.

Note: RepayToken can be obtained via the RecurringBilling component.

RepayTokenMode:   Indicates the type of token that is being used for the transaction.

Indicates the type of token that is being used for the transaction. If RepayProcessTokenCredit is set to True this must be set to one of the following values.

Possible values:

Value Description
0 Default (Repay Gateway Default Format).
1 Card Format.

RepayVoidMode:   Indicates whether to perform a Void or Reversal.

If RepayVoidMode is set to "0" (default), VoidTransaction sends a void to undo an unsettled transaction. If RepayVoidMode is set to "1" (Reversal), this ensures the transaction is unsettled and also removes the authorization from the issuing bank.

Possible values:

Value Description
0 Void (Default).
1 Reversal.

ResponseCardNumber:   The card number as returned in the response from the gateway.

After a request to a gateway, this configuration setting will contain the card number from the gateway's response. This is currently only available when Gateway is set to gwAuthorizeNetXML.

ResponseCardType:   The card type as returned in the response from the gateway.

After a request to a gateway, this configuration setting will contain the card type (Visa, Mastercard, etc.) from the gateway's response. This is currently only available when Gateway is set to gwAuthorizeNetXML.

SagePayCreateToken:   Sends a create token request to the SagePay gateway.

This is an action config which when called will send a create token request to the SagePay gateway. A successful response will contain the SagePayToken for the specified Number. Note: when using this config you must set the "VPSProtocol" SpecialFields to "3.00".

SagePayRemoveToken:   Sends a remove token request to the SagePay gateway.

This is an action config which when called will send a remove token request to the SagePay gateway. The specified SagePayToken will be removed from the SagePay server. Note: when using this config you must set the "VPSProtocol" SpecialFields to "3.00".

SagePayRepeat:   Performs a Repeat transaction for the SagePay gateway.

This is an action config which when called will perform a Repeat transaction for the SagePay gateway. The 'TransactionId' from a previous authorization response, that you would like to repeat for the card associated with the transaction, must be specified as a parameter. For example, a Repeat transaction using a TransactionId of 123 would be: ICharge.Config("SagePayRepeat=123").

"RelatedSecurityKey" and "RelatedVendorTXCode" special fields are required for Repeats. These are parsed out of the original authorization response.

SagePayRequestToken:   Specifies whether to request a token when performing an Auth or Sale when using the SagePay gateway.

This field allows you to specify whether to have SagePay generate a token and send it in the response. When set to 'True', a token will be returned in a Sale or AuthOnly response and can be accessed via SagePayToken. Note: when using this config you must set the "VPSProtocol" SpecialFields to "3.00". The default value is 'False'.

SagePayStoreToken:   Specifies whether to store a token when using the SagePay gateway.

This field allows you to specify whether to store a token and on the SagePay server. This field must be set to 'True' to have the token remain on the server after use. Otherwise, if set to 'False', the Token will be used to perform the requested transaction and then deleted from the server. Note: when using this config you must set the "VPSProtocol" SpecialFields to "3.00". The default value is 'False'.

SagePayToken:   The token value for a corresponding card when using the SagePay gateway.

This field is used to retrieve or specify a token value. This field will be populated after a call to either SagePayCreateToken or SagePayRequestToken is set to 'True' and a Sale or AuthOnly request is performed. This field can be specified prior to calling SagePayRemoveToken or performing a transaction using a token value instead of Card.

SagePayUseAbort:   Indicates whether to use Abort or Void for void transactions.

The SagePay gateway (formerly Protx) has two different void transaction types. If SagePayUseAbort is set to false (default), void transactions are sent with the VOID transaction type. If true, void transactions are sent with the ABORT transaction type. Aborts are used for voiding auth-only transactions, and voids are used for voiding sale/capture transactions.

The TransactionId from the original request must be passed as the parameter in the VoidTransaction method. In addition, the following Special Fields are required for both Abort and Void transactions:

SecurityKey Security Key from original transaction response.
TxAuthNo ApprovalCode from original transaction response.

Shift4AuthToken:   Specifies the Auth Token when making an Access Token request to the Shift4 gateway.

This configuration setting is used to specify the AuthToken to include when making an Access Token Exchange request to the Shift4 gateway. An access token is required for any other interaction with the gateway.

Shift4ClientGuid:   Specifies the Client Guid when making an Access Token request to the Shift4 gateway.

This configuration setting is used to specify the Client Guid to include when making an Access Token Exchange request to the Shift4 gateway. An access token is required for any other interaction with the gateway.

Shift4GetAccessToken:   Performs an Access Token Exchange request with the Shift4 gateway.

This is an action config which when called will perform an Access Token Exchange request with the Shift4 gateway. Before calling this config, the MerchantLogin property and the Shift4InterfaceName, Shift4InterfaceVersion, Shift4AuthToken, and Shift4ClientGuid configuration settings should be set. MerchantPassword will be set to the access token if the request is successful. Note that an AuthToken can only be exchanged for an access token once, so be sure to save the result of the request for future use.

Shift4InterfaceName:   Specifies the name of the interface for the Shift4 gateway.

Shift4 requires you to identify the interface that you are using to communicate with the API (i.e. your application). This configuration setting is used to specify the name of the interface.

Shift4InterfaceVersion:   Specifies the version of the interface for the Shift4 gateway.

Shift4 requires you to identify the interface that you are using to communicate with the API (i.e. your application). This configuration setting is used to specify the version of the interface.

SquareAdditionalRecipients:   Additional recipients data to send with a Square Sale or AuthOnly request.

This setting can be set to a JSON array like the following one in order to send one or more additional recipients data objects when calling Sale or AuthOnly: [ { "location_id": "057P5VYJ4A5X1", "description": "Application fees", "amount_money": { "amount": 20, "currency": "USD" }, "receivable_id": "ISu5xwxJ5v0CMJTQq7RvqyMF" } ] Note: Content set using this setting will be used as the value of the additional_recipients JSON field in the request body; it is not validated or manipulated first, it is used "as-is". This configuration setting is only used by the Square Transactions API (gwSquare).

SquareApplicationFee:   Allows you to specify an application fee as part of the transaction.

This setting can be set to an amount that should be charged to the merchant as an application fee for making the transaction. This should a whole number in the smallest denomination of the selected currency, so for example if the currency is set to USD and this value is set to 100, there will be a $1 application fee. This configuration setting is only used by the Square Payments API (gwSquarePayments).

SquareCustomerCardId:   The Id of the card saved to a customer profile.

This configuration setting is used to specify the Id of a card-on-file associated with the Square customer profile specified by Id (which must be set, along with this configuration setting, to when making a Sale or AuthOnly request against a card-on-file).

Note that if a card nonce has been specified using the CardToken configuration setting, this setting's value is ignored and the card nonce is sent instead (regardless of whether Id is set). This configuration setting is used by both the Square Transactions API (gwSquare) and the Square Payments API (gwSquarePayments).

SquareIdempotencyKey:   Value that uniquely identifies a Square Sale, AuthOnly, or Refund request.

Square requires that each Sale, AuthOnly, or Refund request have an idempotency key sent with it.

Idempotency key values should uniquely represent a real Sale, AuthOnly, or Refund. Any Sale, AuthOnly, or Refund request made using a duplicate idempotency key is ignored by Square. This configuration setting is used by both the Square Transactions API (gwSquare) and the Square Payments API (gwSquarePayments).

SquareLocationId:   Square location Id to make the transaction request against.

Square requires that all transaction requests be made against one of the "location Ids" associated with a merchant's account.

This configuration setting must be set prior to making any requests when Gateway is set to gwSquare. This configuration setting is required by the Square Transactions API (gwSquare) and optional in the Square Payments API (gwSquarePayments).

SquareOrderId:   Square Order Id to associate with a Square Sale or AuthOnly request.

This configuration setting can be used to specify a Square Order Id to associate with a Sale or AuthOnly transaction request.

Note: Square will reject any transaction request that includes an Order Id if that transaction's amount does not match the associated Order's total amount. This configuration setting is used by both the Square Transactions API (gwSquare) and the Square Payments API (gwSquarePayments).

SquareTenderId:   Square Tender Id associated with a Square transaction.

This configuration setting is used to specify a Square Tender Id. It is populated after a successful Sale or AuthOnly request, and must be specified before making a Refund request.

Important: In addition to a Tender Id, Square transactions also have a Transaction Id. Be sure to persist both Ids after making a Sale or AuthOnly request, as both are required in order to make a Refund request! This configuration setting is only used by the Square Transactions API (gwSquare).

StoreCardOnFile:   For the Stored Credentials framework - Used to indicate that the merchant will be storing the customer's card on file (COF).

For the Stored Credentials framework, this configuration setting should be set to true to indicate that the merchant will be storing the customer's card information. Permission should be obtained from the customer prior to storing card data. This configuration setting is used by the CyberSource gateway.

StripeApplicationFee:   A fee in cents that will be applied to the charge.

A fee in cents that will be applied to the charge and transferred to the application owner's Stripe account. To use an application fee, the request must be made on behalf of another account, using StripeOnBehalfOf and StripeDestinationAccount configuration settings.

StripeDestinationAccount:   Id of an existing, connected Stripe account.

Id of an existing, connected stripe account. This configuration setting is required when an application fee will be transferred to the application owner's Stripe account via StripeApplicationFee configuration settings.

StripeDestinationAmount:   The amount to transfer to the destination account.

The amount to transfer to the destination account without creating an application fee. Cannot be combined with the StripeApplicationFee configuration setting. Must be equal to or lesser than the charge amount.

StripeOnBehalfOf:   The Stripe account Id that these funds are intended for.

The Stripe account Id that funds are intended for. Automatically set if you are also setting the StripeApplicationFee configuration setting.

StripeRefundApplicationFee:   Whether the application fee should be refunded when refunding the charge.

Whether the application fee should be refunded when refunding the charge. If a full charge refund is given, the full application fee will be refunded. Else, the application fee will be refunded with an amount proportional to the amount of the charge refunded. An application fee can only be refunded by the application that created the charge. This configuration setting is optional and can be set to either True or False.

Note that by default Stripe will not refund application fees.

StripeRefundReason:   Reason for the refund.

Reason for the refund. Possible values are duplicate, fraudulent, and requested_by_customer.

StripeRefundReverseTransfer:   Whether the transfer should be reversed when refunding the charge.

Whether the transfer should be reversed when refunding the charge. The transfer will be reversed for the same amount being refunded (either the entire or partial amount). A transfer can only be reversed by the application that created the charge. This configuration setting is optional and can be set to either True or False.

Note that by default Stripe will not refund application fees.

StripeShippingCarrier:   The delivery service that shipped a physical product.

The delivery service that shipped a physical product, such as FedEx, UPS, USPS, etc.

StripeShippingTrackingNumber:   The tracking number for a physical product.

The tracking number for a physical product, obtained from the delivery service.

StripeTransferGroup:   Identifies the transaction as part of a group.

Identifies the transaction as part of a group.

StripeVersion:   Determines which version of the Stripe API should be used.

When making a transaction with Stripe, this configuration setting tells Stripe which version of the API will be used. By default, Stripe will use the API version configured on the merchant's account. This setting should be the date of the version you want to use, such as "2019-09-09".

SurchargeAmount:   Used to specify the amount of the surcharge for the transaction.

This configuration setting is used when there is an additional fee included in the transaction to specify the amount of that fee. This field is used by the Shift4 gateway.

TerminalId:   Terminal Id value sent in the transaction.

Many gateways allow/require an Id (terminal, developer, client, user, etc) sent in addition to the MerchantLogin and MerchantPassword. This config is supported for the following gateways: Adyen (required), BarClay (required), BluePay, Nuvei (required), Heartland, HSBC (required), Orbital, PayFuse (required), PaymentWorksuite, Planet Payment (required), SkipJack, and WorldPayXML (required). For Orbital, this config is optional but if not specified a value of '001' will be sent. For Heartland, this config is used for MasterCard's Card Accepter Terminal Id requirement.

TipAmount:   Used to specify the amount of the tip for the transaction.

This configuration setting is used when there is a tip included in the transaction to specify the amount of the tip. This field is used by the Shift4 gateway.

USAEPayPerformVoidRelease:   Specifies whether to perform a void or void:release transaction.

This field is used to specify whether you wish to perform a void or void:release transaction when VoidTransaction is called. When set to "True", the void:release transaction will be sent. The void:release transaction is the same as a void with the exception that the cardholders bank is notified immediately that they can release the funds. The regular void transaction, on the other hand, does not notify the cardholder bank until the batch closes. The default value is "False" (so a regular void transaction is sent).

UseCardOnFile:   For the Stored Credentials framework - Used to indicate that the merchant is using stored card on file (COF) information for the request.

For the Stored Credentials framework, this configuration setting should be set to true to indicate that the merchant is using stored card information. This configuration setting is used by the CyberSource gateway.

UserId:   Used to specify an Id for the API user.

This configuration setting is used to specify an Id for the user, if one is required. Used by the Barclay, Ingenico, Metrobank, and Shift4 gateways. For the Barclay and Ingenico gateways, this configuration setting should contain the name of your application (API) user. For Shift4 or Metrobank, this is the clerk or terminal operator.

VeritasBankName:   Name of the card issuer.

This configuration setting is required when calling the Sale method and must be set to the name of the card issuer. For example: icharge.Config("VeritasBankName=Bank of China"); icharge.Sale(); Note: The BankName setting can be used instead of this.

VeritasEncryptionKey:   Encryption key used to encrypt credit card information.

This configuration setting must be set to the encryption key provided by the gateway. Encryption key used to encrypt credit card information.

This configuration setting must be set to the encryption key provided by the gateway.

VeritasEncryptionKey:   Encryption key used to encrypt credit card information.

This configuration setting must be set to the encryption key provided by the gateway. Encryption key used to encrypt credit card information.

This configuration setting must be set to the encryption key provided by the gateway.

VeritasToken:   Veritas token.

Veritas token is provided by the gateway when activating the merchant account.

VeritasVoidRefundReasonId:   Veritas gateway void reason.

Reason for voiding an authorized transaction for Veritas gateway. This configuration setting must be set when calling the VoidTransaction method.

Possible values:

Value Description
1 A mistake has been made (Default).
2 Broken product.
3 Wrong product delivered.

WorldpayOnlineToken:   Worldpay Online token.

Worldpay Online token used in place of payment information when making a transaction.

WorldpayOnlineTokenAction:   Used to generate, update, or delete a Worldpay Online token.

This configuration setting, when set, will cause the component either generate, update, or delete a Worldpay Online token. Valid values are:

Value Description
0 Generate a new, single-use token.
1 Generate a new, reusable token.
2 Update a reusable token with the CVV of the card it represents (must be done before each re-use of the token)
3 Delete a token.

XChildrenCount:   The number of child elements of the current element.

The number of child attributes of the current element. The XChildren configuration options will be indexed from 0 to XChildrenCount-1.

The current element is specified via the XPath configuration option.

This configuration option is read-only.

XChildrenName[x]:   The name of the child element.

Provides the name of the x'th child element of the current element.

The current element is specified via the XPath configuration option.

This configuration option is read-only.

XChildrenXText[x]:   The inner text of the child element.

Provides the inner text of the x'th child element of the current element.

The current element is specified via the XPath configuration option.

This configuration option is read-only.

XElement:   The name of the current element.

The current element is specified via the XPath configuration option.

This configuration option is read-only.

XPath:   Provides a way to point to a specific element in the returned XML or JSON response.

XPath implements a subset of the XML and JSON XPath specification, allowing you to point to specific elements in the XML or JSON documents. The path is a series of one or more element accessors separated by '/'. The path can be absolute (starting with '/') or relative to the current XPath location. The following are possible values for an element accessor:

'name' A particular element name
name[i] The i-th subelement of the current element with the given name
[i] The i-th subelement of the current element
[last()] The last subelement of the current element
[last()-i] The subelement located at the last location minus i in the current element
name[@attrname="attrvalue"] The subelement containing a particular value for a given attribute (supports single AND double quotes). Not available for JSON responses.
.. The parent of the current element

When XPath is set to a valid path, XElement points to the name of the element, with XChildren and XText providing other properties of the element.

Example (Setting XPath for XML)

Document root Charge.XPath = "/"
Specific Element Charge.XPath = "/root/SubElement1/SubElement2/"
i-th Child Charge.XPath = "/root/SubElement1[i]"

Example (Setting XPath for JSON)

Document root Charge.XPath = "/"
Specific Element Charge.XPath = "/root/SubElement1/SubElement2/"
i-th Child Charge.XPath = "/root/SubElement1/[i]"

XText:   The text of the current element.

The current element is specified in the XPath configuration option.

This configuration option is read-only.

HTTP Config Settings

AcceptEncoding:   Used to tell the server which types of content encodings the client supports.

When AllowHTTPCompression is True, the component adds an Accept-Encoding header to the request being sent to the server. By default, this header's value is "gzip, deflate". This configuration setting allows you to change the value of the Accept-Encoding header. Note: The component only supports gzip and deflate decompression algorithms.

AllowHTTPCompression:   This property enables HTTP compression for receiving data.

This configuration setting enables HTTP compression for receiving data. When set to True (default), the component will accept compressed data. It then will uncompress the data it has received. The component will handle data compressed by both gzip and deflate compression algorithms.

When True, the component adds an Accept-Encoding header to the outgoing request. The value for this header can be controlled by the AcceptEncoding configuration setting. The default value for this header is "gzip, deflate".

The default value is True.

AllowHTTPFallback:   Whether HTTP/2 connections are permitted to fallback to HTTP/1.1.

This configuration setting controls whether HTTP/2 connections are permitted to fall back to HTTP/1.1 when the server does not support HTTP/2. This setting is applicable only when HTTPVersion is set to "2.0".

If set to True (default), the component will automatically use HTTP/1.1 if the server does not support HTTP/2. If set to False, the component throws an exception if the server does not support HTTP/2.

The default value is True.

AllowNTLMFallback:   Whether to allow fallback from Negotiate to NTLM when authenticating.

This configuration setting applies only when AuthScheme is set to Negotiate. If set to True, the component will automatically use New Technology LAN Manager (NTLM) if the server does not support Negotiate authentication. Note: The server must indicate that it supports NTLM authentication through the WWW-Authenticate header for the fallback from Negotiate to NTLM to take place. The default value is False.

Append:   Whether to append data to LocalFile.

This configuration setting determines whether data will be appended when writing to LocalFile. When set to True, downloaded data will be appended to LocalFile. This may be used in conjunction with Range to resume a failed download. This is applicable only when LocalFile is set. The default value is False.

Authorization:   The Authorization string to be sent to the server.

If the Authorization property contains a nonempty string, an Authorization HTTP request header is added to the request. This header conveys Authorization information to the server.

This property is provided so that the HTTP component can be extended with other security schemes in addition to the authorization schemes already implemented by the component.

The AuthScheme property defines the authentication scheme used. In the case of HTTP Basic Authentication (default), every time User and Password are set, they are Base64 encoded, and the result is put in the Authorization property in the form "Basic [encoded-user-password]".

BytesTransferred:   Contains the number of bytes transferred in the response data.

This configuration setting returns the raw number of bytes from the HTTP response data, before the component processes the data, whether it is chunked or compressed. This returns the same value as the Transfer event, by BytesTransferred.

ChunkSize:   Specifies the chunk size in bytes when using chunked encoding.

This is applicable only when UseChunkedEncoding is True. This setting specifies the chunk size in bytes to be used when posting data. The default value is 16384.

CompressHTTPRequest:   Set to true to compress the body of a PUT or POST request.

If set to True, the body of a PUT or POST request will be compressed into gzip format before sending the request. The "Content-Encoding" header is also added to the outgoing request.

The default value is False.

EncodeURL:   If set to True the URL will be encoded by the component.

If set to True, the URL passed to the component will be URL encoded. The default value is False.

FollowRedirects:   Determines what happens when the server issues a redirect.

This option determines what happens when the server issues a redirect. Normally, the component returns an error if the server responds with an "Object Moved" message. If this property is set to 1 (always), the new URL for the object is retrieved automatically every time.

If this property is set to 2 (Same Scheme), the new URL is retrieved automatically only if the URL Scheme is the same; otherwise, the component throws an exception.

Note: Following the HTTP specification, unless this option is set to 1 (Always), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities.

Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty, unless this property is set to 1 (Always), in which case the same credentials are used to connect to the new server.

A Redirect event is fired for every URL the product is redirected to. In the case of automatic redirections, the Redirect event is a good place to set properties related to the new connection (e.g., new authentication parameters).

The default value is 0 (Never). In this case, redirects are never followed, and the component throws an exception instead.

Following are the valid options:

  • 0 - Never
  • 1 - Always
  • 2 - Same Scheme

GetOn302Redirect:   If set to True the component will perform a GET on the new location.

The default value is False. If set to True, the component will perform a GET on the new location. Otherwise, it will use the same HTTP method again.

HTTP2HeadersWithoutIndexing:   HTTP2 headers that should not update the dynamic header table with incremental indexing.

HTTP/2 servers maintain a dynamic table of headers and values seen over the course of a connection. Typically, these headers are inserted into the table through incremental indexing (also known as HPACK, defined in RFC 7541). To tell the component not to use incremental indexing for certain headers, and thus not update the dynamic table, set this configuration option to a comma-delimited list of the header names.

HTTPVersion:   The version of HTTP used by the component.

This property specifies the HTTP version used by the component. Possible values are as follows:

  • "1.0"
  • "1.1" (default)
  • "2.0"
  • "3.0"

When using HTTP/2 ("2.0"), additional restrictions apply. Please see the following notes for details.

HTTP/2 Notes

When using HTTP/2, a secure Secure Sockets Layer/Transport Layer Security (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/2 will result in an error.

If the server does not support HTTP/2, the component will automatically use HTTP/1.1 instead. This is done to provide compatibility without the need for any additional settings. To see which version was used, check NegotiatedHTTPVersion after calling a method. The AllowHTTPFallback setting controls whether this behavior is allowed (default) or disallowed.

HTTP/2 is supported on all versions of Windows. If the Windows version is an earlier version than Windows 8.1/Windows Server 2012 R2, the internal security implementation will be used. If the Windows version is Window 8.1/Windows Server 2012 R2 or later, the system security libraries will be used by default.

HTTP/3 Notes

HTTP/3 is supported only in .NET and Java.

When using HTTP/3, a secure (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/3 will result in an error.

IfModifiedSince:   A date determining the maximum age of the desired document.

If this setting contains a nonempty string, an If-Modified-Since HTTP header is added to the request. The value of this header is used to make the HTTP request conditional: if the requested documented has not been modified since the time specified in the field, a copy of the document will not be returned from the server; instead, a 304 (not modified) response will be returned by the server and the component throws an exception

The format of the date value for IfModifiedSince is detailed in the HTTP specs. For example: Sat, 29 Oct 2017 19:43:31 GMT.

KeepAlive:   Determines whether the HTTP connection is closed after completion of the request.

If True, the component will not send the Connection: Close header. The absence of the Connection header indicates to the server that HTTP persistent connections should be used if supported. Note: Not all servers support persistent connections. You also may explicitly add the Keep-Alive header to the request headers by setting OtherHeaders to Connection: Keep-Alive. If False, the connection will be closed immediately after the server response is received.

The default value for KeepAlive is False.

KerberosSPN:   The Service Principal Name for the Kerberos Domain Controller.

If the Service Principal Name on the Kerberos Domain Controller is not the same as the URL that you are authenticating to, the Service Principal Name should be set here.

LogLevel:   The level of detail that is logged.

This configuration setting controls the level of detail that is logged through the Log event. Possible values are as follows:

0 (None) No events are logged.
1 (Info - default) Informational events are logged.
2 (Verbose) Detailed data are logged.
3 (Debug) Debug data are logged.

The value 1 (Info) logs basic information, including the URL, HTTP version, and status details.

The value 2 (Verbose) logs additional information about the request and response.

The value 3 (Debug) logs the headers and body for both the request and response, as well as additional debug information (if any).

MaxHeaders:   Instructs component to save the amount of headers specified that are returned by the server after a Header event has been fired.

This configuration setting should be set when the TransferredHeaders collection is to be populated when a Header event has been fired. This value represents the number of headers that are to be saved in the collection.

To save all items to the collection, set this configuration setting to -1. If no items are wanted, set this to 0, which will not save any items to the collection. The default for this configuration setting is -1, so all items will be included in the collection.

MaxHTTPCookies:   Instructs component to save the amount of cookies specified that are returned by the server when a SetCookie event is fired.

This configuration setting should be set when populating the Cookies collection as a result of an HTTP request. This value represents the number of cookies that are to be saved in the collection.

To save all items to the collection, set this configuration setting to -1. If no items are wanted, set this to 0, which will not save any items to the collection. The default for this configuration setting is -1, so all items will be included in the collection.

MaxRedirectAttempts:   Limits the number of redirects that are followed in a request.

When FollowRedirects is set to any value other than frNever, the component will follow redirects until this maximum number of redirect attempts are made. The default value is 20.

NegotiatedHTTPVersion:   The negotiated HTTP version.

This configuration setting may be queried after the request is complete to indicate the HTTP version used. When HTTPVersion is set to "2.0" (if the server does not support "2.0"), then the component will fall back to using "1.1" automatically. This setting will indicate which version was used.

OtherHeaders:   Other headers as determined by the user (optional).

This configuration setting can be set to a string of headers to be appended to the HTTP request headers.

The headers must follow the format "header: value" as described in the HTTP specifications. Header lines should be separated by CRLF ("\r\n") .

Use this configuration setting with caution. If this configuration setting contains invalid headers, HTTP requests may fail.

This configuration setting is useful for extending the functionality of the component beyond what is provided.

ProxyAuthorization:   The authorization string to be sent to the proxy server.

This is similar to the Authorization configuration setting, but is used for proxy authorization. If this configuration setting contains a nonempty string, a Proxy-Authorization HTTP request header is added to the request. This header conveys proxy Authorization information to the server. If User and Password are specified, this value is calculated using the algorithm specified by AuthScheme.

ProxyAuthScheme:   The authorization scheme to be used for the proxy.

This configuration setting is provided for use by components that do not directly expose Proxy properties.

ProxyPassword:   A password if authentication is to be used for the proxy.

This configuration setting is provided for use by components that do not directly expose Proxy properties.

ProxyPort:   Port for the proxy server (default 80).

This configuration setting is provided for use by components that do not directly expose Proxy properties.

ProxyServer:   Name or IP address of a proxy server (optional).

This configuration setting is provided for use by components that do not directly expose Proxy properties.

ProxyUser:   A user name if authentication is to be used for the proxy.

This configuration setting is provided for use by components that do not directly expose Proxy properties.

SentHeaders:   The full set of headers as sent by the client.

This configuration setting returns the complete set of raw headers as sent by the client.

StatusLine:   The first line of the last response from the server.

This setting contains the first line of the last response from the server. The format of the line will be [HTTP version] [Result Code] [Description].

TransferredData:   The contents of the last response from the server.

This configuration setting contains the contents of the last response from the server.

TransferredDataLimit:   The maximum number of incoming bytes to be stored by the component.

If TransferredDataLimit is set to 0 (default), no limits are imposed. Otherwise, this reflects the maximum number of incoming bytes that can be stored by the component.

TransferredHeaders:   The full set of headers as received from the server.

This configuration setting returns the complete set of raw headers as received from the server.

TransferredRequest:   The full request as sent by the client.

This configuration setting returns the full request as sent by the client. For performance reasons, the request is not normally saved. Set this configuration setting to ON before making a request to enable it. Following are examples of this request:

.NET Http http = new Http(); http.Config("TransferredRequest=on"); http.PostData = "body"; http.Post("http://someserver.com"); Console.WriteLine(http.Config("TransferredRequest")); C++ HTTP http; http.Config("TransferredRequest=on"); http.SetPostData("body", 5); http.Post("http://someserver.com"); printf("%s\r\n", http.Config("TransferredRequest"));

UseChunkedEncoding:   Enables or Disables HTTP chunked encoding for transfers.

If UseChunkedEncoding is set to True, the component will use HTTP-chunked encoding when posting, if possible. HTTP-chunked encoding allows large files to be sent in chunks instead of all at once. If set to False, the component will not use HTTP-chunked encoding. The default value is False.

Note: Some servers (such as the ASP.NET Development Server) may not support chunked encoding.

UseIDNs:   Whether to encode hostnames to internationalized domain names.

This configuration setting specifies whether hostnames containing non-ASCII characters are encoded to internationalized domain names. When set to True, if a hostname contains non-ASCII characters, it is encoded using Punycode to an IDN (internationalized domain name).

The default value is False and the hostname will always be used exactly as specified.

UsePlatformDeflate:   Whether to use the platform implementation to decompress compressed responses.

This configuration setting specifies whether the platform's deflate-algorithm implementation is used to decompress responses that use compression. If set to True (default), the platform implementation is used. If set to False, an internal implementation is used.

UsePlatformHTTPClient:   Whether or not to use the platform HTTP client.

When using this configuration setting, if True, the component will use the default HTTP client for the platform (URLConnection in Java, WebRequest in .NET, or CFHTTPMessage in Mac/iOS) instead of the internal HTTP implementation. This is important for environments in which direct access to sockets is limited or not allowed (e.g., in the Google AppEngine).

UseProxyAutoConfigURL:   Whether to use a Proxy auto-config file when attempting a connection.

This configuration specifies whether the component will attempt to use the Proxy auto-config URL when establishing a connection and AutoDetect is set to True.

When True (default), the component will check for the existence of a Proxy auto-config URL, and if found, will determine the appropriate proxy to use.

UserAgent:   Information about the user agent (browser).

This is the value supplied in the HTTP User-Agent header. The default setting is "IPWorks HTTP Component - www.nsoftware.com".

Override the default with the name and version of your software.

TCPClient Config Settings

CloseStreamAfterTransfer:   If true, the component will close the upload or download stream after the transfer.

This setting determines whether the input or output stream is closed after the transfer completes. When set to True (default), all streams will be closed after a transfer is completed. In order to keep streams open after the transfer of data, set this to False. the default value is True.

ConnectionTimeout:   Sets a separate timeout value for establishing a connection.

When set, this configuration setting allows you to specify a different timeout value for establishing a connection. Otherwise, the component will use Timeout for establishing a connection and transmitting/receiving data.

FirewallAutoDetect:   Tells the component whether or not to automatically detect and use firewall system settings, if available.

This configuration setting is provided for use by components that do not directly expose Firewall properties.

FirewallHost:   Name or IP address of firewall (optional).

If a FirewallHost is given, requested connections will be authenticated through the specified firewall when connecting.

If the FirewallHost setting is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the FirewallHost setting is set to the corresponding address. If the search is not successful, an error is returned.

Note: This setting is provided for use by components that do not directly expose Firewall properties.

FirewallListener:   If true, the component binds to a SOCKS firewall as a server (TCPClient only).

This entry is for TCPClient only and does not work for other components that descend from TCPClient.

If this entry is set, the component acts as a server. RemoteHost and RemotePort are used to tell the SOCKS firewall in which address and port to listen to. The firewall rules may ignore RemoteHost, and it is recommended that RemoteHost be set to empty string in this case.

RemotePort is the port in which the firewall will listen to. If set to 0, the firewall will select a random port. The binding (address and port) is provided through the ConnectionStatus event.

The connection to the firewall is made by calling the Connect method.

FirewallPassword:   Password to be used if authentication is to be used when connecting through the firewall.

If FirewallHost is specified, the FirewallUser and FirewallPassword settings are used to connect and authenticate to the given firewall. If the authentication fails, the component throws an exception.

Note: This setting is provided for use by components that do not directly expose Firewall properties.

FirewallPort:   The TCP port for the FirewallHost;.

The FirewallPort is set automatically when FirewallType is set to a valid value.

Note: This configuration setting is provided for use by components that do not directly expose Firewall properties.

FirewallType:   Determines the type of firewall to connect through.

The appropriate values are as follows:

0No firewall (default setting).
1Connect through a tunneling proxy. FirewallPort is set to 80.
2Connect through a SOCKS4 Proxy. FirewallPort is set to 1080.
3Connect through a SOCKS5 Proxy. FirewallPort is set to 1080.
10Connect through a SOCKS4A Proxy. FirewallPort is set to 1080.

Note: This setting is provided for use by components that do not directly expose Firewall properties.

FirewallUser:   A user name if authentication is to be used connecting through a firewall.

If the FirewallHost is specified, the FirewallUser and FirewallPassword settings are used to connect and authenticate to the Firewall. If the authentication fails, the component throws an exception.

Note: This setting is provided for use by components that do not directly expose Firewall properties.

KeepAliveInterval:   The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.

When set, TCPKeepAlive will automatically be set to True. A TCP keep-alive packet will be sent after a period of inactivity as defined by KeepAliveTime. If no acknowledgment is received from the remote host, the keep-alive packet will be sent again. This configuration setting specifies the interval at which the successive keep-alive packets are sent in milliseconds. This system default if this value is not specified here is 1 second.

Note: This value is not applicable in macOS.

KeepAliveTime:   The inactivity time in milliseconds before a TCP keep-alive packet is sent.

When set, TCPKeepAlive will automatically be set to True. By default, the operating system will determine the time a connection is idle before a Transmission Control Protocol (TCP) keep-alive packet is sent. This system default if this value is not specified here is 2 hours. In many cases, a shorter interval is more useful. Set this value to the desired interval in milliseconds.

Linger:   When set to True, connections are terminated gracefully.

This property controls how a connection is closed. The default is True.

In the case that Linger is True (default), two scenarios determine how long the connection will linger. In the first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP timeout expires.

In the second scenario, if LingerTime is a positive value, the system will attempt to send pending data until the specified LingerTime is reached. If this attempt fails, then the system will reset the connection.

The default behavior (which is also the default mode for stream sockets) might result in a long delay in closing the connection. Although the component returns control immediately, the system could hold system resources until all pending data are sent (even after your application closes).

Setting this property to False forces an immediate disconnection. If you know that the other side has received all the data you sent (e.g., by a client acknowledgment), setting this property to False might be the appropriate course of action.

LingerTime:   Time in seconds to have the connection linger.

LingerTime is the time, in seconds, the socket connection will linger. This value is 0 by default, which means it will use the default IP timeout.

LocalHost:   The name of the local host through which connections are initiated or accepted.

The LocalHost setting contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.

If the component is connected, the LocalHost setting shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).

LocalPort:   The port in the local host where the component binds.

This must be set before a connection is attempted. It instructs the component to bind to a specific port (or communication endpoint) in the local machine.

Setting this to 0 (default) enables the system to choose a port at random. The chosen port will be shown by LocalPort after the connection is established.

LocalPort cannot be changed once a connection is made. Any attempt to set this when a connection is active will generate an error.

This; setting is useful when trying to connect to services that require a trusted port in the client side. An example is the remote shell (rsh) service in UNIX systems.

MaxLineLength:   The maximum amount of data to accumulate when no EOL is found.

MaxLineLength is the size of an internal buffer, which holds received data while waiting for an EOL string.

If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset.

If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset.

The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes.

MaxTransferRate:   The transfer rate limit in bytes per second.

This configuration setting can be used to throttle outbound TCP traffic. Set this to the number of bytes to be sent per second. By default, this is not set and there is no limit.

ProxyExceptionsList:   A semicolon separated list of hosts and IPs to bypass when using a proxy.

This configuration setting optionally specifies a semicolon-separated list of hostnames or IP addresses to bypass when a proxy is in use. When requests are made to hosts specified in this property, the proxy will not be used. For instance:

www.google.com;www.nsoftware.com

TCPKeepAlive:   Determines whether or not the keep alive socket option is enabled.

If set to True, the socket's keep-alive option is enabled and keep-alive packets will be sent periodically to maintain the connection. Set KeepAliveTime and KeepAliveInterval to configure the timing of the keep-alive packets.

Note: This value is not applicable in Java.

TcpNoDelay:   Whether or not to delay when sending packets.

When true, the socket will send all data that is ready to send at once. When false, the socket will send smaller buffered packets of data at small intervals. This is known as the Nagle algorithm.

By default, this config is set to false.

UseIPv6:   Whether to use IPv6.

When set to 0 (default), the component will use IPv4 exclusively. When set to 1, the component will use IPv6 exclusively. To instruct the component to prefer IPv6 addresses, but use IPv4 if IPv6 is not supported on the system, this setting should be set to 2. The default value is 0. Possible values are:

0 IPv4 Only
1 IPv6 Only
2 IPv6 with IPv4 fallback

UseNTLMv2:   Whether to use NTLM V2.

When authenticating with NTLM, this setting specifies whether NTLM V2 is used. By default this value is False and NTLM V1 will be used. Set this to True to use NTLM V2.

SSL Config Settings

CACertFilePaths:   The paths to CA certificate files when using Mono on Unix/Linux.

This setting specifies the paths on disk to CA certificate files when using Mono on Unix/Linux. It is not applicable in any other circumstances.

The value is formatted as a list of paths separated by semicolons. The component will check for the existence of each file in the order specified. When a file is found the CA certificates within the file will be loaded and used to determine the validity of server or client certificates.

The default value is:

/etc/ssl/ca-bundle.pem;/etc/pki/tls/certs/ca-bundle.crt;/etc/ssl/certs/ca-certificates.crt;/etc/pki/tls/cacert.pem

LogSSLPackets:   Controls whether SSL packets are logged when using the internal security API.

When SSLProvider is set to Internal, this setting controls whether SSL packets should be logged. By default, this setting is False, as it is only useful for debugging purposes.

When enabled, SSL packet logs are output using the SSLStatus event, which will fire each time an SSL packet is sent or received.

Enabling this setting has no effect if SSLProvider is set to Platform.

ReuseSSLSession:   Determines if the SSL session is reused.

If set to true, the component will reuse the context if and only if the following criteria are met:

  • The target host name is the same.
  • The system cache entry has not expired (default timeout is 10 hours).
  • The application process that calls the function is the same.
  • The logon session is the same.
  • The instance of the component is the same.

SSLCACerts:   A newline separated list of CA certificate to use during SSL client authentication.

This setting specifies one or more CA certificates to be included in the request when performing SSL client authentication. Some servers require the entire chain, including CA certificates, to be presented when performing SSL client authentication. The value of this setting is a newline (CrLf) separated list of certificates. For instance:

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

SSLCheckCRL:   Whether to check the Certificate Revocation List for the server certificate.

This setting specifies whether the component will check the Certificate Revocation List specified by the server certificate. If set to 1 or 2, the component will first obtain the list of CRL URLs from the server certificate's CRL distribution points extension. The component will then make HTTP requests to each CRL endpoint to check the validity of the server's certificate. If the certificate has been revoked or any other issues are found during validation the component throws an exception.

When set to 0 (default) the CRL check will not be performed by the component. When set to 1, it will attempt to perform the CRL check, but will continue without an error if the server's certificate does not support CRL. When set to 2, it will perform the CRL check and will throw an error if CRL is not supported.

This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.

SSLCheckOCSP:   Whether to use OCSP to check the status of the server certificate.

This setting specifies whether the component will use OCSP to check the validity of the server certificate. If set to 1 or 2, the component will first obtain the OCSP URL from the server certificate's OCSP extension. The component will then locate the issuing certificate and make an HTTP request to the OCSP endpoint to check the validity of the server's certificate. If the certificate has been revoked or any other issues are found during validation the component throws an exception.

When set to 0 (default) the component will not perform an OCSP check. When set to 1, it will attempt to perform the OCSP check, but will continue without an error if the server's certificate does not support OCSP. When set to 2, it will perform the OCSP check and will throw an error if OCSP is not supported.

This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.

SSLCipherStrength:   The minimum cipher strength used for bulk encryption.

This minimum cipher strength largely dependent on the security modules installed on the system. If the cipher strength specified is not supported, an error will be returned when connections are initiated.

Please note that this setting contains the minimum cipher strength requested from the security library. The actual cipher strength used for the connection is shown by the SSLStatus event.

Use this setting with caution. Requesting a lower cipher strength than necessary could potentially cause serious security vulnerabilities in your application.

When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList config setting.

SSLEnabledCipherSuites:   The cipher suite to be used in an SSL negotiation.

The enabled cipher suites to be used in SSL negotiation.

By default, the enabled cipher suites will include all available ciphers ("*").

The special value "*" means that the component will pick all of the supported cipher suites. If SSLEnabledCipherSuites is set to any other value, only the specified cipher suites will be considered.

Multiple cipher suites are separated by semicolons.

Example values when SSLProvider is set to Platform: obj.config("SSLEnabledCipherSuites=*"); obj.config("SSLEnabledCipherSuites=CALG_AES_256"); obj.config("SSLEnabledCipherSuites=CALG_AES_256;CALG_3DES"); Possible values when SSLProvider is set to Platform include:

  • CALG_3DES
  • CALG_3DES_112
  • CALG_AES
  • CALG_AES_128
  • CALG_AES_192
  • CALG_AES_256
  • CALG_AGREEDKEY_ANY
  • CALG_CYLINK_MEK
  • CALG_DES
  • CALG_DESX
  • CALG_DH_EPHEM
  • CALG_DH_SF
  • CALG_DSS_SIGN
  • CALG_ECDH
  • CALG_ECDH_EPHEM
  • CALG_ECDSA
  • CALG_ECMQV
  • CALG_HASH_REPLACE_OWF
  • CALG_HUGHES_MD5
  • CALG_HMAC
  • CALG_KEA_KEYX
  • CALG_MAC
  • CALG_MD2
  • CALG_MD4
  • CALG_MD5
  • CALG_NO_SIGN
  • CALG_OID_INFO_CNG_ONLY
  • CALG_OID_INFO_PARAMETERS
  • CALG_PCT1_MASTER
  • CALG_RC2
  • CALG_RC4
  • CALG_RC5
  • CALG_RSA_KEYX
  • CALG_RSA_SIGN
  • CALG_SCHANNEL_ENC_KEY
  • CALG_SCHANNEL_MAC_KEY
  • CALG_SCHANNEL_MASTER_HASH
  • CALG_SEAL
  • CALG_SHA
  • CALG_SHA1
  • CALG_SHA_256
  • CALG_SHA_384
  • CALG_SHA_512
  • CALG_SKIPJACK
  • CALG_SSL2_MASTER
  • CALG_SSL3_MASTER
  • CALG_SSL3_SHAMD5
  • CALG_TEK
  • CALG_TLS1_MASTER
  • CALG_TLS1PRF
Example values when SSLProvider is set to Internal: obj.config("SSLEnabledCipherSuites=*"); obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA"); obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA;TLS_DH_ANON_WITH_AES_128_CBC_SHA"); Possible values when SSLProvider is set to Internal include:
  • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_AES_256_GCM_SHA384
  • TLS_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
  • TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
  • TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (Not Recommended)
  • TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (Not Recommended)
  • TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (Not Recommended)
  • TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (Not Recommended)
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
  • TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
  • TLS_DHE_DSS_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  • TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
  • TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_DHE_DSS_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
  • TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
  • TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA
  • TLS_RSA_WITH_DES_CBC_SHA
  • TLS_DHE_RSA_WITH_DES_CBC_SHA
  • TLS_DHE_DSS_WITH_DES_CBC_SHA
  • TLS_RSA_WITH_RC4_128_MD5
  • TLS_RSA_WITH_RC4_128_SHA

When TLS 1.3 is negotiated (see SSLEnabledProtocols) only the following cipher suites are supported:

  • TLS_AES_256_GCM_SHA384
  • TLS_CHACHA20_POLY1305_SHA256
  • TLS_AES_128_GCM_SHA256

SSLEnabledCipherSuites is used together with SSLCipherStrength.

SSLEnabledProtocols:   Used to enable/disable the supported security protocols.

Used to enable/disable the supported security protocols.

Not all supported protocols are enabled by default (the value of this setting is 4032). If you want more granular control over the enabled protocols, you can set this property to the binary 'OR' of one or more of the following values:

TLS1.312288 (Hex 3000)
TLS1.23072 (Hex C00) (Default)
TLS1.1768 (Hex 300) (Default)
TLS1 192 (Hex C0) (Default)
SSL3 48 (Hex 30)
SSL2 12 (Hex 0C)

SSLEnabledProtocols - TLS 1.3 Notes

By default when TLS 1.3 is enabled the component will use the internal TLS implementation when the SSLProvider is set to Automatic for all editions.

In editions which are designed to run on Windows SSLProvider can be set to Platform to use the platform implementation instead of the internal implementation. When configured in this manner, please note that the platform provider is only supported on Windows 11 / Windows Server 2022 and up. The default internal provider is available on all platforms and is not restricted to any specific OS version.

If set to 1 (Platform provider) please be aware of the following notes:

  • The platform provider is only available on Windows 11 / Windows Server 2022 and up.
  • SSLEnabledCipherSuites and other similar SSL configuration settings are not supported.
  • If SSLEnabledProtocols includes both TLS 1.3 and TLS 1.2 the above restrictions are still applicable even if TLS 1.2 is negotiated. Enabling TLS 1.3 with the platform provider changes the implementation used for all TLS versions.

SSLEnableRenegotiation:   Whether the renegotiation_info SSL extension is supported.

This setting specifies whether the renegotiation_info SSL extension will be used in the request when using the internal security API. This setting is true by default, but can be set to false to disable the extension.

This setting is only applicable when SSLProvider is set to Internal.

SSLIncludeCertChain:   Whether the entire certificate chain is included in the SSLServerAuthentication event.

This setting specifies whether the Encoded parameter of the SSLServerAuthentication event contains the full certificate chain. By default this value is False and only the leaf certificate will be present in the Encoded parameter of the SSLServerAuthentication event.

If set to True all certificates returned by the server will be present in the Encoded parameter of the SSLServerAuthentication event. This includes the leaf certificate, any intermediate certificate, and the root certificate.

Note: When SSLProvider is set to Internal this value is automatically set to true. This is needed for proper validation when using the internal provider.

SSLKeyLogFile:   The location of a file where per-session secrets are written for debugging purposes.

This setting optionally specifies the full path to a file on disk where per-session secrets are stored for debugging purposes.

When set, the component will save the session secrets in the same format as the SSLKEYLOGFILE environment variable functionality used by most major browsers and tools such as Chrome, Firefox, and cURL. This file can then be used in tools such as Wireshark to decrypt TLS traffice for debugging purposes. When writing to this file the component will only append, it will not overwrite previous values.

Note: This setting is only applicable when SSLProvider is set to Internal.

SSLNegotiatedCipher:   Returns the negotiated ciphersuite.

Returns the ciphersuite negotiated during the SSL handshake.

Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedCipher[connId]");

SSLNegotiatedCipherStrength:   Returns the negotiated ciphersuite strength.

Returns the strength of the ciphersuite negotiated during the SSL handshake.

Note: For server components (e.g.TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedCipherStrength[connId]");

SSLNegotiatedCipherSuite:   Returns the negotiated ciphersuite.

Returns the ciphersuite negotiated during the SSL handshake represented as a single string.

Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedCipherSuite[connId]");

SSLNegotiatedKeyExchange:   Returns the negotiated key exchange algorithm.

Returns the key exchange algorithm negotiated during the SSL handshake.

Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedKeyExchange[connId]");

SSLNegotiatedKeyExchangeStrength:   Returns the negotiated key exchange algorithm strength.

Returns the strenghth of the key exchange algorithm negotiated during the SSL handshake.

Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedKeyExchangeStrength[connId]");

SSLNegotiatedVersion:   Returns the negotiated protocol version.

Returns the protocol version negotiated during the SSL handshake.

Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example: server.Config("SSLNegotiatedVersion[connId]");

SSLSecurityFlags:   Flags that control certificate verification.

The following flags are defined (specified in hexadecimal notation). They can be or-ed together to exclude multiple conditions:

0x00000001Ignore time validity status of certificate.
0x00000002Ignore time validity status of CTL.
0x00000004Ignore non-nested certificate times.
0x00000010Allow unknown Certificate Authority.
0x00000020Ignore wrong certificate usage.
0x00000100Ignore unknown certificate revocation status.
0x00000200Ignore unknown CTL signer revocation status.
0x00000400Ignore unknown Certificate Authority revocation status.
0x00000800Ignore unknown Root revocation status.
0x00008000Allow test Root certificate.
0x00004000Trust test Root certificate.
0x80000000Ignore non-matching CN (certificate CN not-matching server name).

This functionality is currently not available in Java or when the provider is OpenSSL.

SSLServerCACerts:   A newline separated list of CA certificate to use during SSL server certificate validation.

This setting optionally specifies one or more CA certificates to be used when verifying the server certificate. When verifying the server's certificate the certificates trusted by the system will be used as part of the verification process. If the server's CA certificates are not installed to the trusted system store, they may be specified here so they are included when performing the verification process. This setting should only be set if the server's CA certificates are not already trusted on the system and cannot be installed to the trusted system store.

The value of this setting is a newline (CrLf) separated list of certificates. For instance:

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

TLS12SignatureAlgorithms:   Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal.

This setting specifies the allowed server certificate signature algorithms when SSLProvider is set to Internal and SSLEnabledProtocols is set to allow TLS 1.2.

When specified the component will verify that the server certificate signature algorithm is among the values specified in this setting. If the server certificate signature algorithm is unsupported the component throws an exception.

The format of this value is a comma separated list of hash-signature combinations. For instance: component.SSLProvider = TCPClientSSLProviders.sslpInternal; component.Config("SSLEnabledProtocols=3072"); //TLS 1.2 component.Config("TLS12SignatureAlgorithms=sha256-rsa,sha256-dsa,sha1-rsa,sha1-dsa"); The default value for this setting is sha512-ecdsa,sha512-rsa,sha512-dsa,sha384-ecdsa,sha384-rsa,sha384-dsa,sha256-ecdsa,sha256-rsa,sha256-dsa,sha224-ecdsa,sha224-rsa,sha224-dsa,sha1-ecdsa,sha1-rsa,sha1-dsa.

In order to not restrict the server's certificate signature algorithm, specify an empty string as the value for this setting, which will cause the signature_algorithms TLS 1.2 extension to not be sent.

TLS12SupportedGroups:   The supported groups for ECC.

This setting specifies a comma separated list of named groups used in TLS 1.2 for ECC.

The default value is ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1.

When using TLS 1.2 and SSLProvider is set to Internal, the values refer to the supported groups for ECC. The following values are supported:

  • "ecdhe_secp256r1" (default)
  • "ecdhe_secp384r1" (default)
  • "ecdhe_secp521r1" (default)

TLS13KeyShareGroups:   The groups for which to pregenerate key shares.

This setting specifies a comma separated list of named groups used in TLS 1.3 for key exchange. The groups specified here will have key share data pregenerated locally before establishing a connection. This can prevent an additional round trip during the handshake if the group is supported by the server.

The default value is set to balance common supported groups and the computational resources required to generate key shares. As a result only some groups are included by default in this setting.

Note: All supported groups can always be used during the handshake even if not listed here, but if a group is used which is not present in this list it will incur an additional round trip and time to generate the key share for that group.

In most cases this setting does not need to be modified. This should only be modified if there is a specific reason to do so.

The default value is ecdhe_x25519,ecdhe_secp256r1,ecdhe_secp384r1,ffdhe_2048,ffdhe_3072

The values are ordered from most preferred to least preferred. The following values are supported:

  • "ecdhe_x25519" (default)
  • "ecdhe_x448"
  • "ecdhe_secp256r1" (default)
  • "ecdhe_secp384r1" (default)
  • "ecdhe_secp521r1"
  • "ffdhe_2048" (default)
  • "ffdhe_3072" (default)
  • "ffdhe_4096"
  • "ffdhe_6144"
  • "ffdhe_8192"

TLS13SignatureAlgorithms:   The allowed certificate signature algorithms.

This setting holds a comma separated list of allowed signature algorithms. Possible values are:

  • "ed25519" (default)
  • "ed448" (default)
  • "ecdsa_secp256r1_sha256" (default)
  • "ecdsa_secp384r1_sha384" (default)
  • "ecdsa_secp521r1_sha512" (default)
  • "rsa_pkcs1_sha256" (default)
  • "rsa_pkcs1_sha384" (default)
  • "rsa_pkcs1_sha512" (default)
  • "rsa_pss_sha256" (default)
  • "rsa_pss_sha384" (default)
  • "rsa_pss_sha512" (default)
The default value is rsa_pss_sha256,rsa_pss_sha384,rsa_pss_sha512,rsa_pkcs1_sha256,rsa_pkcs1_sha384,rsa_pkcs1_sha512,ecdsa_secp256r1_sha256,ecdsa_secp384r1_sha384,ecdsa_secp521r1_sha512,ed25519,ed448. This setting is only applicable when SSLEnabledProtocols includes TLS 1.3.
TLS13SupportedGroups:   The supported groups for (EC)DHE key exchange.

This setting specifies a comma separated list of named groups used in TLS 1.3 for key exchange. This setting should only be modified if there is a specific reason to do so.

The default value is ecdhe_x25519,ecdhe_x448,ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1,ffdhe_2048,ffdhe_3072,ffdhe_4096,ffdhe_6144,ffdhe_8192

The values are ordered from most preferred to least preferred. The following values are supported:

  • "ecdhe_x25519" (default)
  • "ecdhe_x448" (default)
  • "ecdhe_secp256r1" (default)
  • "ecdhe_secp384r1" (default)
  • "ecdhe_secp521r1" (default)
  • "ffdhe_2048" (default)
  • "ffdhe_3072" (default)
  • "ffdhe_4096" (default)
  • "ffdhe_6144" (default)
  • "ffdhe_8192" (default)

Socket Config Settings

AbsoluteTimeout:   Determines whether timeouts are inactivity timeouts or absolute timeouts.

If AbsoluteTimeout is set to True, any method which does not complete within Timeout seconds will be aborted. By default, AbsoluteTimeout is False, and the timeout is an inactivity timeout.

Note: This option is not valid for UDP ports.

FirewallData:   Used to send extra data to the firewall.

When the firewall is a tunneling proxy, use this property to send custom (additional) headers to the firewall (e.g. headers for custom authentication schemes).

InBufferSize:   The size in bytes of the incoming queue of the socket.

This is the size of an internal queue in the TCP/IP stack. You can increase or decrease its size depending on the amount of data that you will be receiving. Increasing the value of the InBufferSize setting can provide significant improvements in performance in some cases.

Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the InBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.

OutBufferSize:   The size in bytes of the outgoing queue of the socket.

This is the size of an internal queue in the TCP/IP stack. You can increase or decrease its size depending on the amount of data that you will be sending. Increasing the value of the OutBufferSize setting can provide significant improvements in performance in some cases.

Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the OutBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.

Base Config Settings

BuildInfo:   Information about the product's build.

When queried, this setting will return a string containing information about the product's build.

GUIAvailable:   Tells the component whether or not a message loop is available for processing events.

In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the component does not attempt to process external events.

LicenseInfo:   Information about the current license.

When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

  • Product: The product the license is for.
  • Product Key: The key the license was generated from.
  • License Source: Where the license was found (e.g., RuntimeLicense, License File).
  • License Type: The type of license installed (e.g., Royalty Free, Single Server).
  • Last Valid Build: The last valid build number for which the license will work.
MaskSensitive:   Whether sensitive data is masked in log messages.

In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to true to mask sensitive data. The default is true.

This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.

UseInternalSecurityAPI:   Tells the component whether or not to use the system security libraries or an internal implementation.

When set to false, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments this is not desirable. To use a completely managed security implementation set this setting to true.

Setting this setting to true tells the component to use the internal implementation instead of using the system security libraries.

On Windows, this setting is set to false by default. On Linux/macOS, this setting is set to true by default.

If using the .NET Standard Library, this setting will be true on all platforms. The .NET Standard library does not support using the system security libraries.

Note: This setting is static. The value set is applicable to all components used in the application.

When this value is set the product's system DLL is no longer required as a reference, as all unmanaged code is stored in that file.

Trappable Errors (ICharge Component)

ICharge Errors

159   Invalid form variable index (out of range).
501   Data field invalid length.
502   Data field invalid format.
503   Data field out of range.
504   Luhn digit check failed.
505   Card date invalid.
506   Card expired.
507   Card type unknown.
510   No gateway specified.
511   Invalid data entered.
512   Truncated response.
513   Invalid response.
514   A Special Field is required for this transaction type.
535   Signature verification failed.
542   Error computing MD5 hash for Authorize.Net
593   Required properties are missing from request.

CardValidator Errors

504   Luhn digit check failed.
505   Card date invalid.
506   Card expired.
703   Invalid CardNumber format (contains letters or unknown characters).
704   Could not determine the Credit Card type.
705   Error parsing TrackData. Format cannot be determined.

The component may also return one of the following error codes, which are inherited from other components.

HTTP Errors

118   Firewall Error. Error description contains detailed message.
143   Busy executing current method.
151   HTTP protocol error. The error message has the server response.
152   No server specified in URL
153   Specified URLScheme is invalid.
155   Range operation is not supported by server.
156   Invalid cookie index (out of range).
301   Interrupted.
302   Can't open AttachedFile.

The component may also return one of the following error codes, which are inherited from other components.

TCPClient Errors

100   You cannot change the RemotePort at this time. A connection is in progress.
101   You cannot change the RemoteHost (Server) at this time. A connection is in progress.
102   The RemoteHost address is invalid (0.0.0.0).
104   Already connected. If you want to reconnect, close the current connection first.
106   You cannot change the LocalPort at this time. A connection is in progress.
107   You cannot change the LocalHost at this time. A connection is in progress.
112   You cannot change MaxLineLength at this time. A connection is in progress.
116   RemotePort cannot be zero. Please specify a valid service port number.
117   You cannot change the UseConnection option while the component is active.
135   Operation would block.
201   Timeout.
211   Action impossible in control's present state.
212   Action impossible while not connected.
213   Action impossible while listening.
301   Timeout.
303   Could not open file.
434   Unable to convert string to selected CodePage.
1105   Already connecting. If you want to reconnect, close the current connection first.
1117   You need to connect first.
1119   You cannot change the LocalHost at this time. A connection is in progress.
1120   Connection dropped by remote host.

SSL Errors

270   Cannot load specified security library.
271   Cannot open certificate store.
272   Cannot find specified certificate.
273   Cannot acquire security credentials.
274   Cannot find certificate chain.
275   Cannot verify certificate chain.
276   Error during handshake.
280   Error verifying certificate.
281   Could not find client certificate.
282   Could not find server certificate.
283   Error encrypting data.
284   Error decrypting data.

TCP/IP Errors

10004   [10004] Interrupted system call.
10009   [10009] Bad file number.
10013   [10013] Access denied.
10014   [10014] Bad address.
10022   [10022] Invalid argument.
10024   [10024] Too many open files.
10035   [10035] Operation would block.
10036   [10036] Operation now in progress.
10037   [10037] Operation already in progress.
10038   [10038] Socket operation on non-socket.
10039   [10039] Destination address required.
10040   [10040] Message too long.
10041   [10041] Protocol wrong type for socket.
10042   [10042] Bad protocol option.
10043   [10043] Protocol not supported.
10044   [10044] Socket type not supported.
10045   [10045] Operation not supported on socket.
10046   [10046] Protocol family not supported.
10047   [10047] Address family not supported by protocol family.
10048   [10048] Address already in use.
10049   [10049] Can't assign requested address.
10050   [10050] Network is down.
10051   [10051] Network is unreachable.
10052   [10052] Net dropped connection or reset.
10053   [10053] Software caused connection abort.
10054   [10054] Connection reset by peer.
10055   [10055] No buffer space available.
10056   [10056] Socket is already connected.
10057   [10057] Socket is not connected.
10058   [10058] Can't send after socket shutdown.
10059   [10059] Too many references, can't splice.
10060   [10060] Connection timed out.
10061   [10061] Connection refused.
10062   [10062] Too many levels of symbolic links.
10063   [10063] File name too long.
10064   [10064] Host is down.
10065   [10065] No route to host.
10066   [10066] Directory not empty
10067   [10067] Too many processes.
10068   [10068] Too many users.
10069   [10069] Disc Quota Exceeded.
10070   [10070] Stale NFS file handle.
10071   [10071] Too many levels of remote in path.
10091   [10091] Network subsystem is unavailable.
10092   [10092] WINSOCK DLL Version out of range.
10093   [10093] Winsock not loaded yet.
11001   [11001] Host not found.
11002   [11002] Non-authoritative 'Host not found' (try again or check DNS setup).
11003   [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP.
11004   [11004] Valid name, no data record (check DNS setup).

Copyright (c) 2023 4D Payments Inc.
E-Payment Integrator 2022 .NET Edition - Version 22.0 [Build 8593]