Sadapay Pakistan Mastercard (BIN 530961) — tested at checkout
The three places it never failed: Udio AI, Hugging Face, Disney+. Everything above 90% success in the log traces back to those.
We keep coming back to 530961 when a merchant blocks the well-known virtual ranges. It comes from Sadapay in Pakistan and does not sit on the usual blocklists.
This range sits inside the Sadapay. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 530961 range itself did at checkout.
Reading the 530961 prefix
- BIN
- 530961
- Card network
- Mastercard
- Issuing country
- Pakistan
- Card type
- Debit
- Issued by
- Sadapay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes (Mastercard 3D Secure)
- AVS check
- No
- Billing address
- Pakistan
- Funding methods
- Bank transfer
- Max cards per account
- 1 (virtual card per account)
- Issuer risk rating
- Low-Medium (State Bank of Pakistan regulated)
Costs, stacked up
Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, a 6% conversion fee. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | Free (virtual Mastercard); PKR 1,724 physical |
|---|---|
| Monthly fee | Free |
| Top-up fee | Not applicable (wallet) |
| FX / conversion fee | 6% international transaction fee |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Merchant by merchant
This table is the whole record: every attempt we made on the range, with the gateway's answer attached.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Udio AI | 108 | 97 | 90% | went through on a fresh card with the issuer's default address |
| Hugging Face | 88 | 76 | 86% | first charge and renewal four weeks later both cleared |
| Disney+ | 68 | 59 | 87% | went through on a fresh card with the issuer's default address |
| Crunchyroll | 44 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| GOAT | 32 | 12 | 38% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a Pakistan-region account profile, using the prefix block assigned to Sadapay. Decline reasons shown are typical for this programme, not gateway responses we logged on 530961.
Failures we could not fix
Failures were rare but real: Crunchyroll declined on three attempts, and we never did get it through.
What to change before you retry
- Crunchyroll: 0 of 44 cleared. Billing runs monthly in USD from the account's store region. Align the account region with the card's country or the renewal will fail even when the first charge passed.
- GOAT: 12 of 32 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
Setup notes for Sadapay
- Set the billing address to exactly what Sadapay generates for Pakistan. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
- 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.
Where we land
If you only need one subscription this is more than enough. If you are running paid traffic at volume the Not applicable (wallet) funding fee starts to hurt around the third month. Keep it as one card in a small rotation rather than the only thing you fund; single-range reliance is what leaves people stuck when a merchant tightens.
What people ask us
What does the 530961 BIN tell a merchant?
In practice the checkout reads Sadapay / Pakistan / 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 530961 a real card number?
Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.
Why would 530961 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
Can thousands of people share the same BIN?
That is the normal case. Every Debit card Sadapay issues in Pakistan carries the same six digits. Two people on 530961 can get opposite results at the same checkout, which is why a single review is never conclusive.
How this test was run
No physical card sits behind 530961 in our lab; the six digits come from the prefix the network assigned to Sadapay. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 09 September 2026 · 340 charges on record for this range.