Customer-Facing Account Opening
Production
This MANTL product should be exposed to your customers on a subdomain of your primary website. We usually use the subdomain open. e.g. if your primary domain is the-bank.com, your customers might open accounts with us at https://open.the-bank.com.
Your networking engineer will be responsible for creating a CNAME record that points the subdomain to MANTL's platform at ss.prod.mantl.com.
This environment is secured with geofencing at the edge and only allows traffic originating in the US.
Note: Your chosen URL must be associated with a domain that your financial institution owns.
User Acceptance Testing (UAT)
Before going live in Production, each client will receive a UAT environment for configuration preparation, testing, and training.
Each environment has its own subdomain under *.uat.mantl.com
e.g. https://the-bank-ss.uat.mantl.com
Our UAT environments are secured with a firewall that require a username and password that will be provided by your Integration or CSM manager.
MANTL Console For Employees
Third-Party Analytics
MANTL leverages Datadog and Heap for tracking analytics. This allows us to monitor and troubleshoot user sessions. To provide the best support, we ask that your financial institution allow web browser traffic to these hosts:
https://*.browser-intake-datadoghq.com/https://cdn.heapanalytics.com/
If your financial institution uses adblockers, add these to your allow list.
Production
This is your live production environment applicants and Console users use to create and open accounts. This is a secure site that has several security measures in place to protect your data, including:
- Malicious and bot traffic filtering from Cloudflare
- Distributed denial of service (DDoS) protection
- Geo-filtering for non-US IP addresses
- Multifactor authentication at log-in secured using IP authorizations.
User Acceptance Testing (UAT)
Before going live in Production, you'll be given access to a clone of our Console product for configuration preparation, testing, and training. Any users, customers, or applications created in this environment will not be written to a real core.
Our UAT environments are secured with a firewall that require a username and password that will be provided by your Integration or CSM manager.