FloPay Backend Changelog

v1.10.34 - Saved wallets show the card behind them #

An Apple Pay or Google Pay wallet saved without a purchase now keeps its card brand, last four digits and expiry, so customers can tell their saved methods apart on the hosted manage page and merchants get the same card details from the payment methods API.

A wallet a customer saved without a purchase, for example on the hosted manage page, was listed only as "Apple Pay" or "Google Pay". It is now saved with the card behind it.

What changed

• When an Apple Pay or Google Pay setup completes, the card brand, last four digits and expiry month and year of the card behind the wallet are saved with it.
• The hosted manage page lists such a wallet as, for example, Apple Pay · Visa •••• 4242.
• GET /v1/payment-methods returns brand, lastFour, expiryMonth and expiryYear for these wallets, as it already does for cards.

Why it matters

Customers with more than one saved wallet, or a wallet and a card, can tell them apart when they choose a default or remove one.

Developer notes

• No response shape changes: the fields already exist and were null for these wallets.
• The card details are read with the setup itself, on the account the setup ran on. If they are not available, the wallet is saved and the setup completes exactly as before, without them.
• Wallets saved before this release keep empty card fields; there is no backfill.
• Bank debit and card setup are unchanged. No migration.
• This release contains no breaking changes.