Invalid Security Code Format Does Not Place A Credit Card Order On Hold
(Doc ID 1533283.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Payments - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
When entering an invalid security code (ie. invalid format) on a credit card order, the order is not placed on a credit card authorization hold.
A credit card order is placed with a nominal amount.
However, an invalid card 'security code' has been specified for the order. For example, security code-like 'AAAA'.
The order is not placed on a hold. Instead, it is authorized.
Expecting a hold to be placed on the order because an INVALID card security code is specified.
The issue can be reproduced at will with the following steps:
1. Order Management > Sales Order form
2. Enter sales order header with a valid credit card number, card holder, Expiry Date, but an invalid security code format such as AAA, then the value should be numeric.
3. Payment is authorized
4. Order is booked and not placed on hold
The issue has the following business impact:
Due to this issue, users cannot get a message that the security code is invalid and the order does not go on hold.
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