Changelog

This release improves the payment experience in two key areas: checkout renders faster, and the 3D Secure flow for card payments handles authentication results more clearly and reliably.

Checkout shows up faster

Previously, the SDK waited for a payment method update before rendering the checkout form. That round trip could add around 500 ms before the customer saw the form.

With rebill@1.17.39, checkout renders first, and that update runs only when the customer submits the payment, safely and in order.

Customers see the payment form sooner, without changing when the payment method is charged or skipping the bank verification step.

A better 3DS experience

We also improved the 3D Secure flow for cards in cases where a bank-approved authentication could be misinterpreted.

When a bank approves a 3DS authentication without showing a challenge, the SDK now correctly recognizes that response as a valid approval.

And when a challenge is required, the iframe now allows biometric authentication and passkeys when supported by the bank.

How to use it

Update the rebill package to version 1.17.39.

There are no breaking changes and no integration changes required.

Available in: rebill@1.17.39

npm install rebill@1.17.39

Card-update notifications sent through WhatsApp now include a shorter link, keeping each message clear and easy to read.

Links are shortened automatically when the notification is sent. Open the subscription in your dashboard and request a card update as usual.

If WhatsApp is enabled as a notification method in your notification settings, your customer receives a shorter link through that channel to update their card.

Available now for card-update links sent in WhatsApp notifications.

This release improves how checkout captures the buyer's location, giving each new payment more accurate regional information for payment operations, price selection, and risk evaluation.

More context for every payment

We've improved how the SDK determines the country associated with each payment based on the buyer's location.

This gives different parts of the payment experience more accurate regional information:

• The country available in each payment's details.

• Price selection for multi-currency products and plans.

• Context used during risk evaluation.

The country determined for each transaction is available in the country field of GET /v3/payments and in the payment details.

A more accurate multi-currency experience

For products or plans with prices configured in multiple currencies, price selection depends on the buyer's location.

The SDK now uses more accurate regional context to determine which price applies to each customer. This allows buyers across different markets to access the price configured for their currency when available.

If you use multi-currency pricing, we recommend reviewing your configuration before updating to make sure each market has the expected pricing.

Products with a single price or fixed pricing are not affected.

We recommend updating

To take advantage of this improvement on new payments, we recommend updating the SDK.

Payments created before this update won't change and will keep the information they were originally recorded with.

No integration changes required

There are no new properties or changes to callbacks, events, or response structure.

You only need to update the SDK version to start using the new behavior.

Available in: rebill@1.17.38

npm install rebill@1.17.38