CardValidator ConfigurationThe component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
CardValidator Configuration Settings
|NameOnCard: The name encoded in the track data on the credit card.If the TrackData you're parsing is Track1 data, it contains the customer's name, and should be identical to the name printed on the face of the card. Track2 data does not contain this name. This field will be filled after a call to ValidateCard.|
Base Configuration Settings
Tells the component whether or not a message loop is available for processing events.In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.
In some non-GUI applications an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GuiAvailable to false will ensure that the component does not attempt to process external events.
|UseBackgroundThread: Whether threads created by the component are background threads.If set to True, when the component creates a thread the thread's IsBackground property will be explicitly set to True. By default this setting is False.|
Tells the component whether or not to use the system security libraries or an internal implementation.
By default the component will use the system security libraries to perform cryptographic functions.
When set to False calls to unmanaged code will be made. In certain environments this is not desirable.
To use a completely managed security implementation set this setting to True.
Setting this to True tells the component to use the internal implementation
instead of using the system's security API.
Note: This setting is static. The value set is applicable to all components used in the application.
When this value is set the product's system DLL is no longer required as a reference, as all unmanaged code is stored in that file.