| Table of Contents |
|---|
🛠️ Potential Solutions
...
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.
...
Option 1 - Payment Methods List in Sanity - Recommended
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.
...
| Info |
|---|
This new screen (sanity document) will only list the available offline payment methods for the market. The restaurant level configuration will be stored in the restaurant documents, and managed via DOP as detailed in below. |
...
| Info |
|---|
The design team has not created these screens yet, this is just a sketch |
Field and Details | Screen on Sanity |
|---|---|
The new screen in the Restaurant Menu. In this screen we can add, remove and edit the payment method |  |
Screen where we can add new payment |  |
Title of Payment (name) - Payment title, we will use this title to save the status within documents restaurant for identification |  |
Payment method brand (paymentMethodBrand) - a string key that must match the one in WL_app. We will use this value to ensure consistent validation in the front-end. Example: “CASH“, “SODEXO_VOUCHER“, “PAYMENT_ON_DELIVERY_CARD” |  |
...
Sanity and DOP Payments | Whitelabel Payments | Payments avaliable to user on payment screen |
|---|---|---|
cash: true Sodexo Voucher: false Ticket Restaurant: false Payment delivery card: true | Credit Card Paypal cash Sodexo Voucher Ticket Restaurant Payment delivery card | Credit Card Paypal cash Payment delivery card |
...