topic Expiration Date newly required for CREDIT transactions? in Integration and Testing

Expiration Date newly required for CREDIT transactions?

seakayaker4life — Mon, 27 Oct 2014 17:50:11 GMT

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

Re: Expiration Date newly required for CREDIT transactions?

RaynorC1emen7 — Mon, 27 Oct 2014 19:45:25 GMT

AIM XML pdf doc? It said it is optional.

Re: Expiration Date newly required for CREDIT transactions?

seakayaker4life — Mon, 27 Oct 2014 22:30:32 GMT

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!

Re: Expiration Date newly required for CREDIT transactions?

RichardH — Tue, 28 Oct 2014 00:02:04 GMT

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

Richard