Skip to main content
The platform’s architecture separates read and write paths. Balance enquiries and transaction history are served from the database read replica, while redemption and earn operations execute against the primary database.
The platform’s architecture separates read and write paths. Balance enquiries and transaction history are served from the database read replica, while redemption and earn operations execute against the primary database. In a scenario where the primary write path is unavailable but the read replica remains healthy, balance and history queries would continue to return results. However, this is not exposed as a formally declared “read-only mode” with a user-facing degradation banner or automatic failover toggle. Implementing a declared degraded/read-only mode, where balances and history remain visible, redemption is disabled with a user-facing message, and the system automatically transitions when write-path health checks fail, can be scoped as a configuration enhancement during the implementation phase. Learn more: Xoxoday Loyalife Help Centre

Can customers view their redemption history and point...

Xoxoday Loyalife gives members real-time access to full redemption history, point balances, and transaction records on web and mobile…

Can I set up a white-labeled storefront for redemptions?

Xoxoday Loyalife supports a fully white-labeled, mobile-responsive redemption storefront that mirrors your brand identity and processes redemptions…