Beta Program Agreement

Last updated: July 13, 2026

This Beta Program Agreement (“Beta Agreement”) is between PaymentEvolution Corporation (“PaymentEvolution”) and the person or organization accepted into a PaymentEvolution beta, pilot, preview, early-access or evaluation program (“Participant” or “you”).

If you already have a Master Services Agreement (“MSA”) with PaymentEvolution, this Beta Agreement forms part of it and governs Pre-Release Materials. If you do not, MSA sections 2, 3.4–3.6, 5, 6, 7, 8.4, 9, 10.4–10.5 and 11 are incorporated as reasonably applicable. The Canadian Data Processing Agreement (“DPA”) applies whenever PaymentEvolution processes Personal Information for you. Applicable Law always prevails.

By accepting an invitation, clicking to accept or accessing Pre-Release Materials, you agree to this Beta Agreement. If you act for an organization, you confirm that you can bind it.

1. Purpose

The Beta Program lets approved participants evaluate incomplete features and provide feedback before general release. It is not a promise that a feature will be released, remain available or work in a particular way.

2. Eligibility and Accounts

You must be at least 18, have authority to participate and provide accurate registration information. Access is personal to approved users and may not be shared. You must protect credentials, use multi-factor authentication where offered and immediately report suspected unauthorized access.

PaymentEvolution may limit enrolment, features, data, capacity, countries, industries or use cases based on security, risk, legal or product needs.

3. Pre-Release Materials

“Pre-Release Materials” includes software, APIs, models, Documentation, designs, credentials, test data, prototypes, outputs and non-public information identified as beta, preview, pilot, experimental, evaluation or early access.

Pre-Release Materials may be incomplete, unstable, inaccurate, changed without backward compatibility, unavailable or never released. Do not rely on them for production, legal deadlines, payroll, tax, benefits, employment decisions or live payments unless PaymentEvolution gives written Production Approval under section 6.

4. Limited license

During the Beta Program, PaymentEvolution grants you a revocable, non-exclusive, non-transferable, non-sublicensable license to use the Pre-Release Materials only for the approved internal evaluation and feedback. PaymentEvolution and its licensors keep all intellectual-property rights. No right to production use, resale, white-labelling, publication or commercial exploitation is granted.

5. Restrictions

You must not:

• provide access or materials to an unapproved person;

• use the Beta Program for a live payroll, remittance, benefits decision or payment except under section 6;

• use real Personal Information where synthetic or de-identified data is sufficient;

• reverse engineer, copy or create a competing product from Pre-Release Materials except where law does not permit that restriction;

• bypass security, access, geographic, rate or usage limits;

• perform vulnerability or penetration testing without written authorization;

• scrape an interface or use an undocumented endpoint;

• use Pre-Release Materials, outputs or data to train a general-purpose AI model;

• publish benchmarks, screenshots or performance results without written permission; or

• use the Beta Program unlawfully, for high-risk safety-critical activity or to harm another person.

6. Payments and live data

6.1 Default rule: sandbox only

Beta payment activity must use a sandbox, synthetic data and test funds that have no real monetary value. Do not send live funds, bank instructions, payroll data or real payment credentials to a Beta environment.

6.2 Production Approval required

A Beta feature may process live Personal Information or Transactions only if PaymentEvolution gives separate written Production Approval that identifies the feature, environment, permitted data, payment flow, controls, responsibilities and duration. General Beta access, a successful test or an employee statement is not Production Approval.

Before approval, PaymentEvolution may require security review, the MSA, DPA, Order Form, End User Terms, identity verification, payment controls, a privacy assessment and regulatory assessment.

6.3 If live funds are received

If PaymentEvolution receives live Client Funds in connection with a Beta feature, MSA section 5 applies in full. A “test,” “beta,” “pending,” “clearing” or “in flight” label does not change whether funds are Held Funds or In-Transit Funds. PaymentEvolution’s safeguarding, transfer, return and principal-restoration obligations cannot be disclaimed or capped by this Beta Agreement.

7. Feedback

You may provide comments, bug reports, ideas and suggestions (“Feedback”). You grant PaymentEvolution a worldwide, perpetual, irrevocable, royalty-free right to use, modify and incorporate Feedback without payment or attribution. This does not transfer ownership of your Client Data or permit PaymentEvolution to disclose your Confidential Information.

