Midjourney API Top-Up: Balance, Invoices, and Risks (2026)

People who want to top up a "Midjourney API" usually get stuck at the first step: there is no official top-up entry point. The reason is that Midjourney currently offers no general API open to the public; its product is still subscription-based, with generation entry points in Discord and on the web.

So this kind of top-up almost always happens on third-party platforms: you pay a vendor and receive callable interface quota and balance in return. This article explains the models, process, invoicing, and risks of such top-ups, so you can ask the right questions before paying. Specific prices and service terms are subject to the vendor contract and the in-site model pricing page.

Note: Midjourney is a trademark of its owner. This article is for technical discussion only and has no affiliation with Midjourney. Third-party platforms are responsible for their own qualifications, billing, and invoicing policies; verify them before paying.

1. First, See Clearly: Who Are You Paying?

For an official subscription, the payee is Midjourney, and you buy monthly or annual generation quota used through Discord or the web. For a third-party top-up, the payee is the vendor, and you buy a balance or credits in the platform account, which you then use through its HTTP interface.

These are not the same account system: a third-party platform balance cannot be used officially, and an official subscription does not turn directly into API call quota. Before paying, confirm that the payee, domain, and contract counterparty match, and avoid transferring money to a personal account.

2. Three Common Top-Up Models

Model	What you buy	Billing method	Suitable for	Main risks
Prepaid balance	Platform account balance, deducted per call	Per image, per task, or per credit	Volatile usage; pay as you go	Balance expiry, limited refunds
Credit package	A fixed number of generations	Package price divided by count	Stable, predictable usage	Bonus credits restricted by model and time
Bring your own account (BYOA)	The vendor's automation layer; the account is yours	Platform fee plus official subscription	You already have a subscription and want programmatic calls	Account restrictions, terms risk
Monthly seat	A fixed monthly call quota	Monthly payment; add-ons or throttling after quota	Long-term stable use	Costs rise after quota

"Top up X and get Y free" looks like a bargain, but bonus amounts are often non-refundable, expire, or work only on lower-priority channels. To judge the value, fold bonus credits into usable quota rather than looking at face value.

3. Six Confirmations Before Topping Up

Payee: whether the company name, domain, contract counterparty, and invoice seller are consistent.
Currency and exchange rate: which point in time the conversion uses, whether payment-channel fees are included, and which rate applies to refunds.
Arrival time: whether crediting is instant or requires manual review, and how failed payments are returned.
Minimum top-up: the minimum amount and whether there are first-purchase restrictions.
Balance validity: whether it expires, and whether extension or refund is possible after expiry.
Refund rules: how unused balance, bonus balance, and consumed amounts are handled separately.

4. The Top-Up Process

Register with the vendor, verify its business license or entity information, and confirm that the receiving account matches the contract.
Top up a small amount first, enough for 20–50 real tasks; do not prepay a large sum at once.
Test with real prompts: success rate, charges for failures, result-link lifetime, and concurrency limits.
Confirm in writing with support: invoice type, issuance time, invoice category, and whether corporate bank transfer is supported.
Save order numbers, payment receipts, chat records, and quotes, and file them in your procurement ledger.
After testing passes, top up according to the monthly budget, and set key quotas and balance alerts in the dashboard.
Reconcile weekly: record top-ups, actual consumption, failure charges, refunds, and bonus balances separately.

5. Exchange Rates, Fees, and Bonus Balances

The friction of cross-border settlement is often underestimated. On platforms priced in foreign currency but paid in RMB, the actual credited amount is reduced by the exchange spread and payment-channel fees; a refund converts the currency again and may lose another spread. Use this framework when calculating real cost:

Usable quota = payment amount ÷ settlement rate − payment-channel fee
Cost per image = usable quota ÷ images generated × (1 + failure rate)

"Images generated" must be based on successful tasks and actually usable images, not theoretical counts; the "failure rate" includes moderation rejections, timeouts, and retries. If bonus credits are restricted by model or time window, list them separately instead of merging them into freely usable balance.

