Maintained answers · Technical and developer
Understand the application, source, APIs, updates, and extension boundary.
Questions and answers
Product behavior, requirements, pricing, and integrations can change. The contextual link in each answer is the maintained next step.
Answer 01
Direct linkNo. Reward Loyalty is a complete Laravel application with its own routes, database, member, staff, partner, and administration interfaces. The license holder receives the application source and operates it.
Read the Laravel application guide before planning an extension.
Answer 02
Direct linkThe stack changes as the product receives framework and dependency updates. Use the current technology-stack page and current requirements instead of a copied marketing-page number.
Answer 03
Direct linkUse the Agent API for scoped machine-to-machine loyalty operations. Use webhooks when another system should receive supported committed events. Use the locale REST API for product clients and member, partner, or staff session flows.
The Agent API guide and integration overview define the current boundary.
Answer 04
Direct linkYes, with a merge and testing process that protects the custom work. Keep changes small, document them, review release notes and migrations, and test the update against the customized installation on staging.
The updating guide explains backups, update paths, and custom-change responsibility.
Other answer topics
Open the cluster that matches the next decision instead of stretching one answer beyond its evidence.
Pick what runs. Your choice is stored on this device for 12 months and you can change it any time through Cookie settings in the footer.
Necessary
Session and security cookies (reward-loyalty-session, XSRF-TOKEN). Forms and sign-in break without them.
Analytics
Google Analytics counts visits and shows which pages work. Sets _ga cookies for two years.
Every cookie, purpose, and retention period: cookie policy.