· 9 min read · Pricing
Prepaid credits that expire: Designing fair expiry messaging
Prepaid credits that expire: designing fair expiry messaging – show dates, FIFO spend, found-only rules, and no dark-pattern countdown traps.
Prepaid credit packs that expire are honest only when messaging is fair: clear dates, no dark-pattern countdowns that hide found-only rules, and spend that matches found-only billing. Buyers should know when credits end – and that empty completed finds never needed those credits in the first place.
Invenitor is a people search and lookup API, not a sales cloud. Coverage varies; we do not publish hit-rate percentages. Seat contrast: Seat Subscriptions vs Pay-Per-Lookup Credits. Hidden free-plan traps: The Hidden Cost of Free-Plan Enrichment Tools. Pillar: Credits, Empty Results, and Timeouts.
What fair expiry messaging includes
| Element | Fair | Unfair |
|---|---|---|
| Expiry date | Visible at purchase and in account | Hidden until day 29 |
| Found-only billing | Stated next to pack tiles | Buried after checkout |
| FIFO | Oldest pack spends first (when offered) | Ambiguous multi-pack burn |
| Empties | Empty completed finds free | Implied every call burns |
Live tiles: /pricing. Pack sizing: 25 to 1,000 Credits. INR rail: INR Credit Packs, Razorpay, UPI, Cards, Wallets. Primer: What Are API Credits. Definition: What Is Pay-Per-Lookup Pricing?.
Designing the copy (product + content)
- State pack size, price, and expiry window in one glance.
- Restate found-only billing verbatim near the buy button.
- Explain that timeouts/errors do not spend – so expiry anxiety should not push invent-on-empty behavior.
- Offer a path to top up before expiry without shame UX.
- Link docs so builders can reconcile ledgers – /docs.
Honesty: Empty Means Not Found. Marketing language: When We Have Them. Trust: Trust Checklist.
Desk behavior when credits near expiry
Agents and expiry
Agent pipelines should read remaining credits and expiry from the same account truth as humans – /mcp.md, Do not let a copilot invent contacts because a pack is ending.
Commercial path
Sample five free lookups. Choose 25–1,000 from found history. Note the expiry date in the runbook with the API key – Rate Limits and Keys. Onboarding without dark patterns: From free credits to First Paid Pack.
What should you do next?
Open /pricing. Read found-only billing and the expiry line together. Run five free finds via /docs. Buy a pack sized to real found outcomes – not to fear of expiry.
Procurement one-liner
We buy prepaid lookup credits with visible expiry and found-only rules – empty completed finds are free; timeouts and errors do not spend.
Expiry runbook snippet
Message template for account UI
Your pack expires on DATE. Credits follow found-only rules. Empty completed finds are free. Top up when your next sprint needs more found outcomes.
Questions
When does a credit spend?
1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend.
Why do prepaid credits expire?
Packs are time-bounded commercial units. Fair vendors show the date clearly and keep found-only billing intact.
Should I burn credits on empties before expiry?
No. Empty completed finds are free – inventing fills to "use" credits is worse.
What is fair expiry messaging?
Visible dates, found-only billing next to tiles, clear FIFO if multiple packs, no hidden countdown traps.
How do desks plan around 30-day windows?
Size packs from found history for the sprint; top up intentionally; keep expiry on the key runbook.
Do agents need expiry awareness?
Yes – copilots should respect remaining credits and never invent contacts because a pack is ending.
Where do we verify pricing?
/pricing, INR credit packs, 25 to 1,000 credits guide, and the credits pillar post.
