FloPay SDK Changelog

v1.10.4 - Payment-method setup is laid out like checkout #

The save-a-payment-method form now offers wallets and alternative methods the way checkout does, above the card form, and leaves out a method the provider cannot offer.

The React payment-method setup component now draws wallets and alternative payment methods with the same components as the checkout component, so a customer sees the same form whether paying or saving a method.

What changed

• Order. Wallets come first, then PayPal, then one tile per alternative method, then an or add a card rule and the hosted card form. Previously the card form came first.
• Apple Pay. Wallets are requested the way checkout requests them, so Apple Pay is offered wherever checkout offers it. Previously it appeared only in Safari with a card already in Wallet.
• Alternative methods are tiles. A method such as SEPA Direct Debit is a tile that opens its form and a Save … button. The tile appears once the provider confirms it can render the method.
• Unavailable methods are left out. A wallet the device does not have, or a method the provider does not support in the session currency (SEPA Direct Debit outside EUR, for example), is not drawn and onError is not called. Previously a save button could appear with no form above it.
• New error code. When no advertised method can be offered at all, onError receives payment_method_setup_unavailable with retryable: false.

Integration notes

No change is required. The props, callbacks and the methods offered are the same: the form still renders exactly what the setup session lists in advertisedPaymentMethods.

If your tests click [data-flopay-payment-method-save] for an alternative method, open that method's tile first ([data-testid="flopay-stripe-method-button-<method>"]).

To offer SEPA Direct Debit, send the customer's currency when you create the setup session.