Short answer: choose Standard semantics when throughput and recovery latency matter more than delivery order, and choose FIFO semantics when a retry must be serialized with related work. For a nightly payment-provider reconciliation, the decision is less about the queue name than about the idempotency key, the message group, and the alert that tells an operator the retry budget is being consumed.
The useful boundary is this: Standard delivery is at least once with best-effort ordering, so every handler must tolerate duplicates and reordering. FIFO provides ordered processing within a message group and deduplication behavior, but that ordering can turn one slow or poisoned job into a queue-wide delay for that group.…