Table of Contents

FedEx – Authentication & Customer Verification

Overview

FedEx requires secure authentication and customer verification before shipping services can be used. This includes API authorization, customer registration, and multi-factor authentication (MFA).

Short Guideline

  • Customer Registration
  • Display FedEx EULA
    • The FedEx End User License Agreement must be shown to end customers
    • Customer consent must be recorded
  • Factor 1 – Address Validation
    • Validates customer address against FedEx records
  • Factor 2 – Identity Verification Supported methods:
    • PIN via Email
    • PIN via SMS
    • PIN via Automated Call
    • Invoice Validation (alternative)
  • Factor 2 Bypass
    • Available only for approved and trusted customers, controlled by FedEx configuration.

API Authorization

All FedEx APIs require authenticated access using OAuth-based authorization.

Authorization API

  • Generates access tokens
  • Controls API access
  • Mandatory for all FedEx API calls
Note

Access tokens must be securely stored and refreshed as required!

Customer Registration

Before shipping services can be enabled, you must complete the FedEx registration process.

FedEx EULA Requirement

  • The FedEx End User License Agreement (EULA) must be displayed
  • Customers must explicitly accept the EULA
  • Acceptance must be recorded by the application
Note

This step is mandatory for compliance!

Multi-Factor Authentication (MFA)

FedEx uses a two-factor authentication model for customer validation.

Factor 1 – Address Validation

  • Validates sender address against FedEx records
  • Ensures legitimacy of the customer account
  • Required before proceeding to Factor 2

Factor 2 – PIN-Based Verification

FedEx uses a one-time PIN to validate customer identity. PIN delivery methods:

  • Email
  • SMS
  • Automated voice call

PIN Validation

  • Customer enters the received PIN
  • PIN is validated via FedEx API
  • Successful validation enables shipping access

Invoice Validation (Alternative Factor 2)

  • Verifies customer using invoice-related information
  • Used when PIN delivery is unavailable or additional validation is required

Factor 2 Bypass

  • Allows skipping second-factor validation
  • Available only for approved and trusted customers
  • Controlled by FedEx configuration

Best Practices

  • Always display the latest FedEx EULA
  • Support multiple PIN delivery channels
  • Implement retry and error handling for failed validation
  • Securely store authentication credentials
Back to top ↑