Note |
---|
Note that this feature is still under development and not available for use. If you are interested in implementing it on your market, please contact your Customer Success Manager. |
This page documents the expected user experience when RBI guests redeem promo codes when they place orders at a Kiosk, part of Customer Journey Scenarios - Kiosk. See also Kiosk - Redeem Rewards and Kiosk - Edge Cases.
...
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest does not log into loyalty, clicks on promo code section in the Kiosk, and inputs the promo code (e.g. A00001) |
|
|
|
Guest customizes the unlocked offer at will and adds to basket |
|
|
|
Guest checks out and pays |
|
|
|
...
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest opens the Loyalty code page on the RBI app |
|
|
|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest scans the loyalty code or inputs 6 digit code in Kiosk |
|
|
|
Guest goes to Promo code section in Kiosk and inputs the promo code (e.g. A00001) |
|
|
|
Guest customizes the offer at will and adds to basket |
|
|
|
Guest checks out and pays |
|
|
|
...
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest inputs a valid promo code in Kiosk screen (e.g. A00001) |
|
|
|
Guest customizes the offer at will and adds to basket |
|
| |
Guest goes to a second Kiosk and enters the same promo code (e.g. A00001) |
|
|
|
Guest goes back to the first Kiosk, checks out and pays |
|
|
|
Validate Coupon Endpoint
Use Case: The following endpoint allows a promo code to be validated/redeemed by the RBI Loyalty platform.
Endpoint URL: https://{reg}-{env}-{brand}-loyalty-middleware.rbictg.com/loyalty/coupon/validate
Expected Request Payload (assigning points):
...
code
: String
The code to be validated/redeemed by the loyalty platform.
...
loyaltyId
: String
Optional. The loyaltyId of the user. If not present, the validation will occur to an anonymous user.
shouldRedeem
: Boolean
Optional. Indicates whether the code should be validated and redeemed.
...
|
...
false
: the code will be validated only.
Expected Request Payload:
Code Block |
---|
{
"code": "ABCDE123",
"loyaltyId": "6d13456a-1304-5109-a117-af4de20b2487",
"shouldRedeem": true
} |
Expected Response Payload:
...