HomeGuidesAPI Reference
Log InTalk to Sales
Guides
Talk to Sales
Start typing to search…

Release November 2025 - v7.21

Learn about the new releases in Loyalife

1. Pay with Rewards - APIs

  • New APIs Added to accommodate Pay with Rewards feature: Create Redemption API, Cancel Redemption API, List Redemption API, and Get Redemption API.
  • Create Redemption API:
    • Users cannot create a request if the member has insufficient points, zero points, or negative points.
    • Users cannot create a request for non-existing, inactive, suspended, cancelled, or membership blocked members.
    • Users cannot create a request if the member already has an active request or if points exceed 11 digits.
    • Users cannot create a request when the validity period exceeds 90 days.
    • ValidityPeriodInDays logic: If 0 or not passed, defaults to 3 days; otherwise uses the specified number.
  • Cancel Redemption API:
    • Users can cancel a request only when status is "Pending". Cannot cancel if "Processed".
    • Appropriate error messages are returned for invalid or non-existing IDs.
  • List Redemption API:
    • Users can view requests for all statuses or filter by specific status.
    • Passing status=0 returns all statuses.
  • Get Redemption API:
    • Users can fetch specific requests by ID to view the member's current status.

2. Cashback Issuance APIs

  • As part of cashback issuance, Create, List, and Get Cashback APIs are added.
  • Create Cashback:
    • Mandatory inputs: ProgramId, RelationReference, Points, RewardType (Type is 2).
    • Member must have sufficient balance; otherwise, returns "Insufficient Point Balance".
    • Cashback request is written to txn_details_with_breakage immediately with "Pending" status.
    • JSON file generation occurs at EOD via cron, changing status to "Processed".
    • Points must be integers.
  • List Cashback:
    • Mandatory inputs: ProgramId, RelationReference, Reward Type.
    • Optional filters: Status (0 returns all), RecordsPerPage (defaults to 10 if not provided), PageNumber.
  • Get Cashback:
    • Requires CashbackId to fetch a specific record.
    • Cashback entries do not support cancellation or expiration.
    • Optional "Description" field is stored in DB but excluded from the JSON file.

3. Consume Data based on DateTime

  • Users can pass date & time data in YYYY-MM-DD HH:MM:SS format in both API and file uploads.
  • If the date is passed only in YYYY-MM-DD format, it is stored as YYYY-MM-DD 00:00:00.000.
  • Note: Throughout the application, date selection is still based on date; the time picker is not implemented.

4. Pay with Rewards - Transaction File Processing & Redemption Matching & Pay with Rewards Feature

  • File generation and processing cron job implemented to handle the redemption process.
  • Can be triggered by sending a local datetime attribute; runs based on transaction date even if not in the cron schedule.
  • Runs for a specific program (supports on-prem client only).
  • File generation format: YYYYMMDDHHMMSSCashBackFileGeneration.json (contains dates in YYYYMMDD format).
  • Accrual transactions after a request are considered for redemption (sorted by date/time). Transactions before the request are ignored.
  • Decimal values are ignored and treated as spoilage points.
  • "Debit by redemption" filter in transaction reports fetches Pay with Rewards/Cashback records.

5. Cashback File Generation for Pay with Rewards / Direct Cashback

  • Cashback file generation is available for Pay with Rewards and Direct Cashback.
  • Card Number is treated as the Reference Number.
  • Transaction Code is MP-MPAYM-G02 for all cashback transactions.
  • Redeemed points calculated based on cashback rate defined in program settings.
  • Currency is hard-coded as 404.
  • Transaction Date is blank (redeemed immediately); Posting Date is the same as the cashback request date.
  • Transaction Reference Number and Custom fields are blank.

6. Enable Hand back File Generation with Success Logs for All File Types (TXN, CPD)

  • Enhanced hand back file generation to include success logs for TXN & CPD file types.
  • TXN files: Error code is hidden; only detailed error messages are shown.
  • CPD files: Both error code and error message are visible.

7. Add Regex Pattern Matching and Transformation to Pre-Processing Operations

  • Pre-processing now uses regex to trim spaces in customer transaction/CPD files before Loyalife processing.
  • Regex converts date formats (ddmmyyyy/mmddyyyy) to the required yyyy-mm-dd format (time cannot be changed).
  • Handles conversions like changing preferred language codes.

