Please make sure that the import file process and mapping was followed correctly. The following apply only after the import process has been accurately completed.
Additionally this applies to only Payment Gateways that support Network Tokenization such as Stripe and EziDebit.
This is because of two reasons:
- The import created an auth txn OR was not charged using import files:
Therefore it would not store the credit card expiry. In this case if you still want to store the expiry you can do so on custom fields. Please refer to the following article:
https://help.payments2us.com/en_US/Import-Files-FAQ/how-to-import-expiry-date-to-recurring-record-if-the-import-file-feature-is-not-used-to-charge-card-or-for-an-auth-transaction
- Network Tokenization:
Some payment gateways support network tokenization (such as Stripe and EziDebit), which lets you to keep charging a card even when the card has expired and this happens because the expiry date is automatically updated by the payment gateway on their systems against that token. They fetch this information directly from the card provider. If you are using these gateways, the expiry date field will remain blank. For further info, please refer to https://help.payments2us.com/all-payment-gateway/network-tokenization-and-charging-expired-cards