Summary: A legacy "FedEx Test" account (FedEx's old SOAP web services) left on a test profile next to the active FedEx account makes FedEx reject the credentials. Remove the legacy FedEx Test account and reprocess.

Problem

Shipments in a test or QA profile stop processing and FedEx returns the credentials as invalid, even though shipping worked recently. The profile has a "FedEx Test" account alongside the active FedEx account.

Cause

FedEx no longer supports its legacy web services (SOAP). When a legacy "FedEx Test" account stays on the profile next to the active new-API FedEx account, the legacy account's calls are rejected and it shows up as invalid FedEx credentials at process time. The error comes from FedEx (the legacy credentials are flagged invalid), not from Shipstore.

Fix

  1. Open the test or QA profile's carrier settings in Shipstore.
  2. Find the legacy "FedEx Test" account that uses FedEx's legacy web services (SOAP).
  3. Remove the legacy FedEx Test account, leaving the active FedEx account on the new API.
  4. Process a test FedEx shipment on the profile to confirm it succeeds.
  5. If you need a FedEx test account, register a new one through the FedEx Developer Portal for the new API instead of restoring the legacy SOAP account.
  6. Confirm the test profile points at the test environment you want and uses that profile's own API key (test profiles are left out of profile switching).

What you should see

A FedEx test shipment on the profile processes with no invalid-credentials error, and only the active new-API FedEx account remains on the test profile.

Related articles

  • Test-mode profile shipments fail (use the carrier's test credentials)
  • Re-register your FedEx accounts for the new FedEx API
  • FedEx "Unauthorized Status. 401 Response" after a key change