8. Support Custom Date Range Generation in Custom Report Module

  • A new "Generate" button allows users to generate data between two date ranges (Start Date, End Date).
  • Existing reports must be updated as older SQL queries lack the new parameters.
  • Only Admin users can create custom reports. Users with "Create Report" permission can share/delete/generate. Users with "View Report" permission can only view/generate/download.
  • Parameters must use {{startDate}} and {{endDate}} format.

9. Create Redemption Report under Custom Report Module

  • New "Redemption Report" available under Reports → Custom Reports with date range support.
  • Requires bin_number attribute to be present under member attributes.
  • Exposes cash_equivalent_points from redemption transaction JSON for "Purchase Points Used".
  • "Earned Points Used" is automatically computed as (Total Points Redeemed - Purchase Points Used).

10. Expose Maker-Checker Add/Remove Points feature Report via Custom Report Module

  • Monthly custom report generated on the 1st of every month (previous month's data).
  • Captures Checker ID (user who approved/rejected) and Description (merchant name).
  • Status shows "Pending" if currently with checker or approver.
  • "Decision Time" is blank if the request is pending.
  • Supports manual generation via start/end date.

11. Generate Member Audit Report from Member Audit Log - Custom Date compatible query

  • Monthly generated report (1st of month for previous month's data).
  • Requires member attribute bin_number (string, non-mandatory/unique). If empty, the field appears as null.
  • Fixed columns: Member ID, Bank Identifier, Activity, Date, Time, IP, Device/Browser (data sent by storefront).
  • Supports manual custom report generation via start/end date filters.
  • Headers are now present in the custom report.

12. Create Bonus Report under Custom Report Module to Include BNS, Manual Bonus & Miscellaneous Point Debits

  • Pulls data from three sources: BNS File Transactions, Manual Bonus Additions, and Miscellaneous Point Debits.
  • Columns: Member ID, BIN, Creation Date, Bonus Points, Bonus Type, Narration, and Description.
  • Supports custom Start/End Date parameters and monthly scheduling.
  • Handles invalid date ranges and no-data scenarios; includes Excel export capability.

13. Introduce Identifier for Manual Point Adjustments (Single & Bulk Add/Remove)

  • All transactions created via Add/Remove Points now include the prefix "Manual Adjustment" in the narration (e.g., "Manual Adjustment – Bonus Points").
  • Existing narration values remain unchanged but are prefixed.
  • Updated narration is visible in Transaction Summary, Exports, and Reports.
  • Users can filter by keyword "Manual Adjustment" to isolate these entries.

14. Create Monthly Custom Report – Member Points Movement Summary MTD

  • Monthly report showing points movement for members (e.g., 1st to 30th).
  • Columns include: Member Relation Reference, Date (Range), Opening Balance (1st of month), Accrued Miles, Redeemed Miles, Expired Miles.
  • Includes "Adj Miles Back (Credit)" and "Adj Miles Back (Debit)" for points modified via Bulk Upload or Manual Add/Remove.
  • Closing Balance reflects status as of the last day of the month.

15. Custom Summary Report - Under Custom Report Module

  • Displays summary columns per member: Member ID, BIN, Last Update, Status.
  • Point Breakdowns: Purchase Points (Type 4), Bonus Points, Earned Points (Type 1 excluding Type 4), Redeemed Points.
  • Totals: Total Points Available, Total Purchase Points Available, Total Earn Points Available.

16. Enable Maker & Checker comments for Manual Add/Remove Points (Maker-Checker flow)

  • If maker-checker is enabled, a separate section allows the maker to input comments during Add/Remove requests.
  • This value appears in the maker-checker request description (not in the approve changes section).
  • Audit trail remains unchanged (captures verifier/approver comments, not maker comments).

17. Add Member Activity code in LBMS DB (prod)

  • Available Activity Codes: PayWithRewards (168), PointsTransfer (169), Cashback (170), SportBooking (171), SportSearch (172), SportDetails (173).
  • Activities are passed via InsertMemberActivityWithSessionID and InsertMemberActivity APIs.
  • No validation for mapping codes to descriptions (e.g., user can pass code 168 for PointsTransfer).
  • Activities can be exported via the Member Activity export feature.

Updated about 1 month ago