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.

Business Central gets more global, SEPA Direct Debit arrives, and payment flows pick up some welcome polish. This release brings new ways to collect and manage payments while making everyday experiences safer and more reliable.

New Features

Business Central is ready for multi-currency payments

Business Central merchants can now choose the right currency and gateway for foreign-currency invoices. Payment posting uses Business Central's own exchange rates, helping prevent over- or under-applied payments, with related improvements across balances, deposits, reversals, and home-currency displays.

Cleaner Business Central contact and invoice emails

Multiple email addresses are now validated, deduplicated, and synced more reliably. Invoice recipients can also be pulled from the To, CC, and BCC fields, helping receipts and reminders reach the right people.

Safer Business Central refunds and credit memos

Refunds now follow the supported non-integrated workflow, with the accounting portion recorded manually. Automatic credit memo processing is disabled to avoid incomplete or inaccurate accounting records.

Bank accounts for Business Central settlement setup

Business Central merchants can now select actual bank accounts for settlement deposits instead of general ledger asset accounts. This prepares the way for bank-reconciliation-aware payout posting; automated payout posting is not part of this release.

SEPA Direct Debit for European merchants

Benji Payments now supports SEPA consent, mandate details, advance notifications, and payment scheduling across merchant and customer payment experiences. SEPA payments are also kept distinct from Benji Payments BACS account validation in the UK market.

Smarter payment routing for API integrations

API clients can discover which gateway options support cards or specific bank-payment methods, including supported currencies and company defaults. Integrators can also download customer or merchant receipt PDFs and resend receipt emails without charging the customer again or creating accounting activity.

Customer Portal SSO implementation guides

New developer guides cover custom JWT and OAuth/OIDC Customer Portal SSO, including setup, security, identity matching, errors, and examples for embedded login experiences.

Bug Fixes

Faster merchant access during accounting outages

When an accounting connection is temporarily unavailable, merchant login and company switching can continue using saved data instead of waiting on the unavailable provider or incorrectly asking merchants to reconnect.

More reliable sender details for customer emails

When a merchant email is missing or its verified sending identity is rejected, customer-facing messages now use the designated no-reply address while preserving the merchant's display name.

A steadier experience behind the scenes

Various fixes improve reminder and unit-test reliability, reduce repeated outage-alert emails, and strengthen onboarding tracking. These changes do not directly alter payment behavior, but they help keep Benji Pays running smoothly.

You've been asking for this one... a lot.

Here it is. When a saved card expires, is declined, Benji emails your customer for you — with the last four digits of the card that failed, the invoices riding on it, and a secure link to drop in a new one. No portal login, no password, no call to your team.

You decide when it fires: which failures count (dead-end declines like expired is the recommended start), whether it covers customer payments, payments you key in yourself, auto-processing runs, or all three, and how often to send. Default is one email every 5 days.

It also knows when to quit. Once the invoice is paid, a new card is on file, a bank payment is submitted, or the card auto-updates behind the scenes, the emails stop. And no customer gets "update your card" and "your invoice is overdue" on the same day.

Set it up under Settings → Invoice Rover → Add New Rule → Payment Method Update.

Full Setup Guide here

Collecting payments just got a lot more hands-off and security got a leg up.

This release expands automated collection options for integrations through our API, streamlines our upcoming Business Central integration's gateway setup, better protects against card testing and smooths out a few customer portal payment moments.

New Features

Create and track payment method requests through the API

Integrations can now create secure card-on-file request links and track their status through the API. Customers complete the familiar portal flow, while the calling system stays in control of delivering the link. It is a tidy new building block for automated collection when no payment method is on file.

Charge invoices through the API

Integrations can charge a saved payment method against an invoice and receive clear results for the payment, accounting writeback, and receipt. That means overdue receivables can move forward through automated workflows without requiring someone to process every invoice in the dashboard.

Retry accounting writebacks without charging again through the API

If a payment succeeds while QuickBooks, Xero, or Business Central is unavailable, integrations can retry just the accounting writeback. The customer is not charged again and does not receive a duplicate receipt, making recovery safer and simpler.

Retrieve payment methods with authorization evidence through the API

Integrations can retrieve an individual saved payment method together with its recorded authorization details. This provides stronger evidence when responding to disputes involving off-session payments, while keeping access scoped to the merchant's organization.

Set up Business Central payment journals right from the gateway

Business Central merchants can select or create a cash receipt journal while adding or editing a gateway. This removes a separate trip to settings, helps prevent setup mistakes, and keeps the gateway disabled until the required journal is ready.

Security

IP rate limiting controls better protect against card testing

Pay Now links are now have multiple layers of rate limiting to better prevent and manage automated abuse and card-testing attempts. The safeguards monitor patterns across individual payers, payment links, and repeated declines, helping stop suspicious activity before it reaches payment processing.

Bug Fixes

Surcharge confirmation text is ready when the dialog opens

The payment portal now waits for translations before displaying the surcharge acknowledgement. Customers see readable, translated explanations and actions from the first load instead of raw translation keys.

Benji Payments can be retried after cancelling

Cancelling the surcharge confirmation no longer leaves the Pay button spinning. Customers can change their mind and retry the payment normally, with no refresh required.

Customer portal payment dialogs are back in style

The Pay Multiple Invoices modal and surcharge popup now load the intended font consistently, restoring a polished and familiar payment experience.

Various behind-the-scenes fixes also improve platform security, deployment reporting, and internal support workflows. These changes do not directly affect customers, but they help keep Benji Pays running smoothly.

Download official invoice PDFs through the Merchant API

Teams using the Benji Pays Merchant API can now retrieve the official invoice PDF directly from a connected accounting system. This makes it easier for AR and collections tools to attach the authoritative document to their own customer communications, without asking Benji Pays to send the email.

Choose the right Business Central environment

Connecting Microsoft Dynamics 365 Business Central is now more flexible. Merchants can choose from their available production and sandbox environments, with the company list automatically updating to match their selection.

Bug Fixes

More reliable Business Central connections

A Business Central company can no longer be connected to multiple Benji Pays organizations. Existing owners can still reconnect safely, helping prevent duplicate synchronization, competing webhooks, and unclear data ownership.

Safer payments, smoother follow-through, and better shared context have arrived.

This release gives teams clearer ways to collaborate, more control over the customer portal, and extra protection around customer payments. It also includes several fixes that improve receipt delivery, accounting accuracy, and day-to-day merchant communication.

New Features

Keep customer context in one place

Teams can now record, reply to, resolve, edit, and pin internal notes directly on a customer. Notes are built for shared collection and billing context, helping everyone stay aligned on important instructions while keeping those conversations private from customers. The experience also includes safeguards designed to prevent unsafe content and sensitive payment information from being stored in notes.

Recover invoice lookups securely

Merchants can now offer a secure recovery form when a customer's public Pay Now lookup does not find an invoice. Customers can retry with an invoice number and date, while expiring payment links, reCAPTCHA, throttling, and privacy-friendly error messages add stronger protection against card testing. Successful lookups continue to work just as they do today.

Choose which invoice PDFs customers see

A new customer portal setting lets merchants hide accounting-system invoice PDFs while keeping invoice balances, payment options, and separately uploaded attachments available. This gives businesses using multiple systems more control over which invoice document their customers receive.

Bug Fixes

Partial payment links now charge the intended amount

Applied invoice links now carry the requested partial amount all the way through payment processing, helping protect customers from accidental overcharges and making reconciliation easier for merchants.

More reliable receipt delivery

Receipt preparation now waits for invoice details to be available before determining recipients. This improves delivery to invoice contacts and reduces unnecessary operational alerts without changing the payment flow.

Accurate accounting methods for Benji Payments bank payments

EFT, ACH, SEPA, and Benji Payments BACS transactions now consistently use the merchant's configured Bank Payments method in nightly runs and the customer portal. This keeps accounting records aligned with merchant settings and avoids incorrect classifications.

Clearer chargeback and returned-item notifications

Merchant and admin notifications now clearly identify both chargebacks and returned items, explain the manual accounting steps needed to reopen an invoice for collection, and point teams to the relevant support guidance.

Getting paid and managing refunds just got easier. This release brings secure invoice-specific payment links, Business Central credit memo refunds, smoother Sherweb onboarding, and several payment reliability improvements.

New Features

Create payment links tied directly to invoices

Partners can now create secure payment links for specific invoices through the API. Customers can make full or partial payments through the familiar portal experience, and each payment is automatically applied to the correct invoice.

Refund Business Central payments against credit memos

Business Central merchants can now process refunds against credit memos through the standard void and refund experience. Benji safely tracks available credit to prevent duplicate or excessive refunds and provides clear guidance when manual posting is required.

Bug Fixes

More reliable EPG voids and refunds

Elavon Payment Gateway (EPG) merchants can now void and refund payments with gateway-managed surcharges more reliably. Successful reversals retain the correct surcharge amounts, while unsuccessful attempts return clearer, safer error messages.

Transferred cards now work with portal surcharging

Customers can use token-transferred Benji Payments cards in the customer and payment portals when surcharging is enabled. We've also improved profile-creation messages so actionable errors are clearer without exposing internal details.

Various behind-the-scenes improvements strengthen trial billing records, accounting reference lookups, release operations, and automated payment testing. These changes do not alter customer charges, but they help keep Benji running smoothly.

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.