Flow of payment gateway

I am trying to update a payment gateway so that it can also accept recurring payments, but I am a bit stuck in understandig the flow of the gateway plugin. Could anyone explain how the logic is? Maybe by telling when and from where the functions in the gateway file is called eg: getSinglePaymentRequstParams, getSubscriptionRequstParams, handleReturn, handleCancel, handleNotification

It seems that a single payment has the flow
getSinglePaymentRequstParams
getSubscriptionRequstParams
handleNotification
handleNotification
handleReturn

I do not understand why the getSubscriptionRequstParams is called when it is a single payment ?

> "I am trying to update a payment gateway"

Can you please be more specific, so that we may help you ?

1. which Payment Gateway are you updating (they have very different internal structures)
2. what exactly are you trying to achieve ? (this may help us tell you if you are looking at the right one)

(the Help us Help You article in "Support" menu has other very useful hints to help better us help you better.   )

I am trying to adapt the Quickpay gateway plugin to also accept recurring payments. So far I can get it to register a subscription at Quickpay, but I cannot catch the callback and then trigger the actual payment. I need to understand more of the logic in CBSubs' flow. I have looked at the Worldpay plugin to try to understand - but it might not be the same flow as Quickpay: learn.quickpay.net/tech-talk/guides/subscriptions/#introduction-to-subscriptions

Could you maybe give me some hints to move on ?

I've now come a little further, but not shure if it is the right way. I can now signup at quickpay for a subscription, then on the response I can trigger a recurring payment, but my problem now is that it needs a new unique order_id - The Subscription order_id and the recurring payment order_id cannot be the same at Quickpay. How does CBSubs handle this ?

The order_id for quickpay is whatever the prefix you have configured in the gateway plus the basket id. The prefix is removed on processing leaving just the basket id allowing the order to match and pay the correct basket. When a gateway requires this behavior and has similar for unique subscription payments you need to generate an incremented order_id and strip away the increment during processing. Probably just a matter of improving the _prepareOrderID function.

I don't recommend doing any of this though and simply use Stripe which already has nearly all of Stripes features implemented and is significantly more secure for your users as payment information never touches your server.

I don't se why Strip is more secure - payment details are entered in a quickpay window and not on the website server - so what is the difference ??
Anyway - I have gotten it to work now. Only thing I need now is to catch the triggering of a new recurring payment. So what I need to know is what this URL exactly does:


xxxxxxx.dk/index.php?option=com_comprofiler&task=pluginclass&plugin=cbpaidsubscriptions&do=autopayments&key=d41d8cd98f00erf4e9800998ecf8427e&format=raw

Right now nothing happens when I use it - which method should it trigger in the payment gateway ?