Data collected
Account and merchant details needed to operate the service, connected transaction records, programme actions, consent records and security signals.
Security and consent
Clear data boundaries are part of the product.
EzMarket explains what data supports a connected programme, why it is needed and what participating merchants should not receive.
PilotWhy it is collected
To process authorised flows, link qualified activity, prevent fraud, support the account and prepare merchant-scoped reporting.
Merchant scope
A participating merchant receives programme information for its own authorised activity—not a shared customer directory across merchants.
Consent choices
Payment participation and optional marketing permission must be explained separately. Optional marketing consent can be withdrawn.
Retention
Records should be retained only for operational, security, dispute and legal needs under an approved retention schedule.
Qualification checks
Pilot rules cover settlement status, agreed refund windows, duplicate referrals and suspicious activity before an outcome is treated as qualified.
Planned
Refund and reward checks come before wider rollout.
The pilot must show how refunds change rewards and the amount left for your business, including any refund adjustment pending. These checks and complete reporting still need to be verified before wider use.
Not shared across merchants
Your customer record stays with your business.
EzMarket does not present one merchant with another merchant’s customer list, programme history or private transaction details.
Merchant pilot
Ready to bring customers back?
Tell us a little about your business. Checking your fit does not create a paid commitment.