Re: payment deferred/release

Thu, 15 Oct 2009 01:06:01 -0700 

Inline

Regards
Scott

On 15/10/2009, at 8:31 PM, Abdullah Shaikh wrote:


Hi Scott,

Comments inline
On Thu, Oct 15, 2009 at 1:30 AM, Scott Gray <[email protected] >wrote: 


Comments inline

Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 14/10/2009, at 6:08 AM, Abdullah Shaikh wrote:

Also, my understanding is that authorisation/capture is same as
deferred/release with the exception that authorisation/capture doesn't 
validate the cvv & other validations but deferred/release does.
I have no idea what deferred/release is but an authorization and capture 
does validate all credit card information at authorization time.  My
understanding of a release is that it releases an authorization i.e. cancels 
a payment before it has been captured.
Deferred/Release is same as Authorization/Capture. My only confusion was regarding the sending of cancel request for an authorization to the payment 
gateway.
Okay, yes you use the release mechanism, I don't have the exact type name on hand
By this what I meant was that authorisation/capture does validate cvv & other validations but that it does in the second step i.e. in capture and not at the time of placing the order, that means if the capture service fails, which will be invoked by the merchant, then the merchant will have 
to
inform the customer and ask him to place the order again.



No, generally doing a capture requires only the token provided by the
gateway at authorization time.
Yes, I agree, it just requires a token to capture an authorized payment, but what I meant was if at the time of authorization if the customer provides an invalid cvv no. does the payment gateway validate it at that time itself or 
just register the authorization and does the validation at the time of
capture ?. if it does so at the time of capture then the order has to be 
placed again.
If an invalid cvv were provided then authorization would fail. The authorization validates all payment information, checks that funds are available and reserves them. 


But in deferred/release, the validations takes place at the time of
placing
the order, that means if the customer enters the cvv code wrong then the customer stands the chance to reenter the cvv code, and there wont be any validations check when the merchant goes for releasing the payment because 
it has already been validated.



This is what auth/capture does but generally OFBiz doesn't provide
functionality out of the box for a user to correct their credit card
details.


Also the other difference between these 2 types is that in
deferred/release
the payment should ideally be released within 6 days as per credit card 
schemes, this restriction does not applies to authorise/capture type
service.
The amount of time you can hold an authorization for varies depending on 
the credit card type and the gateway provider.
There may be other differences which I may not be aware off, but they its 
depends on your custom requirements.


On Tue, Oct 13, 2009 at 9:36 PM, Abdullah Shaikh <
[email protected]> wrote:

I am implementing a payment gateway, in which instead of

authorisation/capture i.e using interfaces ccAuthInterface &
ccCaptureInterface, I will be using deferred/release transaction types, 
to
implement this I can do it using the before mentioned interfaces, but 
then I
saw there is a interface for release i.e. paymentReleaseInterface but no interface definition for deferred, I guess there should be a interface 
defined for deferred type in services_paymentmethod.xml.
deferred just sounds like an authorization. I would double check that release does what you think it does because as I mentioned above I'm used to 
it meaning to cancel an authorization.
Yes can you please confirm if release means to cancel an authorization ? 

Correct






Also, my understanding is that authorisation/capture is same as
deferred/release with the exception that authorisation/capture doesn't 
validate the cvv & other validations but deferred/release does.
If the above statement is correct then, in order manager under "Payment Information", currently we display "Capture" button when the payment is authorised, but if we implement the above, then we need to check if the payment was using the authorisation then display capture or if using 
deferred then display Release button.




It all just sounds like the same thing but using different words.




Does this makes sense or have I missed somethings ?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to