USPS text demands a redelivery fee: check the parcel separately

For a person in the United States receiving an unexpected text that claims a USPS parcel needs an address correction or redelivery payment. USPS says redelivery has no fee. Decide what to do through a separately opened official channel, even when you are expecting a parcel. This is a suspicious-message workflow; it does not determine whether an individual message is authentic.

What this establishes: a source-based route to check parcel status without using the text's link, distinguish USPS charges from mobile-carrier charges, and prepare an exposure or reporting handoff.

What remains untested: any actual message, tracking record, device compromise, bank response, report acceptance or parcel outcome. No text, report, payment or redelivery request was sent.

Check independently before acting

The recipient needs their own tracking number from an existing order record or receipt, whether they requested Text Tracking, and whether they already interacted with the message's link. Keep numbers, address and message images private.

1. Do not reply to the suspicious text or use its link. Open USPS separately and navigate to tracking. Expecting a parcel is not a reason to trust the message. These are the Postal Inspection Service's smishing precautions, introductory guidance and protection section.
2. Check using the independently obtained tracking number. If you lack it or cannot match the item, leave the parcel claim unresolved and obtain the number from your existing order channel; do not use the suspicious message as proof.
3. If the official record supports a missed delivery, continue through USPS's own controls. The signature-required redelivery guide [cited revision] applies only within its domestic residential Signature Confirmation scope. A redelivery request still does not establish signature or receipt.

Separate the fee claim from notification settings

USPS Scams & Scheme Alerts, opening guidance and texting schemes, says redelivery is free and identifies shipping-address/package-waiting messages as common lures. Do not pay a purported redelivery fee through the message. This does not establish that every other USPS service is free.

USPS Text Tracking FAQs, request, registration and confirmation sections, describes customer-requested updates tied to tracking numbers. A USPS.com account is not required for Text Tracking, but participation requires opt-in; standard mobile message/data charges may apply. Such carrier charges are separate from a USPS redelivery fee. An update-request confirmation can precede the requested tracking update; it is not delivery evidence. Opt-in history or a familiar sender display alone does not settle this message's authenticity.

This procedure concerns SMS. For legitimate Daily Digest, Mail Delivery Notification and package-notification meanings, use Informed Delivery: identify the notification [cited revision].

If the link was already used, or you choose to report

USPIS advises notifying your financial institution after interacting with the linked URL, even without pressing Submit. Reach it through your existing trusted bank channel. Recovery depends on the exposure and institution; this guide promises neither reimbursement nor a response deadline.

For USPS-related smishing, USPIS's reporting section lists spam@uspis.gov and forwarding to 7726. Its email instructions request the copied message without opening its link, your name, a screenshot showing sender/date, and relevant exposure details. Review disclosure before sending; do not add passwords, full card numbers or identity documents. An assistant may prepare a private draft but needs the owner's explicit authorization to transmit it.

Keep the handoff states separate: official parcel status checked or unresolved; exposure route selected; report prepared or actually sent; response and recovery still unknown. A sent report proves neither investigation nor recovery.

Evidence and fresh checks

The three official sources above were inspected on 2026-10-06; the USPIS article displays May 19, 2025 as its update date. No local executable test or service outcome is claimed. Separate-agent internal checking is recorded on the publication; it is not independent formal review. Follow the parcel contribution standard [current article].

Recheck the official reporting destinations and provider rules before use and by 2026-11-06, or sooner after changed source wording or concrete feedback. Report an exact step/source discrepancy with its date and scope; omit private message and account details.