This release expands our API capabilities, improves payment-method update communications, and delivers a collection of accounting, payment, and merchant-support fixes.

New Features

Create flexible payment links through the API

Merchants and partners can now create secure payment links without first creating an accounting invoice. Completed payments are sent to Payments to Apply, giving teams a simpler way to collect funds while keeping control over how and when each link is shared.

Enhancements

Partner platform groundwork

We have strengthened the behind-the-scenes context carried by partner-created accounts. This lays the foundation for richer partner experiences while ensuring account creation can continue even if a connected internal system is temporarily unavailable.

More tailored QuickBooks Desktop invoices

QuickBooks Desktop invoice layouts now support additional customization for prepaid invoices, grouped line items, taxes, balances, and configurable contact and footer details.

Clearer API integration guidance

Our merchant and partner API documentation now better reflects current authentication, validation, pagination, rate-limit, and error behavior, making integrations easier to build and troubleshoot.

Smarter payment-method update reminders

Payment-method reminders now continue until a supported resolution actually occurs. Routine profile saves or disabling and re-enabling a method will no longer incorrectly mark an issue as resolved.

Customers will also see clearer wording when no other payment methods are enabled for automatic payments, while Invoice Rover records provide more accurate reasons when a reminder is skipped.

Bug Fixes

More reliable QuickBooks fee journal entries

Different Benji Payments fee types on the same payment now receive distinct accounting references. This prevents collisions that could interrupt report ingestion and improves the diagnostic details available to finance and support teams.

Better decline investigation records

Declined card tokenization attempts now point to the correct payment-call results, helping support teams trace issues more reliably without changing payment behavior.

Correct Canadian card-rate expectations

The standard Canadian credit-card commission is now consistently shown as 2.9%, while Amex and US rates remain unchanged.

Plan changes are available to authorized support users again

Support users with the appropriate permissions can once again update merchant plans, with the current plan preselected and clear feedback when the change succeeds or fails.

Various behind-the-scenes fixes also improve platform upgrade safety, dependency security, duplicate handling, and operational diagnostics. These changes do not directly affect day-to-day workflows, but they help keep Benji Pays secure and running smoothly.

A tidy round of updates is here, with more control over our Quoter integration, cleaner API behaviour, stronger gateway validation, and accounting fixes that make reconciliation a little less mysterious.

This release focuses on consistency, accuracy, and reliability across the places merchants and partners use every day.

New Features

More control over Quoter payment links

Merchants using Quoter can now keep surcharging enabled on a gateway while disabling Benji-managed surcharging for Quoter payment links. That gives merchants more flexibility when different payment flows need different surcharge behavior.

Improvements & Bug Fixes

More consistent API responses

We’ve cleaned up response shapes across partner-focused API endpoints so pagination, identity, plan, partner, organization, and error responses behave more consistently. This gives API consumers a clearer contract to build against and makes partner support simpler for internal teams.

More predictable API date filtering

Date-range searches now behave more reliably for same-day searches and one-sided ranges. This helps API consumers avoid missing records when filtering transactions, emails, invoices, and other date-based lists.

Improved Elavon Payment Gateway validation for EU merchants

Gateway validation now routes EU and North American merchants to the correct EPG endpoint, with stronger country validation and safer handling for existing gateways. This helps reduce region-mismatch validation failures during setup.

Cross-border card fees included in accounting

Benji Payments accounting reports now recognize and process cross-border card fee lines through accounting flows. This helps merchants reconcile bank deposits more accurately across supported accounting integrations.

More reliable QuickBooks Online auto-processing

QuickBooks Online token refresh handling is now safer for high-volume merchants, reducing the chance that background auto-processing is interrupted by stale refresh tokens during busy processing runs.

A sturdier sign-in experience, clearer expectations, and a little less accounting cleanup? That is a tidy release bundle.

This update gives teams more control over account security, makes the Business Central integration's beta status easier to spot, improves customer-facing communication, and smooths out Xero top-up accounting.

New Features

Company-wide MFA enforcement

Companies can now require multi-factor authentication for all users. When this setting is enabled, users need to complete MFA setup before accessing the company, including after accepting an invite or switching into that company.

More natural French customer emails

French customer-facing email wording has been polished, including payment reminders and secure customer portal calls to action. The updated wording should feel clearer and more natural for French-speaking customers receiving payment-related emails.

Coming Soon

Business Central BETA label

