Trying to add new card to purchase database

Simon Drayton 0 Reputation points

Hi all,

I'm hoping someone here has hit this and can point me in the right direction, because a week with support hasn't resolved it. In fact i don't even seem to care with level of comms and questions in the last 8 days.

The problem: I'm trying to add a credit card to purchase a service (Azure SQL Database). The card saves fine and shows in the payment methods list. But when I select it to complete the purchase, the portal just returns me to the same screen — no error message, no decline notice, nothing. It silently fails.

What I've already checked / tried:

  • Tried three different cards, all of them credit cards (not debit/prepaid/virtual).
  • All cards are US-registered with full US billing addresses; the account owner is a long-term US resident.
  • The billing account is registered in the US region.
  • Cards add and save successfully the failure only happens at the point of selecting the card to purchase.

Questions for the community:

  1. Has anyone seen this silent "returns to the same screen" behaviour, and what was the actual cause?

👁 User's image

  1. Could this be a billing-account region or profile mismatch even when the cards themselves are US-based?
  2. Is there a way to see the real decline/failure reason from my side, or a portal page where the underlying billing error surfaces?
  3. Any known browser/cache/session issues that produce this exact symptom?

Any pointers appreciated I have an overdue database migration blocked entirely by this. Thanks.

  1. Bharath Y P 9,730 Reputation points • Microsoft External Staff • Moderator

    Hello Simon, We understand that you are Credit card adds successfully, Card is visible under Payment methods. But Failure happens only when selecting it during subscription upgrade / purchase and No error message > silent redirect loop, This strongly indicates Azure didn’t bind the payment method to the billing scope used for purchase.

    Based on the docs we have, here are the most relevant angles to try.

    1) Confirm the right permissions (MCA billing profile scope)

    If you’re under a Microsoft Customer Agreement (MCA), credit cards are tied to a billing profile, and updating/using the payment method requires the right role.

    Make sure your role is one of:

    • Billing account owner or contributor
    • Billing profile owner or contributor

    (If you’re missing this, the UI can behave oddly because the portal can’t correctly authorize the change/checkout under your permissions.)

    2) Re-add the card via the correct blade (Cost Management + Billing → Payment methods)

    The recommended path is:

    • Azure portal → Cost Management + Billing
    • Choose the billing profile
    • Billing → Payment methods
    • Add payment method
    • Save (optionally set as default/active if that’s part of your flow)

    This ensures you’re not adding it in a place that doesn’t actually get used by the purchase checkout flow.

    3) Use the troubleshooting guidance for “payment issues”

    Microsoft’s “purchase/sign-up/upgrade payment issues” troubleshooting resources point to a few common causes even when the card “looks good”:

    • The payment method/PI isn’t actually able to process the service consumption (for example, threshold billing / authorization behavior)
    • Card/authorization problems on the financial institution side
    • Past due balances / subscription disablement scenarios
    • Declined payment (sometimes tied to the specific payment instrument on the subscription)

    Even though your portal doesn’t show a decline reason, this category of problems is exactly what those resources are for. If you don’t see a UI error, it’s still worth checking whether the purchase requires an authorization/settlement that’s currently failing.

    4) Check for session/browser issues (try private browsing)

    For payment-method pages, Microsoft specifically calls out:

    • If you get a “session has expired” style issue, try a private browsing session.

    Even if you’re not seeing that exact message, it’s still a quick sanity test because some checkout flows can fail silently when a session token/cookie state is off.

    5) Card eligibility / country support

    The docs also note:

    • Credit/debit cards are accepted by most countries/regions, but some countries have restrictions (example: Hong Kong and Brazil support credit cards only).
    • Also, verify you’re not using a card type that Azure disallows in your scenario.

    (You’ve said you tried multiple US-registered credit cards, so this is probably “less likely,” but still worth double-checking the card type really is credit and not something categorized differently by the issuer.)

    6) Where to look for the underlying reason

    From the provided docs, there isn’t a specific portal screen that guarantees the checkout decline reason will be shown to you. The closest practical approach suggested is to use the billing/payment troubleshooting resources and then escalate with support if the issue persists.

    If you need to get a real decline reason quickly, the likely best path is to open a support request from the Azure portal (docs explicitly recommend support request creation from the portal for payment troubleshooting).

    Reference links

    Hope this helps. If the information was useful, please consider accepting the answer and upvoting. Feel free to reach out if you need any further assistance. Thank you.

Sign in to comment

1 answer

  1. AI answer

    The behavior described (card appears to save, but the purchase flow loops back to the same “add/select payment method” screen with no error) is consistent with Azure silently rejecting the card or the payment method association, even when the card itself looks valid.

    From the available guidance, the most common causes and checks are:

    1. Card type or issuer not supported in Azure
      • Azure doesn’t accept virtual or prepaid cards for subscriptions or Azure SQL Database purchases, even if they’re branded as Visa/Mastercard and work elsewhere.
      • Some specific issuers (for example, certain fintech/bank alternatives) are known to be rejected in particular Microsoft payment flows, even when they are physical cards. In those cases, the supported path is to use a standard bank-issued credit or debit card that meets Azure’s regional rules.
      • If any of the cards are from such providers, switch to a traditional bank card and retry.
    2. Country/region or billing-profile mismatch
      • The billing account’s country/region must match the country/region of the payment method. If there is any mismatch (for example, tenant or billing profile not actually US even though the user is in the US), the card can be rejected.
      • Azure enforces region-specific rules (for example, some regions only support credit cards, some only Visa/Mastercard). If the billing account is actually mapped to one of those regions, a card that doesn’t meet the rule will fail.
      • To rule this out, verify the billing account’s country/region and ensure the card is issued from the same country/region as the billing account.
    3. Card data or status issues
      • If the name, address, or CVV do not exactly match what the bank has on file, the card can be declined during the authorization step even though it appears to save successfully.
      • If the card is inactive, blocked, or not enabled for international/online transactions, the authorization can fail.
      • The recommended action is to confirm with the bank/card issuer that:
        • The card is active and not blocked.
        • International and online transactions are enabled.
        • The address and name being entered match the bank’s records.
    4. Outdated or blocked card information
      • If the card information is outdated or the card has previously failed authorizations, Azure can require updating or replacing the card before allowing further purchases.
      • Use the Azure portal’s payment methods experience to ensure the card is fully up to date. If problems persist, remove the card and add a different one that meets the supported payment-method rules.
    5. How to surface the real failure reason
      • For subscription and payment issues where the portal doesn’t show an error, Microsoft directs users to the declined card and payment issues troubleshooting flows. These flows don’t expose raw bank decline codes to customers but do narrow down the cause to:
        • Unsupported card type (virtual/prepaid, or specific issuer scenarios).
        • Country/region mismatch.
        • Inaccurate card details.
        • Inactive/blocked card.
      • If none of those apply and the portal still loops, the next supported step is to create a support request under Azure Billing so that support can see the backend decline codes and any risk checks that are blocking the transaction.
    6. Browser or session issues
      • For sign-up and payment flows, Azure relies on third-party cookies and specific browser behaviors. When cookies or certain content are blocked, the payment or verification step can appear to hang or silently fail.
      • Recommended checks:
        • Ensure third-party cookies are allowed for the Azure portal.
        • Try a different browser or an InPrivate/Incognito session.
        • Clear cache/cookies and retry the payment flow.
    7. If the card keeps failing
      • If a card continues to be declined or silently rejected after confirming all of the above, the supported resolution is to:
        • Use a different, standard bank-issued credit or debit card that complies with Azure’s payment-method rules for the billing account’s region.
        • If that still fails, open or update an Azure Billing support request so that support can review the specific billing account and payment method association.

    These steps address the most likely causes of the “returns to the same screen” symptom for Azure SQL Database purchases when cards appear to save but cannot be used to complete the transaction.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer