|
Monday 12 February 2007 8:53:32 am
Well ... That's reasonable enough. I would borrow ideas from the redirect gateway's implementation. Adapt your gateway to use those ideas at the point where you return from your card type form submission, before the workflow event ends ... for starters. It's going to take an experienced eZ / PHP developer to implement your own unique api's required php code into the workflow event to support (in effect) both feature sets of both types of payment gateway classes. There really is no big secret in this area of eZ publish, you write a workflow event of type payment gateway, there are several examples in eZ publish itself and in other payment gateway extensions of how you can implement the code eZ publish needs to support these base features within eZ publish, the rest of the code needed is for your own api, you write to support your own payment gateway's api.
A redirect to a url is not much different from background curl request to a url...
This is an area for development not talk, no?
Cheers,
//kracker <i>Sole - Selling Live Water - Respect Pt 3</i>
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|
