Do not implement AEAT XML inside your product
Your application works with JSON and integration contracts while the bridge keeps transport, technical rules, and presentation inside the fiscal core.
VERIFACTU FOR CUSTOM SOFTWARE AND SAASv0.1.0 published
Add VeriFactu to your software without turning your product into another fiscal engine.
Integrate through REST API, server-side SDK, or webhooks. Your application keeps its domain while Kairoseth Fiscal centralizes preflight, idempotency, reconciliation, and VeriFactu presentation.
FISCAL API
Your team integrates a stable contract; Puente keeps the fiscal complexity.
The boundary is designed so SaaS and vertical software can add VeriFactu without distributing certificates, XML, and reconciliation rules across customers.
REST API v1 and server-side SDK
Integrate directly over HTTP or wrap the contract with the SDK without moving certificates or tenant authority into the frontend or customer environment.
Signed webhooks for event-driven flows
The webhook route uses HMAC signatures and anti-replay controls so source-system events are accepted without becoming implicit trust.
Preflight as a product endpoint
Validate payload, mapping, and configuration before issuing and return actionable errors to your own UI.
Idempotency-Key is required
The same operation keeps a stable identity even when your backend retries after timeouts, network errors, or asynchronous jobs.
Connector Contract Suite
Custom connectors can be validated against one common contract so each integration does not invent different semantics.
INTEGRATION CONTRACT
From your application JSON to fiscal state in four steps.
You can wrap the workflow inside your own interface and preserve your product's user experience.
Your software sends business facts
Invoice, customer, totals, and tax lines arrive as neutral JSON; you do not need to model AEAT SOAP/XML internally.
Puente applies mapping and preflight
Sensitive configuration stays server-side and errors return through a stable structure that can be integrated into your UX.
Issue with idempotency
Your backend uses Idempotency-Key and receives recordId/status without depending on a perfect remote response on the first attempt.
Status, reconciliation, and presentation
Your software can query state and consume the QR/text presentation contract without rebuilding fiscal rules locally.
KEEP AEAT OUT OF YOUR PRODUCT CORE
Integrate VeriFactu as a capability, not as a second fiscal architecture inside your software.
The goal is for your application to know the Kairoseth Fiscal contract without reproducing certificates, endpoints, hashing, QR, reconciliation, or regulatory changes in every installation.
FAQ
Questions for developers and custom software teams.
A clear technical boundary for integrating without duplicating the fiscal engine.
Can I add VeriFactu to my SaaS without building my own fiscal module?
Yes. Kairoseth Fiscal API is designed so your product keeps its functional domain while delegating the supported fiscal contract, preflight, idempotency, status, and presentation to Puente VeriFactu.
Do I have to use the SDK?
No. REST is the primary contract. The server-side SDK is a convenience layer for calls and semantics without changing the canonical protocol.
Can I use webhooks instead of calling the API from my backend?
Yes, when the source flow is event-driven. Webhooks are signed and tenant identity/mapping are resolved server-side.
Can the AEAT certificate live inside my application?
Kairoseth Fiscal keeps the certificate and sensitive fiscal secrets inside the secure runtime, not in frontend code, plugins, or the source system.
How should I handle errors before showing 'invoice issued'?
Run preflight before issue and then treat recordId/status as the operational source. If the remote result is uncertain, the bridge reconciles instead of recommending a blind resend.
Can I build my own adapter?
Yes. The project provides a Connector Contract Suite and reference connector. The broader Universal Adapter Contract remains a separate development stream, and any additional adapter must pass its own contracts and gates before it is presented as supported.
Can I start a custom software integration now?
Yes. Kairoseth Fiscal v0.1.0 is published and we can diagnose whether Fiscal API or Fiscal Custom is the better fit, define the contract, and validate preflight. AEAT production remains controlled access and is not enabled by purchasing a plan.
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 · SOFTWARE PROPIO
Check my softwareShow us your invoice model and we will design the minimum mapping.
We review payloads, events, retries, numbering, and UX so VeriFactu fits into your product without pushing fiscal complexity onto the end customer.