The payment recognised Mariam. Your CRM recorded an anonymous basket.

Mariam leaves a padel court in Dubai on Sunday evening and stops at your hypermarket for chicken, Greek yoghurt, blueberries and sparkling water.

At checkout, the phone stays in the bag. Mariam doesn’t open your loyalty app or give the cashier a member number, and instead taps a UAE-issued Visa linked to an external rewards programme. The purchase qualifies without another scan.

The external programme connects Mariam to the store, time and payment value. Your till keeps the basket. Your CRM connects neither record because your member ID never entered the transaction.

Mariam repeats the trip for three Sundays, then stops. Your sales report loses a basket. Your CRM misses the lapse because it never knew those baskets were Mariam’s.

When your CEO asks what the loyalty partnership did for retention, will you show another reward issued or a named customer you can bring back?

Payit rewards the financial routine around the shop.

Dubai is targeting 90% cashless transactions across its public and private sectors by the end of 2026. (Digital Dubai, 2026)

In May, Payit added rewards to the UAE wallet its customers use for payments, transfers and salary deposits, with redemption across retail and lifestyle categories. (Payit via Gulf News, May 2026)

If your programme begins only when Mariam remembers your app, the wallet can recognise an interaction your CRM misses.

Emirates gets the linked-card event. The partner gets an anonymised view.

Skywards Everyday makes the split visible. A member links an eligible Visa or Mastercard. At a participating UAE outlet, the payment provider can share the store, date, time and value with Emirates so the miles can be awarded. The partner generally receives anonymised transaction data instead of the member’s personal data. (Emirates Skywards)

One tap, two records

The external programme receives the member, store, date, time and value. Your till and CRM receive chicken, yoghurt, blueberries and no member. The transaction was rewarded on both sides. Only one side can bring Mariam back.

Your till knows Mariam bought chicken, yoghurt and blueberries. Skywards can know which member earned, where and when. Unless your loyalty ID connects the records, your CRM can’t see the routine, the lapse or the customer worth contacting.

At an Aldar mall, one Visa can earn two loyalty currencies.

Darna’s terms allow one eligible Visa transaction at participating Aldar malls to earn Darna points and Etihad Guest miles when the card is linked to both programmes. (Darna Rewards, November 2025)

One tap. Two balances. The decision isn’t whether the programmes can coexist. It is what each relationship should do.

The external layer can reduce earning friction. Your loyalty programme and CRM should preserve the member identity, basket history, permission and retention measurement.

If the same tap produces two currencies but no usable customer event in your CRM, coexistence has rewarded the purchase without strengthening your relationship.

An external programme can recognise the payment. Your loyalty programme still has to recognise the customer.

If the report stops at rewards issued, it can’t defend retention.

Your partnership deck may show rewarded transactions and total value. Neither proves that you recognised Mariam, could make contact or influenced another visit.

01 · The retailer-identified rate

What percentage of externally rewarded transactions can you connect to one customer ID in your CRM?

If the external programme recognises Mariam but your CRM doesn’t, you’ve counted another programme’s customer recognition as your relationship.

02 · The retailer-contactable rate

Of the customers you can identify, what percentage can you contact under permission held by your business?

An anonymised report isn’t permission. If every follow-up must pass through the external programme, it controls the next customer conversation.

03 · The next-visit rate

What percentage of externally rewarded customers returned within their normal repeat window, and how did that compare with similar customers who weren’t rewarded?

If your report ends at points issued or sales attached, you’ve measured activity, not loyalty. Mariam’s lapse remains invisible.

Trace one rewarded transaction.

Take one externally rewarded transaction. Follow it across the payment layer, POS, loyalty record and CRM. Mark whether you can connect the member to the basket, communicate with permission, and measure what happened on the next visit.

The first blank that stops you making a retention decision is the part of the partnership to investigate.

Thanks for reading this far. Mariam’s payment was recognised. The next visit still belongs to the programme that can recognise the customer.