This article covers the email communications we send your Narmi Grow or Narmi Banking users. We use Transport Layer Security (TLS) to securely send emails, ensuring that communications between servers are encrypted. This standard security protocol helps protect your information by preventing unauthorized parties from intercepting or altering the content of our emails while they’re in transit to the email provider. Most major email providers, like Gmail or Outlook, support TLS encryption.

The following conditions apply to end-user communications:

Emails are sent via the Narmi system and typically have a "from" address of no-reply@[financial-institution-domain] unless you have a default "from" email address specified in Institution settings > Default From Email. Emails will originate from IP addresses: 54.240.77.60, 216.221.168.104, 206.55.148.80, and 206.55.148.28.
We send communications to the email address associated with the user’s account.
For joint business applications, communications are sent to the primary applicant only.
For joint consumer applications, by default, communications are sent to the primary applicant only. Emails can be sent to joint applicants for the following:
- Applications that are approved, denied, or moved to “manual review.” To enable this, go to Narmi Command under Institution settings > Send Emails To Joint Applicants > True.
- Applications that are moved to “documents requested.” To enable this, go to Institution settings > CAO Send Documents Requested Emails to Joint Applicants > True.
For security, no usernames are included in end-user email communications. If your institution wants to allow users to see their username in communications, contact your Narmi Relationship Manager to make this change.
All Narmi Grow emails are automatically sent unless specified as optional below.
All Narmi Banking emails are automatically sent to end users except those specified in Digital Banking Optional Alerts.

For information on the SMS communications we send to Narmi Banking users, go to Digital Banking SMS Communications.

For information on push notifications, go to Digital Banking Push Notifications.

Configuring Emails

Some emails are configurable in Narmi Command and if so, that is specified below. To configure, go to the Narmi Command sidebar, select Configurations > Institution settings, then search for the setting specified. For instructions, go to Updating Email Templates. Note: Some communications have separate email templates for Consumer Account Opening (CAO) and Business Account Opening (BAO), specified below.

In {{glossary.UAT}} environments, for institution settings that configure email templates, you can select View sample email. This opens a new browser tab with a preview of the email as it appears to the end user and allows you to test the links within the email.
Institution setting for BAO continuation email template with option to view sample email highlighted.

Other Customization

To edit your institution logo shown in the email footer, go to Updating Institution Logos. To update the text in the email footer, contact your Narmi Relationship Manager.
To include an FDIC or NCUA logo in the email footer, go to Narmi Command under Configurations > Institution settings > Member FDIC or NCUA Logo URL.
To edit the length of time in seconds that a link sent in an Account Opening communication is valid, go to Institution settings > Email Link Validity. The default is 72 hours (259200 seconds).
To update the subject line of email confirmation communications, go to Institution settings > Email Confirmation Email Subject. The default subject line is "Verify Email Address."

Account Opening Email Communications

The following emails are organized by category—Business, Consumer, Funding, General, and Staff-Led. All Narmi Grow emails are automatically sent unless specified as optional below.

Business Account Opening Only

Business Verification – Sent when an organization returns to the Business Account Opening flow. Configure this email via Institution settings > Organization Verification Email Template.
Business Email Confirmation – Sent to confirm identity as part of the Account Opening flow, for example, when returning applicants want to continue an application. Configure this email via Institution settings > BAO Email Confirmation Email Template.
Business Application Continuation (Optional) – If the application state is "Creating," you can opt to send a continuation email to the applicant reminding them to continue their application. To do this, go to the Narmi Command sidebar > Account opening > Applications > open the specific application view > select the three dots > select Send continuation email. Configure this email via Institution settings > BAO Continuation Email Template.

Business Ownership

