Exchange files with your trading partners over AS2 without running an AS2 appliance behind it. AS2 is the secure B2B protocol big retailers and clearinghouses require. Files.com is a standards-compliant AS2 endpoint with signed MDN receipts on every message, certificates managed in the app, and a folder for every partner. Your partner connects the same way they always do and never knows what’s behind it, so you answer the mandate without buying and running a server.
No credit card required · 7-day free trial · Live in minutes
If you sell to a large retailer, file healthcare claims, or supply a manufacturing network, someone on the other end almost certainly requires AS2. The usual way to answer that is to stand up an on-premise AS2 server (Sterling, GoAnywhere, Cleo, Axway) and then live with certificate rotations, capacity planning, and patching for the life of the box.
Files.com runs AS2 without the box. Turn AS2 on, exchange certificates with your partner, and the endpoint is live. It runs with the same governance, scale, and automation as the rest of your file transfers, so there’s nothing separate to operate.
AS2 sits on the same site as SFTP and FTP, which is how retailers and distributors run order, inventory, and shipment file exchange with every trading partner on one endpoint.
Pillr Health moved its 340B partner exchange off Axway after AS2 transfers and PGP decryption kept failing. On rebuilding those same workflows on Files.com:
“Creating integrations is so easy, especially the AS2 connections. PGP encryption is so seamless to implement.”
Encrypted, signed, and receipted, with a folder for each partner so files flow in and out.
Files.com receives AS2 over HTTPS on port 443, with S/MIME encryption and signing. The endpoint follows the RFC 4130 standard, so your partner connects exactly the way they connect to anyone else.
Every transmission comes back with an MDN, a Message Disposition Notification. That is the signed digital receipt that proves your partner got the exact bytes you sent. Files.com supports synchronous and asynchronous receipts, so neither side can later claim a file never arrived, and you never have to wonder whether it did.
Turn AS2 on and Files.com creates a folder structure for each trading partner, the company on the other end of the exchange. Each one gets an inbox, an outbox, and a sent folder. Drop a file in a partner’s outbox and it goes out. Files that arrive land in their inbox, ready for the rest of your workflow, so you never wire up the plumbing by hand.
Outbound messages retry on their own until delivery is confirmed. Paired with the MDN receipt, every transmission either comes back confirmed or shows up as a failure for you to act on. Nothing gets silently dropped.
AS2 carries the document byte-for-byte. The platform reads, converts, and validates it alongside the transport.
TransformScript parses and transforms X12 and EDIFACT documents natively, so the 850 that arrives becomes the file shape your ERP ingests. You write the mapping as expressions in the platform, not as a translator you build and host.
File extraction pulls fields out of EDI documents into searchable metadata, and content validation reads inside the parsed document, flagging the delivery whose contents are wrong, not just missing.
Files.com customers exchange AS2 and EDI with effectively every major trading partner. The big retailers and distributors mandate it from their vendors, the healthcare clearinghouses mandate it from their filers, and Files.com presents to each one as a standards-compliant RFC 4130 endpoint. Your partner connects the way they connect to everyone else, and the mandate is answered.
Upload, renew, and rotate the encryption and signing certificates for each partner right in the Files.com UI. Expiration alerts warn you before a certificate lapses, so a missed renewal never takes a partner offline. You stop editing connection scripts on a server every time something rotates.
Your partner sees a standards-compliant AS2 endpoint and never knows what’s behind it. There’s no on-premise AS2 server to size, patch, or babysit. You skip running Sterling, GoAnywhere, Cleo, or Axway just to answer one AS2 mandate.
AS2 is a first-class part of Workflows and Automation. A file landing in a partner’s inbox can trigger a workflow. Any workflow can deliver its result out to a partner over AS2 as the final step. It works in both directions, so a partner exchange can drive automation and automation can drive a partner exchange.
When a partner sends a spike of traffic, Files.com expands to absorb it. No per-endpoint sizing, no capacity planning. An appliance in a rack can’t do that.
The AS2 world treats key-signing ceremony as the point: strict validation chains, rejected transmissions, hours spent comparing certificate fingerprints. And the documents being protected are inventory files and shipment manifests, the paperwork that used to ride taped to the side of a pallet. AS2’s signing ceremony is wildly out of proportion to the documents it protects, and much of it survives because legacy vendors profit when AS2 is hard.
Files.com defaults to making the delivery work. Auto mode reads the first message from a partner and locks validation to the most secure level that partner actually supports. Nobody spends a week tuning settings, and an expired certificate doesn’t strand a shipment your business is waiting on. When a partner genuinely requires strict validation, turn it on: full chain-of-trust enforcement is a per-partner setting, not a different product.
Setting up a new AS2 partner is part of onboarding them onto Files.com. Each partner gets a self-contained space and exchanged certificates, handled through partner onboarding. If a partner wants an extra encryption layer, you can wrap files in PGP encryption on top of the AS2 exchange.
AS2 is available on the Power tier and above, and Enterprise includes as many connections as you require. Files.com publishes what each plan includes.
The same shape shows up at every manufacturer, distributor and retailer that moved partner EDI onto Files.com.
Retailers, 3PLs, carriers and VANs each connect the way they already do: SFTP for most, AS2 where it is mandated, FTPS for the holdouts. Your ERP or translator reads and writes one folder tree, so adding a partner never means adding a server.
When a big-box retailer or a clearinghouse requires AS2, the connection is set up in the same console as the SFTP accounts. Certificates, MDNs and retries are handled for you, so nobody maintains a Java gateway for three partners.
Each partner sees only its own inbound and outbound folders, and automations move 850s in and 810s out on arrival. A cross-partner leak stops being possible, and the audit log shows exactly what each partner sent and picked up.
Partners connect to a hostname on your domain, and the two dedicated IP addresses that come with it give their firewall teams a short list to allowlist once, so onboarding does not stall on the counterparty’s change ticket.
What teams ask about how Files.com handles AS2, MDN receipts, EDI, and compatibility with their trading partners.
AS2 (Applicability Statement 2, defined in RFC 4130) is the secure peer-to-peer protocol used for B2B file exchange, most often to move EDI documents between trading partners. Large retailers like Walmart and Target, healthcare claims clearinghouses, and supply-chain networks commonly require their vendors to exchange files over AS2. Files.com is a standards-compliant AS2 endpoint, so you can meet that requirement without running your own AS2 server.
Files.com follows RFC 4130 and is compatible with the major AS2 clients and servers, including IBM Sterling, Axway, Seeburger, and Cleo. Your trading partners connect the same way they connect to anyone else and never know what is behind your endpoint.
Files.com sends and receives AS2. Inbound transmissions arrive on port 443, and outbound messages transmit to your trading partner’s endpoint with AES-256-CBC encryption and SHA-256 signing. Drop a file in a partner’s outbox and it transmits; files your partner sends land in their inbox.
Files.com parses and transforms X12 and EDIFACT documents natively with TransformScript, right alongside the AS2 transport. The AS2 layer moves your payload byte-for-byte, and the platform handles translation, extraction, and validation on the same parsed document. One system carries the file and converts it.
Files.com pairs every AS2 transmission with an MDN (Message Disposition Notification), a signed digital receipt that cryptographically confirms the recipient got the exact bytes sent. That gives you non-repudiation: neither side can later claim a file did not arrive. Files.com supports both synchronous and asynchronous MDNs and retries outbound messages automatically until delivery is confirmed.
Files.com limits outgoing AS2 messages to 25 MB, and most EDI payloads are far smaller than that. Higher limits are available on request, and compressed incoming messages decompress automatically.
Files.com customers exchange AS2 and EDI with effectively every major trading partner: Walmart, Amazon, Target, Costco, Kroger, the healthcare clearinghouses, and the rest of the networks that mandate AS2 from their vendors. Files.com presents as a standards-compliant RFC 4130 endpoint, so it connects wherever the mandate comes from.
Files.com logs every AS2 transmission to the platform audit log, with the sender and receiver identities, the MDN status, and the certificate fingerprint used. The log exports to your SIEM, so partner exchanges land in the same audit trail as the rest of your file transfers.
Files.com offers AS2 on the Power tier and above. Enterprise includes as many AS2 connections as you require; Power includes an allotment you can expand. Current connection counts and pricing are published for every plan.
Files.com hosts the endpoint. Each partner gets its own SFTP, FTPS or AS2 connection on your domain, lands purchase orders in a folder your ERP or translator already polls, and picks up invoices and ship notices from an outbound folder that automations fill. There is no server to patch, and your integration keeps reading the same paths. That is how order, inventory and shipment files move with suppliers and 3PLs.
Yes. Files.com folder permissions scope each partner account to its own folder tree on every protocol, and Partner Workspaces let the partner manage its own users inside that boundary. Every login and transfer is recorded per partner in the audit log.
Yes. AS2 runs on the same Files.com site as SFTP, so a partner that mandates AS2 gets a connection, a certificate and MDN handling in the console you already use, and its documents land in the same folder structure and automations as everyone else’s.
Start the 7-day trial, exchange certificates with your trading partner, and have a standards-compliant AS2 endpoint running. You get signed receipts and automatic retries, with no appliance to operate.
No credit card required • Free for 7 days • Live in minutes
Order, inventory, and shipment files with suppliers, carriers, and 3PLs on one endpoint.
Transport, X12 translation, validation, and routing for every trading partner, plus the transaction-set library.
Self-service partner onboarding — branded intake, a workspace each.