Stripe: the connection's threshold decides simplified invoices again, and a buyer's NIF data never comes from the card
Without complete fiscal data, a charge above the connection's simplified threshold (400 € by default) is no longer issued: it waits as a draft standard invoice.
This replaces part of what we announced on 9 October. simplificada_threshold is no longer ignored, and the buyer data of a charge with a NIF is stricter. Charges that used to be issued automatically can now wait as drafts until the buyer's data is completed.
What else changed
- The threshold applies. A charge whose buyer has no complete fiscal data (tax ID, name and address) gets a simplified invoice only up to the connection's
simplificada_threshold. Above it, the charge waits as a draft standard invoice. The default is 400 €; you can raise it up to 3,000 €, which states that your activity is one of those in article 4.2 of RD 1619/2012. - With a NIF, the card is never used. The buyer's name comes only from the same Stripe object that carries the NIF, and the address only from what the buyer declared; the card adds nothing, not even the country. A NIF sent through metadata still accepts the card's billing details as declared.
- A NIF without name or address never becomes a simplified invoice. At any amount, the charge waits as a draft standard invoice until the data is completed.
Where to go next
Stripe: sales outside the Spanish VAT territory follow the product's tax code, and stop when in doubt
Whether a charge is goods or services now comes from the Stripe product's tax code; unclear cases stop with a retryable `TAX_TREATMENT_NEEDS_DATA` instead of being issued.
Payment events say how each one ended
Every payment event now carries `outcome`: `INVOICED`, `IN_PROGRESS`, `NOT_INVOICED`, `RESOLVED`, `INCIDENT` or `NO_CHANGE`.