Receive AS2 messages and deliver them over SFTP
Take AS2 messages from your trading partners and deliver the verified payload securely over SFTP. DocEvent terminates AS2 — decryption, signature verification and the MDN receipt — and pushes each file to your SFTP server over SSH, with retries and a full audit trail.
From
AS2
To
SFTP
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How AS2 to SFTP routing works
Source
AS2
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
DocEvent Channel
routes · retries · logs
Destination
SFTP Server
Files are pushed securely to an SFTP server over SSH.
1
File arrives via AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to SFTP
SSH key or password authentication. Standard port 22. Configurable remote path.
Common use cases
Real workflows that teams automate with a AS2 → SFTP channel.
- Deliver decrypted partner EDI into your SFTP intake directory
- Bridge AS2 trading partners to an SFTP-only internal platform
- Keep AS2 at the edge and SSH inside your own network
- Onboard an AS2 partner without touching your SFTP-based processing
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the AS2 or SFTP side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.Destination:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages