E-Payment Integrator 2020 Delphi Edition

Questions / Feedback?

ICharge Configuration

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 Configuration 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.

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.

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.

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 raises 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 property 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".

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 Configuration 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 config 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 setting enables HTTP compression for receiving data. When set to True (default), the component will accept compressed data. It will then 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 config. 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 setting controls whether HTTP/2 connections are permitted to fallback to HTTP/1.1 when the server does not support HTTP/2. This setting is only applicable 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 raises an exception if the server does not support HTTP/2.

The default value is True.

Append:   Whether to append data to LocalFile.

This setting determines whether data is 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 only applicable 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 non-empty 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.

Returns the raw number of bytes from the HTTP response data, prior to the component processing the data, whether it is chunked and/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 only applicable 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 raises an exception.

Note that 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 could potentially change the conditions of the initial request and create security vulnerabilities.

Furthermore, if either the new URL server and port are different than 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 raises an exception instead.

Valid options are:

  • 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 via 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:

  • "1.0"
  • "1.1" (default)
  • "2.0"

When using HTTP/2 ("2.0") additional restrictions apply. Please see notes below for details.

HTTP/2 Notes

When using HTTP/2 only secure (TLS/SSL) connections are currently supported. 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 in order 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 Windows 8.1/Server 2012 R2 or later. If HTTP/2 is used on a version of Windows prior to these versions the component raises an exception.

Note: HTTP/2 is currently only supported on Windows.

IfModifiedSince:   A date determining the maximum age of the desired document.

If this setting contains a non-empty 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. An example is:

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 that not all server support persistent connections. You may also 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 setting controls the level of detail that is logged through the Log event. Possible values are:

0 (None) No events are logged.
1 (Info - default) Informational events are logged.
2 (Verbose) Detailed data is logged.
3 (Debug) Debug data is 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).

MaxRedirectAttempts:   Limits the number of redirects that are followed in a request.

When FollowRedirects is set to any value besides 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 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" the component will fallback to using "1.1" automatically. This setting will indicate which was used.

OtherHeaders:   Other headers as determined by the user (optional).

This configuration option can be set to a string of headers to be appended to the HTTP request headers.

The headers must be of the format "header: value" as described in the HTTP specifications. Header lines should be separated by CRLF ('#13#10') .

Use this configuration option with caution. If this configuration option contains invalid headers, HTTP requests may fail.

This configuration option is useful for extending the functionality of the component beyond what is provided.

ProxyAuthorization:   The authorization string to be sent to the proxy server.

Similar to the Authorization config, but for proxy authorization. If this config contains a non-empty 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 is the same as AuthScheme. This 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 is the same as Password. This setting is provided for use by components that do not directly expose Proxy properties.

ProxyPort:   Port for the proxy server (default 80).

This is the same as Port. This 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 is the same as Server. This 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 is the same as User. This 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 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 config to ON before making a request to enable it. Examples are below.

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

The default value is False and the hostname will always be used exactly as specified. Note: The CodePage setting must be set to a value capable of interpreting the specified host name. For instance to specify UTF-8 set CodePage to 65001.

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.

IPPort Configuration 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 is the same as AutoDetect. This 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 is the same as Host. This setting is provided for use by components that do not directly expose Firewall properties.

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 raises an exception.

NOTE: This is the same as Password. This setting is provided for use by components that do not directly expose Firewall properties.

FirewallPort:   The TCP port for the FirewallHost;.

Note that the FirewallPort is set automatically when FirewallType is set to a valid value.

NOTE: This is the same as Port. This 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 is the same as FirewallType. 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 raises an exception.

NOTE: This is the same as User. 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 acknowledgement is received from the remote host the keep-alive packet will be re-sent. This 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 Java or MAC.

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

Note: This value is not applicable in Java.

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), there are two scenarios for determining how long the connection will linger. The first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP protocol timeout expires.

In the second scenario, 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 is 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 (by a client acknowledgment, for example), 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, to leave the socket connection linger. This value is 0 by default, which means it will use the default IP protocol 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 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 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

SSL Configuration Settings

LogSSLPackets:   Controls whether SSL packets are logged when using the internal security API.

When the UseInternalSecurityAPI configuration setting is True, 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 UseInternalSecurityAPI is False.

OpenSSLCADir:   The path to a directory containing CA certificates.

This functionality is available only when the provider is OpenSSL.

The path set by this property should point to a directory containing CA certificates in PEM format. The files each contain one CA certificate. The files are looked up by the CA subject name hash value, which must hence be available. If more than one CA certificate with the same name hash value exist, the extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). OpenSSL recommends to use the c_rehash utility to create the necessary links. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.

OpenSSLCAFile:   Name of the file containing the list of CA's trusted by your application.

This functionality is available only when the provider is OpenSSL.

The file set by this property should contain a list of CA certificates in PEM format. The file can contain several CA certificates identified by

-----BEGIN CERTIFICATE-----

... (CA certificate in base64 encoding) ...

-----END CERTIFICATE-----

sequences. Before, between, and after the certificates text is allowed which can be used e.g. for descriptions of the certificates. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.

