Those sound like some important holes in current functionality, and yes I think
it'd be great to have both of those in the project.
-David
Jacopo Cappellato wrote:
Hi all,
I'm in the process of testing the following scenario (a customer
reported some weird things, but I'm still not sure by what they are
caused):
1) order with credit card payment preference
2) the payment *authorization* is succesful (the order is created and
approved)
3) when the order is shipped, the payment capture is declined by the
payment processor
In order to test it I've created a new service named
"alwaysDeclineCCCapture" (can I commit it into trunk?).
I've noticed that the declined response is never stored in the
PaymentGatewayResponse entity by the
PaymentGatewayServices.processCaptureResult(...) method; the attached
patch will fix this: can I commit this one?
Going on with my tests.
Jacopo
