...
Level I | Basic transaction data like card number and transaction amount that is required for standard consumer transactions and provides provide standard interchange rates. |
Level II | More detailed transaction data, like a sales tax that , is required for B2B transactions and provides lower interchange rates. |
Level III | Comprehensive transaction information like line item details and shipping, that is required for high-value (large ticket) B2B transaction transactions and provides the lowest interchange rates. |
...
| Info |
|---|
Note: Each additional level of data submission, Level I to Level II to Level III data, requires all data from the previous level in addition to the new data required. Example: In order to To submit Level III data, all Level I and Level II data requirements must already be met to qualify for Level III interchange rates. |
...
All transactions, regardless of card brand, must meet these data requirements in order to qualify for basic interchange or Level I:
...
Each card brand will feature its own list of requirements necessary to receive interchange rates by using Level II or Level III data to qualify on its card network. Each major card brand - Visa, MasterCard, American Express, and Discover - has been listed below with individual details to clearly explain their requirements.
...
Merchants must process 1 to 6 million Visa transactions per year.
Merchants must process between $20,000 and $1,000,000 in annual e-commerce transactions per year.
Merchants must submit the following forms to the Visa Verification team:
Annual Attestation of Compliance (AOC)
Annual Self-Assessment Questionnaire (SAQ)
Quarterly Network Scan by an Approved Scan Vendor (ASV2)
...
| Expand | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Level II data must include all Level I data requirements in addition to the requirements listed below. Sales Tax and Order Information - Sales tax information for each transaction including:
Merchant Information - Details about the Merchant selling the product or service items including:
|
...
Merchants must process a combined total of 1 to 6 million MasterCard & Maestro transactions per year.
Merchants must process between $20,000 and $1,000,000 in annual e-commerce transactions per year.
Merchants must submit the following forms to the MasterCard:
Annual Attestation of Compliance (AOC)
Annual Self-Assessment Questionnaire (SAQ)
Quarterly Network Scan by an Approved Scan Vendor (ASV2)
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Level II data must include all Level I data requirements in addition to the requirements listed below. Sales Tax Information - Sales tax information for each transaction including:
Merchant Information - Details about the Merchant selling the product or service items including:
|
...
| Expand | ||
|---|---|---|
| ||
In addition to the interchange data requirements above, the MasterCard card network has specific additional requirements to qualify:
|
| Expand | ||
|---|---|---|
| ||
Large Ticket transactions refer to transactions with a larger total dollar amount. Based Your interchange rate may change based on the transaction amount , your interchange rate may change to offer better pricing from MasterCard’s large ticket program for high-dollar-value transactions. In addition to the data requirements above, the MasterCard network has specific additional requirements to qualify for Large Ticket interchange pricing:
|
...
| Warning |
|---|
Unavailable: American Express does not offer discounts or changes in interchanges interchange rates for Level III data submissions |
...
| Warning |
|---|
Unavailable: American Express does not offer any discounts or changes in interchanges interchange rates for Level II or Level III data submissions. |
...
To take advantage of lower interchange rates, this Level II and Level III data must be submitted alongside your transaction. This ensures the customer’s card brand network is able to can receive and assess the data to determine which interchange rate the transaction will receive.
| Info |
|---|
Before you begin, we recommend checking each card’s eligibility for Level II and Level III processing as American Express and Discover don’t offer direct data submission options for Level II or III to qualify for lower interchange rates. A simple query shown below will quickly identify the card type:
The response will display the method (card brand), type (debit, credit, or both), and card category (personal, corporate card, etc.), which will allow you to know before submitting the additional data , if the card brand network supports lower interchange rates or Level II or Level III data submissions. |
...
| Expand | ||
|---|---|---|
| ||
To submit Level II transaction data using the Create Payments page:
Click Process Payment to complete the submission. |
| Expand | ||
|---|---|---|
| ||
Non-Profit and Governmental entities that qualify for a tax-exempt status can apply this setting to their platform entity. This provides the proper mapping for Level II data submission when tax amounts are set to 0%.
To apply tax-exempt status to non-profit entity groups from the Groups page:
Click Save to complete the Merchant enrollment in the Tax Exempt Group. |
...
| Expand | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
To submit Level II transaction data using the
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||
Non-Profit and Governmental entities that qualify for a tax-exempt status can apply this setting to their platform entity. This provides the proper mapping for Level II data submission when tax amounts are set to 0%.
To apply tax-exempt status to non-profit entity groups using the
Your successful response should look like the following:
Note: All other non-applicable response parameters above are set with their default values. Visit our API Documentation to read more about the other available response fields' descriptions. See the descriptions below for the applicable response parameters.
|
| Expand | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
To submit Level III transaction data using the
Note: Descriptions for Level II data shown here are available in the Submit Level II data using the Payrix API section above.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
...
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Step 1: Under your
Code Block | | |||||||
|
Step 2: Under a new <script> tag, add the API Key, Merchant ID, and Transaction Amount:
| Code Block | ||
|---|---|---|
| ||
<script>
PayFields.config.apiKey = "ab123c4def5g6hijkl7890m12345no6p";
PayFields.config.merchant = "t1_mer_123ab4c567defg8h90123i45";
PayFields.config.amount = {Transaction Amount};
<!---- continued by Step 3 ----> |
Step 3: Under the same <script> tag as Step 2, add the Order Field, Tax Field, and Billing Address:
| Code Block | ||
|---|---|---|
| ||
<!---- preceeded by Step 2 ---->
PayFields.config.order = {order number};
PayFields.config.tax = {tax number};
PayFields.config.billingAddress = {
address: '123 Madison Street',
city: 'New York',
state: 'NY',
zip: '12345',
email: '',
phone: '5555555555',
address2: 'Suite 555',
company: 'Essential Co',
country: 'USA'
};
PayFields.config.invoiceResult = {Invoice Object}
</script> |
Result: Example HTML File
| Code Block | ||
|---|---|---|
| ||
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<script type="text/javascript" src="https://test-api.payrix.com/payFieldsScript"></script>
<title>PayFields Test</title>
</head>
<body>
<input type="button" id="submit" value="Pay"></input>
<!-- Button needed for PayFrame -->
<script>
PayFields.button = {element: "#submit", value: "Pay"};
</script>
<script>
PayFields.fields = [
{type: "number", element: "#number"},
{type: "cvv", element: "#cvv"},
{type: "name", element: "#name"},
{type: "address", element: "#address"},
{type: "expiration", element: "#expiration"},
{type: "tax", element: "#tax"},
{type: "order", element: "#order"},
];
</script>
<script>
PayFields.config.apiKey = "ab123c4def5g6hijkl7890m12345no6p";
PayFields.config.merchant = "t1_mer_123ab4c567defg8h90123i45";
PayFields.config.amount = 500;
PayFields.config.order = {orderNumber};
PayFields.config.tax = {taxNumber};
PayFields.config.billingAddress = {
address: '123 Madison Street',
city: 'New York',
state: 'NY',
zip: '12345',
email: '',
phone: '5555555555',
address2: 'Suite 555',
company: 'Essential Co',
country: 'USA'
};
PayFields.config.invoiceResult = {invoiceObject}
</script>
</body>
</html> |
| Expand | |||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
Step 1: Complete Steps 1-3 above. Step 2: Under your
Step 3: Under your
Result: Example HTML File
|