Paying for OpenRouter: Fees, Declined Cards, 402/429 Fixes (2026)

Most developers don't pick OpenRouter for the price. The model rates are passed through from the providers, so calling Claude or Gemini through OpenRouter costs roughly what it costs calling the provider directly. The reason to use it is simpler: one balance, 400+ models, no separate account at every lab, and automatic fallback when a provider rate-limits you. If you build against multiple models, that convenience compounds fast.

Where people get stuck is the money side. Card declines at top-up, cryptic 402 errors mid-task, confusion about whether the crypto route is worth it. This guide walks through OpenRouter's entire payment system as it stands in October 2026: the fee structure, how to troubleshoot a declined card, what 402 and 429 actually mean, and where virtual cards fit. Everything factual here was verified against OpenRouter's official docs and blog on October 10, 2026.

Credits, not subscriptions

First, a correction to a common assumption: OpenRouter has no monthly plan. The structure is a free tier plus pay-as-you-go. You can use free models without adding a card at all, and once you buy credits, every request deducts from your balance by the token. There's no recurring charge, no billing cycle, nothing to cancel.

Inference pricing carries no markup. OpenRouter passes through provider rates and makes money on the credit purchase fee instead. That's a different business model from the typical "API reseller" that quietly inflates per-token prices while advertising free top-ups. With OpenRouter, the fee is visible, upfront, and avoidable only by going direct to each provider.

The top-up entry point is Settings → Credits. One number matters more than most people realize: after your first $10 credit purchase, the daily limit on free models jumps from 50 requests to 1,000. If you lean on free models for batch testing, that $10 is really buying you a quota upgrade, not just balance.

The fee structure: 5.5% by card, 5% by USDC

OpenRouter simplified its fee schedule in June 2025 (the official blog post "Simplifying Our Platform Fee" killed the old $0.35 fixed component). What stands today:

• Cards via Stripe: 5.5% of the order, $0.80 minimum. A $10 top-up pays $0.80 in fees. A $100 top-up pays $5.50.
• USDC via Coinbase: flat 5%, no minimum.
• Alipay: processed through the same Stripe rail, so it's priced in the 5.5% tier.

Do the math on small amounts and the crypto route usually wins: on a $10 top-up you'd pay $0.80 by card (8%) versus $0.50 by USDC (5%). But the two rails have opposite refund policies, which we'll get to in the risks section, and that difference can easily outweigh half a percent.

PayPal is not an option. The official FAQ says it's "coming soon," and it has said that for a while. Any tutorial claiming PayPal works for OpenRouter credits is out of date or selling something.

When your card gets declined

Card payments run through Stripe, and Stripe's own newsroom has documented that OpenRouter uses Radar for Fraud Teams for risk scoring, alongside local payment methods like Alipay, WeChat Pay, Amazon Pay, Cash App, and Google Pay. The practical consequence: when a charge fails, it's usually Stripe's risk model saying no, not OpenRouter. That changes how you troubleshoot.

Work through this order:

1. Check whether you were actually charged. The FAQ has a dedicated entry for this: Stripe integration occasionally delays credit delivery by up to an hour. If your balance is still empty after an hour, you have no Stripe receipt email, and no charge on the card, the payment failed. Try a different card. If you were charged, forward the receipt to support.
2. Check issuer-side settings. International and online transaction toggles, per-charge limits. These charges are in USD; plenty of banks disable cross-border card payments by default.
3. Match the billing address exactly. Stripe runs AVS checks. A single transposed postal code can trigger a decline. Paste the address from your issuer records rather than typing it.
4. Stop after repeated failures. Three declines in a row gets the payment method temporarily locked. Retrying the same card makes it worse. Switch cards or wait 24 hours.

One trap worth spelling out: Stripe treats rapid repeated attempts on the same card as a fraud signal in itself. The instinctive "try again immediately" is exactly the behavior that converts a soft decline into a locked profile.

Where virtual cards actually stand

OpenRouter is a top-up scenario, not a subscription scenario, and that distinction defines how virtual cards behave here:

• Manual top-ups, no auto-renewal. There's no monthly charge that could surprise-fail when the issuer's BIN policy changes. A successful top-up locks in; what happens to the card afterward doesn't touch your balance.
• Prepaid virtual cards fit naturally. Small controlled loads, no recurring billing for a fraud engine to worry about. USDT-funded virtual cards with a Visa or Mastercard BIN and online payments enabled generally work for top-ups.
• Failures skew toward risk scoring, not balance. Subscription merchants decline virtual BIN ranges preemptively because of chargeback exposure on recurring billing. A one-off top-up carries less of that risk, so Stripe Radar tolerates it more. That said, some prepaid BIN ranges still get declined outright: if you see card_declined with sufficient balance, the fastest diagnostic is a card from a different issuer.
• Check the BIN before you blame the platform. Knowing whether your card is prepaid, debit, or credit, and who issued it, predicts decline probability. We've written a full guide on free BIN lookups and what you should never type into one: free BIN lookup tools and their safety limits.

