A code to the customer's phone before their account is used
The customer asks: The member reads out a code we text them before their loyalty balance, credit or account can be used at the till
- Verdict: Ready, with limits (6)
- Door: Capture on an event · area: Customers and loyalty › New and existing customers
- Recipe: Customer code check: a one-time code before a customer's account is used
- Sample: S48 — Customer code check (pp_ccc): a one-time code before a customer's account is used
- Checked: run on our test bench 2026-10-23 · a code texted through iVendNext's own SMS settings and Notification, the right code letting the customer on and the payment through, a wrong code refused, the customer with no mobile number taken off
What you build
A capture on customer select that answers with a code field. When the cashier puts a customer of a group the retailer names on a sale, your service writes a code to a record of its own, and the retailer's own Notification texts it to the mobile number on the customer's record. The cashier types the code the customer reads out; until it is right, no door that takes payment takes that customer. The sample S48 does it, one rule per customer group.
Limits
- The code comes when the customer is picked, not when they pay from their loyalty balance: name the groups that need it.
- The code goes to the number on the customer's record: a cashier who may change that number can send it elsewhere, unless iVendNext keeps the phone fields for its managers.
- The retailer locks the customer's group (permission level 1, managers only), or a cashier could move a member to a group that is never asked.
- iVendNext's own SMS settings and a Notification send the text: the kit brings no gateway.
- Never asked for the store's walk-in customer; offline the declared down answer applies.
- One app answers customer select on a POS Profile.
Tell the customer
Before a member's loyalty balance or account can be used at the till, we text them a code and the cashier asks for it, so no one else can spend what is theirs.
What next
- Tell the customer the 6 limits above, and write them into the proposal.
- Follow the recipe: Customer code check: a one-time code before a customer's account is used.
- Copy the sample: S48 — Customer code check (pp_ccc): a one-time code before a customer's account is used, and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Test it with your service stopped: the till applies the answer you declared for when it is down.
Related needs
- After a sale the customer gets our message asking how the visit was, taps an answer, and we see the answers by store — Ready, with limits (5)
- Every new customer must give a phone number or an e-mail — Ready, with limits (2)
- A one-time code sent to the customer before a new customer is made at the till — Ready, with limits (2)
- A question or a check when the cashier picks an existing customer for the sale — Ready, with limits (6)
Start a project shortlist with this need · Put it in your blueprint · Every need