Locked code, expired link, or already downloaded

Four things stop a Safe Transfer. Three of them the sender has to fix.

Your code stopped working

Ten wrong attempts locks the code. Use the "I lost my code: verify again" link on the entry screen: it runs the identity check again and issues a new code. You do not need the sender for this one.

Before retyping, remember the code is not case-sensitive and dashes are optional. See Using your access code.

A locked code looks the same until you try

The landing page does not warn you that the code is locked: it still offers Enter access code. You find out on the attempt. So if a code you are sure about keeps failing, assume the lock rather than a typo, and re-verify.

The transfer has expired

The expiry date passed. Nothing was downloaded and nothing is recoverable from your side: the link is closed.

Ask the sender for a new transfer. They still have the files; sending again takes a minute.

The message "This transfer is no longer available: the link has expired. Nothing was downloaded", with a note that the access was recorded in the sender's audit trail.

Already downloaded

A one-time transfer that has been used. The link closed itself after the first successful download, which is what one-time means.

Check your Downloads folder first: often the file is already there and the "problem" is that you came back for a second copy. If it genuinely did not save, ask the sender to resend. See One-time links and expiry dates.

The message "Already downloaded: this one-time transfer has already been downloaded and is now closed."

Either way, the sender can see it

Both of these screens say the attempt was recorded in the sender's audit trail. That works in your favour: the sender can confirm the link really was dead rather than taking your word for it.

Verification will not pass

The check matches against the name the sender entered for you. If they mistyped it, or used a shortened version that does not match your ID, the check can fail however carefully you do it.

Tell them what name is on your ID and ask them to correct it and resend. The provider holds the detail of why a check failed: swipesign only knows that it did.

No message offers a way around

If any of these appear, no legitimate alternative route exists. A message offering another link to the same files, especially one asking for payment or a code, should be treated with suspicion. Contact the sender using details you already had.

What to tell the sender

The subject line of the transfer, roughly when you tried, and the exact message you saw. They can see your progress in their audit trail, whether you opened it, verified, and downloaded, which usually identifies the problem immediately.