Why did my BetMGM deposit fail and why is my withdrawal still pending? The most common cause is a mismatch between the amount or account details a player used and the conditions attached to that payment route.

Deposits and withdrawals declined because of limits

The player sees a decline message at the cashier and the requested amount stays untouched.

• The amount is above the ceiling allowed for that payment route.
• The amount is below the minimum the operator accepts for the chosen method.
• The account is not fully confirmed, so larger movements are held back.
• The player has already used the allowed total for the day or the week.
• The payment method belongs to someone other than the account holder.

1. Split the amount into smaller parts and try the same method again.
2. Switch to a different payment route that accepts the amount you want.
3. Confirm that the chosen method appears in your own name only.
4. Complete any identity checks that are still outstanding on the account.
5. Check whether a daily or weekly total has already been reached.
6. Wait for the limit window to reset before trying the larger amount again.
7. Remove saved payment details and enter them again carefully.
8. Make sure the card or account has enough available balance.
9. Try the request from the phone browser instead of a saved tab.
10. Keep a screenshot of the decline message for reference.
11. Ask support to explain which limit applies to your account.

Contact support when the decline persists after you have adjusted the amount and the method.

A withdrawal that stays pending longer than expected

The player sees the withdrawal marked as pending while the balance no longer shows the amount. betmgm99.com treats a pending request as one that is still being reviewed before the money leaves.

• Identity or address checks are still open on the account.
• The withdrawal was requested with a method different from the deposit.
• Bonus conditions tied to the deposit are not yet met.
• The account has an open query or a recent change of details.
• A routine review is in progress on the account.

1. Open the transaction history and confirm the request is listed as pending.
2. Complete any document request that appears on the account.
3. Return the withdrawal to the balance and request it again.
4. Use the same method you used to deposit where the operator requires it.
5. Check that bonus conditions attached to your deposit have been met.
6. Clear the browser cache, then sign in again to see the current status.
7. Cancel a duplicate request if you sent the same amount twice.
8. Make sure your personal details match the ones on your payment account.
9. Keep the reference number shown for the pending request.
10. Write down when you submitted the request for your own record.
11. Wait for the review to finish before sending another request.
12. Contact support with the reference number if the request still shows as pending after the stated review window.

Contact support once the pending status outlasts the review period shown on your account and no document request explains the delay.

Money left the bank but never reached the casino balance

The player sees the bank debit but the wallet shows no matching credit.

• The payment is still travelling between the bank and the operator.
• The transaction failed after the bank authorised it.
• The deposit went to a different account than the one now open.
• A saved payment detail was out of date.
• The payment route requires the bank to confirm before crediting.

1. Refresh the wallet from the browser and sign in again.
2. Compare the bank statement entry with the transaction history on the account.
3. Confirm the debit is settled and not merely authorised.
4. Check that you are signed in to the account you deposited to.
5. Look for a failed deposit entry in the transaction history.
6. Re-enter the payment details and repeat the deposit only once.
7. Note the reference number from the bank statement.
8. Save a copy of the bank statement line for the disputed amount.
9. Look for an automatic reversal on the bank side.
10. Keep the account open and unchanged while the case is checked.
11. Send support the bank reference and the date of the debit.

Contact support as soon as the bank debit is settled and no credit appears on the account.

Login fails or the account is locked after wrong attempts

The player sees an error at sign-in or a locked message after several failed tries.

• The password was typed with the wrong keyboard layout or case.
• Too many failed attempts triggered a temporary lock.
• The account has two-factor confirmation that is not completing.
• The saved password in the browser is out of date.
• A second account exists with a similar email address.

1. Retype the password slowly, checking capital letters and symbols.
2. Use the show-password option to see what is actually entered.
3. Confirm the email address matches the one on the account.
4. Complete the two-factor step with a fresh code.
5. Clear saved passwords for the site and enter the details again.
6. Try the phone browser on mobile data instead of Wi-Fi.
7. Wait out the temporary lock before trying again.
8. Use the password reset option and set a new password.
9. Sign out of all other devices before retrying.
10. Keep the account email inbox open for the reset message.
11. Contact support if the lock message persists after a successful reset.

Contact support when a reset does not lift the lock or the code never arrives.

Quick Reference

The table below pairs each problem with its usual cause and the first thing to check.

A declined amount often clears once it is split into smaller parts. A pending withdrawal usually waits on a document that the player has not yet sent. Missing deposits are frequently still settling between the bank and the operator. A lock is usually temporary and lifts after a short wait. Resetting the password is the fastest route back into an account. Recording each reference number makes every later support contact faster.

Keep your account details, email address and payment methods matching and current, and most of these problems will never reach the support queue.