Release Notes for June 22, 2026: More Payment Visibility, Smarter Recovery, and Cleaner API Docs

This week's update has some small but valuable improvements, and back end groundwork for the upcoming API release.

Feature Updates

Transaction reporting is now available through the API  (groundwork)

Developers can now retrieve organization payment transactions through the Benji API, including filters for status, type, customer, gateway, amount, invoice, surcharge, settlement details, voids, refunds, and invoice allocations. It brings more of the merchant transaction table into API-friendly form, so reporting and integrations can do more without manual exports.

Stripe card declines now feed Payment Method Update flows  

Stripe card declines can now create payment update events, helping Benji identify when a saved payment method needs customer attention. That means better follow-up when cards are expired, invalid, blocked, or repeatedly declining, while transient gateway problems are handled separately.

Benji Payments enhanced card data is cleaner and more precise  

We tightened how enhanced card transaction data is prepared, including line quantities, unit prices, surcharge descriptions, and minimum tax handling. The result is cleaner Level II/III payment data for Benji Payments transactions.

Bug Fixes

QuickBooks Online empty results no longer trip nightly processing  

Nightly processing now handles empty QuickBooks Online invoice or customer query responses more gracefully. When QuickBooks returns no matching records, Benji Pays now treats that as an empty list instead of letting the process crash.

QuickBooks Desktop sync locks recover faster  

QuickBooks Desktop sync locks now use a shorter default lock window, while still respecting company-specific sync intervals. If a connector stops polling, stale locks can clear sooner without changing the normal QuickBooks Web Connector reconnect timing.