The customer intelligence layer for payment acquirers.
Loopbase turns payment data into customer intelligence — repeat behaviour, visit frequency, churn risk, and retention opportunities — then gives merchants the tools to act on it. One integration across your merchant portfolio.
The Gap
Your network sees every transaction.
Your merchant can't see every single customer.
A payment event tells you what was spent, where, and when. What most merchants still lack is a persistent view of the customer relationship behind those transactions — who comes back, how often they return, how spending changes, and when behaviour starts to deteriorate. Loopbase adds that intelligence layer without entering the authorisation or settlement path.
What a payment event contains
Amount — 87.50
Terminal ID — TRM-4471
Timestamp — 14:22, 3 Mar
Transaction reference — 004512
Merchant ID — MRC-0093
What it doesn’t
Who paid
Whether they have been here before
When they last came
Whether they are about to stop coming
IDENTITY LAYER
Loopbase adds the customer intelligence layer.
How the data works
Measure behaviour.
Act with consent.
Measurement and engagement are different problems. Loopbase separates them: transaction-level signals power intelligence, while customer-facing engagement only begins when the customer has explicitly opted in.
TIER 1
Transaction intelligence
Where the payment flow exposes a stable, privacy-preserving reference, Loopbase can recognise repeat behaviour without requiring customer enrolment or collecting personally identifiable information. That enables merchant-level measures such as repeat rate, visit cadence, and spend trajectory across identifiable transaction volume.
TIER 2
Consented engagement.
When a customer opts in, the merchant gains a permissioned relationship — through a phone number, wallet pass, or supported messaging channel. Loopbase can then power rewards, win-back campaigns, and lifecycle engagement against the intelligence already being generated.
THE OPERATING MODEL
Intelligence runs on Tier 1. Engagement runs on Tier 2.
Loyalty is one way Tier 2 gets populated, it is not what Loopbase is.
Enrolled customers self-select toward loyal ones, so absolute repeat rate within Tier 2 skews high. Trend movement within a consistent panel remains valid. We tell you this before you ask.
The Missing Piece
Your network sees every transaction. It has never seen a single customer.
For Acquirers
MDR compresses. This doesn’t.
Payment volume is a lagging signal. Customer behaviour moves first. Loopbase gives you earlier visibility into changes in repeat behaviour, visit frequency, and retention — while creating a merchant-services revenue line that isn’t priced off basis points.
Use cases
For merchants.
Enabling visibility.
Use cases
The autonomous layer.
Copilot surfaces your next move.
Loopbase continuously watches customer behaviour for changes in visit frequency, spend and inactivity — then surfaces the customers and segments worth acting on.
How it works
One platform.
Thousands of merchant integrations.
Step 1
Connect Loopbase to the transaction data required for merchant intelligence. The integration is read-only: Loopbase does not authorise transactions, move funds, or sit in the settlement path.
Step 2
Provision merchants from the partner console individually or in bulk. Each merchant receives access to its intelligence, retention tools, and configurable customer programme without building a separate integration.
Step 3
Use the identification path supported by the payment environment — an existing transaction reference or, for opted-in customers, QR, phone number, wallet pass, or another supported enrolment method. Loopbase connects repeat behaviour to the merchant relationship while keeping engagement consented and merchant-scoped.
Built for teams
Everything your merchants
need to know their customers.
Customer database
A merchant-level view of opted-in customers, visit history, spend behaviour, and relationship status.
Repeat rate & churn risk
See changes in customer behaviour before they become visible in payment volume.
Rewards & Offers
Merchant-branded rewards and offers designed around actual customer behaviour.
Retention opportunities
Loopbase surfaces customers and segments worth acting on; the merchant decides what gets sent.
Portfolio visibility
Track merchant activation, customer behaviour, retention signals, and programme performance from one partner console.
Built for financial infrastructure
Loopbase is designed to operate outside the payment authorisation and settlement path, with scoped access controls and data isolation built into the platform.
Your whole team. One platform.
Why Loopbase
Other Tools
Sold merchant by merchant
Separate integrations
Data fragmented across tools
Often dependent on POS or hardware
Relationship owned by software vendor
Distributed through the acquirer
One platform-level integration
Portfolio-wide customer intelligence
Merchant activation within minutes
Acquirer controls distribution and pricing
Pricing
Built to sell through you,
not around you.
FAQ
You have questions.
We have answers.
Why we’re building this
Loopbase started from a structural observation: payment acquirers sit at the centre of millions of merchant transactions, yet most merchants still lack a usable customer intelligence layer built on top of those flows. We believe that layer belongs at the platform level — distributed through the acquirer, not integrated merchant by merchant.
– Aditya Vaidya, Founder
Let’s talk about your book.
If you run an acquiring portfolio, give us twenty minutes. We’ll understand your merchant mix, transaction environment, and device estate — then show you where Loopbase could sit in your stack.