Shuttle vs Prommt for Platforms and Merchants

By Shuttle Team, March 27, 2026

Two Approaches to Payment Requests

Prommt and Shuttle both help businesses collect payments remotely, through links, messages, and digital channels rather than traditional card-present terminals.

But they serve different audiences and solve different problems.

Prommt is a payment request platform for enterprise merchants. It sends branded payment links via SMS, email, and chat, with a strong focus on Pay by Bank (open banking) for high-value transactions. It sells directly to merchants in verticals like automotive, hospitality, and luxury retail.

Shuttle is a payment layer for platforms and merchants. It supports payment links, voice checkout, open banking, digital wallets, and 40+ PSPs, across embedded, white-label, and direct merchant channels.


Side-by-Side Comparison

Prommt

Shuttle

What it is

Payment request platform for merchants

Payment layer for platforms and merchants

Payment links

SMS, email, web chat, messaging apps

SMS, email, embeddable

Open banking / Pay by Bank

Yes, across multiple European markets via Token.io

Yes, UK

Card payments

Yes: via merchant's existing gateway

Yes: 40+ supported gateways

Voice payments

No: sends a link during the call

Yes: PCI-compliant DTMF capture during the call

AI agent payments

No

Yes: voice and chat agent payment capture

ACH / Direct Debit

Via open banking where available

ACH (US), BACS Direct Debit (UK)

PSP flexibility

Gateway-dependent: uses merchant's existing PSP

40+ PSPs: configured per merchant and payment type

Multi-merchant / platform

Sold direct to merchants

Yes: white-label multi-tenant architecture

White-label

Branded checkout pages

White-label: checkout, portal, onboarding (on the Embedded Payment Layer)

Merchant portal

Prommt dashboard

White-label portal branded as your platform

PCI compliance

PCI DSS Level 1

PCI DSS Level 1 + ISO 27001 + SOC 2

Pricing

Not published on Prommt's website

$49 per live instance per month; on the Twilio Pay Connector, plus from $0.20 per transaction, falling with volume, billed through your Twilio account

Chase / reminders

Automated chase paths with payment method fallback

Link expiry; build your own reminders with Zapier, Make.com or the API

Gateway selection

Rules-based card vs bank routing

By payment method, with each merchant on its own gateway


Where Prommt Wins

Chase paths and payment retry logic

Prommt's automated chase sequences are genuinely well-built. When a payment request goes unpaid, Prommt can send follow-up reminders that offer alternative payment methods: if a card payment fails, the next reminder can default to Pay by Bank. This nudges completion rates up in a way that most payment link tools don't attempt.

Open banking depth in Europe

Prommt has invested heavily in Pay by Bank through Token.io, across multiple European markets. For merchants processing high-value transactions (car sales, luxury goods, property deposits) where card fees become painful, Prommt's open banking coverage across Europe is broader than most competitors.

Vertical-specific integrations

Prommt has built integrations with industry systems: Oracle OPERA for hospitality, dealer management systems for automotive. If you're a hotel or car dealership already running OPERA or a specific DMS, Prommt's pre-built connectors reduce implementation time. These are narrow but deep integrations that horizontal payment tools typically don't have.

High-value transaction optimisation

Prommt is purpose-built for high-value remote payments: car deposits, hotel stays, luxury purchases. The payment experience is designed for transactions where the customer needs reassurance and the merchant needs completion certainty. Smart defaults (Pay by Bank for transactions over a threshold, card for smaller amounts) are configured at the merchant level.


Where Shuttle Wins

Voice payments: capture during the call, not after it

This is the fundamental channel gap.

Prommt's approach to phone payments: the agent sends a payment link during the call, the customer opens it on their phone, completes payment, and confirms back to the agent. It works, but it breaks the conversation flow, adds friction, and depends on the customer having their phone and email accessible.

Shuttle's approach: the customer enters card details via keypad (DTMF) during the call. The agent stays on the line. The digits never reach the agent. Payment completes without leaving the conversation.

For contact centres, debt collection, insurance renewals and hotel reservations (anywhere payments happen during phone calls), voice checkout closes the payment in-call rather than hoping the customer follows a link afterwards.

40+ PSPs vs gateway-dependent

