When adding a FedEx carrier connection, Logiwa IO offers a second setup method called Verify with FedEx MFA. Instead of pasting a Client ID, Client Secret, and Account Number from the FedEx Developer Portal, you verify your FedEx account directly and Logiwa IO generates and stores the connection credentials for you automatically.
When to Use It
Use Verify with FedEx MFA when:
You don't have (or don't want to manage) FedEx Developer Portal API keys
You'd rather confirm ownership of the FedEx account through a PIN, invoice, or a call with FedEx Technical Support
You want Logiwa IO to generate and store the connection credentials for you, with nothing to copy or paste
Prerequisites
Before starting, have ready:
Your 9-digit FedEx account number
The billing address on file for that account (street, city, state, postal code)
Access to the phone number or email on the account's billing profile, in case a PIN is sent there
Step-by-Step Instructions
Navigate to Integrations > Shipping and click Add New Connection on the FedEx Integration page.
Select your Warehouse and set the Test Account toggle. Yes routes verification through FedEx's sandbox environment; No routes it through production. ⚠️ Verify against live system before publishing.
Under Setup method, select Verify with FedEx MFA.
Enter the Account Number, Street address, City, State, Postal code, and Locality (e.g., en_US, es_US, en_CA, fr_CA). Available verification options can differ by locality.
Choose how to verify the account:
Verify with a PIN or invoice details — Logiwa IO sends an Address Validation request to FedEx and shows you the verification options it returns.
FedEx Technical Support — you authenticate by phone with FedEx first.
If you chose Verify with a PIN or invoice details, click Verify account, then pick one of the options FedEx returns:
Verify with a PIN — choose a delivery channel (SMS, email, or call, depending on locality), click Send PIN, and enter the 6-digit code within 10 minutes. Two incorrect attempts lock this method for 24 hours; use Resend PIN if it expires.
Invoice details — enter a recent invoice number, date, and amount instead of a PIN.
If you chose FedEx Technical Support, call the number shown, authenticate with the agent, and ask them to apply the account bypass for API onboarding. Return to Logiwa IO and click I've authenticated by phone — re-run validation. If FedEx hasn't propagated the bypass yet, Logiwa IO shows an error — wait a moment and retry, or confirm with FedEx that the bypass was applied. ⚠️ Verify against live system before publishing.
Once verified, click Continue. Confirm: you should see a confirmation that the account was verified and that Logiwa IO issued the connection credentials automatically — there's nothing to copy or paste.
Complete the General, Clients, Services, Packages, and Advanced tabs the same way as the API key flow (see the FedEx Integration article), then click Finish.
Key Fields & Options
Field | Description | Notes |
Locality | Region/language sent with the Address Validation request | Determines which PIN channels are offered; e.g., Canadian localities don't offer SMS |
Test Account | Sandbox vs. production FedEx environment | Set before choosing a verification method |
Verification method | Verify with a PIN or invoice details vs. FedEx Technical Support | The first leads to PIN or invoice; the second leads to a phone-authenticated bypass |
Common Questions & Edge Cases
Why don't I see an SMS option for my PIN? PIN delivery channels depend on locality — Canadian localities (en_CA, fr_CA) offer email or call only, not SMS.
What happens if I enter the wrong PIN twice? The PIN method locks for 24 hours. Use the FedEx Technical Support option instead, or wait and retry.
Do I still need to enter API keys anywhere? No. Once verification succeeds, Logiwa IO stores the credentials FedEx issues on the backend; the Clients tab of the setup drawer confirms this and requires no further action.
Can I switch back to entering API keys after choosing MFA? Yes — reopen Add New Connection and select Enter API keys instead.