There are three different failures in this thread all being called "declined", and they have different fixes. Worth separating them before you burn a fifth card.
1. The BIN is refused before your bank is asked
The platform keeps its own list. Prepaid and most virtual ranges are on it, and so are plenty of ordinary consumer debit ranges from particular issuing countries. Nothing ever reaches your bank, which is exactly why the card "works everywhere else". The tell is an instant rejection — under a second — and no message from the issuer.
2. Your bank refuses the verification charge
Usually a small authorisation, sometimes zero-value. Some issuers decline zero-value auths outright, others flag the merchant category. Here you do get the SMS. Approving it in the banking app and re-adding the card fixes it maybe half the time.
3. The account is already flagged and the card is the excuse
This is your three-hour one. Card attaches, spend starts, payment failure appears, account pauses. That billing failure is downstream of a risk decision that was made before you attached anything. Swapping cards does nothing, and every attempt is one more data point tying your cards to each other.
What I would actually do: stop adding cards to that account entirely. Test any new card somewhere with existing spend history before it goes near a fresh account, and keep one card per business manager. I have not tested that above five accounts on a single entity, so treat the last part as a preference rather than a finding.
Short version: instant means the BIN, a text from your bank means the bank, and dying three hours in means it was never about the card.