Pay for AI APIs in rupiah with QRIS
Indonesian developers already pay for everything with QRIS: coffee, tickets, even monthly subscriptions. For AI APIs, though, that habit breaks at the payment step: almost every international platform asks for a credit card.
This article explains how the “pay for AI APIs in rupiah” flow works at Giant Router, what is shown before you pay, and what happens to the balance afterwards. If you want to know why this topic matters for anyone blocked by credit cards, read how to pay without a credit card first.
The flow, step by step
1. Sign up. Email + verification. No credit card in the sign-up.
2. Pick a top-up amount. Available presets start at Rp10,000 (trial), Rp25,000, Rp50,000 (the working balance usually recommended), up to Rp100,000. For a try-out, Rp10,000 is already enough for many requests on the cheap models.
3. Check the rate and the credit BEFORE paying. On the payment page, you see two numbers: the rupiah amount you will pay, and the amount of USD credit that will land, computed from the display rate at that moment. This quote is locked to that invoice. No rate changing on you later after you scan the QR.
4. Scan the QRIS. From any bank app or digital wallet you already use. No card data changes hands.
5. Balance lands, create an API key. Every key can be given a budget limit. For a trial, set Rp10,000. That means: whatever your app does, including a buggy loop, usage stops at that limit. The balance cannot go negative.
6. Do the work, read the report. Every request is recorded: model, tokens in and out, cost. This is the report you use to compute cost per task, and if you freelance, it is what you attach for reimbursement (see: billing clients for AI API usage).
What is shown and what is hidden
We don’t like costs that appear later, so here is everything on the payment path:
| Question | Answer |
|---|---|
| What rate is used? | The display rate is shown on the payment page, locked per invoice |
| Any admin fee for you? | None; you pay the preset amount, that’s all |
| What happens if the QR expires? | The order is voided; you create a new one without penalty |
| Can the balance go negative? | No; requests stop at the per-key budget limit |
| Can the balance be withdrawn? | No. Balance is service-use credit; what you can claim is the guarantee below |
The last point matters for honest expectations: Giant Router balance is not savings, it is closed credit. But if a model is removed from the catalog, or your key gets blocked by a provider for something that is not your violation, the remaining balance tied to it is refunded pro-rata. The full rules are in the Balance Guarantee. It is a contract, not a marketing promise.
How much is enough to start?
To feel the flow and produce something real at the same time: Rp10,000. With the flash-class models (the cheapest prices in the catalog), that amount covers many small experiments: drafts, function refactors, simple chatbots. For daily coding work with bigger models, the Rp50,000 preset is the usual comfortable starting point.
You don’t have to trust our estimate. The per-million-token price of every model is openly displayed on the homepage, and the per-request cost report shows your real usage numbers after the first request.
Who this flow fits
- Students and learners with no credit card at all; QRIS solves that, and per-key budget limits make an experiment a Rp10,000 risk, not a balance risk.
- Freelancers and agencies who need one key per client with per-project cost reports; reimbursement becomes an attachment, not an argument.
- Indie builders who already have working code and just need access whose payment doesn’t create drama.
Three myths that make people postpone
“The rate must be a rip-off.” The display rate is shown before you pay and locked per invoice; you see exactly rupiah-to-credit before any money moves. Compare with a credit card: the issuer’s rate only becomes clear after the transaction goes through.
“You have to top up big, or it burns.” You don’t need big: presets start at Rp10,000, and the better question is not “will it burn?”, but “how much do I need this week?”, then top up accordingly. The per-key budget limit makes sure the remaining balance is not quietly drained by one wrong key.
“QRIS is for retail, not for developers.” QRIS actually has two qualities that fit infrastructure: the network is national (payable from any bank or wallet you already use), and amounts can be small with no big minimum.
A one-working-day flow example
- Morning: top up Rp25,000, create a working key with a Rp20,000 limit.
- Midday: work through a few tasks in the editor with an economical model; the usage report shows every request with its cost.
- Afternoon: one heavy design decision comes up, run it on a big model; the request’s cost is visible in the report, not an end-of-month surprise.
- Evening: check the report; the remaining balance is visible, per-task usage can be recomputed.
A flow like this is what makes “pay in rupiah” not just about the payment method, but about you understanding what you bought, that same day.