# Loyalty integration through Fynd Engage

Learn how a third-party loyalty program integrates with the Fynd storefront and Store OS (POS) through Fynd Engage. This guide covers the routing contract, redemption lifecycle, and webhook events that your integration consumes.

## How the integration works

Fynd Engage is a provider-agnostic loyalty hub. The storefront and POS communicate only with Engage. For each sales channel, Engage decides whether loyalty is served by its native engine or routed to an external provider. Engage then translates each request and response between the two schemas.

Your system implements a fixed adapter contract. No storefront-side changes are required.

1. **Storefront and POS** - Provides checkout, wallet, and customer screens across web, app, and Store OS. These surfaces call the Engage contract and never call the loyalty partner directly
2. **Fynd Engage** - Resolves the configured provider, maps values to the partner API, routes synchronous requests, and forwards mapped commerce events
3. **Loyalty partner** - Owns balances, redemptions, earn rules, and tiers. The partner exposes adapter methods and consumes emitted events
4. **Fynd Commerce events** - Provides order, shipment, user, and coupon events that Engage maps and forwards to the loyalty partner


## Explore the integration guide

Architecture and flow
Understand provider resolution, synchronous API routing, asynchronous events, and the complete integration flow

API contract
Implement the required Engage capabilities, adapter methods, and provider mappings

Redemption lifecycle
Follow a cart from wallet lookup and redemption hold through confirmation or timed reversion

Webhooks
Consume order, shipment, and user events and apply the correct loyalty action for each status

Coupon rewards
Issue customer-scoped coupons through Fynd Commerce and track coupon creation and redemption

Implementation checklist
Confirm that your adapter, holds, webhooks, shipment accounting, and credentials are ready

## Integration traffic

Traffic runs in two directions:

- **Synchronous APIs:** The storefront calls Engage, Engage maps and routes the request to the loyalty partner, the partner responds, and Engage maps the response back.
- **Asynchronous events:** Fynd Commerce webhooks flow into Engage. Engage maps order, shipment, and user events before emitting them to the loyalty partner.


Continue to [Architecture and end-to-end flow](/engage/partner-integrations/architecture) to understand the request and event paths.