For Citibank Meerbusch customers, you can now use the Address Verification Service for the Visa and MasterCard card types for United Kingdom addresses.
For Citibank Meerbusch customers, you can now use card verification numbers for the Visa and MasterCard card types.
For Citibank Meerbusch customers, you can now submit the "moto" and "recur" flags for the request-level field e_commerce_indicator.
For Citibank Meerbusch customers, you can now receive the value "3" for the reply field auth_cv_result, indicating that the processor did not return a card verification result code.
For Citibank Meerbusch, Paymentech New Hampshire, and Streamline customers, you can use Verified by Visa with the ics_auth application after authenticating a Verified by Visa accountholder. For Paymentech customers, you must send cavv and xid data in 28-character base 64 encoding.
For FDMS Nashville, FDMS South, Paymentech, and Vital customers, you can now now submit the "vbv_attempted" flag for the request-level field e_commerce_indicator. For U.S. processors, CyberSource will convert the "vbv_attempted" flag to an "internet" flag, since those processors do not yet support vbv_attempted transactions.
For Citibank Meerbusch and Streamline customers, cavv and xid data for Verified by Visa transactions is not sent to Visa, since Visa Europe does not yet support these data fields.
Citibank Meerbusch supports the Visa and MasterCard card types.
For Citibank Meerbusch customers, you will now receive the reply flag ESYSTEM for some system errors instead of DINVALIDDATA.
The default message for the auth_rmsg, auth_reversal_rmsg, bill_rmsg, credit_rmsg, ecp_debit_rmsg, and ecp_credit_rmsg reply fields is now "Request was processed successfully".
The reply fields score_hotlist_info and score_internet_info can now contain additional Advanced Fraud Screen information codes. See the Advanced Fraud Screen Implementation Guide for a complete list of information codes.
You can now send email addresses that contain an underscore at the end of the user name.
The ics_risk_update application now accepts the request-level fields cc_bin, containing the first six digits of the customer's credit card number, and domain, containing the customer's email domain.
The transaction detail page now includes the Advanced Fraud Screen information codes for ics_score transactions.