Payments Roadmap Done

For Software Platforms

Your platform needs a payment layer that scales with you, not a build project that owns your roadmap. Shuttle gives you everything required to embed payments across any channel, without becoming a PayFac or losing control.

Developer relaxing at laptop, payments roadmap done

Trusted by leading platforms

Why platforms come to Shuttle

  1. 1

    Enterprise deals start demanding specific PSPs

    Supporting them one-by-one breaks the roadmap.

  2. 2

    Embedded payments become unavoidable

    Becoming a PayFac introduces risk, compliance, and operational drag.

  3. 3

    Payments start leaking into product conversations

    Shuttle exists to remove that pressure, without forcing platforms into trade-offs they'll regret later.

  4. 4

    Every provider works differently

    One integration and one data model across all of them, so your product handles payments the same way whichever provider sits behind a given merchant.

  5. 5

    Payments make the platform harder to leave

    Merchants who take their money through your product have more reason to stay in it, and a fragmented payment experience is what sends them looking elsewhere.

  6. 6

    The card never touches you or Shuttle

    Card details go straight to the gateway. They never reach your platform, and on a call the digits go from the keypad to the gateway without passing the agent. Shuttle keeps no vault of its own: cards are tokenised with the merchant's own gateway and the token stays there. Your PCI scope stays limited, and Shuttle holds PCI DSS Level 1, SOC 2 Type 2 and ISO 27001.

Doing nothing is also a decision, and it usually shows up as lost or delayed deals.

One Payment Layer, Four Pillars

The Shuttle Solution

Design

White-label checkout and merchant experiences that match your brand. Checkout, onboarding and portal carry your logo, colours and domain.

Deploy

Pre-built components and managed infrastructure mean your team focuses on your product, not payments plumbing.

Develop

RESTful APIs, SDKs, and webhooks designed for platform teams. Extend and customise the payment experience.

Support

Merchant support and compliance expertise. Shuttle carries its own PCI DSS Level 1 certification and tracks the regulatory changes, so your scope stays limited.

The Platform Components

What You Get

Shuttle processor selection with PSP logos and connect buttons
Checkout preview generated during onboarding

Onboarding

An embeddable component that lets merchants browse, select, and connect their preferred payment processors, with OAuth or API key authentication built in.

  • 40+ payment processors, connected by OAuth or API key
  • Country-filtered processor availability
  • Fraud prevention & 3D Secure configuration
Integration
<!-- Embed the onboarding widget -->
<div data-shuttle-embed="DEEP_LINK_ID"></div>

<script>
// Or mount programmatically
Shuttle.embed("DEEP_LINK_ID", "#onboarding", {
  max_height: 800
});
</script>

Checkout

An embeddable payment form rendered as an iFrame inside your product. Supports cards and local payment methods with the merchant's logo, colours and domain.

  • Inline or modal display modes
  • Cards & local payment methods
  • PCI DSS Level 1 compliant
Integration
<!-- Embedded checkout with a nonce -->
<div data-shuttle-checkout="CHECKOUT_NONCE"></div>

<script>
// The browser event is a UI cue, not proof of payment.
// Check the origin, then confirm server-side before you fulfil.
window.addEventListener("message", (e) => {
  if (e.origin !== "https://app.shuttleglobal.com") return;
  if (e.data.type !== "PAYMENT_SUCCESS") return;

  // Update the UI now, and verify on your server before fulfilling.
  showConfirmation();
  fetch("/api/payments/" + e.data.paymentId + "/verify", { method: "POST" });
});
</script>

Express Checkout

Render express payment methods like Apple Pay, Google Pay, and PayPal directly in your checkout flow. Wallet buttons appear when a connected processor supports network tokens.

  • Apple Pay & Google Pay wallet buttons
  • PayPal, Affirm & Buy Now Pay Later options (on request)
  • Embeddable BNPL promotional messaging from each provider
  • Loads in the topmost frame for native wallet access
Integration
<!-- Render wallet buttons -->
<div data-shuttle-payment="PAYMENT_CONFIG"
     data-shuttle-signature="HMAC_SIG">
</div>

<script>
// Or trigger programmatically
Shuttle.doPayment(paymentConfig, signature);
</script>

Merchant Activity View

Give merchants real-time visibility into transactions, refunds and payment activity through an embeddable dashboard component.

  • Transaction list with filters & search
  • Account & customer management
  • Scheduled payment monitoring
  • Exportable reporting
Integration
<!-- Embed the activity dashboard -->
<div data-shuttle-embed="ACTIVITY_LINK_ID"></div>

<script>
Shuttle.embed("ACTIVITY_LINK_ID", "#dashboard", {
  max_height: 900
});
</script>
Shuttle merchant portal

Merchant Portal

A white-label portal merchants access independently to manage payments, view reports, handle refunds, and configure their settings.

  • Multi-level organisation structure
  • Payment processor configuration & rules
  • Team management with role-based access
  • Modular app marketplace architecture
🇬🇧
English
Pay Now
🇩🇪
Deutsch
Jetzt bezahlen
🇯🇵
日本語
今すぐ支払う
🇧🇷
Português
Pagar agora
🇸🇦
العربية
ادفع الآن
🇫🇷
Français
Payer maintenant

Translations

Shuttle's embeddable components can be translated into any language: run your checkout in German, onboarding in Japanese, or express payments in Portuguese.

  • Translate embeddable components into any language
  • Your platform, your language

The Numbers

Why use Shuttle vs build it yourself

Building payment infrastructure is expensive, complex, and slow. Shuttle takes most of that off your team.

$360k

Saved in a year by one platform on Shuttle, against building and maintaining the same payment infrastructure itself. One customer, their figure, not an average.

$225k

The average annual PCI DSS Level 1 assessment fee for a Tier 1 merchant, before technology, operating and staff costs (Ponemon Institute / Thales, 2010). Shuttle already holds Level 1, so your platform does not build it.

12 months

Development time that same platform saved by building on Shuttle rather than integrating payment providers itself.

Start with Checkout. Move to Embed when you roll out.

How platforms start

1

Start on the merchant product

If you have a small number of merchants and you are happy for the payment pages to carry Shuttle branding rather than your own, start here. Put them on the same product a merchant buys directly, with Links, Voice or both. Each merchant runs its own Merchant Portal, with its own team, checkout branding and gateway credentials, and you pay per live instance, where an instance is one payment channel: three merchants each taking links is three instances.

2

Roll out with the Embedded Payment Layer

When payments become part of your product, move to Embed: your own checkout, merchant onboarding and experience, white-label, with Voice and Links alongside and no per-instance fees.

Simple, Transparent Pricing

Pricing

Voice Checkout

Card payments over the phone, with your PCI scope limited

$49 /mo per live instance
  • Twilio Pay: $0.20 per transaction, billed through your Twilio account
  • IVR, human agent & AI agent
  • Card capture on the call, with your PCI scope limited
  • 245 Shuttle-billed transactions included every month; Twilio bills its own separately
  • From $0.20 per transaction, falling with volume
  • Works with Twilio today, and any carrier coming soon
Links Checkout

Send payment links via SMS, email, or chat

$49 /mo per live instance
  • Branded payment links
  • SMS, email & chat delivery
  • Real-time payment tracking
  • 245 Shuttle-billed transactions included every month, then from $0.20 per transaction

Ready to embed payments?

Talk to our platform team and see how Shuttle fits your platform.

Book a Call