Amendmended Order paymentGroupId Does Not Match ID Used in paymentGroups Array
(Doc ID 2545358.1)
Last updated on JANUARY 13, 2020
Applies to:Oracle Commerce Cloud Service - Version N/A and later
Information in this document applies to any platform.
When amending an order after it has been placed, in situations where adding additional payment information is required for instance, customers are noticing that in these follow-up payments the second/new paymentGroupId does not have the same number-key as the second/new 'authorizationStatus' both representing the same follow-up payment.
This can cause reconciliation issues later, since the payment group ID and it's authorization object do not match up.
To illustrate review the following paymentGroupID and authorization status for an intial payment (not the second/new one):
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