Smarter Business Central Payments and Easier Charge Recovery

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.