Does Stripe issue legal invoices in Spain? The truth about Stripe Invoicing and Verifactu

#The short answer

No. Stripe does not issue legal invoices valid in Spain. Stripe Invoicing generates PDF documents that are useful for your customer, but it does not implement the cryptographic chaining, the SHA-256 fingerprint, the verifiable QR code or the real-time submission to the AEAT (Spanish Tax Agency) required by the Verifactu regulation since 1 July 2025. To comply you need certified invoicing software connected to your Stripe account.

#What is Stripe Invoicing?

Stripe Invoicing is the Stripe tool that generates and sends PDF invoices linked to a payment. It allows you to add VAT, customer details, sequential numbering and basic branding, and it is fully functional for Anglo-Saxon markets where the sales document does not require a fiscal signature.

What Stripe Invoicing does do:

• Creates a PDF with a tax breakdown (Stripe Tax)
• Sends it to the customer by email
• Applies sequential numbering per account
• Provides a hosted invoice page (public URL with the document)
• Marks the payment status: open, paid, void

What Stripe Invoicing does not do, with regard to the 2026 Spanish regulation:

• Does not sign each invoice with a hash chained to the previous one
• Does not generate the AEAT verification QR
• Does not submit the billing record to the Tax Agency
• Does not implement the mandatory RRSIF fields (Royal Decree 1007/2023)
• Is not certified software under the Verifactu regulation

For a company or freelancer in the US or UK, Stripe Invoicing is enough. For an individual or legal entity with tax residence in Spain, it is only the first step.

#What is Verifactu?

Verifactu is the mandatory technical system that regulates how invoices must be issued, signed and submitted in Spain from 1 July 2025 (companies) and 1 July 2027 (freelancers, after the postponement approved in 2026). It is defined in Royal Decree 1007/2023 and develops the Anti-Fraud Law (Law 11/2021).

In practice, a Verifactu-compliant invoice has four technical requirements that no international payment gateway meets by default:

1. Chained SHA-256 hash — each invoice includes the fingerprint of the previous one, forming an immutable chain
2. Verifiable QR code — printed/embedded in the PDF, redirects to the AEAT portal
3. Automatic submission to the Tax Agency — the record is sent in real time through the official API
4. Certified software — the system that issues them must be declared compliant with the RRSIF

If any of these four elements is missing, the invoice is not legal according to the AEAT, even if it has a perfect PDF and the customer has paid it.

#Comparison: Stripe Invoicing vs Verifactu invoice

Summary: Stripe Invoicing covers the form of the document. Verifactu regulates the legal substance that the document must have to be a valid invoice in Spain.

#The 5 things Stripe doesn’t do to comply with Verifactu

If you only rely on Stripe Invoicing, these are the concrete gaps:

1. It does not generate the chained hash. The AEAT requires each invoice to include the SHA-256 of the immediately previous one. Without that chain, an audit detects that your software is not Verifactu.
2. It does not issue the verification QR. The QR must encode issuer NIF, number, date and fingerprint, and point to the prewww1.aeat.es portal. Stripe generates a QR to go to the hosted invoice page, not to the official verifier.
3. It does not send the record to the AEAT. Verifactu requires submitting each invoice, automatic or “voluntary-on-demand” (non-Verifactu mode), to the SOAP API of the Tax Agency. Stripe never talks to the AEAT.
4. It does not include the RRSIF fields. The regulation requires a set of specific fields (IDEmisorFactura, NumSerieFactura, Huella, TipoFactura, etc.) in a normalised XML format. The Stripe Invoice JSON does not map 1-to-1.
5. It is not certified. The RRSIF requires the issuing software to declare conformity and keep cryptographic traceability of the records. Stripe, as an international gateway, is not in this register.

Conclusion: Stripe can be your payment source, but the legal invoice source has to be another system.

#What happens if I only use Stripe Invoicing in Spain?

The RRSIF penalty regime classifies infractions in two levels:

• Penalty for the software user: up to €50,000 per fiscal year if it is proven that you use a non-compliant system.
• Penalty for the software manufacturer: up to €150,000 per fiscal year and per type of infraction if non-certified issuing software is marketed.

On top of this is the operational risk: if the AEAT requests the invoices in an inspection and you cannot provide the registry book signed in Verifactu format, you face a VAT regularisation based on estimated turnover — historically upwards.

The dates are clear:

• 1 July 2025 — entry into force for companies with turnover > €6M
• 1 January 2026 — remaining companies (with negotiated technical extension)
• 1 July 2027 — freelancers and professionals (dates confirmed after the 2026 postponement)

If your activity charges via Stripe and issues to Spanish customers or residents in Spain, you are within scope.

#The solution: a Stripe ↔ Verifactu software connector

The correct architecture is not “replace Stripe” — Stripe is still your gateway. It is connecting Stripe to certified invoicing software that listens to each payment and issues the legal invoice in parallel.

The pattern is called a connector and it solves the previous five gaps without asking you to modify your charging code:

• Your Stripe stays intact: payment links, checkout, subscriptions, webhooks
• The connector listens to payment events via Stripe Connect (OAuth 2.0)
• For each confirmed payment, it generates a Verifactu invoice with hash + QR + AEAT submission
• The invoice is sent to the customer by email, or remains available via API for your system

