MasterCard Requirements

MasterCard Specific Certification Requirements include:

• Payment Facilitator
• Zero-dollar Approval with Subsequent Declines
• Card Verification Value (CVV2/CVC2/CID)
• Approvals

Payment Facilitator

Customers who are identified as a Payment Facilitator need to migrate to the Elavon E4 host in order to pass the following dynamic fields:.

• Merchant passes API fields 7015 – 7051 to a payment facilitator, who in turn is responsible for passing these fields to Elavon.
• Sale transaction in which the final dollar amount is known at the time of authorization (amount will not change) the following values are used:
  • F is Final Amount
  • P is passed on an authorization (type 01) if the final dollar amount may change between the authorization and Prior Authorization transactions

The following table identifies API fields 7015 – 7051.

API Field	Field Name	Size	Type	Merchant is able to dynamically change:
7015	Dynamic DBA	1-25	A/N	“Doing Business As” name on each transaction submitted to the host for authorization.
7016	Dynamic Street Address	1-30	A/N	Street Address on each transaction submitted to the host for authorization.
7017	Dynamic City	2	A/N	Street Address on each transaction submitted to the host for authorization.
7018	Dynamic State	2	A/N	State on each transaction submitted to the host for authorization.
7019	Dynamic Postal Code	1-9	A/N	Postal Code on each transaction submitted to the host for authorization.
7020	Dynamic Postal Code	1-9	A/N	Country Code on each transaction submitted to the host for authorization.
7021	Dynamic Phone Number	1-20	N	Merchant Phone Number on each transaction submitted to the host for authorization.
7022	Dynamic Sub-Merchant ID	1-15	N	Allows the merchant to dynamically change the Sub-Merchant ID on each transaction submitted to the host for authorization.
7023	Dynamic Email Address	1-70	A/N	email address on each transaction submitted to the host for authorization.
7024	Dynamic MCC	4	N	MCC on each transaction submitted to the host for authorization.
7025	Dynamic Tax ID	1-14	A/N	Tax ID on each transaction submitted to the host for authorization.
7051	Dynamic Auth Type Indicator	1	A/N	Required for Payment Facilitator Merchants. Type of Authorization Transaction Valid Values: F = Final Amount - amount is not expected to change for settlement P = Pre-Authorization / Estimated Amount - amount may change between auth and settlement The amount referenced is the total transaction amount provided in API field 2

Zero-dollar Approval with Subsequent Declines

To get a zero-dollar approval with subsequent declines, use the Zero Card (see Demo Card Scenarios).

• Transaction is approved if the transaction amount (API 0002) is $0.00.
• If transaction amount requested is greater than $0.00, the standard decline logic is applied.

Address Verification Service Approvals and Declines

For Address Verification Service (AVS), use the following values:

• AVS ZIP Code (API 0700)

Example: 33606

• AVS Billing Street Address (API 0701)

  Example: 100 MAIN ST

  Any matching values would be a match, and any other values would be a non-match.

The results will be placed in AVS Result Code (API 1020).

• Y – Both ZIP Code and Billing Street Address Match
• Z – ZIP Code Matches and Billing Street Address Does Not Match
• A – ZIP Code Does Not Match and Billing Street Address Match
• N – Neither ZIP Code or Billing Street Address Match

Card Verification Value (CVV2/CVC2/CID)

For Verification Value (CVV2/CVC2/CID), use the following values:

• CVV2/CVC2/CID Information (API 0050)

Example: 382

A matching value would be a match, and any other value would be a non-match. The results will be placed in CVV2/CVC2/CID Response (API 0040).

• M – Match
• N – No Match

Approvals

To get a credit card approval, use any other card number that is not a Decline Card, Zero Card or Partial Authorization Card.

• previous PDF Downloads
• next Point to Point Encryption