Announcements

New updates and improvements to Benji Pays

  1. Webhook Visibility, Accurate Partial Payments, and Smoother Checkout

    Release Notes

    This release lets API integrations review their webhook registrations, makes sure customers are charged exactly the partial amount they choose, and makes card payments and payout reporting more dependable.

    New API capabilities

    The Benji Pays API is currently in beta.

    View your webhook registrations

    Integrations can now list all of their webhook registrations, or look up a single one, to check which endpoints are set up and which payment events each receives. Signing secrets are never shown again after a webhook is created.

    Payments and reporting

    Partial payments after invoice lookup charge the right amount

    When customers find an invoice through Invoice Lookup and edit the amount to make a partial payment, that exact amount is now what’s charged, across all supported card gateways.

    Receipt email field always shows on Pay Now links

    When a receipt email address is required on a Pay Now link or card request, the field now always appears on the payment form, so customers can complete their payment without getting stuck.

    Fewer failed Bambora charges from billing details

    Long billing addresses and province or state values in different formats are now handled correctly, so saved cards keep working and any error message accurately explains what needs attention.

    Accurate fees for chargebacks in payout reports

    Benji Payments payout reports now show the correct fee for chargeback lines, making reconciliation simpler.

    Customer Portal

    Embedded portal works on more custom domains

    The Customer Portal now loads inside your website when your custom domain uses a multi-part ending such as .com.au or .co.uk.

    Business Central (coming soon)

    Automatic extension updates

    We’re preparing Benji Pays to install and update its Business Central extension for you. Updates will be scheduled during each Business Central environment’s own update window, so they won’t interrupt your team’s day.

    Security

    Stronger protection on payment pages and portal settings

    We’ve added extra safeguards to public payment pages and portal settings to help keep your customers’ details protected. No action is needed on your part.

    Behind the scenes

    We’ve also improved our internal admin tools, support alerting, hosting reliability, and automated testing. These updates help our team support you faster and deliver more reliable releases.

  2. The Benji Pays API Is Now in Public Beta

    New Feature
    Announcement

    The Benji Pays API is now in public beta. You can start building your own integrations and workflows on Benji Pays. Visit our API documentation to get started.

    What beta means

    The API is available to use now, and we’ll keep expanding what it can do. Some details may change as we improve it, and we welcome your feedback as you build.

    What’s possible

    The API lets you create integrations and workflows that fit the way your business already works. Here’s what some customers are already doing:

    Custom dashboards for cash position

    Teams are building their own dashboards to get a clearer view of their cash position, bringing Benji Pays data into the tools they already rely on.

    Payment method requests at onboarding

    Others are automatically sending payment method requests as their customers onboard, so payment details are collected as part of the signup flow instead of as a later follow-up.

    What’s next

    We’re continually adding new functionality to the API. Check back here and follow these release notes — we’ll announce new API capabilities as they go live.

  3. Payment Webhooks, Clearer API Access, and More Reliable Accounting

    Release Notes

    This release lets API integrations receive payment webhooks, makes API permissions easier to manage, and makes Business Central posting and Elavon clearing more reliable.

    New API capabilities

    The Benji Pays API is currently in beta.

    Register webhooks for payment events (work in progress)

    Integrations can now register their own HTTPS endpoints to be notified when a payment succeeds or fails. Each registration comes with a signing secret so you can confirm every notification really came from Benji Pays.

    A clearer API Access permissions picker

    Permissions on the API Access page are now grouped by area, such as gateways, invoices and customers, with a short description and a read or write badge for each. Search, select-all options and a running count make it easier to grant exactly the access an integration needs.

    Business Central (coming soon)

    Payments post in the right currency, every time

    When Benji Pays applies a payment, refund or deposit in Business Central, it now checks the customer’s current currency directly in Business Central. If the customer can’t be read at that moment, the payment isn’t posted and you’ll see a clear message asking you to retry. This keeps posted amounts accurate and avoids manual corrections.

    Security

    Stronger protection for Elavon card payments

    We’ve added extra safeguards to Elavon card entry on pay links and in the Customer Portal.

    Safer billing address updates

    We’ve tightened how billing address details submitted in the Customer Portal are checked and shown in merchant notification emails.

    Bug Fixes

    Elavon gets its own clearing account

    “Create Clearing Account” on an Elavon gateway now creates a dedicated clearing account in QuickBooks Online or Xero, so Elavon card receipts stay separate from Benji Payments payouts.

    Plan pricing matches your billing currency

    The plan price shown at card entry now always matches your billing currency and any custom pricing agreed with our team.

    Accounting setup forms submit smoothly

    Merchants setting up a new company can once again connect QuickBooks Online, Xero or Business Central from the accounting selection step.

    Behind the scenes

    We’ve also improved our internal support and account management tools and expanded automated testing. These updates help our team assist you faster and deliver more reliable releases.

  4. More Control Over API Receipts, Plus Business Central Reconciliation

    Release Notes

    This release gives API integrators more control over receipt attachments, brings Benji Payments reconciliation to Business Central, and makes applying payments in Business Central more dependable.

    New API capabilities

    Choose which PDF goes on each API receipt

    API charges now accept an optional attach PDF setting, so integrators can decide per charge whether the receipt email includes a PDF. For invoice charges it controls the invoice PDF and falls back to your company’s attach invoice setting when left out. For prepayments it attaches the payment PDF from your accounting system, such as a QuickBooks deposit, and attaches nothing unless you ask for it. This brings API receipts in line with the options merchants already have in the app.

    Business Central (coming soon)

    Automated reconciliation for Benji Payments

    Business Central merchants using Benji Payments can now have settlement activity posted to Business Central automatically. Choose a dedicated reconciliation journal in your gateway settings to turn it on, and payouts, fees and chargebacks will flow into Business Central without manual journal entries.

    Payments stay open when Business Central rejects a posting

    If Business Central declines a payment you apply from Payments to Apply, the payment now stays open with a clear message explaining why, instead of looking like it was applied. You can fix the issue in Business Central and try again without losing track of the payment.

    Behind the scenes

    We’ve also laid groundwork for upcoming API features and improved admin activity logging, code review automation, build tooling, and deployment notifications. These updates help us investigate issues sooner and deliver more reliable releases.

  5. Safer Portal Payments, Smoother Pay Now, and Clearer Currencies

    Release Notes

    This release strengthens customer portal payment protection, makes Pay Now and Adyen boarding more reliable, improves currency display and API docs, and helps Business Central merchants stay connected.

    Payments

    Saved cards on Clover Pay Now links submit reliably

    Customers paying a Clover Pay Now link with a saved card no longer hit intermittent “idempotency” errors. Payments go through the first time, including after browser back/forward or autofill restores a previously selected card.

    Cleaner Adyen boarding when a time zone needs updating

    Adyen boarding now checks that a company time zone is in a valid Region/City format before creating anything with Adyen. Merchants get a clear message to update the time zone instead of ending up with a stuck boarding record.

    Customer Portal

    GBP invoice tables show the pound symbol

    Customer Portal invoice totals and balances for GBP invoices now display £ instead of $.

    Security update

    Xero integration security update

    We’ve applied Xero’s latest recommended security update to our Xero integration and further tightened how connection details are protected. No action is needed on your part.

    Business Central (coming soon)

    Know when your Business Central connection needs attention

    If your Business Central connection is revoked or stops working, Benji Pays now lets you know with a one-time email and a reconnect banner, the same way it already does for QuickBooks Online and Xero. Reconnecting gets you back up and running without losing payments.

    Bug Fixes

    ConnectWise customer matching completes reliably

    Customer matching between ConnectWise and your accounting system now finishes even when some accounting customers have no email addresses on file.

    QuickBooks Desktop sync stops when a company is suspended

    When a company account is suspended, QuickBooks Desktop Web Connector sync now stops along with the portal and other services. Enabled companies continue to sync as usual.

    Behind the scenes

    We’ve also improved how bank payment gateways are transitioned to Benji Payments, strengthened activity-log IP attribution and security-alert handling, and improved local development tooling and deployment workflows. These updates help us investigate issues sooner and deliver more reliable releases.

  6. Easier Xero Deposits, B.C. Time Zone Support, and a Smoother Deposit Dialog

    Release Notes

    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.

  7. 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.

  8. A More flexible API and smoother Business Central payments

    Announcement
    Release Notes

    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.

  9. More control for Business Central, clearer reconciliation, and broader SEPA support

    New Feature
    Release Notes

    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.

  10. Cleaner APIs, Smoother Admin Workflows, and Stronger Release Checks

    Release Notes

    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.