Partner Terms & Conditions

Summary of operational and payment principles for parking partners using Comparkly.

Partnership Framework

1. Contractual Priority

This page provides a readable operational summary only. The signed partner contract remains the legally binding document and prevails in case of conflict.

2. Roles in the Comparkly Model

Comparkly operates the marketplace, booking interface, communications, and payout orchestration.
The parking partner provides the parking service to the customer.
Payments are processed by Stripe as regulated PSP through Stripe Connect (SCT). Comparkly provides marketplace orchestration and payment instructions.
Merchant of Record split applies by component: the Partner is Merchant of Record for the parking component, and Comparkly is Merchant of Record for the Comparkly service fee where charged to customers.
This summary is operational; exact allocation of legal and financial responsibilities is governed by the signed partner contract.

3. Partner Onboarding Prerequisites

An active approved partner contract is required before payouts can be executed.
Stripe Connect onboarding and KYC/KYB completion are mandatory to receive transfers.
If payout compliance is incomplete, payouts can be held until remediation.
Partners must provide and keep updated trader and tax information required for platform traceability and regulatory reporting (including DSA and DAC7 obligations).

4. Customer Payment Flow

LE70 and GT70 Charge Timing

LE70 bookings are charged in full at booking. For GT70 bookings, only non-refundable fees are charged at booking and the remaining parking amount is charged around J-30.

SCT Transfer Model

Partner settlement is executed under Stripe Connect SCT according to payout eligibility and release cycles defined in the signed contract.

Refunds and Reversals

In case of cancellation, refunds are processed through Stripe with automatic reversal of the partner transfer when applicable.

5. Payout Eligibility and Release Cycles

Payout eligibility is based on arrival date and booking/payment status according to contract rules.
Eligible bookings are released in bi-monthly cycles at 18:00 Europe/Brussels.
Cycle on day 15 (18:00): arrivals from day 1 to day 14 of the current month.
Cycle on day 1 (18:00): arrivals from day 15 to end of previous month.

Transfers are executed via Stripe Connect with transfer group traceability per booking.

6. Batch Validation, Holds, and Reversals

Before execution, payout batches are subject to internal controls (fraud checks, dispute checks, compliance checks, data consistency).
Comparkly can place a batch or payout item on hold when risk or compliance issues are detected.
After transfer execution, refund, chargeback, or correction events may trigger transfer reversal and/or compensation in future cycles.

7. Data Protection and Communications

For booking data exchanged under the partnership, Comparkly and the Partner each act as independent controllers for their own purposes and legal obligations.
Partners must maintain appropriate security and notify Comparkly of incidents without delay.
Payout and operational communications are available through the partner interface and operational emails.

8. Changes and Contact

Comparkly may update this summary when operations evolve. Contractual notice obligations remain governed by the signed partner agreement.

Partnership support: business@comparkly.com
Legal support: legal@comparkly.com

Last Updated: February 2026