Licensing notice Kadyan Paygate India (OPC) Private Limited holds an NPCI Agent Institution licence for Bharat Connect (BBPS). This is the only licence we hold. We are not licensed or regulated by the Reserve Bank of India. Prepaid cards are issued by our RBI-licensed partner banks and issuers, and customer funds are held by those partners, not by us. How we work
Talk to us
ExpensesBill paymentsLoyalty EngagementCardsHow we work Grievance redressalPrivacy & cookies Talk to us
Home/Services/Customer engagement
Customer 360 and engagement

The same person, recognised everywhere.

A card swipe in Jaipur, a UPI scan at the counter, an app session at midnight and a support call on Monday are one customer. We resolve them into a single profile — built on what people actually did, because the spending data is on our ledger — and give you segments and journeys you can act on.

1Profile per person, across every channel
RealSpend data, not survey answers
ConsentRecorded per channel, enforced everywhere
App Card UPI Support Store Web
Why it is different

A profile built on money, not on guesses.

Most customer platforms know what someone clicked. We know what they paid for, where, how often, and whether they came back — because the transactions run through the same platform.

Identity that actually resolves

Mobile number, card token, email, loyalty ID and app device collapse into one record, with a confidence score and a history of every merge.

Behaviour you can trust

Segments are built from cleared transactions and real visits. A customer who 'drifted' is one whose spend actually stopped.

Journeys that trigger on events

A balance running low, a missed month, a first swipe, a tier about to lapse — each can start a journey the moment it happens.

Every feature

What is in the box.

Profile

Identity resolution

Deterministic matching on verified identifiers, probabilistic matching on the rest, with a reviewable merge history and one-click unmerge.

Profile

Unified timeline

Every card spend, bill payment, points movement, app session, store visit and support ticket in one chronological view per person.

Profile

Computed attributes

Lifetime value, average basket, visit frequency, preferred category, preferred store, days since last transaction — recalculated as events arrive.

Profile

Consent and preference centre

Channel-level consent (SMS, WhatsApp, email, push) recorded with timestamp and source, enforced automatically in every journey.

Segments

Behavioural segment builder

Combine spend, frequency, recency, category, geography, tier and consent in a visual builder. Segments refresh continuously.

Segments

Ready-made segments

Lapsing, high-value, new-this-month, single-visit, tier-adjacent, never-redeemed — available on day one and editable.

Segments

Lookalikes and exclusions

Find customers who behave like your best ones; exclude anyone who complained last week or opted out yesterday.

Journeys

Event-triggered journeys

Start on a transaction, a balance threshold, a tier change, an inactivity window or a support outcome. Branch on what the person does next.

Journeys

Multi-channel delivery

App push, SMS, WhatsApp, email and in-app messages, each respecting the person's consent and a frequency cap you set.

Journeys

Offers worth money

Attach a points credit, a card balance top-up or a bill-payment credit to any message. Redemption is tracked back to the journey.

Journeys

A/B tests and holdouts

Test message, timing and offer size, with a holdout group so you can see what the journey actually changed.

Analytics

Cohort and retention views

Retention by acquisition month, channel or first category. Revenue per cohort over time. Churn curves that use real spend.

Analytics

Campaign attribution

Incremental spend, redemptions and visits attributed to each journey against the holdout — not last-touch guesswork.

Analytics

Store and branch performance

Footfall, repeat rate and average spend by location, from the same transaction data.

Data

Import and export

Bring in CRM, POS and web data by file or API; export profiles, segments and events to your warehouse or CRM on a schedule.

Data

Webhooks and API

Every profile event is available in real time for your own systems, with the same consent flags attached.

Data

Privacy by design

Data stays in India, is minimised per purpose, and is deleted on schedule. Data-principal requests are handled through one console.

Data

Role-based access

Marketing sees segments, not card numbers. Support sees the timeline, not the segment logic. Auditors see everything, read-only.

How it works

From scattered signals to one journey.

1

Connect the sources

Card, bill and points data are already on the platform. Add your POS, app, website and CRM by file or API.

2

Resolve identities

We match identifiers into one profile per person, with a confidence score and a history you can review.

3

Build segments

Use the ready-made ones or build your own from real behaviour. They refresh as new events arrive.

4

Run journeys, measure honestly

Trigger messages and offers on events, deliver within consent, and read the result against a holdout.

Who uses it

Anyone who wants the second visit.

Retail and D2C

Recognise the shopper across store and app, win back the ones who drifted, and move the near-tier customers over the line.

Fuel and QSR chains

Frequency-driven businesses where a missed week is a signal, and where a small credit on the card brings the visit back.

Banks, NBFCs and insurers

Customer profiles that include payment behaviour, with journeys for on-time payment, renewal and cross-sell.

Transit and mobility

Riders on NCMC cards recognised across metro, bus and parking, with journeys for lapsed commuters.

Employers

Employee profiles that combine benefits usage, recognition and expense behaviour for HR analytics, within consent.

Hospitality

Guest profiles across properties with preferences, spend and loyalty status in one view for the front desk.

Straight answers

Questions about engagement and data.

Whose data is it?
Yours. When you run a programme for your customers or employees, you are the data fiduciary and we process on your instructions under a data-processing addendum. Our Privacy and Cookies Policy sets out both roles.
Where is the data stored?
On infrastructure located in India, in line with the RBI's directions on payment data. It is not transferred outside India.
How is consent handled?
Recorded per channel with source and timestamp, and enforced automatically — a journey will not send an SMS to someone who has not consented to SMS, regardless of what the segment says.
Can we connect our existing CRM?
Yes. Import by file or API, export profiles and segments back on a schedule, and receive events by webhook. Most clients keep their CRM and use us for the behavioural layer.
What does 'built on real spending' actually mean?
Card spends, bill payments and points movements happen on our ledger, so a segment like 'spent at least twice a month for six months and nothing in the last sixty days' is computed from cleared transactions, not from data someone typed into a form.

See it with your own numbers.

A 30-minute call, a straight answer on timeline and cost, and partner licence details for your compliance team.

Also on the platform

Works better together.