Benji Pays feature requests

In my prior ACH processor, we had significantly more insight into the status of each transaction as it proceeded through from initial transaction, to in process, to settled - including estimates for settlement timing that could be reported on as soon as the transaction was made. This allowed me to forecast the deposits for the coming days based on upcoming settlement dates. Additionally, transaction level detail included this more detailed information as well like invoice number and settlement date. All of this allows for better tracking of ACH transactions across the four-day window from initial processing to final settlement. There is also a status column on the report that indicates which transactions are still in process "Open" and which ones are settled "Complete" with links to the settlement info on the completed ones.

Add a toggle in Invoice Rover that restricts automated reminder emails to invoices that have already been manually sent by the merchant. This would benefit merchants who need to review and approve invoices individually before they are visible to customers, preventing Invoice Rover from sending payment requests for invoices that aren't yet ready.

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.

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.

Add import and automation of Credit Card Settlement deposit reconciliation for USA Bambora Merchants via Fiserv's APIs.

A card reader that syncs directly with Benjipays and enables easy surcharging and reconciling

EPG is Elavon's new payment gateway and will support mercants in North America and Europe.

When sending an invoice to a customer, there's an option under "Choose Gateway for Pay Now Link in Email" that gives customers both payment options (credit card and ach). However, the link defaults to credit card. I'd like to set ach as the default.

"Authorise" is considered an incorrect spelling of the word in the USA. "Authorize" should be used instead for customers in the USA.

We receive orders from customers across a variety of order and delivery days and methods, and we process those transactions before they go out for delivery. Before migrating to Benji Pays, our process was to sort invoices in Quickbooks Online by the "Ship Date" field, process all those transactions that were to be delivered the next business day, and reach out to the customer with any issues. My request is to add the "Ship Date" field as an option to include in the Invoices tab to allow for filtering/sorting by the value of that field.

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.