KEY TAKEAWAYS
- Per classified result, from a prepaid BTC/LTC balance.
- Errors and unknown results are never charged.
- Costs are displayed before every run.
- Bulk rates available on request.
- Every checking economics result class should map to a defined workflow action.
- Failed checking economics checks say nothing about the card — fix the cause and retry.
Checking here is prepaid and per-result. No subscriptions are required, no minimum spend per run, and no hidden fees.
How pricing works
- Prepaid balance — fund once with BTC or LTC; every check deducts from the balance.
- Per classified result — you pay the gateway price for each Live or Dead result. Unknown and error outcomes are free.
- Price shown first — every checker displays its cost per Live and Dead card before you start.
- Holds released — the maximum cost is reserved and any unused portion is refunded automatically.
Lowering cost per result
- Deduplicate lists before running them.
- Retry errors only — dead cards are final.
- Use free format tools to filter malformed rows.
- Track cost per classified card, not cost per request.
Bulk rates and subscriptions
High-volume users can request discounted bulk rates or a monthly plan. Contact support with your expected volume and target gateways and we will confirm the terms.
Get started
Create an account, deposit, and open a checker. Costs are visible in your history down to the exact unit.
Card checking is priced per classified result from a prepaid balance, and that structure decides the true economics: errors cost nothing, retries stay rational, and the only number worth optimizing is cost per classified card. A route that is cheaper per request but classifies less often is the expensive option.
Funding is crypto-only and credited automatically; history records the charge and balance for every check, so the math is never a mystery. Cost per classified card equals total spend divided by live-plus-dead results — a number any operator can compute from their own history.
Key points about checking economics
- Per classified result; errors never billed
- Optimize cost per classified card, not per request
- Crypto funding credited automatically
- Per-check cost and balance in history
How checking economics actually works
Error means the check itself failed technically: a timeout, a provider fault or malformed input. No classification was produced, and no charge applies. Nothing in the check moves money: the request asks a question, the issuer answers, and the platform records one of four outcomes against your account. A verification answer reflects the issuer's view at the moment of the request; nothing about it changes the card, the account or the cardholder. Behind the scenes, every check follows the same chain: your input, the gateway format, the provider connection, the issuer response and the classification you see. That single habit separates routine checking economics from expensive checking economics.
Checks are routed through providers rather than card networks directly, so the same card can behave differently on different routes. The platform keeps one history row per request with status, cost and before/after balance, which makes the whole loop auditable at the individual check level. Unknown means no definitive answer was received — often an issuer challenge or soft decline — so the card remains unclassified and deserves at most one fallback pass. That single habit separates routine checking economics from expensive checking economics.
Running checking economics well: the operating steps
Run one primary gateway with a fallback route. When the primary degrades, re-run only the unclassified remainder on the fallback. Watch two numbers over time: the classified rate and the error rate. Together they explain almost every surprise in monthly spend. Validate checksums and expiry dates before any paid request; the free browser tools exist precisely so malformed rows never reach a provider. Size batches to the provider ceiling. Past that line, extra concurrency converts into timeouts rather than throughput. Keep it in mind whenever checking economics results are reviewed.
Interpreting outcomes in checking economics
The honest reading of unknown is "no answer yet". The card is neither good nor bad, and the remedy is a different route, not a repeat of the same one. A live answer is evidence about the account, not a guarantee about a specific future transaction; issuer rules can change between the check and the charge. The four result classes are a decision matrix, not a score: live proceeds, dead recovers, unknown gets one careful retry, error returns to the queue. Errors are free by design: no classification means no charge, so retrying after fixing the cause costs nothing but effort. That single habit separates routine checking economics from expensive checking economics.
Scaling checking economics without surprises
Keep the API key server-side and regenerable; a leaked key is a billing incident as much as a security one. Keep one primary gateway and one fallback, and switch on evidence — error spikes and classified-rate drops — rather than on price alone. Budget verification against the cost of failure, not against zero; the comparison is what makes spend defensible. Alert on classified-rate drops, not just on errors; silent degradation is the expensive kind. The habit costs nothing and removes a recurring class of mistakes.
What checking economics cannot promise
Where a check is used inside a payment flow, it complements authorization rather than replacing it. The platform does not trade card data, and nothing in the system is designed to bypass a cardholder's consent. Verification is at its best when it is boring: a routine status step inside an existing, authorised process. In checking economics work, that is the difference between a signal and a guess.
Paying for checking economics: the honest math
Funding is prepaid in BTC and LTC; deposits credit automatically once confirmed, and checks draw from the balance per classified result. Billing follows the classification: live and dead results are billed at the gateway price, while errors are free. The API returns the balance on every response, so integrations can meter themselves. Top up before long runs; an interrupted run is the most avoidable kind of waste. That distinction is what keeps checking economics decisions clean.
Handling keys and data in checking economics
The dashboard shows the key once and lets you rotate it at will; rotation is cheap, leaks are not. API keys are server-side secrets: they belong in environment configuration, never in URLs, logs or client bundles. Encrypted transport and account-scoped access are defaults; nothing about the integration requires changing them. Log identifiers and outcomes, not card numbers. Debugging almost never requires a PAN. Remember it the next time checking economics produces an ambiguous answer.
What aggregate data says about checking economics
The platform publishes outcome distributions and latency percentiles from real traffic, refreshed monthly, precisely so expectations can be calibrated against reality. Sample sizes matter. Small windows produce noisy percentages, which is why published aggregates carry minimum thresholds. Cost per classified card is the honest metric. A cheap-per-request route with a high failure rate is the most expensive option in practice. Trends beat snapshots: a classified rate that drifts over weeks says more than any single run's result. That single habit separates routine checking economics from expensive checking economics.
Common mistakes around checking economics
Chasing every unknown in checking economics with unlimited retries costs more than classifying the rest of the list. Skipping format validation before checking economics turns simple input mistakes into provider rejects that look like card problems. Storing card data beyond the needs of checking economics creates risk without adding value.
- Assuming every checking economics gateway covers every brand is the fastest way to a list full of errors.
- Treating an error as a dead card in checking economics throws away cards that were never classified, and errors are the cheapest outcomes to recover.
- Skipping format validation before checking economics turns simple input mistakes into provider rejects that look like card problems.
- Running checking economics without a fallback means one degraded provider turns an entire batch into unknowns.
What checking economics cannot promise
Results describe the account, never the person; they should inform routing and risk decisions, not identity decisions. Operators remain responsible for the legal basis on which they hold and process card data. Verification is a signal, not a guarantee: a live result does not promise that a later charge will be approved. Remember it the next time checking economics produces an ambiguous answer.
Validation helpers for checking economics
Every browser tool runs client-side: input never leaves the page, which keeps format validation free and private. The Luhn validator and expiry checker catch format problems before any paid request leaves the browser. BIN search and IIN lookup answer the issuer question — brand, type, bank, country — without touching account status. The habit costs nothing and removes a recurring class of mistakes.