For developers

Connect loyalty to the systems you already use.

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.

From an existing system to a loyalty outcome

A reference integration flow. Validate the endpoints and permissions for your account before implementation.

  1. 01Website, POS or app
  2. 02Your server-side adapter
  3. 03Fair Loyalty API
  4. 04Member progress and rewards

Choose the loyalty experience. Keep your stack.

Connect the mechanics that fit your program. Confirm each operation and rule against the current API contract.

Points

Connect eligible purchase values to the configured earning rules and display the resulting balance.

Stamps

Record qualifying visits or purchases and show progress toward a defined milestone.

Rewards

Read eligible rewards and connect redemption to your checkout flow after authorization.

Member cards

Link your customer identity to a loyalty account and surface the digital card or membership view.

Build around your existing customer journey

Websites and eCommerce

Connect enrollment and qualifying order events. Present loyalty progress inside your current account area.

POS and checkout

Use an adapter for supported checkout events. Map purchases, refunds and member identification to the documented operations.

Customer apps and portals

Surface balances, progress and eligible rewards inside your own interface, using authorized server-side requests.

A clear boundary between your system and loyalty

Keep credentials on your server. Your adapter translates business events, applies the documented request contract and returns the outcome to your interface.

Illustrative event mapping · not an API request
{
  "source": "pos",
  "event": "purchase.completed",
  "business_reference": "morrow-cafe",
  "member_reference": "member-0084",
  "purchase": {
    "amount": 24,
    "currency": "QAR"
  },
  "external_transaction_reference": "sale-0026"
}

Plan a reliable integration

01

Protect credentials

Keep secrets out of browser code and mobile bundles. Scope access to the intended business and operations.

02

Map identities

Define how customers, businesses, branches and external transaction references map to the loyalty account.

03

Handle repeat events

Choose a documented deduplication approach. Confirm idempotency support before retrying a purchase or redemption.

04

Verify reversals

Check available refund and cancellation operations so a reversed sale does not leave incorrect loyalty progress.

05

Test the complete journey

Exercise enrollment, earning, balance refresh and redemption with authorized test accounts.

06

Observe outcomes

Monitor failures and reconciliation. Avoid logging customer personal data or credentials unnecessarily.

Developer resources

Start with the available guides. The API reference and integration-specific examples will be linked here as they are configured.

API referenceComing soon
Integration examplesComing soon
Webhook event catalogComing soon

Product facts and pricing ↗

Integration questions

Can Fair Loyalty connect to any established system?

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.

Do I need to replace my POS or website?

The integration approach keeps your current interface. Your backend or middleware connects supported business events to the loyalty API.

Are these code examples ready to execute?

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.

Build loyalty into your existing experience.

Share your system, the customer journey and the operations you need. Confirm the API contract, then implement and test the adapter.

Discuss your integration ↗
WhatsApp