Native PrestaShop VeriFactu module
PrestaShop extracts commercial facts from OrderInvoice and OrderSlip while AEAT rules, XML, certificates, and fiscal classification remain in Kairoseth Fiscal.
PRESTASHOP VERIFACTU · MODULE & INTEGRATIONModule v0.5.0 released
PrestaShop VeriFactu module: integrate invoices, credit slips, and QR without embedding AEAT logic in your store.
The PrestaShop VeriFactu integration connects native invoices and credit slips to Kairoseth Fiscal. The module extracts commercial data, validates before fiscalization, and consumes QR presentation generated by the secure core.
PRESTASHOP VERIFACTU INTEGRATION
PrestaShop keeps its workflow. The module adds the VeriFactu layer.
The module relies on OrderInvoice, OrderSlip, and native hooks. The store never receives the AEAT certificate or decides sensitive fiscal classifications.
Preflight before record creation
Validate an invoice or credit slip before fiscalization. If the runtime lacks the capabilities required for presentation, the flow fails closed.
QR on native invoice and credit-slip PDFs
The current module consumes server-authored presentation data and renders it through native invoice and OrderSlip PDF hooks.
Corrective operations based on OrderSlip
Each credit slip keeps its own identity, reference to the original invoice, and separate server-side fiscal profile.
Opt-in automation
Invoices and credit slips use separate switches that are disabled by default. The safe manual flow remains available without automation.
Capability-first compatibility
The module does not branch on a specific PrestaShop version number: it detects real hooks and capabilities, while CI documents the versions actually executed.
FISCAL CONNECT IMPLEMENTATION
How we implement the VeriFactu module in PrestaShop.
We do not sell only a module. Integration depends on your version, numbering, PDF flow, credit slips, installed modules, and actual runtime capabilities.
Review version and modules
We check the actual PrestaShop and PHP versions plus invoicing modules or customizations involved in OrderInvoice or OrderSlip.
Install module v0.5.0
We start from Kairoseth Fiscal's published reproducible ZIP, also validated through an upgrade path from the prior version.
Configuration and preflight
We validate numbering, customer data, taxes, currency, and server-side mapping before allowing fiscal side effects.
Test invoice and credit-slip flows
We verify a native invoice and, when relevant, a corrective OrderSlip with its own identity and idempotency.
Validate PDF QR presentation
We review displayPDFInvoice and displayPDFOrderSlip to confirm the PDF consumes server-authored presentation without inventing regulatory data.
Handoff and support
Implementation leaves capabilities, enabled automations, validation checks, and Fiscal Connect support documented.
HOW IT WORKS
From the native PrestaShop invoice to VeriFactu through a controlled flow.
Manual mode stays available even when automation is disabled. Invoice and credit slip follow the same rule: validate, create once, then reconcile.
PrestaShop provides the native invoice
The module reads number, date, currency, customer, totals, and tax breakdown through native OrderInvoice APIs.
Kairoseth Fiscal validates the payload
Preflight checks structure and consistency before an operation is created.
Create or reconcile with idempotency
If recordId already exists, the module refreshes state. It does not reissue an invoice as a fallback.
The PDF consumes server-authored presentation
Invoice and OrderSlip PDFs use QR URL and text already validated by the core, without rebuilding AEAT rules inside PrestaShop.
TESTED COMPATIBILITY
Three PrestaShop generations tested with the real ZIP.
Runtime remains capability-first while the CI matrix proves installation, payload creation, and upgrade flows on real combinations.
- PrestaShop 1.7.8+ through capability detection
- PrestaShop 1.7.8.11 / PHP 7.4 validated in CI
- PrestaShop 8.1.7 / PHP 8.1 validated in CI
- PrestaShop 8.2.7 / PHP 8.1 validated in CI
- displayPDFInvoice for invoices
- displayPDFOrderSlip for corrective credit slips
- Reproducible ZIP with a real 0.4.0 → 0.5.0 upgrade path
PrestaShop 1.7.8.11 · PHP 7.4
Module installation and smoke test completed successfully.
PrestaShop 8.1.7 · PHP 8.1
Module installation and smoke test completed successfully.
PrestaShop 8.2.7 · PHP 8.1
Module installation and smoke test completed successfully.
QR IN NATIVE PDF
VeriFactu presentation comes from the server; PrestaShop only validates and renders it.
After issuance or reconciliation, the module stores the returned presentation block and uses it in displayPDFInvoice or displayPDFOrderSlip. If a recordId exists but presentation is missing or invalid, rendering fails closed instead of inventing a QR.
FAQ
PrestaShop VeriFactu module questions.
Key points before installing or adapting the integration.
Is there a PrestaShop VeriFactu module in Kairoseth Fiscal?
Yes. Technical release v0.1.0 publishes PrestaShop module v0.5.0 while keeping sensitive fiscal rules outside the ecommerce application and using the same common contract as other connectors.
Is this a PrestaShop VeriFactu app, plugin, or module?
All three terms are used in searches. Technically, it is a native PrestaShop module connected to Kairoseth Fiscal: the store supplies invoices and credit slips while the secure runtime keeps certificates, AEAT rules, preflight, state, and idempotency. It is not a standalone fiscal app that duplicates regulatory logic inside ecommerce.
Which PrestaShop versions are tested?
The current matrix runs the real ZIP on PrestaShop 1.7.8.11 with PHP 7.4, PrestaShop 8.1.7 with PHP 8.1, and PrestaShop 8.2.7 with PHP 8.1. Runtime compatibility is capability-first from PrestaShop 1.7.8.
Does the VeriFactu QR appear in the invoice PDF?
Version 0.5.0 consumes presentation data authored by Kairoseth Fiscal and renders it through displayPDFInvoice. Credit slips use displayPDFOrderSlip. If the required capability is missing, issuance fails closed before a fiscal record is created.
What happens with PrestaShop credit slips?
Each OrderSlip is treated as an independent corrective operation linked to the original invoice, with its own idempotency and separate server-side corrective MappingProfile.
Can I start in manual mode?
Yes. The manual preflight → create record → refresh status flow is always available. Invoice and credit-slip automation are enabled separately and remain OFF by default.
Does PrestaShop store the AEAT certificate?
No. The certificate and sensitive fiscal credentials remain only inside the secure Kairoseth Fiscal runtime.
Does publishing the module mean my store can enable AEAT production immediately?
No. Module v0.5.0 is published and tested, but fiscal production activation is a separate gate. Controlled access refers to assisted fiscal go-live and onboarding, not to a pending module release.
How much does the PrestaShop integration cost?
We are not publishing amounts until W4 closes unit economics and support. The planned model separates setup where needed from a recurring Fiscal Connect fee.
TRUST & CONTROL
Authority stays explicit as the platform grows.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
KAIROSETH PLATFORMCONTROL PLANE
- Identity
- Shared account
- Verified
- Organization
- Tenant scope
- Required
- Product
- RBAC assignment
- Explicit
- Sensitive actions
- Policy gate
- Controlled
Organization scope
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Product-scoped roles
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Server authority
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Controlled execution
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Public trust evidence
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
KAIROSETH FISCAL + PRESTASHOP
Request PrestaShop VeriFactu integrationWe review your PrestaShop version and actual invoice and credit-slip workflow.
We check capabilities, version, PDF flow, fiscal numbering, and credit-slip workflow before activating a fiscal integration.