Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

Version 1 Next »

  1. Default status:

When the feature is deployed on the environment and the payment method is added on the Sanity, the payment method is created on DOP with the default status as "Null".

However, even if the status is "Null", if the payment method is Enabled on Launch Darkly, the payment method will continue to be listed on the dropdown. In order to deactivate the payment method, it is necessary to deactivate by DOP and save.

Regarding rolling out this feature, we recommend a bulk update in all restaurants in each market.

For new restaurants, it will be necessary to edit and save.

  1. Payment method dropdown caching

There is an existing caching on the payment method dropdown in the user session. So after a payment method is activated or deactivated via DOP, the update will reflect if the user reloads the page or reopens the app. This behavior already happens in other places in the Whitelabel. Still, we are refining a solution to fix this on the dropdown as we also implemented the cash limitation feature.

  1. The modal update confirmation

The modal update confirmation is already implemented on the cash limitation only when the user is updating two or more restaurants. We keep this behavior on the allow payments as well.

  1. Translation payment methods on DOP

The payment methods title displayed on the DOP page is getting the translation from Lokalise. Just in case it is necessary to customize it, we will have to implement this.

  • No labels