Developer forum

Hi Marco,

IRemoteCapture is the interface you need to implement if you want your CheckoutHandler to support capture (transferring the money from the customer's account to the shop's account). If the CheckoutHandler supports Capture then eCom administration can allow editors to perform that action from within Dynamicweb itself, rather than going to the Payment Gateway administration.

From what I understand, you need some way of polling the gateway to see whether the payment has succeeded yet. For example, customer is redirected to the gateway and makes the payment. The gateway then goes away for some unknown amount of time, and then marks the payment as complete. Is that correct?

Normally, communication with the Payment Gateway goes like this:

1. Dynamicweb redirects the customer to the gateway
2. Customer enters their information at the gateway and clicks 'Ok'
3. Gateway makes a callback to Dynamicweb with information whether the payment succeeded or not
4. Customer is redirected back to Dynamicweb after successfully completing the payment

- Jeppe

Ah, I think the Remote Capture is not what I need after all.

That is correct (about the polling). All the gateway does is supply the customer with some references that he can then use to pay at a later time (through cash machines or web banking). There is the callback option as well but it depends on settings the customer selects on their registration account (that side of things is sorted.)

The other option, that I am currently trying to resolve, is accessing a web service to check whether a payment has been made for the references generated. So we need to check periodically, since we don´t know when the payment will be made (or at all).

From what you said I guess that the capture is always initiated through the back office by someone. Is that correct?

Marco