FloPay Backend Changelog

v1.7.27 - Accurate PayPal opening invoices #

PayPal subscription checkouts now retain one opening invoice, keeping payment records, merchant events, and later refunds aligned.

PayPal subscription checkouts now retain the purchase and invoice created during checkout when PayPal confirms the opening charge. Merchants see one opening payment and invoice across reporting, customer timelines, and webhook delivery, including when confirmations are repeated or arrive concurrently.

What changed

• The opening PayPal charge remains associated with the original checkout purchase and invoice instead of producing a second billing record, and it is not counted as a subscription renewal.
• Mixed checkouts keep the correct amounts assigned to the subscription and any one-time items, so later refunds, reversals, and chargebacks remain associated with the affected purchases and opening invoice.
• Repeated or concurrent confirmations produce one complete set of the existing invoice.created, invoice.paid, and applicable item.purchased events. Opening charges do not emit subscription.renewed.
• When a confirmed historical duplicate is reconciled, reporting excludes the duplicate while previously issued payment and invoice identifiers remain usable.

Why it matters

• Payment, invoice, timeline, and reporting views no longer overstate PayPal opening activity with duplicate records.
• Finance teams and webhook consumers can reconcile the opening charge and later financial adjustments against the same checkout invoice.

Developer notes

• Public API routes, request and response schemas, SDK exports, webhook event names, and webhook payload schemas are unchanged.
• No SDK update, payload migration, merchant configuration, or operational action is required. Webhook consumers should continue to process events idempotently.