Master Services Terms and Catalog of Services Descriptions

Version: v1.0
Effective Date: December 10, 2025

Master Services Terms

These Master Service Terms (“Master Services Terms”) govern the professional services that Merge API, Inc. (“Merge”) may provide to customers (“Customer”) in connection with use by Customers of the Merge Unified API and other hosted software applications (the “Service”). The specific professional services offered by Merge (the “Services”) are set forth in various “Services Descriptions” referencing these Master Services Terms, which may be purchased by a Customer by means of inclusion of a corresponding SKU (each, a “Services SKU”) on an Order Form. These Master Services Terms do not, by themselves, obligate either party to perform Services. Services will be performed only upon execution of an Order Form referencing one or more Services SKUs.

Order Forms will define the commercial terms applicable to each engagement, including pricing, quantities, and timelines. In the event of a conflict, the following order of precedence will prevail: Order Form, followed by the applicable Services Description(s), followed by these Master Services Terms, followed by the Master Service Agreement between Merge and the Customer (“MSA”).

1. Purpose and Use

These Master Services Terms govern the standard service offerings available from Merge. Each Service Description includes a description of scope, deliverables, assumptions, and acceptance criteria applicable to each such offering. Order Forms may reference multiple Services SKUs. These Master Services Terms will be incorporated by reference into any Order Form that includes a Services SKU.

2. General Assumptions

Unless otherwise stated in a Services Description or Order Form:

• Customer will provide timely access to personnel, systems, test environments, documentation, and decision-makers necessary for performance of the Services.
• Services will be performed remotely during normal business hours unless otherwise agreed in writing.
• Customer is responsible for internal testing, deployment, and change management unless separately contracted.
• Delays in Customer responsibilities may impact timelines and fees.

3. Standard Responsibilities

Merge Responsibilities

‍Merge will:

• Perform Services in a professional and workmanlike manner;
• Provide qualified personnel to execute the Services;
• Communicate status and material issues in a commercially reasonable manner; and
• Perform configuration or advisory work within the Merge platform where applicable.

Customer Responsibilities

‍Customer will:

• Provide resources with sufficient knowledge and authority to make timely decisions;
• Supply required documentation, testing accounts, and integration templates;
• Review and approve deliverables in a commercially reasonable time frame; and
• Perform any required development or configuration in Customer systems or codebase.

4. Changes to Scope

Any material change to the scope, sequencing, or duration of the Services will require a written change request, which may be executed via email. Approved changes may result in adjustments to fees and delivery timelines.

5. Acceptance

Upon completion of a deliverable or milestone, Merge will notify Customer (“Initial Delivery”). Customer will have ten (10) business days to review and either (a) confirm acceptance, or (b) provide written notice of material deficiencies. Absent such notice, deliverables will be deemed accepted 10 business days from Initial Delivery. Merge will correct any material deficiencies promptly, and the corrected deliverables will be deemed accepted upon re-delivery.

6. Legal Terms

• Unless otherwise set forth in an Order Form or in a Services Description, all work product created by Merge in connection with the Services, will be deemed to be Merge intellectual property, and Merge will be entitled to offer such intellectual property to its other customers as part of the Service.
• Merge’s liability for the performance of each Services SKU is limited to the fees paid for such Services SKU.

7. Termination

Either party may terminate the portion of an Order Form attributable to a Services engagement in accordance with the termination provisions of the MSA.

8. Service SKU Framework

Each SKU below includes:

• Description
• Scope of Services
• Exclusions
• Deliverables
• Customer Responsibilities
• Typical Timeline
• Acceptance Criteria.

9. Available Services SKUs

PS-001

‍PS-001: Integration Field Mapping & Data Transformation (Per Integration)

Description

Merge will configure integration-wide field mappings and data transformations for one (1) third-party integration based on the Customer's list of data fields to enable Customer to consume additional normalized data via the Merge Unified API (the “Services”). Each integration purchased will appear as a separate line item in the Order Form.

Scope of Services

For each integration purchased under this SKU, Merge will:

• Review the Customer's list of data fields and data requirements
• Configure field mappings for the selected third-party integration
• Configure in-product transformation logic
• Where platform functionality is insufficient, provide transformation logic and/or code snippets for Customer execution

Exclusions

Unless otherwise agreed in writing, this SKU does not include:

• Work for additional integrations (each requires its own SKU purchase)
• Development of custom integrations not supported by Merge
• Modification of Customer systems or codebase
• Ongoing maintenance post-delivery
• Field mapping for data not exposed by the third-party system

Deliverables

For the purchased integration, Merge will deliver:

• Configured field mappings in the Merge platform
• Configured in-product transformations and/or transformation logic
• Documentation of mappings and transformation rules

Customer Responsibilities

The list of data fields must be provided before the start of the project. Any subsequent changes to the list of data fields will be considered a change in scope, requiring a written change request in accordance with Section4 and may result in adjustments to fees and delivery timelines.

Customer will:

• Provide the list of data fields and sample data
• Provide beta/test account for the specific integration purchased
• Assign technical resources for access, testing, and validation

Typical Timeline

