MasterCard Specific Requirements Clause Samples

The 'MasterCard Specific Requirements' clause sets out particular obligations and standards that must be followed when processing transactions or conducting business involving MasterCard. This clause typically details compliance measures, operational procedures, and reporting requirements unique to MasterCard, such as adhering to its security protocols or dispute resolution processes. Its core function is to ensure that all parties meet MasterCard’s regulatory and operational expectations, thereby reducing the risk of non-compliance and facilitating smooth transaction processing.
MasterCard Specific Requirements. You may request or encourage a customer to use a payment card with an acceptance brand other than MasterCard or other form of payment or a Card of a different product type (e.g., traditional cards, premium cards, rewards cards) than the Card the consumer initially presents. You may do so by methods that include, but are not limited to: a. offering the customer an immediate discount from your list, stated, or standard price, a rebate, a free or discounted product or service, or any other incentive or benefit if the customer uses a particular payment card with an acceptance brand other than MasterCard or other particular form of payment; b. offering the customer an immediate discount from your list, stated, or standard price, a rebate, a free or discounted product or service, or any other incentive or benefit if the customer, who initially presents a MasterCard, uses instead another payment card or another form of payment; c. expressing a preference for the use of a particular payment card or form of payment; d. promoting the use of a particular general purpose payment card with an acceptance brand other than MasterCard or the use of a particular form or forms of payment through posted information, through the size, prominence, or sequencing of payment choices, or through other communications to customers (provided that merchants will abide by the MasterCard trademark standards relating to the display of its marks); or e. communicating to customers the reasonably estimated or actual costs incurred by you when a customer uses particular payment cards or forms of payment or the relative costs of using different general purpose payment cards or forms of payment. You are free to engage in the POS practices that are described above, or any other substantially equivalent practices.
View SourceView Similar (22)

Related to MasterCard Specific Requirements

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., ▇▇▇▇▇▇▇ claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by ▇▇▇▇▇▇▇▇▇▇, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.