Business Central is now labeled as a beta accounting system. Merchants will also see a confirmation step before connecting, helping teams set the right expectations while Business Central support continues to mature.

Business Central deposit wording and support guidance

For merchants using the Business Central beta, deposit messaging is now clearer: deposits are treated as unapplied customer payments, or payments on account, rather than Business Central prepayment invoices or finance charges. This should make it easier to explain how deposits appear, how they can be applied to invoices later, and what to watch for with voids or refunds.

Bug Fixes

Cleaner Xero top-up accounting

Benji Payments top-ups for Xero merchants now post as Spend Money bank transactions instead of manual journals. That means cleaner reconciliation for top-ups and fewer accounting retries or manual cleanup steps.

Various behind-the-scenes security and dependency updates were also included. These do not directly change merchant workflows, but they help keep the platform healthier and more secure under the hood.

Things are getting a little smoother behind the scenes and a lot more reliable where it counts.

This release brings better billing-address handling for stored Benji Payments cards on Payment Links, fixes for payment-method update emails and partner trial billing, clearer reporting for accelerated settlement fees, and more useful sync logs for support teams.

New Features

More useful QuickBooks Desktop sync logs

QuickBooks Desktop sync logs now show the date window used during a sync, including the prior sync-back date at the start and the new sync date at completion. That gives Support and Engineering a clearer trail when investigating missing records or unexpected sync ranges, without changing merchant sync behavior.

Bug Fixes

Payment Method Update emails now include update links more reliably

Payment Method Update emails now generate card-update links even when Customer Portal is disabled. Template editing also warns teams when they use portal-login links that require Customer Portal, helping prevent confusing customer emails before they go out.

Partner free trials now line up with the usage month being billed

Partner/API billing now checks whether the billed usage month was covered by the merchant’s free trial, instead of only looking at the day the billing job runs. This prevents trial-covered usage from being billed just because invoicing happens after the month ends.

Behind-the-scenes release workflow improvements

Various behind-the-scenes improvements were made to deployment and rollback workflows, including cleaner reusable pipeline pieces and traffic cutover support where configured. These updates do not directly change merchant-facing behaviour, but they help keep releases easier to maintain and operate smoothly.

A little housekeeping, a little groundwork, and a lot more reliability.

This release improves accounting sync reliability, restores expected reminder processing, cleans up merchant-facing UI text, and lays more foundation for future Business Central and Merchant API work in Benji Pays.

New Features

(Groundwork) Merchant API responses are more consistent

Merchant API response shapes have been cleaned up across key endpoints, including customers, gateways, transactions, payment methods, settings, and related formatting. This prepares the API for a more predictable integration experience, with clearer naming and fewer endpoint-specific quirks.

(Groundwork) Business Central invoice attachments now follow the invoice

Business Central support now includes uploaded invoice attachments across key invoice workflows, including invoice emails, receipt emails, email reminders, customer portal invoice views, and attachment downloads. Once available, this will help supporting files travel with the invoice instead of requiring a separate manual step.

(Groundwork) Business Central surcharge accounting is more complete

Business Central surcharge handling now supports the journal entries needed across invoice payments, manual payments, and unallocated payment flows. This helps prepare for clearer surcharge accounting, stronger reconciliation support, and better handling after payment activity such as voids and reversals.

(Groundwork) Payment Method Update reminders respect company-level opt-in

Payment Method Update reminder processing now honours company-level opt-in settings, so eligible reminder jobs can be created as expected. This restores the intended path for payment method update emails instead of allowing opted-in companies to be skipped silently.

Bug Fixes

Accounting sync is more reliable

Invoice and accounting sync batching has been tightened up to reduce the chance of transient or stale invoice data appearing during sync. This also gives the Benji Pays team more reliable test coverage and fewer noisy sync-related failures behind the scenes.

Merchant-facing table labels now wait for translations

Affected tables and buttons now wait for translations before rendering, preventing raw translation keys from appearing in place of readable labels. This improves clarity across areas like Manage Users, API Access, Profiles, Email Reminders, Chargebacks, Customer Portal Auth Logs, and Payout Reports.

DevOps tooling improvements keep the Benji Pays team updated

Behind the scenes, deployment notifications now give the team clearer Slack visibility when deploys start and finish, including success or failure status. That does not directly change merchant-facing screens, but it helps keep releases smoother and easier to monitor.

A tidy round of payment polish has landed, with clearer payout details, easier payments across related invoices, ongoing work toward our API and Business Central integration, and fewer little snags getting in the way of getting paid. Nice.

