Retail Control
Properties Methods Events Config Settings Errors
The Retail control is used to authorize credit card transactions with any of the supported Internet Payment Gateways.
Syntax
Retail
Remarks
The Retail control allows you to use multiple Internet Payment Gateways through one interface and one control. This allows for easy migration from one gateway to another, as well as quick integration into applications or web services.
The Retail control allows your website to securely perform credit card transactions without the need to redirect to a third-party site. All transactions are accomplished through a secure HTTPS Post to any supported gateway. The secure response is received and then stored in the control's response properties. Any web site on a standard HTTP server or any stand-alone application can process transactions without the need for a secure server or third-party intervention.
The first thing you must do is select one of the many gateways supported by the Retail control, and set up an account with that gateway vendor. Once you have an account set up with a valid (or test) login Id and password, you can use the Retail control.
To begin, set the Gateway property to the gateway you wish to use. If this gateway supports an alternate URL to send test transactions to, set the GatewayURL at this time.
Next, set the MerchantLogin (and for some gateways the MerchantPassword). These are supplied by your gateway vendor when you set up an account.
Now you are ready to process transactions. For each transaction, you can set the Card and TransactionAmount properties. For swiped card transactions you can set CardMagneticStripe or for manually entered transactions you can set CardNumber, CardExpMonth, CardExpYear. Most gateways will also require additional properties, such as CustomerAddress, CustomerFirstName, CustomerLastName, InvoiceNumber, etc. Any additional required properties are listed in the Gateway property description.
Once these properties are set, you may run validity checks on the card data with the AVSOnly method, or simply authorize the transaction with the Sale method. If your Gateway supports them, you may also perform a wide variety of transaction types such as VoidTransaction, Refund, Credit, or Force. Please review the method pages for further details about these methods and their designed functionality.
The following gateways are supported by the Retail control:
| Gateway | Home page |
| No Gateway (0) | n/a |
| Authorize.Net AIM (1) | http://www.authorize.net |
| eProcessing Transparent Database Engine (2) | http://www.eProcessingNetwork.com |
| iTransact RediCharge HTML (4) | http://www.itransact.com |
| NetBilling DirectMode (5) | http://www.netbilling.com |
| PayFlow Pro (6) | https://www.paypal.com/webapps/mpp/payflow-payment-gateway |
| USA ePay CGI Transaction Gateway (7) | http://www.usaepay.com |
| Plug 'n Pay (8) | http://www.plugnpay.com |
| Planet Payment iPay (9) | http://planetpayment.com/ |
| MPCS (10) | http://merchantcommerce.net/ |
| RTWare (11) | http://www.rtware.net/ |
| ECX (12) | http://www.ecx.com |
| Bank of America (Global Gateway e4) (13) | http://bankofamerica.com/merchantservices |
| Merchant Anywhere (Transaction Central) (15) | http://www.merchantanywhere.com/ |
| SkipJack (16) | http://www.skipjack.com |
| TrustCommerce API (19) | http://www.trustcommerce.com |
| PayFuse XML (ClearCommerce Engine) (21) | http://www.firstnationalmerchants.com/ |
| LinkPoint (24) | http://www.linkpoint.com |
| Fast Transact VeloCT (Direct Mode) (27) | http://www.fasttransact.com/ |
| NetworkMerchants Direct-Post API (28) | http://www.nmi.com/ |
| TransFirst Transaction Central Classic (formerly PRIGate) (30) | www.transfirst.com |
| Merchant Partners (Transaction Engine) (31) | http://www.merchantpartners.com/ |
| First Data Global Gateway (Linkpoint) (33) | http://www.firstdata.com |
| YourPay (Linkpoint) (34) | http://www.yourpay.com |
| ACH Payments AGI (35) | http://www.ach-payments.com |
| Forte AGI / Payments Gateway AGI(36) | https://www.forte.net/ |
| Cyber Source SOAP API (37) | http://www.cybersource.com |
| goEmerchant XML (39) | http://www.goemerchant.com/ |
| Chase Merchant Services (Linkpoint) (41) | http://www.chase.com |
| Thompson Merchant Services NexCommerce (iTransact mode) (42) | http://www.thompsonmerchant.com |
| TransFirst Transaction Central (44) | http://www.transfirst.com. (This is different from TransFirst eLink, supported above. The TransactionCentral gateway is also used by MerchantAnywhere and PRIGate) |
| Sterling SPOT XML API (HTTPS POST) (45) | http://www.sterlingpayment.com |
| PayJunction Trinity Gateway (46) | http://www.payjunction.com |
| Elavon/NOVA/My Virtual Merchant (49) | http://www.myvirtualmerchant.com |
| Verifi Direct-Post API (54) | http://www.verifi.com |
| Merchant E-Solutions Payment Gateway (Trident API) (56) | http://merchante-solutions.com/ |
| PayLeap Web Services API (57) | http://www.payleap.com |
| Worldpay XML (Direct/Invisible) (59) | http://www.worldpay.com |
| ProPay Merchant Services API (60) | http://www.propay.com |
| Intuit QuickBooks Merchant Services (QBMS) (61) | This gateway is no longer in service. It has been replaced by Quickbooks Payments (113). |
| Heartland POS Gateway (62) | http://www.heartlandpaymentsystems.com/ |
| Litle Online Gateway (63) | http://www.litle.com/ |
| BrainTree DirectPost (Server-to-Server Orange) Gateway (64) | http://www.braintreepaymentsolutions.com/ |
| JetPay Gateway (65) | http://www.jetpay.com/ |
| HSBC XML API (ClearCommerce Engine) (66) | https://www.business.hsbc.uk/en-gb/payments/business-card |
| BluePay 2.0 Post (67) | http://www.bluepay.com |
| PayTrace Payment Gateway (70) | https://www.paytrace.net/ |
| TransNational Bankcard (74) | http://www.tnbci.com/ |
| First Data Global Gateway E4 (80) | http://www.firstdata.com |
| Bluefin (82) | http://www.bluefin.com/ |
| Payscape (83) | http://www.payscape.com |
| Pay Direct (Link2Gov) (84) | https://www.fisglobal.com/solutions/other/government/ |
| WorldPay US Link Gateway (87) | https://www.worldpay.com/en-us/index |
| 3DSI Payment WorkSuite (88) | http://www.3dsi.com/ |
| First Data PayPoint (90) | https://www.firstdata.com/en_us/customer-center/financial-institutions/paypoint.html |
| Converge (formerly MyVirtualMerchant) (93) | https://support.convergepay.com/s/ |
| Payeezy Gateway (formerly First Data E4) (94) | https://developer.payeezy.com/ |
| Authorize.NET XML (96) | http://www.authorize.net |
| PhoeniXGate Gateway (97) | http://www.phoenixmanagednetworks.com/ |
| Repay Gateway (98) | https://www.repay.com/ |
| BASYS Gateway (106) | https://basyspro.com/ |
| Quickbooks Payments (113) | https://quickbooks.intuit.com/payments/ |
| Shift4 (114) | https://www.shift4.com/ |
| PayTrace Payment Gateway JSON (117) | https://www.paytrace.net/ |
Property List
The following is the full list of the properties of the control with short descriptions. Click on the links for further details.
| AuthCode | Authorization code from a previous transaction. |
| CardType | Type of credit card being used in this transaction. |
| CardCVVData | Three digit security code on back of card (optional). |
| CardCVVPresence | Indicates the presence of the card verification value. |
| CardEntryDataSource | This property contains a 1-character code identifying the source of the customer data. |
| CardExpMonth | Expiration month of the credit card specified in Number . |
| CardExpYear | Expiration year of the credit card specified in Number . |
| CardIsEncrypted | Determines whether data set to the Number or MagneticStripe properties is validated. |
| CardMagneticStripe | Track data read off of the card's magnetic stripe. |
| CardNumber | Customer's credit card number for the transaction. |
| CustomerAddress | Customer's street address. |
| CustomerAddress2 | A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc. |
| CustomerAggregate | This property allows you to get or set an XML aggregate built from all of the Customer properties. |
| CustomerCity | Customer's city. |
| CustomerCountry | Customer's country. |
| CustomerEmail | Customer's email address. |
| CustomerFax | Customer's fax number. |
| CustomerFirstName | Customer's first name. |
| CustomerFullName | Customer's full name. |
| CustomerId | Merchant-generated customer Id. |
| CustomerLastName | Customer's last name. |
| CustomerPhone | Customer's phone number. |
| CustomerState | Customer's state. |
| CustomerZip | Customer's zip code (or postal code if outside of the USA). |
| Gateway | Gateway to process transactions with. |
| GatewayURL | Default URL for a specific Gateway . |
| InvoiceNumber | Merchant-generated invoice number. |
| Level2Aggregate | The level 2 aggregate containing the data to be sent in the request. |
| Level3Aggregate | The level 3 aggregate containing the data to be sent in the request. |
| MerchantLogin | Merchant's Gateway login. |
| MerchantPassword | Merchant's Gateway password. |
| ProxyAuthScheme | This property is used to tell the control which type of authorization to perform when connecting to the proxy. |
| ProxyAutoDetect | This property tells the control whether or not to automatically detect and use proxy system settings, if available. |
| ProxyPassword | This property contains a password if authentication is to be used for the proxy. |
| ProxyPort | This property contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80). |
| ProxyServer | If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified. |
| ProxySSL | This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. |
| ProxyUser | This property contains a user name, if authentication is to be used for the proxy. |
| ResponseApprovalCode | Contains an authorization code when a transaction has been approved. |
| ResponseApproved | Indicates the status of the last transaction. |
| ResponseApprovedAmount | The amount approved for the transaction, this is the amount actually charged to the credit card. |
| ResponseAVSResult | Contains the Address Verification System result code. |
| ResponseCode | Indicates the status of the authorization request. |
| ResponseCVVResult | Contains the returned CVV2 result code if it was requested. |
| ResponseData | The entire response returned from the gateway processor. |
| ResponseErrorCode | Additional error code returned by some gateways. |
| ResponseErrorText | Additional error description returned by some gateways. |
| ResponseInvoiceNumber | Invoice number submitted in authorization request (if applicable). |
| ResponseProcessorCode | Response code from the underlying processor. |
| ResponseText | Text information that describes each response code. |
| ResponseTransactionId | Contains the Visa Transaction Identifier or MasterCard Reference Number. |
| ShippingAddress | Customer's shipping street address. |
| ShippingAddress2 | A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc. |
| ShippingCity | Customer's shipping city. |
| ShippingCountry | Customer's shipping country. |
| ShippingEmail | Customer's email address. |
| ShippingFirstName | Customer's first name. |
| ShippingLastName | Customer's last name. |
| ShippingPhone | Customer's phone number. |
| ShippingState | Customer's shipping state. |
| ShippingZip | Customer's shipping zip code (or postal code if outside of the USA). |
| SpecialFieldCount | The number of records in the SpecialField arrays. |
| SpecialFieldName | Name of special configuration property to submit in this transaction. |
| SpecialFieldValue | Value of special configuration property to submit in this transaction. |
| SSLAcceptServerCertEncoded | This is the certificate (PEM/base64 encoded). |
| SSLCertEncoded | This is the certificate (PEM/base64 encoded). |
| SSLCertStore | This is the name of the certificate store for the client certificate. |
| SSLCertStorePassword | If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store. |
| SSLCertStoreType | This is the type of certificate store for this certificate. |
| SSLCertSubject | This is the subject of the certificate used for client authentication. |
| SSLProvider | This specifies the SSL/TLS implementation to use. |
| SSLServerCertEncoded | This is the certificate (PEM/base64 encoded). |
| TestMode | Turns test mode on and off for transactions sent to the current Gateway . |
| Timeout | A timeout for the control. |
| TransactionAmount | Purchase amount for an authorization transaction. |
| TransactionDesc | Description of goods purchased. |
| TransactionId | Merchant-generated transaction Id used for all transactions. |
Method List
The following is the full list of the methods of the control with short descriptions. Click on the links for further details.
| AddSpecialField | Adds a special field name and the corresponding value. |
| AuthOnly | Initiates an authorization-only request transaction. |
| AVSOnly | Used to check the validity of the card without authorizing funds. |
| Capture | Captures a previously authorized transaction. |
| Config | Sets or retrieves a configuration setting. |
| Credit | Credits a customer's card. |
| DoEvents | Processes events from the internal message queue. |
| Force | Used when authorization cannot be obtained online. |
| GetResponseVar | Parses additional information out of the response. |
| Interrupt | Interrupts the current action. |
| Refund | Refunds a previously captured transaction. |
| Reset | Clears all properties to their default values. |
| ResetSpecialFields | Resets all special fields to the default settings. |
| Sale | Initiates an Sale transaction (authorization and capture). |
| VoidTransaction | Voids a previously authorized transaction. |
Event List
The following is the full list of the events fired by the control with short descriptions. Click on the links for further details.
| Error | Information about errors during data delivery. |
| SSLServerAuthentication | Fired after the server presents its certificate to the client. |
| SSLStatus | Shows the progress of the secure connection. |
Config Settings
The following is a list of config settings for the control with short descriptions. Click on the links for further details.
| 3DSAuthenticationStatus | Indicates whether a transaction qualifies as a ThreeDSecure (3DS) authenticated transaction. |
| 3DSCAVV | Cardholder Authentication Verification Value from a 3D Secure authentication. |
| 3DSDSTransactionId | Directory server transaction Id from a 3D Secure authentication. |
| 3DSECI | Electronic Commerce Indicator. |
| 3DSEnrollmentStatus | Indicates whether 3D Secure authentication is available for the cardholder. |
| 3DSXID | TransactionId from a 3D Secure authentication. |
| AllowPartialAuths | Specifies whether partial authorizations are allowed. |
| AmountFormat | Used to set the input format for TransactionAmount. |
| ApplePayData | The Base-64 encoded data containing the encrypted payment data from Apple for use when performing Apple Pay transactions. |
| AuthNetShipToCompany | The name of the company associated with the customer's shipping address. |
| AuthNetSplitTenderId | Authorize.Net assigned id for partially authorized transactions. |
| BluePayKSN | The Key Serial Number (KSN) used to encrypt the card magnetic stripe data for the BluePay gateway. |
| BluePayMasterId | Used to reference a previous transaction in BluePay. |
| BluePayPreEncryptedTrackLength | The length of the magnetic stripe data prior to encryption for the BluePay gateway. |
| BluePayUpdate | Used to perform an Update transaction for BluePay. |
| CardEncrypted | Specifies whether the card magnetic stripe data is encrypted. |
| CardholderPresentCode | Specifies the way in which transaction took place. |
| CardIssueNumber | Special Issue Number used for Switch and Solo cards. |
| CardPresent | Specifies whether the card is present during the transaction. |
| CardStartMonth | Used for some international cards. |
| CardStartYear | Used for some international cards. |
| CardType | Type of credit card being used in this transaction. |
| CAVVResponse | Contains CAVV response value returned by the gateway. |
| COFPermission | Indicates if the customer gave permission to make a Card On File transaction. |
| ConvenienceFee | The total convenience fee charged for a transaction. |
| CurrencyCode | Currency code for the currency of the transaction. |
| CurrencyExponent | Currency exponent to be used in conjunction with the Currency code of the transaction. |
| CyberSourceAuthToken | The request token from a previous authorization for the CyberSource gateway. |
| CyberSourceProfileId | The Id of a Customer's Profile stored within the CyberSource gateway. |
| CyberSourceVoidMode | Indicates whether to perform a Void or Reversal. |
| CyberSourceXMLEscape | Determines whether to XML escape the CyberSource gateway request field values. |
| DebitKSN | Clear-text Key Sequence Number retrieved from a PIN pad. |
| DebitPIN | DUKPT DES encrypted pin block, retrieved from a PIN pad. |
| DynamicDescriptor | A merchant defined transaction description which appears on the customer's credit card statement. |
| EscapeXML | Automatically escape data within XML tags. |
| FDMSCurrentBalance | Contains the current card balance value returned in a response for the First Data E4, Payeezy, and Bank Of America gateways. |
| FDMSGiftCardTransactionType | Specifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways. |
| FDMSKeyId | The Key Id that corresponds to the HMAC Key for the First Data E4, Payeezy, and Bank Of America gateways. |
| FDMSProcessGiftCard | Specifies whether the card being processed is a gift card for the First Data E4, Payeezy, and Bank Of America gateways. |
| FDMSTransArmorToken | The Transarmor token that replaces a card number and used for transaction processing. |
| FDMSWalletProviderId | Specifies the transaction type to perform on a gift card for the First Data E4, Payeezy, and Bank Of America gateways. |
| GlobalIrisRefundPassword | The Refund password for the Global Iris gateway. |
| GoEMerchantUseGatewayId | Indicates whether to send a password or gateway Id for the GoEMerchant gateway. |
| HashAlgorithm | Algorithm used for hashing. |
| HashSecret | Security key used to generate a hash for gateways supporting such functionality. |
| HeartlandDeveloperId | Optional DeveloperId field used by the Heartland gateway. |
| HeartlandDeviceId | DeviceId field required by the Heartland gateway. |
| HeartlandLicenseId | LicenseId field required by the Heartland gateway. |
| HeartlandReversalAmount | The settlement amount to be used when performing a reversal for the Heartland gateway. |
| HeartlandSecretAPIKey | Specifies the secret key to be used for authentication with Heartland. |
| HeartlandShipDay | Ship day field required by the Heartland gateway e-commerce/direct marketing transactions. |
| HeartlandShipMonth | Ship month field required by the Heartland gateway e-commerce/direct marketing transactions. |
| HeartlandSiteId | SiteId field required by the Heartland gateway. |
| HeartlandSiteTrace | Optional transaction identifier for the Heartland gateway. |
| HeartlandTokenMapping | The type of token to return when using Tokenization with the Heartland gateway. |
| HeartlandTokenValue | Used to retrieve or specify a Heartland token value. |
| HeartlandVersionNumber | Optional VersionNumber field used by the Heartland gateway. |
| LitleAdvancedFraudChecksId | Used to specify the Id for use in the AdvancedFraudChecks element for the Litle gateway. |
| LitleCardholderID | Describes the method used to identify the cardholder at the point of sale for the Litle gateway. |
| LitleCustomBillingAggregate | Used to specify an XML aggregate for Custom Billing support within the Litle gateway. |
| MerchantAlias | An additional merchant property used to specify an alias for the merchant. |
| MerchantCode | A gateway-supplied merchant number, code, or Id. |
| MerchantPartnersLast4Digits | The last 4 digits of the card number for a transaction processed via the MerchantPartners gateway. |
| MerchantPartnersProfileId | The profile Id to be used to process a transaction via the MerchantPartners or WorldPay Link gateways. |
| MerchantPartnersReaderType | The reader type used to read and encrypt a swiped card for the MerchantPartners or WorldPay Link gateways. |
| MITAESSeedId | The Seed Id used to perform AES encryption for the MIT gateway. |
| MITBranchId | Branch reference number for the MIT gateway. |
| MITCompanyId | Company reference number for the MIT gateway. |
| MITCountry | Country of operation for the MIT gateway. |
| MITEncryptionAlgorithm | The Encryption Algorithm to use with the MIT gateway. |
| MITEncryptionKey | The Encryption Key to use with the MIT gateway. |
| MITFlag | For the MIT framework - Used to indicate that a transaction is merchant initiated. |
| MITPriorTransId | For the MIT framework - Used to specify a prior transaction id to be referenced in a merchant initiated transaction. |
| MITRecurring | Specifies whether to perform a recurring transaction request for the MIT gateway. |
| MITTPOperation | The operation type for the MIT gateway. |
| MITType | For the MIT framework - Indicates the type of transaction being requested in a Merchant-Initiated Transaction (MIT). |
| MonerisNVPAPI | Indicates whether to use the NVP API for the gwMoneris and gwMonerisUSA gateway. |
| MyVirtualMerchantTransactionType | Used to override the transaction type to send in a transaction for the MyVirtualMerchant and Converge gateways. |
| MyVirtualMerchantUserId | The MyVirtualMerchant user Id as configured on VirtualMerchant. |
| NetbanxAccountNumber | Account Number for the Netbanx gateway. |
| NetBillingVersion | The Version to be sent in the User-Agent heading of a NetBilling gateway request. |
| OrbitalAuthReversal | Indicates whether to perform an authorization reversal when calling VoidTransaction for the Orbital gateway. |
| OrbitalConnectionPassword | Orbital Connection Password field used by the Orbital gateway. |
| OrbitalConnectionUsername | Orbital Connection Username field used by the Orbital gateway. |
| OrbitalCustomerProfileFromOrderInd | Customer Profile Number generation Options for the Orbital gateway. |
| OrbitalCustomerProfileOrderOverrideInd | Indicator to specify how the CustomerId is leveraged to populate other data sets for the Orbital gateway. |
| OrbitalTxRefIdx | Indentifies the unique controls of transactions that have been adjusted more than one time for the Orbital gateway. |
| OrbitalVoidAdjustedAmount | Specifies the amount to void from a previous authoization for the Orbital gateway. |
| PayDirectConvenienceFee | The total convenience fee charged when using the PayDirect gateway. |
| PayDirectMerchantAmount | The MerchantAmount used by the PayDirect gateway. |
| PayDirectSettleMerchantCode | The Settle Merchant Code required for authorization when using the PayDirect gateway. |
| PayerIP | The IP address of the payer. |
| PayFlowProInquiry | Submits an Inquiry transaction to the PayFlowPro gateway. |
| PayFlowProToken | Used specify a token to be used instead of card data for the Payflow Pro gateway. |
| PayFlowProUpload | Submits an Upload transaction to the PayFlowPro gateway. |
| PayJunctionUpdateAmount | Indicates whether the capture method should send an update amount request when using the PayJunction gateway. |
| PaymentWorkSuiteClientCode | The 3DSI assigned client code sent in a request to the PaymentWorksuite gateway. |
| PaymentWorkSuiteLocationCode | The 3DSI assigned location code sent in a request to the PaymentWorksuite gateway. |
| PaymentWorkSuiteMerchantCode | The 3DSI assigned merchant code sent in a request to the PaymentWorksuite gateway. |
| PayPointFreedomAPI | Indicates whether to use the Freedom API for the gwPayPoint and gwSECPay gateways. |
| PayTraceAddPurchaseCardData | Sends a Level3 request for the PayTrace gateway. |
| PayTraceIntegratorId | Used to specify the Integrator Id value assigned by the PayTrace gateway. |
| PayTraceJSONCardToken | The token value for a corresponding card. |
| PayTraceJSONEncryptionKey | The Encryption Key to use with the PayTraceJSON gateway. |
| PayTraceJSONGetClientKeyToken | Retrieves a new Client Key (PROTECT AUTH TOKEN) from PayTrace. |
| PKPaymentToken | Used to send an Apple Pay PKPaymentToken to the gateway. |
| QBMSMobile | Whether or not this transaction is being sent from a mobile device. |
| QBPaymentsMobile | Whether or not this transaction is being sent from a mobile device. |
| RawRequest | Returns the data that was sent to the gateway. |
| RawResponse | Returns the data that was received from the gateway. |
| RecurringIndicator | Marks a request as a recurring transaction. |
| SagePayCreateToken | Sends a create token request to the SagePay gateway. |
| SagePayRemoveToken | Sends a remove token request to the SagePay gateway. |
| SagePayRepeat | Performs a Repeat transaction for the SagePay gateway. |
| SagePayRequestToken | Specifies whether to request a token when performing an Auth or Sale when using the SagePay gateway. |
| SagePayStoreToken | Specifies whether to store a token when using the SagePay gateway. |
| SagePayToken | The token value for a corresponding card when using the SagePay gateway. |
| SagePayUseAbort | Indicates whether to use Abort or Void for void transactions. |
| Shift4AuthToken | Specifies the Auth Token when making an Access Token request to the Shift4 gateway. |
| Shift4ClientGuid | Specifies the Client Guid when making an Access Token request to the Shift4 gateway. |
| Shift4GetAccessToken | Performs an Access Token Exchange request with the Shift4 gateway. |
| Shift4InterfaceName | Specifies the name of the interface for the Shift4 gateway. |
| Shift4InterfaceVersion | Specifies the version of the interface for the Shift4 gateway. |
| StoreCardOnFile | For the Stored Credentials framework - Used to indicate that the merchant will be storing the customer's card on file (COF). |
| SurchargeAmount | Used to specify the amount of the surcharge for the transaction. |
| TerminalCapability | The capability of the terminal that is used to submit the transaction. |
| TerminalId | Terminal Id value sent in the transaction. |
| TerminalManufacturer | The manufacturer of the terminal used to submit the transaction. |
| TerminalModel | The model of the terminal used to submit the transaction. |
| TerminalType | The terminal type that is used to submit the transaction. |
| TipAmount | Used to specify the amount of the tip for the transaction. |
| USAEPayPerformVoidRelease | Specifies whether to perform a void or void:release transaction. |
| UseCardOnFile | For the Stored Credentials framework - Used to indicate that the merchant is using stored card on file (COF) information for the request. |
| UserId | Used to specify an Id for the API user. |
| XChildrenCount | The number of child elements of the current element. |
| XChildrenName[x] | The name of the child element. |
| XChildrenXText[x] | The inner text of the child element. |
| XElement | The name of the current element. |
| XPath | Provides a way to point to a specific element in the returned XML or JSON response. |
| XText | The text of the current element. |
| AcceptEncoding | Used to tell the server which types of content encodings the client supports. |
| AllowHTTPCompression | This property enables HTTP compression for receiving data. |
| AllowHTTPFallback | Whether HTTP/2 connections are permitted to fallback to HTTP/1.1. |
| Append | Whether to append data to LocalFile. |
| Authorization | The Authorization string to be sent to the server. |
| BytesTransferred | Contains the number of bytes transferred in the response data. |
| ChunkSize | Specifies the chunk size in bytes when using chunked encoding. |
| CompressHTTPRequest | Set to true to compress the body of a PUT or POST request. |
| EncodeURL | If set to True the URL will be encoded by the control. |
| FollowRedirects | Determines what happens when the server issues a redirect. |
| GetOn302Redirect | If set to True the control will perform a GET on the new location. |
| HTTP2HeadersWithoutIndexing | HTTP2 headers that should not update the dynamic header table with incremental indexing. |
| HTTPVersion | The version of HTTP used by the control. |
| IfModifiedSince | A date determining the maximum age of the desired document. |
| KeepAlive | Determines whether the HTTP connection is closed after completion of the request. |
| KerberosSPN | The Service Principal Name for the Kerberos Domain Controller. |
| LogLevel | The level of detail that is logged. |
| MaxRedirectAttempts | Limits the number of redirects that are followed in a request. |
| NegotiatedHTTPVersion | The negotiated HTTP version. |
| OtherHeaders | Other headers as determined by the user (optional). |
| ProxyAuthorization | The authorization string to be sent to the proxy server. |
| ProxyAuthScheme | The authorization scheme to be used for the proxy. |
| ProxyPassword | A password if authentication is to be used for the proxy. |
| ProxyPort | Port for the proxy server (default 80). |
| ProxyServer | Name or IP address of a proxy server (optional). |
| ProxyUser | A user name if authentication is to be used for the proxy. |
| SentHeaders | The full set of headers as sent by the client. |
| StatusLine | The first line of the last response from the server. |
| TransferredData | The contents of the last response from the server. |
| TransferredDataLimit | The maximum number of incoming bytes to be stored by the control. |
| TransferredHeaders | The full set of headers as received from the server. |
| TransferredRequest | The full request as sent by the client. |
| UseChunkedEncoding | Enables or Disables HTTP chunked encoding for transfers. |
| UseIDNs | Whether to encode hostnames to internationalized domain names. |
| UseProxyAutoConfigURL | Whether to use a Proxy auto-config file when attempting a connection. |
| UserAgent | Information about the user agent (browser). |
| ConnectionTimeout | Sets a separate timeout value for establishing a connection. |
| FirewallAutoDetect | Tells the control whether or not to automatically detect and use firewall system settings, if available. |
| FirewallHost | Name or IP address of firewall (optional). |
| FirewallPassword | Password to be used if authentication is to be used when connecting through the firewall. |
| FirewallPort | The TCP port for the FirewallHost;. |
| FirewallType | Determines the type of firewall to connect through. |
| FirewallUser | A user name if authentication is to be used connecting through a firewall. |
| KeepAliveInterval | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. |
| KeepAliveTime | The inactivity time in milliseconds before a TCP keep-alive packet is sent. |
| Linger | When set to True, connections are terminated gracefully. |
| LingerTime | Time in seconds to have the connection linger. |
| LocalHost | The name of the local host through which connections are initiated or accepted. |
| LocalPort | The port in the local host where the control binds. |
| MaxLineLength | The maximum amount of data to accumulate when no EOL is found. |
| MaxTransferRate | The transfer rate limit in bytes per second. |
| ProxyExceptionsList | A semicolon separated list of hosts and IPs to bypass when using a proxy. |
| TCPKeepAlive | Determines whether or not the keep alive socket option is enabled. |
| TcpNoDelay | Whether or not to delay when sending packets. |
| UseIPv6 | Whether to use IPv6. |
| LogSSLPackets | Controls whether SSL packets are logged when using the internal security API. |
| OpenSSLCADir | The path to a directory containing CA certificates. |
| OpenSSLCAFile | Name of the file containing the list of CA's trusted by your application. |
| OpenSSLCipherList | A string that controls the ciphers to be used by SSL. |
| OpenSSLPrngSeedData | The data to seed the pseudo random number generator (PRNG). |
| ReuseSSLSession | Determines if the SSL session is reused. |
| SSLCACerts | A newline separated list of CA certificate to use during SSL client authentication. |
| SSLCheckCRL | Whether to check the Certificate Revocation List for the server certificate. |
| SSLCheckOCSP | Whether to use OCSP to check the status of the server certificate. |
| SSLCipherStrength | The minimum cipher strength used for bulk encryption. |
| SSLEnabledCipherSuites | The cipher suite to be used in an SSL negotiation. |
| SSLEnabledProtocols | Used to enable/disable the supported security protocols. |
| SSLEnableRenegotiation | Whether the renegotiation_info SSL extension is supported. |
| SSLIncludeCertChain | Whether the entire certificate chain is included in the SSLServerAuthentication event. |
| SSLKeyLogFile | The location of a file where per-session secrets are written for debugging purposes. |
| SSLNegotiatedCipher | Returns the negotiated ciphersuite. |
| SSLNegotiatedCipherStrength | Returns the negotiated ciphersuite strength. |
| SSLNegotiatedCipherSuite | Returns the negotiated ciphersuite. |
| SSLNegotiatedKeyExchange | Returns the negotiated key exchange algorithm. |
| SSLNegotiatedKeyExchangeStrength | Returns the negotiated key exchange algorithm strength. |
| SSLNegotiatedVersion | Returns the negotiated protocol version. |
| SSLSecurityFlags | Flags that control certificate verification. |
| SSLServerCACerts | A newline separated list of CA certificate to use during SSL server certificate validation. |
| TLS12SignatureAlgorithms | Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal. |
| TLS12SupportedGroups | The supported groups for ECC. |
| TLS13KeyShareGroups | The groups for which to pregenerate key shares. |
| TLS13SignatureAlgorithms | The allowed certificate signature algorithms. |
| TLS13SupportedGroups | The supported groups for (EC)DHE key exchange. |
| AbsoluteTimeout | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
| FirewallData | Used to send extra data to the firewall. |
| InBufferSize | The size in bytes of the incoming queue of the socket. |
| OutBufferSize | The size in bytes of the outgoing queue of the socket. |
| CodePage | The system code page used for Unicode to Multibyte translations. |
| MaskSensitive | Whether sensitive data is masked in log messages. |
| UseInternalSecurityAPI | Tells the control whether or not to use the system security libraries or an internal implementation. |
AuthCode Property (Retail Control)
Authorization code from a previous transaction.
Syntax
retailcontrol.AuthCode[=string]
Default Value
""
Remarks
Some gateways require the merchant to include the ResponseApprovalCode from the original transaction in Credit, VoidTransaction, and Capture transactions. You may send the original approval code in this AuthCode property. The gateways which require this are listed below:
- gwIntellipay (3)
- gwBankOfAmerica (13)
- gwInnovative (14)
- gwACHPAyments (35)
- gwForte (36)
- gwSagePay (50)
- gwDataCash (77)
- gwFirstDataE4 (80)
Data Type
String
CardType Property (Retail Control)
Type of credit card being used in this transaction.
Syntax
retailcontrol.CardType[=integer]
Possible Values
ctUnknown(0), ctVisa(1), ctMasterCard(2), ctAMEX(3), ctDiscover(4), ctDiners(5), ctJCB(6), ctVisaElectron(7), ctMaestro(8), ctLaser(10)
Default Value
0
Remarks
Type of credit card being used in this transaction. This property contains the customer's credit card type. This is automatically computed after the CardNumber is set, but it can also be changed manually. A list of valid card types is included below.
| ctUnknown (0) | Invalid or unknown prefix, card type not known. |
| ctVisa (1) | Visa or Delta Card. |
| ctMasterCard (2) | MasterCard. |
| ctAMEX (3) | American Express Card. |
| ctDiscover (4) | Discover Card. |
| ctDiners (5) | Diners Club or Carte Blanche Card. |
| ctJCB (6) | JCB Card. |
| ctVisaElectron (7) | Visa Electron Card (runs as a Visa for most gateways) |
| ctMaestro (8) | Maestro Card |
| ctLaser (10) | Laser Card (Ireland) |
This property is not available at design time.
Data Type
Integer
CardCVVData Property (Retail Control)
Three digit security code on back of card (optional).
Syntax
retailcontrol.CardCVVData[=string]
Default Value
""
Remarks
Three digit security code on back of card (optional).
This alphanumeric property contains the three digit Visa "Card Verification Value" (CVV), MasterCard "Card Verification Code" (CVC), or four-digit American Express "Card Identification Number" (CID). This value appears as additional characters embossed on the card signature line following the credit card account number on the back of the credit card. This is an optional property which can be used to determine if the customer is actually in possession of the credit card.
Even if the CardCVVData is incorrect, the transaction may still be authorized. It is up to the merchant to examine the ResponseCVVResult property and decide whether to honor the transaction or not.
Note: When set to a non-empty value, CardCVVPresence will be automatically set to cvpProvided. If set to empty string (""), CardCVVPresence will be automatically set to cvpNotProvided.
This property is not available at design time.
Data Type
String
CardCVVPresence Property (Retail Control)
Indicates the presence of the card verification value.
Syntax
retailcontrol.CardCVVPresence[=integer]
Possible Values
cvpNotProvided(0), cvpProvided(1), cvpIllegible(2), cvpNotOnCard(3)
Default Value
0
Remarks
Indicates the presence of the card verification value.
This property is used to indicate the presence of CardCVVData.
The control will automatically set this value to cvpProvided when a CardCVVData value is specified. You can explicitly specify the CardCVVPresence indicator by setting this property.
Available values are:
- cvpNotProvided (0)
- cvpProvided (1)
- cvpIllegible (2)
- cvpNotOnCard (3)
This property is not available at design time.
Data Type
Integer
CardEntryDataSource Property (Retail Control)
This property contains a 1-character code identifying the source of the customer data.
Syntax
retailcontrol.CardEntryDataSource[=integer]
Possible Values
edsTrack1(0), edsTrack2(1), edsManualEntryTrack1Capable(2), edsManualEntryTrack2Capable(3), edsManualEntryNoCardReader(4), edsTrack1Contactless(5), edsTrack2Contactless(6), edsManualEntryContactlessCapable(7), edsIVR(8), edsKiosk(9)
Default Value
0
Remarks
This property contains a 1-character code identifying the source of the customer data. The table below shows all supported values for this property.
| edsTrack1 (0) | Full Magnetic stripe read and transmit, Track 1. |
| edsTrack2 (1) | Full magnetic stripe read and transmit, Track 2. |
| edsManualEntryTrack1Capable (2) | Manually keyed, Track 1 capable. |
| edsManualEntryTrack2Capable (3) | Manually keyed, Track 2 capable. |
| edsManualEntryNoCardReader (4) | Manually keyed, terminal has no card reading capability (use this for e-commerce and MOTO transactions). |
| edsTrack2Contactless (6) | Full magnetic stripe read (Track 2 only), Chip Card capable terminal (Visa, Mastercard, and JCB Transactions only). |
| edsManualEntryContactlessCapable (7) | Manually keyed, Chip Card read capable terminal (Visa, MasterCard, and JCB transactions only). |
This property is not available at design time.
Data Type
Integer
CardExpMonth Property (Retail Control)
Expiration month of the credit card specified in Number .
Syntax
retailcontrol.CardExpMonth[=integer]
Default Value
1
Remarks
Expiration month of the credit card specified in CardNumber.
This property contains the expiration date of the customer's credit card, and must be in the range 1 - 12.
This property is not available at design time.
Data Type
Integer
CardExpYear Property (Retail Control)
Expiration year of the credit card specified in Number .
Syntax
retailcontrol.CardExpYear[=integer]
Default Value
2000
Remarks
Expiration year of the credit card specified in CardNumber.
This property contains the expiration date of the customer's credit card. This property must be in the range 0 - 99, or 2000 - 2099. Any date before the year 2000 or after 2099 cannot be specified.
This property is not available at design time.
Data Type
Integer
CardIsEncrypted Property (Retail Control)
Determines whether data set to the Number or MagneticStripe properties is validated.
Syntax
retailcontrol.CardIsEncrypted[=boolean]
Default Value
False
Remarks
Determines whether data set to the CardNumber or CardMagneticStripe fields is validated.
By default, when the CardNumber or CardMagneticStripe fields are set, the value will be validated and normalized. For instance, "4444-33332222 1111" will be normalized as "4444333322221111" and CardMagneticStripe data will be parsed for the track specified by CardEntryDataSource. However, any other non-numerical data entered will cause an exception to be thrown. It may be useful in some gateways to send other data in the CardNumber or CardMagneticStripe fields, and this can be accomplished by setting IsEncrypted to true. However, please note that in doing so automatic calculation of the CardType may be affected, and the card number will not be verified.
This property is not available at design time.
Data Type
Boolean
CardMagneticStripe Property (Retail Control)
Track data read off of the card's magnetic stripe.
Syntax
retailcontrol.CardMagneticStripe[=string]
Default Value
""
Remarks
Track data read off of the card's magnetic stripe.
If CardEntryDataSource is not one of the manually entered enumerations, then this property must be set with the track1 or track2 data from the magnetic stripe on the back of the customer's credit card. This includes everything after but not including the start sentinel (% or ;) and up to but not including the end sentinel (?) and LRC check character. You may only set this property with track 1 or track 2 data, and may not pass both. Use the CardEntryDataSource property to indicate which track you are sending.
The following example shows how to set the CardMagneticStripe and CardEntryDataSource properties if the data read off the card is "%B4788250000028291^TSYS^05121015432112345678?;4788250000028291=05121015432112345678?"
control.CardMagneticStripe = "B4788250000028291^TSYS^05121015432112345678"
control.CardEntryDataSource = edsTrack1
or
control.CardMagneticStripe = "4788250000028291=05121015432112345678"
control.CardEntryDataSource = edsTrack2
Industry regulations do not allow merchants or processors to store track data in any form of persistent storage. Failure to abide by this regulation can result in significant fines and other penalties.
This property is not available at design time.
Data Type
String
CardNumber Property (Retail Control)
Customer's credit card number for the transaction.
Syntax
retailcontrol.CardNumber[=string]
Default Value
""
Remarks
Customer's credit card number for the transaction.
If you're sending the transaction with CardMagneticStripe data, this property should be left empty.
This property is not available at design time.
Data Type
String
CustomerAddress Property (Retail Control)
Customer's street address.
Syntax
retailcontrol.CustomerAddress[=string]
Default Value
""
Remarks
Customer's street address. This property is used as part of the Address Verification Service (AVS) and contains the customer's street address as it appears on their monthly statement. Only the street number, street name, and apartment number are required in This property. City, state, and zip code are set in the CustomerCity, CustomerState, and CustomerZip properties.
The length of this property varies by gateway. If the customer's address is very long, it is admissible to include only the street number in This property.
NOTE: For the Moneris gateway, this property should contain only the customer's street number. The street name should be added via the AddSpecialField method. For example:
control.CustomerAddress = "123"
control.AddSpecialField("avs_street_name", "Nowhere Ln")
This property is not available at design time.
Data Type
String
CustomerAddress2 Property (Retail Control)
A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.
Syntax
retailcontrol.CustomerAddress2[=string]
Default Value
""
Remarks
A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.).
This property is not available at design time.
Data Type
String
CustomerAggregate Property (Retail Control)
This property allows you to get or set an XML aggregate built from all of the Customer properties.
Syntax
retailcontrol.CustomerAggregate[=string]
Default Value
""
Remarks
This property allows you to get or set an XML aggregate built from all of the Customer properties.
"EPCustomer" is the root element. The Customer properties make up the tags under the root, but
without the beginning "Customer". For instance:
<EPCustomer>
<Address>123 Nowhere Ln.</Address>
<Address2>Apt 3B.</Address2>
<City>Beverly Hills</City>
...
</EPCustomer>
This property is not available at design time.
Data Type
String
CustomerCity Property (Retail Control)
Customer's city.
Syntax
retailcontrol.CustomerCity[=string]
Default Value
""
Remarks
Customer's city. This property is used as part of the Address Verification Service (AVS) and contains the customer's city as it appears on their monthly statement. Other AVS properties include CustomerAddress, CustomerState, and CustomerZip.
This property is not available at design time.
Data Type
String
CustomerCountry Property (Retail Control)
Customer's country.
Syntax
retailcontrol.CustomerCountry[=string]
Default Value
""
Remarks
Customer's country. This property contains the country in which the customer is located. Most gateways use a two-letter country code, specified in ISO-3166.
Note: If using this property with the PayFuse gateway, this property should contain the ISO-3166 numeric code instead of the standard two-letter code. For example, the ISO code for the US is "840".
This property is not available at design time.
Data Type
String
CustomerEmail Property (Retail Control)
Customer's email address.
Syntax
retailcontrol.CustomerEmail[=string]
Default Value
""
Remarks
Customer's email address. This optional property contains the customer's email address.
This property is not available at design time.
Data Type
String
CustomerFax Property (Retail Control)
Customer's fax number.
Syntax
retailcontrol.CustomerFax[=string]
Default Value
""
Remarks
Customer's fax number. This optional property contains the customer's fax number.
This property is not available at design time.
Data Type
String
CustomerFirstName Property (Retail Control)
Customer's first name.
Syntax
retailcontrol.CustomerFirstName[=string]
Default Value
""
Remarks
Customer's first name. This property contains the customer's first name.
This property is not available at design time.
Data Type
String
CustomerFullName Property (Retail Control)
Customer's full name.
Syntax
retailcontrol.CustomerFullName[=string]
Default Value
""
Remarks
Customer's full name. This property contains the customer's full name as it appears on the credit card or bank account. Many gateways use this property in addition to, or instead of, the CustomerFirstName and CustomerLastName properties. If a gateway requires a CustomerFullName and the property is empty, CustomerFullName will be constructed using the contents of CustomerFirstName and CustomerLastName.
This property is not available at design time.
Data Type
String
CustomerId Property (Retail Control)
Merchant-generated customer Id.
Syntax
retailcontrol.CustomerId[=string]
Default Value
""
Remarks
Merchant-generated customer Id. This property contains a merchant-generated customer identification number. This number should be unique for each different customer that places an order with the merchant.
This property is not available at design time.
Data Type
String
CustomerLastName Property (Retail Control)
Customer's last name.
Syntax
retailcontrol.CustomerLastName[=string]
Default Value
""
Remarks
Customer's last name. This property contains the customer's last name as it appears on their credit card.
This property is not available at design time.
Data Type
String
CustomerPhone Property (Retail Control)
Customer's phone number.
Syntax
retailcontrol.CustomerPhone[=string]
Default Value
""
Remarks
Customer's phone number. This optional property contains the customer's phone number.
This property is not available at design time.
Data Type
String
CustomerState Property (Retail Control)
Customer's state.
Syntax
retailcontrol.CustomerState[=string]
Default Value
""
Remarks
Customer's state. This property is used as part of the Address Verification Service (AVS) and contains the two character postal abbreviation of the customer's state as it appears on their monthly statement. Other AVS properties include CustomerAddress, CustomerCity, and CustomerZip.
This property is not available at design time.
Data Type
String
CustomerZip Property (Retail Control)
Customer's zip code (or postal code if outside of the USA).
Syntax
retailcontrol.CustomerZip[=string]
Default Value
""
Remarks
Customer's zip code (or postal code if outside of the USA). This property is used as part of the Address Verification Service (AVS), and contains the customer's zip code as it appears on their monthly statement. Other AVS properties include CustomerAddress, CustomerCity, and CustomerState.
This property is not available at design time.
Data Type
String
Gateway Property (Retail Control)
Gateway to process transactions with.
Syntax
retailcontrol.Gateway[=integer]
Possible Values
rgwNoGateway(0), rgwAuthorizeNet(1), rgwEprocessing(2), rgwITransact(4), rgwNetBilling(5), rgwPayFlowPro(6), rgwUSAePay(7), rgwPlugNPay(8), rgwPlanetPayment(9), rgwMPCS(10), rgwRTWare(11), rgwECX(12), rgwBankOfAmerica(13), rgwMerchantAnywhere(15), rgwSkipjack(16), rgwTrustCommerce(19), rgwPayFuse(21), rgwLinkPoint(24), rgwFastTransact(27), rgwNetworkMerchants(28), rgwPRIGate(30), rgwMerchantPartners(31), rgwFirstData(33), rgwYourPay(34), rgwACHPAyments(35), rgwForte(36), rgwCyberSource(37), rgwGoEMerchant(39), rgwChase(41), rgwNexCommerce(42), rgwTransactionCentral(44), rgwSterling(45), rgwPayJunction(46), rgwMyVirtualMerchant(49), rgwVerifi(54), rgwMerchantESolutions(56), rgwPayLeap(57), rgwWorldPayXML(59), rgwProPay(60), rgwQBMS(61), rgwHeartland(62), rgwLitle(63), rgwBrainTree(64), rgwJetPay(65), rgwHSBC(66), rgwBluePay(67), rgwPayTrace(70), rgwTransNationalBankcard(74), rgwFirstDataE4(80), rgwBluefin(82), rgwPayscape(83), rgwPayDirect(84), rgwWorldPayLink(87), rgwPaymentWorkSuite(88), rgwFirstDataPayPoint(90), rgwPayeezy(94), rgwAuthorizeNetXML(96), rgwPhoeniXGate(97), rgwRepay(98), rgwBASYS(106), rgwQBPayments(113), rgwShift4(114), rgwHeartlandPortico(116), rgwPayTraceJSON(117)
Default Value
0
Remarks
This property is used to select the gateway with which transactions will be processed. Setting the Gateway property will also fill the GatewayURL, SpecialFieldName, and SpecialFieldValue properties with default data for the selected gateway. The following table shows the currently supported gateways, as well as the corporate home page for each.
| Gateway | Home page |
| No Gateway (0) | n/a |
| Authorize.Net AIM (1) | http://www.authorize.net |
| eProcessing Transparent Database Engine (2) | http://www.eProcessingNetwork.com |
| iTransact RediCharge HTML (4) | http://www.itransact.com |
| NetBilling DirectMode (5) | http://www.netbilling.com |
| PayFlow Pro (6) | https://www.paypal.com/webapps/mpp/payflow-payment-gateway |
| USA ePay CGI Transaction Gateway (7) | http://www.usaepay.com |
| Plug 'n Pay (8) | http://www.plugnpay.com |
| Planet Payment iPay (9) | http://planetpayment.com/ |
| MPCS (10) | http://merchantcommerce.net/ |
| RTWare (11) | http://www.rtware.net/ |
| ECX (12) | http://www.ecx.com |
| Bank of America (Global Gateway e4) (13) | http://bankofamerica.com/merchantservices |
| Merchant Anywhere (Transaction Central) (15) | http://www.merchantanywhere.com/ |
| SkipJack (16) | http://www.skipjack.com |
| TrustCommerce API (19) | http://www.trustcommerce.com |
| PayFuse XML (ClearCommerce Engine) (21) | http://www.firstnationalmerchants.com/ |
| LinkPoint (24) | http://www.linkpoint.com |
| Fast Transact VeloCT (Direct Mode) (27) | http://www.fasttransact.com/ |
| NetworkMerchants Direct-Post API (28) | http://www.nmi.com/ |
| TransFirst Transaction Central Classic (formerly PRIGate) (30) | www.transfirst.com |
| Merchant Partners (Transaction Engine) (31) | http://www.merchantpartners.com/ |
| First Data Global Gateway (Linkpoint) (33) | http://www.firstdata.com |
| YourPay (Linkpoint) (34) | http://www.yourpay.com |
| ACH Payments AGI (35) | http://www.ach-payments.com |
| Forte AGI / Payments Gateway AGI(36) | https://www.forte.net/ |
| Cyber Source SOAP API (37) | http://www.cybersource.com |
| goEmerchant XML (39) | http://www.goemerchant.com/ |
| Chase Merchant Services (Linkpoint) (41) | http://www.chase.com |
| Thompson Merchant Services NexCommerce (iTransact mode) (42) | http://www.thompsonmerchant.com |
| TransFirst Transaction Central (44) | http://www.transfirst.com. (This is different from TransFirst eLink, supported above. The TransactionCentral gateway is also used by MerchantAnywhere and PRIGate) |
| Sterling SPOT XML API (HTTPS POST) (45) | http://www.sterlingpayment.com |
| PayJunction Trinity Gateway (46) | http://www.payjunction.com |
| Elavon/NOVA/My Virtual Merchant (49) | http://www.myvirtualmerchant.com |
| Verifi Direct-Post API (54) | http://www.verifi.com |
| Merchant E-Solutions Payment Gateway (Trident API) (56) | http://merchante-solutions.com/ |
| PayLeap Web Services API (57) | http://www.payleap.com |
| Worldpay XML (Direct/Invisible) (59) | http://www.worldpay.com |
| ProPay Merchant Services API (60) | http://www.propay.com |
| Intuit QuickBooks Merchant Services (QBMS) (61) | This gateway is no longer in service. It has been replaced by Quickbooks Payments (113). |
| Heartland POS Gateway (62) | http://www.heartlandpaymentsystems.com/ |
| Litle Online Gateway (63) | http://www.litle.com/ |
| BrainTree DirectPost (Server-to-Server Orange) Gateway (64) | http://www.braintreepaymentsolutions.com/ |
| JetPay Gateway (65) | http://www.jetpay.com/ |
| HSBC XML API (ClearCommerce Engine) (66) | https://www.business.hsbc.uk/en-gb/payments/business-card |
| BluePay 2.0 Post (67) | http://www.bluepay.com |
| PayTrace Payment Gateway (70) | https://www.paytrace.net/ |
| TransNational Bankcard (74) | http://www.tnbci.com/ |
| First Data Global Gateway E4 (80) | http://www.firstdata.com |
| Bluefin (82) | http://www.bluefin.com/ |
| Payscape (83) | http://www.payscape.com |
| Pay Direct (Link2Gov) (84) | https://www.fisglobal.com/solutions/other/government/ |
| WorldPay US Link Gateway (87) | https://www.worldpay.com/en-us/index |
| 3DSI Payment WorkSuite (88) | http://www.3dsi.com/ |
| First Data PayPoint (90) | https://www.firstdata.com/en_us/customer-center/financial-institutions/paypoint.html |
| Converge (formerly MyVirtualMerchant) (93) | https://support.convergepay.com/s/ |
| Payeezy Gateway (formerly First Data E4) (94) | https://developer.payeezy.com/ |
| Authorize.NET XML (96) | http://www.authorize.net |
| PhoeniXGate Gateway (97) | http://www.phoenixmanagednetworks.com/ |
| Repay Gateway (98) | https://www.repay.com/ |
| BASYS Gateway (106) | https://basyspro.com/ |
| Quickbooks Payments (113) | https://quickbooks.intuit.com/payments/ |
| Shift4 (114) | https://www.shift4.com/ |
| PayTrace Payment Gateway JSON (117) | https://www.paytrace.net/ |
Data Type
Integer
GatewayURL Property (Retail Control)
Default URL for a specific Gateway .
Syntax
retailcontrol.GatewayURL[=string]
Default Value
""
Remarks
This property is used to change the default URL for a specific Gateway. This is useful for specifying a different URL for testing purposes, or to support additional gateway processors that share a protocol format (such as additional Authorize.net compatible gateways). Please note that the proper "http://" or "https://" formatting must be observed. See "Testing Information" in the Table of Contents for a list of test URLs.
Data Type
String
InvoiceNumber Property (Retail Control)
Merchant-generated invoice number.
Syntax
retailcontrol.InvoiceNumber[=string]
Default Value
""
Remarks
This field contains a merchant-generated invoice number. This number should be unique for each transaction. This property is optional for most gateways, but it is recommended that the merchant use an invoice number to keep track of transactions. See the Gateway property to determine if this is a required or optional field for the gateway you are using.
Data Type
String
Level2Aggregate Property (Retail Control)
The level 2 aggregate containing the data to be sent in the request.
Syntax
retailcontrol.Level2Aggregate[=string]
Default Value
""
Remarks
This property is used to specify the level 2 aggregate obtained from Level2 control. When specified, the control will parse the aggregate and send the specified values within the transaction request to process the transaction as a level 2 transaction.
Data Type
String
Level3Aggregate Property (Retail Control)
The level 3 aggregate containing the data to be sent in the request.
Syntax
retailcontrol.Level3Aggregate[=string]
Default Value
""
Remarks
This property is used to specify the level 3 aggregate obtained from Level3 control. When specified, the control will parse the aggregate and send the specified values within the transaction request to process the transaction as a level 3 transaction.
Data Type
String
MerchantLogin Property (Retail Control)
Merchant's Gateway login.
Syntax
retailcontrol.MerchantLogin[=string]
Default Value
""
Remarks
This is the login Id supplied by the Gateway you signed up with to process credit card transactions.
Data Type
String
MerchantPassword Property (Retail Control)
Merchant's Gateway password.
Syntax
retailcontrol.MerchantPassword[=string]
Default Value
""
Remarks
This is the password supplied by the Gateway you signed up with to process credit card transactions. Some gateways require passwords only for Credit or Void transactions, some require it for all transactions, and some do not require this field at all.
Data Type
String
ProxyAuthScheme Property (Retail Control)
This property is used to tell the control which type of authorization to perform when connecting to the proxy.
Syntax
retailcontrol.ProxyAuthScheme[=integer]
Possible Values
authBasic(0), authDigest(1), authProprietary(2), authNone(3), authNtlm(4), authNegotiate(5)
Default Value
0
Remarks
This property is used to tell the control which type of authorization to perform when connecting to the proxy. This is used only when the ProxyUser and ProxyPassword properties are set.
ProxyAuthScheme should be set to authNone (3) when no authentication is expected.
By default, ProxyAuthScheme is authBasic (0), and if the ProxyUser and ProxyPassword properties are set, the component will attempt basic authentication.
If ProxyAuthScheme is set to authDigest (1), digest authentication will be attempted instead.
If ProxyAuthScheme is set to authProprietary (2), then the authorization token will not be generated by the control. Look at the configuration file for the control being used to find more information about manually setting this token.
If ProxyAuthScheme is set to authNtlm (4), NTLM authentication will be used.
For security reasons, setting this property will clear the values of ProxyUser and ProxyPassword.
Data Type
Integer
ProxyAutoDetect Property (Retail Control)
This property tells the control whether or not to automatically detect and use proxy system settings, if available.
Syntax
retailcontrol.ProxyAutoDetect[=boolean]
Default Value
False
Remarks
This property tells the control whether or not to automatically detect and use proxy system settings, if available. The default value is .
Data Type
Boolean
ProxyPassword Property (Retail Control)
This property contains a password if authentication is to be used for the proxy.
Syntax
retailcontrol.ProxyPassword[=string]
Default Value
""
Remarks
This property contains a password if authentication is to be used for the proxy.
If ProxyAuthScheme is set to Basic Authentication, the ProxyUser and ProxyPassword are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If ProxyAuthScheme is set to Digest Authentication, the ProxyUser and ProxyPassword properties are used to respond to the Digest Authentication challenge from the server.
If ProxyAuthScheme is set to NTLM Authentication, the ProxyUser and ProxyPassword properties are used to authenticate through NTLM negotiation.
Data Type
String
ProxyPort Property (Retail Control)
This property contains the Transmission Control Protocol (TCP) port for the proxy Server (default 80).
Syntax
retailcontrol.ProxyPort[=integer]
Default Value
80
Remarks
This property contains the Transmission Control Protocol (TCP) port for the proxy ProxyServer (default 80). See the description of the ProxyServer property for details.
Data Type
Integer
ProxyServer Property (Retail Control)
If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.
Syntax
retailcontrol.ProxyServer[=string]
Default Value
""
Remarks
If a proxy ProxyServer is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.
If the ProxyServer property is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the ProxyServer property is set to the corresponding address. If the search is not successful, an error is returned.
Data Type
String
ProxySSL Property (Retail Control)
This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy.
Syntax
retailcontrol.ProxySSL[=integer]
Possible Values
psAutomatic(0), psAlways(1), psNever(2), psTunnel(3)
Default Value
0
Remarks
This property determines when to use a Secure Sockets Layer (SSL) for the connection to the proxy. The applicable values are as follows:
| psAutomatic (0) | Default setting. If the URL is an https URL, the control will use the psTunnel option. If the URL is an http URL, the control will use the psNever option. |
| psAlways (1) | The connection is always SSL enabled. |
| psNever (2) | The connection is not SSL enabled. |
| psTunnel (3) | The connection is made through a tunneling (HTTP) proxy. |
Data Type
Integer
ProxyUser Property (Retail Control)
This property contains a user name, if authentication is to be used for the proxy.
Syntax
retailcontrol.ProxyUser[=string]
Default Value
""
Remarks
This property contains a user name, if authentication is to be used for the proxy.
If ProxyAuthScheme is set to Basic Authentication, the ProxyUser and ProxyPassword are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If ProxyAuthScheme is set to Digest Authentication, the ProxyUser and ProxyPassword properties are used to respond to the Digest Authentication challenge from the server.
If ProxyAuthScheme is set to NTLM Authentication, the ProxyUser and ProxyPassword properties are used to authenticate through NTLM negotiation.
Data Type
String
ResponseApprovalCode Property (Retail Control)
Contains an authorization code when a transaction has been approved.
Syntax
retailcontrol.ResponseApprovalCode
Default Value
""
Remarks
Contains an authorization code when a transaction has been approved. This property contains an authorization code when a transaction has been approved. If the ResponseCode returned indicates that the transaction is not approved, then the contents of this property should be ignored.
This property is read-only and not available at design time.
Data Type
String
ResponseApproved Property (Retail Control)
Indicates the status of the last transaction.
Syntax
retailcontrol.ResponseApproved
Default Value
False
Remarks
Indicates the status of the last transaction. This property will be True if the last transaction was approved. However, you should not rely solely on the value contained in this property. After every transaction, the ResponseCode should be inspected and evaluated according to the specifications of the Gateway in use. A list of response codes for each gateway is listed in the table of contents. However, it is recommended that the developer acquire the current list from the Gateway which is being used.
This property is read-only and not available at design time.
Data Type
Boolean
ResponseApprovedAmount Property (Retail Control)
The amount approved for the transaction, this is the amount actually charged to the credit card.
Syntax
retailcontrol.ResponseApprovedAmount
Default Value
""
Remarks
The amount approved for the transaction, this is the amount actually charged to the credit card.
This property is primarily used when gateways allow partial authorizations and AllowPartialAuths is 'True'. Thus this property is not used by all gateways and should not alone be used to determine if a transaction was successful (such as in the case that this property is not populated).
This property is read-only and not available at design time.
Data Type
String
ResponseAVSResult Property (Retail Control)
Contains the Address Verification System result code.
Syntax
retailcontrol.ResponseAVSResult
Default Value
""
Remarks
Contains the Address Verification System result code. This one character property contains the Address Verification Service (AVS) result code. An AVS result code can provide additional information concerning the authentication of a particular transaction for which cardholder address verification was requested. An AVS result code of "0" will be returned in the response message when no address verification has been requested. The value returned should be stored for later retrieval, as it may be required when voiding or refunding a transaction. Valid AVS response codes are listed below, and are identical across all Gateway (note that some gateways do not return an AVS response).
| ResponseAVSResult | Description |
| A | Address matches, Zip does not. |
| E | AVS error. |
| G | Non-U.S. issuing bank does not support AVS. |
| N | No match on Address or CustomerZip. |
| P | AVS not applicable for this transaction. |
| R | Retry - Issuer system unavailable. |
| S | Service not supported by issuer. |
| U | Address information is unavailable. |
| W | Nine digit Zip matches, Address does not. |
| X | Exact AVS match, nine digit Zip. |
| Y | Exact AVS match, five digit Zip. |
| Z | Five digit Zip matches, Address does not. |
Note: Some gateways use their own response codes instead of those in the above table; those response codes are detailed below for such gateways.
Adyen
For Adyen, this property will contain the following possible values:
| 0 | Unknown |
| 1 | Address matches, postal code doesn't |
| 2 | Neither postal code nor address match |
| 3 | AVS unavailable |
| 4 | AVS not supported for this card type |
| 5 | No AVS data provided |
| 6 | Postal code matches, address doesn't match |
| 7 | Both postal code and address match |
| 8 | Address not checked, postal code unknown |
| 9 | Address matches, postal code unknown |
| 10 | Address doesn't match, postal code unknown |
| 11 | Postal code not checked, address unknown |
| 12 | Address matches, postal code not checked |
| 13 | Address doesn't match, postal code not checked |
| 14 | Postal code matches, address unknown |
| 15 | Postal code matches, address not checked |
| 16 | Postal code doesn't match, address unknown |
| 17 | Postal code doesn't match, address not checked |
| 18 | Neither postal code nor address were checked |
American Payment Solutions
For American Payment Solutions, this property will contain the following possible values:
| X | Exact match, 9-character numeric ZIP |
| Y, D, or M | Exact match, 5-character numeric ZIP |
| 2 or 6 | Exact match, 5-character numeric ZIP, customer name |
| A or B | Address match only |
| 3 or 7 | Address, customer name match only |
| W | 9-character numeric ZIP match only |
| Z, P, or L | 5-character ZIP match only |
| 1 or 5 | 5-character ZIP, customer name match only |
| N or C | No address or ZIP match only |
| 4 or 8 | No address or ZIP or customer name match only |
| U | Address unavailable |
| G or I | Non-U.S. issuer does not participate |
| R | Issuer system unavailable |
| E | Not a mail/phone order |
| S | Service not supported |
| 0, O, or B | AVS not available |
Barclay
For Barclay, the property will contain the following possible values:
| YY | Address and zip code or postal code match |
| YN | Address matches only |
| NY | Zip code or postal code matches |
| NN | Neither address nor zip code or postal code matches; address is not parsable |
| UU | Address information is unavailable, service is unavailable, or Error; Unknown |
| Blank | No AVS performed |
BlueSnap
For BlueSnap, the property will contain a 3-character string (if AVS checks were done), which contains the AVS checks for the following properties:
| 1st Character | Name AVS check |
| 2nd Character | Address AVS check |
| 3rd Character | Postal/Zip Code AVS check |
The possible values for each result character are:
| M | Matches |
| N | Does not match |
| U | Could not be verified |
HSBC
For HSBC, the property will contain the following possible values:
| YY | Address and zip code or postal code match |
| YN | Address matches only |
| NY | Zip code or postal code matches |
| NN | Neither address nor zip code or postal code matches; address is not parsable |
| UU | Address information is unavailable, service is unavailable, or Error; Unknown |
| FF | Issuer does not participate in AVS |
| Blank | No AVS performed |
PayTrace / PayTraceJSON
For PayTrace / PayTraceJSON, the property will contain the following possible values:
| Full Exact Match | |
| Address Match Only | |
| Zip Match Only | |
| No Match | |
| Address Unavailable | |
| Non-US Issuer does not participate | |
| Issuer System Unavailable | |
| Not a Mail/Phone Order | |
| Service Not Supported |
QBMS
For the QBMS gateway, the ResponseAVSResult property will contain the result for the street address, a comma, and then the result for the zip code. The values returned are "Pass", "Fail", and "NotAvailable". Therefore, an ResponseAVSResult of "Fail,Pass" means that the street address failed validation, but the zip code passed.
DataCash
For DataCash, the property will contain the following possible values (of which correspond to both AVS and CVV checks):
| NO DATA MATCHES | |
| ADDRESS MATCH ONLY | |
| SECURITY CODE MATCH ONLY | |
| ALL MATCH | |
| DATA NOT CHECKED |
Stripe
For Stripe, the property will contain the following possible values:
| Pass | The first address line or zip code provided is correct. |
| Fail | The first address line or zip code provided is incorrect. |
| Unavailable | The customer's bank did not check the first address line or zip code provided. |
| Unchecked | The first address line or zip code was provided but has not yet been checked. |
Worldpay
For Worldpay, the property will contain a 4-character string, which contains the AVS checks for the following properties:
| 1st Character | Card Verification Value (CVV) check |
| 2nd Character | Postal/Zip Code AVS check |
| 3rd Character | Address AVS check |
| 4th Character | Country Comparison check |
The possible values for each result character are:
| 0 | Not Supported. |
| 1 | Not Checked. |
| 2 | Matched. |
| 4 | No Match. |
| 8 | Partial Match. |
Worldpay Online
For Worldpay Online, the property will contain one of the following:
| Value | Description |
| APPROVED | The supplied street and postal code details fully matched the payment provider's records |
| PARTIAL APPROVED | One of the supplied street or postal code details did not match the payment provider's records |
| NOT SENT TO ACQUIRER | Problem with acquirer - possibly no AVS support |
| NO RESPONSE FROM ACQUIRER | Problem with acquirer - possibly no AVS support |
| NOT CHECKED BY ACQUIRER | The acquirer did not check the address details |
| NOT SUPPLIED BY SHOPPER | Missing, incomplete or invalid address details in the order prevented the address from being checked |
| FAILED | Both street and postal code details did not match the payment provider's records |
This property is read-only and not available at design time.
Data Type
String
ResponseCode Property (Retail Control)
Indicates the status of the authorization request.
Syntax
retailcontrol.ResponseCode
Default Value
""
Remarks
Indicates the status of the authorization request. This property contains the actual response code as returned by the Gateway. Unlike the ResponseApproved property, this ResponseCode property may provide more details about why a transaction was declined. Therefore, it is recommended that developers check the ResponseCode as well as the ResponseApproved property. The Point of Sale system should evaluate this response code and NOT the ResponseText to determine nature of a response message. The current (at the time of this release) response codes for the supported Gateways are listed in the table of contents to your left.
This property is read-only and not available at design time.
Data Type
String
ResponseCVVResult Property (Retail Control)
Contains the returned CVV2 result code if it was requested.
Syntax
retailcontrol.ResponseCVVResult
Default Value
""
Remarks
Contains the returned CVV2 result code if it was requested. This property contains the host returned CVV2 result code (if CVV data was sent in the request). The following is a list of current result codes:
| M | CVV2 Match. |
| N | CVV2 No Match. |
| P | Not Processed. |
| S | Merchant has indicated that CVV2 is not present on card. |
| U | Issuer not certified and/or has not provided Visa encryption keys. |
Note: Some gateways use their own response codes instead of those in the above table; those response codes are detailed below for such gateways.
HSBC
For HSBC, the property will contain:
| 0 | Card type does not support CVM |
| 1 | CVM match |
| 2 | CVM did not match issuer value |
| 3 | CVM was not processed |
| 4 | CVM should be on the card but cardholder indicated otherwise |
| 5 | CVM not supported by issuer |
| 6 | Not valid |
| 7 | No response from server |
Adyen
For Adyen, the property will contain:
| 0 | Unknown |
| 1 | Matches |
| 2 | Does not match |
| 3 | Not checked |
| 4 | No CVC/CVV provided, but was required |
| 5 | Issuer not certified for CVC/CVV |
| 6 | No CVC/CVV provided |
Barclay
For Barclay, the property will contain:
| 0,1 | CVM was not processed |
| 2 | CVM match |
| 4 | CVM does not match issuer value |
| Unknown | CVM invalid or missing |
| Blank | No response from server |
BlueSnap
For BlueSnap, the property will contain:
| MA | Match |
| NC | Issuer is not certified for CVV2/CVC2/CID |
| ND | Check was not done |
| NM | No match |
| NP | CVV2/CVC2/CID should be on the card but is not present |
| NR | CVV check not requested |
DataCash
For DataCash, the property will contain the following possible values (of which correspond to both AVS and CVV checks):
| NO DATA MATCHES | |
| ADDRESS MATCH ONLY | |
| SECURITY CODE MATCH ONLY | |
| ALL MATCH | |
| DATA NOT CHECKED |
Stripe
For Stripe, the property will contain the following possible values:
| Pass | The CVC provided is correct. |
| Fail | The CVC provided is incorrect. |
| Unavailable | The customer's bank did not check the CVC provided. |
| Unchecked | The CVC was provided but has not yet been checked. |
Worldpay Online
For Worldpay Online, the property will contain one of the following:
| Value | Description |
| APPROVED | The supplied CVC details matched the payment provider's records |
| NOT SENT TO ACQUIRER | Problem with acquirer - possibly no CVC support |
| NO RESPONSE FROM ACQUIRER | Problem with acquirer - possibly no CVC support |
| NOT CHECKED BY ACQUIRER | The acquirer did not check the CVC details |
| NOT SUPPLIED BY SHOPPER | Missing, or invalid CVC in the payment details prevented the CVC from being checked |
| FAILED | The supplied CVC did not match the payment provider's records |
This property is read-only and not available at design time.
Data Type
String
ResponseData Property (Retail Control)
The entire response returned from the gateway processor.
Syntax
retailcontrol.ResponseData
Default Value
""
Remarks
The entire response returned from the gateway processor. This property contains the entire response returned from the gateway processor. You may use this to parse additional information that is not returned in the standard response properties.
This property is read-only and not available at design time.
Data Type
String
ResponseErrorCode Property (Retail Control)
Additional error code returned by some gateways.
Syntax
retailcontrol.ResponseErrorCode
Default Value
""
Remarks
Additional error code returned by some gateways. If a gateway returns it, this property will contain an additional code that may explain why the transaction was declined. You may also wish to inspect ResponseErrorText for a human-readable description of this ResponseErrorCode.
This property is read-only and not available at design time.
Data Type
String
ResponseErrorText Property (Retail Control)
Additional error description returned by some gateways.
Syntax
retailcontrol.ResponseErrorText
Default Value
""
Remarks
Additional error description returned by some gateways. If a gateway returns it, this property will contain a human-readable description of the error which occurred (if any). You may also wish to inspect ResponseErrorCode for an accompanying code which may be parsed and used by your application.
This property is read-only and not available at design time.
Data Type
String
ResponseInvoiceNumber Property (Retail Control)
Invoice number submitted in authorization request (if applicable).
Syntax
retailcontrol.ResponseInvoiceNumber
Default Value
""
Remarks
Invoice number submitted in authorization request (if applicable). This property contains the Invoice Number submitted in the original transaction, echoed back by the Gateway host.
This property is read-only and not available at design time.
Data Type
String
ResponseProcessorCode Property (Retail Control)
Response code from the underlying processor.
Syntax
retailcontrol.ResponseProcessorCode
Default Value
""
Remarks
Response code from the underlying processor. Often times a Gateway will return a ResponseCode that indicates only whether the transaction is approved or declined. Many of these also include a secondary code that provides more details as to why the transaction was declined.
Note, for the PayFlowPro Gateway this property will contain a "1" if the transaction was a duplicate, a "-1" if duplicate checking service is unavailable, and will be blank for a successfully authorized transaction.
This property is read-only and not available at design time.
Data Type
String
ResponseText Property (Retail Control)
Text information that describes each response code.
Syntax
retailcontrol.ResponseText
Default Value
""
Remarks
Text information that describes each response code. This property contains a response or display text message. This message can be used by the terminal to display the authorization result. The display text must not be used to determine the nature of a response message. A Gateway may translate the response according to the language indicated in the merchant account setup (if applicable).
This property is read-only and not available at design time.
Data Type
String
ResponseTransactionId Property (Retail Control)
Contains the Visa Transaction Identifier or MasterCard Reference Number.
Syntax
retailcontrol.ResponseTransactionId
Default Value
""
Remarks
Contains the Visa Transaction Identifier or MasterCard Reference Number. This property contains a transaction identifier or reference number. The Point of Sale (POS) device should not attempt to interpret the meaning of any data appearing in this property. Data returned in this property (if any) should be recorded and used to submit a modification of this transaction at a later time (such as voiding the transaction or capturing an authorization-only transaction, if applicable).
This property is read-only and not available at design time.
Data Type
String
ShippingAddress Property (Retail Control)
Customer's shipping street address.
Syntax
retailcontrol.ShippingAddress[=string]
Default Value
""
Remarks
Customer's shipping street address.
This property is not available at design time.
Data Type
String
ShippingAddress2 Property (Retail Control)
A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.
Syntax
retailcontrol.ShippingAddress2[=string]
Default Value
""
Remarks
A specific detail on the customer's shipping address (such as building, suite, apartment, floor number etc.).
This property is not available at design time.
Data Type
String
ShippingCity Property (Retail Control)
Customer's shipping city.
Syntax
retailcontrol.ShippingCity[=string]
Default Value
""
Remarks
Customer's shipping city.
This property is not available at design time.
Data Type
String
ShippingCountry Property (Retail Control)
Customer's shipping country.
Syntax
retailcontrol.ShippingCountry[=string]
Default Value
""
Remarks
Customer's shipping country. This property contains the country in which the customer is located. Most gateways use a two-letter country code, specified in ISO-3166.
This property is not available at design time.
Data Type
String
ShippingEmail Property (Retail Control)
Customer's email address.
Syntax
retailcontrol.ShippingEmail[=string]
Default Value
""
Remarks
Customer's email address.
This property is not available at design time.
Data Type
String
ShippingFirstName Property (Retail Control)
Customer's first name.
Syntax
retailcontrol.ShippingFirstName[=string]
Default Value
""
Remarks
Customer's first name.
This property is not available at design time.
Data Type
String
ShippingLastName Property (Retail Control)
Customer's last name.
Syntax
retailcontrol.ShippingLastName[=string]
Default Value
""
Remarks
Customer's last name.
This property is not available at design time.
Data Type
String
ShippingPhone Property (Retail Control)
Customer's phone number.
Syntax
retailcontrol.ShippingPhone[=string]
Default Value
""
Remarks
Customer's phone number.
This property is not available at design time.
Data Type
String
ShippingState Property (Retail Control)
Customer's shipping state.
Syntax
retailcontrol.ShippingState[=string]
Default Value
""
Remarks
Customer's shipping state.
This property is not available at design time.
Data Type
String
ShippingZip Property (Retail Control)
Customer's shipping zip code (or postal code if outside of the USA).
Syntax
retailcontrol.ShippingZip[=string]
Default Value
""
Remarks
Customer's shipping zip code (or postal code if outside of the USA).
This property is not available at design time.
Data Type
String
SpecialFieldCount Property (Retail Control)
The number of records in the SpecialField arrays.
Syntax
retailcontrol.SpecialFieldCount[=integer]
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at SpecialFieldCount - 1.This property is not available at design time.
Data Type
Integer
SpecialFieldName Property (Retail Control)
Name of special configuration property to submit in this transaction.
Syntax
retailcontrol.SpecialFieldName(FieldIndex)[=string]
Default Value
""
Remarks
Name of special configuration field to submit in this transaction. The SpecialFieldName and SpecialFieldValue properties can be used to send special gateway configuration and transaction properties for each transaction. These properties can also be used to extend the functionality of this control by submitting additional information to the gateway.
This property is not applicable for the LinkPoint, FirstData, YourPay, PayFuse, or Orbital gateways.
The FieldIndex parameter specifies the index of the item in the array. The size of the array is controlled by the SpecialFieldCount property.
This property is not available at design time.
Data Type
String
SpecialFieldValue Property (Retail Control)
Value of special configuration property to submit in this transaction.
Syntax
retailcontrol.SpecialFieldValue(FieldIndex)[=string]
Default Value
""
Remarks
Value of special configuration field to submit in this transaction. The SpecialFieldName and SpecialFieldValue properties can be used to send special gateway configuration and transaction properties for each transaction. These properties can also be used to extend the functionality of this control by submitting additional information to the gateway.
Note: This property is not applicable for the LinkPoint, FirstData, YourPay, PayFuse, or Orbital gateways.
The FieldIndex parameter specifies the index of the item in the array. The size of the array is controlled by the SpecialFieldCount property.
This property is not available at design time.
Data Type
String
SSLAcceptServerCertEncoded Property (Retail Control)
This is the certificate (PEM/base64 encoded).
Syntax
retailcontrol.SSLAcceptServerCertEncoded[=string]
Default Value
""
Remarks
This is the certificate (PEM/base64 encoded). This property is used to assign a specific certificate. The SSLAcceptServerCertStore and SSLAcceptServerCertSubject properties also may be used to specify a certificate.
When SSLAcceptServerCertEncoded is set, a search is initiated in the current SSLAcceptServerCertStore for the private key of the certificate. If the key is found, SSLAcceptServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLAcceptServerCertSubject is set to an empty string.
To read or write binary data to the property, a Variant (Byte Array) version is provided in .SSLAcceptServerCertEncodedB.
This property is not available at design time.
Data Type
Binary String
SSLCertEncoded Property (Retail Control)
This is the certificate (PEM/base64 encoded).
Syntax
retailcontrol.SSLCertEncoded[=string]
Default Value
""
Remarks
This is the certificate (PEM/base64 encoded). This property is used to assign a specific certificate. The SSLCertStore and SSLCertSubject properties also may be used to specify a certificate.
When SSLCertEncoded is set, a search is initiated in the current SSLCertStore for the private key of the certificate. If the key is found, SSLCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLCertSubject is set to an empty string.
To read or write binary data to the property, a Variant (Byte Array) version is provided in .SSLCertEncodedB.
This property is not available at design time.
Data Type
Binary String
SSLCertStore Property (Retail Control)
This is the name of the certificate store for the client certificate.
Syntax
retailcontrol.SSLCertStore[=string]
Default Value
"MY"
Remarks
This is the name of the certificate store for the client certificate.
The SSLCertStoreType property denotes the type of the certificate store specified by SSLCertStore. If the store is password protected, specify the password in SSLCertStorePassword.
SSLCertStore is used in conjunction with the SSLCertSubject property to specify client certificates. If SSLCertStore has a value, and SSLCertSubject or SSLCertEncoded is set, a search for a certificate is initiated. Please see the SSLCertSubject property for details.
Designations of certificate stores are platform-dependent.
The following are designations of the most common User and Machine certificate stores in Windows:
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e. PKCS12 certificate store).
To read or write binary data to the property, a Variant (Byte Array) version is provided in .SSLCertStoreB.
Data Type
Binary String
SSLCertStorePassword Property (Retail Control)
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Syntax
retailcontrol.SSLCertStorePassword[=string]
Default Value
""
Remarks
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Data Type
String
SSLCertStoreType Property (Retail Control)
This is the type of certificate store for this certificate.
Syntax
retailcontrol.SSLCertStoreType[=integer]
Possible Values
cstUser(0), cstMachine(1), cstPFXFile(2), cstPFXBlob(3), cstJKSFile(4), cstJKSBlob(5), cstPEMKeyFile(6), cstPEMKeyBlob(7), cstPublicKeyFile(8), cstPublicKeyBlob(9), cstSSHPublicKeyBlob(10), cstP7BFile(11), cstP7BBlob(12), cstSSHPublicKeyFile(13), cstPPKFile(14), cstPPKBlob(15), cstXMLFile(16), cstXMLBlob(17), cstJWKFile(18), cstJWKBlob(19), cstSecurityKey(20), cstBCFKSFile(21), cstBCFKSBlob(22), cstPKCS11(23), cstAuto(99)
Default Value
0
Remarks
This is the type of certificate store for this certificate.
The control supports both public and private keys in a variety of formats. When the cstAuto value is used the control will automatically determine the type. This property can take one of the following values:
| 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note: this store type is not available in Java. |
| 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. Note: this store type is not available in Java. |
| 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS12) file containing certificates. |
| 3 (cstPFXBlob) | The certificate store is a string (binary or base64-encoded) representing a certificate store in PFX (PKCS12) format. |
| 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. Note: this store type is only available in Java. |
| 5 (cstJKSBlob) | The certificate store is a string (binary or base64-encoded) representing a certificate store in Java Key Store (JKS) format. Note: this store type is only available in Java. |
| 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| 7 (cstPEMKeyBlob) | The certificate store is a string (binary or base64-encoded) that contains a private key and an optional certificate. |
| 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| 9 (cstPublicKeyBlob) | The certificate store is a string (binary or base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or base64-encoded) that contains an SSH-style public key. |
| 11 (cstP7BFile) | The certificate store is the name of a PKCS7 file containing certificates. |
| 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS7 format. |
| 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
| 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
| 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
| 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
| 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
| 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
| 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). Note: this store type is only available in Java and .NET. |
| 22 (cstBCFKSBlob) | The certificate store is a string (binary or base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. Note: this store type is only available in Java and .NET. |
| 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS11 interface.
To use a security key the necessary data must first be collected using the CertMgr control. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS11 dll. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the SSLCertStore and set SSLCertStorePassword to the PIN. Code Example: SSH Authentication with Security Key
|
| 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |
Data Type
Integer
SSLCertSubject Property (Retail Control)
This is the subject of the certificate used for client authentication.
Syntax
retailcontrol.SSLCertSubject[=string]
Default Value
""
Remarks
This is the subject of the certificate used for client authentication.
This property must be set after all other certificate properites are set. When this property is set, a search is performed in the current certificate store certificate with matching subject.
If a matching certificate is found, the property is set to the full subject of the matching certificate.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks a random certificate in the certificate store.
The certificate subject is a comma separated list of distinguished name fields and values. For instance "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are displayed below.
| Field | Meaning |
| CN | Common Name. This is commonly a host name like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |
If a field value contains a comma it must be quoted.
Data Type
String
SSLProvider Property (Retail Control)
This specifies the SSL/TLS implementation to use.
Syntax
retailcontrol.SSLProvider[=integer]
Possible Values
sslpAutomatic(0), sslpPlatform(1), sslpInternal(2)
Default Value
0
Remarks
This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the control will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.
Possible values are:
| 0 (sslpAutomatic - default) | Automatically selects the appropriate implementation. |
| 1 (sslpPlatform) | Uses the platform/system implementation. |
| 2 (sslpInternal) | Uses the internal implementation. |
In most cases using the default value (Automatic) is recommended. The control will select a provider depending on the current platform.
When Automatic is selected the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used.
Data Type
Integer
SSLServerCertEncoded Property (Retail Control)
This is the certificate (PEM/base64 encoded).
Syntax
retailcontrol.SSLServerCertEncoded
Default Value
""
Remarks
This is the certificate (PEM/base64 encoded). This property is used to assign a specific certificate. The SSLServerCertStore and SSLServerCertSubject properties also may be used to specify a certificate.
When SSLServerCertEncoded is set, a search is initiated in the current SSLServerCertStore for the private key of the certificate. If the key is found, SSLServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLServerCertSubject is set to an empty string.
To read or write binary data to the property, a Variant (Byte Array) version is provided in .SSLServerCertEncodedB.
This property is read-only and not available at design time.
Data Type
Binary String
TestMode Property (Retail Control)
Turns test mode on and off for transactions sent to the current Gateway .
Syntax
retailcontrol.TestMode[=boolean]
Default Value
False
Remarks
You can use this property to set a test mode flag that will be sent in an authorization request. Not all Gateways support test modes. If you set the TestMode property to True and the current Gateway does not support it, the control will fails with an error.
Data Type
Boolean
Timeout Property (Retail Control)
A timeout for the control.
Syntax
retailcontrol.Timeout[=integer]
Default Value
30
Remarks
If Timeout is set to a positive value, and an operation cannot be completed immediately, the control will retry the operation for a maximum of Timeout seconds.
The default value for Timeout is 30 (seconds).
Data Type
Integer
TransactionAmount Property (Retail Control)
Purchase amount for an authorization transaction.
Syntax
retailcontrol.TransactionAmount[=string]
Default Value
""
Remarks
This field contains the transaction amount to be authorized. Gateways may have differing requirements for how the TransactionAmount should be formatted, so refer to the ICharge Gateway Setup page for details on the gateway you are using.
Data Type
String
TransactionDesc Property (Retail Control)
Description of goods purchased.
Syntax
retailcontrol.TransactionDesc[=string]
Default Value
""
Remarks
This field contains a description of the goods or services being purchased. Please see the "ICharge Gateway Setup and Required Properties" page to determine if this is a required or optional field for the gateway you are using.
Data Type
String
TransactionId Property (Retail Control)
Merchant-generated transaction Id used for all transactions.
Syntax
retailcontrol.TransactionId[=string]
Default Value
""
Remarks
This property is used to send a merchant-generated transaction id to the Gateway, if the gateway supports that feature.
Data Type
String
AddSpecialField Method (Retail Control)
Adds a special field name and the corresponding value.
Syntax
retailcontrol.AddSpecialField Name, Value
Remarks
Please refer to the SpecialFieldName and SpecialFieldValue properties for more information on form variables and how they are managed.
AuthOnly Method (Retail Control)
Initiates an authorization-only request transaction.
Syntax
retailcontrol.AuthOnly
Remarks
This method sends an authorization-only request to the specified Gateway. This transaction is not added to the current open batch, and must be completed later with the Capture method (you may use the Sale method if you wish to authorize and capture in one step).
Note: If the Gateway does not support this method, the control will fails with an error.
AVSOnly Method (Retail Control)
Used to check the validity of the card without authorizing funds.
Syntax
retailcontrol.AVSOnly
Remarks
This method can be used if you wish to perform fraud (AVS and CVV) checks on a card, but don't actually wish to charge the customer. This is useful for pre-ordering an item that has not yet been released or is currently back- ordered. The card information is validated by the merchant, and when the item is later in stock and ships to the customer, an Sale transaction can be performed.
Note: If the Gateway does not support this method, the control will fails with an error.
Capture Method (Retail Control)
Captures a previously authorized transaction.
Syntax
retailcontrol.Capture TransactionId, CaptureAmount
Remarks
This method captures a transaction that has been previously authorized with the AuthOnly method. The TransactionId parameter indicates to the Gateway which transaction is to be captured, and should contain the ResponseTransactionId from the original transaction. The CaptureAmount parameter is the value to be captured from the customer's credit card, and can be different from the authorized amount.
Please see the gateway information in the table of contents to determine if your gateway supports Capture transactions.
The LinkPoint and PSIGateXML gateways require you send the ResponseInvoiceNumber rather than the ResponseTransactionId.
The SecurePay gateway does not require the TransactionId for captures. Instead, you must send the ResponseApprovalCode returned from the original response in the AuthCode property.
The MyVirtualMerchant and Converge gateways do not require the TransactionId for captures. Instead, you must send the ResponseApprovalCode returned from the original response in the AuthCode property. Note that there is a new capture transaction type available for these gateways. To use the new transaction type, set the MyVirtualMerchantTransactionType to "CCCOMPLETE" and call Capture like normal. When using this transaction type, TransactionId is required and ResponseApprovalCode is not applicable.
Config Method (Retail Control)
Sets or retrieves a configuration setting.
Syntax
retailcontrol.Config ConfigurationString
Remarks
Config is a generic method available in every control. It is used to set and retrieve configuration settings for the control.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the control, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
Credit Method (Retail Control)
Credits a customer's card.
Syntax
retailcontrol.Credit
Remarks
This method credits a customer's card specified via Card. This type of transaction is NOT based on previous transaction. Some gateways refer to these as "Open" or "Blind" Credits.
TransactionAmount is used to specify the amount you wish to return to the customer's card.
Please see the gateway information in the table of contents to determine if your gateway supports Credit transactions.
DoEvents Method (Retail Control)
Processes events from the internal message queue.
Syntax
retailcontrol.DoEvents
Remarks
When DoEvents is called, the control processes any available events. If no events are available, it waits for a preset period of time, and then returns.
Force Method (Retail Control)
Used when authorization cannot be obtained online.
Syntax
retailcontrol.Force VoiceAuthCode
Remarks
This method is used when the response to a Sale or AuthOnly request indicates that voice authorization is required. The merchant then telephones the call center and receives a voice authorization code. Calling the Force method with this code in the VoiceAuthCode parameter will complete the transaction.
Note: If the Gateway does not support this method, the control will fails with an error.
GetResponseVar Method (Retail Control)
Parses additional information out of the response.
Syntax
retailcontrol.GetResponseVar Name
Remarks
Due to the fact that this control supports so many gateways, only the most commonly used response variables are parsed into the Response properties. Any additional response information contained within the ResponseData may be retrieved with this GetResponseVar method. There are three formats for the ResponseData returned by the gateways this control supports: Name/value pairs, delimited list, or XML. The value you pass in the Name parameter changes based on these formats, as detailed below:
If the ResponseData property contains name/value pairs, pass the name in the Name parameter and this method will return the value. For instance, if ResponseData contains "ResponseCode=00&FraudScore=53&ApprovalCode=123456&...", calling GetResponseVar("FraudScore") will return "53".
However, if ResponseData contains a delimited list, pass the index of the field you wish to receive. For instance, if ResponseData contains "00|53|123456|...", calling GetResponseVar("1") will return "53".
Finally, if ResponseData contains XML, pass the xpath to the value you wish to receive. For instance, if ResponseData contains "<Response><Code>00</Code><FraudScore>53</FraudScore><ApprovalCode>123456</ApprovalCode></Response>", calling GetResponseVar("/Response/FraudScore") will return "53".
Interrupt Method (Retail Control)
Interrupts the current action.
Syntax
retailcontrol.Interrupt
Remarks
This method interrupts any processing that the control is currently executing.
Refund Method (Retail Control)
Refunds a previously captured transaction.
Syntax
retailcontrol.Refund TransactionId, RefundAmount
Remarks
This method refunds a transaction that has already been captured, or settled. If the transaction is still outstanding use the VoidTransaction method instead. The TransactionId parameter indicates to the Gateway which transaction is to be refunded, and should contain the ResponseTransactionId from the original transaction. The RefundAmount parameter is the value to be refunded back to the customer, and can be all or part of the original TransactionAmount
Please see the gateway information in the table of contents to determine if your gateway supports Refund transactions.
The gw3DSI gateway requires the following additional fields for Refund transactions:
control.AddSpecialField "UserId", "my 3DSI-assigned UserId" '(Different than MerchantLogin)
control.MerchantPassword = "my 3DSI-assigned Pwd"
The LinkPoint and PSIGateXML gateways require you send the ResponseInvoiceNumber rather than the ResponseTransactionId.
Reset Method (Retail Control)
Clears all properties to their default values.
Syntax
retailcontrol.Reset
Remarks
This method clears all properties to their default values and returns the component to its default state.
ResetSpecialFields Method (Retail Control)
Resets all special fields to the default settings.
Syntax
retailcontrol.ResetSpecialFields
Remarks
This function resets all special gateway configuration fields to the default settings for the specified Gateway.
Please refer to the SpecialFieldName and SpecialFieldValue properties for more information on form variables and how they are managed.
Sale Method (Retail Control)
Initiates an Sale transaction (authorization and capture).
Syntax
retailcontrol.Sale
Remarks
Sends a basic sale transaction to the Gateway. This transaction decrements the cardholder's open-to-buy funds for the TransactionAmount, and the transaction is automatically added to the current open batch.
VoidTransaction Method (Retail Control)
Voids a previously authorized transaction.
Syntax
retailcontrol.VoidTransaction TransactionId
Remarks
This method voids a transaction that has been previously authorized, but which has not yet gone to settlement, or been "captured". The TransactionId parameter indicates to the Gateway which transaction is to be voided, and should contain the ResponseTransactionId from the original transaction.
Please see the gateway information in the table of contents to determine if your gateway supports Void transactions.
To cancel a transaction which has already been captured, use the Credit method.
The LinkPoint gateway requires you send the ResponseInvoiceNumber rather than the ResponseTransactionId.
For the PSIGateXML gateway, send the ResponseTransactionId as normal.
For the Heartland gateway, a reversal transaction will be sent when a TransactionAmount is specified. Otherwise a void transaction will be sent.
Error Event (Retail Control)
Information about errors during data delivery.
Syntax
Sub retailcontrol_Error(ErrorCode As Integer, Description As String)
Remarks
The Error event is fired in case of exceptional conditions during message processing.
ErrorCode contains an error code and Description contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.
SSLServerAuthentication Event (Retail Control)
Fired after the server presents its certificate to the client.
Syntax
Sub retailcontrol_SSLServerAuthentication(CertEncoded As String, CertSubject As String, CertIssuer As String, Status As String, Accept As Boolean)
Remarks
This event is where the client can decide whether to continue with the connection process or not. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether to continue or not.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string "OK"). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (Retail Control)
Shows the progress of the secure connection.
Syntax
Sub retailcontrol_SSLStatus(Message As String)
Remarks
The event is fired for informational and logging purposes only. Used to track the progress of the connection.
Config Settings (Retail Control)
The control 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 control, access to these internal properties is provided through the Config method.Retail Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3DSAuthenticationStatus:
Indicates whether a transaction qualifies as a ThreeDSecure (3DS) authenticated transaction.This setting is used to pass the 3D Secure authentication status on to the transaction server. This component may
be used in conjunction with the ThreeDSecure component or with any other 3D Secure MPI implementation. Other values
necessary for passing 3D Secure data include 3DSCAVV, 3DSXID and 3DSECI.
This setting is only valid for E-Commerce transactions. Applicable values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 ResponseApprovedAmount. 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 control will automatically convert the amount from
the specified format to the format expected by the gateway. Valid values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| BluePayKSN: The Key Serial Number (KSN) used to encrypt the card magnetic stripe data for the BluePay gateway.This config is used to specify the Key Serial Number (KSN) value after encrypting card magnetic stripe (track) data and is returned using BluePay's encryption tools. Prior to specifying encrypted card data, CardEncrypted should be set to "True". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| BluePayMasterId: Used to reference a previous transaction in BluePay.This setting takes a previous transaction's ResponseTransactionId. For any parameters that are not set, BluePay will use values from the referenced transaction. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| BluePayPreEncryptedTrackLength: The length of the magnetic stripe data prior to encryption for the BluePay gateway.This config is used to specify the length of the magnetic stripe (track) data prior to it being encrypted using BluePay's encryption tools. Prior to specifying encrypted card data, CardEncrypted should be set to "True". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 ResponseTransactionId of the previous request, and the transaction can only be updated before it has been settled by BluePay. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CardEncrypted:
Specifies whether the card magnetic stripe data is encrypted.Set this config to "True" to allow encrypted card track data to be specified and sent in the request.
Note that this config must be set to "True" prior to setting CardMagneticStripe to the encrypted
magnetic stripe data, otherwise an exception may be thrown when the component attempts to verify the
magnetic stripe data format. The default value is "False".
Note: When using the BASYS, PhoeniXGate, or Repay Gateways, set this configuration setting to True so both Track1 and Track2 Data are sent in the request. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CardPresent:
Specifies whether the card is present during the transaction.When set to "True" (default value), in the case of a manually entered card, the transaction
will be processed with the card being identified as present. When set to "False", the transaction
will be processed as a 'Card Not Present' transaction.
This config is currently applicable to the Heartland gateway. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CardType:
Type of credit card being used in this transaction.This config is used to specify the type of credit card being used in a retail transaction.
The type will be computed by the component based on the Card data but this value can be
specified to override any computed values.
The available card types are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CAVVResponse: Contains CAVV response value returned by the gateway.This property will contain the CAVV response value to the authorization and will be populated along with Response. Values vary between gateways, so please consult gateway documentation for more information. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| COFPermission: Indicates if the customer gave permission to make a Card On File transaction.When true, this setting indicates that the customer gave the merchant permission to perform a Card On File (COF) transaction. Currently only used by CardPointe (gwCardPointe). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ConvenienceFee: The total convenience fee charged for a transaction.This field is used to specify the total convenience fee charged for the transaction. This field is applicable to the FirstDataPayPoint and Litle / Vantiv gateway. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 control does not perform any XML escaping and the values are sent exactly as specified. The default value is "False". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DebitKSN:
Clear-text Key Sequence Number retrieved from a PIN pad.This field is used to set a 19 or 20-byte Key Sequence Number (KSN). This field is associated with
DebitPIN and both are required for Debit Sale transactions.
The following gateways support Debit card transactions:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| DebitPIN:
DUKPT DES encrypted pin block, retrieved from a PIN pad.This field is used to set a 16-byte encrypted PIN for a Debit card. This field is associated with
DebitKSN and both are required for Debit Sale transactions.
The following gateways support Debit card transactions:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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, CardExpMonth, and CardExpYear 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 control 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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, ResponseTransactionId, 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 control fails with an error. 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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");
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| LitleCardholderID:
Describes the method used to identify the cardholder at the point of sale for the Litle gateway.This config is used to specify the method used to identify the customer when performing a retail transaction.
The available values are (if not specified, the component will send 'signature' by default):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
Below is a sample XML aggregate for the url child:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MerchantPartnersReaderType:
The reader type used to read and encrypt a swiped card for the MerchantPartners or WorldPay Link gateways.This setting is used to specify the encrypted reader type used to read and encrypt a swiped card. The specified value is sent
in the request and is used by the gateway to decrypt the card data so the transaction can be processed.
Valid Values:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OrbitalCustomerProfileOrderOverrideInd:
Indicator to specify how the CustomerId is leveraged to populate other data sets for the Orbital gateway.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 ResponseTransactionId from the transaction you wish to retrieve. You may also call PFPInquiry without setting it to anything. In this case the CustomerId 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 ResponseTransactionId 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):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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, ResponseTransactionId will contain the token value that corresponds to the credit card data stored. This token value can then be used to process transactions via PayFlowProToken. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PayJunctionUpdateAmount: Indicates whether the capture method should send an update amount request when using the PayJunction gateway.This field allows you to specify whether Capture will send an update amount or a capture request. By default, this value is 'False', which sends a capture request to mark an AuthOnly transaction for capture. This particular function does not allow you to alter the amount but instead just marks the authorized amount (from the AuthOnly transaction) for capture. When this field is set to 'True', the Capture method will send an update amount request allowing you to alter the amount that will be captured. This method can be used after AuthOnly and Sale transactions. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PaymentWorkSuiteClientCode: The 3DSI assigned client code sent in a request to the PaymentWorksuite gateway.This field is used to specify the client code that is assigned by 3DSI. This code uniquely identifies your organization for the purpose of accessing and authenticating to the Payment WorkSuite. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PaymentWorkSuiteLocationCode: The 3DSI assigned location code sent in a request to the PaymentWorksuite gateway.This field is used to specify the location code that uniquely identifies a specific location that is associated with the merchant identified by the specified PaymentWorkSuiteMerchantCode. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PaymentWorkSuiteMerchantCode: The 3DSI assigned merchant code sent in a request to the PaymentWorksuite gateway.This field is used to specify the merchant code that uniquely identifies a specific merchant within the Payment WorkSuite. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PayPointFreedomAPI: Indicates whether to use the Freedom API for the gwPayPoint and gwSECPay gateways.The field is used to indicate whether to use the Freedom API for either the gwPayPoint and gwSECPay gateway. When set to true, the Freedom API will be used instead of the XML Hosted specification. Note that you must set Gateway to either gwPayPoint or gwSECPay prior to setting this field. Additionally, if you decide to use the Freedom API, this field must be set directly after setting Gateway (as GatewayURL will be updated). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PayTraceAddPurchaseCardData:
Sends a Level3 request for the PayTrace gateway.This config is used to add Purchase Card (Level2 and Level3) Data to an existing sale transaction for the PayTrace gateway.
The Level2Aggregate and Level3Aggregate fields can be set to specify the purchase card data you wish to add prior to
calling this config. A TransactionId, from the response of the original sale, is required to be specified when calling
this config; i.e.:
ICharge.Config("PayTraceAddPurchaseCardData=123456789");
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PayTraceIntegratorId: Used to specify the Integrator Id value assigned by the PayTrace gateway.This value is assigned by PayTrace and is used for validation and tracking purposes. The default value is: "90000035NSFT". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PayTraceJSONCardToken:
The token value for a corresponding card.This field is used to specify card token value that you retrieved from Protect.js (see PayTrace documentation for details).
This field must be set prior to performing a transaction using a token value instead of a Card.
Note that this is only valid when calling Sale or AuthOnly methods and the Gateway property is set to gwPayTraceJSON (117) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PayTraceJSONEncryptionKey:
The Encryption Key to use with the PayTraceJSON gateway.This field is used to specify the encryption key that you retrieved from Protect.js (see PayTrace documentation for details).
Note that this is only valid when calling Sale or AuthOnly methods and the Gateway property is set to gwPayTraceJSON (117) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
PayTraceJSONGetClientKeyToken:
Retrieves a new Client Key (PROTECT AUTH TOKEN) from PayTrace.This is an Action config. Getting this config will cause the control to obtain a Client Key (PROTECT AUTH TOKEN) from PayTrace.
The Client Key will be used to authorize your application to use Protect.js to retrieve Card Token (hpf token) and Encryption Key (enc key).
Please see PayTrace documentation for details. This key is valid for 20 minutes.
icharge = new Icharge();
icharge.Gateway = IchargeGateways.gwPayTraceJSON;
icharge.GatewayURL = "https://api.paytrace.com";
icharge.MerchantLogin = bearerToken;
string clientKeyToken = control.Config("PayTraceJSONGetClientKeyToken"); //use this key to obtain "hpf_token" and "enc_key" from Protect.js
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 CardNumber. 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 ResponseTransactionId 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TerminalCapability:
The capability of the terminal that is used to submit the transaction.This config is used to specify the capability of the terminal being used in a retail transaction.
The available values for the CyberSource gateway are (If not specified, the component will set the value to either '2' or '3' based on the specified CardEntryDataSource.):
The available values for the Litle gateway are (If not specified, the component will set the value to 'magstripe'.):
For Shift4 this field is more complicated, and should be set to a JSON object matching the value of the device.capability field from the Shift4 documentation. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TerminalManufacturer: The manufacturer of the terminal used to submit the transaction.This config is used to specify the manufacturer of the terminal (device) being used in a retail transaction. This config is used with the Shift4 gateway. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TerminalModel: The model of the terminal used to submit the transaction.This config is used to specify the model of the terminal (device) being used in a retail transaction. This config is used with the Shift4 gateway. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TerminalType:
The terminal type that is used to submit the transaction.This config is used to specify the terminal (device) type being used in a retail transaction.
The available values for Authorize.NET are (required):
The available values for USA EPay are (required):
The available values for Chase, First Data, LinkPoint, and YourPay are (required):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
Example (Setting XPath for XML)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| XText:
The text of the current element.The current element is specified in the XPath configuration option.
This configuration option is read-only. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HTTP Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AcceptEncoding: Used to tell the server which types of content encodings the client supports.When AllowHTTPCompression is True, the control adds an Accept-Encoding header to the request being sent to the server. By default, this header's value is "gzip, deflate". This configuration setting allows you to change the value of the Accept-Encoding header. Note: The control only supports gzip and deflate decompression algorithms. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AllowHTTPCompression:
This property enables HTTP compression for receiving data.This configuration setting enables HTTP compression for receiving data.
When set to True (default), the control will accept compressed data. It then will uncompress the data it has received. The control will handle data compressed by both gzip and deflate compression algorithms.
When True, the control adds an Accept-Encoding header to the outgoing request. The value for this header can be controlled by the AcceptEncoding configuration setting. The default value for this header is "gzip, deflate". The default value is True. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AllowHTTPFallback:
Whether HTTP/2 connections are permitted to fallback to HTTP/1.1.This configuration setting controls whether HTTP/2 connections are permitted to fall back to HTTP/1.1 when the server
does not support HTTP/2. This setting is applicable only when HTTPVersion is set to "2.0".
If set to True (default), the control will automatically use HTTP/1.1 if the server does not support HTTP/2. If set to False, the control fails with an error if the server does not support HTTP/2. The default value is True. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Append: Whether to append data to LocalFile.This configuration setting determines whether data will be appended when writing to LocalFile. When set to True, downloaded data will be appended to LocalFile. This may be used in conjunction with Range to resume a failed download. This is applicable only when LocalFile is set. The default value is False. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Authorization:
The Authorization string to be sent to the server.If the Authorization property contains a nonempty string,
an Authorization HTTP request header is added to the
request. This header conveys Authorization information to the
server.
This property is provided so that the HTTP control can be extended with other security schemes in addition to the authorization schemes already implemented by the control. The AuthScheme property defines the authentication scheme used. In the case of HTTP Basic Authentication (default), every time User and Password are set, they are Base64 encoded, and the result is put in the Authorization property in the form "Basic [encoded-user-password]". |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| BytesTransferred: Contains the number of bytes transferred in the response data.This configuration setting returns the raw number of bytes from the HTTP response data, before the component processes the data, whether it is chunked or compressed. This returns the same value as the Transfer event, by BytesTransferred. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ChunkSize: Specifies the chunk size in bytes when using chunked encoding.This is applicable only when UseChunkedEncoding is True. This setting specifies the chunk size in bytes to be used when posting data. The default value is 16384. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CompressHTTPRequest:
Set to true to compress the body of a PUT or POST request.If set to True, the body of a PUT or POST request will be compressed into gzip format before sending the request. The "Content-Encoding" header is also added to the outgoing request.
The default value is False. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| EncodeURL: If set to True the URL will be encoded by the control.If set to True, the URL passed to the control 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 control 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 control fails with an error. Note: Following the HTTP specification, unless this option is set to 1 (Always), automatic redirects will be performed only for GET or HEAD requests. Other methods potentially could change the conditions of the initial request and create security vulnerabilities. Furthermore, if either the new URL server or port are different from the existing one, User and Password are also reset to empty, unless this property is set to 1 (Always), in which case the same credentials are used to connect to the new server. A Redirect event is fired for every URL the product is redirected to. In the case of automatic redirections, the Redirect event is a good place to set properties related to the new connection (e.g., new authentication parameters). The default value is 0 (Never). In this case, redirects are never followed, and the control fails with an error instead. Following are the valid options:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| GetOn302Redirect: If set to True the control will perform a GET on the new location.The default value is False. If set to True, the control will perform a GET on the new location. Otherwise, it will use the same HTTP method again. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| HTTP2HeadersWithoutIndexing: HTTP2 headers that should not update the dynamic header table with incremental indexing.HTTP/2 servers maintain a dynamic table of headers and values seen over the course of a connection. Typically, these headers are inserted into the table through incremental indexing (also known as HPACK, defined in RFC 7541). To tell the component not to use incremental indexing for certain headers, and thus not update the dynamic table, set this configuration option to a comma-delimited list of the header names. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HTTPVersion:
The version of HTTP used by the control.This property specifies the HTTP version used by the control. Possible values are as follows:
When using HTTP/2 ("2.0"), additional restrictions apply. Please see the following notes for details.
HTTP/2 NotesWhen using HTTP/2, a secure Secure Sockets Layer/Transport Layer Security (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/2 will result in an error. If the server does not support HTTP/2, the control will automatically use HTTP/1.1 instead. This is done to provide compatibility without the need for any additional settings. To see which version was used, check NegotiatedHTTPVersion after calling a method. The AllowHTTPFallback setting controls whether this behavior is allowed (default) or disallowed.
HTTP/3 NotesHTTP/3 is supported only in .NET and Java. When using HTTP/3, a secure (TLS/SSL) connection is required. Attempting to use a plaintext URL with HTTP/3 will result in an error. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IfModifiedSince:
A date determining the maximum age of the desired document.If this setting contains a nonempty string, an If-Modified-Since HTTP header is added to the request.
The value of this header is used to make the HTTP request conditional: if the requested documented has not
been modified since the time specified in the field, a copy of the document will not be returned from
the server; instead, a 304 (not modified) response will be returned by the server and the component throws an exception
The format of the date value for IfModifiedSince is detailed in the HTTP specs. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| KeepAlive:
Determines whether the HTTP connection is closed after completion of the request.If True, the component will not send the Connection: Close header. The absence of the Connection header indicates to the server
that HTTP persistent connections should be used if supported.
Note: Not all servers support persistent connections. You also may explicitly add the Keep-Alive header to the request headers by setting OtherHeaders to Connection: Keep-Alive.
If False, the connection will be closed immediately after the server response is received.
The default value for KeepAlive is False. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| KerberosSPN: The Service Principal Name for the Kerberos Domain Controller.If the Service Principal Name on the Kerberos Domain Controller is not the same as the URL that you are authenticating to, the Service Principal Name should be set here. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LogLevel:
The level of detail that is logged.This configuration setting controls the level of detail that is logged through the Log event. Possible values are as follows:
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 other than frNever, the control will follow redirects until this maximum number of redirect attempts are made. The default value is 20. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| NegotiatedHTTPVersion: The negotiated HTTP version.This configuration setting may be queried after the request is complete to indicate the HTTP version used. When HTTPVersion is set to "2.0" (if the server does not support "2.0"), then the control will fall back to using "1.1" automatically. This setting will indicate which version was used. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| OtherHeaders:
Other headers as determined by the user (optional).This configuration setting can be set to a string of headers to be appended to the HTTP request headers.
The headers must follow the format "header: value" as described in the HTTP specifications. Header lines should be separated by CRLF (Chr$(13) & Chr$(10)) . Use this configuration setting with caution. If this configuration setting contains invalid headers, HTTP requests may fail. This configuration setting is useful for extending the functionality of the control beyond what is provided. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyAuthorization: The authorization string to be sent to the proxy server.This is similar to the Authorization configuration setting, but is used for proxy authorization. If this configuration setting contains a nonempty string, a Proxy-Authorization HTTP request header is added to the request. This header conveys proxy Authorization information to the server. If ProxyUser and ProxyPassword are specified, this value is calculated using the algorithm specified by ProxyAuthScheme. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyAuthScheme: The authorization scheme to be used for the proxy.This configuration setting is provided for use by controls that do not directly expose Proxy properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyPassword: A password if authentication is to be used for the proxy.This configuration setting is provided for use by controls that do not directly expose Proxy properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyPort: Port for the proxy server (default 80).This configuration setting is provided for use by controls that do not directly expose Proxy properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyServer: Name or IP address of a proxy server (optional).This configuration setting is provided for use by controls that do not directly expose Proxy properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyUser: A user name if authentication is to be used for the proxy.This configuration setting is provided for use by controls that do not directly expose Proxy properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SentHeaders: The full set of headers as sent by the client.This configuration setting returns the complete set of raw headers as sent by the client. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| StatusLine: The first line of the last response from the server.This setting contains the first line of the last response from the server. The format of the line will be [HTTP version] [Result Code] [Description]. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TransferredData: The contents of the last response from the server.This configuration setting contains the contents of the last response from the server. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TransferredDataLimit: The maximum number of incoming bytes to be stored by the control.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 control. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TransferredHeaders: The full set of headers as received from the server.This configuration setting returns the complete set of raw headers as received from the server. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TransferredRequest:
The full request as sent by the client.This configuration setting returns the full request as sent by the client. For performance reasons, the request is not normally saved. Set this configuration setting to ON before making a request to enable it. Following are examples of this request:
.NET
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UseChunkedEncoding:
Enables or Disables HTTP chunked encoding for transfers.If UseChunkedEncoding is set to True, the control 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 control will not use HTTP-chunked encoding. The default value is False.
Note: Some servers (such as the ASP.NET Development Server) may not support chunked encoding. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UseIDNs:
Whether to encode hostnames to internationalized domain names.This configuration setting specifies whether hostnames containing non-ASCII characters are encoded to internationalized domain names. When set to True, if a hostname contains non-ASCII characters, it is encoded using Punycode to an IDN (internationalized domain name).
The default value is False and the hostname will always be used exactly as specified. 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. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UseProxyAutoConfigURL:
Whether to use a Proxy auto-config file when attempting a connection.This configuration specifies whether the control will attempt to use the Proxy auto-config URL when establishing a connection and ProxyAutoDetect is set to True.
When True (default), the control will check for the existence of a Proxy auto-config URL, and if found, will determine the appropriate proxy to use. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UserAgent:
Information about the user agent (browser).This is the value supplied in the HTTP User-Agent header. The default
setting is "IPWorks HTTP Component - www.nsoftware.com".
Override the default with the name and version of your software. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TCPClient Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 control will use Timeout for establishing a connection and transmitting/receiving data. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FirewallAutoDetect: Tells the control whether or not to automatically detect and use firewall system settings, if available.This configuration setting is provided for use by controls that do not directly expose Firewall properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FirewallHost:
Name or IP address of firewall (optional).If a FirewallHost is given, requested connections will be authenticated through the specified firewall
when connecting.
If the FirewallHost setting is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the FirewallHost setting is set to the corresponding address. If the search is not successful, an error is returned. Note: This setting is provided for use by controls 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 control fails with an error.
Note: This setting is provided for use by controls that do not directly expose Firewall properties. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FirewallPort:
The TCP port for the FirewallHost;.The FirewallPort is set automatically when FirewallType is set to a valid value.
Note: This configuration setting is provided for use by controls that do not directly expose Firewall properties. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
FirewallType:
Determines the type of firewall to connect through.The appropriate values are as follows:
Note: This setting is provided for use by controls 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 control fails with an error.
Note: This setting is provided for use by controls that do not directly expose Firewall properties. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| KeepAliveInterval:
The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.When set, TCPKeepAlive will automatically be set to True.
A TCP keep-alive packet will be sent after a period of inactivity as
defined by KeepAliveTime. If no acknowledgment is received from the remote host, the keep-alive packet
will be sent again. This configuration setting specifies the interval at which the successive keep-alive packets are sent in milliseconds.
This system default if this value is not specified here is 1 second.
Note: This value is not applicable in macOS. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| KeepAliveTime: The inactivity time in milliseconds before a TCP keep-alive packet is sent.When set, TCPKeepAlive will automatically be set to True. By default, the operating system will determine the time a connection is idle before a Transmission Control Protocol (TCP) keep-alive packet is sent. This system default if this value is not specified here is 2 hours. In many cases, a shorter interval is more useful. Set this value to the desired interval in milliseconds. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linger:
When set to True, connections are terminated gracefully.This property controls how a connection is closed. The default is True.
In the case that Linger is True (default), two scenarios determine how long the connection will linger. In the first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP timeout expires. In the second scenario, if LingerTime is a positive value, the system will attempt to send pending data until the specified LingerTime is reached. If this attempt fails, then the system will reset the connection. The default behavior (which is also the default mode for stream sockets) might result in a long delay in closing the connection. Although the control returns control immediately, the system could hold system resources until all pending data are sent (even after your application closes). Setting this property to False forces an immediate disconnection. If you know that the other side has received all the data you sent (e.g., by a client acknowledgment), setting this property to False might be the appropriate course of action. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| LingerTime: Time in seconds to have the connection linger. LingerTime is the time, in seconds, the socket connection will linger. This value is 0 by default, which means it will use the default IP timeout. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| LocalHost:
The name of the local host through which connections are initiated or accepted.
The LocalHost setting contains the name of the local host
as obtained by the gethostname() system call, or if the
user has assigned an IP address, the value of that address.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the control initiate connections (or accept in the case of server controls) only through that interface. If the control 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 control binds.
This must be set before a connection is
attempted. It instructs the control to bind to a specific
port (or communication endpoint) in the local machine.
Setting this to 0 (default) enables the system to choose a port at random. The chosen port will be shown by LocalPort after the connection is established. LocalPort cannot be changed once a connection is made. Any attempt to set this when a connection is active will generate an error. This; setting is useful when trying to connect to services that require a trusted port in the client side. An example is the remote shell (rsh) service in UNIX systems. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MaxLineLength:
The maximum amount of data to accumulate when no EOL is found.MaxLineLength is the size of an internal buffer, which holds received data while waiting for an EOL
string.
If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset. If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset. The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MaxTransferRate: The transfer rate limit in bytes per second.This configuration setting can be used to throttle outbound TCP traffic. Set this to the number of bytes to be sent per second. By default, this is not set and there is no limit. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ProxyExceptionsList:
A semicolon separated list of hosts and IPs to bypass when using a proxy.This configuration setting optionally specifies a semicolon-separated list of hostnames or IP addresses to bypass when a proxy is in use.
When requests are made to hosts specified in this property, the proxy will not be used. For instance:
www.google.com;www.nsoftware.com |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TCPKeepAlive:
Determines whether or not the keep alive socket option is enabled.If set to True, the socket's keep-alive option is enabled and keep-alive packets will be sent periodically
to maintain the connection. Set KeepAliveTime and KeepAliveInterval to
configure the timing of the keep-alive packets.
Note: This value is not applicable in Java. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TcpNoDelay:
Whether or not to delay when sending packets.
When true, the socket will send all data that is ready to send at once. When
false, the socket will send smaller buffered packets of data at small intervals.
This is known as the Nagle algorithm.
By default, this config is set to false. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
UseIPv6:
Whether to use IPv6.When set to 0 (default), the control will use IPv4 exclusively.
When set to 1, the control will use IPv6 exclusively. To instruct the control 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SSL Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| LogSSLPackets:
Controls whether SSL packets are logged when using the internal security API.When SSLProvider is set to Internal, this setting controls whether SSL packets should be logged. By default, this setting is False, as it is only useful for debugging purposes.
When enabled, SSL packet logs are output using the SSLStatus event, which will fire each time an SSL packet is sent or received. Enabling this setting has no effect if SSLProvider is set to Platform. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 control will reuse the context if and only if the following criteria are met:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 control will check the Certificate Revocation List specified by the server certificate. If set to 1 or 2, the control will first obtain the list of CRL URLs from the server certificate's CRL distribution points extension. The control 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 control fails with an error.
When set to 0 (default) the CRL check will not be performed by the control. When set to 1, it will attempt to perform the CRL check, but will continue without an error if the server's certificate does not support CRL. When set to 2, it will perform the CRL check and will throw an error if CRL is not supported. This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLCheckOCSP:
Whether to use OCSP to check the status of the server certificate.This setting specifies whether the control will use OCSP to check the validity of the server certificate. If set to 1 or 2, the control will first obtain the OCSP URL from the server certificate's OCSP extension. The control will then locate the issuing certificate and make an HTTP request to the OCSP endpoint to check the validity of the server's certificate. If the certificate has been revoked or any other issues are found during validation the control fails with an error.
When set to 0 (default) the control will not perform an OCSP check. When set to 1, it will attempt to perform the OCSP check, but will continue without an error if the server's certificate does not support OCSP. When set to 2, it will perform the OCSP check and will throw an error if OCSP is not supported. This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLCipherStrength:
The minimum cipher strength used for bulk encryption.
This minimum cipher strength largely dependent on the security modules installed
on the system. If the cipher strength specified is not supported,
an error will be returned when connections are initiated.
Please note that this setting contains the minimum cipher strength requested from the security library. The actual cipher strength used for the connection is shown by the SSLStatus event. Use this setting with caution. Requesting a lower cipher strength than necessary could potentially cause serious security vulnerabilities in your application. When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList config setting. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLEnabledCipherSuites:
The cipher suite to be used in an SSL negotiation.The enabled cipher suites to be used in SSL negotiation.
By default, the enabled cipher suites will include all available ciphers ("*"). The special value "*" means that the control will pick all of the supported cipher suites. If SSLEnabledCipherSuites is set to any other value, only the specified cipher suites will be considered. Multiple cipher suites are separated by semicolons. Example values when SSLProvider is set to Platform:
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA;TLS_DH_ANON_WITH_AES_128_CBC_SHA");
Possible values when SSLProvider is set to Internal include:
When TLS 1.3 is negotiated (see SSLEnabledProtocols) only the following cipher suites are supported:
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:
SSLEnabledProtocols - TLS 1.3 Notes By default when TLS 1.3 is enabled the control will use the internal TLS implementation when the SSLProvider is set to Automatic for all editions. In editions which are designed to run on Windows SSLProvider can be set to Platform to use the platform implementation instead of the internal implementation. When configured in this manner, please note that the platform provider is only supported on Windows 11 / Windows Server 2022 and up. The default internal provider is available on all platforms and is not restricted to any specific OS version. If set to 1 (Platform provider) please be aware of the following notes:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 by default, but can be set to to disable the extension.
This setting is only applicable when SSLProvider is set to Internal. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLIncludeCertChain:
Whether the entire certificate chain is included in the SSLServerAuthentication event.This setting specifies whether the Encoded parameter of the SSLServerAuthentication event contains
the full certificate chain. By default this value is False and only the leaf certificate will be present
in the Encoded parameter of the SSLServerAuthentication event.
If set to True all certificates returned by the server will be present in the Encoded parameter of the SSLServerAuthentication event. This includes the leaf certificate, any intermediate certificate, and the root certificate. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLKeyLogFile:
The location of a file where per-session secrets are written for debugging purposes.This setting optionally specifies the full path to a file on disk where per-session secrets are stored for debugging purposes.
When set, the control will save the session secrets in the same format as the SSLKEYLOGFILE environment variable functionality used by most major browsers and tools such as Chrome, Firefox, and cURL. This file can then be used in tools such as Wireshark to decrypt TLS traffice for debugging purposes. When writing to this file the control will only append, it will not overwrite previous values. Note: This setting is only applicable when SSLProvider is set to Internal. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedCipher:
Returns the negotiated ciphersuite.Returns the ciphersuite negotiated during the SSL handshake.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedCipherStrength:
Returns the negotiated ciphersuite strength.Returns the strength of the ciphersuite negotiated during the SSL handshake.
Note: For server components (e.g.TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedCipherSuite:
Returns the negotiated ciphersuite.Returns the ciphersuite negotiated during the SSL handshake represented as a single string.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedKeyExchange:
Returns the negotiated key exchange algorithm.Returns the key exchange algorithm negotiated during the SSL handshake.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedKeyExchangeStrength:
Returns the negotiated key exchange algorithm strength.Returns the strenghth of the key exchange algorithm negotiated during the SSL handshake.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLNegotiatedVersion:
Returns the negotiated protocol version.Returns the protocol version negotiated during the SSL handshake.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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:
This functionality is currently not available when the provider is OpenSSL. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SSLServerCACerts:
A newline separated list of CA certificate to use during SSL server certificate validation.This setting optionally specifies one or more CA certificates to be used when verifying the server certificate. When verifying the server's certificate the certificates trusted by the system will be used as part of the verification process. If the server's CA certificates are not installed to the trusted system store, they may be specified here so they are included when performing the verification process. This setting should only be set if the server's CA certificates are not already trusted on the system and cannot be installed to the trusted system store.
The value of this setting is a newline (CrLf) separated list of certificates. For instance: -----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE----- |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TLS12SignatureAlgorithms:
Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal.This setting specifies the allowed server certificate signature algorithms when SSLProvider is set to Internal and SSLEnabledProtocols is set to allow TLS 1.2.
When specified the control 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 control fails with an error. The format of this value is a comma separated list of hash-signature combinations. For instance:
In order to not restrict the server's certificate signature algorithm, specify an empty string as the value for this setting, which will cause the signature_algorithms TLS 1.2 extension to not be sent. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| TLS12SupportedGroups:
The supported groups for ECC.This setting specifies a comma separated list of named groups used in TLS 1.2 for ECC.
The default value is ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1. When using TLS 1.2 and SSLProvider is set to Internal, the values refer to the supported groups for ECC. The following values are supported:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
TLS13SignatureAlgorithms:
The allowed certificate signature algorithms.This setting holds a comma separated list of allowed signature algorithms. Possible values are:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Socket Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| AbsoluteTimeout:
Determines whether timeouts are inactivity timeouts or absolute timeouts.If AbsoluteTimeout is set to True, any method which does not complete within Timeout seconds
will be aborted. By default, AbsoluteTimeout is False, and the timeout is an inactivity timeout.
Note: This option is not valid for UDP ports. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| FirewallData: Used to send extra data to the firewall.When the firewall is a tunneling proxy, use this property to send custom (additional) headers to the firewall (e.g. headers for custom authentication schemes). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| InBufferSize:
The size in bytes of the incoming queue of the socket.
This is the size of an internal queue in the TCP/IP stack.
You can increase or decrease its size depending on the amount
of data that you will be receiving. Increasing the value of the
InBufferSize setting can provide significant improvements in
performance in some cases.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the control 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 control is activated the OutBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Base Config Settings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CodePage:
The system code page used for Unicode to Multibyte translations.The default code page is Unicode UTF-8 (65001).
The following is a list of valid code page identifiers:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| MaskSensitive:
Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to to mask sensitive data. The default is .
This setting only works on these controls: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UseInternalSecurityAPI:
Tells the control whether or not to use the system security libraries or an internal implementation.
When set to , the control will use the system security libraries by default to perform cryptographic functions where applicable.
Setting this setting to tells the control to use the internal implementation instead of using the system security libraries. This setting is set to by default on all platforms. |
Trappable Errors (Retail Control)
Retail Errors
| 20160 Invalid form variable index (out of range). | |
| 20502 Data field invalid length. | |
| 20503 Data field invalid format. | |
| 20504 Data field out of range. | |
| 20505 Luhn digit check failed. | |
| 20506 Card date invalid. | |
| 20507 Card expired. | |
| 20508 Card type unknown. | |
| 20511 No gateway specified. | |
| 20512 Invalid data entered. | |
| 20513 Truncated response. | |
| 20514 Invalid response. | |
| 20515 A Special Field is required for this transaction type. | |
| 20536 Signature verification failed. | |
| 20543 Error computing MD5 hash for Authorize.Net |
CardValidator Errors
| 20505 Luhn digit check failed. | |
| 20506 Card date invalid. | |
| 20507 Card expired. | |
| 20704 Invalid CardNumber format (contains letters or unknown characters). | |
| 20705 Could not determine the Credit Card type. | |
| 20706 Error parsing TrackData. Format cannot be determined. |
The control may also return one of the following error codes, which are inherited from other controls.
HTTP Errors
| 20119 Firewall Error. Error description contains detailed message. | |
| 20144 Busy executing current method. | |
| 20152 HTTP protocol error. The error message has the server response. | |
| 20153 No server specified in URL | |
| 20154 Specified URLScheme is invalid. | |
| 20156 Range operation is not supported by server. | |
| 20157 Invalid cookie index (out of range). | |
| 20302 Interrupted. | |
| 20303 Can't open AttachedFile. |
The control may also return one of the following error codes, which are inherited from other controls.
TCPClient Errors
| 20101 You cannot change the RemotePort at this time. A connection is in progress. | |
| 20102 You cannot change the RemoteHost (Server) at this time. A connection is in progress. | |
| 20103 The RemoteHost address is invalid (0.0.0.0). | |
| 20105 Already connected. If you want to reconnect, close the current connection first. | |
| 20107 You cannot change the LocalPort at this time. A connection is in progress. | |
| 20108 You cannot change the LocalHost at this time. A connection is in progress. | |
| 20113 You cannot change MaxLineLength at this time. A connection is in progress. | |
| 20117 RemotePort cannot be zero. Please specify a valid service port number. | |
| 20118 You cannot change the UseConnection option while the control is active. | |
| 20136 Operation would block. | |
| 20202 Timeout. | |
| 20212 Action impossible in control's present state. | |
| 20213 Action impossible while not connected. | |
| 20214 Action impossible while listening. | |
| 20302 Timeout. | |
| 20303 Could not open file. | |
| 20435 Unable to convert string to selected CodePage. | |
| 21106 Already connecting. If you want to reconnect, close the current connection first. | |
| 21118 You need to connect first. | |
| 21120 You cannot change the LocalHost at this time. A connection is in progress. | |
| 21121 Connection dropped by remote host. |
SSL Errors
| 20271 Cannot load specified security library. | |
| 20272 Cannot open certificate store. | |
| 20273 Cannot find specified certificate. | |
| 20274 Cannot acquire security credentials. | |
| 20275 Cannot find certificate chain. | |
| 20276 Cannot verify certificate chain. | |
| 20277 Error during handshake. | |
| 20281 Error verifying certificate. | |
| 20282 Could not find client certificate. | |
| 20283 Could not find server certificate. | |
| 20284 Error encrypting data. | |
| 20285 Error decrypting data. |
TCP/IP Errors
| 25005 [10004] Interrupted system call. | |
| 25010 [10009] Bad file number. | |
| 25014 [10013] Access denied. | |
| 25015 [10014] Bad address. | |
| 25023 [10022] Invalid argument. | |
| 25025 [10024] Too many open files. | |
| 25036 [10035] Operation would block. | |
| 25037 [10036] Operation now in progress. | |
| 25038 [10037] Operation already in progress. | |
| 25039 [10038] Socket operation on non-socket. | |
| 25040 [10039] Destination address required. | |
| 25041 [10040] Message too long. | |
| 25042 [10041] Protocol wrong type for socket. | |
| 25043 [10042] Bad protocol option. | |
| 25044 [10043] Protocol not supported. | |
| 25045 [10044] Socket type not supported. | |
| 25046 [10045] Operation not supported on socket. | |
| 25047 [10046] Protocol family not supported. | |
| 25048 [10047] Address family not supported by protocol family. | |
| 25049 [10048] Address already in use. | |
| 25050 [10049] Can't assign requested address. | |
| 25051 [10050] Network is down. | |
| 25052 [10051] Network is unreachable. | |
| 25053 [10052] Net dropped connection or reset. | |
| 25054 [10053] Software caused connection abort. | |
| 25055 [10054] Connection reset by peer. | |
| 25056 [10055] No buffer space available. | |
| 25057 [10056] Socket is already connected. | |
| 25058 [10057] Socket is not connected. | |
| 25059 [10058] Can't send after socket shutdown. | |
| 25060 [10059] Too many references, can't splice. | |
| 25061 [10060] Connection timed out. | |
| 25062 [10061] Connection refused. | |
| 25063 [10062] Too many levels of symbolic links. | |
| 25064 [10063] File name too long. | |
| 25065 [10064] Host is down. | |
| 25066 [10065] No route to host. | |
| 25067 [10066] Directory not empty | |
| 25068 [10067] Too many processes. | |
| 25069 [10068] Too many users. | |
| 25070 [10069] Disc Quota Exceeded. | |
| 25071 [10070] Stale NFS file handle. | |
| 25072 [10071] Too many levels of remote in path. | |
| 25092 [10091] Network subsystem is unavailable. | |
| 25093 [10092] WINSOCK DLL Version out of range. | |
| 25094 [10093] Winsock not loaded yet. | |
| 26002 [11001] Host not found. | |
| 26003 [11002] Non-authoritative 'Host not found' (try again or check DNS setup). | |
| 26004 [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP. | |
| 26005 [11004] Valid name, no data record (check DNS setup). |