J.P. Morgan Host-to-Host File Transmission

As part of the CBPR+, the Society for Worldwide Interbank Financial Telecommunication (SWIFT) and leading Payment Market Infrastructures (PMI) mandates the inclusion of Country Code and Town Name for all payment fields. This mandate aims to offer precise compliance information and higher automation in processing payments.

As of November 2025, there will be three valid formats for providing postal addresses in payment messages:

1. Fully unstructured: Will be decommissioned by November 2026, and all address fields must be in a structured or hybrid format.
2. Fully structured: Typically comprising distinct components such as street name, post code, town, and country details.
3. Hybrid option: combines structured elements within Postal Address (Town Name and Country are mandatory information) as well as unstructured format (AddressLine can be up to 2 lines of 70 characters) for greater flexibility during the transition.

Who is impacted?

These requirements apply to cross-border payments sent over the SWIFT network and to payments processed through clearing systems that require hybrid or fully structured addresses. Impacted systems include Fedwire, CHIPS, SEPA, Swiss Interbank Clearing, CHAPS-UK, Target2-Euro, and South Africa’s SAMOS. Payments that do not follow the new address requirements may be rejected or delayed, which could impact your processing timelines.

ISO20022 Support

X12 Support

Global Flat File (GFF) Support

Our SSL certificate used for AS2, HTTPS, and NDM protocols will be replaced on March 21, 2026. Additional details can be found on our H2H SSL Support page as the renewal date approaches.

Our SSH key and SSL certificate used for SFTP and FTPS protocols will be replaced November 7, 2026. Additional details can be found on our H2H SSH Support and H2H SSL Support pages as the renewal date approaches.

• 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.
    • Beginning in 2Q2025, all certificates and keys used for transport authentication must have a finite validity period of 1 year 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.
  • Elliptical curve algorithms are not supported at this time.