Verifactu with SumUp: how to connect your payments with the Verifactu API
Verifacti has no official SumUp integration: your own service reads each transaction from the SumUp API and sends it to the Verifactu API as a simplified invoice, which returns the QR for the ticket you give the customer (SumUp's receipt doesn't include it). 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 SumUp
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 SumUp with the API
Flow: charge in SumUp (periodic query of the transaction history) → your service → 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 a SumUp API key to read your transactions (with the merchant code in SUMUP_MERCHANT_CODE).
- SumUp doesn't notify each card-reader charge: query the history every few minutes (
GET /v2.1/merchants/{merchant_code}/transactions/history) and, for each new successful charge, read the transaction (products with their VAT) and callPOST /verifactu/createas a simplified invoice (F2). - Use your own series with sequential numbering and store
uuidandqrfor the ticket.
SumUp doesn't number invoices: you set the number, the next one in your series.
Do you build software and want to offer Verifactu to your customers? See POS.
Example: from the charge to the record
A Node.js function that reads the SumUp transaction, converts the VAT rate (SumUp gives it as a fraction: 0.21), groups the products by rate and sends it as a simplified invoice, without the tip. A free-amount charge with no products has to be completed by hand.
"use strict";
// Cobro en SumUp → API Verifactu como factura simplificada (Node.js 18+).
// Lee una transacción de la API de SumUp y la envía a Verifacti.
// Variables de entorno: SUMUP_API_KEY, SUMUP_MERCHANT_CODE, VERIFACTI_API_KEY.
const crypto = require('node:crypto');
const hoy = ()=>new Intl.DateTimeFormat('es-ES', {
timeZone: 'Europe/Madrid',
day: '2-digit',
month: '2-digit',
year: 'numeric'
}).format(new Date()).replaceAll('/', '-');
function factura(tx, numero) {
const porTipo = {};
for (const p of tx.products){
const tipo = String(Math.round(p.vat_rate * 10000) / 100); // SumUp da el tipo como fracción: 0.21 → 21
porTipo[tipo] ??= {
base: 0,
cuota: 0
};
porTipo[tipo].base += p.total_price;
porTipo[tipo].cuota += p.vat_amount;
}
return {
serie: 'SUMUP-',
numero,
fecha_expedicion: hoy(),
tipo_factura: 'F2',
descripcion: 'Venta con SumUp',
lineas: Object.entries(porTipo).map(([tipo, l])=>({
base_imponible: l.base.toFixed(2),
tipo_impositivo: tipo,
cuota_repercutida: l.cuota.toFixed(2)
})),
importe_total: (tx.amount - (tx.tip_amount || 0)).toFixed(2)
};
}
// numero: el siguiente de tu serie de facturas (correlativo y sin huecos)
async function registrarCobro(transactionCode, numero) {
const sumup = await fetch(`https://api.sumup.com/v2.1/merchants/${process.env.SUMUP_MERCHANT_CODE}/transactions?transaction_code=${transactionCode}`, {
headers: {
Authorization: `Bearer ${process.env.SUMUP_API_KEY}`
}
});
const tx = await sumup.json();
if (tx.status !== 'SUCCESSFUL') return null;
if (!tx.products?.length) return {
status: null,
error: 'Cobro sin productos: indica la base y el tipo de IVA a mano'
};
const cuerpo = JSON.stringify(factura(tx, numero));
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': `sumup-${transactionCode}-${crypto.createHash('sha256').update(cuerpo).digest('hex').slice(0, 12)}`
},
body: cuerpo
});
return {
status: r.status,
registro: await r.json()
}; // guarda registro.uuid y registro.qr
}
module.exports = {
registrarCobro
};The code groups the lines by VAT rate and always sends a simplified invoice (F2); if the customer asks for a full invoice, issue an exchange invoice (F3). It sends the Idempotency-Key header with the transaction identifier plus a digest of the body: an identical retry never duplicates the invoice and, if you fix the data after an error, the key changes. 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 SumUp
| Case | What to do | Read more |
|---|---|---|
| Numbering | Use your own series per POS, sequential and gap-free | 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 SumUp
More questions about VerifactuIs there an integration from Verifacti for SumUp?
Does SumUp 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?
Connect SumUp in the test environment
Create your free account and try the API with a test NIF before going to production.