YUNO SERVICE LEVELAGREEMENTS (SLA)

1. OVERVIEW

This service level agreement defines and describes the daily operating procedures between Yuno and the Company in support of service stability.

‍

The procedures described are based on processes that help ensure the efficient provision of service to the Company. This will ensure that the service operates to an agreed standard, is PCI DSS compliant, and that system and data integrity is maintained.

‍

2. INCIDENT MANAGEMENT

2.1 YUNO SERVICE DESK: ROLES AND RESPONSIBILITIES

‍

● Provide a single point of entry to the Company for incidents, support requests and change requests, relating to the payment orchestration service and the functional and technical aspect of the services provided to the Company.

● Categorization and prioritization of incidents, support requests, investigation and diagnosis of incidents/technical problems for resolution and coordination with the Company team to close incidents and support requests.

● Provide response time in accordance with agreed service levels.

● Keep the Company updated on regular progress throughout the life of an incident.

● Notify the Company of any planned or emergency outages affecting Yuno production services.

● As necessary, establish escalation policies for identified critical or serious incidents.

● Customer service and support to the Company in the provision of Yuno's production systems and networks.

● Yuno uses Jira as a logging and tracking tool for recorded incidents.

‍

‍

2.2 INCIDENT MANAGEMENT CHANNELS

‍

For any incident that needs to be reported to Yuno, an incident log will be generated at the Yuno service desk through the following channels that will be made available:

‍

EMAIL: support@y.uno

‍

Yuno will continue to provide periodic incident status updates to the Company via email or telephone. Depending on the nature of an incident, it may be necessary to develop and implement a software solution in the application to correct the underlying cause.

For each incident, a report must be submitted that determines the root cause and tracks the implementation of a permanent solution.

‍

Yuno is responsible for proactively monitoring your applications, operating systems and databases. Any critical and high-intensity incidents, e.g. malicious, suspicious or disruptive events affecting Company services, will be notified to Company staff and will be tracked by Yuno Service Desk until closure.

‍

For critical incidents, the Yuno Service Desk team will be available to respond according to the times set out in section 2.4.2.

‍

‍

2.3 INCIDENT MANAGEMENT

‍

For any critical priority incident, Yuno's service desk team will generate an incident record and assign it to your support team, who will respond within a reasonable timeframe based on the criticality of the incident and make a selection of necessary actions to minimize risk whenever possible. . The incident priority can be modified if a change in urgency/impact is identified. (See table 2.4.1)

‍

It will be the Yuno team's responsibility to keep the Company informed of incident updates periodically until the incident is resolved and closed.

‍

2.3.1 YUNO TICKET FORM

When submitting a form at the following link, a ticket will be generated with the SLAs defined in this document.

‍

2.3.2 COMPANY CONTACT FOR INCIDENT MANAGEMENT

This section refers to the structure of the Company's Help Desk, which will have interaction with Yuno for any incident. The Company's technical and functional support contact is detailed below:

‍

2.4 CLASSIFICATION OF INCIDENTS AND SERVICE LEVELS

2.4.1 INCIDENT CLASSIFICATION

Yuno will be responsible for logging, diagnosis and support based on incident classification as defined below:

‍

‍

2.4.2 CLASSIFICATION OF SERVICE LEVELS

Yuno will respond to incidents reported by the Company according to their seriousness at the following times:

‍

3.MAIN MEASURES

‍

AVAILABILITY SERVICE LEVELS

‍

The Service Level metric will be calculated as the scheduled service time in a measurement window minus the total duration of unscheduled outages in the same measurement window divided by the scheduled service time in the measurement window, as follows:

‍

Exclusions. Yuno does not include in the calculation of downtime when Services are not provided due to:

● Scheduled maintenance windows in which the expected unavailability has been communicated at least two business days before the interruption, except in the case of emergency changes;

● Force majeure events;

● Company actions or omissions;

● Events arising from the Company's systems or any Company website;

● ISP or Internet outages outside of Yuno's control; any

● Interruptions Yuno considers reasonably necessary

● Incidents involving the Yuno platform with third-party dependencies (e.g. PSPs, Acquirers, Anti-Fraud, etc.)

‍

4. RESPONSIBILITIES FOR NON-COMPLIANCE WITH SERVICE LEVELS

‍

PENALTY ACCORDING TO THE IMPACT OF FAILING TO COMPLY WITH SERVICE LEVELS

‍

Yuno will use commercially reasonable efforts to make the Services available 99.9% or more of the time during any calendar month. Subject to the exclusions set out in the previous paragraph, interruption will be understood as any time when the Services are not available for a cause that is within Yuno's control. The availability rule does not apply to any feature of the Services that Yuno identifies as a "beta" feature or service.

‍

If Yuno is unable to achieve the above percentage of availability, Company will be entitled to receive a credit (“Service Credit”) calculated as a percentage of the Subscription Fees. The increase in Service Credits is based on the number of outages added, as set forth below.

‍

Service credits are non-transferable and will be issued in the currency used in the Purchase Order. To receive a Service Credit, Company must contact Yuno in writing within thirty (30) days of discontinuation and demonstrate, to Yuno's reasonable satisfaction, that Company's use of the Services has been negatively affected as a result of the interruption. Validated Service Credits will be applied to the next invoice pending payment to Yuno by the Company.

‍

Only resources. Notwithstanding any inconsistent terms herein, Service Credits are Company's sole and exclusive remedy for any interruption of Services.

‍

‍

5. MAINTENANCE AND PLANNED OUTAGES

‍

In the event of planned outage or planned maintenance, Yuno will notify the Company via email seven calendar days prior to the event, in order to minimize service disruption, these maintenance must be agreed between both parties to mitigate impacts. These activities should be infrequent and planned during periods of low traffic. In the event of emergency maintenance, the Company will be contacted as soon as possible with the resolution and expected deadline. The notification will include:

‍

1. The change record number for reference

2. Brief description of the change.

3. Date and time of planned implementation of the change

4. The impact of the expected service on the customer.

5. The Company will provide Yuno with contacts via email to be notified about possible maintenance and interruptions.

‍

The Company will provide Yuno by email with contacts to be notified of any

maintenance and outages.