Estimated delivery time: 3–8 weeks per integration, depending on Customer readiness and resource availability. An estimated date of delivery will be specified in the order form.

Acceptance CriteriaInitial

Delivery of the Services occurs when, for the purchased integration:

• Field mappings align with Customer’s requirements
• Transformations produce expected test results
• Documentation is provided to Customer

Acceptance will follow the procedure in Section 5 of the Master Services Terms.

PS-002

PS-002: Third-Party Integration Partnership Enablement (Per Integration)

Description

Merge will support Customer in securing approval and enablement for one (1) third-party integration partnership, including end-to-end support for partner onboarding and approval processes.

Scope of Services

For each purchased integration, Merge will:

• Create and configure self‑serve partner accounts and applications, where applicable
• Complete and submit required documentation and technical questionnaires
• Produce and submit demo materials and testing evidence required by the partner
• Coordinate conversations and communication with the partner teams
• Track requirements, feedback, and status for the approval process
• Provide periodic updates to Customer regarding progress and next steps

Merge may support up to five (5) integrations in parallel. Each integration counts as one purchased unit.

Exclusions

Unless otherwise agreed in writing, this SKU does not include:

• Custom development or engineering work
• Relationship management or commercial negotiations beyond partnership approval
• Guaranteed approval outcomes, as approval decisions rest solely with the partner
• Legal review or negotiation on behalf of Customer

Deliverables

• Completed partner account and/or registration forms for the purchased integration
• Submitted demo materials and supporting technical information
• Coordination and communication with partner teams
• Status updates and documentation of requirements and decision points

Customer Responsibilities

Customer will:

• Provide a single point of contact for internal questions and escalations
• Supply any Customer‑specific materials or approvals required by third‑party partners
• Support Customer‑owned internal reviews or compliance steps

Typical Timeline

Timelines may vary based on partner processes and Customer responsiveness. Enterprise‑level partner programs may require extended review cycles. Merge will use reasonable efforts to advance each application.

Acceptance Criteria

The Services will be delivered, and will be deemed accepted, upon:

• Submission of all required materials to the third‑party provider

If the partner rejects a partnership request despite completion of the above, the unit will still count as fulfilled, as partner approval decisions are outside Merge’s control.

PS-003

PS-003: Unified API Implementation (Per Category)

Description

Merge will implement the Merge Unified API for one (1) integration category (e.g., HRIS, ATS, CRM,Ticketing, Accounting, File Storage, etc.) within Customer’s software environment (the “Services”). This SKU includes all configuration and setup required to connect integrations listed in the applicable Order Form.

Scope of Services

For each purchased category, Merge will perform the following tasks across the integrations specified in the Order Form:

• Embed Merge Link UI: Integrate Merge’s authentication interface into the Customer’s application(standard implementation, no customizations).
• Credential Exchange & Secure Storage: Configure token exchange between frontend and backend and establish secure storage for credentials.
• Recurring Sync Setup: Implement standard synchronization processes following Merge documentation to retrieve common model data and remote data on a recurring basis.
• Passthrough Requests: Configure up to two (2) passthrough requests per integration within the category to fetch required data.
• Webhook Receivers: Set up up to ten (10) “Common Model Synced” and one (1) “Linked AccountLinked” webhook listener per category.
• Field Mappings: Configure up to ten (10) field mappings per category to align Merge’s common models with Customer’s internal data model.
• Unit Testing: Develop and execute basic unit tests for code written or modified by Merge.

Exclusions

This SKU excludes:

• Work for integrations outside the purchased category.
• Modification of Customer’s codebase beyond the described implementation scope.
• Custom UI design or front-end integration of Merge Link.
• Ongoing maintenance or support after implementation (requires separate SKU).

Deliverables

• Configured Merge Link and credential exchange for the purchased category
• Functional recurring syncs and passthrough requests for integrations listed in the Order Form
• Configured webhooks and field mappings for the category
• Unit test coverage and final QA documentation

Roles and Responsibilities

Merge:

• Assign a Forward Deployed Engineer (approx. 20 hrs/week) and Customer Success Manager (2hrs/week)
• Deliver configuration, QA, and enablement across integrations in the category
• Provide documentation, test plans, and final handoff materials

Customer:

• Assign one (1) developer (approx. 3 hrs/week) and one (1) project manager (2 hrs/week)
• Provide integration credentials, test environments, and access to systems
• Review deliverables, execute validation, and confirm acceptance

Timeline

A delivery date and milestone schedule for the implementation will be defined in the applicable Order Form.Such delivery dates are provided as good‑faith estimates only and may vary based on project complexity and the number of integrations within the category.

Acceptance Criteria

Initial Delivery of the Services occurs when:

• All work items in the Scope of Services are delivered for integrations listed in the Order Form;
• Customer verifies successful end-to-end operation for at least one integration within the category; or
• Ten (10) business days have passed since Merge’s completion notice without material objection.

Acceptance will follow the procedure in Section 5 of the Master Services Terms

Service-Specific Terms

The Deliverables set forth above will be owned by Customer and considered a “work made for hire.” Merge retains rights to its background IP, to the extent incorporated into any of the Deliverables, and grants Customer a license to use such IP solely in connection with the implementation.