Stakeholder First Notification – Initial email sent to the ownership stakeholders for them to submit their personal information. The link in the email expires after 72 hours. Configure this email via Institution settings > BAO Owners' Information First Notification Email Template.
Stakeholder Reminder – Reminder email sent to the ownership stakeholders for them to submit their personal information. The link in the email expires after 72 hours. Configure this email via Institution settings > BAO Owners' Information Reminder Email Template.
All Stakeholder Info Complete – Email sent to the primary applicant when all stakeholders have added their personal information. Configure this email via Institution settings > BAO All Owners' Information Added Email Template.
Individual Stakeholder Info Added – Email sent to the primary applicant when an individual stakeholder has completed their personal information. Configure this email via Institution settings > BAO Beneficial Owner Information Completed Email Template.

Consumer Account Opening Only

Consumer Verification – Sent when an applicant verifies their email address in Consumer Account Opening. Configure this email via Institution settings > Consumer Applicant Verification Email Template.
Consumer Email Confirmation – Sent to confirm identity as part of the Account Opening flow, for example, when returning applicants want to continue an application. Configure this email via Institution settings > CAO Email Confirmation Email Template.
Consumer Application Continuation (Optional) – If the application state is "Creating," you can opt to send this continuation email to the applicant, reminding them to continue their application. To do this, go to the Narmi Command sidebar > Account opening > Applications > open the specific application view > select the three dots > select Send continuation email. Configure this email via Institution settings > CAO Continuation Email Template.
IRA Opened – Sent when an applicant opens an Individual Retirement Account (IRA), which includes IRA details from your institution. Configure this email via Institution settings > IRA Account Opened Email Template.
Review Application – Sent when a staff member modifies a consumer applicant's product selection to better fit their needs. The application must be in a “Review” state to edit. Go to Product Swaps for more information. The email contains a link for the applicant to review the new products and continue the application. Configure this email via Institution settings > CAO Product Swaps Email Template.

Funding

Funding Failed – Sent when {{glossary.Identity decisioning}} was successfully processed, but the account did not proceed to the {{glossary.Core}} banking system. (This can be due to several possible reasons, such as insufficient funds or an invalid credit card number. See Funding Failed for more information.) This email suggests to the applicant that they try a different funding method. A link in the email directs the applicant back to the application to enter a new funding type and submit the application. Configure this email via Institution settings > Funding Failed Template Note: There are separate templates for business and consumer applicants.
Retry Funding (Optional) – If the application state is "Funding failed," the applicant automatically receives the Funding Failed email mentioned above. You can opt to send another Funding Failed email to the applicant in Narmi Command > open the application view > select the three dots > select Send retry funding email. Note: This is a separate action from updating the application state to "Retry funding" and only sends the Funding Failed email.

General

Note: To enable the Approved, Manual Review, and Denied emails for consumer joint applicants, go to Institution settings > Send Emails To Joint Applicants > True. To enable and configure the Documents Requested email for consumer joint applicants, see instructions below.

Existing User Mismatch – Sent when an existing user starts an application with a different email address than the one currently associated with the user on the core. The email is sent to the address entered on the application to alert the user to check the email on file. Configure this email via Institution settings > DAO Existing User Email Mismatch Email Template.
Application Approved – Sent to the primary applicant and consumer joint applicant upon successful opening of the account on the core. This applicant passed identity verification, successfully funded the account, and the account opened on the core. This contains a link for the primary and consumer joint to view their account information. Configure this email via Institution settings > Application Approved Template (for new applicants) or Existing User Application Approved Template (for existing users). If you’d like to prevent the approved email from being sent, leave the Application Approved Template or Existing User Application Approved Template settings blank. Note: There are separate templates for business, consumer, and consumer joint applicants.
Documents Requested (Automatic and Optional) – If your financial institution is integrated with Vouched, they must upload additional documentation during the account opening flow to complete their application. If they do not upload document when prompted during the flow, a “documents requested” email is automatically sent to primary applicants after 15 minutes. This email provides a link that directs them to the Vouched page, where they upload documents. Configure this email via Institution settings > Documents Requested Template. In the template, do not change the “Finish your application” link as {auth_link} automatically gets replaced with the URL to the Vouched flow. Note: There are separate templates for business and consumer applicants.
- For Business Account Opening only, you can edit the email subject line via Institution settings > BAO Documents Requested Subject.
- You can opt to send this email to consumer joint applicants by default via Institution settings > CAO Send Documents Requested Emails to Joint Applicants > True. Configure this email via Institution settings > Joint Documents Requested Template.
- You can also opt to send a reminder email to the primary applicants notifying them that documents are requested. To do this, go to the Narmi Command sidebar > Account opening > Applications > open the specific application view > select the three dots > select Send docs requested email. Note: This action only sends an email to the primary applicant, not joint applicants, even if you have the setting CAO Send Documents Requested Emails to Joint Applicants > True.
For more information on the “Docs requested” status, go to Application Statuses.
Manual Review – Sent to the primary applicant and consumer joint applicant when the application enters the "manual review" state after submitting an application. "Manual review" is an application outcome from Alloy which causes us to pause the application. The application must be manually decisioned by the financial institution in the Alloy platform. Configure this email via Institution settings > Manual Review Template. Note: There are separate templates for business, consumer, and consumer joint applicants.
Application Denied (Consumers or owners/partners in an organization only) – Sent to the primary applicant and consumer joint applicant when the application enters the "denied" state after submitting an application. "Denied" is an application outcome from Alloy, which causes us to stop the application from proceeding. Businesses are not auto-denied. Configure this email via Institution settings > Application Denied Template. Note: There are separate templates for business, consumer, and consumer joint applicants.

