B2B file transfer

How it works

Expect keys, a folder contract, a schedule, and a receipt. A consumer share link is the wrong pattern. Identities are organizations, not only people.

A distributor pushes a 600 MB catalog nightly to a retailer over SFTP. The agreement names the key, the path, and a 02:00 deadline. A missed file pages both sides. A personal link would not page anyone.

How it differs

B2B is not client portal traffic, though a portal can serve a business user. The test is whether a system is the counterparty.

Skipping the agreement and 'just sending' leaves no one to call when the key expires.

Write the profile.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For b2b file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive b2b file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.