An AS2 connection allows you to securely exchange EDI, XML, and/or Delimited messages over the internet, using Multipurpose Internet Mail Extensions (MIME) and the hypertext transmission protocol (HTTP) as the transport protocol. Use the details below to set up your AS2 connection with Rithum.
Depending on when you integrated to Rithum’s platforms via AS2, you may use one of the following destinations to connect to us:
http://as2.commercehub.com |
OR | https://as2.rithum.com/us/receive |
The following information is for connections to https://as2.rithum.com/us/receive.
Note: If you have not been contacted about moving from as2.commercehub.com or As2-*.dsco.io to https://as2.rithum.com/us/receive, do not attempt to utilize the following connection information without reaching out to Rithum Software Support first.
Prerequisites
- If your AS2 client software does not support Server Name Indication (SNI) headers, refer to the SNI Header section for more information.
- If you use any of the following softwares for AS2, you may need to update your version or upgrade your software to be compatible with Rithum AS2. Reach out to Software Support for further guidance:
IBM iSeries
IBM Sterling
OpenText GXS BizManager
ZMOD AS2
- If you maintain multiple AS2 connections to the Rithum platform, reach out to Software Support to confirm the AS2 connections being migrated.
Recommended Connection Settings
- TLS v1.3 Enabled
Minimum Connection Requirements
- SNI Headers Enabled
Environment Details
Staging
Platform Endpoint URL: HTTPS://as2-staging.rithum.com/us/receive
AS2 certificate: as2-staging_rithum_com.crt
Environment Details
Production
Platform Endpoint URL:
HTTPS://as2.rithum.com/us/receive
Note: This Endpoint URL requires HTTPS with TLS v1.2+ connections.
Asynchronous MDN Endpoint URL:
If you intend to use an asynchronous connection, send MDNs to: HTTPS://as2.rithum.com/us/receive/mdn
Note: We recommend that you send your asynchronous MDN to the URL within 5 minutes of receiving the file. After 5 minutes, the transfer will be considered failed.
Port: 443
Static IP Pool:
• 3.227.140.114
• 54.225.3.225
• 3.224.250.206
• 44.236.75.232
• 52.42.144.200
• 52.39.18.225
AS2/Signing certificate: as2_rithum_com.crt
Do not use before April 28, 2025, 12pm ET.
Expires on April 24, 2026
Intermediate certificate: DigiCertCA.crt
SSL certificate:
Rithum uses a 3rd Party Certificate provider to provide SSL/TLS certificates for our domains. The provider may update the SSL/TLS certificates on our service at any time. Rithum does not support or recommend manually installing SSL/TLS certificates to your AS2 software. Your AS2 server software should connect to our AS2 server URL and use the valid SSL/TLS certificates at https://as2.rithum.com/us/receive automatically.
Server Name Indication (SNI) Header Requirements
Action required:
1. Verify SNI Support. Please check with your AS2 client software provider or your IT department to ensure that your AS2 client supports SNI headers.
2. Upgrade if Necessary. If your AS2 client does not support SNI, an upgrade will be required. We recommend you contact your software vendor for the necessary updates or patches. If you’re unable to upgrade your AS2 software, you may be interested in other integration options.
3. Test Connectivity. After confirming SNI support, please reach out to Software Support if you would like to test the new connection. We can confirm that both you and Rithum are able to send and receive messages from the new server.
If you have any questions or need help verifying SNI support, reach out to Software Support.