Release Notes: August 9

Loyalty

Get Reward Details in check/rewardDetails.json Endpoint

This endpoint obtains detailed information about a reward wallet’s configuration, including applicable item IDs and reward conditions. Added detailed documentation for check/rewardDetails.json in our developers.paytronix.com API documentation.

Guest Web Reverse Enroll Canadian Postal Code Validation via Google Maps API

Canadian guests will no longer face issues with postal code validation on reverse enroll. Leveraging the Google Maps API, we have integrated an automated fallback system that ensures postal codes are verified even if they are not present in our database. This enhancement makes sure Canadian postal codes are accurately validated to improve user experience. For cases where the postal code isn't found in the database, the API validation kicks in as a last resort, updating our database with any new postal codes.

Loyalty 

Consistency in postAndAccruePoints API Responses

To align with Oracle Simphony's integration, modifications were made to the postAndAccruePoints API responses. The noWorkSuccess response will now include a responseCode field with a value of 200, ensuring consistency with the success response. This change addresses Oracle's assumption that all API responses contain a responseCode, which led to endless retries on their end. This update will help prevent future issues with their integration while considering the behavior of other API endpoints.

Messaging

Support email replacement parameter for SMS registration messages

We've enhanced the SMS registration process by adding support for email replacement parameter. Previously, the doSmsEmailRegister() flow did not include email as a replacement parameter, unlike the doEnroll() flow, which supported an array of parameters including card number, email, phone number, and keyword. Now, doSmsEmailRegister() also supports the email parameter, aligning both flows and ensuring a more robust handling of SMS registrations.

Self XSS in Email Builder (Text Editor)

We've implemented a new validation feature to enhance security when adding HTML content to emails. This update includes a safeguard that prevents cross-site scripting (XSS) payloads, ensuring a safer and more secure experience for all users.