Verifactu with Stripe: how to connect your payments with the Verifactu API
Verifacti has no official Stripe app: you connect Stripe with the Verifactu API by listening to the payment webhook (invoice.paid) in your backend, which sends the invoice as JSON and stores the QR. No XML to generate, no hash to compute and no digital certificate: Verifacti sends the invoicing record to the AEAT as a colaborador social. In Álava, Bizkaia and Gipuzkoa, the same pattern works with the TicketBAI API.
Which APIs you need for Stripe
Your connector uses two pieces: the submission API that matches the NIF (Verifactu API in common territory; TicketBAI API in Álava, Bizkaia and Gipuzkoa) and the NIF management API, integrated once to register the NIF, manage the representation form and receive webhooks. Each NIF uses one API or the other depending on where it is taxed.
How to connect Stripe with the API
Flow: charge in Stripe (invoice.paid webhook; for one-off Checkout payments, enable invoice_creation and the same event covers them) → your backend → Verifactu API or TicketBAI API → AEAT or foral treasury.
- Register the NIF with the NIF management API and sign the representation form. Each NIF has its own API key.
- Create the webhook endpoint for
invoice.paidthrough the API, withapi_version: '2024-06-20'(stripe.webhookEndpoints.create): Stripe builds the event with the endpoint's version and the code reads fields of that version. - Verify the signature with
stripe.webhooks.constructEvent. - Build the invoice from the Stripe
invoice(number, taxes by rate, customer NIF) and callPOST /verifactu/createwith the event id asIdempotency-Key. - Store
uuidandqrand send the customer your own PDF or email with the QR: Stripe's PDF can't carry it. Turn off Stripe's invoice emails and PDFs.
Check in Stripe's invoice settings that numbering is account-level: then the number is sequential, and the code splits the prefix into series and the sequence into number. Zero-amount invoices are not sent.
Do you build software and want to offer Verifactu to your customers? See SaaS.
Example: from the charge to the record
A Node.js backend with Express and the official Stripe library. Taxes come from total_tax_amounts (base and amount per rate); if the customer has a Spanish NIF, the invoice is a full one (F1).
// Webhook invoice.paid de Stripe → API Verifactu (Node.js 18+, Express, stripe).
// Variables de entorno: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, VERIFACTI_API_KEY.
// El endpoint del webhook tiene que estar en la versión 2024-06-20 (créalo por API con
// api_version: '2024-06-20'): Stripe construye el evento con la versión del endpoint.
const express = require('express');
const Stripe = require('stripe');
const stripe = Stripe(process.env.STRIPE_SECRET_KEY, {
apiVersion: '2024-06-20'
});
const app = express();
const fecha = (segundos)=>new Intl.DateTimeFormat('es-ES', {
timeZone: 'Europe/Madrid',
day: '2-digit',
month: '2-digit',
year: 'numeric'
}).format(new Date(segundos * 1000)).replaceAll('/', '-');
const euros = (centimos)=>(centimos / 100).toFixed(2);
async function factura(invoice) {
const lineas = [];
for (const t of invoice.total_tax_amounts){
const tasa = await stripe.taxRates.retrieve(t.tax_rate);
lineas.push({
base_imponible: euros(t.taxable_amount),
tipo_impositivo: String(tasa.percentage),
cuota_repercutida: euros(t.amount)
});
}
const [, serie, numero] = invoice.number.match(/^(.*?)(\d+)$/);
const nif = (invoice.customer_tax_ids || []).find((id)=>id.type === 'es_cif' || id.type === 'eu_vat' && id.value.startsWith('ES'));
return {
serie,
numero,
fecha_expedicion: fecha(invoice.status_transitions.finalized_at),
tipo_factura: nif ? 'F1' : 'F2',
descripcion: invoice.lines.data[0]?.description || 'Suscripción',
...nif && {
nif: nif.value.replace(/^ES/, ''),
nombre: invoice.customer_name
},
lineas,
importe_total: euros(invoice.total)
};
}
app.post('/webhooks/stripe', express.raw({
type: 'application/json'
}), async (req, res)=>{
let event;
try {
event = stripe.webhooks.constructEvent(req.body, req.get('Stripe-Signature'), process.env.STRIPE_WEBHOOK_SECRET);
} catch {
return res.sendStatus(400);
}
if (event.type !== 'invoice.paid' || event.data.object.total === 0) return res.sendStatus(200);
const r = await fetch('https://api.verifacti.com/verifactu/create', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.VERIFACTI_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': event.id
},
body: JSON.stringify(await factura(event.data.object))
});
const registro = await r.json();
if (r.status !== 200 && r.status !== 400) return res.sendStatus(500); // Stripe reintentará el evento
if (r.status === 400) console.error('Verifacti', registro.codigo, registro.error);
// Guarda registro.uuid y registro.url en invoice.metadata y el QR en tu base de datos
// (la metadata de Stripe admite 500 caracteres por valor: el QR no cabe)
res.sendStatus(200);
});
app.listen(3000);The code groups the lines by VAT rate and uses F1 if the customer has a NIF and F2 otherwise. It sends the event id as Idempotency-Key: if Stripe resends the same event, the API returns the original response. The issue date is the date Stripe issued the invoice, so the body doesn't change even if the resend arrives another day. The response carries the uuid, the state (Pendiente: the submission to the AEAT is queued), the verification URL, the QR in Base64 and the hash: store them with the invoice.
More code in the Verifactu tutorials. For TicketBAI, the call goes to POST /ticketbai/create with the foral NIF's API key: the fields, in the TicketBAI API documentation.
Special cases in Stripe
| Case | What to do | Read more |
|---|---|---|
| Numbering | Every invoice needs a series with sequential numbering. If invoice numbers can have gaps, give the invoice its own number | Verifactu requirements |
| Customer without a NIF | Simplified invoice (F2), without nif or nombre. The API rejects an F2 above €3,000 (vf-verifactu-f2_limite_3000) | Simplified invoice |
| Return or refund | Corrective invoice: R5 if the original was simplified; R1–R4 if it was a full invoice | Corrective invoices |
| Customer asks for a full invoice later | Exchange invoice (F3) replacing the simplified one | Exchange invoice |
| Canary Islands, Ceuta and Melilla | IGIC or IPSI in the lines (impuesto field), not VAT | IGIC · IPSI |
| Products without VAT | Check whether they are exempt (operacion_exenta) or not subject (calificacion_operacion): they are not sent at rate 0 | Exempt invoice |
| Cancellation | Only for invoices that should never have been issued: POST /verifactu/cancel | Cancellation |
| Sale to another EU country | It depends on whether the customer is a business and on the distance-selling threshold | Intra-EU examples |
| Several companies or shops | One NIF per company, each with its own API key | NIF management API |
Dates
The first row only applies if you build the connector to sell it: then you sell invoicing software. For those who invoice, the Verifactu dates are published in the BOE and the postponement to October 2028 is announced with no rule published. In Álava, Bizkaia and Gipuzkoa, TicketBAI is in force.
| Who | Date | Status | Rule |
|---|---|---|---|
| Producers and resellers of invoicing software RDL 15/2025 did not change this date. | Since 29 Jul 2025 | In force | RD 1007/2023 · Orden HAC/1177/2024 |
| Corporate Income Tax payers | 1 Jan 2027 | Published in the BOE, future date | RDL 15/2025 |
| Everyone else, including the self-employed | 1 Jul 2027 | Published in the BOE, future date | RDL 15/2025 |
| Postponement of the pending obligations The note does not specify the scope for businesses invoicing over €8M. | Oct 2028 | Announced, no rule published | Nota de Hacienda, 5 oct 2026 |
| TicketBAI in Álava: foral taxpayers Phased from 1 April 2022; all other taxpayers since 1 December 2022. | Since 1 Dec 2022 | In force | NF 13/2021 y DF 48/2021 · FAQ 1.9 · calendario |
| Batuz in Bizkaia (TicketBAI and LROE): all taxpayers Companies that are not SMEs since 1 January 2024; everyone else in windows on 1 July 2024, 1 January 2025, 1 July 2025 and 1 January 2026. | Since 1 Jan 2026 | In force | NF 8/2023 · Batuz |
| TicketBAI in Gipuzkoa: foral taxpayers Phased by activity from 1 July 2022. | Since 1 Jun 2023 | In force | NF 3/2020 · DF 32/2020 |
This is not advice: each taxpayer determines what applies to them with their adviser.
More detail in Verifactu dates and TicketBAI.
Pricing
Public tariff of the Verifactu API and the TicketBAI API: you pay per NIF active in production, VAT excluded. Custom per-NIF pricing is available for volume.
From
€14.99
per month for the first NIF active in production, VAT excluded
See all pricing- The price per NIF goes down with every tier.
- Free test environment and test NIF.
- Annual plan with a 10% discount, no setup fees.
- Up to 3,000 invoicing records per month per NIF.
- Startup plan for companies under 12 months old, with under €100,000 in revenue and under €200,000 in funding.
- Same price with the Verifactu API and the TicketBAI API: each NIF uses one or the other depending on where it is taxed.
- Online signing of the representation form: €2.90 + VAT per signature.
Developer resources
For your AI: llms.txt and the OpenAPI specification.
Questions about Verifactu and Stripe
More questions about VerifactuIs there an app from Verifacti for Stripe?
Does Stripe comply with Verifactu on its own?
Does it work for TicketBAI too?
/ticketbai/create), the invoice fields and the API key change.Do I need a digital certificate?
How much does it cost?
Other integrations
Connect Stripe in the test environment
Create your free account and try the API with a test NIF before going to production.