Also watch the price-change clause. The underlying cost of third-party interfaces depends on official subscriptions and account supply, so a vendor may adjust deduction multipliers at any time. The contract should ideally state whether price changes are announced in advance and whether purchased balances are affected.

6. Invoicing and Corporate Procurement

Corporate buyers usually care about four things: whether an invoice can be issued, what type, when, and by whom.

Invoice type: a standard VAT invoice or a special VAT invoice, depending on the vendor's qualifications and your taxpayer status.
Invoice category: commonly technical service fees, information service fees, or software service fees, and it must match the actual service.
Issuance timing: per order, monthly summary, or after consumption is complete; confirm in advance.
Three-way consistency: the contract, payment, and invoice counterparties should match to avoid difficulties explaining the transaction in a later audit.

Individual top-ups often receive only standard invoices, or none at all. If a company needs a special VAT invoice, it should use the corporate process before paying, sign a service contract, and write invoicing obligations and liability for breach into the contract. Do not ask whether an invoice is possible only after paying, and do not accept an invoice category that does not match the actual service.

7. Refunds and Balance Risk

A balance on a third-party platform is essentially a prepayment, not a deposit. If the vendor stops operating, the interface goes down, or the account pool is restricted, the balance may become unusable. Common refund rules are: unused balance may be refunded with a fee, bonus balance is non-refundable, consumed amounts are non-refundable, and amounts beyond a certain period are non-refundable.

The way to control risk is not to find a platform that promises balances never expire, but to control exposure: top up small amounts frequently, do not hold more than one month of usage in balance, keep contracts and payment records, and prefer vendors that offer corporate accounts and formal contracts.

Also mind the compliance boundary. Midjourney's terms of service restrict automated access and third-party applications used without permission, and wrapper models may sit in a gray area. Before using one for commercial delivery, have procurement or legal confirm the terms risk; do not equate "it can be called" with "it can be used commercially in compliance."

8. Vendor Due Diligence and Procurement Red Flags

Pause payment and investigate further if any of the following appears:

The vendor asks for your Midjourney account password or email verification code.
The vendor accepts only personal transfers and refuses to sign a contract or provide entity information.
The vendor claims balances never expire, calls are unlimited, and there are no restrictions at all.
The vendor cannot explain the billing basis and is vague about whether failures and retries are charged.
The quote is clearly below the cost implied by an official subscription, with no explanation of the source.
The invoice seller, payee, and contract counterparty do not match.
There is no service status page, no alerting, and no written refund clause.

During due diligence, ask directly for three things: a written quote and billing explanation, a service contract template, and a recent sample invoice. Vendors willing to provide them with consistent information usually carry lower risk.

9. FAQ

Does Midjourney officially support topping up API balance?

As of October 2026, there is no general API open to the public and no developer balance system; generation remains subscription-based. So-called "API top-ups" are mostly third-party platform activity.

Does the balance expire after top-up?

It depends on the platform terms. Some reset at the end of each calendar month, some extend from the last consumption, and some remain valid long-term but restrict refunds. Before topping up, ask for the validity period and expiry handling in writing.

Can I get a special VAT invoice?

It depends on the vendor's taxpayer qualifications and your purchasing entity. Before paying, confirm the invoice type, category, tax rate, and issuance timing, and ensure the contract, payment, and invoice counterparties match.

Can I get a refund after topping up?

Most platforms offer conditional refunds only for unused balance; bonus balance and consumed amounts are usually non-refundable. Cross-border payments may also incur exchange losses, and refunds can take a long time to arrive.

Why do some platforms ask for my account password?

The BYOA model needs to drive your own subscription account, so it requests login credentials. This approach carries higher account-security and terms risk; prefer the vendor's own account-pool model, or switch to an official subscription with manual workflows.

Next Steps

For teams that need to manage multiple model calls and bills in one place, start by opening an account from the registration page, test with a small amount, and then scale up; supported models and billing methods are listed on the model pricing page. When a Midjourney channel is involved, confirm the vendor's qualifications, billing basis, and invoicing capability before deciding whether to prepay.