Closed wvengen closed 10 years ago
Work has started on the onlinepay branch using a plugin lib/foodsoft_adyen
.
We can still use Mollie for iDEAL, if we like (which has moved to a separate plugin lib/foodsoft_mollie
).
@Cor-Jan do we want to use Adyen's iDEAL when we can still use Mollie?
paytor is 43 cnts per transaction (processing by mollie, normally 99 ct per transaction) adyen is 60 ct per transaction but on the same payment platform.
switch to adyen is for easyness of use/overview. is a really important too. i would say. switch to adyen. keeps it structured
At this moment, when the foodsoft_mollie
plugin is enabled, the membership fee can be paid using that. Since we want to be able to use other providers as well, we need a preference to specify which provider is used to do online payments. Added task for that in issue description.
If this is too much work, we can resort to using only one payment plugin for everything. A helper method could then check which plugin is enabled, and give the appropriate payment link. Or something like that.
The Adyen PIN payment app works by intercepting the adyen:///payment
url. The query string has parameters like amount
to give payment details. There is also a callback url, where the user will be directed to after payment. Sounds easy!
Update: the Android app uses the http://www.adyen.com/android-app/payment
url instead.
After every transaction a new tab is created (when returning from the Adyen app). This is annoying. Possible solutions:
setTimeout
to read cookie, and if it's set - close the window.Fixed the issue of opening a new tab each time the Adyen app returns by creating an app - see foodsoft-app-payment, install from here (after enabling apps from unknown sources, see here and here, for example).
Mostly works, but as there were contractual issues, this is cancelled.
We'll be using Adyen shuttle PIN terminals, so we need to support them as payment provider.
n.b. iDEAL payments are for a next iteration