Ensenta FAQs

What is an EWS risk factor?    

EWS Risk Factors are used when clients have Ensenta's Integrated Fraud Check product. Financial institutions may customize a risk factor’s severity (reject or accept) and its review queue (only applicable if the risk factor is set to accept) during EWS set-up.

Please note that business or ATM channels cannot have any risk factors set to reject.

The name of each risk factor is comprised of four parts:

1. Risk type: IFC (Integrated Fraud Check)
2. EWS risk type: Hard, Soft, Informational, or Open/Active
3. Type of data: Participant or Non-Participant
4. Risk factor name

Does Ensenta perform any check image validation?

Yes, Ensenta does complete check image validation, however, a check image is rarely rejected. If Ensenta's OCR can validate a MICR number, account number, date, etc. is present, the image will pass validation. Validation will only reject if the picture is not of a check.

How are RDC limits, risk rules/factors, and queue routing determined?

Ensenta has default limits and risk rule routing based on research. Post-delivery of the platform, segment limits can be edited in EZAdmin on the “Limit Dashboard”.

All risk rules are configurable by the FI. Ensenta allows for some risk rules and routing to be customized. Ensenta offers a risk review that would cover additional changes to risk rules and routing; however, this requires an SOW and additional project with Ensenta.

Please reach out to your Narmi General Manager with questions.

How long does Ensenta retain check images?

Check images are retained for 6 months from the date of deposit and are then purged. If check images from over 6 months ago are needed, check with the Item Processing Vendor.

How soon is a check image available in EZAdmin?

The check image is available real-time in EZAdmin after a user submits their deposit. 

Why are checks rejected in EZAdmin posting and not included on an exceptions report?

This is expected behavior. If an FI has Narmi Real-Time Posting for RDC, all checks in manual review queues will be posted. When FI staff reject (or adjust) a deposit in EZAdmin, a manual reversal (or adjustment) must be made:

1. Via direct reversal in the core system OR
2. Via batch process, using a return file from Ensenta

Read more about Narmi Real-Time Posting for RDC here. 

Can FIs create individual limits on users?

Yes. Read more here.

Note: Any individual limits will override the designated limits defined by the Narmi segment that the user is in.

If a user updates their email address in the Narmi platform, will that change flow to Ensenta so that alerts or other communications from Ensenta get sent to the correct email address? 

Yes. If a user changes their email address in the Narmi platform, Narmi will send the updated email address to Ensenta after that user's banking session is complete. Ensenta will use that new email address to send alerts and all other future communications.

Can the receipts that users receive upon completing an RDC on a mobile device be customized? For example: can a financial institution’s logo be included in the receipt?

Only simple text is supported (no images, coloring, font change, or HTML supported at this time).

Is there a character limit for the FI’s name that appears on the RDC receipt a user receives?

In the subject line, there is a character limit of 200. According to Ensenta Support, the body has no character limit.

Does Narmi rely on Ensenta to post an RDC transaction to the core banking system? 

No. Narmi takes care of posting the mobile deposit transaction directly to the core.