Masked Expiration Date in Hosted CIM's getCustomerProfileRequest

[ZeroGravPro]

I'm using Hosted CIM which means I never have access to credit card numbers or expiration dates. When I call getCustomerProfileRequest I get back a lot of useful data, but expiration date comes back masked (XXXX). Why is this? I only get back the last 4 digits of the CC number, so it's seems expdate would be safe. Anyway, is there any way to get back the expiration date without it being masked?

Note: I have read through this similar post, but I don't believe it specifically answers my question: http://community.developer.authorize.net/t5/Integration-and-Testing/Masking-Expiration-Date/m-p/1119...

In that post it seems to be referring to standard CIM (not hosted) in which the integration has access to the PAN and expdate as it passes through the network. But with hosted CIM that is not the case, so I'm at the mercy of what authnet will send back to me via getCustomerProfileRequest().

Thanks.

Zero Gravity Programming

[RaynorC1emen7]

Currently only the mask expiration date is return fom CIM.

[dgw2jr]

This is getting very frustrating. No CardType or Expiration values come back with the PaymentProfiles, but the properties exist in the SDK? Why?

[RichardH]

Hello @dgw2jr

These enhancements are on our backlog, but I don't have any details on when they might be available.  I do recommend you create a request in our new Ideas forum. This will allow others to vote on and make suggestions to improve the requests.

Richard

[CoryAuth]

For what it is worth; I created a case in the idea exchange.  Please vote for it in hopes they make this simple change in the very near future.

http://community.developer.authorize.net/t5/Ideas/UnMasked-Expiration-Date-in-Hosted-CIM-s/idi-p/494...