Skip to content

Independent marketplace for verified cloud accounts

How to Verify Cloud Credits Before and After a Transfer

Credit balances are provider-controlled, time-limited and service-restricted. This guide shows where each billing console displays them and how to verify a balance yourself.

Credits are the most misunderstood line in any account listing. They look like money, they are quoted like money, and they behave almost nothing like money. A credit is an entry in a provider’s billing system that reduces certain charges under certain conditions until a certain date, and every one of those words carries weight.

This guide is about verification rather than strategy. If you want to know what credits can be spent on in general, read what cloud credits cover. What follows is the narrower question of how you confirm, with your own eyes and inside the provider’s console, that a stated balance is real, usable and still there after the account reaches you.

What a credit balance actually is

Providers issue credits for several reasons: startup programmes, partner schemes, promotional signups, service disruption goodwill, and sales negotiations. Each origin brings its own rules. A promotional credit attached to a signup often has the tightest restrictions. A negotiated credit on a commercial agreement may be broad but tied to the contracting entity rather than the account.

In every case the provider retains control. Credits can expire, can be limited to named services, can exclude certain regions, and can be voided if the terms under which they were granted are not met. They are also not transferable in the ordinary sense: they live where they were issued. Any account you look at should be valued on what it can do, with the credit treated as a bonus that may not survive.

Find the right page in each console

Every provider puts this somewhere different, and the summary figure on the billing landing page is often not the one you want. Look for a dedicated credits, promotions, vouchers or billing adjustments view rather than the headline balance. That page is where expiry dates and applicability notes live.

On the large platforms the credit view sits inside the billing or cost management section, usually one level down from the main dashboard. On smaller providers it may be a simple account balance figure with a transaction log. If you are evaluating an account on Amazon Web Services, Microsoft Azure or Oracle Cloud, open that page yourself during the handover rather than accepting a figure quoted to you.

Read the expiry, not the headline number

A balance without a date is not information. Credits commonly expire on a fixed calendar date, and some expire in tranches, so a single balance can hide several expiry points. Note each tranche and its date. Then ask whether your planned workload can realistically consume that tranche before it lapses.

Burn rate is the part people skip. A balance that would take two years to spend and expires in three months is worth a fraction of its face value. Work out your expected monthly spend first, using a simple model like the one in building a cloud budget, then compare it to the expiry schedule. If the numbers do not meet, the credit is mostly decoration.

Check which services the credit applies to

Service restrictions are where most of the value quietly disappears. Credits frequently exclude third party marketplace purchases, support plans, reserved or committed capacity, domain registrations, and sometimes specific premium services. Some are restricted to a single product family. Some apply only in particular regions.

The restriction text is usually on the same console page as the balance, in small print next to each credit entry. Read it line by line and map it against what you intend to run. If your plan is GPU heavy, check that accelerated compute is not on the exclusion list, since that is a common carve out and it matters a great deal for anyone following running AI workloads on cloud credits.

What to confirm before any money changes hands

Before a purchase, you want evidence rather than assertion. A live screen share where the seller navigates to the credit page in the provider’s console, with the account identifier visible, tells you more than any screenshot. Screenshots are easy to stage and easy to date wrongly.

Ask four questions and write down the answers. What is the balance, by tranche? What is the expiry of each tranche? Which services or purchase types are excluded? Was the credit granted under a programme with ongoing conditions, such as a startup scheme that requires continued eligibility? If the seller cannot answer the fourth question, assume the credit is conditional.

Be sceptical of round numbers quoted without a console view behind them. Billing systems rarely produce tidy figures once partial months and taxes are involved, so a suspiciously neat balance is worth a second look. It is also fair to ask for the invoice history alongside the credit page, because invoices show whether the credit has been offsetting real charges or has simply been sitting untouched since it was issued.

The verification pass after transfer

Once the account is yours, repeat the whole check from your own session. This is not distrust, it is basic practice: balances change, credits are sometimes consumed between agreement and handover, and a programme credit can be revoked when account details change.

Run a deliberate small test. Launch a modest resource, let it bill for a day, and look at the invoice detail to confirm that the credit is actually offsetting the charge rather than sitting unused. Billing views update on a delay, often a day or more, so give it time before concluding anything. Do this during the same window you work through the post handover security checklist, since both need console access anyway.