OpenSSLCipherList:   A string that controls the ciphers to be used by SSL.

This functionality is available only when the provider is OpenSSL.

The format of this string is described in the OpenSSL man page ciphers(1) section "CIPHER LIST FORMAT". Please refer to it for details. The default string "DEFAULT" is determined at compile time and is normally equivalent to "ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH".

OpenSSLPrngSeedData:   The data to seed the pseudo random number generator (PRNG).

This functionality is available only when the provider is OpenSSL.

By default OpenSSL uses the device file "/dev/urandom" to seed the PRNG and setting OpenSSLPrngSeedData is not required. If set, the string specified is used to seed the PRNG.

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 True 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 raises an exception.

When set to False (default) the CRL check will not be performed by the component.

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 UseInternalSecurityAPI is False (default):

obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=CALG_AES_256");
obj.config("SSLEnabledCipherSuites=CALG_AES_256;CALG_3DES");
Possible values when UseInternalSecurityAPI is False (default) 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 UseInternalSecurityAPI is True:
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 UseInternalSecurityAPI is True 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
  • TLS_DH_RSA_WITH_AES_256_GCM_SHA384
  • TLS_DH_DSS_WITH_AES_128_GCM_SHA256
  • TLS_DH_DSS_WITH_AES_256_GCM_SHA384
  • 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)

When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList setting.

Note: TLS 1.1 and TLS1.2 support are only available starting with Windows 7.

Note: Enabling TLS 1.3 will automatically set UseInternalSecurityAPI to True.

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 UseInternalSecurityAPI is set to True.

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.

SSLProvider:   The name of the security provider to use.

Change this setting to use security providers other than the system default.

Use this setting with caution. Disabling SSL security or pointing to the wrong provider could potentially cause serious security vulnerabilities in your application.

The special value "*" (default) picks the default SSL provider defined in the system.

Note: On Windows systems, the default SSL Provider is "Microsoft Unified Security Protocol Provider" and cannot be changed .

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 when the provider is OpenSSL.

TLS12SignatureAlgorithms:   Defines the allowed TLS 1.2 signature algorithms when UseInternalSecurityAPI is True.

This setting specifies the allowed server certificate signature algorithms when UseInternalSecurityAPI is True 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 raises an exception.

The format of this value is a comma separated list of hash-signature combinations. For instance:

IPPort.Config("UseInternalSecurityAPI=true");
IPPort.Config("SSLEnabledProtocols=3072"); //TLS 1.2
IPPort.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 UseInternalSecurityAPI is set to True, 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 Configuration 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 Configuration Settings

BuildInfo:   Information about the product's build.

When queried, this setting will return a string containing information about the product's build.

CodePage:   The system code page used for Unicode to Multibyte translations.

The default code page is the Active Code Page (0).

The following is a list of valid code page identifiers:

