Our Products
Embed the payment layer, or create payment channels
Embed it into your own product, or run it yourself. Connect a compatible payment gateway to a channel.
For Software Platforms
Shuttle for Platforms
Embed payments into your own product, across every channel your merchants need, without becoming a PayFac.
Voice Checkout
Card payments taken inside the call, with people or AI agents.
Links Checkout
A hosted checkout you send as a link.
Embedded Payment Layer
Payments built into your own product, white-label.
For Merchants and platforms starting out
Shuttle for Merchants
Take payments yourself, by link or on the phone, on any compatible gateway you already use.
Links Checkout
A hosted checkout you send as a link.
Voice Checkout
Card payments taken inside the call.
One is fine. Three is untenable.
Building payment provider integrations yourself
One provider
Fine
Read their docs, build it, ship it. A known piece of work with an end to it.
- 1 data model
- 1 set of rules
Two providers
A nuisance
The second one does everything its own way. You write the same feature twice, and you fix it twice every time either provider changes something.
- 2 data models
- 2 sets of rules
- Translation matrix
Three providers
Untenable
Three sets of docs, three different ways to describe a refund, three support contacts to chase. And if the card data passes through you, so does the PCI scope.
- 3 data models
- Translation nightmare
- 3 relationships
- SAQ-D, if cards pass through you
Shuttle is the layer that makes it one integration instead. Run more than one provider at a time, send each payment method to its own gateway, and keep the providers you already have. Why we built it that way →
Talk to us
Not sure which is right for you? Tell us how you take payments today, and we'll point you to the right product.
Book a Call