The gateway timed out. Where did the payment go?

Frequently asked questions

What should you do with a message you can't confirm was processed?

Never mark it complete — an uncompleted message becomes available for redelivery instead of being silently lost, which is what lets retries recover from a transient failure like a payment gateway timeout.

What stops a bad message from retrying forever?

MaxDeliveryCount — once a message's delivery count reaches that limit it's automatically moved to the dead-letter queue instead of retrying indefinitely. The dead-letter queue is only useful if something alerts on its depth; left unread, it's the same as losing the message.

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

• AI Bot Attacks on a Mobile App Login, and How Azure Stops Them

  A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.

• Azure Key Vault Explained: The One Secret Tutorials Never Remove

  Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.

• How to Secure a Mobile API on Azure in Five Steps, in the Right Order

  HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.