Staff-Led Account Opening Only

Staff-Led Disclosures – Sent when your staff sends a disclosure notification email for staff-led applications (business and consumer). To do this, from the Disclosures section of the staff-led flow, select Send to applicant. Configure this email via Institution Settings > Staff-Led Disclosures Email Template.
Staff-Led Application Continuation (Consumer and Business) – If the application state is "Creating" or “Creating preapproved,” you can opt to send a continuation email to the applicant, reminding them to continue their application. To do this, go to the Narmi Command sidebar > Account opening > Applications > open the specific application view > select the three dots > select Send continuation email.
Note: For continuing applications in “Creating preapproved,” since the application has already passed KYC, applicants cannot update their personal information.
For the Business Staff-Led flow, this can also be sent when the staff member selects Send to applicant in the application header. Configure this email via Institution Settings > CAO Continuation Email Template for consumers or BAO Continuation Email Template for businesses.

Digital Banking Email Communications

The following Narmi Banking emails are automatically sent to end users. For optional communications based on alerts set up by the user, go to Digital Banking Optional Alerts.

The following emails are organized by category—Business Banking, Enrollment, Money Movement, Transactions, User Setup, and Other.

Business Banking

Organization Invite – Sent when a business admin invites a new user to join their organization's Narmi Banking account. Configure this email via Institution settings > Organization Invite Template.
Organization Address Change Acknowledgement - Sent to Admin users when a business user changes the organization address from Narmi Banking Settings.
Wire Dual Approval Approved – Sent when a wire the user submitted is approved (dual approvals must be enabled). Configure this email via Institution settings > Dual Approval Approved Email Template.
Wire Dual Approval Denied – Sent when a wire the user submitted is denied (dual approvals must be enabled). Configure this email via Institution settings > Dual Approval Denied Email Template.
Wire Dual Approval Requested – Sent to all users who are permitted to approve wires when a wire is submitted for approval (dual approvals must be enabled). Configure this email via Institution settings > Dual Approval Requested Email Template.
ACH Payment Initiated/Approved – Sent when a user performs an ACH payment to confirm the payment was initiated (once the payment automatically or manually passes risk evaluation).
ACH Payment Canceled – Sent when a user performs an ACH payment that was rejected after risk evaluation. A transaction may be canceled for several reasons, such as insufficient account balance, deactivated account, or other account issues.
ACH Payment Dual Approval Approved – Sent when a one-time ACH payment the user submitted is approved (dual approvals must be enabled). Configure this email via Institution Settings > Ach Dual Approval Approved Email Template.
ACH Payment Dual Approval Denied – Sent when a one-time ACH payment the user submitted is rejected (dual approvals must be enabled). Configure this email via Institution settings > Ach Dual Approval Denied Email Template.
ACH Payment Dual Approval Requested – Sent to all users who are permitted to approve ACH payments when a one-time ACH payment is submitted for approval (dual approvals must be enabled). Configure this email via Institution settings > Ach Dual Approval Requested Email Template.
Scheduled ACH Payment Dual Approval Approved – Sent to the user who scheduled the payment when the payment they submitted was approved (dual approvals must be enabled). Configure this email via Institution settings > Scheduled Ach Dual Approval Approved Email Template.
Scheduled ACH Payment Dual Approval Denied – Sent to the user who scheduled the payment when the payment they submitted was denied (dual approvals must be enabled). Configure this email via Institution settings > Scheduled Ach Dual Approval Denied Email Template.
Scheduled ACH Payment Dual Approval Requested – Sent to all users who are permitted to approve ACH payments when a scheduled ACH payment is submitted for approval (dual approvals must be enabled). Configure this email via Institution settings > Scheduled Ach Dual Approval Requested Email Template.
Scheduled ACH Payment Canceled Requester – Sent to the user who scheduled the payment when a scheduled ACH payment is canceled due to the missing dual approval. Configure this email via Institution settings > Scheduled Ach Payment Canceled Dual Approval Expired Requester Email Template.
Scheduled ACH Payment Canceled Approver – Sent to all users who are permitted to approve ACH payments when a scheduled ACH payment is canceled due to the missing dual approval. Configure this email via Institution settings > Scheduled Ach Payment Canceled Dual Approval Expired Responder Email Template.
Recurring ACH Payment Canceled Requester – Sent to the user who scheduled the payment when a recurring ACH payment is canceled due to the missing dual approval, but future payments may still go through. Configure this email via Institution settings > Scheduled Ach Payment Canceled Dual Approval Pending Requester Email Template.
Recurring ACH Payment Canceled Approver – Sent to all users who are permitted to approve ACH payments when a recurring ACH payment is canceled due to the missing dual approval, asking them to approve future payments. Configure this email via Institution settings > Scheduled Ach Payment Canceled Dual Approval Pending Responder Email Template.
Single recurring ACH Payment Canceled Requester – Sent to the user who scheduled the payment when a recurring ACH payment is canceled due to the missing dual approval, and there are no future payments. Configure this email via Institution settings > Single Scheduled Ach Payment Canceled Dual Approval Expired Requester Email Template.
Single recurring ACH Payment Canceled Approver – Sent to all users who are permitted to approve ACH payments when a recurring ACH payment is canceled due to the missing dual approval, and there are no future payments. Configure this email via Institution settings > Single Scheduled Ach Payment Canceled Dual Approval Expired Responder Email Template.

Cards

Lost/Stolen/Never Received Card – Sent to users who reported their card lost, stolen, or never received in the manage cards feature. Configure this email via Institution Settings > Card Misplaced Email. The default text explains that the lost card was canceled, and the user will be issued a new physical card with a new number in 5-7 business days.
Damaged Card – Sent to users who reported their card damaged in the manage cards feature. Configure this email via Institution settings > Card Damaged Email. The default text explains that the user will be issued a new physical card with a new number in 5-7 business days, but they can continue using the damaged card until they activate the new one.
Travel Notice Confirmation – Sent to users who set a travel notice on their debit or credit card. Configure this email via Institution settings > Travel Notes Email.
Limit Increase Confirmation – Sent to users who submitted a request for a limit increase on their debit card, which was approved. Configure this email via Institution Settings > Card Limits Increase Email.

Enrollment

Welcome Email – Sent when a user's Narmi Banking account is activated. It includes a link to confirm their email address within 3 days. You cannot change this number of days. You can configure the email text via Institution settings > Welcome Email Template. Do not change {link_timeout_days} or <a href={reset_link}</a> as those values are automatically populated.
Enrollment Code – If your financial institution requires two-factor authentication or has enabled enrollment codes, a prompt displays during enrollment for the user to enter a verification code. This email is sent to the email address associated with the account and includes the verification code.
Online Banking Add Account Verification – This email is only sent from institutions where the Memberships "Link another account" feature is enabled in Narmi Banking Settings. For more information on this feature, go to Memberships.
If a user enters the correct details to link an account, we check whether their email has already been confirmed or not:
- If the email has already been confirmed, we automatically link the account
- If the email has not been confirmed and your institution supports enrollment codes, rather than automatically linking, we send an email to the core-provided email on the account they're attempting to link. When the user opens the email and selects Confirm, the account will be successfully linked.
User Exists without Reset Link – We send this email if we identify that a user has already enrolled but is attempting to enroll from the "Tell us more about you" page of enrollment. We determine which email is sent based on whether the institution supports core authentication or not.
This use case is where the core uses authentication, meaning the core also stores a record of the username/password and has its own defined username/password validation. We send the email and display an error to the user.
User Exists – We send this email if we identify that a user has already enrolled, but is attempting to enroll from the "Tell us more about you" page of enrollment. We determine which email is sent based on whether the institution supports core authentication or not. This use case is where the core DOES NOT use authentication. We search our own Narmi database for a user with the given core_user_id and user_category (personal or business). If we find that a user already exists, we send an email with a password reset link and display an error to the user.
Enrollment Continuation – We send this email when a user has not finished their enrollment and they either 1) re-enter information in the "Tell us more about you" page or 2) try resetting their password. The email includes a link for them to continue enrollment.

