Flow of payment gateway

So would it also be acceptable to override the httpsRequestGuzzle and then add the optional argument as stated here for child class: www.php.net/manual/en/language.oop5.abstract.php

httpsRequestGuzzle is just a helper function for calling Guzzle. You don't have to use it or override it, but you should be using Guzzle. The gateway already has a working example of using Guzzle directly to call Quickpay API; simply copy it and adjust the data being sent.

I get that, but I just find the helper function simple and nice to use ind the plugin.

Have sent a new plugin for review. Hope you have the time to take a quick glance at it.

Can see that there was a little problem with the amount of the recurring payment if it differs from the initial payment. I have now corrected that, but I need to know: What is mc_amount2 good for ? mc_amount1 is the amount of the first payment and mc_amount3 is the amount of the next payments - so what is amount2 ??

mc_amount2 and period2 are used if there's a different initial payment amount and duration in the plan. mc_amount1 and period1 are always the initial payment and duration. mc_amount3 and period3 are always the recurring amount and duration. For recurring subscriptions you typically won't use mc_amount2 and period2 since their values will get pushed to mc_amount3 and period3, but if you had a single payment plan with different initial amount and duration then it's important to have access to amount1 and amount2 for example.