Benji Pays feature requests

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.

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.

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.

On the login page for the portal, we can customize the logo and the brand colour and that is it. It would be nice to be able to customize the Login message. Right now, the login message says: WELCOME Log in to Benji Pays to continue to the Customer Portal It would be nice to be able to customize BOTH messages, the "Header" and the "Body" of the login modal/window.

Add import and automation of Credit Card Settlement deposit reconciliation for Stripe Merchants

New API that will cover most Benji Pays data structures and functionality

Clients currently enter bank account numbers only once during payment setup, which could lead to typos. Recommendation to add a confirmation field requiring clients to enter their bank account number twice (similar to password confirmation patterns). The system would validate that both entries match before saving. This is standard for sensitive data entry (email confirmation, password confirmation) and is specifically recommended for ACH/bank account validation. Additionally, it would be helpful to pre‑validate the routing number; once entered, the associated banking institution can be automatically identified and displayed in the portal to provide immediate confirmation to the client that the routing number is correct - although I understand this would be more cumbersome to add.

We have customers who want to share portal access to their accounts payable team. They want the ability to log into the payment portal. Add email addresses and grant them portal access.

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.

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.

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.

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

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

For example, monthly recurring service fees are auto processed through ACH and other invoices for hardware purchases are auto processed to a credit card or a different ACH account. Could be based on Xero branding themes / QuickBooks Payment Terms, memo or reference field.