1. Service provider
PayLinker is published by Nicolas MARTIN, 93 avenue Georges Clémenceau, 34500 Béziers, France, SIRET 518 239 926 00034, APE code 6201Z. Contact: contact@paylinker.fr.
2. Purpose and scope
These terms of sale and use, the “Terms”, govern PayLinker's service to customers acting for professional purposes. They cover payment links, transactional communications, ticketing, subscriptions, commissions and SMS credits.
They are not the terms between the Customer and its own customers or between an Organiser and a Buyer. The Customer must supply the pre-contractual information, sales terms, cancellation rules and refund policy appropriate to its activity.
3. Definitions
- Buyer: a person ordering one or more Tickets from the Organiser.
- Ticket: a paid digital admission title issued after a confirmed Order and linked to a validation method.
- Customer: the professional individual or organisation using the Service.
- Order: the selected Tickets and the related payment transaction.
- Control: a scan or manual Ticket validation.
- Recipient: a person receiving a payment link from the Customer.
- Event: an activity created and organised under the Customer's responsibility.
- Organiser: the Customer publishing an Event and selling Tickets to Buyers.
- Service: PayLinker's payment-link, communication and ticketing functions.
- Stripe: the payment provider used through the Customer's connected account.
- User: a person authorised by the Customer to access its PayLinker organisation.
4. Acceptance and version of the Terms
The Customer accepts these Terms when creating an account or when renewed acceptance is validly requested. The Customer must read them before using the Service and retain the version supplied to it.
The privacy policy informs individuals about data processing. Access to that policy is not general consent to processing required to perform the contract.
5. Professional account and access
The Customer supplies accurate, complete and current information, protects credentials, manages User permissions and promptly revokes unnecessary access. Suspected or unauthorised use must be reported to PayLinker.
PayLinker may request information reasonably required to confirm professional status, secure the Service or comply with law. The Customer is responsible for actions performed through its access, except where a failure is attributable to PayLinker.
6. Payment links
The Customer chooses the Recipient, amount, purpose and message. It warrants that it may lawfully use the Recipient's contact details and remains responsible for the underlying claim or service, its own terms and any refunds.
Depending on available functions, a link may request a deposit, earnest payment, security deposit or full payment. The Customer must correctly characterise the payment and explain its legal consequences. PayLinker supplies creation, delivery and tracking tools; it is not the creditor of the requested sum.
7. Email and SMS communications
The Customer may send transactional links and information by email or SMS. It checks the contact details, content and lawful basis and must not use these functions for unsolicited or unlawful marketing.
SMS delivery uses the credits shown in the interface. One SMS currently equals one credit, while email does not use SMS credits. Delivery also depends on third-party networks and providers.
8. Event creation and publication
The Service currently allows Events to be created without a separate creation charge and without a preset maximum number, subject to reasonable professional use, technical capacity and these Terms. The current product only permits Ticket types with a strictly positive price.
The Organiser supplies the name, description, cover, venue, date, time, relevant timezone, quantities and Ticket types. An operational connected Stripe account is required to publish and open sales where the flow requires it.
9. Organiser obligations
The Organiser alone is responsible for the Event's existence, legality, organisation and delivery. It obtains required permissions, insurance and rights, complies with safety and accessibility rules, and supplies accurate venue, schedule, price and admission information.
It sets quantities, sales, cancellation, postponement and refund terms, determines the applicable withdrawal regime, meets tax duties, authorises staff and handles Buyer claims concerning the Event.
10. Contract between Organiser and Buyer
The Ticket contract is made directly between the Organiser and the Buyer. PayLinker does not set the price, decide availability or admission, guarantee that the Event will take place, or decide cancellation or refund on its own.
Before an Order, the Organiser must make its identity, sales terms, cancellation or refund policy and Event information available. It is responsible for preserving evidence required by applicable law.
11. Ticket types, price and availability
The Organiser sets the price and capacity of each Ticket type and accounts for sales outside PayLinker. Selected places may be reserved temporarily during payment; allocation is final only after payment is confirmed and the server processes the Order.
The Organiser monitors availability and corrects errors attributable to it. A technical defect attributable to PayLinker is handled under the availability and liability provisions below.
12. Payment and connected Stripe account
Stripe processes payments through the Organiser's connected account. The Organiser enters into and maintains its Stripe agreement, completes requested checks and follows that provider's rules. In the audited flow, funds are directed to the Organiser's connected account; PayLinker does not store full payment-card data or hold the Organiser's funds.
Stripe may apply its own fees, delays, reserves, checks, suspensions and dispute procedures. PayLinker remains responsible for an integration defect directly attributable to it. Instalment options are only offered when made available by Stripe and under Stripe's criteria.
13. PayLinker pricing, subscription and commission
Unless a specific offer has been accepted, published pricing currently provides:
- a plan without a subscription carrying a PayLinker commission of 0.5% + EUR 0.20 per successful transaction, plus Stripe fees;
- a Pro plan at EUR 9.90 per month, with 0% PayLinker commission on transactions, while Stripe fees remain separate;
- SMS credit packs starting at EUR 15.
Applicable amounts, currencies and tax information are those displayed before purchase and on the invoice. Subscriptions are paid in advance for the stated period. SMS credits and started periods are refunded only where required by law, the accepted offer or a failure attributable to PayLinker.
14. Confirmation, issue and delivery of Tickets
Tickets are created only after Stripe actually confirms payment and PayLinker processes that confirmation. They are sent to the Buyer's supplied email address. Several Tickets from one Order may be grouped in one message, with each retaining its own validation method.
The Organiser should ask Buyers to check their email and provide a resend or support route. A browser return page alone is not proof of payment.
15. QR codes and personal use of a Ticket
Each Ticket has a unique QR code or validation method. The Buyer must protect it against copying and follow the Organiser's transfer rules. Sharing a Ticket may allow another person to use it first.
A recognised code enables technical validation but does not automatically prove the presenter's identity or replace other lawful admission requirements set by the Organiser.
16. Admission control
Users authorised by the Organiser may scan Tickets through the web or mobile interface or validate them manually. The Service may report a valid, invalid or previously used Ticket and record the Control history.
The Organiser applies least privilege, secures devices and revokes access promptly. A duplicate-scan warning assists the decision, but the Organiser remains responsible for reception and the final admission decision under law and its terms.
17. Event cancellation, postponement or change
The Organiser decides and is responsible for cancelling, postponing or materially changing an Event. It informs Buyers within an appropriate time and applies the law and the terms accepted at sale.
Archiving an Event in PayLinker does not cancel it, notify Buyers or issue refunds. The Organiser must arrange those actions and retain a way to handle existing Orders.
18. Refunds, fees and disputes
Where a refund is due or granted, the Organiser determines the amount and executes it through Stripe or the agreed method, except for an obligation directly applying to PayLinker. Stripe fees and PayLinker commissions follow the accepted price schedule, payment-provider terms and mandatory law; repayment of those fees is not automatic.
The Organiser handles disputes and chargebacks relating to its service and supplies supporting evidence. PayLinker cooperates within its role and remains responsible for consequences directly caused by its proven fault.
19. Buyer withdrawal rights
The Organiser determines the withdrawal regime applicable to the sold service and informs the Buyer before the Order. Certain leisure services supplied on a specific date or during a specific period may fall within the exception in Article L221-28 of the French Consumer Code, but the exception does not automatically apply to every Event.
Where a withdrawal right applies, the Organiser supplies the information and facilities required by law. PayLinker does not legally classify the Event on the Organiser's behalf.
20. Prohibited activities and content
The Service must not be used for unlawful, fraudulent, misleading, infringing or Stripe-prohibited activity. The Customer must not enter card data, secrets, unnecessary sensitive data or prohibited content into free-text fields.
PayLinker may remove manifestly unlawful content or suspend sales where security, law or a serious emergency requires it. The Customer is informed where possible and permitted.
21. Intellectual property
The Customer retains rights in its text, images, marks and other content and grants PayLinker, for the time required to provide the Service, a non-exclusive right to host, technically reproduce and display it as instructed.
The Customer warrants that it has all necessary rights and permissions. PayLinker retains rights in its software, documentation, brands, interfaces and original work.
22. Availability, maintenance and incidents
PayLinker applies reasonable professional measures to maintain Service availability and security. Maintenance, incidents, third-party providers or force majeure may cause interruption. Planned operations are arranged to limit impact where possible.
For an Event where admission is critical, the Organiser should prepare a proportionate continuity procedure, such as a secured attendance list, without bypassing validation rules.
23. PayLinker liability
PayLinker is liable for direct, certain and foreseeable loss resulting from a proven breach attributable to it. It is not responsible for the Organiser's service, content, admission decisions or an independent act of Stripe, without prejudice to an integration defect attributable to PayLinker.
To the extent permitted by law, PayLinker's total liability is limited to sums actually paid by the Customer for the Service during the twelve months preceding the event giving rise to the claim. The limitation does not apply where prohibited, including fraud, gross fault, personal injury or an obligation that cannot lawfully be limited.
24. Customer liability
The Customer is responsible for its breaches, content, regulated activity, Users and obligations to Recipients and Buyers. It cooperates in good faith to limit loss and address claims.
It may not make PayLinker bear consequences specific to its own Event, content or choices. Equally, no provision removes the Customer's remedy for a fault attributable to PayLinker.
25. Data protection
PayLinker is controller for its own accounts, contracts, duties, support and security. For Recipient, Buyer, attendee, Ticket and Control data processed on the Customer's instructions, PayLinker generally acts as processor and the Customer as controller.
The Customer supplies required notices, identifies a lawful basis, limits data and access, handles rights and avoids unnecessary sensitive data. The privacy policy explains PayLinker's processing. Where PayLinker acts as processor, the terms required by Article 28 GDPR are agreed with the professional Customer.
26. Suspension, termination and end of contract
PayLinker may proportionately suspend all or part of the Service for a security risk, suspected fraud, non-payment, legal requirement, manifestly unlawful content, Stripe unavailability or material breach. Notice is given where compatible with urgency and law.
The Customer may end its subscription through its account where that function is available; a started period remains payable under the accepted offer. Ending the contract does not remove the Customer's duties to Recipients or Buyers. Data access, return, archiving or deletion follow applicable law and instructions.
27. Changes to the Service and Terms
PayLinker may change the Service or Terms for a legitimate functional, legal, technical, pricing or security reason. Material changes are communicated within a reasonable advance period unless legal or security urgency requires otherwise.
The applicable version and date remain available. Where renewed acceptance is necessary, it is requested before the relevant functions continue.
28. Force majeure
Neither party is liable to the extent an event meeting the French-law criteria for force majeure prevents performance. The affected party informs the other, reasonably mitigates the effects and resumes performance as soon as possible.
29. Governing law and disputes
The Terms are governed by French law, subject to mandatory rules. In a dispute, the parties first seek an amicable solution by writing to contact@paylinker.fr.
If no agreement is reached, the competent courts are determined under applicable procedural rules. This contract is for professionals and does not remove any mandatory protection available to either party.
30. Effective date
This version is dated 14 July 2026 and applies from publication. Earlier versions remain applicable to periods during which they were accepted, subject to mandatory law.
Last updated: 14 July 2026