What is the legacy "rollover" bucket I see in my older Credits History?

If you signed up for Valid Email Checker before our subscription policy change, your Credits History may contain rows tagged with a third bucket called "rollover", along with a transaction type called rollover_addition. These are real entries from a previous policy and they will stay in your history forever, but no new rollover credits are being created on any account today.

What rollover used to do

In the previous subscription model, if you finished a billing cycle with unused Monthly credits, those credits were transferred into a separate "rollover" bucket at cycle-end rather than being reset to zero. A rollover_addition row landed in your Credits History to record the transfer. Rollover credits then sat in their own bucket and could be spent on later verifications.

What changed and why

The rollover policy was retired. New monthly subscriptions reset the Monthly bucket at cycle-end without carrying anything forward. PAYG covers the "credits that never expire" case more cleanly, and the two-bucket model (Monthly + PAYG) is easier to reason about than three. The rollover bucket survives only to display historical rows that already existed before the policy change.

How rollover credits behave on remaining accounts

If your account still has a non-zero rollover balance, those credits are spendable like any other. The consumption order is: Monthly first, then rollover, then PAYG (see credit consumption order). Verification rows that drain rollover are tagged "rollover" in the bucket column. Once the balance hits zero, the bucket is effectively dormant and you will not see any new rollover rows.

You will not see "rollover" on new accounts

If you signed up after the policy change, you will never see a "rollover" row, a rollover_addition transaction type, or a rollover entry in the balance widget. Your buckets are Monthly and PAYG only. See Monthly vs PAYG for how those two work.