Table of contents
Definition
Status |
| ||||
RBIberia Owner |
...
Paula Winter |
RBI Owner |
...
❓ Open questions
| Info |
|---|
We need to constantly make this section empty. |
Requirements
Andrea Ruani, Raphael Ferreira |
Requirements
Problem statement
Iberia market wants to provide users multiple options to facilitate the payment step.
Bizum is the most used online solution (4.5 M users in Spain) and it became a priority for the Iberia market.
Acceptance criteria
Success metrics
🤔 Assumptions
Premises
Solution
Scenarios
| Info |
|---|
Note: these are high-level scenarios that must pass testing before we can release the feature. They should also be used to drive design. Note that we do not specify user interface details in these steps - that is deliberate so that we focus on the process and not on the UI since the UI can change throughout design and development. |
Scenario 1: xxx
...
Steps
...
Expected results
...
Do this
...
Expect that
Design
Figma design here: [insert link]
Development
...
A new Bizum payment must be created for Paycomet.
This payment must work the same as Paycomet's PayPal, it must generate a link and be used in an Iframe where the payment will be processed.
The confirmation/tracking page should show the correct text in the payment reminder for this new payment method
The receipt email should show the correct payment option for this new payment method
The new method should be available in the user account methods list
We have to pay attention to changes from the Payments team, they are making some changes to their routine, and this new implementation cannot change the current behavior.
There are two flags that change the application's behavior: enable-paycomet-webhook-notifications (BE) and enable-backend-commit-order (BE & FE), we must test both ways, with the flags enabled and disabled.