Benji Pays feature requests

Right now it is a manual process to chase customers down when their automatic recurring payment method expires or is declined permanently. This should be a relatively simple process to automate - customers can be notified via email that their payment method needs to be updated.

Show Credit memos from the accounting system in the main Merchant Portal and the Customer Portal

Create a mechanism to generate late fees, automatically added to the accounting system. Following requirements: Do not alter existing invoices to avoid altering past financial periods - Likely generate a new "late fee" invoice Configurable rules to include / exclude clients, ignore certain invoices etc. Percentage based, with different percentages for different time periods Continue to generate late fee invoices until original invoice is paid

Currently customers do not get a notification when an auto-pay transaction is declined. We should have the ability to have the system send a "Transaction Failed" email to the customer.

Currently we send a notification to the merchant, however, for our cloud accounting systems we could have this auto update the accounting system with the new information.

Ability to set global Email CC/BCC for payment requests

Hi Benji Pays team, I’d like to submit a request for support of Australian Direct Debit processing via the NPP/BECS framework, in addition to your current ACH offering. As it stands, ACH is not available in Australia, meaning that businesses like ours are unable to use Benji Pays for local bank-to-bank direct debit payments. This severely limits our ability to consolidate payment workflows within Benji Pays, and forces us to rely on third-party services like GoCardless, which introduces added complexity, cost, and disconnect from the unified billing and reconciliation benefits that Benji Pays is known for. Given the rising adoption of HaloPSA in the Australian market, and the fact that Benji Pays is one of the most trusted and integrated payment automation platforms for the MSP and PSA ecosystem, this is a key functionality gap that is likely costing you significant opportunity across the ANZ region. By supporting NPP/BECS for recurring direct debit processing, Benji Pays would: 1). Open up full functionality for Australian businesses wanting to centralise payments under one platform. 2). Attract MSPs and service providers looking to streamline billing in HaloPSA without needing third-party payment tools. 3). Gain a competitive edge against local alternatives that already support AU direct debit but lack your deep PSA integrations. This would be a strategic enhancement that not only addresses a clear technical limitation, but also significantly improves your product-market fit in a fast-growing region. Looking forward to your thoughts on this, and I’d be happy to discuss use cases or test functionality if you're exploring a beta! Cheers!

Ability to restrict user access so that certain users can only process payments without viewing sensitive account or financial information. Current Behavior: At the moment, there are only two permission options available: Manage Customer ProfilesManual Transaction Processing (Requires Manage Customer Profiles) (Includes “View Reports”) Because “Manual Transaction Processing” includes “View Reports,” users with this permission can currently see the home dashboard, including outstanding and overdue invoice totals, which may not be appropriate for all roles. Requested Enhancement: Add a “Payment-Only” permission level (or equivalent custom access control) that allows a user to: Access a customer profile Select an invoice Take a payment …but not view reports, dashboards, or financial summaries.

I would like to be able to open the customer portal as a client (impersonate) however, limited to view only. This would be helpful in walking our clients through how to navigate the system. see what they see and be aware of any changes visually or functionally that need to be made.

User a service like Plaid.com or Flinks.com to allow users to connect their banking details by loging into their online banking in addition to allowing them to enter their banking information manually. This can improve Approval rates and reduce the risk of account infomation being entered incorrectly. There may be a nominal cost to this.

For example when adding a credit card for a customer and they want that payment method used for hardware only, we could label it "hardware only"

would be nice if there was a global setting to automatically send this template when a new user is added with portal access

Allow a customer to visit the customer portal and make a payment for a quote which doesn't have an invoice created yet using a saved payment method

White labeling Benji Pays allows MSPs to strengthen their brand by offering payment automation under their own name, and not marketing for BenjiPays. This can create a seamless and trusted client experience and not further question around who is Benji and can I also trust them with my information. Further, not disclosing our business patterners may help reduce targeted attacks.

Once the bambora batch has settled, create the final deposit transaction in the accounting system to aid with reconciliation.