Skip to main content

How can I resolve issues causing failed or declined deposits on Dabble?

Updated over a month ago

How to Resolve Failed or Declined Deposit Issues on Dabble

Having trouble with unsuccessful deposits on Dabble? Follow this guide to identify possible causes and resolve your issue:

Common Causes of Deposit Failures or Declines

  1. Insufficient funds in the linked account.

  2. Banking issues, such as blocked or declined payments.

  3. Payment processor safety measures to ensure transaction integrity.

  4. Incorrect payment details or outdated app versions.

  5. Internet connection or location services hindering transaction completion.

  6. Incorrect or mismatched payment details (such as card number, expiration date, or CVV).

  7. Using unsupported payment methods such as prepaid cards, Amex, or gift cards.

  • Ensure you are using an accepted payment method, such as Visa or Mastercard credit/debit cards. Certain banks may block transactions due to merchant category restrictions or lack of fraud verification.

After multiple failed attempts, some banks or merchants may temporarily block transactions


General Troubleshooting Steps

Before Retrying Your Deposit

  • Ensure your payment method is acceptable (Credit Card, Debit Card, or Apple Pay). Note that Dabble does not accept prepaid cards, Amex, or gift cards.

  • Confirm your payment details are accurate (e.g., card number, expiration, CVV

  • Confirm sufficient account funds.

  • Verify that payment details are accurate.

  • Maintain a stable internet connection during the transaction.

  • Make sure the billing address on your payment method matches the address in your Dabble account profile.

If a Declined Payment Shows as Pending

If a payment shows as pending but does not go through, the funds never reached Dabble. It is typical for banks to release these pending funds within the following timeframes:

  • Standard Pending Transactions: Funds are usually released back to your account within 48 hours , , .

  • Additional Considerations: If the transaction coincides with weekends or holidays, processing may extend up to 3 business days

  • Repeated failed transactions or rapid retries can trigger security flags. Allow 24 to 48 hours for the security block to clear and retry your transaction afterward.


Addressing Specific Scenarios

Frequent Failed Attempts

  • Repeated failed transactions can temporarily block further attempts by the payment processor or bank. Wait 24 to 48 hours before attempting again. Excessive failed attempts may flag your account. Use a new card or alternative payment method if needed.

Bank-Related Issues

  • Contact your bank to understand their reasons for declining the payments. Blocks applied by the bank may take 24 hours or more to clear. Ensure no restrictions exist on your linked card.

App Troubleshooting

  • Log out and back into the Dabble app, or uninstall and reinstall the app to refresh session data.

  • Ensure the app is updated to the latest version from Google Play or the App Store.

Location-Based Troubleshooting

  • Enable location services and high-accuracy modes on Android devices. Ensure your device is not in battery saver mode or using mock location services or VPNs. Retry your deposit after completing these steps.


FAQs

What if None of the Above Solutions Works?

  • If the issue still persists, collect a screenshot of the error, and reach out to Dabble's support team for further assistance.

What Should I Do If My Apple Pay Deposit Fails?

  • Update the app, log out and log in again, or try an alternative payment method such as PayID when Apple Pay deposits fail.

Proactive Tips to Avoid Future Declines

  • Use only supported payment methods and ensure sufficient account funds before attempting a deposit.

  • Address known issues such as incorrect details or internet instability before retrying a failed transaction.


Contact your bank and Dabble’s support team for assistance when needed. By following these steps, your deposit issue is likely to be resolved quickly and effectively.

Did this answer your question?