Transmissions Connectivity Details

Your transmissions services and server connectivity
are moving to JPMorganChase

Welcome to JPMorganChase! Now that we’ve integrated your deposit accounts to our platforms, it’s time to integrate your Payments data transmissions services and server connectivity.

To maintain connectivity between our systems, all incoming and outgoing file transmissions (for your Payments products and services including Wires, ACH, Check Disbursements, Check Positive Pay, Statements and Reporting) must be integrated to the JPMorganChase platform. This will require your technical team’s attention to the following details.

New server addressing

If you are connecting through a public network, you must make the below changes to your route configuration.

If JPMorganChase will connect to you to transmit files:

Confirm your firewalls and access lists are still opened to the appropriate IP ranges. If these ranges are not open, please work with your administrator to make the necessary changes to any applications which use an IP access list in their configuration to allow the IPs to connect.

159.53.0.0/16 which is equivalent to 159.53.0.0 – 159.53.255.255
170.148.0.0/16 which is equivalent to 170.148.0.0 – 170.148.255.255
146.143.0.0/16 which is equivalent to 146.143.0.0 – 146.143.255.255

If you will connect to JPMorganChase to transmit or receive files, complete the following:

Open your firewalls and access lists for the following IP range:

198.36.0.0/22 which is equivalent to 198.36.0.0 – 198.36.3.255

Update your route configuration to point to the new URL(s) on port 22.

Environment	Old URL	NEW URL
Test	https://securefiletransfer.frbnp3.com	https://ftscat.mfts.jpmchase.com
Production	https://smft.firstrepublic.com	https://fts1.mfts.jpmchase.com

Supported SFTP/SCP Algorithms and Ciphers

HMAC

hmac-sha1-96
hmac-sha2-256
hmac-sha2-512
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com

CIPHERS

hmac-sha1-96
hmac-sha2-256
hmac-sha2-512
hmac-sha2-256-etm@openssh.com
hmac-sha2-512-etm@openssh.com

Key Exchange

ecdh-sha2-nistp256
ecdh-sha2-nistp384
ecdh-sha2-nistp521
diffie-hellman-group-exchange-sha256
diffie-hellman-group16-sha512
diffie-hellman-group18-sha512
diffie-hellman-group14-sha256

If your application does not support the available ciphers, or otherwise does not have the required encryption capabilities, then it may be necessary to change its configuration, upgrade it to current version or replace it.

JPMC Key Management Requirements

JPMC corporate policy requires all file transmissions, including test files, be sent via a secure session, and that all inbound transaction files be digitally signed.

All Certificates and Keys must be 2048-bit or more in key strength. Certificates must have a two-year-or-less expiration date and Keys must have a two-year-or-less expiration date.

Please exchange your keys with your assigned Implementation Engineer. Test the key/certificate properly before JPMC moves your setup to production. You should have different keys for CAT and Production file transfers. You can schedule your Key Addition session with your Implementation Engineer.

JPMorganChase adheres to these key standards:

Key must be RSA
Key strength must be 2048 bits or more
Key expirations must be two years or less

Testing the Connection

We encourage you to test connectivity and file delivery in the J.P. Morgan Client Acceptance Test (CAT) environment. If you encounter an error when testing, please examine the verbose logs from your application to identify the issue.

Perform an SFTP connection to ftscat.mfts.jpmchase.com on port number 22.
If using password-based authentication, log in using your user ID and password.
If using key-based authentication, use your private version of the public key that is loaded in the J.P. Morgan test environment.
If you need assistance with passwords, or with loading the keys, please contact your migration team representative.

Chase.com | JPMorgan.com | JPMorgan.com/payments

Privacy | Terms of Use | Accessibility | Cookies Policy | Regulatory Disclosures

Remember: We won't ask for confidential information such as your password, personal identification number (PIN) or other account information in a text message or email, or over the phone unless you call us about an issue, such as something to do with your account.

The information provided here is intended to help clients protect themselves from fraud and cyberfraud. It does not provide a comprehensive list of all types of fraud activities or identify all types of cybersecurity best practices. Your company or organization is responsible for determining how to best protect itself against fraud and cyberfraud and for selecting the best practices that are most appropriate to your needs.

Clients who do not use appropriate fraud-prevention tools increase their risk of losses and are liable for all losses incurred for payments originating using any authorized users’ security credentials or others who have designated transaction authority.