Repeated RunPod Stripe payment problems
Is there any way to pay RunPod without using Stripe? For the past three days, multiple cards have been rejected without any explanation. This is a recurring issue: a fully funded card is declined with no specific reason provided. Interestingly, the same cards work seamlessly on e.g Anthropic or PayPal, which suggests the issue might stem from RunPod’s Stripe setup. I speculate, being entirely ignorant of the mechanics. Yesterday, after failing to pay directly, I sent the funds via PayPal to a friend in the UK—the card was debited without incident or even an OTP request. However, the UK card was rejected by Stripe. No reasons given despite verification having been given via banking app.
The problem appears to lie in the repeated requirement for verification on each payment, including Link and bank-level OTP verification. While such steps might seem bank-related, other services process payments effortlessly after the card is registered. As noted in Anthropic and PayPal examples, you are able to just pay without these additional hurdles.
The issue is really quite disruptive, and becomes the more frustrating when one is desperate to work on data locked inside RunPod and there is no explanation or path to resolution.
6 Replies
pm me details, yes we do have rules around cards usage and you may be running into those and stripe will block the transaction
I sent the details through yesterday
This is an outrage surely?
Unfortunately No, when your balance is below 0, we give you couple days to keep your network volume. But if you still not able to add money. System will auto remove the resources you are using.
Your position demonstrates not only a troubling lack of care but also a level of disregard that no reputable company should defend. Let us examine the facts:
RunPod's storage fees rank among the highest in the market. The maintenance of a 600GB drive at approximately $30 per month represents a significant investment, clearly indicating the valuable nature of the stored data. Any business observing a customer's continued retention of such a large drive over months, given its premium cost, would recognise this significance.
The deletion of a drive after merely "a couple of days," without reasonable attempts to contact the customer, demonstrates reckless disregard for crucial data. "Reasonable" is an objective standard, and this was no unforeseen accident—it was entirely predictable and preventable. Your failure to communicate effectively with a premium-paying customer suggests serious negligence. More concerning still is your non-responsiveness despite knowing that unresolved payment issues would result in data deletion. And if your customer is hospitalised after a traffic accident? This appears an ill-considered position broadly.
In my specific case, I documented in this thread my attempts over several days to resolve a payment issue—one your representative acknowledged as inherent to your system and this by design. Your customers neither understand these system mechanics nor have access to any recourse when problems arise. What options exist when your system locks out a customer?
I sent private messages to two team members explaining the situation's urgency, receiving no response. Even after this post gained attention, it took hours for initial staff acknowledgement, followed by a day of silence and merely a "like" to my follow-up message. During this period of apparent indifference, my drive was erased.
Those aware of the situation failed to intervene or expedite a resolution despite their knowledge of the policy you callously raise as a shield. Yet it is no shield at all given the self-evidently egregious circumstances. This case represents clear negligence that played out on a public platform, yet your response suggests a disturbing lack of concern for customer welfare.
Your dismissive response is unacceptable, and I assure you this matter will not be easily resolved. This issue concerns a service provider's fundamental duty to maintain basic standards of care and communication. The evidence demonstrates a pattern of neglect and apathy that cannot be defended.
Given these circumstances, you owe both myself and others similarly affected a formal apology and appropriate compensation for the significant harm caused. Should you choose not to address this matter properly, I will take necessary steps to prevent other paying customers from experiencing such disrespect.
I await your prompt and comprehensive response, including a compensation proposal that reflects the severity of these failures.
I sincerely apologize for the data loss you’ve experienced and for not addressing your payment issue in a timely manner. This was entirely my oversight, and I take full responsibility for it. I should not have assumed your issue was resolved simply because you shared the details via DM with my colleague.
While Discord isn’t our official support channel and we typically recommend using our contact page to submit a ticket for urgent matters like payments, I understand that mentioning this now may feel like an excuse.
To make things right, you can either create a ticket directly and share the ticket number with me, or, if you prefer, you can DM me your RunPod email address, and I’ll open a ticket on your behalf to ensure it’s handled promptly.
https://contact.runpod.io/hc/en-us/requests/new
Please know that we are fully committed to resolving this issue and will do everything we can to make things right.