This release makes it easier for API integrations to take deposits with Xero, gets Benji Pays ready for British Columbia’s move to permanent Pacific Time, and smooths out the deposit dialog.

New API capabilities

List Xero accounts for deposits

Integrations connected to Xero can now request the list of valid accounts to use when taking a deposit: revenue accounts for prepayments and bank accounts for overpayments. Instead of looking up account details separately, API consumers can pick the right account straight from Benji Pays, making deposit charges quicker to set up and less error-prone.

New permission for accounting accounts

A new read permission for accounting accounts is now available on the API access settings page, so admins can choose exactly which API keys can see this list.

Ready for B.C.’s permanent Pacific Time

Schedules stay on your local time after Nov 1

British Columbia is keeping its clocks at UTC-7 year-round starting November 1, 2026. We’ve updated our time zone data so merchants in B.C. keep getting Auto Processing runs, email reminders, and other scheduled activity at the local time they’ve chosen, with dates and times shown correctly.

Bug Fixes

Take a Deposit opens cleanly

The Take a Deposit dialog no longer shows an error message when it opens before a customer is selected. Picking a customer loads their payment profiles as usual, and the Send button stays off until a customer and card are chosen.

Behind the scenes

We’ve also laid the groundwork for upcoming webhook support, expanded automated testing for Business Central, nightly payment processing, and time zone handling, and improved our support documentation tools. These updates help us deliver reliable releases and keep everything running smoothly.

This release prevents avoidable Business Central payment errors, gives API integrations a reliable way to recover charges, and keeps payments running smoothly behind the scenes.

Business Central (coming soon)

Payments wait for the invoice posting date

Benji Pays now checks a Business Central invoice’s posting date before taking payment. Invoices dated in the future can’t be paid until that date arrives, so customers are no longer charged for payments that Business Central would later reject. Merchants will see the Pay option disabled with an explanation, the customer portal hides these invoices until they’re payable, and automatic processing skips them without turning off processing for the customer’s other invoices.

Posting dates available through the API

Business Central invoices returned by the API now include their posting date, and charge requests for invoices that aren’t yet payable return a clear error. This helps integrations know in advance when an invoice is ready to be paid.

New API capabilities

Recover a charge using its idempotency key

Integrations can now look up a transaction by the idempotency key used to create it, even long after the original request. If a response is lost due to a timeout or crash, your system can confirm what happened instead of retrying blindly. Repeating a charge with a key that has already been used now points you to the existing transaction rather than risking a duplicate payment.

Security

Important security update applied

We’ve applied an important security update to core platform components to keep Benji Pays protected against a recently disclosed vulnerability. The update is already in place, and there’s nothing merchants or customers need to do.

Behind the scenes

We’ve also moved our Bambora payment connections to Shift4’s new web addresses ahead of the old ones being retired. This update helps keep payments running smoothly, with nothing for merchants to change.

This release expands API capabilities and makes invoice payments and Business Central workflows more reliable.

New API capabilities

• Integrations can retrieve processor-specific saved-payment tokens alongside masked payment details. These tokens provide a secure reference to stored payment methods without exposing card numbers, security codes, or gateway credentials.

• Integrations can programmatically manage supported customer settings for Invoice Rover, automatic payment processing, and the customer portal, subject to existing permissions and plan availability.

• API invoice charges now use a more consistent payment, accounting, and receipt workflow. Integrators receive clearer results when follow-up steps fail, better status information for queued bank payments, and improved protection against duplicate charges after payment capture.

Business Central Improvements

• Invoice payment links now load affected Business Central invoices correctly while continuing to verify currency compatibility.

• Links opened while reviewing or voiding posted payments now direct merchants to the correct Business Central company, removing the need for manual navigation.

Faster onboarding

Support and activation teams now receive specific Elavon validation messages when available, making configuration and permission issues easier to identify and resolve.

Behind the scenes

We also improved release automation, platform upgrade handling, and integration-test diagnostics. These changes support more consistent staging deployments and faster identification of release issues.

This draft reflects functionality currently on Staging and Demo. Please review the wording and confirm production availability before customer publication. Frill is currently unavailable, so no Frill draft was created.

This release gives merchants more control over payment workflows, improves settlement reporting, and makes several Business Central processes more reliable.

Business Central improvements

A quick reminder for everyone. Our Business Central integration is available only in beta and is still missing some key features. A select group of merchants are helping us test it but it is not yet ready for general release.

