In some cases, properties may be able to post Visa or Mastercard payments successfully, but receive a “billing ZIP code cannot be blank” error when attempting to post American Express transactions. This issue typically appears when Address Verification Service (AVS) and Card Verification Value (CVV) checks are enabled at the processor level.
For American Express transactions processed through Fortis, the processor may require a billing ZIP code if AVS enforcement is turned on. Visual Matrix does not currently transmit billing ZIP codes for Fortis transactions, which can cause Amex payments to fail even when entered manually or attempted through the PIN pad.
This often explains situations where:
- Manual card entry returns a ZIP-code-required error
- PIN pad transactions are declined even when a ZIP code is entered
- The card does not tokenize after the attempt
- Visa and Mastercard payments continue to work as expected
Why this happens
- AVS and CVV settings are enabled on the Fortis merchant account.
- Fortis requires a billing ZIP code for American Express when AVS is active.
- Visual Matrix cannot override or bypass this requirement.
- As a result, the transaction is declined before it can tokenize or post successfully.
How to resolve the issue
Contact Fortis and request that AVS and CVV be disabled for the affected merchant account(s).
Once AVS and CVV are disabled, American Express transactions should process normally in Visual Matrix.
This change must be made on the Fortis side; Visual Matrix cannot adjust or override these validation requirements.
If multiple properties share the same ownership or merchant setup (for example, Lone Star Lodge I and Lone Star Lodge II), AVS and CVV settings should be reviewed and disabled consistently across all related accounts.
Leaving AVS and CVV enabled for American Express with Fortis may continue to block transactions, prevent tokenization, and cause payment failures even when the card is valid.