If you are using Payer Authentication with the SCMP API, in certain situations you now might receive an additional reply field for the ics_pa_validate service. The field is pa_validate_eci_raw and contains the raw Electronic Commerce Indicator data from the Verified by Visa or MasterCard SecureCode system. You may or may not receive this field for a given transaction.
If you receive a pa_validate_eci_raw value, when you call the ics_auth service to authorize the credit card, send the value in a new ics_auth request field called eci_raw. Some processors require that you send this value in the ics_auth request if you received it during Payer Authentication; contact your processor to determine their requirements.
For information about the Payer Authentication services, see the Payer Authentication Implementation Guide. For information about credit card authorization, see the Credit Card Services Implementation Guide. Both guides are available on the Support Center in the Services Documentation area.
CyberSource now supports MasterCard SecureCode using the Streamline payment processor.
Contact both Streamline and CyberSource if you want to sign up to use MasterCard SecureCode.
For the Global Payment Service, two API fields were removed and are no longer used. In addition, two other API fields that had been required are now optional. All four of the fields are used for bank transfer refunds and direct debits.
For the Web Services APIs, the two fields that were removed are bankInfo_name and bankInfo_address.
For the Web Services APIs, the two fields that are now optional are bankInfo_city and fundTransfer_accountName.
For the SCMP API, the two fields that were removed are bank_name and bank_address.
For the SCMP API, the two fields that are now optional are bank_city and bank_account_name.
For information about bank transfer refunds and direct debits, see the Global Payment Service Developer's Guide, available on the Support Center in the Services Documentation area.