![]() |
| > Home > Documentation > Latest documentation > Local config directives > CreditCardAuto |
|
CreditCardAutoEnables the automatic encryption and saving of credit card information. Synopsis
This is a Yes or No directive. The default is No. ScopeThis directive is only available for use in the local (catalog.cfg) configuration file. It will not affect any other website in any way. This directive will not work in the global (interchange.cfg) configuration file. DescriptionThis directive enables the automatic encryption and saving of credit card information. In order for this to work properly, the EncryptProgram directive must be set to properly encode the data. This option uses the following standard fields on Interchange order processing forms: mv_credit_card_numberThe actual credit card number, which will be wiped from memory after checking to see if it looks valid. This variable will never be saved, or otherwise carried forward, in the user's session. mv_credit_card_exp_allThe expiration date, as a text field in the form MM/YY (will take a four-digit year as well). If it is not present, the "mv_credit_card_exp_month" and "mv_credit_card_exp_year" CGI values are examined. This value is set by Interchange when the card validation returns, if not previously set. mv_credit_card_exp_monthThe expiration date month, used if the "mv_credit_card_exp_all" CGI values is not present. This value is set by Interchange when the card validation returns, if not previously set. mv_credit_card_exp_yearThe expiration date year, used if the "mv_credit_card_exp_all" CGI value is not present. It is set by Interchange when the card validation returns, if not previously set. mv_credit_card_cvv2The credit card's CVV2 (security code) value, usually printed on the signature strip on the back of the card. This variable will never be saved, or otherwise carried forward, in the user's session. mv_credit_card_errorSet by Interchange to indicate the error if the card does not validate properly. The error message is not too enlightening if validation is the problem. mv_credit_card_forceSet this CGI value to 1 to force Interchange to encrypt the card despite its idea of validity. Will still set the flag for validity to 0 if the number/date does not validate. Interchange still won't accept badly formatted expiration dates. mv_credit_card_separateSet this value to 1 to cause Interchange encrypt only the card number, and not accompany it with the expiration date and card type. mv_credit_card_infoSet by Interchange to the encrypted card information if the card validates properly. If GnuPG or PGP is used in ASCII armour mode, this field can be placed on the order report and embedded in the order email, complete with markers. This allows a secure order to be read for content, without exposing the credit card number to risk. mv_credit_card_validSet true by Interchange if the the card validates properly. Set false otherwise.
|
| Home | Legal nonsense | Privacy policy | Contact us |