Integration and Testing

Authorize.Net API questions and help with your payment integration.

Reply
Member
Posts: 6
Registered: ‎10-27-2014
Accepted Solution

Expiration Date newly required for CREDIT transactions?

I have been using the name/value-pairs API for several years now. I am looking to switch to the XML API so I can use the new blended accounts (it was not clear to me that I could use NVP on the blended accounts -- please correct me if I am wrong).

The XML API documentation states that a credit card expiration date is required to perform a CREDIT (refund) transaction. This is not the case for the NVP API, and would require me to either redesign my web app entirely to obtain the expiration date for a refund, or would require me to save the expiration date (which introduces huge PCI compliance issues).

Am I reading the documentation correctly, and is the documentation correct? This seems like a fundamental change that is not necessary since it has worked for years without the expiration.

Thanks for any help you can give.

Dan


Accepted Solutions
Solution
Accepted by topic author seakayaker4life
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Expiration Date newly required for CREDIT transactions?

AIM XML pdf doc? It said it is optional.

View solution in original post


All Replies
Solution
Accepted by topic author seakayaker4life
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Expiration Date newly required for CREDIT transactions?

AIM XML pdf doc? It said it is optional.

Member
Posts: 6
Registered: ‎10-27-2014

Re: Expiration Date newly required for CREDIT transactions?

I was reading HTML doc. There are errors within the Authorization/Capture section as well so it just looks like they didn't bother to proofread.

 

Thanks!

Posts: 2,765
Topics: 57
Kudos: 270
Blog Posts: 67
Registered: ‎12-05-2011

Re: Expiration Date newly required for CREDIT transactions?

I forwarded this to our documentation team.  Thanks for the report.

 

Richard