Release 1.13

Unified Payments, QRs & Buttons: The generation of QR codes and payment buttons has been updated to rely on a unified Payment Links API, which uses payment-request` UUIDs to generate the visual assets. Legacy Endpoints: The older dedicated QR code and payment button API endpoints, although still supported, have been consolidated and are now officially marked as legacy.

Generic Document Support: Introduced a suite of generic API endpoints that allow integrators to dynamically support over 30 document types using standard scheme identifiers instead of hardcoded enums.
New Generic Webhook: Added the PEPPOL_DOCUMENT_RECEIVED` webhook type to uniformly handle the reception of any incoming Peppol document type, though it is incompatible with the legacy webhook types.
Country-Specific Compliance: Expanded the Peppol integration guide with detailed B2B/B2G e-invoicing mandates, enforcement timelines, and specific participant identifier guidelines for Luxembourg, the Netherlands, and Germany.
Retry strategy: Introduced a new retryStrategy parameter (NO_RETRIES and EXPONENTIAL_BACK_OFF) for Peppol asynchronous document sending to automatically handle temporary delivery failures.