...

Currently, the restaurant lacks the ability to choose which payment methods to use, particularly offline options like cash, vouchers, or at-home terminals, during the delivery process. RBIIberia aims to provide this flexibility to the restaurant, allowing it to temporarily disable the "at-home terminal" payment method whenever it is not available.

We have two tools that can be used by restaurants to configure payment method availability: Sanity and DOP.

Option 1: Use Sanity for payment methods configurations - Discarded

Pros

• This is the standard tool for Fz’s (market) configuration persona

• Sanity is deployed for every Fz (market) in RBI

...

• Operations team doesn’t have access to Sanity.

  • Possibilities:

    • New sanity access roles for the operations team

    • Operations team would require Fz’s configurators to update it if necessary

• For Restaurant configuration level, it should be done one by one (despite that it can be added a new configuration to do for all restaurants at once).

• It’s not possible to do these configurations for the offline payment methods.

Option 2: Use DOP for payment methods configurations - (Chosen by business)

Pros

• This is the tool used by the Operations team. If we use this one, they don’t need to learn and to get access to use another tool.

• This tool supports the configurations for offline payment methods (mainly for terminal machine at home and cash).

• Possibility to do these configurations at restaurant level. But it can also be extended to edit for multiple restaurants, just as "Cash Limitation feature".

• It’s possible to configure payments on DOP and create a “view only” version on Sanity. Then WL can query this information.

...

• DOP is used only by Iberia and Germany. This solution will only impact these markets.

✅ Proposed Solution

...

• .

✅ Proposed Solution

Add Payment Methods List on DOP

...

Currently, the management of available payment methods by market and brand is hard-coded in the Front-end (Whitelabel). This implementation relies on a feature flagLD feature flags from the guest app project , making it impossible to retrieve this information from other services, such as DOP.

To address this issue, we need to prioritize finding a solution. Here are the options we are considering:

Option 1 - Payment Methods List in Sanity - Recommended

We Recommend this Solution

After receiving feedback from the Menu team (Rafael Souza, Eduardo Yosida, and Lucas Palencia) and the Transactions team (Felipe Rooke), we have concluded that this solution is the best option at this time.

In this solution, we will create a new document for the list of payment methods. The DOP already has synchronization with Sanity, allowing it to access this information and determine which methods will be active or inactive. This way, the restaurant will have its payment methods organized by market and brand.Note:

...

...

Solution Option 1

In this solution, we need to implement new screens in Sanity to manage payment methods.

...

...