CBSubs Quickpay - Mobilepay subscription

Hi

Would it be possible to integrate this payment method in the Quickpay gateway for CBSubs: learn.quickpay.net/helpdesk/en/articles/payment-methods/mobilepay-subscriptions/

It would make the solution even more attractive in Denmark. If you could make a quote for the work it would be possible to make a donation for this development.

There's already plans to add support for specifying custom payment methods list as per the below feature ticket.

forge.joomlapolis.com/issues/8497

I'm planning to just change it to a textbox so you can specify whatever payment methods Quickpay supports. I've went ahead and implemented this and is pending review, merge, and then can be released.

But I do not believe that, that is quite enough. Quickpay is saying that it needs some other logic, as the recurring payment needs a withdrawel date set in the paramtere: auto_capture_at which must be at least 24 hours in the future. If you can skim the documentation, and make a quote on it - the expense for developing could be covered.

We'd only consider supporting that once it is out of Beta. I don't want to be a position of exhausting valuable development time on a payment method that may completely change. Once it has reached a stable state will take a look at it for a future release.

It's not just a matter of cost. There's only so many hours in a day and I've other tasks with higher priority right now. I'm in the middle of working on CB Activity 6.0.0 so I can only afford time for minor implementations on other projects right now.

Have made a feature ticket for this in the meantime.

forge.joomlapolis.com/issues/8832

I have just talked to Quickpay and they told me that the mobilepay-subscription is no longer in beta, and this is now removed from the description.
I have also send you a PM

Ok, have updated the feature ticket to note it's not in beta anymore. I however still do not have the time to implement this at the moment. So it will likely be at least 1-2 months before I do have time. This looks like a completely different implementation behavior compared to their other recurring usages so it's likely to be complicated since I basically have to maintain 2 different recurring behaviors.