Points
Connect eligible purchase values to the configured earning rules and display the resulting balance.
Integrate Fair Loyalty with your website, POS or customer app through the API. Keep your existing customer experience and connect eligible purchases, member progress and rewards to one loyalty program.
Compatibility depends on your system’s API access and the Fair Loyalty operations available to your integration.
A reference integration flow. Validate the endpoints and permissions for your account before implementation.
Connect the mechanics that fit your program. Confirm each operation and rule against the current API contract.
Connect eligible purchase values to the configured earning rules and display the resulting balance.
Record qualifying visits or purchases and show progress toward a defined milestone.
Read eligible rewards and connect redemption to your checkout flow after authorization.
Link your customer identity to a loyalty account and surface the digital card or membership view.
Connect enrollment and qualifying order events. Present loyalty progress inside your current account area.
Use an adapter for supported checkout events. Map purchases, refunds and member identification to the documented operations.
Surface balances, progress and eligible rewards inside your own interface, using authorized server-side requests.
Keep credentials on your server. Your adapter translates business events, applies the documented request contract and returns the outcome to your interface.
{
"source": "pos",
"event": "purchase.completed",
"business_reference": "morrow-cafe",
"member_reference": "member-0084",
"purchase": {
"amount": 24,
"currency": "QAR"
},
"external_transaction_reference": "sale-0026"
}Keep secrets out of browser code and mobile bundles. Scope access to the intended business and operations.
Define how customers, businesses, branches and external transaction references map to the loyalty account.
Choose a documented deduplication approach. Confirm idempotency support before retrying a purchase or redemption.
Check available refund and cancellation operations so a reversed sale does not leave incorrect loyalty progress.
Exercise enrollment, earning, balance refresh and redemption with authorized test accounts.
Monitor failures and reconciliation. Avoid logging customer personal data or credentials unnecessarily.
Start with the available guides. The API reference and integration-specific examples will be linked here as they are configured.
Understand the program configuration before connecting transaction events.
See how member identification, purchases and redemption fit checkout.
Explore the agent-facing workflow and permission considerations.
Systems that expose suitable APIs, events or integration hooks can be connected through an adapter. A closed system may need vendor support. Compatibility is assessed against the available operations rather than assumed.
The integration approach keeps your current interface. Your backend or middleware connects supported business events to the loyalty API.
No. The event mapping illustrates the architecture; it does not define a published endpoint, authentication format or request schema. Use the current API contract for implementation.
Share your system, the customer journey and the operations you need. Confirm the API contract, then implement and test the adapter.
Discuss your integration ↗