Money Movement

Note: For money movement emails related to business banking only, go to the Business Banking section.

ACH Transaction Initiated – Sent when a user performs an ACH transfer to confirm the transfer was initiated.
Transfer Failed – Sent when a user performs an ACH transfer to confirm the transfer failed.
Wire Submitted – Sent when a user requests a wire transfer to confirm the wire request was received.
ACH Rejected – Sent when a user's ACH transfer was canceled by staff.
Wire Rejected – Sent when a user's wire request was rejected by staff.
Loan Payment Rejected – Sent when the user's loan payment is rejected because it is greater than the loan balance.
External Account Verified – Sent when an external account has been successfully verified and added to the user's existing Narmi Banking account.

Transactions

Transaction Alert Rate Limited – Sent when a user's transactions are rate-limited. This email requests that the user review their transactions.

User Setup

Set User Credentials – Sent when the user leaves the enrollment flow before choosing a username and password.
Email Change Confirmation – Sent to verify the email address when a user changes it from their Narmi Banking Settings.
Email Change Acknowledgment – Sent to acknowledge when a user changes their email address from Narmi Banking Settings.
Password Change Acknowledgment - Sent to acknowledge when a user changes their password from Narmi Banking Settings (not the password reset). For more information, go to Changing Passwords.
User Address Change Acknowledgement - Sent when a user changes their mailing or residential address from Narmi Banking Settings.
Two-Factor Authentication (2FA) Code – Sent when a user logs in with 2FA.
Two-Factor Authentication (2FA) Device Updated – Sent when a user adds or removes their 2FA security device from Narmi Banking Settings.
Reset Username or Password - Sent when a user attempts to recover their username or password via the "Forgot your username or password?" link on the login page. This email includes a link to reset the password. Usernames are masked in the reset email for security. If your institution wants to allow users to see their username in the reset email, contact your Narmi Relationship Manager to make this change.
If your institution has usernames masked in the reset email, your staff can look up the username to manually give to the customer. This is located in Narmi Command in the right sidebar of their user profile.

Other

Direct Deposit Manual Enrollment – Sent when a user successfully downloads a direct deposit form. This includes an attachment with the Direct Deposit Enrollment Form PDF. Configure this email via Institution settings > Direct Deposit Manual Enrollment Email Template.
Statement Notification – Sent when the user's paperless statement is available for viewing.
Support Messages - Sent when the user receives a secure message from your institution through Narmi Banking.
Open Banking API Notification – Sent when the user shares account data with a third-party application like Venmo, CashApp, Rocket Money, etc. This email is optional if your institution has enabled our Open Banking API to share customer financial data with authorized third parties. Once enabled, your institution can turn on this email via Institution Settings > Enable OIDC Data Access Email Notifications > True. Configure this email via Institution settings > Openid Access Granted Email. Go to About Open Banking for more information.

