You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacopo Cappellato <ti...@sastau.it> on 2007/07/01 12:03:50 UTC

Testing a declined capture request

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

Re: Testing a declined capture request

Posted by Jacopo Cappellato <ti...@sastau.it>.
David,

I've committed my patch (a slightly different version) in rev. 552432

Thanks,

Jacopo

  David E Jones wrote:
> 
> 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
>>

Re: Testing a declined capture request

Posted by David E Jones <jo...@hotwaxmedia.com>.
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
>