Substituted the omnipay/mollie client with the official mollie php client.
Motivation and context
Why is this change required? What problem does it solve?
This supports tighter integration with the Mollie API in the future. I.e. for recurring payments functionality.
How has this been tested?
PHPUnit. Tests left untouched, still green. Mollie gateway code refactored.
Screenshots (if appropriate)
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.
Description
Substituted the omnipay/mollie client with the official mollie php client.
Motivation and context
Why is this change required? What problem does it solve? This supports tighter integration with the Mollie API in the future. I.e. for recurring payments functionality.
How has this been tested?
PHPUnit. Tests left untouched, still green. Mollie gateway code refactored.
Screenshots (if appropriate)
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist:
Go over all the following points, and put an
xin all the boxes that apply.Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.
If you're unsure about any of these, don't hesitate to ask. We're here to help!