BIN lookup · Visa · Saudi Arabia · log through 13 Sep 2026 14:40 UTC

Visa Virtual Card BIN 475624 - Saudi Arabia (Debit)

The gist

Our log shows clean passes on App Store, Epic Games Store, Steam, first charge and renewal both going through.

475624Visa Saudi ArabiaDebit 224/307 cleared

The first thing to know about 475624 is that it is not an anonymous range. STC Pay issues it in Saudi Arabia and the Visa prefix is registered, which is why fewer merchants treat it as high risk.

475624, decoded

BIN
475624
Card network
Visa
Issuing country
Saudi Arabia
Card type
Debit
Issued by
STC Pay
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Not published
Funding methods
Bank transfer
Max cards per account
Not published
Issuer risk rating
Medium

The money side

Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, a 3% conversion fee. Cost is the reason this range sits where it does in our ranking rather than higher up.

Card creation feeFree
Monthly feeFree
Top-up fee
FX / conversion fee3% international (STC Bank card)
Declined transaction fee
Minimum top-up

Results by merchant

Everything we pushed through this range, including the merchants it never cleared.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
App Store989092%first charge and renewal four weeks later both cleared
Epic Games Store797190%went through on a fresh card with the issuer's default address
Steam615285%went through on a fresh card with the issuer's default address
Tidal3900%3-D Secure challenge never completed. The order timed out waiting for the OTP.
Crunchyroll301137%Range blocked at the acquirer. Declined before the authorisation was even routed.

Run from a Saudi Arabia-region account between 03 Jul to 04 Sep 2026, with the billing address set to the issuer default unless noted. Declines were logged with the reason the gateway returned.

Failures we could not fix

Two merchants gave us trouble, Tidal and Crunchyroll. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.

What to change before you retry

Before you try it

  1. No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.
  2. Watch the 3% conversion fee. Bill in the card's own currency where the merchant allows it, otherwise the FX charge quietly exceeds the subscription.
  3. Paste the Saudi Arabia billing address STC Pay generates rather than typing your own. One transposed digit is enough to fail the check.

Verdict, briefly

We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. The pattern across all 307 attempts was consistent, which is the most useful thing you can say about a card range.

BIN questions, answered

What does the 475624 BIN tell a merchant?

In practice the checkout reads STC Pay / Saudi Arabia / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.

Is 475624 a real card number?

No, and this trips people up. 475624 is a range identifier shared across every card STC Pay issues in Saudi Arabia. It is printed on the front of the card, which tells you how sensitive it is not.

Why would 475624 be declined if the range is fine?

Of the 307 attempts behind this page, the losses broke down as address mismatch first, incomplete 3-D Secure second, and merchant-side range blocks a distant third. Only the last one is about 475624.

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

We bought a STC Pay card, funded it, and pushed 307 charges through live merchant checkout pages between 03 Jul to 04 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 224 cleared.

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 13 Sep 2026 14:40 UTC · rate last re-checked 12 September 2026 · 307 charges on record for this range.