Prommt sits on top of the merchant's existing payment gateway. It doesn't process transactions. It creates a checkout page that routes to whatever gateway the merchant already has.

That suits a merchant with one gateway. Platforms have a different need:

  • Enterprise merchants with PSP mandates are fine, but platforms that want to offer embedded payments across a merchant base need a multi-PSP architecture

Shuttle connects to 40+ PSPs through a single integration. One API, 40+ supported gateways, each merchant on its own.

Platform and multi-merchant architecture

Prommt sells direct to merchants.

Shuttle is designed for platforms that serve hundreds or thousands of merchants: white-label onboarding, per-merchant PSP configuration and branded merchant portals.

If you're a software platform, marketplace, BPO or SaaS company embedding payments for your customers, Shuttle's multi-tenant architecture is built for this.

Published pricing

Prommt does not publish prices on its website.

Shuttle's Links Checkout is $49 per live instance per month. Voice payments on the Twilio Marketplace are $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account.

Payment method coverage

Shuttle covers:

  • Cards (40+ PSPs)

  • Open banking / Pay by Bank (UK)

  • ACH Direct Debit (US)

  • BACS Direct Debit (UK)

  • Apple Pay, Google Pay, PayPal (on request)

  • Affirm (BNPL, on request)

  • Local payment methods via Stripe, Adyen, Mollie (iDEAL, Bancontact, etc.)


When to Choose Prommt

  • You're a single merchant in automotive, hospitality, or luxury retail

  • High-value transactions where Pay by Bank saves significant card fees

  • You need Oracle OPERA or automotive DMS integration

  • Chase paths and automated payment retry are critical to your workflow

  • You need Pay by Bank across multiple European markets

  • You don't need voice payment capture, AI agents, or multi-merchant architecture

When to Choose Shuttle

  • You're a platform, BPO, or SaaS company embedding payments for multiple merchants

  • You need voice payments: capturing card details during calls, not sending links after them

  • You serve merchants with different PSP requirements

  • You want payment links AND voice checkout AND embedded payments from one provider

  • You need white-label everything: checkout, portal, onboarding

  • You want Apple Pay, Google Pay, BNPL, and local payment methods alongside cards and bank transfers

When to Use Both

Shuttle is PSP-agnostic: if a merchant's transactions route through a gateway that Prommt connects to, both can coexist. In practice, Shuttle's payment links overlap with Prommt's payment requests. The question is whether Prommt's chase paths and European open banking coverage matter for your use case.


FAQ

Is Shuttle a direct competitor to Prommt?

Shuttle overlaps with Prommt on payment links: both let merchants send branded payment requests via SMS, email, and messaging. But Shuttle also covers voice payments, embedded checkout, AI agent payments, and multi-PSP platform architecture. Prommt is a payment request tool. Shuttle is a payment layer.

Does Shuttle support Pay by Bank / open banking?

Yes. Shuttle supports open banking (Pay by Bank) in the UK, alongside cards, ACH, BACS, digital wallets, and BNPL. Prommt currently has broader European open banking coverage through Token.io.

Can Shuttle replace Prommt for car dealerships?

Yes. Shuttle's payment links for car dealerships cover the same use case: sending branded payment requests for deposits, balances, and F&I products. Plus voice checkout for customers who call to pay, and Apple Pay / Google Pay for faster completion. See the automotive guide for the full breakdown.

What about Prommt's chase paths?

Prommt's automated follow-up sequences are a strong feature. Shuttle has no built-in chasing: it supports link expiry, and you can build your own reminder schedule with Shuttle payment links and Zapier, Make.com or the API. If chase automation with payment method fallback is critical, Prommt is built for it.

How does pricing compare for high-value transactions?

Prommt does not publish prices on its website, so compare quotes directly. Shuttle's Links Checkout is $49 per live instance per month, and both support open banking for high-value payments where card fees bite.



Need more than payment requests?

Shuttle gives you payment links, voice checkout, open banking, and 40+ PSPs, with white-label branding and multi-merchant architecture. See pricing.

See Payment Links | See Voice Checkout | Book a Demo

Talk to us

See how Shuttle can power payments for your platform: multi-PSP, multi-channel and white-label.