Page Comparison

...

• Pay@Counter Test Cases

  • User logins in the Kiosk with or without pre-selected items, selects Pay@Counter, and completes purchase in the counter/POS successfully

    • User loyalty points with new order are updated before user pays for order in the counter/POS

    • Once user pays for order in the counter/POS successfully, then user continues with updated loyalty point balance

    • Data events: the event Loyalty Transaction Claimed when channel = RESTAURANT and the event Loyalty Transaction Claimed In-store are triggered at this time

      • If Rewards are included in the purchase, the event Reward Redeemed In Store is also fired

      • If Offers are included in the purchase, the event Offer Redeemed In-store is also fired

  • User logins in the Kiosk with or without pre-selected items, selects Pay@Counter, and NEVER completes purchase in the counter/POS successfully

    • User loyalty points with new order are updated before user pays for order in the counter/POS

    • After X amount of time where this transaction was not closed in the counter/POS, POS vendor send VOID transaction to Loyalty API and user loyalty points returns to previous balance before transaction was started

    • Data events: the event Loyalty Transaction Voided and Loyalty Transaction Deleted are triggered at this time

...

More information about the Loyalty Middleware can be found here: Loyalty API

Generating OTP codes 

To generate 6-digit codes for testing and identifying user, you will need to go to the RBI app on the Staging environment and:

...