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

Updated on June 15, 2024

We have two environments: CAT (Client Acceptance Testing), also known as User 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 you use in production.

Regularly scheduled maintenance windows for CAT occur Tuesday 5 p.m. – 12 a.m. ET and Thursday 5 p.m. – 12 a.m. ET.  If you experience connectivity issue during these times, please retry after the window has expired.

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).
    • If the digital signature is successfully validated, an automated process will trigger an outbound file using what you originally sent.
    • If the digital signature cannot be validated, the file will not be processed.

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>

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.

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.

URL IP Address
SFTP/FTPS/AS2/HTTPS
transmissions-uat.jpmorgan.com (Primary) 159.53.62.207
AS2/HTTPS
transmissions-uat1.jpmorgan.com 159.53.62.210
transmissions-uat2.jpmorgan.com 159.53.62.209
transmissions-uat3.jpmorgan.com 159.53.62.208
transmissions-uat4.jpmorgan.com 159.53.62.211
transmissions-uat5.jpmorgan.com 159.53.62.213
transmissions-uat6.jpmorgan.com 159.53.62.212
transmissions-uat7.jpmorgan.com 159.53.62.215
transmissions-uat8.jpmorgan.com 159.53.62.216

Supported SSH Ciphers

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-sha2-256
  • hmac-sha256@ssh.com (alias support ending June 2023)
  • hmac-sha512@ssh.com (alias support ending June 2023)

Supported SSH Key Exchange Algorithms and Public Keys Supported

  • diffie-hellman-group-exchange-sha256

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:

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_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

CAT Keys / Certificates

Here are the J.P. Morgan test keys and certificates. Note that 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 if you require receiving signed files, please download the J.P. Morgan public test PGP key and rename as needed.

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.

Please use the applicable certificate for connections to node ECGQAA by NDM via IBM® Sterling Connect:Direct® with Secure:

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.