For compliance administrators, IT administrators, and implementation teams.
Before you begin
Confirm what files your organization needs to transfer to MCO eComms.
Confirm the source or integration that will use the SFTP connection.
Confirm whether your organization requires inbound file delivery to MCO eComms or outbound retrieval from a third-party system.
Confirm who on your team should receive the SFTP connection details.
Identify the public IP address your organization’s SFTP client or automated transfer process will use.
Contact your MCO onboarding representative or MCO Service team to request SFTP setup.
NOTE: MCO must allowlist the public IP address used by your SFTP client before the connection can be used.
SFTP connection overview
Secure File Transfer Protocol, or SFTP, is used to transfer files securely between your organization and MCO eComms.
Some source setups require customers or third-party systems to place files in an MCO-managed SFTP location. Other setups require MCO eComms to retrieve files from a third-party SFTP location. Your MCO onboarding representative or MCO Service team will confirm which approach applies to your implementation.
After the SFTP setup request is approved, MCO provides the connection details needed to complete the transfer configuration.
Request SFTP setup
Contact your MCO onboarding representative or MCO Service team.
Provide the source, integration or purpose of the required SFTP.
Confirm the expected file type or data source.
Confirm whether files will be transferred to MCO eComms or retrieved by MCO eComms.
Provide the customer contact who should receive the SFTP details.
Provide the public IP address your organization’s SFTP client or automated transfer process will use.
Wait for MCO to confirm the SFTP setup is complete.
SFTP details provided by MCO
After setup is complete, MCO provides the SFTP details required for the connection.
Detail | Description |
Hostname | The SFTP server address used for the connection. |
SFTP username | The username assigned to your organization or source setup. |
Credentials | The authentication details required to connect to the SFTP location. |
Folder path | The folder location to use, when a specific path is required. |
IP allowlisting | MCO allowlists the public IP address your organization provides for the SFTP client or automated transfer process. |
File handling instructions | Any source-specific instructions for naming, packaging, encrypting, or placing files. |
NOTE: If your organization’s SFTP client IP address changes, notify MCO before the next transfer. File transfer may fail until the new IP address is allowlisted.
Configure your file transfer
After you receive the SFTP details from MCO, configure your SFTP client, automated process, or third-party system.
Enter the hostname provided by MCO.
Enter the SFTP username provided by MCO.
Configure the authentication method using the credentials provided by MCO.
Configure the folder path, if MCO provides one.
Confirm any file naming or packaging requirements for the source.
Transfer a test file if MCO requests one.
Notify MCO after the test file is uploaded or the connection is configured.
WARNING! Do not change file names, folder paths, compression format, or encryption settings unless MCO instructs you to do so. Changes can delay or prevent file processing.
Test the SFTP connection
MCO may ask your organization to complete a test transfer before the source is moved into production.
Test item | Description |
Connection test | Confirms the hostname, username, and credentials work as expected. |
Folder access | Confirms your organization can access the required SFTP folder. |
File transfer | Confirms files can be uploaded or retrieved successfully. |
File processing | Confirms MCO eComms can process the transferred file, when applicable. |
Ongoing file transfer
After the SFTP connection is active, files should be transferred according to the agreed schedule and source requirements.
Your organization should monitor the transfer process and notify MCO if:
Files are not being delivered as expected.
A third-party system changes the file format.
File names or folder structures change.
Credentials need to be rotated.
A scheduled transfer fails.
The source or integration should be paused or disabled.
Result
The SFTP connection is configured and ready for the agreed source or integration. Files can be transferred securely using the hostname, username, credentials, and file handling instructions provided by MCO.
After files are received and processed, supported communications can be made available in MCO eComms according to your organization’s configured setup and policies.