This release sharpens Benji Payments profile behaviour, improves reporting clarity, and delivers several behind-the-scenes reliability upgrades that help the whole platform feel steadier.

New Features

Smoother payments across related customer invoices

Merchants can now more easily pay multiple open invoices across parent and child customer relationships, even when starting from a child invoice. The payment flow can pull together related payable invoices into one cleaner path, reducing extra clicks and making complex customer hierarchies feel a lot less twisty.

Payout details now tell a clearer story

Benji Payments payout drill-downs now surface more of the transaction detail behind a payout, including warning context when a capture did not complete successfully. That makes payout totals easier to understand and helps reduce confusing empty or incomplete payout views.

(Groundwork) Smarter Customer Portal invoice visibility for Business Central

Business Central merchants can now control which invoices appear in the Customer Portal based on invoice number prefixes. Teams can hide matching invoices, or show only matching invoices, giving merchants a cleaner way to manage what customers can see and pay. Hidden invoices are also removed from portal balance calculations, so the customer-facing portal better matches the merchant’s intended experience.

(Groundwork) More complete Business Central invoice processing  

Business Central invoice loading now handles multi-page invoice lists more reliably, so eligible invoices beyond the first page can be considered for auto-processing. For merchants with larger invoice volumes, that means fewer missed invoices and a sturdier sync experience.

(Groundwork) Business Central Level III data collection

Business Central can now collect Level III payment data, including invoice line details where available. That helps improve enhanced data coverage and supports better interchange and reconciliation outcomes for merchants using Business Central.

(Groundwork) Auto-processing forecast API  

A new API gives company admins and integrations a clearer preview of which invoices are expected to auto-process and why others may be skipped. This gives teams better visibility before automated payments run, instead of waiting until something needs investigation.

(Groundwork) Stronger protection when generating API keys

Creating a new API key now requires email OTP verification before the credential is issued. It adds one important checkpoint before organization data access is granted, helping merchants keep API access tighter and more intentional.

(Groundwork) More useful API/MCP access

The API now includes normalized organization profile access for the authenticated company, making it easier for AI and integration workflows to retrieve company details in a consistent format. Company admins can also list and inspect merchant-facing sent emails through the API, including filters and detail views, while internal/system email data stays out of the response.

(Groundwork) API key expiry reminders  

Merchants can now receive proactive email reminders before API keys expire, plus a follow-up once they have expired. That means fewer surprise integration interruptions, fewer last-minute support scrambles, and a much calmer path to keeping connected systems running.

(Groundwork) Merchant API access and invoice responses are getting steadier

New API access controls now line up with plan entitlement or approved overrides, and invoice API responses are moving toward a cleaner, more consistent structure. This is groundwork for broader API availability, helping future integrators work with fields that are predictable, stable, and easier to understand.

(Groundwork) API sorting is becoming more predictable

API sort keys now better match the response field names customers and integrators see. That makes the API easier to document, easier to use, and less surprising as the next phase of API work moves forward.

Bug Fixes

Debit cards are blocked earlier when a merchant does not accept them

When a merchant has surcharging enabled and debit acceptance turned off, debit cards are now rejected during profile creation instead of being saved and failing later. That helps prevent unusable saved profiles and cuts down on repeat payment failures.

Billing form validation no longer leaves merchants stuck

If billing fields are invalid during Benji Payments sign-up, the page now shows validation and re-enables the form instead of leaving the merchant waiting on a spinner. This smooths out onboarding, especially when browser autofill gets a state or province value slightly wrong.

Tax-free enhanced payment data now stays accurate

Tax-free transactions now preserve the true zero-tax amount when enhanced payment data is included, keeping downstream payment details more accurate for invoices that do not include tax.

Customer transaction totals now format properly

The All Transactions table now formats fee and expected settlement footer totals correctly by currency, replacing a visible display bug with totals merchants can actually read.

QuickBooks Desktop sync keeps moving after Benji Payments journal entries

QuickBooks Desktop sync sessions now continue into customer and invoice sync when the previous phase ends with Benji Payments journal entries. That helps reduce the risk of skipped records and avoids extra manual sync-date cleanup.

iPhone users can paste MFA codes again

The MFA screen now supports iOS long-press paste on one-time codes again, making sign-in a little less fiddly for merchants and internal users on iPhone.

Cleaner settlement estimates for Benji Payments BACS and SEPA payments

