Skip to main content
Plum is Xoxoday’s rewards marketplace — a catalogue of vouchers, gift cards, and experiences from thousands of brands. Loyalife integrates with Plum so that members can redeem their loyalty points directly against Plum’s catalogue without re-entering credentials.

​
How it works

When a member chooses to redeem points through the Plum catalogue, Loyalife:
  1. Validates the member’s point balance and confirms it meets the minimum redemption threshold.
  2. Creates a secure SSO session and transfers the member to Plum’s catalogue in a single click — no separate Plum login required.
  3. Plum uses a separate Redemption Rate Token to apply the correct points-to-currency conversion rate configured in your program.
The member browses and selects a reward. The redemption request flows back to Loyalife, which debits the appropriate number of points from the member’s account.

​
Authentication architecture

Loyalife uses two distinct API tokens for the Plum integration:
TokenPurposeScope
SSO TokenTransfers the user session from Loyalife to Plum (single sign-on)Authentication only
Redemption Rate TokenAPI calls related to fetching and applying the redemption rate configurationRedemption configuration only
These tokens are stored separately in environment configuration. Previously, a single shared token was used for both operations, which caused session conflicts and inconsistent authentication. The separation ensures each operation has its own security context.
Both tokens are configured by the Loyalife implementation team. Program admins do not manage tokens directly — contact your Loyalife account team if a token needs to be rotated.

​
Redemption rate

The redemption rate defines how many loyalty points equal one unit of currency when redeeming through Plum. Example: If the redemption rate is set to 100 points = ₹1, a member with 5,000 points has ₹50 in redemption value on Plum. The redemption rate is configured in Configuration → Marketplace Settings. Changes to the rate use the Redemption Rate Token and take effect for new redemption sessions.

​
Member experience

Members access the Plum catalogue from the member-facing app or web portal. The flow:
  1. Member taps Redeem Points or navigates to the rewards catalogue.
  2. The app initiates an SSO handoff to Plum using the member’s active session.
  3. Member lands on Plum’s catalogue, already authenticated, with their available redemption balance shown.
  4. Member selects a voucher or gift card and confirms the redemption.
  5. Points are debited from the member’s Loyalife account.
  6. The voucher or gift card is delivered to the member (via email or in-app).

​
Minimum redemption threshold

You can set a minimum number of points a member must have before Plum redemption is available to them. Configure this under Configuration → Marketplace Settings.

​
Member status and redemption

Only Active members can redeem through Plum. Members with Inactive, Suspended, Blocked, or Cancelled status cannot initiate a redemption session.

​
Troubleshooting

Member cannot access the Plum catalogue (session error).
  • Verify the SSO Token is valid and has not expired. Contact the Loyalife implementation team to rotate if needed.
  • Confirm the member’s status is Active.
Redemption rate is applying incorrectly.
  • Check the current rate in Configuration → Marketplace Settings.
  • Verify the Redemption Rate Token is correctly configured and not stale.
Points debited but voucher not received.
  • Check Plum’s order status for the transaction reference.
  • Redemption-related disputes between members and Plum should be raised with the Plum support team, providing the transaction reference from the member’s Loyalife transaction history.
Every successful Plum redemption generates a Debit By Redemption entry on the member’s ledger. If a redemption is subsequently reversed (e.g., unfulfilled voucher), the restored points appear as a Redemption Reversal credit. Both entry types are filterable in Transactional reports under Reports & Analytics → Transaction Category.