If you're comparing against the provider-direct route, our earlier piece on OpenAI API usage tiers and card binding covers the other model: prepaid wallet, card verification, organization-level rate tiers. The short version: OpenAI wants a funded wallet and a verified card before you scale; OpenRouter just wants a positive balance. For anyone unwilling to prepay a provider wallet, that's a meaningfully lower bar.

402 vs 429: two very different "no"

This is the part of OpenRouter's documentation that deserves more attention, because these two error codes get conflated constantly. 402 is a money problem. 429 is a speed problem.

402: balance, key limit, or in-flight budget

Every 402 response carries an error.metadata.limit_source field, and there are three flavors:

• openrouter_credits: your account balance can't cover the request. Add credits.
• openrouter_key_limit: this specific API key hit the spending cap you configured for it. Raise the cap or wait for its reset.
• openrouter_in_flight_budget: your balance is positive, but the combined estimated cost of your concurrent requests exceeded the in-flight budget (a fraction of your balance, capped). The response includes a Retry-After header. Wait and retry; adding money is not the fix.

For ongoing monitoring, GET /api/v1/key returns limit_remaining and usage_daily fields. Wire that into your dashboard before errors start arriving, not after.

429: rate limits

Two sources again: OpenRouter's platform layer (the 50/day free-tier cap, or DDoS protection) and the upstream provider rate-limiting the model itself. Provider-side 429s automatically retry across other providers via fallback routing. The official guidance is blunt: exponential backoff, honor Retry-After, or buy $10 of credits to lift the free-tier daily cap from 50 to 1,000.

Keeping costs under control

The billing granularity makes OpenRouter unusually easy to budget. A few habits that pay off:

• Separate keys with per-key limits. Give your experiments a key capped at $5 and production its own key. If a key leaks, the cap is the worst-case loss.
• Top up in $20–50 increments. Larger single purchases amortize the $0.80 minimum, but the terms reserve the right to expire unused credits after a year. Don't treat it as a savings account.
• Watch usage_daily, not just the balance. A sudden spike in daily usage usually means a runaway loop or a leaked key. Discovering that at balance-zero is expensive; discovering it in a dashboard is a five-minute fix.
• BYOK is billed differently. Bringing your own provider key (BYOK) incurs a 5% usage-based fee, which the team has said will become a fixed monthly subscription eventually. That's separate from the top-up fee, so don't double-count.

Risks and fine print

The hard rules, before you pay:

• Refunds: 24 hours, unused credits only. The official policy lets you request a refund within 24 hours of purchase via the refund button. Platform fees are non-refundable, and crypto payments are never refundable.
• USDC is cheaper and irreversible. The 0.5% you save buys you zero undo. Wrong amount, wrong account, no reversal. If you're unsure about your usage volume, make the first purchase on a card.
• Unused credits can expire after a year per the terms. There's no sign of mass enforcement, but don't park money you won't spend.
• Stripe delivery delays are a known issue. The FAQ acknowledges up to an hour. Don't hammer retry because credits didn't appear in seconds; that's how you turn a successful payment into a fraud-flagged one.

FAQ

Is there a minimum top-up?

No hard minimum, but $10 is the practical threshold: it lifts the free-model daily cap from 50 to 1,000 requests and keeps the $0.80 minimum fee proportionate. Below $10 there's little point.

Can I pay with Alipay? How is it priced?

Yes. The FAQ lists major cards, Alipay, and USDC. Alipay runs through Stripe at the 5.5% tier ($0.80 minimum). For many users this is the simplest rail, no crypto on-ramp required.

My virtual card was declined. Is my BIN blacklisted?

Not necessarily, and assuming so wastes time. Rule out, in order: delivery delay (wait an hour), issuer international/online toggles, AVS billing-address mismatch, and retry-lockout from repeated attempts. Only then test with a card from a different issuer to isolate the BIN variable.

How fast do credits arrive?

Normally instantly. The Stripe rail occasionally delays up to one hour, per the official FAQ. If credits are missing after that: a Stripe receipt email means the charge succeeded and support can fix it; no receipt means the payment failed and you can safely retry with another card.

OpenRouter vs. going direct to each provider: which is cheaper?

Per-token prices are the same; OpenRouter charges 5–5.5% on top-ups. Going direct saves that fee but costs you separate accounts, prepaid wallets, and card verification at every provider. Scattered usage across many models favors OpenRouter; heavy single-provider usage favors direct.

Wrapping up

OpenRouter's payment system works well for the multi-model, small-balance, high-frequency developer, provided you respect two edges: the 24-hour refund window on card purchases and the total finality of crypto. Three things to remember: card refunds exist for 24 hours, USDC is cheaper but irreversible, and $10 unlocks the 1,000/day free-tier cap. If your actual use case is subscribing to AI coding tools rather than API credits, that's a different payment logic entirely, covered in our AI coding tools comparison.

Note: fees, refund windows, and daily request caps in this article were verified against OpenRouter's official documentation and blog on October 10, 2026. Check the official pages for current figures. Nothing here is financial advice.