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

BLIK Spike #3827

Open
Tracked by #3814
bborman22 opened this issue Feb 3, 2025 · 0 comments
Open
Tracked by #3814

BLIK Spike #3827

bborman22 opened this issue Feb 3, 2025 · 0 comments
Labels
type: spike The issue is related to researching an upcoming task or project.

Comments

@bborman22
Copy link
Contributor

bborman22 commented Feb 3, 2025

The goal of this spike is to get a sense of scope and touch points needed to enable the BLIK 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 BLIK. 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):

  • This payment method may suffer from the same deferred intent restriction as ACSS and so we should coordinate the effort there (cc @ricardo as the engineer currently working on ACSS).
  • 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.
@bborman22 bborman22 added the type: spike The issue is related to researching an upcoming task or project. label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: spike The issue is related to researching an upcoming task or project.
Projects
None yet
Development

No branches or pull requests

1 participant