Designed to: catch stale or missing data before it reaches a decision.
An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution
Platform · Perx Data Acquisition
Any format. Any frequency. One steady flow of customer data into Perx.
Card payments every second, app activity as it happens, the core banking file every night. Perx Data Acquisition takes each signal in the form and at the pace your systems already send it, checks it in, and puts it on one stream for Perx Intelligence Suite. It is designed to do this without a months-long field-mapping project, and without moving data out of the region it must stay in.
Loyalty. Measured in Profit
33×
reduction in CAC, to $9 per customer
A leading Singapore neo bank
~80%
first-transaction activation rate, up from 42%
SMBC Jenius, Digital Bank · Indonesia
$67.9M
in transaction value, at 1.2x ROI in 7 months
Capitec, Retail Bank · South Africa
What makes it different
Most data projects start with months of mapping. Perx starts with the data you have.
Today
Integration stalls on field mapping and data residency approvals.
Customer data sits across cards, mortgages, policies and claims, the app, the CRM and partner systems, each with its own format and refresh cycle. Every new source means a remapping exercise before go-live. Then the residency review asks where the data will live, and the project waits again.
With Perx Data Acquisition
Designed to connect any source as it is, hosted by Perx or inside your own environment.
One collection format accepts every source in the format it arrives. Real-time and batch data run on the same contract. Perx runs in a Perx-managed cloud, through an on-premise collector, or fully on-premise. Customer identifiers are hashed or tokenised at collection.
The problem it solves
The data exists. It just
never arrives in one place.
Every system, its own format and schedule
Cards stream every second, the app logs as it goes, core banking sends a file overnight. Each has its own field names, so no single team sees the whole customer.
Months of mapping before go-live
Data platform projects start by remapping every field from every source. Value waits until the last source is clean.
Residency blocks the deal
Cloud-only platforms ask regulated institutions to move customer data out of the region it must stay in. Risk says no, and the project stops.
Engagement outside your tools goes uncounted
A push opened in your marketing tool, a partner redemption or a complaint ticket never reaches the customer picture, so targeting misses half the relationship.
How Perx Data Acquisition solves it
One collection layer for
every customer signal.
Real-time APIs, Kafka streams, the Perx SDK, webhooks, and SFTP or batch files, all on one contract. The data foundation Perx Intelligence Suite and every campaign run on.
Collection · Streamed or batched
Every signal, the moment it enters.
Transactions, app and microsite activity, rewards, points, consent, and partner and marketing-tool events, in the format each one arrives.
Deployment · Data residency
Your data lives where your regulator needs it to.
A Perx-managed region, an on-premise collector, or fully on-premise. The same data contract in every pattern.
Privacy, consent & source health
Nothing collected without its consent state. Nothing silently dropped.
Identifiers hashed at collection, consent captured per customer, and every source monitored for freshness.
How a signal travels
Follow one card payment from your system to Perx.
A customer pays for lunch. Here is what happens to that one signal, step by step. The same path runs whether the signal arrives alone, every second, or in tonight’s file.
- You send it, as it is.
Your system sends the payment in its own format, the moment it happens. No reformatting first.
HTTPS API · SDK · webhook · file - Perx checks who’s sending.
Your system’s credentials are matched against a one-way fingerprint. Perx never stores the credential itself.
Credential check - Your settings are already to hand.
Perx keeps your organisation’s settings close by, so checks don’t wait on a database lookup every time.
Layered cache - Guardrails before anything moves.
Account status, agreed volumes and permissions are checked on every request.
Status · quota · permissions - Labelled as yours.
The record is tagged to your organisation, so your data never mixes with anyone else’s.
Organisation tag - Onto the stream.
The payment joins one event stream, and the stream confirms it has it.
Kafka - A receipt, straight back.
Your system gets an acknowledgement as soon as the payment is safely on the stream, then carries on. It never waits for what happens next.
202 Accepted
Collection · Real-time and batch on one contract
Start with the data you have, and everything that arrives next.
Perx Data Acquisition connects to the systems you already run and accepts every signal in the format it arrives. Every source goes into one fixed collection envelope, stored exactly as it came in. Data is not rejected because field names differ across systems. Mapping to a standard customer model happens later, in Perx Intelligence Suite.
Cards, mortgages, the app and partner systems can each send data in their own format from day one.
Real-time API and Kafka ingestion
Event-driven APIs and Kafka streaming collect transactions, app and microsite activity, rewards, points and consent events as they happen. Your transaction data reaches Perx the moment it happens, not in last night’s batch file.
Proof: On the current Perx platform, customer touchpoints across Perx clients grew from 6.0 billion to 8.3 billion a year.
SDK and microsite event capture
The Perx SDK and microsites capture in-app and on-page behaviour, such as sessions, clicks and page views. Offline events are sent when the device reconnects, so app behaviour lands alongside transactions for the same customer.
Designed to: put app behaviour and transactions in the same customer record, so digital and loyalty teams stop working from two versions of the customer.
SFTP, batch and existing pipelines
Existing SFTP and batch files are accepted alongside real-time streams through the same ingestion contract, with replay and partial-success handling. Your current integrations keep running and feed the same intelligence.
Designed to: add capability without the risk and cost of rebuilding the pipelines you already run.
Every signal, in the format it arrives
One fixed collection envelope for every source. Nothing is rejected because a field is named differently in another system, and no source has to be remapped before it connects.
Designed to: shorten the path from contract to first signal, because your teams skip the months of field remapping before go-live.
Deployment · Data residency
Your data lives where your regulator needs it to.
Choose one of three deployment patterns. Run Perx in a Perx-managed cloud, forward from an on-premise collector, or run Perx Data Acquisition and Perx Intelligence Suite fully on-premise so raw data never leaves your environment. The data contract is the same in every pattern, so you can change deployment later without re-integrating.
Data residency stops being the reason the answer is no.
Perx-managed cloud
Run Perx in a Perx-managed cloud, with hosting, security and operations handled by Perx.
Proof: Perx is ISO/IEC 27001 and ISO 27018 certified and holds SOC 2 Type II.
On-premise collector
A collector inside your environment forwards to Perx. You can send pre-computed facts, such as engagement indicators or dormancy flags, instead of raw transactions, with customer identifiers hashed.
Designed to: let institutions with strict data-transfer rules connect without sending raw transaction records.
Fully on-premise
Perx Data Acquisition and Perx Intelligence Suite both run inside your perimeter. Raw data never leaves your environment.
Designed to: meet the InfoSec requirements of large regulated banks, insurers and telco financial services businesses.
One data contract in every pattern
Every deployment pattern uses the same data contract. Start fully on-premise and move to Perx-managed hosting later, or the reverse, without re-integrating your sources.
Designed to: let you change deployment as your regulator’s position or your own strategy changes, without starting over.
Privacy, consent & source health
Privacy starts where data enters. Problems surface before a campaign runs.
Consent, channel permission and jurisdiction events are captured per customer as data arrives. Every source is monitored for freshness and sync health, and failed records are held in quarantine with the original payload. You know when a feed breaks before a decision runs on stale data.
Nothing is silently dropped. Every failed record is held with its payload, its error and its retry count.
Privacy and consent captured at collection
Consent, channel permission and jurisdiction events are captured per customer. Customer identifiers are hashed or tokenised, and sensitive identifiers are hashed, rejected or quarantined by regional policy: GDPR, PDPA, DPDP or POPIA.
Proof: Perx is ISO/IEC 27001 and ISO 27018 certified and holds SOC 2 Type II.
Source health monitoring and quarantine
Every source is monitored for freshness and sync health. Failed records are held in quarantine with the original payload, the error and the retry count. Perx Intelligence Suite shows data freshness and source coverage next to every signal.
Broad source coverage
Collection for CRM and CDP, core banking and card processors, external rewards and points engines, marketing and messaging tools, partner callbacks, notification providers, and support and feedback tools.
Designed to: make targeting reflect the customer’s whole relationship, including engagement that happens outside Perx.
Read-only to your systems
Perx Data Acquisition integrates at the data layer and only receives data. It never writes back to your core banking or source systems.
Designed to: keep your core systems out of scope of the integration.
Also built for
The same three levers, tuned to
where a bank is starting from
Large Retail Banks
Modernizing a legacy points system
Runs on existing core banking data no multi-year replatforming. Capitec’s numbers above are the proof point for what this looks like at incumbent, multi-million-customer scale.
Micro-Lenders & BNPL
Turning repayment into a rewarded habit
For a lender, the loyalty problem isn’t points it’s repayment behaviour. Streak-based repayment missions and gamified credit-health journeys turn on-time payment into a habit instead of a collections exercise.
67% CAC reduction · 51% of dormant users reactivated in 30 days
Wallets, Superapps & Remittance
Built on frequency, not balances
Missions tied to monthly send streaks and reload cadence are built to convert one-off usage into repeat behaviour, the same mechanic logic proven in the Activate and Retain sections above. No client stat is attached here yet none exists for this segment.
67% CAC reduction · 51% of dormant users reactivated in 30 days
Where it fits
The data foundation under your Perx programme.
Perx Data Acquisition collects the signals. Perx Intelligence Suite turns them into intelligence your team can act on, in the campaigns, rewards and journeys you already run on Perx.
Your systems
Where signals start
Cards, accounts, the app, CRM, partners and messaging tools.
Perx Data Acquisition
Collect
Every signal, in any format, at any frequency, checked in and on one stream.
Perx Intelligence Suite
Understand
Explainable signals on who needs attention, and why.
Your Perx programme
Act
Campaign Engine, Rewards Engine and Behaviour Mechanics run the campaigns, rewards and journeys.
Every customer interaction in your Perx campaigns is captured back through Perx Data Acquisition, so each customer’s next signal reflects what they just did.
Frequently asked
Questions your CDO, CTO and InfoSec team will ask.
What is Perx Data Acquisition?
Perx Data Acquisition is the data foundation of the Perx Customer Intelligence & Growth Platform. It collects every customer signal, such as transactions, app and microsite activity, rewards and points, consent, partner and marketing-tool events, through real-time APIs, Kafka streams, the Perx SDK, webhooks, and SFTP or batch files, in the format each signal arrives.
Does Perx Data Acquisition connect to our core banking system?
Perx Data Acquisition only receives data. It integrates at the data layer and never writes back to your core banking or source systems.
Does raw customer data have to leave our environment?
No. Perx Data Acquisition is designed to run in a Perx-managed cloud, through an on-premise collector that forwards to Perx, or fully on-premise alongside Perx Intelligence Suite. With the on-premise collector you can send pre-computed facts instead of raw transactions, and customer identifiers are hashed or tokenised at collection.
Do we need to clean or remap our data before connecting?
No. Every signal is stored in the format it arrives, and data is not rejected because field names differ across systems. Mapping to a standard customer model happens in Perx Intelligence Suite, which flags missing or stale sources instead of hiding them.
Can we keep our existing SFTP and batch pipelines?
Yes. Existing SFTP and batch files are accepted alongside real-time streams through the same ingestion contract, with replay and partial-success handling.
Does Perx Data Acquisition replace our data warehouse?
No. It sits alongside your data warehouse, collecting the signals your systems already hold so Perx Intelligence Suite can turn them into intelligence your team can act on.
Related features
More inside Perx Data Acquisition.
Checked on every request
Sender credentials, account status, agreed volumes and permissions are verified before any signal moves.
Offline event capture
The Perx SDK holds in-app events while a device is offline and sends them when it reconnects.
Replay and partial-success handling
A batch with a few bad rows still loads the good ones. Failed rows can be replayed once fixed.
A receipt for every signal
Each sending system gets an acknowledgement as soon as its signal is safely on the stream, so it never waits on downstream processing.
Consent and channel permission events
Consent changes are collected per customer, so every downstream screen, export and handoff can enforce them.
Separate by design
Every record is tagged to your organisation at check-in, so your data never mixes with anyone else’s.
Built for BFSI compliance
A data layer your InfoSec team, CDO and regulator can all sign off on.
ISO/IEC 27001, ISO 27018 and SOC 2 Type II
Certified security and cloud privacy controls, with the security pack available before procurement asks.
Hashed at collection
Customer identifiers are hashed or tokenised the moment they arrive, before any processing.
Regional privacy policies
Sensitive identifiers are hashed, rejected or quarantined according to GDPR, PDPA, DPDP or POPIA.
Read-only to your systems
Perx receives data and never writes back to your core banking or source systems.
Data where your regulator needs it
A Perx-managed cloud, an on-premise collector, or fully on-premise.
Nothing silently dropped
Failed records are quarantined with their original payload, error and retry count, ready for review and replay.
Built for BFSI compliance
None of this works if compliance is
bolted on afterward
Every mechanic above ships with BFSI regulatory requirements embedded, not retrofitted — stated up front because compliance and infosec are named blockers in most BFSI buying committees, not an afterthought to raise once a deal is already moving.
ISO/IEC 27001 & 27018
Certified, audit-ready from deployment.
GDPR-compliant by design
Zero- and first-party data, no third-party dependency.
Full RBAC & maker-checker
The right approvals in place before any rule or campaign deploys.
Explore other engines
Collecting the data is step one. Here's what works on it.
AI-Powered
Segmentation, journeys, microsites and social sharing, launched without an IT ticket.
See Perx Data Acquisition in action.
In 30 minutes, we’ll walk your data team through how your sources connect, where your data can live, and how every signal reaches Perx Intelligence Suite.
An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution
SAY HELLO
Perx Technologies Pte Ltd
20A Tanjong Pagar Road
Singapore 088443
An ISO/IEC27001:2013 and ISO 27018:2019 compliant cloud solution
An ISO/IEC27001:2013 and ISO 27018:2019 certified cloud solution