Beta’s On: ConnectWise Is Live, BACS Gets Smoother, and Benji Payments Gets Sharper
Fresh updates to Benji Pays are here.
This release brings smoother scheduling, cleaner payment handling, and a few important fixes that make day-to-day workflows feel more reliable across Benji Payments.
New Features
ConnectWise Beta Is Now Live for All Users — The ConnectWise customer and contact import is now live in Beta for all users, with clearer in-product labeling so teams know exactly what’s ready to explore. For setup details, syncing behavior, customer mapping, and PDF priority configuration, customers can use our ConnectWise PSA invoice PDF integration guide.
BACS Advance Notice Improvements for UK Merchants — Benji Payments BACS can now better handle multiple scheduled advance notice payments for the same invoice in a single batch run, with cleaner linking between notice and payment records for a clearer audit trail.
Customer Portal Scheduling for BACS and SEPA — Customers can now schedule payments more reliably when an invoice already has a scheduled BACS or SEPA advance notice payment attached.
Future Release Groundwork for API Security — We’ve laid the groundwork for upcoming API key expiration controls, which will give merchants more flexibility over integration security in a future release.
Bug Fixes
Payment Event Cleanup After Success — Successful payments now clear related open payment events more cleanly, helping reduce confusion around outdated declined or retry records.
Elavon and Converge Surcharge Reliability — Fixed an issue in the customer portal that could prevent surcharge and debit-card checks from completing correctly in some Elavon and Converge payment flows.
Benji Payments Decline Handling — A generic bank decline will no longer incorrectly disable a customer’s saved payment profile, helping prevent unnecessary disruption after softer declines.
New User Setup Fix — Resolved an onboarding issue that could trigger an error before account details had fully loaded.
OTP Localization Fix — Fixed a timing issue so one-time passcode and 2FA text loads with the correct translations more consistently.