It is the only reasonable route if you already have Stripe in production and you cannot (or do not want to) migrate to a Spanish gateway.

#How a Stripe + Verifactu connector flow works

Take the case of BeeL., which uses exactly this model:

1. OAuth connection with Stripe Connect. You authorise BeeL. from the Stripe dashboard in one click. You don’t share API keys, you don’t install webhooks. Access is read-only over transactions and can be revoked at any time.
2. Series and filter configuration. You define which payments generate an invoice (for example, ignore micropayments < €5) and with which sequential series (STRIPE-2026-, SUB-2026-, etc.). One series per Stripe store if you have several accounts.
3. Automatic event detection. Each payment_intent.succeeded, invoice.payment_succeeded or charge.refunded triggers the invoicing logic: BeeL. creates the Verifactu invoice (or rectifying invoice, if it’s a refund), signs it with SHA-256, generates the QR and sends it to the AEAT.
4. Delivery to the customer. The PDF invoice with valid QR arrives in the customer’s email automatically, with the fiscal branding of your company or activity. Your internal system receives BeeL.’s invoice.created via webhook if you want to store the legal id.

The result: every euro charged through Stripe has its legal Verifactu invoice, with no development and no risk of non-compliance.

#Quick comparison: Stripe ↔ Verifactu connectors on the market

Not all market solutions fit the same profile. These are the five main ones you’ll bump into when researching:

#How to choose in 30 seconds

• You’re a freelancer or SME charging via Stripe in Spain, and you want REST API + multi-store in a single plan → BeeL. Developer (€15.90/month annual).
• Your volume is very low (less than 25 invoices/month) and you sell with several gateways → Quaderno.
• You’re a multi-country SaaS building legal invoicing across several regimes (Spain + Italy + Poland) → Invopop.
• Your tax residence is in the Basque Country and you need TicketBAI in addition to Verifactu → Verifacti.
• You already have an app installed in the Stripe Marketplace and your volume is stable → EasyVerifactu.

Individual comparisons: BeeL. vs EasyVerifactu · BeeL. vs Verifacti · BeeL. vs Invopop · BeeL. vs Quaderno. Full hub at The best Stripe + Verifactu integration in 2026.

#Frequently asked questions

#Is Stripe Invoicing a valid electronic invoice?

Not in Spain. It’s a payment PDF with numbering, but it lacks the four Verifactu elements: chained hash, AEAT QR, submission to the Tax Agency and software certification. In countries without these requirements (US, UK, part of the EU), it can be sufficient.

#Can I keep using Stripe if I have to comply with Verifactu?

Yes. Stripe stays as the payment gateway — what changes is that the legal invoice is issued by certified software connected to your Stripe, not by Stripe Invoicing. Your charging flow is not modified.

#Does Stripe Tax comply with Verifactu?

No. Stripe Tax calculates and applies the correct VAT rate based on country and product, but it is not a system for issuing legal invoices in Spain. It is complementary to Verifactu, not a substitute.

#Do I need to modify my current Stripe code to connect Verifactu software?

No, if you use a connector based on Stripe Connect (OAuth 2.0). You authorise access from the Stripe dashboard and the connector subscribes to events without you touching the code. If you build it by hand against the API of an invoicing software, yes: you’ll add 500–1,000 lines of integration.

#What about Stripe refunds in Verifactu?

Each charge.refunded (total or partial) must generate a rectifying invoice that is also signed, chained to the previous hash and sent to the AEAT. A good connector does it automatically; if you handle it manually, it’s one of the points where the most mistakes are made. There is a complete guide to rectifying invoices here.

#Does Verifactu apply if I only charge for recurring subscriptions?

Yes, and with added casuistry: prorations, mid-cycle plan changes, applied credits and cancellations generate invoices or rectifying invoices that must be chained correctly. It is one of the most technically demanding flows.

#If I’m a freelancer and it’s not yet mandatory for me, should I wait?

The mandatory date for freelancers is 1 July 2027. Waiting until the last month implies an accelerated migration, compressed testing and risk of incidents in production. Adopting it voluntarily before gives you months of buffer and a fiscal advantage: Verifactu invoices are presumption of veracity before the AEAT.

#Can I send Verifactu invoices to foreign customers?

Yes. The invoice is signed and sent to the AEAT in the same way, and the QR remains verifiable. What varies is the application of VAT (intra-community, export, ROI). The PDF received by the customer outside Spain includes the QR but does not require anything from them — it is traceability for your Spanish taxation.

#Conclusion

Stripe is one of the best payment gateways in the world, but it is not a legal invoicing software in Spain and has no intention of being one: the Spanish fiscal market is too specific for a global company to maintain certification.

The right question is not “should I leave Stripe?” — it is “how do I connect Stripe to certified software that issues the Verifactu invoice on my behalf?”. The modern answer is an OAuth connector that listens to Stripe events and handles the rest, without you having to touch your codebase.

If you want to see how it’s done in practice, at BeeL. + Stripe you have the complete flow: from the OAuth connection to the automatic issuance of Verifactu invoices for Payment Links, Checkout, subscriptions and multi-store. You connect in one click and start issuing the same day.