> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/vente-en-ligne/procedure-de-mise-en-place-de-payline/note-technique-et-fonctionnelle-integration-payline.md).

# Technical and Functional Note – Payline Integration

**Company:** Vakario (publisher of Yoplanning software) **Product concerned:** Yoplanning booking engine **Date:** October 2025 **Subject:** Description of the payment flow via Payline (MONEXT) and PCI DSS compliance

***

### 1. Background

Yoplanning is a SaaS solution for online management and booking used by leisure and outdoor activity operators. Vakario does not collect, process, or store any credit card data. Payment integration is based exclusively on the Payline by MONEXT system, certified PCI DSS Level 1 (certificate attached).

***

### 2. General flow diagram

1. The customer clicks on **“Pay”** in the Yoplanning booking interface.
2. The Yoplanning server calls the Payline `do_web_payment` API with the following data:
   * Amount
   * Currency
   * Merchant's VAD number
   * Yoplanning order ID
   * `success_url` / `cancel_url` / `notification_url`
   * Payer's name, first name, email and billing address
3. Payline returns a **secure payment URL**, to which Yoplanning **redirects the customer**.
4. The customer enters their banking information on the **Payline page hosted by MONEXT**.
5. After authorization, Payline redirects the client to the configured URLs and **notifies the Yoplanning server**.
6. Yoplanning then calls `get_web_payment_details` to retrieve the payment information and **creates the internal order**.

***

### 3. Data recorded by Yoplanning

* Amount paid
* Currency
* Payline transaction number
* Order ID
* Billing data (last name, first name, email, address)

No credit card data is stored or handled by Vakario. All communications are encrypted via HTTPS (TLS 1.2 minimum).

***

### 4. Security and Compliance

* Integration in **redirection mode** (outside the PCI DSS Vakario scope).
* **AoC PCI DSS v4.0** certificate from MONEXT covering all processing.
* **No** credit card data is stored, manipulated or transmitted by Yoplanning.
* All connections are secured via HTTPS (TLS 1.2 minimum).

***

### 5. Maintenance and updates

* Checking Payline endpoints with each major update.
* API version tracking and regular internal audit.
* Retention of **non-sensitive technical logs** for traceability.

***

### 6. Annexes

MONEXT / Payline PCI DSS certification

{% file src="/files/c58gHtVz1jPobEVOYhXc" %}

***

**Vakario – Yoplanning** \&#xNAN;*Spublisher of the Yoplanning software* 📧 <support@yoplanning.com> 🌐 <https://yoplanning.com>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/vente-en-ligne/procedure-de-mise-en-place-de-payline/note-technique-et-fonctionnelle-integration-payline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.