Platform Integration Approaches

When integrating Shuttle into your platform, you have three distinct approaches available, each offering different levels of control and implementation complexity. This guide helps you choose the right integration strategy for your platform's needs.

Overview

Shuttle offers a layered approach to integration, allowing platforms to start simple and evolve their integration as their needs grow. Whether you're looking for a zero-code solution or a fully white-labeled payments experience, we have an approach that fits.

Integration Levels

Level 1: Zero-Code Integration via Workflow Automation

Best for: Platforms with no available engineering capacity or needing rapid deployment

• Implementation Time: Hours to days
• Technical Requirements: None - no developers needed
• Tools: Make/Zapier (manual setup per merchant) or Cyclr (template-based scaling)

With this approach, you can:

• Generate payment links automatically based on triggers in your system
• Send payment links via email or SMS
• Track payment completion and trigger fulfillment actions
• Onboard merchants without writing any code

How it works:

1. An action occurs in your software (e.g., invoice created)
2. Workflow automation generates a Shuttle payment link
3. Link is sent to the customer
4. Payment completion triggers your fulfillment process

Learn more about Zero Integration Onboarding →

Level 2: Payment Links for Platforms

Best for: Platforms where merchants have (or can set up) their own Shuttle account

• Implementation Time: Days to weeks
• Technical Requirements: API integration capabilities
• Key Features: OAuth connect, programmatic payment link generation

Merchants set up and manage their own Shuttle account through the Shuttle Merchant Portal — including their branding, domain, and payment processor setup. They then connect their account to your platform via OAuth.

With this approach, you can:

• Connect to merchants' existing Shuttle accounts via OAuth
• Generate payment links on behalf of connected merchants via API
• Send customers to Shuttle-hosted checkout pages
• Receive webhook notifications when payments complete

How it works:

1. Merchant sets up their Shuttle account in the Merchant Portal
2. Merchant connects their account to your platform via OAuth
3. Your platform generates payment links on their behalf
4. Customers are directed to Shuttle-hosted checkout
5. Payment data flows back through webhooks

View Payment Links for Platforms Documentation →

Level 3: Embedded Payments for Platforms

Best for: Platforms requiring complete control over the payment experience with no visible Shuttle branding

• Implementation Time: Weeks
• Technical Requirements: Full development team
• Key Features: White-labeled everything, deep API integration

The platform owns the entire payment experience. Merchants are provisioned by the platform and never interact with Shuttle directly — they may not know Shuttle is involved at all.

With this approach, you can:

• Provision merchant accounts programmatically
• Embed payment forms and onboarding flows directly in your platform
• White-label the full payment experience under your brand
• Access the complete Merchant Instance API on behalf of any merchant you manage

How it works:

1. Your platform provisions merchant instances via the Platform API
2. Payment forms and onboarding are embedded directly in your UI
3. Customers complete payment without leaving your platform
4. You maintain full control over the user experience

View Embedded Payments for Platforms Documentation →

Choosing Your Integration Level

Consider these factors when selecting your approach: