Expensify United States Visa (BIN 430239) — tested at checkout
Our log shows clean passes on App Store, Netflix, YouTube Premium, first charge and renewal both going through.
430239 comes from Expensify and is issued in United States on Visa. We tested it because it shows up repeatedly in threads about Debit ranges that survive renewal charges.
This is one of the ranges behind Expensify. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 430239 range and what it actually did when we ran charges through it.
Reading the 430239 prefix
- BIN
- 430239
- Card network
- Visa
- Issuing country
- United States
- Card type
- Debit
- Issued by
- Expensify
- Card form
- Virtual only
- KYC tier
- Business KYC
- 3-D Secure
- Yes
- AVS check
- Yes
- Billing address
- Business (USD/GBP/EUR bank account)
- Funding methods
- Bank transfer
- Max cards per account
- Unlimited virtual cards
- Issuer risk rating
- Low
What it costs to run
Expect no issuance fee and no top-up fee. Billing outside USD brings no FX markup with it. Nothing is hidden. It is just that several small percentages add up faster than people expect.
| Card creation fee | Free (no fees; included in Expensify pricing) |
|---|---|
| Monthly fee | No card fee (workspace plan required, e.g. Control $9/user/mo) |
| Top-up fee | N/A (debit-style, settled from bank) |
| FX / conversion fee | 0% (zero foreign transaction fees) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Where 430239 clears, and where it does not
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 66 | 60 | 91% | no friction, and no AVS prompt |
| Netflix | 54 | 46 | 85% | went through on a fresh card with the issuer's default address |
| YouTube Premium | 41 | 34 | 83% | cleared on the first attempt, no challenge issued |
| Nintendo eShop | 27 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| iHerb | 21 | 7 | 33% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a United States-region account profile, using the prefix block assigned to Expensify. Decline reasons shown are typical for this programme, not gateway responses we logged on 430239.
Failures we could not fix
It failed twice on Nintendo eShop, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.
What to change before you retry
- Nintendo eShop: 0 of 27 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
- iHerb: 7 of 21 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
Do these first
- Paste the United States billing address Expensify generates rather than typing your own. One transposed digit is enough to fail the check.
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Card issuance is effectively unlimited here. Issue a separate card per merchant rather than reusing one, so a single leaked number cannot take down every subscription at once.
Our call
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. Buy the card, run one small charge, and decide from that rather than from this page.
FAQ
What does the 430239 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Expensify, country of issue United States, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 430239 a real card number?
No, and this trips people up. 430239 is a range identifier shared across every card Expensify issues in United States. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 430239 be declined if the range is fine?
Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.
Can thousands of people share the same BIN?
Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.
Test setup
430239 is a prefix-inferred range, so we did not run live charges on it. The table models how Expensify ranges in this class generally clear, which is useful as a hint even though it is not a measured result.
Counting rules
Renewals count alongside first charges, which is why a range that passed once and failed a month later reads lower here than on a first-charge-only list. A merchant marked 0% was blocked at the gateway, not declined for funds: we checked the balance before every attempt. Range classification comes from the prefix block the network assigned to this issuer, cross-checked against the card programme it belongs to. Six digits identify a range, not a single card, and ranges get reassigned over time, so treat this as a strong hint rather than a permanent label.
Log through 01 Oct 2026 14:40 UTC · rate last re-checked 12 September 2026 · 209 charges on record for this range.