Currency, tax and invoicing details

Credits are denominated in a currency and applied against invoices issued in that currency. If your billing profile is in a different currency from the one the credit was issued in, the effective value can shift. Changing the billing country or currency on an account is sometimes irreversible and can invalidate an existing credit, so check the provider’s rules before you touch those fields.

Tax is the other wrinkle. In many jurisdictions credits offset the net charge and tax is still assessed on the gross, which means a fully credited month can still produce a payable invoice. Nothing is wrong when this happens, but it surprises people who expected a zero bill. Keep a valid payment method on file so a small tax line does not suspend the account.

Invoice formatting matters if you need to claim the spend back. Some providers show the credit as a discount line on the invoice, others issue a separate adjustment document, and a few only reflect it in the cost console without ever printing it on the invoice itself. Find out which pattern applies before your accountant asks, because reconstructing it later from console screenshots is tedious and rarely convincing.

When a balance disappears

Occasionally a credit vanishes after a transfer. The usual causes are expiry that nobody noticed, a programme condition that lapsed when account details changed, or a credit that was tied to a billing account rather than the project you now hold. Open a support case with the provider, state the facts plainly, and accept that the outcome is the provider’s to decide.

The defensive position is to never let credits drive the purchase decision. Choose the account for the platform, the region availability and the price of what you will actually run. Compare on those terms, for example AWS against Oracle Cloud, and treat any surviving credit as a discount on a decision you would have made regardless.

A short verification routine

Keep it simple and repeatable. Open the credits page in the provider’s console with the account identifier visible. Record each tranche, its value and its expiry. Read the exclusion text for each. Compare the total usable amount against your projected spend before the earliest expiry. After transfer, repeat all of it and run a small live charge to confirm the offset.

That routine takes under an hour and it converts a marketing number into a figure you can plan with. If the result is lower than advertised, that is still a win, because you found out before you built anything on the assumption.

Keep the record. A dated note of each tranche, its expiry and its exclusions is the thing you will want in three months when the balance looks wrong. It also lets you set a reminder a few weeks before the earliest expiry, which is the only reliable way to avoid watching a balance lapse unused. Credits reward planning and punish optimism, and the difference between the two is usually nothing more than a calendar entry.

Related comparisons

AWS vs Vultr
vs

AWS vs Vultr

Some teams need many small locations and fast access to bare metal or GPU capacity more than they need a…

AWS vs Oracle Cloud
vs

AWS vs Oracle Cloud

Oracle Cloud is a database company's cloud, with a distinctive bandwidth and bare metal posture. This comparison weighs that identity…

AWS vs IBM Cloud
vs

AWS vs IBM Cloud

IBM Cloud is built around OpenShift, regulated industries and hardware you cannot rent elsewhere. This comparison sets that platform thesis…

AWS vs OVH
vs

AWS vs OVH

When jurisdiction is the requirement rather than the preference, OVHcloud and AWS answer it differently. This comparison starts from data…

Accounts discussed in this guide

Buy AWS Account
Buy AWS Account
Amazon Web Services

Buy AWS Account

Amazon Web Services has become synonymous with cloud computing itself, and for millions of developers and businesses around the world, an AWS account is…

From$25 14 options

Keep reading

CI/CD Pipelines That Deploy to Cloud Infrastructure Safely
CI/CD Pipelines That Deploy to Cloud Infrastructure Safely
DevOps and Deployment 7 min read

CI/CD Pipelines That Deploy to Cloud Infrastructure Safely

A practical look at how to structure a deployment pipeline that touches real cloud infrastructure, with particular attention to how the pipeline…

Root Email, MFA and API Keys: Securing an Inherited Account
Security and IAM 7 min read

Root Email, MFA and API Keys: Securing an Inherited Account

Credential hygiene for an account someone else created. Covers the root mailbox, replacing authentication factors, closing recovery paths and rotating keys without…

IAM Fundamentals: Users, Roles and Least Privilege
IAM Fundamentals: Users, Roles and Least Privilege
Security and IAM 7 min read

IAM Fundamentals: Users, Roles and Least Privilege

Identity and access management decides who can do what in your cloud account. This guide covers users versus roles, how permission decisions…

Need the account, not just the theory?

Browse documented configurations across every provider in the catalog, or ask us which one fits your workload.

Telegram