Transaction declines are the single most common complaint about OneCard. But most declines are fixable — once you know which type you are dealing with. There are three distinct categories, each with a different cause and a different fix.
The information in this article is based on user research (primarily r/CreditCardsIndia) and personal usage experience. OneCard does not publicly document its decline logic or risk engine. The company's internal rules are not known to us and the system may behave differently in specific cases. Use this as a practical guide, not a guarantee.
These are the simplest declines and the most overlooked. OneCard gives you granular control over your card — which means there are several settings that can silently block a transaction if you have not configured them correctly.
This catches a lot of users. If you fix a card control setting and immediately try the transaction again, the system can flag the rapid retry itself as suspicious behaviour — triggering an additional block on top of the original one. Wait at least 5 minutes after any card control change before retrying.
OneCard has a feature called Swipe2Auth. In certain situations — typically when a transaction looks slightly unusual but not severely risky — instead of outright declining it, OneCard sends you a push notification asking you to confirm the transaction is genuine. If you approve the prompt, your next attempt at the same merchant goes through.
The failure mode that trips up a large number of users: notifications are switched off for the OneCard app. The prompt arrives, you never see it, you assume the card is broken, and you spend the next hour troubleshooting a problem that was solved by a single tap you never received.
After a decline, open the OneCard app immediately and check your notification inbox or the transaction feed. If a Swipe2Auth prompt is waiting, approve it and retry the transaction. If you never receive these prompts, go to your phone's settings and ensure notifications are enabled for the OneCard app.
These are declines that cannot be overridden — not by you, and not by customer support. They are triggered by OneCard's risk engine when a transaction pattern looks high-risk. Common triggers include:
For risk-based declines, the standard advice from both customer support and experienced users is the same: wait approximately 24 hours and try again. The risk flag is time-bound, not permanent. This is an estimate based on user experience — the exact cooling-off period is not publicly documented.
Several users have reported that partially repaying your outstanding balance helped a blocked transaction go through sooner. The logic appears to be that reducing utilisation lowers the perceived risk. This is based on user experience and not officially confirmed — but it costs nothing to try and has worked for a number of people.
It is worth setting expectations before calling or emailing support, because the outcome depends entirely on which type of decline you have.
Based on user reports, support response times are variable and the chat-only support model frustrates users in time-sensitive situations — particularly when facing a decline abroad. If you are travelling internationally, the most important thing you can do in advance is enable your international transaction toggle and ensure your International Pass is active before you leave.
Based on the pattern we see in user complaints, a significant proportion of "mysterious" OneCard declines are actually Swipe2Auth prompts that were never seen. Before troubleshooting anything else, confirm that OneCard app notifications are enabled on your device. This one setting resolves more decline complaints than any other fix.
For any important purchase — especially the first large transaction, a new merchant, or international use — check these three things first: notifications are on, the relevant card control is enabled (e.g. international toggle for foreign purchases), and your outstanding balance is not close to your limit.
OneCard declines fall into three categories: card control restrictions (amount cap, international off, wrong PIN/CVV), Swipe2Auth prompts you may have missed due to notifications being off, and risk-based blocks on large or unusual transactions. Each type has a different fix.
Open the OneCard app, go to card controls, and check your settings: international transactions toggle, amount cap, and card lock status. After making any change, wait at least 5 minutes before retrying — immediate retries after a control change can themselves trigger a flag.
Swipe2Auth is a feature where OneCard sends you a notification asking you to confirm a transaction is genuine. If you approve it, the next attempt goes through. Many users miss this prompt because OneCard app notifications are switched off on their phone.
Retrying too quickly after a decline — especially after changing a card control — can itself be flagged as suspicious behaviour and trigger additional blocks. Wait at least 5 minutes after any control change before retrying.
For card control changes, wait 5 minutes. For risk-based declines (large amounts, new merchants, unusual patterns), wait approximately 24 hours before retrying. These are estimates based on user experience — exact timelines are not publicly documented by OneCard.
For card control declines, customer support can guide you to fix the setting yourself. For risk-based declines, support typically advises waiting — these blocks generally cannot be instantly overridden. Based on user reports, the standard advice is to wait and retry.
Some users have reported that partially repaying their outstanding balance helped a pending transaction go through. This is based on user experience and not officially documented by OneCard — but it is worth trying before waiting out the full 24-hour window.
Was this article helpful?
Found this useful? Share it.
Still have questions?
Ask our AI assistant — honest answers, including when OneCard isn't the right card.