In order to test default functionality when a credit card payment on an
order is declined, we changed the settings in Product Store, Payments
tab for Payment Auth service to alwaysDeclineCCProcessor.
Then we tested by creating an order and submitting a CC# as a payment
method. Of course the CC was declined, and the Order status was set to
ORDER_REJECTED, OrderITemStatus was also set to rejected. Since there is
no valid status change allowed from ORDER_REJECTED to anything else,
there appears to be no way to take the existing order, assign a new
paymentMethodId and reattempt authorization with a different credit
card. Is this true?
To remedy this, we could add an entry to StatusValidChange that allows a
movement from ORDER_REJECTED back to ORDER_APPROVED, modify secas.xml
and theoretically that should allow the user to select an alternate
payment method from the Order Detail screen and reprocess payment.
Is this the best way to handle this? The requirement is to allow an
order taker to switch to a different credit card if the first one is
declined - without having to completely re-enter the order.
If anyone has encountered this before, or has a suggestion about an
approach, that would be most welcome. Thanks
--
Dave Tenerowicz
[EMAIL PROTECTED]
Office: 303.493.6727
Mobile 303.906.6116
Fax 303.814.8331
Visit us at http://www.salmonllc.com
For ERP Information:
http://www.salmonllc.com/Jsp/vanity/ERP_CRM.jsp?nav=2&NavBarId=ERP_CRMServices
