You want to issue US cards. One rule stands in your way.
In the United States, only a bank or credit union can hold a card BIN (Galileo).
Not a startup. Not a platform. A bank.
Getting your own means audits, capital reserves in the millions, and a year or two you would rather spend building. This is the wall most teams hit on day one.
So skip it. You do not need your own charter. You can use ours.
We already hold the sponsor bank relationship and the US BIN. You send one API call, and a US Visa card exists a second later, with a US billing address ready for checkout.
No banking project. No payments hire. You can issue your first card today, and there is no KYC to buy it.
In short: An API for virtual card issuing in the USA lets your company create US Visa cards through code, using a sponsor bank’s BIN instead of your own banking license. Gpaynow supplies that bank relationship, the US BIN, and a US billing address, so your cards behave like domestic cards at American merchants. You can issue your first card today, with no KYC to buy.
Key takeaways
✅ US BINs come only from banks and credit unions, so you need a sponsor bank to issue cards here.
✅ The sponsor bank stays the legal issuer of record, while you run the product and the brand.
✅ A US BIN plus a matching US billing address helps your cards clear AVS checks at American merchants.
✅ Building your own program means capital reserves and audits; using our API means days.
✅ You can start now with no KYC to buy your first card.
Who can issue cards in the United States?
Only a chartered bank or credit union can hold a US card BIN. Everyone else issues through one of them.
A BIN is the opening digits of a card number. It identifies the issuing institution to Visa and to every merchant that sees the card.
To hold your own, you must become a principal member of the card network. That takes audits, certification, and capital reserves that run into the millions.
This is why nearly every US fintech you know runs on somebody else’s BIN. The alternative is a multi-year banking project.
What a sponsor bank does, and what you still own
A sponsor bank lends you its charter and its BIN so you can issue cards legally. It stays the issuer of record, and its compliance team carries the regulatory duty.
You keep the parts customers see. The brand on the card, the product design, the spend rules, the support experience, and the customer relationship all stay yours.
The split is clean in practice. The bank answers to regulators and the network. You answer to your users.
We manage that bank relationship for you. That means you do not negotiate a sponsorship deal, pass a bank’s onboarding review, or wait on a charter.
Why a US BIN and US billing address matter
American merchants read the card’s origin before they approve a charge. A US-issued card with a matching US billing address looks like what their systems expect.
Two checks decide most of this.
AVS: The Address Verification Service compares the billing address you enter with the one on file for the card. A mismatch is a common reason a charge fails, even with money available.
BIN type: Many US platforms decline prepaid BINs on principle. We issue US Visa credit BINs, which those merchants treat as ordinary credit cards.
We give you both pieces: a US BIN, and a US billing address to use at checkout.
Worth saying plainly, since you will read bolder claims elsewhere. No provider controls whether a given merchant approves a card. Each one sets its own rules, and Visa sets the rest. What we control is the BIN type and the billing details we hand you.
Who needs a US virtual card API, and why?
Two very different groups reach for US cards. People inside the United States, and people outside it who have to pay American companies.
The pain is not the same, so the fix is not either.
If you are in the United States
American teams already have cards. The problem is that one card is doing far too many jobs.
You are paying vendors from a single card. Every tool, ad account, and supplier bill runs through one number. When a charge looks wrong, tracing it takes real time.
One leaked number breaks everything. If that card is exposed, every service tied to it stops at once, and you re-enter a new number in dozens of places.
Your team needs cards you can turn off. A contractor starts, a project ends, someone leaves. You want a card that dies with the job.
You want to give your own customers cards. Fintechs, expense tools, and marketplaces need to issue cards inside their product, not buy them one by one.
How we help: you issue a separate US card per vendor, per employee, or per customer, each with a hard cap. A leak stays boxed in one card. A project ends, you freeze one card, and nothing else moves. Deeper on this in our corporate virtual card API and SMB guide.
If you are outside the United States
Here the problem is simpler and more painful. The services you depend on are American, and your card is not.
Your local card gets declined: US platforms often refuse cards issued abroad, or refuse prepaid BINs. You have the money, and the charge still fails.
Checkout asks for a US billing address: Many US vendors run an AVS check. Without a US address on the card, the charge can fail even when the card is fine.
Your bank caps or blocks foreign spend: Some banks limit international charges, or cut them off entirely, which leaves your subscriptions exposed mid-cycle.
Currency swaps eat the difference: Paying a US bill from a local-currency card adds a conversion fee to every charge.
Local payment apps do not work: The wallets you use daily are usually not accepted by US software vendors.
How we help: we give you a US Visa card with a US BIN and a US billing address, funded from your balance or with stablecoins. It presents as a domestic card at US checkouts, so the common reasons for failure are removed before you pay. Buyers in specific markets can start with our Nigeria guide or the guide to paying the OpenAI API from China.
What both groups end up paying for
The vendors are mostly the same list, wherever you sit.
✅ Cloud and hosting bills like AWS, Google Cloud, and Azure
✅ AI and API usage, including OpenAI and other model providers
✅ Ad accounts on Meta, Google, and TikTok
✅ Software subscriptions such as Adobe, Shopify, and Canva
✅ Marketplace fees, domains, and developer tools
One card per vendor turns that list into something you can read, cap, and cancel.
Build your own program, or use an API?
You have two real options in the US market. The right one depends on your stage and your appetite for a banking project.
Build direct. You apply for principal membership, hold capital reserves, pass audits, and negotiate with a sponsor or network yourself. This suits large institutions with payments teams and years of runway.
Use an issuing API. You connect to a platform that already holds the bank relationship and the BIN. You write code, not charters, and you launch in days.
Most teams pick the second path, then revisit the first only at real scale. Comparing your choices? See our guide to the best virtual card issuing API providers.
How Gpaynow issues US virtual cards
Gpaynow gives you a US card program through one API. We hold the bank and network side, and you control the cards.
US Visa BINs: Your cards carry a US BIN and a US billing address, so they behave like domestic cards at American merchants.
Instant issuance: One API call creates a live card. Full request and response samples are in our
API quickstart.
Spend rules that hold: Set a hard cap per card, block merchant categories, lock a card to one vendor, or make it single-use. See our spending controls docs.
Approve charges in real time: Use just-in-time funding so your own logic approves or declines each charge before money moves.
Virtual and physical: Issue virtual cards instantly, add physical cards when you need them, and push cards into Apple Pay or Google Pay.
Funding that fits you: Top up from your balance or with stablecoins, and hold more than one currency. See our crypto virtual card API.
No KYC to buy: Get a card without a long sign-up.
Start here.
Who issues US virtual cards with us
Teams reach for a US program when their customers, vendors, or platforms are American. These are the common cases.
Fintechs and neobanks launching a US card product without a charter.
Expense and AP tools giving American businesses cards for staff and suppliers. See our corporate virtual card API.
Marketplaces and platforms paying US sellers, drivers, or contractors with single-use cards.
Global operators who need a US card because their software and ad vendors are US-based.
Small teams replacing one shared company card. See the virtual card API for SMBs.
How to launch a US card program
You can go from sign-up to a live US card in a short cycle. Here is the order that works.
Get sandbox access: Sign up and take your test key. Build against fake money first.
Issue and test a card: Create a card, set a cap, and run test charges through your flow.
Wire your webhooks: Catch each charge as it happens so your ledger and your books stay current.
Move to live keys: Switch keys, issue a small batch of real cards, and watch the first charges clear.
Scale up: Add cards, tighten rules, and grow volume on the same integration.
US rules you should know about
Running cards in the US means living with a few rules. Most are handled for you, but you should know they exist.
The bank owns regulatory liability: Your sponsor bank answers to its regulators and to Visa for the program.
KYC and KYB apply at scale: Buying a single card needs no KYC with us. Running a card program that serves customers brings identity checks, which are built into the platform.
Card data has a standard: PCI DSS governs how card numbers are stored and shown. We keep that data on our side, which keeps most of the burden off your systems.
Networks set acceptance: Visa rules, and each merchant’s own risk settings, decide what clears.
Frequently asked questions
Can I issue virtual cards in the USA without a bank license?
Yes. You issue through a sponsor bank’s BIN. We hold that bank relationship, so you can issue US cards through our API without your own charter.
Who is the legal issuer of my cards?
The sponsor bank is the issuer of record. You own the brand, the product, the spend rules, and the customer relationship.
What is a BIN, and why does it need to be American?
A BIN is the opening digits of a card number that identify the issuing bank. A US BIN tells American merchants the card is domestic, which matters for their risk checks.
Why do US merchants decline some virtual cards?
Two common reasons are a billing address that fails the AVS check, and a prepaid BIN that the merchant blocks. We issue US credit BINs and give you a US billing address to use.
How fast can I launch a US card program?
Days. You can test in the sandbox today, then move to live keys once your flow works, instead of waiting on a banking project.
Do I need KYC to buy a card?
No KYC to buy your first card. Running a program that issues cards to your own customers brings identity checks, which are part of the platform.
Can I issue physical cards in the US too?
Yes. You can issue virtual cards instantly and order physical cards from the same platform and the same API.
Can a company outside the US issue US cards with you?
Often, yes. Many global teams issue US cards because their vendors are American. Talk with us about your setup and we will tell you what applies.
Why do I need a US card if I live outside the United States?
Because most of the services you pay for are American. US platforms often decline cards issued abroad or prepaid BINs, and many run an address check at checkout. A US card with a US billing address removes those common failure points.
Do I get a US billing address with my card?
Yes. We give you a US billing address to use at checkout, which is what the AVS check compares against. This is one of the main reasons foreign-issued cards fail on US sites.
Launch your US card program
The charter is the hard part. We already have that covered.
Create your Gpaynow account, issue a US virtual card in the sandbox today, and switch to live keys when your flow is ready. No banking project, and no KYC to buy your first card.
