Release Notes
Enhancement:
Allow Payment -> Ticket association with payment identifier
TreezPay SDK consumer creates tickets only after successful payment response received. However, if so then the ticket has to be associated with and reflect the actual integrated payment type that was performed and logged in TP service
An external api user cannot update a ticket with an integrated pay type as those conventions are reserved for internal services.
This enhancement updates the ticket with appropriate payment object
pay type
amounts (fee, tip)
timestamp
2. Sticky card Enhancement
a.Update Sticky Customer via PATCH
This feature enables customer profile synchronisation between Treez and Sticky Cards. When a customer's email or phone number is updated in Treez customer management, the system validates if Sticky is enabled, fetches the Sticky customer ID and sends a PATCH request to Sticky's API to update the corresponding attributes.
b. Refactor Sticky Balance to show balance from fetch customer api in customer management and cart profile view
This enhancement validates the implementation of real-time loyalty balance fetching from the Sticky Wallet API in both Customer Management and POS customer profile views. The change ensures that loyalty balances reflect current point totals rather than post-redemption snapshots, addressing discrepancies when redemptions occur on e-commerce channels.
c.Pass the dispensary identifier (shortname) to Sticky Cards
Sticky Cards operates at an org level, while Treez customer IDs exist at a store level. Without the dispensary identifier, Sticky Cards cannot determine which store a specific Treez customer ID is associated with, making it impossible to properly associate customer data with a non-unique Treez Customer ID for multi-location operators.
This enhances the POST call include the Treez URL shortname as Dispensary id. The identifier (shortname) has sent to Sticky Cards on customer lookup so that Sticky can determine which store a Treez customer ID belongs to.
3. Pay<>SDK Split Payments and Fee Confirmation
This enhancement supports Split payments (e.g., Cash + Integrated Payment) when using the PaySDK widget for integrated payments. Additionally, users are shown payment fee breakdowns before processing, which is standard in the native integrated payment flow.
When the split payment is done, PaySDK widget receives current balance amount (not full ticket total)
When payment completes, system records all payments including non-integrated type