-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order of construction #1
Comments
To select for these payment types, we either need multiple gateways - one per payment type - or an option at the top level to switch between them. The multiple gateway approach would involve an awful lot of classes to deal with, so I'm going to head down the option approach, and see how that goes. |
1 similar comment
To select for these payment types, we either need multiple gateways - one per payment type - or an option at the top level to switch between them. The multiple gateway approach would involve an awful lot of classes to deal with, so I'm going to head down the option approach, and see how that goes. |
Direct Debit comes in two related forms:
I've not looked into it enough yet to tell whether we need to treat it as two payment types, or just one with some data/logic differences triggered by the parameters. |
There are other services too, so be added to this list. They include listing banks and customers, and managing card tokens. |
The payment methods are to be built in the following order:
iDEAL and EPS are not used in Germany, so are taking a lower priority.
The PaymentPage payment type supports multiple payment types, selectable by the user.
The text was updated successfully, but these errors were encountered: