These release notes apply to the production server.
CyberSource has created two hedge settings for the SCMP API of the Advanced Fraud Screen. Both hedge settings function similarly. In assigning the level of risk, the hedge settings alter the weight of the multiple tests that CyberSource performs on phone numbers and on the text content of customers' orders. To use these new hedges, use the offer-line fields score_phone_hedge and score_nonsensical_hedge. The fields are described in the Advanced Fraud Screen Implementation Guide, which is available on the Support Center.
The Payer Authentication Validate Authentication service now returns the XID for MasterCard SecureCode transactions. If you receive the XID during MasterCard SecureCode payer authentication, you should provide it with the credit card authorization. CyberSource now supports acceptance of the XID as part of the request for MasterCard SecureCode authorization, but currently CyberSource forwards the XID only if the processor is Barclays. For more information, see the Payer Authentication Implementation Guide and the Credit Card Services Implementation Guide, which are both available on the Support Center.
With this release, CyberSource supports the processing of airline settlement data by merchants in the airline industry who use Vital as their processor.
This release fixes an issue that affected Level III transactions with the Vital processor. Previously, we were automatically setting the local tax indicator (otherTax_localTaxIndicator for the Simple Order API, or local_tax_indicator for the SCMP API) based on the value you provided for the local tax (otherTax_localTax for the Simple Order API, or local_tax for the SCMP API). Now, we use the value you provide for the local tax indicator no matter what value you provide for the local tax. If you do not provide a value for the local tax indicator, we set the indicator to 1 if you set the local tax > 0, and to 0 if you set the local tax = 0 or do not provide a local tax.
With this release, CyberSource supports a new implementation for PIN-less debit card transactions with the Paymentech processor. The previous implementation used the ICS Credit Card Services to process the cards, while the new implementation uses a new ICS service specially designed for debit cards. The new implementation also includes a BIN validation service that determines whether a card can be used for PIN-less debit transactions. For more information, see the PIN-less Debit Card Services Implementation Guide, which is available on the Support Center.