Do not include third-party confidential information or Personal Information in Feedback unless necessary and authorized.

8. Confidentiality

Pre-Release Materials, non-public features, performance, roadmaps and related communications are PaymentEvolution Confidential Information. You will use them only for the Beta Program, protect them with at least reasonable care, and disclose them only to approved personnel who need access and are bound to protect them.

Confidentiality does not apply to information you can show was lawfully known without restriction, independently developed, lawfully received from another source or publicly available without breach. If law requires disclosure, give PaymentEvolution advance notice where permitted and disclose only what is required.

You may not make a public announcement about the Beta Program or use PaymentEvolution marks without written permission.

9. Privacy and security

The Privacy Policy and DPA apply according to the parties’ actual roles. You must use the least sensitive data reasonably needed, follow test-data instructions, restrict access, secure exports and integrations, and delete test data when requested or when the Program ends.

Notify privacy@paymentevolution.com and the Beta contact without unreasonable delay after discovering a Security Incident involving Pre-Release Materials or data. Preserve evidence, contain the issue and cooperate on remediation and legally required notices. Do not publicly disclose a vulnerability before PaymentEvolution has a reasonable opportunity to investigate and remediate, unless law requires otherwise.

10. Changes, support and availability

PaymentEvolution may add, change, suspend or remove Pre-Release Materials at any time. Unless the invitation says otherwise, no service level, maintenance, migration, data-recovery or support commitment applies. We may provide support at our discretion and may ask you to install updates or stop using an affected version.

Keep independent backups of permitted test data and do not make Pre-Release Materials a critical dependency.

11. Disclaimers

To the extent law permits, Pre-Release Materials are provided “as is” and “as available,” with all faults. PaymentEvolution does not promise that they will be secure, uninterrupted, accurate, complete, compatible, fit for a purpose, or released. They may cause errors, duplicate actions, data loss or business interruption. You are responsible for evaluation, human review and avoiding production reliance.

This disclaimer does not exclude a promise expressly stated in this Beta Agreement, our obligations for Client Funds, fraud, willful misconduct, gross negligence, or a duty that cannot legally be excluded.

12. Liability

If a separate MSA has been accepted or signed, its section 9 governs. If no separate MSA applies, the following standalone limits govern despite the limited incorporation of MSA terms at the start of this Beta Agreement: neither party is liable for indirect, incidental, special, exemplary or consequential damages, lost profit, revenue, goodwill or anticipated savings arising from the Beta Program, and each party’s total liability is limited to CAD $100.

The exclusions and cap do not apply to:

• PaymentEvolution’s obligation to transfer, return, safeguard or restore Client Funds;

• a party’s fraud, willful misconduct or gross negligence;

• breach of confidentiality, privacy or security obligations, for which the cap is CAD $10,000 if no MSA applies;

• infringement or misappropriation of the other party’s intellectual property;

• death or personal injury caused by negligence; or

• liability that Applicable Law does not permit the parties to limit.

13. Term and termination

This Beta Agreement begins when you accept or first access Pre-Release Materials and ends when the Program or your participation ends. Either party may end participation at any time. PaymentEvolution may suspend or terminate immediately for security risk, unauthorized disclosure, unlawful use, live payment activity without approval, material breach or a regulatory requirement.

On termination, stop using Pre-Release Materials, revoke credentials, return or destroy Confidential Information as directed, and delete test data unless retention is legally required. PaymentEvolution may delete Beta data without a migration obligation, subject to the DPA and any written Production Approval.

Termination does not affect pending live Transactions or Client Funds, which remain governed by MSA sections 5 and 10.4. Sections 5, 6.3, 7–9, 11–14 and provisions that by nature should survive will do so.

14. Export, sanctions and government use

You will comply with Canadian export controls and sanctions and will not make Pre-Release Materials available to a prohibited country, person or use. Government use requires PaymentEvolution’s written approval and any additional security, procurement and records terms.

15. General

The MSA general terms apply. If no MSA otherwise applies, Ontario law and the federal laws of Canada applicable there govern, and the parties submit to the courts in Toronto, subject to mandatory law. This Beta Agreement and the invitation or written Production Approval are the entire agreement about the Beta Program. A Production Approval can change a provision only if it identifies the provision and cannot override Applicable Law, the DPA or Client Fund protections.