Benji Pays feature requests

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

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

Add ability to use hosted ConnectWise api url.

This is a feature on QBO that is really nice, where we can see if the customer has opened, and viewed the invoice.

The plan here is to bring the new payment modal concepts from our Self Serve customer portal into the main application, allowing for a single stop to select 1 or more invoices, enter the amounts (if not paying the full amounts) and add a new payment method all at once.

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.

Provide a way to have end customers log into the Benji Pays self serve customer portal either by using their Halo credentials against the Halo IDP, or via a custom integration that would allow Benji Pays to securely verify the user and log them into their Benji Pays portal.

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.

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.

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"

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.

It is useful because it will save us from merchants constantly asking us how to put the URL in an email and what information the email should include. It will keep the information on the customer portal accurate and consistent for all customers which will eliminate merchants misinforming their customers about the features of the Customer Portal. https://www.loom.com/share/5c6e0c5349074842a126d19c77ff16a6

It would be great if payments scheduled by customers would show as "scheduled" instead of "skipped". "Skipped" looks like we made the change to skip the invoice instead of a customer choosing to schedule the payment.

Merchant request to have the Customer Portal token in email templates to display as the word "Customer Portal" in the template and not as a link as shown in the pic attached

To increase security and reduce the chances of card testing we will add recaptcha to all payment pages that do not required a login. Default will be Googles invisible captcha that analyzes behaviour and requires user's input if it deems the session is riskyAn option to enhance recaptcha coverage will be available to all of our merchants to add the "I'm not a robot" checkbox recaptcha instead of the default invisible recaptcha.