PRODUCT-SPECIFIC SCHEDULE

PAYONOMY LIMITED [UNARIC PAYMENTS AND UNARIC PAYMENTS 
FOR CERTINIA]

Last Updated: August 1st, 2025
Effective From: August 1st, 2025

This Product-Specific Schedule ("Schedule") forms part of the Agreement between Company and Customer and is incorporated into the Order Form referencing this Schedule. Capitalized terms used but not defined herein shall have the meaning given in the Agreement.

Important Notice Regarding Changes

PLEASE  NOTE  THAT  COMPANY  RESERVES  THE  RIGHT  TO  AND  MAY  UPDATE  OR AMEND THIS SCHEDULE FROM TIME TO TIME IN ACCORDANCE WITH SECTION 6.1 [AMENDMENTS  TO  AND  UPDATES  OF  THE  TERMS  OF  THIS  SCHEDULE]  OF  THIS SCHEDULE. CUSTOMERS ARE ENCOURAGED TO REVIEW THIS SCHEDULE AND THE AGREEMENT REGULARLY TO STAY INFORMED OF ANY CHANGES. THE DATE OF THE LAST UPDATE TO THIS SCHEDULE IS INDICATED ABOVE. CONTINUED ACCESS TO OR USE OF THE SERVICES AFTER ANY SUCH UPDATE CONSTITUTES ACCEPTANCE OF THE AMENDED TERMS.

