What is the "monthly" bucket in my Credits History?

Every row in the Valid Email Checker Credits History page is tagged with a bucket — the source or destination of the credits in that transaction. "monthly" is one of the two active bucket labels you will see, alongside "payg". Knowing which bucket a transaction touched explains why your balances moved the way they did.

What "monthly" actually means on a row

A row tagged "monthly" means the credits in that transaction either came from or went to your subscription bucket. The subscription bucket is the pool that resets at the end of each billing period. When you signed up for a monthly plan, the credits that landed in your account immediately afterward show up as "monthly" rows. When you verify an email and the credit is deducted from your subscription allotment, that row is also tagged "monthly".

When you will see "monthly" rows

• Subscription activation or renewal — credits arriving from your monthly plan show as purchase_monthly or subscription_renewal with bucket "monthly".
• Verifications drawn from subscription credits — when the consumption order drains Monthly first, every credit spent shows up as a single_verification, bulk_verification, or api_bulk_verification row with bucket "monthly".
• Refunds returning to Monthly — if an Unknown result was originally paid for from Monthly, the refund row is tagged "monthly" as well.

Bulk jobs may produce two rows

A bulk verification that drains your Monthly bucket and then dips into PAYG produces two rows in Credits History: one tagged "monthly" for the portion drawn from Monthly, and one tagged "payg" for the portion drawn from PAYG. Both have the same description and timestamp, so you can match them up. The total credits used equals the sum of the two rows. See also what is the "payg" bucket.

Monthly resets, so leftover does not roll forward

Monthly credits reset every billing cycle. If you finished a cycle with unused Monthly credits, you will not see a "rollover" or "carry-forward" entry in Credits History — there isn't one, because the credits expire silently when the cycle ends and the new cycle starts with a fresh allotment. The legacy rollover_addition transaction type that did the carry-forward is no longer emitted on any account (see the legacy rollover bucket).

No subscription = no monthly rows

Pay-As-You-Go-only users never see "monthly" rows in their history because they never had a subscription. Everything in their Credits History will be tagged "payg". This is normal, not a problem.