> ## Documentation Index
> Fetch the complete documentation index at: https://supastack.dev/llms.txt
> Use this file to discover all available pages before exploring further.
> For the full documentation corpus in one file, fetch: https://supastack.dev/llms-full.txt

# How to Pay for AWS SES, Supabase, and Other Dev Tools from Russia

Russian-issued bank cards are declined by AWS, Supabase and most US dev services. The options that actually work in 2026: foreign-issued cards, intermediary payment services, self-hosting, and provider switches, with the honest trade-offs of each.

_Published 2026-11-22._
_Updated 2026-11-22._

> **How can I pay for AWS SES or Supabase from Russia?**
> It depends on the service and what you have access to. Cards issued by Russian banks are declined at the payment-network level, so no domestic or Mir card will work. The practical paths are a card issued by a foreign bank, an intermediary service that pays the invoice for a commission, or sidestepping the service: Supabase is open source and self-hosts on any VPS, and SES has alternative email providers. Keep account details real and expect provider rules to keep shifting.

## The short answer

Your card is not broken. Since 2022, Visa and Mastercard do not process international payments for Russian-issued cards, Mir is not accepted abroad, and processors like Stripe decline Russian bank identification numbers on top of that. AWS SES, Supabase and most US dev tools simply have no way to charge a Russian card. What actually works comes down to four options.

None of them is instant magic, but each is proven and in wide use. Pick based on how much ongoing effort you can afford and whether you can change tools at all.

| Option | Effort | Main trade-off |
|---|---|---|
| A foreign-issued bank card | Highest upfront, easiest long-term | You need to open or source a card abroad |
| Intermediary payment service | Lowest | Commission per payment plus a trust decision |
| Self-host the tool | Highest ongoing | You own the ops; no managed-cloud bill |
| Switch providers | Medium | Different feature set, new vendor to learn |


## Why Russian cards get declined

Three separate walls stack up. At the network layer, Visa and Mastercard stopped processing international transactions for Russian-issued cards in March 2022, and Mir has almost no acceptance abroad. At the processor layer, Stripe and similar gateways screen the card's bank identification number and decline Russian ranges even where a charge might technically route. At the vendor layer, AWS suspended new account sign-ups from Russia and Belarus in 2022; existing accounts kept running, which is why people can still log in but cannot pay.

That is why the error messages feel random: "card declined", "payment method not available in your region", or a silent retry loop all describe the same block. Switching to another Russian bank card changes nothing, since the entire domestic range is filtered, not one issuer.


## Option 1: pay with a foreign-issued card

The cleanest fix is a card issued by a bank outside Russia. Many developers hold accounts in Kazakhstan, Kyrgyzstan, Georgia, Armenia, Uzbekistan or the UAE; requirements range from fully remote onboarding to an in-person visit, and rules shift over time, so verify the current terms for your citizenship before planning around one bank.

Once you have the card, attach it in the provider's billing console exactly as issued: billing country, name and address should match the card issuer's records, not a made-up US address. Keep a small balance buffer because international authorizations place temporary holds, and add the card before the invoice date so a failed first attempt does not suspend the account.

Virtual card services sit in the middle: fast to issue online and topped up with rubles or crypto, but prepaid ranges are the first ones providers re-check and sometimes flag. They work often enough to be worth trying for small invoices; verify the issuer explicitly supports the service you need before paying anything large.


## Option 2: intermediary payment services

A second market exists for exactly this problem: services that pay your invoice for a commission. You send rubles by local transfer, SBP or crypto, they charge their own foreign card against your provider's bill, and you get a receipt. Commissions typically run a few percent per payment, sometimes plus a fixed fee.

The model is established enough to have a market, but it concentrates trust: a third party sits next to your billing. Prefer intermediaries that pay your own invoice rather than selling "ready accounts" (purchased accounts get banned and you own nothing), never hand over root credentials, keep every receipt and chat record, and test with a small payment first.


## Option 3: self-host or switch providers

Supabase is the easiest case because it is open source end to end. You can run the full stack (Postgres, GoTrue auth, PostgREST, Storage, Realtime) on any VPS, including regional providers like Yandex Cloud, Selectel or Timeweb that bill locally in rubles, or on an inexpensive European VPS paid with any method above. You trade the managed dashboard for full control and no vendor bill; for a small product the ops burden is modest.

SES is different because it is a service rather than software, but transactional email has many providers. Alternatives such as Resend, SMTP services with non-US billing, or regional ESPs may accept the card you have, and the [AWS SES setup guide](https://supastack.dev/docs/web/aws-ses.md) shows the kit's provider-adapter pattern: swap the adapter, keep the templates. For infrastructure generally, regional clouds cover the basics while you keep critical services on whatever billing works.


## Keep the account, not just the payment

Whatever path you choose, keep the account defensible. Use your real name and real details; inventing a US persona to match a card is what turns a payment workaround into a terms-of-service ban. Provider policies also keep moving: AWS froze new Russian sign-ups in 2022 and has not announced a reversal, and processors tighten card filters without notice.

Useful habits: pay monthly rather than annually while the ground shifts, export data and infrastructure definitions regularly, keep a second reachable payment method on file where the provider allows it, and never let a critical account depend on a single intermediary. The goal is a clean exit path, not just a working card.


## If you sell software yourself

The wall you just hit is the same one your own customers will hit. Card declines look like churn but are really coverage gaps: buyers in regions that Stripe and the US card networks underserve simply cannot pay you, no matter how good the product is.

The mitigation is billing breadth: merchant-of-record providers that settle globally, PayPal, regional options and crypto where your audience needs it, plus invoice-based payment for B2B. [SaaS payment providers compared](https://supastack.dev/blog/saas-payment-providers-compared.md) walks the trade-offs, and it is why supastack wires eight web billing providers plus RevenueCat behind one entitlement ledger, so the provider your customers can actually pay with is configuration, not a rewrite. The [payment setup guide](https://supastack.dev/docs/web/setup-payments.md) shows the wiring.


## Common questions

The same handful of questions comes up in every thread on this topic.

- Will a Mir card work for AWS or Supabase?, No. Mir is not accepted by either service, and Russian-issued Visa and Mastercard are declined for international charges.
- Do virtual cards work?, Sometimes. They are the fastest to get but also among the first providers re-check and flag. Confirm the issuer supports your specific service before loading money, and prefer them for smaller invoices.
- Is paying through an intermediary safe?, It depends on the provider. Services that charge your own invoice for a published commission are widely used; "pre-verified accounts" for sale are the version that gets people banned and loses you the account.
- Can I still open a new AWS account from Russia?, New sign-ups from Russia and Belarus have been suspended since 2022. Existing accounts continue to operate and can be billed to an accepted foreign card.
- What is the cheapest reliable path?, For Supabase, self-hosting on a regional VPS costs only the server bill. For AWS SES, a foreign card you own beats recurring intermediary fees once you pay more than a few invoices.
