Loyalty and ID lookup
Recognise loyalty members from the card they pay with, sign up new members on the terminal, and keep member data up to date.
With Aera ID lookup, the card a customer pays with is also their membership card. The terminal reads the card, Aera looks it up in your ID Vault, and your POS gets the member number back before the payment. The customer taps once.
Three parties make it work. Find your part:
Sign the agreement, get your ID Vault and API access, and turn on ID lookup on your terminals.
Start here: Set up ID lookup
Build the checkout: look up the member before the payment, and sign up new members on the terminal.
Start here: Loyalty and card acquisition, in the ECR integration guide
Keep the member data in the ID Vault up to date: finish sign-ups, add and replace cards, delete members.
Start here: Manage member identities
How it works
- 1Your POS → TerminalCardAcquisitionRead the card first, with the amount.
- 2Terminal → Aera ID VaultLook up the cardThe customer taps. The terminal looks up the card in your ID Vault.
- 3Aera ID Vault → TerminalMember numberThe card belongs to a member.
- 4Terminal → Your POSCardAcquisition responseLoyaltyAccount has the member number. No LoyaltyAccount: offer sign-up.
- 5Your POS → Loyalty programGet benefitsYour POS asks your loyalty program for the member's discount or points.
- 6Loyalty program → Your POSDiscountThe new amount must not be higher than in the card acquisition.
- 7Your POS → TerminalPayment with CardAcquisitionReferencePay with the same card: the customer doesn't tap again.
- 8Terminal → Your POSPayment response: AeResponseCode 000Approved, with the member discount, in one tap.
- The POS sends a CardAcquisition request. The customer taps or inserts the card.
- The terminal looks up the card in your ID Vault.
- If the card belongs to a member, the response has the member number. The POS gives the discount or points. See Recognise members at checkout.
- The POS sends the Payment. The customer doesn't tap again.
- If the card isn't linked to a member, the POS can offer a sign-up on the terminal. See Enrol members at the terminal.
- The loyalty program finishes the sign-up and keeps the member's cards up to date. See Manage member identities.
Who does what
| Who | Does what | Pages |
|---|---|---|
| Merchant | Signs the agreement, orders API access, decides what a lookup returns, and asks Aera to turn on ID lookup | Set up ID lookup |
| ECR provider | Runs the checkout: looks up the member, offers sign-up, then pays or aborts | In the ECR integration guide: Loyalty and card acquisition, Recognise members at checkout, Enrol members at the terminal |
| Loyalty program | Owns the members: finishes sign-ups, adds and replaces cards, deletes members, through the Identity Services API. Encrypts card numbers before sending them | Manage member identities, PAR and encrypted card data |
| ECR provider and loyalty program | Test together before going live | Test and go live |
| Aera | Sets up your ID Vault, stores the data on your behalf and runs the lookup |
You are the data controller for the data in your ID Vault, and responsible for consents and the legal basis for processing. Aera processes the data on your behalf.
Key terms
| Term | What it means |
|---|---|
| ID Vault | Your own protected data area at Aera. Only your data, kept apart from other customers' data |
| Identity | One person, with a unique ConsumerId |
| Identifier | Something unique to the person that Aera can look up: a payment card, a bank account number, a mobile number |
| Loyalty value | What you want back when a member is found, usually the member number |
| Attribute | Personal data that isn't unique, such as name or postcode |
Get started
-
Merchant: Set up ID lookup: agreement, ID Vault and API access.
-
ECR provider: build the checkout with Recognise members at checkout and Enrol members at the terminal.
-
Loyalty program: connect to Aera with Manage member identities. Card numbers must be encrypted: see PAR and encrypted card data.
-
Together: test lookup, sign-up and cross loyalty, then go live. See Test and go live.
Steps 2 and 3 can run at the same time.
Used CardHolderOnBoarding before? See Move from CardHolderOnBoarding.
Updated 5 days ago