Skip to content
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

Open
30 of 36 tasks
judgej opened this issue Dec 11, 2017 · 4 comments
Open
30 of 36 tasks

Order of construction #1

judgej opened this issue Dec 11, 2017 · 4 comments

Comments

@judgej
Copy link
Member

judgej commented Dec 11, 2017

The payment methods are to be built in the following order:

  1. CreditCard
    • Authorize
    • Purchase
    • Capture
    • Refund
    • Void
    • Query Pseudo Card (PKN Info)
    • Recurring (repeat) transaction)
  2. PayPal
    • Purchase
  3. DirectDebit
    • Authorize with payment page
    • Authorize without payment page
    • Purchase with payment page
    • Purchase without payment page
    • Capture
    • Refund
    • Void
    • Query Pseudo Card (PKN Info)
  4. Giropay
    • Authorize (not sure if this is available)
    • Purchase (initialise)
    • Check bankstatus
    • Giropay issuer bank query
    • Retrieve sender information
    • Bank selection widget (not a message, perhaps a helper)
  5. Paydirekt
    • Authorize
    • Purchase
    • Capture
    • Refund
    • Void
  6. iDEAL
    • Purchase
  7. EPS

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.

  • Get Transaction message (covers all payment types)
@judgej
Copy link
Member Author

judgej commented Dec 13, 2017

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
@judgej
Copy link
Member Author

judgej commented Dec 16, 2017

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.

@judgej
Copy link
Member Author

judgej commented Dec 16, 2017

Direct Debit comes in two related forms:

  • With a payment page.
  • Without a payment page.

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.

@judgej
Copy link
Member Author

judgej commented Dec 16, 2017

There are other services too, so be added to this list. They include listing banks and customers, and managing card tokens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant