Loyalty Card Scenarios Review
Scenarios of loyalty card life cycle in the Koshelek app
Documentation has moved
The information on this page is no longer updated and may be obsolete. The most current Koshelek documentation is now available at the new address:
1. User Registration in the Koshelek app
Only registered users can issue loyalty cards in the Koshelek app. If a user is not registered, the registration scenario begins when the user attempts 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
In the Koshelek app, a user can issue an existing card (previously registered in partner’s CRM system by a phone number or email address) or a new card.
Before a card is issued, the user must agree with terms of issuance (given by the partner) and specify allowed communication channels between the loyalty program operator and the user (SMS, еmails, voice calls, other ways). When the card is 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
Cardsmobile Loyalty Online API provides main service requests on a loyalty card, such as:
show card balance;
get and display partner's list of promotional offers available for the card holder;
view history on card operations;
request for update customer's personal data — if a user changes the personal data in their profile in the Koshelek app, the updated details are transmitted to the partner.
3. Additional Scenarios
By agreement with a partner, additional methods inside the Cardsmobile Loyalty Online API may be provided, if required. These additional methods can be used to satisfy special needs of the partner.
Last updated
