Release Notes

October 12, 2026

CHANGED
Trip resolution requests go to the Trip Resolution service’s own host instead of the licensing API proxy. Request and response are unchanged.
FIXED
countryCode and promotionSlugs on BRScanOptions are declared nullable, which removes the nullability warning customer apps saw when compiling the SDK headers. In Swift they are now String? and [Any]? instead of implicitly unwrapped optionals.

September 24, 2026

FIXED
A scan could freeze after the user chose to retake the photo from the missing fields prompt in the standard camera UX, and the only way out was force quitting the app. The retake now returns to the camera and completes.
FIXED
Receipts could finish with no data when a Scan API request failed. The Scan API is reached at scan.blinkreceipt.com again, a failed request is retried once and no longer blocks the remaining frames of the scan, and a classifier that returns no result is no longer counted as “not a receipt”. Falling back to on-device OCR after a failed retry is a separate follow-up.
CHANGED
Scan results handed to BlinkEngage now carry scan diagnostics (failure codes and frame counters), and Scan API requests record why a scan was routed to the server. Backend persistence of the diagnostics is in progress.
CHANGED
The BlinkEngage bridge passes the host view controller when a scan session starts. BlinkEngage 1.14.0 will require BlinkReceipt 1.76.0 or later.

September 1, 2026

FIXED
Scanning a second receipt without fully leaving the scanner returned the first receipt’s data instead of its own, wrongly flagging valid receipts as duplicates and risking denial of a user’s reward. This was the leading cause of the false duplicates found in recent testing. Each scan now returns its own data, removing that cause.
ADDED
isReturn: receipts flag whether they’re a return, right on the receipt object, and it defaults to false. It introduces no breaking changes.
CHANGED
This release includes parser v1.55.1.

August 12, 2026

CHANGED
Stability improvements and performance enhancements.

July 20, 2026

ADDED

BlnkEngage Improvements
Monetization (BlinkEngage) scans now verify that the total, merchant name, and purchase date are present before submission. If any are missing, a drawer prompts the user to retake the photo or enter values manually. If every missing field is recovered by retake, the scan submits as normal; if any field is entered manually, the scan routes to a blocking screen and is not submitted to BlinkEngage. Non-monetization scans are unaffected..

July 1, 2026

ADDED

Fuel Extraction Improvements
Improved fuel grade extraction accuracy and reliability.

Stability Improvements
Resolved a crash that could occur when processing specific receipt formats.
General performance and stability enhancements.

June 12, 2026

ADDED

Improvements
Enhanced barcode extraction to improve barcode recognition and reliability across supported receipt formats.
Improved duplicate detection accuracy to better identify duplicate submissions while reducing false positives.