Forum OpenACS Q&A: Re: Payment Service Contract

Collapse
6: Re: Payment Service Contract (response to 5)
Posted by Richard Hamilton on 06/10/03 10:00 AM
Brad,

I do plan to implement it as a module, so I am sure that I will need to take you up on your offer of answering some questions as I progress.

Bart,

I will look through the two c libraries (SecPay and CyberSource) and will propose some additions to the payment gateway service contract. Perhaps then, once that has survived scrutiny I can set about writing an implementation.

Am I better to use the Authorize.net Gateway as a guide or stick to the Payflow one?

Richard
Collapse
7: Re: Payment Service Contract (response to 6)
Posted by Bart Teeuwisse on 06/10/03 02:37 PM
Richard,

use both modules as a guide. Authorize.net Gateway is better documented where as Payflow uses a C library to connect to the credit card processor. The modules implement the same service contract and thus have much in common.

/Bart