🔒 Safer invoice data and more reliable profile RFCs

• Changed — Invoice counterparty names and RFCs — Since October 1, invoices no longer include the name or RFC of the other party. For example, on payroll (nomina) invoices the employer's RFC and company name (razón social) are no longer available; on income (ingreso) invoices, the same applies to the client being invoiced. This affects GET /invoices and invoice exports: the fields issuer_name, rfc_issuer, receiver_name and rfc_receiver stay in the schema but return null (or an empty cell in CSV) for the other party. The consulted individual's or business's own name and RFC are unchanged. In the Console, the invoices table now shows a single Role column instead of separate Issuer and Receiver columns.
• Improved — More reliable rfc on profiles — GET /profile/{identifier} now returns a complete RFC for people whose profile previously showed an empty, truncated or generic one. The field name and format are unchanged.
• Improved — More reliable webhook delivery — We reworked how verification webhooks are delivered end to end: events arrive more consistently and without duplicates. No changes are needed on your side.

🔒 Employer and client details no longer shared on invoices

To limit the data shared through Buró de Ingresos to what is strictly necessary, and to protect the data of our Data Partners, GET /invoices and invoice exports now only return the RFC and name of the consulted individual or business:

• The counterparty's fields are null (or empty in CSV): the issuer (issuer_name/rfc_issuer) when the subject is the receiver — e.g. the employer on a nomina invoice — and the receiver (receiver_name/rfc_receiver) when the subject is the issuer — e.g. the client on an ingreso invoice.
• The subject's own RFC and name are unchanged, and so are all amounts, dates and income signals.
• The response schema is the same, so integrations that already treat these fields as nullable keep working.
• In the Console, the invoices table replaces the Issuer and Receiver columns with a single Role column showing whether the consulted individual or business was the Issuer, the Receiver or Both (self-issued invoices) on each invoice.

🪪 More reliable profile RFC

Profiles now return a complete RFC when one is available for the person, instead of an empty, truncated or generic value. This may change the rfc returned by GET /profile/{identifier} for a small share of people; the field location and format are unchanged.