Card-on-File Mandates and the NVP API

Ronin — Mon, 19 Jul 2021 20:26:39 GMT

Hello,

We have several clients using Authorize.Net that have received emails about the Credential-on-File (COF) and Merchant Initiated Transaction (MIT) mandates. They refer to this URL:

https://support.authorize.net/s/article/Authorize-Net-Mandate-Compliance-Overview

Our challenge here is that we are using the older Name-Value Pair (NVP) API that uses this endpoint:
https://secure2.authorize.net/gateway/transact.dll

None of the information referenced in the email applies to this version of the API. We do not use either the Customer Information Manger (CIM) or the Automated Recurring Billing (ARB).

How can we best honor these new mandates using the NVP API? If we cannot, will there be some effect on our client's transactions? For that matter, is there any documentation for the NVP API that is still available online, including all available parameters?

Thank you

topic Card-on-File Mandates and the NVP API in Integration and Testing

Card-on-File Mandates and the NVP API