...
With cash limitation data, the WL-App can validate if some rule is active and if it needs to hide physical payments;
This control is by each user;
At the moment of payment, the WL-app retrieves information about the user's most recent delivery order using the
getUserOrdersfunction. This includes restaurant details and any applicable limitation rules. Based on this information, we need to implement logic that hides the physical payment option if any limitation is met.For example, if it is the user's first home delivery purchase, which we can determine if the
getUserOrdersquery returns zero orders of this type, and the selected restaurant has a rule that the first purchase must not exceed $30.00 (as specified by the restaurant's information from Sanity), then the WL-app can check the current order value on this screen. If the order total cents exceeds the limit, the WL-app will hide the physical payment options.With all these details, the WL-app can effectively decide whether to display or hide the physical payment option.
| Zenuml sequence macro lite | ||||||
|---|---|---|---|---|---|---|
| ||||||
...
Consequences
Create new fields in Restaurant Document on Sanity to store Cash Limitation rules data;
Create a new screen on DOP (FZ-Portal) so that user can manipulate Cash Limitation rules and store them on Sanity;
Use the Sanity Client Lib to get and save information on Sanity, this library is already available on DOP
Create a new logic on WL-App in the payment page to control the exhibition according to the information and limitations that are got from Restaurant;
...