CreditCard Configuration

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

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

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

See the Gateway property to determine if this is an available field for the gateway you are using.

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

Available values are:

• 0 - Not Provided
• 1 - Provided
• 2 - Illegible
• 3 - Not On Card

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

This field contains the expiration year of the customer's credit card. This field may be a two digit representation of the expiration year, in the range 0 - 99 or a four-digit year, in the range 2000 to 2099.

This field contains the customer's credit card number. When this field is set, white space and dashes are stripped out and the CardType field is automatically computed.

When this option is set to "true" and the LogMode is set to "Verbose" the task will log the raw request sent to the gateway and the raw response received back from the gateway in the LogFile. The default is "false".

Used to enable/disable the supported security protocols.

Not all supported protocols are enabled by default (the value of this setting is 240). 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:

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

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.

The LocalHost configuration 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 multihomed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the task initiate connections (or accept in the case of server tasks) only through that interface.

If the task is connected, the LocalHost configuration 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 multihomed hosts (machines with more than one IP interface).

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.

By default the task will use the system security libraries to perform cryptographic functions. This means calls to unmanaged code will be made. In certain environments this is not desirable. To use a completely managed security implementation set this setting to True. Setting this to True tells the task to use the internal managed implementation instead of using the system's security API.

Note that when this value is set the product's system dll is no longer required as a reference, as all unmanaged code is stored in this file.