Custom payment gateway

krileon wrote:

Your requested gateway is already on the list. We're keeping track of all user requested gateways at this time. Please keep in mind this does not guarantee implementation nor can I provide for you a timeframe.

ok great!

can You answer to my earlier question?

Do You know approximately when CBSubs 1.1 will be relased?

Why I'm asking?
If the relased date is in let's say two months I can buy CBSubs and use Offline method by this time and then implement custom using api.

Honestly, no idea. Hopefully soon, but issues arise with each test phase that need to be addressed accordingly. We've also critical features that need implementation and testing before release. We're currently in strong testing right now so hopefully soon, but I can't give you a definite time frame.

Hi!

I can't find information/list of all payement gateways implemented in brand new CBSubs 1.1.

Can You give me a hint?

jarpens wrote:

Hi!

I can't find information/list of all payement gateways implemented in brand new CBSubs 1.1.

Can You give me a hint?

CBSubs 1.1 announcement has forum discussion here:

www.joomlapolis.com/component/option,com_joomlaboard/Itemid,38/func,view/id,147124/catid,92/

Beat has provided a full changelog.

Implemented gateways are:

+ Paypal
+ Authorize.net (with AVS)
+ 2CheckOut
+ Ogone
+ PostFinance
+ Offline
+ Dummy

We will be working with 3P developers to get more gateways out in the future.

nant wrote: jarpens wrote:

Implemented gateways are:
+ Paypal
+ Authorize.net (with AVS)
+ 2CheckOut
+ Ogone
+ PostFinance
+ Offline
+ Dummy

I'm in France and some bank uses Atos or Paybox ... witch are not (yet) implemented.
Am I right ? Is it in the "todo list" ?
Thanks
Matt

Am I right ?

Yes, the suggested gateways are not implemented.

Is it in the "todo list" ?

We've noted all user requested gateways in a feature ticket, but please note this does not guarantee implementation. It is simply for our records so we can keep track of all requested gateways and could be considered for future implementation. For obvious reasons not all gateways can be implemented as they must pass our standards expectations as well as API needs. Implementing and testing a gateway is a time consuming and pain staking process which can be worsened if a provider does not wish to work closely with us on such an implemented. This means we're limited as to what we implement.