-
Notifications
You must be signed in to change notification settings - Fork 217
Closed as not planned
Labels
component: LPMs/APMsIssues related to LPMs/APMsIssues related to LPMs/APMstype: spikeThe issue is related to researching an upcoming task or project.The issue is related to researching an upcoming task or project.
Description
The goal of this spike is to get a sense of scope and touch points needed to enable the Swish payment method. This task should be timeboxed to about 2 days and conclude with a write up on the findings. The write up should allow us to give a more accurate estimate for effort to enable Swish. Since we have recently gone through this process for the other payment methods, this spike doesn't need to be that in depth and rather should be used to identify any glaring differences with the payment method that could impact timelines. Some of the questions we should look to answer (include, but not limited to):
- What efforts are required through the Stripe account, if any, to enable for set up, testing, communication.
- Look for areas to reuse code
- Look for ways to "template" out this payment method process (i.e. look at previous epic task lists as a starting point, look at the relevant PRs and which files they touch)
- Ensuring the new checkout experience is supported.
- A nice to have would be a proof of concept branch to explore.
Metadata
Metadata
Assignees
Labels
component: LPMs/APMsIssues related to LPMs/APMsIssues related to LPMs/APMstype: spikeThe issue is related to researching an upcoming task or project.The issue is related to researching an upcoming task or project.