FloPay Backend Changelog

v1.10.28 - Customers can choose a default card on the hosted manage page #

A customer signed in to the Flopay hosted manage page can now make one of their saved cards the default, and their subscriptions with that merchant move onto it. A card added or replaced from the page becomes the default automatically. Merchant payment method and setup session endpoints are unchanged.

Until now, a customer could add, replace or remove cards on the hosted manage page, but could not choose which card their subscriptions use. Flopay now lets the customer choose a default card.

What changed

• A signed-in customer can make any of their active cards with that merchant the default. It becomes their only default card with that merchant, and the card list shows which card it is.
• Their active subscriptions with that merchant move to the default card, as long as the card can pay for them.
• Renewals try the default card first. If it cannot be charged, they fall back to the cards the customer already has on file, in the same order as before. Customers who never choose a default card are renewed exactly as before.
• Subscriptions the card cannot pay for stay on their current payment method, and the customer is told how many and why. This covers subscriptions paid through PayPal and subscriptions billed through a payment gateway where the card is not saved.
• A card the customer adds or replaces on the page becomes the default automatically, and the page shows how many subscriptions moved. The customer can choose another default at any time.
• If a subscription cannot be moved, nothing changes: the previous default card stays the default, every subscription stays where it was, and the customer can try again.
• Cancelled, expired and failed subscriptions, subscriptions with other merchants and other customers' cards are never changed.

Why it matters

• A customer who adds a new card can move their subscriptions off a card they mean to stop using, without contacting the merchant.

Developer notes

• Merchant payment method endpoints, setup session creation and cards saved through a merchant's own integration behave exactly as before. No new field appears in merchant responses.
• This release contains no breaking changes.