Forum OpenACS Development: eCommerce Payment Gateways

Collapse
Posted by Gregor Obernosterer on
Does anybody know whether there is a non-Credit Card fulfillment gateway for the eCommerce package. Our customer is not really keen on storing and processing Credit Card information. Any hints?

/Gregor

Collapse
Posted by Bart Teeuwisse on
Gregor,

the eCommerce package is designed around credit cards. Credit cards are the most common payment method for on-line purchases. The Payment Service Contract allows for different credit card processing services but is ill suited for other payment methods like eChecks or PayPal.

Which payment method will your client be using?

/Bart

Collapse
Posted by Gregor Obernosterer on
it is done "offline". The customer is allowed to enter his credit card number, but the finance department checks offline the credibility and only proceeds with the order if the card is valid. Besides the credit card payment method the customer should be able to pay using a payment form. Only after the money is in the vendor's account the order is processed.

As you see this is not a fully automatic fulfillment process, but the client won't change the process at present as the volumes are considerably low.

Thanxs for the given explanation.

/Gregor

Collapse
Posted by Bart Teeuwisse on
Gregor,

this sounds like a good fit for a custom implementation of the payment service contract. The custom payment gateway would place the requests for credit card authorization in a queue. The gateway returns 'failure-retry' so that the eCommerce package will accept the order and silently retry to authorize the card at a later time.

There is a parameter in the eCommerce package to specify how long the eCommerce should be retrying for. The default is 8 hours but you could extend that to 48 hours to give the finance department more time to perform the real check. Upon the first retry by the eCommerce package after the real check has been performed the gateway would return 'success' or 'failure'.

As the order is shipped the eCommerce package contacts the gateway to charge the authorized card. Again the gateway places the request in a queue for the finance department and returns 'failure-retry' and the request is handled in the same manner as the authorize request.

There is no need to change the logic in the eCommerce package. All customization is handled by the payment gateway.

/Bart

Collapse
Posted by Janine Ohmer on
Another possibility is to use the Sample Gateway.  It collects the credit card information but doesn't actually do any authorizing; it just returns 'success' for everything.

This would lead to all the orders in the eCommerce system looking like the card has been charged when it has not been, but if your client is going to process the cards offline then they are going to have to have some procedure to cross-reference the cleared payments with orders anyway.  Orders which prove to have had invalid credit cards can be voided.