You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's supporting 3 types of integrations + configurations with a high number of total combinations
no support for non-credit-card payments (e.g. ApplePay, etc)
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
We considered updating the existing extension to work with SSF first, and then cleaning it up, but we concluded that the effort would have increased
We considered cleaning up the extension before adding to SSF support, and then switching to the Payment Element, but that too would have needed more effort
We considered starting with Stripe Checkout, but that would have disrupted the current setup too much (maybe can be a feature added in the future)*
Plan
Start from scratch using the current extension only as a reference and cherry pick code (vs copying everything and then cleaning up)
We want to start from the Payment Element which comes with support for multiple payment methods, while still working well in the classic step-based checkout featured in SSF (vs. switching to the fully external Stripe Checkout)
*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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: