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: API Integration with Payment Links

Best for: Platforms wanting programmatic control while maintaining simplicity

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

With this approach, you can:

• Embed OAuth authentication directly in your platform
• Generate payment links via API calls
• Customize payment link parameters dynamically
• Maintain your brand while leveraging Shuttle's payment infrastructure

How it works:

1. Merchants authorize your platform via embedded OAuth
2. Your platform generates payment links programmatically
3. Links are distributed through your existing channels
4. Payment data flows back through webhooks

View Payment Links for Platforms Documentation →

Level 3: Fully Embedded Payments Experience

Best for: Platforms requiring complete control over the payment experience

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

With this approach, you can:

• Provide white-labeled merchant onboarding
• Embed payment forms directly in your platform
• Maintain complete brand consistency
• Offer a seamless, integrated payment experience

How it works:

1. Merchants onboard through your white-labeled flow
2. Payment forms are embedded directly in your UI
3. Customers never leave your platform
4. You maintain full control over the user experience

Explore Embedded Payments for Platforms →

Choosing Your Integration Level

Consider these factors when selecting your approach: