FloPay Backend Changelog

v1.10.33 - Manage page handles saved Apple Pay, Google Pay and PayPal #

Customers on the hosted manage page can now see, add, remove and choose as their default a saved Apple Pay or Google Pay wallet or a PayPal account, as well as cards. Subscriptions the chosen method can pay move onto it, and the manage page webhooks carry the method's real type. PayPal can now be saved on a no-purchase setup session.

The hosted manage page could list a saved PayPal account but not change it, and did not show wallets saved for later use at all. Customers who pay with Apple Pay, Google Pay or PayPal can now manage those methods on the same page as their cards.

What changed

• The manage page lists cards, PayPal accounts and the Apple Pay and Google Pay wallets saved for later use. Every row has a method type, a readable label such as Apple Pay or PayPal (a•••@example.com), and a real default marker.
• Customers can remove a wallet or a PayPal account. A PayPal account that a subscription still depends on stays, with the existing payer-action code.
• Customers can make a wallet or a PayPal account their default. The active subscriptions it can pay move onto it, and the rest are reported with the existing reasons. Renewals and retries try the default first, whatever its type.
• A setup started from the manage page carries the currency of the customer's subscriptions (or else the merchant's default currency), so Apple Pay and Google Pay can be offered. A wallet or PayPal saved there becomes the default, and the setup result now names its method type.
• PayPal can be saved on a no-purchase setup session: the vault setup token is created on the PayPal account the session offered.
• The "used for" list on the manage page now includes subscriptions paid by a saved wallet or PayPal account.
• payment_method.added, payment_method.removed and payment_method.default_changed webhooks carry the real type (card or paypal) and a new methodType field.

Why it matters

Customers who chose a wallet or PayPal can keep their payment details up to date without contacting the merchant, and merchants learn exactly which kind of method changed.

Developer notes

• All changes are additive. Existing fields keep their meaning; readOnly stays on manage rows and is now always false.
• Webhook consumers that only expected type: "card" may now also see type: "paypal"; the new methodType names the wallet.
• One additive migration adds a nullable checkout_session_id column and index to user_non_card_payment_method.
• Merchant payment method endpoints are unchanged.
• This release contains no breaking changes.