Changelog

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.

Testing a subscription integration shouldn’t mean waiting days to see what happens next.

We improved Rebill’s sandbox so you can validate renewals, failed recurring payments, retries, and the final subscription outcome within a single testing session.

Move a subscription forward when you need to

You can trigger the next charge for a sandbox subscription whenever you’re ready using:

POST /v3/subscriptions/{id}/sandbox/advance

Use it as many times as needed to move through the complete lifecycle:

Initial payment → Renewal → Failed payment → Retries → Final outcome

Instead of waiting for each scheduled charge, you can move through the flow step by step and validate the full subscription lifecycle in minutes.

Test subscriptions with hourly plans

Plans created through the API can now use an hourly frequency in sandbox.

This makes it possible to test renewals automatically without waiting for the previous minimum daily cycle.

Hourly frequency is available only in sandbox.

Simulate failed renewals and retries

We’ve also added new test card scenarios for Argentina, Brazil, Mexico, Chile, Colombia, and the United States.

You can use:

• A card that approves the initial payment and declines renewals.

• A card that always declines due to insufficient funds.

Both scenarios automatically trigger the subscription retry flow, so you can validate how your integration responds to a failed recurring payment without manually changing the payment method.

Complete the retry cycle in hours, not days

Automatic sandbox retries now run after:

2 hours → 2 hours → 3 hours → 3 hours

This reduces the complete retry cycle from 10 days to 10 hours, with no additional configuration required.

And when you need to test even faster, you can use the sandbox endpoint to advance each attempt and move through the full cycle in minutes.

Together, these improvements let you validate subscription creation, renewals, a failed payment scenario, every retry, and the final outcome before going live, without depending on support to modify the test flow.

These tools are available for card subscriptions in sandbox. Cash and bank transfer subscriptions are not included because their recurring payments are handled manually.

View test payment methods documentation

Every coupon now comes with its own payment history.

From the coupon details page, you can instantly see every payment where that coupon was redeemed, along with the most important information:

• Original payment amount

• Discount applied

• Final amount paid

• Customer

• Payment status

• Payment date

Need to start from a payment instead? You can also filter the Payments page by discount, making it easy to find every transaction associated with a specific promotion.

Whether you're measuring campaign performance, reconciling discounts, or investigating a customer issue, coupon activity is now just a couple of clicks away.