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.
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. 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. 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. 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. > > 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. > > Does this makes sense or have I missed somethings ? >
