Closed elia closed 1 year ago
In case external payments will need additional support from routes (e.g. ApplePay/GooglePay allowing to change the address) that will be dealt with in further versions.
After a live discussion on this with a few core-team members from @nebulab no objections were raised, closing and proceeding to create more detailed issues.
Problem
The current implementation is very old:
Proposal
We want to overhaul the extension and at the same time drop support for the legacy frontend, moving to a more scaffolding based installation (vs. view/controller inheritance).
Ruled-out approaches
Plan
*Stripe Checkout is an extremely optimized checkout solution and we might want to add support to it in the future. Since it includes a lot of new required functionality (webhooks, possibly syncing Product and other information with Stripe) we considered this out of scope for the overhaul.