We no longer support this browser. Using a supported browser will provide a better experience.

Please update your browser.

Close browser message

J.P. Morgan Host-to-Host Client Acceptance Testing

Client Acceptance Testing (CAT)

J.P. Morgan has two environments: CAT (Client Acceptance Testing) and Production. Each environment has multiple URLs that can be used for connectivity. Usually, the URL that you use in CAT will be similar to the URL that you use in production.

Please note, production data should never be transmitted to the CAT environment and test data should never be sent to the production environment. In order to ensure this does not happen, we require that you give us one certificate or key for CAT, and a different certificate or key for production.

CAT environment changes are implemented prior to Production without notice.

 

CAT Self-Service Testing

For Self-Service testing, please follow the steps below:

  1. Connect to the J.P. Morgan Host-to-Host test server to verify connectivity.
  2. Send a digitally signed "junk" text file to verify the process flow using the file naming convention below (case sensitive).

a. If the digital signature is successfully validated, an automated process will trigger an outbound file using what you originally sent.

b. If the digital signature cannot be validated, the file will not be processed.

 

SFTP/FTPS Process

Test URL: transmissions-uat.jpmorgan.com
Inbound Test (no process) File
Directory: /Inbound/Encrypted
File name: <H2H_PartnerID>.TEST.IN.<anything>
<H2H_PartnerID> = H2H User ID. This would be the same ID used for Production.
<anything> = any alpha numeric character including dashes, dots or underscore, but no spaces and no use of "&"

If the above file is validated, we will stage the same file for you to download (see below).

Outbound test Ack File
Directory: /Outbound/Encrypted
File name: <H2H_PartnerID>.TEST.OUT.<seq#>.<date/time>

 

AS2 TEST process

Test URL: transmissions-uat.jpmorgan.com or the HTTPS URL assigned to you.
Inbound Test (no process) File
File name: <H2H_PartnerID>.TEST.IN.<anything>
<H2H_PartnerID> = H2H User ID. This would be the same ID used for Production.
<anything> = any alpha numeric character including dashes, dots or underscore, but no spaces and no use of "&"

File name should be presented the same location where you present it for your existing production files (e.g., Content-Type, Content-Disposition).

If the above file is validated, we will send the same file to you as the delivery URL we have for you in CAT. You may also receive the positive MDN back from us for your transmission, which can also confirm the positive delivery of the file to us.

 

HTTPS TEST Process

Test URL: transmissions-uat.jpmorgan.com or the HTTPS URL assigned to you

Inbound Test (no process) File

Full Deliver URL: https://transmissions-uat.jpmorgan.com/invoke/FMSPartnerInterface.inbound/httpGateway

TEST File parameters:
&jpmcDataType=TEST
&jpmcDataFormat=IN
&jpmcProtocol=HTTPS
&jpmcSecurity=PGP/Bypass (based on your security configuration)

If the above file is validated, we will stage the same file for you to download, which can be downloaded using the below parameters:
URL: https://transmissions-uat.jpmorgan.com/invoke/FMSPartnerInterface.inbound/downloadJPMCData

&jpmcDataType=TEST
&jpmcDataFormat=OUT
&jpmcProtocol=HTTPS
&jpmcSecurity=PGP/Bypass (based on your security configuration)

CAT URLs

All SFTP and FTPS connections will utilize the Primary URL. AS2 and HTTPs connections could potentially use one of our other URLs. If you are unsure which URL you should be using, please contact our Support team.

  • SFTP/FTPS/AS2/HTTPS

   transmissions-uat.jpmorgan.com (Primary)

  • AS2/HTTPS

   transmissions-uat1.jpmorgan.com

   transmissions-uat2.jpmorgan.com

   transmissions-uat3.jpmorgan.com

   transmissions-uat4.jpmorgan.com

   transmissions-uat5.jpmorgan.com

   transmissions-uat6.jpmorgan.com

   transmissions-uat7.jpmorgan.com

   transmissions-uat8.jpmorgan.com

 

Host-to-Host Supported SSH Ciphers

Support for HMAC-SHA1 and diffie-hellman-group-exchange-sha1 was discontinued in Q12021.

Only the following ciphers are supported for internet-based connections to CAT via applications that use Secure File Transfer Protocol (sFTP):

Supported Ciphers for SSH

  • AES128-CTR
  • AES192-CTR
  • AES256-CTR

Supported Keyed-Hash Message Authentication Code (HMAC)

  • hmac-sha2-512
  • hmac-sha512
  • hmac-sha2-256
  • hmac-sha256

Supported SSH Key Exchange Algorithms and Public Keys Supported

  • diffie-hellman-group-exchange-sha256

 

Host-to-Host Supported SSL Ciphers

CAT environment changes are implemented prior to Production without notice.

Only the following ciphers are supported for internet-based connections to CAT via applications that use:

  • File Transport Protocol Secure (FTPS)

   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

   TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

   TLS_DHE_DSS_WITH_AES_256_GCM_SHA384

   TLS_DHE_DSS_WITH_AES_256_CBC_SHA256

   TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

   TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

   TLS_DHE_DSS_WITH_AES_128_GCM_SHA256

   TLS_DHE_DSS_WITH_AES_128_CBC_SHA256

   TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

   TLS_RSA_WITH_AES_256_CBC_SHA256

   TLS_RSA_WITH_AES_128_CBC_SHA256

   TLS_RSA_WITH_AES_256_GCM_SHA384

   TLS_RSA_WITH_AES_128_GCM_SHA256

 

  • Applicability Statement 2 (AS2) and Hypertext Transfer Protocol Secure (HTTPS)

   TLS_RSA_WITH_AES_128_CBC_SHA256

   TLS_RSA_WITH_AES_256_CBC_SHA256

   TLS_RSA_WITH_AES_256_GCM_SHA384

   TLS_RSA_WITH_AES_128_GCM_SHA256

 

CAT Keys / Certificates

Please find J.P. Morgan test keys and certificates. Also note we will also need your keys or certificates in order to successfully authenticate a connection. If you experience authentication failures, please contact our support team for assistance.

If you require encrypting files you transmit or receive signed files, please download the J.P. Morgan public test PGP key and rename as needed.

A new J.P. Morgan test PGP key will be made available after July 28 and the current key replaced on August 5.

If you connect via SFTP to transmissions-uat.jpmorgan.com on port 22, please download the J.P. Morgan public test key and rename as needed.

If J.P. Morgan pushes files to you via SFTP, please download the J.P. Morgan public host test key and rename as needed.

If you connect via FTPS to transmissions-uat.jpmorgan.com on port 21, please download the J.P. Morgan public test key and rename as needed.

If you connect via AS2 or HTTPS to transmissions-uat.jpmorgan.com, please download the J.P. Morgan public test key and rename as needed.

If you are doing Strict Host Checking, you will also need to download the certificate for the specific URL you are using, in addition to the primary certificate.

New J.P. Morgan test SSL certificates will be made available after July 26 with the existing test certificates replaced on August 23

Support

If you have any questions, please contact the J.P. Morgan Solution Center Transmissions Support team at 978-805-1200, or by emailing CAS.helpdesk@jpmchase.com. Representatives are available 24 hours a day, Monday through Friday. Government, municipal and public sector clients should call 844-718-0643.

The support team cannot advise clients on specific actions required to make changes to their systems. Clients should contact their application vendors for assistance.

All trademarks, trade names and service marks appearing herein are the property of their respective owners.