Credential-on-File (COF) and Merchant Initiated Transaction (MIT) mandates

Created on 19 April 2021, over 3 years ago

Updated 23 April 2024, 8 months ago

Received this email from client:

Dear Authorize.net Merchant,

Visa, Mastercard, and Discover have released mandates that outline requirements for merchants who store customer payment credentials for possible future use: the Credential-on-File (COF) and Merchant Initiated Transaction (MIT) mandates, which cover transactions that are processed using stored credentials. All businesses must comply with these mandates to avoid possible fees from your merchant account provider and/or possible transaction declines.

Authorize.net supports Visa, Mastercard, and Discover Credential-on-File (COF) and Merchant Initiated Transaction (MIT) mandates on your processor, First Data Nashville. Please see below for any actions you may need to take:

- Authorize.net’s Automated Recurring Billing (ARB) service supports the COF and MIT mandate requirements. While you use ARB, your ARB transactions are supported without any changes.
- If you are using our Customer Information Manager (CIM) service, there are new API fields you may need to use, depending on your specific business. Please refer your web developer or solution provider to the API Reference Guide and the API Developer Guide for more information.
- If you store payment information using a service outside Authorize.net, please refer your web developer or solution provider to the API Reference Guide and the API Developer Guide for more information.

If you have any questions regarding this email, please contact support or ask your web developer for assistance.

Sincerely,
Authorize.net

Anyone knows if this requires any changes to the module?

Thank you!

💬 Support request

Status

Closed: outdated

Version

1.0

Component

Miscellaneous

Created by

🇧🇦Bosnia and Herzegovina nno

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 8 months ago →
🇺🇸United States rhovland Oregon
The accept.js integration uses the Customer Information Manager (CIM) to store card details for reuse.

The API documentation for that is here https://developer.authorize.net/api/reference/index.html#customer-profil...

It appears there are no special fields beyond what is already being sent by the module.

This email appears to be notifying customers that they need to be using either ARB or CIM for stored payment details to be compliant.

I cannot find any information about these supposed "new API fields" mentioned.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024