Move from CardHolderOnBoarding

Aera's earlier enrolment, CardHolderOnBoarding, started after a payment and reused that payment (STAN and amount) to sign the customer up. The new model starts with a card acquisition and keeps the member's data up to date for as long as they are a member.

What changes

Before: CardHolderOnBoarding	Now: card acquisition and identity management
Payment first, sign-up afterwards	Lookup first, then sign-up, then payment, all with one tap
Sign-up tied to an earlier payment (STAN and amount)	Sign-up uses the card acquisition reference
Lookup inside the payment	Lookup in the CardAcquisition response, before the payment
One program per lookup	Your own and a partner's program in the same lookup
Sign-up only. Little support for new or replaced cards	Full life cycle: add, replace and delete cards and members

What you need to change

In your POS:

Use CardAcquisition for every lookup. See Recognise members at checkout.
Run the sign-up with Input after the card acquisition, then pay with the same card. See Enrol members at the terminal.
Stop sending CardHolderOnBoarding requests.

In your loyalty program:

Complete temporary identities, and add, replace and delete cards and members. See Manage member identities.
Encrypt card numbers and send the PAR. See PAR and encrypted card data.

Then run the tests again.