Effective October 1, 2024 the Production maintenance window will change to:
Saturday 5:00 p.m. ET – Sunday 1:00 a.m. ET
For more information, please visit our Recommended Best Practices.
Overview
J.P. Morgan Host-to-Host is communications & security platform used for file transmission that supports internet connectivity for external clients to send bulk payments or receive reporting files using SFTP, HTTPS, and AS2 protocols.
Upcoming Events
Production Maintenance Window change
October 1, 2024
SFTP SSH Key Replacement1Q2025
Our SSH Key for the SFTP Protocol will be replaced in 1Q2025, as the old key will expire. The new key will be available for download on our SSH Support.
FTPS SSL Certificate Replacement
1Q2025
Our SSL certificate for the FTPS protocol will be replaced in 1Q2025, as the old certificate is expiring. The new certificate will be available for download on our SSL Support page.
Data Center Migration
2024
Beginning 2024 all Host-to-Host file transmissions will begin transitioning to our new production strategic data centers. All transmissions will need to utilize the new data centers by August 31, 2024.
Additional details are available on the H2H Data Center Migration pages.
SSL AS2, HTTPS, NDM Certificate Replacement2Q2025
Our SSL certificate for the AS2, HTTPS, NDM protocols will be replaced in 2Q2025, as the old certificates will expire. The new certificates will be available for download on our SSL Support.
- All keys used with file transmission must expire in 2 years or less. All expiring keys must be renewed with unique and newly created keys and not previously used. There are no exceptions to this policy.
- Transport Layer Security version 1.2 (TLSv1.2) is the minimum standard for communication session encryption for the following applications and protocols:
Applicability Statement 2 (AS2)
Hypertext Transfer Protocol Secure (HTTPS)
File Transport Protocol Secure (FTPS) – No longer supported for new setups
NDM via IBM® Sterling Connect:Direct® with Secure+®
- The Administrative Procedures for Certificates include the following standards:
- All certificates and keys must have a finite validity period of two years or less.
- No certificate shall be accepted unless it adheres, at minimum, to the following cryptographic specification:
- Message digest: SHA-256, AES256
- Asymmetric algorithm: RSA, DSS (DSS is not supported for SSH protocols).
- Asymmetric algorithm key length: 2048 bits or more.
- Elliptical curve algorithms are not supported at this time.
Certificates, Keys and Ciphers
Find everything you need, from bank security credentials to supports cryptography settings, to ensure your systems are compatible with J.P. Morgan Host-to-Host.
-
Partner Key Management
The PKM process is used by clients to submit their production security credentials for renewal.
-
Best Practices
Review best practices to help keep file transmissions reliable and secure and ensure the best experience.
-
Client Acceptance Testing (CAT)
Test and verify connectivity using our CAT, also known as UAT, environment.
-
H2H Resiliency
Configure your system to use DNS and short-lived IP caching.
Support
Questions? Contact our support team at 978-805-1200 or HosttoHost.helpdesk@jpmorgan.com. Representatives are available to assist you 24 hours a day, Monday through Friday. Government, municipal and public sector clients should call 844-718-0643.
Please note the support team cannot advise clients on specific actions needed to make the required system changes. Clients should contact the application vendors for this information.
All trademarks, trade names and service marks appearing herein are the property of their respective owners.