This should not be a blog post.
I should not have enough material to write 500 words about changing an expired credit card.
Yet here we are.
Recently, I needed to do something incredibly complicated: proactively update the credit card attached to several WordPress plugin subscriptions before the old card expired.
That’s it.
No API integration. No custom PHP. No database migration. No server configuration.
Just:
Log in → Billing → Update Credit Card.
Except I couldn’t.
Across accounts for SearchWP, CosmicGiant, GravityKit, Perfmatters, and Uncanny Owl, I could not find a straightforward way to simply replace the payment card being used for future renewals.
One company let me do it easily: Gravity Wiz.
And, frankly, that wasn’t much of a surprise. Those people consistently seem to think through the little details that make software pleasant to use.
But this isn’t meant to make fun of the other companies. Quite the opposite.
It’s kind of sad.
These Are Software Companies
That’s the part that makes this so strange.
We’re not talking about the local dentist’s website running a payment form somebody built in 2017.
These are companies that build WordPress software.
Really good WordPress software, in many cases.
They build complex plugins involving APIs, automation, databases, licensing systems, conditional logic, integrations, background processes, and all sorts of technically impressive things.
Yet a customer can’t say:
“My credit card expires next month. Here’s my new one.”
How did we get here?
What’s Actually Causing This?
I suspect the problem isn’t that these developers don’t know how to build an “Update Card” button.
The underlying issue is probably the billing infrastructure.
Software companies often have multiple systems stitched together: a payment processor, subscription platform, licensing system, customer portal, merchant-of-record service, accounting system, or some combination of them.
Sometimes the customer account and the billing account aren’t really the same account at all.
Maybe the payment platform only exposes certain actions. Maybe subscriptions were created under an older billing system. Maybe the company’s licensing software doesn’t provide a clean customer-facing billing portal. Maybe allowing payment-method changes requires additional development or security considerations.
There are probably perfectly legitimate technical reasons.
But here’s the uncomfortable question:
Why are we letting our billing software dictate such a basic part of the customer experience?
Think About What We’re Missing
If changing a credit card is unnecessarily difficult, what else are customers struggling with?
Can they easily update their company name?
Change the billing contact?
Download every invoice?
See exactly what renews next year?
Switch payment methods?
Change the email attached to the subscription?
Consolidate licenses?
Cancel without emailing support?
These aren’t glamorous features.
Nobody announces them at WordCamp.
But they’re the things customers actually interact with.
All I Wanted to Do Was Pay You
That’s what makes this especially ridiculous.
I’m not trying to cancel.
I’m not disputing a charge.
I’m not asking for a refund.
I’m literally trying to make it easier for you to collect money from me next year.
A customer proactively updating an expiring card is probably one of the better customers you can have. They’re thinking ahead specifically so their subscription doesn’t fail.
Don’t make that person open a support ticket.
Don’t make them wait for the card to decline.
Don’t make them receive three “We couldn’t process your renewal” emails six months from now.
Give them a button.
Gravity Wiz did.
Everyone else: come on.
We’re WordPress developers.
Collectively, we can do better than this.
Leave a Reply