This page documents edge cases that can happen when RBI guests place orders using the POS, part of Customer Journey Scenarios - POS. See also POS - Redeem Offers and POS - Redeem Rewards.
Contents
1. Switch users
This is a potential fraud use, where a guest authenticates themselves using one loyalty code, and then attempts to redeem rewards using a different loyalty code.
This scenario is the same whether guests are redeeming offers or rewards.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens the Loyalty code page on the RBI app |
|
|
|
Cashier is prompted to add a loyalty code |
|
|
|
Guest either scans the loyalty code, or tells the 6 digit code to the cashier |
|
|
|
Guest opens an reward on the RBI app in a different device, using a different user, and chooses to redeem in restaurant |
|
|
|
Guest (on their second device) either scans the reward’s QR code, or tells the 6 digit code to the cashier |
|
|
|
2. Payment Failure
This can be caused if users do not have enough funds to be able to complete the transaction.
This scenario is the same whether guests are redeeming offers or rewards.
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage (POS) |
---|---|---|---|
Guest opens a reward on the RBI app |
|
|
|
Guest taps “Redeem in Restaurant” |
|
|
|
Cashier is prompted whether the Guest has loyalty, and confirms |
|
|
|
Guest either scans the reward code, or tells the 6 digit code to the cashier |
|
|
|
Cashier attempts to finalize the order but there is a payment failure and order is not completed |
|
|
|
There are no more scenarios. You can return to Customer Journey Scenarios - POS