The Seqino PDP API provides a modern and simplified interface to France's e-Invoicing services, giving you the power of a Platform de Dématérialisation Partenaire (PDP) without the burden of managing one.
Core Concepts
Understanding the relationship between Sponsors, Clients, and Mandates is essential to working with the Seqino PDP API.
Key Entities
🏢 The Sponsor
Who: A Client of Seqino that signed up for the grey-label or white-label API. Examples include ERPs, Banks, Accounting Platforms, ODs.
Role: Provides PDP services to their customers using Seqino APIs.
Responsibility: Gather mandates, integrate Seqino's API. Manage invoicing operations on behalf of the Clients.
Creation process: Contract between Sponsor and Seqino.
👥 The Clients
Who: A company or a department that uses the Sponsor's software/service (external to Seqino) for electronic invoicing and other services.
Role: Create, send, receive, pay invoices.
Responsibility:
The client will need to sign a mandate or delegate its consent to the PDP Sponsor.
🤍 White label: the client designates the Sponsor as its PDP.
🖤 Grey label: the client designates Seqino as its PDP.
Identifier:
X-PDP-Client-Idheader (required for most operations). Unique identifier.Creation process: Through the Sponsor dashboard or Onboarding API.
📋 Mandate
What:
A Mandate allows the Client to grant the Sponsor the right to manage PDP operation on their behalf, specifically receiving invoices and managing their lifecycle.
The scope of a mandate reflects the scope of a PPF directory entry (Ligne d'annuaire). The following types of scopes are allowed:
SIREN
SIREN + suffix (Simple flat way of separating multiple departments without using SIRET)
SIREN + SIRET
SIREN + SIRET + routing_code (code routage)
Purpose: Materializes the relationship between a PDP (reception PDP) and a business entity.
Creation process: Through the Sponsor dashboard or Onboarding API.