# Integration review complete

Bogdan’s final response resolves all three remaining clarifications. No outstanding questions remain from this functionality review. This documentation update does not change backend behavior.

## API verification permissions

An explicit API address_verification_type works independently of company-level CASS/NCOA enablement. The company setting is used only when the API request omits the field. SFTP verification is controlled entirely by the company setting; there is no file field. Verification cannot be combined with international mail.

## Auto Recharge

Auto Recharge attempts only one reload per order. The configured reload amount must cover the entire shortage. For a $500 order with $200 in the wallet, the shortage is $300. A $100 reload is insufficient: the order is refused and the card is not charged. Raise the configured reload amount or add funds before retrying the existing order.

## FedEx SFTP phone fields

Use Return Phone for the sender and Recipient Phone Number for the recipient. Return Phone Number is not recognized and is silently ignored; a FedEx file missing the required sender phone is rejected. Dashes, spaces, parentheses and dots are stripped. A leading 1 or +1 is accepted; the normalized number must contain exactly 10 U.S. digits. Plain 10-digit input is recommended.

The known XML LOOKUP empty-file issue remains documented as current behavior, not a pending clarification or a promised fix. Documentation validation is separate from live integration testing.