How Email Verifier Credits Work

Email Verifier uses credits. The dashboard shows both the plan allowance and any credits you have purchased, so you can see the exact cost before a job begins.

What a verification costs

In a Deep job, addresses at providers that do not offer useful mailbox-level evidence are charged at 1 credit. The dashboard and API estimate calculate this from the addresses in your list. Use the displayed total rather than multiplying a list size by two.

Monthly allowance

Monthly credits do not roll over. The verifier shows your current balance and reset date. If you need more before then, buy a credit pack.

Credit packs

Prices displayed at checkout follow your account's billing currency where it is available. Purchased credits do not expire.

To buy a pack, open Email Verifier, select Buy Credits, choose the amount and complete the checkout shown in the dashboard.

Pack-selection examples

These examples are planning tools, not quoted checkout totals. The price preview before you start the job is the figure that matters for the addresses actually submitted.

Actions that do and do not use credits

This distinction is useful when a source file needs cleaning. You can prepare, inspect and correct the list before starting a job. Credits are for the verification work, not for finding which column contains the addresses.

Which balance is used first

On the standard TrekMail host, a verification spends the monthly allowance first and purchased credits second. This lets you use the included allowance before drawing down a pack.

On a White Label host, verification uses the purchased balance. The mail-plan allowance belongs to the agency's TrekMail account and is not exposed inside its branded product.

Why the balance can look different

On the regular TrekMail host, the credit panel separates monthly and purchased amounts. A monthly allowance is linked to the mail plan and resets on its displayed schedule. A purchased pack is a separate balance. On a White Label host, users see the balance they can actually spend there, which is the purchased balance.

If an integration reads credits through the API, use total_available as the number to compare with a new job estimate. On the regular host, the API also returns the monthly and purchased parts. Do not add a balance from one host to a request sent to another host.

Changes to a mail plan

The monthly allowance follows the account's effective mail plan. The credit panel is the place to check the amount and its upcoming reset after a plan change. Purchased credits remain a separate balance, so an allowance change does not erase a pack that was already bought.

Before a bulk job starts

The verifier extracts addresses, removes duplicates and shows an estimate before you select Start Verification. Check:

• the number of unique addresses;
• the selected mode;
• the actual credit cost;
• whether the balance covers the whole job.

Credits are deducted when the job starts. If the balance cannot cover the list, the job does not start, so you do not get a partly funded verification.

If you submit the same normalized list in the same mode within 24 hours, TrekMail returns the existing job rather than spending credits again.

What happens when a source contains duplicates

Duplicates within one list are normalized before the price is calculated, so the same address is not charged twice in that job. This is not a reason to ignore duplicate contacts in the source system. Keep one canonical contact record where possible, otherwise campaign reporting and opt-out handling can become inconsistent even when the verification cost is correct.

When a list is submitted again during the duplicate-protection window, treat the returned existing job as the source of truth. It may still be processing, or it may already have a result ready to review. This is safer than issuing fresh submissions until an uncertain browser or network response appears to succeed.

Cancellation and results

You can cancel a pending or processing job. Processed rows remain available, and credits for unprocessed work are refunded. Jobs and their results are retained for 15 days, so download the export you need before that period ends.

If a job is already complete, cancelling it cannot create a refund because there is no unprocessed work. If a submission fails before a job can be staged, TrekMail handles the charge as a failed start rather than leaving you with a paid job that does not exist. If something looks wrong, check the job history before submitting another copy.

Retention reminder

The 15-day result window is separate from the credit balance. A credit can be spent correctly even after the detailed result has reached the end of its retention period. Download the CSV or text export needed for audit and campaign work while it is available, and protect that exported contact data according to your own privacy process.

Keep accounting simple

Use the job name to make a later review easy. Names such as September newsletter import or Partner A sample are more useful than a generic date. Save the export and the job ID with the campaign record. This gives a reviewer the source, estimated cost, actual credit charge and resulting segment without needing to reconstruct the decision from an inbox.

Keep an eye on the balance

The verifier warns when the available balance is low. Check the estimate before a large list, especially when using Deep mode. For automated workflows, use GET /api/v1/verify/credits to read the current balance before submitting a job.

Do not run several large submissions at once based on an old balance check. Read the balance again before each admission, use a distinct idempotency key for each API bulk request and log the returned credits_charged value. This reduces surprises when more than one integration shares an account.

If a balance or purchase looks wrong

Refresh the verifier and check that you are on the intended TrekMail or White Label host. Then check the job history for a job that may already have been created. If you need support, provide the job ID, job name and the visible error or purchase reference. Never provide an API token, full card number, mailbox password or a complete contact export.

See Email Verifier Pricing and Credit Packs for planning examples.