Rapyd API Fails on Subscription Payments – And Their Team Doesn’t Care
We’ve been running into a recurring issue with Rapyd’s API when processing subscription payments:
ERROR_GET_PAYMENT_METHOD_TYPE
This happens when the very same cards Rapyd creates for subscriptions are later not recognized by their own API.
In short — Rapyd is breaking its own process.
We’ve reached out to support multiple times, and the response has been… silence. No urgency, no fix, no accountability.
For businesses running subscriptions, this isn’t a small bug — it’s a deal-breaker. How are we supposed to operate a reliable subscription service when the payment processor can’t process its own saved cards?
If Rapyd doesn’t address this, we’ll be looking for a payment provider that takes uptime, reliability, and their customers’ business seriously.