Verification Checklist
- ✓Before buying a prepaid credit pack, did you explicitly ask the vendor whether unused credits are refundable, and get a clear answer in writing or in the contract
- ✓Did you explicitly ask whether unused credits can be transferred to another affiliated entity or sub-account, rather than assuming it is possible by default
- ✓Does the procurement contract or service agreement spell out refund conditions in writing - handling fees, deadlines to file a claim, whether already-invoiced amounts are excluded
- ✓If your company has multiple affiliated accounts or subsidiary entities, did you confirm before purchase whether matching real-name/KYC identity across those accounts is required for a transfer
- ✓Is the credit pack's validity period, and whether it can be renewed or migrated, also spelled out in the contract rather than something you only ask support about near expiry
1. Prepaid credit packs and pay-as-you-go are fundamentally different
Pay-as-you-go billing means you're charged for exactly what you consume, and the account balance is essentially just a running ledger you can stop adding to at any time. A prepaid credit pack works differently: the enterprise makes a one-time top-up or buys a bundle of tokens or calls upfront, usually at a lower unit price than pay-as-you-go. This "buy the usage right upfront" model means the vendor has already recognized that revenue the moment you pay - what you're holding is a prepaid entitlement to use the service, not a balance you can unconditionally cancel and get back. Because of this fundamental difference, whether unused credits can be converted back into cash or handed off to another account is entirely a matter of the vendor's own business policy, not something that follows automatically the way "just stop using it, no further obligation" does under pay-as-you-go. Without understanding this distinction, it's easy to assume "it's my money, so I should be able to get a refund or transfer it whenever I want" - but neither is a given once you've prepaid.
2. Question one: is a refund even possible - there's no industry-wide answer
Vendors differ widely on whether prepaid credits or account balances can be refunded, and each sets its own rule in its own service agreement - there's no cross-vendor convention to fall back on. As one example, DeepSeek's published open-platform terms of service state that users can file a refund request through the platform's billing and "refund management" page, and for requests that meet the refund criteria, the platform will return the remaining unconsumed top-up amount after deducting necessary handling costs - but amounts already consumed, or amounts for which an invoice has already been issued, are not refundable. That tells you at least one vendor has a defined process with real limits, but exactly how much gets deducted as "necessary cost," whether every top-up channel qualifies, and whether enterprise wire-transfer top-ups face extra restrictions all depend on whatever rules are posted at the time. A different vendor could set entirely different terms - some might allow unconditional refunds on unused credits, others might state upfront that credit packs are non-refundable once purchased. That's the reality behind "no unified answer": the only reliable move is to ask the vendor's sales or support team this exact question before purchase, and keep a written confirmation or screenshot rather than guessing based on how another vendor handles it.
3. Question two: transferring to an affiliated account - support varies by vendor
The second common question: companies often run more than one LLM API account - a parent-company primary account, subsidiary accounts, or separate accounts registered by different business units - and if one account's credit pack goes unused, can the remainder be moved to another affiliated account. Whether that capability exists at all depends entirely on how the specific vendor designed its product; not every vendor offers this kind of cross-account resource transfer. One useful reference point is Alibaba Cloud's "resource transfer" feature for infrastructure products like Elastic Compute Service: the official documentation states plainly that transfers are only supported for specific product types (such as ECS instances and pay-as-you-go Elastic IP), and both the sending and receiving accounts must complete real-name verification, with enterprise accounts generally only able to transfer to another account under the same verified business entity. Even within one cloud vendor, cross-account transfer is enabled product by product - it is never a blanket capability that automatically applies to everything that vendor sells. Applied to LLM API credit packs specifically, whether cross-account transfer is supported at all, and whether transferring to an affiliated corporate account requires extra documentation or dual account-manager approval, has to be confirmed directly with that API vendor rather than assumed from how a different product line behaves.
4. Why these two questions must be settled before purchase, not after
Many enterprises buying a prepaid credit pack focus their attention on the discount and how fast the top-up lands, and rarely push for a clear written answer on "what happens if we don't use it all" before signing. By the time a mis-sized budget, a cancelled project, or a pivot in business direction leaves a large chunk of credits sitting idle, the negotiating position has completely changed. Before purchase, you're a prospective customer, and the vendor has an incentive to make concessions or give clear commitments on refund and transfer terms in order to close the deal. After purchase, the money has landed and the revenue is already recognized - the vendor has no equivalent incentive to make an exception for a deal that's already closed, and whether a refund or transfer happens tends to follow the signed agreement strictly, with far less room to negotiate. In other words, this isn't just a matter of whether the contract language happens to be clear - the bargaining leverage on both sides genuinely shifts before versus after purchase. Asking these two questions before buying costs you almost nothing extra; trying to win the same concessions afterward can cost real time and effort, or simply fail.
5. Bottom line: treat both questions as mandatory items on your procurement checklist
Before buying a prepaid credit pack for a domestic LLM API, put "can unused credits be refunded" and "can unused credits be transferred to an affiliated account" on the same must-answer checklist as price and discount comparisons - ideally with written confirmation before you sign. The answers vary by vendor with no universal rule to lean on, and one vendor's policy should never be assumed to apply to another. What is certain is that asking these two questions before purchase is always cheaper than trying to negotiate them after the credit pack has already been bought.