IdentifierName
037IBM EBCDIC - U.S./Canada
437OEM - United States
500IBM EBCDIC - International
708Arabic - ASMO 708
709Arabic - ASMO 449+, BCON V4
710Arabic - Transparent Arabic
720Arabic - Transparent ASMO
737OEM - Greek (formerly 437G)
775OEM - Baltic
850OEM - Multilingual Latin I
852OEM - Latin II
855OEM - Cyrillic (primarily Russian)
857OEM - Turkish
858OEM - Multlingual Latin I + Euro symbol
860OEM - Portuguese
861OEM - Icelandic
862OEM - Hebrew
863OEM - Canadian-French
864OEM - Arabic
865OEM - Nordic
866OEM - Russian
869OEM - Modern Greek
870IBM EBCDIC - Multilingual/ROECE (Latin-2)
874ANSI/OEM - Thai (same as 28605, ISO 8859-15)
875IBM EBCDIC - Modern Greek
932ANSI/OEM - Japanese, Shift-JIS
936ANSI/OEM - Simplified Chinese (PRC, Singapore)
949ANSI/OEM - Korean (Unified Hangeul Code)
950ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC)
1026IBM EBCDIC - Turkish (Latin-5)
1047IBM EBCDIC - Latin 1/Open System
1140IBM EBCDIC - U.S./Canada (037 + Euro symbol)
1141IBM EBCDIC - Germany (20273 + Euro symbol)
1142IBM EBCDIC - Denmark/Norway (20277 + Euro symbol)
1143IBM EBCDIC - Finland/Sweden (20278 + Euro symbol)
1144IBM EBCDIC - Italy (20280 + Euro symbol)
1145IBM EBCDIC - Latin America/Spain (20284 + Euro symbol)
1146IBM EBCDIC - United Kingdom (20285 + Euro symbol)
1147IBM EBCDIC - France (20297 + Euro symbol)
1148IBM EBCDIC - International (500 + Euro symbol)
1149IBM EBCDIC - Icelandic (20871 + Euro symbol)
1200Unicode UCS-2 Little-Endian (BMP of ISO 10646)
1201Unicode UCS-2 Big-Endian
1250ANSI - Central European
1251ANSI - Cyrillic
1252ANSI - Latin I
1253ANSI - Greek
1254ANSI - Turkish
1255ANSI - Hebrew
1256ANSI - Arabic
1257ANSI - Baltic
1258ANSI/OEM - Vietnamese
1361Korean (Johab)
10000MAC - Roman
10001MAC - Japanese
10002MAC - Traditional Chinese (Big5)
10003MAC - Korean
10004MAC - Arabic
10005MAC - Hebrew
10006MAC - Greek I
10007MAC - Cyrillic
10008MAC - Simplified Chinese (GB 2312)
10010MAC - Romania
10017MAC - Ukraine
10021MAC - Thai
10029MAC - Latin II
10079MAC - Icelandic
10081MAC - Turkish
10082MAC - Croatia
12000Unicode UCS-4 Little-Endian
12001Unicode UCS-4 Big-Endian
20000CNS - Taiwan
20001TCA - Taiwan
20002Eten - Taiwan
20003IBM5550 - Taiwan
20004TeleText - Taiwan
20005Wang - Taiwan
20105IA5 IRV International Alphabet No. 5 (7-bit)
20106IA5 German (7-bit)
20107IA5 Swedish (7-bit)
20108IA5 Norwegian (7-bit)
20127US-ASCII (7-bit)
20261T.61
20269ISO 6937 Non-Spacing Accent
20273IBM EBCDIC - Germany
20277IBM EBCDIC - Denmark/Norway
20278IBM EBCDIC - Finland/Sweden
20280IBM EBCDIC - Italy
20284IBM EBCDIC - Latin America/Spain
20285IBM EBCDIC - United Kingdom
20290IBM EBCDIC - Japanese Katakana Extended
20297IBM EBCDIC - France
20420IBM EBCDIC - Arabic
20423IBM EBCDIC - Greek
20424IBM EBCDIC - Hebrew
20833IBM EBCDIC - Korean Extended
20838IBM EBCDIC - Thai
20866Russian - KOI8-R
20871IBM EBCDIC - Icelandic
20880IBM EBCDIC - Cyrillic (Russian)
20905IBM EBCDIC - Turkish
20924IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol)
20932JIS X 0208-1990 & 0121-1990
20936Simplified Chinese (GB2312)
21025IBM EBCDIC - Cyrillic (Serbian, Bulgarian)
21027Extended Alpha Lowercase
21866Ukrainian (KOI8-U)
28591ISO 8859-1 Latin I
28592ISO 8859-2 Central Europe
28593ISO 8859-3 Latin 3
28594ISO 8859-4 Baltic
28595ISO 8859-5 Cyrillic
28596ISO 8859-6 Arabic
28597ISO 8859-7 Greek
28598ISO 8859-8 Hebrew
28599ISO 8859-9 Latin 5
28605ISO 8859-15 Latin 9
29001Europa 3
38598ISO 8859-8 Hebrew
50220ISO 2022 Japanese with no halfwidth Katakana
50221ISO 2022 Japanese with halfwidth Katakana
50222ISO 2022 Japanese JIS X 0201-1989
50225ISO 2022 Korean
50227ISO 2022 Simplified Chinese
50229ISO 2022 Traditional Chinese
50930Japanese (Katakana) Extended
50931US/Canada and Japanese
50933Korean Extended and Korean
50935Simplified Chinese Extended and Simplified Chinese
50936Simplified Chinese
50937US/Canada and Traditional Chinese
50939Japanese (Latin) Extended and Japanese
51932EUC - Japanese
51936EUC - Simplified Chinese
51949EUC - Korean
51950EUC - Traditional Chinese
52936HZ-GB2312 Simplified Chinese
54936Windows XP: GB18030 Simplified Chinese (4 Byte)
57002ISCII Devanagari
57003ISCII Bengali
57004ISCII Tamil
57005ISCII Telugu
57006ISCII Assamese
57007ISCII Oriya
57008ISCII Kannada
57009ISCII Malayalam
57010ISCII Gujarati
57011ISCII Punjabi
65000Unicode UTF-7
65001Unicode UTF-8

The following is a list of valid code page identifiers for Mac OS only:

IdentifierName
1ASCII
2NEXTSTEP
3JapaneseEUC
4UTF8
5ISOLatin1
6Symbol
7NonLossyASCII
8ShiftJIS
9ISOLatin2
10Unicode
11WindowsCP1251
12WindowsCP1252
13WindowsCP1253
14WindowsCP1254
15WindowsCP1250
21ISO2022JP
30MacOSRoman
10UTF16String
0x90000100UTF16BigEndian
0x94000100UTF16LittleEndian
0x8c000100UTF32String
0x98000100UTF32BigEndian
0x9c000100UTF32LittleEndian
65536Proprietary

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).
UseInternalSecurityAPI:   Tells the component whether or not to use the system security libraries or an internal implementation.

By default the component will use the system security libraries to perform cryptographic functions. Setting this to True tells the component to use the internal implementation instead of using the system's security API.

Copyright (c) 2021 /n software inc. - All rights reserved.
E-Payment Integrator 2020 Delphi Edition - Version 20.0 [Build 7941]