- 1 Minute to read
- Print
- DarkLight
- PDF
Funding Limits
- 1 Minute to read
- Print
- DarkLight
- PDF
There are two areas in the platform where funding limits are enforced—the front end (applicant-facing) and the back end (not applicant-facing).
Front-end Limits
Front-end limits are visible to the applicant and they cannot proceed unless they fund accounts within your financial institution’s specified limits. If the applicant enters funding above your limit, an error message appears. We allow product-specific limits, for example, a CD can have a higher limit than a checking account.
Back-end Limits
In addition to the front-end limits, Narmi, Authorize.net, and Elavon also enforce limits on the back-end. These limits are a combination of daily limits and monthly limits. These limits are configured during implementation but can be changed after implementation.
If your financial institution uses Narmi AO ACH Service to facilitate ACH funding (as opposed to Authorize.net), your institution has complete control over the funding limits you would like to set; Authorize.net is not involved with limits.
Changing Limits
Your financial institution can choose to change funding limits. To change the limit on the front end, please contact support@narmi.com with your request. This must be approved by an executive at your financial institution.
You may also be required to submit a limit change request to Elavon for card funding, and Authorize.net if your institution uses their eCheck product for ACH funding (as opposed to Narmi AO ACH Service). Narmi recommends two weeks' advance notice for a limit change, as further documentation may be required for underwriting purposes to Authorize.net.