Desk Note: Tracing Top-Ups, Invoices and Refunds
Start with the payment, the document and the balance
A billing question often starts with three things that look related but mean different things: money leaving your bank account, an invoice appearing in a dashboard, and credit appearing in an API account. Keeping those separate makes everyday billing much easier to follow.
An invoice documents a billed transaction. A prepaid balance is credit available for eligible future usage. A refund returns money under the provider’s applicable terms. One does not automatically establish the status of the others: an invoice is not proof that a refund is available, and an unused balance is not necessarily withdrawable cash.
A top-up pays ahead of future API usage
With prepaid billing, you add funds before making requests. Eligible usage then reduces your available balance. Pay-as-you-go describes charging based on consumption; prepaid describes when you fund that consumption. A service can use both arrangements together.
For a simplified example, suppose you add $50 and later incur $8 in usage charges. Your remaining balance would be $42, assuming no taxes, fees, promotional adjustments or other deductions. These numbers illustrate the accounting, not Relay365 pricing or payment terms.
The amount charged for a request can depend on the model, input and output volume, and other billable features. Requests using Claude Haiku 4.5 and Gemini 2.5 Flash, for example, should be checked against their respective current rates rather than treated as interchangeable billing units.
Match each invoice to the transaction it records
Before sending a document to accounting, check whether it covers a top-up, a usage period or another charge. Providers can issue billing documents differently, so do not assume a top-up invoice and a usage statement represent two separate payments.
- Check that the customer name, billing address and any required tax details are correct.
- Match the document’s transaction reference, date, currency and amount to your payment record.
- Confirm whether taxes or fees are included in the total or shown separately.
- Keep usage records alongside payment documents so you can explain both the funding and the consumption.
A payment receipt generally confirms payment, while a usage statement explains consumption. Local accounting and tax requirements determine which documents your business needs; a dashboard balance alone may not be enough.
Separate a refund request from a credit adjustment
A refund usually sends money back through an approved payment route. An account credit instead increases the balance available inside the service. Both can resolve billing issues, but they have different effects on your cash and future spending.
Unused credit does not, by itself, establish refund eligibility. Before adding funds, check the provider’s current rules for unused balances, consumed usage, promotional credits, request deadlines and any applicable deductions. If the terms are unclear, ask support before making a large top-up.
When requesting a correction, provide the transaction reference, payment date, amount and a short explanation. For a disputed usage charge, include relevant request identifiers and timestamps without exposing API keys or sensitive prompt content. Ask whether the proposed resolution is a cash refund or an account adjustment, and request confirmation of any expected processing window.
Keep purchased credit separate from referral rewards
Relay365 members can also earn a referral bounty when people they invite pay. Treat that as a separate category from purchased API credit unless the applicable terms explicitly connect them. Check the reward’s eligibility, availability and payout rules rather than assuming it can fund requests or be refunded like a top-up.
Leave the next shift a clear billing trail
Relay365 is worth considering if you want a pay-as-you-go relay desk for multiple model families. For a new user, a modest initial top-up and a few controlled requests can make the billing workflow easier to understand before committing more funds. Confirm the current rates, invoice options and refund terms first.
If that arrangement fits your workflow, create a Relay365 account and review the billing details before funding it. Keep payment confirmations, invoices, usage records and support decisions together. The goal is simple: another person should be able to see what was paid, what was consumed, what remains and whether any refund is still pending.
Further desk bulletins
| Date | Bulletin title | Filed under | Language |
|---|---|---|---|
| 2026-10-27 | Shift Note: Long System Prompts Keep Adding Input Cost | Spend watch | EN |
| 2026-10-27 | Shift Note: Count the Full Payload Before Sending | Spend watch | EN |
| 2026-10-27 | Shift note: prototype trial on a small top-up | Spend watch | EN |
| 2026-10-27 | Shift note: AI spend assigned to each pull request | Spend watch | EN |
| 2026-10-27 | Shift Note: Bulk Queue First, Hard Cases Escalated | Spend watch | EN |
| 2026-10-27 | Shift Note: Stop Agent Loops Before the Bill Climbs | Spend watch | EN |
Curious how it runs on your own code? Sign up →