UnMasked Expiration Date in Hosted CIM's getCustomerProfileRequest

Status: Delivered
by on ‎01-23-2015 10:08 AM

As mentioned in the following post:

 

http://community.developer.authorize.net/t5/Integration-and-Testing/Masked-Expiration-Date-in-Hosted...

 

The card expiry date is masked when returned in the getCustomerProfileRequest.  As the card number is masked, there is no PCI requirement that the expiry date of the card also be masked.  Without the expiry date, it makes it impossible for us to automate the process of notifying our customer's clients that their card will be soon expiring.  The reason for us going this route is to offer an ARB solution managed completely from within our application.  It is imparative for us to have access to this date.

 

The idea is a simple one.  Return the expiry date in the CIM getCustomerProfileRequest unmasked.

 

Thanks.

Status: Delivered
Comments
by
on ‎09-21-2016 04:22 PM

Thank you for paying attention to the community feedback and enhancing the product.

 

Is the change live yet in production ? I am getting this:

 

[E00003] The element 'getCustomerProfileRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'unmaskExpirationDate' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'clientId, refId, customerProfileId' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'.

 

by
on ‎02-16-2020 09:05 PM

In coding, if letters are used to signify months, “A” will indicate January all the way to December ending with “L”. Next to these letters will typically be numbers indicating the day and the year. However, sometimes the numbered year will come before the letter. GHD SPROTS

by
on ‎07-15-2020 02:41 AM

Yes May be They'll have the idea.