⚠️ This article applies to Pay-as-you-go accounts only.
What is Pay-as-you-go 2.0?
Pay-as-you-go 2.0 is a major update coming to BriteVerify that primarily changes how billing works for your account. Today, we meter your usage of verifications and send you an invoice at the beginning of every month. With 2.0, we are moving to a pre-paid credit system. To perform verifications, you will need to have a credit balance.
Is migration necessary?
Yes, it is necessary to migrate your account. On April 7, all un-migrated accounts will be automatically migrated, so be sure to take advantage of this transition period.
How do I know if my account has migrated?
If your account has not yet migrated, you will see a green update banner at the top of the My Lists page. It looks like this:
If your account has been migrated, this banner will not appear. Also, you will see your credit balance in the lower left corner.
What does migrating involve?
We've made migrating your account to 2.0 an easy, one-button click, but there are some housekeeping items to be aware of.
- Invoices are going away. As mentioned above, we are moving from a metered invoicing system to a pre-paid credit system. To do this, we need to close the books on your metered usage and bring the account to a fully paid status, which requires charging your payment method for any usage up to that point in the month. Then, we can restart your account under the new credit system. If you take advantage of the free 5,000 credits, your account balance will be 5,000. If not, your account balance will start with zero credits.
- To check your balance beforehand proceeding, go to the Usage tab. There you can see approximately how much you owe since your last invoice (not counting any verifications you may have performed in the previous hour).
- API usage requires Auto-replenish to be on. If you use one or more of the BriteVerify APIs, Auto-replenish is now required, so make sure it's turned on. Your API key access will be paused until it is. This measure is to ensure that your API implementations are never interrupted because your account runs out of credits.