Loyalty Card Scenarios Review
Scenarios of loyalty card life cycle in the Koshelek App
1. User Registration in the Koshelek App
Only registered users can issue loyalty cards in the Koshelek App. If the user is not registered, the registration scenario begins when the user attempting to issue a card. Each registered account is associated with a confirmed phone number. The email address of the user is used as an additional identifier.
2. Main Scenarios
2.1. Loyalty Card Issuing
The user can issue in the Koshelek App an existing card (previously registered in the partner’s CRM system by phone number or email address), or a new card.
Before the card is issued, the user must agree with terms of issuance conditions (given by the partner), and specify allowed channels to communicate of the loyalty program operator with the user (SMS, email, voice calls, other ways). When the card issued, user’s personal data and the list of allowed communication channels are transferred to the partner.
2.2. Loyalty Card Service Requests and User Profile Update
Loyalty Online API provides main service requests on a loyalty card, such as:
- show card balance;
- get and display list of promotional offers of the partner available for the card holder;
- view history on card operations;
- request for update customer’s personal data: if the user changes the personal data in his profile in the Koshelek App, the updated data are transmitted to the partner;
- issue a card using a prearranged card pool on our side;
- issue a card without a number using only phone number;
- assign a card number after data transmitting to the partner within the POST request.
3. Additional Scenarios
By agreement with a partner, additional methods inside Loyalty Online API may be provided, if required. These additional methods can be used to satisfy special needs of the partner.
4. Promos
4.1 Submit cash receipt data
This method can be used during partner promos with cash receipts. When the user scans cash receipt in the Koshelek app, Koshelek server will use this method to send purchase details, including user ID data and QR code data of scanned receipt.
Note
Available since Loyalty API version 1.1.0 onwards.