Why does the checkout button say report purchases are not available?
The button is disabled because paid report purchasing is switched off right now. Nothing is wrong with your VIN or your card, and no payment can start.
Check the review date and linked sources for context. Live availability, prices and record coverage can vary by VIN, source, jurisdiction and time.
That label means paid report purchasing is currently switched off, not that something is wrong with your VIN or your card. The review page reads “Report purchases not yet available” whenever the site's commerce readiness check reports checkout as not ready, or after an attempt came back with the not-active response. While the button is disabled no payment can be started, and your free VIN decode keeps working.
- It is a site-side availability state, not a rejection of your vehicle or your payment method.
- A disabled purchase action means no payment can be started at all.
- Free VIN identity decoding and the provider sample report are unaffected.
What the readiness check is protecting
Every page asks a commerce health endpoint whether checkout is ready, and the review page mirrors that answer on the button. The readiness behind it is operational, not cosmetic: it checks payment configuration, that the order database schema is in place, that a report fulfillment worker is alive and recently seen, that recent fulfillment jobs are not failing, that report email delivery is healthy, and that provider report capacity exists.
The gate is deliberately fail-closed. If any of those signals cannot be confirmed, purchasing closes rather than accepting money for a report we may not be able to generate and deliver. That is the same principle as the pricing page's statement that when the purchase action is disabled, no payment can be started.
What you can still do right now
Your free VIN identity result stays available, so you can still confirm the year, make, model and build details for the vehicle in front of you. The sample center still shows the original, unmodified provider report so you can judge the format before you ever pay.
Come back and reload the review page later: the readiness answer is re-fetched with caching disabled every time the page loads, so a reopened checkout shows up as soon as it is restored. If the button stays disabled and you need to know where you stand on an existing purchase, use the contact page with your order reference.
What this does not cover
- The page does not tell you which readiness signal is closed — the public response reports only whether checkout is ready and in which mode.
- The current policy does not state a restoration time, and we do not publish an estimate.
Sources reviewed
Open the underlying public source and verify that its scope matches the question you are asking.
Frequently asked questions
Was I charged anything while the button was disabled?
No. The disabled button does not call checkout, and the checkout endpoint separately refuses the request with a message stating that no payment was started.
Does this mean my VIN is not supported?
No. An unsupported or sandbox-restricted VIN produces its own separate message about the VIN. This label is about purchasing availability across the site.
Is the free VIN check affected?
No. VIN identity decoding is a separate system from paid report purchasing and keeps running while checkout is closed.
Will refreshing the page fix it?
It will show the current state. The page re-reads the commerce health endpoint with caching disabled on every load, so a reopened checkout appears without clearing anything.