Release notes for June 15, 2026: Laying the Groundwork
We’ve bundled a healthy run of recent Benji Pays improvements into one tidy update: sharper payment data, clearer API behaviour, better accounting-system fit, and more dependable payment workflows.
This batch is especially good news for teams using the Partner API, QuickBooks, Business Central, Xero, Benji Payments BACS, and recurring or scheduled payment flows. Less guesswork, more clarity, and a sturdier foundation under the hood.
Groundwork for Upcoming Features
More useful Partner API coverage
The Partner API has grown with more complete organization, settings, gateway, customer, payment method, and invoice behaviour. That means partners and internal teams get cleaner, more predictable data shapes and better documentation for building against Benji Pays.
Named API keys
API keys now need a clear, merchant-facing name when they are created, and that name appears in API access lists. It is a small quality-of-life upgrade with a big payoff: fewer mystery keys, easier housekeeping, and clearer support conversations.
Better payment-event tracking
Recent Payment Method Update work expands the foundation for detecting and acting on payment declines across more gateway flows. Some of this is still behind configuration or operational rollout, but it moves Benji Pays closer to smarter card-updating and payment recovery workflows.
Safer deployment
The engineering team has continued improving blue-green deployment paths and release pipeline reliability. This is mostly behind the scenes, but it supports safer, smoother releases over time.
Bug Fixes
Clearer Benji Payments BACS and SEPA timing
Advance-notice messaging has been tightened up so merchants and customers see timing that better matches the selected payment profile or scheme default. For UK merchants using Benji Payments BACS, that means payment, deposit, and instalment-plan flows are clearer and more trustworthy.
Safer batch and scheduled payments
Batch auto-pay now coordinates better with invoice locking when locking is enabled, reducing the risk of overlapping payment attempts. Scheduled payment handling has also been improved for parent and sub-customer invoice scenarios, so the right saved profile can be used in the right place.
More resilient accounting and reporting workflows
QuickBooks Online report parsing is more tolerant of updated report response shapes, helping protect A/R, revenue, dashboard, and reconciliation workflows. Xero reconnect behaviour and accounting-report reliability have also been tightened up across recent releases.
Sharper invoice and customer handling
Invoice sorting, customer lookup, and dashboard/reporting paths have been cleaned up so data is easier to query, sort, and display correctly. Invalid API sort values now return clearer errors instead of quietly doing the wrong thing.