Overview

In the Amount Finalised scenario, the Payment Application will trigger TruModule to display a TruRating Question after the final tender amount has been confirmed by the customer but before they are prompted to present their card. This scenario is applicable in retail environments where the operator/customer may perform one or more operations through the payment terminal or PED that effect the tender amount and that therefore requires this confirmation step to be performed (e.g. adding gratuity, processing a loyalty card).

Cash and voucher payments are out of scope for this scenario.

UML Sequence

The sequence of events and messages for this scenario is shown in the following UML diagram:

UML Sequence
UML Sequence

In this scenario the Payment Application will wait until the customer Rates, Skips or a Timeout occurs. Timeout time is configurable.

Refef to the screen design specification and the example TruService messages exchanges for more information.

Outline

A sample customer and operator journey for rating at the point the tender amount is finalised is summarised in the following simple table:

Step Activity Comments
1 Customer approaches point of service with basket / goods to purchase PED is idle or displaying the advertising loop
2 Operator starts transaction by scanning or in another way adding first item to basket  
3 Operator continues scanning/adding transaction items to transaction  
4 Operator finishes adding item to customer’s transaction, total is calculated  
5 Operator processes tenders based on customer requirement Steps 6 onwards performed when CARD tender selected
6 Operator select CARD tender This can be any payment type processed by the payment application (i.e. contact & contactless payments)
7 Any solution or environment specific processing occurs (e.g.):  
Loyalty  
Amount adjustment  
Gratuity  
8 Merchant/customer confirms the final amount  
9 Rating question is selected Next question in sequence is selected. A question may not be asked based on configuration. If no question is selected, then tender proceeds as normal (step 12)
10 Rating question is displayed on the PED Customer invited to respond 0-9 or Clear to skip. If customer provides a rating or skip before timeout, then they receive a confirmation message via the PED “Thanks for Rating”’ or “Sorry you Didn’t rate”
11 Rating question is cancelled after a configurable number of seconds if rating not given PED is returned to idle state
12 Customer is prompted to tap or insert their card based on payment application configuration  
13 Card payment process continues as normal  
14 TruRating receipt text is included on the customer’s receipt  

NOTE: Key aspect of this customer journey is that the card payment process is suspended while the rating question is displayed and answered, skipped or timed out.

Feedback