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.

We've made subscription testing in sandbox easier.

Until now, hourly billing frequency was only available through the API. You can now configure it directly from the Dashboard when creating a plan or a subscription Payment Link.

Configure hourly plans without using the API

In sandbox mode, you'll find hourly frequency under Custom.

This gives merchants integrating Rebill and their development teams a faster way to test recurring billing cycles directly from the Dashboard.

Hourly frequency remains exclusive to sandbox and does not affect production configurations.

A simpler testing experience

Hourly billing works alongside the existing sandbox tools for advancing subscriptions and testing renewals, failed payments, and retries.

You can now configure more of that testing flow directly from the Dashboard, reducing the steps required to validate your integration before going live.