FTP and FTPS

Riversoft® STCP DirectLink exchanges files with partners’ FTP and FTPS (FTP over TLS) servers. The connection is always started by Riversoft STCP DirectLink: there is no FTP service for inbound connections. To receive connections from partners, use SFTP, AS2 or Webhook.

Component	Who starts the connection	Function
FTP connector	Riversoft STCP DirectLink (outbound connection)	Connects to the partner’s FTP or FTPS server to send and fetch files.

Outbound connections (FTP connector)

Send

    flowchart LR
    subgraph DL[Riversoft STCP DirectLink]
      SA["saida directory"] --> C[FTP connector]
    end
    C -->|send| P[Partner FTP/FTPS server]

Fetch

    flowchart LR
    subgraph DL[Riversoft STCP DirectLink]
      C[FTP connector] --> EN["entrada directory"]
    end
    P[Partner FTP/FTPS server] -->|fetch| C

Note

Sending and fetching can happen in the same connection: Riversoft STCP DirectLink first sends the files, then fetches the partner’s files. Depending on the mode configured in the user, the connection can also only send or only fetch.

Riversoft STCP DirectLink connects to the partner’s server by schedule, or when the operator starts the connection in the Riversoft Console Portal. In the same connection, it:

sends the files available to the partner in the user’s mailbox (saida directory);
fetches the partner’s files from the agreed directory and writes them to the entrada directory of the mailbox.

Step	Behavior
Send	The file is written with a temporary name (temporary directory or extension, when configured) and renamed at the end.
Fetch	Only files matching the configured mask are fetched.
After fetching	The file can be copied to a backup directory on the partner’s server and, if configured, removed from the source directory.
Mode	The transfer always uses passive mode.
Security	No TLS (FTP), explicit FTPS or implicit FTPS. In FTPS, the connection can validate the server certificate and use a client certificate.
Network	The connection can go through an HTTP, HTTPS, SOCKS4 or SOCKS5 proxy, and through a specific local address.

What to agree with the partner

Item	Description
Server	FTP or FTPS server address and port.
Security	FTP, explicit FTPS or implicit FTPS; client certificate and CA, when required.
Credential	User and password.
Directories	Where to deliver the files and where to fetch them, with the mask of the files to fetch.
Post-processing	Whether fetched files must be removed or moved to backup on the partner’s server.

These details are registered in the user, in the Riversoft Console Portal, together with the connection schedule.

Security

Use FTPS whenever the partner supports it. In FTP without TLS, user, password and files travel unencrypted.
Keep server certificate validation enabled.
Prefer SFTP when the partner offers both options.

AS2 SFTP