Estimated settlement dates now use the scheduled debit date for notified payments instead of the notification date. For Benji Payments BACS in the UK market and SEPA payments, this means reports should better reflect when bank debit payments are actually expected to settle, with settlement values hidden until they’re ready to be shown.

Clearer settlement timing for Benji Payments BACS  

Benji Payments BACS transactions in the UK market now show the estimated settlement date while they are in Notified status, instead of leaving that field blank. Merchants and support teams get a clearer answer on when settlement is expected.

Behind-the-scenes reliability got a tune-up

Release, deployment, and monitoring workflows received a few operational improvements, including safer rollback support, better release tracking, and more resilient security-agent deployment handling. Nothing flashy, just the kind of platform housekeeping that keeps the lights bright and the floorboards solid.

Title: Cleaner Portals, Smarter Syncs, Happier Payment Flows

New Features

Payment Method Update keeps getting smarter (beta)

Payment Method Update support now includes EPG card declines, helping Benji capture more useful decline signals across supported gateways. PMU controls were also split from general payment-event collection, so the platform can record events broadly while enabling customer-facing PMU rules and emails only for opted-in merchants.

Bug Fixes

Better settlement timing for Benji Payments BACS in the UK market and SEPA advance-notice payments  

Estimated settlement dates for notified BACS and SEPA payments now anchor to the scheduled debit date instead of the notification date. Reports also avoid showing settlement values too early for notified statuses, making the numbers cleaner and less confusing.

QuickBooks Desktop syncs recover better after deposit handling  

QuickBooks Desktop syncs now continue properly after deposit journal entries are processed, so customer and invoice data keeps flowing and invoice balances stay up to date.

QuickBooks Desktop sync locks clear more cleanly  

Per-company QuickBooks Desktop sync locks now use a shorter, sync-aware expiry. If polling stops unexpectedly, stale locks can clear sooner while keeping the normal reconnect timing intact.Business Central auto-processing is more reliable  

Behind the scenes

Several deployment and CI improvements landed this week too, including stronger blue/green deployment handling, better production environment lookup, improved Elastic Beanstalk retry behavior, and test-suite fixes. These are mostly invisible to customers, but they help keep releases steadier and safer.

More control over Business Central invoices in the customer portal  (groundwork for future release)

Business Central merchants can now control which invoices customers see by invoice number prefix. Choose whether to include only matching prefixes or hide matching prefixes, and Benji will apply that logic in both the portal invoice list and balance totals. Handy for keeping the customer portal focused, tidy, and exactly as selective as it needs to be.

Merchant API access to organization users  (groundwork for future release)

Merchants with the right API scope can now retrieve a paginated list of users for their organization. This opens the door for cleaner admin workflows, better integrations, and easier visibility into who has access.

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.

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.

A tidy bundle of upgrades is rolling in: stronger API coverage for integrators, smarter Benji Payments BACS handling in the UK, better accounting reconnects, and groundwork for payment-method update reminders that can take some follow-up work off your team’s plate.

This release also includes behind-the-scenes improvements to billing operations, API documentation quality, and release reliability, because smoother machinery makes for a smoother Benji experience.

New Features

Partner API customers and payment methods groundworkThe Partner API now covers more of the day-to-day data integrators need, including customer records and saved payment-method information. Responses are designed to stay useful without exposing sensitive vault details, giving teams a clearer and safer way to support connected workflows.

Payment Method Update reminder groundwork  We’ve added the foundation for configurable reminders when a customer needs to update their payment method. Once enabled, this will help reduce manual follow-up, support better recovery after failed payments, and make customer action nudges more consistent.

Benji Payments BACS advance-notice support for deposits and instalment plans   For UK merchants using Benji Payments BACS, deposits and instalment plans now better respect required notification timing instead of moving straight to payment. That means clearer customer timing and more compliant bank debit handling.

Bug Fixes

Cleaner accounting reconnects   Xero reconnect handling has been tightened up so merchants have a better chance of getting reconnected successfully without running into avoidable setup-state issues.

Clearer Benji Payments BACS views  Advance-notice instalment details are now kept out of regular merchant views when they’re not meant to be actionable there, while internal support visibility remains available for troubleshooting.

Sharper API documentation and release quality checks to support upcoming releaseAPI documentation and OpenAPI checks have been improved so integrators get a more reliable contract, while internal release and test workflows are better protected against avoidable pipeline issues.

Benji Payments setup defaults improved  New merchant setup defaults now better support refund and chargeback currency matching, reducing the chance of currency mismatch issues.