AGREED TERMS

  1. Definitions

    Authorisation:  
    means  a  request  initiated  via  the  Services  to  capture  a  payment  method
    (whether inbound or outbound),  
    Conversion Data:
    means any pre-existing mandate IDs or repeat card tokens loaded onto
    Company’s system as Authorisations
    Development  Licence:  
    means  a  paid  for  option  including  maintained  “Trial  Licence”
    connected to Customers chosen Salesforce Org as further specified hereinbelow.  
    Payment:
    means an inbound or outbound transfer of funds initiated via the Services, including
    one-time or recurring charges, processed using supported payment methods (including but not
    limited to credit/debit cards, ACH, Bank Debits, Validation, Wallet for Payment or digital
    wallets).
    Processor / Payment Service Provider:
    means software / provider used to transfer payment
    information from the merchant to acquiring bank. Company supports a number of well-known
    Processors including: Braintree, Worldpay, Elavon, Authorize.net, GoCardless, and Stripe.
    Refund:
    means a return of funds initiated via the Services by the Customer in relation to a
    previously completed Payment.
    Service Uptime:
    means the proper functioning of all applicable Services, but does not include
    the proper functioning of telephone circuits, Internet services or VoIP transport services outside
    of Company’s control, nor servers or services provided by or managed by the Customer or the
    Customer's customers or the Processors.
    SOW:
    means a schedule of work which lists the agreed upon configurations for the applicable
    Service.
    Transaction:
    means any activity processed via the applicable Service, including but not limited to Payments, Authorisations, Refunds, or the use of Conversion Data.
  2. Product-Specific Fees:

    2.1 Transaction Fees: Customer shall pay to Company a fee for each Transaction processed via the applicable Service. Transaction Fees apply to all chargeable activity types, including but not limited to:
    (a)  Payments  (including  but  not  limited  to  credit/debit  cards,  ACH,  Bank  Debits, Validation, Wallet for Payment or digital wallets); (b)  Refunds; and
    (c)  Authorisations.

    Fees for Conversion Data are set out separately in section 2.2

    The  applicable  Transaction  Fees  shall  be  as  specified  in  the  relevant  Order  Form.  For clarification, unless otherwise stated in an Order Form or agreed SOW, Company shall invoice a separate Transaction Fee for each individual Transaction.

    2.2 Fees for Conversion Data.  Customer shall pay to Company a fee further specified in an applicable  Order  Form  for  each  Conversion  Data  loaded  onto  Company’s  system  unless specifically included as part of an agreed SOW. For clarification, Company shall invoice a Transaction Fee for each individual item of Conversion Data loaded onto Company’s system, unless specified otherwise in an applicable Order Form or as part of an agreed SOW.

    2.3 Fees for Development Licence. Customer shall pay to Company a fee further specified in an applicable Order Form for a Development Licence. Transactions are included in this fee. Fair usage limits apply. Fees for Development Licence shall be invoiced and are due and payable in accordance with the Agreement.

  3. Development Licence: The Customer acknowledges and agrees that the Development Licence may  only  be  used  for  test  transactions  and  must  not  be  used  for  any  live  payments  or transactions involving real funds or monetary value. Only test card or bank details may be processed under this licence

  4. Service Level Agreement (“SLA”)

    4.1 Company shall provide at least a 99.9% service uptime availability level for the applicable Services. In calculating the service availability level, the following interruptions or downtime shall be disregarded:
    (a)  interruptions or downtime caused by failures or defects in the Customer's equipment or internet connection;
    (b)  interruptions or downtime caused by failures or defects in the Processor's equipment or internet connection;
    (c)  Scheduled Maintenance;
    (d)  Maintenance which is requested or caused by the Customer; and any Force Majeure Event.

    4.2 Service  Uptime  availability  levels  shall  be  based  on  the  monthly  average  percentage availability, calculated at the end of each month as the total actual uptime minutes during the month divided by the total possible uptime minutes in the month.

    4.3 Service Downtime includes the time from occurrence of the failure to any part of the applicable Service (subject to clause 4.1. (a) and 4.1. (b) to the time of resolution of the failure to the applicable Service. Service Downtime means that the Company’s system is not available, and no useful work can be performed.

    4.4 Downtime  does  not  include  quality  of  service  issues  that  cause  minor  or  partial loss  of functionality, intermittent problems or minor degradation of operations which do not prevent the applicable Service from being used in the manner intended. In such case Customer may initiate the Support as further described in the Agreement.

    4.5 Company will use its reasonable endeavours to procure that scheduled maintenance will only occur  outside  of  business  hours,  and  for  not  more  than  21.92  minutes  per  month.  If commercially  reasonable,  Company  shall  provide  at  least  one  (1)  weeks’  notice  for  any scheduled maintenance and its intended time window.

    4.6 If Company fails to meet any of the terms of this SLA in any given month, and provided that the Customer submits a written request within one (1) month following the month in which the incident occurred, Company shall credit Customer with one twelfth (1/12) of the value of the applicable Fee as defined in the Agreement.

  5. PCI-DSS Compliance

    5.1 Company is responsible for ensuring the applicable Service, systems and applications meet all
    requirements for PCI-DSS Level 1 compliance and for any costs associated with maintaining
    such compliance.  

    5.2 Company, in regard to the applicable Service shall maintain a Compliance Statement and may
    provide attestation, scan and penetration results to Customer upon written request.

    5.3 Customer  shall  complete  and  adhere  to  its  PCI  Compliance  requirements  applicable  to
    Customer, including but not limiting to completing PCI DSS Self-Assessment Questionnaires
    (SAQs).

  6. Miscellaneous

    6.1 Amendments to and Updates of the terms of this Schedule: Company may amend or update the terms of the Schedule from time to time in its sole discretion. Amendments will become effective upon posting of an updated version of the Schedule at www.unaric.com/policies/product-schedule-payonomy, and the “Last Updated” date above will reflect the date of the latest amendment. Customer is responsible for reviewing the Schedule periodically to stay informed of any changes. Continued access to or use of the Services after such posting shall constitute acceptance of the amended terms, subject to the limitations set out below. For the avoidance of doubt, this section 6.1 does not apply to Order Forms or to changes to fees, subscription terms, or renewal periods specified in an active Order Form, which may only be amended by mutual written agreement of the parties. Amended terms shall not apply to any active Order Form during its current term, but shall apply to any Renewal Term or new Order Form entered into after the effective date of the amendment.

    6.2 Term and Termination: This Schedule shall continue for the duration of the applicable subscription term as set forth in the applicable Order Form and shall renew in accordance with the Agreement. For clarification, this Schedule shall automatically expire upon expiration or termination of the Agreement or the applicable Order Form to which it relates without the need for further notice.  

    6.3 Conflict: In the event of a conflict between this Schedule and the Agreement, the terms of this Schedule shall govern with respect to the applicable Service only.