Target email reminders by payment term  

Choose which invoice payment terms are included in each reminder rule, including invoices with no payment terms. This helps ensure customers receive reminders that match your collection strategy.

Simpler gateway setup  

Unused settlement-bank fields are now hidden when configuring legacy gateways, removing misleading requirements while preserving the information needed for Benji Payments.

Complete surcharge handling during voids  

Voiding or reversing a payment now also removes or reverses its surcharge journal entry, keeping accounting records balanced and reducing manual corrections.

More accurate settlement-account validation  

Benji Payments settlement accounts are now correctly validated as Business Central bank accounts. This prevents false configuration warnings and avoids valid report lines being skipped.

Payments and reporting

Broader support for SEPA payments  

SEPA payment forms now collect and validate billing addresses across merchant checkout, the customer portal, and payment links. Customers using non-EEA SEPA IBANs can now complete payments that require an address.

Estimated settlement dates in CSV exports  

Transaction Reporting CSV downloads now include the estimated settlement date shown in the on-screen report, using your company’s local date. This makes cash-flow planning and reconciliation easier.

Filter API transactions by payment location  

API consumers can now filter transactions by where a payment originated, including the merchant app, customer portal, payment portal, and API. This enables more precise reporting, reconciliation, and troubleshooting.

Behind the scenes

We’ve also improved Business Central support reporting, custom-pricing administration, release automation, and platform dependencies. These updates help our teams investigate issues, manage merchant accounts, and deliver reliable releases more efficiently.

This release strengthens payment security, improves API consistency, and makes several support-led processes more dependable.

What's Improved

Enhanced fraud protection for hosted payments  

Customers using protected payment portals will complete a reCAPTCHA check before entering card details, helping prevent automated card testing without adding repeated prompts during a normal payment.

More flexible payment-link routing  

API integrations can now select payment options using gateway capabilities, making multi-gateway configurations easier to maintain while preserving existing store-based routing.

Cleaner monetary values in API responses  

Transaction, allocation, refund, and void amounts are now consistently rounded to two decimal places, giving integrations cleaner and more predictable financial data.

Important Fixes

More reliable bank-profile migrations  

We corrected an issue that could prevent ACH bank profiles from transferring successfully during support-led migrations to Benji Payments.

Smoother account and payout operations  

Support teams now have safer tools for transferring billing information between replacement accounts and collecting chargeback fees without unnecessarily delaying merchant payouts.

Behind the Scenes

We’ve expanded automated testing, added earlier checks before changes are merged, and improved failure notifications. Together, these updates help us identify regressions sooner and deliver more reliable releases.

New Features

Business Central, now with a simpler plan choice

Business Central merchants will see the Elite plan automatically selected, making signup clearer and preventing incorrect plan selections.

Payment links arrive in Business Central

Business Central merchants can now access and copy generic, gateway-specific, and integration payment links from Settings, making it easier to share the right payment experience.

Collect prepayments through the API

Integrations can now securely charge a stored payment method for deposits, retainers, and other prepayments before an invoice exists. Built-in retry protection helps prevent accidental duplicate charges.

More accurate subscription taxes

Subscription tax settings can now reflect the correct billing jurisdiction even when a merchant uses a different customer-facing address.

Bug Fixes

Stronger safeguards for saved payment methods

The customer portal now takes additional steps to ensure a saved payment method belongs to the customer or an authorized related profile before it can be used, adding another layer of protection while preserving supported parent and job workflows.

Quiet improvements behind the scenes

Various fixes improve onboarding account tracking, Benji Payments application migrations, and QuickBooks Online processing. These changes do not directly alter customer workflows, but they help keep everything running smoothly behind the scenes.

New Features

Smarter Business Central invoice processing

Clearer Auto Processing guidance now explains which invoices are eligible, while unposted invoices are kept out of payable workflows. This helps prevent avoidable payment errors and keeps processing focused on invoices that are ready to be paid.

Stronger protection for payment sessions

Elavon and Global Payments checkout flows now have improved reCAPTCHA protection earlier in the payment process, helping prevent automated card-testing attempts without adding another challenge for legitimate customers.

More flexible Benji Payments pricing

Tiered pricing can now apply percentage-based fees only to the portion of a payment above a configured threshold, including ACH payments.

Bug Fixes

Disabled payment profiles stay disabled during migration

Disabled Bambora bank profiles now retain their disabled status when migrated to Benji Payments, preventing unintended use and reducing manual cleanup.

