The Most Common Competitor Isn't a Company
When platforms evaluate how to add payment capabilities, the first instinct is rarely to buy a solution. It's to build one.
"We have great engineers. We'll integrate Stripe, build onboarding flows, and handle it ourselves."
This makes intuitive sense. Your team knows your product. Direct integrations give you control. And the initial scope seems manageable: a PSP API, some checkout components, basic transaction management.
But the initial scope is never the final scope. And the gap between the two is where platforms lose months, burn budget, and divert engineering from the product that actually differentiates them.
What "Build It Ourselves" Actually Means
Phase 1: The First PSP
What you expect:
Integrate Stripe (or Adyen) APIs
Build a checkout flow
Handle basic payment processing
What you actually build:
PSP API integration with full error handling, idempotency, and retry logic
Webhook receivers and event processing for payment lifecycle events
Tokenisation flow for storing card data securely
Checkout UI components matched to your platform's design
Basic refund and dispute handling
Transaction logging and reporting
Engineering cost: A small team for a few months. This part goes roughly to plan.
Phase 2: The Reality Check
Your first PSP integration is live. Then:
Product asks for merchant-level reporting (not just platform-level)
Finance asks for reconciliation between PSP settlements and your records
An enterprise customer demands Worldpay instead of Stripe
Your compliance team discovers PCI DSS obligations
Customer support needs a way to process refunds and manage disputes
Each of these is a separate project. None was in the original scope.
Phase 3: The Compounding
A second enterprise customer requires Adyen. You scope a second PSP integration.
The contact centre team asks for phone payments. You discover voice PCI is a different problem entirely.
The AI team wants payment capture in their chat agent. Another integration surface.
PCI DSS audit reveals your infrastructure needs significant changes to achieve certification.
Worldpay updates their API. Your integration breaks.
Your "three-month project" is now a permanent engineering function.
The Real Cost: Build vs Shuttle
Build In-House | Shuttle | |
|---|---|---|
PCI DSS compliance | Achieve and maintain Level 1 yourself: assessments, scans, remediation and staff time. ~$225k a year average PCI DSS Level 1 assessment cost for a large merchant, before technology and staff costs (Ponemon Institute / Thales, 2010) | Scope limited: Shuttle is PCI DSS Level 1 certified |
PSP coverage | 1-2 gateways (each a months-long integration) | 40+ gateways through a single integration |
Adding a new PSP | A months-long engineering project | Configuration change, if the PSP is one of the 40+ supported. Saved cards stay with the gateway that stored them |
Year 1 total cost | Engineering team, PCI assessment and remediation, and tooling | Transaction-based pricing (POA) |
Annual ongoing cost | Maintenance, annual PCI assessment and ongoing engineering | Transaction-based pricing (POA) |
Channel coverage | Checkout only (voice, links, AI require separate builds) | Checkout, voice, payment links, chat, AI agents |
Adding a new channel | New engineering project per channel | Already available |
Merchant onboarding | You build and maintain it | Pre-built, white-label |
Merchant portal | You build and maintain it | Pre-built, white-label |
Refunds | You build it | Built-in |
Transaction and refund data | You build it | Built-in: one format across every PSP |
Three-Year Cost Comparison
Year 1 | Year 2 | Year 3 | 3-Year Total | |
|---|---|---|---|---|
Build | Initial build, first PCI assessment and remediation, tooling | Maintenance, annual PCI assessment, new PSPs and channels | Maintenance, annual PCI assessment, new PSPs and channels | An engineering team and a PCI programme, every year |
Shuttle | Transaction fees | Transaction fees | Transaction fees | Transaction fees (POA) |
What You Give Up When You Build
Product Velocity
Every engineer on payment infrastructure is an engineer off your product roadmap. Your competitors ship features while your team maintains webhook handlers and PCI audit trails.
Every sprint spent on payments is a sprint not spent on what makes your platform different.
Enterprise Deal Speed
An enterprise customer needs a PSP you haven't integrated. With an in-house build, that's a new integration project before you can close the deal. If their PSP is one of the 40+ Shuttle supports, it's configuration, not a new integration. Saved cards stay with the gateway that stored them.
In competitive markets, the platform that can say "yes, we support your PSP" first wins the deal.
Multi-Channel Capability
Your in-house build covers online checkout. Now your business needs:
Voice payments for the contact centre
Payment links for field service teams
AI agent payment capture for the chatbot
Each is a separate build project with its own PCI implications, telephony requirements, and integration surfaces. Or each is already available through Shuttle's existing integration.
PCI Scope Control
Every system that touches card data is in PCI scope. Your application servers, databases, network infrastructure, deployment pipelines, and the laptops of engineers who access those systems. Adding a channel (voice, chat) expands the scope further.
Shuttle's architecture keeps card data in a certified environment that your systems never touch. Adding channels or PSPs doesn't bring card data into your systems.
When Building In-House Makes Sense
To be fair, there are scenarios where building makes sense:
Payments ARE your product. You're a fintech building payment infrastructure as your competitive advantage.
You process billions annually. At that scale, owning the payment stack and running a dedicated payments team can make sense.
You have existing PCI infrastructure. Banks, financial institutions, and regulated entities that are already PCI Level 1 certified.
You only need one PSP, one channel, forever. No enterprise customers will demand PSP choice. No channels beyond checkout will be needed. (Rare, but possible.)
You have time before deals depend on it. No revenue is waiting on payment capabilities.
If none of these apply (and for most software platforms, none do), the build path costs more, takes longer, and delivers less flexibility than using a payment layer.
The Switching Moment
Most platforms that switch from build-to-buy follow the same pattern:
Trigger 1: The second PSP. The first enterprise customer mandating a different gateway. Building one more integration is feasible. The realisation that there will be a third, fourth, and fifth is what changes the calculus.
Trigger 2: PCI audit scope. The first comprehensive PCI assessment reveals how much infrastructure is in scope and how much it costs to remediate and maintain.
Trigger 3: Channel expansion. The business needs voice payments, or payment links, or AI agent support. Building each from scratch is a multi-month project, or it's already available through a payment layer.
Trigger 4: Engineering frustration. The payments team asks why they're maintaining webhook handlers and PSP integrations instead of building the features that differentiate the platform.
The platforms that recognise these triggers early save the most money. The ones that push through accumulate technical debt until the switching cost feels prohibitive, but the ongoing cost of maintenance usually justifies the switch regardless.
FAQ
We've already built a Stripe integration. Is it too late? No. Merchants with their own Stripe account and API key can connect it to Shuttle. Saved cards stay with the gateway that stored them. The payment layer adds multi-PSP capability, additional channels and white-label tooling alongside what you've built.
Won't adding a payment layer slow down transactions? The transaction still processes through the merchant's own PSP. Shuttle passes the payment to that PSP and tokenises the card with it; it does not add a second processor.
What about our custom checkout design? Shuttle's checkout is white-label, with your logo, colours and domain. Your merchants' customers see your brand, not Shuttle's.
Can we migrate incrementally? Yes. You can route new merchants through Shuttle while existing merchants continue on your direct integration. Over time, you can move existing merchants across to gain transaction and refund data in one format, plus additional channels; saved cards stay with the gateway that stored them. There's no "big bang" migration required.
How do we calculate the real ROI? Add up: engineering headcount dedicated to payments (fully loaded cost), PCI compliance costs (audit, infrastructure, tools), deals delayed or lost due to PSP limitations, and time-to-market for new payment features. Compare to Shuttle's transaction-based pricing.
Stop building payment infrastructure. Start shipping your product. See how platforms use Shuttle to offer 40+ PSPs, multi-channel payments and white-label merchant tools. Shuttle is PCI DSS Level 1, which limits your PCI scope.