Payment processing is not an area where problems can be left for later. When Stripe integrations fail, customers cannot complete purchases, subscription renewals break, and revenue stops. The margin for error is narrow, and the consequences of a poorly maintained integration are immediate. Expression 37 builds and maintains Stripe integrations for ExpressionEngine and Craft CMS websites, with a focus on reliability and ongoing support rather than one-off implementation.
Most Stripe integrations that come to us for support were built some time ago and have not kept pace with changes to the Stripe API or the underlying CMS. Others were implemented by developers who are no longer available, leaving the business with a payment system nobody fully understands. We take over those integrations properly, assess their current state, and provide the ongoing maintenance they require.
What This Work Covers
- Initial integration of Stripe with ExpressionEngine or Craft CMS websites
- Maintenance of existing Stripe integrations, including compatibility updates as the Stripe API evolves
- Support for one-off payments, subscriptions, and recurring billing arrangements
- Webhook configuration and maintenance, ensuring payment events are handled correctly
- Stripe Elements and Stripe.js implementation for secure, on-site payment forms
- Troubleshooting payment failures, webhook delivery issues, and integration errors
- Testing and validation after Stripe API updates to confirm continued correct operation
Common questions:
Our Stripe integration was built by someone else. Can you take it over?
Yes. Taking over an existing Stripe integration is straightforward with a proper code review. We assess how the integration was built, what version of the Stripe API it uses, what webhooks are configured, and how payments are processed and recorded. From that review we can advise on what, if anything, needs updating and provide ongoing maintenance from there.
Stripe has changed its API and we think our integration might be affected. What should we do?
This is a common concern, particularly for integrations built several years ago. Stripe deprecates older API versions periodically, and integrations built against those versions eventually stop working or lose access to newer features. An assessment of your integration against the current Stripe API will identify any issues before they become live problems.
We process subscription payments and renewals are sometimes failing. Can you investigate?
Yes. Subscription failures are usually traceable to specific points in the payment flow: webhook delivery failures, expired cards handled incorrectly, changes to subscription logic following a Stripe update, or issues with how failed payments are retried. A methodical review of the payment flow and webhook logs will identify the cause.
Do you handle the initial setup of Stripe for a new site, or only existing integrations?
Both. Where a site needs Stripe integrated for the first time, we handle the full implementation including payment forms, webhook configuration, and the backend logic for handling payment events. For existing integrations that need taking over or updating, the process starts with an assessment of what is already in place.
What does ongoing Stripe support typically look like after the initial work is done?
Most clients move to a retainer arrangement that covers the payment integration as part of broader site support. That means monitoring for any issues as Stripe releases API updates, handling any maintenance that arises, and being available quickly when something affects payment processing. Payment systems warrant closer attention than most parts of a site.
