What Should Be Done in OCC to Handle Cybersource's New Reply Field?
(Doc ID 2711221.1)
Last updated on SEPTEMBER 22, 2020
Applies to:Oracle Commerce Cloud Service - Version N/A and later
Information in this document applies to any platform.
CyberSource may add additional reply field. For instance, following is a notification from CyberSource about adding a new reply field, payment_account_reference:
CyberSource will add the following new reply field to Secure Acceptance in both the Hosted Checkout and API integrations. Reply field name: payment_account_reference The change is expected to be published in late August. To avoid any impact, please proceed as follows: - Parse the reply data according to the names of the fields instead of their order in the reply. For more information on parsing reply fields, see the Secure Acceptance Implementation Guides documentation for your scripting language. - The signature that you generate must be the same value that is included in the signature response field. - Your error handler should use the decision field to determine the transaction result if it receives a reason code that it does not recognize. - If your implementation expects static response fields, you must update this to dynamically build the signature string as specified in the Secure Acceptance Integration Guide and the sample Code. This will prevent any impact both with this additional field as well as any future enhancements that Cybersource may offer. The Secure Acceptance Integration Guide and the sample Code documentation can be accessed at the link below: https://www.cybersource.com/en-us/support/technical-documentation/apis-and-integration.html#SecureAcceptance
Please contact your Customer Support representatives with any questions you may have about this change. What should we do in OCC in corresponding to the newly added CyberSource reply field?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document