Feature - Allow Payment Methods
For now, this solution is only available in the markets where paycomet is applicable and applies exclusively to home delivery services.
CONTEXT
With this feature, the restaurant operator can choose which offline payment methods to use, such as cash, vouchers, or home terminals during the delivery process. RBI aims to provide this flexibility to the restaurant by allowing it to temporarily disable the “offline” payment methods whenever it is unavailable.
IMPLEMENTED SOLUTIONS
Version 1
In the implemented solution, operation team users with access to the FZ-Portal will be able to decide which offline payment methods to activate or deactivate for each restaurant. Additionally, they will have the option to make bulk changes, selecting one or multiple restaurants.
Once these changes are made, the guest application (whitelabel) will not display the disabled payment methods during the checkout process for home delivery.
Use-Cases
FZ-Portal Allow Payments | Payment Methods on WL |
|---|---|
All offline payments enabled 
| All options enabled
|
Remove the cash of payment method
| Display all payment less Cash
|
Remove all offine Payments
| Display only online payments
|
There is a timeframe to update the new information regarding the payment method in the app, which may take up to 15 minutes.
Database
The value of these rules is saved on Sanity. More details here.
FZ-Portal (DOP)
To change this information, we need to use the FZ-Portal. More details here.
Feature Flag
Intl Tech - Guest App (Whitelabel)
enable-payment-methods-control
FZ Portal (DOP)
enable-payment-methods-control
Version 2
In the updated solution, operation team users with access to the FZ-Portal can schedule a period during which specific payment methods will be disabled. During this period, the disabled payment methods will not appear in the guest application (whitelabel), and they will automatically be re-enabled after the period ends.
Additionally, users can still permanently disable payment methods, as in v1. A new "quick fill" functionality has also been introduced, allowing operators to edit all payment methods at once. The bulk update option remains available, enabling changes for one or multiple selected restaurants at the same time.
Use-Cases
FZ-Portal Allow Payments | Payment Methods on WL |
|---|---|
Deactivate a payment with a date to reactivate  | Not display the payment until reactivate date  |
Schedule a payment to be deactivated in the future  | Display the payment until deactivate date. After reactivate date display the payment again  |
Use quick fill option to edit all payments at once  |
|
Permanent Deactivation of a payment | Not display the payment until operator reactivate |
Feature Flag
Intl Tech - Guest App (Whitelabel)
enable-payment-methods-control
FZ Portal (DOP)
enable-payment-methods-control
enable-schedule-payment-methods-control
max-concurrent-restaurants-requests
In this feature, users can update several restaurants, for instance, some markets can update over 1000 restaurants. This can occasionally lead to time-outs, as the time-out limit in the API Gateway is set to 29 seconds and can't be changed.
To address this issue, we divided the request into many smaller ones. There is an FF called max-concurrent-restaurants-requests, which allows us to choose how many restaurants we want to modify per request. Therefore, if we set this FF to 200 restaurants for an operation involving 1000 restaurants, the system will send 5 requests of 200 restaurants each. We conducted some tests, and this approach has not resulted in any time-out issues.