I don't have any specific coding questions about this at the moment. Mainly I am interested in wether or not this is PCI compliant. From what I gathered by reading other topics about displaying the expiration date, the right way to do it is to store the expiration date separately from the CC number.
In cases where a user may have multiple payment profiles would I be allowed to store each expiration date with each payment profile ID in my own table?
In addition, would I also be allowed to store the card type and name on the card in cases where the BillTo name is different than the name on the card?
I see that the name on card and card type aren't stored so I would only be able to display them from my own database. Would this be an okay way to store things?
Go to Solution. All you should need is card number and expiration date, neither of which should be stored locally. You can retrieve a masked version of the credit card number from Authorize. You can just mark the profile as expired in your own db when it fails to go through the first time, and send them a notification that their card has expired and they need to update it. View solution in original post.