Digital Banking SMS Communications

The following communications are sent to your Narmi Banking users via text message. All SMS notifications are automatically sent in addition to the corresponding email communication to the phone number associated with the user’s account.

Mobile Two-factor (2FA) Authentication Code – Sent when a mobile device is used for 2FA.
Text: <{{glossary.FI}} Name>: DON'T share. Use code 123456 to verify your identity. We'll never call or text you to ask for this code. Call us if you didn't request it.
Password Change Acknowledgment – Sent to acknowledge when a user changes their password from Narmi Banking Settings (not the password reset). This message is customizable by contacting your Narmi Relationship Manager.
Text: Alert: Your {institution_name} password has been updated. If you didn't initiate this change, please contact us immediately at {help_phone}.
Custom alerts – Sent based on custom alerts set up by the user in their Security Settings if “text” was selected as the notification type. Account numbers are masked in email and text transaction alerts.

Digital Banking Push Notifications

The following communications are sent to your Narmi Banking users via push notification if the user has push enabled on their device. All push notifications are sent in addition to the corresponding email communication to the phone number associated with the user’s account.

Note: If a user is actively using the mobile app, the push notification will not be sent.

Password Change Acknowledgment Push – A push notification is sent for password changes from Narmi Banking Settings (not the password reset).
Text: Your password has been updated. If you did not initiate this change, please contact us at (Support Phone Number institution setting)
Support Message Push – A push notification is sent when the user receives a secure message from your institution. Tapping on the push notification opens the secure message in Narmi Banking.
Text: View your new secure message from Support

Digital Banking Optional Alerts

The following communications are sent to your Narmi Banking users only if they set up alerts in their Narmi Banking Settings. They can be sent via email or SMS, depending on the delivery method selected by the user. If the user has the mobile app and allows notifications in their device settings, they can elect to receive push notifications for all Balance, Spending, and Custom alerts described below, but not for Security alerts. For more information, go to Alerts.

Balance

For information on setting up these alerts, go to Balance Alerts.

Low Available Balance – Sent when a user’s balance falls below an amount specified in their alert settings. Configure this email via Institution settings > Low Available Balance Email Template.
Available Balance – Notifies a user of their available balance. This alert is sent at 11:00 a.m. EST on the days specified by the user in their alert settings. Configure this email via Institution settings > Available Balance Email Template.
Incoming Transaction Alert – Sent when a user has an incoming transaction that exceeds the amount specified in their alert settings. The alert is sent when the transaction is pending and sent again when it is posted. For more information, go to Balance Alerts. Configure these emails via Institution settings > Credit Transaction Pending Email Template and Credit Transaction Posted Email Template.
Loan Payment Due (consumers with loan accounts only) – Sent when a user’s loan payment is due. Can be sent up to 7 days before the payment due date. Configure this email via Institution settings > Loan Payment Reminder Email Setting.
Loan Payment Overdue (consumers with loan accounts only) – Sent when a user’s loan payment is overdue. We send this notification once per loan payment cycle, on the day after the payment due date. Configure this email via Institution settings > Loan Payment Overdue Email Setting.

Spending

Account numbers are masked in email, SMS, and push transaction alerts.

Outgoing Transaction Alert – Sent when a user has a posted transaction that exceeds the amount specified in their alert settings. For more information, go to Spending Alerts. Configure this email via Institution settings > Debit Transaction Email Template.
Note: By default, the transaction alert only applies to posted transactions, not pending transactions. Please contact your Narmi Relationship Manager if you would like this alert to apply to pending transactions. Once enabled, alerts include the status of the transaction as “Pending” or “Posted.”

Custom

Custom alerts allow users to set up unique alerts based on criteria most important to them, such as large deposits, specific merchant transactions, or unusual activity. For more information, go to Custom Alerts.

Alerts List