Stronger reliability behind the scenes

Various fixes improve authenticated API response handling, real-time connection resilience, and development environment consistency. These changes do not directly affect everyday workflows but help keep Benji Pays secure and running smoothly.

Payments are getting tougher on abuse and easier on everyone else. This release strengthens payment security, expands billing flexibility, and smooths several everyday workflows.

New Features

Stronger payment protection

New reCAPTCHA safeguards help prevent card testing across Benji Payments and Stripe payment flows. Attempt-aware validation and dedicated rate limits protect legitimate customers from abusive traffic without getting in the way of valid retries.

More billing currencies

SaaS plans can now be presented and billed in CAD, USD, GBP, or EUR based on the merchant’s billing currency, with currency-specific pricing and the appropriate payment experience.

Safer support for Benji Payments applications

Authorized support staff can now move boarding applications between companies through a protected, verified workflow. This reduces turnaround time while preserving validation and activity records for both companies.

Bug Fixes

More reliable intentional API payments

Merchants can explicitly charge a valid saved payment method through the API even when that method is excluded from automatic processing. Scheduled collections remain protected.

Clearer Elavon payment pages

Customers using EPG/Elavon now see merchant-configured payment notices, including important surcharge information, directly above the payment form.

Faster recovery from accounting disconnections

Merchants receive one clear notification when QuickBooks Online or Xero credentials stop working, along with a direct action to reconnect.

Customer notes work for permitted merchant users

Users with the appropriate company permissions can once again create and edit customer notes without receiving broader support access.

Payment profiles load the first time

The Payment Profiles page now displays profiles on the initial visit instead of occasionally requiring a second search.

Plus

Behind the scenes, we also strengthened trusted-IP rate limiting and improved payment-profile migration reliability.

Business Central workflows just got a useful tune-up, with payment terms easier to find and customer email settings easier to understand. We have also strengthened the tools our teams use to onboard and support merchants behind the scenes.

New Features

Payment terms, right where you need them

Business Central merchants can now view payment terms by name across Manual Processing, customer invoices and Temporary Payments. Payment terms can also be searched, filtered and sorted, making it quicker to review invoices and apply payments with confidence.

User Experience

Clearer customer email controls

Updated labels and guidance now make it clear that a customer's email setting applies to all Benji Pays emails, including receipts, reminders, invoices, statements and general messages. The behaviour has not changed; it is simply easier to understand before making an update.

Bug Fixes

Smoother support and onboarding behind the scenes

We have improved Business Central diagnostics, support-led gateway setup, payment-profile migrations and Benji Payments account configuration. These changes do not alter day-to-day merchant workflows, but they help our teams investigate issues faster, reduce onboarding delays and keep payment setup running reliably.

Payments just got a little tougher on trouble and a lot smoother for everyone else.

This update strengthens payment data protections, improves invoice delivery and billing reliability, and tidies up several everyday payment experiences.

New Features

OneBill invoice PDFs, right where customers need them

Merchants using OneBill can now configure it as their invoice PDF source. Customers receive the right documents in invoice emails, payment receipts, and portal views, with accounting fallbacks preserved when needed. See the Integrations screen for setup.

More focused help with portal name changes

Authorized support staff can now help rename a merchant portal without requiring broader account permissions. Existing validation, uniqueness checks, cache updates, and audit logging stay firmly in place.

Security

Stronger privacy for payment profiles

Customer payment data gets stronger protection in API responses. Merchants and support teams still have the masked information they need.

Smarter protection for public payments

Solved reCAPTCHA challenges have a reduced lifetime. Legitimate customers still get several retries, with a fresh challenge requested only when needed.

Fairer rate limits on custom portal domains

Custom merchant domains now identify the actual payer behind each request instead of grouping visitors under a shared network address. Abuse protection stays active without legitimate customers collectively running into the same limit.

Bug Fixes

Long customer names no longer interrupt checkout

First-time payment setup through Global Payments now handles QuickBooks customer names that exceed the gateway's reference limit. References are shortened safely, while existing stored payment profiles remain unchanged.

Better logo sizing in Outlook

Merchant logos in account summaries, invoice reminders, and payment-method update emails now include Outlook-friendly dimensions, keeping branding neatly sized across email clients.

A smoother-running platform behind the scenes

Various improvements strengthen merchant split migrations, deployment connections, and bank-profile migration tools. These updates do not directly change the customer experience, but they help support safer operations and keep Benji Pays running smoothly.