Last updated on SEPTEMBER 21, 2016
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.2 version, Payment Electronic
We are currently integrating the FSCM9.2 with CuberSource using the Secure acceptance integration. In case of an error response. Peoplesoft captures the reason code and uses the corresponding delivered message catalogue entry to display the appropriate error message on the screen. There are few reason codes in CyberSource which are not mapped in the message catalogue entries in PeopleSoft. Peoplesoft screen returns blank error messages in this case.
The delivered message set number for Peoplesoft 12600. I have mentioned the below the CyberSource reason codes for which we require PeoplSoft error messages
223 - The customer’s payment or credit has been declined because there is an existing duplicate check, the original transaction was not approved, or a valid authorization could not be located.
235 -The processor declined the request due to the requested amount exceeding the authorized amount.
241 - The request ID is invalid for the follow-on request.
246 - The debit or credit is not voidable because the debit or credit information has already been submitted to your processor. Or, you requested a void for a type of transaction that cannot be voided.
247 - You requested a credit for a debit that was previously voided.
388 - The routing number did not pass verification as described in ACH Verification.
All reason codes in CyberSource should be mapped in the message catalogue entries in PeopleSoft.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms