Less Chasing, More Collecting

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.