Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This is a template that should be used to document each feature. It’s meant to be easy, not prescriptive - change it at will!

Table of contents

Definition

Status

NOT STARTED IN DESIGN IN DEVELOPMENT COMPLETED

RBIberia Owner

RBI Owner

❓ Open questions

We need to constantly make this section empty.

MAIN QUESTIONS TO START DISCOVERY

  1. What is the usage of this method payment in BK PT?

  2. Do you have any demographic or customer data related to those who make payments with card at home?

  3. Is this payment method used in PLK ES and/or BK ES?

  4. What has been the decrease in sales after the launch?

  5. What is the flow in Airtouch?

  6. Are there any regulatory or legal considerations that might impact the implementation of card payments at home?

Tech Questions

  1. What are the API endpoints of integations?

  2. Is there any official technical documentation?

  3. What are the security/compliance concerns?

ALTERNATIVE SOLUTION

Considering the problem “user preference is the payment at home compared with the other ones for several reason (trust, simplicity, speed)”, we could explore more options like:

  • Prioritize MBWay as it’s the main payment method and it’s fast, simple and trusted in the Portuguese market

  • Offer discounts to use the online payment method

  • Add “pago seguro” and other logos to the payment page

Requirements

Problem statement

BK PT customers are facing limitations and inconveniences when making payments. To address this, we aim to implement a feature that allows users to make card payments at home (with POS owned by the driver?). The goal is to maintain the existing user experience avoiding impact on sales.

Acceptance criteria

Success metrics

🤔 Assumptions

Scope:

1 - Change the color of the “Rewards“ header

3 - Create a carrossel based on the quantity of crow

4 - Food image and button with disabled aspects when crows aren´t sufficient to buy the product

Solution

Scenarios

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

Release

  • No labels