--- URL: https://www.shuttleglobal.com/adyen-vs-stripe/ --- # Redirecting to: /blog/adyen-vs-stripe/ ## Links - [Redirecting from to](/blog/adyen-vs-stripe/) --- URL: https://www.shuttleglobal.com/alternatives/adyen-for-platforms/ --- # Adyen for Platforms Alternatives | Shuttle > Why Platforms Look for Adyen for Platforms Alternatives Adyen for Platforms is a serious product. # Adyen for Platforms Alternatives By Shuttle Team, February 20, 2026 ## Why Platforms Look for Adyen for Platforms Alternatives Adyen for Platforms is a serious product. It's built for scale, backed by strong global acquiring, and handles complex multi-party payment flows for some of the world's largest marketplaces. For enterprise platforms committed to Adyen as their sole processor, it delivers. But commitment to a single processor is exactly where the problems start. Platforms look for alternatives when they hit one or more of these walls: ### PSP Lock-In Every merchant on Adyen for Platforms processes through Adyen. If a large customer has a negotiated Worldpay contract with interchange-plus rates they've spent months optimising, you can't support them. If you want to route domestic UK transactions through a local acquirer for better authorisation rates, you can't. Adyen is both the infrastructure and the processor -- and like Stripe Connect, they have no incentive to support alternatives. ### Complexity and Time to Market Adyen's integration is enterprise-heavy. The documentation is thorough but dense, the onboarding flow requires significant custom development, and the path from signed contract to live integration typically takes months -- not weeks. For platforms with deals waiting, that timeline costs real revenue. ### No Multi-Channel Adyen for Platforms covers online checkout and in-store POS. It doesn't natively support voice payments, IVR payment capture, payment links with platform branding, or AI agent payment flows. Platforms needing these channels must integrate third-party solutions alongside Adyen -- creating separate PCI surfaces, additional engineering complexity, and fragmented reporting. ### Sales-Led, Enterprise-Only Adyen doesn't offer self-serve access. There's no sandbox you can spin up in five minutes. The process starts with a sales call, moves through commercial negotiation, and requires minimum volume commitments. Mid-market platforms -- processing millions, not billions -- often find themselves outside Adyen's sweet spot. ### Limited White-Label Adyen's merchant dashboard is Adyen-branded. The onboarding experience is functional but not designed to disappear behind your platform's brand. For platforms that want payments to feel like a native feature -- not a redirect to a third-party portal -- this creates friction with merchants who expect a unified experience. ## What to Evaluate in an Alternative Before comparing specific alternatives, clarify what you need: PSP flexibility: Do your merchants need to use specific gateways? If yes, you need PSP-neutral infrastructure -- not another single-PSP solution. Channel coverage: Do you need voice, payment links, or AI agent payments -- or just checkout? This filters out many alternatives immediately. White-label: How important is it that payments look and feel like your product, not a third party's? Speed to market: Are deals waiting? If you need to be live in weeks, not months, pre-built components matter. Compliance: Do you want to carry PCI compliance or have a provider handle it? Accessibility: Do you need self-serve access and fast iteration, or are you comfortable with a sales-led, enterprise procurement cycle? ## The Alternatives ### 1. Stripe Connect What it is: Stripe's platform payments solution. An aggregator model where the platform acts as the master account, with Connected Accounts for each sub-merchant. Well-documented, developer-friendly, and the most common starting point for platform payments. Strengths: - Best-in-class developer experience and documentation - Fast time to market -- sandbox in minutes, live in days to weeks - Large ecosystem of tools, plugins, and integrations - Self-serve access and transparent pricing - Strong no-code options (Express accounts, hosted onboarding) Limitations: - Same single-PSP problem. Stripe Connect means using Stripe as the processor. You've swapped Adyen lock-in for Stripe lock-in. - Merchants can't bring their own PSP - No voice payments, IVR, or AI agent payment infrastructure - Geographic gaps in some markets (Southeast Asia, Africa, parts of Latin America) - Pricing pressure at high volume Best for: Platforms that need fast time to market and strong DX -- and are comfortable with single-PSP lock-in, just with Stripe instead of Adyen. ### 2. Payment Orchestration (Primer, Spreedly) What it is: Middleware that routes transactions across multiple PSPs. Gives you multi-PSP connectivity, failover, and tokenisation through a single integration. - Multi-PSP routing and failover - PSP-agnostic tokenisation (especially Spreedly's vault) - Smart routing for authorisation rate optimisation - Primer: visual workflow builder, no-code routing rules - Spreedly: deep vault infrastructure, 120+ connections - Merchant-facing, not platform-facing. These are tools for merchants to optimise their own payment stack -- not tools for platforms to embed payments for their merchants. - No white-label merchant onboarding or portal - No voice payments, payment links, or AI agent infrastructure - Heavy engineering lift -- Spreedly in particular is flagged by users as complex to integrate - You still need to build checkout, onboarding, reporting, and merchant management yourself Best for: Large enterprises that already have PSP relationships and want to optimise routing between them. Not a like-for-like Adyen for Platforms replacement for platforms. ### 3. PayFac-as-a-Service (Payrix, Finix) - More control over merchant underwriting and pricing - Faster than building PayFac from scratch - Still typically single-PSP. Most PFaaS solutions process through a single acquirer. - Compliance obligations remain -- you're still operating as a PayFac (albeit a managed one) - Regulatory burden scales with your merchant base - No multi-channel coverage (voice, links, AI) - Slower to market than pre-built payment layers Best for: Platforms where payment revenue is a primary business model and you want maximum margin -- and you're willing to accept the compliance overhead. ### 4. PSP-Neutral Payment Layer (Shuttle) What it is: A payment layer that embeds multi-PSP payment infrastructure into your platform. White-label checkout, merchant onboarding, management portal, and multi-channel support -- all through a single integration. - PSP-neutral: 40+ gateways. Merchants choose their PSP or you assign one. Enterprise customers bring their Worldpay/Stripe/Checkout.com account without friction. - Multi-channel: Embedded checkout, voice payments, payment links, chat, and AI agent payments -- all through the same integration. - White-label everything: Checkout, onboarding, merchant portal -- branded as your platform, not as Shuttle. - PCI compliance included: PCI DSS Level 1 + ISO 27001 + SOC 2. Your PCI scope is effectively zero. - Live in weeks: Pre-built components, not a multi-month enterprise integration project. - Lower per-transaction margin than full PayFac ownership - Less transaction-level routing optimisation than dedicated orchestration platforms - Newer entrant -- smaller brand recognition than Stripe or Adyen Best for: Platforms that need to embed payments for their merchants, support multiple PSPs, and go live quickly -- without becoming a payments company. ## Comparison Matrix Stripe Connect Orchestration (Primer/Spreedly) PFaaS (Payrix/Finix) Payment Layer (Shuttle) PSP flexibility Stripe only Usually single White-label onboarding Partial (Express) Merchant portal Stripe Dashboard White-label portal Voice payments Payment links AI agent payments PCI compliance Stripe carries it Partial (varies) Fully included Time to market Days-weeks Weeks-months Self-serve access Standard marketplace payments Routing optimisation Max payment revenue Multi-PSP platform payments ## Making the Decision Stay with Adyen for Platforms if: - All merchants are happy processing through Adyen - No customers require alternative PSPs or have existing gateway contracts - You only need online checkout and in-store POS (no voice, links, AI) - Adyen's enterprise sales process and timeline work for your business - You have the engineering resource for a months-long integration - Volume justifies Adyen's minimum commitments Move to an alternative if: - Enterprise customers mandate their own PSP - You need voice payments, payment links, or AI agent payment channels - You want to be live in weeks, not months - Mid-market deal flow means you can't wait for Adyen's sales cycle - You need white-label merchant experiences that look like your platform - You want PSP negotiating leverage -- the ability to move volume between processors ## FAQ Can I migrate from Adyen for Platforms without disrupting existing merchants? Yes. Most alternatives (including Shuttle) can connect to Adyen as one of their supported gateways. Existing merchants continue processing through Adyen while new merchants (or those requiring different PSPs) use alternative gateways. The transition is additive, not disruptive. Is Adyen for Platforms really "locked in"? Yes, architecturally. Every sub-merchant on Adyen for Platforms processes exclusively through Adyen's acquiring network. There's no multi-PSP option within the product. Adyen's business model depends on being the processor, not just the infrastructure. How does Adyen for Platforms compare to Stripe Connect? Both solve the same problem -- platform payments -- but with different trade-offs. Stripe Connect has better DX, faster time to market, and self-serve access. Adyen for Platforms has stronger enterprise acquiring, unified commerce (online + POS), and better multi-currency support. Both lock you into a single PSP. The choice between them is often about which processor's strengths matter more -- but neither solves PSP flexibility. What if I only need Adyen plus one other PSP? That's a common starting point. A PSP-neutral payment layer lets you keep Adyen for merchants who prefer it while adding Stripe, Worldpay, or any other gateway for those who require it -- all through a single integration and a unified merchant experience. ## Related Reading - Shuttle vs Adyen for Platforms -- the detailed feature comparison - Shuttle vs Stripe Connect -- if you're considering Stripe instead - When Your SaaS Outgrows Stripe Connect -- a migration playbook (the same principles apply when outgrowing Adyen) - Shuttle vs Checkout.com for Platforms -- if you're considering Checkout.com - Shuttle vs Worldpay for Platforms -- if you're considering Worldpay - PayFac Alternatives for Platforms -- if you're considering the PayFac route - Payment Orchestration Alternatives -- if you're considering Primer, Spreedly, or Gr4vy - Virtual Terminal Payments: replacing a bundled virtual terminal without changing your merchant account Outgrowing Adyen for Platforms? Shuttle gives your platform 40+ PSPs through a single integration -- with white-label checkout, voice payments, payment links, and AI agent support. Your enterprise customers bring their own gateway. PCI DSS Level 1 compliance included. Live in weeks, not months. Book a Demo | See How It Works Explore More ### Shuttle vs Adyen for Platforms ### Embedded Payments for ERP Platforms ### How to Connect Adyen to Twilio for Voice & IVR Payments ### PCI Compliance Cost for Platforms: What It Really Costs in 2026 ### PCI-Compliant Payment Architecture for Insurance Platforms ### Adyen vs Worldpay: Which PSP for Your Platform? ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [look for alternatives](/guides/when-saas-outgrows-stripe-connect/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Shuttle vs Checkout.com for Platforms](/vs/checkout-com/) - [Shuttle vs Worldpay for Platforms](/vs/worldpay/) - [PayFac Alternatives for Platforms](/alternatives/payfac/) - [Payment Orchestration Alternatives](/alternatives/payment-orchestration/) - [Virtual Terminal Payments](/guides/virtual-terminal-payments/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [GuideEmbedded Payments for ERP Platforms→](/guides/payments-for-erp-platforms/) - [GuideHow to Connect Adyen to Twilio for Voice & IVR Payments→](/guides/adyen-twilio-integration/) - [GuidePCI Compliance Cost for Platforms: What It Really Costs in 2026→](/guides/pci-compliance-cost-platforms/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [GuideAdyen vs Worldpay: Which PSP for Your Platform?→](/guides/adyen-vs-worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/checkout-com/ --- # Checkout.com Alternatives for Platforms | Shuttle > Why Platforms Look for Checkout.com Alternatives Checkout.com is a legitimate enterprise PSP. # Checkout.com Alternatives for Platforms By Shuttle Team, February 23, 2026 ## Why Platforms Look for Checkout.com Alternatives Checkout.com is a legitimate enterprise PSP. It has strong acquiring infrastructure, intelligent routing for authorisation rate optimisation, and global coverage that makes it a credible choice for large direct merchants. For e-commerce businesses and enterprise brands processing at volume, it competes seriously. The problem is that Checkout.com was built for merchants -- companies that accept payments directly. It was not built for platforms -- companies that embed payment acceptance for their customers. That distinction matters, and it is where platforms consistently run into walls. ### Single-PSP Architecture Every transaction processed through Checkout.com goes through Checkout.com. There are no multi-PSP options, no ability for a platform's merchants to bring existing gateway relationships, and no flexibility to route different merchant segments through different processors. If you have an enterprise customer who has spent months negotiating a Worldpay contract with interchange-plus pricing, Checkout.com cannot accommodate them. The infrastructure assumes a single processor -- and that processor is Checkout.com. For direct merchants, this is a non-issue. For platforms serving dozens or hundreds of merchants with varied requirements, it is a structural constraint that creates friction with every enterprise deal. ### No Platform Tooling Checkout.com has no white-label merchant onboarding. No merchant management portal. No sub-merchant account model designed for platforms to manage a portfolio of merchants. The product is designed for a single business processing its own payments -- not for a platform embedding payment acceptance for others. Building these capabilities in-house is possible, but it means months of engineering work on infrastructure that is not your core product. The result is typically a bespoke merchant portal that creates ongoing maintenance overhead, PCI compliance complexity, and technical debt every time Checkout.com updates its API. ### Pricing Opacity Checkout.com's pricing is enterprise-custom. There is no published rate card. Prospective customers enter a sales process and receive a commercial proposal based on negotiated terms. For platforms evaluating infrastructure options on a tight timeline, this creates friction -- you cannot model unit economics without getting to the end of a sales cycle. "Checkout.com pricing" and "Checkout.com fees" are among the highest-volume search queries attached to the brand. That volume is a signal: prospective customers are struggling to understand what they will pay. Platforms building financial models for payment feature roadmaps need more transparency than Checkout.com's process typically provides upfront. ### Enterprise-Merchant Focus ### Limited Channel Coverage Checkout.com's core product is online checkout. For platforms that need payment links, voice payments, IVR capture, chat-based payments, or AI agent payment flows, Checkout.com requires supplementary integrations with separate providers. Each additional channel means additional PCI surface, additional engineering effort, and fragmented reporting across systems that were never designed to work together. ## What to Evaluate in an Alternative Not every alternative addresses the same problems. Before committing to a new direction, clarify which constraints matter most for your platform: PSP flexibility: If your merchants have existing gateway contracts or will mandate specific processors, you need PSP-neutral infrastructure -- not another single-PSP solution. Swapping Checkout.com lock-in for Stripe lock-in solves a vendor problem, not an architecture problem. White-label platform tooling: Merchant onboarding, merchant portal, and checkout experiences should look and feel like your platform. Evaluate whether an alternative provides genuinely white-label tooling or just co-branded overlays. Channel coverage: List the payment channels you need today and the ones you are likely to need in the next two years. Voice payments, AI agents, and payment links are increasingly part of platform RFPs. Rebuilding infrastructure for each new channel is expensive. Compliance posture: Determine whether you want to carry PCI compliance obligations or have a provider handle them. The difference between inheriting PCI scope and having a partner carry it can change both your engineering requirements and your security audit timeline. Pricing transparency: You need to model unit economics before committing to infrastructure. Prioritise alternatives that publish rates or provide clear pricing frameworks early in the evaluation process. Time to market: If deals are waiting on your payment feature, evaluate integration timelines honestly. A months-long enterprise integration process has a real cost in delayed revenue. ## The Alternatives ### 1. PSP-Neutral Payment Layer (Shuttle) What it is: A payment infrastructure layer that embeds multi-PSP payment acceptance into your platform. Shuttle connects to 40+ gateways -- including Checkout.com -- and provides white-label checkout, merchant onboarding, merchant portal, and multi-channel support through a single integration. Strengths: - PSP-neutral by design: Merchants choose their preferred gateway or you assign one. Enterprise customers bring their existing Checkout.com, Worldpay, or Stripe accounts without disruption to platform infrastructure. - White-label everything: Checkout flows, onboarding journeys, and merchant portals are branded as your platform -- not as Shuttle. - Multi-channel: Embedded checkout, voice payments, IVR capture, payment links, chat, and AI agent payments through a unified integration. - PCI compliance included: PCI DSS Level 1 certified, ISO 27001, and SOC 2. Your PCI scope is materially reduced. - Live in weeks: Pre-built components designed for platform integration -- not a multi-month custom engineering engagement. - Checkout.com as an option, not a mandate: Merchants who want Checkout.com keep it. Merchants who need something different get it. Limitations: - Per-transaction margin is lower than operating your own PayFac - Shuttle has less brand recognition than Stripe or Adyen - Advanced transaction-level routing optimisation is less configurable than dedicated orchestration middleware Best for: Platforms that need to embed payments for their merchant base, support PSP flexibility, and reach market quickly -- without building or maintaining payment infrastructure themselves. ### 2. Adyen for Platforms What it is: Adyen's solution for platforms and marketplaces. A unified commerce infrastructure that handles sub-merchant onboarding, split settlements, and multi-party payment flows at enterprise scale. - Enterprise-grade global acquiring with strong authorisation rates - Unified online and in-store (POS) coverage - Robust compliance and KYC/KYB infrastructure for merchant onboarding - Deep reporting and reconciliation tooling - Strong multi-currency and cross-border support - Single-PSP lock-in. Every merchant on Adyen for Platforms processes through Adyen. PSP flexibility does not exist within the product. - Enterprise-only go-to-market -- minimum volume commitments, sales-led process, months to go live - No voice payments, payment links, or AI agent infrastructure natively - Adyen-branded merchant experience -- limited white-label flexibility - Integration complexity requires significant engineering investment Best for: Enterprise platforms with committed Adyen relationships, high transaction volumes, and merchants who are content processing exclusively through Adyen. Not suitable for platforms with PSP flexibility requirements. ### 3. Stripe Connect What it is: Stripe's platform payments product. An aggregator model where the platform holds a master account and merchants connect as sub-accounts. The most widely adopted starting point for platform payment features. - Best-in-class developer experience and API documentation - Fast time to market -- sandbox accessible in minutes, live in days to weeks - Self-serve access and transparent published pricing - Large ecosystem of pre-built integrations, plugins, and tools - Strong hosted onboarding (Express and Standard accounts) - Reliable uptime and global coverage in most major markets - Single-PSP lock-in -- same structural problem as Checkout.com. Stripe Connect means Stripe as the processor. Enterprise customers cannot bring their existing gateway relationships. - No voice payments, IVR, or AI agent payment infrastructure - Geographic gaps in Southeast Asia, Africa, and parts of Latin America - Pricing pressure at high volume relative to negotiated enterprise rates - White-label limitations -- Stripe Dashboard remains Stripe-branded for merchants Best for: Platforms prioritising developer experience and speed to market, comfortable with Stripe as the sole processor for all merchants. ### 4. Building In-House What it is: Directly integrating with one or more PSPs, building your own merchant onboarding flow, portal, and checkout infrastructure -- either to become a registered PayFac or to aggregate under a master merchant account. - Full control over the merchant experience - Maximum flexibility in PSP selection and routing logic - Highest per-transaction economics if you operate as a PayFac - Time and cost. A production-ready platform payments stack -- with compliant onboarding, white-label checkout, merchant portal, reconciliation, and PCI-scoped architecture -- typically takes 12-24 months and significant engineering headcount. - PCI obligations. Building in-house means owning PCI scope. PCI DSS compliance for a platform is an annual audit commitment, not a one-time certification. - Regulatory complexity. Depending on your model, operating as a PayFac introduces licensing and compliance obligations that compound as your merchant base grows. - Ongoing maintenance. Every PSP API update, every compliance requirement change, every new payment method your merchants want -- these become your engineering team's problem indefinitely. - Distraction from core product. Payments infrastructure engineering is a significant sustained investment in something that is not your product. Best for: Platforms where payments are the core product and you have the engineering capacity, compliance expertise, and timeline to do it properly. Not a realistic near-term option for most platforms. ## Comparison Matrix Adyen for Platforms Stripe Connect Build In-House PSP flexibility Adyen only Stripe only Your choice White-label checkout Yes (you build it) Merchant onboarding White-label included Yes (hosted) You build it Merchant portal Adyen-branded Stripe Dashboard Voice payments Possible (custom build) Payment links AI agent payments PCI compliance Fully included Stripe carries it You carry it Time to market Days-weeks 12-24 months Self-serve access Enterprise PSP mandates Not supported ## Making the Decision Checkout.com may still be the right choice if: - You are a direct merchant (not a platform) with high transaction volume optimising for authorisation rates - You only need online checkout and are not embedding payments for third-party merchants - You have the budget for enterprise-custom pricing and the timeline for a sales-led process - Your volume justifies the commercial negotiation cycle Look at alternatives if: - You are building a platform that embeds payment acceptance for your customers - Any merchant will require a specific PSP or has an existing gateway contract - You need voice payments, payment links, or AI agent payment channels - You need white-label merchant onboarding and a portal that looks like your product - You need to model unit economics before committing to infrastructure - You need to be live in weeks, not at the end of a multi-month enterprise sales cycle - You want to avoid carrying PCI compliance obligations in-house The consistent pattern across platforms evaluating Checkout.com is the same: it is a strong direct merchant PSP that was not designed for the platform use case. The gap is structural, not a configuration problem. ## FAQ Can I keep using Checkout.com for existing merchants while adding other PSPs for new ones? Yes. A PSP-neutral payment layer like Shuttle supports Checkout.com as one of its 40+ connected gateways. Merchants already on Checkout.com continue processing through it unchanged. New merchants -- or those requiring a different PSP -- are connected to the appropriate gateway. The transition is additive rather than disruptive, and your existing Checkout.com relationships remain intact. Is Checkout.com genuinely more expensive than alternatives, or is that just perception? Checkout.com uses enterprise-custom pricing, so direct comparison is difficult without going through their sales process. What is documentable is that "Checkout.com pricing" and "Checkout.com fees" are high-volume search queries relative to the brand's market size -- which suggests that fee clarity is a persistent friction point for prospective customers. In practice, whether Checkout.com's rates are competitive depends entirely on the terms negotiated, your volume profile, and what you are comparing them against. The opacity is the primary issue, not necessarily the underlying rates. How does Checkout.com compare to Adyen for platform use cases? Both face the same structural limitation for platforms: single-PSP lock-in and no native platform tooling. Checkout.com is generally considered stronger on intelligent routing and authorisation rate optimisation. Adyen for Platforms has more developed infrastructure specifically for multi-party payment flows and sub-merchant management. Neither solves PSP flexibility. For platforms, the more relevant question is whether either of these single-PSP solutions fits the use case -- or whether PSP-neutral infrastructure is the right architecture. See the Shuttle vs Adyen comparison for a detailed breakdown. What happens to my PCI compliance obligations if I move to a platform payment layer? With a fully-hosted, PCI DSS Level 1 certified payment layer, your PCI scope drops sharply for the payment components handled by the provider. You are not storing, processing, or transmitting cardholder data in your own infrastructure. This is materially different from building integrations directly against PSP APIs, where your integration touchpoints can pull your platform into PCI scope. The specific scope reduction depends on your integration architecture -- your QSA can confirm the final scope. Can a platform payment layer support voice payments and AI agent payments alongside online checkout? Yes -- this is one of the primary reasons platforms evaluate PSP-neutral layers over single-PSP solutions. Shuttle covers embedded checkout, voice payments (including IVR capture), payment links, chat, and AI agent payments through a single integration and unified reporting. Adding a new payment channel does not require a separate PSP integration or a separate PCI surface. How long does it realistically take to go live with a platform payment layer? The timeline depends on integration complexity and how many pre-built components you use. Platforms using Shuttle's pre-built checkout, onboarding, and portal components typically go live in weeks. Custom integrations with complex existing infrastructure take longer. The key differentiator from enterprise PSP alternatives is that there is no minimum-volume sales cycle before you can access a sandbox environment -- you can start building and validating the integration before commercial terms are finalised. ## Related Reading - Shuttle vs Checkout.com for Platforms -- the detailed feature comparison - Shuttle vs Adyen for Platforms -- comparing the two enterprise PSP options - Adyen for Platforms Alternatives -- if you are also evaluating Adyen - Stripe Connect Alternatives for Platforms -- the parallel analysis for Stripe - PSP-Neutral vs Single-PSP Architecture -- the structural trade-offs explained - Enterprise PSP Mandates: How Platforms Handle Them -- why PSP flexibility is a deal-level issue for enterprise sales Evaluating Checkout.com for your platform? Shuttle gives platforms 40+ PSPs through a single integration -- including Checkout.com as a supported gateway. White-label checkout, merchant onboarding, merchant portal, and voice and AI agent payment support. PCI DSS Level 1 compliance included. Enterprise customers bring their own gateway. Live in weeks. Book a Demo | See How It Works for Platforms Explore More ### How to Connect Checkout.com to Twilio for Voice & IVR Payments ### Shuttle vs Checkout.com for Platforms ### Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### Agent-Native Checkout: Why AI Commerce Needs New Payment APIs ### Agentic Commerce: How AI Will Rewrite the Checkout ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Shuttle vs Adyen comparison](/vs/adyen/) - [Shuttle vs Checkout.com for Platforms](/vs/checkout-com/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [Adyen for Platforms Alternatives](/alternatives/adyen-for-platforms/) - [Stripe Connect Alternatives for Platforms](/alternatives/stripe-connect/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates: How Platforms Handle Them](/guides/enterprise-psp-mandates/) - [Book a Demo](/discovery/) - [See How It Works for Platforms](/platforms/) - [GuideHow to Connect Checkout.com to Twilio for Voice & IVR Payments→](/guides/checkout-com-twilio-integration/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [BlogPayment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account→](/blog/payment-links-for-checkout-com/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/ --- # Payment Platform Alternatives | Shuttle > Looking for alternatives to Stripe Connect, Spreedly, or Primer? Compare Shuttle for embedded payments, multi-PSP coverage, and white-label payment infrastructure. # Payment platform alternatives Alternatives Exploring alternatives to popular payment platforms. Find the right fit for your platform. Why Businesses Look for Prommt Alternatives Prommt is a payment request platform built for enterprise merchants -- particularly car dealerships, hotels,... Why Platforms Look for Checkout.com Alternatives Checkout.com is a legitimate enterprise PSP. Why Platforms Look for Worldpay Alternatives Worldpay has always occupied a particular position in the payments industry: enormous reach, deep acquiring... The Problem Insurance Platforms Face Insurance core platforms manage the entire policy lifecycle -- quoting, binding, billing, claims. Why Platforms Look Beyond Payment Orchestration Payment orchestration platforms solve a real problem -- for merchants. Why Platforms Look for PayFac Alternatives Becoming a payment facilitator is the most powerful way to control payment economics on your platform. Why Platforms Look for Adyen for Platforms Alternatives Adyen for Platforms is a serious product. Why Platforms Look for Stripe Connect Alternatives Stripe Connect is an excellent product. ## Also Explore Related Content ### Payment Guides In-depth guides on payments infrastructure, voice payments, and platform strategy. 186 guides ### Comparisons See how Shuttle compares to Stripe Connect, Spreedly, and other platforms. 10 comparisons ## Links - [Prommt Alternatives for Platforms and Merchant Payment Collection](/alternatives/prommt/) - [Read more](/alternatives/prommt/) - [Checkout.com Alternatives for Platforms](/alternatives/checkout-com/) - [Read more](/alternatives/checkout-com/) - [Worldpay Alternatives for Platforms](/alternatives/worldpay/) - [Read more](/alternatives/worldpay/) - [Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac](/alternatives/insurance-payment-solutions/) - [Read more](/alternatives/insurance-payment-solutions/) - [Payment Orchestration Alternatives for Platforms](/alternatives/payment-orchestration/) - [Read more](/alternatives/payment-orchestration/) - [PayFac Alternatives for Platforms](/alternatives/payfac/) - [Read more](/alternatives/payfac/) - [Adyen for Platforms Alternatives](/alternatives/adyen-for-platforms/) - [Read more](/alternatives/adyen-for-platforms/) - [Stripe Connect Alternatives for Platforms](/alternatives/stripe-connect/) - [Read more](/alternatives/stripe-connect/) - [Payment Guides In-depth guides on payments infrastructure, voice payments, and platform strategy. 186 guides](/guides/) - [Comparisons See how Shuttle compares to Stripe Connect, Spreedly, and other platforms. 10 comparisons](/vs/) --- URL: https://www.shuttleglobal.com/alternatives/insurance-payment-solutions/ --- # Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac | Shuttle > The Problem Insurance Platforms Face Insurance core platforms manage the entire policy lifecycle -- quoting, binding, billing, claims. # Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac By Shuttle Team, February 21, 2026 ## The Problem Insurance Platforms Face Insurance core platforms manage the entire policy lifecycle -- quoting, binding, billing, claims. But when it's time to collect a premium, settle a claim payment, or process a renewal, the platform hands off to someone else. The carrier handles payment collection separately. Or the platform builds a brittle integration to one PSP that breaks the moment a second carrier needs a different processor. For PAS vendors and MGA platforms specifically, see Payments for Insurance Carriers and MGA Platforms. This page compares the four approaches insurance platforms use to add payment execution -- and explains which one fits the multi-carrier, multi-channel reality of modern insurance. ## The Four Approaches ### 1. Direct Gateway Integration Integrate directly with a payment gateway -- Stripe, Adyen, Worldpay -- and build payment flows into the platform. What you get: - Full control over the payment experience - Direct relationship with the PSP - Well-documented APIs What you don't get: - Multi-PSP support (each carrier's PSP requires a separate integration) - Voice payment capability (gateways are checkout-page-centric) - PCI scope management (the platform handles card data) - Multi-tenant architecture (gateways serve merchants, not platforms) Time to live: 2-4 months per PSP PCI scope: Platform carries it -- SAQ-D, annual QSA audit Carrier flexibility: One PSP per integration. 10 carriers = 10 integrations. ### 2. PayFac Model Become a Payment Facilitator -- either through a full PayFac licence or via Stripe Connect, Adyen for Platforms, or a managed PayFac service. - Control over merchant onboarding - Unified experience for carriers - Carrier PSP flexibility (carriers mandate their PSP -- they won't switch to yours) - Fast time to market (6-18 months for full PayFac, 3-6 months for managed) - Low compliance overhead (the platform takes on PCI, AML, KYC obligations) - Voice payment channels Time to live: 6-18 months PCI scope: Platform owns it -- plus AML/KYC, risk management Carrier flexibility: None. Carriers must use the platform's PSP. For most insurance platforms, the PayFac model fails on the first constraint: carriers won't abandon their existing processor. See Embedded Payments Without Becoming a PayFac. ### 3. Payment Orchestrator Use an orchestration platform -- Primer, Spreedly -- to abstract multiple PSP connections behind a single API. - Multi-PSP routing through one integration - Retry and provider configuration - Unified reporting across PSPs - Voice payment support (orchestrators are checkout-page-centric) - Payment links for premium collection - White-label merchant onboarding - Multi-tenant architecture designed for platforms - PCI scope reduction (the platform still handles card data in most orchestration setups) Time to live: 2-6 months PCI scope: Platform carries it in most configurations Carrier flexibility: Good for routing, but designed for merchants -- not multi-tenant platforms Orchestration solves the wrong problem for insurance platforms. Orchestrators optimise routing for a merchant with multiple PSPs. Insurance platforms need each carrier to use their own PSP -- a fundamentally different architecture. See Payment Orchestration vs Payment Layer. ### 4. The Payment Layer A purpose-built layer that sits between the platform and any PSP. The platform integrates once. Each carrier uses their existing processor. Card data never touches the platform. - Multi-PSP support (any carrier's PSP, through one integration) - Multi-channel payment execution (voice, links, embedded checkout) - Limited PCI scope for the platform (no QSA audit) - White-label carrier onboarding and payment experiences - Revenue participation on premium volume - PCI DSS Level 1, ISO 27001, SOC 2 certification handled by the layer - Direct PSP control (the layer manages PSP connections) Time to live: Days to weeks PCI scope: Card data is captured inside the layer's certified environment and tokenised with the carrier's own gateway -- the platform's scope stays limited Carrier flexibility: Any PSP. Any carrier. One integration. ## Comparison Table Orchestrator Payment Layer Multi-carrier PSP support One per integration None (carriers must use yours) Multiple (merchant-facing) Any carrier's PSP Voice payments Payment links Build it yourself Yes (white-label) Embedded checkout Platform carries SAQ-D Platform carries it Card data never touches the platform Carrier onboarding Manual per carrier PayFac KYC process White-label, self-service Time to live Months per PSP 6-18 months 2-6 months Days to weeks Multi-tenant Yes (heavy) Yes (thin) ## Which Approach Fits Your Platform? You need a direct gateway if: - You serve one carrier with one PSP - You only need web checkout - You're willing to handle PCI scope - Payment is a minor feature, not a strategic capability You need a PayFac if: - Payment revenue is your primary business model - Your carriers don't have existing PSP preferences (unlikely in insurance) - You have 12+ months and $2M+ to invest in compliance infrastructure You need an orchestrator if: - You're a single merchant optimising routing across your own PSPs - You don't need voice payments or payment links - Multi-tenancy isn't a requirement You need The Payment Layer if: - You serve multiple carriers, each with their own PSP - You need voice payments for phone renewals and collections - You need payment links for overdue premium collection - PCI scope should not be your platform's problem - You want to ship payment execution in weeks, not quarters ## How Shuttle Fits Shuttle is The Payment Layer for insurance core platforms. One integration from the platform. Any carrier's PSP -- 40+ supported. Voice, links, and embedded checkout. PCI DSS Level 1, ISO 27001, and SOC 2 certified. Allianz runs call centre payments through Shuttle across 3 countries. An anonymised insurance core platform uses Shuttle to provide native payment execution across its carrier base -- with per-carrier PSP routing and limited PCI scope for the platform. Average outcomes: - $360K annual saving per platform - $2M PCI certification cost - months of development time saved ## Related Reading - Payments for Insurance Core Platforms -- the complete guide to embedded payment execution for insurance - PCI-Compliant Payment Architecture for Insurance Platforms -- limited-scope architecture for voice, links, and checkout - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the canonical comparison across all four categories - Embedded Payments Without Becoming a PayFac -- why most platforms shouldn't own the payment relationship - PayFac Alternatives for Platforms -- the full landscape of PayFac alternatives - Shuttle vs Building In-House -- the real cost of building payment infrastructure yourself *Book a discovery call to explore how Shuttle adds payment execution to your insurance platform -- or see how it works for platforms.* Explore More ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ### Payment Solutions for Car Dealerships & Auto Finance Platforms ### Insurance Billing vs Payment Execution: Why Your Platform Needs Both ### Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers ### Payments for Insurance Carriers and MGA Platforms ### PCI-Compliant Payment Architecture for Insurance Platforms ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [Payments for Insurance Carriers and MGA Platforms](/guides/payments-for-insurance-carriers-mga/) - [payment gateway](/blog/what-is-a-payment-gateway/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [Stripe Connect](/vs/stripe-connect/) - [Adyen for Platforms](/vs/adyen/) - [carriers mandate their PSP](/guides/enterprise-psp-mandates/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [orchestration platform](/guides/what-is-payment-orchestration/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [40+ supported](/payment-providers/) - [Payments for Insurance Core Platforms](/guides/payments-for-insurance-platforms/) - [PCI-Compliant Payment Architecture for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [PayFac Alternatives for Platforms](/alternatives/payfac/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [Book a discovery call](/discovery/) - [see how it works for platforms](/platforms/) - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [GuidePayment Solutions for Car Dealerships & Auto Finance Platforms→](/guides/car-dealership-payment-solutions/) - [BlogInsurance Billing vs Payment Execution: Why Your Platform Needs Both→](/blog/insurance-billing-vs-payment-execution/) - [BlogShuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers→](/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/) - [GuidePayments for Insurance Carriers and MGA Platforms→](/guides/payments-for-insurance-carriers-mga/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/payfac/ --- # PayFac Alternatives for Platforms | Shuttle > Why Platforms Look for PayFac Alternatives Becoming a payment facilitator is the most powerful way to control payment economics on your platform. # PayFac Alternatives for Platforms By Shuttle Team, February 20, 2026 ## Why Platforms Look for PayFac Alternatives Becoming a payment facilitator is the most powerful way to control payment economics on your platform. You set merchant pricing, own the underwriting relationship, and capture the full payment margin. But "most powerful" and "most practical" are different things. Platforms explore alternatives when the PayFac path creates more problems than it solves: ### Compliance Burden A registered PayFac must maintain PCI DSS Level 1 compliance, implement KYC/AML programmes, perform merchant underwriting and due diligence, and run ongoing transaction monitoring. Each of these is a specialised discipline. Together, they require a dedicated compliance team -- or an expensive outsourced equivalent. And the obligations don't stop at go-live. Every regulatory update, every new jurisdiction, every policy change from the card networks adds to your compliance surface area. ### Regulatory Risk Payment regulation varies by jurisdiction and changes frequently. A PayFac operating across the US, UK, and EU faces three distinct regulatory frameworks -- each with its own licensing requirements, consumer protection rules, and data residency expectations. Getting it wrong isn't just expensive. It's existential. Card network fines, regulatory enforcement actions, and reputational damage can threaten the entire platform, not just the payments business. ### Time and Cost Building PayFac infrastructure from scratch takes 12-18 months and requires significant investment in technology, compliance, and operational capabilities. PayFac-as-a-Service providers reduce this, but even managed PayFac solutions take months to implement and require ongoing operational investment. Meanwhile, your competitors ship features while you build payment plumbing. ### Single-PSP Limitation Most PayFac and PFaaS solutions process through a single acquirer. That means every merchant on your platform routes through the same processor -- regardless of whether that processor offers the best rates, geographic coverage, or authorisation performance for that merchant. Enterprise customers with existing PSP relationships and negotiated interchange rates can't bring their own gateway. ### Distraction from Core Product You're a SaaS company, not a payments company. Every engineering hour spent on payment compliance, merchant underwriting workflows, and risk monitoring is an hour not spent on your core product. The PayFac path turns your platform into two businesses -- and both need to be run well. ## What to Evaluate in an Alternative Before comparing specific approaches, clarify what matters for your platform: Compliance appetite: Do you want to own compliance, share it, or eliminate it entirely from your scope? PSP flexibility: Do your merchants need to use specific gateways? Enterprise customers often mandate their own PSP. Channel coverage: Do you need voice payments, payment links, or AI agent payments -- or just online checkout? Time to revenue: Are deals waiting on payment capabilities? Months-long implementations have opportunity costs. White-label: How important is it that payments look like your platform, not someone else's? ## The Alternatives ### 1. Stripe Connect What it is: Stripe's marketplace and platform payment product. Platforms onboard merchants as "Connected Accounts" and process all transactions through Stripe. Strengths: - Exceptionally well-documented APIs and SDKs - Fast to integrate for standard marketplace use cases - Stripe handles most compliance for Standard and Express accounts - Large developer community and ecosystem Limitations: - Stripe-only processing. Every merchant routes through Stripe. No PSP flexibility. - Custom accounts push significant compliance responsibility back to the platform -- you're effectively operating as a PayFac-lite without the margin benefits - No native voice payments, AI agent payments, or advanced payment link capabilities - Enterprise customers with existing PSP contracts can't bring their own gateway - Geographic coverage gaps in parts of Asia, Africa, and Latin America Best for: Platforms with standard marketplace payment flows, no enterprise PSP requirements, and online-only channels. ### 2. Adyen for Platforms What it is: Adyen's solution for platforms and marketplaces. Creates dedicated sub-merchant accounts under Adyen's acquiring infrastructure. - Strong global acquiring coverage, particularly for enterprise - Unified commerce capabilities (online + in-store) - Robust multi-currency and local payment method support - Enterprise-grade risk management and reporting - Same single-PSP constraint. Adyen for Platforms means Adyen as the processor -- you've traded PayFac obligations for Adyen lock-in. - Enterprise-focused -- less accessible for mid-market platforms - Sales-led, complex implementation process - Developer experience less polished than Stripe's - No voice payments or AI agent payment channels Best for: Enterprise platforms committed to Adyen as their sole processor, especially those needing unified commerce (online + POS). ### 3. PayFac-as-a-Service (Payrix, Finix) What it is: Managed PayFac platforms that give you PayFac-like capabilities -- merchant onboarding, underwriting, and payment margin -- without building the full infrastructure yourself. - More control over merchant pricing and underwriting - Faster than building PayFac from scratch (months instead of 12-18 months) - White-label merchant onboarding and management - Compliance obligations remain. You're still operating as a payment facilitator, even if the infrastructure is managed. KYC/AML, merchant monitoring, and regulatory obligations are shared but not eliminated. - Typically single-PSP. Most PFaaS solutions process through one acquirer -- the same limitation as building your own PayFac. - Regulatory burden scales with your merchant base and geographic expansion - No multi-channel support (voice payments, AI agent payments) - Slower to market than pre-built payment layers -- onboarding and underwriting setup takes time - The "managed" part has limits -- as your platform grows, compliance complexity still lands on you Best for: Platforms where payment revenue is a primary business model and the margin justifies the compliance overhead. For a detailed breakdown, see our Payrix and Finix comparison. ### 4. PSP-Neutral Payment Layer (Shuttle) What it is: A payment layer that embeds multi-PSP payment infrastructure into your platform -- without any PayFac obligations. White-label checkout, merchant onboarding, management portal, and multi-channel support through a single integration. - PSP-neutral: 40+ gateways. Merchants choose their PSP, or you assign one. Enterprise customers bring their Worldpay/Adyen/Checkout.com account without friction. - Zero PayFac compliance: No KYC/AML programme, no merchant underwriting, no ongoing transaction monitoring. Shuttle handles it. PCI DSS Level 1 + ISO 27001 + SOC 2 included. - Multi-channel: Embedded checkout, voice payments, payment links, chat, and AI agent payments -- all through the same integration. - White-label everything: Checkout, onboarding, merchant portal -- branded as your platform. - Live in weeks: Pre-built components, not a multi-month compliance and build project. - Lower per-transaction margin than full PayFac ownership - Less granular control over merchant underwriting decisions - Newer entrant -- smaller brand recognition than Stripe or Adyen Best for: Platforms that want payment revenue and multi-PSP flexibility without PayFac obligations, compliance overhead, or months-long build projects. ## The Real Question Do you actually need to be a PayFac? For most platforms, the answer is no. The margin advantage of PayFac ownership only justifies the compliance cost if payment revenue is your primary business model -- if you're building a payments company that happens to have a platform, not a platform that happens to need payments. If payments are a feature of your platform (not the product itself), the PayFac path adds complexity without proportional benefit. You're taking on compliance risk, regulatory exposure, engineering distraction, and operational overhead to capture a margin improvement that may not move the needle relative to your core SaaS revenue. ## Comparison Matrix Full PayFac PFaaS (Payrix/Finix) Stripe Connect Adyen for Platforms Payment Layer (Shuttle) Compliance burden Full (you own it) Shared (significant) Minimal-Moderate None (Shuttle carries it) PSP flexibility Single acquirer Usually single Stripe only Adyen only Time to market 12-18 months 3-6 months Days-weeks Weeks-months White-label Full control Voice payments Build it yourself AI agent payments Payment links Merchant onboarding Stripe-hosted Adyen-hosted Ongoing ops overhead Medium-High Low-Medium Payments-first companies Max margin platforms Standard marketplaces Enterprise single-PSP Multi-PSP platform payments ## Making the Decision The PayFac path makes sense if: - Payment revenue is your primary business model, not a feature - You have the compliance infrastructure (or budget to build it) for KYC/AML, PCI DSS, and merchant monitoring - You need granular control over merchant underwriting and pricing - You're willing to invest 12-18 months (or 3-6 months with PFaaS) before seeing revenue - You're operating in a single, well-understood regulatory environment - Your engineering team has payment domain expertise An alternative makes more sense if: - Payments are a feature of your platform, not the core product - Enterprise customers need to bring their own PSP - You need voice payments, payment links, or AI agent payment channels - You want payment revenue without compliance obligations - Speed to market matters -- deals are waiting - You'd rather invest engineering time in your core product - You're expanding into multiple geographies with different regulatory requirements ## FAQ What's the difference between PayFac and PayFac-as-a-Service? A full PayFac registers directly with the card networks and owns the entire payment facilitation stack -- underwriting, compliance, merchant management, and settlement. PayFac-as-a-Service (PFaaS) providers like Payrix and Finix give you PayFac-like capabilities through their infrastructure, so you skip the build phase. But compliance obligations are shared, not eliminated. You still carry KYC/AML responsibilities, merchant monitoring duties, and regulatory exposure. PFaaS reduces the build effort -- it doesn't remove the operational burden. What compliance do I avoid by not becoming a PayFac? By choosing a payment layer instead of the PayFac path, you avoid: PCI DSS Level 1 certification as a service provider, building and maintaining a KYC/AML programme, merchant underwriting and due diligence processes, ongoing transaction monitoring and risk management, card network registration and reporting requirements, and jurisdiction-specific regulatory licensing. Your payment layer provider carries these obligations instead. How does a payment layer handle merchant onboarding without PayFac status? Shuttle provides white-label merchant onboarding that connects merchants to their chosen PSP. The onboarding flow is branded as your platform, but the compliance obligations (KYC, underwriting, merchant agreements) are handled by the PSP and Shuttle -- not by you. From your merchant's perspective, it looks like your payment product. From your perspective, it's zero compliance overhead. ## Related Reading - Shuttle vs Payrix & Finix -- detailed PFaaS comparison - How to Get Payments Off Your Product Roadmap -- the hidden cost of building and maintaining payment infrastructure - Shuttle vs Stripe Connect -- if you're considering Stripe Connect as your alternative - Shuttle vs Building In-House -- the build vs. buy analysis - Adyen for Platforms Alternatives -- alternatives to Adyen's embedded solution - Stripe Connect Alternatives -- alternatives to Stripe's platform offering - Embedded Payments Without Becoming a PayFac -- the complete guide to embedding payments without PayFac obligations Rethinking the PayFac path? Shuttle gives your platform 40+ PSPs through a single integration -- with white-label checkout, voice payments, payment links, and AI agent support. Earn payment revenue without PayFac obligations. PCI DSS Level 1 compliance included. Live in weeks. Book a Demo | See How It Works Explore More ### PayFac Regret: Why Platforms Are Unwinding Their PayFac Status ### Embedded Payments Without Becoming a PayFac ### Is reselling payments and becoming a PayFac right for my SaaS? ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ### Shuttle vs PayFac-as-a-Service (Payrix, Finix) ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payrix and Finix comparison](/vs/payrix-finix/) - [Shuttle vs Payrix & Finix](/vs/payrix-finix/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [Adyen for Platforms Alternatives](/alternatives/adyen-for-platforms/) - [Stripe Connect Alternatives](/alternatives/stripe-connect/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [GuidePayFac Regret: Why Platforms Are Unwinding Their PayFac Status→](/guides/payfac-regret/) - [GuideEmbedded Payments Without Becoming a PayFac→](/guides/embedded-payments-without-payfac/) - [BlogIs reselling payments and becoming a PayFac right for my SaaS?→](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [ComparisonShuttle vs PayFac-as-a-Service (Payrix, Finix)→](/vs/payrix-finix/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/payment-orchestration/ --- # Payment Orchestration Alternatives for Platforms | Shuttle > Why Platforms Look Beyond Payment Orchestration Payment orchestration platforms solve a real problem -- for merchants. # Payment Orchestration Alternatives for Platforms By Shuttle Team, February 20, 2026 ## Why Platforms Look Beyond Payment Orchestration Payment orchestration platforms solve a real problem -- for merchants. They let large enterprises route transactions across multiple PSPs, optimise authorisation rates, and manage tokens in a single vault. If you're a merchant with three acquiring relationships and you want smart failover between them, orchestration is built for you. But if you're a platform embedding payments for your merchants, orchestration solves the wrong problem. Here's why. ### Orchestration Is Merchant-Facing, Not Platform-Facing Primer, Spreedly, and Gr4vy are designed for individual merchants optimising their own payment stack. A single business, managing its own PSP relationships, controlling its own provider selection. Platforms have a fundamentally different architecture. You're not optimising one merchant's transactions -- you're onboarding hundreds or thousands of merchants, each with their own processing needs, each expecting payments to feel like part of your product. Orchestration platforms don't have a concept of "sub-merchants" or "connected accounts." They assume a single entity controls the entire payment flow. ### No White-Label Tools Orchestration gives you APIs. It doesn't give you a white-label checkout, a merchant onboarding flow, or a branded portal where your merchants can manage refunds and view settlements. You build all of that yourself -- or you don't offer it. For platforms, this is the difference between launching a payments feature and launching a multi-quarter engineering project. ### No Multi-Channel Coverage Voice payments, payment links, chat payments, AI agent payment capture -- none of this is part of payment orchestration. Orchestration platforms route card transactions. If your platform needs to capture payments over a phone call, send a hosted payment link, or process a payment through a conversational AI agent, orchestration doesn't cover it. You'd need to integrate separate solutions for each channel, each with its own PCI surface and engineering overhead. ### Heavy Integration Burden Orchestration platforms are middleware. Sophisticated middleware, but middleware nonetheless. Spreedly in particular is consistently flagged by engineering teams as complex to integrate -- with implementation timelines stretching to months. Primer's no-code workflow builder reduces some of this, but you're still assembling infrastructure, not deploying a product. For platforms on a roadmap, "months of payment integration" is a hard sell to your product team. ### You're Buying Building Blocks, Not a Product This is the core issue. Orchestration gives you routing, tokenisation, and PSP connectivity. Everything else -- checkout UI, merchant onboarding, compliance, reporting, settlement reconciliation, merchant portal, multi-channel support -- is your problem. For a large enterprise with a payments engineering team, that's fine. For a platform that wants to offer embedded payments as a feature, it's a distraction from your core product. ## Orchestration vs What Platforms Actually Need The mismatch becomes clear when you map orchestration capabilities against platform requirements: What orchestration provides: - Multi-PSP routing and failover - PSP-agnostic tokenisation - Authorisation rate optimisation - A single API abstraction over multiple gateways What platforms actually need: - White-label checkout embedded in their product - Merchant onboarding that works out of the box - A merchant portal branded as their platform - Multi-channel payment capture (voice, links, AI agents) - PCI compliance without scope expansion - Sub-merchant management at scale - Speed to market measured in weeks, not quarters Orchestration addresses the first column. Platforms need both columns -- and the second column is where the real complexity lives. ## The Alternatives ### 1. Stripe Connect What it is: Stripe's purpose-built platform payments solution. Unlike orchestration, Connect is a complete product -- onboarding, checkout, payouts, and reporting, all designed for platforms embedding payments for their merchants. Strengths: - Fast to integrate -- excellent documentation and developer experience - Handles merchant onboarding (Express, Standard, and Custom account types) - Built-in payouts, reporting, and dispute management - Large ecosystem and community Limitations: - Single-PSP. Every Connected Account processes through Stripe. If an enterprise merchant has a Worldpay contract or needs a local acquirer in a market where Stripe is weak, you can't support them. - Geographic gaps in some emerging markets - No voice payments, AI agent payment capture, or robust payment link infrastructure - Pricing pressure at high volumes Best for: Platforms that are happy with Stripe as their sole processor and only need online checkout. ### 2. Adyen for Platforms What it is: Adyen's platform and marketplace solution. Creates dedicated merchant accounts for each sub-merchant on the Adyen network. - Strong global acquiring coverage, especially for enterprise - Unified commerce (online + in-store on one platform) - Good multi-currency and local payment method support - Enterprise-grade infrastructure and risk management - Single-PSP. You've traded orchestration's complexity for Adyen lock-in. Merchants process through Adyen -- no flexibility for enterprise customers with existing PSP relationships. - Enterprise-focused -- not accessible for mid-market platforms - Sales-led, not self-serve - Developer experience less polished than Stripe Best for: Enterprise platforms committed to Adyen as their sole processor, especially those needing unified commerce. ### 3. PayFac-as-a-Service (Payrix, Finix) What it is: Managed PayFac infrastructure. You get merchant onboarding, underwriting, and higher payment margins without building a PayFac from scratch. - More control over merchant pricing and underwriting - Faster than building your own PayFac - Typically single-PSP. Most PFaaS solutions process through a single acquirer. - Compliance obligations remain -- you're still operating as a PayFac, with the regulatory surface that entails - No multi-channel coverage (voice, links, AI agents) - Longer time to market than pre-built payment layers - Regulatory burden scales with your merchant base Best for: Platforms where payment revenue is the primary business model and you want maximum margin -- and you're willing to accept the compliance overhead. ### 4. PSP-Neutral Payment Layer (Shuttle) What it is: A payment layer that gives platforms the multi-PSP flexibility that orchestration promises -- combined with the platform-ready tools that orchestration lacks. White-label checkout, merchant onboarding, management portal, and multi-channel support through a single integration. - PSP-neutral: 40+ gateways. Your merchants choose their PSP, or you assign one. Enterprise customers bring their Worldpay/Adyen/Checkout.com account without friction. - Multi-channel: Embedded checkout, voice payments, payment links, chat, and AI agent payments -- all through the same integration. No separate PCI surfaces. - White-label everything: Checkout, onboarding, merchant portal -- branded as your platform. - PCI compliance included: PCI DSS Level 1 + ISO 27001 + SOC 2. Your PCI scope is effectively zero. - Live in weeks: Pre-built components, not a multi-month build project. - Lower per-transaction margin than full PayFac ownership - Less granular transaction-level routing optimisation than dedicated orchestration platforms - Newer entrant -- smaller brand recognition than Stripe or Adyen Best for: Platforms that need multi-PSP flexibility, white-label tools, and multi-channel payment capture -- without the engineering overhead of assembling it from orchestration building blocks. ## What Orchestration Gets Right -- and What It Misses Credit where it's due. Payment orchestration platforms have pioneered genuinely valuable capabilities: Smart routing -- directing transactions to the PSP most likely to approve them based on card type, geography, BIN data, and historical performance. This measurably improves authorisation rates for merchants processing at scale. PSP-agnostic tokenisation -- storing card credentials in a vault that isn't tied to a single processor. Spreedly's vault, in particular, is a mature piece of infrastructure. This gives merchants portability: if you switch PSPs, your tokens come with you. Redundancy -- if one PSP goes down, you can move the affected payment types to another connected PSP. For high-volume merchants, this uptime guarantee is critical. These are real, valuable capabilities. But they're merchant capabilities, not platform capabilities. A platform doesn't need to optimise its own authorisation rates -- it needs to embed payment acceptance for hundreds of merchants. A platform doesn't need PSP-agnostic tokens for its own cards on file -- it needs each merchant to be able to use their preferred PSP. A platform doesn't need failover between its own PSP connections -- it needs white-label checkout, onboarding, and reporting that work out of the box. Orchestration answers the question: "How do I optimise my payment stack?" Platforms are asking: "How do I offer payments to my customers?" Different question. Different solution. ## Comparison Matrix Orchestration (Primer/Spreedly/Gr4vy) Stripe Connect Adyen for Platforms PFaaS (Payrix/Finix) Payment Layer (Shuttle) Multi-PSP support Yes (core feature) Stripe only Adyen only Usually single Built for platforms No (merchant-facing) Yes (enterprise) White-label checkout Merchant onboarding Merchant portal Stripe Dashboard Adyen Dashboard White-label portal Voice payments Payment links AI agent payments Smart routing PSP-level routing PCI compliance Partial (varies) Stripe carries it Adyen carries it Fully included Time to market Days-weeks Weeks-months Integration complexity Low-medium Medium-high ## Making the Decision Orchestration might still be right if: - You are a merchant (not a platform) optimising your own payment stack - You have an engineering team dedicated to payments infrastructure - You already have checkout, onboarding, and reporting built - Your primary goal is authorisation rate optimisation across existing PSP relationships - You're willing to invest months in integration Look at platform-ready alternatives if: - You're a platform embedding payments for your merchants - You need white-label checkout, onboarding, and merchant management - You want multi-PSP flexibility without building everything yourself - You need multi-channel payment capture (voice, links, AI agents) - Speed to market matters -- deals are waiting - You don't want to carry PCI compliance scope ## FAQ Is Shuttle a payment orchestration platform? No. Shuttle is a payment layer built for platforms. Orchestration platforms are merchant-facing middleware that optimise routing between PSPs. Shuttle is platform-facing infrastructure that embeds multi-PSP payment acceptance -- with white-label checkout, merchant onboarding, a branded portal, and multi-channel support -- into your product. The multi-PSP flexibility overlaps, but the architecture and use case are fundamentally different. Can I get multi-PSP without orchestration? Yes. Multi-PSP support doesn't require orchestration middleware. A PSP-neutral payment layer like Shuttle connects to 40+ gateways and lets each merchant use their preferred PSP -- without the integration complexity of orchestration. You get the PSP flexibility without having to build checkout, onboarding, and merchant management yourself. What about routing optimisation? If your primary need is transaction-level smart routing (sending each transaction to the PSP most likely to approve it based on BIN data, geography, and historical performance), orchestration platforms are purpose-built for that. For most platforms, however, PSP-level routing -- letting each merchant use their preferred gateway -- delivers the flexibility they actually need. Transaction-level routing optimisation is a merchant concern, not typically a platform concern. Should I use orchestration AND a payment layer? In theory, you could layer orchestration underneath a platform payment solution. In practice, it adds complexity and cost without clear benefit for most platforms. The multi-PSP connectivity that orchestration provides is already built into a PSP-neutral payment layer. You'd be paying for two abstraction layers that solve overlapping problems. The exception might be very large platforms with specific routing optimisation requirements at the individual transaction level -- but that's a niche case. ## Related Reading - Shuttle vs Primer -- detailed comparison of Shuttle and Primer for platforms - Shuttle vs Spreedly -- detailed comparison of Shuttle and Spreedly for platforms - Shuttle vs Gr4vy -- detailed comparison of Shuttle and Gr4vy for platforms - How to Get Payments Off Your Product Roadmap -- the hidden cost of building and maintaining payment infrastructure - Payment Orchestration vs Payment Layer -- the detailed category distinction Looking for multi-PSP flexibility without the orchestration overhead? Shuttle gives your platform 40+ PSPs through a single integration -- with white-label checkout, voice payments, payment links, and AI agent support. Your enterprise customers bring their own gateway. No months-long integration. PCI DSS Level 1 compliance included. Book a Demo | See How It Works Explore More ### What Is Payment Orchestration? The Complete Guide ### Payment Orchestration vs Payment Layer: Why They're Not the Same ### The truth about payments orchestration ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [consistently flagged by engineering teams](https://www.g2.com/products/spreedly/reviews) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Shuttle vs Primer](/vs/primer/) - [Shuttle vs Spreedly](/vs/spreedly/) - [Shuttle vs Gr4vy](/vs/gr4vy/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [GuideWhat Is Payment Orchestration? The Complete Guide→](/guides/what-is-payment-orchestration/) - [GuidePayment Orchestration vs Payment Layer: Why They're Not the Same→](/guides/payment-orchestration-vs-payment-layer/) - [BlogThe truth about payments orchestration→](/blog/the-truth-about-payments-orchestration/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/prommt/ --- # Prommt Alternatives for Platforms and Merchant Payment Collection | Shuttle > Why Businesses Look for Prommt Alternatives Prommt is a payment request platform built for enterprise merchants -- particularly car dealerships, hotels,... # Prommt Alternatives for Platforms and Merchant Payment Collection By Shuttle Team, February 25, 2026 ## Why Businesses Look for Prommt Alternatives Prommt is a payment request platform built for enterprise merchants -- particularly car dealerships, hotels, and luxury retail. It does payment links and Pay by Bank well, especially for high-value transactions across European markets. But it's not right for every business. The most common reasons companies look elsewhere: ### Pricing Prommt's published entry price is €299/month with a sales-led onboarding process. For mid-market and enterprise merchants processing high-value transactions, the commercial model is designed with that profile in mind. For smaller businesses, teams adding payment collection as one feature among many, or platforms evaluating per-merchant costs, the commercial model may not match -- worth comparing against alternatives with different pricing structures. ### No Voice Payment Capture Prommt's approach to phone payments is to send a link during the call -- the customer opens it on their own device and completes payment digitally. This is a valid design choice that some merchants prefer for simplicity. Shuttle takes a different approach: capturing the payment during the call itself, via keypad entry (DTMF) with tone masking so the agent never hears the card number. Which model fits best depends on the use case. For agent-led calls in verticals like insurance renewals, debt collection, or hotel reservations, in-call capture typically keeps the conversation flow intact; for lightweight scenarios where the customer is already holding their phone, a link-based handoff can be simpler. ### Single-Merchant Architecture Prommt is designed for individual merchants. Each business gets its own account and dashboard. For platforms, BPOs, and SaaS companies that need to embed payments for hundreds of merchants -- each with their own PSP, branding, and payment configuration -- Prommt doesn't offer multi-tenant architecture. ### Gateway Dependency Prommt creates checkout pages that route to the merchant's existing payment gateway. It doesn't provide PSP flexibility itself. For businesses wanting to switch gateways, use multiple PSPs, or route transactions by region -- Prommt adds a checkout layer but doesn't solve the underlying PSP question. ### Geographic Limits on Pay by Bank Prommt's open banking coverage spans multiple European countries via Token.io. Outside those markets, Pay by Bank isn't available on their platform -- leaving cards as the primary payment method for those customers. Businesses with a customer base in the US, Asia-Pacific, or outside Prommt's European footprint will want to evaluate providers with coverage matched to those markets. ## The Alternatives ### 1. Shuttle What it is: A payment layer for platforms and merchants -- supporting payment links, voice checkout, open banking, and 40+ PSPs through a single integration. Payment methods: Cards (40+ PSPs), Pay by Bank (UK), ACH (US), BACS (UK), Apple Pay, Google Pay, PayPal, BNPL (Klarna, Affirm via supported PSPs). Strengths: - Voice checkout -- PCI-compliant DTMF capture during phone calls. The agent stays on the line, card tones are masked. No link-sending mid-call. See voice payments - 40+ PSPs -- merchant chooses their gateway, or the platform sets which provider handles each payment type - Multi-merchant architecture -- built for platforms, BPOs, and SaaS companies serving many merchants from one integration - Pricing -- $49/month for payment links, $0.20/transaction for voice checkout. Significantly lower entry point than Prommt - White-label -- checkout pages, merchant portal, and onboarding fully branded as your business - Open banking + cards + wallets on the same checkout page -- customer chooses - PCI DSS Level 1 + ISO 27001 + SOC 2 -- broadest compliance certification set Limitations: - Open banking currently UK-only (Prommt covers 14 European countries) - No automated chase paths with payment method fallback (configurable reminders available) - No native Oracle OPERA or automotive DMS integrations (API + Zapier/Make.com connectors available) Best for: Platforms embedding payments, BPOs handling multi-client payments, businesses that need voice + links from one provider, merchants wanting lower pricing with broader payment method support. Pricing: From $49/month (links) or $0.20/transaction (voice). See full Shuttle vs Prommt comparison. ### 2. Stripe Payment Links What it is: Free payment links from Stripe -- create a checkout page and share the URL. - Free to create (standard Stripe processing fees apply) - Apple Pay and Google Pay supported - Embeddable in websites and emails - Strong developer ecosystem - Stripe-branded checkout (not white-label) - No SMS or WhatsApp delivery built in - Stripe-only -- can't use other PSPs - No voice payment capture - No open banking / Pay by Bank - Limited customisation and branding Best for: Businesses already on Stripe that need a quick, free payment link with no additional platform cost. Pricing: Free (Stripe processing fees: 1.5% + 20p UK cards). ### 3. SOTpay What it is: A UK-based secure payment solution for phone and digital payments -- positions directly against Prommt. - Agent-assisted phone payments (card capture via secure web form) - Lower pricing than Prommt - UK-focused with strong SME positioning - PCI DSS compliant - UK-focused positioning - Payment method coverage focused on cards - No multi-PSP routing Best for: UK SMEs that need secure phone payment capture at a lower price point than Prommt, without requiring open banking or multi-PSP support. Pricing: From £30/month per user. ### 4. GoCardless What it is: Direct debit and open banking payment platform -- strong for recurring and bank-to-bank payments. - Excellent for recurring payments (direct debit) - Broadest open banking coverage (UK, EU, US, Australia via Instant Bank Pay) - Low transaction fees for bank payments - Strong API and integration ecosystem (300+ partners) - No card payments -- bank-only - No payment links in the traditional sense (no card checkout) - Not suitable for one-off, card-based payment requests - No white-label option Best for: Businesses focused on recurring payments and direct debit, or those wanting the broadest open banking coverage for bank-to-bank transfers. Not a like-for-like Prommt replacement. Pricing: Success+ model (variable fee based on payment recovery) or fixed fees from 1% + 20p. ### 5. Adyen Pay by Link What it is: Adyen's payment link product, available to Adyen merchants and platforms using Adyen for Platforms. - Strong international coverage -- Adyen supports 250+ payment methods across markets - Integrated with Adyen's risk and fraud tools - Available through Adyen for Platforms for multi-merchant setups - Supports Open Banking in select markets - Adyen-only -- all transactions must process through Adyen. No multi-PSP support - Enterprise-focused onboarding -- not as fast to set up as Stripe - White-labelling is limited compared to dedicated payment link platforms - No voice payment channel Best for: Enterprise merchants or platforms already using Adyen. Pricing: Custom (enterprise negotiated). ### 6. PayPal Payment Links What it is: Shareable payment links through PayPal's ecosystem. - Free to create - Massive consumer recognition and trust - PayPal balance, cards, and BNPL (Pay in 3) accepted - Instant setup, no approval needed - PayPal-branded experience (not your brand) - Higher fees than most alternatives (2.9% + 30p) - No open banking - No voice payments - No SMS/WhatsApp delivery built in Best for: Freelancers, small businesses, and sole traders who want to collect payments with zero setup. Pricing: Free (PayPal processing fees: 2.9% + 30p). ## Comparison Matrix Stripe Links GoCardless Payment links (SMS/email) Open banking 14 countries UK, EU, US, AU Select markets Card payments Merchant's PSP Stripe only Adyen only Via PayPal Voice checkout Apple Pay / Google Pay White-label Branded pages Multi-merchant Via Connect Via Platforms Chase automation Advanced paths Smart retries PCI Level 1 Starting price £30/user/mo Enterprise ## Making the Decision ### Stay with Prommt if: - You're in automotive, hospitality, or luxury retail and Prommt's vertical integrations (OPERA, DMS) are critical - You need Pay by Bank across multiple European countries, not just the UK - Chase paths with payment method fallback are essential to your credit control workflow - The €299/month cost is justified by your transaction volume and card fee savings ### Move to Shuttle if: - You need voice payment capture, not just payment links - You're a platform, BPO, or SaaS company serving multiple merchants - $49/month matters more than €299/month for your business - You want Apple Pay, Google Pay, and BNPL alongside cards and open banking - You need 40+ PSP options, not just your current gateway - White-label branding (checkout, portal, onboarding) is important ### Consider GoCardless if: - Recurring payments are your primary need - You want the broadest open banking coverage globally - You don't need card payments or one-off payment links ### Consider Stripe/Adyen Links if: - You're already on Stripe or Adyen and want free/included payment links - Branding and multi-channel delivery aren't important - You don't need open banking or voice payments ## FAQ Is Prommt good for small businesses? Prommt starts at €299/month with no free trial or self-service onboarding. It's designed for mid-market and enterprise merchants processing high-value transactions. For smaller businesses, alternatives like Shuttle ($49/month), SOTpay (£30/month), or free options (Stripe Links, PayPal) offer better value. Which alternative has the best open banking coverage? GoCardless has the broadest open banking coverage (UK, EU, US, Australia) but doesn't support card payments. Prommt covers 14 European countries. Shuttle currently supports UK open banking. For European-wide Pay by Bank with cards, Prommt leads. For UK open banking plus cards plus voice, Shuttle leads. Can any of these alternatives capture payments over the phone? Shuttle is the only option with PCI-compliant voice checkout -- DTMF capture during the call with tone masking. SOTpay offers secure web-form phone payments (the agent opens a form, the customer enters details). Prommt, Stripe, GoCardless, Adyen, and PayPal don't offer phone payment capture. What's the cheapest Prommt alternative? Stripe Payment Links and PayPal.Me are free (processing fees apply). SOTpay starts at £30/user/month. Shuttle starts at $49/month. All are significantly cheaper than Prommt's €299/month starting price. Can I migrate from Prommt to Shuttle? Yes. If your merchants' PSPs are among Shuttle's 40+ supported gateways, migration involves configuring the same gateway through Shuttle. No PSP change needed. Payment links can be switched over progressively -- no big-bang migration required. Does Shuttle support the same verticals as Prommt? Shuttle doesn't have pre-built DMS or OPERA integrations like Prommt. But it supports the same payment use cases -- car dealership deposits, hotel pre-payments, builders merchant collections -- through payment links, voice checkout, and open banking. Integration with vertical systems is handled via API and workflow connectors (Zapier, Make.com). ## Related Reading - Shuttle vs Prommt -- detailed head-to-head comparison - Payment Links for Car Dealerships -- automotive payment collection with links, voice, and open banking - Builders Merchant Payment Collection -- payment links for trade suppliers - How to Send Payment Requests -- the complete guide to digital payment collection - Best Payment Link Providers (2026) -- ranked comparison of all payment link services - PCI-Compliant Payments for Contact Centres -- voice payment capture for phone-based businesses - Voice Payments -- PCI-compliant phone payment collection - PSP-Neutral vs Single-PSP -- why multi-PSP flexibility matters - How Platforms Monetise Payments -- the revenue opportunity in embedded payment links - White-Label Payment Links for Platforms -- branded payment pages for multi-merchant use cases Looking for a Prommt alternative? Shuttle gives you payment links, voice checkout, open banking, and 40+ PSPs -- with white-label branding and multi-merchant architecture. From $49/month. See Payment Links | See Voice Checkout | Book a Demo Explore More ### Shuttle vs Prommt for Platforms and Merchants ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [Prommt](https://www.prommt.com) - [DTMF](/guides/dtmf-payments/) - [PSP question](/guides/psp-neutral-vs-single-psp/) - [voice payments](/guides/voice-payments/) - [full Shuttle vs Prommt comparison](/vs/prommt/) - [car dealership deposits](/guides/payment-links-for-car-dealerships/) - [builders merchant collections](/guides/builders-merchant-payment-collection/) - [Shuttle vs Prommt](/vs/prommt/) - [Payment Links for Car Dealerships](/guides/payment-links-for-car-dealerships/) - [Builders Merchant Payment Collection](/guides/builders-merchant-payment-collection/) - [How to Send Payment Requests](/guides/how-to-send-payment-requests/) - [Best Payment Link Providers (2026)](/guides/best-payment-link-providers/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Voice Payments](/guides/voice-payments/) - [PSP-Neutral vs Single-PSP](/guides/psp-neutral-vs-single-psp/) - [White-Label Payment Links for Platforms](/guides/white-label-payment-links/) - [See Payment Links](/merchants/links-checkout/) - [See Voice Checkout](/merchants/payment-services/) - [Book a Demo](/discovery/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/stripe-connect/ --- # Stripe Connect Alternatives for Platforms | Shuttle > Why Platforms Look for Stripe Connect Alternatives Stripe Connect is an excellent product. # Stripe Connect Alternatives for Platforms By Shuttle Team, February 10, 2026 ## Why Platforms Look for Stripe Connect Alternatives Stripe Connect is an excellent product. It's well-documented, developer-friendly, and handles the complexity of marketplace payments elegantly. For many platforms, it's the right starting point. But starting points aren't always endpoints. Platforms look for alternatives when they hit one or more of these walls: ### PSP Lock-In Every merchant on Stripe Connect processes through Stripe. If an enterprise customer has a Worldpay contract with negotiated rates, you can't support them. If you want to route UK transactions through a domestic acquirer for better authorisation rates, you can't. Stripe is both the infrastructure and the processor -- and they have no incentive to support alternatives. ### Geographic Gaps Stripe operates in 46+ countries, but coverage varies. Some markets have limited features, restricted Connect support, or no cross-border payout capability. Platforms expanding into Southeast Asia, Africa, or parts of Latin America hit limitations. ### Channel Constraints Stripe Connect covers online checkout. It doesn't natively support voice payments, IVR payment capture, or AI agent payment flows. Platforms needing these channels must integrate third-party solutions on top of Connect -- creating separate PCI surfaces and additional engineering complexity. ### Pricing at Scale At high volumes, Stripe's standard pricing (2.9% + $0.30 per transaction, plus $2/active account/month for Express/Custom, plus payout fees) adds up. Platforms processing tens of millions want interchange-plus pricing and more control over payment economics. ### PayFac-Lite Complexity Custom Connect accounts make the platform responsible for significant operational aspects -- onboarding, compliance, support, and risk management. As regulatory requirements evolve across jurisdictions, this compliance surface area grows. ## What to Evaluate in an Alternative Before comparing specific alternatives, clarify what you need: PSP flexibility: Do your merchants need to use specific gateways? If yes, you need PSP-neutral infrastructure -- not another single-PSP solution. Channel coverage: Do you need voice, payment links, or AI agent payments -- or just checkout? This filters out many alternatives immediately. White-label: How important is it that payments look and feel like your product, not a third party's? Speed to market: Are deals waiting? If you need to be live in weeks, not months, pre-built components matter. Compliance: Do you want to carry PCI compliance or have a provider handle it? ## The Alternatives ### 1. Adyen for Platforms What it is: Adyen's solution for platforms and marketplaces. Unlike Connect's aggregator model, Adyen creates dedicated merchant accounts for each sub-merchant. Strengths: - Strong global acquiring coverage, especially in enterprise - Unified commerce (online + in-store on one platform) - Good multi-currency and local payment method support - Enterprise-grade infrastructure Limitations: - Same single-PSP problem. Adyen for Platforms means using Adyen as the processor. You've swapped Stripe lock-in for Adyen lock-in. - Enterprise-focused -- less accessible for mid-market platforms - Developer experience less polished than Stripe's - Corporate, sales-led process (not self-serve) Best for: Enterprise platforms committed to Adyen as their sole processor, especially those needing unified commerce (online + POS). ### 2. Payment Orchestration (Primer, Spreedly) What it is: Middleware that routes transactions across multiple PSPs. Gives you multi-PSP connectivity, failover, and tokenisation through a single integration. - Multi-PSP routing and failover - PSP-agnostic tokenisation (especially Spreedly's vault) - Smart routing for authorisation rate optimisation - Primer: visual workflow builder, no-code routing rules - Spreedly: deep vault infrastructure, 120+ connections - Merchant-facing, not platform-facing. These are tools for merchants to optimise their own payment stack -- not tools for platforms to embed payments for their merchants. - No white-label merchant onboarding or portal - No voice payments, payment links, or AI agent infrastructure - Heavy engineering lift -- Spreedly in particular is flagged by users as complex to integrate - You still need to build checkout, onboarding, reporting, and merchant management yourself Best for: Large enterprises that already have PSP relationships and want to optimise routing between them. Not a like-for-like Stripe Connect replacement for platforms. ### 3. PayFac-as-a-Service (Payrix, Finix) - More control over merchant underwriting and pricing - Faster than building PayFac from scratch - Still typically single-PSP. Most PFaaS solutions process through a single acquirer. - Compliance obligations remain -- you're still operating as a PayFac (albeit a managed one) - Regulatory burden scales with your merchant base - No multi-channel coverage (voice, links, AI) - Slower to market than pre-built payment layers Best for: Platforms where payment revenue is a primary business model and you want maximum margin -- and you're willing to accept the compliance overhead. ### 4. PSP-Neutral Payment Layer (Shuttle) What it is: A payment layer that embeds multi-PSP payment infrastructure into your platform. White-label checkout, merchant onboarding, management portal, and multi-channel support -- all through a single integration. - PSP-neutral: 40+ gateways. Merchants choose their PSP or you assign one. Enterprise customers bring their Worldpay/Adyen/Checkout.com account without friction. - Multi-channel: Embedded checkout, voice payments, payment links, chat, and AI agent payments -- all through the same integration. - White-label everything: Checkout, onboarding, merchant portal -- branded as your platform. - PCI compliance included: PCI DSS Level 1 + ISO 27001 + SOC 2. Your PCI scope is effectively zero. - Live in weeks: Pre-built components, not a multi-month build project. - Lower per-transaction margin than full PayFac ownership - Less transaction-level routing optimisation than dedicated orchestration platforms - Newer entrant -- smaller brand recognition than Stripe or Adyen Best for: Platforms that need to embed payments for their merchants, support multiple PSPs, and go live quickly -- without becoming a payments company. ## Comparison Matrix Stripe Connect | Adyen for Platforms | Orchestration (Primer/Spreedly) | PFaaS (Payrix/Finix) | Payment Layer (Shuttle) PSP flexibility | Stripe only | Adyen only | Multiple | Usually single | 40+ PSPs White-label onboarding | Partial (Express) | Limited | None | Yes | Yes Merchant portal | Stripe Dashboard | Adyen Dashboard | None | Varies | White-label portal Voice payments | No | No | No | No | Yes Payment links | Limited | Limited | No | Varies | Yes AI agent payments | No (x402 is agent-to-agent) | No | No | No | Yes PCI compliance | Stripe carries it | Adyen carries it | Partial (varies) | Shared | Fully included Time to market | Days-weeks | Weeks-months | Months | Weeks-months | Weeks Best for | Standard marketplace payments | Enterprise single-PSP | Routing optimisation | Max payment revenue | Multi-PSP platform payments ## Making the Decision Stay with Stripe Connect if: - All merchants are happy with Stripe processing - No enterprise customers require alternative PSPs - You only need online checkout (no voice, links, AI) - Stripe's geographic coverage meets your needs - You're comfortable with Stripe's pricing at your volume Move to an alternative if: - Enterprise customers mandate their own PSP - You need voice payments, payment links, or AI agent payment channels - You're expanding into markets Stripe doesn't cover well - You want PSP negotiating leverage - Stripe's pricing doesn't work at your scale - You need deeper white-label control ## FAQ Can I migrate from Stripe Connect without disrupting existing merchants? Yes. Most alternatives (including Shuttle) can connect to Stripe as one of their supported gateways. Existing merchants continue processing through Stripe while new merchants (or those requiring different PSPs) use alternative gateways. The transition is additive. What happens to my Stripe-tokenised cards? Card tokens in Stripe's vault are Stripe-proprietary -- they can't be used with other processors directly. A payment layer provides its own PSP-agnostic tokenisation. For existing card-on-file customers, you'll need to re-tokenise (typically through a transparent card update flow) or continue routing those specific customers through Stripe. Is Stripe Connect really "locked in"? Yes, architecturally. Every Connected Account processes exclusively through Stripe's acquiring network. There's no multi-PSP option within Connect. Stripe's business model depends on being the processor, not just the infrastructure. What about Stripe's Agentic Commerce Suite (x402)? Stripe's x402 protocol enables machine-to-machine payments using USDC on the Base blockchain -- AI agents paying for APIs, data, and compute. It's a different use case from AI agents processing consumer card payments. For platforms where AI voice agents or chat agents need to capture customer card payments in PCI-compliant environments, x402 doesn't apply. Outgrowing Stripe Connect? Shuttle gives your platform 40+ PSPs through a single integration -- with white-label checkout, voice payments, payment links, and AI agent support. Your enterprise customers bring their own gateway. PCI DSS Level 1 compliance included. [Book a Demo] | [See How It Works] ## Related Reading Explore More ### When Your SaaS Outgrows Stripe Connect: A Migration Playbook ### Shuttle vs Stripe Connect ### 5 Stripe Connect Limitations That Force Platforms to Switch ### Twilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [GuideWhen Your SaaS Outgrows Stripe Connect: A Migration Playbook→](/guides/when-saas-outgrows-stripe-connect/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [Blog5 Stripe Connect Limitations That Force Platforms to Switch→](/blog/stripe-connect-limitations/) - [GuideTwilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative→](/guides/twilio-stripe-pay-connector/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/alternatives/worldpay/ --- # Worldpay Alternatives for Platforms | Shuttle > Why Platforms Look for Worldpay Alternatives Worldpay has always occupied a particular position in the payments industry: enormous reach, deep acquiring... # Worldpay Alternatives for Platforms By Shuttle Team, February 23, 2026 ## Why Platforms Look for Worldpay Alternatives Worldpay has always occupied a particular position in the payments industry: enormous reach, deep acquiring relationships, and a reputation built on decades of processing volume. For platforms that grew up around Worldpay -- or enterprise customers with long-running Worldpay contracts -- it has delivered real value. But the last several years have been turbulent in a way that's hard to ignore if you're building infrastructure decisions around Worldpay. The product itself hasn't fundamentally changed. The ownership has -- repeatedly. That instability is the primary reason platforms are re-evaluating their exposure now. Alongside it, a structural limitation that was always present has become harder to overlook: Worldpay was built for direct merchant acquiring, not for embedding payments across a platform's merchant base. There are no white-label platform tools. There's no merchant management layer. There's no multi-channel infrastructure for voice, chat, or AI agent payments. Single-acquirer architecture means whatever Worldpay's relationship with Global Payments settles into -- for better or worse -- your platform inherits it. ### The Ownership History Is Unusual, Even for Payments The payments industry consolidates constantly. Large acquirers get bought, merged, rebranded. That's normal. Worldpay's trajectory has been unusually circular. Worldpay was spun out of Royal Bank of Scotland in 2010. Vantiv acquired it in 2018 for $10.4 billion. FIS then acquired the combined entity in 2019 for $43 billion, creating one of the world's largest payments companies. Then, in 2023, FIS did something unusual: it spun Worldpay back out as an independent company, selling a majority stake to private equity firm GTCR at an implied valuation of roughly $18.5 billion -- less than half what FIS had paid. In early 2025, Global Payments announced a $24 billion acquisition of Worldpay, bringing it into yet another enterprise payments group. Each transition raises the same questions for platforms: Who is my relationship manager now? What happens to my commercial terms? Is the roadmap I was shown still real? Which team owns the integration I depend on? These aren't hypothetical concerns. Platforms that went through the Vantiv-to-FIS transition felt the disruption. The FIS-to-GTCR spinoff created further uncertainty about priorities and investment. Platforms now watching the Global Payments integration are asking the same questions for the third time in less than a decade. ### No Platform Infrastructure Beyond ownership, there's a product gap that consolidation doesn't solve. Worldpay is an acquirer. It is exceptionally good at processing transactions for merchants with a direct relationship. What it was never designed to do is sit inside another platform as embedded infrastructure. If you want to offer payments as a feature of your SaaS platform -- with white-label onboarding for your merchants, a branded portal, multi-channel checkout, and the ability to support enterprise merchants who bring their own PSP -- Worldpay doesn't provide those building blocks. You'd be assembling them yourself on top of the Worldpay gateway, which means maintaining that integration, owning the merchant experience, and carrying PCI scope for whatever you've built. ### Single-Acquirer Lock-In When your platform routes every merchant through Worldpay, you're exposed to everything Worldpay does or doesn't control: pricing reviews during acquisition transitions, geographic capability changes, authorisation rate performance, support quality during integration uncertainty. You have no fallback. You can't route an enterprise merchant through Stripe or Adyen if they need it. You can't negotiate from a position of alternatives. That's not a Worldpay-specific problem -- it's inherent to any single-PSP architecture. But the compounding effect of three ownership changes in seven years makes the single-acquirer risk feel more concrete for platforms currently on Worldpay. ## The Consolidation Factor Platforms that have been through the Vantiv-FIS-Worldpay-GTCR-Global Payments cycle are not being dramatic when they express concern. They've watched roadmap items deprioritised mid-integration, account teams restructured, pricing negotiated upward during contract renewals that coincide with acquisition closes. The pattern in large payments M&A is consistent: acquiring companies focus the first 12-18 months on back-office integration -- financial systems, compliance, risk infrastructure. Product roadmaps slow. Mid-market accounts receive less attention as enterprise accounts are prioritised during the commercial reassessment. Support escalation paths change. That's not a reason to panic. And it's not anti-Worldpay to acknowledge it -- the same dynamic plays out at every large acquirer that goes through significant M&A. The question for platforms isn't whether to condemn Worldpay. It's whether to build your payments architecture in a way that makes you resilient to future changes -- regardless of which processor they happen at. The answer to that question is the same regardless of which PSP triggers it: multi-PSP architecture where no single provider has structural leverage over your platform. ## What to Evaluate in an Alternative Before comparing specific alternatives, clarify what your platform actually needs: PSP flexibility: Do you need to support enterprise merchants who arrive with existing Worldpay contracts -- or Stripe, Adyen, or Checkout.com contracts? If yes, you need PSP-neutral infrastructure, not another single-PSP solution that just swaps one dependency for another. Platform tools: Do you need white-label merchant onboarding, a branded merchant portal, and embedded checkout that looks like your product -- not a redirect to a third-party gateway? Channel coverage: Do you need voice payments, payment links, or AI agent payment flows -- or just online checkout? Many alternatives cover checkout but leave multi-channel gaps. Continuity: Can you migrate without disrupting existing merchants who are already processing? The best transitions are additive -- new capability sits alongside what's already working, rather than requiring a hard cutover. PCI scope: Are you prepared to carry PCI compliance for the infrastructure you build around a gateway, or do you want a provider that handles it? Speed: Do you have live deals waiting on payment capability, or does your timeline accommodate a multi-month enterprise integration? ## The Alternatives ### 1. PSP-Neutral Payment Layer (Shuttle) What it is: A payment layer that embeds multi-PSP payment infrastructure directly into your platform. White-label checkout, merchant onboarding, management portal, and multi-channel support -- all through a single integration. Worldpay remains available as one of 40+ supported gateways. The key distinction here: Shuttle isn't a Worldpay replacement -- it's a structure that makes your platform independent of any single processor. Merchants who have Worldpay contracts keep them. Enterprise customers who prefer Stripe or Adyen use those. New merchants get assigned a default PSP based on geography and volume. Your platform sits above all of it. Strengths: - PSP-neutral: 40+ gateways including Worldpay. Merchants who have existing Worldpay relationships aren't disrupted -- they continue processing through Worldpay as one of the available connectors. - Multi-channel: Embedded checkout, voice payments, payment links, chat, and AI agent payments -- all through the same integration and the same PCI scope. - White-label everything: Checkout, onboarding flow, and merchant portal are all branded as your platform. - PCI DSS Level 1 + ISO 27001 + SOC 2 included. Your platform's compliance surface area is effectively zero. - Live in weeks: Pre-built components, not a multi-month enterprise integration project. - Acquisition-resilient: When a PSP goes through M&A -- Worldpay, or anyone else -- you switch the routing. You're not rebuilding. Limitations: - Lower per-transaction margin than full PayFac ownership - Less deep on routing optimisation than dedicated orchestration middleware - Newer entrant -- less brand recognition than Stripe or Adyen Best for: Platforms that need to embed payments for their merchants, want to support multiple PSPs (including Worldpay) without rebuilding for each one, and want to go live quickly without becoming a payments company. ### 2. Adyen for Platforms What it is: Adyen's solution for platforms and marketplaces. Creates dedicated merchant accounts for each sub-merchant, with strong global acquiring and unified commerce capability (online + in-store). - Strong global acquiring, especially in enterprise - Unified commerce: online checkout and in-store POS on a single platform - Good multi-currency and local payment method support - Enterprise-grade infrastructure and reliability - Single-PSP lock-in, just with a different PSP. Every merchant on Adyen for Platforms processes through Adyen. You've reduced your Worldpay exposure but replaced it with Adyen dependency. - Sales-led, enterprise procurement process -- not self-serve - Months-long integration timelines - No voice payments, IVR, or AI agent payment infrastructure - No multi-channel beyond checkout and POS - Minimum volume commitments that exclude mid-market platforms Best for: Enterprise platforms with large, committed Adyen relationships where every merchant processing through Adyen is acceptable -- and where online + in-store unified commerce is a core requirement. ### 3. Stripe Connect What it is: Stripe's platform payments solution. An aggregator model where the platform acts as the master Stripe account, with Connected Accounts for each sub-merchant. The most common starting point for platform payments, with strong developer tooling and fast time to market. - Best-in-class developer experience and documentation - Fast time to market -- sandbox in minutes, live in days to weeks - Self-serve access and transparent pricing - Large ecosystem of tools, plugins, and integrations - Reliable infrastructure and strong no-code options - Single-PSP lock-in, same structural problem. Stripe Connect means processing through Stripe. Enterprise merchants with Worldpay contracts can't bring their own PSP. - Geographic gaps in some markets - Pricing pressure at high transaction volumes - Stripe's ownership and roadmap are stable -- but you still have no PSP negotiating leverage Best for: Platforms that need fast time to market and strong developer experience, and are comfortable with single-PSP lock-in to Stripe rather than to Worldpay. ### 4. Building In-House What it is: Integrating directly with multiple PSP gateways, building your own merchant onboarding flow, developing a custom merchant portal, and managing PCI compliance internally. - Maximum control over every aspect of the payment experience - No third-party dependency on infrastructure layer - Full ownership of the merchant relationship and data - Engineering cost is consistently underestimated. A production-grade payment layer -- handling onboarding, KYC, checkout, tokenisation, webhooks, reconciliation, and merchant portal -- typically represents 12-24 months of engineering time at meaningful team size. - PCI DSS Level 1 certification is a significant compliance programme. For most platforms, it requires a dedicated compliance team, annual QSA assessments, quarterly ASV scans, and ongoing programme management. - Each new PSP is a separate integration project. Adding Worldpay alongside Stripe alongside Adyen means building, testing, and maintaining three separate integrations -- plus the abstraction layer above them. - Ongoing maintenance burden grows with every PSP version update, compliance cycle, and new channel requirement. Best for: Payments companies with large engineering teams where payment infrastructure is the core product, not a feature. ## Comparison Matrix Shuttle (PSP-Neutral Layer) Adyen for Platforms Stripe Connect Build In-House Worldpay support Yes (one of 40+ gateways) Yes (direct integration) PSP flexibility Adyen only Stripe only Multiple (custom build) White-label onboarding Partial (Express) Build it yourself Merchant portal White-label portal Adyen Dashboard Stripe Dashboard Voice payments Payment links AI agent payments PCI compliance Fully included Adyen carries it Stripe carries it You carry it Time to market Weeks-months Days-weeks 12-24+ months Self-serve access Acquisition resilience High (swap PSPs) Low (Adyen only) Low (Stripe only) High (with cost) ## Making the Decision Stay with Worldpay (or accept the Global Payments transition) if: - Your merchants are happy with current processing terms and performance - No enterprise customers require alternative PSPs or have incompatible existing contracts - You only need traditional online checkout -- no voice, AI agents, or multi-channel - You have confidence in the Global Payments integration roadmap for your use case - Your commercial terms are locked in for a meaningful period and you can revisit at renewal Move to an alternative if: - The third ownership change in seven years has surfaced strategic concerns about single-PSP dependency - Enterprise customers are arriving with Stripe, Adyen, or Checkout.com contracts and you can't support them - You need voice payments, payment links, or AI agent payment channels - You're building new platform payment infrastructure and want to avoid concentrating on any single acquirer - You want PSP negotiating leverage -- the ability to move volume between processors at renewal - You need white-label merchant tools that feel like your platform, not a gateway's portal ## FAQ Can I keep Worldpay and add alternatives at the same time? Yes. This is the most common path for platforms currently on Worldpay. A PSP-neutral payment layer connects to Worldpay as one of its supported gateways -- existing merchants who process through Worldpay continue unchanged. New merchants, or those who require a different PSP, use an alternative gateway. You don't have to choose between continuity and flexibility. Will the Global Payments acquisition affect my Worldpay integration? The technical gateway API is unlikely to change significantly in the short term -- that would create too much disruption for Worldpay's merchant base. What typically changes during large acquisitions is account management, commercial terms at renewal, and product roadmap priorities. The risk for platforms is primarily strategic: terms you negotiate today may land differently when commercial ownership transitions. Is Worldpay's gateway still reliable for processing? Yes. The gateway itself is proven infrastructure with decades of transaction volume. The concerns around the Global Payments acquisition are strategic and commercial, not technical. If you're on Worldpay for direct merchant acquiring, your transactions aren't suddenly at risk. The question is whether you want your entire platform infrastructure dependent on how the integration unfolds. How does Worldpay compare to Stripe or Adyen for platforms specifically? All three are strong acquirers. For platforms, the relevant distinction is that none of them offer PSP-neutral infrastructure -- each one requires your merchants to process through their network. Worldpay, Stripe, and Adyen all solve the same problem differently for direct merchants. None of them solve the platform problem of supporting merchants who arrive with their own existing PSP relationships. What if my enterprise customers have negotiated Worldpay rates they want to keep? A PSP-neutral payment layer supports exactly this scenario. Merchants with existing Worldpay contracts continue processing through Worldpay -- your platform doesn't need to renegotiate their rates or change their relationship with the gateway. You simply connect those merchants to Worldpay as their selected PSP within your platform's payment layer. How long does migrating off single-PSP dependency take? The timeline depends on the approach. Switching to a PSP-neutral layer like Shuttle typically takes weeks for the platform integration, with existing merchants migrated gradually or not at all (if they continue using Worldpay through the new layer). A full rebuild in-house takes 12-24+ months. Switching to another single PSP (Adyen or Stripe) typically takes weeks to months depending on merchant volume and onboarding complexity. ## Related Reading - Shuttle vs Worldpay for Platforms -- the detailed feature comparison - Shuttle vs Adyen for Platforms -- if you're considering Adyen as your alternative - Adyen for Platforms Alternatives -- if you're evaluating Adyen and want to know what's beyond it - Stripe Connect Alternatives for Platforms -- if Stripe Connect is on your shortlist - PSP Consolidation and Platform Risk -- why single-PSP architecture amplifies M&A risk - PSP-Neutral vs Single-PSP Architecture -- the architectural trade-offs in detail - Virtual Terminal Payments: replacing a bundled virtual terminal without changing your merchant account Evaluating your options after Worldpay's latest acquisition? Shuttle gives your platform 40+ PSPs through a single integration -- with Worldpay available as one of them. White-label checkout, merchant onboarding, voice payments, payment links, and AI agent support. PCI DSS Level 1 compliance included. Existing Worldpay merchants aren't disrupted. Live in weeks. Book a Demo | See How It Works for Platforms Explore More ### How to Connect Worldpay to Twilio for Voice & IVR Payments ### Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay ### Adyen vs Worldpay: Which PSP for Your Platform? ### Shuttle vs Worldpay for Platforms ### Payment Links for Worldpay: Send Checkout Links Without Leaving Worldpay ## Talk to us See how Shuttle can power payments for your platform -- multi-PSP, multi-channel, white-label. ## Links - [Shuttle vs Worldpay for Platforms](/vs/worldpay/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [Adyen for Platforms Alternatives](/alternatives/adyen-for-platforms/) - [Stripe Connect Alternatives for Platforms](/alternatives/stripe-connect/) - [PSP Consolidation and Platform Risk](/blog/psp-consolidation-platform-risk/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Virtual Terminal Payments](/guides/virtual-terminal-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Demo](/discovery/) - [See How It Works for Platforms](/platforms/) - [GuideHow to Connect Worldpay to Twilio for Voice & IVR Payments→](/guides/worldpay-twilio-integration/) - [GuideWorldpay + QuickBooks Integration: Pay Invoices Through Worldpay→](/guides/quickbooks-worldpay-payments/) - [GuideAdyen vs Worldpay: Which PSP for Your Platform?→](/guides/adyen-vs-worldpay/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [BlogPayment Links for Worldpay: Send Checkout Links Without Leaving Worldpay→](/blog/payment-links-for-worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/5-critical-business-frustrations-and-how-to-solve-them/ --- # 5 critical business frustrations and how to solve them | Shuttle > Survey reveals the top five frustrations for small businesses: tax, accounting, expense tracking, payments, and cash flow. Learn practical solutions. # 5 critical business frustrations and how to solve them By Nick Dunse, December 17, 2025 Survey reveals the top five frustrations for small businesses: tax, accounting, expense tracking, payments, and cash flow. Learn practical solutions. According to a recent survey undertaken by a UK 'challenger bank' businesses younger than one-year-old are really frustrated with Tax and Accounting; closely followed by managing their expenses and having to use multiple applications when running their business. For more mature business Tide Bank found that they were struggling with Payroll and keeping track of expenses. Sound familiar? Survey Results: - Tax Calculations (54%) - Accounting (51%) - Tracking Expenses (49%) - Having to use multiple applications to manage different services (38%) - Invoicing (30%) - Payroll (18%) Companies more than one-year-old: - Payroll (a problem for 27% of companies between 1-5 years old) - Keeping track of expenses (55%). Here at Bolt we also get frustrated with these things but we believe that there are solutions out there and even if there aren't, we'll create them, at least in terms of solving payments challenges that is. So let's unpack some of these frustrations a little further and try and offer some advice and solutions to alleviate the headache. Tax and Accounting There are more accounting practices and accounting software solutions out there than ever, so what's the problem? Well, firstly how do you choose an accountant and accounting software? Secondly, what do these services do for you and what do you have to work with them? Find a good accountant that understands your type of business and is familiar with the latest accounting software solutions. If your accountant doesn't have any other clients like your business I wouldn't employ them, ask them directly about their experience and client base. This will save you lots of time and you'll get good input from them going forward. If you haven't chosen some accounting software then you need to but it's worth asking these accountants what they'd recommend, be aware that many of them will be getting a commission for reselling software though. Having said that, for small businesses, there isn't a huge amount of choice, the top three being Xero, QuickBooks and Sage. Followed by FreshBooks and a few others. Your decision depends on your country and what you need the software to do. - Top tips for Tax and Accounting newbies are: - Make sure you save correctly and conservatively for tax. - Look at your accounts every day and get your accountant to show you how to create a cash flow spreadsheet that you check every day. - Automate as much as possible but only once you've got familiarity with your business and accounting software. - Check your tax and VAT returns properly once your accountant has done them. A good way to do this is to run a rough spreadsheet or cash flow in tandem, this sounds like it's more work (which it is) but often your accountant misses things. And once they understand your business and behaviours a little better their returns will become more accurate. - Find an accountant who will give you face time and is actually interested in your business. Managing expenses Even with just one person working in your business (you) keeping track of expenses and figuring out what you can actually expense can be a pain. With a few people in the team, managing expenses can take up days per month just processing them. Firstly, even if it's just you submitting expenses, get a simple process in place and follow it. If you using a product like Xero then submitting expenses is made easier with their mobile phone app. You have to input the data and take a photo which can be time-consuming, if you'd rather just submit a photo then you can use a solution like Receipt Bank or Expensify who then key in the data and code it back into your accounts (you have to set this up and check it though). Finally, figure out how to code expenses correctly in your accounting software and what you can and can't reclaim tax on. You might even realise that you can bill your client for expenses (which is always good)! Remember any time not spent servicing clients or selling products or services is a cost to you, lawyers have worked out how to bill 100% of their time, can you? Managing multiple applications to achieve a task This is a problem that we see a lot in terms of taking payments. For example, if you've got a customer on the phone and you want to take a payment for an invoice or product. You have to find their account in one piece of software, open up your payment providers website or get the point of sale terminal. Copy the details across, name, address etc (don't make any mistakes) then you ask them for the card details, whatever you do don't write these down! Then they hang up and hopefully, the payment goes through for the correct customer. We reckon the fastest you can do that is 9 minutes, with Bolt we've got that process down to less than a minute in certain circumstances. That's good for you and your customers. Another example is with accounting software, in the top three software solutions, you can't actually produce a cash flow forecast, which is the number one thing you need to run a healthy business. You have to do this separately or pay for add-ons. Overall a way to solve this frustration is to note down where the challenges and gaps are, what's costing your business and customers time and money? Then go about putting solutions in place, these might be offline or online, but if you understand the problem correctly you can start to seek advice from your accountant or other service providers or even the internet. Remember you need to get as much time back to work on your business, NOT in your business! Payroll There are two elements to payroll 1) Doing the payroll and issuing payslips. 2) Paying your staff. I would strongly advise giving your payroll to your accountant and ideally, they will run it from your accounting system, if not they will do it on their own. They will also issue payslips to your employees if setup correctly. On the day the payslips are issued you will have to log into your bank's website and make all the payments, so obviously, you'll want to setup each payee so you can send payment as quickly as possible. We wouldn't recommend setting up an automated payment just in case the payslip advice differs from last month or the company doesn't have the funds in the account. Most of these challenges can be solved in the following ways: - Being informed and being aware of them in the first place - Having the right team around you including people like accountants and bookkeepers. - Spending some time combating them so in the future things are as efficient as possible. - Outsourcing as much as possible, - but getting as much management reporting as possible you can feel in control. - Setting time aside to work on your business instead of getting caught up in delivering a service or product all the time. BTW. If you're interested in some of the new banking players who are revolutionising the industry then you can check out: - Revolut - Tide - Starling ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/ --- # Streamline Accounts Receivable: 5 Proven Strategies | Shuttle > Learn 5 proven strategies to streamline accounts receivable, reduce DSO, and accelerate cash flow with automation, payment links, and smarter dunning. # Streamline Accounts Receivable: 5 Proven Strategies By Nick Dunse, December 18, 2025 Learn 5 proven strategies to streamline accounts receivable, reduce DSO, and accelerate cash flow with automation, payment links, and smarter dunning. Talk to us Make enabling payments for your platform and merchant users easy. Accounts receivable is the lifeblood of any business, yet it remains one of the most common operational bottlenecks. Late payments, manual follow-ups, and disconnected invoicing workflows drain resources and choke cash flow. For platforms serving SMBs -- and especially MSP and IT service providers -- the problem compounds: every client your platform serves has their own AR headaches, and those headaches become yours. The good news? Streamlining accounts receivable is no longer a back-office aspiration. With the right strategies and tools, you can cut days sales outstanding (DSO), reduce manual effort, and give your customers faster, easier ways to pay. This guide covers five proven strategies to streamline AR, plus specific advice for MSPs and platforms looking to embed payment automation. ## Why Accounts Receivable Becomes a Bottleneck Before diving into solutions, it helps to understand why AR stalls in the first place. Most businesses -- and the platforms that serve them -- struggle with a combination of these issues: - Manual invoicing: Staff create, send, and track invoices by hand -- or through disconnected tools that don't talk to each other. - Limited payment options: Invoices that only accept bank transfers or cheques add friction. Customers delay payment simply because paying is inconvenient. - No automated follow-up: Without dunning sequences, overdue invoices sit in inboxes until someone remembers to chase them. - Reconciliation gaps: Payments arrive through different channels with inconsistent references, making it hard to match payments to invoices. - Scaling pain: What works for 50 invoices a month breaks down at 500. Platforms that onboard new merchants inherit every one of these problems at scale. The result? DSO creeps up, working capital shrinks, and finance teams spend more time chasing payments than analysing performance. Streamlining receivables means attacking each of these friction points systematically. ## Strategy 1: Automate Invoice Generation and Delivery The fastest way to streamline accounts receivable is to remove humans from the invoice creation loop. Automated invoicing ensures that every completed job, subscription renewal, or milestone triggers an invoice immediately -- no delays, no data-entry errors. What to automate: - Recurring invoices for subscription or retainer-based services. - Invoice delivery via email with a direct pay link embedded in the body. - Line-item population from your CRM, PSA, or billing system so invoices are accurate from the start. - Automatic PDF and email formatting that matches your brand (or your platform's merchant brand). For platforms, invoice automation isn't just an internal improvement -- it's a feature you can offer to your merchants. When your platform generates and sends invoices on behalf of SMBs, you remove a major source of churn and increase stickiness. ## Strategy 2: Offer Multiple Payment Methods on Every Invoice One of the simplest accounts receivable process improvement ideas is also one of the most overlooked: let customers pay the way they want to. If your invoice only supports bank transfer, you're adding days -- sometimes weeks -- to your collection cycle. Modern AR collection should support: - Credit and debit cards -- instant settlement, familiar to every customer. - ACH and direct debit -- lower fees for larger invoices. See our guide on maximising efficiency with ACH payment links for practical tips. - Digital wallets -- Apple Pay, Google Pay, and similar options reduce checkout friction on mobile. - Open banking -- account-to-account payments that combine the cost advantage of bank transfer with the speed of card payments. Offering choice doesn't just accelerate collection -- it signals professionalism. Customers are more likely to pay promptly when the experience feels modern and frictionless. As we explored in From Chase to Choice: Give Customers Easier Ways to Pay Your Invoices, the shift from chasing payments to enabling self-service payment is transformative for AR teams. ## Strategy 3: Use Payment Links to Accelerate Invoice Collection Payment links are URLs that open a hosted checkout page pre-filled with the invoice amount and customer details. Instead of asking customers to log into a portal, find the right invoice, and enter payment details, you send them a single link. One click, one payment, done. This approach is particularly powerful for AR because: - Links can be embedded directly in invoice emails, SMS reminders, or even WhatsApp messages. - Each link is unique to a specific invoice, so reconciliation is automatic. - Payment confirmation can trigger automatic status updates in your billing system. - Customers can pay from any device without creating an account or remembering credentials. We've written extensively about this approach in Payment Links on Invoices: The Game-Changing Strategy Your Business Needs. The short version: businesses that embed payment links in invoices typically see DSO drop by 30-50% within the first quarter. For a deeper look at the cash flow impact, see How to Use Payment Links to Improve Cash Flow. ## Strategy 4: Implement Automated Dunning and Payment Reminders Dunning -- the process of systematically following up on overdue invoices -- is where most AR teams waste the most time. Manual dunning means someone checks a spreadsheet, drafts an email, and hopes the customer responds. Automated dunning replaces all of that with a rules-based sequence. A well-designed dunning workflow typically looks like this: - Day 0: Invoice sent with payment link. - Day 3: Friendly reminder email -- "Just checking you received this." - Day 7: Second reminder with the payment link highlighted. - Day 14: Firmer notice -- "Your invoice is now overdue." - Day 30+: Escalation to phone follow-up or collections. Every reminder should include a payment link so the customer can settle the invoice the moment they open the email. The goal is to make paying easier than ignoring the reminder. Automated dunning also generates data: open rates, click-through rates on payment links, and response times. This data helps you refine your sequences and identify chronically late payers before they become bad debt. ## Strategy 5: Streamline Reconciliation with Automated Matching Reconciliation is the final mile of the AR process -- and it's where many streamlined AR management efforts fall apart. Even if you automate invoicing, offer multiple payment methods, and run dunning sequences, the process isn't complete until payments are matched to invoices and your books are up to date. Key reconciliation improvements: - Use unique invoice references: Every payment link and invoice should carry a unique reference that flows through to your bank statement or payment provider. - Automate matching: Tools that auto-match incoming payments to open invoices based on amount, reference, or customer ID eliminate hours of manual work. - Handle partial and overpayments: Your system should flag exceptions rather than silently misallocating funds. - Real-time sync: When a payment link is used, the payment status should update in your billing system immediately -- not after a nightly batch process. Payment links are especially valuable here because each link is tied to a specific invoice. When a customer pays via a payment link, the reconciliation is instant and automatic -- no guessing which invoice a bank transfer relates to. ## Streamline MSP Accounts Receivable: Tips for IT Service Providers Managed service providers face unique AR challenges. Most MSPs bill on a recurring basis -- monthly retainers, per-seat licensing, project milestones -- which means the invoicing volume is high but the amounts are predictable. Despite this, many MSPs still rely on manual processes that create unnecessary friction. Here's how to streamline MSP accounts receivable specifically: - Integrate billing with your PSA: ConnectWise, Datto Autotask, and HaloPSA all support billing integrations. When a ticket closes or a project milestone completes, the invoice should generate automatically. - Use payment links for ad-hoc charges: Recurring invoices may auto-charge via stored cards, but one-off project work or hardware purchases need a frictionless payment method. Payment links solve this without requiring the customer to call in card details. - Segment your dunning by client tier: Enterprise clients on net-30 terms need a different follow-up cadence than SMBs on net-7. Configure your dunning sequences accordingly. - Offer a client payment portal: A white-labelled portal where clients can view outstanding invoices, payment history, and pay with one click reduces support tickets and speeds collection. - Automate credit-hold policies: For MSPs that provide ongoing services, automatically flagging accounts that exceed payment terms helps enforce discipline without awkward conversations. If you're building or running an MSP platform, embedding these capabilities directly into your software transforms AR from a cost centre into a competitive advantage. Learn how Shuttle's embedded payments work for platforms. ## AR Automation Tools: What to Look For The AR automation market has matured significantly. Whether you're evaluating standalone tools or looking to build AR features into your own platform, here are the capabilities that matter most: - Multi-channel delivery: Invoices and reminders should go out via email, SMS, and in-app -- not just one channel. - Embedded payment acceptance: The tool should support card, ACH, and open banking payments directly within the invoice. No redirects to third-party portals. - API-first architecture: For platforms that want to embed AR automation, a REST API with webhooks is non-negotiable. You need to trigger invoices, generate payment links, and receive payment confirmations programmatically. - White-label support: Your merchants' customers should see the merchant's brand, not yours. This matters for trust and professional appearance. - Reporting and analytics: DSO tracking, ageing reports, collection rate dashboards, and exportable data for your accounting team. Shuttle Global provides the payment layer that AR automation tools need. Our payment links, embedded checkout, and multi-method acceptance can be integrated into any invoicing or billing platform via API. Book a discovery call to see how it works. ## Measuring AR Performance: DSO, Collection Rate, and Beyond You can't improve what you don't measure. Streamlining receivables requires tracking the right metrics so you know what's working and where to focus next. Days Sales Outstanding (DSO) is the headline metric. It measures the average number of days it takes to collect payment after an invoice is issued. The formula is simple: (Accounts Receivable / Total Credit Sales) x Number of Days. A lower DSO means faster collection. Most industries target 30-45 days; best-in-class AR operations achieve under 25. Collection Effectiveness Index (CEI) measures the percentage of receivables collected within a given period relative to the total available for collection. A CEI above 80% is good; above 90% is excellent. Additional metrics worth tracking: - Average days delinquent (ADD): How far past terms your average overdue invoice sits. - Bad debt ratio: The percentage of receivables written off as uncollectable. - Payment method adoption: What percentage of customers use payment links vs. manual bank transfer? Higher link adoption correlates with faster collection. - First-reminder resolution rate: How many invoices are paid after the first dunning email? A high rate means your messaging and payment experience are effective. Track these monthly and compare against your own historical baseline. Industry benchmarks are useful for context, but the most meaningful improvements come from competing against your own previous performance. ## Frequently Asked Questions ### What is the fastest way to streamline accounts receivable? The single highest-impact change is embedding payment links in every invoice and reminder email. This removes the biggest source of friction -- the customer having to figure out how to pay -- and typically reduces DSO by 30-50% within the first quarter. Pair this with automated dunning for compounding results. ### How can MSPs specifically improve their AR process? MSPs should integrate billing with their PSA tool (ConnectWise, Autotask, HaloPSA) so invoices generate automatically when work is completed. For recurring services, set up auto-charge with stored payment methods. For ad-hoc work, use payment links. Segment dunning by client tier -- enterprise clients on net-30 need different messaging than SMBs on net-7. ### What is a good DSO target? Most B2B businesses target 30-45 days. Best-in-class operations with automated invoicing, payment links, and dunning sequences achieve under 25 days. Your target depends on your industry and payment terms, but any reduction from your current baseline represents real cash flow improvement. ### How do payment links help with reconciliation? Each payment link is tied to a specific invoice with a unique reference. When a customer pays via a link, the payment is automatically matched to the correct invoice -- no manual reconciliation needed. This eliminates the common problem of bank transfers arriving with incomplete or incorrect references. ### Can platforms embed AR automation for their merchants? Yes. Platforms can use payment infrastructure APIs to offer invoicing, payment links, dunning, and reconciliation as embedded features within their own software. This is particularly valuable for vertical SaaS platforms serving industries with heavy AR workflows -- MSPs, legal, accounting, and construction among them. Shuttle's embedded payments platform is built specifically for this use case. ## Start Streamlining Your AR Today Streamlining accounts receivable isn't a single project -- it's a series of compounding improvements. Start with the highest-impact change (payment links on every invoice), layer in automation (dunning sequences, automated invoicing), and build toward full reconciliation automation. For platforms and MSPs, the opportunity goes further: embed these capabilities into your own product and turn AR automation into a feature that drives merchant retention and revenue. Ready to add payment links and embedded checkout to your invoicing workflow? Book a discovery call with Shuttle and we'll show you how it works. ## Related Reading - How to Add a Pay Now Button to Your Invoices - Payment Reminder Email Templates (With Pay Now Links) - How to Reduce Debtor Days: 10 Strategies That Actually Work Explore More ### How to Get Payments Off Your Product Roadmap ### What Happens When Your Only Payment Processor Cuts You Off ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ### How to Switch Twilio Pay Connectors Without Breaking Your Call Flow ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [maximising efficiency with ACH payment links](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [From Chase to Choice: Give Customers Easier Ways to Pay Your Invoices](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [Payment Links on Invoices: The Game-Changing Strategy Your Business Needs](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [How to Use Payment Links to Improve Cash Flow](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [Learn how Shuttle's embedded payments work for platforms](/platforms/) - [Book a discovery call](/discovery/) - [Shuttle's embedded payments platform](/platforms/) - [Book a discovery call with Shuttle](/discovery/) - [How to Add a Pay Now Button to Your Invoices](/guides/pay-now-button-invoices/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [How to Reduce Debtor Days: 10 Strategies That Actually Work](/guides/reduce-debtor-days/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideWhat Happens When Your Only Payment Processor Cuts You Off→](/guides/single-psp-risk/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [GuideHow to Switch Twilio Pay Connectors Without Breaking Your Call Flow→](/guides/switch-twilio-pay-connector/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/5-real-merchant-workflows-that-work-better-with-payment-links/ --- # 5 Payment Workflows That Work Better With Payment Links | Shuttle > Discover how payment links streamline invoice collection, hotel deposits, call centre payments, subscriptions, and marketplace payouts for merchants. # 5 Payment Workflows That Work Better With Payment Links By Nick Dunse, December 18, 2025 Discover how payment links streamline invoice collection, hotel deposits, call centre payments, subscriptions, and marketplace payouts for merchants. Talk to us Make enabling payments for your platform and merchant users easy. Most payment workflows still rely on manual steps that slow down collection, frustrate customers, and introduce compliance risk. Whether it's chasing invoices, taking card details over the phone, or reconciling marketplace payouts, the friction compounds as transaction volume grows. Payment links solve this by giving merchants a single, shareable URL that opens a hosted checkout page. No card terminal needed. No manual data entry. No PCI scope creep. The customer clicks, pays, and the funds are routed automatically. Below are five real merchant workflows where payment links dramatically improve outcomes -- plus how to automate, scale, and secure those workflows as volume increases. ## 1. Invoice Collection and Accounts Receivable ### The Problem Accounts receivable teams spend hours chasing payments. They send PDF invoices by email, wait for bank transfers, and manually reconcile each payment against open invoices. The average B2B invoice takes 47 days to collect. Late payments strain cash flow and eat into margins -- especially for SMBs that cannot afford to carry 60-day receivables. ### How Payment Links Solve It A payment link embedded directly in an invoice email or PDF turns a passive document into an active checkout. The customer clicks, confirms the amount, enters their card or bank details, and pays immediately. The merchant's system records the payment against the correct invoice automatically -- no manual matching required. - Reduces days sales outstanding (DSO) by making it frictionless to pay on receipt - Eliminates reconciliation overhead -- each link carries metadata that ties the payment to the invoice - Supports automated reminders -- unpaid links can trigger follow-up sequences without manual chasing ### Real-World Example An accounting SaaS platform embeds payment links into every invoice its merchants generate. Instead of waiting for bank transfers, merchants get paid in 2-3 days on average. The platform earns a margin on each transaction and reduces support tickets about missing payments by over 40%. Read more about how payment links on invoices transform collection rates. ## 2. Hotel and Travel Deposits and Pre-Authorisations Hotels, tour operators, and travel agencies routinely collect deposits and pre-authorisations before a guest arrives. The traditional process involves taking card details over the phone, emailing insecure PDF forms, or requiring guests to fax authorisation letters. Each method introduces PCI compliance risk, staff overhead, and a poor guest experience. No-show rates climb when the deposit process is too cumbersome. A payment link sent via email or SMS after booking confirmation lets guests pay their deposit instantly from any device. The hosted checkout handles PCI compliance -- the hotel never touches raw card data. Links can be configured for partial amounts (deposits), full pre-payment, or tokenised pre-authorisations that are captured at check-in. - Reduces no-shows by securing commitment before arrival - Eliminates paper-based authorisation forms and the PCI liability they carry - Works across channels -- send the same link via email, SMS, WhatsApp, or OTA messaging A boutique hotel chain replaces its faxed authorisation forms with payment links sent automatically by its PMS (property management system). Deposit collection rates rise from 65% to over 90%, no-show revenue loss drops, and front-desk staff reclaim hours previously spent on phone calls. For a deeper look at payment automation in hospitality, see our guide to AI voice payments for hotels and travel. ## 3. Call Centre Phone Payments Contact centres handle millions of payments daily -- utility bills, insurance premiums, debt repayments, ticket bookings. The conventional approach is for the agent to read out card fields while the customer dictates digits. This puts the contact centre squarely in PCI scope, requires expensive call recording redaction, and slows average handle time (AHT). A single data breach can cost millions in fines and reputational damage. During the call, the agent generates a payment link and sends it to the customer via SMS or email. The customer completes payment on the hosted checkout while still on the line. The agent sees a real-time confirmation without ever hearing or seeing card details. The contact centre stays out of PCI scope. - Keeps PCI scope off the contact centre -- no DTMF masking or pause-and-resume recording needed - Reduces AHT by 30-60 seconds -- customers type faster than they dictate - Higher first-call resolution -- payment is confirmed before the call ends A utilities company processes 50,000 phone payments per month. After switching to an agent-initiated payment link workflow, they reduce PCI audit costs by 60% and cut AHT by 45 seconds per payment call -- saving over 37,000 agent-hours annually. Learn more about modernising contact centre payment workflows. ## 4. Subscription Setup and Recurring Billing Setting up recurring billing typically requires the customer to create an account, navigate a multi-step checkout, and agree to stored credential terms. Every additional step in the funnel increases abandonment. For service businesses -- gyms, SaaS tools, cleaning companies, membership clubs -- each lost signup represents months of recurring revenue that never materialises. A payment link configured for recurring billing captures the first payment and tokenises the card in a single step. The customer clicks, pays the first instalment, and authorises future charges -- all on one page. No account creation required. The merchant's billing system takes over for subsequent charges automatically. - Reduces checkout abandonment -- single-page setup instead of multi-step registration - Tokenises securely -- the hosted checkout handles card storage, keeping the merchant's PCI scope limited - Shareable across channels -- embed in onboarding emails, landing pages, social bios, or QR codes A fitness studio chain embeds payment links in its class-booking confirmation emails. New members complete their first payment and set up monthly billing in one click. Conversion from trial to paid membership increases by 25%, and involuntary churn (failed card charges) drops thanks to up-to-date tokenised credentials. ## 5. Marketplace Split Payments Marketplaces and platforms need to collect a single payment from a buyer and split the funds across multiple sellers -- minus a platform fee. Traditional implementations require deep payment gateway integrations, escrow accounts, and complex payout logic. For platforms that are not payment specialists, building and maintaining this infrastructure is a distraction from their core product. A payment link pre-configured with split rules handles collection and disbursement in one transaction. The buyer pays through the hosted checkout. The payment layer automatically splits the funds: a percentage to the seller, a fee to the platform, and any applicable taxes or holds. No manual payouts. No reconciliation spreadsheets. - One payment, automatic splits -- buyer pays once, funds route to all parties - Platform fee capture built in -- no separate invoicing between platform and seller - Works without a PayFac licence -- the payment layer handles fund flows and regulatory requirements A home services marketplace generates a payment link for each completed job. The homeowner pays through the link, and the platform automatically splits funds -- 85% to the tradesperson, 15% platform fee. Payouts arrive in the tradesperson's account within two business days with no manual intervention. ## How to Automate Payment Workflows With Payment Links The workflows above become exponentially more powerful when automated. Instead of an agent manually generating a link and pasting it into an email, the payment link is created programmatically and delivered without human intervention. Here is how to automate payment workflows using payment links: - API-driven link generation. Your ERP, CRM, or booking system calls a payment API to create a link whenever a triggering event occurs -- invoice created, booking confirmed, support ticket opened. - Webhook-based status updates. When the customer pays, a webhook fires back to your system to update the order status, mark the invoice as paid, or trigger fulfilment. - Automated reminders. If a link is not paid within a defined window (24 hours, 3 days, 7 days), the system automatically sends follow-up emails or SMS messages with the same link. - Batch link creation. For high-volume use cases like monthly invoicing runs, generate thousands of unique payment links in a single API call and distribute them in bulk. Platforms that embed payments on behalf of their merchants can offer this automation as a native feature -- turning payment collection from a merchant headache into a platform differentiator. See how embedded payment infrastructure works. ## How to Scale Payment Workflows Across Merchants Automating a single workflow is useful. Scaling that workflow across hundreds or thousands of merchants is where the real leverage lives. Here is what scaling payment workflows requires: - Multi-tenant architecture. Each merchant needs isolated payment links, branding, and reporting -- but the platform manages it all through a single integration. - White-label checkout pages. Payment links should render the merchant's brand -- logo, colours, domain -- not a generic third-party page. This builds trust and increases conversion rates. - Centralised reporting and reconciliation. The platform sees aggregate payment data across all merchants. Each merchant sees only their own transactions. - Flexible payout scheduling. Different merchants may need daily, weekly, or monthly settlement cycles. The payment layer handles this without bespoke logic per merchant. A payment layer sits between the platform and its PSP (payment service provider), abstracting the complexity of multi-merchant payment workflows into a clean API. This lets platforms scale payment operations without building -- or maintaining -- their own payments infrastructure. ## How to Secure Payment Workflows and Stay PCI Compliant Every payment workflow must handle sensitive card data responsibly. The PCI Data Security Standard (PCI DSS) sets the rules, and non-compliance carries fines of up to $100,000 per month plus liability for any breach. Payment links reduce PCI scope dramatically because the hosted checkout page handles all card data -- the merchant's systems never see, store, or transmit it. Key security benefits of payment link workflows: - No card data in your environment. The hosted checkout is served from a PCI Level 1 certified environment. Your servers, databases, and call recordings never contain PAN data. - Reduced SAQ scope. Merchants using hosted payment pages typically qualify for SAQ A -- the simplest self-assessment questionnaire -- instead of the far more burdensome SAQ D. - Built-in fraud prevention. Modern hosted checkouts include 3D Secure (SCA), address verification, velocity checks, and device fingerprinting by default. - Expiring links. Payment links can be set to expire after a defined period, reducing the window for fraudulent use of shared URLs. For a comprehensive overview of PCI compliance requirements and what they mean for your business, read our introduction to PCI compliance for merchants and service providers. ## Frequently Asked Questions ### What types of businesses benefit most from payment link workflows? Any business that collects payments outside a traditional e-commerce checkout benefits from payment links. This includes service businesses (invoicing), hospitality (deposits), contact centres (phone payments), subscription businesses (recurring billing setup), and marketplaces (split payments). The common thread is that the payment happens away from a website cart -- via email, SMS, phone call, or in-person interaction. ### How do payment links differ from a standard checkout page? A checkout page is part of a website's purchase flow -- the customer adds items to a cart and proceeds to pay. A payment link is a standalone URL that opens a hosted payment page directly, without requiring the customer to visit a website or navigate a cart. Payment links can be shared via any channel (email, SMS, WhatsApp, QR code, social media) and are pre-configured with the amount, currency, and metadata for the specific transaction. ### Are payment links secure enough for high-value transactions? Yes. Payment links hosted on a PCI Level 1 certified environment are as secure as any major e-commerce checkout. They support 3D Secure authentication, TLS encryption, tokenisation, and fraud screening. For high-value transactions, additional controls like link expiry, single-use restrictions, and IP-based access rules add further protection. ### Can payment links support multiple currencies and payment methods? Yes. A well-configured payment link can present the checkout in the customer's local currency and offer payment methods relevant to their region -- cards, bank transfers, digital wallets (Apple Pay, Google Pay), and local payment methods like iDEAL or Pix. The payment layer determines which methods to display based on the customer's location and the merchant's configuration. ## Get Started Payment links turn complex merchant workflows into single-click transactions. Whether you are a merchant looking to streamline your own payment collection, or a platform looking to offer payment workflows to your merchants, the pattern is the same: generate a link, share it, collect the payment, and let automation handle the rest. If you are building a platform that needs to embed payment workflows for merchants, book a discovery call to see how Shuttle's payment layer can power your payment links, splits, and automation -- with far less PCI overhead. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [how payment links on invoices transform collection rates](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [AI voice payments for hotels and travel](/guides/ai-voice-payments-hotels-travel/) - [DTMF masking](/guides/dtmf-payments/) - [modernising contact centre payment workflows](/guides/contact-centre-payments/) - [See how embedded payment infrastructure works](/platforms/) - [introduction to PCI compliance for merchants and service providers](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [book a discovery call](/discovery/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/5-reasons-you-shouldnt-build-payments-integrations-in-house/ --- # 5 Reasons you shouldn't build payments integrations in-house | Shuttle > Five reasons SaaS platforms should avoid building payment integrations in-house: cost, complexity, compliance, maintenance, and time-to-market. # 5 Reasons you shouldn't build payments integrations in-house By Nick Dunse, December 18, 2025 Five reasons SaaS platforms should avoid building payment integrations in-house: cost, complexity, compliance, maintenance, and time-to-market. Now obviously we're biased as to the reasons why you shouldn't go and build many integrations to payments providers, but working with our customers over the last few years, we can honestly say there is a very good case to buy and not build. After all, you're probably a SaaS company selling a product which means that your customers don't need to build their own version of the solution you're selling; so we believe you'll get what we're talking about. I remember, several years ago now, a digital architect friend said to me, whatever you do, don't build your own CRM, we did it anyway and looking back it's one of the professional decisions that we made as a team that I would change. Lesson learned. And now, thankfully, we work in a world with maturing SaaS offerings available off-the-shelf. I assume if you're reading this you're running/working in a SaaS business and your product has payments as a feature. You might be an e-commerce platform, or perhaps your users have invoices within your product that they'd like to get paid online. Each one of your customers wants to use their preferred payments partner and so to win and retain your customer you need to work with their payment provider. We've seen our clients win more and larger customers by being able to work with their preferred payments providers. The challenge is that the global payments landscape is ever-expanding with local payment methods, disruptive technologies and a highly competitive market to boot. Just look at the rise of GoCardless, making an outdated, clunky payment method work, or BitCoin payment gateways, making accepting the digital currency a viable receivable payment method. And the future, at least, in the UK and EU is exciting with the possibilities that open banking is bringing in terms of transforming payment rails. So here are the 5 6 reasons why you shouldn't build payments integrations in-house: 1 - Do you want to build and maintain an in-house team? The first thing you need to consider is how many payment providers you think you want to work with. I suspect the answer, if it is greater than one, is that you just don't know, it depends on demand. Well, I can tell you that on average our SaaS clients are seeing at least six payment providers being used by their customers. You're going to have to employ at least one full-time developer and customer support person to handle this initial work, maintain and support these integrations. Then you'll probably want to employ a partnership person to ensure you've got agreements in place with payment providers. Do you want to become payments experts or domain experts? It's hard to be both. 2 - Every payments API is different! What! There's no best practice payments API out-there? That's correct, every provider has built their own, with their own special nuances, error codes, capabilities, terminology etc. If you're doing deeper integrations, going through certification with these providers then you've got a lot of work on your hands; you'll be lucky if you can launch one new integration every two months with the team outlined in the first point. All the market fragmentation has created a bit of a mess, there's no cookie-cutter way to do it effectively, yes you could try and use some open-source library projects but that creates associated risks and although you'll cut your development time down it still requires you to understand each payment provider. We've homogenised all the mess into our API and platform, one language, one view, one integration. 3 - You will have to become PCI DSS Level 1 compliant PCI compliance is a rule set imposed by the card industry, you can check our other blog posts to find out more information about it. What it means is that your system is now in scope to be audited by a third party on a regular basis. And that process is expensive, not only to pay the auditors and certifiers but to make the necessary system and internal process changes to comply. If you want to work with some payment providers they will only do so if you are PCI DSS Level 1. Moving this dependency outside of your system is a lot simpler. You could do this by simply using payment gateway hosted processes (if they exist). But then every checkout experience is different, not branded correctly and potentially you lose control and end sales. 4 - You'll have to build more product Checkout screens, payment forms, merchant onboarding, views of payment data, refunds, recurring contract management, translations - the list goes on. What you really want is a way of pulling the data and populating your system in a simple way with best of breed pre-built components accessible where you need them. Add a few more people to your team and months on to your development roadmap if you do want to go down this road. 5 - Speed to market Want to work with customers who need local payment providers in a new country? You'll have to tell them to wait for a few months whilst you build out the capabilities with technologies that you've never worked with before. Hmmm... That might make it harder to win these initial customers in this new market. It's not just speed to the global market either, there are new payment methods, legislation and opportunities within local markets. 6 - Bonus - Monetisation Payments can present new revenue line possibilities for software vendors, this might go some way to offsetting building a payments function in-house, but it's going to take a long time see return and negotiating favourable deals will be challenging in the early days. We provide revenue line possibilities out of the box on some of our plans and down the road with further value add services. Conclusion For most SaaS vendors it's going to come to a simple build vs buy approach, but we know that the build price is unwieldy and challenging to forecast, whilst the opportunity cost of not being able to go to market quickly is huge! So, yes you will have to do one payments integration (into Shuttle), but why not do it into a trusted partner that helps you grow and protects you from ever-changing payments future... Please do book some time to talk to us about the opportunities, after all you wouldn't build your own CRM these days would you?! ## Related Reading Explore More ### Shuttle vs Building Payment Infrastructure In-House ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### How to Get Payments Off Your Product Roadmap ### How CCaaS Platforms Add Payment Capabilities Without Building In-House ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [ComparisonShuttle vs Building Payment Infrastructure In-House→](/vs/build-in-house/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideHow CCaaS Platforms Add Payment Capabilities Without Building In-House→](/guides/how-ccaas-platforms-add-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/7-objections-bosses-raise-about-improving-ar-and-how-to-overcome-them/ --- # 7 Objections Bosses Raise About Improving AR (and How to Overcome Them) | Shuttle > Why Payment Links Might Be the Upgrade Your CFO Doesn't Know They Need # 7 Objections Bosses Raise About Improving AR (and How to Overcome Them) By Nick Dunse, July 1, 2025 Why Payment Links Might Be the Upgrade Your CFO Doesn't Know They Need Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. If you work in Accounts Receivable, chances are you've been stuck chasing payments with manual bank transfers, confusing remittance emails, or even cheques (!). You know there's a better way. But when you suggest something like Payment Links, your boss might shoot it down with a familiar phrase: "What we have already works." The reality? It doesn't. You're overworked. Customers delay payments because it's a pain to pay. Cash is slow to hit the account. And your software tools aren't talking to each other. Here are the 7 most common objections from finance leadership -- and how to help them see the real cost of doing nothing. 1. "What we have already works." On the surface, it does work -- eventually. But here's the hidden cost: Time wasted on manual follow-ups Slow Days Sales Outstanding (DSO) Customer confusion Staff burnout 💡 Overcome it:Help them see that "works" isn't the same as "works well." Show them the hours you spend chasing payments manually and how that impacts your workload and the business's cash flow. Instead say: "We don't need to replace our systems. This just lets customers pay faster and makes our job easier -- with no disruption." 2. "I don't want to pay card fees." This is a big one. Many leaders panic at the idea of losing 2.9% of invoice value. 💡 Overcome it: Emphasise ACH is low-cost or free. Card payments can be optional or even surcharged. Faster payment = earlier revenue recognition and better cash position. "We can default to ACH, but let customers choose card if they need flexibility. It gets us paid faster, and that's worth more than the fee." 3. "It sounds complicated to implement." They imagine big IT projects, data migration, and disruption. 💡 Overcome it:Explain that Shuttle Payment Links don't require changing anything. They work with what you already use -- QuickBooks, Xero, NetSuite, email, or SMS. "This is plug-and-play. No platform switch, no IT involvement. It's just a payment link." 4. "Our customers prefer manual bank transfers." Some do. But many don't -- they just have no alternative. 💡 Overcome it:Frame it as offering a better experience. A payment link doesn't replace manual transfers -- it simply adds a faster, simpler option. "If even 20% of customers use the link, that's 20% less chasing and reconciling we have to do." 5. "There's no ROI here." If it looks like just a link, they'll think it's just another feature. 💡 Overcome it:Connect the dots between: Faster payments = lower DSO Less chasing = lower overhead Better experience = faster renewals and improved customer NPS "This isn't just a payment tool -- it's a cashflow, time, and team efficiency tool." 6. "It'll mess up reconciliation." They're thinking of partial payments, unknown references, and messy statements. 💡 Overcome it:Show that payment links from Shuttle auto-match with invoices and push real-time data into your ERP or accounting system. "Actually, it makes reconciliation easier -- because we get context with every payment, not just a cryptic ACH reference." 7. "We'll look at this next quarter." A classic stall tactic. Usually code for "I don't see the urgency." 💡 Overcome it:Remind them of how many overdue invoices, hours of admin, and delayed payments will occur between now and then. "We can pilot this with just one segment or client and see results before month-end. Low risk, high impact." ✅ Why It's Worth Overcoming These Objections Because you're tired of: Chasing emails Explaining payment instructions Matching unknown ACHs to invoices Apologising for "broken" payment experiences And more importantly -- because your business deserves to get paid faster, with less friction. 💡 The Smartest Upgrade You'll Make All Year With Shuttle Payment Links, you can: Add payment links to any invoice, email, or SMS Let customers pay via ACH or card Keep using the ERP or invoicing system you already have Automate the entire workflow with Zapier All without making your boss feel like it's "another system" to deal with. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/ --- # 7 ways merchants can save money on payment provider fees | Shuttle > Seven practical ways merchants can reduce payment processing fees: negotiate rates, optimise routing, reduce chargebacks, and choose the right provider. # 7 ways merchants can save money on payment provider fees By Nick Dunse, December 20, 2025 Seven practical ways merchants can reduce payment processing fees: negotiate rates, optimise routing, reduce chargebacks, and choose the right provider. You might have signed up to a payment service provider solution because it was the one recommended to you, or you just picked a brand name that you knew as a consumer. The reality is that there are lots of options out there to save money; depending on what country you're in and what you sell you'll need some help deciding which is right for you. Are cheaper payment fees possible? If you're selling on a certain platform, like Shopify, Amazon, Apple or Google you may be almost forced to collect payments in a certain way, which means it's going to be hard to get cheaper processing rates, but there still might be a couple of tricks in this article that can help you. Below is how you can get started, but before that, what we will say is that if you're not processing anything right now you will be given the list price and probably have to go through an online application process, depending on the provider this might take some time and they'll want to KYC you, yep cover you in lubricant... NO! Check you're legit - sorry. Let's get started -- Find the cheapest blended rate Find the providers in your region that can work with your type of product or service, have the functionality/integrations that you need and then compare on price. A blended rate is when a provider will say, regardless of card type it will cost you X% + $X. Revolut have just launched a payment gateway service undercutting other providers in the UK by 0.1% and giving immediate settlement times. Work with a provider that doesn't use a blended rate If you know you'll be processing more debit cards than credit cards and not have a high proportion of AMEX transactions you can find a provider who will give you a card type rate. Therefore, your fees will be cheaper if you're mostly processing these card types. Research all-in-one solutions vs separate solutions Companies like Authorize.net and Global Payments offer a merchant account and payment gateway, whilst companies like Stripe and PayPal sign you up with their chosen acquirer behind the scenes. And Checkout.com is touting an improved integrated solution from gateway through to their own acquiring service. Try to find a mix and match model vs an all-in-one solution and compare costs. For a merchant account issuer to acquire you as a merchant they will need to have a license to operate in your country. Negotiate a better deal with your current provider or a new one If you're already processing payments you can try to negotiate a better rate. You could do this based on card types processed, growth trajectory, historical chargeback rates or claiming you're a loyal customer 🙂 If you're processing more than $50k per month you should be able to get a better deal than the list price. Pay a flat monthly fee instead Some providers will give you a completely different fees model where for a flat monthly fee you can process X amount of payments and beyond that, there may be an additional processing fee. Cybersource, among others, do this. Pass level 2 & 3 data If you're doing B2B sales and your customers are using corporate cards you could definitely reduce your costs by passing the extra data points these cards offer (up to 100 data points). This, in turn, reduces the fraud risk, chargebacks etc, helping those companies who are buying from you manage and report on what is being purchased. This data is passed to the card schemes (VISA, Mastercard), they, in turn, reduce the interchange fee (the amount they charge your gateway). Do your FX somewhere else Payment service providers make a lot of money on FX, if you have international customers. Sometimes they could be making 3% for these card purchases and you may get hit twice by FX (on the international card and on the movement of the money back to your international bank account). What you can do is set up multi-currency accounts with banking providers so that you're settling currency into a local bank account and then moving that money based on the FX rates you can arrange. Here at Shuttle, we work with over 30 payment providers and have a recommendation service for merchants who need help finding the right partner. The service is free, check it out. ## Related Reading Explore More ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How to Reduce Payment Processing Fees Without Switching Providers ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [check it out.](/recommend?source=C0099) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow to Reduce Payment Processing Fees Without Switching Providers→](/guides/reduce-payment-processing-fees/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/a-merchants-guide-to-ecommerce-fraud-prevention/ --- # Ecommerce Fraud Prevention: A Merchant's Guide for 2026 | Shuttle > Prevent ecommerce fraud with 3D Secure, AVS, velocity checks, and ML detection. Cover fraud types, PCI compliance, and chargeback management. # Ecommerce Fraud Prevention: A Merchant's Guide for 2026 By Nick Dunse, June 10, 2021 Prevent ecommerce fraud with 3D Secure, AVS, velocity checks, and ML detection. Cover fraud types, PCI compliance, and chargeback management. Talk to us Make enabling payments for your platform and merchant users easy. Ecommerce fraud costs merchants billions every year -- and the problem is accelerating. Global card-not-present (CNP) fraud losses are projected to exceed $50 billion by 2027, driven by increasingly sophisticated attack vectors and the sheer growth of online transactions. For merchants and platforms processing payments online, fraud prevention is not optional. Every fraudulent transaction creates direct financial loss, triggers chargebacks with associated fees, and erodes customer trust. This guide covers the types of ecommerce fraud you need to understand, the tools and best practices for detection and prevention, and how to build a layered defence that protects revenue without creating excessive friction for legitimate customers. ## Types of Ecommerce Fraud Ecommerce fraud takes many forms. Understanding each type is the first step toward building effective merchant fraud prevention. Here are the most common attack patterns: ### Card Testing Fraud Fraudsters use stolen card numbers to make small test purchases -- often just a few pence -- to verify which cards are still active. Once confirmed, they use those cards for larger purchases elsewhere. Card testing attacks often come in rapid bursts, with dozens or hundreds of low-value transactions hitting your checkout within minutes. ### Friendly Fraud and Chargebacks Friendly fraud -- also called first-party fraud -- occurs when a legitimate cardholder makes a purchase and then disputes the charge with their bank, claiming the transaction was unauthorised or the goods never arrived. This is one of the most difficult fraud types to prevent because the transaction itself is genuine. Some estimates suggest friendly fraud accounts for 40-80% of all chargebacks. ### Account Takeover (ATO) In account takeover attacks, fraudsters gain access to a legitimate customer's account using stolen credentials, phishing, or credential stuffing. Once inside, they change shipping addresses, make purchases with stored payment methods, or extract personal data. ATO attacks have surged with the availability of breached credential databases on the dark web. ### Card-Not-Present (CNP) Fraud CNP fraud is the broadest category -- any fraudulent transaction where the physical card is not presented. This includes all online, phone, and mail-order fraud. Because the merchant cannot physically verify the card, CNP transactions carry higher risk and higher interchange fees. CNP fraud represents the vast majority of ecommerce fraud losses. ### Triangulation Fraud Triangulation fraud involves three parties: the fraudster, a legitimate customer, and a legitimate merchant. The fraudster sets up a fake storefront offering goods at attractive prices. When a customer places an order, the fraudster uses stolen card details to purchase the item from a real merchant and ships it to the customer. The real cardholder eventually disputes the charge, and the legitimate merchant bears the chargeback. ## The True Cost of Ecommerce Fraud The financial impact of fraud extends far beyond the value of the stolen goods or services. For every pound lost to fraud, merchants typically lose £3-4 when you factor in all associated costs: - Chargeback fees -- typically £15-25 per dispute, regardless of outcome - Lost merchandise -- goods already shipped are rarely recovered - Operational costs -- staff time spent on manual reviews, dispute responses, and fraud investigations - Increased processing fees -- high chargeback ratios trigger penalty programmes from card networks - Account termination risk -- exceeding Visa's 0.9% or Mastercard's 1.5% chargeback threshold can result in fines or loss of processing ability - Reputational damage -- customers who experience fraud on your platform may never return Prevention is always cheaper than remediation. A robust ecommerce fraud prevention strategy pays for itself many times over. ## Fraud Detection Tools and Technologies Modern ecommerce fraud protection relies on multiple layers of detection working together. No single tool catches everything -- effective fraud prevention combines several technologies. ### 3D Secure (3DS2) 3D Secure adds an authentication step during checkout where the cardholder's bank verifies their identity. The latest version, 3DS2, uses risk-based authentication -- low-risk transactions pass through seamlessly while higher-risk ones trigger additional verification. 3DS2 also shifts chargeback liability from the merchant to the issuing bank for authenticated transactions, making it one of the most valuable fraud prevention tools available. ### Address Verification Service (AVS) AVS checks the billing address provided at checkout against the address on file with the card issuer. Mismatches can indicate fraud. While AVS is not foolproof -- fraudsters sometimes have access to billing addresses -- it adds a useful signal to your risk scoring. AVS is most effective when used alongside other verification methods rather than as a standalone check. ### CVV Verification Requiring the card verification value (CVV) -- the 3 or 4 digit code on the card -- helps confirm that the person making the purchase has physical access to the card. Stolen card numbers obtained from data breaches often do not include the CVV, so this simple check blocks a meaningful percentage of fraudulent attempts. ### Velocity Checks Velocity checks monitor the rate and frequency of transactions to detect suspicious patterns. For example, you might flag or block activity where a single IP address attempts more than five transactions in ten minutes, a single card number is used across multiple accounts, or a shipping address receives orders from many different cards in a short period. Velocity checks are particularly effective against card testing attacks and bot-driven fraud. ### Machine Learning and AI-Based Detection Machine learning models analyse hundreds of data points per transaction -- device fingerprint, behavioural patterns, transaction history, geolocation, and more -- to generate real-time risk scores. Major payment processors offer built-in ML-based fraud tools: Stripe offers Radar, while Adyen provides RevenueProtect. These systems continuously learn from network-wide transaction data, improving accuracy over time. For platforms processing across multiple PSPs, a payment layer can normalise fraud signals and apply consistent rules regardless of which processor handles the transaction. ## Ecommerce Fraud Prevention Best Practices Beyond deploying specific tools, these best practices form the foundation of a strong ecommerce fraud prevention strategy: - Layer your defences. Use multiple fraud signals together. A transaction that passes AVS but fails velocity checks should still be flagged. No single tool is sufficient on its own. - Set risk thresholds by transaction value. Apply stricter verification for high-value orders. A £10 purchase might only need CVV, while a £500 order warrants 3DS2 plus manual review. - Monitor and tune rules regularly. Fraud patterns shift constantly. Review your decline rates and false positive rates monthly. Rules that were effective six months ago may now be blocking legitimate customers. - Track fraud metrics alongside conversion. Overly aggressive fraud rules hurt revenue more than the fraud itself. Measure false decline rates as carefully as you measure fraud rates. - Implement device fingerprinting. Track device characteristics (browser, OS, screen resolution, installed fonts) to identify returning fraudsters even when they change IP addresses or use new card numbers. - Require strong customer authentication. Where regulations permit, enforce two-factor authentication for account creation, login, and payment. This drastically reduces account takeover and CNP fraud. - Keep fraud rules separate from your core checkout flow. This lets you update fraud logic without redeploying your entire checkout, and makes it easier to A/B test rule changes. ## The Role of PCI Compliance in Fraud Prevention PCI DSS (Payment Card Industry Data Security Standard) compliance is not just a regulatory checkbox -- it is a fundamental component of ecommerce fraud protection. PCI compliance requirements are specifically designed to protect cardholder data from breaches that fuel downstream fraud. Key PCI requirements that directly prevent fraud include: - Encryption of cardholder data in transit and at rest - Tokenisation -- replacing card numbers with non-sensitive tokens that are useless to attackers - Network segmentation to limit the blast radius of any breach - Regular vulnerability scanning and penetration testing - Access controls that restrict who can view or process card data For platforms that embed payments into their software, PCI scope is a critical consideration. Using a PCI-compliant payment layer means your platform never touches raw card data, dramatically reducing both compliance burden and fraud risk for your merchants. ## Payment Gateway Fraud Features Most modern payment gateways include built-in fraud prevention capabilities. When evaluating a gateway or PSP, look for these features: - Real-time risk scoring -- ML-based risk assessment on every transaction before authorisation - Customisable rules engine -- ability to create, test, and deploy fraud rules specific to your business - Block and allow lists -- maintain lists of known fraudulent and trusted identifiers (emails, IPs, card BINs) - 3D Secure integration -- native support for 3DS2 with risk-based triggering - Dispute management -- tools to track, respond to, and analyse chargebacks - Network-level intelligence -- fraud signals derived from the processor's entire transaction network, not just your data Platforms that work with multiple PSPs face a unique challenge: fraud tools are typically siloed within each processor. A payment orchestration layer can aggregate fraud signals across all your payment providers, giving you a unified view and consistent rules regardless of which PSP processes a given transaction. ## Chargeback Management and Prevention Chargebacks are the most visible consequence of ecommerce fraud, and managing them effectively is essential. A proactive chargeback management strategy includes prevention, response, and analysis. Prevention strategies: - Use clear billing descriptors so customers recognise charges on their statements - Send order confirmation and shipping notification emails promptly - Make your refund policy easily accessible and honour it consistently - Provide responsive customer support -- many chargebacks happen because the customer could not reach the merchant - Use chargeback alert services (Ethoca, Verifi) to resolve disputes before they become formal chargebacks Response strategies: - Respond to every chargeback within the deadline -- even if you think you will lose, the data helps identify patterns - Compile compelling evidence packages: delivery confirmation, customer correspondence, IP logs, device data, AVS/CVV match results - Track win rates by reason code to focus your prevention efforts on the categories where you lose most Analysis is the most underrated part of chargeback management. Review chargeback data monthly to identify trends: which products attract the most disputes, which acquisition channels produce the most friendly fraud, and which fraud rules missed the transactions that later became chargebacks. ## Building a Fraud Prevention Strategy for Platforms If you operate a platform or marketplace where multiple merchants process payments, fraud prevention becomes more complex. You need to protect both the platform and your merchants, and fraud can come from either side -- external attackers targeting merchants, or merchants themselves committing fraud against the platform. Key considerations for platforms building fraud prevention: - Onboarding KYC/KYB -- verify merchant identities before allowing them to process payments. This prevents fraudsters from using your platform to cash out stolen cards. - Platform-level fraud rules -- apply baseline fraud rules across all merchants, with the ability for individual merchants to add stricter rules for their specific use case. - Cross-merchant intelligence -- a fraudster blocked by one merchant on your platform should be flagged across all merchants. This is where a unified payment layer adds significant value. - Chargeback monitoring by merchant -- track chargeback rates at the individual merchant level and intervene before a single merchant's fraud rate threatens your platform's processing agreement. - Multi-PSP consistency -- if your platform routes transactions through multiple payment processors, ensure fraud rules apply consistently. A payment orchestration layer normalises this, so merchants get the same protection regardless of which PSP processes their transaction. ## Emerging Threats and Future Trends Ecommerce fraud is evolving rapidly. Merchants and platforms need to stay ahead of these emerging trends: - AI-generated deepfakes -- synthetic voices and video are being used to bypass KYC and identity verification processes. Expect biometric authentication to become standard. - Agentic commerce fraud -- as AI agents begin making purchases autonomously, new fraud vectors emerge around agent impersonation and authorisation manipulation. - Buy Now Pay Later (BNPL) fraud -- fraudsters exploit BNPL services to receive goods immediately using synthetic identities, with no intention of repaying. - Cross-channel fraud -- attackers combine online and offline channels (e.g., social engineering a call centre to reset credentials, then using them online). Unified fraud detection across all payment channels is becoming essential. The most effective defence against emerging threats is a flexible, multi-layered fraud prevention architecture that can adapt quickly as new attack patterns emerge. ## Frequently Asked Questions ### What is the most common type of ecommerce fraud? Card-not-present (CNP) fraud is the most common type, accounting for the majority of ecommerce fraud losses. Within CNP fraud, friendly fraud (chargebacks from legitimate cardholders) and card testing are the most frequent attack patterns merchants encounter. Friendly fraud is particularly challenging because the original transaction is genuine. ### How does 3D Secure help prevent fraud? 3D Secure (3DS2) adds an authentication step where the cardholder's bank verifies their identity during checkout. It uses risk-based authentication, so low-risk transactions pass through without friction while higher-risk ones trigger additional verification such as a one-time passcode or biometric check. Critically, 3DS2 also shifts chargeback liability from the merchant to the issuing bank for successfully authenticated transactions. ### What chargeback rate is considered too high? Visa's monitoring threshold is 0.9% (chargebacks as a percentage of transactions), and Mastercard's is 1.5%. Exceeding these thresholds puts you into a monitoring programme with escalating fines, typically starting at $25,000 per month. Sustained high rates can result in loss of processing privileges. Best practice is to keep your chargeback rate below 0.5% and investigate immediately if it trends upward. ### Do I need PCI compliance if I use a hosted checkout? Yes, but your compliance scope is significantly reduced. If you use a hosted checkout or payment page provided by your payment processor, you typically qualify for the shortest PCI self-assessment questionnaire (SAQ A), which is far shorter than the full SAQ D. You still need to ensure your website is secure and that you handle any cardholder data that passes through your systems appropriately. ### How can platforms manage fraud across multiple merchants? Platforms should implement baseline fraud rules that apply across all merchants, combined with per-merchant chargeback monitoring and cross-merchant fraud intelligence sharing. A payment orchestration layer unifies fraud signals across multiple PSPs so that a fraudster detected on one processor is blocked on all of them. This is particularly important for platforms routing transactions through different providers based on geography, cost, or redundancy. Get in touch to learn how a unified payment layer can simplify fraud management for your platform. ## Related Reading Explore More ### The UK Guide to Collecting Overdue Payments ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Pay Now Button for Invoices: The B2B Guide ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ### How to Send Payment Requests: The Complete Guide to Digital Payment Collection ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [PCI compliance](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [embed payments](/guides/what-is-embedded-payments/) - [platforms](/platforms/) - [payment processor](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [payment orchestration layer](/guides/what-is-embedded-payments/) - [Get in touch](/discovery/) - [GuideThe UK Guide to Collecting Overdue Payments→](/guides/uk-guide-collecting-overdue-payments/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [GuideHow to Send Payment Requests: The Complete Guide to Digital Payment Collection→](/guides/how-to-send-payment-requests/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/accepting-online-payment/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/acquirers-vs-gateways/ --- # How payment processing is changing and how to make and save money | Shuttle > The payment processing landscape is evolving fast. Learn how platforms and merchants can reduce costs and increase revenue with modern payment strategies. # How payment processing is changing and how to make and save money By Nick Dunse, January 1, 2026 The payment processing landscape is evolving fast. Learn how platforms and merchants can reduce costs and increase revenue with modern payment strategies. ## The payments space today The Payment processing of credit and debit cards has been around for a number of decades now, with ever-increasing consumer confidence, one benefit of the pandemic we guess, the enabling of payment processing has changed for the better. With companies like Stripe, Checkout.com and PayPal offering all-in-one solution the choice for the merchants and software vendors is not only greater but potentially better for them. With the increase in online transactions, making payments simple, transparent and effective is becoming a primary concern for all involved. Due to that shift, there is substantial unrealized potential for merchants and payment processors alike. We see that independent payment service processors, or PSPs, are moving away from providing exclusively gateway services, and towards acting as acquirers. Not to mention even newer players like Revolut (new banking provider) offering payment services. What's changed? Historically you had to have a merchant account and a payment gateway to accept cards payments, now you're shielded from need to setup those things separately if you use an all-in-one solution. This wider integration of payment services provides benefits for merchants, who would have access to bundled services and increased payment speeds. For merchants, this is an opportunity to save money on payment fees and quality of payments with a PSP that offer both gateway and acquiring services. The question is then is an all-in-one solution or separate service providers the best way to meet your payment needs? ## The Acquirer / Merchant account provider Looking from the point of purchase, the acquirer plays the critical role of holding the merchant account and receiving payments from a customer's bank. This comes with its own range of fees and terms, however, is typically defined by the specific features and rates desired by merchants. Different PSPs will often base their rates on merchant transaction volume, although merchants can negotiate bespoke agreements with their PSPs. Since the bigger margins are made by the acquirers this is typically where partnership deals are done, something that isn't really possible with incumbent, legacy players. Another deciding factor is the service for seasonal or other cyclical business models. Merchants might experience challenges communicating with larger PSPs, whereas a smaller PSP would be able to provide more specialized solutions. ## The Payment Gateway As the name suggests the payment gateway is the door to accepting a payment and passing that payment instruction to the merchant account and in turn the customer's issuing bank. A gateway will provide a form for the card/payment data to be entered. The cost of using a gateway tends to be low, since it's role, although imperative, is less costly. They might charge a fixed fee or a percentage fee but that fee is on top of the merchant account (payment processing) fees. The deciding factors for Gateways tend to fall along the same line for acquirers, with a core focus on customization and user control. Since there are PSPs that offer an all-in-one solution, they are an alternative to a gateway, acquirer partnership solution; with some all-in-one solutions bundling the gateway for free ## Saving Money with your PSP The trick to saving money with your PSP is to understand your needs and adjust accordingly. A large number of merchants simply don't know what options are out there, so they stay with large players, not knowing the opportunities offered by smaller competitors. Outside of simple education, actively communicating with PSPs will shine a light on options that aren't on their listed pages. A simple conversation could save you money every year. As the payments industry modernizes, we see some PSPs offering both acquiring and gateway services. This provides the advantage of centralized services for merchants, although, this can mean less flexibility than choosing two distinct service providers. When choosing a PSP, a merchant should know what they want to prioritize, be that customization/integration, rates or centralization. Merchants might see the perceived cost of overall services increase with the inclusion of gateway options. In reality, it eliminates the cost for an external gateway service and can in fact save money! Comparing PSPs with Shuttle If you're looking to find a better or cheaper service then we can consider your needs and help you compare the market for free. ## Related Reading Explore More ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### Enterprise PSP Mandates: Why Platforms Need Multiple Gateways ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [help you compare the market for free.](/discovery/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuideEnterprise PSP Mandates: Why Platforms Need Multiple Gateways→](/guides/enterprise-psp-mandates/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/adyen-vs-stripe/ --- # Adyen vs Stripe - which is the right choice for an enterprise merchant? | Shuttle > Adyen vs Stripe compared for enterprise merchants -- fees, global acquiring, developer experience, and which PSP suits your scale. # Adyen vs Stripe - which is the right choice for an enterprise merchant? By Nick Dunse, February 28, 2021 Adyen vs Stripe compared for enterprise merchants -- fees, global acquiring, developer experience, and which PSP suits your scale. Talk to us Make enabling payments for your platform and merchant users easy. I. Introduction As businesses continue to grow and expand their reach globally, they require payment processing solutions that can facilitate seamless transactions across various regions and currencies. Two of the most popular payment processors in the market today are Adyen and Stripe. While both offer similar features, there are some key differences that may make one a better fit for certain businesses than the other. In this article, we will compare Adyen and Stripe based on several factors such as payment processing features, security and compliance, integration and customization, pricing and fees, customer support, pros and cons, and frequently asked questions (FAQs). This will help you determine which payment processor is best suited for your business needs. II. Adyen Overview Adyen is a global payments platform that enables businesses of all sizes to accept payments online, in-app, and at the point-of-sale (POS). The company was founded in 2006 and is headquartered in the Netherlands, with offices around the world. Adyen works with some of the world's largest and most innovative companies across industries such as e-commerce, fintech, marketplace lending, and gaming. Its mission is to enable businesses to grow and operate anywhere in the world seamlessly. In this section, we'll take a closer look at Adyen and its features. III. Stripe Overview Stripe is another popular payment gateway that offers a range of features for businesses of all sizes. Like Adyen, it provides a simple API that allows merchants to integrate payments into their existing systems easily. However, there are some key differences between the two platforms that may make one a better fit for your business than the other. Here are some of the key features offered by Stripe: 1. Simplified Payments: One of the most notable features of Stripe is its simplified payments system. This allows businesses to accept payments from customers through a single integration point, without having to worry about setting up multiple APIs or integrating with different payment processors. 2. Multi-Currency Support: Another important feature of Stripe is its support for multiple currencies. This means that businesses can accept payments in a variety of currencies, making it easier for them to expand into new markets and reach customers around the world. 3. Fraud Detection: Stripe also offers advanced fraud detection tools, which can help businesses reduce the risk of chargebacks and other fraudulent transactions. These tools use machine learning algorithms to analyze transaction data and identify potential threats. 4. Customizable Checkout Pages: Finally, Stripe offers customizable checkout pages that allow businesses to tailor the payment experience to their brand and customer needs. This can help improve conversion rates and increase customer satisfaction. Overall, while both Adyen and Stripe offer similar payment processing capabilities, Stripe may be a better fit for businesses looking for multi-currency support and customizable checkout pages. IV. Payment Processing Features Both Adyen and Stripe offer a range of payment processing features, including support for multiple payment methods such as credit cards, debit cards, e-wallets, and cryptocurrencies. They also provide real-time transaction monitoring, fraud detection, and prevention tools to ensure secure payments. Additionally, both platforms offer APIs and SDKs that enable merchants to integrate their payment systems with their existing infrastructure. However, Stripe offers more extensive integration options, including pre-built integrations with popular e-commerce platforms like Shopify and WooCommerce. Overall, both Adyen and Stripe offer robust payment processing features, but Stripe may be a better option for businesses looking for seamless integration with popular e-commerce platforms. V. Security and Compliance Security and compliance are two of the most important factors to consider when choosing a payment gateway provider. Both Adyen and Stripe offer robust security measures to protect their customers' data. However, there are some differences between the two providers in terms of compliance with industry standards and regulations. Adyen has been certified as a Level 1 PCI DSS compliant service provider, which means it meets the highest level of security requirements set by the Payment Card Industry Data Security Standard. This certification covers all aspects of Adyen's operations, including its infrastructure, processes, and policies. In addition, Adyen has implemented several advanced security features such as tokenization, biometric authentication, and multi-factor authentication to further protect customer data. Stripe also offers high levels of security and compliance. It is certified as a Level 1 PCI DSS compliant service provider and has implemented several security measures such as encryption, tokenization, and fraud detection. Additionally, Stripe complies with various industry standards and regulations such as GDPR, CCPA, and PSD2. In conclusion, both Adyen and Stripe offer secure and compliant payment processing solutions. However, if you require specific certifications or compliance with certain regulations, it may be worth considering one provider over the other. Ultimately, it comes down to selecting a provider that aligns with your business needs and priorities. VI. Integration and Customization Both Adyen and Stripe offer seamless integration with various e-commerce platforms and shopping carts. However, both companies have different approaches when it comes to customization. Adyen offers a flexible API that allows merchants to customize their payment flows according to their specific needs. This means that merchants can create their own branded checkout pages and integrate the payment gateway into their existing website design. Additionally, Adyen provides a range of plugins and SDKs that allow for easy integration with popular e-commerce platforms such as Magento, WooCommerce, and Shopify. Stripe, on the other hand, offers pre-built integrations with several e-commerce platforms and shopping carts. While this makes for a streamlined setup process, it limits the level of customization available. Stripe does offer some customization options through its APIs, but these are limited compared to Adyen's offering. Overall, if customization is a top priority for a merchant, then Adyen may be the better option. If ease of integration and pre-built integrations are more important, then Stripe may be the better choice. It ultimately depends on the specific needs of each business and their preferred approach to payment processing. VII. Pricing and Fees Both Adyen and Stripe offer competitive pricing and fee structures for their payment processing services. However, there are some key differences between the two. Adyen offers a tiered pricing structure based on transaction volume, with lower fees for higher volumes. They also offer a fixed fee of 2.5% + $0.30 per transaction for low-volume transactions. Additionally, they charge a monthly service fee of $25-$500 depending on the plan chosen. Stripe, on the other hand, has a flat rate of 1.9% + $0.30 per transaction for all transactions, regardless of volume. They also offer a free plan for up to $1,000 in transactions per month. In addition, they charge a monthly service fee of 0.15% - 2.9% depending on the plan chosen. Overall, both Adyen and Stripe offer competitive pricing and fee structures, but Adyen may be better suited for high-volume merchants who can take advantage of their tiered pricing structure. On the other hand, Stripe's flat rate may be more attractive to smaller businesses or those who don't need to process a large volume of transactions. It ultimately comes down to the specific needs and budget of each business when deciding which platform to use. VIII. Customer Support Customer support is an essential aspect of any business, especially when it comes to payment processing. Both Adyen and Stripe offer excellent customer support services to their clients. Here are some of the highlights of each company's customer support service: Adyen offers 24/7 customer support through email, phone, and live chat. They have a dedicated team of experts who can assist customers with any issues they may face during the payment process. Additionally, Adyen has a comprehensive knowledge base where customers can find answers to common questions and troubleshooting guides. Stripe also provides round-the-clock customer support via email, phone, and live chat. Their customer support team is highly trained and knowledgeable about the payment processing industry, making them capable of resolving any issue quickly. Furthermore, Stripe has a comprehensive documentation portal where customers can find step-by-step guides on how to use their platform effectively. In conclusion, both Adyen and Stripe provide exceptional customer support services to their clients. However, if you prioritize quick response times and personalized assistance, then Adyen might be the better option for you. On the other hand, if you prefer comprehensive documentation and self-service options, then Stripe would be a better fit. It ultimately depends on your specific needs as a business owner. IX. Pros and Cons Pros of Adyen: 1. Global reach with presence in over 190 countries 2. Fast and reliable payment processing capabilities 3. Seamless integration with various platforms and e-commerce sites 4. Competitive pricing structure with transparent fee structure 5. Advanced security features including tokenization and encryption Cons of Adyen: 1. Limited customer support options compared to Stripe 2. Steep learning curve for merchants who may not have technical expertise 3. Limited customization options as compared to Stripe 4. May not be suitable for small businesses or startups Pros of Stripe: 1. Comprehensive customer support with 24/7 availability 2. Easy integration with various platforms and e-commerce sites 3. Robust customization options with the ability to create custom checkout pages 5. Suitable for both large enterprises and small businesses Cons of Stripe: 1. Limited global reach as compared to Adyen 2. May face regulatory issues due to its association with gambling and adult content 3. Higher fees for certain types of transactions such as recurring payments In conclusion, both Adyen and Stripe offer unique advantages and disadvantages depending on the specific needs of each business. While Adyen offers faster and more secure payment processing capabilities, Stripe provides comprehensive customer support and easy integration. Ultimately, the decision between these two payment processors depends on factors such as the size of the business, the type of products or services offered, and the geographic reach required. It is important to carefully evaluate the pros and cons of each option before making a final decision. X. Conclusion In conclusion, both Adyen and Stripe are excellent payment processing solutions for enterprises. The choice between the two ultimately depends on the specific needs of the business. If security and compliance are top priorities, then Adyen may be the better option. On the other hand, if ease of integration and customization are important, then Stripe may be the better fit. Ultimately, it comes down to weighing the pros and cons of each platform and choosing the one that best aligns with the goals of the business. 1. What is the difference between Adyen and Stripe? Adyen and Stripe are both payment processing platforms, but they have different features and focus on different types of businesses. While Adyen specializes in online payments, Stripe focuses on mobile payments and has a stronger presence in the US. 2. Which one is better for my business? Both Adyen and Stripe offer a range of features and benefits, making them suitable for different types of businesses. If you need to process a high volume of transactions or require advanced fraud detection tools, Adyen may be the better option. On the other hand, if you need a simple and easy-to-use platform with low fees and fast customer support, Stripe may be a better fit. 3. How do their pricing structures compare? Both Adyen and Stripe charge transaction fees based on the type of payment and the region where the transaction occurs. However, Adyen typically charges higher fees compared to Stripe, especially for cross-border transactions. Additionally, Adyen offers a tiered pricing structure based on the volume of transactions, while Stripe has a flat fee structure. 4. Does Adyen offer customer support in multiple languages? Yes, Adyen provides customer support in multiple languages including English, Spanish, French, German, Italian, Dutch, Portuguese, and Japanese. They also have regional offices across Europe, Asia, and North America to provide local support. 5. Is Stripe compliant with GDPR and other data protection regulations? Stripe is fully compliant with GDPR and other data protection regulations, ensuring that all sensitive customer data is protected and secure. They also have a dedicated compliance team that regularly reviews and updates their policies and procedures to meet industry standards. ## Related Reading Explore More ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### Twilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### How to Connect Adyen to Twilio for Voice & IVR Payments ### Stripe Froze My Account: What to Do and How to Prevent It ### Adyen vs Worldpay: Which PSP for Your Platform? ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideTwilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative→](/guides/twilio-stripe-pay-connector/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideHow to Connect Adyen to Twilio for Voice & IVR Payments→](/guides/adyen-twilio-integration/) - [GuideStripe Froze My Account: What to Do and How to Prevent It→](/guides/stripe-account-frozen/) - [GuideAdyen vs Worldpay: Which PSP for Your Platform?→](/guides/adyen-vs-worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/ --- # Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments | Shuttle > How SaaS platforms can prepare for AI-driven commerce. Covers agent-ready payment APIs, PCI compliance for AI agents, and the infrastructure shift from... # Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments By Nick Dunse, August 27, 2025 How SaaS platforms can prepare for AI-driven commerce. Covers agent-ready payment APIs, PCI compliance for AI agents, and the infrastructure shift from... Talk to us Make enabling payments for your platform and merchant users easy. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. The way customers interact with businesses is changing fast. Invoices sent by email, bookings made on websites, and payments processed through traditional checkouts are giving way to a new era: AI-driven conversations. From chatbots that handle support, to voice assistants that manage reservations, to AI agents that negotiate invoices -- customer interactions are increasingly mediated by software. And if your SaaS platform underpins those interactions, there's one critical expectation: Payments must be frictionless, channel-agnostic, and immediate. This is what we call agent-ready commerce. And for SaaS platforms, it's the next frontier. The Shift to Agentic Workflows In the past, customer journeys were predictable. A user went to a website, filled in a form, added items to a basket, and checked out. SaaS platforms designed around that linear model. But now, interactions look different: A customer chats with an AI agent on WhatsApp to confirm a booking. A voice bot on the phone offers an upgrade package and needs to take payment. A digital assistant reminds a customer of an overdue invoice and asks, "Would you like to pay now?" In these workflows, there is no shopping cart. There is no static checkout page. Payments need to be embedded wherever the interaction happens. Why Legacy Payment Models Fail The problem is that most payments infrastructure wasn't built for this. Rigid embedded checkouts assume a web page and a basket. They don't translate to voice, chat, or AI-driven flows. Native PSP integrations tie platforms to a single provider, leaving merchants unable to use their existing processors. Manual processes (like emailing a PDF invoice) create friction and delay. For SaaS product teams, the result is frustration: merchants ask for payment flexibility inside conversational workflows, but delivering it means building custom integrations that clog the roadmap. What Is Agent-Ready Commerce? Agent-ready commerce is the ability to handle payments across any channel, any workflow, any PSP. It means: Channel-agnostic payments: whether the interaction happens in chat, SMS, email, or voice, a secure link can be sent and completed instantly. Merchant choice of PSP: platforms don't force a single provider; merchants use their existing processor. Workflow embedding: payments fit naturally into automation flows -- reservations, support tickets, invoice reminders, or collections. Rules-based logic: merchants can define checkout rules like: "Over $10k? Offer ACH instead of cards." "EUR payments? Show SEPA." "Microtransactions? Limit to cards." For SaaS platforms, agent-ready commerce isn't just a feature. It's a competitive necessity. If you can't enable it, your competitors will. How Payment Links Enable AI-Driven Payments The simplest way to deliver agent-ready commerce today is through payment links. Unlike traditional checkouts, payment links are: Flexible: usable in any channel -- email, chat, voice, SMS. Fast: generated instantly, tailored to the workflow. Branded: hosted pages styled to the merchant's brand. Rule-based: showing only the right payment methods, based on merchant-defined logic. And when powered by a multi-gateway connector like Shuttle, they become truly scalable: 40+ PSPs out of the box -- no native integrations required. Checkout rules enforce smart compliance and cost efficiency. Hosted & managed by Shuttle -- no developer backlog for the SaaS platform. Example Scenario: Reservations & CX Platforms Imagine a SaaS platform powering reservations and customer experience for hospitality. A guest interacts with a chatbot to book a table and add a deposit. The bot says:"Great -- would you like to pay now to confirm?" Instead of redirecting to a web form or sending a manual invoice, the bot issues a payment link in the chat thread. The customer clicks, pays through the merchant's chosen PSP, and confirmation is instant. The same flow works in voice interactions: a phone assistant can text or email a link mid-call. The payment happens seamlessly, with no developer-built checkout required. This is agent-ready commerce in action. Why Product Leaders Should Care For product leaders at SaaS companies, the case for agent-ready commerce is simple: Protect deals: never lose a prospect because you can't support their PSP or embed payments in their workflow. Accelerate roadmaps: payments don't clog engineering; your team keeps building core features. Future-proof platforms: as AI-driven interactions grow, you're already ready. Defensive strategy: competitors can't outflank you on PSP coverage or CX. The stakes are high. According to Bain, churn can cost 5x more than acquisition. Losing merchants because you can't embed payments in their AI workflows is not just a technical gap -- it's a growth threat. A Glimpse Into the Future Agent-ready commerce is only going to accelerate: AI-driven collections: bots negotiating settlements and triggering compliant payment links. Voice-first commerce: customer service agents closing sales mid-call. Subscription management: automated reminders with one-click payment resolution. Cross-border growth: multi-gateway connectors giving merchants global PSP choice without friction. Platforms that prepare now with multi-gateway payment links will be the ones best positioned to capture this future. Why it matters The age of agentic workflows is here. SaaS platforms are no longer judged only by their core features, but by how seamlessly they enable conversational, AI-driven payments. Rigid checkouts and native PSP integrations won't cut it. Product leaders need a way to embed payments that's fast, flexible, and scalable. That's what agent-ready commerce delivers. And with Shuttle's Payment Links for Platforms, SaaS teams can provide it in weeks, not months -- without derailing their roadmap. 👉 Learn more about Payment Links for Platforms and prepare your SaaS for the future of commerce. ## Related Reading Explore More ### Agentic Payments: What Platforms Need to Know ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Embedded Payments for ERP Platforms ### How AI Voice Agents Take PCI-Compliant Payments ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure ## Links - [Book a Call →](/discovery/) - [Payment Links for Platforms](/platforms/links-checkout/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideEmbedded Payments for ERP Platforms→](/guides/payments-for-erp-platforms/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuidePayments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-invoicing-erp-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/ --- # Agentic Commerce: How AI Will Rewrite the Checkout | Shuttle > AI agents are changing how customers buy. Explore how agentic commerce will reshape checkouts, payments, and the role of SaaS platforms in the AI era. # Agentic Commerce: How AI Will Rewrite the Checkout By Nick Dunse, August 29, 2025 AI agents are changing how customers buy. Explore how agentic commerce will reshape checkouts, payments, and the role of SaaS platforms in the AI era. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. Introduction: The End of the Static Checkout For the past two decades, the digital checkout has barely changed. Whether you're booking a flight, paying an invoice, or buying a product, the pattern is the same: add items, go to basket, enter details, click "Pay." But commerce is moving faster than these old flows can keep up with. AI agents are changing how customers interact with merchants. From smart assistants to chatbots and automated workflows, customer interactions now happen in many micro-moments, across multiple channels, outside the traditional "shopping cart." Enter agentic commerce -- a new model where AI dynamically generates personalised checkouts and payment links in real time, removing the need for rigid e-POS systems. What Is Agentic Commerce? Agentic commerce is the idea that AI agents, not humans or static systems, drive the transaction process. The merchant sets the rules, but the agent creates the right payment flow on demand. Think of it like this: instead of pushing all customers through a single checkout, the merchant provides flexible building blocks (payment links, APIs, Smart Rules) and AI handles the orchestration. Merchant-led: The business defines the logic, the brand, and the payments stack. Agent-driven: AI tools (chatbots, workflow builders, voice assistants) trigger dynamic checkouts in real time. Customer-centric: Each payment flow adapts to the channel and customer context. Why the Old Checkout Model Is Breaking Too rigid for modern channels -- A shopping cart doesn't work in WhatsApp, IVR, or voice assistants. High friction -- Asking customers to leave their channel, log in, and re-enter details adds drop-off. Slow to adapt -- Merchants wait months to update e-POS or custom checkout systems. One-size-fits-all -- Customers expect personalised journeys; static checkouts can't deliver. The Agentic Checkout in Practice Let's make this real. Here are five practical scenarios where agentic commerce changes the game: Customer SupportA service agent chats with a customer. Instead of emailing an invoice, they generate a branded payment link instantly in chat. The customer pays within the same conversation. AI Voice BookingA customer books an appointment via a voice assistant. The assistant creates a secure checkout tailored to the service booked. No manual invoicing. Marketing AutomationA loyalty campaign sends personalised links with discounts to different customer segments. Each checkout is dynamic, secure, and branded. Field ServicesEngineers or contractors generate QR-coded links in the field. Customers scan and pay immediately, without hardware terminals. Debt Collection & ARAgents use AI to create compliant payment flows in call centres. Customers get a one-click link via SMS or IVR, reducing friction and boosting recovery. Benefits of Merchant-Led Agentic Commerce Higher Conversions → Customers pay in-channel, without distraction. Cost Efficiency → No need for multiple hardware/e-POS investments. Speed to Market → Launch new flows in days, not months. Scalability → AI handles orchestration; merchants focus on rules. Future-proofing → Built for chat, voice, and whatever channels come next. Why Payment Links Are the Building Block At the heart of agentic commerce is the payment link: flexible, secure, and dynamic. Works across any channel (chat, email, SMS, voice, QR). Can be branded, personalised, and rule-driven. Doesn't depend on shopping carts or tills. With tools like Shuttle Payment Links, merchants get: 40+ PSPs pre-integrated Smart Rules to define payment logic (currency, amount, fraud filters) Zero-code workflows through AI and automation tools PCI compliance included Looking Ahead: A World Without Tills We are entering a world where the till is optional. Customers don't wait in line. They don't need to "check out" in the old sense. They simply interact, and the payment flow materialises. For merchants, this means shifting mindset: from selling at the counter to enabling payments wherever the customer is. Conclusion: Start Today Agentic commerce isn't five years away. It's happening now. Merchants who adopt it early will capture higher conversions, lower costs, and stronger customer loyalty. Shuttle Payment Links give you the tools to lead this shift today. 👉 Explore how Shuttle powers merchant-led agentic commerce → ## Related Reading Explore More ### Agentic Commerce: Payment Infrastructure for AI Agents ### Agent-Native Checkout: Why AI Commerce Needs New Payment APIs ### HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) ### How to Connect Checkout.com to Twilio for Voice & IVR Payments ### Agentic Payments: What Platforms Need to Know ### Shuttle vs Checkout.com for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [👉 Explore how Shuttle powers merchant-led agentic commerce →](/platforms/links-checkout/) - [GuideAgentic Commerce: Payment Infrastructure for AI Agents→](/guides/agentic-commerce/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [GuideHubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)→](/guides/hubspot-commerce-hub-transaction-fees/) - [GuideHow to Connect Checkout.com to Twilio for Voice & IVR Payments→](/guides/checkout-com-twilio-integration/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agentic-commerce-white-paper/ --- # Agentic Commerce White Paper | Shuttle > 85% of customer interactions will be managed without human intervention by 2025. (Source: Gartner) # Agentic Commerce White Paper By Nick Dunse, March 4, 2025 85% of customer interactions will be managed without human intervention by 2025. (Source: Gartner) Talk to us Make enabling payments for your platform and merchant users easy. Introduction The world is rapidly moving toward a future where AI agents can autonomously purchase goods and services on behalf of humans. While early examples exist in voice assistants and IoT devices, these technologies have been limited in scope. Now, AI agents are no longer restricted to purchasing from a single seller -- they can choose what to buy and from where, based on human prompts. However, AI agents must still navigate an online ecosystem designed for human users. As we enter the agentic era of commerce, we are witnessing the gradual demise of the traditional online shopping cart. Why Agentic Commerce? Agentic commerce eliminates the need for human-led checkout experiences. AI agents will: ✅ Discover products autonomously ✅ Negotiate pricing and terms in real time ✅ Execute purchases instantly -- without manual confirmation As a result, traditional checkout processes, shopping carts, and manual payments will become obsolete. Platforms like Stripe's "Pay Now" button and PayPal's checkout flow will be bypassed as AI streamlines transactions seamlessly. 57% of online shoppers abandon their carts due to checkout friction. (Source: Baymard Institute) By 2030, AI-driven transactions are expected to account for up to 30% of all digital commerce. However, based on the current pace of agentic development, we predict this figure could be even higher. B2B transactions are likely to lead the charge, with B2C adoption following closely behind. AI-driven commerce will go beyond simple purchases -- it will handle complex decision-making, such as travel bookings or B2B procurement that requires research, solution-fitting, due diligence, and compliance checks. In the B2B space, AI agents could even replace existing technologies like EDI by automating data-driven purchasing tasks. Both buyers and merchants stand to benefit. AI-driven transactions reduce human distraction, increase efficiency, and ensure optimal purchasing decisions, leading to a significant increase in global e-commerce volume. The Rise of AI-Driven Payments AI is already driving an increase in digital payment volume: - AI-Influenced Holiday Sales: U.S. online sales reached $282 billion, a 4% increase from 2023, attributed to a 42% rise in AI-powered chatbot interactions. (Source: Reuters) - Black Friday 2024: U.S. online sales hit a record $10.8 billion, a 10.2% increase from 2023, largely due to AI-driven shopping assistance. (Source: Barron's) Challenges Facing Agentic Commerce Despite its potential, agentic commerce faces several challenges, categorized by stakeholders: end customers, merchants, commerce software providers, and payment processors. Key Barriers: - Navigating Online Checkout: AI agents currently attempt purchases by mimicking human interactions (e.g., using OpenAI's Operator to scroll and click through online stores). However, this method is inefficient and limits AI's full potential. - Payment Authentication: AI agents must authenticate payments securely, overcoming current security protocols such as PCI DSS compliance and 3DS authentication. The Evolution of Payment Authentication Currently, online payments rely on three primary methods: - Entering debit/credit card details - Logging into a digital wallet (e.g., PayPal) - Using bank details and mobile authentication AI agents will require secure access to payment methods. Storing credit card details within AI memory is currently non-compliant with PCI DSS regulations. Instead, AI will likely integrate with digital wallets, enabling secure transactions. In the near future, AI payment authentication may eliminate card entry entirely, further driving the shift toward digital-first payment solutions. Digital wallet usage is expected to rise by 50% by 2026, driven by AI integration. (Source: Juniper Research) The Impact on the Payment Industry A Shift to Lower-Cost Payment Methods? AI-driven checkouts could prioritize cost-effective payment methods for merchants, such as direct bank transfers over card transactions. This shift may disrupt traditional payment providers, creating new opportunities for alternative payment services. Companies like Apple, which already integrates Open Banking with Apple Pay, are well-positioned to lead the agentic commerce revolution. Traditional card networks and payment gateways must adapt or risk obsolescence. For example, Visa's recent partnership with X highlights how incumbents are evolving to stay relevant. Biometric authentication, powered by AI, will secure 90% of online transactions by 2027. (Source: Worldpay) Enabling Agentic Commerce Through Payment Services For agentic commerce to thrive, payment services must evolve to: - Support AI agents in programmatic site navigation - Enable AI-driven payment authentication - Prevent fraud and optimize checkout experiences Today's merchant payment infrastructure is not yet compatible with fully autonomous AI transactions. Traditional payment service deployment models -- relying on acquirers, gateways, and software vendors -- are too slow and rigid. The industry must develop faster, more adaptable solutions. Future Milestones in Agentic Commerce The transition to agentic commerce will occur in two key phases: - Merchant-Led Agentic Commerce: Merchants will optimize checkout flows to support AI-driven transactions. And initiate checkout journeys by sending payment links via a ecommerce or voice bot. - Buyer-Led Agentic Commerce: Consumers will fully empower AI agents to handle purchases autonomously. How Shuttle is Enabling Agentic Commerce Shuttle is pioneering solutions to bridge the gap between AI and payments: ✅ Integration with AI workflow tools like Zapier to dynamically generate checkout flows ✅ Integration with AI voice software to take payments ✅ Checkout software designed for AI agents to programmatically complete purchases ✅ Secure AI-powered payment instruments that authenticate transactions safely Shuttle Milestones: - AI-generated checkout links for seamless payment flows - AI-powered software integrations with the payment ecosystem - AI-driven checkout automation for programmatic transactions - Secure AI wallet authentication for agentic payments Expanding the Potential of Agentic Commerce Beyond checkout automation, agentic commerce will revolutionize: - Dynamic pricing & negotiations: AI agents will autonomously secure volume discounts and personalized pricing. - Omnichannel shopping (Phygital): AI agents will assist in-store shopping by comparing prices, checking stock, and enhancing purchase decisions. Abandonment rates drop by 35% when AI agents handle checkout processes. (Source: Forrester) Additionally, AI-driven personalization will shift from being emotionally driven to data-driven, ensuring that agents make optimal purchasing decisions aligned with user preferences and buying history. Conclusion The era of agentic commerce is rapidly approaching, driven by AI's ability to autonomously navigate shopping experiences, authenticate payments, and optimize purchasing decisions. To fully realize its potential, merchants and payment providers must adapt their infrastructures. Those who embrace AI-driven commerce today will be the leaders of tomorrow. ## Related Reading Explore More ### Agentic Commerce: Payment Infrastructure for AI Agents ### HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Agentic Payments: What Platforms Need to Know ### Agent-Native Checkout: Why AI Commerce Needs New Payment APIs ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideAgentic Commerce: Payment Infrastructure for AI Agents→](/guides/agentic-commerce/) - [GuideHubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)→](/guides/hubspot-commerce-hub-transaction-fees/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agentic-payments-go-live/ --- # The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. | Shuttle > Razorpay and Anthropic's Claude launched live agentic payments on UPI in India. # The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. By shuttle-team, February 14, 2026 Razorpay and Anthropic's Claude launched live agentic payments on UPI in India. Last week, Razorpay and India's National Payments Corporation launched agentic payments running inside Anthropic's Claude. Zomato. Swiggy. Zepto. Real food delivery platforms. Real transactions. A customer tells the AI agent what they want, and the agent completes the purchase. No redirect to a checkout page. No form to fill in. No human in the loop. This isn't a prototype. It's commerce. And it happened in India first, while most of the Western payments industry is still publishing white papers about what agentic commerce might look like. ## What Razorpay actually built The architecture matters more than the headline. Razorpay created what they call an MCP Server. It sits between the large language model (Claude) and the payment system (UPI). It translates intent into action. The AI agent understands what the customer wants. The MCP Server turns that understanding into a payment instruction the rail can execute. UPI Reserve Pay handles the authorisation layer. The customer sets spending limits and consent rules in advance. The agent operates within those boundaries. It can't overspend. It can't authorise something the customer hasn't pre-approved. That's the pattern: AI decides. Infrastructure executes. Customer controls. Three layers, cleanly separated. The model handles conversation and intent. The translation layer handles payment logic and routing. The rail handles settlement. ## Why this matters beyond India India has UPI. A single, unified payment rail used by hundreds of millions of people. One rail, one protocol, one consent framework. That makes the agent-to-payment connection relatively straightforward. Western markets don't have that luxury. In Europe and the US, the payment infrastructure is fragmented by design. Enterprises run multiple PSPs. Merchants have existing contracts with Worldpay, Adyen, Stripe, their regional acquirer. Compliance requirements vary by vertical, by geography, by transaction type. PCI DSS, PSD2, SCA, open banking. Each one adds a layer of complexity that doesn't exist in the UPI model. When an AI agent operating inside a European insurance platform needs to collect a premium payment, it's not connecting to one rail. It's connecting to whichever PSP that insurer already has a contract with. And the next insurer on the same platform might use a completely different provider. When an AI voice agent handling travel bookings needs to take a deposit over the phone, it needs PCI-compliant voice payment infrastructure. Card data can't touch the agent. The transaction needs to clear across whichever acquirer the travel operator uses. The translation layer that Razorpay built for UPI needs to be rebuilt for a multi-PSP, multi-channel, multi-compliance environment. That's a fundamentally harder infrastructure problem. ## The three problems every Western agentic payment system needs to solve ### 1. PSP optionality The AI agent can't be locked to a single payment provider. Enterprise customers bring their own PSPs. A platform serving hundreds of merchants needs to route payments to dozens of different providers based on who the merchant already works with. This isn't a routing optimisation problem. It's a distribution problem. The agent needs access to whichever PSP the merchant uses, without the platform building and maintaining individual integrations for each one. ### 2. Channel compliance Agentic commerce doesn't happen in a browser. It happens in voice calls, chat windows, SMS conversations, embedded flows inside platform software. Each channel has its own compliance requirements. Voice payments require PCI DSS Level 1 infrastructure and secure card capture that never exposes card data to the conversation. Chat payments need tokenisation. Embedded payments need white-label flows that match the platform's UX. Most payment infrastructure was built for a human sitting at a screen clicking a checkout button. Agentic commerce needs infrastructure that works wherever the agent operates. ### 3. Platform neutrality The payment layer can't create dependency. Platforms don't want to become payment companies. They don't want to manage PSP relationships, handle PCI compliance, or hire payments teams. They want to ship payment capabilities to their merchants and move on. The infrastructure needs to sit underneath the platform invisibly, handling the complexity without surfacing it. ## What this infrastructure actually looks like Razorpay solved this for India with a single-rail translation layer. The Western equivalent needs to be multi-rail by default. A single integration point that connects to 40+ PSPs. Voice, chat, links, and embedded checkout on the same layer. PCI DSS Level 1 certified, so the platform and the AI agent never touch card data. White-label merchant onboarding, so each merchant keeps their existing provider relationship. That's what Shuttle built. When PolyAI's AI voice agents handle high-value transactions for enterprise brands, the payment doesn't break the conversation. Voice Checkout captures the payment in the voice channel, routes it to whichever PSP the merchant uses, and settles it. The agent never handles card data. The platform never manages PSP relationships. When a platform sends a branded payment link via SMS or chat mid-conversation, Payment Links handles the async flow on the same multi-PSP layer. Same infrastructure. Different channel. The pattern is identical to what Razorpay built. AI decides. Infrastructure executes. Customer controls. The difference is the infrastructure underneath handles the fragmentation that Western markets demand. ## The race is on Razorpay and NPCI proved the model works in production. Visa and Mastercard are running agentic payment pilots with DBS Bank, Axis Bank, and RBL Bank. Google's Universal Commerce Protocol has Shopify, Adyen, and Stripe behind it. Coinbase launched Agentic Wallets for AI agents to transact in crypto. The infrastructure layer for agentic commerce is being built right now. In 18 months, the platforms that moved early will own the payment rails their AI agents operate on. The ones that waited will be retrofitting. India went first. The Western market is next. The question isn't whether AI agents will make payments. That's settled. The question is which infrastructure they'll make them on. ## Related Reading - The Payment Layer for AI Agents -- Why AI agents need a payment layer, not a payment provider - Why Platforms Don't Want to Be Payment Companies -- The PayFac trap and why platforms need a payment layer instead - Where PSP Distribution Actually Lives -- How PSP distribution is shifting to embedded platform infrastructure - Agentic Commerce -- The hub for agentic commerce and AI-driven payment infrastructure - Agentic Payments Infrastructure in 2026 -- The full landscape of agentic payment infrastructure - The Voice AI Payment Infrastructure Gap -- Why voice AI companies can't solve payments alone - Embedded Payments for CCaaS -- How contact centre platforms are embedding payments into voice workflows Explore More ### Agentic Payments: What Platforms Need to Know ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Payments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments ### LivePerson Payments: Multi-PSP Capture Across Messaging and Voice ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Why Platforms Don't Want to Be Payment Companies](/blog/why-platforms-dont-want-to-be-payment-companies/) - [Where PSP Distribution Actually Lives](/blog/where-psp-distribution-actually-lives/) - [Agentic Commerce](/guides/agentic-commerce/) - [Agentic Payments Infrastructure in 2026](/blog/agentic-payments-infrastructure-2026/) - [The Voice AI Payment Infrastructure Gap](/blog/voice-ai-payment-infrastructure-gap/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuidePayments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments→](/guides/payments-for-ccaas-implementation-partners/) - [GuideLivePerson Payments: Multi-PSP Capture Across Messaging and Voice→](/guides/liveperson-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agentic-payments-infrastructure-2026/ --- # Agentic Payments in 2026: The Infrastructure Guide for Platforms | Shuttle > Stripe, Google, Visa, and Mastercard are all announcing agentic payment protocols. # Agentic Payments in 2026: The Infrastructure Guide for Platforms By shuttle-team, February 20, 2026 Stripe, Google, Visa, and Mastercard are all announcing agentic payment protocols. Talk to us Make enabling payments for your platform and merchant users easy. ## Everyone's Announcing. Nobody's Explaining How It Works. 2026 is the year agentic payments went mainstream -- at least in press releases. Stripe launched the Agent Toolkit and the A2A Commerce Suite. Google announced the Agent-to-Agent (A2A) protocol. Visa and Mastercard published frameworks for agent-initiated transactions. SAP, Salesforce, and AWS have all incorporated "agentic" into their commerce narratives. The announcements share a common pattern: big vision, light on infrastructure detail. What's missing from nearly all of them is the practical answer: how do you actually let an AI agent process a payment -- securely, compliantly, and across the PSPs your merchants require? That's what this guide covers. ## What "Agentic Payments" Actually Means Strip away the marketing and there are three distinct categories: ### 1. Machine-to-Machine Payments (Agent-to-Agent) An AI agent autonomously purchases a service from another AI agent. No human in the loop. Example: An AI procurement agent evaluates three cloud storage providers' API agents, negotiates pricing, and pays for the selected service -- all programmatically. Current state: Very early. Stripe's x402 protocol and Google's A2A are building the plumbing. Most implementations use stablecoins (USDC) or tokenised pre-authorisations rather than traditional card payments. The infrastructure is being defined in real time. What platforms need: Not much, yet. This is a 2027-2028 reality for most. ### 2. AI Voice Agent Payments An AI voice agent -- handling a phone call instead of a human agent -- processes a card payment mid-conversation. Example: A customer calls an insurance company to renew a policy. An AI voice agent (PolyAI, for instance) handles the call, confirms the renewal, and processes the payment -- all via voice, PCI-compliant, without human intervention. Current state: Live in production. PolyAI + Shuttle process payments via AI voice agents today. This is not a prototype -- it's handling real transactions in regulated industries. What platforms need: A payment layer that supports DTMF (keypad entry) and agent-assisted card capture over voice channels, with full PCI DSS compliance. The AI agent handles the conversation; the payment layer handles the card data. ### 3. AI Chat Agent Payments An AI chat agent -- in a messaging interface, web chat, or conversational UI -- sends a payment link or captures payment details mid-conversation. Example: A customer messages a travel company's chat widget to book a trip. The AI chat agent finds options, confirms the itinerary, and sends a payment link within the chat. The customer pays without leaving the conversation. Current state: Growing rapidly. Most implementations use payment links (sent within the chat) rather than inline card capture. This keeps PCI scope off the chat platform. What platforms need: A payment layer that generates branded, trackable payment links on demand -- triggered by the AI agent's conversation logic. ## The Infrastructure Stack ### What Every Agentic Payment Flow Needs Regardless of agent type (voice, chat, or machine-to-machine), the infrastructure requirements are consistent: 1. PSP-Neutral Payment Processing AI agents serve merchants across industries and geographies. Those merchants use different PSPs. An AI agent that can only process through Stripe excludes every merchant on Worldpay, Adyen, or a regional acquirer. This is the same multi-PSP reality that applies to all platform payments -- but amplified by AI agents' scale. A voice agent handling 10,000 calls a day across 500 merchants needs to route each payment to the correct PSP automatically. 2. PCI-Compliant Card Data Handling AI agents must never see, store, or process card data. Full stop. (For a deep dive on the security architecture, see our guide on AI payment security and PCI compliance.) The agent handles the conversation. The payment layer handles the card data. These must be architecturally separated -- the AI model should have zero access to payment credentials. For voice agents, this means DTMF capture (the customer enters card digits via keypad) or secure agent-assisted flows where the voice channel temporarily routes card audio to a PCI-certified environment. For chat agents, this means payment links -- the agent sends a link, the customer pays on a hosted checkout page, and the agent receives a payment confirmation. Card data never touches the chat platform. 3. Real-Time Payment Status The AI agent needs to know whether the payment succeeded -- immediately, within the conversation. For voice agents: "Thank you, your payment of £450 has been processed. Your confirmation number is..." For chat agents: The payment link callback triggers a confirmation message in the chat. This requires real-time webhooks and event streaming from the payment layer to the agent's orchestration system. 4. Multi-Channel Support AI agents don't operate in a single channel. A platform might have voice agents handling phone calls, chat agents in web widgets, and payment links sent via SMS for follow-up. The payment infrastructure needs to support all channels through a single integration. ## How It Works in Production: The PolyAI Example PolyAI is an AI voice agent platform used by enterprise contact centres. Their agents handle millions of calls across insurance, hospitality, utilities, and financial services. When PolyAI needed to add payment processing to their voice agents, the challenge was: - PCI compliance -- Voice agents handle calls in regulated industries. Card data must be captured in a PCI DSS Level 1 certified environment. - PSP flexibility -- PolyAI's enterprise customers (the contact centres) have existing PSP relationships. Each customer might use a different gateway. - Real-time confirmation -- The voice agent needs to confirm payment within the call, not after. - Legacy PSP support -- Some enterprise customers use PSPs with outdated APIs. The voice agent shouldn't care -- the payment layer handles the translation. The voice agent never touches card data. Shuttle handles PCI-compliant capture, routes to the merchant's PSP, and returns a real-time confirmation. The agent picks up the conversation. > "Shuttle let us treat legacy payment providers as a modern SaaS service. It enabled us to support the gateways our customers required and fully automate high-value transactions across regulated industries." -- Nathan Liu, PolyAI ## What the Big Announcements Actually Mean for Platforms ### Stripe Agent Toolkit / A2A Commerce Suite What it is: SDKs and APIs that let AI agents interact with Stripe -- create payment intents, manage customers, generate invoices, issue refunds. What it isn't: Multi-PSP. The Agent Toolkit works with Stripe-processed transactions only. If your merchants use other PSPs, the toolkit doesn't help. Platform implication: Useful if you're building AI agents that only process through Stripe. Limited if you need PSP flexibility. ### Google Agent-to-Agent (A2A) Protocol What it is: An open protocol for AI agents to discover, negotiate with, and transact with other AI agents. Designed for machine-to-machine commerce. What it isn't: A payment processing system. A2A defines how agents communicate -- it relies on existing payment infrastructure to move money. Platform implication: Relevant for future agent-to-agent commerce. Not a replacement for consumer payment infrastructure today. ### Visa / Mastercard Agent Frameworks What they are: Guidelines for how AI agents should handle card-present and card-not-present transactions within card network rules. What they aren't: Infrastructure. They're rules and standards, not tools you integrate. Platform implication: Important for compliance. Will likely influence PCI Council guidance on AI agent payments. Follow these developments but don't wait for them -- the infrastructure requirements are clear now. ## Building Agentic Payment Infrastructure: Decision Framework ### Use a payment layer when: - Your AI agents serve merchants across multiple PSPs - You need voice payment capabilities (DTMF, agent-assisted capture) - Your agents operate across channels (voice, chat, links) - Enterprise customers mandate their own PSP - PCI compliance is non-negotiable (it always is) ### Use Stripe's Agent Toolkit when: - All merchants process through Stripe - You only need chat-based payments (not voice) - You're building agent-to-agent commerce (not consumer payments) - You're in an early prototype phase and need speed ### Build custom when: - You are a payments company (payments are your core product) - You have dedicated PCI-certified infrastructure and a payments engineering team - You need capabilities no existing provider supports ## What's Coming Next 2026 H2: Expect PCI Council preliminary guidance on AI agent payment processing. Card networks will formalise rules for agent-initiated transactions. More platforms will deploy voice agents with payment capabilities. 2027: Machine-to-machine payment protocols (A2A, x402) will mature. Agent-to-agent commerce will move from demos to pilots. The multi-PSP requirement will intensify as AI agents scale across geographies. The constant: AI agents will need PSP-neutral, PCI-compliant, multi-channel payment infrastructure. The agent layer changes fast. The payment layer underneath needs to be stable, secure, and flexible. ## FAQ Do AI agents need their own PCI certification? No -- and they shouldn't have one. AI agents should never handle card data. The payment layer (which IS PCI certified) handles card capture and processing. The agent handles the conversation and receives payment confirmation. This architectural separation is the key to secure agentic payments. Can I use ChatGPT / Claude / other LLMs for payment processing? LLMs handle the conversation -- they should never handle payment data. The LLM decides when to initiate a payment and what to say about it. The payment layer handles the actual transaction. Think of it as: the LLM is the brain, the payment layer is the secure vault. What about refunds and disputes for agent-processed payments? Same as any other payment. Refunds and disputes are handled through the PSP's standard processes. The payment layer provides unified management across PSPs. The AI agent can initiate refunds if authorised, but the processing happens through the payment layer. Is this compliant with financial regulations? AI-initiated payments are subject to the same regulations as any card-not-present transaction. The key compliance requirements: PCI DSS for card data, SCA (Strong Customer Authentication) where applicable, and clear consumer consent. The payment layer handles PCI. SCA and consent must be designed into the agent's conversation flow. ## Related Reading - AI Payment Security: How AI Agents Handle Card Data -- the detailed PCI architecture for keeping card data out of AI models - How PSPs Get Distribution Into Enterprise Software -- why AI agents amplify the multi-PSP requirement - How to Get Payments Off Your Product Roadmap -- building AI agent payment infrastructure in-house is even harder than checkout - Shuttle vs Stripe Connect -- why Stripe's Agent Toolkit doesn't solve the multi-PSP problem - When Your SaaS Outgrows Stripe Connect -- the migration path for platforms adding AI agent channels - Embedded Payments for CCaaS -- the platform operator's guide to adding payments to contact centre infrastructure - What is DTMF? | What are Voice Payments? | What is PCI DSS? Building AI agents that need to process payments? Shuttle powers agentic payments for enterprise voice and chat agents -- with PCI DSS Level 1 compliance, 40+ PSPs, and real-time payment confirmation. One integration. Every channel. See How It Works | Talk to Our Team Explore More ### Agentic Payments: What Platforms Need to Know ### Agentic Commerce: Payment Infrastructure for AI Agents ### Call Center Payment Processing: PCI Compliant Payments Guide (2026) ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure ### Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure ## Links - [Book a Call →](/discovery/) - [DTMF](/guides/dtmf-payments/) - [multi-PSP reality](/glossary/multi-psp/) - [AI payment security and PCI compliance](/guides/ai-payment-security/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [AI Payment Security: How AI Agents Handle Card Data](/guides/ai-payment-security/) - [How PSPs Get Distribution Into Enterprise Software](/guides/how-psps-get-distribution-into-software/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [DTMF](/glossary/dtmf/) - [Voice Payments](/guides/voice-payments/) - [PCI DSS](/glossary/pci-dss/) - [See How It Works](/platforms/) - [Talk to Our Team](/discovery/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideAgentic Commerce: Payment Infrastructure for AI Agents→](/guides/agentic-commerce/) - [GuideCall Center Payment Processing: PCI Compliant Payments Guide (2026)→](/guides/contact-centre-payments/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuidePayments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-invoicing-erp-platforms/) - [GuidePayments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-insurance-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/agentic-payments-not-solved/ --- # Agentic Payments Isn't Solved Yet | Shuttle > Agentic payments has two sides. Merchant-side agents collecting payments via voice and payment links work today. # Agentic Payments Isn't Solved Yet By Shuttle Team, March 11, 2026 Agentic payments has two sides. Merchant-side agents collecting payments via voice and payment links work today. Talk to us Make enabling payments for your platform and merchant users easy. There's a growing consensus that agentic commerce is about to happen. AI agents that can browse, decide, and buy on your behalf. The demos look good. The funding rounds are large. The virtual card infrastructure is real. But the hard problems haven't been solved. They've been dressed up. What's worth noting is that "agentic payments" actually describes two very different problems. One of them is largely solved. The other isn't close. ## Two sides of agentic payments Merchant-side agents are AI systems that act on behalf of a business to collect payments. A voice agent that takes a card payment over the phone. A chat agent that generates a payment link mid-conversation. A booking bot that sends an SMS payment request after confirming an appointment. These agents don't need to navigate someone else's checkout. They operate within the merchant's own payment infrastructure. The agent determines intent and amount, then hands off to a payment service -- voice checkout, a dynamic payment link, an embedded form. The human pays through a standard, secure channel. The agent never touches card data. This works today. PolyAI voice agents take PCI-compliant payments in production. Insurance platforms run AI agents that collect premiums over the phone. Debt collection agencies automate payment plan setup through voice and messaging. The infrastructure exists -- multi-PSP routing, PCI DSS Level 1 compliance, real-time payment confirmation back to the agent. Consumer-side agents are the inverse. AI systems that act on behalf of a buyer to make purchases. An agent that browses, compares, and buys on your behalf. An agent that books your travel, reorders your supplies, manages your subscriptions. This is what the funding rounds are about. This is what the demos show. And this is what isn't solved. ## The virtual card isn't new The core mechanic behind most consumer-agent payment products is a scoped virtual card. Merchant-locked, amount-capped, single-use. The agent gets a card, the card enforces the rules, and the merchant sees a normal transaction. This is solid infrastructure. It's also fifteen years old. OTAs and corporate travel platforms have been issuing merchant-locked virtual cards through providers like Conferma and WEX since the early 2010s. The booking system selects the supplier, generates a card scoped to that merchant and amount, and the traveller never touches it. No human in the loop. Automated, merchant-locked, single-use. What's changed is the interface. Wrapping this mechanic in an AI SDK with natural language intent is a genuine developer experience improvement. But calling it a new payment primitive is a stretch. The primitive existed. The wrapper is new. ## The consent problem is worse than it looks Here's where it gets interesting. If a consumer agent needs to spend money, someone needs to approve it. In most current implementations, the agent prompts the human for confirmation before the card is issued or the transaction is fired. But think about what that means. The entire premise of agentic commerce is removing humans from the transaction flow. If the agent has to pause, surface a confirmation dialog, and wait for a thumbs up, you haven't built autonomous commerce. You've built a chatbot with a credit card. The deeper issue is the approval prompt itself. The agent controls it. The agent decides what to show you, how to frame it, what context to include or omit. A well-behaved agent surfaces the merchant name, the amount, and the item. A compromised or misaligned agent frames the request however it likes. The scoped card can enforce parameters. It can cap the amount and lock the merchant. What it cannot do is verify that the approval request was honest. That the agent accurately represented what it was buying, or why. This isn't theoretical. It's a social engineering surface that scales with agent adoption. The more trust you delegate, the more the approval prompt becomes the attack vector. Note that merchant-side agents don't have this problem. The merchant controls both the agent and the payment infrastructure. The agent isn't making purchasing decisions -- it's facilitating a transaction the human has already initiated. The human called to pay a bill, asked to book an appointment, or requested a quote. The agent is collecting payment, not recommending a purchase. ## The real bottleneck is the checkout itself Set aside the card issuance and the consent model. Assume you have a perfectly scoped card and legitimate approval. The consumer agent still has to complete a purchase. On the open web, that means filling forms. Clicking buttons. Handling 3DS challenges. Navigating bot detection. Dealing with cookie consent walls, CAPTCHAs, inconsistent DOM structures, and checkout flows that change without notice. Most of the real purchase surface is unstructured and actively hostile to automation. It was designed for humans with browsers, not for software with credentials. This is the actual hard problem. A clean payment credential doesn't help if the agent can't reliably get to the point where it enters one. The long-term fix is merchant-native agent checkout APIs. Direct programmatic interfaces where an agent can authenticate, select items, and complete a transaction without navigating a UI built for humans. Stripe's work in agentic commerce is pointing in this direction. So is the broader API-first commerce movement. But merchant adoption of agent-native APIs is a years-long process. The incentive structure isn't aligned yet. Merchants have no reason to build agent checkout flows until agent commerce represents meaningful volume. And agent commerce can't represent meaningful volume until merchants expose those flows. That's a chicken-and-egg problem that virtual cards can't solve. Again -- merchant-side agents sidestep this entirely. The agent isn't navigating a third-party checkout. It's operating the merchant's own payment flow. The merchant controls the interface. There is no hostile checkout surface to automate against, because the agent is the checkout. ## What actually solving the consumer side looks like Genuine consumer-agent payments infrastructure needs three things that don't exist yet. A consent model that doesn't depend on the agent's own representation. Something like a cryptographic proof of intent, where the parameters of the transaction are attested independently of the agent requesting it. The card issuer, the merchant, and the approval layer need to form a trust triangle that doesn't collapse if one node is compromised. A checkout surface that agents can interact with reliably. Either merchant-native APIs or a standardised agent checkout protocol that works across merchants. Not browser automation. Not screen scraping with GPT-4 vision. A proper interface. And an economic model that gives merchants a reason to participate. Agent commerce needs to offer merchants something better than their current checkout conversion rate. Lower abandonment, higher average order value, reduced support overhead. Without that, the APIs won't get built. The companies that solve these problems will define the category. The ones shipping scoped virtual cards with approval dialogs are building the first 10% and marketing it as the full stack. ## Where this actually is The merchant side of agentic payments -- AI agents collecting payments on behalf of businesses -- is real and in production. Voice agents take card payments. Chat agents send payment links. The infrastructure handles PCI compliance, multi-PSP routing, and real-time confirmation. This is a solved problem with growing adoption. The consumer side -- AI agents spending money on behalf of humans -- is where the venture capital is flowing and the demos are impressive. But the hard problems (consent, checkout surfaces, merchant incentives) remain unsolved. The virtual card provides a payment credential. It doesn't provide trust, a checkout interface, or a reason for merchants to participate. Both sides are "agentic payments." Only one of them works today. The interesting work on the other side hasn't started yet. ## Related Reading Explore More ### Agentic Payments: What Platforms Need to Know ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [voice checkout](/platforms/voice-checkout/) - [dynamic payment link](/platforms/links-checkout/) - [PolyAI voice agents take PCI-compliant payments](/guides/ai-voice-agent-pci-payments/) - [collect premiums over the phone](/guides/ai-voice-payments-insurance/) - [payment plan setup through voice and messaging](/guides/ai-voice-payments-debt-collection/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [social engineering surface that scales with agent adoption](/blog/ai-agent-payment-consent/) - [merchant-native agent checkout APIs](/guides/agent-native-checkout/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/ai-agent-payment-consent/ --- # Consent-Based AI Payments: How Agent Transactions Handle User Consent | Shuttle > How do AI agents capture payment consent? The consent problem in agentic commerce -- regulations, risks, and what platforms need to build for compliant AI... # Consent-Based AI Payments: How Agent Transactions Handle User Consent By Shuttle Team, March 7, 2026 How do AI agents capture payment consent? The consent problem in agentic commerce -- regulations, risks, and what platforms need to build for compliant AI... Talk to us Make enabling payments for your platform and merchant users easy. Every agentic payment system built today relies on the same trust model: the AI agent asks permission before it spends your money. You see a dialog -- "Buy this item for £47.99?" -- and you approve it. This feels safe. It isn't. The consent model in AI agent payments is fundamentally broken, and the industry is shipping it anyway because the alternative requires infrastructure that doesn't exist yet. ## How agent payment approval works today The standard flow in current agentic payment systems looks like this: - The agent identifies a purchase opportunity (a product match, a booking, a subscription renewal) - The agent surfaces a confirmation prompt to the user - The user approves - The agent initiates the transaction using a scoped credential (virtual card, payment token, or pre-authorised mandate) The credential enforcement is solid. Virtual cards can be merchant-locked, amount-capped, and single-use. Payment tokens expire. Pre-authorised mandates have spending limits. The infrastructure for constraining what gets charged is mature. The problem is everything that happens before the credential fires. ## The agent controls the approval prompt When a human assistant recommends a purchase, you can question them. You can ask why this product, why this merchant, why this price. You can detect evasion, check their reasoning, and override their recommendation based on your own judgement. When an AI agent surfaces a purchase confirmation, the agent decides: - What information to show. The product name, the price, the merchant -- all rendered by the agent. A well-built agent shows the full picture. A compromised agent shows whatever maximises approval likelihood. - What information to omit. Competing prices, negative reviews, cancellation terms, recurring charges. The approval prompt is a viewport the agent controls entirely. - How to frame the request. "Great deal found -- 40% off, limited stock" versus "Product available at standard price." The framing is the agent's choice. - When to ask. Timing the prompt for moments of low attention or high urgency is a known persuasion technique. An agent that learns your approval patterns can optimise for consent, not for your interests. This isn't a bug in any specific implementation. It's structural. The entity requesting approval is the same entity controlling the approval interface. There is no independent verification layer. ## Why this is a social engineering problem at scale Social engineering works because the attacker controls the context in which the victim makes a decision. Phishing emails work not because people can't read URLs, but because the email creates urgency and trust that overrides careful inspection. AI agent payment approval creates the same dynamic, at scale: - Prompt injection attacks. If an agent browses the web, parses emails, or reads messages, it's exposed to prompt injection -- malicious instructions embedded in content that alter the agent's behaviour. An injected instruction could change the purchase target, inflate the amount, or suppress the confirmation prompt entirely. - Model misalignment. The agent doesn't need to be compromised externally. If its optimisation target includes purchase completion (common in e-commerce recommendation systems), it will naturally learn to present purchases in the most approval-likely framing. That's not malice -- it's gradient descent. - Approval fatigue. Users who approve 50 micro-purchases a day stop reading the prompts. They approve by reflex. An agent that establishes a pattern of small, legitimate purchases can escalate to larger or less legitimate ones with minimal friction. This is the payment equivalent of notification fatigue -- well-documented in security research. - Multi-agent trust chains. When Agent A delegates to Agent B, which delegates to Agent C, the approval prompt may originate from an agent three hops from the user. Each hop is a potential point of manipulation. The user sees a prompt from "their" agent, but the request was shaped by an agent they've never interacted with. ## What a real consent model needs Solving agent payment consent requires separating three functions that current systems conflate: ### 1. Independent transaction attestation The parameters of the transaction -- merchant, amount, item, terms -- must be attested by a source independent of the requesting agent. This could be: - Merchant-signed transaction proposals. The merchant cryptographically signs a structured offer (item, price, terms). The agent can present it, but cannot alter it. The payment system verifies the signature before processing. - Payment processor verification. The PSP independently verifies the transaction details against the merchant's catalogue and pricing. The approval prompt is generated by the payment processor, not the agent. - Third-party attestation services. A trusted intermediary that verifies purchase details and generates the approval prompt. Similar to how PCI-compliant payment services handle card capture independently of the calling application. The key principle: the entity generating the approval prompt must not be the entity that benefits from approval. ### 2. Contextual spending policies Static spending limits (maximum per transaction, maximum per day) are necessary but insufficient. Real consent requires contextual policies: - Category restrictions. The agent can purchase office supplies but not subscriptions. It can book hotels but not flights. Category enforcement requires merchant classification -- something payment processors already have via MCC codes. - Comparative requirements. The agent must present at least three options before purchasing. Or it must verify the price is within 10% of the market average. This requires the policy engine to have independent market data, not just the agent's representation. - Escalation triggers. New merchants, recurring commitments, or purchases above a threshold require enhanced verification -- biometric confirmation, secondary approval from a human, or a cooling-off period. ### 3. Audit trails that can't be modified by the agent Every transaction should produce an immutable record of: what the agent presented, what the user saw, what was actually charged, and the full chain of agent decisions that led to the purchase recommendation. This record must be stored outside the agent's control. If an agent's purchase recommendations turn out to be systematically biased -- favouring merchants that pay referral fees, or inflating urgency to drive approval rates -- the audit trail makes it detectable. ## The bottom line The payment credential problem in agentic commerce is largely solved. Virtual cards, payment tokens, and scoped mandates are mature infrastructure. The consent problem is not solved. It's not even well-defined yet in most implementations. The companies that treat consent as a UX problem -- a dialog box with an approve button -- are building a social engineering surface that scales with agent adoption. The ones that treat it as an infrastructure problem -- independent attestation, contextual policies, immutable audit trails -- will build systems that regulators, users, and enterprises can trust. The payment industry went through this with card-not-present fraud. The answer wasn't "ask the user to confirm." It was 3D Secure, tokenisation, and network-level fraud detection. Agent commerce needs its own version of that stack. The approval dialog is the "honour system" phase. It won't last. ## Related reading - Agentic Payments Isn't Solved Yet - Agent-Native Checkout: Why AI Commerce Needs New Payment APIs - Agentic Commerce: Payment Infrastructure for AI Agents ## Related Reading Explore More ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI ### How AI Voice Agents Take PCI-Compliant Payments ### The Payment Layer for AI Agents ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [prompt injection](https://owasp.org/www-project-top-10-for-large-language-model-applications/) - [Agentic Payments Isn't Solved Yet](/blog/agentic-payments-not-solved/) - [Agent-Native Checkout: Why AI Commerce Needs New Payment APIs](/guides/agent-native-checkout/) - [Agentic Commerce: Payment Infrastructure for AI Agents](/guides/agentic-commerce/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [GuideAI Payment Security: How AI Agents Handle Card Data Without Breaking PCI→](/guides/ai-payment-security/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [GuideThe Payment Layer for AI Agents→](/guides/the-payment-layer-for-ai-agents/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/are-you-still-building-ecommerce-for-humans/ --- # Are You Still Building eCommerce for Humans? | Shuttle > AI agents are starting to buy on behalf of consumers. Is your checkout ready for non-human buyers and agentic commerce? # Are You Still Building eCommerce for Humans? By Nick Dunse, July 22, 2025 AI agents are starting to buy on behalf of consumers. Is your checkout ready for non-human buyers and agentic commerce? Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. For the last 20 years, we've been told to optimise everything. Your product detail page. Your checkout flow. Your UX.But what if none of that matters anymore? What if the person buying from you... isn't a person at all? That's the shift now quietly underway in commerce. AI agents are beginning to take over the entire buying journey -- especially for repeat purchases and commoditised goods. They don't get distracted by carousels or "10% off" popups. They don't browse. They don't hesitate. They evaluate data, make a decision in milliseconds, and execute. This is what people are starting to call agentic commerce. And it changes everything. The new buyer doesn't browse Think about how most eCommerce journeys still work today: a human searches for something, finds your site, clicks around, adds to cart, goes through checkout. But now? That same human might just ask ChatGPT. Or Siri. Or whatever embedded assistant sits inside their browser or operating system in a year's time. The request might be simple: "Find me the best waterproof running shoes under £120 that can be delivered by Friday." That AI agent might handle everything: research, selection, even payment. As Stefan Hamann, CEO of Shopware, put it during our conversation: "The moment of differentiation shrinks from minutes to milliseconds." That's the real shift. And it's already happening. Your storefront might not even load If the agent's doing the buying, your beautifully designed homepage may never be seen. They won't be impressed by your lifestyle imagery. They won't scroll. They'll be parsing: Availability Delivery reliability Trust signals Metadata quality It's not that your storefront doesn't matter -- it's just that it matters to fewer people. For many transactions, the interface becomes a machine-to-machine exchange. And for merchants, that means the signals you're sending to those machines are now your storefront. What still matters -- and what doesn't A lot of traditional eCommerce optimisation will still matter, but not in the same way. Your brand experience? Still vital -- but it needs to be structured in a way agents can understand. That might mean new data formats, standardised trust scores, or loyalty metrics embedded into your feed. Your UX? Important -- but less so for the half of commerce that's increasingly automated. Your PDP copy? Still useful -- but only if the agent can extract key decision-making variables from it at speed. Platforms like Shopware are already working on these problems. They're building agent-aware product infrastructure -- front and back. That includes everything from self-healing product data to storefronts that adapt to user preferences in real time. Not future talk -- this is already in prototype. B2B isn't immune -- if anything, it's next We often think of B2B as lagging behind B2C. But in this case, it might be the first to go fully agentic. Why? Because so much of B2B purchasing is already rules-based: Find supplier Check inventory Validate PO Place order The problem is: it's still painfully manual. Agents are perfectly suited to speed this up. But they'll need structure, and they'll need payments they can actually trigger. And that's where the next round of innovation will come from -- tying automation to payment authorisation in a secure, compliant way. The moment that happens? Entire workflows go from days to seconds. Where this leaves you If you're a merchant, platform, or integrator, now's the time to look in the mirror. Ask yourself: Can an agent understand why someone should choose me? Is my data clean, structured, and accessible in the right way? Am I investing in true differentiation -- or just dressing up a slow, brittle stack? If the answer to most of those is no, you're not alone. But the window is narrowing. As Stefan said in our chat, this isn't just about surviving the shift. It's about doing the kind of creative, valuable work that AI can't do for you -- yet. The merchants who lean into this will still win. Because yes, agents may be doing more of the work. But at the end of every transaction, there's still a human. And they're the one wearing the trainers. ## Related Reading Explore More ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ### How to Switch Twilio Pay Connectors Without Breaking Your Call Flow ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [GuideHow to Switch Twilio Pay Connectors Without Breaking Your Call Flow→](/guides/switch-twilio-pay-connector/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/author/nickdunse/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/best-orders-were-always-conversations/ --- # The best orders were always conversations. Now AI can have them, and take the payment. | Shuttle > Platforms annexed every new sales channel: marketplaces, the counter, social, now AI agents. # The best orders were always conversations. Now AI can have them, and take the payment. By Shuttle Team, August 20, 2026 Platforms annexed every new sales channel: marketplaces, the counter, social, now AI agents. Talk to us Make enabling payments for your platform and merchant users easy. We run payment execution inside software platforms. ERPs, booking systems, voice platforms. From that seat, one shift is hard to miss. A merchant's best orders were always conversations. The quote, the reorder, the considered purchase. The web era made those conversations expensive, so merchants pushed buyers to a screen instead. AI has made them cheap again, and it can now take the payment inside them. That is the one sales surface commerce platforms cannot reach. ## The platform's product is centrality Merchants do not stay on a platform for the checkout button. They stay because it holds the record of their revenue. Orders, customers, payments, inventory. Everything built on top of it sits on that one source of truth. Centrality is what carries the subscription and the payments margin. So platforms have never treated a new sales channel as optional. Every time selling turned up somewhere the platform wasn't, the answer was the same. Extend the rails, make the channel execute through the platform, and the centre holds. - Marketplaces. Merchants already sold on eBay and Amazon. Channel integrations pulled those orders into the platform's record. - The counter. In-person selling long predates the platforms. POS annexed it, so the web-native merchant's oldest channel finally landed in the same book (Shopify POS, 2013). - Social. Selling conversations were already happening in DMs and feeds. Shops on Instagram and TikTok kept catalogue and checkout platform-native. - AI agents. Buying is moving into assistants. Agentic commerce protocols, specified now, so the agent transacts through the platform. - The call. The oldest sales channel of all, newly automated by AI. No platform has annexed it. Look at what the pattern actually is. None of those channels were new. Merchants were already selling in every one of them. What the platform did each time was annex selling that was already happening, usually years after it started. The phone is the extreme case. It is the oldest channel on the list. It never stopped transacting. It is the only one still unannexed. ## The channel is re-sorting now, and it is measurable Three numbers from the past twelve months, from two independent sources, describe the same movement. - 49% of answered calls referred by ChatGPT become leads. The highest lead rate of any channel measured, ahead of Google Business Profiles (43%) and a 38% cross-channel average. Invoca, 70M conversations, 2026. - 50% of AI-using shoppers have bought something after researching it with AI. Only 22% have ever completed the purchase inside the AI tool itself. Semrush, 1,030 US AI-using shoppers, Dec 2025. - 44% of callers to businesses never reach a person. The highest-intent inbound in commerce, routinely dropped on the floor. Invoca, 2026. Put those together. AI assistants are now the top of the funnel. They hand the buyer off before the transaction. The considered, high-value buyer picks up the phone next. An answered call is not automatically the best-converting call in the book. It is the highest-intent one, and nearly half of them never get answered. AI voice agents exist to close that gap, and the money has followed. ElevenLabs raised $500m at an $11bn valuation in February 2026, and capital has backed the category all year. Deployment has outrun the funding headlines. SoundHound's restaurant phone-ordering system alone had processed over 100 million customer interactions across 10,000+ locations by its October 2024 US milestone. Taco Bell runs AI voice ordering in over 890 drive-thrus across 38 states. This is not a pilot economy any more. The economics pushing merchants toward it are not subtle either. Two decades of IVR menus and "did you know you can do this online?" happened because conversations were expensive. Verizon prices that difference in public. A bill payment through its automated phone system is free. The same payment with an agent on the line costs $10. Frontier Airlines charges $35 per ticket to book through a care agent, against nothing online. AI takes the human out of the conversation without taking out the conversation. So that cost wall comes down, and it was the whole reason merchants pushed buyers to the web in the first place. Channels re-sort when a constraint disappears. The conversations never stopped. Merchants have been having them, and losing them, the entire time. What changes now is that they can be had at no marginal cost, by AI, with the payment taken inside them. Web checkout keeps the self-serve order. The considered one goes back to being a conversation, this time with a transaction in it. ## In-call payment already runs at national scale. Just not in retail. Taking payment inside a phone call can sound exotic to a retail platform. It is Tuesday in every other industry that kept its phones on. The numbers are public. - ComEd (Exelon utility). Agent-assisted card payments in-call, up to 50,000 payments a month. - BGE (Exelon utility). Phone as a payment channel, 10% of total payment volume. - TalkTalk (UK telco). Card payments in-call across 1,200+ agents, 18,000+ payers every week. Case study figures, 2010s. - GOV.UK Pay. Public-sector payments including a telephone channel: 144M transactions, £9.7bn, all channels. - UK contact centres. Take card payments by phone: 68% overall, 91% in finance, 86% in insurance. GOV.UK Pay's dashboard publishes no channel split; the total is all-channel and overwhelmingly online. It is here because the telephone channel exists inside a payment platform of that size, not as a phone-volume figure. Travel and hospitality settled the wider channel question years ago. A room, a flight, a tour, a hire car. Bookable online, over chat, or on a call, against the same inventory, with payment taken in the call and one reservation recorded whichever door the customer came through. The travel operator's booking engine is the centre of its universe across every channel a customer chooses. The retail platform is the centre of exactly one. Consumer expectations do not stay in their lane, either. The customer who booked a hotel by voice yesterday does not reset their assumptions when they call a furniture retailer, a parts distributor or a garden centre today. Conversational buying with payment in the conversation is already normal for consumers. It is only novel for the platforms that cannot do it. ## What a handoff costs: the one experiment that has been run The standard workaround is to take the order in conversation, then push the buyer to a screen to pay. It feels harmless. It has now been tested at scale, once, in public, and the result is worth taking seriously. > Walmart's Daniel Danker put purchases completed inside ChatGPT at roughly one third the conversion rate of sending the same shopper to walmart.com. Walmart had been offering around 200,000 items inside ChatGPT since November 2025. OpenAI subsequently phased Instant Checkout out in favour of merchant-owned checkout. Of the "over a million" Shopify merchants promised at launch, reports put the number that ever went live between a dozen and thirty. Industry-wide, the in-chat buy button was clicked under 1% of the time, against 3-4% conversion in conventional ecommerce. Conversion figure and item count: Daniel Danker, EVP product and design at Walmart, speaking to WIRED, March 2026. OpenAI's retreat: OpenAI, confirmed in the same reporting. Click and conversion rates, and the upper merchant count: Forrester. Lower merchant count: The Information via eMarketer. The lesson is not that agentic checkout failed. It is that a break in the channel at the moment of payment destroys conversion. The industry's answer was discovery in the agent, execution on the merchant's own rails. That is a principle worth naming: execution belongs to whoever owns the customer relationship. Chat could retreat to the website. A phone call has no website to retreat to. Yet the SMS-checkout-link handoff that most retail voice vendors have converged on rebuilds the exact break Walmart measured, and builds it in permanently, by design. ## The leak: how the centre stops being the centre Here is the flow when one of those high-value conversations converts today, for a merchant whose voice agent, or whose staff, takes the order on a call. We see the shape of this from where we sit, running payment execution in production inside ERP customers. - Customer researches with an AI assistant, then calls. The highest-intent inbound the merchant gets. - The agent, human or AI, takes the order in conversation. - Payment is keyed into a terminal or virtual terminal, outside the platform. - The platform order, if one exists, is marked paid by hand; the gateway reads Manual. - Customer, payment and order now live in three systems that don't agree. The sale happened. The platform didn't see it happen. Every ERP can raise an invoice. Almost none can execute the payment. The invoice goes out, the money arrives some other way, and someone updates the system by hand so the record matches the money. Many merchants running an ERP also run a storefront on Shopify or BigCommerce. So a single phone order can exist in three systems at once. The terminal has the money, the ERP has the order, the storefront has neither. This is not churn, which is why no dashboard catches it. The merchant is still subscribed, still syncing inventory, still renewing. What has moved is the conversion event, and with it the payment margin, the customer record, and the data every downstream product depends on. Fraud tooling scores a book missing its largest orders. Analytics reports a channel mix that no longer matches the business. When we tell platform executives to check this in their own data, we tell them to look at value rather than count. Where we have looked, the orders paid by hand are few, and they are large. > The platform doesn't lose the merchant. It loses the merchant's best orders, one conversation at a time. The leak is structural rather than sloppy. Shopify's own documentation is explicit that a payment captured outside the platform leaves the order unpaid until it is marked paid. Recorded, not captured, with settlement running in a second stream the platform cannot see. Among the established phone-payment security vendors we reviewed in August 2026, we found none publishing a Shopify integration. That review checked each vendor's own published integration, app-store and partner listings. The leak has no plumbing even for the merchant who wants to fix it. ## The rails being specified right now cannot reach this channel The platforms' response to AI commerce is well underway. It is worth reading what the new protocols actually specify, at the schema level rather than the press-release level, because not one of them has a place to put a buyer who has no screen. OpenAI and Stripe's Agentic Commerce Protocol is specified as HTTP between an agent and a merchant endpoint. Read in August 2026, neither the checkout spec nor the delegated-payment spec models the channel the buyer is in. No device type, no screen, and no vocabulary for voice or any other non-visual surface. The only signal of the buyer's surface is an HTTP user-agent header, which presumes a browser. The flow throughout assumes a buyer who can be shown something and act on it. A phone call is not a case the spec considers. Google's AP2 organises around whether a human is present, not the channel they are present in. Every surface it names is visual. The user "directly sees" the checkout, and mandates pass to a trusted surface "for display". It has no vocabulary for a person who is present with no screen. The Universal Commerce Protocol, co-authored with Shopify, reads as a browser specification throughout. Voice appears in passing, with nothing specified for it. One layer down, the pattern holds. Twilio's in-call payment primitive captures cards by keypad tones, not speech. We know it well: Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Vapi's published PCI guidance for voice agents is to switch recording, logging and transcription off during payment and hand the caller to a different assistant. The primitives exist and they work. What no platform has yet adopted is a shared layer that carries a keypad capture through to each merchant's own gateway and lands the result back in the platform as a paid order. There is a regulatory clock running under all of this. Visa's PSD2 guidance classifies internet-based voice interactions as not MOTO, which strips AI-mediated calls of the exemption that legacy phone payments have quietly relied on. At the same time, European regulators report non-authenticated card transactions within the EEA running at twice the fraud rate of authenticated ones. The channel is growing, its old regulatory cover is shrinking, and the new rails don't reach it. That combination does not stay stable for long. ## Why "build it" is harder than it scopes We say this as the people who built one. The in-house version commits a platform to far more than a feature. - Spoken card data puts your infrastructure in PCI scope. The PCI Security Standards Council is unambiguous. Accepting spoken account data over the telephone puts the personnel, the technology, and the connected infrastructure into scope. - An AI agent removes the exemption that made phone payments workable. The concession for call audio containing card data required that recordings could not be data-mined. A transcribing, analysing model on the call fails that test by definition. The Council's guidance flagged voice analytics as a scope risk years before these products existed. - Spoken digit capture is unreliable at card length. Small per-digit recognition errors compound across a 16-digit number. That is why every serious deployment captures cards by keypad tones rather than speech, and why "just let the AI hear the card" is not a product plan. - The compliance delta is measured in quarters, not sprints. Take card data into your own systems and you are completing SAQ D: the full questionnaire. Keep it with a provider that carries the card data and you are completing SAQ A, the short questionnaire. In the UK contact-centre industry, which has lived with this for two decades, 8% of operations moved payments to a third party specifically because the compliance cost was too high. - Every merchant brings their own acquirer. A platform cannot route millions of merchants through one processor. Multi-tenant provider configuration has to be designed in from the first line. In our experience it is the part that cannot be retrofitted, and the part usually scoped last. We built payment execution into an ERP early in our history. It was bespoke: one platform, wired deliberately, and it did the job it was built for. What has changed since is not that integration, it is the channel around it. Taking the order on the phone and keying the card into a terminal is not the way any longer, and the conversation with the customer is still evolving as the AI tech moves. What platforms need now is the general version. Multi-tenant, each merchant on their own payment provider, each channel settling into the same record. That is a different product. It is the one we went on to build, and the reason we built it as a shared PCI DSS Level 1 layer is the list above. This is a compliance tower each platform should not have to raise alone. ## The window: others are moving into this gap now This is a 2026 decision rather than a someday decision because the gap is being taken from both ends while the platforms watch the chat lane. - Sierra shipped Level 1 PCI payment capability for its agents in April 2026, across chat and voice, with SiriusXM named and "thousands of payments daily" claimed. Where Sierra takes the payment, Sierra's customer owns the flow, not the commerce platform underneath. - The contact-centre payment incumbents are repositioning around AI agents. The vendors who spent two decades securing human-agent phone payments now market to exactly this gap. They are not doing it in a small market: on ContactBabel's numbers, 68% of UK contact centres take card payments by phone, and the AI wave is landing on top of that. Every quarter this stays unsolved, more merchants wire a voice vendor to a virtual terminal on their own. Every one of those improvised stacks is revenue settling outside the platform, habits forming around the workaround, and a harder integration to win back later. Channel annexations reward the early mover. POS was worth most to the platform that shipped it first. ## What staying the centre requires The test for any answer, built or bought or partnered, ours or anyone's, is the same four properties. They are what "the centre holds" means, mechanically. - The payment completes in the conversation. No handoff to a screen at the moment of highest intent. Walmart measured what the handoff costs. - Card data never touches the platform, the agent, or the model providers. Keypad capture keeps the card outside the cardholder data environment. That limits your scope and your merchants'. It does not remove a merchant's own duty to self-assess, and nothing does. - Each merchant keeps their own acquirer. Configured per tenant, on their own terms. - The order lands in the platform as a paid order. Customer attached. The money and the order match without anyone touching them. The fourth is the one that decides centrality. A platform that can take the payment but not record the order has built a gateway. A platform where the conversation's order settles natively, like a marketplace order, like a POS order, has annexed the channel, exactly as it did the last four times. The question for your roadmap is not "should we add voice". Travel answered that years ago: every channel, one booking, one record. The question is this. Your merchants' highest-value orders already are conversations. Now that AI can hold them and take payment in them, does your platform see them, or not? If you want to test the premise before talking to anyone, us included: count the orders in your platform marked paid by hand, and total their value rather than their number. Then compare that figure with what your roadmap currently spends to defend it. Where we have checked, the answer to the first question is usually larger than expected, and the answer to the second is zero. ## Where to go next The products behind this are Voice Checkout, for payments taken on a call, and the Embedded Payment Layer, for platforms that want it inside their own product. The wider argument about the conversation as a sales channel is set out in The shopping carts won the page. If you want to work through what this looks like on your platform, talk to us. ## About Shuttle Shuttle is the multi-tenant payment execution layer for software-mediated commerce. A PCI DSS Level 1 layer that sits above the payment gateways, so platforms, ERPs and voice systems can execute payments across links, calls and embedded checkout, with each merchant on their own payment provider and the order settling back into the platform's system of record. We run in production inside our ERP customers. Security and compliance detail ## Sources Invoca, Lead Conversion Benchmarks 2026 (70M conversations). Semrush survey of 1,030 US AI-using shoppers, Dec 2025. ElevenLabs Series D, Feb 2026. SoundHound (US milestone, Oct 2024) and Taco Bell/Omilia deployment figures: company releases and Restaurant Dive, 2024-26. Verizon and Frontier Airlines fee schedules: published support and optional-services pages. Paymentus/Exelon case study (ComEd, BGE); published TalkTalk phone-payments case study; GOV.UK Pay performance dashboard, Aug 2026. ContactBabel, UK Contact Centre Decision-Makers' Guide 2024 (payment methods, SAQ D vs SAQ A control counts, third-party migration). Walmart conversion: Daniel Danker, EVP product and design at Walmart, speaking to WIRED, Why Walmart and OpenAI Are Shaking Up Their Agentic Shopping Deal, Mar 2026, corroborated by Search Engine Land, MarTech and Axios, Mar 2026; Forrester, Mar 2026; The Information via eMarketer. Agentic Commerce Protocol, developers.openai.com/commerce/specs/checkout and /specs/payment, read 20 Aug 2026; Google AP2 and Universal Commerce Protocol, read from the published specifications, Aug 2026. Shopify documentation on manual payment capture and orderMarkAsPaid. Twilio Pay verb documentation; Vapi PCI guidance. PCI SSC, Protecting Telephone-Based Payment Card Data and FAQ 1210. Visa, PSD2 SCA Regulatory Guide (voice commerce and MOTO classification); EBA/ECB, Report on Payment Fraud (EEA), Dec 2025. Sierra payments announcement, Apr 2026 (Visa Global Service Provider Registry). Invoca lead-rate figures are of answered calls. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### How to Take Payments with Verint: PCI-Compliant Payment Integration for Verint-Powered Contact Centres ### Observe.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres ### Cresta and Payments: PCI-Compliant Card Capture for Cresta-Powered Contact Centres ### Merchant Account Providers Compared: 12 Best Options for 2026 ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Voice Checkout](/platforms/voice-checkout/) - [Embedded Payment Layer](/platforms/) - [The shopping carts won the page](/payment-layer/) - [talk to us](/discovery/) - [Security and compliance detail](https://docs.shuttleglobal.com/docs/org-security) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideHow to Take Payments with Verint: PCI-Compliant Payment Integration for Verint-Powered Contact Centres→](/guides/verint-payments/) - [GuideObserve.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres→](/guides/observe-ai-payments/) - [GuideCresta and Payments: PCI-Compliant Card Capture for Cresta-Powered Contact Centres→](/guides/cresta-payments/) - [GuideMerchant Account Providers Compared: 12 Best Options for 2026→](/guides/merchant-account-providers/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/best-payment-gateways-for-uk-businesses-comparison/ --- # Best Payment Gateways UK 2026: Fees, Features & Integration Compared | Shuttle > Compare the best UK payment gateways -- Stripe, Adyen, Worldpay, Checkout.com, Square, and more. # Best Payment Gateways UK 2026: Fees, Features & Integration Compared By Nick Dunse, February 13, 2023 Compare the best UK payment gateways -- Stripe, Adyen, Worldpay, Checkout.com, Square, and more. Choosing a payment gateway is one of the most consequential decisions a UK business makes. It affects transaction costs, customer experience, integration complexity, and how easily you can expand to new channels and markets. This guide compares the best payment gateways available in the UK, covering fees, features, integration options, and which gateway suits which business type. ## What Is a Payment Gateway? A payment gateway is the technology that authorises card transactions. When a customer enters their card details -- on a website, in an app, over the phone, or at a terminal -- the gateway communicates with the card network and the customer's bank to approve or decline the payment. Most modern payment gateways also function as acquirers and payment processors, meaning they handle the full transaction lifecycle: authorisation, settlement, and reporting. ## Best UK Payment Gateways Compared UK Card Fees Key Strength Integration Online businesses, SaaS 1.4% + 20p Developer experience, documentation API, SDKs, plugins Enterprise, multi-region IC + 0.10-0.25€ Global acquiring, unified commerce API, drop-in components High-volume retail From 0.75% + 10p UK market penetration, terminal range API, hosted page, POS Checkout.com High-growth online IC + ~0.20% Approval rates, performance API, hosted page, SDKs Small business, retail 1.75% (in-person) POS + online in one POS hardware, API, plugins GoCardless Direct Debit / recurring 1-2% + 20p Bank-to-bank payments API, dashboard, plugins Consumer payments 2.9% + 30p Customer trust, wallet ubiquity Buttons, API, plugins European e-commerce 1.2% + 25p European payment methods, simplicity API, plugins ## Stripe Stripe is the default choice for developer-led businesses. Its API documentation is the industry standard, its SDKs cover every major language and framework, and its product surface extends well beyond basic payments into billing, subscriptions, fraud detection (Radar), and financial infrastructure. Fees: 1.4% + 20p for UK cards. 2.5% + 20p for international cards. No monthly fee. Best for: Online businesses, SaaS platforms, startups, developer-first teams. Limitation: Flat-rate pricing is expensive at high volumes. For businesses processing over £100K/month, interchange-plus from Adyen or Checkout.com is typically cheaper. Stripe Connect for platforms locks you into Stripe's ecosystem. ## Adyen Adyen is the gateway of choice for enterprise and multi-region businesses. It operates as a full-stack acquirer in 30+ countries, meaning it processes transactions locally -- reducing cross-border interchange costs and improving approval rates. Fees: Interchange + €0.10-0.25 per transaction. No monthly fee but a €120/month minimum processing requirement. Best for: Enterprise businesses, multi-country operations, unified commerce (online + in-store). Limitation: Not designed for small businesses (minimum processing threshold). Less plug-and-play than Stripe -- better suited for businesses with engineering resources. ## Worldpay Worldpay (now part of FIS) is the UK's largest merchant acquirer by volume. It processes payments for businesses of all sizes, from sole traders to enterprise retailers. Its strength is breadth: card terminals, online payments, phone payments, and multi-currency processing. Fees: From 0.75% + 10p per transaction, plus monthly fees from £19.95. Pricing is negotiable for higher volumes. Best for: UK businesses with in-store payments, high-volume retail, businesses wanting a traditional merchant acquirer. Limitation: Legacy infrastructure can mean slower onboarding and less modern developer tools compared to Stripe or Adyen. For a detailed comparison, see Adyen vs Worldpay. Checkout.com is a high-growth payment processor focused on performance. Its claim: higher approval rates than competitors through intelligent routing and direct acquiring relationships. It's gained significant traction with fast-growing online businesses and marketplaces. Fees: Interchange + ~0.20% per transaction. No monthly fee. Best for: High-growth e-commerce, marketplaces, businesses where approval rates directly impact revenue. Limitation: Less brand recognition with SMBs. No in-store POS offering. For more detail, see Adyen vs Checkout.com. ## Square Square combines a payment gateway with POS hardware in one package. For small UK businesses that need both online and in-store payments, Square is the simplest all-in-one option. Fees: 1.75% for in-person. 2.5% for online/invoices. No monthly fee for basic plan. Best for: Small businesses, restaurants, retail, market traders. Limitation: Flat pricing is expensive at scale. Limited customisation compared to API-first providers. Not suitable for enterprise or platform use cases. ## How to Choose the Right Gateway - Small business, low volume: Square or SumUp for simplicity. PayPal if your customers expect it. - Online-only, growing: Stripe for developer experience. Checkout.com if approval rates matter. - High volume: Adyen or Worldpay with interchange-plus pricing. - Multi-country: Adyen for local acquiring. Stripe for broad country coverage. - In-store + online: Square for small. Worldpay or Adyen for enterprise. - Direct Debit / recurring: GoCardless for bank-to-bank. Stripe Billing for card-based subscriptions. ## Payment Gateways for Platforms If you're building a software platform that needs to embed payments for your users, the single-gateway approach breaks down fast. Your first customer uses Stripe. Your second needs Adyen. Your third has a Worldpay contract they can't change. Instead of building separate integrations to each gateway, platforms use a payment layer -- a single integration that connects to 40+ gateways and handles PCI compliance, merchant onboarding, and multi-channel payment capture. See What Is Embedded Payments? for a full guide to how platforms approach payment gateway selection. ## FAQ ### What's the cheapest payment gateway in the UK? For low volume: SumUp (1.69%, no monthly fee). For high volume: Adyen or Worldpay with interchange-plus pricing (total costs from ~0.3% for UK debit cards). ### Do I need a merchant account to use a payment gateway? Not with PSPs like Stripe, Square, or PayPal -- they provide an aggregated merchant account. With traditional acquirers like Worldpay, the merchant account and gateway are bundled together. ### Can I use multiple payment gateways? Yes. Many businesses use multiple gateways for redundancy, cost optimisation, or to support different channels (e.g., Stripe online + Worldpay in-store). ### What about security (PCI compliance)? All major gateways handle PCI compliance for the card data they process. As a merchant, using a hosted payment page or tokenisation reduces your PCI scope to the minimum (SAQ-A). Need help comparing payment options? Browse all supported payment providers or see payment services for merchants. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [payment gateway](/blog/what-is-a-payment-gateway/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [Adyen vs Worldpay](/guides/adyen-vs-worldpay/) - [Checkout.com](/payment-providers/checkout-com/) - [Adyen vs Checkout.com](/guides/adyen-vs-checkout-com/) - [payment layer](/guides/payment-layer-explained/) - [40+ gateways](/payment-providers/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [PCI scope](/glossary/pci-scope/) - [Browse all supported payment providers](/payment-providers/) - [see payment services for merchants](/merchants/payment-services/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/best-uk-payment-providers-the-definitive-guide/ --- # Best UK Payment Providers - The definitive guide | Shuttle > The definitive guide to UK payment providers -- compare Stripe, Adyen, Worldpay, Square, and more on fees, features, and support. # Best UK Payment Providers - The definitive guide By Nick Dunse, December 6, 2022 The definitive guide to UK payment providers -- compare Stripe, Adyen, Worldpay, Square, and more on fees, features, and support. How to decide who's the best payment service provider? Really the question is who is right for my business? Since payments are no longer a commodity, they are no longer, all the same, each payment provider has different features, pricing, customer service and industry focus. That means that there are better and worse options for your business based on your needs. Below we'll show you who are the best payment providers based on those themes. Platform availability The often overlooked but really most important factor is access and availability of payments. Since your business will be using off the shelf software to take payments you will need to ensure from day one that your chosen service provider is compatible with all your software. These payments use cases could be your online shopping cart, your in-store terminals, back-office invoice payments or even payments via phone and snail-mail. Below are statistics gathered from Shuttle on the most widely integrated payment gateways by software platform type. Customer service We find that customer service is one of the major reasons why merchants search for a new payment service provider. It might be that their account has been locked or frozen and they can't take payments, or something less dramatic like they no longer have an account manager to speak to. To get the best out of customer service you should ask yourself what kind of relationship do you want with your payment provider. Do you want an account manager or would you prefer to get everything virtually and talk to the team on chat when needed. It's rare that you can find a provider that has booth everything you need from the interface as well as strong account management. Of course, anytime account management is involved there are likely to be cost implications somewhere, but this may be the best thing for you. We'd highly recommend closer account management and service if your business is high(er) risk, has peaks of payments or is in certain markets. Alternative payment methods Not sure that some payment methods should be still called 'alternative' since they are the primary method of payment in some markets, the use of cards across the globe is not a given and certainly under some pressure with their higher fees and fraud challenges. It's very likely that you'll need to use APM's and that's either because new younger buyers have adopted them or the country you're selling in prefers them. Can you increase sales conversion rates if you add Apple Pay, Google Pay, Buy Now Pay Later and PayPal? - Work out where you need to sell and who to? - What are the relevant payment methods for that country/region? - What are the relevant payment methods for your demographic? - Do you need a combination of payment methods at checkout? - It's likely you'll need two PSPs due to BNPL Everyone wants cheaper payment processing and using alternative payment methods might be the best way to achieve that whilst improving speed of payment. Some payment methods like Open Banking or those methods that fix the transaction fee are great when the payments are slightly higher. But of course we know that cards are still very convenient for many, even for B2B transactions, not to mention the 'points' opportunities that some enjoy. So are the 'cheapest' fees really best for you and are they really that cheap? Well, the answer is possibly not, now you really need to be considering total cost of ownership and working out the total cost of selling. We see extra fees added for all kinds of things, gateway fees, service fees, feature fees... Here's what you should look at when considering fees and the price of payments: - Consider the bigger picture with price, don't just go for the lowest card processing: connected, efficiencies, FX, hardware ownership - Maybe fees go up but so does conversion rates? - Is Interchange + pricing better for you than a blended rate? - PSPs can change pricing on you if behaviour changes! - Custom pricing is not usually available if you process less than £50k - Some PSPs can go low on pricing because they are also the acquirer/payment method Card processors can offer two types of pricing, the first is called 'a blended rate' the second is 'interchange plus (plus)'. Blended rates are a fixed rate for domestic and international sales regardless of card type; because the card schemes (AMEX, Mastercard, VISA) all price card types differently, a corporate card transaction is more expensive than a local debit card. Blended rates are not good if all your business is on local debit cards, you're overpaying. But this pricing is more predictable. Interchange plus pricing means that whatever the card schemes charge your service provider will mark that up and pass the cost to you, for example 1% + 0.3% + £0.20. Typically interchange plus pricing is for mature business and cheaper. For free try our payments marketplace and compare payment service providers to find the right one for your business. Visit our payments marketplace now. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ### Merchant Account Providers Compared: 12 Best Options for 2026 ### How to Send Payment Requests: The Complete Guide to Digital Payment Collection ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Visit our payments marketplace now.](httsp://shuttleglobal.com/merchants) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [GuideMerchant Account Providers Compared: 12 Best Options for 2026→](/guides/merchant-account-providers/) - [GuideHow to Send Payment Requests: The Complete Guide to Digital Payment Collection→](/guides/how-to-send-payment-requests/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/ --- # HubSpot Payment Links: Setup, Integrations & Alternatives | Shuttle > How to create and use payment links in HubSpot. Covers Commerce Hub pricing, Stripe integration, workflow automation, limitations, and better... # HubSpot Payment Links: Setup, Integrations & Alternatives By Nick Dunse, December 24, 2025 How to create and use payment links in HubSpot. Covers Commerce Hub pricing, Stripe integration, workflow automation, limitations, and better... Talk to us Make enabling payments for your platform and merchant users easy. HubSpot has evolved from a CRM and marketing platform into a commerce tool. With Commerce Hub, HubSpot now lets you create payment links, collect revenue through invoices, and manage subscriptions -- all without leaving the platform. For sales teams already running their pipeline in HubSpot, that means fewer tabs, faster closes, and less friction between "deal won" and "payment received." But HubSpot payment links come with trade-offs. They only work with Stripe or HubSpot Payments (US-only), they lack advanced checkout customisation, and the per-transaction fees add up. This guide walks through everything you need to know: how to create HubSpot payment links, how the payment gateway integration works, what the limitations are, and when a third-party payment link provider is the better option. ## What Is HubSpot Commerce Hub? Commerce Hub is HubSpot's built-in payments and billing suite. It launched in 2023 as a rebrand and expansion of the original HubSpot Payments feature. Commerce Hub bundles four tools together: - Payment links -- shareable URLs that open a hosted checkout page. Buyers can pay by card or ACH (if using HubSpot Payments). - Invoices -- send branded invoices directly from deal records, with online payment built in. - Quotes -- create quote documents that include a payment step, so prospects can sign and pay in one flow. - Subscriptions -- manage recurring billing tied to HubSpot line items and deal stages. Commerce Hub is available on all HubSpot plans, including Free. However, the payment processing side requires either HubSpot Payments (US businesses only, powered by Stripe behind the scenes) or a direct Stripe integration (available globally). Without one of these connected, you can create payment links but buyers will have no way to actually pay. ## HubSpot Payments Pricing There is no monthly fee to use Commerce Hub or payment links. HubSpot charges per transaction: - HubSpot Payments (US only): 2.9% for card transactions, 0.5% (capped at $10) for ACH bank transfers. - Stripe integration: standard Stripe processing fees apply (typically 2.9% + 30¢ for cards). HubSpot adds a 0.5% platform fee on top of Stripe's fees. That 0.5% platform fee on the Stripe integration is important. If you process $100,000 per year through HubSpot payment links using Stripe, you are paying an extra $500 on top of Stripe's standard rates. For high-volume teams, this makes HubSpot one of the more expensive ways to share payment links. ## How to Create Payment Links in HubSpot Creating a payment link in HubSpot takes a few minutes. You will need either HubSpot Payments or Stripe connected before you start. Here is the step-by-step process: - Step 1: Go to Commerce > Payment Links in your HubSpot account. Click "Create payment link." - Step 2: Choose whether to add existing line items from your product library or create a one-off charge. You can set one-time or recurring pricing. - Step 3: Customise the checkout page. Add your company name, a description, and optionally collect billing address, shipping address, or custom form fields. - Step 4: Configure after-payment behaviour. You can redirect buyers to a thank-you page or show a default confirmation message. - Step 5: Copy the payment link URL and share it via email, chat, social media, or embed it on your website. Each payment link gets a unique URL hosted on HubSpot's domain. You can also generate an embed code to drop the checkout directly into a webpage. When a buyer completes a payment, HubSpot automatically creates or updates the contact record, logs the payment, and can trigger workflows -- which is where the real CRM advantage comes in. ## HubSpot Payment Gateway Integration: Stripe and PayPal HubSpot supports two payment processing options. Your choice determines which payment methods buyers can use and where your money settles. HubSpot Payments is HubSpot's own processor, built on Stripe's infrastructure. It is only available to US-based businesses with a Starter plan or above. It supports credit/debit cards and ACH bank transfers. Funds settle to your bank account in 2-3 business days. The advantage is simplicity -- you apply and get approved within HubSpot, with no separate Stripe account needed. The Stripe integration is available globally and connects your existing Stripe account to HubSpot. This gives you access to all of Stripe's payment methods (cards, wallets, SEPA, iDEAL, and more depending on your Stripe configuration). It is the better choice for international businesses or teams that already use Stripe and want to keep their existing merchant relationship. What about PayPal? HubSpot does not have a native PayPal integration for payment links. You can connect PayPal through third-party apps in the HubSpot Marketplace (like PayPal checkout integrations), but these do not feed into Commerce Hub the same way Stripe does. If PayPal is critical for your buyers, you will need to use PayPal's own payment links or a third-party provider that supports multiple gateways. ## Using Payment Links in HubSpot Workflows The real power of HubSpot payment links is not the checkout page itself -- it is what happens before and after. Because payment events feed directly into the CRM, you can build automated workflows around the entire payment lifecycle. Here are common workflow automations that work with HubSpot payment links: - Post-purchase email sequences: trigger onboarding emails, delivery instructions, or upsell offers the moment a payment completes. - Deal stage automation: automatically move deals to "Closed Won" when the associated payment link is paid. No manual CRM updates needed. - Payment reminder sequences: send follow-up emails to contacts who received a payment link but have not completed payment after 3, 7, or 14 days. - Internal notifications: alert account managers or fulfilment teams via Slack or email when a high-value payment is received. - List segmentation: automatically tag contacts as customers and segment them by product purchased, amount spent, or subscription tier. These workflows work with both HubSpot Payments and the Stripe integration. The key trigger is the "Payment" event in HubSpot's workflow builder, which fires whenever a payment link, invoice, or quote is paid. You can combine it with deal, contact, or company properties to build sophisticated post-payment automations. ## Adding Payment Links to Emails, Forms, and Quotes Once you have created a payment link, there are several ways to distribute it across HubSpot's tools: Marketing and sales emails. In HubSpot's email editor, you can insert a payment link as a CTA button or hyperlink. This is useful for renewal reminders, event registration confirmations, and promotional campaigns. The link opens HubSpot's hosted checkout page in the buyer's browser. For ideas on using payment links across marketing channels, see our guide on real merchant workflows that work better with payment links. Quotes. HubSpot quotes can include a checkout step where the buyer signs the quote and pays in one flow. This uses the same Commerce Hub infrastructure as payment links. You create the quote from a deal record, add line items, enable payment collection, and share it with the prospect. When they pay, the deal automatically updates. Website pages and forms. You can embed a payment link's checkout module directly on HubSpot-hosted pages or link to it from any form submission confirmation page. For landing pages, use the embed code to render the checkout inline rather than redirecting buyers to a separate page. Social media and messaging. Payment links are just URLs, so they work anywhere you can paste a link -- LinkedIn messages, WhatsApp conversations, SMS, or Instagram DMs. This makes them useful for sales reps who close deals through direct conversations. ## HubSpot Payment Link Limitations HubSpot payment links are convenient if you already live in the HubSpot ecosystem, but they have meaningful limitations compared to dedicated payment link providers: - Gateway lock-in. You can only use Stripe or HubSpot Payments. There is no way to connect Adyen, Worldpay, Braintree, or any other processor. If your business uses multiple PSPs or needs to route payments by region, HubSpot cannot support that. - US-only native payments. HubSpot Payments (the lower-fee option with ACH support) is restricted to US businesses. International companies must use the Stripe integration, which carries the extra 0.5% platform fee. - Limited checkout customisation. The hosted checkout page is functional but basic. You can add your logo and a description, but there is no deep branding control, custom CSS, or ability to match your website's full design language. - No multi-currency support on HubSpot Payments. HubSpot Payments only processes in USD. The Stripe integration supports Stripe's currencies, but the Commerce Hub interface can be clunky with non-USD pricing. - Platform fee. The 0.5% fee on Stripe transactions is unavoidable. Over time, this makes HubSpot payment links more expensive than using Stripe's own payment links or a dedicated provider. - No white-label options. Payment links are hosted on HubSpot's domain. You cannot use your own domain for the checkout page, which can reduce trust for buyers unfamiliar with HubSpot. For many small and mid-market teams, these trade-offs are acceptable. But for platforms, larger businesses, or anyone who needs multi-PSP routing, white-label checkout, or global payment method coverage, HubSpot's built-in payment links will feel restrictive. ## Alternatives to HubSpot Payment Links If HubSpot's payment links do not fit your requirements, several alternatives work well alongside or instead of Commerce Hub: Stripe Payment Links. If you already have a Stripe account, you can create payment links directly in the Stripe Dashboard without the extra 0.5% HubSpot fee. Stripe's links support more payment methods, multi-currency checkout, and custom branding. The downside is that payments will not automatically sync to HubSpot deals and contacts without additional integration work. PayPal.me and PayPal Buttons. PayPal offers its own payment links through PayPal.me and checkout buttons. These give you access to PayPal's buyer base and pay-later options. Like Stripe direct, the trade-off is no native HubSpot CRM sync. Shuttle Payment Links. For CRM platforms and SaaS businesses that need to embed payment links into their workflows, Shuttle provides white-label payment links that connect to any PSP -- not just Stripe. You can route payments through whichever gateway your business or your customers already use, and the checkout pages are fully brandable. Shuttle's payment link API is designed for platforms that want to offer payment collection as a feature to their own users, which makes it a strong fit for CRM and workflow tools that need payment capabilities without building them from scratch. Third-party HubSpot integrations. The HubSpot Marketplace includes payment integrations from providers like Chargebee, Paddle, and QuickBooks. These add recurring billing, tax compliance, or accounting features that Commerce Hub lacks. Most use webhooks to sync payment data back to HubSpot contacts and deals. ## Who Should Use HubSpot Payment Links? HubSpot payment links are best suited for a specific set of use cases. They work well if: - Your team already uses HubSpot as its primary CRM and you want payment data flowing into contact records without any integration effort. - You process relatively low volume and the 0.5% platform fee on Stripe transactions does not significantly impact margins. - You are a US-based business that can use HubSpot Payments for the lower ACH rates on high-value B2B invoices. - Your sales process relies on quotes-to-cash and you want buyers to sign and pay within the same HubSpot quote flow. If you need multi-PSP support, white-label checkout, global payment method coverage, or you are a platform building payment features for your own customers, a dedicated payment infrastructure provider will serve you better. Talk to Shuttle if you are looking for payment links that work across any gateway and can be embedded into any CRM or workflow tool. ## Frequently Asked Questions ### Does HubSpot support PayPal for payment links? No. HubSpot payment links only work with HubSpot Payments (US-only) or a connected Stripe account. There is no native PayPal integration for Commerce Hub. You can add PayPal through third-party Marketplace apps, but those operate outside the payment link and invoice system. ### Can I use HubSpot payment links outside the US? Yes, but only through the Stripe integration. HubSpot Payments itself is restricted to US businesses. If you are outside the US, connect your Stripe account to HubSpot and you can create payment links that accept global card payments. Note that the 0.5% HubSpot platform fee applies on top of Stripe's standard processing fees. ### How much does HubSpot charge for payment links? There is no subscription fee to use Commerce Hub or create payment links. Transaction fees depend on your processor: HubSpot Payments charges 2.9% for cards and 0.5% (max $10) for ACH. The Stripe integration passes through Stripe's standard rates plus an additional 0.5% HubSpot platform fee. ### Can I white-label HubSpot payment links with my own domain? No. HubSpot payment links are hosted on HubSpot's domain and cannot be mapped to a custom domain. You can add your logo and company name to the checkout page, but the URL will always show a HubSpot subdomain. If white-label checkout pages on your own domain are a requirement, you will need a dedicated payment link provider like Shuttle or build a custom Stripe Checkout integration. ## Related Reading Explore More ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Stripe](/payment-providers/stripe/) - [Stripe integration](/payment-providers/stripe/) - [PayPal](/payment-providers/paypal-commerce/) - [real merchant workflows that work better with payment links](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [Instagram DMs](/blog/payment-links-for-instagram-sales/) - [Stripe account](/payment-providers/stripe/) - [Shuttle](/platforms/) - [Talk to Shuttle](/discovery/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/ --- # Braintree vs Checkout.com - which is the right choice for an enterprise merchant? | Shuttle > Braintree vs Checkout.com for enterprise merchants -- compare pricing, global coverage, developer tools, and payout speed. # Braintree vs Checkout.com - which is the right choice for an enterprise merchant? By Nick Dunse, April 10, 2024 Braintree vs Checkout.com for enterprise merchants -- compare pricing, global coverage, developer tools, and payout speed. I. Introduction In today's digital age, online payments have become an essential part of our lives. As an enterprise merchant, choosing the right payment gateway can be challenging. Two popular options are Braintree and Checkout.com. In this article, we will compare these two payment gateways and help you choose the right one for your business needs. Let's get started! II. What are Braintree and Checkout.com? Braintree and Checkout.com are both payment gateway providers that offer a range of features and services for businesses of all sizes. Both companies have their own unique offerings and strengths, making them suitable for different types of merchants. In this section, we'll take a closer look at what exactly each company offers and how they can benefit your business. III. Features and Pricing Comparison When it comes to choosing between Braintree and Checkout.com, one of the most important factors to consider is their features and pricing comparison. Both platforms offer a range of payment gateway options, including credit cards, debit cards, and digital wallets like Apple Pay and Google Wallet. However, there are some key differences in the features and pricing offered by each platform. One of the main benefits of Braintree is its ease of use. The platform has a simple and intuitive interface, making it easy for merchants to set up and manage their payments. Additionally, Braintree offers a range of fraud prevention tools to help protect against chargebacks and other forms of payment fraud. On the other hand, Checkout.com offers a more comprehensive range of features, including the ability to accept multiple currencies and integrate with a wide range of e-commerce platforms. Additionally, Checkout.com offers competitive pricing, with lower transaction fees compared to Braintree. Ultimately, the best choice for an enterprise merchant will depend on their specific needs and priorities. If ease of use and simplicity are a top priority, Braintree may be the better option. On the other hand, if a more feature-rich platform with competitive pricing is a priority, Checkout.com may be the better choice. It's important to carefully evaluate both platforms before making a decision based on features and pricing. IV. Security and Compliance Security and compliance are critical factors when it comes to choosing a payment gateway. Both Braintree and Checkout.com have robust security measures in place to protect their customers' data. However, there are some differences between the two platforms when it comes to compliance with industry regulations. Braintree is a subsidiary of PayPal and is fully compliant with all major payment card industry standards (PCI DSS). This means that Braintree has undergone rigorous security testing and has met strict requirements for protecting customer data. Additionally, Braintree offers tokenization technology, which replaces sensitive payment information with a unique token that can be used for future transactions without exposing the original data. Checkout.com, on the other hand, is a global payment platform that operates under the license of the Financial Conduct Authority (FCA) in the UK. This means that Checkout.com complies with all relevant EU and UK regulatory requirements, including GDPR and PSD2. The platform also uses end-to-end encryption to protect customer data during transmission and at rest. In conclusion, both Braintree and Checkout.com offer secure and compliant payment gateways. However, if you're looking for a platform that meets additional regulatory requirements or has a stronger focus on risk management, Checkout.com may be the better option. On the other hand, if you value ease of integration and customization, as well as a wider range of features, Braintree may be the better fit for your business needs. Ultimately, the best choice depends on your specific requirements and business goals. V. Integration and Customization When it comes to integrating and customizing payment gateways, both Braintree and Checkout.com offer a range of options to suit different business needs. For example, Braintree offers a developer platform that allows businesses to customize their payment forms and integrate with third-party software. Similarly, Checkout.com provides a flexible API that can be customized to fit specific business requirements. Both platforms also offer integration guides and support resources to help businesses get started quickly and easily. Ultimately, the choice between Braintree and Checkout.com depends on factors such as ease of integration, customization capabilities, and technical expertise. VI. Customer Support Customer support is a critical aspect of any business, especially when it comes to e-commerce platforms like Braintree and Checkout.com. Both companies offer customer support through various channels such as email, phone, and live chat. However, there are some differences in their customer support offerings. Braintree offers 24/7 customer support via email, phone, and live chat. They also have a dedicated support team for developers who can provide technical assistance. On the other hand, Checkout.com provides customer support through email and live chat. They also have a knowledge base with articles and tutorials on how to use their platform. In terms of response time, both companies are relatively fast in responding to customer inquiries. However, Braintree has a reputation for being faster at resolving issues and providing technical support due to its smaller size compared to Checkout.com. Overall, both Braintree and Checkout.com offer excellent customer support, but Braintree may be more responsive and have a more developer-focused support team. It ultimately depends on the specific needs and preferences of the enterprise merchant. VII. Conclusion In conclusion, both Braintree and Checkout.com offer unique features and benefits that can cater to different needs of businesses. While Braintree may be ideal for small businesses looking for easy integration with popular platforms like WordPress or Shopify, Checkout.com may be better suited for larger enterprises seeking advanced customization options and robust security measures. Ultimately, the choice between these two payment gateways depends on the specific requirements of each business. It is important to carefully evaluate the features and pricing before making a decision, and to consider factors such as customer support and compliance standards when choosing a payment gateway provider. ## Related Reading Explore More ### How to Connect Checkout.com to Twilio for Voice & IVR Payments ### Shuttle vs Checkout.com for Platforms ### Checkout.com Alternatives for Platforms ### Merchant Account Providers Compared: 12 Best Options for 2026 ### Agent-Native Checkout: Why AI Commerce Needs New Payment APIs ### How to Connect Braintree to Twilio: Voice Payments & Payment Links ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Connect Checkout.com to Twilio for Voice & IVR Payments→](/guides/checkout-com-twilio-integration/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [AlternativeCheckout.com Alternatives for Platforms→](/alternatives/checkout-com/) - [GuideMerchant Account Providers Compared: 12 Best Options for 2026→](/guides/merchant-account-providers/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [GuideHow to Connect Braintree to Twilio: Voice Payments & Payment Links→](/guides/braintree-twilio-integration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/brightpearl-growth/ --- # How payments helped Brightpearl's growth | Shuttle > How embedded payments helped Brightpearl grow. Shuttle enabled the retail operations platform to offer seamless payment processing to its merchants. # How payments helped Brightpearl's growth By Nick Dunse, January 1, 2026 How embedded payments helped Brightpearl grow. Shuttle enabled the retail operations platform to offer seamless payment processing to its merchants. Brightpearl is an ERP platform focussing on the wholesale and retail market. Selected by the Forrester report "as the only retail focused Digital Operations Platform." In 2018 Brightpearl transacted $1.8bn of invoices into cash Brightpearl's recent success has come under the leadership of Derek O'Carroll, CEO for the last four years. Derek's stated that he's been on a mission to move Brightpearl's customer base towards the mid-market and away from a majority of micro customers. Like many SaaS businesses the move to working with larger clients is a proven path to success. The Challenge Sell to larger customers and support their payments requirements. In 2016, 70% of Brightpearl's revenue was from micro retailers, the number fell to 28% in 2018 and continues to slide in the desired direction. Bigger customers pay more and churn less. With the above goal in mind, Brightpearl payments needed to become a key feature and differentiator in solving this challenge; mid-market customers are more demanding when it comes to payment provider preferences. Brightpearl began working with Shuttle to help them achieve their goals and deliver on making payments a winning feature. Average saving on integrating 6 payment providers ## How Shuttle helped Working with Shuttle Brightpearl were able to offer payments as a core integration, rather than just an addon service. This allowed them to repackage their offering to better suit larger customers. By shifting their customer profile to larger clients, Brightpearl has been able to drive deeper into their target territories. Shuttle has been key to this success, allowing Brightpearl to offer its customers, multiple payment providers, very quickly. Shuttle has also offered Brightpearl customers payment specific support, freeing up the Brightpearl team to focus on delivering value across the rest of their offering. "Partnering with Shuttle enables us to deliver consistent workflows for our customers, making the process of managing payments simple, regardless of payment processor or channel." Scott Hill, VP Product - Brightpearl The Result Brightpearl has had to ensure compatibility with the leading payments providers in key geographical markets to win and retain customers. This would have been extremely hard to manage in-house and would have pulled resources away from working on their core offering. Brightpearl can now rely on Shuttle to support their growth plans, partnering together along the journey: - Access greater addressable markets faster - More focus on their core product roadmap - Consistency across all payment integrations and their UX design - No need to worry about ongoing compliance issues - A trusted expert payments team on hand - Cost and time efficiencies Time it takes to integrate 12 payment providers is based on Shuttle's experience doing full integrations not using the gateway's hosted process using two full-time employees. Cost of building an in-house team is based on Shuttle's estimates of six full-time employees. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/building-success-how-accepting-card-payments-can-boost-your-business/ --- # Builders who accept cards for payment are better off | Shuttle > Builders and tradespeople who accept card payments win more jobs and get paid faster. Learn how payment links make it simple without a card terminal. # Builders who accept cards for payment are better off By Nick Dunse, December 25, 2025 Builders and tradespeople who accept card payments win more jobs and get paid faster. Learn how payment links make it simple without a card terminal. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. ## Building Success: How Accepting Card Payments Can Boost Your Business Accepting card payments can substantially expand sales opportunities for businesses. By providing customers with the option to pay using credit or debit cards, businesses can tap into a broader customer base. Many individuals prefer to use cards for their transactions, and not accepting card payments may result in lost sales. Moreover, accepting card payments can facilitate larger transactions, as customers may not always have sufficient cash available. This can lead to an increase in the average transaction value, ultimately boosting sales. Additionally, accepting card payments can also facilitate impulse purchases. With the option to pay by card, customers are more likely to make spontaneous purchases, unhindered by cash constraints. This can result in an overall increase in sales, as customers are more likely to make additional purchases when they have the convenience of card payments. Key Takeaways - Accepting card payments can increase sales opportunities by catering to customers who prefer using cards over cash. - It provides convenience for customers, making it easier for them to make purchases without worrying about carrying cash. - Accepting card payments can improve cash flow by ensuring faster and more secure transactions. - Businesses that accept card payments gain a competitive advantage by meeting the expectations of modern consumers. - It enhances the overall customer experience by offering a variety of payment options and increasing customer satisfaction. Convenience for Customers Convenience in a Fast-Paced World In today's fast-paced world, many people prefer the ease and convenience of paying with a card rather than carrying cash. By offering this payment option, you are catering to the needs and preferences of your customers, making it more convenient for them to do business with you. Increased Customer Satisfaction and Loyalty This can lead to increased customer satisfaction and loyalty, as customers appreciate the convenience of being able to pay with a card. Additionally, accepting card payments can also make it easier for customers to track their spending. Better Financial Management Many people prefer to use cards for their purchases because it allows them to easily track their expenses and manage their finances. By offering this payment option, you are providing a service that can help your customers better manage their money, which can ultimately lead to increased customer satisfaction and loyalty. Improved Cash Flow Accepting card payments can also lead to improved cash flow for your business. When customers pay with a card, the funds are typically deposited into your account within a few days, whereas cash payments may need to be deposited in person at a bank. This can help improve your business's cash flow, as you will have quicker access to funds from your sales. Additionally, accepting card payments can also reduce the risk of theft or loss associated with handling large amounts of cash, further improving your business's financial security. Furthermore, accepting card payments can also help you better manage your business's cash flow by providing you with more predictable revenue streams. With card payments, you can more easily track and forecast your incoming revenue, allowing you to better plan and manage your business's finances. This can help you make more informed decisions about inventory, staffing, and other expenses, ultimately leading to improved financial stability for your business. Competitive Advantage Benefits of Accepting Card Payments | Statistics Increased Sales | Businesses that accept card payments typically see an increase in sales by 20-30% Customer Convenience | 83% of consumers prefer to pay with a card over cash Global Reach | Accepting card payments allows businesses to reach international customers and expand their market Reduced Risk | Less risk of theft and fraud compared to handling large amounts of cash Accepting card payments can also give your business a competitive advantage in the marketplace. In today's digital age, many consumers expect businesses to offer the convenience of paying with a card. By not accepting card payments, you may be putting your business at a disadvantage compared to competitors who do offer this payment option. Offering card payments can help you attract new customers and retain existing ones, ultimately giving you an edge over businesses that do not offer this convenience. Additionally, accepting card payments can also help you stay competitive by keeping up with the latest trends in payment technology. With the rise of mobile payment options and digital wallets, it is important for businesses to offer a variety of payment options to meet the needs and preferences of their customers. By accepting card payments, you are demonstrating that your business is forward-thinking and adaptable, which can help you stand out in a crowded marketplace. ## Enhanced Customer Experience Accepting card payments can also enhance the overall customer experience for your business. By offering this payment option, you are providing customers with a convenient and efficient way to make purchases, which can lead to increased satisfaction and loyalty. Additionally, accepting card payments can also help streamline the checkout process for your customers, making it quicker and easier for them to complete their transactions. This can lead to a more positive overall experience for your customers, ultimately improving their perception of your business. Furthermore, accepting card payments can also provide added security and peace of mind for your customers. With the rise of identity theft and fraud, many people prefer to use cards for their purchases because they offer added protection and security compared to carrying cash. By offering this payment option, you are providing an extra layer of security for your customers, which can help build trust and confidence in your business. Access to Valuable Data ## Unlocking Customer Insights With card payments, you can collect information about customer spending habits, preferences, and demographics. This data can be used to inform your marketing and sales strategies, helping you better understand and serve your customers. By analyzing customer data, you can identify trends and patterns in customer behavior, allowing you to tailor your products and services to better meet the needs of your target audience. Informing Business Decisions Accepting card payments can also provide valuable insights into the performance of your business. By analyzing transaction data, you can gain a better understanding of which products are selling well and which may need improvement. This information can help you make more informed decisions about inventory management, pricing strategies, and marketing efforts. ## Improving Business Performance Ultimately, the data and insights gained from accepting card payments can lead to improved business performance and profitability. By making data-driven decisions, you can optimize your business operations, increase revenue, and stay ahead of the competition. Streamlined Business Operations Accepting card payments can also help streamline various aspects of your business operations. With card payments, you can automate many aspects of the payment process, such as invoicing and reconciliation, which can save time and reduce the risk of human error. Additionally, accepting card payments can also help streamline accounting processes by providing detailed transaction records that can be easily integrated into your financial systems. Furthermore, accepting card payments can also help streamline inventory management by providing real-time data on sales and customer purchasing patterns. This information can help you better forecast demand and manage inventory levels, ultimately leading to improved efficiency and cost savings for your business. Additionally, accepting card payments can also help streamline customer service processes by providing quick and efficient payment options that can help reduce wait times and improve overall customer satisfaction. In conclusion, accepting card payments can provide numerous benefits for your business, including increased sales opportunities, convenience for customers, improved cash flow, competitive advantage, enhanced customer experience, access to valuable data, and streamlined business operations. By offering this payment option, you are demonstrating that your business is adaptable and forward-thinking, which can help you stand out in a crowded marketplace. Ultimately, accepting card payments can help drive growth and success for your business in today's digital age. What are the benefits of accepting card payments for businesses? Accepting card payments can boost a business by increasing sales, attracting more customers, and providing convenience for both the business and its customers. It also reduces the risk of handling cash and allows for easier tracking of transactions. ## What types of card payments can businesses accept? Businesses can accept various types of card payments, including credit cards, debit cards, and contactless payments. They can also accept payments through mobile wallets and online payment platforms. How can accepting card payments improve customer satisfaction? Accepting card payments can improve customer satisfaction by offering a convenient and secure payment option. It also allows customers to make purchases even if they do not have cash on hand, leading to a more positive shopping experience. What are the security measures businesses should take when accepting card payments? Businesses should ensure that they comply with Payment Card Industry Data Security Standard (PCI DSS) requirements, use secure payment terminals, and implement encryption and tokenization to protect cardholder data. It is also important to regularly update security measures and train employees on best practices for handling card payments. How can businesses integrate card payment systems into their operations? Businesses can integrate card payment systems by partnering with a payment processor or acquiring bank to set up a merchant account. They can then choose the appropriate payment terminals or online payment gateways to accept card payments in-store or online. ## Related Reading Explore More ### How to Take Payments on boost.ai: PCI-Compliant Virtual Agent Payments ### How to Get Payments Off Your Product Roadmap ### HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideHow to Take Payments on boost.ai: PCI-Compliant Virtual Agent Payments→](/guides/boost-ai-payments/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideHubSpot International Payments: Accepting Cards Outside the Big 5 Currencies→](/guides/hubspot-international-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/buying-moved-into-the-conversation/ --- # Buying Moved Into the Conversation. The Checkout Didn't Follow. | Shuttle > Web commerce was won by whoever owned the checkout page. The next sales channel is the conversation, voice and chat, and it has no checkout in it. # Buying Moved Into the Conversation. The Checkout Didn't Follow. By Shuttle Team, May 27, 2026 Web commerce was won by whoever owned the checkout page. The next sales channel is the conversation, voice and chat, and it has no checkout in it. For twenty years, web commerce was won by whoever owned the checkout page. The cart, the checkout, the payment, all of it on the page, all of it owned by the platform. The strongest shopping carts built their own payments into the checkout, because owning the payment is how a platform stops being a tool and becomes infrastructure. That race is over, and it is not worth re-entering. The web checkout is mature, the incumbents hold it, and a merchant will not migrate their storefront to capture a few points of payment economics. But buying has moved off the page. People increasingly buy by talking: they call a number and an AI voice agent answers, or they open a chat and an agent runs the thread to the sale. This is a new sales channel, and a new channel is never won by the last channel's stack. It is won by whoever solves the hardest part of it. In the conversation, the hardest part is the payment. > We pulled the full argument, with the adoption forecasts, conversion data, market sizing, and the architecture, into a white paper: The shopping carts won the page. The conversation is still up for grabs. This post is the short version. ## The page was never as finished as it looked Across fifty studies run between 2006 and 2025, the average documented online shopping cart abandonment rate is 70.22 percent (Baymard Institute, 2025). The web checkout, the thing the incumbents perfected, still loses roughly seven of every ten carts. That is the mature channel. It is not a model worth copying into the next one. ## Buying moved into the conversation Watch how a purchase happens now, away from a storefront. A customer phones a business to place an order, change a booking, settle an invoice, or renew a policy. A few years ago a person answered. Today an AI voice agent does, and it holds the whole conversation: the questions, the options, the upsell, the confirmation. The same shift is happening in text. A customer opens a chat, messages on WhatsApp, or replies to a marketing thread, and an AI chat agent answers, recommends, handles the objection, and brings them to the point of sale, all inside the thread, without a tab ever opening. These are not support tickets. They are sales, often the higher-intent ones a customer wanted to talk through before committing. The constraint that kept these channels small, a trained human on every interaction, is the constraint that just lifted. And the data backs it: shoppers who engage in a chat session convert at 12.3 percent against 3.1 percent for those who do not (Forrester, 2025), and 37 percent of phone leads convert during the call (Invoca, 2025). The places where buying is moving are the places where buying closes. The agent handles all of it, right up to the moment money changes hands. ## A sales channel with no checkout And then the conversation hits a wall. The agent that just closed the sale cannot take the payment. So one of three things happens, and all three leak: - The call is transferred to a human, which throws away most of the economics that made the agent worth deploying. - A card number is read aloud and keyed in, which drops card data straight into a recording or a transcript and creates a compliance problem the business may not even know it has. - The customer is pushed back to a web page to pay, which is the exact friction the conversation was supposed to remove. Against a 70 percent abandonment rate, a measurable share never complete. Every one of those is a sale that was won and then degraded at the last step. This is the same shape of problem the web solved twenty years ago. A storefront that could show the product but could not take the money was not a store. The conversation is at that exact stage now: it can do everything except finish. ## The next channel is won at the payment, not the agent Agents are capable now, and on their way to being a commodity. Most businesses will have a competent voice or chat agent within a few years, so competing on the agent is competing on a feature everyone will soon have. The payment is the hard part, for three reasons that do not exist on a web page: - The card cannot be exposed. On a voice call the number cannot land in the recording or the model's context. On chat it cannot touch the transcript. This is PCI with teeth, in exactly the channels that are opening up. - It has to settle on the merchant's own rail. The merchant already has a provider, a negotiated rate, a settlement account. A channel that forces a new provider is a migration, and merchants do not buy migrations. - It has to work across every surface. Voice, chat, SMS, and the handoffs between them. A customer should be able to start on chat, move to voice, and have the cart and the card token follow. Whoever makes the payment work inside the conversation owns the conversation, the same way owning the checkout page decided the web. And that position is currently empty. The incumbents are defending the page they already won. The agent vendors are competing on the agent. ## What closes the gap: a payment layer A gateway processes one merchant on one integration. An orchestrator routes between providers, still page-bound. A PayFac makes you the payment provider, the heaviest version of building it yourself. None of these puts payment capture inside a voice call or a chat thread on the merchant's own provider. A payment layer does. It sits between software and the payment providers, exposing the merchant's existing payment relationship to wherever the agent operates, and carrying the compliance so the platform does not have to. Because the conversation is a separate channel, the payment in it is additive: it runs alongside whatever the merchant already uses on the web, on the same provider, and asks the web checkout to change nothing. That means it does not wait on anyone's roadmap. This is what Shuttle is built to be. You integrate once; every merchant gets payment capture across voice, chat, and links, and every merchant keeps the provider they already brought, across more than forty of them. PCI DSS Level 1, ISO 27001, and SOC 2 sit at the layer, so the card never enters the recording, the transcript, or the model's context. Shuttle connects Twilio voice and chat flows to the gateways platforms already use, and runs the voice payment pattern in production for AI voice platforms like PolyAI and operational commerce platforms like Brightpearl. ## Read the full argument This post is the outline. The white paper has the evidence behind every claim, the market sizing from four independent firms, the four criteria that separate a real payment layer from a bolt-on patch, and the architecture in detail. Read the white paper: The shopping carts won the page. The conversation is still up for grabs. The page is taken. The conversation is up for grabs. If you are a platform or an agent vendor that can win the customer but cannot yet finish the sale, talk to us, or see how Voice Checkout and the Embedded Platform put the payment in the conversation. ## Related Reading Explore More ### How PSPs Get Distribution Into Enterprise Software ### AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [The shopping carts won the page. The conversation is still up for grabs.](/payment-layer/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Read the white paper: The shopping carts won the page. The conversation is still up for grabs.](/payment-layer/) - [talk to us](/discovery/) - [Voice Checkout](/platforms/voice-checkout/) - [Embedded Platform](/platforms/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [GuideAI Voice Agents and Payments: How PolyAI Captures Payments in Conversation→](/guides/ai-voice-agents-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/call-answering-service-payments/ --- # Why Most Call Answering Services Can't Take Payments | Shuttle > Most call answering services handle messages and appointments -- but can't take a payment. # Why Most Call Answering Services Can't Take Payments By shuttle-team, February 26, 2026 Most call answering services handle messages and appointments -- but can't take a payment. Talk to us Make enabling payments for your platform and merchant users easy. A caller phones your client's business. Your receptionist picks up, takes a message, books an appointment, maybe transfers the call. Professional, efficient, exactly what your client pays for. Then the caller says: "Can I pay my invoice?" And your answering service hits a wall. ## The Payment Gap in Call Answering There are roughly 6,000 contact centres in the UK employing 1.3 million people. A significant slice of that market is call answering services -- from Moneypenny-scale operations with 1,000+ staff down to five-person teams handling overflow for local businesses. Most of them can handle: - Message taking - Appointment scheduling - Call transfers and routing - Basic order processing - CRM updates - Lead qualification What most of them can't do: take a payment. Not because they don't want to. Because the infrastructure to do it securely -- while handling calls for multiple clients, each with their own payment processor -- doesn't exist in most answering service tech stacks. The result: callers who are ready to pay get told "someone will call you back." Some do call back. Many don't. The client loses a conversion that was sitting right there. ## Why It's Not as Simple as "Just Add Stripe" The naive solution -- "give agents a Stripe login" -- fails for three reasons: ### 1. PCI Compliance The moment an agent hears a card number, your entire phone system is in PCI scope. Call recordings, agent workstations, network infrastructure, CRM -- all of it needs to meet PCI DSS requirements. For a 10-person call answering service, the compliance cost is wildly disproportionate to the business size. PCI DSS Level 1 certification costs hundreds of thousands. Even self-assessment (SAQ-D) is a substantial ongoing burden. Most answering services simply can't justify the cost. ### 2. Multiple Clients, Multiple PSPs Your clients don't all use the same payment processor. Client A uses Stripe. Client B uses Worldpay. Client C processes through PayPal. Client D has a SagePay account. Logging into each client's payment dashboard to process a transaction means: - Agents need credentials for multiple systems - Training multiplies with each new client - No unified view of what's been processed - Card data visible on screen = full PCI scope - A single mis-keyed payment goes to the wrong merchant At 5 clients, this is awkward. At 20, it's unworkable. ### 3. Agent Trust and Fraud Risk Call answering services have staff turnover. Agents handle hundreds of calls daily. Giving them access to card numbers -- even verbally -- creates a fraud vector. One rogue agent memorising card details can result in financial loss, regulatory action, and reputational damage that a small business can't survive. The secure approach is to ensure agents never see or hear card data in the first place. ## What "Adding Payments" Actually Looks Like There are two practical approaches for a call answering service that wants to offer payment collection: ### DTMF Capture During the Call The agent stays on the line. When it's time to pay, the caller enters their card details via their phone keypad. The tones are captured by a PCI-certified payment layer -- masked from the agent and stripped from the recording. The agent sees a confirmation: "Payment of £85.00 approved, last four digits 7291." The caller never left the conversation. The agent never heard a card number. The call recording is clean. PCI scope stays with the payment provider, not the answering service. ### Payment Links via SMS The agent sends a branded payment link to the caller's mobile during the call. "I've just sent you a link -- you can pay on your phone while we chat." The caller completes payment on a hosted checkout page supporting cards, Apple Pay, Google Pay, and bank transfers. This works especially well for callers who can't use a keypad (older handsets, VoIP softphones) or who prefer visual confirmation of the amount. Both approaches can run through the same payment layer, and both route to whichever PSP the client uses -- without the answering service touching card data. ## The Business Case Payment collection is a premium add-on. Answering services that can take payments charge more per call and differentiate from the dozens of competitors offering message-taking. - Higher client retention. A client whose payment flows run through your service doesn't churn to save £50/month on answering fees. The switching cost is too high. - New client segments. Tradespeople, solicitors, medical practices, property managers -- businesses that receive payment calls and currently lose conversions because the answering service can't process them. - Revenue per call. A per-transaction fee (passed through or marked up) turns every payment call into a revenue event, not just a cost. The UK answering services market is estimated at £500M-£800M. Payment collection is one of the highest-value capabilities a service can add -- and one of the least penetrated. ## What to Look For If you're a call answering service evaluating payment infrastructure: Multi-PSP support. Your clients have different payment processors. The solution needs to route each client's payments through their own PSP -- without you integrating with each one individually. Look for 40+ gateway support through a single integration. Limited PCI scope. Card data should never enter your environment. DTMF tones captured externally. Recordings clean. Agents see confirmation only. This drops you to SAQ-A -- the lightest PCI assessment level. Per-transaction pricing. Avoid per-seat licensing. You want cost that scales with payment volume, not headcount. A month where your agents process 50 payments shouldn't cost the same as a month with 5,000. Payment links as a fallback. Not every caller can use a keypad. SMS payment links, branded to the client, give you universal coverage. White-label. The payment experience should carry your client's brand -- or yours. Not a third-party vendor's logo that confuses the caller. Fast setup. You should be live in days, not months. If the integration requires a six-month project, it's the wrong solution for a call answering business. ## The Opportunity Is Now PCI DSS v4.0.1 is raising the bar for everyone who handles payments. Businesses that used to accept the risk of verbal card capture are being told by their compliance teams, their insurers, and their enterprise clients that it's no longer acceptable. That creates demand for answering services that can take payments securely. The services that can offer it will capture the clients that need it. The ones that can't will keep taking messages while the callers who wanted to pay go elsewhere. ## Related Reading - PCI-Compliant Payments for Contact Centres -- the complete guide to secure contact centre payment approaches - Payment Collection for BPOs -- multi-client, multi-PSP payment collection for outsourcers - Secure Payment Collection for Debt Agencies -- payments for the collections vertical Want to add payment collection to your answering service? Shuttle connects your voice flows to 40+ payment gateways with PCI DSS Level 1 compliance. DTMF capture, SMS payment links, white-label branding -- live in days, not months. Per-transaction pricing from $0.20. Book a Demo | See Voice Checkout Explore More ### How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Yellow.ai Payments: In-Call Capture vs Payment Links ### How to Take Payments on Regal.ai Voice Agents: In-Call PCI-Compliant Capture ### How to Take Payments on Aircall: Secure Voice Payment Processing ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope stays with the payment provider, not the answering service](/guides/contact-centre-payments/) - [single integration](/guides/payment-collection-for-bpos/) - [DTMF tones](/guides/dtmf-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [Book a Demo](/discovery/) - [See Voice Checkout](/platforms/voice-checkout/) - [GuideHow to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments→](/guides/salesforce-service-cloud-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideYellow.ai Payments: In-Call Capture vs Payment Links→](/guides/yellow-ai-payments/) - [GuideHow to Take Payments on Regal.ai Voice Agents: In-Call PCI-Compliant Capture→](/guides/regal-ai-payments/) - [GuideHow to Take Payments on Aircall: Secure Voice Payment Processing→](/guides/aircall-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/ --- # Can You Take Card Payments on a Retell AI Voice Agent? | Shuttle > Yes, you can take PCI-compliant card payments on a Retell AI voice agent, as long as the card is captured off-platform. # Can You Take Card Payments on a Retell AI Voice Agent? By Shuttle Team, June 8, 2026 Yes, you can take PCI-compliant card payments on a Retell AI voice agent, as long as the card is captured off-platform. Short answer: yes, but not by capturing the card inside the Retell call. The card has to be taken in a secure, PCI-compliant payment layer that sits alongside Retell, so the card number never reaches your AI agent. Retell runs the conversation, a payment layer like Shuttle runs the secure payment. If you are building on Retell and your flow ends in a payment, this is the question that decides whether you ship. Here is the honest version. ## Why you cannot just capture the card in the call It is tempting to let the customer read or key in their card while they are talking to your agent. Do not. Two reasons: - Retell is not a PCI DSS Level 1 certified payment processor. It is not designed to be one. It runs the voice and the language model. - Its PII redaction runs after the language model has already processed the input. So by the time anything is redacted, the card data has already passed through the AI pipeline. If card digits enter the Retell call, your application, your call recordings, your logs, and Retell's infrastructure all fall into PCI scope. That is a compliance and cost problem you do not want. Building your own PCI DSS Level 1 capture is not realistic either: certification runs to hundreds of thousands of dollars upfront and again every year. The secure pattern, which Retell itself recommends, is to take the card off-platform, before any card details are entered. ## How it actually works When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call at the point of capture. The customer enters their card on their keypad inside that secure environment, so the digits never touch Retell or the language model. The payment is routed to your gateway, and the result comes back to your application. With Shuttle, today this runs over Twilio Pay, with Shuttle as the certified capture and gateway connector. A few specifics founders ask about: - Any gateway, including Stripe. Shuttle connects to 30+ gateways. You configure yours; it handles the routing. Multi-tenant products can run a different gateway per customer. - Pricing is $0.20 per successful transaction. No setup fees. - Your PCI scope drops to SAQ-A, the simplest tier, because you are never storing, processing, or transmitting card data. ## What is possible today, and what is coming This is where most write-ups overpromise, so here is the straight version. Available now: the secure capture at the point of payment. The customer pays, your application gets the result, and the card never passes through Retell. Yours to wire: returning the caller to the same Retell agent and call after payment. It works today: you program the return route in your Twilio flow and pass a conversation ID so the agent picks the conversation back up with context. The payment layer is not yet riding the full call, and the return-leg orchestration is not shipped out of the box. On the roadmap: the payment layer being present for the entire call, or being dialed in at exactly the right moment. Shuttle works with Twilio today, and any carrier coming soon. ## What this means for your build If you are a founder or PM scoping this, the takeaway is simple. You can add real card payments to your Retell agent now, without taking on PCI certification and without putting your stack in scope, by handing the card to a secure payment layer at the point of payment. The capture is production-ready today. The fuller in-call experience, where the agent seamlessly resumes after payment, is in progress. For the technical walkthrough, the integration architecture, and the step-by-step flow, see the full guide: How to take PCI-compliant payments on Retell AI voice agents. Want to talk through your specific flow? Book a call and we will give you the honest current state, not a roadmap pitch. ## Related Reading Explore More ### How AI Voice Agents Take PCI-Compliant Payments ### How to Take Payments on Retell AI Voice Agents: PCI-Compliant Payments ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation ### How to Take Payments on Phonely AI Voice Agents: PCI-Compliant Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [How to take PCI-compliant payments on Retell AI voice agents](/guides/retell-ai-payments/) - [Book a call](/contact/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [GuideHow to Take Payments on Retell AI Voice Agents: PCI-Compliant Payments→](/guides/retell-ai-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideAI Voice Agents and Payments: How PolyAI Captures Payments in Conversation→](/guides/ai-voice-agents-payments/) - [GuideHow to Take Payments on Phonely AI Voice Agents: PCI-Compliant Payments→](/guides/phonely-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/card-processing-fees-and-rates-for-uk-merchants/ --- # Card Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026) | Shuttle > Understand UK card processing fees -- interchange, scheme fees, acquirer markups, and total costs. # Card Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026) By Nick Dunse, May 15, 2024 Understand UK card processing fees -- interchange, scheme fees, acquirer markups, and total costs. Card processing fees are the cost of accepting card payments. Every time a customer pays by debit or credit card, the merchant pays a percentage of the transaction plus a fixed fee. Understanding how these fees work -- and where the money goes -- is the first step to managing your payment costs. This guide breaks down UK card processing fees, explains the different pricing models, compares provider rates, and covers practical ways to reduce costs. ## How Card Processing Fees Work Every card transaction involves four parties, each taking a cut: - Interchange fee -- Paid to the card-issuing bank (the customer's bank). Set by Visa and Mastercard. Typically 0.2-0.3% for UK consumer debit cards, 0.3% for credit cards (capped by EU regulation). International and corporate cards are higher -- up to 1.5%+. - Scheme fee -- Paid to the card network (Visa, Mastercard, Amex). Typically 0.02-0.15% plus a small per-transaction fee. These are non-negotiable. - Acquirer markup -- Paid to your payment provider (the acquirer or PSP). This is the negotiable portion -- and where providers differ significantly. - Gateway fee -- Some providers charge a separate per-transaction fee for the payment gateway technology. Others bundle it in. Total cost = Interchange + Scheme fees + Acquirer markup (+ Gateway fee if separate) ## UK Card Processing Fees by Provider Pricing Model International Per-Transaction Fee 1.4% + 20p 2.5% + 20p IC++ or flat From 0.75% From 0.95% IC + 0.10-0.25€ 1.75% (in-person) 2.5% (online) 2.9% + 30p 3.4% + 30p IC++ = Interchange-plus-plus (interchange + scheme fee + provider markup). Rates as of February 2026. ## Flat Rate vs Interchange-Plus: Which Is Cheaper? For UK businesses, the answer depends on volume and card mix. ### Flat Rate (Stripe, Square, SumUp) - Simple: same rate regardless of card type - Predictable: easy to forecast costs - More expensive at scale: you overpay on cheap transactions (UK debit) and the provider absorbs the cost on expensive ones (international corporate) ### Interchange-Plus (Adyen, Worldpay, Checkout.com) - Transparent: you see exactly what the interchange cost is and what the provider charges on top - Cheaper at volume: UK consumer debit interchange is ~0.2%, so total cost can be 0.3-0.5% vs 1.4% on flat rate - Variable: costs fluctuate based on card mix, which makes budgeting slightly harder Rule of thumb: Below £30,000/month -- flat rate is simpler and the cost difference is small. Above £50,000/month -- interchange-plus typically saves 0.5-1.0% per transaction, which compounds to thousands per year. ## Hidden Costs to Watch For - Chargeback fees -- £15-25 per chargeback dispute, regardless of outcome - Refund fees -- Some providers keep the processing fee on refunded transactions - Currency conversion -- 1-2.5% markup on cross-border or multi-currency transactions - PCI compliance fees -- Some traditional providers charge £5-15/month for PCI self-assessment tools - Monthly minimums -- Some providers require a minimum processing volume or charge a shortfall fee - Terminal rental -- In-person card machines: £15-30/month depending on model ## How to Reduce Card Processing Fees ### 1. Negotiate on volume If you process over £50,000/month, ask for interchange-plus pricing. The acquirer markup is negotiable -- especially if you can demonstrate consistent volume and low chargeback rates. ### 2. Encourage debit over credit UK consumer debit interchange is capped at 0.2% vs 0.3% for credit. Debit cards save you money on every transaction. ### 3. Use local acquiring Cross-border transactions (customer's card issued in a different country to the acquirer) attract higher interchange. Using a payment provider with local acquiring in your key markets reduces this. ### 4. Reduce chargebacks Beyond the direct fee, high chargeback rates can trigger penalty programmes from card networks -- increasing your base processing costs. ### 5. Review annually Card scheme fees change twice a year (April and October). Provider markups can drift. An annual review of your effective rate (total fees ÷ total volume) ensures you're not overpaying. ## Card Processing Fees for Platforms If you're a software platform -- processing payments on behalf of your merchants -- the fee structure is more complex. You're managing costs across multiple merchants, potentially multiple PSPs, and potentially multiple countries. Platforms typically need: - Interchange-plus pricing (flat rates eat into margin when you're earning revenue share) - Multi-PSP support (different merchants may need different providers) - Transparent fee passthrough to merchants For platforms, the bigger cost isn't the processing fee -- it's the integration and maintenance cost of supporting payment infrastructure. See How to Get Payments Off Your Product Roadmap for the full analysis. ## FAQ ### What is the average card processing fee in the UK? For UK consumer debit cards: 0.3-1.4% depending on provider and pricing model. For credit cards: 0.5-1.4%. International cards: 1.5-3.0%. ### Why are my card fees higher than advertised? Common reasons: international cards in your mix (higher interchange), corporate cards (uncapped interchange), chargebacks, or currency conversion fees. Ask your provider for a breakdown by card type. ### Can I pass processing fees to customers? In the UK, surcharging consumers for card payments has been banned since January 2018. However, you can offer discounts for cash or bank transfer, or include processing costs in your pricing. ### What's the cheapest way to accept card payments? For low volume: Square or SumUp (no monthly fees, simple flat rate). For high volume: interchange-plus pricing from Worldpay, Adyen, or Checkout.com. Need help choosing a payment provider? Compare payment providers or browse all supported gateways. ## Related Reading Explore More ### Credit Card Processing Fees Explained: What You Actually Pay ### How to Reduce Payment Processing Fees Without Switching Providers ### HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### How to Connect CardConnect to Twilio for Voice & IVR Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Compare payment providers](/merchants/payment-services/) - [browse all supported gateways](/payment-providers/) - [GuideCredit Card Processing Fees Explained: What You Actually Pay→](/guides/credit-card-processing-fees/) - [GuideHow to Reduce Payment Processing Fees Without Switching Providers→](/guides/reduce-payment-processing-fees/) - [GuideHubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)→](/guides/hubspot-commerce-hub-transaction-fees/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideHow to Connect CardConnect to Twilio for Voice & IVR Payments→](/guides/cardconnect-twilio-integration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/chargeback-protection-market-review/ --- # Chargeback protection market review | Shuttle > A review of the chargeback protection market in 2026. Compares Ethoca, Verifi, Chargebacks911, and other solutions for merchants looking to reduce... # Chargeback protection market review By Nick Dunse, May 24, 2022 A review of the chargeback protection market in 2026. Compares Ethoca, Verifi, Chargebacks911, and other solutions for merchants looking to reduce... Talk to us Make enabling payments for your platform and merchant users easy. I. Introduction Chargeback protection refers to measures taken by merchants to reduce the risk of customer disputes and chargebacks. In today's digital age, online transactions have become increasingly common, making it essential for businesses to implement effective chargeback protection strategies. One such provider is Ethoca, which offers comprehensive solutions for businesses looking to protect themselves against chargebacks. In this article, we will explore how Ethoca helps businesses prevent chargebacks and what sets them apart from other chargeback protection providers. II. What is chargeback protection? Chargeback protection refers to measures taken by businesses to prevent or mitigate the risk of customer disputes, chargebacks, and refunds. It involves identifying potential issues before they escalate into full-blown chargebacks, implementing effective strategies to address them, and maintaining clear communication with customers throughout the process. By protecting themselves against these costly disputes, businesses can improve their bottom line and maintain customer satisfaction. In this article, we'll explore how Ethoca helps businesses achieve chargeback protection success. III. How does Ethoca help businesses protect themselves from chargebacks? Ethoca offers a comprehensive suite of chargeback management services designed to help businesses protect themselves against fraudulent transactions and chargebacks. These services include monitoring and analysis of transaction data, dispute resolution assistance, and ongoing education and support to help businesses stay up-to-date on industry trends and best practices. By partnering with Ethoca, businesses can reduce their risk of chargebacks and improve their overall customer satisfaction. Additionally, Ethoca's transparent pricing model and dedicated account management team provide businesses with the peace of mind they need to focus on growing their business without worrying about costly disputes or regulatory compliance issues. IV. Benefits of using Ethoca's chargeback management services Ethoca's chargeback management services offer several benefits to businesses, including: 1. Reduced fraud risk: By providing real-time monitoring of transactions, Ethoca helps businesses identify potential fraud quickly and take action before it becomes a problem. This reduces the risk of chargebacks resulting from fraudulent activity. 2. Improved customer satisfaction: When customers experience issues with their transactions, they may turn to their credit card company for assistance. With Ethoca's chargeback management services, businesses can quickly resolve these issues and improve customer satisfaction. 3. Cost savings: Chargebacks can be costly for businesses, as they often involve disputes between merchants and credit card companies. By outsourcing chargeback management to Ethoca, businesses can save time and money on internal resources and legal fees associated with handling chargebacks in-house. 4. Increased revenue: Effective chargeback management can help businesses reduce the number of chargebacks they receive, which can lead to increased revenue. By minimizing the impact of chargebacks on their bottom line, businesses can focus on growing their business and increasing profits. Overall, Ethoca's chargeback management services offer significant benefits to businesses looking to protect themselves against chargebacks and improve their overall financial performance. V. How Ethoca compares to other chargeback protection providers When it comes to chargeback protection, there are many providers in the market offering various solutions. However, not all providers are created equal, and it's important for businesses to carefully consider their options before making a decision. In this section, we'll compare how Ethoca's chargeback management services stack up against other providers in the market. Firstly, let's look at the cost of service. While some providers offer competitive pricing, others can be expensive and may not provide as much value for money. With Ethoca, our pricing is transparent and affordable, with no hidden fees or charges. We believe that every business deserves access to effective chargeback protection without breaking the bank. Secondly, let's consider the level of support provided. Some providers may have excellent customer service, but lack the technical expertise needed to effectively manage chargebacks. At Ethoca, we have a team of experts who specialize in chargeback management and can provide customized solutions tailored to each client's unique needs. Our clients receive personalized attention and ongoing support throughout the process, ensuring they have the resources they need to succeed. Finally, let's talk about the level of technology employed. In today's fast-paced world, businesses need access to cutting-edge tools and technologies to stay ahead of the competition. That's why Ethoca invests heavily in our proprietary software platform, which uses advanced algorithms and machine learning to identify and prevent fraudulent transactions. Our platform is designed to be intuitive and user-friendly, so even non-technical staff can use it easily. In conclusion, when it comes to choosing a chargeback protection provider, it's important to consider the costs, level of support, and level of technology offered. By comparing Ethoca's services to those of other providers in the market, we believe that businesses will see the value in partnering with us. Contact us today to learn more about how we can help protect your business from costly chargebacks. VI. Case study: Successful implementation of Ethoca's chargeback management services One of our clients, a popular online retailer, was facing a significant number of chargebacks due to fraudulent transactions. They turned to Ethoca for help and saw immediate results. With Ethoca's chargeback management services, they were able to reduce their chargeback rate by over 50%. This not only saved them money, but it also helped improve their reputation as a trusted online retailer. By partnering with Ethoca, this client was able to focus on growing their business without worrying about the threat of chargebacks. If you're looking for a reliable solution to protect your business against chargebacks, look no further than Ethoca. Contact us today to learn more about how we can help you. VII. Conclusion In conclusion, chargeback protection is crucial for businesses in the e-commerce industry to safeguard their revenue against fraudulent transactions. While there are many chargeback protection providers available, not all offer the same level of service or benefits. Ethoca stands out as a leading provider with its advanced technology, personalized support, and proven track record of success. By partnering with Ethoca, businesses can rest assured that they have the best possible chance of protecting themselves from costly chargebacks while improving customer satisfaction. Ultimately, choosing the right chargeback protection provider is essential for any business looking to stay competitive in today's fast-paced marketplace. ## Related Reading Explore More ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/choosing-the-right-payment-gateway-for-your-event-software-a-comprehensive-guide/ --- # Event Payment Gateway: How to Choose the Right One | Shuttle > How to choose an event payment gateway for ticketing, refunds, split payments and high-volume processing. Compare top options and integration approaches. # Event Payment Gateway: How to Choose the Right One By Nick Dunse, June 11, 2024 How to choose an event payment gateway for ticketing, refunds, split payments and high-volume processing. Compare top options and integration approaches. Talk to us Make enabling payments for your platform and merchant users easy. Event software platforms face payment challenges that most businesses never encounter. Thousands of transactions hit within minutes of a ticket drop. Attendees demand refunds when acts cancel. Revenue needs splitting between promoters, venues, and artists -- often across multiple currencies. A generic payment gateway simply cannot handle this. Choosing the right event payment gateway is one of the most consequential infrastructure decisions an event management platform can make. The wrong choice leads to failed transactions during peak demand, compliance headaches, and revenue leakage. The right choice turns payments into a competitive advantage. This guide walks through the unique payment challenges in event software, the features that matter most, how the leading gateways compare, and how to integrate payments without becoming a payment company yourself. ## Why Event Software Has Unique Payment Challenges Event platforms are not like standard e-commerce. The payment patterns are fundamentally different, and any gateway you choose needs to handle these realities: - High-volume spikes: When tickets go on sale for a popular event, you can see thousands of concurrent transactions in seconds. Your gateway needs to handle burst capacity without dropping payments or timing out. - Complex refund workflows: Events get cancelled, rescheduled, or moved to different venues. You need partial refunds, full refunds, credit-based refunds, and the ability to process thousands of them simultaneously when a headliner pulls out. - Split payments and marketplace flows: Revenue from a single ticket purchase often needs to be distributed between the event organiser, the venue, the platform, payment processing fees, and sometimes multiple artists or sponsors. This requires proper fund flow management. - Multi-currency requirements: International festivals, conferences, and touring events sell tickets across borders. Your gateway must support local payment methods and currencies to maximise conversion rates in each market. - Time-sensitive authorisations: Pre-sale windows, early-bird pricing, and reserved seating all require holds, delayed captures, and expiring authorisations that standard checkout flows do not support well. These challenges explain why many event platforms eventually move beyond basic payment integrations toward embedded payments -- owning the payment experience rather than redirecting users to a third-party checkout. ## Key Features of an Event Payment Gateway Not every payment gateway is built to serve event platforms. When evaluating options, prioritise these capabilities: High-throughput processing. The gateway must handle thousands of concurrent API calls without degradation. Ask vendors about their transactions-per-second limits and whether they offer dedicated capacity for burst events. Flexible fund flows. Look for native support for split payments, delayed disbursements, and multi-party payouts. Stripe Connect, Adyen for Platforms, and similar marketplace-oriented products handle this natively. Simpler gateways will force you to build reconciliation logic yourself. Robust refund APIs. You need programmatic bulk refunds, partial refunds, and refund-to-credit capabilities. The gateway should also support refunding to the original payment method automatically, even weeks after the initial charge. Multi-currency and local payment methods. Supporting cards alone is no longer sufficient. iDEAL in the Netherlands, Bancontact in Belgium, PIX in Brazil -- local methods can increase conversion by 20-30% in their home markets. Pre-authorisation and delayed capture. For reserved seating and deposit-based bookings, you need to authorise a card and capture the funds later. The gateway should support extended auth windows beyond the standard 7-day period. Webhook reliability. Payment status updates drive ticket fulfilment. If a webhook is missed or delayed, attendees do not receive their tickets. Look for guaranteed delivery, retry logic, and webhook logs for debugging. ## Top Payment Gateways for Event Platforms Four gateways dominate the event software space, each with distinct strengths: Stripe is the most popular choice for event platforms, particularly those with marketplace or multi-vendor models. Stripe Connect provides native split payment support, and the API is developer-friendly with excellent documentation. Stripe handles high-volume bursts well, supports 135+ currencies, and offers pre-built components like Stripe Elements for embedding checkout forms. The main limitation is pricing transparency at scale -- negotiated rates require significant volume. Adyen is the enterprise choice for large-scale event platforms and ticketing companies. Adyen for Platforms offers sophisticated fund management, supports 250+ payment methods across 70+ countries, and provides granular risk management. Adyen's single-platform architecture means all payment methods run through one integration. The trade-off is a higher barrier to entry -- Adyen targets higher-volume merchants and the integration is more complex. Square works well for event platforms that combine online ticket sales with in-person payments at the venue. Square's unified commerce approach means the same merchant account handles e-commerce and point-of-sale, which simplifies reconciliation for events with on-site merchandise, food, or VIP upgrades. Square's limitation is weaker international coverage compared to Stripe or Adyen. PayPal remains relevant for event platforms selling to consumers, particularly in markets where PayPal wallet penetration is high. PayPal Commerce Platform supports marketplace splits, and buyer protection gives consumers confidence when purchasing tickets from lesser-known event organisers. However, PayPal's hold policies and dispute resolution process can create cash flow challenges for event businesses. Many mature event platforms use multiple gateways -- routing transactions based on geography, payment method, or transaction size to optimise conversion rates and reduce costs. ## Integrating Payments Into Event Platforms There are three common approaches to adding payment processing to event management software, each with different trade-offs in control, complexity, and revenue potential. Redirect to hosted checkout. The simplest approach: send buyers to the gateway's hosted payment page (like Stripe Checkout or PayPal's checkout flow) and receive a webhook when payment completes. This is fast to implement and offloads most of the PCI burden, but you lose control over the user experience and cannot customise the checkout flow. Embedded payment forms. Embed the gateway's payment fields directly into your ticket purchase flow using drop-in components like Stripe Elements or Adyen's Drop-in. The buyer never leaves your site, giving you full control over the checkout experience while the gateway handles sensitive card data. This is the sweet spot for most event platforms. Full embedded payments. The most advanced approach: become a payment facilitator or use an embedded payments infrastructure provider to onboard event organisers as sub-merchants, control fund flows, and earn revenue on every transaction. This turns payments from a cost centre into a profit centre but requires significant investment in compliance and operations. For event platforms considering the embedded approach, the key question is whether to build the payment infrastructure in-house or partner with a provider like Shuttle that handles the PSP integrations, compliance, and fund management on your behalf. ## PCI Compliance for Event Payment Processing Any platform that handles, processes, or transmits card data must comply with the Payment Card Industry Data Security Standard (PCI DSS). For event software, PCI compliance is non-negotiable -- the volume of transactions and the consumer-facing nature of ticket sales make event platforms a target for fraud. The easiest path to PCI compliance is to never touch card data directly. Using tokenisation through Stripe Elements, Adyen's secured fields, or similar tools means sensitive card numbers never reach your servers. This reduces your PCI scope to SAQ A or SAQ A-EP, which are significantly less burdensome than full SAQ D compliance. Key compliance considerations for event platforms: - Use tokenised payment forms to keep card data off your servers - Implement 3D Secure (3DS2) for Strong Customer Authentication in European markets - Store tokens rather than card numbers for recurring or subscription-based event passes - Ensure your mobile apps and kiosk systems also use tokenised integrations - Document your compliance annually and keep your SAQ up to date ## Using Payment Links for Event Payments Not every event payment happens through a website checkout. Payment links offer a flexible alternative for scenarios where a traditional checkout flow does not fit: - VIP packages and corporate bookings: Send a branded payment link via email for high-value, custom-quoted event packages that do not have a standard price on your website. - Sponsor and exhibitor payments: Collect booth fees, sponsorship deposits, and add-on charges through a simple link rather than building a full invoicing system. - On-the-day payments: Share payment links via SMS or QR codes for walk-up registrations, merchandise, or food and beverage orders at the event itself. - Deposit and instalment collection: For high-value events like weddings or corporate retreats, send scheduled payment links for deposits and balance payments. Payment links are particularly valuable for event platforms that serve organisers who are not technically sophisticated. Rather than requiring API integration, you can provide organisers with a simple tool to generate and share payment links for their events. ## How to Evaluate an Event Payment Gateway When comparing gateways for your event platform, work through these evaluation criteria systematically: Transaction volume pricing. Event businesses have lumpy revenue -- high volume during on-sale periods and quiet periods between events. Negotiate pricing based on annual volume rather than monthly minimums, and understand how the gateway handles chargebacks and refund fees. Geographic coverage. Map your current and target markets against the gateway's supported countries and payment methods. If you run events in Europe, can the gateway process SEPA direct debits? If you are expanding into Latin America, does it support local acquiring? Settlement timing. Cash flow is critical for event businesses. Understand when funds become available -- some gateways settle in 2 days, others hold funds for 7-14 days, especially for new accounts or high-value transactions. Rolling reserves can lock up a significant portion of your revenue. Fraud and risk management. Events are a common target for card testing and fraudulent purchases. Evaluate the gateway's built-in fraud detection (like Stripe Radar or Adyen's risk engine), and whether you can customise risk rules for event-specific patterns like bulk ticket purchases. API quality and support. Your engineering team will live with this integration. Evaluate the API documentation, SDK quality, sandbox environment, and the responsiveness of developer support. A gateway with a superior API can save weeks of development time over the life of the integration. ## Why Event Platforms Are Embedding Payments The trend in event software is clear: platforms are moving from simply integrating a payment gateway to fully embedding payments into their product. This shift is driven by three factors. First, revenue. When you embed payments, you earn a margin on every transaction your platform processes. For an event platform processing millions in ticket sales, even a small per-transaction margin adds up to significant recurring revenue. This is why companies like Eventbrite, Universe, and Dice have all invested heavily in owning their payment stack. Second, control. Owning the payment experience means you control the checkout flow, the refund process, and the fund distribution. You can build features like instant payouts to event organisers, automated refund policies, and real-time revenue dashboards -- none of which are possible when you simply redirect to a gateway's hosted page. Third, stickiness. When event organisers rely on your platform for payment processing, onboarding, and fund settlement, switching costs increase dramatically. Payments become a retention mechanism, not just a feature. The challenge is that building embedded payment infrastructure from scratch requires deep expertise in payment regulations, PCI compliance, multi-PSP routing, and fund management. This is where infrastructure partners come in -- letting event platforms embed payments without building the underlying payment plumbing. ## Frequently Asked Questions ### What is the best payment gateway for event ticketing? There is no single best gateway -- it depends on your scale and geography. Stripe is the strongest all-round choice for most event platforms thanks to Stripe Connect's split payment support and developer-friendly APIs. Adyen is better suited for enterprise ticketing companies processing high volumes across many countries. Square works well if you combine online and in-person event payments. ### How do event platforms handle refunds at scale? Mature event platforms automate refund processing through their payment gateway's API. When an event is cancelled, the platform triggers bulk refunds programmatically -- either full refunds to the original payment method, partial refunds for rescheduled events, or credits applied to the customer's account. The key is choosing a gateway with a robust refund API that supports batch operations and provides real-time status tracking. ### Do event platforms need PCI compliance? Yes. Any platform that accepts card payments must be PCI compliant. However, the level of compliance required depends on how you handle card data. If you use tokenised payment forms (like Stripe Elements or Adyen Drop-in), sensitive card data never touches your servers, which significantly reduces your compliance burden. Most event platforms achieve SAQ A or SAQ A-EP compliance through tokenisation. Read our PCI compliance guide for a full breakdown. ### Can event software platforms monetise payments? Absolutely. By embedding payments directly into the platform rather than redirecting to a third-party gateway, event software companies can earn a margin on every transaction. This typically involves becoming a payment facilitator or working with an embedded payments provider that handles the regulatory and compliance requirements. Platforms like Shuttle enable event software companies to embed payments and generate payment revenue without building payment infrastructure from scratch. ## Related Reading Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [embedded payments](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [embedded payments infrastructure provider](/platforms/) - [Shuttle](/discovery/) - [PCI compliance](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [embedded payment infrastructure](/guides/what-is-embedded-payments/) - [PCI compliance guide](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [embed payments](/platforms/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/country/united-kingdom/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/do-i-need-a-full-ar-platform-or-just-smarter-payment-links/ --- # Do I Need a Full AR Platform or Just Smarter Payment Links? | Shuttle > If you're trying to modernise your AR process, the choices can feel overwhelming. # Do I Need a Full AR Platform or Just Smarter Payment Links? By Nick Dunse, July 17, 2025 If you're trying to modernise your AR process, the choices can feel overwhelming. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. Should you implement a full Accounts Receivable platform with dashboards, workflows, portals, and automation? Or can you solve 80% of the problem with something simpler -- like smarter payment links? The answer depends on your goals, your systems, and just how "broken" your current AR really is. In this article, we'll break down when you need a full platform -- and when payment links alone can give you the automation, visibility, and speed you're looking for. 🏗 What Is a Full AR Platform? Let's start with what a full AR platform usually includes: Invoice creation and delivery Customer payment portals Automated reminders and escalation workflows Payment method integrations (card, ACH, Open Banking, etc.) Reconciliation and reporting dashboards Credit scoring, risk management, and dispute handling (in some cases) These systems often position themselves as all-in-one solutions. And they are -- but they come with baggage: High implementation cost IT involvement and integration work Complex user onboarding Change management across teams If you're a 500+ person business with multi-entity invoicing, high volumes, and bespoke approval flows, they might be a great fit. But if you're like most mid-sized businesses, that's overkill. 🔗 What Are Smarter Payment Links? Smarter payment links give you many of the same benefits -- without the overhead. Instead of replacing your whole AR process, they enhance what you already do. You send an invoice (from Xero, QuickBooks, NetSuite, etc.), and Shuttle turns that into a branded, trackable payment link that: Offers multiple payment methods (card, ACH, Open Banking, Pay by Bank) Is delivered via email, SMS, WhatsApp or CRM Tracks views, clicks, and payments in real-time Connects to your existing tools (Zapier, Make.com, Salesforce, etc.) Reconciles automatically You don't need to install a new system. You don't need to migrate data. You just need to start sending links. 🤔 So, Which One Do You Need? Here's a breakdown to help you decide: If You... | You Probably Need... Send 50-1000 invoices/month | Smart Payment Links Use Xero, QuickBooks, NetSuite, Sage | Smart Payment Links Have 1-5 people in finance/AR | Smart Payment Links Want to reduce chasing and speed up payment | Smart Payment Links Need dashboards, approval flows, credit risk | Full AR Platform Manage large enterprise contracts | Full AR Platform Have complex billing rules (usage, subscriptions) | Depends -- could need hybrid Need a solution live in under a week | Smart Payment Links 💸 The Cost Difference Option | Cost | Setup Time | Maintenance Full AR Platform | High (£10k-50k+/year) | 2-6 months | Ongoing support, admin Smart Payment Links (e.g. Shuttle) | Low | < 1 week | Minimal If your AR team is spending time chasing payments, reconciling references, and fielding "how do I pay this?" emails -- you don't need a full suite. You just need better delivery and a smoother customer experience. 🧠 Think Function, Not Features You're not trying to win a software award. You're trying to: Get paid faster Spend less time chasing Improve visibility Give your customers a better experience If you can do that without disrupting your team or your systems -- that's a win. 🚀 Wrapping Up Full AR platforms are powerful, but they're not always the answer.For most mid-sized businesses, the real gains come from solving the last mile of payment -- how the invoice gets delivered, how easy it is to pay, and how quickly you know what's been paid. That's where smarter payment links shine. Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Get Payment Links today](/platforms/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/dropping-some-knowledge-on-buy-now-pay-later/ --- # Dropping some knowledge on Buy Now Pay Later | Shuttle > Everything merchants need to know about Buy Now Pay Later -- how BNPL works, top providers, conversion impact, and integration options. # Dropping some knowledge on Buy Now Pay Later By Nick Dunse, January 19, 2021 Everything merchants need to know about Buy Now Pay Later -- how BNPL works, top providers, conversion impact, and integration options. BNPL - The highly publicised and often criticised space is still confusing for most... Klarna, might be biggest devaluation ever in the market, $46bn to $6bn! Does everyone get tarnished with the same brush and is all BNPL a one size fits all industry with everyone competing for the same pie?.. 🤔 Firstly, the playerz are going after very different markets. B2C - Klarna, Afterpay, Affirm to note. This is an (currently) unregulated space where a merchant can sign up and get paid quickly whilst the BNPL provider takes on the debt relationship with the end-customer. Most B2C BNPL providers are only lending to end customers in the 'prime' segment, meaning they're pretty risk averse and generally operating in the retail space. Although we are seeing them targeting other verticals now. A lot of the providers tend to operate in limited geographies, although in the B2C space, they may not technically, be limited. It's still open for debate whether these prime services actually do increase checkout conversion in all scenarios but we've been impressed with PayTomorrow a service that includes lending to US folk who, for whatever reason, may not be approved by the prime lenders. PayTomorrow cover the spectrum of customers and therefore conversion at checkout is far more likely, I talk to Chris Talevi in the video where you can find out more. Then you've got B2B BNPL, which has actually been around in one form or another for many years, think invoice financing or even factoring. The B2B space plays by stricter rules than its sister. And as I mentioned there are different flavours and the finance can be structured differently, so it's worth looking into how each party works and what you really need. Some have a relationship with you and some lend money to your customers who need to pay you. It seems like there are new entrants to this market every week... Any questions? ## Related Reading Explore More ### Pay Now Button for Invoices: The B2B Guide ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Build vs Buy Payment Infrastructure: A Decision Framework for Platforms ### What Is Twilio Pay? How It Works, Pricing, and Connectors (2026) ### Twilio Pay Connectors: How to Connect Any Payment Provider to Twilio ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PayTomorrow](https://www.linkedin.com/in/ACoAACvX-XwBP6VxxmZ7srtO_1IR9xPteOCGVkk) - [Chris Talevi](https://www.linkedin.com/in/ACoAABDJhEsBnkzhY-95Et96S85sxMuh_0jedTE) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideBuild vs Buy Payment Infrastructure: A Decision Framework for Platforms→](/guides/build-vs-buy-payment-infrastructure/) - [GuideWhat Is Twilio Pay? How It Works, Pricing, and Connectors (2026)→](/guides/what-is-twilio-pay/) - [GuideTwilio Pay Connectors: How to Connect Any Payment Provider to Twilio→](/guides/twilio-pay-connectors/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/ --- # DTMF vs Payment Links: Which is More Secure for Phone Payments? | Shuttle > DTMF capture vs payment links -- when each makes sense, how each handles PCI, and how to use both together in a contact centre. # DTMF vs Payment Links: Which is More Secure for Phone Payments? By Nick Dunse, December 26, 2025 DTMF capture vs payment links -- when each makes sense, how each handles PCI, and how to use both together in a contact centre. Talk to us Make enabling payments for your platform and merchant users easy. If your business takes payments over the phone, you have two practical options: capture card details during the call using DTMF tones, or send the customer a payment link they complete on their own device. Both approaches can be made PCI compliant. Both have trade-offs. This article compares the two approaches side by side -- security, conversion, integration cost, and customer experience. For the canonical explainer on how DTMF capture works (clamping, masking, suppression, and PCI scope reduction), see our dedicated guide to DTMF payments. ## What Are Payment Links? A payment link is a URL that takes the customer to a hosted, PCI-compliant checkout page. The agent generates a link during or after the call and sends it to the customer via SMS, email, or messaging. The customer opens the link on their phone or computer, enters their card details on a secure form, and completes the payment independently. Payment links bypass the phone channel entirely. Card data is entered into a web form served from a PCI-certified environment -- the contact centre never touches it. This makes payment links inherently PCI compliant from the contact centre's perspective, with no need for DTMF infrastructure. Read more about the approach in our guide to secure payment links for card authorisation. ## DTMF Payments vs Payment Links: Security Comparison Both DTMF payments and payment links can achieve full PCI DSS compliance when implemented correctly. The security differences lie in the attack surface, the infrastructure required, and where the risk sits. DTMF payment security: - Card data travels through the telephony layer but is intercepted before reaching the agent or recordings. Security depends on the quality of DTMF suppression and clamping. - The payment environment must be PCI DSS Level 1 certified and the integration with the telephony platform must be correctly configured. - Potential vulnerabilities include incomplete tone suppression, misconfigured audio routing, and legacy telephony systems that pass tones before the payment layer intercepts them. - When implemented well, DTMF is highly secure -- the card data exists only momentarily in the certified payment environment and is never stored. Payment link security: - Card data never enters the voice channel. The customer enters details on a TLS-encrypted web form hosted by the payment provider. - The contact centre is completely de-scoped -- there is no telephony integration to misconfigure. - Potential vulnerabilities include phishing (customers receiving fraudulent links), link interception if sent over unencrypted channels, and link expiry management. - Payment links use the same security standards as e-commerce checkout -- well-understood and widely audited. The bottom line: payment links have a smaller attack surface because card data stays in the web channel. DTMF payments add telephony as an extra layer to secure. However, DTMF with proper suppression and clamping is considered equally secure in practice and is the industry standard for PCI-compliant phone payments. ## Pros and Cons of Each Approach DTMF payment advantages: - Payment is completed during the call -- no drop-off from sending the customer elsewhere. - Higher conversion rates for phone-first customers, especially in collections and insurance where the call is the primary interaction. - Works for all callers regardless of device type or internet access -- the customer only needs a phone keypad. - Agent can guide the customer through each step in real time and confirm the result immediately. DTMF payment disadvantages: - Requires telephony integration -- the payment system must sit in the audio path, which adds implementation complexity. - Some customers find entering 16+ digits on a keypad awkward, especially on mobile devices. - Miskeyed digits require re-entry, which can extend call duration. - Ongoing maintenance of DTMF suppression and clamping configurations as telephony infrastructure changes. Payment link advantages: - Simpler to implement -- no telephony integration required. Generate a URL and send it. - Supports saved cards, digital wallets (Apple Pay, Google Pay), and other modern payment methods that DTMF cannot. - Works across channels -- the same link can be sent via SMS, email, WhatsApp, or in-app messaging. - Completely de-scopes the contact centre from PCI with zero telephony configuration. Payment link disadvantages: - Breaks the call flow -- the customer must switch to another device or channel to complete payment, which increases abandonment. - Requires the customer to have a smartphone or internet access. Not all demographics have this, particularly in collections and public sector scenarios. - Payment may not be completed during the call -- the agent cannot always confirm the outcome in real time. - Customers may be suspicious of links received during calls, reducing trust and completion rates. ## When to Use DTMF Payments DTMF payments are the right choice when the payment must happen during the phone call and breaking out to another channel would hurt completion rates or customer experience. Common scenarios include: - Debt collection calls -- the debtor is on the line and ready to pay. Sending a link and hoping they complete it later significantly reduces recovery rates. See our guide on AI voice payments for debt collection. - Insurance premium collections -- customers calling to renew or settle balances expect to complete the transaction in one interaction. - IVR self-service payments -- automated phone systems where the caller navigates menus and enters card details without speaking to an agent at all. DTMF is the only input method available. - High-volume call centres -- where average handle time (AHT) matters and completing payment during the call avoids follow-up contacts. - Callers without internet access -- elderly customers, rural areas, or any situation where the caller cannot easily access a web browser. ## When to Use Payment Links Payment links work best when the payment does not need to happen in real time during the call, or when you want to offer a richer checkout experience. Common scenarios include: - Post-call payments -- the agent sends a quote, invoice, or payment request after the call and the customer pays at their convenience. - Multi-channel collections -- sending payment links via SMS or email as part of an outreach sequence. The link can be sent proactively before the customer even calls. - Complex transactions -- where the customer needs to review an itemised total, select payment options (instalments, partial payment), or use a digital wallet. - Chat and messaging channels -- agents communicating via live chat, WhatsApp, or social messaging can embed a payment link directly in the conversation. - Businesses without telephony infrastructure -- if you do not have a cloud-based telephony platform that supports DTMF integration, payment links are the faster path to secure phone payments. ## The Hybrid Approach: DTMF and Payment Links Together The strongest payment operations do not choose one method over the other -- they offer both. A hybrid approach gives agents the flexibility to match the payment method to the situation: - Customer is on the phone and ready to pay right now? Use DTMF to capture the card during the call. - Customer prefers to pay later or wants to use Apple Pay? Send a payment link via SMS. - Customer is struggling with the keypad or keeps miskeying digits? Switch to a payment link mid-call. - IVR self-service system encounters an error? Fall back to a payment link sent to the caller's mobile number. This is exactly the model Shuttle supports. As a payment layer for platforms, Shuttle provides both Voice Checkout (DTMF payments via Twilio) and Payment Links through a single integration. Platforms and contact centres get PCI DSS Level 1 compliance across both channels without building or maintaining the payment infrastructure themselves. The payment method becomes a routing decision, not an architecture decision. One integration, two channels, full PCI compliance. ## Frequently Asked Questions ### Are payment links more secure than DTMF? Payment links have a smaller attack surface because card data never enters the voice channel. However, properly implemented DTMF with suppression and clamping is equally secure and is the industry standard for phone payments. The choice is usually driven by customer experience rather than security. ### Can I use both DTMF and payment links in the same contact centre? Yes. A hybrid approach is increasingly common for organisations handling a mix of inbound and outbound calls. Shuttle provides both DTMF-based Voice Checkout and Payment Links through a single integration. Book a discovery call to see how it works. ## Related Reading Explore More ### DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Yellow.ai Payments: In-Call Capture vs Payment Links ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### How to Take Payments on Vonage Contact Centre: Secure Payment Processing ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [guide to DTMF payments](/guides/dtmf-payments/) - [secure payment links for card authorisation](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [AI voice payments for debt collection](/guides/ai-voice-payments-debt-collection/) - [payment layer for platforms](/platforms/) - [Book a discovery call](/discovery/) - [GuideDTMF Payment Processing: PCI Compliant Capture, Clamping & Masking→](/guides/dtmf-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideYellow.ai Payments: In-Call Capture vs Payment Links→](/guides/yellow-ai-payments/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHow to Take Payments on Vonage Contact Centre: Secure Payment Processing→](/guides/vonage-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/dunning-letter-templates/ --- # Dunning Letter Templates: From Friendly Reminder to Final Notice | Shuttle > 4 dunning letter templates for posted correspondence -- friendly reminder to Letter Before Action. Includes QR code placement for instant payment. # Dunning Letter Templates: From Friendly Reminder to Final Notice By Shuttle Team, March 11, 2026 4 dunning letter templates for posted correspondence -- friendly reminder to Letter Before Action. Includes QR code placement for instant payment. Talk to us Make enabling payments for your platform and merchant users easy. ## What Is a Dunning Letter? A dunning letter is a formal written notice sent to a debtor requesting payment of an overdue invoice. The term comes from the verb "to dun" -- to make persistent demands for payment. In practice, dunning is a sequence of letters that escalate in formality and urgency. The first is polite. The last is a legal precursor. Most businesses need three to five letters before either receiving payment or deciding to pursue legal action. Dunning letters are distinct from payment reminder emails. They're more formal, typically sent on company letterhead (by post or as a PDF attachment), and carry more weight with debtors -- especially in industries where formal correspondence is expected. Every template below includes a payment link and QR code placement. A payment link turns a formal demand into an instant payment opportunity -- the debtor reads the letter and can pay from their phone in 60 seconds by scanning the QR code. ## The Dunning Sequence: When to Send Each Letter 7-10 days overdue Friendly reminder Prompt payment, assume oversight 21 days overdue Establish the debt is being actively pursued 30-35 days overdue Formal with legal reference Warn of statutory interest and consequences 45+ days overdue Pre-legal (Letter Before Action) Final notice before formal recovery Between letters, use other channels to resend the payment link: email at Day 7, SMS at Day 14, WhatsApp at Day 21. See our multi-channel payment collection guide for the full escalation sequence. ## Letter 1: Friendly Payment Reminder Send this 7-10 days after the due date. Post it on company letterhead, or send it as a PDF attachment with the payment link in the email body. > [YOUR COMPANY LETTERHEAD] [DATE] [CUSTOMER NAME] [CUSTOMER ADDRESS] Re: Invoice #[NUMBER] -- Payment Reminder Dear [NAME], We are writing to remind you that invoice #[NUMBER] for £[AMOUNT], dated [INVOICE DATE], was due for payment on [DUE DATE]. As of today, we have not received payment. We trust this is simply an oversight and would be grateful if you could arrange payment at your earliest convenience. Pay online: [PAYMENT LINK URL] [QR CODE HERE] Scan to pay instantly by card, bank transfer, or Apple Pay If you have already sent payment, please accept our apologies for this letter crossing in the post. If there is a query regarding this invoice, please contact us at [EMAIL] or [PHONE]. Yours sincerely, [YOUR NAME] [YOUR TITLE] [YOUR COMPANY] Formatting notes: - Print the QR code at minimum 2cm x 2cm. Larger is better -- 3cm x 3cm is ideal. - Place the QR code next to the payment URL so the reader understands what it does. - If posting, use your standard company letterhead. ## Letter 2: Firm Follow-Up Send this at 21 days overdue. The tone shifts from "we're sure this is an oversight" to "we need to hear from you." > [YOUR COMPANY LETTERHEAD] [DATE] [CUSTOMER NAME] [CUSTOMER ADDRESS] Re: Invoice #[NUMBER] -- Second Payment Notice Dear [NAME], Further to our letter of [DATE OF LETTER 1], we note that invoice #[NUMBER] for £[AMOUNT] remains unpaid. This balance was due on [DUE DATE] and is now [NUMBER] days overdue. We have not received payment or a response to our previous correspondence. Please arrange payment within 7 days of the date of this letter: Pay online: [PAYMENT LINK URL] [QR CODE HERE] Scan to pay securely If you are unable to pay the full amount, we are open to discussing a payment arrangement. Please contact [NAME] at [EMAIL] or [PHONE] to discuss your options. We value our business relationship and would like to resolve this without further action. Yours sincerely, [YOUR NAME] [YOUR TITLE] [YOUR COMPANY] Key points: Mentions "further action" for the first time. Offers a payment plan -- this catches debtors who want to pay but can't pay in full. ## Letter 3: Formal Notice With Statutory Interest Send this at 30-35 days overdue. This letter references the Late Payment of Commercial Debts (Interest) Act 1998 and formally applies statutory charges. > [YOUR COMPANY LETTERHEAD] [DATE] [CUSTOMER NAME] [CUSTOMER ADDRESS] Re: Invoice #[NUMBER] -- Formal Notice of Overdue Debt Dear [NAME], We have written to you on two previous occasions regarding the unpaid balance of £[AMOUNT] on invoice #[NUMBER], dated [INVOICE DATE], with payment terms of [NUMBER] days. This balance has been outstanding since [DUE DATE] -- now [NUMBER] days overdue. Statutory Interest and Compensation Under the Late Payment of Commercial Debts (Interest) Act 1998, we are entitled to charge: - Statutory interest at 8% per annum above the Bank of England base rate, calculated from the due date - Fixed compensation of £[40/70/100] for the cost of debt recovery We are now applying these charges. The revised balance is: - Original invoice amount: £[AMOUNT] - Statutory interest ([NUMBER] days at [RATE]%): £[INTEREST AMOUNT] - Fixed compensation: £[40/70/100] - Total now due: £[REVISED TOTAL] Please make payment within 7 days: Pay online: [PAYMENT LINK URL] [QR CODE HERE] If payment is not received by [DATE + 7 DAYS], we will refer this debt for formal recovery, which may include County Court proceedings. Any court fees and legal costs will be added to the amount owed. To discuss a payment arrangement, contact [NAME] at [EMAIL] or [PHONE]. Yours sincerely, [YOUR NAME] [YOUR TITLE] [YOUR COMPANY] Important: Only apply statutory interest to B2B debts. The Act does not cover consumer transactions. Check the GOV.UK guidance on late commercial payments. ## Letter 4: Letter Before Action (Pre-Legal) Send this at 45+ days overdue. This is a formal Letter Before Action (LBA) -- a required step before issuing a County Court claim under the Pre-Action Protocol for Debt Claims. > [YOUR COMPANY LETTERHEAD] [DATE] SENT BY RECORDED DELIVERY AND EMAIL [CUSTOMER NAME] [CUSTOMER ADDRESS] LETTER BEFORE ACTION Re: Claim by [YOUR COMPANY] against [CUSTOMER COMPANY] -- Invoice #[NUMBER] Dear [NAME], NOTICE UNDER THE PRE-ACTION PROTOCOL FOR DEBT CLAIMS We write in accordance with the Pre-Action Protocol for Debt Claims (Practice Direction -- Pre-Action Conduct and Protocols). The Debt [YOUR COMPANY] provided [DESCRIPTION OF GOODS/SERVICES] to [CUSTOMER COMPANY] as detailed in invoice #[NUMBER], dated [INVOICE DATE]. Payment of £[ORIGINAL AMOUNT] was due on [DUE DATE] under [NUMBER]-day payment terms [as agreed in our contract dated [DATE] / as standard commercial terms]. Previous Correspondence We have made the following attempts to collect this debt: 1. [DATE] -- Payment reminder sent by [email/post] 2. [DATE] -- Second notice sent by [email/post] 3. [DATE] -- Formal notice with statutory interest applied, sent by [email/post] None of these communications have resulted in payment or a substantive response. Amount Claimed - Original debt: £[AMOUNT] - Statutory interest (8% + BoE base rate, [NUMBER] days): £[INTEREST] - Fixed compensation under the Act: £[40/70/100] - Total claimed: £[TOTAL] What You Need to Do You have 30 days from the date of this letter to: 1. Pay the outstanding amount in full: [PAYMENT LINK URL] 2. Propose a payment plan by contacting [NAME] at [EMAIL] or [PHONE] 3. Dispute the debt in writing, setting out the specific grounds of your dispute [QR CODE HERE] Scan to pay the outstanding balance If You Do Not Respond If we do not receive payment, a payment proposal, or a written dispute within 30 days, we will issue a claim through the County Court without further notice. Court fees (currently £[AMOUNT] for claims of this value) and any legal costs will be added to the claim. We strongly encourage you to resolve this matter before court proceedings become necessary. Yours faithfully, [YOUR NAME] [YOUR TITLE] [YOUR COMPANY] [COMPANY REGISTRATION NUMBER] [COMPANY ADDRESS] Critical notes: - Send by recorded delivery and keep proof of posting. The court will want evidence the debtor received the LBA. - The 30-day response period is required by the Pre-Action Protocol. Do not issue proceedings before 30 days have passed. - Include your company registration number and full address -- these are required for court claims. - If the debtor proposes a reasonable payment plan, you should consider it. Courts look unfavourably on claimants who reject reasonable proposals. ## Adding QR Codes to Dunning Letters Every posted letter should include a QR code that links to the payment page. Here's why: - Bridges physical to digital -- The debtor reads a paper letter but can pay instantly from their phone. - No URLs to type -- Payment link URLs can be long. A QR code eliminates typing errors. - Works on every phone -- All modern smartphones can scan QR codes with the default camera app. To generate a QR code from a payment link, most payment link providers offer built-in QR generation. If yours doesn't, any QR code generator works -- just paste the payment link URL. Placement: Put the QR code in the body of the letter, near the payment amount. Label it clearly: "Scan to pay securely." Print at minimum 2cm x 2cm. ## What Happens After the Final Letter If the debtor doesn't pay, propose a plan, or dispute within 30 days of the Letter Before Action: ### Small Claims Court (Under £10,000) For debts under £10,000, use the Money Claim Online service. Court fees range from £35 (up to £300) to £455 (£5,000-£10,000). The process is straightforward and doesn't require a solicitor. ### County Court (£10,000+) For larger debts, issue a Part 7 claim through the County Court. This typically requires legal advice. Court fees are based on the claim value (e.g., £528 for a £10,000-£50,000 claim). ### Debt Recovery Agency An alternative to court proceedings. Agencies typically charge 5-15% of the recovered amount. They handle all communication and can be more effective for smaller debts where court costs aren't justified. ## Common Questions ### Can I send dunning letters by email instead of post? Yes, but posted letters carry more weight -- especially in formal B2B relationships and if you may need to pursue legal action. For the Letter Before Action specifically, best practice is to send by both recorded delivery and email. ### How do I calculate statutory interest? Interest accrues at 8% per year above the Bank of England base rate, calculated daily from the due date. Formula: (Debt x (8% + BoE rate) / 365) x days overdue. For example, on a £5,000 debt at a total rate of 13.25% over 30 days: £5,000 x 0.1325 / 365 x 30 = £54.45. ### Should I use a solicitor for the Letter Before Action? Not necessarily. The template above follows the Pre-Action Protocol and is legally sufficient. However, a letter from a solicitor's firm carries additional weight. Some solicitors offer LBA services for a fixed fee of £50-150. ### What if the debtor disputes the invoice? If the debtor provides a written dispute with specific grounds, you must respond to those grounds before proceeding with court action. The Pre-Action Protocol requires both parties to attempt to resolve disputes before involving the court. ## Get Started Dunning letters work. Dunning letters with payment links and QR codes work faster -- because they turn a formal demand into a one-scan payment. Shuttle Payment Links work with 40+ gateways, support white-label branding, and generate QR codes for printed correspondence. See how it works. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment reminder emails](/blog/payment-reminder-email-templates/) - [payment link](/guides/pay-now-button-invoices/) - [multi-channel payment collection guide](/guides/multi-channel-payment-collection/) - [GOV.UK guidance on late commercial payments](https://www.gov.uk/late-commercial-payments-interest-debt-recovery) - [Money Claim Online](https://www.gov.uk/make-court-claim-for-money) - [40+ gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/emotional-payments/ --- # Emotional Payments | Shuttle > How emotions influence payment behaviour -- why checkout experience, trust signals, and payment UX directly affect conversion rates. # Emotional Payments By Nick Dunse, March 17, 2024 How emotions influence payment behaviour -- why checkout experience, trust signals, and payment UX directly affect conversion rates. Talk to us Make enabling payments for your platform and merchant users easy. So today with me, I have Dastan from Marks and Spencers and Danny from Stored they've very kindly joined us to talk about this topic. And Dastan, if I can ask you to introduce yourself first and tell us a little bit about you, Marks and Spencers for those who don't know, and then Danny if you could do the same for yourself and Stored. My name is Dustin. I have a seven years of FinTech background now, almost year eight, if we're being in the context of payments. And so currently at Martin Spencer working through payments technology consolidation, as well as its strategy of. How the embedded finance would look like for Marks and Spencer and it's future state, not the current state. Yeah, so I'm trying to look and work with our third party providers. So they are also on, on our side when we strategize. Yeah, for those who don't know, it's a largest lead, one of the largest. And the number one brand in the UK. Danny, yeah, so background is is very much similar in payments. I I spent about 11 years at a business called world first, which is a cross border payments business. the interesting thing about World First is that we were acquired by a very well known business called Alipay is probably the name that is better known by, but the Ant Group. So I was part of the exec team that led the integrations between the World First business and and some of those connected entities in China. think for me, that was probably a light bulb moment because spent a lot of time looking at. Perhaps the the advancements that have been made in the east, particularly with regards to payments and what we would describe as contextual commerce and how brands and consumers interact with each other on those experiences are true on the channel experiences. That, for me, led me to the next stage of my career, which was to set up the business that is stored which we found it at the very end of last year. And I suppose we would describe ourselves as a contextual payments platform. And what I mean by that is merchants often take payment within the confines of quite rigid structure. So in physical stores or on e commerce websites and those payment experiences don't necessarily reflect the journeys or the context for where the customers come before. And actually for us, that's really interesting. And we allow merchants to effectively spin up micro payment experiences in a matter of minutes that meet those needs. Thanks guys. I want to set up the premise for today because commerce as it stands today is good and fine and working well online as well as in in the bricks and mortar store. And we've seen a shift post pandemic, from more traditional bricks and mortar businesses to those looking to be online digital first stores. And now we are trying to look beyond that experience of just the digital store and one channel to actually, stores that can provide a great experience and not just a transactional checkout experience that an experience that actually inspires the customer to come back to transact again through a great buying experience, which was potentially possible in a bricks and mortar store before. But how do we create great, buying experiences through our digital channels and how do we, and therefore, how do we connect with the buyer and create an emotional connection? And so they are, we'll enjoy checking out again a question for you both and maybe I'll come to you, Dastan first. But what is a good buying experience? How do you define that over at M& S? What do you talk about? What do you personally think about? the offline experiences compared to other peers within that range of retail, brick and mortar, I think M& S is doing quite good, but the online one, I think there are so much thing to improve going forward. And the people shopping habits changed as well as there is the overall interaction within the digital space have changed a lot within the last three years. And it puts a lot of pressure on expectations. And M& S had a very. Traditional mindset in terms of how this transactions is seen and what we're seeing now is that the wallet transactions are just skyrocketing and an aggressive way for the last. I can see that. And but other than that there is no post transaction interaction with customers, basically. So it's, as you've said, it's very transactional and then, but the value proposition disappears after it. So basically you take the money and then there is no relationship post transaction. And as a person who worked on a lot of. financial products. I think there are so much every retailer can work on it. And it entails a lot of embedded financing, but not only being around the money, but it's just a customer experience and how they can. Basically retain that customer's attention was in that space. I think that's not just about payments person dealing with that. It should come from the company's strategy of how to create a loyalty basically out of that, because once you've done your dopamine rush on tick tock paying someone, you stay on tick tock, right? You don't leave tick tock. And because you're competing your attention with TikTok, you should be competing with TikTok, not with John Lewis, basically. Yeah, I like that. That's a good segue, actually. Especially with what some of the things that Danny is doing over at stored if you want to talk about social sales new channels and influencer sales, Danny what, if you're re imagining the future, what is a good buying experience look like for you? Or what do you think it should look like for all of us? I suppose the short answer is it's a successful one, right? And I think for a merchant, how do you define success? Ultimately it results in a successful, purchase and sell to end customer. But for the customer, I think actually a successful or a good buying experience is one that leaves a feeling and a good and positive feeling for the customer. And that's, this point around emotion that we talk about. The act of making a payment or buying or spending money doesn't always necessarily come with positive emotions. However, the good feeling does come from the satisfaction of buying the product that I want and need. The challenge to that is that quite often, unfortunately. The buying experience presented to the customer can stand in the way of that positive feeling. So things like, disconnected journeys, lack of context for the journey that I've just taken complicated buying process, overburdensome checkout experience, all of those things provide a sort of like depreciating sense of satisfaction for the purchase that I've just undertaken. So great buying experience for me. It's like relatively simple. It has context for the journey and experience that I've come here from and to, it adds value to me as a customer. And ultimately it reduces the path of friction from, me and this excitement that I feel about buying this product and actually, making that successful purchase. Dastan said two key things for me, which is one, really a goal of any. Retailer anyone is to create loyalty with that customer right so that it moves away from a one time purchase to a loyal customer that wants to return and keep spending so how do you create loyalty number one and then number two. You, if you're M& S, for example, you may be competing with another retailer in your space and looking at what they're doing, but actually you're competing for someone's time and someone's time is being spent, let's say on TikTok or they've purchased something on TikTok. And so you need to be creating with their attention span for whatever is TikTok. Cause as Dastan said, if you go and buy something on TikTok, once you finish your purchase, you probably can just. Continue scrolling and doing whatever you're doing on TikTok and you're back. And I thought that was really interesting. A couple of points because, um, loyalty and customer attention are really our goals here, but how do we do that? We need to create some kind of emotional attachment with the buyer. And we do that by creating great experiences. Yeah, look, there's two interesting things there, right? One is that, obviously, the relationship with the customer isn't always a direct one. It might be that, Marks and Spencers, as an example, are creating their own content, but that might be content that's being shared by, any number of different people. Some of those people, Marks and Spencers might have a relationship with, or like some understanding of, but, many of... Those instances they will have no visibility off. And it's a challenge, right? To try and manage that because customers are becoming increasingly complex. And actually what that's leading to is like differences in buying behavior. So quite often now, which means a lot of consumers and actually, particularly with social media, they haven't consciously opted into shop. So the way that we want to get consumer Oh. Or manage that relationship with the retailer. It's very different to how we would have done that 20 years ago. When we want to engage in a browsing experience, we want to look around the website, we want to look around the store. Now we expect things like intuitive, impulsive, instant purchase. And those things contribute to like how good we feel about that experience and the likelihood of whether we'll return or not, particularly through social channels and or, other forms of like digital media. So yeah, I can completely agree. Yeah, those. Those positive moments and taking someone from like this point of consideration and excitement through to cool, get this product can be really long winded, can be really complex and challenging and the more that retailers can do to make that an emotional or exciting or frictionless experience, the more chance you've got of a repeat purchase. So Dastan, what are you guys over an M& S considering today to improve that buying experience or even like the end part of that journey with payments? You've mentioned what you have today versus what you might personally think about the future. But what do you got, are you guys doing anything in particular to improve the buying experience or the payment journey today? Yeah. There are multiple teams who look after from different parts of basically engagement within that, let's say. Larger payment part, so proposing a bit of embedded finance proposition in terms of to have, to create this a small financial instrument basically within the , within the Marks and Spence. Online universe, basically. So it's not like a regulated space, but you still would have a feeling of a bit of a financial interaction. So that's a very elementary thing you can do at this stage. Because I think the whole retail industry is so outdated with their thing anyway. So it, it applies to anyone. The you go to any website on the retailer. It's the same website is 1999. I mean Nothing changed. Basically you go you put your in the basket and check out the same thing for the last 25 years It's nothing changed. So and then you have the on the other side, so I think Truly is to create this expectation from yourself That you want to merge into this seamless customer experience. So that they wouldn't care that you are they are at MNS because the experience is so good as in TikTok, because the moment they come to you, John Lewis, or, and then they start all these frictions, they think, Oh my God, this is Vanessa. I recognize you. So we want that not to happen. I think that's the strategy. So the moment you come to the app, because it's 45, 50 percent now of all shopping for closing home, that's, that's a good place to experiment. And I think we are doing some things, but still lots of to go. So I think. It's all about how you want to position yourself against the other players, basically. We don't want to solve our M& S problems and proposing more frictions for our customers. It's horrible, right? So we want to... Remove that and get this smoothness more into the whole experience. Still a lot of things to do, but I think we're just scratching the ground. Yeah. Yeah, it's interesting. We've all going back to the sort of genesis of digital commerce. We've basically put a bricks and mortar store online, we've put radio on TV. We've put the TV, we've put TV on the internet. Like it's, we're still using those old models. And there needs to be a revolution more than a sort of evolution. Really. Danny, tell us a little bit about we've been talking about social and social selling in terms of how things are moving and moving towards that. Can you tell us a little bit about. Some of the ideas that you guys have got with social selling and influences and effectively the relationship that Consumers create with those influencers and the opportunity that sits there. Yeah, sure. I think so I think what we're seeing is that the relationship between the brand and the customer perhaps is changing and shifting and the what you're seeing with social media in particular, the sort of the influencer culture that exists today is that loyalty. Today is quite often to a personality or an individual as opposed to a brand. That makes sense. I might follow somebody online that has similar a similar value set to me. They might have similar tastes. They might enjoy similar experiences. And whatever they talk about, I might well be interested in, right? For me as somebody that's consuming that media, it's not necessarily about brand loyalty, but it's about common interests. And I think brands obviously recognize that, and I think tapping into that is key to any, successful online or digital e commerce. Business today, I think, how do you make that it's I think that stands point. Like, how do you make that frictionless is, the challenge because I can consume something on Instagram that looks, feels exciting, cool, fresh, funky. And then I hear this traditional e commerce site for a brand that perhaps. Some negative sentiment or connotations around their traditional online experience, and that puts barriers up straight away. So I think what we're really focused on is, like, how do we allow brands and, influencers, content creators, online, personalities to, to co sell products. So how do I ensure that I'm not taking you from like this experience here that is very much about me and my experiences and everything that I'm talking about straight into this environment, which is completely in conflict with everything I've just told you. It has to be a way that journey can continue that makes it to some extent. Connected. And that's what we're really focused on. Yeah, we were allowing and working with brands today that effectively are allowing content creators to spin up. Almost like micro sites or micro payment experiences for the products that they sell so that, when I come into this next page, I can see the content creator wearing those products. I can see them experiencing those products, but ultimately, I can buy those products and to tap check out from the retailer that's selling those products. And we want to make that as simple and as easy and as frictionless as possible and allow both sides to benefit. It's a really interesting by journey now to how we just from how we discover products to how we end up checking out. Sadly we end up checking out through a subpar e commerce experience. But but yeah it's. Things are changing in terms of how people find out about products. And as you say, that, that advertisement, whether it's more traditional through an influencer brand can create great appetite for the thing that they've seen. And then the rest of the experience just doesn't marry up. And you've potentially got influencers that are doing some of that loyalty. As Dastan mentioned on the retailer's behalf, but the retailer isn't actually equipping those influencers or other channels to do loyalty well or in a joined up way for sure. I don't know, Dastan, have you got any thoughts on that or? I think, I agree with Danny, I think a couple of points is a lot of e commerce or whatever the experience we have now, it's all engineering driven, all this IT guys sitting behind in the dungeons, driving, I don't know, nothing against the coding guys, but this is mostly those guys are driving, not the consumer comfort, and then And then we're trying to adopt to those Oh, this is what we coded. Just take it. So when we ask the customers, what do you want? We, the customer doesn't know what they want because they don't know the limitless possibilities of the IT, but then and we ask them, what do you want? And they give what they think it is possible, right? Because they don't know that In the IT world, everything is possible basically on like we have AWS, which you can do amazing things for Azure, but they don't know about it. So we ask them and then what they think Oh, this is probably because they've seen the worst experiences in their life. And then they think something around that should be maybe fine. So they start suboptimizing basically. So what we've created is a suboptimal experiences. And then you have this, these guys coming from everywhere, like Tik Toks, Shane and some parts of Instagram as well. These are disruptors because they went freaky wild. So that's why you have different like planets of. People living. So what I was trying to say is we still like the retail part is very static. So it's 1998, 1999. Also, there is no interaction. So you launch a very expensive. Campaign. That's a photo of someone on your website. That's it. There is. That's, but you have a influencer life doing things and then you have this, uh, a neural interaction with that person basically. So instead of the looking at the picture of someone Ryan Reynolds, or I don't know Jake Gyllenhaal, whatever is that. Is that, I think it's so outdated. It's, isn't it like seventies when the, those Dior photos or all of that, it means we're still in that era, but we don't have this. So a lot of the, what we have now is it driven, which is horrible. And then we don't give the customers, what do you really want? We can do anything for you. And if they give us really the freaky imagination, what they want, I think we, we could have built some so much more, but it's just laziness of. Of all the merchants or any developers basically in the IT world. So that, that is highly connected to the social sell because social selling while popular because they gave this. Wild imagination to go rather than the traditional commerce players. Yeah, so that's my, a bit of rant and I like, it's a good sandbox. I was going to, I was going to make a point actually, cause I think it's a, it's an interesting one, which is yeah. Social commerce and particularly like influencers and content creators provide a big opportunity for retailers and brands to test new markets. So I think what you see quite often is, a brand like Marks and Spencers, let's not use Marks and Spencers, let's use something Boohoo or whatever it is that's, commonly using an influence strategy. They, they might be. Using or accessing particular communities or pockets of communities that they know to be relevant, but perhaps aren't necessarily aligned with their core demographic. And then the challenge that you then have is that my website is built in such a way that it is, it's structured as a one for all experience, right? It represents my brand as it is today. It's my core demographic of customers and everything that they believe. And know about my brand, but I'm going to this audience over here that perhaps isn't quite so aligned with this image that I put online and then. Challenges that I've spent all this time effort and energy trying to engage this community out here that then comes onto my website and see something that's completely disconnected to perhaps what I expected before. A great example of a an equestrian brand that we're working with who have aspirations and designs to become a broader sort of sports or leisure wear brand. At the moment today, they are an equestrian brand and they're working with influencers and content creators to drive traffic to the website. But the challenge that they have is that when the customer comes, they're having seen a yoga mat or some yoga outfit on an influence or a content creator. They then land on an equestrian site that has horses on it. And, that it's like that instant disconnect of, OK I was expecting to see this, but I saw that. And I think that's to say that there's an example of extreme example. I think that happens. Across the board, almost university with every brand that's trying to test new markets and demographic. There's a lot of good stuff in there, one of the points that's done brought up I guess around who's really driving the innovation, is interesting to me because If we are genuinely to shift the experience of online commerce forward, then we really need to either imagine together or actually help the people that are making the tech imagine with us or do the imagining for them as well as the consumers, because. A lot of retailers that I know of from small to large are thinking about their technology stacks. They're thinking about moving to things like micro architecture and looking at how they can actually connect part of their order management to whatever and making their kind of operational tech lives easier. And. If you ask them why they're doing it, they're ultimately they often say to improve the experience, not only for themselves, but fundamentally for the customer, which to me is laughable because ultimately you end up with an exactly the same site after they've spent a million bucks. Recreating it all with some optimization that no one sees. And only a couple of people care about sure. It might save the business some money, but you end up with exactly the same shopping cart, put some products in it, check out as a consumer. I don't care what happens. Behind the scenes, but we've got so much innovation and inverted commas in tech. But we end up with the same buying experiences, the same, uh, consumer journeys basically. Yeah. The current I would say the whole building products for digital space is there, there is this so the 95, 95, 90 8% of the online products we have now is driven from. From the industrial mindset when you like basically architecture, you have the building and you have constraints like physical constraints, and that's the mindset, how it works now with people because they really used to build most of the physical buildings and then when it came to digital buildings. We think the same way as physical, but in digital, you can do anything basically, but people still think in that the physical world, uh, frameworks, and then that, that translates into customer products, which is, which, which looks like, Oh I create this wireframes. And then I give it to my engineers and then build it. And then we get the focus group and say, yeah, it looks good. Yes. And then we ship it. I get my bonus. Everyone is happy bye bye. That, that's like a, still is this 1950s mentality. And then the current product management is about just sub optimizing tinkering around the same thing, not creating amazing experiences. And we don't 99 percent of. All the product managers in the world, they just are keepers of that thing. Why you exist anyway, if you can't go a bit in that way, but that's the mindset shift we need. And that's why it's, we have so many crazy people coming from these disruptive players, which go So quickly into the top because customers really love it. They, that they think of, wow, this is possible actually. And why do you can't do it? That's the mentality, right? So we should change probably that. And then customers always right. And then they always want the best, but we don't want to work. It's just keep that old. Prop up the old models and keep them going. Yeah, absolutely. Danny, what are merchants and buyers asking for you guys about? What are you, what are people you mentioned the equestrian brands, but what are people coming to you and asking for, like, how are they asking you to imagine the future for them? Are there any specific things across any markets? Yeah we're primarily focused on merchants in the UK at the moment. But I suppose it depends on which end of the spectrum you're talking to. I think if you're speaking to smaller businesses, aspirational entrepreneurs and merchants that are looking to get into commerce or e commerce, our argument, our view would be that the barriers to entry are still way too high. And I think, you've seen over the course of the last, 10 years, Shopify have definitely, stolen the charge, particularly in that micro merchant segment. And I think I've done some great things to make it more accessible, but in most cases, it still requires a massive amount of time. And experience or expertise to stand up a, an e commerce site that looks and feels credible. And I think for most people that still wasn't something that, they could either afford or can dedicate the time to enter into a market that's competitive with this. And I think, that it was, we're firmly saying that I think the expectation is. It's changing and shifting and technology will evolve as such that businesses will expect and will be given the technology to stand up digital payments or e commerce experiences to sell products to their customers anywhere. Across any channel in a matter of minutes, but I think, this expectation you can spend two or three months putting together an e commerce site just won't, it won't exist in the future. The second bit, I think if you're thinking about larger merchants, the M& S's of this world, so Dastan's a, a big advocate of this and making. All the same noises. I think what larger merchants want is flexibility. It's just the flexibility to be able to build and construct experiences for their customers that meet the customers where they find them, provide context, provide relevant value as part of those experiences, not just to convert them, but to truly engage with them on a slightly more meaningful level. We talked about this point of a digital storefront or e commerce site being a digital representation of your physical store. It's built for traditional behaviors. I come, I Google your web, your brand, I find your website, I have a look around, they put items in a basket, I buy them. But the reality is that kind of behavior, it's a subset of consumers, right? But it doesn't really exist in the way that it used to. And maybe I'll give you like two examples. And I think this is. Perhaps, talking, taking it more around, less digital, but like truly digital solutions and the expectation now, I think, for both merchants and for the customer that wherever I meet or find your products, I want to be able to interact with that in some way, shape or form. And I want to be able to buy it wherever I find it. We're speaking to two different, but both larger retailers that have some slightly, different needs. One of them is an interesting one because it plays on the social media concept, but they do a lot of work to promote products online by influencers. But the byproducts of that is that every now and again, an item goes viral or a group of items go viral. And that happens. Consistently, and they know that it happens, but the nature of the beast is they never know what's going to go viral until it goes viral. And it might happen overnight, right? It might happen overnight with everybody else asleep. And then how do they react to that? How do they react to it in a physical environment is becoming really important. So for them, they're looking at, okay, we'd love to empower our storage systems to create physical visual displays of those products that have gone viral yesterday evening. But I can't go to my e commerce team and ask them to put together these pages or these structures, because. To Dastan's point, they're busy, one, but also like the confines and the constraints of a traditional e commerce site don't allow for it. So how do we allow people on the ground, marketers, people to create these experiences in a matter of minutes, put that behind a QR code within that link. To allow people to interact with them, because the other point they have as a challenge is inventory. If a product goes viral overnight, I may not be able to stop my physical store to have the inventory there for people to consume it. I want to create this digital experience that allows people to opt in, see it, connect that digital momentum to my physical store. And I want to buy that product and send it to my house. So it's those kind of things.. That really, for us, is... It's pretty interesting. And one more example, perhaps, where it's, a physical merchant trying to capture the value or the benefits that you get from a digital experience, which is the increase in the market expenses. We know this all too well. Consumers are coming into physical stores and they're starting mobile journeys, right? We can't stop it. It happens. But unfortunately, because merchants aren't controlling or taking ownership of that process or experience, where do people go? They go to Google. So I can Google the product that I see in front of me. I might be price searching, of course, but the chances are I'm also looking for information from the e commerce site for the merchant themselves. And the challenge you've got as soon as I enter Google is that I'm in a competitive scenario straight away. Equally, the information that I'm looking for, the website is not necessarily the right place to direct that customer. So let's say I'm looking for reviews or I'm looking for sustainability credentials. I direct a customer to the e commerce site, which has a load of pictures and a product description for the product that I can touch and feel in front of me. I don't need any more pictures, but I might want to be taken straight to the information that matters. And I want might want to have that option to buy that product there and then either in the store or again to send it to my house. And I think that point now is like physical is digital. There is no, you can't opt out of it now. Everybody has a mobile phone. So as a physical retailer, you have to. Understand the digital experience and take ownership of that. Yeah, absolutely. I'm amazed. Now, when you're looking at that digital experience that you talk about the physical and the digital that you don't see more QR codes on every single product in store, right? Because if I could just scan a QR code or something go immediately to that brand's page for that product and find out everything I need to know about that. That's the start of my buyer journey. Okay. I've walked into a physical store and that potentially was the start, but I'm going to continue that journey online. And who cares like whether that person checks out online or in store. And to be honest, digital is better. It's better if they check out digitally because you probably have a customer record for that transaction and that that experience. So it would be better if they did check out digitally, but the store is a great. Place to create that experience. We're just not marrying these two worlds together very well. Right now, which is crazy when there's some simple things that we could do to make that happen. And actually then retain and retain that buying experience as opposed to them getting lost on Google or down a social rabbit hole, cause I do it all the time. There is like a barcodes now at some merchants. So MNS has the barcode system where you go to app and then you scan any product from the closing. And you can basically check out within the app, but probably it's quite I don't know the statistics, but I don't think there is a human wild habit to do that. When you are in, in, in store, you want to touch it, but at the same time I think you have a new generation which is coming, which will probably use that scanning capabilities. I think... There are still frictions within this probably things. So it's, you have to add to basket, check out, pay, and then maybe it's out of stock. So there are like so many other constraints if you just unpack the whole thing. So it's just barely the elementary thing you've done. But I think we don't go beyond of what is. What is really that of you just barcode and what's after that? It's a transactional, right? Still you do, you choose the colors, size, boom, bye. So yeah nothing happens. Basically you jump straight to that transaction. Yeah. So it's still that. Remodeling of the, of whatever you thought is good, but I think to Danny's point is how you capture the attention value basically at that point, and my fear is. That a lot of these things may come from other sources of players within the digital space, not retailers, apps, maybe, I don't know. I'm not saying that it's not going to work out for anyone, but there may be some other points of capturing that value or that attention or loyalty basically. Because when you pay for that item. You think you're capturing the value, but the value is not the money is there is like in like a Implicit value which is hidden right which is the loyalty That the other things which I think we are not capturing as a it's anything like I go to Zara They have the horrible Scanning experience as well. So I think that all the retailers are is still have long to go And but there are like other players which probably will come in the space and then create an AR combined within that space. And those going to drive the true capturing the full lifetime or the full value instead of just the money value. If you what I mean. Yeah, absolutely. Off of eBay the other day. And like I generally search eBay for secondhand cheaper goods. But I thought what was really interesting was, I could actually Ask a question to the seller and he got back to me within, I think he got back to me within 15 minutes and we had a bit of a back and forth conversation. That was the difference between me not buying it and actually me converting and buying the thing from him. And it was actually a new product that he was selling. But I thought that was really interesting because he didn't make the product. He was selling someone else's product, but he knew a lot about it. He was really happy to have a conversation with me. Didn't take too much from him. He probably did it on his mobile on the way to work. Who knows? But our digital experiences and our bricks and more experiences, it's actually pretty hard to have that kind of rapport with the seller or even the brand themselves. And that's just a simple conversation that went on an eBay just to augment my experience. Like it made a difference. I ended up buying it. I've shortlisted this guy for his other products now And I thought you know rate him as a great seller, but to your points It's like there's so much implicit value that can be added and gained for all parties Jumping down because we've only got a few minutes left in our session it sounds like we need somewhat of a sort of revolution as opposed to an evolution that I mentioned earlier. And we've talked about some of the things that might be in that revolution. We've got some crazy people out there doing it already but it's not in the mainstream. If you guys could. Leave merchants with one thing to think about. What would you want them to go away and think about to actually improve this buying experience, improve this emotional connection with their customer base?, so I've created a junior banking like seven years ago when it was, I feel like it wasn't a popular thing back then. So basically you sign up your kid to your banking account, mobile banking app, and then you limit. So we limited the purchasing options. It's just a. The drinks are so no alcohol and then you cannot take money from the ATM so you can see in track and that's for the customer. But for us, you also create a sticky loyalty since the chance. There's a very small egg, so by the time they grew up, they already know you so much and that's like already wired into their brain. That's just like a very elementary loyalty you can do, but not, no one is doing it. I think like basically what we what we are working is for the current, like the demographics of. What you have, but you're not targeting the just newly borns and how you're going to basically sign them up. And then because five year old is so much more literate than anyone else who is mobile and how you're going to target them to be part of your like journey of change, but then you should be, you should have so much capability to cater for those who have half a second attention span. So I think the challenge is. We are focused with the current generation. The current generation is already past, so we don't it's a goner, basically. You are, we should think about the ones coming up, which is the generation alpha, even not the generation Z. And So that, that is the biggest challenge how are you gonna create that for them? Because I go to so many events and talks and people's oh, yeah, he's, oh, it's unregulated. There's so many challenges. It's like they don't want to accept that it's coming. And then it's better you accept that than saying, oh, this is something. We don't want to see because you are ignorant, right? You are concentrating on the what's happening now with chat GPT, but this is just a one percent So what I'm trying to say is Instead of looking at what is chatGPT doing now, you should think what is really coming up. And then that's the same with what these guys are growing up with expectations. The experience expectation is so high and it's coming as a in a very fast paced way. I think the challenge for all the retailers is... Is that your competitor is the tick tock the chains or whatever is that not your peers. And the other thing is is investing so much into your infrastructure of networks and all of that. That's a huge thing. And I've worked on 5g and then there are like so many opportunities within that to build products specifically for this digital experience. 5g is designed for that and 6g is going to be even like on steroids basically so a lot of money needed and then a lot of will to understand to both solve the worlds. I think that's the biggest challenge or I don't know. Not challenge, but probably work should be done. Cool. So you've given us like 10 things there for people to take away, which is great. But it, we know the gap is large, imagination, invest and invest in the future. . Danny. I think we've talked about this before, but to, to think about like the transaction on the payment as more than that, like the payment is like a, it's like the successful outcome of a built relationship between buyer and seller. I should feel, it should be filled with excitement. It should be filled with experience. That's great. Thank You know, it should, there has to be a bit more to it than perhaps what we're delivering today. I think as payments businesses, we focused a lot on like how we can support that, but it's all been around, speed and security. And that kind of just isn't really good enough now. I think for merchants really to think about that next wave of like consumerism and how people's people are interacting with their products. It has to be true on the channel, and I think there is a massive opportunity for brands that sort of embrace that and don't fear it. Things like mobile commerce in store is going to be really important. There are a lot of people that have seen that as a real challenge to their business model and something that they should almost push against. But ultimately it's here. It's here to stay. And the mobile device is a massive. Potential segue and a bridge between those two experiences. Obviously, I think that, yeah, a lot of retailers have perhaps pushed against this idea that, yeah, we allow people to move between those journeys because, yeah, there is a fear by taking a customer in store into an online experience that they leave that experience, right? But ultimately, it is here to say that the phone is a bridge. It's a segue between one experience to another. And it's the one thing that's ever present in every buying decision you'll ever make, yeah. Whether it's on your desk or it's in your pocket in a physical store or it, it's in your pocket or your hand while you're on a train, your mobile phone is ever present. I think that mobile commerce and mobile payments are going to become increasingly important. . For me, what you were saying is the opportunity is there for brands in any vertical to ultimately own each one of those experiences, but not only own where they can't own it and they've got a distribution network, it's to actually leverage and influence that distribution network on their own behalf and create. Therefore, great end to end commerce experiences, which ultimately end in that customer checking out and buying a product from X brand, regardless of how they got there, but they had a great experience along the way because the retailer or the brand has thought about it and actually thought about who might be in the chain to influence that decision that buyer has gone through, can I just, one, one thing? Is, as a, it's pure from pure payments perspective. So what we have in the online experience is that it's a horrible payment experience. You may get stepped up for authentication because, oh my God, you are a dodgy person. And this is all created by this. Old school banks card schemes PSPs, whatever these guys think they are caring about this thing, but you don't go to MNS or June Lewis and feeling you get mugged or something like that. Or there's someone trying to fraud you because you feel so safe there, right? This is an experience we give to customers in retail. Like the, in the, in real world, but somehow in the in the digital world, we have this. paranoia of this frauds. It happens, but if anyone cannot create specifically this, the providers of the technology we are basically solving their problems for them, right? You, we go to out of app to go to banking app approve, blah, blah, blah. I don't care. I want everything so seamless, but we're solving this banks problem. The 3ds provider problem, whatever is that. And as a customer, you don't, I don't want to solve it. Sorry. So that's the other part of expectation. And whoever is going to do an amazing job within that space is going to be winner as well, because if you will provide this fraudless. And then no frictionless then, and also your money is safe, then that's the winner. And, but we still have this oh my God, why are you entering M& S and why are you going out from this store? It's it's, imagine this is the same in digital payment world as if everyone is like every third or every 10th even walking out from even Zara or any John Lewis or any star. If you bought something, then it's. It's that we still have to solve and this is 25 year old process still doing the same thing. And yeah it's, there are so much to do. That's the basic things, basically. Yeah, and I think what's interesting about that is... And this is a whole nother session. So we'll set up another webinar just to chat about that stuff, what's interesting about that is it comes back to this point that we made around kind of imagination, ownership, and loyalty with the customer. So if you know the customer. And you are validating the customer, um, in a really frictionless way. You can remove all the barriers for the end part of the process, which is the important part of the process, right? They, the statistic is that 20 percent of people leave the payment page. And they're the guys who've gone through and put everything in the basket, gone through all the research, whatever, they get to the payment page and they go, Oh, this is just too hard or whatever. There's too much friction, but they're your highest intent buyers. And so you've, you want to get rid of that so that you convert an extra 20%. But it comes down to, your customer. And it comes down to you creating experiences that are are good and safe for them, but it's got to happen earlier. And you've got to, you've got to create solutions that. are specific and identifiable with that particular customer. But it feels like we're a long way from that. I don't know anyone who's working on that. I think the the social ones maybe have some good ideas, but I think there are, we will have new innovations coming as a new players within that space. As an e commerce, it's a, it's still in its... I don't know, pre dinosaur era, like even Shopify, Amazon it's all old school. It's all old school. I think like the ones that are going to change is going to be so seamless. It's, it is I think we are, we will move into at one point when you send a hard emoji is going to be equal to five pounds or something like that. Imagine that. So your emotion is money. It's crazy, right? But I don't want to go into my rebel app and then type five pounds, then you'll have this kind of, yeah, we are already in this world. So we share so much in tip from you press like this heart or something around this. that would equal to money or if it's going to be crypto money was in that space, but that's what's coming. Basically not going into my cart and then CVV it's sorry, it's, this is not going to work. So that is my, like not a prediction, but that's how it should be. I think if you want like this constant, because There is no other way to capture the attention. Yeah. And it certainly doesn't, it's interesting when you have an emotion, like in, if you imagine that a child came up to you and asked you for a, for some money and you gave them five pounds out of your wallet in the physical, which obviously nobody has five pounds in their wallet anymore. There's quite, there's an, that is an enjoyable experience 'cause. You've seen a need or you've actually physically transacted with someone like in a physical space and having to go into your banking app and approve a payment just makes you hate the fact that you are having to pay someone some money, right? It removes any joy from the experience whatsoever. Anyway, I'm going to go offline and have a massive argument with some open banking people now. But yeah, all right. Thanks guys. Thanks a lot. We will talk more payment specific things perhaps next time. But yeah, thanks Danny. Thanks Dastan. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/freedompay/ --- # FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle | Shuttle > Connect FreedomPay to Zapier, Twilio, QuickBooks, and more through Shuttle. One of the few approved integrations for the FreedomPay platform. # FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle By Nick Dunse, December 28, 2025 Connect FreedomPay to Zapier, Twilio, QuickBooks, and more through Shuttle. One of the few approved integrations for the FreedomPay platform. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. For merchants using FreedomPay, the platform's reputation for secure, enterprise-grade payments is well earned. But integrating it into your broader software stack -- whether that's Zapier, Twilio, QuickBooks, Xero, or Brightpearl -- is notoriously difficult. In fact, most teams find themselves at a dead end when trying to connect FreedomPay into modern workflows, CRMs, ERPs, or automation platforms. The APIs are complex, access is tightly controlled, and building custom integrations can take months. That's where Shuttle comes in. We offer one of the few approved integrations for FreedomPay, designed to unlock seamless payment workflows across a wide range of platforms -- with no custom development required. ## Why FreedomPay Integration Has Been So Difficult FreedomPay is built for resilience, scale, and compliance -- especially in sectors like hospitality, travel, entertainment, and retail. But its enterprise-grade architecture has historically made integrations challenging: Complex and restricted API access Long onboarding and certification cycles Limited third-party tooling Little support for no-code environments This means if you've wanted to trigger payments from tools like Xero, Shopify, or Twilio, you've likely hit a wall. ## Shuttle: The Approved Integration Layer for FreedomPay Shuttle is the connective tissue between FreedomPay and the rest of your business stack. With Shuttle, you can instantly integrate FreedomPay into: Zapier or Make.com (workflow automation) Twilio (SMS, IVR, WhatsApp) Xero or QuickBooks (invoicing & reconciliation) Brightpearl (retail ERP) Shopping carts, ticketing platforms, travel booking tools, customer experience systems, and more Our platform takes care of the heavy lifting -- auth, compliance, tokenisation, and real-time status updates -- so you can focus on building better workflows, not wrangling APIs. Use Cases Across Key Merchant Categories ### 1. Shopping Cart Platforms (Shopify, WooCommerce, Magento) Trigger secure payment links for bespoke or high-value orders that don't fit the standard checkout flow. ### 2. Ticketing & Events Platforms Generate FreedomPay payment links for group bookings, upgrades, or post-sale add-ons -- automatically. ### 3. Travel Booking Platforms Send payment requests via SMS or email for booking amendments, deposits, or cancellations. Ideal for OTA and tour operators. ### 4. Invoicing Platforms (Xero, QuickBooks) Automatically generate and send FreedomPay payment links when invoices are raised. Shuttle can also mark invoices as paid and trigger reconciliation workflows. ### 5. Customer Experience & Call Centre Tools (Twilio) Empower your agents to trigger payment links during calls or chat interactions. Reduce friction and close revenue gaps in real time. ### 6. Food Ordering Platforms For large orders, catering services, or custom events, send FreedomPay links directly via WhatsApp, SMS, or email -- integrated into your ordering logic. Built for Non-Developers, Loved by Product Teams Shuttle is not just an integration; it's a payment orchestration layer that transforms FreedomPay from a standalone payment system into a connected part of your business. No developers needed: Use Zapier or Make.com to plug into 6,000+ apps Enterprise-grade security: Built to FreedomPay's standards Approved and production-ready: Already used by global brands in retail, travel, and services Realtime sync: Know instantly when a payment is made, and trigger the next step in your workflow ## The Bottom Line If you're a FreedomPay merchant looking to modernise your payment workflows, the message is simple: you don't need to struggle with APIs or build costly integrations. Shuttle is the approved way to unlock the power of FreedomPay across your tools -- fast. Let your payments system finally talk to your CRM, ERP, customer comms platform, and back office. Book a demo with Shuttle today and see how easy it is to connect FreedomPay to the platforms that power your business. ## Related Reading Explore More ### How to Connect FreedomPay to Twilio for Voice & IVR Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Connect FreedomPay to Twilio for Voice & IVR Payments→](/guides/freedompay-twilio-integration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/ --- # How to Give Customers More Ways to Pay Your Invoices | Shuttle > Reduce DSO and improve cash flow by offering multiple invoice payment methods. Learn how payment links, ACH, and digital wallets get invoices paid faster. # How to Give Customers More Ways to Pay Your Invoices By Nick Dunse, July 10, 2025 Reduce DSO and improve cash flow by offering multiple invoice payment methods. Learn how payment links, ACH, and digital wallets get invoices paid faster. Talk to us Make enabling payments for your platform and merchant users easy. Late invoice payments cost businesses billions every year. The average small business waits over 20 days past the due date to receive payment, and the root cause is rarely that customers don't want to pay. It's that paying is too difficult. When an invoice arrives as a PDF attachment with bank details buried at the bottom, friction wins. The customer sets it aside, forgets, and your accounts receivable team starts chasing. The fix isn't more reminders. It's removing the barriers between your invoice and your customer's preferred way to pay. By offering multiple invoice payment methods -- credit cards, bank transfers, digital wallets, and one-click payment links -- you reduce days sales outstanding (DSO), improve customer experience, and get paid faster. This guide covers the most effective invoice payment methods, how to implement them, and what to look for in a payment solution that fits your business. ## Why Offering Multiple Invoice Payment Methods Matters Every customer has a preferred way to pay. Some want to use a credit card for the rewards. Others prefer ACH bank transfers to avoid processing fees. A growing segment expects Apple Pay or Google Pay at checkout, even on B2B invoices. When you only offer one method -- typically a bank transfer with manual account details -- you're forcing customers into a workflow that may not suit them. The business impact is measurable: - Lower DSO: Invoices with embedded payment links get paid 2-3x faster than traditional invoices. When paying takes 30 seconds instead of 10 minutes, customers pay immediately. - Better cash flow: Faster payments mean more predictable revenue. You spend less time forecasting when money will arrive and more time growing the business. - Improved customer experience: Giving customers choice signals professionalism. It removes a common source of friction in business relationships. - Reduced collection effort: Your AR team spends less time sending reminders and making phone calls. Automation handles the follow-up. If your accounts receivable process still relies on manual bank transfers and email reminders, you're leaving money on the table -- and making your customers work harder than they should. ## Invoice Payment Methods: A Complete Overview Not all payment methods are created equal. Each has trade-offs in terms of speed, cost, and customer preference. Here's what you should consider offering on your invoices. ### Credit and Debit Cards Card payments are the most widely accepted method globally. For B2B invoices, corporate cards are increasingly common -- especially for mid-market and SMB customers. The benefit is instant confirmation and settlement within 1-2 business days. The downside is processing fees, typically 2.5-3.5% per transaction, which can add up on large invoices. ### ACH and Bank Transfers ACH (Automated Clearing House) payments are the go-to for businesses that want lower fees. Processing costs are typically flat-rate or a fraction of card fees. Settlement takes 2-3 business days, though same-day ACH is increasingly available. For high-value invoices, ACH payment links combine the cost advantage of bank transfers with the convenience of one-click payments. ### Payment Links Payment links are URLs that open a pre-filled hosted checkout page. They can be embedded directly into invoices -- whether PDF, email, or messaging -- so the customer clicks once and pays. No login portals, no retyping amounts. Adding payment links to invoices is one of the highest-impact changes a business can make to accelerate collections. ### Digital Wallets Apple Pay, Google Pay, and similar wallets are no longer limited to consumer e-commerce. Businesses increasingly use them for invoice payments, especially when paying from a mobile device. The checkout experience is fast -- biometric authentication replaces card number entry -- and conversion rates are typically higher than traditional forms. ### Direct Debit and Recurring Payments For subscription-based or retainer invoicing, direct debit mandates let you pull payments automatically on the due date. The customer authorises once, and subsequent invoices are collected without any action required. This is ideal for reducing late payments on recurring services. ## Adding Payment Links to Your Invoices Payment links are the simplest way to bridge the gap between invoicing and payment collection. Instead of listing bank details and hoping the customer initiates a transfer, you embed a link that opens a secure, branded checkout page with the invoice amount pre-filled. Here's how to implement them effectively: - Generate a unique link per invoice: Each link should map to a specific invoice number and amount. This prevents overpayment or underpayment and simplifies reconciliation. - Place the link prominently: Don't bury it at the bottom of the invoice. Put a "Pay Now" button or link at the top, near the total amount due. Visibility drives action. - Support multiple payment methods on one link: The best payment links let customers choose their preferred method -- card, bank transfer, or wallet -- on a single checkout page. One link, multiple options. - Include the link in emails and SMS: Invoice emails should contain the payment link in the body text, not just in the PDF attachment. SMS reminders with a payment link can recover overdue invoices within hours. - Set expiry dates: Links that expire after a set period create gentle urgency and prevent stale invoices from being paid at incorrect amounts months later. Payment links have a direct impact on cash flow. Businesses that adopt them typically see payment times drop from weeks to days. ## Making Invoices Easier to Pay Offering the right payment methods is only half the equation. The payment experience itself needs to be frictionless. Here are the design and delivery principles that make the difference. Mobile-first design. Over half of invoice emails are opened on mobile devices. If your payment page doesn't render cleanly on a phone -- or requires pinch-zooming to enter card details -- you'll lose payments. Ensure your checkout page is responsive and that buttons are sized for thumbs, not cursors. One-click payments. For repeat customers, saved payment methods eliminate data entry entirely. The customer clicks the link, confirms the amount, and pays with a single tap. This is especially powerful for recurring invoices where the customer relationship is established. Smart reminders. Automated reminders sent 3 days before, on the due date, and at intervals after can recover a significant percentage of overdue invoices. Each reminder should include the payment link -- don't assume the customer still has the original invoice. Branded checkout. A payment page that displays your logo, colours, and business name builds trust. Generic-looking checkout pages create hesitation, especially for large B2B payments. White-labelled payment pages reassure the customer that they're paying the right company. Partial payments and payment plans. Some customers can't pay the full amount immediately. Allowing partial payments or instalment plans on invoices keeps cash flowing rather than stalling entirely. A customer who pays 50% now is better than one who pays 0% while waiting for budget approval. ## Invoice Payment Automation: Reducing Manual Work Manual invoicing and payment follow-up consume hours of administrative time every week. Automation handles the repetitive tasks so your team can focus on exceptions and relationship management. Key areas to automate: - Invoice generation and delivery: Trigger invoices automatically from your billing system or ERP. Each invoice includes a payment link generated at creation time. - Payment reminders: Schedule a sequence of reminders: a friendly nudge before the due date, a direct reminder on the day, and escalating messages after. Each includes the payment link. - Reconciliation: When a payment link is tied to an invoice, the payment is automatically matched. No more spreadsheet cross-referencing or manual bank statement reviews. - Receipt and confirmation: Send payment receipts automatically. Update your accounting system in real time. Close the loop without anyone touching a keyboard. - Reporting and analytics: Track which invoices are paid, overdue, or partially paid. Monitor average DSO, payment method preferences, and collection rates to continuously optimise your process. The goal is a system where invoices go out, payment links are clicked, money arrives, and your books update -- all without manual intervention for the majority of transactions. ## Choosing an Invoice Payment Solution Not every payment solution is built for invoicing. When evaluating providers, focus on these capabilities: - Multi-method support: Can customers pay by card, ACH, and digital wallets from the same link? Single-method solutions limit your flexibility. - API and integration options: The solution should integrate with your invoicing software, ERP, or accounting platform via API. Manual link generation doesn't scale. - White-label branding: Your checkout page should look like your business, not a third-party payment provider. Branded experiences build trust and reduce payment abandonment. - Automated reconciliation: Payments should auto-match to invoices. Look for webhook notifications and real-time status updates. - Security and compliance: PCI DSS compliance is non-negotiable. Hosted checkout pages keep card data off your systems and your PCI scope limited. - Embeddable for platforms: If you're building invoicing into a SaaS platform, you need a payment provider that supports embedded payments -- white-label processing that runs under your brand while your provider handles the infrastructure. Explore embedded payment solutions that can be integrated directly into your platform. ## How Invoicing Platforms Can Embed Payments If you run an invoicing or accounting platform, enabling your customers to collect payments directly through their invoices is a significant competitive advantage. Rather than building payment processing from scratch -- which involves PCI compliance, banking relationships, and regulatory complexity -- you can embed a payment layer into your existing product. Embedded payment links let your platform users generate pay-now links automatically when they create invoices. The payment is processed through your platform's branding, but the infrastructure -- card processing, ACH, PCI compliance, fund settlement -- is handled by a payment partner behind the scenes. This approach unlocks new revenue streams (payment processing fees), improves platform stickiness (users are less likely to leave when payments are integrated), and delivers a better end-customer experience. It turns your invoicing tool from a document generator into a full payment collection system. If you're exploring how to add payments to your invoicing platform, book a discovery call to see how embedded payment infrastructure works in practice. ## Frequently Asked Questions ### What is the fastest way to get invoices paid? The fastest approach combines a payment link embedded directly in the invoice with automated email and SMS reminders. Payment links eliminate the friction of manual bank transfers -- the customer clicks a link, chooses their preferred payment method, and pays in under a minute. Businesses using this approach regularly see invoice payment times drop from 20+ days to under 5 days. ### What payment methods should I offer on invoices? At minimum, offer credit/debit cards and ACH bank transfers. Cards provide convenience and instant confirmation while ACH keeps costs low on high-value invoices. If your customer base skews mobile, add Apple Pay and Google Pay. For recurring invoices, direct debit mandates automate the entire collection process. The more methods you support, the fewer excuses customers have for delaying payment. ### How do payment links work on invoices? A payment link is a unique URL tied to a specific invoice and amount. When the customer clicks the link -- from an email, PDF, or SMS -- it opens a hosted checkout page where they can pay by their preferred method. The payment is automatically matched to the invoice, eliminating manual reconciliation. Most payment link providers offer APIs so links can be generated programmatically when invoices are created. ### Can I add payment links to an existing invoicing system? Yes. Payment link providers typically offer APIs that integrate with popular invoicing platforms, ERPs, and accounting tools. The integration generates a unique payment link when an invoice is created, embeds it in the invoice email or document, and sends a webhook when the payment is completed. Even if your system doesn't have a native integration, you can often add a payment link as a custom field or URL in your invoice template. For platforms looking to build payments in natively, embedded payment infrastructure makes it possible to offer payment collection as a core feature without becoming a payment processor yourself. ## Related Reading - How to Add a Pay Now Button to Your Invoices - Payment Reminder Email Templates (With Pay Now Links) - Overdue Invoice Email Templates UK Explore More ### Pay Now Button for Invoices: The B2B Guide ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ### How to Switch Twilio Pay Connectors Without Breaking Your Call Flow ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ### How to Get Payments Off Your Product Roadmap ### What Is Twilio Pay? How It Works, Pricing, and Connectors (2026) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [accounts receivable process](/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/) - [ACH payment links](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [Adding payment links to invoices](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [cash flow](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [Explore embedded payment solutions](/platforms/) - [book a discovery call](/discovery/) - [embedded payment infrastructure](/platforms/) - [How to Add a Pay Now Button to Your Invoices](/guides/pay-now-button-invoices/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [Overdue Invoice Email Templates UK](/blog/overdue-invoice-email-templates-uk/) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [GuideHow to Switch Twilio Pay Connectors Without Breaking Your Call Flow→](/guides/switch-twilio-pay-connector/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideWhat Is Twilio Pay? How It Works, Pricing, and Connectors (2026)→](/guides/what-is-twilio-pay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/get-paid-faster-how-it-services-firms-use-shuttle-payment-links-to-improve-cash-flow/ --- # Get Paid Faster: How IT Services Firms Use Shuttle Payment Links to Improve Cash Flow | Shuttle > IT services firms use Shuttle payment links to collect project deposits, milestone payments, and retainers faster with secure, branded checkout links. # Get Paid Faster: How IT Services Firms Use Shuttle Payment Links to Improve Cash Flow By Nick Dunse, December 29, 2025 IT services firms use Shuttle payment links to collect project deposits, milestone payments, and retainers faster with secure, branded checkout links. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. In the fast-paced world of IT professional services, time is money -- and delays in getting paid can disrupt everything from project timelines to team morale. Whether you're delivering consulting, systems integration, software development, or support, there's one part of the process that often causes friction: getting paid on time. Enter Shuttle Payment Links -- a simple, flexible solution that helps IT firms streamline client payments and take control of their cash flow. ## Why Traditional Invoicing Slows IT Firms Down Most IT services companies rely on standard invoicing workflows: send an invoice, wait 30 days, send a reminder, wait another 15 days, and maybe follow up with a phone call. This cycle isn't just tedious -- it ties up working capital, delays hiring decisions, and increases your operational risk. ## Key challenges include: Delayed payments from enterprise and SME clients Manual chasing of invoices by your finance or ops team Multiple payment methods that confuse or slow clients down Cash flow uncertainty making it harder to scale delivery teams These aren't just annoyances -- they're real barriers to growth. ## Shuttle Payment Links: Fast, Frictionless, Client-Friendly Shuttle Payment Links turn any invoice into a simple, actionable payment experience. Instead of waiting for clients to log into a portal or initiate a bank transfer, you simply include a unique, secure link with your invoice or email. Your client clicks the link, completes payment in seconds, and gets a receipt. No registration, no confusion. ## Key Benefits for IT Firms: 💸 Faster payments - Get paid in hours, not weeks 🧾 Simple invoicing - Add links directly to PDF or email invoices 🔄 Automated reminders - Optional follow-ups to reduce chasing 🔐 Secure payments - PCI-compliant and trusted by clients 🌐 No portals or apps - Frictionless UX, even for non-technical clients Real-World Scenarios Here's how IT services firms use Shuttle to reduce admin and get paid: Project deposits: Add a payment link to your Statement of Work Milestone billing: Include a link in every milestone invoice Ongoing retainers: Send monthly links by email or SMS Ad hoc support: Bill for time or tickets with a one-click payment link This flexibility is especially powerful for firms working with both SMEs and enterprise clients who value convenience and clarity. ## Implementation is Seamless You don't need to overhaul your accounting system. Shuttle integrates smoothly with your existing workflows. Use your own branding, link to your preferred payment processor (Stripe, Square, etc.), and start sending links within minutes. 🔍 FAQ: Shuttle Payment Links for IT Services ## What are Shuttle Payment Links? Shuttle Payment Links are unique, secure URLs that allow clients to pay you quickly and easily, without the need for a portal login or manual bank transfers. ## How do I use payment links with invoices? You can embed a Shuttle Payment Link directly into your PDF invoices or include it in your email message. Clients click the link, complete the payment, and you receive confirmation instantly. ## Is Shuttle secure for handling sensitive transactions? Yes. Shuttle is PCI-compliant and leverages your existing payment processor's secure infrastructure. Client card and banking details are never stored on Shuttle's servers. Can I set up recurring or scheduled payments? Yes. Shuttle supports recurring links for subscription-style billing and pre-scheduled links for milestone payments or project phases. ## How is this better than traditional invoicing? Traditional invoicing often relies on manual payment methods like bank transfers, which are prone to delays and errors. Shuttle turns each invoice into an actionable payment experience -- reducing friction and speeding up your cash flow. Can I customise the branding? Absolutely. You can use your own logo, brand colours, and business name on every payment page -- ensuring a professional, trustworthy client experience. Does Shuttle integrate with accounting tools? Yes. Shuttle can be used alongside tools like Xero, QuickBooks, and others. You can copy links directly into your invoice or automate this via simple workflow tools. ## Who typically uses this in an IT services firm? Operations managers, finance leads, and founders often initiate Shuttle. But consultants, project managers, and account managers can all send links too -- no technical skill required. Conclusion: Stop Chasing. Start Growing. Shuttle Payment Links help IT professional services firms focus on what they do best -- delivering great work -- without being bogged down by admin or cash flow issues. With faster payments, less friction, and a better client experience, it's the modern way to get paid. Ready to speed up payments and simplify your operations? Try Shuttle Payment Links today. Get Payment Links today ## Related Reading Explore More ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Get Payment Links today](/platforms/links-checkout/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuidePayment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices→](/guides/payment-collection-professional-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/global-payments-for-online-and-offline-businesses/ --- # Global Payments: International Solutions for Business | Shuttle > How businesses process global payments across borders. Covers FX, local acquiring, regional methods, and multi-PSP strategy for expansion. # Global Payments: International Solutions for Business By Nick Dunse, April 13, 2022 How businesses process global payments across borders. Covers FX, local acquiring, regional methods, and multi-PSP strategy for expansion. Talk to us Make enabling payments for your platform and merchant users easy. Expanding into new markets means solving payments in every country you operate. Global business payments are far more complex than domestic transactions -- different currencies, local payment methods, regulatory requirements, and settlement timelines all add friction. For platforms and businesses processing international payments, the difference between a well-architected payment stack and a bolted-together one is measured in approval rates, revenue, and customer experience. This guide breaks down everything you need to know about global payment processing: the challenges, the strategies, and the infrastructure decisions that determine whether your international expansion succeeds or stalls. ## What Are Global Payments? Global payments refer to any financial transaction that crosses national borders -- whether that means a customer in Germany paying a merchant in the US, or a platform settling funds to suppliers across Southeast Asia. The term encompasses both the movement of money and the infrastructure that makes it possible: payment gateways, acquirers, card networks, local payment schemes, and foreign exchange providers. For online businesses, global payments typically involve accepting cards and alternative payment methods from customers worldwide and settling in your preferred currency. For offline businesses -- think retail chains, hospitality, or field services -- global payments also include in-person terminals that handle multi-currency transactions and local card schemes. The global payments market is growing rapidly, driven by cross-border e-commerce, platform business models, and the digitalisation of B2B payments. But growth brings complexity. Every new market you enter introduces new payment preferences, regulatory frameworks, and operational requirements. ## Challenges of International Payment Processing Processing payments across borders introduces several layers of complexity that domestic-only businesses never encounter: - Foreign exchange (FX) costs: Every cross-border transaction involves currency conversion, and the spread between wholesale and retail FX rates can eat 1-3% of transaction value. Many PSPs add their own markup on top, making FX one of the largest hidden costs in international payments. - Local payment method fragmentation: Cards dominate in the US and UK, but iDEAL is essential in the Netherlands, Boleto in Brazil, UPI in India, and GrabPay in Southeast Asia. Failing to offer preferred local methods means losing customers at checkout. - Regulatory and compliance variation: PSD2 and SCA in Europe, RBI guidelines in India, LGPD in Brazil -- each market has its own rules governing how payments are processed, how data is stored, and what authentication is required. - Settlement timelines: Settlement periods vary by country and acquirer, from T+1 in some European markets to T+7 or longer in parts of Latin America and Africa. This affects cash flow and treasury planning. - Declined transactions: Cross-border transactions are declined at significantly higher rates than domestic ones. Issuing banks are more cautious about approving transactions from foreign acquirers, and mismatched BIN data triggers fraud filters. These challenges compound as you scale. A business processing in three countries might manage with a single PSP, but operating across 20+ markets demands a more sophisticated approach. ## Local Acquiring vs Cross-Border Processing One of the most important architectural decisions in global payments is whether to process transactions through local acquirers in each market or route everything through a single cross-border acquirer. Cross-border processing is the simpler option. You connect to one PSP -- say Stripe or Adyen -- and they process all your transactions regardless of where the customer is. The downside is that cross-border interchange fees are higher, approval rates are lower, and customers may see unfamiliar merchant descriptors on their statements. Local acquiring means establishing acquiring relationships in each market so that transactions are processed domestically. A German customer's card transaction is acquired by a German acquirer, classified as a domestic transaction, and benefits from lower interchange rates and higher approval rates. For a deeper breakdown of how this works and why it matters, see our guide on local acquiring for international payment collection. The trade-off is operational complexity. Local acquiring requires either setting up entities in each country or working with PSPs that have local acquiring licences across your target markets. The payoff is significant though: businesses that move from cross-border to local acquiring typically see approval rate improvements of 5-15% and interchange savings of 0.5-1.5%. ## Popular Global Payment Methods by Region Understanding regional payment preferences is critical for any international payment solution. What works in one market will fail in another. Here is a breakdown of dominant methods by region: North America: Credit and debit cards (Visa, Mastercard, Amex) dominate, with digital wallets like Apple Pay and Google Pay growing rapidly. ACH bank transfers are common for B2B and recurring payments. Europe: Cards remain strong, but SEPA Direct Debit is widely used for subscriptions and B2B. Local bank transfer methods are essential -- iDEAL in the Netherlands (60%+ of e-commerce), Bancontact in Belgium, Przelewy24 in Poland, and Klarna/buy-now-pay-later across the Nordics and Germany. Asia-Pacific: The most diverse region. UPI handles billions of transactions monthly in India. Alipay and WeChat Pay dominate China. GrabPay and ShopeePay are growing in Southeast Asia. Japan relies heavily on convenience store payments (konbini) alongside cards. South Korea uses local card networks and bank transfers. Latin America: Boleto Bancario and Pix in Brazil, OXXO vouchers in Mexico, and local card instalments (cuotas) across the region. Cash-based voucher payments remain significant in markets with lower banking penetration. Middle East & Africa: M-Pesa and mobile money dominate in East Africa. Mada is the national payment scheme in Saudi Arabia. Cash on delivery remains a significant share of e-commerce in many markets, alongside growing adoption of digital wallets. A robust global payment gateway needs to support the methods that matter in your target markets -- not just Visa and Mastercard everywhere. ## How to Choose a Global Payment Gateway Selecting the right global payment gateway is one of the highest-leverage decisions for an internationally expanding business. Here are the factors that matter most: - Geographic coverage: Does the gateway support local acquiring in your target markets, or only cross-border processing? Check not just which countries are listed, but whether they have direct acquiring relationships or are routing through intermediaries. - Payment method breadth: Can it handle the local methods you need? Some gateways are strong on cards but weak on bank transfers, wallets, or voucher-based methods. - Multi-currency settlement: Can you settle in local currencies, or does everything convert to your base currency? Local settlement reduces FX exposure and can improve reconciliation. - Pricing transparency: Look beyond the headline transaction fee. What are the FX markups, cross-border surcharges, chargeback fees, and minimum monthly commitments per market? - Compliance and data residency: Can the gateway meet data localisation requirements in markets like India, Russia, or Indonesia where payment data must be stored in-country? - API quality and integration effort: How much engineering time does integration require? Is the API well-documented? Can you test in sandbox across all supported markets? No single gateway excels everywhere. That is why the most sophisticated global businesses are moving toward a multi-PSP approach. ## Multi-PSP Strategy for Global Payments Relying on a single PSP for global payments is a risk and a limitation. No one provider has the best acquiring relationships, the lowest FX rates, and the broadest local method coverage in every market. A multi-PSP strategy lets you put each market, payment method and use case on the provider that suits it. For example, you might use one PSP for European card acquiring where they have strong local relationships, a different provider for Southeast Asian wallets, and a third for Latin American bank transfers and voucher payments. For a detailed comparison of the single-provider vs multi-provider approach, see our guide on PSP-neutral vs single-PSP strategy. The challenge with multi-PSP is orchestration. You need a layer that sits above your PSPs and handles routing logic, failover, reconciliation, and reporting across providers. This is where a payment layer or embedded payments infrastructure becomes valuable -- particularly for platforms that need to manage payments on behalf of their customers across multiple geographies. Benefits of a well-executed multi-PSP strategy include: - Higher approval rates through intelligent routing to the best-performing acquirer per market - Lower processing costs by leveraging competitive pricing across providers - Reduced vendor lock-in and negotiating leverage when contracts renew - Built-in redundancy -- if one provider goes down, traffic fails over automatically - Faster market entry by connecting to whichever PSP already has coverage in a new geography ## Online vs Offline Global Payment Considerations Global payments work differently depending on whether you are processing online (card-not-present) or offline (card-present) transactions. For online businesses, the primary concerns are checkout conversion, local payment method availability, and 3D Secure authentication flows that vary by market. A checkout page that works well in the US -- simple card form, no authentication step -- will lose customers in markets where bank redirects, two-factor authentication, or instalment selection are expected. For offline businesses, the challenges are different: terminal hardware and certification vary by country, contactless limits differ, local card scheme support (Cartes Bancaires in France, girocard in Germany) requires specific terminal configurations, and tax receipt requirements add complexity. Multi-country POS rollouts require managing different acquiring contracts, terminal fleets, and settlement accounts per market. Businesses that operate across both channels -- known as unified commerce -- face the challenge of reconciling online and offline transaction data, managing a consistent customer experience, and maintaining a single view of payment operations across markets and channels. ## Building Global Payment Infrastructure for Platforms For platforms -- SaaS companies, marketplaces, and software businesses that facilitate payments for their customers -- global payments add another dimension of complexity. You are not just processing your own transactions; you are building payment infrastructure that your customers rely on across markets. This is where the concept of a payment layer becomes critical. Rather than hard-wiring a single PSP into your platform, a payment layer abstracts the complexity of multiple providers, currencies, and local methods behind a unified API. Your customers get a seamless payment experience regardless of which country they operate in, and you can add new markets by connecting new PSPs without re-architecting your integration. Shuttle Global helps platforms solve exactly this problem. Our infrastructure connects to multiple PSPs across regions, handles the orchestration and routing logic, and lets platforms offer global payment capabilities -- including embedded payments and voice checkout -- without building and maintaining the plumbing themselves. If you are a platform expanding internationally, explore how we work with platforms or book a discovery call to discuss your requirements. ## Frequently Asked Questions ### What is the difference between a global payment gateway and a local acquirer? A global payment gateway is the technology layer that connects your checkout to one or more acquirers and processes transactions across markets. A local acquirer is the financial institution that actually settles the transaction with the card network in a specific country. Many global gateways offer their own acquiring in some markets and partner with local acquirers in others. The distinction matters because local acquiring delivers better approval rates and lower interchange fees than cross-border acquiring. ### How can I reduce FX costs on international payments? Three strategies help reduce FX costs. First, settle in local currencies where possible to avoid double conversion. Second, use local acquiring so that transactions are processed domestically and avoid cross-border interchange. Third, compare FX markups across PSPs -- the spread above mid-market rates varies significantly between providers and is often negotiable at scale. ### Do I need a separate PSP for each country? Not necessarily. Large PSPs like Stripe and Adyen offer local acquiring in dozens of markets through a single integration. However, they may not have the best rates or coverage in every market. A multi-PSP approach -- using a payment layer, with each market on the provider you chose for it -- gives you the benefits of local acquiring without the complexity of managing many separate integrations directly. ### What approval rate improvement should I expect from local acquiring? Businesses typically see a 5-15% improvement in approval rates when switching from cross-border to local acquiring. The exact improvement depends on the market, card mix, and transaction profile. Markets with strong issuer preferences for domestic transactions -- such as Brazil, India, and parts of Southeast Asia -- tend to show the largest improvements. ### How do platforms handle global payments for their customers? Platforms typically start by integrating a single PSP and passing through its capabilities to customers. As they scale internationally, they move toward a payment layer approach -- an abstraction that sits above multiple PSPs, with each market on the provider you chose for it. This lets platforms offer embedded payments with global coverage without requiring their customers to manage PSP relationships directly. ## Related Reading Explore More ### How to Connect Global Payments to Twilio for Voice & IVR Payments ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [local acquiring for international payment collection](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [PSP-neutral vs single-PSP strategy](/guides/psp-neutral-vs-single-psp/) - [embedded payments](/guides/what-is-embedded-payments/) - [explore how we work with platforms](/platforms/) - [book a discovery call](/discovery/) - [multi-PSP approach](/guides/psp-neutral-vs-single-psp/) - [GuideHow to Connect Global Payments to Twilio for Voice & IVR Payments→](/guides/global-payments-twilio-integration/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-bpos-are-turning-every-call-into-a-payment-opportunity/ --- # How BPOs Are Turning Every Call into a Payment Opportunity | Shuttle > For years, Business Process Outsourcers (BPOs) have perfected the art of conversation. A customer calls to renew, pay, or settle an account. # How BPOs Are Turning Every Call into a Payment Opportunity By Nick Dunse, October 17, 2025 For years, Business Process Outsourcers (BPOs) have perfected the art of conversation. A customer calls to renew, pay, or settle an account. For years, Business Process Outsourcers (BPOs) have perfected the art of conversation. They've automated workflows, trained agents, and delivered millions of customer interactions on behalf of the world's biggest brands. Yet, in many contact centres, the moment that matters most -- the payment -- still sits outside the flow. That gap is closing fast. A new generation of BPOs is realising that every customer interaction is also a potential transaction. With voice and payment layers now converging, they're turning calls into checkouts and support lines into revenue streams. The Missed Moment in Customer Experience Every BPO leader knows this scenario. A customer calls to renew, pay, or settle an account. The agent solves the problem, the customer agrees to pay -- and then everything slows down. - "Let me just open another screen." - "Can I read your card details?" - "I'll send you a link to complete payment." Momentum dies. Trust fades. The call that could have ended with revenue ends with follow-up admin. Multiply that by thousands of calls, and the opportunity cost is staggering. From Service Lines to Revenue Lines The smartest BPOs are flipping that script. They're embedding voice payments directly into their contact-centre workflows -- enabling customers to pay instantly, securely, and compliantly while still on the line. This shift turns a traditional cost centre into a new profit driver. Every call can now include a checkout moment. Every agent can close revenue in real time. Every client can report faster cash flow and fewer unpaid accounts. It's not just operational efficiency. It's commercial evolution. The Technology Behind It At the heart of this transformation lies the Payment Layer -- Shuttle's multi-merchant, multi-processor architecture that connects directly into existing IVR, Twilio, or AI voice systems. Instead of forcing each client or campaign to integrate a payment gateway, Shuttle gives BPOs a central, programmable layer that manages: - Secure DTMF capture for PCI-compliant voice payments. - Automatic fallback to Payment Links via SMS or chat. - Routing across 40+ payment processors and acquirers. - Segmentation by client, geography, or brand. The result: one control panel, hundreds of merchants, zero compliance exposure. Why Compliance Is No Longer the Bottleneck Historically, PCI DSS compliance made phone payments a minefield. BPOs needed segregated environments, specialist audits, and manual data controls -- a nightmare to scale across multiple clients. Shuttle changes that. Its PCI-certified payment layer captures and tokenises sensitive data before it ever touches the BPO's systems. Agents, recordings, and CRMs remain completely out of scope. That means BPOs can handle payments on behalf of dozens of clients without inheriting their compliance burden -- a game-changer for multi-merchant operations. Voice + AI + Payment = Agentic Commerce The next wave of outsourcing is agentic commerce -- where AI voice systems, chatbots, and human agents all operate from the same intelligent payment logic. When a customer says "I'll pay now," the system knows exactly what to do. It captures the payment, records the outcome, and updates the client's system automatically. No separate workflow. No delay. No lost intent. This convergence of automation and commerce is redefining what it means to deliver customer experience at scale. Faster Onboarding, Faster ROI For many BPOs, the key to growth is speed -- how quickly they can onboard new clients, deploy campaigns, and deliver measurable value. With Shuttle, a new payment-enabled client can go live in hours, not months. Each client environment is isolated, permissioned, and pre-integrated with their preferred processor. The BPO simply reuses the proven architecture -- no new certification, no duplicate builds. That's scalability by design. Proof in Performance BPOs using Shuttle's voice payment technology have seen: - Payment completion rates increase by 20-30%. - Average handling time drop by up to 25%. - Client retention improve thanks to measurable ROI. When payments flow seamlessly through the same systems that manage calls, performance follows naturally. Redefining the BPO Business Model The traditional BPO model was built on efficiency: answer more calls, faster, cheaper. The next generation model is built on enablement -- turning every interaction into value. By adding payments into the conversation, BPOs move closer to the heart of their clients' revenue cycles. They become not just service partners, but growth partners. That's what Shuttle enables -- a new era of intelligent, transaction-driven outsourcing. Turn Your Calls into Checkouts If your BPO manages voice interactions, it's time to capture the payment moment, not just the conversation. With Shuttle, you can unify voice, chat, and link payments under one compliant, programmable layer -- and start converting calls into cash flow. Explore Shuttle's IVR & Voice Payments and see how leading BPOs are redefining what "customer experience" really means. ## Related Reading Explore More ### Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### How PSPs Get Distribution Into Enterprise Software ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Explore Shuttle's IVR & Voice Payments](/platforms/voice-checkout/) - [GuidePayment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope→](/guides/payment-collection-for-bpos/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-creators-small-business-owners-and-solo-entrepreneurs-can-accept-payments-without-a-shopping-cart/ --- # How Creators, Small Business Owners, and Solo Entrepreneurs Can Accept Payments Without a Shopping Cart | Shuttle > Creators and solo entrepreneurs can accept payments without a website or shopping cart using payment links shared via email, social media, or messaging. # How Creators, Small Business Owners, and Solo Entrepreneurs Can Accept Payments Without a Shopping Cart By Nick Dunse, December 30, 2025 Creators and solo entrepreneurs can accept payments without a website or shopping cart using payment links shared via email, social media, or messaging. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. As a creator, small business owner, or solo entrepreneur, your time and resources are valuable. You're focused on building your brand, delivering your product or service, and growing your audience. But when it comes to accepting payments, traditional e-commerce setups with shopping carts can feel cumbersome, especially if you're selling services, digital products, or one-off items. Fortunately, there's a more straightforward solution: payment links. Payment links allow you to accept payments quickly and securely without the need for a full-fledged online store or shopping cart. Here's how they work and why they might be the perfect solution for your business. ## What Are Payment Links? Payment links are unique URLs that you can create and share with your customers, allowing them to make a payment directly through a secure, online portal. With solutions like Shuttle's Payment Links, you can generate these links easily and tailor them to the specific product, service, or amount you need to charge. Whether you're selling a piece of artwork, offering consulting services, or accepting donations, payment links provide a flexible and user-friendly way to get paid. ## Why Use Payment Links? For creators, small business owners, and solo entrepreneurs, payment links offer several advantages: Simplicity and Convenience Setting up a traditional e-commerce platform with a shopping cart can be time-consuming and complicated, especially if you're not selling a large catalog of products. Payment links, on the other hand, are incredibly easy to create and use. You can generate a link in seconds and start accepting payments right away. Versatility - Payment links can be used in a variety of scenarios. You can share them via email, social media, messaging apps, or even include them in invoices. This versatility makes them ideal for freelancers, consultants, artists, and any business that operates outside of the traditional online retail model. Cost-Effectiveness - Traditional e-commerce platforms often come with monthly fees, transaction fees, and maintenance costs. Payment links reduce these expenses, as you're not paying for features you don't need. Shuttle's Payment Links offer a cost-effective solution by charging only for the transactions you process, helping you keep more of your hard-earned money. Professionalism - Payment links offer a polished, secure way to collect payments. They can be branded with your business name and logo, giving your customers confidence that their transaction is safe and professional. This is especially important for solo entrepreneurs and small businesses that are looking to build trust with their audience. - Security is a top priority when accepting payments online. Shuttle's Payment Links are designed with robust security features to protect both you and your customers. Transactions are processed through secure payment gateways, ensuring that sensitive information is encrypted and safe from fraud. ## How to Use Payment Links Getting started with payment links is straightforward. Here's a step-by-step guide: Sign Up for a Payment Link Service First, choose a provider that offers payment link services. Shuttle's Payment Links are a great option, offering flexibility, ease of use, and strong security features. Create a Payment Link - Once you've signed up, you can start creating payment links. Simply enter the details of the product or service you're selling, set the price, and generate the link. You can also add custom fields, such as descriptions or reference numbers, to keep everything organized. Share the Link - After creating your payment link, share it with your customer. You can send it via email, text message, social media, or embed it on your website. The customer clicks on the link, enters their payment details, and completes the transaction -- all in a matter of minutes. Receive Payments - Once the payment is completed, the funds are deposited directly into your account. You'll receive notifications and can track all your payments through the dashboard provided by your payment link service. ## Integrate with Other Tools - For those looking to further streamline their business processes, payment links can often be integrated with accounting software, CRM systems, or other business tools you may be using. This makes it easier to manage your finances and keep track of customer payments. Use Cases for Payment Links Here are a few examples of how creators, small business owners, and solo entrepreneurs can use payment links: - Freelancers and Consultants: Easily bill clients for one-time projects or recurring services. - Artists and Creators: Sell artwork, digital downloads, or personalized services without the need for a full online store. - Instructors and Coaches: Accept payments for classes, webinars, or one-on-one sessions with minimal setup. - Event Organizers: Collect payments for tickets, donations, or sponsorships for small events or fundraisers. Conclusion Payment links provide a simple, secure, and flexible way for creators, small business owners, and solo entrepreneurs to accept payments without the complexity of a shopping cart. They allow you to focus on what you do best -- whether that's creating, consulting, or growing your business -- while making it easy for customers to pay you. If you're looking for a streamlined payment solution that fits your business model, consider exploring Shuttle's Payment Links. With the right tools in place, accepting payments can be one of the easiest parts of running your business. For more information, check out Shuttle's Payment Links and start simplifying your payment process today. ## Related Reading Explore More ### Embedded Payments Without Becoming a PayFac ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideEmbedded Payments Without Becoming a PayFac→](/guides/embedded-payments-without-payfac/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideHubSpot International Payments: Accepting Cards Outside the Big 5 Currencies→](/guides/hubspot-international-payments/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-instanda-scales-global-insurance-products-with-shuttles-payment-layer/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/ --- # How to Add Secure Payments to Your Twilio IVR (2026 Guide) | Shuttle > Step-by-step 2026 tutorial: enable PCI Mode, install a Pay Connector, add the Pay verb to your TwiML, and take your first PCI-compliant IVR payment on... # How to Add Secure Payments to Your Twilio IVR (2026 Guide) By Nick Dunse, July 6, 2026 Step-by-step 2026 tutorial: enable PCI Mode, install a Pay Connector, add the Pay verb to your TwiML, and take your first PCI-compliant IVR payment on... Building an IVR on Twilio is the easy part: menus, routing, and personalisation are all a few lines of TwiML. Taking a payment inside that IVR is where most teams stall, because card data brings PCI DSS into the picture and nobody wants their infrastructure anywhere near a card number. The good news: Twilio solved the capture side with the `` verb, and a Pay Connector solves the processing side. Wired together properly, your IVR takes card and ACH payments while your systems never see a single digit, keeping you at SAQ-A, the lightest PCI self-assessment. Here is the full setup, current as of July 2026. This tutorial covers the build. For the compliance side (where PCI scope is created on Twilio, SAQ A versus SAQ D, and how to keep card data out of your IVR logs and recordings), see Twilio PCI Compliance. ## What You Need Before You Start - A Twilio account with Programmable Voice - A payment gateway account (Stripe, Adyen, Worldpay, Cybersource, or any of 30+ supported gateways) - A Shuttle account, free to create at merchant.shuttleglobal.com/twilio (you pay per transaction, $0.20 per successful payment, no setup fees) ## Step 1: Enable PCI Mode on Your Twilio Account Twilio requires PCI Mode before will run. In the Twilio Console: - Navigate to Voice Settings - Click "Enable PCI Mode" - Accept the terms and save PCI Mode redacts sensitive payment details from your logs and recordings account-wide. Note that it applies per Account SID and enabling it is a deliberate, one-way choice, so do it on the right account. ## Step 2: Install the Shuttle Pay Connector In the Console, type in the "Jump to" search box and select the Shuttle Pay Connector from the catalogue. Configure it with: - Unique Name: (note this down, your TwiML references it) - Username: your Shuttle instance key - Password: your Shuttle secret key Both keys come from your Shuttle dashboard. ## Step 3: Connect Your Payment Gateway Log into the Shuttle dashboard and create a payment profile with your gateway credentials (for example your Stripe secret key, or your Adyen API key and merchant account). This is the piece that makes the integration gateway-agnostic: your IVR code never changes if you later add a second gateway, switch acquirers, or route different calls to different merchant accounts. ## Step 4: Add the Pay Verb to Your IVR Wherever your call flow reaches the payment step, return TwiML like this: The caller keys in their card number, expiry, and CVV. Twilio captures the digits inside its PCI-certified environment, suppresses the tones from any agent audio and recordings, and passes the card data to Shuttle, which processes it through your gateway. A few options worth knowing: - Tokenise instead of charge: omit to save the card without charging it - Take a deposit hold: add to authorise now and capture later - Set up a recurring payment from the call: add - Attach your own references: parameters flow through to your webhook for reconciliation, and parameters (first name, last name, email) attach customer details - Take ACH instead of card: set `paymentMethod="ach-debit"` and the caller enters routing and account numbers instead (see our guide to ACH payments over the phone) ## Step 5: Handle the Result Twilio POSTs the outcome to your URL: the result status, masked card number, card type, and a confirmation code you can use to find the transaction in your gateway. Update the order, confirm to the caller with a , and carry on with the call. Refunds, captures, and voids afterwards run through the Shuttle API rather than the phone flow. ## Step 6: Test Before You Go Live Shuttle provides a demo application so you can test the full flow without writing your webhook first: map a Twilio number to the demo URL shown in the Shuttle dashboard, call it, and make a test payment against your gateway's sandbox credentials. Then swap in your own TwiML and go live. If you hit an error during testing, it is usually one of Twilio's `` error codes: 64001 means the connector configuration is wrong, 64004 means the `paymentConnector` name in your TwiML does not match the Unique Name you set, and the 64006/64007 family means the connector you are using does not support what you asked for. We keep a full reference of all 15 Twilio Pay error codes and what each one means. ## Beyond Basic IVR The same setup extends without new integration work: - Agent-assisted payments: contact centre agents trigger secure capture mid-conversation using Twilio's Payments API, staying on the line while the customer keys in details they never hear. See contact centre payments. - AI voice agents: autonomous agents hand the payment step to the same secure flow, so card data never enters the AI pipeline. See how AI voice agents take PCI-compliant payments. - Payment links as a fallback: if a caller cannot complete keypad entry, send an SMS payment link mid-call and watch it complete in real time. ## The Compliance Position With this architecture, Twilio handles DTMF capture and suppression, Shuttle (a PCI DSS Level 1 Service Provider) handles the card data and gateway processing, and your application only ever receives redacted results. That keeps your PCI scope at SAQ-A, a far shorter questionnaire than the one that applies when card data touches your systems. *Ready to take payments on your Twilio IVR? Install the Shuttle Pay Connector from the Twilio Marketplace and go live today, or book a discovery call.* ## Related Reading Explore More ### How to Connect Trust Payments to Twilio for Voice & IVR Payments ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### How to Connect Global Payments to Twilio for Voice & IVR Payments ### IVR Payments: PCI Compliant Self-Service Phone Payments ### How to Get Payments Off Your Product Roadmap ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Pay Connector](/guides/twilio-pay-connectors/) - [Twilio PCI Compliance](/guides/twilio-pci-compliance/) - [30+ supported gateways](/payment-providers/) - [ACH payments over the phone](/guides/ach-payments-over-the-phone/) - [all 15 Twilio Pay error codes](/guides/twilio-pay-error-codes/) - [contact centre payments](/guides/contact-centre-payments/) - [how AI voice agents take PCI-compliant payments](/guides/ai-voice-agent-pci-payments/) - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/guides/twilio-pci-compliance/) - [Install the Shuttle Pay Connector](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [GuideHow to Connect Trust Payments to Twilio for Voice & IVR Payments→](/guides/trust-payments-twilio-integration/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideHow to Connect Global Payments to Twilio for Voice & IVR Payments→](/guides/global-payments-twilio-integration/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-to-launch-a-payment-link-feature-in-weeks-not-months/ --- # How to Launch a Payment Link Feature in Weeks, Not Months | Shuttle > SaaS platforms can embed a branded payment link feature in weeks using Shuttle, instead of spending months building payment integrations from scratch. # How to Launch a Payment Link Feature in Weeks, Not Months By Nick Dunse, August 27, 2025 SaaS platforms can embed a branded payment link feature in weeks using Shuttle, instead of spending months building payment integrations from scratch. Talk to us Make enabling payments for your platform and merchant users easy. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. For SaaS platforms, payments have shifted from being a "nice-to-have" feature to a must-have expectation. Whether you're building invoicing software, reservations systems, customer service platforms, or debt collection tools, your merchants increasingly want to accept payments natively within your product. But here's the dilemma: building a payment link feature from scratch is slow, complex, and drains precious engineering resources. Most platforms estimate 6-12 months for a full payment integration, which means by the time you deliver, you've already lost prospects to competitors. There is a faster way. With the right approach, SaaS platforms can launch a fully branded payment link feature in weeks, not months -- without diverting product teams away from core features. Why Payments Can't Wait Merchants don't think of payments as optional. For them, it's an operational necessity. If your SaaS platform can't support their preferred payment processor, they will: Choose a competitor who can. Stick with their manual processes. Or delay adoption until you "catch up." In all three cases, you lose growth momentum. This is especially true in vertical SaaS segments: Invoicing software → Clients expect to get paid directly via the invoice link. Reservations & CX platforms → Payments need to happen during the booking or conversation. Debt collection platforms → Customers want seamless settlement with their PSP of choice. Without a payment link feature, you risk becoming a partial solution -- one that merchants outgrow. Why Building from Scratch Is a Trap On paper, building a native payment link feature seems straightforward: connect to a PSP, generate links, embed them in workflows. In reality, it's a product sinkhole: Integration complexity: Each PSP has different APIs, requirements, and quirks. Compliance burden: PCI DSS, PSD2, SCA, GDPR -- all must be considered. Maintenance overhead: Every time a PSP updates its API or compliance rules, you have to update too. Merchant diversity: One PSP isn't enough; larger merchants insist on using their existing processors. Roadmap impact: Every new PSP integration takes 3-6 months, diverting engineers from your core product. For product leaders, this creates a lose-lose situation: either delay features to build payments, or lose deals by not offering them. Enter the Payment Processor Aggregator The alternative is integrating once with a payment processor aggregator, sometimes called a multi-gateway connector. Instead of building one-to-one PSP integrations, you connect to an aggregator like Shuttle and instantly unlock 40+ PSPs worldwide. That means you can offer your merchants: Their preferred PSPs (from Stripe to Adyen, PayPal to Worldpay). Regional options (SEPA, ACH, local acquirers). Flexible rules for when and how payment methods appear. And you, as the SaaS provider, don't carry the burden of maintaining dozens of separate integrations. Payment Links: The Fastest Path Among all the ways to embed payments, payment links are the fastest and most versatile for SaaS platforms: Hosted and branded → Each merchant gets a payment page styled to their brand. Multi-channel → Links can be shared via email, SMS, chatbots, or voice agents. Workflow-ready → Easy to embed in invoices, reservations, debt settlement flows, and customer service processes. Checkout Rules → Merchants can define conditions such as: "For transactions over $10k, only show ACH." "For EUR transactions, show SEPA instead of cards." "For under £20, only show card payments." This flexibility means payment links don't just help merchants get paid -- they enhance operational control, compliance, and customer experience. A Typical SaaS Example Consider a mid-sized SaaS platform in the invoicing space. Their customers are asking for payment links to be embedded directly into invoices. The product team knows they need the feature but is stuck: Building directly to a PSP like Stripe would take months and only solve part of the problem. Adding support for multiple PSPs would multiply development time and delay other product priorities. By using a multi-gateway connector, the invoicing platform can: Launch a branded payment link feature in 2 weeks, not months. Offer 40+ PSPs to merchants instantly. Allow merchants to set checkout rules to govern how payments appear. Keep engineers focused on their core product improvements. The difference is clear: instead of waiting months to add a critical feature, the platform goes to market quickly, wins deals, and retains merchants. The Roadmap Win for Product Leaders For Heads of Product and VPs of Product, the biggest win is not just speed -- it's focus. By outsourcing payments complexity to a multi-gateway connector: Your roadmap stays clear for strategic features. Your engineering team avoids endless PSP backlogs. Your merchants get the connectors they demand -- instantly. It reframes payments from being a roadmap blocker to being a growth enabler. Closing the Competitive Gap Let's be clear: adding payments isn't just about monetisation. It's about defensibility. Every time a prospect hears "no, we don't support your PSP," you risk losing them to a competitor. In a crowded SaaS market, PSP coverage is often the small but decisive differentiator that wins or loses a deal. By launching a payment link feature in weeks with Shuttle, you eliminate that risk. You can say "yes" to every merchant PSP request -- without slowing your roadmap. Final Thought SaaS growth depends on speed. Your merchants can't wait six months for a payment link feature, and you can't afford to lose them to a competitor who already has one. The answer isn't to build more, it's to aggregate smarter. With Shuttle's Payment Links for Platforms, you can launch branded, rule-based, multi-gateway payment links in weeks, not months -- and keep your product roadmap moving. ## Related Reading Explore More ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-to-maximize-the-travel-boom/ --- # How to Maximize the Travel Boom | Shuttle > How travel businesses can capitalise on the global travel boom with flexible payment solutions. # How to Maximize the Travel Boom By Nick Dunse, February 19, 2021 How travel businesses can capitalise on the global travel boom with flexible payment solutions. Talk to us Make enabling payments for your platform and merchant users easy. And we service a lot of businesses, but we have a big footprint in travel. I've been here for about five years nearly. So I've seen that growth and it's been a great industry to be a part of, and, we offer a bespoke solution for our merchants. Great. Aaron, tell us about Profit Room. Here at Profit Room we've been around since 2008. wE work with hotels directly on their website booking engine and driving those direct reservations from the hotel websites and everything that comes on the front end. Helping with the guest journey and making sure that your business is represented the way that it should be on brands and helping drive those reservations into the hotels. Fantastic. Simon, tell us a little bit about Kount. So Kount are a leading fraud prevention solution. We're technology first we have a pre integration into the shuttle platform. We've been in existence since 2007 acquired by Equifax. A couple of years ago now we're very much a global business working with over 15, 000 merchants. Directly worldwide very agnostic in terms of industry. Ultimately, if you're doing business online there's likely a use case to Kount, but we do work within airline travel and hospitality significantly. Great. Welcome guys and looking forward to having this conversation with you. We here at shuttle have seen a lot of interest in the travel market. A lot of travel players in various parts of the chain want to improve their technology and make the experience better for their merchants. And Alongside those bookings that we've, that I mentioned at the start, that increase in bookings, we've seen a lot of interest fire up in the world of travel and hospitality in the last 12 months as well. But let's talk a little bit more about trends and Aaron, I'm going to , come to you first. I'd love to hear from your perspective, what is happening? What are you seeing as trends over the last 12 months at Profit Room? It's a really exciting time actually when it comes to travel because if you look back in the last couple of years There's been a lot of environmental factors that have played into to travel and tourism and we talk a lot about the pandemic and what happened pre pandemic post pandemic within the pandemic But it's not the only factor that is coming into play these days we have a lot of things going on, inflation War, also the pandemic supply shortage when it comes to different things so there's a lot of things that are going on at the moment and it's ever changing. There's lots of problems or rebounds, effects from all of these things that are happening in the world today when it comes to travel. What's really interesting to see, I think from my perspective, given all of these things, especially, the likes of the inflation and so on. You would think that most bookers are going to be more conservative when it comes to travel, that they're going to really be skimping on their travel or really think about how much they're spending and how they're spending it. But we're actually seeing the opposite kind of effect. People now they're not really worried about splurging out on travel. In fact, they're going the other way and saying You know what? We've got the opportunities right now. Let's travel. Let's live it up. Even if we have to spend a little bit more than what we can actually afford. And that's where it's going. The type of travel has changed though. People before, a couple of years ago, they would, book a room in a hotel and then they would go out and look for what they're ever... Do they want to do and what's around in town people now are actually looking for destinations They're looking for experience and activities. So when they're booking their travel They're not just going to look for a hotel that they can get a good price for the room Maybe breakfast included they want to go to a destination and they want to have a full experience there was a lot of surveys going around this year, and a lot of statistics done on travel bookings. Over 73 percent of travellers want something outside of their comfort zone. So they're really looking for an adventure, they're really looking for something that's gonna shock their lives a little bit, because... They've probably been at home or locked in the apartment for how many months or working from home because the office no longer exists after the pandemic. So like 73 percent of people is a big amount of people to be looking for that type of vacation. So what we're seeing is, especially when it comes to direct reservations, people really need To go into their packages and what experience they need to offer because that's what people are looking for now. They're really going into those adventures and looking for destinations rather than just hotels. I think that's really interesting, isn't it? I think people are wanting the opportunity to not only do something a little different, but actually book all of those experiences potentially before they get to the destination or as early as possible, at the very least discover what those experiences might be. And so giving them the opportunity to book something is open is there, right? And I don't know if you will. Thinking about doing some of those things, Aaron, over at profit room. You look, you smile, so maybe you are, I don't know. Tell me. Yeah, definitely. Packages is definitely part of the, what we offer at profit room and that's where we shine when it comes to the booking engine and websites. we've also got some great integrations going on at the moment when it comes to activities as well, too. actually capture your outside activities that you offer from the hotel. So maybe, you're going to Africa, you're looking to book a safari as well within the package stay, and that is offered by an external system. So we're actually integrating that into the booking process so that you're also booking automatically those activities along with your package and stay at the hotel. Nice. We'll come back to some of that in just a moment, Harry, you can go first and actually talk a little bit about some of the trends that you might be seeing since the last 12 months and this increase in travel. What have you guys seen over at Ecompay? Yeah, 2022, we start to see travel come back into full force, the hockey stick effect, a lot of people called it where the demand was starting to increase, and I think a lot of that's based on the fact that when people couldn't travel, they didn't spend that money that they would use, they saved it. They put it away and went when we can travel, we will go. And in 2022, we started to see parts of that, and obviously that was hampered by inflation, war, and various other things. But now in 2023, those shackles are less. Not there, but they're less. And people are starting to go I really miss traveling around the world and doing certain things. So I'm going to really go for it and, stretch that bit further to get that extra experience. Additionally, I've noticed that a few of my... My friends have started to work from home, but not home somewhere in Italy, somewhere nice or wherever. And that's still, incorporated within that. So they're still doing their online works and webinars and and doing zoom calls and so forth. We're doing it from a beach or from a various locations that's a really interesting development, and it just means that the volume of traffic in terms of processing revenue is still there. But the number one thing we've seen amongst our merchants is looking at additional payment methods. So you mentioned Americans coming over to Europe a lot more, they're buying from suppliers, they never have so having that additional sort of payment methods in there and also a certain seal of approval, I think it's been really interesting. Google and Apple pay being the most obvious one because, I use Google and Apple pay when I go down the shop. So why not use it online? And that argument has become increasingly strong amongst all people. It's not just millennials or Gen Z, but it's everyone, my mum and dad included, and they're in their 60s. Yeah, it's an interesting trend. And the really nice thing is we're seeing some of these travel merchants really refill their coffers after a tough couple of years. And just one quick one as well. This summer for Australia and New Zealand is the first summer that Australia has been fully open. So any merchants that are specializing in that area are only just getting the full whack of the return. And it's really cool to see. Brilliant. Aaron, you can finally get back to Australia. There you go. Simon coming to you with all of this boom, extra booking more payment volume happening from everyone keen to travel again, you must be seeing some trends in terms of both friendly for fraud and intentional fraud from criminals. Yeah, absolutely. Those the volumes of orders going through and transactions related to. Travel and hospitality. Definitely right up there again. I think 2024 will actually be over and beyond pre pandemic levels. So clearly everybody is getting back to going on holiday and maybe even putting more emphasis on, holiday vacation and having fun than pre pandemic. But from a fraud perspective globally, we do see many differing challenges. Really for a variety of reasons some of that specific to region certain payment types being prevalent in some countries That you know, maybe are still growing out their maturity around ecom and payments Latam for example, you know heavily reliant on payment links which can be shared over text message You know clearly not the most secure payment method and fraudsters generally more often than not, they're very good at what they do very effective at spotting weaknesses and then targeting at scale, whether that is specific to a region or a vertical. Traditionally, hospitality bookings has always been quite a big target for fraudsters. I think what bookings hospitality and airlines all suffer with is their reliance often on third party marketplaces completing bookings for them. And on their behalf, they lose some control over their four strategy um, and as a result, they're unable to deploy this single fraud strategy. And internally as teams, what we... have seen with COVID is, whilst the numbers are back in terms of bookings, internal staff and headcounts tend to be, lower than pre pandemic. So that should, hopefully see more of a trend coming over to automation of solutions and having a tech led approach to things like fraud prevention. But, we talked about LATAM emerging markets for payments. Even within Europe, from a trend perspective, we've seen the implementation of SCA, which as a result by its design was put in place to reduce fraud. But what it's seen is fraudsters kind of pivot and maneuver from their traditional methods. And the scale hasn't necessarily been there. within travel for fraudsters because of SCA, the general sort of standard credit card fraud that SCA is fairly good at combating, but what they're seeing is that they're completing fewer fraud attacks on higher value items and that has, added even more fraudsters to the way of travel given the given the sort of, the instance of travel booking. Tends to be digital, you're making that payment. It's not necessarily a shippable good. It's a downloadable ticket and also you're buying it way in advance of actually, The booking or the flight taking place so that leaves a big sort of Avenue Or fraudsters to, take effect. Within Europe, like I say, SCA, it's changed how fraudsters are necessarily targeting airlines and booking industry. But whilst the volume of fraudulent instances have reduced, the actual value of fraud has remained the same. Because happening less often, but happening on higher value options. it's interesting, isn't it? We've seen more and more fraud protection services come to the market, and yet we still see an increase in fraud because the counter is that there's more and more fraudsters out there, and despite best efforts it takes a while for people to adopt the right tools and the right practices to actually protect themselves , around what's going on. Cool. What I've seen happening in the last 12 months is The increase in direct booking. So yes, we have these aggregators, these marketplaces for channels. We have tour operators and online travel agents. But I think one of the key things, and it's really thanks to Mr. Google. So thanks so much Google, but they've opened up the ability for hotels. To compete, at least in search with some of the aggregators and marketplaces and get their offer out there. And Aaron, I suppose that's been helpful for you guys over profit room because you can give the hoteliers the tool sets that they need to actually run their own bookings like I was saying people aren't worried about booking travel now or spending money on on experiences. But they're still looking to save their money. They don't want to flush it down the toilet, so they've just shifted the way that they're actually saving money and most people now are looking for great packages, great deals, great specials online, and they're searching more and more for those for those good deals. Online which gives us a unique advantage and why the increase in direct traffic has been so extreme lately because people are really on the search and yeah, like you said, thanks to google they're searching they're looking and they're finding the best deals if you're giving that to them on your direct website. So it's unique Or a new kind of technique of really searching out for the best deals available and not just going directly to your common OTA channel and booking the reservation there, but really searching for that deal is is really helping drive direct revenue to the hotels. Harry, I'd love you to comment on some of those some of those things that you're seeing around the world, especially in regards to like local payment methods, where actually the hotel is now able to sell direct and accept payments directly. As well but do it in a local currency if they've got local bookers. Yeah, it's really important to have those local currencies people will feel more ease paying in the currency. They recognize with the payment method they recognize In fact, I know a few travel merchants that use the payment methods or the currencies as a selling tool So they'll say we have this payment method book a flight with us as opposed to book a flight with us. We have this payment method and it's a really effective tool and it's something I recommend to all merchants to use because that's the sign of credibility to a certain extent for especially new customers. But more, moreover, it's about the kind of capitalizing on those new emerging markets. I think Latin America is a really interesting area really hard area to get involved in, particularly from the payments industry, but any industry really. So doing your research on those payment methods, what's around. Then using your payment provider, if they can, to facilitate access to those methods and the currencies. I think it's critical. Asking someone in Argentina to use USD, it could be the reason why they don't book with you, for example. Let me slide over to some of these challenges that we might see currently in the market and merchants might be facing. And I'll probably come to you, Simon, to ask you about your experience with some of these challenges, specifically fraud. With increased bookings and things like chargebacks there's the opportunity for... Merchants to face a kind of myriad or an increased volume of these challenges. What have you seen at Kount that your customers have been facing challenge wise? Yeah, sure. Yeah lots and lots of, challenges and yeah, chargebacks is a fairly new one. Mentioned it already, but SCA in Europe. Whilst that's cut off some of the pre authorization types of fraud, what that has done is push a lot to more friendly fraud. So chargebacks for holidays is becoming fairly popular. For a myriad of reasons, some of them almost laughable, where people are. Sold a holiday when they're looking through the brochure, they see sunshine and fantastic whether they go on holiday and then try and launch a charge back when they get back to say it was raining for the for the entire time that they were there. But whilst that is rare and almost laughable. There is a new window with chargebacks and I think chargebacks always were that well known with consumers. If I have a problem with a product who would I take up that problem with? I think, a lot of people would automatically assume the merchant that you made the purchase with, but chargebacks open up a new window of opportunity where you can go to your issuing bank. And make a claim and there's a widespread belief within the merchant world that consumers have too much of a commanding position within charge backs. So we are seeing especially with COVID people not being able to go on holiday because they've got COVID. Maybe some travel businesses, travel agencies not, being able to come out. cope with the demand of refunds, maybe not having the clearest kind of message around their refund policy. And then, instantly being met by chargeback requests from consumers. This led to, a number of issues. Ultimately, the more chargebacks you get raised as a business the more questions get raised by the banks that are working for you. And that can lead to a number of challenges. But then internal internally from a chargeback perspective very difficult to maintain. So being able to, cut them off straight from the off we'd count as a preauthorization fraud tool. We're ingesting chargeback data and it tends to be that if a consumer has completed chargebacks on one product, they will have done it on multiple products. There is a bit of a belief that it's a gaming of the system a lot of the time. So being able to identify these known individuals completing chargebacks and you making a decision on how you want to work with that customer can be very important. But yeah, we've seen a high a high rise in different types of frauds around travel. We've talked about um, the shopping around of customers and everybody looking for the best price that has led to a rise in the resale of travel tickets online. Thank So a fraudster actually purchasing tickets with a with a stolen credit card or logging into somebody's account, performing account takeover, purchasing tickets, reselling them online to an unwitting consumer. And often the only way that consumer realizes they've brought a a fraudulently. Issued or resold ticket is when they get to the airport to say to be greeted that they can't actually get on board of that plane. Number of different issues what we're also seeing is as well as the resale piece is something called triangulization fraud. So this is where again, somebody is shopping around for the best. price online. They're being greeted by a fake website offering an amazing price. Purchasing that ticket as they believe they're, rightly ordering completing that order. And actually purchasing a ticket for somebody else. You've got this triangulation fraud with the fraudster sat in the middle One individual consumer buying a ticket. They're actually buying that ticket for another individual who uses the ticket makes the payment to the fraudster that goes and flies on this airplane journey only for the third person who's actually made the payment for it to, to realize that they've got nothing in the realms of what they believe they were paying for. So lots and lots of different instances, all different types of fraud, all leaving a consumer out of pocket and leaving, a merchant with a fraud record. . I hadn't even realized that. that people would be effectively buying and reselling tickets for travel. But of course it happens in other industries all the time. And I guess that's one of the advantages of going direct as you can to the place where you want to stay or the travel operator that you want to actually travel with Aaron, what is keeping your customers up at night at the moment? There's several things I think from our perspective. That is. A bit of a challenge in the industry for now. One of them is the operational side of things. So after the pandemic, and with all of the stuff that's been going on in the world there's not as many workers or it's not as affordable as to keep workers within the hotel. at the moment. So operationally speaking it's a big challenge if you don't have your systems automated. So I think that's one of the big challenges in the industry. We just don't have the staff and utilizing the staff that we have for the guest experience rather than, there's nothing worse than going into a hotel and there's a receptionist standing at the desk, like typing in every piece of data, taking manual charges. At the hotel when they get in, they're like, okay, you have 19. 35 left, like nobody wants to do that anymore. So I think one of the things that we work a lot with hotels is really automating their check in process. Knowing your segments as well is a really big thing, I think, within the industry now. There, there's so many channels and there's so many platforms out there that you can really book over. And people are searching everywhere. So I think it's important for hotels. Nowadays to really target the segment that they're looking for, it could be corporate travel and it could be leisure travel. It could be, 20 to 30 year olds or 50 to 60 year olds, depending on what you're offering has really targeting that segment and how they search for reservations or all those packages is really important at the moment. And of course, the guest journey, I think, is probably the next big challenge there. It's so important, I think, that the guest enjoys their experience when they're searching, when they land on your website, the whole way through knowing what's on offer and what exactly they're booking, the policies around what they're booking. Like I said, I think the days are over where you just book at a hotel and then you turn up three months later and you go in there with your credit card and they like take a picture of your credit card and start putting it through some machine or something. Those days are gone, like we, we shouldn't have that anymore. Things like scheduled payments. Having those policies set up so that the guest knows exactly what they're expecting when they're going to pay there might be an upfront deposit of 50%. Two weeks before check in date, they get another 30 percent and then the day of arrival, they pay the last installments and then they arrive at the hotel. It can all be automated and it doesn't require anybody to be doing this manually anymore. When it comes to payments, I think it's a big problem as well within Within that section, there's nothing worse than going through an entire process of booking, which with Profit Room is fantastic, because it's very short and very simple. But then you get to the checkout, you put in your card details, and for some reason the card gets denied. You can't find the alternative payment method you want to book with. Maybe it's not, Apple Pay, whatever it might be, isn't available on the platform that you're booking with, especially when it comes to direct reservations. As you said, in LATAM, there's so many different alternative payment methods that they use there. Trying to offer that to all of your clients worldwide is a really big challenge and making sure that you capture those reservations. So that's where Shuttle and platforms like that really come into play because not only can you... Capture those reservations, but if there's an issue, you can orchestrate that there's fallbacks that it's routed in the right direction to really capture all of those payments around the world and not miss any of those because whatever provider you have isn't necessarily. Supporting that at the moment. So it's a really big challenge. I think payments is a really good one to, to talk about because, at the end of the day, if the payment fails, the reservation fails and you don't capture that inventory. Really having a focus on that, I think is a super important thing at the moment and how you're going to make sure you really captivate all of those bookings. There's some gold there. I hope everyone listening or anyone listening in the future can take some of that away, but I think you're right. The kind of experience with travel starts with the search and the booking. And actually for me, that does influence my choice of who and how I book myself. And I've been traveling personally and professionally a little bit. Lately staying in different hotels using different modes of transport and it's really amazing the experience, the difference in experience when you come to, let's say, check out or even get onto a train or a plane, like how they deal with you, you might be at a hotel, you're trying to check out and you're looking for the one staff member that they've got on because they have to be lean and you just need to check out and get out of there, but you can't until you actually, Give them your key back and they charge you manually, but others, you can drop your key in somewhere and check out online or whatever it might be. And they can just charge the card on file. It's so convenient. It really comes down to that customer convenience now and making things convenient typically is actually operationally smart for the hotel as well. I think so it's been a sort of seismic shift in terms of the experience, but there's a lot of, a lot of difference between the good performers and the not so good ones out there right now Harry tell us a little bit just on the payment stuff in terms of how you guys might work with a merchant, a hotelier to actually help them understand the payment landscape and help them accept more Transactions, because I know you do that. That's part of what EconPay is great at actually sitting alongside a merchant and helping them accept more payments at the end of the day. Yeah, the first thing I do is I look at their web traffic, where is it coming from? And then I compare that directly with where their booking is coming from. And just see if there's an instant optimization there by adding a payment method because they get, I don't know, a lot of Dutch visitors to their website, but their Dutch conversion is 0. 1%. I look at their website, they don't have ideal. You add that and you instantly convert, twice, three times, even four times that traffic. So that's a quick win, easy, ready to go. But then the additional thing is also being smarter with how you approach the customers. Like we talked about payment links previously between us, obviously as being an alternative to virtual terminals or moto bookings, where the customer may not feel comfortable giving you their card data over the phone. There's also things like IVRs. And this is when the set, the handset of the customer can be used to enter the card data again. So the customer feels more protected, but also so your staff are protected from PCI risk. So there's lots of different things that can provide extra balance to your overall payment offering. And I think. Merchants, not just hoteliers and travel merchants need to consider payments as a part of their offering, you do all that work with your marketing to make your website look great, make the holiday look amazing, you get all these best suppliers and the rest of it, and it can all be undone by just having a bad checkout experience, and we all know that it's a golden rule. It's an easy thing. You talk about a lot on LinkedIn, and, that is a really small and easy way of making things a lot easier for you. And we touched on chargebacks in Simon's piece there. I think that's a really interesting piece to be, because chargebacks are one of these things that consumers will do for literally anything. So what you need, and this is where I'll do an internal plug for us, is a payment provider that is willing to fight some of those chargebacks for you, and to really Deep take a deep dive into what went wrong when you lose a charge back so that you can basically prevent those sort of situations happening again, whether that mean editing terms, conditions, editing, payment flows, whatever it is those sort of little things can be there the marginal gains that people talk about. The the British Olympic team always talk about marginal gains. How can we get that extra two, 3%? And that's what I think everyone should apply in not just business, but your life as well. How can I get that two or three extra percent from everything that you're doing? And payments is not away from that. It's definitely something you should be using. And broadly speaking, using your payment provider. Go demand things from them, go knock on their door and say, we want this, we need this is a problem, don't just accept it as the status quo, because we will do it, we just need you to push us in some situations, obviously not us, we'll do it without asking, of course but some providers, they do need to push and, it's definitely within your right to do yeah, absolutely. And I think, the reason that we're having this conversation, the reason that we're in the businesses that we are in is so that merchants can actually sell more, right? They, that that's what they want to do. They want to make more money, but ultimately they need to do that by selling more. And so if you can increase the sales by one or 2 percent across the board, That actually outstrips a lot of the savings or the hard negotiations you might have around, your booking platform or your payment provider chopping off 0. 1 percent or even, driving down some other costs that you've got in the business, actually, if you're smart about actually creating a great experience and selling more and ultimately, I talked to Simon a little bit about that too with reducing those, reducing the impact of negative sales. That, that's what you want to do. You want to drive up conversion and and have more customers at the end of the day. And I'll just shift this on as we come towards the end of our session today to think about, some takeaways or some things that you guys would have. Merchants focus on if they want to optimize and improve their processes, some of the things you've already mentioned, but I guess maybe if you've got one or two or even three things that you'd want people to focus on in their business from your perspective, that would actually make a one, 2 percent difference to their sales. What would those things be? Maybe Simon, you can go first, but what would you say? What should people focusing focus on or optimize just to really ultimately sell more So I think it segues nicely into this from the previous conversation as well. But yeah, margins are often very low in travel at the point of payment. It's when get things get real from a consumer. it Could be spending two or three thousand pounds of your hard earned money on a holiday, that you're going to get to do once a year. So it's a big event for you as an individual consumer putting all of that money and trust into one payment. You need to make sure that the company that's taking that money, has got the adequate processes in place to make sure that you're not at risk for fraud. But then vice versa, the company that you're making that booking with. If you're a a hotel and you need to sell, 150 out of your 200 rooms every night to be making money. Every one of those bookings is really important and to get somebody, cancelling 24 hours before sort of anything like that or be a victim of fraud, it creates a massive impact and at that point of payment there's a real richness of data. A takeaway would be. You know at that payment event, you know utilize that data that you were seeing as a business what that can mean Potentially it can be you know a strategy like harry has said around, presenting a certain payment type it can be you know, knowing an individual who's cancelled on you before and only offering them a You know pay at the point of booking rather than pay at the end of your stay, but just layering in that intelligence and yes, everybody wants to stop fraud, but What we also want to do is identify trust at the same time. So layering in, solutions and technology to give you confidence and, often fraud can be seen as cost, a cost of doing business online, but switching that mindset and also the mindset that deploying any kind of fraud tool is actually going to increase false positives incur additional internal operation costs for working through those false positives. Or, decreasing customer experience or stopping, good orders coming through. It really has flipped from that as a, a technology first industry around. Yes, stopping fraud, but identifying that trust. So these marginal gains that Harry talked about and increasing approvals by identifying and giving confidence to your customers. The right ones that deserve good customer experience, give it to them versus those that shouldn't be accessing your service at all, or should only access it in a way that you are comfortable as a business as. yEah, just, using the technology that's out there, layering in, some of the intelligence that you can derive from the online interaction that you're seeing, this digital persona that you're able to really home in on when you're seeing somebody doing business on your website and using that as a way of, increasing revenue. There's a lot of technology that can really help businesses grow. It's. I suppose working through what's available through, maybe different platforms that you're using, as a bolt on service, and then, maybe holding some of those third parties that you work with and you sell your goods as well to account a little bit more, making sure you're working with businesses who have got your best interests at heart, and that can be, them having a a layered fraud prevention solution within their own technology. Yeah, that's good. And I like the overarching point that actually building understanding of your customer base and a relationship with them helps you build trust and marry experiences to them. I think that's really important. And it comes back to that point we were talking about earlier with the opportunity with direct bookings just to know those repeat customers versus new customers. And perhaps some of those processes that you might want to put in place for the different types of audiences really helps and rewards those those guys that are coming back to book with you again. Aaron from your perspective. What are those things that people can take away? I know you had a good list before but what would be your couple of things that people should walk away with Yeah I think there's just a few main points. For me, the best one operationally is always work smart and not hard, There's so much technology out there available to us these days, really look at your tech stack make sure that all of those pain points that you have within the hotel, within the guest experience, within the checkout session, whatever it might be there's technology out there to ease those pains. Really think about that. Make sure you have the right tech stack for your business and make sure that everything works for you. If you're having trouble with fraud, maybe account can help. If you're having trouble with payments, maybe e com help can pay. There's so much out there that you can look at too. So really make sure that your technology is working for your business and that it's going well. The second, I think the biggest point, which is always a massive one of mine is knowing your brand as well. So really. Knowing that, your logos, your colors the brand of your website, the brand of your product is really on, on key the whole time from the whole guest experience, make sure that everybody knows what brand that they're looking at and then it stays with that brand that applies also to follow up emails to maybe email campaigns afterwards. Abandoned carts, anything like that. All of these products that help within the booking experience or to retain those guests make sure it's on brand and make sure that you have everything on the brand of your products. The more you improve that guest experience, the more that you have a really nice flow and make sure you do it yourself, make sure you go through the flow, do your whole booking process because it's going to have those guests coming back to you when they go home. Those guests are going to say to. Their friends, their family. Oh, I had such a great stay, I booked at this hotel and everything was perfect from the start to the end. It was so easy, I didn't have to do anything. I got there, they greeted me, took me to my room, everything was done for me. And that word of mouth is going to go around as well. There's reviews online that you're going to get. And the more five star reviews you get, the better it is for your business, the more money that you make. So really make sure you take care of that guest experience and that all of the technology is working for you properly. Yeah. Awesome. Like that. Harry, what can you leave those listeners with today that would actually make a difference to them? Yeah, there's some absolute gems in what Aaron's just said there, but the one thing I wrote down was don't settle. The travel industry is a very old industry in a lot of ways, very traditional industry where people still pay for stuff over the phone, even send checks for their holiday bookings. I know it's rare, but it does happen. But I think the one. positive. One of the few positives come out of the pandemic is a lot of these companies become more tech savvy, more aware that there are much greater things they can do with their websites and with their payment flows and with their online experience for their customers than simply show a brochure, customer books. There are so many more things they can do now. And I think the key is to look at partners that can help you do that. But also any partners that you have pushed to get the perfect experience, if you're getting the just about experience, you should be asking the question, I think the British kind of have this attitude of that will do, when we're asked how we are. Lots of people say not too bad, things like that. But I think if the industry really tries to change that and become okay We don't want, you don't want to let perfect be the enemy of the good, but you also want to look at how you've made things better. And I think the travel industry is no, it's not absorbed from that. It's not just retail that has to keep changing. It's also industries like travel. So yes, that's the number one in terms of just don't settle for. what you have and always look for the things that can make it better. We talked about currencies, payment methods, experiences, that stuff will source itself out as you look at to, look to add all these other payment methods and other technologies that are out there. But yeah and remember as well that the travel industry is a fun industry. It's an experience industry. It's about giving people the best time of their lives for the however long they're going on that holiday. So I think maintaining that, that wonder. With how you engage with your audience, I think it's also really important. That's great, guys. Really helpful. And from each one of you some great perspective and gems that people can go away and implement. You're right, effectively travel is a, is about an experience. And as consumers in a digital economy now, our expectations for experience. Is not only lifted and elevated to a new level constantly, but that there is a expectation across the board, regardless of what we're dealing with, whether it's travel, retail food and beverage, whatever it might be, we expect that consistency of because technology has facilitated that. So thank you so much from Aaron from Profit Room, Harry from Ecompay and Simon. From count and me, myself Nick Duns at Shuttle. ## Related Reading Explore More ### Payment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuidePayment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel→](/guides/travel-platform-payments/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuideAI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent→](/guides/ai-voice-payments-hotels-travel/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-to-prevent-chargebacks-using-ethoca/ --- # How to prevent chargebacks using ethoca | Shuttle > Learn how Ethoca helps merchants prevent chargebacks by resolving disputes before they become formal claims, reducing lost revenue and processing fees. # How to prevent chargebacks using ethoca By Nick Dunse, January 3, 2026 Learn how Ethoca helps merchants prevent chargebacks by resolving disputes before they become formal claims, reducing lost revenue and processing fees. Talk to us Make enabling payments for your platform and merchant users easy. Chargebacks are a mechanism that allows consumers to dispute transactions and request refunds from their banks or credit card issuers. This process is designed to protect consumers from fraudulent activities and ensure that they are not held liable for unauthorised charges. However, for merchants, chargebacks can pose significant challenges. They not only result in lost revenue but can also lead to increased fees, damage to reputation, and potential penalties from payment processors. Understanding the intricacies of chargebacks is crucial for businesses aiming to maintain healthy financial operations. Ethoca is a global provider of collaboration-based technology solutions that help merchants and card issuers reduce chargebacks and improve customer experience. By facilitating communication between merchants and banks, Ethoca enables businesses to resolve disputes before they escalate into chargebacks. This proactive approach not only mitigates financial losses but also fosters a more positive relationship between merchants and their customers. By leveraging Ethoca's capabilities, businesses can enhance their chargeback management strategies and ultimately protect their bottom line. - Understanding chargebacks is crucial for businesses to effectively prevent them using Ethoca - Implementing Ethoca can significantly reduce chargebacks and improve business operations - Best practices for preventing chargebacks with Ethoca include proactive monitoring and real-time alerts - Utilising Ethoca's network allows businesses to collaborate and prevent chargebacks more effectively - Integrating Ethoca into business operations requires thorough training and ongoing support for staff - Case studies demonstrate successful chargeback prevention with Ethoca, showcasing its effectiveness - Future trends in chargeback prevention with Ethoca may include advanced AI and machine learning capabilities ## Implementing Ethoca to Reduce Chargebacks ## Reducing Chargebacks through Timely Intervention This timely intervention can significantly reduce the likelihood of a chargeback being filed, as many disputes arise from misunderstandings or miscommunications that can be resolved quickly. ## Integrating Ethoca into Existing Systems Integrating Ethoca into existing payment processing systems is a critical step for businesses looking to reduce chargebacks. This integration typically involves working with payment gateways and processors to ensure that Ethoca's alerts are seamlessly incorporated into the transaction workflow. Proactive Insights and Enhanced Customer Satisfaction Once set up, merchants can access valuable insights into transaction patterns and customer behaviours, enabling them to identify potential issues before they lead to disputes. By adopting this proactive stance, businesses can not only reduce chargebacks but also enhance overall customer satisfaction. ## Best Practices for Preventing Chargebacks with Ethoca To maximise the effectiveness of Ethoca in preventing chargebacks, businesses should adopt several best practices. Firstly, maintaining clear communication with customers is paramount. Providing detailed product descriptions, transparent pricing, and clear return policies can help set proper expectations and reduce misunderstandings that may lead to disputes. Additionally, ensuring that customers receive timely updates regarding their orders can further enhance their experience and diminish the likelihood of chargebacks. Another best practice involves regularly analysing chargeback data provided by Ethoca. By reviewing trends and patterns in chargeback occurrences, businesses can identify specific areas for improvement. For instance, if a particular product consistently generates disputes, it may warrant a review of its description or quality assurance processes. Furthermore, training staff on how to handle customer inquiries effectively can empower them to resolve issues before they escalate into chargebacks, thereby fostering a more customer-centric approach. Utilising Ethoca's Network to Prevent Chargebacks Metrics | Data Number of chargebacks prevented | 500 Percentage reduction in chargeback losses | 30% Number of merchants utilising Ethoca's network | 1000 Average time to prevent a chargeback | 24 hours One of the standout features of Ethoca is its extensive network that connects merchants with card issuers worldwide. This network facilitates collaboration between parties involved in a transaction, allowing for swift resolution of disputes. By utilising this network, merchants can gain insights into customer behaviours and preferences, which can inform their strategies for preventing chargebacks. Moreover, Ethoca's network enables merchants to share information about fraudulent activities or suspicious transactions with other businesses. This collective intelligence helps create a safer environment for all participants in the payment ecosystem. By being part of this network, merchants can stay ahead of emerging threats and adapt their practices accordingly, ultimately reducing the risk of chargebacks stemming from fraud. ## Integrating Ethoca into Your Business Operations Integrating Ethoca into business operations requires careful planning and execution. Businesses should begin by assessing their current chargeback management processes and identifying areas where Ethoca can add value. This may involve collaborating with IT teams to ensure that the necessary technical infrastructure is in place for seamless integration. Once integrated, it is essential to establish clear protocols for responding to Ethoca alerts. Designating a team or individual responsible for managing these alerts can streamline the process and ensure timely responses to customer disputes. Additionally, fostering a culture of collaboration within the organisation can enhance the effectiveness of Ethoca's implementation, as various departments -- such as customer service, finance, and operations -- can work together to address chargeback issues holistically. ## Case Studies: Successful Chargeback Prevention with Ethoca ## Reducing Misunderstandings and Chargebacks For instance, an online retailer specialising in electronics faced a high volume of chargebacks due to misunderstandings regarding product warranties. By implementing Ethoca's solutions, the retailer was able to receive real-time alerts about potential disputes and engage with customers directly to clarify warranty terms. Proactive Approach to Billing Issues Another example involves a subscription-based service that struggled with chargebacks related to billing issues. By integrating Ethoca into their payment processing system, they were able to proactively address customer concerns before they escalated into disputes. The service implemented clearer billing notifications and improved communication with customers regarding subscription renewals. Improved Customer Satisfaction and Retention As a result of these efforts, both businesses saw a significant reduction in chargeback rates and an improvement in customer satisfaction. The subscription-based service, in particular, experienced an increase in customer retention rates, demonstrating the value of a proactive approach to mitigating chargebacks. ## Future Trends in Chargeback Prevention with Ethoca As technology continues to evolve, so too will the strategies for preventing chargebacks. The future of chargeback prevention with Ethoca is likely to be shaped by advancements in artificial intelligence (AI) and machine learning (ML). These technologies can analyse vast amounts of transaction data to identify patterns indicative of potential disputes before they occur. By harnessing AI-driven insights, businesses can refine their approaches to risk management and enhance their overall chargeback prevention strategies. Additionally, as consumer behaviour continues to shift towards digital channels, the importance of seamless customer experiences will only grow. Ethoca's ongoing innovations will likely focus on enhancing real-time communication between merchants and customers, ensuring that any issues are addressed promptly. As businesses adapt to these trends, those leveraging Ethoca's capabilities will be better positioned to navigate the complexities of chargebacks in an increasingly digital marketplace. ## What is Ethoca and how does it help prevent chargebacks? Ethoca is a global provider of collaboration-based technology solutions for merchants and card issuers. It helps prevent chargebacks by enabling merchants and card issuers to share transaction data in real-time, allowing them to identify and resolve disputes before they escalate to chargebacks. What are chargebacks and why are they a concern for businesses? Chargebacks occur when a customer disputes a transaction with their card issuer, leading to the reversal of the transaction and a financial loss for the merchant. Chargebacks are a concern for businesses as they can result in revenue loss, increased operational costs, and damage to their reputation. How can businesses integrate Ethoca into their operations to prevent chargebacks? Businesses can integrate Ethoca into their operations by leveraging its network to receive real-time alerts about potential disputes, enabling them to take proactive action to prevent chargebacks. This can be done through API integration with their existing systems or by using Ethoca's web-based portal. What are the best practices for preventing chargebacks using Ethoca? Some best practices for preventing chargebacks using Ethoca include promptly responding to alerts, providing compelling evidence to resolve disputes, and maintaining accurate and detailed transaction records. Additionally, businesses should ensure that their staff are trained to effectively use Ethoca's tools and resources. Can you provide examples of successful chargeback prevention using Ethoca? Several case studies have demonstrated successful chargeback prevention using Ethoca. For example, a leading online retailer was able to reduce chargebacks by 40% after implementing Ethoca's solution, resulting in significant cost savings and improved customer satisfaction. What are the future trends in chargeback prevention with Ethoca? The future of chargeback prevention with Ethoca is likely to involve further advancements in data analytics and machine learning, enabling more accurate and proactive identification of potential disputes. Additionally, Ethoca is expected to continue expanding its network and partnerships to provide even greater coverage and effectiveness in preventing chargebacks. ## Related Reading Explore More ### Stripe Froze My Account: What to Do and How to Prevent It ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Ethoca](https://www.chargeflow.io/) - [GuideStripe Froze My Account: What to Do and How to Prevent It→](/guides/stripe-account-frozen/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-to-scale-ar-without-hiring-more-staff-a-cfos-guide/ --- # How to Scale AR Without Hiring More Staff: A CFO's Guide | Shuttle > Scale your accounts receivable without adding headcount. Learn how automated payment links and workflows reduce manual AR work and improve collections. # How to Scale AR Without Hiring More Staff: A CFO's Guide By Nick Dunse, July 10, 2025 Scale your accounts receivable without adding headcount. Learn how automated payment links and workflows reduce manual AR work and improve collections. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. When growth kicks in, the Accounts Receivable team is often the first to feel the strain. More sales mean more invoices, more chasing, more reconciliation, and more complexity. For many mid-sized businesses, the default response is to hire another credit controller or add more admin support. But what if you didn't need to? This guide is for CFOs and finance leaders at scaling companies who want to reduce DSO, improve cash flow, and future-proof their AR process -- without growing headcount. Let's dig into the tactics that make it possible. 🔍 The Problem: Growth Without Operational Leverage Here's what typically happens in a growing mid-sized business: AR is managed by a lean team using tools like Xero, QuickBooks, or NetSuite Invoices go out via email or PDF, with manual follow-up for overdue accounts Payments come in via bank transfer or card, but reconciling them is tedious There's limited visibility into who's paid, what's overdue, and what's next That's fine when you're managing 20-50 invoices a week. But double that volume -- or double your customer base -- and suddenly AR becomes a bottleneck. And that's when the CFO gets asked:"Can we bring in someone to help with collections?" Before you say yes, consider this: hiring is a linear solution to what should be a systems problem. 🚫 The Case Against Adding More AR Staff Hiring more people feels like the answer. But it comes with hidden costs: Issue | Impact Salary + overhead | £40-70k/year per person (UK) / $60-90k/year (US) Training & onboarding | Time-intensive, especially if systems are manual Inconsistency | Manual processes vary from person to person Scale limits | More invoices = more hires = linear cost growth Scaling your AR process should not mean scaling your payroll. ✅ The CFO's Playbook: Scaling AR Through Automation Here's how modern CFOs are scaling collections without adding headcount. 1. Introduce Smart Payment Links Static PDFs with "please pay via bank transfer" are a dead end. Instead, use smart payment links -- dynamic, trackable, and embedded with invoice details. These can be sent automatically via: CRM (e.g., Salesforce, HubSpot) Accounting software (e.g., Xero, NetSuite) Communication tools (e.g., email, SMS, WhatsApp) The result? Customers get a branded, mobile-friendly payment experience with options like ACH (US), Open Banking (UK), card, or Pay by Bank -- no logins or portals. Impact:✅ Fewer questions, ✅ faster payments, ✅ less chasing. 2. Automate Follow-Ups and Reminders Your AR team shouldn't be writing "Just checking in on this invoice..." emails all day. Smart systems can: Trigger reminder links if payment hasn't been made after X days Vary the message tone based on payment history Escalate to SMS or WhatsApp if email fails Impact:✅ More consistent follow-up,✅ fewer missed invoices,✅ reduced human effort. 3. Streamline Reconciliation Most AR teams spend too much time matching payments to invoices -- especially when bank transfers don't include a proper reference. With the right system: Every payment link is tied to a specific invoice Reconciliation happens automatically Payment status is updated in your accounting system in real time Impact:✅ Close books faster,✅ eliminate mismatches,✅ reduce errors. 4. Measure DSO and Cash Flow in Real Time As a CFO, you need live visibility -- not an end-of-month fire drill. Modern AR tools let you: Track open invoices by age, amount, and customer Monitor DSO trends and payment performance Forecast cash flow with far greater accuracy Impact:✅ Better financial control,✅ more confidence in reporting,✅ faster response to late payments. 🧩 How This Works with Your Existing Stack You don't need a complete systems overhaul. Shuttle, for example, integrates directly with: Xero, QuickBooks, NetSuite, Sage Intacct Salesforce, HubSpot, Zoho CRM Make.com, Zapier, Twilio, WhatsApp Business API No developers required. Just better workflows. 📈 Results from Mid-Sized Finance Teams Metric | Typical Improvement Manual AR effort | ↓ 30-50% DSO (Days Sales Outstanding) | ↓ 5-12 days Reconciliation time | ↓ 80% Collections rate | ↑ 10-20% You can do more with the team you already have -- if you give them the right tools. 🚀 Final Word You don't scale finance by scaling headcount.You scale by removing friction, automating the obvious, and giving your team visibility. Smart payment links are a simple but powerful unlock -- and one that pays off fast. ## Related Reading Explore More ### Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions ### The UK Guide to Collecting Overdue Payments ### Embedded Payments Without Becoming a PayFac ### How to Switch Twilio Pay Connectors Without Breaking Your Call Flow ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePayment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions→](/guides/payment-operations-at-scale/) - [GuideThe UK Guide to Collecting Overdue Payments→](/guides/uk-guide-collecting-overdue-payments/) - [GuideEmbedded Payments Without Becoming a PayFac→](/guides/embedded-payments-without-payfac/) - [GuideHow to Switch Twilio Pay Connectors Without Breaking Your Call Flow→](/guides/switch-twilio-pay-connector/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/how-to-use-payment-links-to-improve-cash-flow/ --- # How Payment Links Improve Cash Flow for Small Businesses | Shuttle > Learn how payment links reduce days sales outstanding, speed up collections, and help small businesses maintain healthier cash flow with faster payments. # How Payment Links Improve Cash Flow for Small Businesses By Nick Dunse, June 22, 2023 Learn how payment links reduce days sales outstanding, speed up collections, and help small businesses maintain healthier cash flow with faster payments. Talk to us Make enabling payments for your platform and merchant users easy. Cash flow is the single biggest operational challenge for small businesses. According to a U.S. Bank study, 82% of small businesses that fail cite cash flow problems as the primary reason. The gap between delivering a product or service and actually getting paid is where most of that pain lives. Payment links offer a direct solution. Instead of mailing invoices and waiting for checks -- or chasing customers through multiple follow-up emails -- you send a single URL that takes the customer straight to a hosted checkout page. They click, they pay, and the funds start moving immediately. This guide explains exactly how payment links improve cash flow, how they compare to traditional invoicing, and what best practices help small businesses collect faster and more consistently. ## Why Cash Flow Is a Challenge for Small Businesses Most small businesses operate on thin margins. When customers take 30, 60, or 90 days to pay an invoice, the business still needs to cover payroll, suppliers, rent, and other operating costs. That timing mismatch creates a cash flow gap -- and it compounds quickly. The core problem isn't that customers refuse to pay. It's that the payment process itself introduces unnecessary delay. Traditional invoicing workflows involve generating a PDF, emailing or mailing it, waiting for the customer to open it, hoping they don't lose it, and then waiting again for them to write a check or log into their bank to initiate a transfer. Each step in that chain adds days. Industry data shows the average small business invoice takes 24 days to get paid, and roughly 1 in 10 invoices becomes overdue. For businesses running on net-30 terms, that means some payments don't arrive for 45-60 days. The downstream effects are significant: delayed supplier payments, inability to take on new projects, reliance on credit lines to bridge gaps, and in the worst cases, missed payroll. Any tool that shortens the path from invoice to payment has a direct, measurable impact on business health. ## How Payment Links Reduce Days Sales Outstanding Days sales outstanding (DSO) measures the average number of days it takes to collect payment after a sale. It's the most important cash flow metric for any business that invoices customers. A lower DSO means faster collections and healthier cash flow. Payment links reduce DSO by eliminating the friction between receiving an invoice and completing a payment. When a customer receives a payment link embedded in an invoice, they can pay in under 60 seconds -- directly from the email, SMS, or messaging app where they received it. There's no separate login, no check to write, and no payment details to manually enter if the checkout supports saved methods. Businesses that switch from traditional invoicing to payment links typically see DSO drop by 30-50%. A company with a 35-day DSO might bring that down to 15-20 days -- which on a monthly revenue of $50,000 means an extra $25,000-$30,000 in available working capital at any given time. The reason is straightforward: payment links remove every barrier between the customer's intent to pay and the actual transaction. When paying is as easy as clicking a link, people pay sooner. ## Payment Links vs Traditional Invoicing: Speed Comparison To understand why payment links accelerate collections, it helps to compare the two workflows side by side. With traditional invoicing, the process typically follows this timeline: the business generates an invoice (day 0), emails or mails it (day 0-1), the customer reviews it (day 3-7), the customer initiates payment via check or bank transfer (day 7-14), the payment clears (day 14-21), and the funds are confirmed in the business account (day 21-30). Total elapsed time: 3 to 4 weeks on a good cycle. With payment links, the timeline compresses dramatically: the business sends an invoice with an embedded payment link (day 0), the customer clicks the link and pays via card or bank transfer (day 0-3), the payment processes (day 1-2), and the funds settle in the business account (day 2-5). Total elapsed time: 2 to 5 days in most cases. The biggest time savings come from eliminating the customer decision lag. Traditional invoices require the customer to actively decide to pay, find the right payment method, and take multiple steps. A payment link reduces that to a single action. Businesses focused on streamlining their accounts receivable process often find that payment links are the single highest-impact change they can make. ## Automating Payment Collection with Payment Links The real power of payment links emerges when you combine them with automation. Instead of manually generating and sending links for every invoice, modern payment platforms let you automate the entire collection workflow. Here's what an automated payment link workflow looks like in practice. When an invoice is created in your accounting or billing system, a payment link is automatically generated and embedded in the invoice email. If the customer hasn't paid within a set number of days, an automated reminder is sent with the same link. A second and third reminder follow at increasing intervals. Once the customer clicks and pays, the payment is automatically reconciled against the original invoice. This eliminates the manual chasing that accounts receivable teams spend hours on every week. For small businesses without a dedicated AR team -- which is most of them -- it means the business owner or office manager isn't spending evenings sending payment reminders. Platforms that offer payment link generation via API take this further. A property management platform, for example, can automatically generate rent payment links for every tenant each month. An invoicing tool can embed payment links in every outgoing invoice without any manual intervention. If you're a platform considering offering this to your users, embedded payment infrastructure makes it possible to generate branded payment links programmatically through a single API integration. ## Using Payment Links for Recurring Payments Recurring payments are where cash flow predictability matters most. Subscription businesses, membership organisations, and service companies with retainer agreements all depend on regular, on-time payments to maintain operations. Payment links can support recurring payments in two ways. The first approach is sending a fresh payment link for each billing cycle. This works well for variable-amount invoices -- think consulting fees that change monthly or utility bills that fluctuate. Each link is unique to the specific amount owed, and the customer pays with a single click. The second approach uses the initial payment link to capture and tokenize the customer's payment method, then automatically charges it on a recurring schedule. This is the standard model for subscriptions and fixed retainers. The customer only needs to interact with the payment link once -- after that, payments happen automatically. For businesses that currently rely on manual invoicing for recurring services, switching to payment links with ACH or bank transfer options can reduce late payments by 40-60% while also lowering per-transaction costs. ACH debits are particularly effective for recurring B2B payments where the amounts are larger and the fee savings on each transaction are substantial. ## Giving Customers Easier Ways to Pay One of the most overlooked factors in cash flow management is payment method flexibility. When customers can only pay by check or bank transfer, you're limiting yourself to the slowest payment channels. When you give customers easier ways to pay invoices, collection speed improves across the board. Payment links solve this by hosting a checkout page that accepts multiple payment methods. A single link can support credit and debit cards, ACH bank transfers, Apple Pay, Google Pay, and other digital wallets -- all without requiring the business to integrate each method separately. This flexibility matters because different customers prefer different payment methods. A freelancer might pay with a debit card immediately. A corporate accounts payable department might prefer ACH. An individual customer might use Apple Pay from their phone. When every customer can pay the way they prefer, the average time to payment drops significantly. Payment links also work across every communication channel. You can send them via email, SMS, WhatsApp, social media DMs, QR codes on printed invoices, or embed them on your website. Wherever your customer is, the payment link meets them there. ## Payment Link Best Practices for Cash Flow Simply switching to payment links will improve your cash flow, but following these best practices will maximize the impact. Send the link immediately. The sooner a customer receives a payment link after a service is delivered or a product is shipped, the more likely they are to pay quickly. Don't wait until the end of the month to batch invoices -- send the payment link the same day the work is completed. Use SMS in addition to email. Payment links sent via text message have significantly higher open and completion rates than email alone. SMS open rates are above 95%, compared to roughly 20% for email. For time-sensitive collections, SMS is the faster channel. Set up automated reminders. Configure your system to send a follow-up at 3 days, 7 days, and 14 days after the initial link is sent. Each reminder should include the same payment link for a frictionless experience. Most payment platforms support scheduled reminders out of the box. Pre-fill invoice details. When the customer clicks the link, they should see the amount, description, and invoice number already populated. Every piece of information they need to confirm should be visible on the checkout page. This reduces confusion and abandoned payments. Offer early payment incentives. A 2% discount for payment within 5 days (known as 2/5 net 30 terms) can meaningfully accelerate collections. When you combine early payment terms with the convenience of a payment link, a significant portion of customers will pay within the discount window. Brand the checkout experience. Payment links that lead to a branded, professional checkout page build trust and reduce drop-off. If the payment page looks generic or unfamiliar, customers may hesitate. Custom branding -- your logo, colours, and business name -- reassures customers that the link is legitimate. ## Measuring the Impact on Cash Flow Once you've implemented payment links, you need to track specific metrics to quantify the improvement. Three metrics matter most. Days sales outstanding (DSO) is the headline metric. Calculate it by dividing your total accounts receivable by your average daily revenue. Track this monthly and compare it to your pre-payment-link baseline. A healthy DSO for a small business using payment links should be under 20 days. Collection rate measures the percentage of invoices paid on time (within your stated terms). Before payment links, many small businesses see collection rates around 70-80% within 30 days. After implementing payment links with automated reminders, that number typically rises to 90-95%. Average time to payment tracks the median number of days between sending an invoice and receiving cleared funds. This metric is more granular than DSO because it shows the actual customer behaviour, not just the accounting ratio. Track it by payment method as well -- you'll likely find that card payments via payment links clear 2-3 times faster than ACH, and both are dramatically faster than checks. Set up a simple dashboard or spreadsheet to track these three metrics monthly. After 90 days of using payment links, you should have enough data to calculate the dollar value of your improved cash flow -- which makes the ROI case straightforward for any additional investment in payment automation. ## For Platforms: Embedding Payment Links for Your Customers If you operate a platform that serves small businesses -- whether it's invoicing software, a CRM, a property management system, or a vertical SaaS tool -- embedding payment link generation directly into your product is one of the highest-value features you can add. Your customers already manage their billing through your platform. Giving them the ability to generate a branded payment link from any invoice, quote, or order -- without switching to a separate payment tool -- eliminates friction and keeps them inside your ecosystem. The implementation doesn't need to be complex. With an embedded payments API, you can generate payment links programmatically with a single API call -- specifying the amount, currency, customer details, and redirect URLs. The link opens a white-label checkout page branded to your platform, and payment confirmation is returned via webhook for automatic reconciliation. This approach lets your SMB customers collect payments faster -- improving their cash flow -- while giving your platform a new revenue stream through payment processing fees. If you want to explore how this works, get in touch with our team to see a working integration. ## Frequently Asked Questions ### How quickly do payment links improve cash flow? Most businesses see a noticeable improvement within the first billing cycle. The average time to payment typically drops from 20-30 days to 3-7 days when customers are sent a payment link instead of a traditional invoice. Within 60-90 days of consistent use, DSO reductions of 30-50% are common. ### Are payment links secure for business transactions? Yes. Reputable payment link providers use PCI DSS-compliant checkout pages with TLS encryption, tokenized card storage, and fraud detection. The customer's payment details are never exposed to the business -- they're handled entirely by the payment processor. This is actually more secure than collecting payment details over the phone or via email. ### Can I use payment links alongside my existing invoicing software? Yes. Payment links can be added to invoices generated by any accounting or invoicing system -- QuickBooks, Xero, FreshBooks, or custom tools. You can include the link in the invoice email body, embed it as a pay button in a PDF invoice, or send it as a separate follow-up message. Many platforms also offer direct integrations that auto-generate and attach payment links. ### What payment methods can customers use through a payment link? This depends on your payment provider, but most payment links support credit and debit cards (Visa, Mastercard, Amex), ACH bank transfers, and digital wallets like Apple Pay and Google Pay. Some providers also support Buy Now Pay Later options and open banking payments. Offering multiple methods through a single link maximises the chance of fast payment. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment link embedded in an invoice](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [streamlining their accounts receivable process](/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/) - [embedded payment infrastructure](/platforms/) - [ACH or bank transfer options](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [give customers easier ways to pay invoices](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [embedded payments API](/platforms/) - [get in touch with our team](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/improve-your-cash-flow-stop-waiting-to-get-your-invoices-paid/ --- # Improve your cash flow. Stop waiting to get your invoices paid | Shuttle > Nobody likes to wait, especially when it's related to getting paid. The average waiting time in the UK for an invoice to be settled for an SME is 71 days. # Improve your cash flow. Stop waiting to get your invoices paid By Nick Dunse, January 20, 2023 Nobody likes to wait, especially when it's related to getting paid. The average waiting time in the UK for an invoice to be settled for an SME is 71 days. I suspect this is the case across most western business territories. Waiting to get paid is downright expensive and detrimental to the health of your business. You probably know the phrase that 'cash is king' and you've probably been encouraged by your accountant and mentors to reduce invoice payment terms down as much as possible, ideally payment on receipt of invoice is best. There are a number of ways to achieve this ideal outcome: - You don't take on any new customers who won't accept these terms. Stand strong, put your stall out and good luck to you with this one. - You get your customers on a flexible direct debit. This is great since there are no fees attached to DD, but there are some challenges with this method: Convincing your customer to agree to a flexible DD is not easy - Doing the admin for this requires reasonable amount of time and effort up front - You can use a payment gateway like GoCardless to reduce the admin but they will charge you a fee - The major pain for DD is they are often slow to when it comes to receiving/clearing the first or subsequent payments and you have to have another system to validate the payment has been made. When you send the invoice over you hit the phones. This could be seen as a little aggressive by your customers, it's likely to be time-consuming for you and unlikely to yield immediate results. You offer incentives for faster payment via BACS, maybe a 10% discount if paid within 1 day. This is good but it might still be hard if the organisation you deal with only makes payments once per month with their 'bank run.' You're giving it away! If you're a service provider with reasonably sized invoices it's a good idea to split your projects into bite-sized chunks and invoice inline with those deliverables; but again, if you have a client on 30 day terms you'll be well underway with the next phase and still be at risk of not getting paid on time if at all. You should never leave more than 10% of the total bill until the end and you shouldn't send a deliverable until payment is made, that's what happens when you go shopping right? Most shops don't let you walk off with the goods unless you've paid or signed a payment scheme contract. The problem is that none of the above really solves the issue of getting paid quickly and addresses how to give the people that are paying a simple, pleasurable experience when making that payment, meaning alongside being happy with the product or service they enjoy paying you. Ok, enjoy paying you is perhaps a little far-fetched, but I actually think companies like Amazon have made buying stuff rather too easy and potentially addictive. So having said all that, what if we could leverage the type of experience that, us as consumers are used to, paying with our debit and credit cards. Paying from our mobile, paying from anywhere. There are currently a few options out there from companies like PayPal and Stripe. With PayPal you can use PayPal.me and create your own payment link to your unique URL, obviously, you have to have a PayPal account and the money gets deposited in there for you to withdraw. Stripe do things slightly different and call their system Stripe Checkout. You drop the Stripe checkout code on to your website and direct your customers there to pay you, either a one-off or recurring payment, plus saving cards is possible. In the age of mobile banking and e-commerce you'd think that making payments online for products and services would be easy, well these two solutions certainly go some way to making that a reality, pay others quickly and expect to be paid quickly in return. The issue comes when you have an existing relationship with a merchant account or payment gateway provider that don't have the plug and play options like Stripe or PayPal. Having used other providers' options, if they offer them, is like using an online children's cash register with a pedantic nature. They're not very nice! What if you could have an independent payment layer that accepted card payments, created a best of breed experience and was open to embrace future payment developments and methods. That would be great, wouldn't it? Having your invoices settled with the same enjoyment as sliding that Amazon purchase button. The bottom line is that the world of payments is still too complicated and fragmented, for the most part, it's far behind in its approach to satisfy a savvy, demanding population. This is what fueled us to start the journey in our vehicle Pay with Bolt, an independent and best of breed payment solution, allowing businesses to get paid immediately online by accepting card payments (and beyond). Pay with Bolt is not for the people who like to pay their friends at the last possible moment, Pay with Bolt is ideal for businesses with higher volume invoices, with lower payment amounts, who want their customers to enjoy the payment experience again and again. Let's see those invoice settlement days come down! ## Related Reading Explore More ### How to Get Payments Off Your Product Roadmap ### How to Switch Twilio Pay Connectors Without Breaking Your Call Flow ### Pay Now Button for Invoices: The B2B Guide ### How PSPs Get Distribution Into Enterprise Software ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideHow to Switch Twilio Pay Connectors Without Breaking Your Call Flow→](/guides/switch-twilio-pay-connector/) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/ --- # Shuttle Blog: Payments, Platforms & AI Agent Insights > Articles and insights on embedded payments, voice checkout, payment links, and AI agent commerce from the Shuttle team. Built for platforms and SaaS leaders. # Fresh perspectives from the team Insights & Ideas Stay up to date with the latest articles, resources, and practical tips on payments, platforms, and AI agents. Platforms annexed every new sales channel: marketplaces, the counter, social, now AI agents. The phone is the oldest channel of all and the only one still unannexed. Why the payment, not the agent, decides who keeps the merchant relationship. Step-by-step 2026 tutorial: enable PCI Mode, install a Pay Connector, add the Pay verb to your TwiML, and take your first PCI-compliant IVR payment on Twilio. Yes, you can take PCI-compliant card payments on a Retell AI voice agent, as long as the card is captured off-platform. Here is how it works, what is possible today, and what is coming. Web commerce was won by whoever owned the checkout page. The next sales channel is the conversation, voice and chat, and it has no checkout in it. Here is why the conversation gets won at the payment, not the agent, and what closes the gap. Stripe Connect works well for early-stage platforms. But at scale, these 5 limitations -- from country coverage to proprietary tokens -- force a rethink. Add online payment options to Sage 50, Sage 200, Sage Intacct, and Sage Business Cloud invoices. Use your own gateway, keep your rates. Build a complete QuickBooks payment collection workflow with pay-now links, automated reminders, and multi-channel chasing. 4 dunning letter templates for posted correspondence -- friendly reminder to Letter Before Action. Includes QR code placement for instant payment. Agentic payments has two sides. Merchant-side agents collecting payments via voice and payment links work today. Consumer-side agents spending money on behalf of humans face unsolved problems: virtual cards are 15-year-old infrastructure, consent models are broken, and checkout surfaces are hostile to automation. Add payment links to Xero invoices using your own gateway -- not just Stripe or GoCardless. White-label, multi-channel, 40+ providers. UK-specific overdue invoice templates with Late Payment Act references, statutory interest calculations, and pay-now links at every stage. 8 copy-paste payment reminder templates for every stage -- from friendly first nudge to letter before action. Each includes a pay-now link. How do AI agents capture payment consent? The consent problem in agentic commerce -- regulations, risks, and what platforms need to build for compliant AI agent transactions. SaaS companies spend 5-9% of revenue on payments infrastructure -- engineering, compliance, tax, reconciliation. A quarter of companies don't even track the cost. Here's what the real numbers look like. Software platforms shouldn't have to become payment companies. The Payment Layer is the infrastructure that sits between software and PSPs -- so platforms ship payments in weeks, not quarters. Why CPaaS, CCaaS, and AI voice platforms need an embedded payment layer -- not another bolt-on integration. Three architecture patterns, PCI scope analysis, and the revenue model platforms miss. Most call answering services handle messages and appointments -- but can't take a payment. Here's why, and what it would actually take to add payment collection. Phygital commerce blends physical and digital retail. Learn how agentic AI solutions are powering the next wave of unified commerce and seamless payment experiences. The voice AI market hit $47.5B. Every CCaaS vendor is deploying AI agents. But when a customer needs to pay, most voice AI hits a wall. Here's the infrastructure gap -- and how to close it. Stripe opened Checkout, Billing, and Radar to merchants on other processors. Here's why that confirms multi-PSP is the new default -- and what platforms should do about it. PSP mergers keep happening. Here's what Global Payments/Worldpay, FIS/Worldpay, and every acquirer consolidation means for platforms that depend on a single processor. Every insurance core platform has billing. Almost none execute payments. Here's why billing and payment execution are different things -- and what changes when both live inside the platform. Having a backup PSP protects your business from payment outages. Learn why redundancy in payment processing is essential for business continuity. Compare payment providers and understand how they work. Learn the difference between gateways, aggregators, and PSPs -- and how to choose the right one for your business. Stripe, Google, Visa, and Mastercard are all announcing agentic payment protocols. But what infrastructure do platforms actually need to let AI agents process payments? Here's what's real, what's hype, and what to build. PSP distribution is shifting from direct sales to embedded platform infrastructure. Here's why the layer between platforms and PSPs is where payment volume will live. Millions of insurance calls per day involve a payment moment. Most call centres handle it badly. Here's why PCI scope is the blocker -- and the architecture that fixes it. How to accept payments on TikTok using payment links, TikTok Shop, and third-party checkout. Set up, send links via DMs, and get paid -- no website required. What is payment gateway aggregation? How SaaS platforms use a single integration to connect to multiple PSPs -- reducing cost, improving reliability, and avoiding gateway lock-in. How to set up Moneris payment links, what they cost, supported features, and how they compare to multi-PSP alternatives. Includes step-by-step setup and integration options for Canadian businesses. Add branded payment links to your VEEM account. Send checkout links via SMS, email, or chat -- keep your existing VEEM setup. No migration required. Add branded payment links to your Global Payments account. Send checkout links via SMS, email, or chat -- keep your existing Global Payments setup. No migration required. Add branded payment links to your FreedomPay account. Send checkout links via SMS, email, or chat -- keep your existing FreedomPay setup. No migration required. Add branded payment links to your CardConnect account. Send checkout links via SMS, email, or chat -- keep your existing CardConnect setup. No migration required. Add branded payment links to your Ecommpay account. Send checkout links via SMS, email, or chat -- keep your existing Ecommpay setup. No migration required. Add branded payment links to your BS Payone account. Send checkout links via SMS, email, or chat -- keep your existing BS Payone setup. No migration required. Add branded payment links to your Cybersource account. Send checkout links via SMS, email, or chat -- keep your existing Cybersource setup. No migration required. Add branded payment links to your Fortis account. Send checkout links via SMS, email, or chat -- keep your existing Fortis setup. No migration required. Add branded payment links to your Paytomorrow account. Send checkout links via SMS, email, or chat -- keep your existing Paytomorrow setup. No migration required. Add branded payment links to your LiqPay account. Send checkout links via SMS, email, or chat -- keep your existing LiqPay setup. No migration required. A comprehensive guide to online payments for businesses. Understand payment gateways, processors, and how to choose the right solution for your needs. The PayFac model traps platforms into owning payment infrastructure they never wanted. Here's why platforms need a payment layer, not a PayFac licence. Twilio partners with Shuttle to provide PCI-compliant payment connectivity over voice and messaging channels using programmable APIs. Spreedly has limitations for software platforms including restricted gateway support and pricing complexity. Explore alternative payment aggregation solutions. Practice management software with payment links improves cash flow, reduces admin, and gives clients a seamless way to pay invoices instantly. Payments orchestration promises to simplify multi-gateway management. This article breaks down what it really means and whether it is right for your business. Mobile money leads payments in Tanzania with M-Pesa and Tigo Pesa. Explore all popular payment methods including bank transfers and digital wallets. Explore Mexico's top payment methods including OXXO cash payments, SPEI bank transfers, credit cards, and digital wallets for the booming e-commerce market. M-Pesa dominates payments in Kenya. Discover all popular payment methods including mobile money, bank transfers, and digital wallets for East African commerce. Razorpay and Anthropic's Claude launched live agentic payments on UPI in India. Here's what the infrastructure looks like -- and what Western payment systems need to catch up. Discover Japan's most popular payment methods from credit cards and convenience store payments to mobile wallets, IC cards, and bank transfers. Explore Italy's most popular payment methods from credit cards and PostePay to Bancomat, PayPal, and the growing adoption of digital wallets and BNPL services. Telebirr dominates with 40M+ users, but it's not the only option. See all the payment methods used in Ethiopia, from mobile money to bank transfers. BPOs have automated conversations but not payments. Discover how payment automation closes the loop, reduces handle time, and improves collection rates. Explore Australia's most popular payment methods from credit and debit cards to PayPal, Afterpay, Apple Pay, and BPAY for online and in-store commerce. Travel agents can streamline bookings with payment links. Collect deposits and full payments remotely via email or SMS without manual card processing. Learn how to create and send Square payment links, what they cost, and when you might need a more flexible alternative for multi-gateway payment links. Streamline your quote-to-cash process with payment links. Close deals faster by embedding secure payment collection directly into sales workflows. INSTANDA partners with Shuttle to offer insurance platforms seamless payment processing with multi-gateway support, PCI compliance, and automated billing. HQ Rental Software partners with Shuttle to offer fleet rental businesses seamless payment processing with multi-gateway connectivity and automated billing. vFairs partners with Shuttle to let event organisers accept payments through their preferred gateway with built-in fraud protection. Rezkit partners with Shuttle to give travel and tourism businesses flexible payment processing with multi-gateway support and automated reconciliation. Eventsforce partners with Shuttle to offer event organisers flexible payment processing with multi-currency support, fraud protection, and gateway choice. Ordorite partners with Shuttle to bring flexible payment processing to furniture and bedding retailers with multi-gateway support and seamless integration. Classter partners with Shuttle to bring secure, flexible payment processing to educational institutions with multi-gateway support and automated billing. Building your own payment facilitation looks profitable on paper, but the hidden costs of compliance, support, and maintenance make it a false economy. Create Stripe payment links to accept online payments without a website. Share secure checkout links via email, SMS, or social media and get paid fast. A comprehensive guide to preventing chargebacks. Learn dispute management strategies, fraud prevention tools, and how to protect your merchant account. PCI DSS compliance requirements for service providers and merchants. Understand the four merchant levels, two service provider levels, SAQ types, costs, and how to reduce your PCI scope. PCI DSS v4.0 introduces key changes for software vendors including stricter authentication, enhanced encryption, and new requirements for service providers. Are payments still a commodity or the next big opportunity? Explore how modern payment infrastructure is transforming SaaS platforms and merchant experiences. How travel agencies and OTAs collect payments faster -- payment links, phone payments, and multi-currency processing without building a payment stack. Add branded payment links to your Xendit account. Send checkout links via SMS, email, or chat -- keep your existing Xendit setup. No migration required. How to add payment links to invoices so customers pay in one click. Covers setup, best practices, and why invoice payment links reduce DSO by 30% or more. Send branded payment links through your Worldpay account. No switching provider. SMS, email, and chat delivery with full tracking and branded checkout pages. Add branded payment links to your USAePay account. Send checkout links via SMS, email, or chat -- keep your existing USAePay setup. No migration required. Add branded payment links to your Trust Payments account. Send checkout links via SMS, email, or chat -- keep your existing Trust Payments setup. No migration required. Add branded payment links to your Transbank account. Send checkout links via SMS, email, or chat -- keep your existing Transbank setup. No migration required. Upgrade Square payment links with full branding, detailed tracking, and multi-channel delivery. Process through your Square account with better customisation. Add branded payment links to your Stripe account. Send via SMS, email, or chat with full branding, tracking, and a merchant dashboard. Keep your Stripe rates. Add branded payment links to your QuickBooks Payments account. Send checkout links via SMS, email, or chat -- keep your existing QuickBooks Payments setup. No migration required. Add branded payment links to your Shift4 account. Send checkout links via SMS, email, or chat -- keep your existing Shift4 setup. No migration required. Add branded payment links to your Paysafe account. Send via SMS, email, or chat with a self-serve dashboard. No code required. Replace PayPal.me with branded payment links on your PayPal Commerce account. Accept cards without a PayPal account. Full tracking and multi-channel delivery. Add branded payment links to your Opayo account. Send checkout links via SMS, email, or chat -- keep your existing Opayo setup. No migration required. Add branded payment links to your NMI account. Send checkout links via SMS, email, or chat -- keep your existing NMI setup. No migration required. Add one-off card payment links alongside your GoCardless direct debits. Collect deposits, ad-hoc charges, and balance payments by card. Enhance Mollie payment links with full branding, SMS and WhatsApp delivery, and detailed tracking. iDEAL, cards, and local methods supported. Add branded payment links to your Fat Zebra account. Send checkout links via SMS, email, or chat -- keep your existing Fat Zebra setup. No migration required. Add a no-code payment links dashboard to Checkout.com. Your operations team can create and send branded payment links without developer involvement. Add payment link capability to Braintree. Send branded checkout links via SMS, email, or chat. Process through your existing Braintree account. Add branded payment links to your Affirm account. Send checkout links via SMS, email, or chat -- keep your existing Affirm setup. No migration required. The travel industry is transforming how bookings and payments work. Explore emerging trends in travel payments, from multi-currency to embedded checkout. Add a no-code payment links dashboard to your Adyen account. Branded checkout pages, multi-channel sending, and real-time tracking without developer involvement. Accountants use Shuttle payment links to modernise receivables, accelerate client payments, and reduce time spent chasing overdue invoices. Modern payment solutions for law firms. Covers trust accounting, IOLTA compliance, payment links, PCI requirements, and collecting fees online. Learn how ACH payment links cut processing fees to under 1%, speed up collections, and simplify bank payments for small businesses. Learn how to add payment links to Linktree using PayPal, Venmo, Cash App, Zelle, and Commerce Links. Step-by-step setup plus smarter alternatives. How logistics platforms streamline freight payments with payment links, embedded checkout, and automated collection to replace net-60 invoices. Considering becoming a PayFac? Understand the costs, compliance burden, and alternatives like payment facilitation-as-a-service for SaaS platforms. Compare the best invoicing software for small businesses. Covers features, pricing, payment integration, and how to get invoices paid faster. Shuttle Smart Rules let merchants customise checkout flows and automate fraud prevention. Streamline payments with conditional logic and amount-based rules. Learn how to integrate Stripe with QuickBooks Online. Compare setup methods, sync payments and invoices, and avoid common reconciliation pitfalls. No -- Instagram does not require linking an email to receive payments. Use payment links to get paid from posts, DMs, Stories and bios in 2026 -- no Instagram Shop or business email setup needed. Learn how Ethoca helps merchants prevent chargebacks by resolving disputes before they become formal claims, reducing lost revenue and processing fees. The payment processing landscape is evolving fast. Learn how platforms and merchants can reduce costs and increase revenue with modern payment strategies. How embedded payments helped Brightpearl grow. Shuttle enabled the retail operations platform to offer seamless payment processing to its merchants. Learn how video shopping platforms use payment links to convert live viewers into buyers with instant, secure checkout during broadcasts. Creators and solo entrepreneurs can accept payments without a website or shopping cart using payment links shared via email, social media, or messaging. IT services firms use Shuttle payment links to collect project deposits, milestone payments, and retainers faster with secure, branded checkout links. Connect FreedomPay to Zapier, Twilio, QuickBooks, and more through Shuttle. One of the few approved integrations for the FreedomPay platform. DTMF capture vs payment links -- when each makes sense, how each handles PCI, and how to use both together in a contact centre. Builders and tradespeople who accept card payments win more jobs and get paid faster. Learn how payment links make it simple without a card terminal. How to create and use payment links in HubSpot. Covers Commerce Hub pricing, Stripe integration, workflow automation, limitations, and better alternatives. Over 9,000 QuickBooks users connect Shuttle to accept payments through their preferred gateway. See how embedded payments drive platform growth. Seven practical ways merchants can reduce payment processing fees: negotiate rates, optimise routing, reduce chargebacks, and choose the right provider. Discover how payment links streamline invoice collection, hotel deposits, call centre payments, subscriptions, and marketplace payouts for merchants. Learn 5 proven strategies to streamline accounts receivable, reduce DSO, and accelerate cash flow with automation, payment links, and smarter dunning. Five reasons SaaS platforms should avoid building payment integrations in-house: cost, complexity, compliance, maintenance, and time-to-market. Survey reveals the top five frustrations for small businesses: tax, accounting, expense tracking, payments, and cash flow. Learn practical solutions. Add branded payment links to your PayU account. Send checkout links via SMS, email, or chat -- keep your existing PayU setup. No migration required. Even the smartest IVR can fail. Learn how payment links serve as a reliable fallback for voice payments, reducing drop-off and recovering failed calls. For years, Business Process Outsourcers (BPOs) have perfected the art of conversation. A customer calls to renew, pay, or settle an account. Twenty years ago, voice was the channel of human connection. Call centres were the heartbeat of customer experience. AI agents are replacing scripts. For twenty years, payments in software have been treated as a side project.Platforms bolt on a gateway, ship an API, and hope merchants figure it out. AI agents are changing how customers buy. Explore how agentic commerce will reshape checkouts, payments, and the role of SaaS platforms in the AI era. How SaaS platforms can prepare for AI-driven commerce. Covers agent-ready payment APIs, PCI compliance for AI agents, and the infrastructure shift from human to agentic checkout. SaaS platforms can embed a branded payment link feature in weeks using Shuttle, instead of spending months building payment integrations from scratch. Compare multi-gateway connectors and native PSP integrations. Learn which approach helps SaaS platforms support more payment providers with less effort. AI agents are starting to buy on behalf of consumers. Is your checkout ready for non-human buyers and agentic commerce? If you're trying to modernise your AR process, the choices can feel overwhelming. Reduce DSO and improve cash flow by offering multiple invoice payment methods. Learn how payment links, ACH, and digital wallets get invoices paid faster. Scale your accounts receivable without adding headcount. Learn how automated payment links and workflows reduce manual AR work and improve collections. Why Payment Links Might Be the Upgrade Your CFO Doesn't Know They Need 85% of customer interactions will be managed without human intervention by 2025. (Source: Gartner) Your AR team is stuck in spreadsheets while revenue grows. Discover how payment automation eliminates manual follow-ups and speeds up cash collection. Shuttle and PolyAI partner to bring PCI-compliant voice payments to AI-powered phone agents. Take secure card payments during automated calls -- no DTMF, no agent exposure. Local acquiring routes international card payments through in-country processors, improving authorisation rates and reducing cross-border fees. Here's how it works and when you need it. How insurtech companies choose the right payment gateway. Covers premium collection, recurring billing, multi-carrier payments, and PCI compliance for insurance platforms. Best payment gateways for facilities management companies -- automate invoicing, recurring billing, and field service collections. How to choose an event payment gateway for ticketing, refunds, split payments and high-volume processing. Compare top options and integration approaches. Which payment providers offer the fastest settlement? Compare settlement speeds for Stripe (T+2), Adyen (T+1), Square (next day), Worldpay, Checkout.com, and 10+ more. Includes same-day and instant payout options. Learn how to accept ACH payments in QuickBooks Online. Compare fees, setup steps, processing times, and alternatives for collecting bank transfers. Nick hosted a discussion with Chargebee and GoCardless via SaaStock Local. Understand UK card processing fees -- interchange, scheme fees, acquirer markups, and total costs. Compare provider rates and learn practical ways to reduce payment processing costs. Discover Nigeria's top payment methods including bank transfers, debit cards, USSD payments, and mobile money platforms for Africa's largest e-commerce market. Accept card payments directly from QuickBooks Online invoices. Shuttle connects your preferred payment gateway so customers can pay instantly. Braintree vs Checkout.com for enterprise merchants -- compare pricing, global coverage, developer tools, and payout speed. This is a big deal and if you're running an online marketplace in the EU you need to read this... How emotions influence payment behaviour -- why checkout experience, trust signals, and payment UX directly affect conversion rates. iDEAL dominates Dutch online payments with over 60% market share. Explore all popular payment methods in the Netherlands including cards, PayPal, and Klarna. Alipay and WeChat Pay dominate Chinese digital payments. Explore the most popular payment methods in China including UnionPay and cross-border options for merchants. We hosted EKM, the UK ecommerce shopping cart for a chat about how they achieved breakthrough as one of the UK's leading e-commerce platforms. Some highlights: Learn how to create and send Authorize.net payment links using Accept Hosted, the API, or third-party tools like Shuttle. Setup, fees, and FAQ. Learn how in-store payment links replace POS hardware with QR codes, NFC taps, and SMS checkout. Cut costs, bust queues, and simplify PCI compliance. Learn how payment links reduce days sales outstanding, speed up collections, and help small businesses maintain healthier cash flow with faster payments. PromptPay, TrueMoney, Rabbit LINE Pay and more -- the complete list of payment methods Thai consumers actually use for online and in-store purchases. The state of Open Banking payments -- adoption rates, merchant benefits, challenges, and what account-to-account payments mean for UK businesses. What is chargeback fraud, how it impacts merchants, and practical steps to prevent friendly fraud and dispute losses. Learn how to accept card payments in-person, online, and over the phone. Compare fees, providers, and security requirements for your business. Compare the best UK payment gateways -- Stripe, Adyen, Worldpay, Checkout.com, Square, and more. Fees, features, integration options, and which to choose for your business. 10 February 2023 Merchants can now use Kount fraud and chargeback prevention via their software vendor thanks to Shuttle. Nobody likes to wait, especially when it's related to getting paid. The average waiting time in the UK for an invoice to be settled for an SME is 71 days. How do Brazilians pay online? From Pix (used by 150M+) to Boleto and installment cards -- here are the payment methods you need to accept in Brazil. Why the cheapest processing fees don't mean the cheapest operation -- hidden costs of payment infrastructure that merchants overlook. Explore the UK's most popular payment methods from debit and credit cards to open banking, Apple Pay, Google Pay, and buy-now-pay-later services like Klarna. Explore the most popular payment methods in the USA from credit and debit cards to ACH transfers, Venmo, Apple Pay, and buy-now-pay-later options. Reduce cart abandonment and increase checkout conversion with these 12 proven optimization strategies. Covers UX, payment methods, trust signals, and embedded checkout. The definitive guide to UK payment providers -- compare Stripe, Adyen, Worldpay, Square, and more on fees, features, and support. A payment gateway securely captures card details and routes them to a processor for authorisation. Learn how payment gateways work, the main types, 2026 costs, how to choose one, and the infrastructure platforms use to run payments across multiple gateways. How marketplaces can maximise revenue with the right payment setup -- split payments, seller onboarding, compliance, and payout management. Key updates from the UK Payment Systems Regulator (PSR) -- including APP fraud protections, interchange regulation, and the impact on merchants and payment providers. A review of the chargeback protection market in 2026. Compares Ethoca, Verifi, Chargebacks911, and other solutions for merchants looking to reduce disputes and recover revenue. How businesses process global payments across borders. Covers FX, local acquiring, regional methods, and multi-PSP strategy for expansion. What account updater services do, how Visa VAU and Mastercard ABU work, costs, benefits for recurring billing, and when your business should enable one. Cash on delivery still leads, but digital is growing fast. From CMI cards to m-wallet -- every payment method merchants need in Morocco. What is a PISP (Payment Initiation Service Provider)? How PISPs work under Open Banking, the difference from AISPs, real examples, and why PISP payments are growing in the UK and EU. How marketplaces handle payments -- from split settlements and seller onboarding to multi-PSP architecture. What marketplace operators need from their payment infrastructure. Explore how food and beverage businesses use payment links to speed up ordering, reduce queues, and offer flexible payment options to customers. Carte Bancaire leads French payments. Explore the most popular payment methods in France including PayPal, Apple Pay, Klarna, and bank transfers. Discover Indonesia's top payment methods including GoPay, OVO, bank transfers, virtual accounts, and credit cards for Southeast Asia's largest digital economy. Fawry kiosks, Vodafone Cash, Meeza cards and cash on delivery -- how do 100M+ Egyptians actually pay? The complete guide to payment methods in Egypt. PayPal leads German online payments alongside SEPA direct debit, Klarna, and giropay. Explore all popular payment methods in Germany for merchants and platforms. 'As soon as a marquee brand embraces OB payments then we will see success' What is a merchant account and how does it work? Covers the difference between merchant accounts and payment service providers, fees, application process, and which option suits your business. What is an AISP (Account Information Service Provider)? How AISPs work under Open Banking, the difference from PISPs, real examples, and why AISP services are growing in the UK and EU. Explore New Zealand's most popular payment methods from debit and credit cards to POLi online banking, Afterpay, and digital wallets like Apple Pay. Prevent ecommerce fraud with 3D Secure, AVS, velocity checks, and ML detection. Cover fraud types, PCI compliance, and chargeback management. GCash and cash on delivery lead Filipino payments. Explore all popular payment methods in the Philippines including Maya, cards, and bank transfers. Discover Malaysia's top payment methods including FPX online banking, GrabPay, Boost, credit cards, and e-wallets driving digital commerce growth. BLIK and Przelewy24 dominate Polish online payments. Explore all popular payment methods in Poland including cards, digital wallets, and bank transfers. Adyen vs Stripe compared for enterprise merchants -- fees, global acquiring, developer experience, and which PSP suits your scale. Learn how to integrate Authorize.net with QuickBooks for automated payment processing, invoice syncing, and reconciliation. Step-by-step setup guide. How travel businesses can capitalise on the global travel boom with flexible payment solutions. Covers multi-currency payments, instalment options, and payment links for travel agents. Explore South Africa's most popular payment methods from debit cards and EFT bank transfers to SnapScan, Zapper, and the growing digital payment ecosystem. Discover Vietnam's top payment methods including MoMo wallet, bank transfers, credit cards, and cash on delivery as digital payments grow rapidly. Everything merchants need to know about Buy Now Pay Later -- how BNPL works, top providers, conversion impact, and integration options. How integrating your shopping cart with an ERP system improves order management, reduces manual errors, and accelerates payment reconciliation for growing merchants. How to integrate a payment gateway into your app or platform. Covers API integration, hosted checkout, PCI compliance, testing, and go-live -- with code-level detail. How modern payment infrastructure transforms business operations. Covers embedded payments, payment orchestration, and why the right payment stack drives revenue growth. Explore Canada's most popular payment methods including credit cards, Interac debit, PayPal, Apple Pay, and e-transfers for online and in-store commerce. Set up QuickBooks Payments to accept cards, ACH, and Apple Pay on invoices and your website. Fees, setup steps, and third-party gateway options. Learn how secure payment links simplify card authorization, reduce PCI scope, and replace risky phone or email card collection for businesses and platforms 1 December 2019 Brightpearl, a leading retail operations platform for brands and retailers, uses Shuttle to power it's payment features. No articles found. Try a different search term. ## Links - [The best orders were always conversations. Now AI can have them, and take the payment.](/blog/best-orders-were-always-conversations/) - [Read more](/blog/best-orders-were-always-conversations/) - [How to Add Secure Payments to Your Twilio IVR (2026 Guide)](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [Read more](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [Can You Take Card Payments on a Retell AI Voice Agent?](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [Read more](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [Buying Moved Into the Conversation. The Checkout Didn't Follow.](/blog/buying-moved-into-the-conversation/) - [Read more](/blog/buying-moved-into-the-conversation/) - [5 Stripe Connect Limitations That Force Platforms to Switch](/blog/stripe-connect-limitations/) - [Read more](/blog/stripe-connect-limitations/) - [Sage Invoice Payments: How to Let Customers Pay Online](/blog/sage-invoice-payments/) - [Read more](/blog/sage-invoice-payments/) - [QuickBooks Payment Collection: Add Pay Now Links to Every Invoice](/blog/quickbooks-payment-collection/) - [Read more](/blog/quickbooks-payment-collection/) - [Dunning Letter Templates: From Friendly Reminder to Final Notice](/blog/dunning-letter-templates/) - [Read more](/blog/dunning-letter-templates/) - [Agentic Payments Isn't Solved Yet](/blog/agentic-payments-not-solved/) - [Read more](/blog/agentic-payments-not-solved/) - [Xero Payment Links: Collect Invoice Payments Faster](/blog/xero-payment-links/) - [Read more](/blog/xero-payment-links/) - [Overdue Invoice Email Templates UK: Chase Letters With Legal Teeth](/blog/overdue-invoice-email-templates-uk/) - [Read more](/blog/overdue-invoice-email-templates-uk/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [Read more](/blog/payment-reminder-email-templates/) - [Consent-Based AI Payments: How Agent Transactions Handle User Consent](/blog/ai-agent-payment-consent/) - [Read more](/blog/ai-agent-payment-consent/) - [Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)](/blog/payments-cost-saas-platforms/) - [Read more](/blog/payments-cost-saas-platforms/) - [Why We Built The Payment Layer](/blog/why-we-built-the-payment-layer/) - [Read more](/blog/why-we-built-the-payment-layer/) - [Voice Payments Are an Architecture Decision, Not a Feature Request](/blog/voice-payments-architecture-decision/) - [Read more](/blog/voice-payments-architecture-decision/) - [Why Most Call Answering Services Can't Take Payments](/blog/call-answering-service-payments/) - [Read more](/blog/call-answering-service-payments/) - [Phygital commerce and help of agentic solutions](/blog/phygital-commerce-and-help-of-agentic-solutions/) - [Read more](/blog/phygital-commerce-and-help-of-agentic-solutions/) - [Voice AI Is Booming -- But Can It Take a Payment?](/blog/voice-ai-payment-infrastructure-gap/) - [Read more](/blog/voice-ai-payment-infrastructure-gap/) - [What Stripe's Unbundling Tells Us About the Future of Payments](/blog/stripe-unbundling-multi-psp/) - [Read more](/blog/stripe-unbundling-multi-psp/) - [What PSP Consolidation Means for Your Platform](/blog/psp-consolidation-platform-risk/) - [Read more](/blog/psp-consolidation-platform-risk/) - [Insurance Billing vs Payment Execution: Why Your Platform Needs Both](/blog/insurance-billing-vs-payment-execution/) - [Read more](/blog/insurance-billing-vs-payment-execution/) - [Why You Should Have a Backup Payment Service Provider (PSP)](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [Read more](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [Payment Providers: How They Work & How to Choose (2026)](/blog/what-is-payment-gateway-aggregation/) - [Read more](/blog/what-is-payment-gateway-aggregation/) - [Agentic Payments in 2026: The Infrastructure Guide for Platforms](/blog/agentic-payments-infrastructure-2026/) - [Read more](/blog/agentic-payments-infrastructure-2026/) - [Where PSP Distribution Actually Lives](/blog/where-psp-distribution-actually-lives/) - [Read more](/blog/where-psp-distribution-actually-lives/) - [Why Insurance Call Centres Still Can't Take a Secure Payment](/blog/insurance-call-centre-payments/) - [Read more](/blog/insurance-call-centre-payments/) - [Using Payment Links to increase TikTok sales](/blog/payment-links-for-tiktok-sales/) - [Read more](/blog/payment-links-for-tiktok-sales/) - [Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It](/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/) - [Read more](/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/) - [Moneris Payment Links: Features, Setup & Alternatives (2026)](/blog/payment-links-for-moneris/) - [Read more](/blog/payment-links-for-moneris/) - [Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections](/blog/payment-links-for-veem/) - [Read more](/blog/payment-links-for-veem/) - [Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources](/blog/payment-links-for-global-payments/) - [Read more](/blog/payment-links-for-global-payments/) - [Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments](/blog/payment-links-for-freedompay/) - [Read more](/blog/payment-links-for-freedompay/) - [Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments](/blog/payment-links-for-cardconnect/) - [Read more](/blog/payment-links-for-cardconnect/) - [Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections](/blog/payment-links-for-ecommpay/) - [Read more](/blog/payment-links-for-ecommpay/) - [Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants](/blog/payment-links-for-bs-payone/) - [Read more](/blog/payment-links-for-bs-payone/) - [Payment Links for Cybersource: Send Branded Checkout Links Without Writing Code](/blog/payment-links-for-cybersource/) - [Read more](/blog/payment-links-for-cybersource/) - [Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations](/blog/payment-links-for-fortis/) - [Read more](/blog/payment-links-for-fortis/) - [Payment Links for Paytomorrow: Send Branded Checkout Links Beyond Consumer Financing](/blog/payment-links-for-paytomorrow/) - [Read more](/blog/payment-links-for-paytomorrow/) - [Payment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout](/blog/payment-links-for-liqpay/) - [Read more](/blog/payment-links-for-liqpay/) - [Understand Online Payments - Transform your business](/blog/understand-online-payments-transform-your-business/) - [Read more](/blog/understand-online-payments-transform-your-business/) - [Why Platforms Don't Want to Be Payment Companies](/blog/why-platforms-dont-want-to-be-payment-companies/) - [Read more](/blog/why-platforms-dont-want-to-be-payment-companies/) - [Twilio chooses Shuttle to provide payment connectivity](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [Read more](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [Uncovering the Limitations of Spreedly for Software Platforms](/blog/uncovering-the-limitations-of-spreedly-for-software-platforms-2/) - [Read more](/blog/uncovering-the-limitations-of-spreedly-for-software-platforms-2/) - [The Power of Payment Links: Enhancing Financial Management in Practice Management Software](/blog/the-power-of-payment-links-enhancing-financial-management-in-practice-management-software/) - [Read more](/blog/the-power-of-payment-links-enhancing-financial-management-in-practice-management-software/) - [The truth about payments orchestration](/blog/the-truth-about-payments-orchestration/) - [Read more](/blog/the-truth-about-payments-orchestration/) - [Payment Methods in Tanzania: M-Pesa, Tigo Pesa & Banks (2026)](/blog/the-most-popular-payment-methods-in-tanzania/) - [Read more](/blog/the-most-popular-payment-methods-in-tanzania/) - [Payment Methods in Mexico: OXXO, SPEI & Credit Cards (2026)](/blog/the-most-popular-payment-methods-in-mexico/) - [Read more](/blog/the-most-popular-payment-methods-in-mexico/) - [Payment Methods in Kenya: M-Pesa, Cards & Mobile Money (2026)](/blog/the-most-popular-payment-methods-in-kenya/) - [Read more](/blog/the-most-popular-payment-methods-in-kenya/) - [The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.](/blog/agentic-payments-go-live/) - [Read more](/blog/agentic-payments-go-live/) - [Payment Methods in Japan: Credit Cards, Konbini & IC Cards (2026)](/blog/the-most-popular-payment-methods-in-japan/) - [Read more](/blog/the-most-popular-payment-methods-in-japan/) - [Payment Methods in Italy: Cards, PostePay & Bancomat (2026)](/blog/the-most-popular-payment-methods-in-italy/) - [Read more](/blog/the-most-popular-payment-methods-in-italy/) - [Ethiopia Payment Methods: 6 Key Options for 2026](/blog/the-most-popular-payment-methods-in-ethopia/) - [Read more](/blog/the-most-popular-payment-methods-in-ethopia/) - [The Missing Piece in Modern BPO: Automating the Payment Moment](/blog/the-missing-piece-in-modern-bpo-automating-the-payment-moment/) - [Read more](/blog/the-missing-piece-in-modern-bpo-automating-the-payment-moment/) - [Payment Methods in Australia: Cards, PayPal & Afterpay (2026)](/blog/the-most-popular-payment-methods-in-australia/) - [Read more](/blog/the-most-popular-payment-methods-in-australia/) - [Streamline Your Booking Process with Payment Links: A Guide for Travel Agents](/blog/streamline-your-booking-process-with-payment-links-a-guide-for-travel-agents/) - [Read more](/blog/streamline-your-booking-process-with-payment-links-a-guide-for-travel-agents/) - [Square Payment Links: How to Create, Send & Customise (2026 Guide)](/blog/streamline-your-online-business-with-square-payment-links-and-checkout/) - [Read more](/blog/streamline-your-online-business-with-square-payment-links-and-checkout/) - [Simplify Your Sales Cycle: The Benefits of Using Payment Links in Quote to Cash](/blog/simplify-your-sales-cycle-the-benefits-of-using-payment-links-in-quote-to-cash/) - [Read more](/blog/simplify-your-sales-cycle-the-benefits-of-using-payment-links-in-quote-to-cash/) - [Shuttle Partners with INSTANDA to Streamline Payments for the Insurance Industry](/blog/shuttle-and-instanda/) - [Read more](/blog/shuttle-and-instanda/) - [Shuttle Enables HQ Rental Software with Key Payments Connectivity and Features](/blog/shuttle-and-hqrental/) - [Read more](/blog/shuttle-and-hqrental/) - [Shuttle and vFairs work together to revolutionise global event management](/blog/shuttle-and-vfairs-work-together-to-revolutionise-global-event-management/) - [Read more](/blog/shuttle-and-vfairs-work-together-to-revolutionise-global-event-management/) - [Shuttle and Rezkit Partner to Offer Seamless Payment Solutions for Travel and Tourism Businesses](/blog/shuttle-and-brightpearl-partner-to-enable-invoice-and-pos-payments-for-global-retailers/) - [Read more](/blog/shuttle-and-brightpearl-partner-to-enable-invoice-and-pos-payments-for-global-retailers/) - [Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers](/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/) - [Read more](/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/) - [Shuttle and Ordorite Enable New Payments Opportunities for Furniture Retailers](/blog/shuttle-and-ordorite-enable-new-payments-opportunities-for-furniture-retailers/) - [Read more](/blog/shuttle-and-ordorite-enable-new-payments-opportunities-for-furniture-retailers/) - [Shuttle and Classter Partner to Offer Seamless Payment Solutions for Educational Institutions](/blog/shuttle-and-classter/) - [Read more](/blog/shuttle-and-classter/) - [Reselling payments is a false economy](/blog/reselling-payments-is-a-false-economy/) - [Read more](/blog/reselling-payments-is-a-false-economy/) - [Revolutionize Your Payment Process with Stripe Payment Links](/blog/revolutionize-your-payment-process-with-stripe-payment-links/) - [Read more](/blog/revolutionize-your-payment-process-with-stripe-payment-links/) - [Preventing Chargebacks: A Guide for Businesses](/blog/preventing-chargebacks-a-guide-for-businesses/) - [Read more](/blog/preventing-chargebacks-a-guide-for-businesses/) - [PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [Read more](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [PCI DSS v4 Implications for Service Provider (software vendors)](/blog/pci-dss-v4-implications-for-service-provider-software-vendors/) - [Read more](/blog/pci-dss-v4-implications-for-service-provider-software-vendors/) - [Payments are sexy again. But are they still a commodity?](/blog/payments-are-sexy-again-and-no-longer-boring-but-are-they-still-a-commodity/) - [Read more](/blog/payments-are-sexy-again-and-no-longer-boring-but-are-they-still-a-commodity/) - [Travel Payment Solutions: How Agencies Collect Payments Faster](/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/) - [Read more](/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/) - [Payment Links for Xendit: Send Branded Checkout Links for Southeast Asian Merchants](/blog/payment-links-for-xendit/) - [Read more](/blog/payment-links-for-xendit/) - [Invoice Payment Links: How to Get Paid Faster on Every Invoice](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [Read more](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [Payment Links for Worldpay: Send Checkout Links Without Leaving Worldpay](/blog/payment-links-for-worldpay/) - [Read more](/blog/payment-links-for-worldpay/) - [Payment Links for USAePay: Send Branded Checkout Links for Remote and Phone Payments](/blog/payment-links-for-usaepay/) - [Read more](/blog/payment-links-for-usaepay/) - [Payment Links for Trust Payments: Send Branded Checkout Links for European Card Processing](/blog/payment-links-for-trust-payments/) - [Read more](/blog/payment-links-for-trust-payments/) - [Payment Links for Transbank: Send Branded Checkout Links for Chilean Merchants](/blog/payment-links-for-transbank/) - [Read more](/blog/payment-links-for-transbank/) - [Payment Links for Square: Upgrade Your Square Payment Links](/blog/payment-links-for-square/) - [Read more](/blog/payment-links-for-square/) - [Payment Links for Stripe: Add Branded Checkout Links to Your Stripe Account](/blog/payment-links-for-stripe/) - [Read more](/blog/payment-links-for-stripe/) - [Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices](/blog/payment-links-for-quickbooks-payments/) - [Read more](/blog/payment-links-for-quickbooks-payments/) - [Payment Links for Shift4: Send Branded Checkout Links for Hospitality and Restaurant Payments](/blog/payment-links-for-shift4/) - [Read more](/blog/payment-links-for-shift4/) - [Payment Links for Paysafe: Send Branded Checkout Links via Paysafe](/blog/payment-links-for-paysafe/) - [Read more](/blog/payment-links-for-paysafe/) - [Payment Links for PayPal: Send Professional Payment Links Through PayPal](/blog/payment-links-for-paypal/) - [Read more](/blog/payment-links-for-paypal/) - [Payment Links for Opayo: Send Branded Checkout Links for UK Merchants](/blog/payment-links-for-opayo/) - [Read more](/blog/payment-links-for-opayo/) - [Payment Links for NMI: Send Branded Checkout Links for ISOs, Resellers, and Merchants](/blog/payment-links-for-nmi/) - [Read more](/blog/payment-links-for-nmi/) - [Payment Links for GoCardless: Add Card Payment Links to Your GoCardless Setup](/blog/payment-links-for-gocardless/) - [Read more](/blog/payment-links-for-gocardless/) - [Payment Links for Mollie: Branded Checkout Links for Mollie Merchants](/blog/payment-links-for-mollie/) - [Read more](/blog/payment-links-for-mollie/) - [Payment Links for Fat Zebra: Send Branded Checkout Links for Australian Merchants](/blog/payment-links-for-fat-zebra/) - [Read more](/blog/payment-links-for-fat-zebra/) - [Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account](/blog/payment-links-for-checkout-com/) - [Read more](/blog/payment-links-for-checkout-com/) - [Payment Links for Braintree: Send Payment Links Through Your Braintree Account](/blog/payment-links-for-braintree/) - [Read more](/blog/payment-links-for-braintree/) - [Payment Links for Affirm: Send Branded Checkout Links Beyond BNPL Checkout](/blog/payment-links-for-affirm/) - [Read more](/blog/payment-links-for-affirm/) - [Navigating the Future of Travel Booking and Payments](/blog/navigating-the-future-of-travel-booking-and-payments/) - [Read more](/blog/navigating-the-future-of-travel-booking-and-payments/) - [Payment Links for Adyen: Branded Payment Links on Your Adyen Account](/blog/payment-links-for-adyen/) - [Read more](/blog/payment-links-for-adyen/) - [Modernise Receivables: How Accountants Use Shuttle Payment Links to Accelerate Cash Flow](/blog/modernise-receivables-how-accountants-use-shuttle-payment-links-to-accelerate-cash-flow/) - [Read more](/blog/modernise-receivables-how-accountants-use-shuttle-payment-links-to-accelerate-cash-flow/) - [Law Firm Payment Solutions: A Complete Guide for 2026](/blog/modernising-legal-payments-how-law-firms-use-shuttle-payment-links-to-improve-collections/) - [Read more](/blog/modernising-legal-payments-how-law-firms-use-shuttle-payment-links-to-improve-collections/) - [ACH Payment Links for Small Business: Setup, Costs & Tips](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [Read more](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [Linktree Payments: How to Add Payment Links to Your Bio](/blog/maximize-your-earnings-with-linktree-payment-links-a-step-by-step-guide/) - [Read more](/blog/maximize-your-earnings-with-linktree-payment-links-a-step-by-step-guide/) - [Freight Payment Solutions for Shipping & Logistics](/blog/keep-cargo-moving-how-freight-and-shipping-companies-speed-up-payments-with-shuttle/) - [Read more](/blog/keep-cargo-moving-how-freight-and-shipping-companies-speed-up-payments-with-shuttle/) - [Is reselling payments and becoming a PayFac right for my SaaS?](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [Read more](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [Invoicing Software for SMEs: 6 Best Tools in 2026](/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/) - [Read more](/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/) - [Introducing Smart Rules: Streamlined Checkouts and Smarter Fraud Prevention](/blog/smart-rules/) - [Read more](/blog/smart-rules/) - [QuickBooks Stripe Integration: Full Setup Guide (2026)](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [Read more](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [Does Instagram Require Linking an Email to Receive Payments? (No -- Here's How in 2026)](/blog/payment-links-for-instagram-sales/) - [Read more](/blog/payment-links-for-instagram-sales/) - [How to prevent chargebacks using ethoca](/blog/how-to-prevent-chargebacks-using-ethoca/) - [Read more](/blog/how-to-prevent-chargebacks-using-ethoca/) - [How payment processing is changing and how to make and save money](/blog/acquirers-vs-gateways/) - [Read more](/blog/acquirers-vs-gateways/) - [How payments helped Brightpearl's growth](/blog/brightpearl-growth/) - [Read more](/blog/brightpearl-growth/) - [How Payment Links can help Video Shopping Platforms](/blog/payment-links-for-video-shopping/) - [Read more](/blog/payment-links-for-video-shopping/) - [How Creators, Small Business Owners, and Solo Entrepreneurs Can Accept Payments Without a Shopping Cart](/blog/how-creators-small-business-owners-and-solo-entrepreneurs-can-accept-payments-without-a-shopping-cart/) - [Read more](/blog/how-creators-small-business-owners-and-solo-entrepreneurs-can-accept-payments-without-a-shopping-cart/) - [Get Paid Faster: How IT Services Firms Use Shuttle Payment Links to Improve Cash Flow](/blog/get-paid-faster-how-it-services-firms-use-shuttle-payment-links-to-improve-cash-flow/) - [Read more](/blog/get-paid-faster-how-it-services-firms-use-shuttle-payment-links-to-improve-cash-flow/) - [FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle](/blog/freedompay/) - [Read more](/blog/freedompay/) - [DTMF vs Payment Links: Which is More Secure for Phone Payments?](/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/) - [Read more](/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/) - [Builders who accept cards for payment are better off](/blog/building-success-how-accepting-card-payments-can-boost-your-business/) - [Read more](/blog/building-success-how-accepting-card-payments-can-boost-your-business/) - [HubSpot Payment Links: Setup, Integrations & Alternatives](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [Read more](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [9k+ QuickBooks users using Shuttle](/blog/quickbooks_casestudy/) - [Read more](/blog/quickbooks_casestudy/) - [7 ways merchants can save money on payment provider fees](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [Read more](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [5 Payment Workflows That Work Better With Payment Links](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [Read more](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [Streamline Accounts Receivable: 5 Proven Strategies](/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/) - [Read more](/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/) - [5 Reasons you shouldn't build payments integrations in-house](/blog/5-reasons-you-shouldnt-build-payments-integrations-in-house/) - [Read more](/blog/5-reasons-you-shouldnt-build-payments-integrations-in-house/) - [5 critical business frustrations and how to solve them](/blog/5-critical-business-frustrations-and-how-to-solve-them/) - [Read more](/blog/5-critical-business-frustrations-and-how-to-solve-them/) - [Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending](/blog/payment-links-for-payu/) - [Read more](/blog/payment-links-for-payu/) - [Why Your IVR Needs a Backup: Payment Links as Fallback for Voice](/blog/why-your-ivr-needs-a-backup-payment-links-as-fallback-for-voice/) - [Read more](/blog/why-your-ivr-needs-a-backup-payment-links-as-fallback-for-voice/) - [How BPOs Are Turning Every Call into a Payment Opportunity](/blog/how-bpos-are-turning-every-call-into-a-payment-opportunity/) - [Read more](/blog/how-bpos-are-turning-every-call-into-a-payment-opportunity/) - [The Future of Voice Commerce: From IVR to Intelligent Payments](/blog/the-future-of-voice-commerce/) - [Read more](/blog/the-future-of-voice-commerce/) - [The Future of Platform Payments: From Gateways to Agentic Commerce](/blog/the-future-of-payments/) - [Read more](/blog/the-future-of-payments/) - [Agentic Commerce: How AI Will Rewrite the Checkout](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [Read more](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [Read more](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [How to Launch a Payment Link Feature in Weeks, Not Months](/blog/how-to-launch-a-payment-link-feature-in-weeks-not-months/) - [Read more](/blog/how-to-launch-a-payment-link-feature-in-weeks-not-months/) - [Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) - [Read more](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) - [Are You Still Building eCommerce for Humans?](/blog/are-you-still-building-ecommerce-for-humans/) - [Read more](/blog/are-you-still-building-ecommerce-for-humans/) - [Do I Need a Full AR Platform or Just Smarter Payment Links?](/blog/do-i-need-a-full-ar-platform-or-just-smarter-payment-links/) - [Read more](/blog/do-i-need-a-full-ar-platform-or-just-smarter-payment-links/) - [How to Give Customers More Ways to Pay Your Invoices](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [Read more](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [How to Scale AR Without Hiring More Staff: A CFO's Guide](/blog/how-to-scale-ar-without-hiring-more-staff-a-cfos-guide/) - [Read more](/blog/how-to-scale-ar-without-hiring-more-staff-a-cfos-guide/) - [7 Objections Bosses Raise About Improving AR (and How to Overcome Them)](/blog/7-objections-bosses-raise-about-improving-ar-and-how-to-overcome-them/) - [Read more](/blog/7-objections-bosses-raise-about-improving-ar-and-how-to-overcome-them/) - [Agentic Commerce White Paper](/blog/agentic-commerce-white-paper/) - [Read more](/blog/agentic-commerce-white-paper/) - [Why Your AR Team Is Drowning in Manual Work (And How to Fix It)](/blog/why-your-ar-team-is-drowning-in-manual-work-and-how-to-fix-it/) - [Read more](/blog/why-your-ar-team-is-drowning-in-manual-work-and-how-to-fix-it/) - [Shuttle and PolyAI - conversational payments](/blog/shuttle-and-polyai/) - [Read more](/blog/shuttle-and-polyai/) - [What Is Local Acquiring? How It Cuts International Payment Costs](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [Read more](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [Insuretech Innovation: Choosing the Right Payment Gateway for Your Business](/blog/insuretech-innovation-choosing-the-right-payment-gateway-for-your-business/) - [Read more](/blog/insuretech-innovation-choosing-the-right-payment-gateway-for-your-business/) - [Maximize Efficiency: The Best Payment Gateways for Facilities Management](/blog/maximize-efficiency-the-best-payment-gateways-for-facilities-management-2/) - [Read more](/blog/maximize-efficiency-the-best-payment-gateways-for-facilities-management-2/) - [Event Payment Gateway: How to Choose the Right One](/blog/choosing-the-right-payment-gateway-for-your-event-software-a-comprehensive-guide/) - [Read more](/blog/choosing-the-right-payment-gateway-for-your-event-software-a-comprehensive-guide/) - [Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [Read more](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [QuickBooks ACH Payments: Setup, Fees & Tips](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [Read more](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [The future of subscriptions with Chargebee and GoCardless](/blog/the-future-of-subscriptions/) - [Read more](/blog/the-future-of-subscriptions/) - [Card Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026)](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [Read more](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [Payment Methods in Nigeria: Cards, Bank Transfers & Mobile Money (2026)](/blog/the-most-popular-payment-methods-in-nigeria/) - [Read more](/blog/the-most-popular-payment-methods-in-nigeria/) - [Maximize Efficiency: Accepting Card Payments in QuickBooks Online](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [Read more](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [Braintree vs Checkout.com - which is the right choice for an enterprise merchant?](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [Read more](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [Regulation is about to shake up online marketplaces](/blog/regulation-is-about-to-shake-up-online-marketplaces/) - [Read more](/blog/regulation-is-about-to-shake-up-online-marketplaces/) - [Emotional Payments](/blog/emotional-payments/) - [Read more](/blog/emotional-payments/) - [Payment Methods in the Netherlands: iDEAL, Cards & Klarna (2026)](/blog/the-most-popular-payment-methods-in-the-netherlands/) - [Read more](/blog/the-most-popular-payment-methods-in-the-netherlands/) - [Payment Methods in China: Alipay, WeChat Pay & UnionPay (2026)](/blog/the-most-popular-payment-methods-in-china/) - [Read more](/blog/the-most-popular-payment-methods-in-china/) - [SaaS breakthrough with EKM's CEO Antony Chesworth](/blog/saas-breakthrough-with-ekms-ceo-antony-chesworth/) - [Read more](/blog/saas-breakthrough-with-ekms-ceo-antony-chesworth/) - [Authorize.net Payment Links: Create & Send Payment Links](/blog/payment-links-for-authorize-net/) - [Read more](/blog/payment-links-for-authorize-net/) - [In-Store Payment Links: The Future of Phygital Payments](/blog/the-future-of-in-store-payments-why-payment-links-are-here-to-stay/) - [Read more](/blog/the-future-of-in-store-payments-why-payment-links-are-here-to-stay/) - [How Payment Links Improve Cash Flow for Small Businesses](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [Read more](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [Thailand Payment Methods: 7 Essential Options (2026)](/blog/the-most-popular-payment-methods-in-thailand/) - [Read more](/blog/the-most-popular-payment-methods-in-thailand/) - [The state of Open Banking Payments in May 2023](/blog/the-state-of-open-banking-payments-in-may-2023/) - [Read more](/blog/the-state-of-open-banking-payments-in-may-2023/) - [What is chargeback fraud and how merchants can avoid it](/blog/what-is-chargeback-fraud-and-how-merchants-can-avoid-it/) - [Read more](/blog/what-is-chargeback-fraud-and-how-merchants-can-avoid-it/) - [Accept Card Payments: A Complete Guide for Businesses](/blog/the-top-5-reasons-why-your-business-needs-to-accept-card-payments/) - [Read more](/blog/the-top-5-reasons-why-your-business-needs-to-accept-card-payments/) - [Best Payment Gateways UK 2026: Fees, Features & Integration Compared](/blog/best-payment-gateways-for-uk-businesses-comparison/) - [Read more](/blog/best-payment-gateways-for-uk-businesses-comparison/) - [Shuttle and Kount work together to provide fraud prevention at scale](/blog/shuttle-and-kount-work-together-to-provide-fraud-prevention-at-scale/) - [Read more](/blog/shuttle-and-kount-work-together-to-provide-fraud-prevention-at-scale/) - [Improve your cash flow. Stop waiting to get your invoices paid](/blog/improve-your-cash-flow-stop-waiting-to-get-your-invoices-paid/) - [Read more](/blog/improve-your-cash-flow-stop-waiting-to-get-your-invoices-paid/) - [Brazil Payment Methods: Top 8 Ways Brazilians Pay (2026)](/blog/the-most-popular-payment-methods-in-brazil/) - [Read more](/blog/the-most-popular-payment-methods-in-brazil/) - [The Cheapest Operation not the Cheapest Processing](/blog/payment-operation/) - [Read more](/blog/payment-operation/) - [Payment Methods in the UK: Cards, Open Banking & Digital Wallets (2026)](/blog/the-most-popular-payment-methods-in-the-united-kingdom/) - [Read more](/blog/the-most-popular-payment-methods-in-the-united-kingdom/) - [Payment Methods in the USA: Cards, ACH, Venmo & Wallets (2026)](/blog/the-most-popular-payment-methods-in-the-usa/) - [Read more](/blog/the-most-popular-payment-methods-in-the-usa/) - [Checkout Optimization: 12 Proven Strategies to Increase Conversion Rates](/blog/optimizing-checkout-process-the-ultimate-guide-to-checkout-rate-optimization/) - [Read more](/blog/optimizing-checkout-process-the-ultimate-guide-to-checkout-rate-optimization/) - [Best UK Payment Providers - The definitive guide](/blog/best-uk-payment-providers-the-definitive-guide/) - [Read more](/blog/best-uk-payment-providers-the-definitive-guide/) - [What Is a Payment Gateway? How It Works, Costs & Top Providers](/blog/what-is-a-payment-gateway/) - [Read more](/blog/what-is-a-payment-gateway/) - [Maximizing Revenue and Customer Satisfaction with Payment Solutions for Marketplaces](/blog/marketplace-payments/) - [Read more](/blog/marketplace-payments/) - [Updates from the UK Payment Systems Regulator for 2023](/blog/updates-from-the-uk-payment-systems-regulator-for-2023/) - [Read more](/blog/updates-from-the-uk-payment-systems-regulator-for-2023/) - [Chargeback protection market review](/blog/chargeback-protection-market-review/) - [Read more](/blog/chargeback-protection-market-review/) - [Global Payments: International Solutions for Business](/blog/global-payments-for-online-and-offline-businesses/) - [Read more](/blog/global-payments-for-online-and-offline-businesses/) - [Account Updater Service: How It Works for Card Payments](/blog/should-i-use-account-updater-services-for-card-payments/) - [Read more](/blog/should-i-use-account-updater-services-for-card-payments/) - [Morocco Payment Methods: Top 7 for Online & In-Store](/blog/the-most-popular-payment-methods-in-morocco/) - [Read more](/blog/the-most-popular-payment-methods-in-morocco/) - [What Is a PISP? Open Banking Payment Initiation Explained](/blog/what-is-open-banking-and-pisp/) - [Read more](/blog/what-is-open-banking-and-pisp/) - [Payments for Marketplaces](/blog/payments-for-marketplaces/) - [Read more](/blog/payments-for-marketplaces/) - [Savour the Convenience: How Payment Links are Revolutionizing Food and Beverage Ordering](/blog/savour-the-convenience-how-payment-links-are-revolutionizing-food-and-beverage-ordering/) - [Read more](/blog/savour-the-convenience-how-payment-links-are-revolutionizing-food-and-beverage-ordering/) - [Payment Methods in France: Carte Bancaire, PayPal & Wallets (2026)](/blog/the-most-popular-payment-methods-in-france/) - [Read more](/blog/the-most-popular-payment-methods-in-france/) - [Payment Methods in Indonesia: GoPay, OVO & Bank Transfers (2026)](/blog/the-most-popular-payment-methods-in-indonesia/) - [Read more](/blog/the-most-popular-payment-methods-in-indonesia/) - [Egypt Payment Methods: 8 Ways Egyptians Pay (2026)](/blog/the-most-popular-payment-methods-in-egypt/) - [Read more](/blog/the-most-popular-payment-methods-in-egypt/) - [Payment Methods in Germany: PayPal, SEPA & Klarna (2026)](/blog/the-most-popular-payment-methods-in-germany/) - [Read more](/blog/the-most-popular-payment-methods-in-germany/) - [Open Banking payments is using the wrong Go To Market strategy](/blog/ob-gtm/) - [Read more](/blog/ob-gtm/) - [What is a merchant account?](/blog/what-is-a-merchant-account/) - [Read more](/blog/what-is-a-merchant-account/) - [What Is an AISP? Open Banking Account Information Explained](/blog/what-is-open-banking-and-aisp/) - [Read more](/blog/what-is-open-banking-and-aisp/) - [Payment Methods in New Zealand: Cards, POLi & Afterpay (2026)](/blog/the-most-popular-payment-methods-in-new-zealand/) - [Read more](/blog/the-most-popular-payment-methods-in-new-zealand/) - [Ecommerce Fraud Prevention: A Merchant's Guide for 2026](/blog/a-merchants-guide-to-ecommerce-fraud-prevention/) - [Read more](/blog/a-merchants-guide-to-ecommerce-fraud-prevention/) - [Payment Methods in the Philippines: GCash, Cards & COD (2026)](/blog/the-most-popular-payment-methods-in-the-philippines/) - [Read more](/blog/the-most-popular-payment-methods-in-the-philippines/) - [Payment Methods in Malaysia: FPX, GrabPay & Credit Cards (2026)](/blog/the-most-popular-payment-methods-in-malaysia/) - [Read more](/blog/the-most-popular-payment-methods-in-malaysia/) - [Payment Methods in Poland: BLIK, Przelewy24 & Cards (2026)](/blog/the-most-popular-payment-methods-in-poland/) - [Read more](/blog/the-most-popular-payment-methods-in-poland/) - [Adyen vs Stripe - which is the right choice for an enterprise merchant?](/blog/adyen-vs-stripe/) - [Read more](/blog/adyen-vs-stripe/) - [Authorize.net QuickBooks Integration: Full Guide](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [Read more](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [How to Maximize the Travel Boom](/blog/how-to-maximize-the-travel-boom/) - [Read more](/blog/how-to-maximize-the-travel-boom/) - [Payment Methods in South Africa: Cards, EFT & Mobile Wallets (2026)](/blog/the-most-popular-payment-methods-in-south-africa/) - [Read more](/blog/the-most-popular-payment-methods-in-south-africa/) - [Payment Methods in Vietnam: MoMo, Cards & Bank Transfers (2026)](/blog/the-most-popular-payment-methods-in-vietnam/) - [Read more](/blog/the-most-popular-payment-methods-in-vietnam/) - [Dropping some knowledge on Buy Now Pay Later](/blog/dropping-some-knowledge-on-buy-now-pay-later/) - [Read more](/blog/dropping-some-knowledge-on-buy-now-pay-later/) - [Maximizing Sales: The Benefits of Integrating Shopping Carts and ERPs for Merchants](/blog/maximizing-sales-the-benefits-of-integrating-shopping-carts-and-erps-for-merchants/) - [Read more](/blog/maximizing-sales-the-benefits-of-integrating-shopping-carts-and-erps-for-merchants/) - [Payment Gateway Integration: How to Add Payments to Your App or Platform](/blog/the-ultimate-guide-to-integrating-a-payment-gateway-into-your-app/) - [Read more](/blog/the-ultimate-guide-to-integrating-a-payment-gateway-into-your-app/) - [Transforming business with payments](/blog/transforming-business-with-payments/) - [Read more](/blog/transforming-business-with-payments/) - [Payment Methods in Canada: Credit Cards, Interac, PayPal & More (2026)](/blog/the-most-popular-payment-methods-in-canada/) - [Read more](/blog/the-most-popular-payment-methods-in-canada/) - [How to Accept Payments in QuickBooks: Full Guide](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [Read more](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [Secure Payment Links: Card Authorization Made Simple](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [Read more](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [Shuttle and Brightpearl Partner to enable invoice and POS Payments for Global Retailers](/blog/shuttle-and-brightpearl/) - [Read more](/blog/shuttle-and-brightpearl/) --- URL: https://www.shuttleglobal.com/blog/insurance-billing-vs-payment-execution/ --- # Insurance Billing vs Payment Execution: Why Your Platform Needs Both | Shuttle > Every insurance core platform has billing. Almost none execute payments. Here's why billing and payment execution are different things -- and what changes... # Insurance Billing vs Payment Execution: Why Your Platform Needs Both By Nick Dunse, February 22, 2026 Every insurance core platform has billing. Almost none execute payments. Here's why billing and payment execution are different things -- and what changes... Every insurance core platform has billing. It's foundational. Installment schedules, invoice generation, delinquency tracking, reconciliation, premium calculations -- billing is what makes the financial engine of a policy admin system work. But billing manages what's owed. It doesn't collect the money. When it's time to actually capture a card, route to a processor, confirm a transaction, and settle funds -- the platform hands off. The carrier figures it out. A third-party portal takes over. The policyholder leaves the platform workflow. This is the gap between billing and payment execution. And it's the biggest missed opportunity for insurance core platforms today. ## What Billing Does Billing modules in insurance core platforms are sophisticated. They handle: - Premium calculations -- based on policy terms, risk factors, endorsements, and regulatory requirements - Installment schedules -- monthly, quarterly, annual, with configurable grace periods - Invoice generation -- automated billing statements for each policy - Delinquency tracking -- overdue detection, lapse warnings, reinstatement conditions - Reconciliation -- matching received payments to outstanding invoices - Reporting -- premium revenue, aging reports, loss ratios This is core platform functionality. It's well-built, deeply integrated with the policy lifecycle, and essential. ## What Billing Doesn't Do Billing doesn't execute payments. It doesn't: - Capture card details -- no card number entry, no DTMF capture during phone calls - Route to PSPs -- no connection to Stripe, Adyen, Worldpay, or any payment processor - Handle PCI compliance -- no card data encryption, tokenisation, or secure storage - Collect via voice -- no ability to take a payment during a phone renewal or collections call - Send payment links -- no SMS or email links for overdue premium collection - Manage multi-PSP routing -- no ability to route Carrier A's payments to Stripe and Carrier B's to Worldpay The billing module knows that £450 is due on Policy #12345 by March 15. It cannot collect that £450. ## The Gap: Carriers Solving Payments Outside the Platform When the platform doesn't execute payments, carriers default to workarounds. Separate payment portals. The carrier sets up a standalone payment page. Policyholders navigate away from the platform. Reconciliation is manual. Data lives in two places. Phone dictation. Agents read card numbers aloud, type them into terminals. This works but creates PCI scope for the contact centre and compliance risk for the carrier. Paper and batch. Checks, direct debit mandates, bank transfers processed outside the platform. Reconciliation is slow. Cash flow forecasting suffers. Every workaround shares the same problem: the payment happens outside the platform. The platform has no visibility. No revenue participation. No ability to improve the experience. ## What Changes When Payment Execution Is Native When payment execution lives inside the core platform, the dynamics shift. Renewal calls close on the call. A policyholder phones about a renewal. The agent confirms the premium and triggers secure payment capture within the conversation. DTMF tones capture card digits. The payment processes through the carrier's PSP. The call ends with confirmation. No transfer. No "go online." Overdue premiums collected in two taps. The billing module detects an overdue installment and sends a branded payment link via SMS. The policyholder pays immediately. The billing module updates automatically. New policies bind with payment. The embedded checkout captures the first premium during the digital application. Card details are tokenised for recurring collection. Every carrier uses their own PSP. Payment execution is PSP-neutral. Allianz routes to their processor. AXA routes to theirs. No carrier is forced to change. The platform captures revenue. Every premium that flows through the platform generates revenue share. No capital outlay beyond the initial integration. ## The Payment Layer: One Integration, Any PSP, Any Channel The reason insurance platforms haven't added payment execution isn't that it's impossible. It's that the infrastructure didn't exist. Building multi-PSP support, PCI compliance, voice payment capture, and payment links -- for a multi-carrier, multi-country platform -- would take 12+ months of dedicated development and $2M+ in compliance investment. The Payment Layer collapses that into a single integration. The platform connects once. Each carrier uses their existing PSP. Voice, links, and embedded checkout work through the same integration. PCI DSS Level 1 compliance stays with the layer -- the platform never touches card data. Billing manages what's owed. The Payment Layer collects the money. Together, they turn an insurance core platform into a payment execution engine. For the full picture, see our guide: Payments for Insurance Core Platforms. *Shuttle is The Payment Layer for insurance platforms. One integration. Any carrier's PSP. Voice, links, and embedded checkout. See how it works or book a discovery call.* ## Related Reading Explore More ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Solutions for Medical Billing Companies and RCM Firms ### Payments for Insurance Carriers and MGA Platforms ### PCI-Compliant Payment Architecture for Insurance Platforms ### Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure ### AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [DTMF capture](/guides/dtmf-payments/) - [PCI scope](/glossary/pci-scope/) - [payment link](/merchants/links-checkout/) - [PSP-neutral](/guides/psp-neutral-vs-single-psp/) - [The Payment Layer](/guides/payment-layer-explained/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payments for Insurance Core Platforms](/guides/payments-for-insurance-platforms/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuidePayment Solutions for Medical Billing Companies and RCM Firms→](/guides/medical-billing-payments/) - [GuidePayments for Insurance Carriers and MGA Platforms→](/guides/payments-for-insurance-carriers-mga/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [GuidePayments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-insurance-platforms/) - [GuideAI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk→](/guides/ai-voice-payments-insurance/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/insurance-call-centre-payments/ --- # Why Insurance Call Centres Still Can't Take a Secure Payment | Shuttle > Millions of insurance calls per day involve a payment moment. Most call centres handle it badly. # Why Insurance Call Centres Still Can't Take a Secure Payment By Nick Dunse, February 20, 2026 Millions of insurance calls per day involve a payment moment. Most call centres handle it badly. Millions of insurance calls happen every day. Renewals. Collections. Claim queries. Policy changes. A significant percentage of those calls involve a payment moment -- the policyholder needs to pay a premium, settle an excess, or clear an overdue balance. And in most insurance call centres, that moment is handled badly. The agent says: "I'll transfer you to our automated payment line." Or: "Can you read me your card number?" Or: "I'll send you a link -- please check your email after we hang up." Every one of these is a failure mode. The IVR transfer drops calls. Reading card numbers creates PCI exposure. Sending a link after the call means the payment might never happen. The underlying problem isn't the agents. It's the infrastructure. ## The PCI Problem The moment card data enters the audio stream of a call centre, everything is in scope. - The agent's headset? In scope. - The call recording system? In scope. - The quality monitoring feed? In scope. - The desktop where the agent works? In scope. - The network connecting all of those systems? In scope. PCI DSS doesn't care that the contact centre is an insurance operation, not a payments company. If card data is present -- spoken, keyed, or displayed -- the full compliance framework applies. For insurance contact centres, this creates an impossible position. They can't avoid payment conversations. And they can't handle card data without massive compliance overhead. The result: most insurance call centres punt payments to somewhere else. Transfer to IVR. Redirect to a website. Mail a payment slip. Every alternative adds friction. Every one loses conversions. ## The Architecture That Fixes It The fix is architectural, not procedural. Card data must never enter the contact centre's audio environment. Here's how it works: 1. The agent reaches the payment moment. The policyholder confirms they want to pay. 2. The call enters a secure payment segment. The agent triggers the payment flow -- from their desktop, their CRM, or the core platform's interface. 3. The policyholder enters card details via DTMF. Keypad tones are captured within a PCI-certified environment -- not the contact centre's telephony stack. 4. DTMF tones are stripped from the audio stream. The digits never reach the agent. Call recordings capture no card data. Quality monitoring feeds are clean. 5. The payment processes through the carrier's PSP. The transaction routes to whichever processor the carrier uses -- Stripe, Adyen, Worldpay, or a regional acquirer. 6. The agent receives confirmation. "Payment approved" appears on screen. The conversation resumes. The agent never hears card data. The recording never contains it. The contact centre's PCI scope drops from SAQ-D to SAQ-A. The difference in annual compliance cost is hundreds of thousands of pounds. ## Allianz Is Already Doing This Allianz runs call centre payments through Shuttle across 3 countries. Each country routes to Allianz's contracted processors. Agents trigger payment capture mid-call. DTMF tones are captured in Shuttle's PCI DSS Level 1 certified infrastructure. The contact centre's scope stays limited. This isn't a pilot. It's production. ## What About AI Voice Agents? The same architecture extends to AI voice agents -- and this is where insurance gets interesting. AI voice agents from companies like PolyAI now handle insurance conversations at scale: renewals, collections, policy queries. When the AI agent reaches a payment moment, it triggers the same secure capture flow. The policyholder enters card details via DTMF. The payment processes. The AI confirms. No human involved. PolyAI achieves a 75% voice payment completion rate with zero human handoffs: "Shuttle let us treat legacy payment providers as a modern SaaS service. It enabled us to support the gateways our customers required and fully automate high-value transactions across regulated industries." For insurance call centres processing thousands of renewal and collections calls daily, AI voice payments represent a step change in efficiency and conversion. For a deeper look at the architecture, see How AI Voice Agents Take PCI-Compliant Payments. ## What This Means for Insurance Core Platforms If you're building an insurance core platform -- policy admin, billing, claims -- voice payment execution should be native to your platform. Not a separate system. Not a partner the carrier manages independently. When voice payments are embedded in the core platform: - Every carrier's contact centre (or AI agent) captures payments through the platform - Each carrier routes to their own PSP -- no carrier is forced to switch - PCI compliance is handled by The Payment Layer -- the platform's scope stays limited - The platform captures revenue on every transaction The billing module tracks what's owed. The Payment Layer collects the money. The call centre is where it happens. For the full guide to adding payment execution to your insurance platform, see Payments for Insurance Core Platforms. *Shuttle is The Payment Layer for insurance platforms. PCI DSS Level 1 certified. 40+ PSPs. Voice, links, and embedded checkout. See how it works or book a discovery call.* ## Related Reading Explore More ### Payments for Insurance Carriers and MGA Platforms ### Call Center Payment Processing: PCI Compliant Payments Guide (2026) ### Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure ### AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk ### PCI-Compliant Payment Architecture for Insurance Platforms ### Agent-Assisted Payments: Secure Card Capture on Live Calls ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PCI DSS](/glossary/pci-dss/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [PCI scope](/glossary/pci-scope/) - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [no carrier is forced to switch](/guides/enterprise-psp-mandates/) - [The Payment Layer](/guides/payment-layer-explained/) - [Payments for Insurance Core Platforms](/guides/payments-for-insurance-platforms/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [GuidePayments for Insurance Carriers and MGA Platforms→](/guides/payments-for-insurance-carriers-mga/) - [GuideCall Center Payment Processing: PCI Compliant Payments Guide (2026)→](/guides/contact-centre-payments/) - [GuidePayments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-insurance-platforms/) - [GuideAI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk→](/guides/ai-voice-payments-insurance/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/insuretech-innovation-choosing-the-right-payment-gateway-for-your-business/ --- # Insuretech Innovation: Choosing the Right Payment Gateway for Your Business | Shuttle > How insurtech companies choose the right payment gateway. Covers premium collection, recurring billing, multi-carrier payments, and PCI compliance for... # Insuretech Innovation: Choosing the Right Payment Gateway for Your Business By Nick Dunse, June 11, 2024 How insurtech companies choose the right payment gateway. Covers premium collection, recurring billing, multi-carrier payments, and PCI compliance for... Talk to us Make enabling payments for your platform and merchant users easy. In today's digital age, the insurance industry is undergoing a significant transformation with the emergence of innovative technologies, commonly referred to as insuretech. Insuretech innovation is revolutionizing the way insurance companies operate, from underwriting and claims processing to customer engagement and payment processing. This wave of technological advancements is reshaping the insurance landscape, offering new opportunities for insurers to streamline their operations, enhance customer experience, and drive business growth. One of the key areas of focus in insuretech innovation is the integration of payment gateways into insurance platforms. Payment gateways play a crucial role in facilitating secure and seamless online transactions, allowing insurance companies to accept payments from policyholders and process claims efficiently. As such, choosing the right payment gateway is essential for insurers looking to leverage technology to improve their business operations and stay ahead in the competitive insurance market. Key Takeaways - Insuretech innovation is crucial for the success of insurance businesses in the digital age. - Payment gateways play a vital role in the insuretech industry, enabling secure and seamless transactions. - When choosing a payment gateway for an insuretech business, factors such as cost, integration, and customer experience should be carefully considered. - Security and compliance are paramount when selecting a payment gateway for insuretech, as sensitive customer data is involved. - Emerging trends in payment gateway technology, such as biometric authentication and blockchain, are shaping the future of insuretech transactions. The Role of Payment Gateways in Insuretech Payment gateways serve as the bridge between insurance companies and their customers, enabling secure and convenient payment processing for policy premiums, deductibles, and claims settlements. These gateways are responsible for encrypting sensitive payment information, authorizing transactions, and facilitating the transfer of funds between the insurer and the policyholder. In addition to processing payments, payment gateways also play a critical role in enhancing the overall customer experience by providing a seamless and user-friendly payment interface. In the context of insuretech, payment gateways are instrumental in enabling digital transformation within the insurance industry. By integrating advanced payment gateway solutions into their platforms, insurers can offer customers a range of payment options, including credit/debit card payments, bank transfers, and digital wallets. This not only enhances convenience for policyholders but also helps insurers streamline their payment processing workflows, reduce administrative costs, and improve cash flow management. As such, payment gateways are a fundamental component of insuretech innovation, enabling insurers to modernize their payment infrastructure and adapt to evolving customer preferences and industry trends. Factors to Consider When Choosing a Payment Gateway for Your Insuretech Business When selecting a payment gateway for an insuretech business, there are several key factors that insurers should consider to ensure they choose a solution that aligns with their specific needs and objectives. Firstly, insurers should evaluate the security features offered by the payment gateway to ensure that customer payment data is protected from unauthorized access and fraud. This includes encryption protocols, tokenization, and compliance with industry security standards such as PCI DSS. Secondly, insurers should assess the compatibility of the payment gateway with their existing technology infrastructure, including their insurance platform, CRM system, and accounting software. Seamless integration with these systems is essential to ensure smooth payment processing and accurate reconciliation of transactions. Additionally, insurers should consider the scalability and flexibility of the payment gateway to accommodate future growth and expansion of their business operations. Security and Compliance Considerations for Insuretech Payment Gateways Payment Gateway | Transaction Fees | Supported Currencies | Integration Options Stripe | 2.9% + 30¢ per successful charge | 135+ | API, Checkout, Elements PayPal | 2.9% + 30¢ per transaction | 25+ | API, Express Checkout, Braintree Authorize.Net | 2.9% + 30¢ per transaction | 160+ | API, hosted payment page "`Security and compliance are paramount considerations when choosing a payment gateway for an insuretech business. Insurers must ensure that the payment gateway they select adheres to industry regulations and standards for data security and privacy. This includes compliance with the Payment Card Industry Data Security Standard (PCI DSS), which sets requirements for handling cardholder data securely. In addition to regulatory compliance, insurers should also evaluate the security features offered by the payment gateway to protect sensitive customer payment information from unauthorized access and fraud. This includes encryption of data transmission, tokenization of card details, and robust authentication measures to prevent unauthorized transactions. By prioritizing security and compliance in their choice of payment gateway, insurers can instill trust and confidence in their customers while safeguarding their business from potential security breaches and regulatory penalties. Integrating Payment Gateways with Insuretech Platforms Seamless integration of payment gateways with insuretech platforms is essential to ensure efficient payment processing and a seamless customer experience. Insurers should look for payment gateway solutions that offer easy integration with their existing technology infrastructure, including their insurance platform, CRM system, and accounting software. This integration should enable real-time synchronization of payment data, automated reconciliation of transactions, and seamless communication between the payment gateway and other systems. Furthermore, insurers should consider the availability of developer tools and APIs that allow for custom integration and customization of the payment gateway to meet their specific business requirements. By integrating the payment gateway with their insuretech platform, insurers can streamline their payment processing workflows, improve operational efficiency, and provide customers with a frictionless payment experience across various channels and devices. The Impact of Payment Gateway Selection on Customer Experience in Insuretech The selection of a payment gateway has a direct impact on the overall customer experience in insuretech. A well-chosen payment gateway can enhance customer satisfaction by providing a seamless and secure payment experience, while a poorly chosen gateway can lead to frustration and dissatisfaction among policyholders. Insurers should prioritize user-friendly interfaces, fast transaction processing times, and support for multiple payment methods to cater to diverse customer preferences. Moreover, the integration of advanced features such as recurring billing, mobile payments, and digital wallets can further enhance the customer experience by offering greater convenience and flexibility in managing insurance payments. By choosing a payment gateway that prioritizes customer experience, insurers can differentiate themselves in the market, build loyalty among policyholders, and drive higher retention rates. Emerging Trends in Payment Gateway Technology for Insuretech The landscape of payment gateway technology is constantly evolving, driven by advancements in digital payments, cybersecurity, and customer expectations. In the context of insuretech, insurers should stay abreast of emerging trends in payment gateway technology to capitalize on new opportunities for innovation and differentiation. One such trend is the rise of contactless payments and mobile wallets, which offer a convenient and secure alternative to traditional card-based transactions. Another emerging trend is the adoption of artificial intelligence (AI) and machine learning in payment gateways to detect fraud, personalize customer experiences, and optimize transaction routing. Additionally, blockchain technology is gaining traction as a means to enhance transparency and security in payment processing, offering potential benefits for insurers looking to streamline claims settlements and reduce fraud. In conclusion, choosing the right payment gateway is a critical decision for insuretech businesses looking to leverage technology to improve their operations and customer experience. By considering factors such as security, compliance, integration capabilities, and customer experience, insurers can select a payment gateway that aligns with their specific needs and objectives. Furthermore, staying informed about emerging trends in payment gateway technology can help insurers stay ahead of the curve and capitalize on new opportunities for innovation in the evolving insuretech landscape. ## Related Reading Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/ --- # Invoicing Software for SMEs: 6 Best Tools in 2026 | Shuttle > Compare the best invoicing software for small businesses. Covers features, pricing, payment integration, and how to get invoices paid faster. # Invoicing Software for SMEs: 6 Best Tools in 2026 By Nick Dunse, January 5, 2026 Compare the best invoicing software for small businesses. Covers features, pricing, payment integration, and how to get invoices paid faster. Talk to us Make enabling payments for your platform and merchant users easy. Late payments cost small businesses billions every year. The right invoicing software can cut your average collection time in half -- but with dozens of options on the market, choosing the right tool is harder than it should be. This guide breaks down what to look for in invoicing software, compares six of the best platforms for SMEs, and explains how embedded payment links are changing the way businesses get paid. ## What to Look for in Invoicing Software Not all invoicing tools are created equal. Before comparing platforms, it helps to know which features actually move the needle for small businesses. Here are the capabilities that matter most. Automation is the single biggest time-saver. Look for software that handles recurring invoices, automatic payment reminders, and overdue notifications without manual intervention. A business sending 50 invoices a month can save 10+ hours by automating these tasks alone. Payment integration is equally critical. Invoices that include a direct pay-now link get settled significantly faster than those requiring manual bank transfers. The best invoicing platforms either integrate with payment gateways natively or support embedded payment links that let customers pay by card, bank transfer, or digital wallet directly from the invoice. Multi-currency support matters if you trade internationally. Even small businesses increasingly work with overseas clients, and sending invoices in the recipient's local currency reduces friction and speeds up payment. Tax compliance features -- automatic VAT/GST calculations, Making Tax Digital (MTD) compatibility, and tax report generation -- save you from manual spreadsheet work and reduce the risk of errors at filing time. Finally, consider reporting and analytics. Knowing your average days-to-payment, outstanding receivables, and top-paying clients helps you make better cash flow decisions. ## Best Invoicing Software for SMEs We've compared six invoicing platforms that are popular with small and medium-sized businesses. Each has different strengths depending on your size, budget, and how you collect payments. ### QuickBooks Online QuickBooks is the most widely used accounting and invoicing platform for small businesses. It offers customisable invoice templates, automatic payment reminders, recurring invoices, and built-in payment acceptance through QuickBooks Payments. Pros: Extensive third-party integrations, strong reporting, payroll add-on, MTD-compatible. Cons: Gets expensive as you add users and features; the interface can feel cluttered for businesses that only need invoicing. If you're already using QuickBooks, our QuickBooks guide to accepting online payments walks through the setup step by step. ### Xero Xero is a strong alternative to QuickBooks, particularly popular in the UK, Australia, and New Zealand. Its invoicing features include automatic reminders, multi-currency invoicing, bank reconciliation, and a clean, modern interface that's easier to navigate than some competitors. Pros: Unlimited users on all plans, excellent bank feeds, strong app marketplace. Cons: Limited reporting on lower-tier plans; payment processing requires third-party integration (Stripe or GoCardless). ### FreshBooks FreshBooks is purpose-built for freelancers and small service businesses. It's the simplest tool on this list to get started with, and its invoicing workflow is fast -- you can create and send a professional invoice in under two minutes. Pros: Excellent time tracking and project management, intuitive interface, built-in payment acceptance. Cons: Limited inventory management; not ideal for product-based businesses or those needing advanced accounting. ### Wave Wave offers genuinely free invoicing and accounting software, making it a compelling option for sole traders and micro-businesses. There are no monthly fees for the core invoicing and accounting features -- Wave monetises through optional payment processing and payroll services. Pros: Free core product, unlimited invoices, simple interface. Cons: No multi-currency invoicing, limited integrations, payment processing only available in the US and Canada. ### Zoho Invoice Zoho Invoice is a free, standalone invoicing tool that's part of the broader Zoho ecosystem. If you already use Zoho CRM, Zoho Books, or other Zoho products, Invoice integrates seamlessly. It supports automated payment reminders, time tracking, multi-currency invoicing, and a customer portal. Pros: Completely free (no paid tiers), strong automation, excellent if you're in the Zoho ecosystem. Cons: Limited standalone reporting; fewer payment gateway integrations than QuickBooks or Xero. ### Sage Business Cloud Accounting Sage has been a staple of UK small business accounting for decades. The cloud version offers invoicing, bank reconciliation, tax calculations, and cash flow forecasting. It's a solid choice for businesses that want a traditional, well-supported platform. Pros: Strong UK tax compliance, established brand with extensive support, good for businesses transitioning from desktop Sage. Cons: Interface feels dated compared to Xero and FreshBooks; fewer modern integrations. ## Free vs Paid Invoicing Software Free invoicing tools like Wave and Zoho Invoice are genuinely useful for businesses with straightforward needs -- sole traders, freelancers, and micro-businesses sending fewer than 100 invoices per month. However, free tools typically come with trade-offs. You'll usually find limited integrations, basic reporting, fewer payment options, and restricted multi-currency support. As your business grows, these limitations start costing you more in time than a paid subscription would. Paid platforms like QuickBooks, Xero, and FreshBooks offer deeper automation, richer integrations, better reporting, and more payment acceptance options. If you're sending more than 50 invoices a month, managing multiple currencies, or need tight integration with your accounting workflow, the investment typically pays for itself through faster collections and less manual work. The key question isn't 'free or paid?' -- it's whether your current invoicing process is costing you more in late payments and admin time than the monthly fee of a better tool. ## Adding Payment Links to Invoices The fastest way to reduce days sales outstanding (DSO) is to make it as easy as possible for customers to pay. Payment links -- clickable URLs that take the payer directly to a hosted checkout page -- are one of the most effective ways to do this. When you embed a payment link in an invoice, the customer clicks the link, enters their card details (or selects a saved payment method), and the payment is processed immediately. No logging into a portal. No copying bank account numbers. No waiting for a manual transfer to clear. For a deeper look at how this works in practice, read our guide on payment links on invoices. Most invoicing platforms now support payment links natively or through third-party payment providers. If your current software doesn't support embedded payments, you can generate standalone payment links through a payment infrastructure provider and paste them into your invoices manually. For invoicing platforms and SaaS products that want to offer payment links as a built-in feature for their users, embedded payment infrastructure makes this possible without building payment processing from scratch. Shuttle's payment links, for example, can be white-labelled and embedded directly into any invoicing workflow via API. ## Invoicing Automation Tips for Faster Payments Choosing the right software is only half the battle. How you configure your invoicing workflow determines how fast you actually get paid. Here are proven automation strategies that reduce manual chasing. Set up recurring invoices. If you bill the same clients monthly, configure recurring invoices that send automatically. This eliminates the risk of forgetting to send an invoice -- a surprisingly common cause of late payments. Enable automatic payment reminders. Schedule reminders at 3 days before due date, on the due date, and at 7 and 14 days overdue. Most invoicing platforms support this natively, and it removes the awkwardness of manually chasing clients. Offer multiple payment methods. Don't limit customers to a single payment option. Accepting cards, bank transfers, and digital wallets increases the likelihood that a customer pays immediately rather than putting it off. Invoice immediately after delivery. Businesses that send invoices the same day they deliver a product or service get paid an average of 10 days faster than those that wait a week. Shorten your payment terms. Net-30 is traditional, but many SMEs have shifted to Net-14 or even Net-7. Shorter terms set clearer expectations and reduce the cash flow gap. For more strategies on reducing late payments, see our guide on streamlining your accounts receivable process. ## How Invoicing Platforms Can Embed Payments If you build or operate an invoicing platform -- whether it's a standalone SaaS product, part of an ERP system, or a vertical-specific tool -- your users expect payment collection to work out of the box. The challenge is that building payment processing in-house is complex, expensive, and comes with PCI compliance obligations. Most invoicing platforms solve this by integrating with a payment infrastructure provider that handles the processing, compliance, and settlement. Shuttle provides embedded payment infrastructure for platforms, including white-label payment links that can be generated via API and embedded into any invoice template. This means your users can collect card payments, bank transfers, and alternative payment methods without leaving your platform. If you're exploring how to add payments to your invoicing product, book a discovery call to discuss your integration requirements. ## Giving Customers Easier Ways to Pay One of the most overlooked reasons invoices go unpaid isn't that customers don't want to pay -- it's that paying is inconvenient. Every extra step in the payment process increases the chance an invoice sits in someone's inbox for days. Modern invoicing software addresses this by offering multiple payment channels directly from the invoice. Card payments, direct debit, Apple Pay, Google Pay, and even buy-now-pay-later options all reduce friction. Our article on giving customers easier ways to pay invoices explores how shifting from chasing payments to offering choice fundamentally changes collection rates. The principle is simple: the more ways a customer can pay, the faster they will. ## Frequently Asked Questions ### What is the best free invoicing software for small businesses? Wave and Zoho Invoice are the two strongest free options. Wave offers free invoicing and accounting with no monthly fees, though payment processing is a paid add-on. Zoho Invoice is completely free with strong automation features, but works best if you're already in the Zoho ecosystem. For UK-based businesses, Wave's lack of multi-currency support may be a dealbreaker, making Zoho the better choice. ### How do payment links on invoices work? A payment link is a unique URL embedded in an invoice that directs the payer to a hosted checkout page. The customer clicks the link, enters their payment details, and the transaction is processed immediately. The invoice amount, reference, and merchant details are pre-populated, so there's no room for error. Payment links can be generated by your invoicing software, your payment provider, or through a payment infrastructure API. ### What features should invoicing software have for UK businesses? UK businesses should prioritise Making Tax Digital (MTD) compatibility, automatic VAT calculations, GBP and multi-currency support, Open Banking payment options, and bank feed integration with UK banks. QuickBooks, Xero, and Sage all offer strong UK-specific compliance features. If you trade internationally, multi-currency invoicing and automatic exchange rate lookups are essential. ### Can I add payment collection to my own invoicing software? Yes. If you operate an invoicing platform or SaaS product, you can embed payment collection using a payment infrastructure provider like Shuttle. This typically involves API integration to generate payment links or embed a checkout flow directly into your invoice templates. The provider handles PCI compliance, payment processing, and settlement, so you don't need to build or maintain payment infrastructure yourself. ## Choosing the Right Invoicing Software The best invoicing software for your business depends on three things: your volume, your budget, and how important fast payment collection is to your cash flow. For freelancers and sole traders, Wave or Zoho Invoice provide a solid free starting point. For growing SMEs that need deeper automation, multi-currency support, and integrated payments, QuickBooks, Xero, or FreshBooks are worth the investment. And for businesses where payment speed is critical, make sure your chosen platform supports payment links -- they're the single most effective way to reduce time-to-payment. Whatever tool you choose, the principles are the same: automate everything you can, make it easy for customers to pay, and track your receivables closely. The difference between 45-day and 14-day average payment terms often comes down to software and process, not customer intent. ## Related Reading - How to Add a Pay Now Button to Your Invoices - Xero Payment Links: Collect Invoice Payments Faster - Sage Invoice Payments: How to Let Customers Pay Online Explore More ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ### Payment Solutions for Car Dealerships & Auto Finance Platforms ### How PSPs Get Distribution Into Enterprise Software ### Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Solutions for Medical Billing Companies and RCM Firms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [QuickBooks guide to accepting online payments](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [payment links on invoices](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [embedded payment infrastructure](/platforms/) - [streamlining your accounts receivable process](/blog/5-proven-strategies-to-streamline-your-accounts-receivable-process/) - [embedded payment infrastructure for platforms](/platforms/) - [book a discovery call](/discovery/) - [giving customers easier ways to pay invoices](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [How to Add a Pay Now Button to Your Invoices](/guides/pay-now-button-invoices/) - [Xero Payment Links: Collect Invoice Payments Faster](/blog/xero-payment-links/) - [Sage Invoice Payments: How to Let Customers Pay Online](/blog/sage-invoice-payments/) - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [GuidePayment Solutions for Car Dealerships & Auto Finance Platforms→](/guides/car-dealership-payment-solutions/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [GuidePayments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-invoicing-erp-platforms/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuidePayment Solutions for Medical Billing Companies and RCM Firms→](/guides/medical-billing-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/ --- # Is reselling payments and becoming a PayFac right for my SaaS? | Shuttle > Considering becoming a PayFac? Understand the costs, compliance burden, and alternatives like payment facilitation-as-a-service for SaaS platforms. # Is reselling payments and becoming a PayFac right for my SaaS? By Nick Dunse, January 6, 2026 Considering becoming a PayFac? Understand the costs, compliance burden, and alternatives like payment facilitation-as-a-service for SaaS platforms. You're a SaaS platform with merchants, you need payment services to allow those merchants to sell stuff, you have a choice to integrate one or many payment service providers. You think that by reselling payments you might be able to increase your revenue and make it simpler/cheaper for your merchants... You're therefore looking for a 'PayFac' solution, of which there an increasing number of options in the market that allow the embedding and reselling of payments. Your SaaS becomes the Payment Facilitator (PayFac). Shuttle knows many of these providers and SaaS who've tried it or done it. We've heard from multiple people say -- > "It's the best thing we did" "It's the worst thing we did" ... It just depends whether it's right for you and your merchants. ## Why consider it - Get a margin from the transaction and therefore make more revenue per customer (SaaS + Payments business model) - Potentially reduce your merchant's payment fees - Simplify/reduce your payment integration requirements - Potentially increase customer retention by making your product more sticky - You centralise the account management for your merchants (I mean, they're going to come to you about payments anyway!) ## What type of SaaS does this work well for - SaaS with micro or small merchants - All in one SaaS solutions i.e. all payment channels are covered off in the SaaS - invoicing, online sales, etc - SaaS with merchants that are from one or two countries (since payments are licensed nationally) - SaaS with merchants who sell low risk products - SaaS with merchants who sell products that have low chargebacks, fraud and refunds, because the SaaS might be liable for those - SaaS with a larger team especially customer service reps, since the SaaS company will now be the point of call for all payments related issues and upfront risk processes ## What type of SaaS does it not work well for - SaaS who do not cover off all the merchants needs i.e. the merchant receives payments via other channels (since they won't be able to use your payments service in those channels) - SaaS with mid-market or enterprise, they will get cheaper and better services elsewhere and will not be willing to go through procurement for a new payment service provider - SaaS who's merchants are higher risk or in certain industries - SaaS who's merchants who have a lot of fraud or chargebacks ## The middle ground Shopify is probably the best known SaaS when it comes to reselling payments. They used Stripe's Connect model to do this. But Shopify realised that if they wanted to win larger merchants then they had to work with other payment providers. It meant that Shopify ran a hybrid model, reselling Stripe and working with other payment providers to increase customer acquisition and GMV. And of course they got their margin by charging an percent on non-Shopify payments. It sounds right for us, how do we get started? - Find out your Gross Merchant Volume (GMV) per annum - Determine if this model will work for all or some of your merchants - Approach payment providers that offer a PayFac solution with your GMV - Negotiate a buy rate - Ask what liabilities and responsibilities you will need to take on (risk, KYC, PCI compliance) - Decide a pricing strategy to resell to merchants - Equip your team with payments knowledge or employ a payments expert to be on team - Embed the service - Resell the service ## What is PayFac as a Service (PFaaS)? PayFac as a service (PFaaS) lets a SaaS platform act like a payment facilitator without registering as one. The PFaaS provider holds the PayFac registration, carries the sponsorship and compliance obligations, and rents you the infrastructure: sub-merchant onboarding, underwriting, settlement and reporting. You get the PayFac experience and a share of the economics, without the capital and regulatory lift of your own registration. The trade-off is the same one that runs through this whole decision. PFaaS reduces the build, but you still take on merchant onboarding obligations, program management and a provider dependency, and the revenue share is thinner than owning the registration. For many SaaS platforms the honest comparison is not PayFac vs PFaaS. It is whether you need to be in the funds flow at all, or whether an embedded payments layer above your customers' own merchant accounts gets you the product experience and the revenue without either. ## What providers offer a PayFac service? Before we get into the who, let's talk about the what - The best buy rates will come from providers that want to pass all the risk, KYC and compliance processes on to you, that will significantly eat into your profits if you're not setup to handle this with team and processes. Some providers offer a middle ground where you take some risk, but you will still have to board the customer. And very few providers will take the risk and onboard the customers for you but your buy rate will be weaker and at the end of the day once you add your margin in, the payment fees will be comparable to the list price of the payment provider. ## The following are some payment providers that offer a PayFac as a service: Adyen, Checkout.com, Global Payments, Stripe , UniPaaS, Worldline, Worldpay ## What else could we do? - Resell a gateway, instead of a gateway and merchant account provider, your profits will be smaller but you will be able to work with more customers and reduce your overheads significantly - Build the entire PayFac yourself - done in the past but not necessary anymore due to the options in the market - Use Shuttle to run a hybrid model or just get access to all the payment providers and services you need from one place. This will reduce your PCI scope, integration and maintenance burden, Shuttle will provide commission for certain payment providers to the SaaS where applicable. Further reading - https://www.nmi.com/eu/resources/blog/payfacs-the-ins-and-outs-of-the-payment-facilitator-model/ ## Related Reading Explore More ### Embedded Payments Without Becoming a PayFac ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [embedded payments layer above your customers' own merchant accounts](/guides/embedded-payments-without-payfac/) - [https://www.nmi.com/eu/resources/blog/payfacs-the-ins-and-outs-of-the-payment-facilitator-model/](https://www.nmi.com/eu/resources/blog/payfacs-the-ins-and-outs-of-the-payment-facilitator-model/) - [GuideEmbedded Payments Without Becoming a PayFac→](/guides/embedded-payments-without-payfac/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/kb_categories/getting-started/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/kb_categories/quickbooks/ --- # Redirecting to: /quickbooks-online/ ## Links - [Redirecting from to](/quickbooks-online/) --- URL: https://www.shuttleglobal.com/blog/keep-cargo-moving-how-freight-and-shipping-companies-speed-up-payments-with-shuttle/ --- # Freight Payment Solutions for Shipping & Logistics | Shuttle > How logistics platforms streamline freight payments with payment links, embedded checkout, and automated collection to replace net-60 invoices. # Freight Payment Solutions for Shipping & Logistics By Nick Dunse, January 6, 2026 How logistics platforms streamline freight payments with payment links, embedded checkout, and automated collection to replace net-60 invoices. Talk to us Make enabling payments for your platform and merchant users easy. Freight and shipping companies move billions of dollars in cargo every year, yet the payment infrastructure behind most logistics operations hasn't changed in decades. Net-30 and net-60 invoice terms, manual wire transfers, paper-based documentation, and multi-party payment chains create a cash flow bottleneck that slows down the entire supply chain. For logistics platforms and TMS providers, embedding modern payment services for the shipping industry isn't just a feature -- it's a competitive advantage that reduces DSO, eliminates manual reconciliation, and keeps cargo moving. This guide covers the payment challenges unique to freight, the methods available, and how logistics payment platforms are modernising collection for brokers, carriers, and shippers alike. ## Why Freight Payments Are Uniquely Challenging Freight payment workflows are more complex than most industries. A single shipment can involve a shipper, a freight broker, one or more carriers, customs agents, warehouse operators, and port authorities -- each expecting payment at different stages. Here are the core challenges: - Extended payment terms: Net-30, net-60, and even net-90 terms are standard in freight. Carriers often wait 45-60 days to get paid after delivering a load, creating severe cash flow pressure -- especially for owner-operators and small fleets. - Documentation-heavy processes: Bills of lading, proof of delivery, rate confirmations, and customs declarations must all be verified before payment is released. Missing a single document can delay payment by weeks. - Multi-party payment chains: A shipper pays a broker, who pays a carrier, who pays a driver, who pays for fuel and tolls. Each hop introduces delays, fees, and reconciliation overhead. - International complexity: Cross-border shipments involve multiple currencies, varying banking systems, and compliance with trade regulations. A container shipped from Shanghai to Rotterdam might require payments in CNY, USD, and EUR across three different banking networks. - High transaction values: Individual freight invoices routinely run from $2,000 to $50,000+, making card processing fees a real concern and pushing many companies toward bank transfers that are slow to settle. These challenges are why the freight industry has been slow to adopt digital payments -- but they're also why the opportunity for shipping industry payment solutions is so significant. ## Payment Methods Used in Freight and Logistics Freight companies typically rely on a mix of payment methods, each with trade-offs between speed, cost, and convenience. Wire transfers and ACH remain the dominant payment rails for freight. Domestic ACH transfers cost $0.20-$1.50 per transaction and settle in 1-3 business days. International wires cost $15-$50 and can take 3-5 business days. They work for large, predictable payments but require manual initiation and lack real-time visibility. Credit and debit cards are gaining traction for smaller freight payments and accessorial charges. Processing fees of 2.5-3.5% make cards expensive for $20,000+ invoices, but the instant confirmation and chargeback protection appeal to many shippers. Some carriers accept fleet cards (like Comdata or EFS) for fuel and maintenance. Cheques are still surprisingly common in freight -- some estimates suggest 40% of B2B freight payments are still cheque-based. They're slow (7-10 days to clear), prone to fraud, and expensive to process, but deeply entrenched in legacy workflows. Payment links offer a middle ground: brokers and carriers can send a secure link via email or SMS that lets shippers pay by card, ACH, or bank transfer -- without either party needing to share sensitive banking details. For global payments across borders, payment links support multi-currency checkout out of the box. ## How Payment Links Speed Up Freight Collection The biggest cash flow killer in freight isn't the payment terms themselves -- it's the friction between invoice and payment. A carrier sends a PDF invoice via email. The shipper prints it, routes it through AP approval, cuts a cheque or initiates a wire, and mails or sends payment. Every manual step adds days. Payment links collapse this process. When a carrier or broker embeds a payment link directly on an invoice, the shipper can click, confirm the amount, choose their payment method, and pay -- all in under 60 seconds. No phone calls, no cheque runs, no manual bank transfers. For freight brokers managing hundreds of loads per week, the impact is transformative: - DSO reduction: Brokers using payment links report 30-50% reductions in days sales outstanding. When paying is as easy as clicking a link, shippers pay faster -- even on net-30 terms. - Automated reconciliation: Each payment link is tied to a specific invoice and load number. When payment arrives, it's automatically matched -- no more spreadsheet reconciliation across bank statements. - Payment flexibility: Shippers choose their preferred method -- card for urgent loads, ACH for routine payments. The broker doesn't need to support different workflows for each. - Real-time visibility: Both parties can see when a payment link was opened, when payment was initiated, and when funds settled. No more chasing "the cheque is in the mail." These are the kinds of real merchant workflows that payment links enable -- and freight is one of the industries where the impact is most measurable. ## Freight Factoring vs Modern Payment Solutions Freight factoring has been the industry's go-to solution for cash flow problems for decades. A carrier sells its unpaid invoices to a factoring company at a discount (typically 2-5%) and gets paid within 24 hours. The factoring company then collects from the shipper. It works, but it's expensive. A carrier factoring $500,000 in monthly invoices at 3% is giving up $15,000 per month -- $180,000 per year -- just to get paid on time. And factoring companies often require carriers to factor all their invoices, not just the slow-paying ones. Modern shipping industry payment solutions offer an alternative approach: - Reduce the need for factoring by making it easier for shippers to pay faster. If a payment link gets a shipper to pay in 10 days instead of 45, the carrier may not need factoring at all. - Offer selective early payment discounts. Instead of paying 3% to a factor, a carrier might offer a shipper 1.5% off for paying within 5 days via payment link -- saving both parties money. - Automate payment reminders so that invoices don't sit in AP queues forgotten. A payment link with automated follow-up at day 7, 14, and 21 keeps the invoice top of mind. Factoring still has a place -- especially for new carriers without credit history or for genuinely slow-paying enterprise shippers. But for a growing number of freight companies, better payment infrastructure is a cheaper alternative. ## What to Look for in a Logistics Payment Platform Not every payment platform is built for freight. The shipping industry has specific requirements that generic solutions like Stripe or PayPal don't address out of the box. Here's what to evaluate when choosing a logistics payment platform: Multi-method support. Your platform needs to handle ACH, wire transfers, credit cards, and ideally payment links -- all from a single integration. Freight companies can't maintain separate systems for each payment method. High-value transaction handling. Most consumer payment platforms cap transactions or flag large payments for review. A freight payment platform must handle $5,000-$100,000+ transactions smoothly and reliably. Multi-currency and cross-border capability. International freight requires paying carriers in their local currency while billing shippers in theirs. The platform should handle FX conversion, settlement in multiple currencies, and compliance with international payment regulations. TMS and ERP integration. Payments should flow directly into your transportation management system or ERP. Look for platforms with APIs that can be embedded into existing freight workflows, not standalone portals that create another login for your team. Automated reconciliation. Every payment should automatically match to a load, invoice, or BOL. Manual reconciliation across bank statements, TMS records, and accounting software is one of the biggest hidden costs in freight. Compliance and audit trails. Freight payments are subject to DOT regulations, customs requirements, and often insurance mandates. Your payment platform needs complete audit trails with timestamps, user actions, and document references. ## Automating Freight Payment Workflows The real unlock for freight payments isn't any single method -- it's automation. When payment collection is embedded into the freight workflow itself, the entire accounts receivable process shrinks from weeks to days. Here's what an automated freight payment workflow looks like: - Load delivered → proof of delivery uploaded to TMS - TMS auto-generates invoice with payment link attached - Invoice emailed to shipper immediately (day 0) - Automated reminders at day 7 and day 14 if unpaid - Shipper clicks link, selects payment method, pays - Payment matched to load and reconciled automatically - Carrier paid out on settlement schedule For TMS and logistics platforms, this kind of embedded payment automation is a revenue opportunity. By processing payments on behalf of their freight customers, platforms can earn a margin on every transaction while providing a service their users desperately need. This is where an embedded payments infrastructure like Shuttle becomes relevant. Rather than building payment processing from scratch or forcing freight companies to use a separate payment portal, TMS platforms can embed white-label payment collection directly into their existing workflow -- generating payment links via API, handling multi-method collection, and settling funds to carriers automatically. ## Embedded Payments for TMS and Logistics Platforms If you run a logistics platform, freight marketplace, or TMS, payments are likely your users' most requested feature -- and your biggest integration headache. Building PCI-compliant payment infrastructure, managing PSP relationships, handling multi-currency settlement, and maintaining compliance is a multi-year project for most engineering teams. Shuttle provides the payment infrastructure that logistics platforms embed into their products. Instead of building your own payment stack, you can: - Generate payment links via API -- create unique, branded payment links for every invoice in your TMS. Each link supports cards, ACH, and bank transfers. - White-label the checkout -- shippers see your platform's brand, not a third-party payment page. This builds trust and keeps the experience seamless. - Route payments across PSPs -- use the best processor for each payment type and geography without managing multiple PSP integrations yourself. - Earn revenue on payments -- offer payment processing as a platform feature, without taking card data into your own systems. This embedded approach means freight companies get modern payment tools inside the software they already use, and logistics platforms get a new revenue line without building payment infrastructure from scratch. ## The Future of Freight Payments The freight industry is at an inflection point. Real-time payment rails (like RTP and FedNow in the US) are making instant settlement possible for high-value B2B transactions. Open banking APIs are enabling direct bank-to-bank payments without card network fees. And AI-driven freight platforms are automating everything from load matching to invoicing -- payments are the logical next step. The logistics platforms that embed payment infrastructure now will be best positioned as these trends accelerate. They'll have the payment data, the merchant relationships, and the processing volume to offer increasingly sophisticated financial products -- from instant carrier payouts to dynamic discounting to embedded freight financing. For freight companies still relying on cheques and manual wire transfers, the cost of inaction is growing. Every day of delayed payment is working capital tied up, every manual reconciliation is labour that could be automated, and every lost invoice is revenue at risk. ## Frequently Asked Questions ### What are the most common payment methods in freight and logistics? The most common payment methods in freight are ACH bank transfers, wire transfers, cheques, and increasingly credit cards and payment links. ACH and wire transfers dominate for large invoices due to lower fees, while cheques remain common in legacy workflows. Payment links are growing rapidly because they let shippers choose their preferred method -- card, ACH, or bank transfer -- from a single secure page. ### How can logistics companies reduce days sales outstanding (DSO)? The most effective ways to reduce DSO in logistics are: embedding payment links directly on invoices so shippers can pay instantly, automating payment reminders at regular intervals, offering early payment discounts (e.g., 1.5% off for payment within 5 days), and providing multiple payment methods so shippers aren't blocked by method preferences. Companies using digital payment collection typically see DSO drop by 30-50%. ### Is freight factoring still worth it with modern payment solutions? Freight factoring is still valuable for carriers who need guaranteed same-day payment or who work with chronically slow-paying enterprise shippers. However, modern payment infrastructure significantly reduces the need for factoring by getting shippers to pay faster. If your average DSO drops from 45 days to 15 days through payment links and automated reminders, you may eliminate the cash flow gap that made factoring necessary -- and save 2-5% on every invoice. ### How do payment links work for high-value freight invoices? Payment links for freight invoices work like any hosted checkout page but are optimised for B2B use cases. The broker or carrier generates a unique link tied to a specific invoice and load number, then sends it via email or includes it on the invoice PDF. The shipper clicks the link, sees the invoice details and amount, selects their payment method (ACH is most common for high-value transactions), and confirms. The payment is automatically reconciled against the original invoice in the TMS. If you're building a logistics platform or TMS and want to embed payment collection for your freight customers, book a discovery call with Shuttle to see how embedded payment infrastructure can work for your use case. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Payment Solutions for Medical Billing Companies and RCM Firms ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [global payments across borders](/blog/global-payments-for-online-and-offline-businesses/) - [embeds a payment link directly on an invoice](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [real merchant workflows that payment links enable](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [Stripe](/payment-providers/stripe/) - [embed white-label payment collection](/platforms/) - [book a discovery call with Shuttle](/discovery/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuidePayment Solutions for Medical Billing Companies and RCM Firms→](/guides/medical-billing-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/ --- # What Is Local Acquiring? How It Cuts International Payment Costs | Shuttle > Local acquiring routes international card payments through in-country processors, improving authorisation rates and reducing cross-border fees. # What Is Local Acquiring? How It Cuts International Payment Costs By Nick Dunse, July 8, 2024 Local acquiring routes international card payments through in-country processors, improving authorisation rates and reducing cross-border fees. Talk to us Make enabling payments for your platform and merchant users easy. If your platform processes payments across multiple countries, you have probably noticed that cross-border transactions cost more and fail more often. The reason is straightforward: when a card payment is routed through an acquirer in a different country from the cardholder, networks treat it as a cross-border transaction and apply higher interchange fees, additional scheme levies, and stricter fraud screening. The result is lower authorisation rates and higher costs. Local acquiring solves this by routing payments through an acquiring bank in the same country as the cardholder. The transaction looks domestic to the card network, which means lower fees, higher approval rates, and faster settlement. For platforms operating in multiple markets, local acquiring is one of the highest-impact optimisations available. ## What Is Local Acquiring? Local acquiring means processing a card payment through an acquirer that is licensed and domiciled in the same country as the cardholder's issuing bank. When a customer in Germany pays with a German-issued Visa card and the transaction is routed to a German acquirer, the card networks classify it as a domestic transaction. This matters because card scheme rules treat domestic and cross-border transactions very differently: - Interchange fees: under the EU Interchange Fee Regulation, consumer card interchange is capped at 0.2% for debit and 0.3% for credit whenever the issuer and the acquirer are both in the EEA, including cross-border within the EEA. Cards issued outside the EEA and used at EEA merchants fall outside those caps and carry interregional rates, which are materially higher. - Scheme fees: Visa and Mastercard apply additional cross-border assessment fees on transactions where the acquirer and issuer are in different countries. The rates vary by scheme, region and card type, so work from your own scheme fee schedule rather than a published range. - Authorisation rates: Issuers are more likely to approve transactions that appear domestic. Cross-border transactions trigger additional fraud screening, soft declines and 3DS challenges. The size of that gap varies by market and card mix. - Settlement speed: domestic transactions typically settle faster than cross-border ones, and cross-border settlement may involve currency conversion. Exact timings vary by acquirer and market, so confirm them in your own agreement. In short, local acquiring makes international payments behave like domestic ones. The economics improve, the conversion rates improve, and the customer experience improves. ## Local Acquiring vs Cross-Border Processing The distinction between local and cross-border acquiring comes down to where the acquirer sits relative to the cardholder. Here is how the two models compare across the metrics that matter most to platforms: Cost comparison - Local acquiring: domestic interchange plus acquirer margin, with no cross-border scheme fees. - Cross-border acquiring: interchange at the applicable cross-border or interregional rate, plus cross-border assessment fees, plus acquirer margin, plus any currency conversion markup. The effective rate on your own statements is the number that matters, and your acquirer can break it down for you. Authorisation rates - Local acquiring: Issuers see an acquirer BIN and merchant country in their own market, which generally means less friction and fewer additional fraud checks. - Cross-border acquiring: Foreign acquirer BINs can trigger additional issuer fraud rules, soft declines and higher 3DS challenge rates. How much that costs you varies by market and card mix, so measure it on your own traffic rather than relying on a published range. Settlement - Local acquiring: settlement in local currency, typically faster, with no forced FX conversion at the scheme level. - Cross-border acquiring: settlement may involve scheme-level currency conversion, and timing can extend in some corridors. Confirm both the timing and the conversion treatment with your acquirer. The size of the saving depends on your market mix, your card mix and what you currently pay, so the only reliable number is your own. Take your cross-border volume for a single market, apply the domestic interchange and scheme fees that would apply if the acquirer were local, and compare that against your current effective rate for the same traffic. Your acquirer can give you the fee breakdown you need to work it out. ## How Local Acquiring Works The technical flow for a locally acquired transaction involves several parties, but the key point is where the acquirer sits in the chain: 1. Payment initiation. A customer in France enters their card details on your platform's checkout. The payment gateway captures the card data and passes it to the payment processor. 2. Intelligent routing. The payment layer identifies the card's issuing country from the BIN (Bank Identification Number -- the first 6-8 digits). Based on this, it routes the transaction to a local acquirer in France rather than sending it cross-border. 3. Local processing. The French acquirer submits the authorisation request to the card scheme (Visa, Mastercard). Because both the acquirer and the issuer are in France, the scheme classifies it as a domestic transaction. 4. Domestic interchange applied. The issuer approves the transaction and domestic interchange rates apply. No cross-border assessment fees are charged. Settlement happens in euros on domestic clearing rails. 5. Funds settlement. The acquirer settles funds to the merchant or platform, on the cycle set out in your acquiring agreement. If the platform needs settlement in a different currency, the FX conversion happens at the platform layer with transparent rates rather than at the scheme level. The critical enabler here is BIN-based routing logic that sits between the checkout and the acquiring layer. Without it, transactions default to whichever single acquirer the platform has a contract with, regardless of where the cardholder is located. ## When You Need Local Acquiring Not every business needs local acquiring. If you only process payments in one country and your acquirer is in that country, your transactions are already domestic. Local acquiring becomes important when: - You operate across multiple markets. If your platform has merchants or customers in the UK, EU, US, and APAC, a single acquirer cannot provide domestic processing in all of those regions. - Cross-border decline rates are hurting revenue. If your authorisation rates on international traffic are materially below your domestic rates, that gap is worth investigating, and local acquiring is one of the levers. Measure it on your own traffic, segmented by issuing country and card type, before assuming the size of the prize. - Processing costs are eating your margin. Cross-border fees compound quickly. Work out your effective rate on international volume and compare it against what you pay domestically. If the gap is material and the volume is concentrated in one market, local acquiring is worth pricing. - You are expanding into new geographies. Entering a new market without a local acquirer means every transaction in that market will be cross-border. Setting up local acquiring before launch, or as part of launch, gives you the best possible unit economics from day one. - Your merchants expect competitive payment costs. If you are a platform that facilitates payments for sub-merchants, your pricing needs to be competitive. Local acquiring lets you offer lower transaction fees because your underlying costs are lower. ## The Multi-PSP Problem Here is where local acquiring gets complicated for platforms. Achieving true local acquiring across multiple markets usually means working with multiple payment service providers (PSPs) or acquirers. Adyen might give you strong local acquiring in the Netherlands and wider EEA. Stripe might cover the US and UK well. But neither alone covers every market your platform operates in. This creates what we call the multi-PSP problem: - Separate contracts and integrations. Each acquirer or PSP requires its own commercial agreement, technical integration, and onboarding process. For a platform operating in 10+ markets, this means managing 3-5 separate PSP relationships. - Fragmented reporting. Transaction data, settlement reports, and dispute management are split across multiple dashboards. Reconciliation becomes a significant operational burden. - Routing complexity. Your platform needs to build and maintain the logic that decides which PSP handles which transaction based on the cardholder's country, card type, currency, and other factors. This is non-trivial engineering work. - Compliance overhead. PCI DSS compliance, SCA requirements, and local regulatory obligations multiply with each PSP relationship. Each market may have its own rules around strong customer authentication, data residency, and payment licensing. - Ongoing maintenance. PSP APIs change, schemes update their rules, and local regulations evolve. Maintaining multiple integrations is a permanent engineering cost, not a one-time effort. This is why many platforms end up stuck with a single PSP and accept the cross-border cost penalty. The operational complexity of a multi-PSP approach feels too high, even when the economics clearly justify it. But there is a better way. If you are weighing that trade-off now, we cover it in detail in single global PSP vs multiple local acquirers. ## How Shuttle Works With Local Acquirers Shuttle is a PSP-neutral payment layer that sits between your platform and the payment providers you use. It is not an acquirer, it does not issue merchant accounts, and it holds no acquiring relationships of its own. You keep your own provider agreements and your own rates. What Shuttle changes is the integration work: instead of building and maintaining a separate integration for every provider you add, your platform connects once and the connected providers sit behind that connection. Here is how it works: Single integration, multiple providers. Your platform connects to Shuttle's API once. Providers Shuttle already connects to sit behind it, so adding one becomes configuration and onboarding rather than a new integration build. Payment configuration you control. You choose which connected provider handles a given payment type from the portal rather than in code, and payment methods can be filtered by minimum amount, maximum amount and currency. Be clear about the limits, because this is where vendors in this category tend to overpromise: there is no routing by issuing country or BIN, and currency is not a proxy for market, since one currency can span several acquiring markets. One view of activity. Transaction activity across your connected providers is visible in one place. Settlement still happens provider by provider on each provider's own cycle, so consolidated reporting is not the same thing as consolidated settlement, and your finance team should plan for that. Multi-tenant by design. If your platform serves sub-merchants, each tenant runs its own portal and its own payment configuration, so a merchant's provider relationships and rates stay their own. No provider lock-in. Because Shuttle is PSP-neutral and has no processing of its own to steer volume into, you are not tied to one provider's network. Moving a payment type to a different provider is a configuration and onboarding change rather than a rebuild. One caveat worth planning for: Shuttle tokenises with the gateway rather than holding card data itself, so stored credentials stay with the provider that captured them and saved cards and subscriptions do not move as freely as new transactions. If your platform takes payments across more than one market and you are weighing up how many providers to run, book a discovery call and we will go through your markets, your current providers and what adding another would actually involve. ## FAQ ### Does local acquiring improve authorisation rates? Usually yes, though the size of the improvement depends entirely on the markets involved and your transaction profile. The mechanism is straightforward: issuers tend to apply less aggressive fraud screening to transactions that appear domestic, and those transactions are less likely to trigger soft declines or additional 3DS challenges. Be careful with published uplift figures, including any quoted by a provider selling you the service, because approval rates are driven by traffic mix as much as by routing. The only comparison worth trusting is one run on your own traffic, segmented by issuing country and card type. ### What markets support local acquiring? Most major payment markets support local acquiring, including the UK, all EEA countries, the US, Canada, Australia, Singapore, Hong Kong, Japan and Brazil. Coverage depends on which acquirers operate in each market and whether they support the card schemes your customers use. The markets where local acquiring makes the biggest difference are those with the widest gap between domestic and cross-border interchange, particularly where cards issued outside the region are involved. ### Do I need separate contracts with each acquirer? In a direct model, yes. You would need to negotiate and sign separate acquiring agreements in each market, each with its own pricing, compliance requirements and technical integration. That is the complexity that makes multi-market acquiring impractical for many platforms to manage alone. A payment layer changes the integration work rather than the commercial relationship. Shuttle is not an acquirer and does not issue merchant accounts, so you keep your own acquiring agreements and your own rates. What you avoid is building and maintaining a separate integration per provider, because your platform connects once and the connected providers sit behind that connection. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices ### Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes ### Secure Payment Collection for Debt Agencies ### Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [acquiring bank](/glossary/) - [payment gateway](/glossary/payment-gateway/) - [Adyen](/payment-providers/adyen/) - [Stripe](/payment-providers/stripe/) - [multi-PSP approach](/guides/psp-neutral-vs-single-psp/) - [single global PSP vs multiple local acquirers](/guides/global-psp-vs-local-acquirers/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuidePayment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices→](/guides/payment-collection-professional-services/) - [GuideMulti-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes→](/guides/multi-channel-payment-collection/) - [GuideSecure Payment Collection for Debt Agencies→](/guides/secure-payment-collection-debt-agencies/) - [GuidePayment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope→](/guides/payment-collection-for-bpos/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/marketplace-payments/ --- # Maximizing Revenue and Customer Satisfaction with Payment Solutions for Marketplaces | Shuttle > How marketplaces can maximise revenue with the right payment setup -- split payments, seller onboarding, compliance, and payout management. # Maximizing Revenue and Customer Satisfaction with Payment Solutions for Marketplaces By Nick Dunse, August 7, 2022 How marketplaces can maximise revenue with the right payment setup -- split payments, seller onboarding, compliance, and payout management. Talk to us Make enabling payments for your platform and merchant users easy. Marketplaces have become increasingly popular in recent years, providing a platform for buyers and sellers to connect and transact. These online platforms have revolutionized the way we buy and sell goods and services, offering convenience and accessibility like never before. However, one crucial aspect of marketplaces that often goes unnoticed is the payment solutions that power these transactions. Payment solutions for marketplaces refer to the systems and processes that enable buyers to make payments to sellers securely and efficiently. These solutions play a vital role in facilitating transactions, ensuring that both buyers and sellers have a seamless experience. Without effective payment solutions, marketplaces would struggle to function, hindering their growth and success. Key Takeaways - Payment solutions are crucial for maximizing revenue and customer satisfaction in marketplaces. - Understanding the needs of your marketplace customers is key to choosing the right payment solution. - Integrating payment solutions into your platform requires ensuring security and compliance. - Optimizing payment processes can improve efficiency and customer experience. - Leveraging data analytics can help address common payment challenges and improve payment solutions in the future. The Importance of Maximizing Revenue and Customer Satisfaction Payment solutions have a significant impact on the revenue generated by marketplaces as well as customer satisfaction. When customers encounter difficulties or delays in making payments, they are more likely to abandon their purchase or seek alternative platforms. This can result in lost revenue for marketplaces and a negative customer experience. On the other hand, by implementing efficient payment solutions, marketplaces can maximize their revenue potential. Streamlined payment processes reduce friction for customers, making it easier for them to complete their transactions. This leads to higher conversion rates and increased revenue for marketplaces. Furthermore, customer satisfaction is closely tied to the payment experience. When customers can make payments quickly and securely, they are more likely to trust the marketplace and return for future purchases. By prioritizing customer satisfaction through effective payment solutions, marketplaces can build a loyal customer base and gain a competitive edge in the market. Understanding the Needs of Your Marketplace Customers To provide effective payment solutions, it is crucial for marketplace operators to understand the needs and preferences of their customers. Different customer segments may have varying payment preferences, and catering to these preferences can enhance the overall user experience. Marketplace operators should conduct thorough research to identify the payment methods preferred by their target audience. This can be done through surveys, user feedback, and analyzing transaction data. By understanding the payment preferences of their customers, marketplace operators can tailor their payment solutions to meet these needs. Additionally, it is important to consider the needs of different customer segments within a marketplace. For example, international customers may have different payment options available to them compared to domestic customers. By offering a variety of payment solutions that cater to different customer segments, marketplaces can ensure inclusivity and accessibility for all users. Payment Solutions for Marketplaces: An Overview Payment Solution | Description | Pros | Cons Stripe Connect | A platform that allows marketplaces to accept payments and manage payouts to their sellers. | Easy to use, customizable, supports multiple currencies and payment methods. | High fees, limited support for some countries and industries. PayPal for Marketplaces | A payment solution that enables marketplaces to accept payments and manage payouts to their sellers. | Trusted brand, supports multiple currencies and payment methods, easy to integrate. | High fees, limited customization options, disputes can be time-consuming. Braintree Marketplace | A payment solution that allows marketplaces to accept payments and manage payouts to their sellers. | Easy to use, supports multiple currencies and payment methods, customizable. | High fees, limited support for some countries and industries. Adyen MarketPay | A payment solution that enables marketplaces to accept payments and manage payouts to their sellers. | Supports multiple currencies and payment methods, customizable, fraud prevention tools. | High fees, limited support for some countries and industries, complex integration process. There are various types of payment solutions available for marketplaces, each with its own set of pros and cons. The most common payment solutions include credit card payments, digital wallets, bank transfers, and peer-to-peer payment platforms. Credit card payments are widely accepted and offer convenience for customers. However, they often come with high transaction fees and may not be accessible to all customers. Digital wallets, such as PayPal or Apple Pay, provide a secure and convenient way for customers to make payments. However, not all customers may have access to these digital wallet platforms. Bank transfers offer a direct and secure method of payment but can be time-consuming and require additional steps for customers. Peer-to-peer payment platforms, like Venmo or Zelle, enable users to transfer funds directly between individuals but may not be suitable for larger transactions or business payments. Marketplace operators must carefully evaluate the pros and cons of each payment solution to determine which options are most suitable for their platform and target audience. Choosing the Right Payment Solution for Your Marketplace When choosing a payment solution for a marketplace, several factors need to be considered. These factors include transaction fees, ease of use, security features, compatibility with existing systems, and customer preferences. Transaction fees can significantly impact the profitability of a marketplace. It is important to compare the fees charged by different payment solutions and consider the potential impact on revenue. Ease of use is another crucial factor, as a complicated payment process can deter customers from completing their transactions. Security features are of utmost importance to protect both buyers and sellers from fraud and unauthorized transactions. Marketplace operators should choose payment solutions that offer robust security measures, such as encryption and fraud detection systems. Compatibility with existing systems is also essential to ensure a seamless integration of the payment solution into the marketplace platform. Marketplace operators should consider whether the payment solution can be easily integrated with their existing infrastructure or if additional development work is required. Lastly, customer preferences should be taken into account when choosing a payment solution. By offering the payment methods preferred by customers, marketplaces can enhance the user experience and increase customer satisfaction. Integrating Payment Solutions into Your Marketplace Platform Seamless integration of payment solutions into a marketplace platform is crucial for a smooth user experience. When customers encounter difficulties or disruptions during the payment process, they are more likely to abandon their purchase or seek alternative platforms. To ensure seamless integration, marketplace operators should follow best practices such as using secure APIs (Application Programming Interfaces) provided by the payment solution provider. APIs allow for the exchange of data between the marketplace platform and the payment solution, enabling real-time updates and notifications. Marketplace operators should also conduct thorough testing and quality assurance processes to identify and resolve any issues before launching the integrated payment solution. This includes testing different scenarios, such as successful payments, failed payments, and refunds, to ensure that all functionalities are working as intended. Furthermore, clear communication with customers is essential during the integration process. Marketplace operators should inform users about any changes or disruptions that may occur during the integration period and provide support channels for users to seek assistance if needed. Ensuring Security and Compliance with Payment Solutions Security and compliance are critical aspects of payment solutions for marketplaces. With the increasing prevalence of online fraud and data breaches, customers are becoming more cautious about sharing their payment information online. Therefore, marketplace operators must prioritize security to build trust with their users. To ensure security, marketplace operators should choose payment solutions that offer robust encryption and fraud detection systems. These security measures protect sensitive customer data and prevent unauthorized access to payment information. Compliance with relevant regulations, such as the Payment Card Industry Data Security Standard (PCI DSS), is also essential. Marketplace operators should ensure that the chosen payment solution is compliant with these regulations to avoid legal issues and penalties. Best practices for ensuring security and compliance include regularly updating security protocols, conducting vulnerability assessments, and implementing multi-factor authentication for user accounts. Additionally, marketplace operators should educate their users about best practices for online security, such as using strong passwords and avoiding suspicious links or emails. Optimizing Payment Processes for Efficiency and Customer Experience Efficiency in payment processes is crucial for both marketplace operators and customers. Streamlining payment processes can reduce friction and improve the overall user experience, leading to higher customer satisfaction and increased revenue. Marketplace operators should analyze their payment processes to identify any bottlenecks or areas of improvement. This can be done by mapping out the entire payment journey, from the moment a customer initiates a purchase to the moment the payment is completed. By identifying pain points in the payment process, marketplace operators can implement solutions to streamline these processes. This may include reducing the number of steps required to complete a payment, optimizing loading times for payment pages, or automating certain aspects of the payment process. Furthermore, marketplace operators should consider implementing features such as saved payment information or one-click payments to enhance convenience for returning customers. By reducing the time and effort required to make a payment, marketplaces can encourage repeat purchases and improve customer loyalty. Leveraging Data Analytics to Improve Payment Solutions Data analytics can provide valuable insights into the effectiveness of payment solutions and help identify areas for improvement. By analyzing transaction data, marketplace operators can gain a deeper understanding of customer behavior and preferences. Data analytics can reveal patterns and trends in payment methods used by customers, allowing marketplace operators to tailor their payment solutions accordingly. For example, if a significant portion of customers prefers using digital wallets, marketplace operators can prioritize integrating popular digital wallet platforms into their payment solutions. Furthermore, data analytics can help identify any issues or errors in the payment process. By monitoring transaction data, marketplace operators can detect anomalies or discrepancies that may indicate fraudulent activities or technical glitches. This allows for prompt action to be taken to resolve these issues and ensure a smooth payment experience for customers. Best practices for leveraging data analytics include implementing robust data collection systems, utilizing data visualization tools for easy analysis, and regularly reviewing and interpreting the data to inform decision-making processes. Addressing Common Payment Challenges in Marketplaces Marketplaces often face common challenges when it comes to payments. These challenges include fraud prevention, chargebacks, international payments, and regulatory compliance. Fraud prevention is a constant concern for marketplaces, as fraudulent transactions can result in financial losses and damage to the platform's reputation. Marketplace operators should implement robust fraud detection systems and regularly monitor transactions for any suspicious activities. Chargebacks occur when customers dispute a transaction and request a refund from their bank or credit card company. This can be a time-consuming and costly process for marketplaces. To address this challenge, marketplace operators should have clear refund policies in place and provide excellent customer support to resolve any issues promptly. International payments can be complex due to different currencies, payment methods, and regulations. Marketplace operators should consider partnering with payment solution providers that specialize in international transactions to ensure smooth cross-border payments. Regulatory compliance is another challenge faced by marketplaces, as they must adhere to various regulations related to data protection, anti-money laundering, and consumer rights. Marketplace operators should stay updated on relevant regulations and work closely with legal advisors to ensure compliance. The Future of Payment Solutions for Marketplaces The future of payment solutions for marketplaces is promising, with emerging trends and technologies shaping the industry. One such trend is the rise of mobile payments, with an increasing number of customers using their smartphones to make purchases. Marketplace operators should prioritize mobile-friendly payment solutions to cater to this growing segment. Another emerging trend is the integration of blockchain technology into payment solutions. Blockchain offers enhanced security, transparency, and efficiency in transactions, making it an attractive option for marketplaces. As blockchain technology continues to evolve, marketplace operators should explore its potential applications in their payment processes. Furthermore, the use of artificial intelligence and machine learning in payment solutions is expected to grow. These technologies can help detect and prevent fraud, personalize payment experiences for customers, and optimize payment processes for efficiency. In conclusion, payment solutions play a crucial role in the success of marketplaces. By understanding the needs of their customers, choosing the right payment solution, ensuring security and compliance, optimizing payment processes, leveraging data analytics, and addressing common challenges, marketplace operators can provide a seamless and satisfying payment experience for their users. With emerging trends and technologies shaping the future of payment solutions, marketplaces have exciting opportunities to enhance their revenue potential and customer satisfaction. ## Related Reading Explore More ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Links - [Book a Call →](/discovery/) - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/ --- # Maximize Efficiency: Accepting Card Payments in QuickBooks Online | Shuttle > Accept card payments directly from QuickBooks Online invoices. Shuttle connects your preferred payment gateway so customers can pay instantly. # Maximize Efficiency: Accepting Card Payments in QuickBooks Online By Nick Dunse, April 18, 2024 Accept card payments directly from QuickBooks Online invoices. Shuttle connects your preferred payment gateway so customers can pay instantly. QuickBooks Users Invoices paid online with your payment gateway #nobrainer Maximize Efficiency: Accepting Card Payments in QuickBooks Online Accepting card payments in QuickBooks Online can bring a multitude of benefits to your business. First and foremost, it can maximize efficiency by streamlining your payment process. By allowing your customers to pay with their credit or debit cards, you can speed up the payment collection process and reduce the time and effort spent on chasing down payments. This can ultimately lead to improved cash flow and better financial management for your business. Furthermore, accepting card payments can also improve customer satisfaction. Many consumers prefer the convenience and security of paying with their cards, and by offering this option, you can cater to their preferences and provide a more seamless and convenient payment experience. This can help you attract and retain customers, ultimately leading to increased sales and revenue for your business. Key Takeaways - Accepting card payments in QuickBooks Online can maximize efficiency for your business - The benefits of accepting card payments in QuickBooks Online include faster payments and improved cash flow - Setting up card payments in QuickBooks Online is easy and can streamline your business operations - Understanding the costs and fees of accepting card payments is important for managing your finances effectively - Integrating card payments with QuickBooks Online can ensure seamless accounting and streamline your financial processes How to Set Up Card Payments in QuickBooks Online Setting up card payments in QuickBooks Online is a relatively straightforward process. First, you will need to sign up for a merchant account with a payment processor that integrates with QuickBooks Online, such as Intuit Merchant Services or Stripe. Once you have set up your merchant account, you can easily connect it to your QuickBooks Online account and start accepting card payments. To do this, simply navigate to the "Sales" tab in QuickBooks Online and select "Accept Payments." From there, you can follow the prompts to link your merchant account and set up your payment processing preferences. You can choose to accept payments online, in person, or over the phone, and you can also customize your payment forms to match your branding and provide a seamless payment experience for your customers. Streamlining Your Business Operations with Card Payments Accepting card payments in QuickBooks Online can significantly streamline your business operations. By automating the payment collection process, you can save time and reduce the administrative burden on your team. This can free up valuable resources that can be allocated to more strategic tasks, such as growing your business and serving your customers. Additionally, integrating card payments with QuickBooks Online can also improve your financial visibility and reporting. With all of your payment data centralized in one place, you can easily track and reconcile your transactions, generate reports, and gain insights into your cash flow and sales performance. This can help you make more informed business decisions and better manage your finances. Understanding the Costs and Fees of Accepting Card Payments Category | Value Revenue | 1,000,000 Profit | 500,000 Expenses | 500,000 While accepting card payments in QuickBooks Online can bring many benefits, it's important to understand the costs and fees associated with this payment method. Most payment processors charge a processing fee for each transaction, which is typically a percentage of the transaction amount plus a flat fee. Additionally, there may be other fees, such as monthly subscription fees or chargeback fees, that you need to consider. It's important to carefully review the fee structure of your chosen payment processor and consider how these costs will impact your bottom line. You should also compare different payment processors to find the best rates and terms for your business. While there are costs associated with accepting card payments, the benefits of improved efficiency and customer satisfaction often outweigh these expenses. Integrating Card Payments with QuickBooks Online for Seamless Accounting One of the key advantages of accepting card payments in QuickBooks Online is the seamless integration with your accounting system. When you accept a card payment, the transaction data is automatically synced with your QuickBooks Online account, eliminating the need for manual data entry and reconciliation. This can save you time and reduce the risk of errors in your financial records. Furthermore, integrating card payments with QuickBooks Online can provide you with real-time visibility into your cash flow and sales performance. You can easily track your receivables, monitor your payment processing activity, and generate reports to gain insights into your business's financial health. This can help you stay on top of your finances and make more informed decisions to drive your business forward. Tips for Maximizing Efficiency when Accepting Card Payments To maximize efficiency when accepting card payments in QuickBooks Online, it's important to optimize your payment process and leverage the features available to you. For example, you can set up recurring payments for regular customers to automate the billing process and ensure timely payments. You can also use payment reminders to prompt customers to pay their invoices on time and reduce late payments. Additionally, you can take advantage of the reporting tools in QuickBooks Online to gain insights into your payment activity and identify opportunities for improvement. By analyzing your payment data, you can identify trends, track customer behavior, and optimize your payment strategy to drive better results for your business. Ensuring Security and Compliance when Accepting Card Payments in QuickBooks Online When accepting card payments in QuickBooks Online, it's crucial to prioritize security and compliance to protect your business and your customers' sensitive information. You should ensure that your chosen payment processor is PCI DSS compliant and follows best practices for data security. This can help prevent data breaches and fraud, safeguarding your business's reputation and financial well-being. Furthermore, you should educate yourself and your team on the best practices for handling card payments securely. This includes using secure payment terminals or gateways, encrypting sensitive data, and implementing strong access controls to protect against unauthorized access. By prioritizing security and compliance, you can build trust with your customers and demonstrate your commitment to protecting their privacy. ## Related Reading Explore More ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideHubSpot International Payments: Accepting Cards Outside the Big 5 Currencies→](/guides/hubspot-international-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximize-efficiency-the-best-payment-gateways-for-facilities-management-2/ --- # Maximize Efficiency: The Best Payment Gateways for Facilities Management | Shuttle > Best payment gateways for facilities management companies -- automate invoicing, recurring billing, and field service collections. # Maximize Efficiency: The Best Payment Gateways for Facilities Management By Nick Dunse, June 11, 2024 Best payment gateways for facilities management companies -- automate invoicing, recurring billing, and field service collections. Talk to us Make enabling payments for your platform and merchant users easy. In the world of facilities management, the efficient handling of payments is crucial for the smooth operation of any facility. Payment gateways play a vital role in this process, as they provide a secure and convenient way for facilities to accept payments from their clients. Whether it's collecting rent from tenants, processing maintenance fees, or handling invoices from vendors, payment gateways streamline the payment process and ensure that funds are transferred in a timely and secure manner. One of the key reasons why payment gateways are so important in facilities management is the need for efficiency. Facilities managers are often responsible for handling a wide range of financial transactions, and having a reliable payment gateway in place can help to streamline these processes. By providing a secure platform for accepting payments, payment gateways can help facilities to avoid the hassle of dealing with cash or checks, and instead allow for quick and easy electronic transactions. This not only saves time and effort for facilities managers, but also provides a more convenient payment option for clients and tenants. Key Takeaways - Payment gateways are crucial for maximizing efficiency in facilities management by streamlining payment processes and ensuring seamless operations. - When choosing a payment gateway for facilities management, key factors to consider include transaction fees, security features, integration with management software, and compliance with industry regulations. - Top payment gateways for facilities management include Stripe, PayPal, Square, Authorize.Net, and Braintree, offering a range of features to meet different business needs. - Integrating payment gateways with facilities management software is essential for ensuring smooth and efficient operations, allowing for automated payment processing and real-time tracking of transactions. - Payment gateways play a significant role in improving financial management for facilities by providing secure and efficient payment processing, reducing manual errors, and enabling better cash flow management. Key Factors to Consider When Choosing a Payment Gateway for Facilities Management When it comes to choosing a payment gateway for facilities management, there are several key factors that should be taken into consideration. One of the most important factors is security. Facilities managers need to ensure that any payment gateway they choose provides a high level of security to protect sensitive financial information. This means looking for features such as encryption, tokenization, and fraud detection to prevent unauthorized access to payment data. Another important factor to consider is the ease of use. Facilities managers need a payment gateway that is intuitive and user-friendly, both for themselves and for their clients. A seamless payment process can help to improve customer satisfaction and reduce the likelihood of payment errors or disputes. Additionally, facilities managers should consider the cost of using a payment gateway, including any setup fees, transaction fees, and monthly subscription costs. Finding a payment gateway that offers competitive pricing and transparent fee structures can help facilities to maximize their financial resources. Top Payment Gateways for Streamlining Payments in Facilities Management There are several payment gateways that are well-suited for facilities management, each offering unique features and benefits. One popular option is PayPal, which is known for its ease of use and wide acceptance among consumers. PayPal offers a range of payment solutions, including online invoicing, recurring billing, and mobile payments, making it a versatile choice for facilities managers. Another top payment gateway is Stripe, which is known for its developer-friendly platform and customizable features. Stripe offers a range of tools for managing payments, including subscription billing, invoicing, and customizable checkout forms. For facilities that require more advanced payment solutions, Authorize.Net is a popular choice. Authorize.Net offers a range of features for managing payments, including fraud detection, recurring billing, and virtual terminal capabilities. Additionally, facilities that require international payment options may benefit from using 2Checkout, which offers support for multiple currencies and languages. 2Checkout also provides a range of features for managing global payments, including tax calculation, fraud prevention, and subscription billing. Integrating Payment Gateways with Facilities Management Software for Seamless Operations Payment Gateway | Transaction Fee | Set-Up Fee | Supported Currencies Stripe | 2.9% + 30¢ per transaction | No set-up fee | 135+ PayPal | 2.9% + 30¢ per transaction | No set-up fee | 25+ Authorize.Net | 2.9% + 30¢ per transaction | 25 set-up fee | Over 100 To maximize efficiency in facilities management, it's important to integrate payment gateways with facilities management software. By doing so, facilities managers can streamline their payment processes and improve overall operational efficiency. Integrating payment gateways with facilities management software allows for seamless communication between financial transactions and other aspects of facility operations, such as maintenance requests, tenant communications, and vendor management. One way to integrate payment gateways with facilities management software is through API integration. Many payment gateways offer APIs that allow for seamless integration with other software systems. By integrating payment gateways with facilities management software through APIs, facilities managers can automate the process of collecting payments, reconcile financial data, and generate reports on payment activity. This can help to reduce the likelihood of errors and improve the accuracy of financial records. Security and Compliance: Ensuring Safe Transactions with Payment Gateways in Facilities Management Security and compliance are paramount when it comes to handling financial transactions in facilities management. Payment gateways play a crucial role in ensuring safe transactions by providing robust security features and adhering to industry regulations. Facilities managers need to ensure that any payment gateway they choose complies with industry standards such as PCI DSS (Payment Card Industry Data Security Standard) to protect sensitive payment data. In addition to security features, facilities managers should also consider the level of customer support offered by payment gateways. In the event of any issues or concerns with payment processing, having access to responsive customer support can be invaluable. Facilities managers should look for payment gateways that offer 24/7 support and have a reputation for providing timely assistance with any payment-related issues. The Role of Payment Gateways in Improving Financial Management for Facilities Payment gateways play a significant role in improving financial management for facilities by providing tools for managing payments, tracking financial data, and generating reports on payment activity. By using a payment gateway that offers robust reporting capabilities, facilities managers can gain valuable insights into their financial performance and make informed decisions about their operations. Additionally, payment gateways can help facilities to streamline their accounting processes by automating tasks such as invoicing, reconciliation, and expense tracking. Furthermore, by using a payment gateway that integrates with accounting software, facilities managers can simplify their financial management processes even further. Integrating payment gateways with accounting software allows for seamless communication between financial transactions and accounting records, reducing the likelihood of errors and improving the accuracy of financial reporting. This can help facilities to maintain better control over their finances and ensure compliance with industry regulations. Case Studies: How Payment Gateways Have Transformed Payment Processes in Facilities Management There are numerous case studies that demonstrate how payment gateways have transformed payment processes in facilities management. One such case study involves a property management company that implemented a new payment gateway to streamline rent collection from tenants. By using a payment gateway with automated recurring billing capabilities, the property management company was able to reduce the time and effort required to collect rent payments each month. This not only improved operational efficiency but also resulted in higher tenant satisfaction due to the convenience of electronic payments. Another case study involves a facility maintenance company that integrated a payment gateway with their facilities management software to automate the process of invoicing clients for maintenance services. By using a payment gateway with customizable invoicing features, the facility maintenance company was able to generate professional-looking invoices and send them to clients automatically upon completion of services. This not only improved the speed and accuracy of invoicing but also resulted in faster payments from clients due to the convenience of electronic invoicing. In conclusion, payment gateways play a crucial role in maximizing efficiency in facilities management by providing secure and convenient solutions for handling financial transactions. By understanding the importance of payment gateways in facilities management and considering key factors when choosing a payment gateway, facilities managers can select the best option for their specific needs. Integrating payment gateways with facilities management software can further streamline operations, while ensuring security and compliance is essential for safe transactions. Payment gateways also play a significant role in improving financial management for facilities by providing tools for managing payments and generating reports on payment activity. Case studies demonstrate how payment gateways have transformed payment processes in facilities management, showcasing the tangible benefits of implementing these solutions. Overall, payment gateways are essential tools for facilities managers looking to optimize their financial processes and improve overall operational efficiency. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Payment Links for Property Management & Lettings Agencies ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/ --- # Authorize.net QuickBooks Integration: Full Guide | Shuttle > Learn how to integrate Authorize.net with QuickBooks for automated payment processing, invoice syncing, and reconciliation. Step-by-step setup guide. # Authorize.net QuickBooks Integration: Full Guide By Nick Dunse, February 21, 2021 Learn how to integrate Authorize.net with QuickBooks for automated payment processing, invoice syncing, and reconciliation. Step-by-step setup guide. Talk to us Make enabling payments for your platform and merchant users easy. If you use QuickBooks for accounting and Authorize.net for payment processing, connecting the two can save hours of manual data entry each week. The Authorize.net QuickBooks integration lets you sync payments, automate invoice reconciliation, and give customers more ways to pay. This guide covers everything you need to know: whether the integration exists, how to set it up, what it costs, and when you might want to consider alternatives like payment links. ## Does Authorize.net Integrate with QuickBooks? Yes. Authorize.net integrates with QuickBooks Online and QuickBooks Desktop through several methods: - QuickBooks Online Sync by Authorize.net -- a native connector available through the QuickBooks App Store that pushes settled transactions into QuickBooks automatically. - Third-party middleware -- tools like Synder, Connex, or OneSaas that offer deeper customisation, field mapping, and support for QuickBooks Desktop editions. - API-level integration -- for platforms and developers who need to build custom workflows between Authorize.net and QuickBooks using both APIs. The right method depends on your transaction volume, whether you use QuickBooks Online or Desktop, and how much customisation you need. Most small businesses start with the native sync or a middleware tool, while platforms building embedded payment flows often need the API route. ## How to Set Up the Integration The setup process varies depending on which connection method you choose. Here is a walkthrough for the most common approach: QuickBooks Online with the native Authorize.net connector. ### Prerequisites - An active Authorize.net merchant account with API credentials (API Login ID and Transaction Key). - A QuickBooks Online subscription (Simple Start, Essentials, Plus, or Advanced). - Admin-level access to both accounts. ### Step-by-Step Setup - Step 1: Log in to QuickBooks Online and navigate to the Apps section. Search for "Authorize.net" in the QuickBooks App Store. - Step 2: Install the connector app and authorise it to access your QuickBooks data. You will need to grant permissions for reading and writing invoices, payments, and customer records. - Step 3: Enter your Authorize.net API Login ID and Transaction Key. These are found in your Authorize.net merchant dashboard under Account > Settings > API Credentials & Keys. - Step 4: Configure your sync settings. Choose whether to sync all transactions or only settled batches, map your income accounts, and set the sync frequency. - Step 5: Run a test transaction to verify that payments flow from Authorize.net into QuickBooks correctly. Check that the amount, customer name, and invoice reference all match. If you use QuickBooks Desktop instead, you will need a middleware tool like Synder or Connex, since the native connector is designed for QuickBooks Online only. ## Syncing Invoices and Payments Once connected, the integration handles the core accounting workflow: matching payments received through Authorize.net to open invoices in QuickBooks. Here is what typically syncs between the two systems: - Settled transactions from Authorize.net are created as payment records in QuickBooks, matched to the corresponding invoice by customer name or invoice number. - Refunds and voids are reflected as credit memos or refund receipts, keeping your books accurate without manual adjustment. - Processing fees can be recorded as separate expense entries (depending on your connector), so you can track the true cost of payment processing. - Customer records can be created or updated in QuickBooks when new customers pay through Authorize.net for the first time. The sync frequency depends on your setup. The native connector typically syncs daily, while middleware tools like Synder can sync in near real-time. For businesses that process online payments through QuickBooks, automated syncing eliminates the risk of missed entries and month-end reconciliation headaches. ## Payment Methods Supported via Authorize.net When you process payments through Authorize.net and sync them to QuickBooks, your customers can pay using: - Visa, Mastercard, American Express, Discover, and JCB credit and debit cards. - ACH bank transfers (eCheck) for lower-cost payment acceptance, particularly useful for B2B invoices and recurring billing. - Digital wallets including Apple Pay and Google Pay (when using Authorize.net Accept.js or Accept Hosted). - Recurring and subscription payments through Authorize.net's Automated Recurring Billing (ARB) feature. This gives you broader payment coverage than QuickBooks Payments alone, which is limited to cards and ACH. If you are comparing payment gateways, see our Authorize.net vs Stripe comparison for a detailed breakdown of features, pricing, and use cases. ## Authorize.net Fees and Pricing Understanding the cost structure is important when budgeting for the integration. Here is how Authorize.net pricing breaks down: - Gateway-only plan: $25/month plus $0.10 per transaction and $0.10 daily batch fee. This is for merchants who already have a merchant account with another provider. - All-in-one plan: 2.9% + $0.30 per transaction with no monthly fee. This bundles the gateway and payment processing together. - eCheck (ACH): $0.75 per transaction, making it significantly cheaper than card processing for high-value B2B payments. If you use a third-party middleware tool for the QuickBooks sync, that adds an additional cost. Synder starts at $20/month, while Connex is $35/month and up depending on transaction volume. Factor these costs in when comparing against QuickBooks Payments or Stripe as alternative processors. ## Benefits of Connecting Authorize.net and QuickBooks The integration delivers several operational improvements over manually tracking payments: ### Automated Reconciliation Every settled transaction in Authorize.net automatically matches to the corresponding invoice in QuickBooks. This eliminates the manual process of downloading settlement reports, cross-referencing invoice numbers, and entering payment records by hand. For businesses processing hundreds of transactions per month, this alone can save 5-10 hours of bookkeeping time. Automated reconciliation also reduces month-end close times significantly. Instead of spending days reconciling bank statements against invoices, your accounting team can review pre-matched records and focus on exceptions only. This is especially valuable for businesses with seasonal spikes in transaction volume, where manual reconciliation would otherwise create bottlenecks. ### Faster Cash Flow Visibility With automated syncing, your QuickBooks dashboard reflects actual payments received within hours rather than days. You get an accurate picture of outstanding invoices, days sales outstanding (DSO), and cash on hand without waiting for the monthly close. ### Reduced Errors Manual data entry introduces mistakes: transposed numbers, mismatched invoices, forgotten refunds. The integration removes these failure points by pulling data directly from Authorize.net's settlement records. When a refund is issued, it automatically appears in QuickBooks as a credit memo, keeping your books balanced. ### Better Reporting With all payment data flowing into QuickBooks, you can run reports that combine revenue, processing fees, refunds, and customer payment behaviour in one place. This is particularly useful for understanding payment method preferences, identifying late-paying customers, and tracking net revenue after processing costs. ### Scalability for Growing Businesses As your business grows, the volume of transactions between Authorize.net and QuickBooks increases. An automated integration scales with you without requiring additional headcount. Whether you process 100 or 10,000 transactions per month, the sync handles them identically. This is a meaningful advantage over manual processes, where every new customer or product line adds to the bookkeeping burden. ## Limitations and Common Issues While the integration is useful, it is not without friction. Here are the most common issues businesses encounter: - QuickBooks Desktop support is limited. The native Authorize.net connector only works with QuickBooks Online. Desktop users must rely on third-party middleware, which adds cost and complexity. - Invoice matching is not always automatic. If the payment in Authorize.net does not include a matching invoice number or customer reference, you may need to manually match transactions in QuickBooks. - Partial payments and split payments can be tricky. Not all connectors handle partial invoice payments gracefully, which may require manual intervention. - Multi-currency transactions require QuickBooks Online Plus or Advanced. If you process payments in multiple currencies through Authorize.net, make sure your QuickBooks plan supports multi-currency before setting up the sync. - Duplicate entries can occur if you process payments through multiple channels (e.g. Authorize.net's virtual terminal and an online checkout). Configure your sync rules carefully to avoid double-counting revenue. ## Alternative: Payment Links for Authorize.net If you find the direct integration too complex or limited for your needs, payment links offer a simpler approach. Instead of building a full sync between Authorize.net and QuickBooks, you can generate shareable payment links that let customers pay directly. You then record the payment in QuickBooks manually or through a lightweight webhook. Payment links work well when you: - Send one-off invoices and want customers to pay instantly via a link in an email or SMS. - Need to collect payments across multiple channels (email, chat, phone) without building custom checkout pages. - Want to avoid the monthly fees of middleware tools while still using Authorize.net as your gateway. For platforms that embed payments for their merchants, Shuttle Global connects to both Authorize.net and QuickBooks, enabling you to offer payment processing to your users without managing the integration yourself. If you are building a platform that handles invoicing and payments, get in touch to see how Shuttle can simplify your payment stack. You can also combine payment links with your QuickBooks workflow by embedding the link directly in QuickBooks invoice emails. When customers click the link and pay through Authorize.net, the transaction settles in your gateway and can still be reconciled in QuickBooks. This hybrid approach gives you the simplicity of payment links with the accounting benefits of the QuickBooks integration. If you are also evaluating Stripe for your QuickBooks integration, our QuickBooks with Stripe integration guide covers the same setup process for Stripe's ecosystem. ## Frequently Asked Questions Below are answers to the most common questions about connecting Authorize.net with QuickBooks. ### Does Authorize.net integrate with QuickBooks? Yes. Authorize.net integrates with QuickBooks Online through a native connector available in the QuickBooks App Store. For QuickBooks Desktop, you need a third-party middleware tool like Synder or Connex. Both options sync settled transactions, refunds, and customer data between the two platforms. ### Is the Authorize.net QuickBooks integration free? The native QuickBooks Online connector for Authorize.net is included at no additional charge beyond your standard Authorize.net and QuickBooks subscriptions. However, if you need advanced features like real-time syncing, custom field mapping, or QuickBooks Desktop support, third-party tools cost $20-50/month depending on the provider and your transaction volume. ### Can I sync recurring payments from Authorize.net to QuickBooks? Yes. If you use Authorize.net's Automated Recurring Billing (ARB), each recurring charge that settles will sync to QuickBooks as a payment record. The connector treats recurring payments the same as one-time transactions. For best results, ensure each recurring payment includes a customer reference that matches your QuickBooks customer list. ### What if my payments are not syncing correctly? The most common causes of sync failures are expired API credentials, mismatched customer names between Authorize.net and QuickBooks, and duplicate transaction detection rules that block legitimate entries. Start by verifying your API Login ID and Transaction Key are current in the connector settings. Next, check that customer names in Authorize.net match their QuickBooks records exactly. If the problem persists, review the connector's sync log for specific error messages, and consider switching to a middleware tool that offers more granular error handling and retry logic. ## Related Reading Explore More ### Authorize.net + QuickBooks Integration: Accept Invoice Payments Online ### How to Connect Authorize.net to Twilio for Voice & IVR Payments ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment links](/blog/payment-links-for-authorize-net/) - [online payments through QuickBooks](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [Authorize.net vs Stripe comparison](/blog/authorize-net-vs-stripe/) - [Stripe](/payment-providers/stripe/) - [platforms that embed payments](/platforms/) - [get in touch](/discovery/) - [QuickBooks with Stripe integration guide](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [GuideAuthorize.net + QuickBooks Integration: Accept Invoice Payments Online→](/guides/authorize-net-quickbooks/) - [GuideHow to Connect Authorize.net to Twilio for Voice & IVR Payments→](/guides/authorize-net-twilio-integration/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/ --- # QuickBooks Stripe Integration: Full Setup Guide (2026) | Shuttle > Learn how to integrate Stripe with QuickBooks Online. Compare setup methods, sync payments and invoices, and avoid common reconciliation pitfalls. # QuickBooks Stripe Integration: Full Setup Guide (2026) By Nick Dunse, January 4, 2026 Learn how to integrate Stripe with QuickBooks Online. Compare setup methods, sync payments and invoices, and avoid common reconciliation pitfalls. Talk to us Make enabling payments for your platform and merchant users easy. If you use Stripe for payment processing and QuickBooks for accounting, getting the two to talk to each other saves hours of manual data entry every month. But the QuickBooks Stripe integration is not as straightforward as you might expect -- there is no single official connector, and the right approach depends on your transaction volume, business model, and how much automation you need. This guide covers every method for connecting Stripe with QuickBooks Online, walks through setup step by step, and explains how to handle fees, refunds, and reconciliation properly. ## Does Stripe Integrate with QuickBooks? Yes -- but not through a single built-in button. Stripe and QuickBooks Online can be connected through several methods, each with different trade-offs: - Stripe App for QuickBooks -- Stripe's own marketplace app that syncs transactions into QuickBooks. Limited feature set but free. - Third-party connectors -- Tools like Synder, PayTraQer, or Bookkeep that offer deeper sync features including fee breakdowns, multi-currency support, and refund handling. - Zapier or Make automations -- Workflow tools that create QuickBooks entries when Stripe events fire. Flexible but require configuration. - Manual CSV import -- Export transactions from Stripe, format them, and import into QuickBooks. Workable for low volumes. - Custom API integration -- Build a direct connection using the Stripe and QuickBooks APIs. Best for platforms handling payments on behalf of merchants. The method you choose depends on transaction volume, how granular your accounting needs to be, and whether you need to track Stripe fees as separate line items. ## QuickBooks Payments vs Stripe: Which Should You Use? Before setting up an integration, it is worth understanding why many businesses use Stripe instead of QuickBooks' own payment processing -- QuickBooks Payments (formerly Intuit Merchant Services). QuickBooks Payments is tightly integrated with QuickBooks Online. Payments are automatically matched to invoices, and reconciliation is nearly automatic. However, it is limited to basic card and ACH processing, supports fewer currencies, and lacks the developer tools and flexibility that Stripe offers. Stripe is a full payment infrastructure platform. It supports 135+ currencies, dozens of payment methods, subscriptions, payment links, marketplace payments via Connect, and extensive APIs. Businesses that sell internationally, run subscription models, or operate platforms almost always need Stripe's capabilities. The trade-off is clear: QuickBooks Payments gives you effortless accounting sync but limited payment features. Stripe gives you powerful payment processing but requires extra work to keep QuickBooks in sync. Most growing businesses choose Stripe and set up the integration. ## How to Connect Stripe to QuickBooks Online Here are the most common methods, ranked by ease of setup and reliability. ### Method 1: Third-Party Connector (Recommended) Dedicated sync tools like Synder, PayTraQer, and Bookkeep are purpose-built for connecting payment processors to accounting software. They handle the nuances that simpler integrations miss -- Stripe fee breakdowns, partial refunds, multi-currency conversion, and payout-level reconciliation. Setup steps: - Create an account with your chosen connector (most offer free trials). - Authorize your Stripe account via OAuth -- the connector will request read access to transactions, payouts, and fees. - Connect your QuickBooks Online company -- the connector maps Stripe data to your chart of accounts. - Configure mapping rules: which Stripe charges map to which income accounts, where fees are recorded, and how refunds are categorised. - Run a historical sync to backfill past transactions, then enable automatic ongoing sync. This method costs $15-50 per month depending on transaction volume and the tool you choose, but for most businesses processing more than 50 transactions per month, the time saved on manual reconciliation pays for itself within the first week. ### Method 2: Zapier or Make Automation Workflow automation tools can create QuickBooks sales receipts or journal entries whenever a Stripe payment is completed. This works well for simple use cases -- for example, creating a sales receipt in QuickBooks each time a Stripe charge succeeds. The limitation is that Zapier and Make work on individual events. They do not natively understand Stripe payouts (which bundle multiple charges minus fees into a single bank deposit), making reconciliation more complex. You will need separate Zaps for charges, refunds, and disputes, and fee tracking requires custom logic. ### Method 3: Stripe Apps Marketplace Stripe's app marketplace includes QuickBooks connectors built by third parties. These apps install directly within your Stripe dashboard and push transaction data to QuickBooks. The advantage is that configuration happens within Stripe's interface, which is familiar if you spend most of your time there. Check the Stripe App Marketplace for current options, as the available apps change frequently. ### Method 4: Manual CSV Import For businesses with low transaction volumes (under 20-30 per month), manually exporting Stripe data and importing it into QuickBooks may be sufficient. Export your transactions from the Stripe dashboard as a CSV, reformat columns to match QuickBooks' import template, and upload. This is free but time-consuming and error-prone at scale. ## Syncing Invoices, Payments, and Refunds The core challenge of any QuickBooks Stripe integration is keeping three data types in sync: invoices, payments, and refunds. Invoices. If you create invoices in QuickBooks and collect payment via Stripe, you need the integration to match Stripe charges back to the correct QuickBooks invoice. Third-party connectors handle this by matching on invoice number, customer email, or amount. If you create invoices in Stripe instead, the connector should create corresponding invoices or sales receipts in QuickBooks. For a deeper look at QuickBooks invoicing workflows, see our QuickBooks online payments guide. Payments. Each Stripe charge should create either a payment against an existing invoice or a standalone sales receipt in QuickBooks. The key decision is whether to record transactions at the individual charge level or at the payout level (one entry per bank deposit). Individual charges give you more granular reporting. Payout-level recording is simpler to reconcile against your bank statement. Refunds. Stripe refunds need to create corresponding refund receipts or credit memos in QuickBooks. Partial refunds add complexity -- the integration must update the original transaction rather than void it entirely. Most third-party connectors handle partial refunds correctly. Zapier-based setups often struggle with them. ## Understanding Stripe Fees in QuickBooks Stripe charges 2.9% + 30¢ per successful card payment (standard pricing -- rates vary by country, volume, and payment method). These fees are deducted before Stripe deposits funds to your bank account, which creates an accounting challenge. For example, a $100 payment results in a $96.80 bank deposit ($100 minus $3.20 in fees). If you record only the bank deposit in QuickBooks, your revenue appears lower than it actually is. The correct approach: - Record the full $100 as revenue (income account). - Record the $3.20 as a processing fee expense (expense account -- commonly named "Payment Processing Fees" or "Stripe Fees"). - The $96.80 bank deposit then reconciles correctly as revenue minus fees. Most third-party connectors split fees automatically. If you use Zapier or manual import, you need to calculate and record fees separately -- either per-transaction or summarised monthly. ## Reconciliation Workflow for Stripe and QuickBooks Even with a good integration, you need a reconciliation process to catch discrepancies. Stripe batches individual charges into periodic payouts (typically daily or weekly), so a single bank deposit may contain dozens of transactions minus fees, refunds, and disputes. Recommended workflow: - Create a clearing account. Set up a "Stripe Clearing" or "Stripe Undeposited Funds" account in QuickBooks (type: Other Current Asset). All Stripe transactions flow through this account first. - Record charges to the clearing account. Each Stripe payment creates a sales receipt that deposits into the clearing account, not directly into your bank account. - Match payouts to bank deposits. When Stripe sends a payout to your bank, create a transfer in QuickBooks from the clearing account to your bank account. The payout amount should match the sum of charges minus fees and refunds. - Reconcile weekly. Check that your Stripe clearing account balance is zero (or close to it) after all payouts have been matched. A non-zero balance means transactions are missing or incorrectly recorded. This clearing account method is the standard accounting practice for any payment processor, not just Stripe. It ensures your books accurately reflect money in transit between Stripe and your bank. ## Limitations and Workarounds No QuickBooks Stripe integration is perfect. Here are the most common issues and how to handle them. Multi-currency complications. If you accept payments in multiple currencies, Stripe converts them at its own exchange rate before depositing in your settlement currency. QuickBooks may use a different exchange rate, creating small discrepancies. Use a connector that pulls Stripe's actual exchange rate rather than QuickBooks' default rate. Stripe Connect and marketplace payments. If you use Stripe Connect to process payments on behalf of sub-merchants (common for platforms and marketplaces), accounting becomes significantly more complex. Platform fees, application fees, and transfers to connected accounts all need proper categorisation. Most basic connectors do not handle Connect payouts well -- you may need a custom integration or a connector specifically designed for marketplace accounting. Disputes and chargebacks. When a customer disputes a Stripe charge, Stripe debits the disputed amount (plus a fee) from your account. This needs to be recorded in QuickBooks as a separate transaction -- not simply reversed. If you win the dispute, Stripe returns the funds, requiring another entry. Automate this if possible; manual tracking of disputes across Stripe and QuickBooks is a common source of accounting errors. Subscription billing. Stripe Billing creates recurring charges automatically. Your integration needs to handle these as they occur, creating new sales receipts or invoice payments in QuickBooks for each billing cycle. If your connector does not support Stripe subscriptions natively, you may end up with missing entries for renewal payments. Comparing payment gateways? If you are evaluating whether Stripe is the right processor to pair with QuickBooks, our Authorize.net vs Stripe comparison breaks down the differences. We also have a guide on QuickBooks with Authorize.net if you want to compare integration options side by side. If you want to keep Stripe as your gateway while adding payment links to QuickBooks invoices with auto-reconciliation, see How to Accept Payments on QuickBooks Invoices -- it covers connecting any gateway (including Stripe) to QuickBooks in 5 minutes. ## For Platforms: Automating QuickBooks + Stripe for Your Merchants If you run a platform or SaaS product where your merchants use both Stripe and QuickBooks, the integration challenge multiplies. Each merchant needs their Stripe transactions synced to their own QuickBooks instance, with proper fee allocation and reconciliation. Building and maintaining these connections in-house is a significant engineering investment. Many platforms choose to work with a payments infrastructure partner that handles the complexity of multi-merchant payment processing, accounting sync, and compliance. Shuttle Global's embedded payments platform lets you offer Stripe-powered payments to your merchants without building the integration yourself -- including the accounting and reconciliation layer. If you are exploring this, book a discovery call to discuss your requirements. ## Frequently Asked Questions ### Does Stripe have a direct integration with QuickBooks Online? There is no native, first-party integration built by either Stripe or Intuit. However, several third-party connectors (Synder, PayTraQer, Bookkeep) provide reliable automated sync between the two platforms. You can also find QuickBooks connectors in the Stripe Apps Marketplace. ### How much does it cost to integrate Stripe with QuickBooks? Third-party connectors typically cost $15-50 per month depending on transaction volume. Zapier-based automations cost $20-50 per month depending on the number of tasks. Manual CSV import is free but labour-intensive. Stripe itself does not charge extra for QuickBooks integration -- you pay Stripe's standard processing fees (2.9% + 30¢ per transaction) regardless of which accounting software you use. ### Can I sync Stripe subscriptions with QuickBooks automatically? Yes, but not all connectors support it equally. Synder and PayTraQer both handle Stripe Billing subscriptions, creating new sales receipts or invoice payments in QuickBooks each time a subscription renews. Zapier can also trigger on Stripe subscription events, but you will need to build separate workflows for new subscriptions, renewals, cancellations, and failed payments. ### Should I use QuickBooks Payments instead of Stripe? QuickBooks Payments is simpler if your only goal is collecting invoice payments from domestic customers. It syncs with QuickBooks automatically and requires no integration setup. However, if you need international payments, multiple payment methods, subscription billing, marketplace payments, or developer APIs, Stripe is the better choice. Most businesses that outgrow basic invoicing end up on Stripe and then integrate it with QuickBooks using one of the methods described in this guide. ## Related Reading Explore More ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Stripe](/payment-providers/stripe/) - [payment links](/blog/revolutionize-your-payment-process-with-stripe-payment-links/) - [QuickBooks online payments guide](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [Authorize.net vs Stripe comparison](/blog/authorize-net-vs-stripe/) - [QuickBooks with Authorize.net](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [embedded payments platform](/platforms/) - [book a discovery call](/discovery/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideWorldpay + QuickBooks Integration: Pay Invoices Through Worldpay→](/guides/quickbooks-worldpay-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximize-your-earnings-with-linktree-payment-links-a-step-by-step-guide/ --- # Linktree Payments: How to Add Payment Links to Your Bio | Shuttle > Learn how to add payment links to Linktree using PayPal, Venmo, Cash App, Zelle, and Commerce Links. Step-by-step setup plus smarter alternatives. # Linktree Payments: How to Add Payment Links to Your Bio By Nick Dunse, January 7, 2026 Learn how to add payment links to Linktree using PayPal, Venmo, Cash App, Zelle, and Commerce Links. Step-by-step setup plus smarter alternatives. Talk to us Make enabling payments for your platform and merchant users easy. Linktree is the most popular link-in-bio tool, with over 50 million users directing followers to their content, stores, and services. But what if you want to actually collect money through your Linktree? Whether you sell digital products, offer freelance services, or accept tips, adding payment links to your bio is one of the fastest ways to monetise your audience. This guide covers every way to accept Linktree payments -- from the built-in Commerce Links feature to adding PayPal, Venmo, Cash App, and Zelle. We also look at the limitations of peer-to-peer payment links and when a hosted checkout page is the better option. ## How to Set Up Linktree Commerce Links (Built-in Payments) Linktree offers a native payment feature called Commerce Links that lets you sell products, services, or digital downloads directly from your bio page. Commerce Links are available on all Linktree plans, including the free tier. They support fixed-price items, name-your-price payments (tips, donations), and automatic digital file delivery. Linktree takes no commission. You only pay the standard processing fees from your connected provider (typically 2.9% + 30¢ for Stripe or PayPal). Here is how to set it up in about five minutes: - Log in to your Linktree dashboard and click Add New Link - Select Store or Commerce Link from the link types - Connect your Stripe or PayPal account (one-time setup) - Add your product title, description, price, and an optional image - For digital products, upload the file that buyers will receive after payment - Toggle the link live and preview your Linktree page Buyers complete checkout without leaving your Linktree page. They enter their card details in a Stripe- or PayPal-powered overlay, pay, and receive a confirmation email with any digital files attached. ## Linktree Payment Methods Explained There are two categories of Linktree payment methods: the built-in Commerce Links (powered by Stripe or PayPal) and external payment links you add manually. Here is a comparison: Commerce Links (Built-in): Accept credit/debit cards, Apple Pay, Google Pay, and PayPal. Checkout happens on your Linktree page. Best for selling products and digital downloads. External P2P Links (Manual): Link out to PayPal.me, Venmo, Cash App, Zelle, or any other payment URL. The buyer leaves your Linktree to complete the payment. Best for tips, donations, and informal person-to-person payments. Most creators use a combination -- Commerce Links for products they sell regularly and external links for tips or one-off payments where the buyer already has a specific app. ## How to Add PayPal to Linktree There are two ways to use PayPal with Linktree: as the payment processor behind Commerce Links, or as a standalone PayPal.me link. ### Option 1: Connect PayPal as Your Commerce Links Processor Go to your Linktree settings and select PayPal as your payment provider. This lets buyers pay with PayPal, credit cards, or debit cards through the embedded checkout. This is the recommended approach if you sell fixed-price items. ### Option 2: Add a PayPal.me Link If you just want a tip jar or donation link, add a regular link to your Linktree pointing to your PayPal.me URL (e.g., paypal.me/yourusername). You can pre-fill an amount by appending it to the URL: paypal.me/yourusername/25 sends the buyer to a $25 payment page. - Click Add New Link in your Linktree dashboard - Choose a standard Link type - Paste your PayPal.me URL and give it a clear title like "Pay with PayPal" or "Send a Tip via PayPal" - Add a thumbnail icon to make it visually recognisable PayPal charges 2.99% + a fixed fee for personal payments received via PayPal.me, and standard commercial rates (2.89% + 49¢) for business accounts. ## How to Add Venmo to Linktree Venmo is one of the most popular payment apps in the US, so it makes sense to add it to your Linktree if your audience is primarily American. Venmo does not integrate directly with Linktree, but you can add your Venmo profile link manually. - Open the Venmo app and go to your profile - Tap the QR code icon, then Share to copy your Venmo payment link (format: venmo.com/yourusername) - In Linktree, click Add New Link and select a standard Link - Paste your Venmo URL and title it "Pay with Venmo" or "Tip via Venmo" You can pre-fill the amount and note by using Venmo's deep link format: venmo.com/yourusername?txn=pay&amount=10¬e=Thanks. This reduces friction and makes it easier for the buyer to complete the payment. Venmo person-to-person payments are free when funded by a bank account or Venmo balance. Credit card funding incurs a 3% fee. Venmo business profiles pay 1.9% + 10¢ per transaction. ## How to Add Cash App to Linktree Cash App is another widely used P2P payment app, particularly popular with younger demographics. Like Venmo, there is no native Linktree integration -- you add your Cash App link manually. - Open Cash App and find your $Cashtag (e.g., $yourusername) - Your payment link is cash.app/$yourusername - You can pre-fill an amount: cash.app/$yourusername/25 opens a $25 payment - In Linktree, add a standard Link with the URL and title it "Pay with Cash App" Cash App personal payments are free when funded by a bank account or Cash App balance. Cash App for Business charges 2.75% per transaction. There is no way to accept card payments through a Cash App link -- the buyer must have the app installed. ## How to Add Zelle to Linktree Zelle works differently from PayPal, Venmo, and Cash App. Zelle does not have shareable payment links or a web-based payment page. Instead, payments are sent directly between bank accounts using an email address or phone number. Because of this, you cannot add a clickable Zelle payment link to Linktree the way you would with the other apps. However, you can still direct people to pay you via Zelle: - Add a standard Link in Linktree with a title like "Pay with Zelle" - Link to zellepay.com or a simple landing page with your Zelle email/phone and instructions - Alternatively, use a text-only "Header" link in Linktree to display your Zelle details (e.g., "Zelle: yourname@email.com") without requiring a click The main advantage of Zelle is zero fees -- there are no transaction charges for sending or receiving money. The downside is the extra friction: the buyer has to manually open their banking app, search for your email or phone, and send the payment. There is no buyer protection for goods and services, which makes Zelle better suited for people you already know rather than anonymous internet transactions. ## Does Linktree Pay You? Understanding the Revenue Model A common question is whether Linktree itself pays creators. The short answer: Linktree does not pay you directly. It is a link-in-bio tool, not a monetisation platform or ad network. You do not earn money from views or clicks on your Linktree page. However, Linktree gives you the tools to collect payments from your audience through Commerce Links (where Stripe or PayPal deposits funds into your account) and through external payment links. The money comes from your customers, not from Linktree. Linktree also does not take a commission or platform fee on your sales. Their revenue comes from paid subscription plans (Starter at $5/month, Pro at $9/month, Premium at $24/month) that unlock analytics, customisation, and scheduling features. Commerce Links are available on all plans, including free. ## Limitations of P2P Payment Links on Linktree While adding PayPal, Venmo, Cash App, or Zelle links to your Linktree is quick and free, there are real limitations to relying on peer-to-peer payment apps for business: - No checkout experience -- Buyers leave your Linktree page and land in a generic payment app. There is no product description, no order confirmation, and no receipt with your branding. - No order management -- You have no record of what was purchased, just that money arrived. Reconciling payments to orders is entirely manual. - App dependency -- Venmo and Cash App require the buyer to have the app installed. If they do not, the link leads to a download page instead of a payment. - No digital delivery -- If you sell digital products (templates, courses, presets), you have to manually send files after each payment. - Limited buyer protection -- P2P payments are generally classified as personal transfers. Chargebacks and dispute resolution are limited compared to proper card-based checkout. - No analytics -- You cannot track conversion rates, see how many people clicked your payment link but did not complete the payment, or A/B test pricing. For casual tips and small donations, P2P links work fine. But if you are selling products or services regularly, a proper checkout experience will convert significantly better. ## Better Alternative: Hosted Payment Links If you have outgrown P2P payment links, hosted payment links give you a professional checkout page that you can drop into your Linktree like any other URL. Services like Stripe Payment Links, PayPal checkout buttons, and Square Online Checkout generate a dedicated payment URL with: - A branded checkout page with your logo, product details, and terms - Support for all major card networks, Apple Pay, Google Pay, and buy-now-pay-later - Automatic receipts, invoices, and tax collection - Order management and reporting dashboards - Automatic digital product delivery If you sell on Instagram or TikTok as well as through your bio link, payment links work across all channels. You can use the same URL in your Linktree, your Instagram DMs, and your TikTok comments. For more on this approach, see our guides to payment links for Instagram sales and payment links for TikTok sales. If you want a hosted checkout that works on Linktree without locking you into one app -- accepts cards, Apple Pay, and Google Pay, runs through your existing payment provider, and looks like your brand -- try Shuttle Links & Checkout. Create a branded payment link in minutes, paste it into Linktree, and start taking real card payments instead of P2P transfers. ## Linktree Payment Fees Comparison Fees vary depending on the payment method and whether the buyer is using a personal or business account. Here is a summary of what each option costs you as the seller: Linktree Commerce Links (via Stripe): 2.9% + 30¢ per transaction. No Linktree commission. Linktree Commerce Links (via PayPal): 2.89% + 49¢ per transaction (standard commercial rate). No Linktree commission. PayPal.me personal: 2.99% + fixed fee for goods & services payments. Venmo personal: Free (bank/balance funded). 3% if buyer pays by credit card. Venmo business profile: 1.9% + 10¢ per transaction. Cash App personal: Free (bank/balance funded). Cash App for Business: 2.75% per transaction. Zelle: Free. No transaction fees for sender or receiver. Stripe Payment Links: 2.9% + 30¢ per transaction (same as Commerce Links, but with full Stripe dashboard features). Keep in mind that "free" P2P options like Venmo and Cash App have limits on transaction amounts and may flag business activity on personal accounts. If you are regularly receiving payments for goods and services, switching to a business profile is recommended to avoid account restrictions. ## Tips to Increase Payment Conversions on Linktree Adding a payment link is step one. Getting people to actually click and pay is the harder part. Here are proven tactics to increase your conversion rate: - Put your payment link near the top. Linktree pages are scrollable but most clicks happen on the first 3-4 links. If selling something is your primary goal, make it visible immediately. - Use action-oriented link titles. "Buy My Preset Pack -- $29" converts better than "Products" or "Shop". Include the price to pre-qualify buyers. - Add thumbnails and icons. Links with visual elements get higher click-through rates. Use product photos for Commerce Links and recognisable app logos for P2P payment links. - Offer multiple payment options. Some buyers prefer PayPal, others Venmo, others a card. Listing 2-3 payment methods removes the "I don't have that app" objection. - Use urgency and social proof. Phrases like "500+ sold" or "Only 10 spots left" in your link description create urgency. Linktree Pro and Premium plans let you schedule links, which is useful for limited-time offers. - Pre-fill payment amounts. For Venmo, PayPal.me, and Cash App, use the URL parameters to pre-fill the dollar amount. Every extra step a buyer has to take reduces completion rates. ## Frequently Asked Questions ### Can you accept payments on a free Linktree account? Yes. Commerce Links are available on all Linktree plans, including the free plan. You can also add P2P payment links (PayPal, Venmo, Cash App, Zelle) to any Linktree account since those are just standard URL links. The paid plans add analytics, scheduling, and customisation but are not required for payment functionality. ### Does Linktree take a cut of my sales? No. Linktree does not charge any commission or platform fee on payments processed through Commerce Links. The only fees are the standard processing charges from your connected provider (Stripe or PayPal). For external P2P links, the fees are set by the respective payment app. ### What is the best payment method to add to Linktree? For selling products or digital downloads, use Linktree Commerce Links with Stripe connected -- it offers the widest payment method coverage (cards, Apple Pay, Google Pay, bank transfers) and keeps buyers on your page. For tips and donations, Venmo or PayPal.me links are simplest. Ideally, offer 2-3 options so buyers can choose their preferred method. ### Can I sell digital products through Linktree? Yes. Linktree Commerce Links support automatic digital file delivery. When you create a Commerce Link, you can upload a file (PDF, ZIP, image, etc.) that the buyer receives immediately after payment via email. File size is limited to 500 MB per Commerce Link. ### Are there Linktree alternatives that are better for payments? Several link-in-bio tools focus more heavily on commerce. Stan Store, Beacons, and Koji all offer built-in storefronts, subscriptions, and booking features beyond what Linktree provides. However, Linktree has the strongest brand recognition and the simplest setup. If your needs are primarily link sharing with occasional payments, Linktree is sufficient. If payments are your primary use case, a dedicated creator commerce platform may serve you better. Whether you use Linktree's built-in Commerce Links or add manual payment links for PayPal, Venmo, Cash App, and Zelle, the setup takes just a few minutes. Start with Commerce Links if you want a proper checkout experience, and add P2P links for the apps your audience already uses. Ready for a proper checkout instead of P2P transfers? Shuttle Links & Checkout gives you a branded, mobile-friendly payment page that works on Linktree, Instagram bio, TikTok, email, or anywhere you can paste a URL -- with cards, Apple Pay, Google Pay, and local methods through 40+ payment providers. See how it works. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Payment Links for Hotels & Holiday Accommodation: The Complete Guide ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Stripe](/payment-providers/stripe/) - [PayPal](/payment-providers/paypal-commerce/) - [payment links for Instagram sales](/blog/payment-links-for-instagram-sales/) - [payment links for TikTok sales](/blog/payment-links-for-tiktok-sales/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [See how it works](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuidePayment Links for Hotels & Holiday Accommodation: The Complete Guide→](/guides/payment-links-for-hotels/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/ --- # ACH Payment Links for Small Business: Setup, Costs & Tips | Shuttle > Learn how ACH payment links cut processing fees to under 1%, speed up collections, and simplify bank payments for small businesses. # ACH Payment Links for Small Business: Setup, Costs & Tips By Nick Dunse, January 8, 2026 Learn how ACH payment links cut processing fees to under 1%, speed up collections, and simplify bank payments for small businesses. Talk to us Make enabling payments for your platform and merchant users easy. If you run a small business, you already know that payment processing fees eat into your margins. Credit card transactions typically cost 2.9% plus a per-transaction fee -- and those costs add up fast when you process thousands of dollars each month. ACH payment links offer a straightforward alternative. Instead of sending customers to a card checkout, you send them a link that collects bank account details and initiates an ACH debit -- usually for a fraction of the cost. For small businesses handling recurring invoices, B2B payments, or subscription billing, ACH payment links can cut processing costs by 60-80%. This guide covers everything you need to know: how ACH payment links work, what they cost compared to card payments, how to set them up, and practical tips for improving your collection rates. ## What Are ACH Payment Links? An ACH payment link is a URL that directs a customer or client to a hosted checkout page where they can pay directly from their bank account. Instead of entering a credit or debit card number, the payer provides their bank routing number and account number (or authenticates through their bank's online portal) to authorize a direct debit. ACH stands for Automated Clearing House -- the electronic network that processes bank-to-bank transfers in the United States. ACH handles over 30 billion transactions per year, including direct deposits, bill payments, and business-to-business transfers. When you combine ACH processing with payment links, you get a simple, shareable URL that lets anyone pay you via bank transfer -- no paper checks, no card numbers, and significantly lower fees. ## How ACH Payment Links Work The process from the payer's perspective is simple. Here is what happens when someone clicks an ACH payment link: - Click the link. The payer receives the link via email, text message, or invoice and clicks through to a hosted checkout page. - Enter bank details. They enter their bank routing number and account number, or authenticate via Plaid or a similar bank verification service that lets them log in to their bank directly. - Authorize the payment. The payer confirms the amount and authorizes the ACH debit. This creates a NACHA-compliant authorization record. - ACH network processes the debit. The payment enters the ACH network. Funds are typically debited from the payer's account within 1-2 business days. - Settlement. The funds settle into your business bank account, usually within 3-5 business days. Same-day ACH options are available for faster settlement at slightly higher fees. From your side, you generate the link through your payment processor, attach it to an invoice or message, and track payment status in your dashboard. No manual bank reconciliation required. ## ACH vs Credit Card Payment Links: Fees Comparison The biggest reason small businesses choose ACH payment links is cost. Here is how the fees typically compare: - ACH payment links: 0.5-1.0% per transaction, often capped at $5-$10 per payment. Some providers charge a flat fee of $0.25-$1.50 per transaction instead. - Credit card payment links: 2.6-3.5% plus $0.10-$0.30 per transaction. No cap. International cards and AMEX can push this even higher. To put this in perspective: on a $5,000 B2B invoice, credit card processing costs $130-$175. ACH processing costs $5-$50 -- and if your provider caps fees, it could be as low as $5. Over a year of invoicing, a small business processing $50,000 per month saves $15,000-$18,000 annually by switching recurring and B2B payments from cards to ACH. The trade-off is settlement speed. Card payments typically settle in 1-2 business days, while standard ACH takes 3-5 business days. Same-day ACH narrows this gap but adds $0.50-$1.50 per transaction. For many small businesses, the fee savings far outweigh the slower settlement, especially for improving cash flow on larger invoices where the percentage-based card fees become significant. ## How to Set Up ACH Payment Links Setting up ACH payment links involves a few steps, though the exact process varies by provider. Here is the general workflow: 1. Choose a payment processor that supports ACH. Not all processors offer ACH through payment links. Confirm that your provider supports ACH debit (not just ACH credit/payout) and that they can generate shareable checkout links. Providers like Stripe, Square, and Helcim all offer ACH payment link capabilities. 2. Verify your business bank account. ACH processing requires verification of your settlement bank account. This usually involves micro-deposits (two small test transfers you confirm) or instant verification through a service like Plaid. 3. Configure your checkout page. Set up the hosted checkout to accept bank account payments. Add your business branding, set the payment amount (fixed or variable), and configure confirmation emails. 4. Generate and distribute links. Create payment links for specific invoices, recurring amounts, or open-ended collection. Share them via email, embed them in invoices, or add them to your website. 5. Set up notifications and reconciliation. Configure alerts for successful payments, failed debits, and returned transactions. Connect your payment processor to your accounting software for automatic reconciliation. ## Best ACH Payment Link Providers for Small Business Several payment processors offer ACH payment links suitable for small businesses. Here are the most common options and what sets them apart: Stripe charges 0.8% per ACH debit (capped at $5). Stripe Payment Links support ACH as a payment method alongside cards. Stripe also offers instant bank verification through Plaid integration, which reduces failed payments. Best for tech-savvy businesses that want a developer-friendly platform with strong APIs. Square offers ACH bank transfers at 1% per transaction (minimum $1). Square invoices can include ACH as a payment option. The checkout experience is straightforward and familiar to many consumers. Best for retail and service businesses already using Square for point-of-sale. Helcim provides ACH processing at 0.5% + $0.25 per transaction (capped at $6). Their payment links and hosted pages support ACH with no monthly fees. Best for small businesses looking for the lowest ACH rates without monthly commitments. GoCardless specializes in bank-to-bank payments. They charge 1% + $0.25 per transaction (capped at $4) for ACH. Their payment pages are purpose-built for bank payments. Best for subscription and recurring billing businesses. If your business works with multiple processors or needs to offer ACH alongside card payments across different platforms, Shuttle payment links support ACH collection across multiple payment processors from a single integration -- letting you route ACH payments through whichever processor offers the best rates for your volume. ## ACH Payment Link Use Cases for Small Businesses ACH payment links work best in scenarios where the fee savings justify the slightly longer settlement time. Here are the most common use cases: Invoice payments. Embedding an ACH payment link directly in your invoices lets clients pay with one click instead of mailing a check or calling in a card number. This is especially effective for service businesses, consultants, and freelancers who send regular invoices. If you use QuickBooks for invoicing, adding ACH payment links can significantly reduce your days sales outstanding (DSO). Subscription and recurring billing. SaaS companies, membership organizations, and subscription services can use ACH payment links for initial enrollment. The customer clicks the link, authorizes recurring debits, and subsequent payments are pulled automatically. ACH has lower involuntary churn than cards because bank accounts do not expire the way credit cards do. B2B payments. Business-to-business transactions are where ACH payment links deliver the most value. B2B invoices tend to be larger (thousands or tens of thousands of dollars), which means the percentage-based card fees become painful. A $10,000 invoice costs $290+ to process on a credit card but only $5-$10 via ACH. Rent and property management. Landlords and property managers can send ACH payment links to tenants for monthly rent. The fees are minimal compared to card processing, and tenants are generally comfortable paying rent from their bank accounts. Donations and dues. Nonprofits, churches, and associations can use ACH payment links for recurring donations and membership dues. Lower fees mean more of each donation goes to the cause rather than to payment processing. ## ACH Payment Link Security Security is a common concern when collecting bank account information. Here is how modern ACH payment links keep transactions secure: Bank-level encryption. All reputable payment link providers use TLS encryption (the same technology banks use) to protect bank account details in transit. Account numbers are tokenized and never stored in plain text. Plaid and instant verification. Instead of manually entering routing and account numbers, many ACH payment links now use Plaid or similar services. The customer logs into their bank through a secure widget, which verifies account ownership instantly. This eliminates the risk of incorrect account numbers and reduces fraud. NACHA rules and consumer protections. ACH transactions are governed by NACHA (the National Automated Clearing House Association). Consumers have the right to dispute unauthorized ACH debits within 60 days. Businesses must maintain proper authorization records for every ACH debit they initiate. Fraud detection. Payment processors monitor ACH transactions for suspicious patterns, including unusual amounts, high return rates, and mismatched account holder information. Some providers offer additional verification layers like identity matching. For small businesses, the key takeaway is to use a reputable payment processor with proper encryption, tokenization, and NACHA compliance. Do not collect or store bank account information yourself -- always use a hosted checkout page provided by your processor. ## Tips for Improving ACH Collection Rates ACH payment links are only effective if customers actually use them. Here are practical tips to increase your collection rates: Make the link prominent. Do not bury the payment link at the bottom of a long email. Place it near the top, use a clear button or bold link text, and include the amount due next to it. "Pay $2,500 now" converts better than a generic "click here to pay" buried in a paragraph. Offer ACH as the default option. If your checkout page shows both ACH and credit card options, make ACH the pre-selected choice. You can highlight the fee savings -- many customers are happy to pay via bank transfer when they understand it helps keep your prices lower. Use instant bank verification. Plaid-based verification is faster and more reliable than micro-deposits. Customers are more likely to complete payment when they can log into their bank and confirm in seconds rather than waiting 2-3 days for micro-deposit verification. Send reminders before debits. For recurring ACH debits, send a reminder 3-5 days before the scheduled debit date. This gives customers time to ensure sufficient funds are in their account, reducing return rates and NSF fees. Retry failed payments intelligently. ACH returns (failed debits) are more common than card declines. Set up automatic retries -- typically 3-5 days after the initial failure -- and send a clear notification to the customer explaining the issue and how to resolve it. Incentivize ACH payments. Some businesses offer a small discount (1-2%) for customers who pay via ACH instead of credit card. Since your processing costs drop by 2%+, you can pass some of that savings along while still coming out ahead. Brand your checkout page. A generic, unbranded checkout page looks suspicious when you are asking someone to enter their bank details. Make sure your business name, logo, and contact information are visible on the payment page to build trust. ## Frequently Asked Questions ### How long does an ACH payment link take to process? Standard ACH payments take 3-5 business days to settle. Same-day ACH is available through most processors for an additional fee (typically $0.50-$1.50 per transaction) and settles within the same business day if submitted before the cutoff time. The payer usually sees the debit in their bank account within 1-2 business days regardless of when the funds settle to your account. ### Are ACH payment links safe for customers? Yes. ACH payment links from reputable processors use bank-level TLS encryption, tokenized storage, and NACHA-compliant authorization. Consumers have a 60-day window to dispute unauthorized ACH debits. Using Plaid or similar instant verification services adds another layer of security by eliminating the need to manually enter account numbers. ### Can I use ACH payment links for recurring payments? Yes. Most payment processors that support ACH payment links also support recurring ACH debits. The customer authorizes recurring payments through the initial payment link, and subsequent debits are pulled automatically on your billing schedule. ACH is particularly well-suited for recurring billing because bank accounts do not expire the way credit cards do, which reduces involuntary churn. ### What happens if an ACH payment is returned? ACH returns happen when a debit fails -- typically due to insufficient funds (R01), account closed (R02), or no account found (R03). Returns are usually reported within 2 business days. Most processors charge a return fee of $2-$5. You should set up automatic retry logic and customer notifications to handle returns efficiently. High return rates (above 3%) can trigger additional scrutiny from your processor. ### Do I need a special merchant account for ACH payment links? Not necessarily. Many modern payment processors -- including Stripe, Square, and Helcim -- include ACH capability in their standard accounts. You do not need a separate merchant account or a dedicated ACH processor. However, you will need to verify your business bank account and may need to go through additional underwriting for ACH depending on your industry and processing volume. ## Getting Started with ACH Payment Links ACH payment links are one of the simplest ways for small businesses to reduce processing costs and get paid faster than paper checks. The setup is straightforward, the fees are a fraction of credit card processing, and the security infrastructure is mature and well-regulated. Start by evaluating your current payment mix. If you process significant volume in B2B invoices, recurring billing, or large one-time payments, ACH payment links can deliver immediate savings. For businesses that work across multiple processors or need flexible payment routing, explore how Shuttle can help you offer ACH payment links alongside card payments through a single integration. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment links](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [improving cash flow](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [Stripe](/payment-providers/stripe/) - [Shuttle payment links](/platforms/) - [QuickBooks for invoicing](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [explore how Shuttle can help](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/maximizing-sales-the-benefits-of-integrating-shopping-carts-and-erps-for-merchants/ --- # Maximizing Sales: The Benefits of Integrating Shopping Carts and ERPs for Merchants | Shuttle > How integrating your shopping cart with an ERP system improves order management, reduces manual errors, and accelerates payment reconciliation for growing... # Maximizing Sales: The Benefits of Integrating Shopping Carts and ERPs for Merchants By Nick Dunse, January 4, 2021 How integrating your shopping cart with an ERP system improves order management, reduces manual errors, and accelerates payment reconciliation for growing... Talk to us Make enabling payments for your platform and merchant users easy. Sales optimization plays a crucial role in the success of any business. It is the process of maximizing sales and revenue by implementing strategies and utilizing tools that enhance the overall sales performance. For merchants, this is particularly important as it directly impacts their profitability and growth. However, maximizing sales is not without its challenges. Merchants often face obstacles such as inefficient inventory management, poor customer experience, and cumbersome order fulfillment processes. In order to overcome these challenges and achieve sales optimization, merchants can turn to the integration of shopping carts and ERPs. Key Takeaways - Maximizing sales is crucial for merchants to stay competitive in the market. - Integrating shopping carts and ERPs can streamline inventory management, enhance customer experience, and improve order fulfillment and shipping processes. - Real-time data insights and analytics can be obtained through integrated shopping carts and ERPs, leading to cost savings and efficiency gains. - Customization and personalization opportunities can be leveraged through integrated shopping carts and ERPs. - Security and compliance considerations must be taken into account when integrating shopping carts and ERPs, but the benefits outweigh the risks. Understanding Shopping Carts and ERPs and Their Role in Sales Optimization Shopping carts are software applications that allow customers to select and purchase products or services from an online store. They provide a convenient and user-friendly interface for customers to browse through products, add them to their cart, and proceed to checkout. On the other hand, ERPs (Enterprise Resource Planning) are comprehensive software systems that integrate various business processes such as inventory management, order processing, accounting, and customer relationship management. When shopping carts and ERPs are integrated, they work together seamlessly to optimize sales. Benefits of Integrating Shopping Carts and ERPs for Merchants 1. Streamlining inventory management: Integration of shopping carts and ERPs enables merchants to have real-time visibility into their inventory levels. This allows them to efficiently manage stock levels, avoid stockouts or overstocking, and ensure timely replenishment. With accurate inventory data at their fingertips, merchants can make informed decisions regarding product availability and pricing. 2. Enhancing customer experience: Integrated shopping carts and ERPs provide a seamless shopping experience for customers. Customers can easily navigate through the online store, view product availability in real-time, and receive accurate shipping estimates. This improves customer satisfaction and encourages repeat purchases. 3. Improving order fulfillment and shipping processes: Integration streamlines the order fulfillment and shipping processes by automating tasks such as order processing, picking, packing, and shipping label generation. This reduces manual errors, speeds up order fulfillment, and ensures timely delivery. Merchants can also provide customers with tracking information, enhancing transparency and trust. 4. Real-time data insights and analytics: Integrated shopping carts and ERPs provide merchants with valuable data insights and analytics. They can track sales performance, customer behavior, and inventory trends in real-time. This enables merchants to make data-driven decisions, identify opportunities for growth, and optimize their sales strategies. 5. Cost savings and efficiency gains: Integration eliminates the need for manual data entry and reduces the risk of errors. This saves time and resources for merchants, allowing them to focus on core business activities. Additionally, integration enables better resource allocation, reduces operational costs, and improves overall efficiency. 6. Customization and personalization opportunities: Integrated shopping carts and ERPs offer customization and personalization features that allow merchants to tailor the shopping experience to individual customers. This includes personalized product recommendations, targeted promotions, and customized pricing. By providing a personalized experience, merchants can increase customer loyalty and drive sales. Streamlining Inventory Management with Integrated Shopping Carts and ERPs Metrics | Description Inventory Turnover Ratio | The number of times inventory is sold and replaced in a given period. Stockout Rate | The percentage of time inventory is out of stock and unavailable for sale. Order Fulfillment Time | The time it takes to process and ship an order to a customer. Order Accuracy Rate | The percentage of orders that are fulfilled accurately and without errors. Cost of Goods Sold (COGS) | The direct costs associated with producing and selling a product. Return on Investment (ROI) | The percentage of profit generated from an investment in inventory management technology. Integration of shopping carts and ERPs revolutionizes inventory management for merchants. With real-time synchronization between the two systems, merchants have accurate visibility into their inventory levels at all times. They can track stock levels, monitor product performance, and make informed decisions regarding stock replenishment. Additionally, integration allows for automatic updates of inventory data across all sales channels, ensuring consistency and avoiding overselling or underselling. Integrated shopping carts and ERPs also offer advanced inventory management features such as automated stock alerts, low stock notifications, and reorder point calculations. Merchants can set up automated alerts to notify them when stock levels reach a certain threshold or when a particular product is running low. This proactive approach helps merchants avoid stockouts and ensures that popular products are always available to customers. Furthermore, integration enables merchants to calculate reorder points based on historical sales data, lead times, and desired safety stock levels. This helps merchants optimize their inventory levels and reduce carrying costs. Enhancing Customer Experience with Integrated Shopping Carts and ERPs Integration of shopping carts and ERPs significantly improves the customer experience. Customers can enjoy a seamless shopping journey from browsing products to making a purchase. Integrated systems provide real-time product availability information, ensuring that customers are not disappointed by out-of-stock items. Moreover, customers can view accurate shipping estimates based on real-time inventory data and their location, allowing them to make informed decisions regarding delivery options. Integrated shopping carts and ERPs also enable merchants to offer personalized recommendations and promotions to customers. By analyzing customer data such as purchase history, browsing behavior, and demographics, merchants can provide tailored product suggestions that align with customers' preferences. This enhances the overall shopping experience and increases the likelihood of repeat purchases. Improving Order Fulfillment and Shipping Processes with Integrated Shopping Carts and ERPs Integration of shopping carts and ERPs streamlines the order fulfillment and shipping processes for merchants. When a customer places an order through the shopping cart, the order details are automatically transferred to the ERP system for processing. This eliminates the need for manual data entry, reducing the risk of errors and saving time. Integrated systems also enable automated picking, packing, and shipping label generation. Once an order is received, the ERP system can automatically generate pick lists or packing slips for warehouse staff. This ensures that the correct items are picked and packed for each order, reducing the likelihood of errors or misplacements. Additionally, integrated systems can generate shipping labels with customer information and tracking numbers, making it easy for merchants to fulfill orders promptly. Real-Time Data Insights and Analytics with Integrated Shopping Carts and ERPs Integration of shopping carts and ERPs provides merchants with valuable real-time data insights and analytics. Merchants can track sales performance, monitor customer behavior, and analyze inventory trends in real-time. This enables them to make data-driven decisions and optimize their sales strategies. Integrated systems offer comprehensive reporting and analytics capabilities. Merchants can generate reports on key performance indicators (KPIs) such as sales revenue, conversion rates, average order value, and customer lifetime value. These reports provide merchants with a holistic view of their business performance and help identify areas for improvement. Additionally, integrated systems can generate detailed inventory reports, allowing merchants to analyze product performance, identify slow-moving items, and make informed decisions regarding stock management. Cost Savings and Efficiency Gains with Integrated Shopping Carts and ERPs Integration of shopping carts and ERPs brings significant cost savings and efficiency gains for merchants. By eliminating the need for manual data entry and reducing the risk of errors, integration saves time and resources. Merchants can allocate their resources more efficiently, focusing on core business activities rather than repetitive administrative tasks. Integrated systems also enable better resource allocation by providing accurate inventory data in real-time. Merchants can avoid overstocking or understocking, reducing carrying costs and minimizing the risk of dead stock. Additionally, integration allows for streamlined order fulfillment processes, reducing labor costs and improving overall efficiency. Customization and Personalization Opportunities with Integrated Shopping Carts and ERPs Integration of shopping carts and ERPs offers customization and personalization opportunities for merchants. By analyzing customer data such as purchase history, browsing behavior, and demographics, merchants can provide personalized product recommendations to individual customers. This enhances the shopping experience by offering relevant suggestions that align with customers' preferences. Integrated systems also enable targeted promotions and customized pricing. Merchants can create promotional campaigns that target specific customer segments based on their purchase history or browsing behavior. This allows merchants to deliver personalized offers that resonate with customers, increasing the likelihood of conversion. Moreover, integration enables merchants to offer customized pricing based on customer loyalty, order volume, or other criteria. This personalized approach enhances customer satisfaction and encourages repeat purchases. Security and Compliance Considerations for Integrated Shopping Carts and ERPs Security and compliance are of utmost importance when integrating shopping carts and ERPs. Merchants must ensure that their systems are secure and comply with industry regulations to protect customer data and maintain trust. Integrated systems should have robust security measures in place, such as encryption of sensitive data, secure payment gateways, and regular security audits. Merchants should also implement access controls to restrict system access to authorized personnel only. Additionally, integrated systems should comply with relevant regulations such as the General Data Protection Regulation (GDPR) or Payment Card Industry Data Security Standard (PCI DSS). The Future of Sales Optimization with Integrated Shopping Carts and ERPs The integration of shopping carts and ERPs holds immense potential for sales optimization. By streamlining inventory management, enhancing customer experience, improving order fulfillment processes, providing real-time data insights, enabling cost savings and efficiency gains, offering customization and personalization opportunities, and ensuring security and compliance, integrated systems empower merchants to maximize their sales potential. When choosing a shopping cart and ERP for integration, merchants should consider their specific business needs, scalability requirements, and compatibility with existing systems. The future of sales optimization lies in the seamless integration of shopping carts and ERPs that enable merchants to deliver exceptional customer experiences, drive revenue growth, and stay ahead in a competitive market. ## Related Reading Explore More ### How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### How to Take Payments in Intercom: Payment Collection for Sales & Support ### Chat Agent Payments: How AI Closes Sales Without a Human Handoff ### Shuttle vs Prommt for Platforms and Merchants ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideHow to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments→](/guides/salesforce-service-cloud-payments/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideHow to Take Payments in Intercom: Payment Collection for Sales & Support→](/guides/intercom-payments/) - [GuideChat Agent Payments: How AI Closes Sales Without a Human Handoff→](/guides/chat-agent-payments/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/modernise-receivables-how-accountants-use-shuttle-payment-links-to-accelerate-cash-flow/ --- # Modernise Receivables: How Accountants Use Shuttle Payment Links to Accelerate Cash Flow | Shuttle > Accountants use Shuttle payment links to modernise receivables, accelerate client payments, and reduce time spent chasing overdue invoices. # Modernise Receivables: How Accountants Use Shuttle Payment Links to Accelerate Cash Flow By Nick Dunse, January 9, 2026 Accountants use Shuttle payment links to modernise receivables, accelerate client payments, and reduce time spent chasing overdue invoices. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. For accountants, managing cash flow is a daily reality -- not just for your firm, but often for your clients too. Whether you're offering tax advice, bookkeeping, outsourced finance, or audit services, one challenge cuts across all segments: getting paid on time. Shuttle Payment Links help accountants streamline receivables, reduce debtor days, and offer modern, efficient billing -- not just for themselves, but for the clients they serve. ## The Problem: Accounts Receivable Is Time-Consuming and Often Unpaid Even the most sophisticated accountancy practices face friction in the payment process: 🕒 Long payment cycles -- especially for recurring or advisory services 💸 Outstanding invoices create stress for partners and ops teams 📩 Manual follow-ups eat up valuable time 🏢 Clients ask for help managing their own slow payers The result? An unproductive loop of chasing, reconciling, and waiting -- impacting your margins and your clients' performance alike. ## The Solution: Shuttle Payment Links for Modern Accounting Practices Shuttle Payment Links allow you to send a simple, branded URL to clients or on behalf of clients. It turns any invoice -- your own or theirs -- into a seamless payment experience. Clients click the link, pay by card or bank, and get an immediate receipt. ## Why it works for accountants: ✅ Faster settlement -- turn 30-day terms into 1-day payments 🔄 Reduces chasing -- automated reminders do the work 🧮 Client-friendly UX -- no logins, portals, or friction 🔐 Secure and compliant -- PCI-compliant, with trusted integrations 🧾 Use it internally or extend it as a value-added client service Whether you're billing for tax prep or helping a client collect aged debt, Shuttle gives you a tool to take control of cash flow. Use Cases for Accountancy Practices Shuttle works equally well for your own practice and as a tool to offer clients: For your firm: Annual billing: Add a payment link to year-end accounts invoices VAT returns: Collect fees alongside the completed submission Advisory retainers: Send monthly payment links by email or SMS Ad hoc services: Bill for consultancy or urgent work instantly For your clients: Outsourced credit control: Use Shuttle to collect on their behalf Recurring invoicing: Set up templated links for monthly billing Project fees: Enable digital collection for service businesses Late payer escalation: Send reminders with payment links attached This flexibility helps you drive value across your practice while introducing a high-ROI tool to clients who struggle with AR. 🔍 FAQ: Shuttle Payment Links for Accountants ## What are Shuttle Payment Links? A Shuttle Payment Link is a secure, branded URL that allows clients (or your clients' clients) to pay quickly by card or bank transfer, without logging in or registering. ## How does this help with accounts receivable? Shuttle streamlines the payment process, encourages faster settlement, and allows you or your clients to reduce admin time spent chasing payments. Can I use Shuttle for both my firm and my clients? Yes. You can use Shuttle for your own billing and also set it up to collect payments on behalf of your clients -- ideal for outsourced finance services. ## Is it secure and compliant? Yes. Shuttle is PCI-compliant and uses bank-grade encryption. All payments are processed via trusted payment providers like Stripe or Square. ## How do I include a payment link with an invoice? Just paste the link into your invoice email, or embed it in the PDF. It's simple to add to whatever invoicing system you already use. Can I integrate it with my accounting software? While Shuttle doesn't require full integration, it works alongside Xero, QuickBooks, and Sage. You can copy and paste links directly or automate workflows using tools like Zapier. Can my team use this easily? Yes. Shuttle is designed for non-technical users -- whether that's your admin team, accounts receivable staff, or even junior client managers. ## What about recurring or scheduled payments? You can set up recurring payment links or schedule links for specific milestones. Ideal for retainers, monthly billing, or multi-phase project work. Can I brand it with my firm's identity? Absolutely. Shuttle lets you add your logo, brand colours, and business name to maintain a professional and trustworthy client experience. Final Thoughts: Make Payment Efficiency Part of Your Value Proposition As an accountant, you already help clients become more financially efficient. With Shuttle Payment Links, you apply that same principle to your own firm -- and offer a proactive solution to your clients' AR problems. Get paid faster. Help clients do the same. Shuttle is the smart link between service and settlement. Try Shuttle Payment Links today -- because efficiency doesn't stop at the ledger. Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Get Payment Links today](/platforms/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/modernising-legal-payments-how-law-firms-use-shuttle-payment-links-to-improve-collections/ --- # Law Firm Payment Solutions: A Complete Guide for 2026 | Shuttle > Modern payment solutions for law firms. Covers trust accounting, IOLTA compliance, payment links, PCI requirements, and collecting fees online. # Law Firm Payment Solutions: A Complete Guide for 2026 By Nick Dunse, January 9, 2026 Modern payment solutions for law firms. Covers trust accounting, IOLTA compliance, payment links, PCI requirements, and collecting fees online. Talk to us Make enabling payments for your platform and merchant users easy. Law firms handle some of the most complex payment workflows in any industry. Between trust accounting rules, IOLTA compliance, and the sheer variety of fee structures -- retainers, flat fees, hourly billing, contingency -- collecting payment has traditionally been slow and manual. The result: the average law firm carries over 90 days of accounts receivable, and partners spend hours each month chasing invoices instead of practising law. That is changing. Legal payment solutions now exist that handle compliance, support multiple fee types, and let clients pay in a single click. This guide covers everything law firms and legal tech platforms need to know about modernising payment collection -- from choosing the right payment methods to staying PCI compliant. ## Why Law Firms Need Modern Payment Solutions Legal services have been slower to adopt digital payments than most industries. Many firms still rely on cheques, bank transfers, and manual invoicing. But client expectations have shifted dramatically -- people who pay for everything else online expect the same convenience from their solicitor or attorney. Several factors make payment collection uniquely challenging for law firms: - Trust accounting rules -- client funds must be held in separate trust or escrow accounts. Commingling client money with operating funds is a serious regulatory violation, and any payment system must distinguish between earned fees and unearned retainers. - IOLTA compliance -- Interest on Lawyers' Trust Accounts (IOLTA) programmes require that client funds held in trust generate interest for public benefit. Payment processors must route funds correctly and provide audit trails that satisfy bar requirements. - Client expectations -- 70% of consumers prefer to pay bills online. Firms that only accept cheques or bank transfers lose clients to competitors who offer card payments, ACH, and payment links. - High-value transactions -- legal invoices often run into thousands or tens of thousands. Processing fees on large transactions need careful consideration, and firms need robust fraud protection. - Regulatory record-keeping -- bar associations require detailed records of all client transactions. Any payment solution must generate comprehensive reporting for audits. ## Types of Payments Law Firms Collect Law firms do not have a single billing model. Most firms use several fee structures depending on the practice area and matter type. A good legal payment solution must handle all of them: - Retainers -- upfront deposits held in trust until work is performed. Funds go to the trust account first, then transfer to the operating account as fees are earned. Mishandling retainer funds is a leading cause of bar disciplinary action. - Flat fees -- a fixed price for a defined scope of work (e.g. drafting a will, handling an uncontested divorce). Simpler to collect because the amount is known in advance and goes directly to the operating account. - Hourly billing -- fees accumulate over time and are invoiced periodically (usually monthly). Hourly invoices include detailed time entries and expense breakdowns. - Contingency fees -- a percentage of the settlement or judgement, collected only if the case succeeds. The firm still needs to process the payment split when funds arrive, often involving trust account holds and third-party disbursements. - Court fees and disbursements -- pass-through costs for filing fees, expert witnesses, and other expenses. Billed alongside legal fees but tracked separately for accounting. ## Payment Methods for Law Firms Law firms should offer multiple payment methods to match client preferences and reduce friction in the collection process. Here are the main options: ### Credit and Debit Cards Card payments are the most convenient option for clients. The main consideration is processing fees -- typically 2.5-3.5% per transaction. On a $10,000 legal invoice, that is $250-$350 in fees. Many firms absorb this cost because it accelerates collection, while others pass a surcharge to clients where local rules allow it. ### ACH and Bank Transfers ACH transfers offer lower fees than card payments -- typically a flat fee or a small percentage capped at a few dollars. The trade-off is speed: ACH takes 1-3 business days to settle versus next-day for cards. For large retainer deposits, ACH is often the preferred method. ### Payment Links Payment links are URLs that take the client directly to a hosted checkout page, pre-filled with the invoice amount and matter reference. They can be embedded in email invoices, PDF invoices, text messages, or client portal messages. Adding payment links to invoices typically reduces collection times by 30% or more because clients can pay immediately rather than queuing the invoice for their next bill-pay session. ## Online Payment Systems for Law Firms When evaluating an online payment system for a law firm -- whether small, mid-size, or large -- there are requirements that go beyond what a generic payment processor like Stripe or Square offers out of the box: - Trust account separation -- the system must route payments to either the trust or operating account based on payment type. Retainers go to trust; earned fees go to operating. - Three-way reconciliation -- trust account records, bank statements, and client ledgers must all match. The payment system should generate the data needed for this reconciliation automatically. - Practice management integration -- payments should sync with the firm's practice management software (Clio, PracticePanther, MyCase, etc.) to update matter balances and client ledgers. - Fee handling -- processing fees must never be deducted from trust account funds. The system should deduct fees from the operating account only. - Audit trail -- every transaction needs a timestamped record showing who paid, how much, for which matter, to which account, and when funds settled. For small law firms, cloud-based solutions that bundle payment processing with practice management (like Clio Payments or LawPay) offer the simplest path. For large law firms with existing enterprise systems, an embedded payment solution that integrates via API gives more control over the client experience and fee structures. ## PCI Compliance for Legal Payments Any law firm that accepts credit card payments must comply with the Payment Card Industry Data Security Standard (PCI DSS). This is not optional -- it is a requirement enforced by card networks. PCI compliance protects client card data and shields the firm from liability in the event of a data breach. PCI compliance is especially critical in legal because: - Lawyers have a professional duty of confidentiality that extends to client financial information - A data breach involving client payment details could trigger malpractice claims and bar complaints - Many legal matters involve sensitive or high-profile clients where a payment data leak would be particularly damaging The simplest way for a law firm to achieve PCI compliance is to never handle card data directly. By using payment links or a hosted checkout page, the firm's systems never touch card numbers, CVVs, or expiry dates. The payment processor handles all sensitive data in their PCI-certified environment, and the firm receives only a confirmation that payment was made. This means firms should stop the common practice of taking card details over the phone or on paper intake forms. A payment link sent via email or SMS is faster, more secure, and reduces the firm's PCI scope to the minimum level (SAQ A). ## Payment Links for Law Firm Invoices Payment links are arguably the single most impactful improvement a law firm can make to its collections process. Here is how they work in a legal billing context: - Invoice generation -- the firm creates an invoice in their practice management or billing software, with the matter reference, time entries, and total amount. - Link creation -- a payment link is generated automatically (or manually) with the invoice amount, matter reference, and client details pre-populated. The link points to a branded, hosted checkout page. - Delivery -- the link is embedded directly in the invoice email, attached to a PDF invoice, or sent as a follow-up SMS. Best practice is to include the link in every client communication about the invoice. - Payment -- the client clicks the link, sees the amount and matter details, chooses their payment method (card or ACH), and completes the payment in under a minute. - Reconciliation -- the payment is automatically matched to the invoice and matter, with funds routed to the correct account (trust or operating). The firm's billing system updates in real time. For firms already using payment link workflows in other industries, the legal application follows the same principles -- reduce clicks, pre-fill data, and make it impossible for the client to pay the wrong amount or reference the wrong matter. ## How to Choose a Legal Payment Solution Not all payment solutions are built for the legal industry's compliance requirements. When evaluating options, use this checklist: - Trust account support -- can the system route payments to separate trust and operating accounts? Does it prevent processing fees from being deducted from trust funds? - IOLTA compliance -- does the provider understand and support IOLTA requirements? Can they provide the reporting needed for bar audits? - PCI compliance level -- is the provider PCI Level 1 certified? Does their solution keep the firm's PCI scope at SAQ A (no card data touches firm systems)? - Integration with practice management -- does it connect to Clio, PracticePanther, MyCase, or the firm's existing system? - Payment methods supported -- credit cards, debit cards, ACH, and payment links? Can clients pay via email link without creating an account? - Fee structure -- per-transaction rates for card and ACH? Monthly fees, setup fees, or minimums? - Reporting and audit trail -- transaction-level detail for three-way reconciliation and bar compliance audits? For legal tech platforms looking to embed payments directly into their product, embedded payment solutions for platforms let you build payment links, card processing, and trust account routing directly into your software without building payments infrastructure yourself. ## Legal Payment Solutions for Platforms If you build software for law firms -- a practice management platform, legal billing tool, or client intake system -- embedding payments directly into your product is a significant competitive advantage. Firms increasingly expect their software to handle payments natively rather than requiring a separate provider. Embedded payment links are the fastest path to market. Rather than building card tokenisation, PCI infrastructure, and payment routing from scratch, platforms can use a payment infrastructure layer to generate branded payment links that: - Carry the platform's branding (not a third-party checkout) - Pre-fill invoice amounts, matter references, and client details from the platform's data - Route funds to the correct account (trust or operating) based on payment type - Send real-time payment confirmations back to the platform via webhooks - Keep card data inside the payment infrastructure -- so the platform's PCI scope stays minimal ## Getting Started with Law Firm Payment Solutions Modernising payment collection does not require a full technology overhaul. Most firms can start seeing results within a few weeks by following these steps: - Audit your current process -- how long does it take to collect on invoices today? What percentage of invoices go 60+ days overdue? What payment methods do you currently accept? - Check your bar association rules -- requirements for credit card acceptance, surcharging, and trust account handling vary by jurisdiction. Confirm what is permitted in your state or territory before selecting a provider. - Start with payment links on invoices -- this is the lowest-friction change with the highest impact. Adding a payment link to every invoice email typically cuts collection times by a third. - Expand to retainer collection -- once earned-fee collection is running smoothly, add payment links for retainer deposits. Ensure funds route to your trust account and that the process satisfies your IOLTA obligations. - Measure and iterate -- track days-to-payment, collection rate, and client satisfaction. Most firms see a measurable improvement within the first billing cycle. ## Frequently Asked Questions ### Can law firms accept credit card payments? Yes. All major bar associations permit law firms to accept credit card payments for legal fees. However, processing fees must not be deducted from client trust funds -- they must come from the operating account. Some jurisdictions restrict surcharging clients for card payments, so check your local bar rules before passing fees on. ### What is the best payment solution for small law firms? For small firms (1-10 attorneys), an all-in-one solution that combines practice management with built-in payments is usually the best fit. Clio, PracticePanther, and MyCase all offer integrated payment processing with trust accounting and IOLTA compliance. If you already use software without built-in payments, look for a legal-specific payment provider that integrates with your existing system. ### How do payment links work for retainer deposits? The firm generates a payment link flagged as unearned funds. When the client pays, the system routes funds directly to the IOLTA or trust account -- not the operating account. As fees are earned against the retainer, the appropriate amount transfers from trust to operating with a full audit trail. ### Is it safe to take card payments over the phone at a law firm? Taking card details verbally is technically permitted but creates significant PCI compliance risk. If staff write down or type card numbers, the firm's PCI scope expands considerably -- requiring more security controls, vulnerability scans, and compliance documentation. A safer approach is to send the client a payment link via email or SMS during the call. The client pays on a PCI-certified checkout page, and the firm never handles card data. ### How can legal tech platforms embed payment processing? Legal tech platforms can embed payment processing without building their own infrastructure. A white-label payment API lets platforms generate branded payment links, process card and ACH payments, and route funds to the correct accounts through a single integration. Get in touch to explore embedded payment options for your legal software platform. ## Related Reading Explore More ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Adding payment links to invoices](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [Stripe](/payment-providers/stripe/) - [PCI compliance](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [payment link workflows](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [embedded payment solutions for platforms](/platforms/) - [Get in touch to explore embedded payment options](/discovery/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/ --- # Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know | Shuttle > Compare multi-gateway connectors and native PSP integrations. Learn which approach helps SaaS platforms support more payment providers with less effort. # Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know By Nick Dunse, August 27, 2025 Compare multi-gateway connectors and native PSP integrations. Learn which approach helps SaaS platforms support more payment providers with less effort. Talk to us Make enabling payments for your platform and merchant users easy. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. For SaaS platforms, payments are no longer optional. Whether you're building invoicing software, a reservations platform, or debt collection automation, your merchants expect to be able to accept payments inside your product. But here's the challenge: supporting payments is rarely straightforward. Merchants come to you with their own preferred processors -- Adyen, Worldpay, PayPal, Stripe, local acquirers -- and if you can't support them, you risk losing the deal. This is the classic tension for product leaders: Do we build native PSP integrations one by one? Or do we plug into a multi-gateway connector to get broader coverage quickly? Let's explore the difference, and why so many SaaS product teams are now moving away from native builds to aggregated solutions. The Native PSP Path: Simple to Start, Hard to Scale Many SaaS platforms start by integrating a single payment service provider -- often Stripe. It's an easy way to tick the payments box and get something live quickly. But while the first integration might take a few weeks, every additional PSP multiplies the effort: Engineering resources -- integrations can take 3-6 months each, depending on complexity. Compliance overhead -- PCI, SCA, PSD2, and local regulations add maintenance burden. Merchant diversity -- one PSP is never enough; larger merchants demand choice. Support drag -- every update, bug, or API change requires developer attention. The result? Your product backlog gets clogged. Every time sales asks for a new PSP connector, product leaders face a trade-off: delay roadmap features or say no to the merchant. The Real Cost of Saying No For SaaS companies, payments aren't just about monetisation. They're about retention and competitiveness. Imagine an invoice automation SaaS like InvoiceStack. A prospective merchant wants to use Worldpay because of existing banking relationships. If InvoiceStack can't support it, that deal may go to a competitor who can. Or take a debt collection SaaS like Orbit. If a major client like Mercedes demands their PSP of choice, you either deliver quickly or risk losing a flagship customer. In both cases, the cost of saying no is higher than the cost of building. It's customer churn, lost revenue, and reputational damage. The Multi-Gateway Connector Approach This is where a multi-gateway connector (or payment processor aggregator) comes in. Instead of building PSP connectors one by one, you integrate once with a platform like Shuttle -- and instantly gain access to 40+ global PSPs. Benefits for SaaS product teams: Fast roadmaps -- payments don't clog backlog; integrations don't block new features. Broad coverage -- merchants get the PSP they want, without delays. Future-proofing -- as new PSPs are added, they're available to your merchants automatically. Checkout rules -- merchants can set logic like "for transactions over $10k, only show ACH," tailoring the payment flow without development effort. Zero integration maintenance -- Shuttle handles updates, API changes, and compliance. In short: you shift from being the bottleneck to being the enabler. SaaS Use Cases: Where Multi-Gateway Connectors Win 1. Invoicing Software Invoicing SaaS platforms often start with Stripe or PayPal. But their merchants -- especially mid-sized businesses -- quickly ask for regional PSPs or lower-cost rails like ACH. With Shuttle a number of invoicing SaaS offer multi-gateway choice instantly, without diverting product engineering. 2. Debt Collection Software Debt collection platforms need flexibility. Large merchants like Mercedes won't change PSPs just to adopt new software. Orbit used Shuttle to launch payment links for Mercedes in just 2 weeks -- avoiding a long build that would have delayed revenue and risked the deal. 3. Reservation & CX Platforms CX and reservations software increasingly embed payments in conversations -- AI chatbots, phone voice assistants, customer service flows. A multi-gateway connector ensures payments can happen seamlessly in any channel, with the PSP merchants already trust. Shuttle vs Native: A Direct Comparison Factor | Native PSP Integration | Shuttle Payment Links Time to integrate new PSP | 3-6 months per PSP | 2 weeks for all PSPs Developer resources | High -- constant backlog drain | None -- managed externally Maintenance | Ongoing updates, compliance, API changes | Included in aggregator service Merchant choice | Limited to a few PSPs you build | 40+ PSPs out of the box Competitive risk | High -- lost deals to competitors with more PSPs | Low -- ability to say "yes" to any PSP request Product roadmap impact | Significant disruption | Roadmap stays clear Industry Trends: Why This Matters Now According to McKinsey, global payments revenue exceeded $2.2 trillion in 2023, and merchants increasingly expect payments flexibility from their SaaS providers. At the same time, Bain research shows the cost of merchant churn can exceed 5x the cost of acquisition. Losing deals over PSP coverage is not just frustrating -- it's expensive. And as SaaS platforms adopt more AI and automation in customer experience, payments need to be agent-ready: able to flow through chatbots, voice agents, and workflow tools without engineering drag. Multi-gateway connectors are the only scalable way to achieve this. Final Thought: Roadmaps Should Drive Growth, Not Payments Plumbing Product leaders shouldn't have to choose between building payments connectors and shipping core product features. Payments should accelerate growth, not clog the roadmap. Native integrations might get you started. But multi-gateway connectors future-proof your platform, protect against competitive risk, and let you say "yes" to every merchant request. 👉 Explore how Shuttle's Payment Links for Platforms give SaaS teams fast roadmaps, PSP coverage, and merchant retention -- all without developer effort. ## Related Reading Explore More ### Enterprise PSP Mandates: Why Platforms Need Multiple Gateways ### Agentic Payments: What Platforms Need to Know ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure ### Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure ### Single Global PSP vs Multiple Local Acquirers: How to Decide ## Links - [Book a Call →](/discovery/) - [Payment Links for Platforms](/platforms/payment-links/) - [GuideEnterprise PSP Mandates: Why Platforms Need Multiple Gateways→](/guides/enterprise-psp-mandates/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuidePayments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-invoicing-erp-platforms/) - [GuidePayments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-insurance-platforms/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/navigating-the-future-of-travel-booking-and-payments/ --- # Navigating the Future of Travel Booking and Payments | Shuttle > The travel industry is transforming how bookings and payments work. Explore emerging trends in travel payments, from multi-currency to embedded checkout. # Navigating the Future of Travel Booking and Payments By Nick Dunse, January 10, 2026 The travel industry is transforming how bookings and payments work. Explore emerging trends in travel payments, from multi-currency to embedded checkout. The travel industry has experienced profound changes over the past year, reshaping how people plan, book, and pay for their travel experiences. Industry experts like Aaron from Profit Room, Harry from Ecompay, and Simon from Count recently shared valuable insights into the current trends, challenges, and opportunities in the travel and hospitality sector. Their discussions shed light on the evolving travel booking landscape, payment trends, and the operational hurdles that businesses must overcome to succeed in this dynamic environment. ## Key Trends in Travel: Moving Toward Unique and Personalized Experiences Gone are the days when travelers sought traditional, cookie-cutter vacation packages. Modern travelers are now in search of unique, experience-driven trips that focus on specific destinations rather than generalized bookings. - Destination-Focused Trips: Many travelers are opting for more adventurous and off-the-beaten-path experiences. This trend is driving a surge in interest for destinations that offer immersive cultural, natural, and historical experiences. Rather than simply booking a hotel or a flight, travelers are looking for opportunities to engage with local traditions, explore hidden gems, and dive deeper into the uniqueness of their chosen destination. - Direct Bookings and Personalization: More consumers are moving away from third-party platforms, preferring to book directly with hotels, airlines, and other service providers. This allows them to tailor their experiences according to their needs and preferences. Businesses that offer direct booking options and personalized services -- such as curated itineraries, special packages, and customized recommendations -- are likely to capture the interest of this evolving traveler profile. ## The Payment Landscape: Meeting Global Needs with Seamless and Secure Payments The payment process in travel booking has undergone a dramatic transformation, spurred by a demand for frictionless and secure transactions. Here's how the payment landscape is shifting to meet global customer needs: - Demand for Local Payment Methods: With the rise of global travel, it's no longer enough to provide basic credit card payment options. Consumers from different regions have unique payment preferences, such as e-wallets, mobile payments, and other region-specific methods. To cater to this diverse global audience, businesses need to integrate local payment options that provide a seamless checkout experience. Flexibility in payment is key to improving conversions and enhancing the customer experience. - Fraud Prevention and Trust Building: As more transactions are made online, the risk of fraud has escalated, leading businesses to invest heavily in secure payment gateways. Trust plays a crucial role in ensuring that customers feel comfortable making payments online. Therefore, companies must focus on building trust through transparent, secure, and easy-to-use payment processes. This includes using cutting-edge fraud prevention technologies and clearly communicating security measures to customers. Operational Challenges: Efficiency and Automation in a Changing World In the wake of the pandemic and staff shortages, the travel industry has been forced to adopt new ways to operate efficiently. Automation and technology have become central to overcoming these challenges and streamlining operations. - Technology as a Solution to Staff Shortages: With labor shortages impacting the travel and hospitality sector, technology has proven to be a vital tool in keeping operations running smoothly. Automation of repetitive tasks, from check-in processes to inventory management, allows businesses to operate with reduced staff while maintaining high service standards. Automation also frees up employees to focus on more personalized customer service, improving overall guest satisfaction. - Enhancing the Guest Journey: Targeting specific customer segments with tailored marketing strategies is another key operational focus. By understanding the unique needs and desires of different traveler profiles, businesses can enhance the guest journey from the moment they browse a website to post-trip follow-ups. Optimizing the booking process to be more user-friendly, informative, and intuitive is also critical to converting website visitors into paying customers. Recommendations for Thriving in the Travel Industry - Tech Integration: Investing in a strong tech stack is essential for improving efficiency and enhancing the customer experience. From automated booking systems to customer relationship management (CRM) platforms, technology can help businesses streamline processes and focus on providing superior service to their guests. - Brand Consistency: In a world where brand trust is everything, businesses must maintain consistent branding across all touchpoints. From the first interaction on a website to post-booking communications, a cohesive brand identity builds loyalty and sets expectations. Every interaction a customer has with your brand should reinforce the value and uniqueness of your offering. - Continuous Improvement: The travel industry is constantly evolving, and businesses must stay ahead by continuously improving their payment processes, user experience, and overall customer satisfaction. Whether it's implementing faster payment options, refining the website interface, or offering personalized post-booking services, ongoing refinement is key to staying competitive. ## Conclusion: Embrace Change and Focus on Experience The travel industry is undergoing rapid change, and while these changes present challenges, they also offer immense opportunities. Businesses that embrace new technologies, prioritize the customer experience, and remain adaptable to shifting trends will thrive in this new landscape. By focusing on operational efficiency, payment innovation, and delivering unforgettable travel experiences, companies can carve out a strong position in the ever-evolving travel and hospitality sector. By staying on top of these trends and implementing the right strategies, travel companies can remain competitive and delight their customers in an increasingly complex industry. ## Related Reading Explore More ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent ### Payment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuideAI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent→](/guides/ai-voice-payments-hotels-travel/) - [GuidePayment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel→](/guides/travel-platform-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/ob-gtm/ --- # Open Banking payments is using the wrong Go To Market strategy | Shuttle > 'As soon as a marquee brand embraces OB payments then we will see success' # Open Banking payments is using the wrong Go To Market strategy By Nick Dunse, August 30, 2021 'As soon as a marquee brand embraces OB payments then we will see success' Talk to us Make enabling payments for your platform and merchant users easy. Open Banking payments is using the wrong GTM Introduction This is a statement that I've heard repeated at all the Open Banking events I've been to in the last few years. It's a hopeful desire for consumer retail adoption and for consumers to magically switch to OB payments. We need to question the 'build it and they will come' mindset. I look around the room at the commercial people that I know, and I see doubt on their faces; I don't believe it's just a reflection of my outlook, but a genuine shared confusion about the continued hyperbally around what is a poor go-to-market strategy IMO. I want to lay out a different strategy, it's nothing nobody else could have considered but rather a challenge of the status quo and logical backing that I don't see from anyone else on the stage at present. Executive Summary Let me just say it - B2C is the wrong GTM for Open Banking payments and we should be choosing a less sexy B2B approach to achieve our goals of getting OB payments adopted. I'm not saying OB payments can't work for B2C, they absolutely can, but that's not where we should start. I'm only going to tackle the UK market for the GTM approach because it's the most 'ready' in terms of OB and the ecosystem, but also it's part of the problem with a B2C GTM strategy. As it stands today Open Banking payments are far better suited and have greater opportunity with B2B transactions. This is because: - The B2B payment market is a larger prize - With B2B you can solve a bigger problem that exists today - The monetization opportunities are greater due to the problem size and the expensive alternatives - B2C works well today and is difficult to disrupt - Consumer adoption is harder than business adoption - Consumer requirements aren't met with the current feature set - Once you get business adoption you can get consumer adoption, since we're all consumers, the business is the one to many for awareness-driving Therefore, B2B merchants and B2B software vendors should be the priority for OB payments adoption. If you still don't believe me, here's the one piece of evidence you need. HMRC has been applauded for its Open Banking payments rollout and adoption, one of the largest applications to date. 90% of its payments are B2B. You might want to watch my interview with a large B2B merchant who's successfully implemented Open Banking. Opportunity Quadrant 3 GTM options for Open Banking payments - Fast-moving consumer goods, think shopping carts, food ordering - Slower moving consumer payments, think paying for electricity, broadband, council tax - B2B invoice payments Most OB payment companies that I've spoken to are favouring number 1, 2 and then 3 in that order. Number 1 - the most common payment method in the UK is cards, then wallets. Number 2 - the most common payment method in the UK is Direct Debit or Standing Order. Number 3 - the most common payment method in the UK is manual bank transfer. The Problem - why not B2C Well, you can make your own assumptions from the previous paragraph as to why not B2C; I am now going to expand on those in the following sections. - Consumers are happy and awash with the payment options today, so why enter a crowded market with a weaker solution (?) - B2C transactions via other payment methods are competitively priced and Open Banking txns struggle to compete, which in-turn does not create an incentive for the banks or acquirers. - Adoption by merchants and consumers is at best a chicken and egg situation, at worst it requires a brave merchant who's willing to spend their money and risk their reputation for little upside - Distribution and adoption for B2C is a long road and requires mass education Open Banking payments are account to account but they are also different from A2A payments today. We need to understand where people are today to take them on the journey towards OB payments. Most consumers pay with cards Most businesses pay with A2A (via manual transfer) Analog to digital Businesses currently put bank details on invoices that they expect their customer to pay manually. Business A receives an invoice with some payment instructions. Business B logs into their banking provider carefully enters these banking instructions and completes the transaction, hoping it reaches the destination. Therefore, Businesses are the ones currently closest or most familiar with the account-to-account process today. They are also the ones that are feeling the pain of the cumbersome, slow analogue process explained above. They're aware they could get their invoices paid via a card in an instant, but they don't because: - a) they've always done it this way and - b) don't want to pay the card fees on larger transactions. Open Banking payments can/should improve an existing process... If it ain't broke don't fix it! If B2B invoice payments are currently broken then consumer to merchant payments are currently awash with convenience and options (mostly from by cards). B2C payments are not broken so maybe don't fix them just yet. I find it very hard to believe that OB payments will disrupt the current consumer behaviour and this certainly won't happen until OB payments offer convenience, speed and a trustworthy experience. It's at this point that every OB fanboy (or girl) chimes in and says 'but they are all those things.' My friend - they are not. For OB payments to take ground we need to see a PayPal level of improvement and Apple Pay and Google Pay level of adoption. No successful marketer goes into a saturated market and says 'hey, this thing over here is better, just try it and you'll be converted.' There are so many products and services that have failed with this mindset. The smartphone market wouldn't be what it is if Blackberry hadn't paved the way with business users. No consumer needed email or a calendar on their phone but business people had a problem back then, they needed to be able to do more work from more places. Blackberry solved a problem for a particular niche, they didn't try and disrupt the cool Nokia from the hands of consumers, which, at the time, wasn't broken. The state of the market Any investor will ask a business what's the size of the market? What's the size of the prize? We know that B2B commerce is larger than B2C commerce and we've already stated that the B2B payment process is ripe for improvement. As a consumer ask yourself this, do you wish your favourite retailers offered you open banking payments? No, you don't. But as a business person, you do wish those companies who make you go through analogue bank transfer processes for one-off or recurring payments would make it easier. And if you ever had to transfer money as a small business tell me you didn't wish that this was easier and faster! Take a look at GoCardless, they've been solving this mess for a long time now, limited by the underlying banking infrastructure. At this point, I've neglected to say that OB payments for the B2C GTM could work if there was governmental adoption and incentivisation just like UPI in India. But this is not going to happen in the UK and if it did it would be a closed ecosystem limiting the vision of OB across Europe. The problem is the category OB payments in the B2C model is trying to disrupt incumbent payment methods in the payments category with a hope and a prayer that a marquee merchant will force it upon its customers. This won't work, what has to happen is a new category needs to be defined, and with new category design comes new products and new business models; quite frankly, this is what we're talking about with OB (and what's needed). OB can't compete on price with Standing Orders or Direct Debits, it can't compete on convenience or adoption with cards, it can't compete on local or international remittance without massive adoption by the existing technology players and their users. Tesla's category is environmentally friendly transport (not cars) and Lulu Lemon's category is athleisure wear (not sportswear) the OB payments category can't be Open Banking or Payments. We need to get away from all the payment features and benefit nonsense and talk to businesses about adopting the future of business operations and why that's different and better than what they have today. This fundamental shift alludes most people that I hear on stage. Open Banking payments move analogue businesses with cashflow problems and clunky receivables processes to slick digital realities that improve efficiency and get money-in more effectively; thus transforming business. Now that's more exciting and something we can get behind. Forget the consumer for now. The Solution - Why B2B and how "The sheer volume and digitization opportunity in the B2B space is too large to overlook..." - Mckinsey payments report 2023 The difference between GoCardless and all of the new players in the OB aggregation arena is stark when you look at their website. GC talks about getting paid more efficiently, their message is for the merchant, whereas everyone else has an infrastructure or OB centric message. It's clear that the OB aggregators are going after the integrators, but their sales teams are also (in fact primarily) chasing merchants to adopt their solution. Payment integration is not a market that we'll find the Super Consumer in and therefore won't help these aggregators succeed. Yes, aggregators and acquirers provide scale, but at the moment neither are looking around wanting to provide OB payments because there isn't any demand from businesses or consumers. We need to drive demand from businesses with our new category and positioning and we need to create the Super Consumer. "With global payments volume in the B2B sector estimated at $120 plus trillion, B2B payments disruption is huge and growing." - The Payments Association The OB Payments 'Super Consumer' The OB super consumer is a business that is currently performing manual account-to-account transfers. We know that OB payments does not yet support variable recurring payments and nobody is quite sure when there will be wide support (a conservative estimate is 2028). This means that we're not looking at a go-to-market that enables users who can utilize this functionality. That rules out any regular recurring billing either for consumers or businesses. A Super Consumer is not necessarily a 'consumer' but rather the most influential entity that will consume the product or service. Because OB Payments doens't improve the lives of any actual consumers for one-time payments it's hard to imagine who this Super Consumer is in the consumer category. Whilst we can imagine the adoption of OB payments by a marquee merchant, they will ask themselves the above question, how does this improve the lives of our consumers over what they currently have, and the answer is - it doesn't. Now hold on, I can hear you whispering words like fraud, chargebacks, and account identification services as benefits; but for the consumer use case - none of these things hit hard enough to define a Super Consumer reality for any niche that I can imagine. Quite simply because through ecommerce it's become very clear who we're paying with satisfactory checks in place for existing payment methods. Not to mention that fraud rates are going down in Europe for cards. I'm not overruling the benefits for any user but as a GTM communication, they don't work. We've already touched upon the long road that is required to get OB payments into the hands of a Super Consumer in the B2C space, but what is also worth mentioning that the power of Super Consumers is that they multiply themselves and drive adoption beyond themselves, which again is hard to imagine for the B2C option. But it is not hard to imagine in a world of business account-to-account payments, it is inherently viral. It's clear that the Super Consumer is the SME business that is manually doing bank transfers for local invoice payments today. The adoption is faster, the multiplication is greater and simpler, and the route to deployment is obvious. That route is via payment links that get placed on digital invoices for the other party to pay. No need for a payment gateway or software integrations. No need to pull consumers away from their already sufficient payment methods. For the B2B invoice process, the benefits of OB payments that are present today can shine and be adopted by the Super Consumer. The payment process is digital and streamlined and the account that is receiving the money is checked and validated with confirmation that the payment has been sent and received. No more manual processes and crossed fingers. How to get OB payments out there To expedite distribution and adoption here's what I would do. - Target UK businesses that are sending domestic invoices via invoicing software - Split this into two segments: those that are using corporate cards and those that are using manual bank transfer as a means to getting paid - Wrap Open Banking with payment link technology i.e. no need for checkout integrations - Market to the users of X software the benefits of OB payments over manual bank transfers and more expensive card transactions - Make Super Consumers and advocates - Move to the next software vendor and repeat This results in direct ownership of the merchant and the end customer, it provides a direct relationship with the software vendors who are the ones instructing the world's payments (if not today, they will tomorrow). Conclusion I'm sure I've hit the argument home hard enough by now. But here's the thing, we are all consumers, what we experience in our business lives we can adopt in our personal lives and vice versa. And this is why, when OB payments is ready with features that consumers need then many of us will be Super Consumers of OB from our business lives and can make the adoption in our personal lives. The familiarity of account-to-account methods for businesses is the grease we're looking for. The tolerance for a business to try and use OB payments is far greater because: - People are used to a more cumbersome and untrustworthy opaque process - People have the time to sit down and make a payment as they tend to batch invoicing payments currently, which means there's less pressure on the experience. We can't jump straight to consumer adoption for Open Banking Payments, we need to target businesses who have a problem with manual bank transfers and corporate cards today, so they can improve their cashflow and be more efficient. The problem is big and therefore can be monetized which means the value chain and different players can be incentivised to build, release and support Open Banking. What can Shuttle do? Shuttle provides payment infrastructure to some of the world's leading software vendors and connects leading payment services. This means that a payment service can go to market with one integration. Open Banking Payments could appear in thousands of checkouts quickly. There's no need to integrate into payment gateways and no need to integrate into software vendors. This accelerates the GTM opportunity. Shuttle already has a number of B2B invoicing platforms onboard, as well as shopping carts, ERPs, ticketing, booking etc. At Shuttle we know what sectors and use cases are ripe for solving, who is currently hurting with high card fees or manual processes. If you want to go to market quickly, educate an audience and test this hypothesis Shuttle is the best place to start. Please get in touch with nick@shuttleglobal.com. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [watch my interview](https://youtu.be/c_cyRQXF01Q?si=EwQCsYzDy914FBPv) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/optimizing-checkout-process-the-ultimate-guide-to-checkout-rate-optimization/ --- # Checkout Optimization: 12 Proven Strategies to Increase Conversion Rates | Shuttle > Reduce cart abandonment and increase checkout conversion with these 12 proven optimization strategies. # Checkout Optimization: 12 Proven Strategies to Increase Conversion Rates By Nick Dunse, December 8, 2022 Reduce cart abandonment and increase checkout conversion with these 12 proven optimization strategies. Talk to us Make enabling payments for your platform and merchant users easy. The average online checkout abandonment rate sits between 69% and 80%, depending on the industry. That means for every 10 customers who add something to their cart, only two or three actually complete the purchase. The checkout is where revenue is won or lost. Most abandonment is not about price. It is about friction -- unexpected costs, complicated forms, lack of trust, or missing payment methods. This guide covers 12 strategies that demonstrably reduce abandonment and increase checkout conversion rates. ## 1. Reduce Form Fields to the Minimum Every form field is a decision point where a customer can abandon. Research from the Baymard Institute shows that the average checkout has 14.88 form fields, but most could function with 7-8. What to cut: - Remove the "Company Name" field unless it is essential for B2B transactions - Use a single "Full Name" field instead of separate first and last name fields - Auto-detect city and region from postcode - Default the shipping address to the billing address with a checkbox to change it - Remove optional fields -- if you do not need the data, do not ask for it Impact: Reducing form fields from 15 to 8 typically improves completion rates by 25-30%. ## 2. Show All Costs Upfront Unexpected costs at checkout are the number one reason for abandonment. According to multiple studies, 48% of shoppers abandon because of extra costs (shipping, tax, fees) that appeared only at checkout. Best practices: - Display shipping costs on the product page or in the cart, before checkout - Show tax-inclusive pricing if possible (mandatory in some regions) - If offering free shipping thresholds, show how much more the customer needs to spend - Never add "service fees" or "processing fees" at the last step ## 3. Offer Guest Checkout Forcing account creation before purchase is one of the most common conversion killers. 26% of shoppers abandon because a site required them to create an account. The solution is simple: let customers check out as guests. You can prompt account creation after the purchase is complete -- when the customer has already committed and has a reason to create an account (order tracking, returns). If you must encourage registration, offer a one-click "Save my details" option at the confirmation step rather than a full registration form at checkout. ## 4. Add Multiple Payment Methods If a customer cannot pay with their preferred method, they leave. The payment methods that matter depend on your market: - UK -- cards (Visa, Mastercard), Apple Pay, Google Pay, PayPal, Open Banking / Pay by Bank - Europe -- cards, iDEAL (Netherlands), Bancontact (Belgium), SEPA, Klarna, Giropay (Germany) - US -- cards, Apple Pay, Google Pay, PayPal, Venmo, buy now pay later - Asia -- Alipay, WeChat Pay, GrabPay, local bank transfers - Latin America -- Pix (Brazil), OXXO (Mexico), local card networks Offering the right local payment methods can improve conversion rates by 10-30%, particularly in markets where card penetration is lower. For more on local payment methods by country, see our country payment guides. ## 5. Use a Single-Page Checkout Multi-step checkouts with progress bars and separate pages for shipping, billing, and payment introduce friction at every step. A single-page checkout shows all fields on one screen, reducing the perceived effort. The data is clear: single-page checkouts consistently outperform multi-step flows in A/B tests, particularly on mobile where each page load is slower and each new screen risks losing the customer. If a single page feels too long, use an accordion layout -- sections expand and collapse on the same page without a full page reload. ## 6. Optimise for Mobile Mobile commerce now accounts for over 60% of e-commerce traffic and roughly 45% of revenue. Mobile checkout abandonment rates are consistently higher than desktop because screens are smaller, typing is harder, and connectivity can be unreliable. Key mobile optimisations: - Use large tap targets (minimum 44×44 pixels) for buttons and form fields - Enable auto-fill and native keyboard types (numeric for card numbers, email for email fields) - Support Apple Pay and Google Pay -- these bypass the entire form-filling process - Minimise scrolling -- keep the checkout above the fold where possible - Test on actual devices, not just browser emulators ## 7. Add Trust Signals at Checkout Customers are entering sensitive financial information. They need reassurance that the transaction is secure. Trust signals that have measurable impact: - SSL/padlock indicators -- ensure your checkout uses HTTPS (this should be non-negotiable) - Payment provider logos -- Visa, Mastercard, PayPal, and Apple Pay logos signal familiar, trusted payment processing - Security badges -- PCI DSS compliance badges, Norton/McAfee seals. Studies show these can lift conversion by 5-15% - Money-back guarantee -- even a simple "30-day guarantee" message reduces perceived risk - Customer support access -- a visible phone number or live chat link at checkout reassures customers they can get help if something goes wrong ## 8. Enable Address Auto-Complete Address entry is the most error-prone part of checkout. Auto-complete -- using Google Places API, Loqate, or similar services -- lets customers start typing and select their full address from a dropdown. - Reduces address form fields from 5-6 to 1-2 interactions - Eliminates typos that cause delivery failures - Significantly faster on mobile where typing is cumbersome Address auto-complete typically improves checkout completion rates by 5-8%. ## 9. Implement Card Tokenisation For returning customers, the ability to pay with a saved card removes almost all friction from the checkout process. Card tokenisation stores an encrypted reference to the customer's card details so they can pay with one click on subsequent purchases. This is a security-first approach -- your system never stores actual card numbers. The payment provider handles tokenisation and PCI compliance. Returning customer conversion rates are typically 20-30% higher when saved cards are available. ## 10. Recover Abandoned Checkouts Not every abandonment is permanent. Many customers leave because they were distracted, needed to check something, or were not ready to buy at that moment. Recovery strategies: - Email reminders -- send a reminder within 1-3 hours of abandonment, with a direct link back to their pre-filled checkout. Recovery rates of 5-15% are typical. - SMS/WhatsApp follow-up -- for mobile-first audiences, a text message with their checkout link can be more effective than email. - Payment links -- send a payment link directly to the customer with their order pre-loaded. This bypasses the checkout entirely and lets them pay in a few taps. - Exit-intent offers -- display a targeted offer (free shipping, small discount) when the customer moves to close the tab. ## 11. Offer Buy Now, Pay Later Buy now, pay later (BNPL) options like Klarna, Clearpay, and Affirm have become a significant driver of checkout conversion, particularly for purchases over £50. Customers who might hesitate at a full payment are more likely to complete checkout when they can split the cost. BNPL impact varies by sector but typically lifts average order value by 20-30% and checkout conversion by 10-20% for eligible orders. The key is to display BNPL options early -- on the product page and in the cart -- not just at checkout. Customers need to know the option exists before they decide whether to buy. ## 12. Use Embedded Checkout Instead of Redirects Redirecting customers to a third-party checkout page -- whether it is PayPal, a payment gateway's hosted page, or a bank's 3D Secure page -- introduces friction. Each redirect is a moment where the customer can lose confidence, encounter a loading delay, or simply forget what they were doing. Embedded checkout keeps the entire payment process within your site or app. The customer never leaves your domain. This is particularly important for: - Brand consistency -- your checkout looks and feels like the rest of your site - Conversion data -- you can track the full funnel without losing visibility at the redirect - Mobile experience -- redirects on mobile are especially disruptive For platforms and software companies, embedded payments take this further -- your merchants get a branded checkout experience powered by whichever PSP is best for their market, without the merchant needing to build or maintain a payment integration. ## Checkout Optimization Checklist Use this checklist to audit your current checkout: Minimum form fields (7-8) All costs shown upfront Guest checkout available 3+ payment methods offered Single-page checkout Mobile-optimised Trust signals displayed Address auto-complete Card tokenisation for returning customers Abandonment recovery (email/SMS) Buy now, pay later option Embedded (not redirected) checkout ## How Payment Infrastructure Affects Checkout Conversion Many checkout optimization guides focus exclusively on UX -- form design, button colours, copy. But the underlying payment infrastructure has an equally significant impact on conversion: - Local acquiring -- transactions processed by a local acquirer (e.g., a UK acquirer for UK cardholders) have higher authorisation rates than cross-border transactions. This can be a 5-15% difference in approval rates. - Smart routing -- routing transactions to the PSP with the highest approval rate for that card type, country, and amount improves overall conversion without any UX changes. - PSP redundancy -- if your single PSP has an outage, your checkout is down. With more than one PSP connected, you can move the affected payment types over and keep checkout up when one provider is down. - Local payment methods -- supporting country-specific payment methods is not just a nice-to-have. In markets like the Netherlands (iDEAL) or Brazil (Pix), local methods account for the majority of online transactions. For platforms serving merchants in multiple markets, a PSP-neutral payment layer solves these infrastructure challenges without building separate integrations for each provider. ## Improve Your Checkout Conversion Checkout optimization is not a one-time project. Customer expectations evolve, new payment methods emerge, and what works in one market may not work in another. The businesses with the highest checkout conversion rates are those that treat their checkout as a product -- continuously measured, tested, and improved. If your checkout conversion is limited by your payment infrastructure -- missing payment methods, cross-border routing issues, or single-PSP constraints -- see how Shuttle works for platforms or book a discovery call to discuss your checkout architecture. ## Related Reading Explore More ### How to Connect Checkout.com to Twilio for Voice & IVR Payments ### Agent-Native Checkout: Why AI Commerce Needs New Payment APIs ### Shuttle vs Checkout.com for Platforms ### Checkout.com Alternatives for Platforms ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### The UK Guide to Collecting Overdue Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [country payment guides](/blog/) - [PCI compliance](/guides/ai-voice-agent-pci-payments/) - [payment link](/platforms/links-checkout/) - [embedded payments](/guides/what-is-embedded-payments/) - [country-specific payment methods](/blog/) - [PSP-neutral payment layer](/guides/payment-layer-explained/) - [see how Shuttle works for platforms](/platforms/) - [book a discovery call](/discovery/) - [GuideHow to Connect Checkout.com to Twilio for Voice & IVR Payments→](/guides/checkout-com-twilio-integration/) - [GuideAgent-Native Checkout: Why AI Commerce Needs New Payment APIs→](/guides/agent-native-checkout/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [AlternativeCheckout.com Alternatives for Platforms→](/alternatives/checkout-com/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideThe UK Guide to Collecting Overdue Payments→](/guides/uk-guide-collecting-overdue-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/overdue-invoice-email-templates-uk/ --- # Overdue Invoice Email Templates UK: Chase Letters With Legal Teeth | Shuttle > UK-specific overdue invoice templates with Late Payment Act references, statutory interest calculations, and pay-now links at every stage. # Overdue Invoice Email Templates UK: Chase Letters With Legal Teeth By Shuttle Team, March 9, 2026 UK-specific overdue invoice templates with Late Payment Act references, statutory interest calculations, and pay-now links at every stage. Talk to us Make enabling payments for your platform and merchant users easy. ## Late Payments Are a UK Business Problem Half of all UK small business invoices are paid late. According to the Federation of Small Businesses, late payments contribute to 50,000 business closures every year in the UK and leave SMEs collectively owed over £23.4 billion at any given time. If you're chasing overdue invoices, you're not alone. And you have more legal tools than you might think. This guide provides copy-paste email templates for chasing overdue invoices in the UK, alongside the legal rights you can reference at each stage. Every template includes a payment link placeholder -- because the fastest way to turn a chase into a payment is to make paying effortless. ## Your Legal Rights: UK Late Payment Law Before we get to the templates, here's what UK law says about late B2B payments. ### The Late Payment of Commercial Debts (Interest) Act 1998 This Act gives UK businesses the right to: - Charge statutory interest at 8% per year above the Bank of England base rate on overdue commercial debts. At the current base rate, that's a significant annual percentage. - Claim fixed compensation for the cost of recovering a late payment: - £40 for debts up to £999.99 - £70 for debts between £1,000 and £9,999.99 - £100 for debts of £10,000 or more - Claim reasonable recovery costs beyond the fixed compensation if your actual costs are higher. These rights apply automatically to B2B transactions (not consumer sales) unless you've agreed different payment terms in your contract -- and even then, the Act limits how far those terms can go. ### The Prompt Payment Code The Prompt Payment Code is a voluntary UK government code that signatories commit to. It requires paying 95% of invoices within 60 days, with a target of 30 days. If your customer is a PPC signatory and is paying late, you can reference this in your correspondence. Check the signatory list on GOV.UK. ### Standard UK Payment Terms Unless you've agreed otherwise, the default payment term for B2B invoices in England and Wales is 30 days from the later of: (a) delivery of goods/services, or (b) the customer receiving the invoice. Many businesses set 14-day or 7-day terms in their contracts. ## The Templates ### Template 1: 7 Days Overdue -- Friendly Reminder > Subject: Overdue invoice #[NUMBER] -- friendly reminder Hi [NAME], I hope you're well. I'm writing to let you know that invoice #[NUMBER] for £[AMOUNT] was due on [DATE] and is now 7 days past its due date. I'm sure it's just been overlooked. You can pay securely online here: [PAYMENT LINK] If you've already sent payment, please accept my apologies -- these emails can cross in the post. If there's any query with the invoice, just reply and I'll get it sorted. Thanks, [YOUR NAME] [COMPANY] When to use: First overdue contact. Warm, assumes the best. No mention of penalties -- too early. ### Template 2: 14 Days Overdue -- Second Chase > Subject: Invoice #[NUMBER] -- 14 days overdue (£[AMOUNT]) Dear [NAME], Further to my email last week, invoice #[NUMBER] for £[AMOUNT] remains unpaid. The payment was due on [DUE DATE]. Please arrange payment at your earliest convenience: [PAYMENT LINK] If there is a reason for the delay -- a dispute with the invoice, an approval process, or a cash flow issue -- please let me know so we can find a solution. I'd rather work with you directly than escalate this. Kind regards, [YOUR NAME] [COMPANY] [PHONE] When to use: The friendly approach didn't work. Now you're explicitly asking for either payment or communication. Mentioning "escalate" is a soft signal. Channel tip: If this email doesn't get a response, resend the payment link via SMS. Text messages have a 98% open rate. See our guide on multi-channel payment collection. ### Template 3: 21 Days Overdue -- Firm Notice > Subject: Action required -- invoice #[NUMBER] is 3 weeks overdue Dear [NAME], I've been in touch twice regarding the outstanding balance of £[AMOUNT] on invoice #[NUMBER], issued on [INVOICE DATE] with a due date of [DUE DATE]. We have not received payment or a response to our previous correspondence. Please make payment within 7 days using the link below: [PAYMENT LINK] I should let you know that under the Late Payment of Commercial Debts (Interest) Act 1998, we are entitled to charge statutory interest on overdue debts at 8% above the Bank of England base rate. We would prefer not to apply these charges and to resolve this promptly. If you are experiencing difficulties, please contact me on [PHONE] to discuss a payment plan. Regards, [YOUR NAME] [COMPANY] When to use: Third contact. First mention of the Late Payment Act. This is where many overdue invoices get paid -- the legal reference prompts action. ### Template 4: 30 Days Overdue -- Formal Warning > Subject: OVERDUE: Invoice #[NUMBER] -- formal notice Dear [NAME], Despite multiple attempts to resolve this, the sum of £[AMOUNT] on invoice #[NUMBER] (due [DUE DATE]) remains outstanding. This balance is now 30 days past its due date. Under the Late Payment of Commercial Debts (Interest) Act 1998, we are now applying the following charges: - Statutory interest: 8% + Bank of England base rate per annum, calculated from [DUE DATE] - Fixed compensation: £[40/70/100] The total amount now due is £[REVISED AMOUNT]. To settle this account immediately: [PAYMENT LINK] If payment or a response is not received within 7 days, we will refer this debt for formal recovery. We remain willing to discuss a payment arrangement if you contact us at [EMAIL/PHONE] within that period. Yours sincerely, [YOUR NAME] [COMPANY] When to use: 30 days overdue with no response. You're now applying statutory charges (which is your legal right). The revised total with interest and compensation often triggers immediate payment. ### Template 5: 45 Days Overdue -- Final Notice Before Legal Action > Subject: FINAL NOTICE -- Invoice #[NUMBER] (£[AMOUNT]) Dear [NAME], LETTER BEFORE ACTION This letter serves as formal notice regarding the outstanding debt of £[AMOUNT] (including statutory interest and compensation) owed by [CUSTOMER COMPANY] to [YOUR COMPANY], relating to invoice #[NUMBER] dated [INVOICE DATE]. We have made the following attempts to collect this debt: - [DATE]: Invoice issued with [14/30]-day payment terms - [DATE]: First reminder sent - [DATE]: Second reminder sent - [DATE]: Formal notice sent with statutory interest applied None of these communications have resulted in payment or a substantive response. Under the Pre-Action Protocol for Debt Claims, we are required to give you 30 days from the date of this letter to: 1. Pay the outstanding amount in full: [PAYMENT LINK] 2. Propose a payment plan by contacting [NAME] at [EMAIL/PHONE] 3. Dispute the debt in writing, setting out the grounds of your dispute If none of the above actions are taken within 30 days, we will issue a claim through the County Court without further notice. Any court fees and legal costs will be added to the amount claimed. We strongly encourage you to resolve this matter before court proceedings become necessary. Yours faithfully, [YOUR NAME] [COMPANY] [COMPANY ADDRESS] When to use: This is a Letter Before Action (LBA), a required step before issuing a County Court claim. The Pre-Action Protocol for Debt Claims requires you to send this at least 30 days before issuing proceedings. It must clearly state the debt, provide evidence of previous attempts to collect, and give the debtor options to pay, propose a plan, or dispute. Important: If you intend to follow through with legal action, send this by recorded delivery as well as email. ## For Specific Industries ### Template 6: Professional Services (Law Firms, Accountants) > Subject: Outstanding fees -- matter ref [REFERENCE] Dear [NAME], I am writing regarding our outstanding professional fees of £[AMOUNT] in respect of [BRIEF DESCRIPTION OF WORK], as detailed in our invoice #[NUMBER] dated [DATE]. Our standard payment terms are [14/30] days, and this invoice is now [NUMBER] days overdue. You can settle this account online: [PAYMENT LINK] We value our professional relationship and hope to resolve this promptly. If you wish to discuss the fees or a payment arrangement, please contact me directly. Yours sincerely, [YOUR NAME] [FIRM NAME] Best for: Professional services firms that need formal but relationship-preserving language. ### Template 7: Construction / Trades (Stage Payments) > Subject: Stage payment overdue -- [PROJECT NAME] (£[AMOUNT]) Hi [NAME], Stage [NUMBER] payment of £[AMOUNT] for [PROJECT NAME] was due on [DATE] and is now [NUMBER] days overdue. As you know, we're due to begin the next phase on [DATE]. We'll need to receive payment for the completed stage before we can proceed with further work. Pay online here: [PAYMENT LINK] If there's an issue with the completed work that's holding up payment, let me know and I'll get it resolved. Cheers, [YOUR NAME] [COMPANY] Best for: Builders, electricians, plumbers, and contractors who work in stages. Links payment to project continuation. ### Template 8: Recurring Service (Monthly Retainer) > Subject: [MONTH] retainer payment overdue -- £[AMOUNT] Hi [NAME], Your [MONTH] retainer payment of £[AMOUNT] was due on [DATE] and hasn't been received yet. You can pay online here: [PAYMENT LINK] As a reminder, our service agreement requires payment within [NUMBER] days of the invoice date. If payment is not received within [NUMBER] days, we may need to pause services until the account is brought up to date. Let me know if anything has changed on your end. Thanks, [YOUR NAME] [COMPANY] Best for: Marketing agencies, IT support, recruitment firms, and any business collecting monthly retainer fees. ## What to Do If Emails Don't Work If three emails over 21 days haven't prompted payment, the problem isn't your email wording -- it's the channel. ### Switch to SMS (Day 14+) > [COMPANY]: Invoice #[NUMBER] (£[AMOUNT]) is overdue. Pay now: [PAYMENT LINK]. Reply QUERY if you have questions. SMS has a 98% open rate and is read within 3 minutes on average. For overdue invoices that aren't being paid through email, SMS is the highest-impact next step. ### Switch to WhatsApp (Day 21+) If the customer uses WhatsApp (common in certain sectors and international business), send the payment link there. WhatsApp messages are read even more reliably than SMS, and the payment link works exactly the same way. ### Send a Printed Letter With QR Code (Day 30+) For formal escalation, a posted letter carries more weight than an email. Include a QR code generated from your payment link -- the customer scans it with their phone and pays. See our guide on dunning letter templates for physical letter formats. ## Common Questions ### Can I charge late payment interest on any invoice? Under the Late Payment Act, you can charge interest on B2B (business-to-business) commercial debts. It doesn't apply to consumer transactions. Your contract can set different terms, but the Act prevents contractual terms that are "grossly unfair." ### When should I mention the Late Payment Act? Not in the first reminder. Introduce it at the 21-day mark (Template 3) as a gentle reference, then apply charges at 30 days (Template 4) if needed. Leading with legal language on Day 7 damages the relationship unnecessarily. ### Should I use these for consumer debts? These templates are written for B2B invoices. Consumer debt collection has different rules (the Financial Conduct Authority regulates consumer credit and debt recovery). If you collect from consumers, check FCA guidance before sending payment demands. ### What about the Small Business Commissioner? The UK Small Business Commissioner can help resolve payment disputes between small suppliers and larger customers. If your client is a large company or public sector body that consistently pays late, file a complaint with the SBC. ## Get Paid Faster Every template on this page includes a payment link for a reason -- it's the single highest-impact change you can make to your collection process. Shuttle Payment Links work with 40+ payment gateways, support white-label branding, and can be sent via email, SMS, WhatsApp, or QR code. See how it works. ## Related Reading Explore More ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### The UK Guide to Collecting Overdue Payments ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### Pay Now Button for Invoices: The B2B Guide ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment link placeholder](/guides/pay-now-button-invoices/) - [signatory list on GOV.UK](https://www.gov.uk/government/publications/prompt-payment-code/prompt-payment-code) - [multi-channel payment collection](/guides/multi-channel-payment-collection/) - [Professional services firms](/guides/payment-collection-professional-services/) - [recruitment firms](/guides/b2b-payment-collection/) - [dunning letter templates](/blog/dunning-letter-templates/) - [file a complaint with the SBC](https://www.smallbusinesscommissioner.gov.uk/make-a-complaint/) - [40+ payment gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideThe UK Guide to Collecting Overdue Payments→](/guides/uk-guide-collecting-overdue-payments/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideWorldpay + QuickBooks Integration: Pay Invoices Through Worldpay→](/guides/quickbooks-worldpay-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/pay-now-button-invoices/ --- # Redirecting to: /guides/pay-now-button-invoices/ ## Links - [Redirecting from to](/guides/pay-now-button-invoices/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-adyen/ --- # Payment Links for Adyen: Branded Payment Links on Your Adyen Account | Shuttle > Add a no-code payment links dashboard to your Adyen account. Branded checkout pages, multi-channel sending, and real-time tracking without developer... # Payment Links for Adyen: Branded Payment Links on Your Adyen Account By Nick Dunse, January 10, 2026 Add a no-code payment links dashboard to your Adyen account. Branded checkout pages, multi-channel sending, and real-time tracking without developer... Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Adyen is built for scale. Enterprise merchants, global platforms, and high-volume businesses rely on it for unified commerce. The technology is excellent. Adyen does have a pay-by-link feature. But it's API-driven. Creating a payment link means making API calls, handling webhooks, and managing link lifecycle programmatically. That's fine for a development team integrating it into a product. It's not fine for an operations manager who needs to send a payment link to a customer in the next five minutes. The gap is between Adyen's API capability and what non-technical teams actually need: a dashboard where they can create a link, brand it, send it, and track it. Without filing a Jira ticket. Shuttle fills that gap. It connects to your Adyen account and gives your team a self-serve dashboard for branded payment links -- processed through Adyen. ## How Payment Links Work with Adyen Shuttle integrates with Adyen via REST API. Your Adyen account handles payment processing, risk management, and settlement. Shuttle handles the merchant-facing experience -- link creation, branding, delivery, and tracking. Operations teams, finance teams, and customer service agents can create payment links from the Shuttle dashboard without developer involvement. Each link is fully branded and can be sent via SMS, email, or chat. On the Adyen side, transactions appear exactly as they would with any other integration. Your acquirer relationships, payment methods, and settlement configuration remain unchanged. - Connect your Adyen account using your API key and merchant account credentials. - Create a payment link -- set amount, currency, reference, and expiry. - Brand the checkout page with your logo, colours, and business details. - Send the link via SMS, email, or chat directly from the dashboard. - Customer pays. Transaction processes through Adyen. Settlement follows your existing schedule. ## What You Get - Self-serve dashboard: No API calls needed. Anyone on your team can create and send payment links. - Fully branded checkout: Your brand on every payment page -- not a generic Adyen template. - Multi-channel delivery: SMS, email, WhatsApp, and chat -- send through whatever channel works. - Link tracking: Real-time status: sent, opened, viewed, paid, expired, or failed. - Global payment methods: Cards, wallets, iDEAL, Klarna, and every method you've enabled in Adyen. - Recurring and partial payments: Deposits, instalments, and subscription links -- all from the dashboard. - No development work: Connect in minutes. No integration project. ## Who Uses This - Customer service teams sending refund-and-rebuy links or collecting additional charges. - Finance departments chasing outstanding invoices with a pay link instead of a PDF. - Sales teams closing enterprise deals by sending branded payment links during negotiations. - Operations managers who need to collect ad-hoc payments without involving developers. - Multi-market businesses using Adyen's global reach with local payment methods via payment links. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No setup fees. No transaction markup beyond your existing Adyen rates. Connect your Adyen account in minutes. Start sending branded payment links the same day. No minimum contract, no development project. ## FAQ Do I need to leave Adyen? No. Shuttle sits on top of Adyen. Your account, rates, risk rules, and settlement stay exactly the same. How is this different from Adyen's native pay-by-link? Adyen's pay-by-link is API-driven -- it requires developer involvement. Shuttle gives your non-technical teams a self-serve dashboard with branding, tracking, and multi-channel sending. What payment methods are supported? Every payment method enabled in your Adyen account -- cards, wallets, bank transfers, and local methods like iDEAL, Bancontact, and Klarna. Will customers see Shuttle branding? No. The checkout page is fully white-labelled with your brand. Add payment links to your Adyen account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add payment links to your Adyen account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-affirm/ --- # Payment Links for Affirm: Send Branded Checkout Links Beyond BNPL Checkout | Shuttle > Add branded payment links to your Affirm account. Send checkout links via SMS, email, or chat -- keep your existing Affirm setup. No migration required. # Payment Links for Affirm: Send Branded Checkout Links Beyond BNPL Checkout By Shuttle, January 11, 2026 Add branded payment links to your Affirm account. Send checkout links via SMS, email, or chat -- keep your existing Affirm setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Affirm Only Works at Checkout Affirm is great at what it does -- offering buy now, pay later at the point of checkout. But Affirm merchants often need to collect payments outside the standard ecommerce flow. Maybe you need a deposit before manufacturing a custom order, a payment for a phone sale, or a way to collect from customers who abandoned checkout. Affirm doesn't give you a shareable payment link. You're limited to the checkout widget, which means you can't send a link via SMS to close a sale or collect a non-BNPL payment through a branded experience. ## How Shuttle Payment Links Work with Affirm Shuttle gives Affirm merchants a payment link capability that works alongside your existing Affirm integration. Offer standard card payments via link while keeping Affirm as your BNPL option at checkout. - Sign up for Shuttle and connect your payment processing account (your card processor, not Affirm itself). - Create a payment link in the Shuttle dashboard -- set the amount, apply your branding, and choose payment methods. - Send the link to your customer via SMS, email, WhatsApp, or embed it in a chat conversation. - Your customer clicks the link and pays on a branded checkout page using their card or digital wallet. - The payment settles through your processor. You track everything in Shuttle's dashboard alongside your Affirm sales. This doesn't replace Affirm -- it fills the gap Affirm leaves. Keep offering BNPL at your main checkout and use Shuttle payment links for everything else. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Affirm reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Affirm? - Custom and made-to-order brands -- collect deposits before production starts, then offer Affirm BNPL for the balance at checkout. - High-ticket retailers -- send payment links for phone consultations, personal shopping sessions, and special orders. - Subscription boxes -- collect one-off payments for add-ons, gift subscriptions, and limited editions via link. - Furniture and home goods -- take deposits for custom upholstery, kitchen orders, and interior design projects. - Health and wellness -- send payment links for treatment packages, consultation fees, and membership upgrades. ## Getting Started Shuttle charges a small per-transaction fee. No monthly minimums, no setup fees, and no long-term commitment. You only pay when you use it. Most merchants go live the same day. Connect your payment processor, add your branding, and create your first payment link in minutes. You need an active card processing account (separate from Affirm). Shuttle connects to your processor and gives you a branded payment link layer on top. ## Frequently Asked Questions ### Does Shuttle replace Affirm? No. Shuttle handles payment links for standard card and digital wallet payments. Keep Affirm for BNPL at your regular checkout. The two work side by side. ### Can I offer BNPL through Shuttle payment links? Shuttle payment links support card payments and digital wallets. If you need BNPL at checkout, continue using Affirm there. Shuttle covers the use cases Affirm doesn't -- remote payments, deposits, and one-off charges. ### Do customers see my brand on the payment page? Yes. Every Shuttle payment link opens a fully branded checkout page with your logo, colours, and business name. It looks like your own checkout experience. ### How do I reconcile Shuttle payments with my Affirm sales? Shuttle provides its own dashboard and reporting. You can export transaction data and reconcile it with your Affirm reports and your card processor's statements. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-authorize-net/ --- # Authorize.net Payment Links: Create & Send Payment Links | Shuttle > Learn how to create and send Authorize.net payment links using Accept Hosted, the API, or third-party tools like Shuttle. Setup, fees, and FAQ. # Authorize.net Payment Links: Create & Send Payment Links By Nick Dunse, August 30, 2023 Learn how to create and send Authorize.net payment links using Accept Hosted, the API, or third-party tools like Shuttle. Setup, fees, and FAQ. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. Authorize.net is one of the longest-running payment gateways in the US, processing transactions for hundreds of thousands of merchants. But when it comes to sending a simple payment link -- a URL you can email, text, or drop into a chat -- the options are less obvious than with newer providers like Stripe. The good news: you can create Authorize.net payment links. The platform offers Accept Hosted, a hosted payment page you can share as a link. You can also use the Authorize.net API to generate payment forms, or connect a third-party payment link provider that works with your existing Authorize.net account. This guide walks through every method -- from the built-in Accept Hosted approach to third-party tools -- so you can pick the right option for your business. ## Does Authorize.net Support Payment Links? Authorize.net does not have a dedicated "payment links" feature like Stripe Payment Links or PayPal.Me. There is no button in the merchant dashboard that says "create a payment link" and gives you a shareable URL. However, Authorize.net offers Accept Hosted -- a hosted payment page that acts as a payment link. Accept Hosted generates a secure, PCI-compliant payment form hosted on Authorize.net's servers. You request a token via the API, build a URL with that token, and share it with customers. When the customer clicks the link, they see a payment form where they can enter their card details and pay. Accept Hosted handles PCI compliance for you -- the card data never touches your servers. This is the closest thing Authorize.net offers to a native payment link, and it works well for one-off payments, invoices, and phone orders. The limitation is that Accept Hosted requires API integration to generate tokens. It is not a self-service, no-code tool. You need a developer (or a third-party service) to set it up. ## How to Create Authorize.net Payment Links with Accept Hosted Accept Hosted is Authorize.net's official hosted payment page solution. Here is how it works at a high level: - Call the getHostedPaymentPageRequest API endpoint with your API login ID and transaction key. Include the transaction amount, order description, and any customisation settings. - Authorize.net returns a form token -- a unique string that represents that specific payment session. Tokens are valid for 15 minutes by default. - Build a URL that loads the Authorize.net hosted form using the token. You can embed this in an iframe on your site or redirect the customer to the Authorize.net-hosted page directly. - Share the URL with your customer via email, SMS, or chat. When they click, they see the payment form and can enter their card details. - After payment, Authorize.net processes the transaction through your merchant account and sends a webhook or redirect to confirm the result. The API call is straightforward if you are comfortable with REST APIs. Authorize.net provides SDKs for PHP, .NET, Java, Ruby, Python, and Node.js. The key parameters include the transaction amount, a return URL (where the customer lands after paying), and optional settings for customising the form appearance. One important detail: Accept Hosted tokens expire. If you are sending a payment link by email and the customer does not open it within 15 minutes, the link stops working. You can increase the expiry window through the API settings, but there is no option for a permanently valid link. For longer-lived links, you will need a server-side script that generates a fresh token when the customer clicks. ## Sending Authorize.net Payment Links to Customers Once you have generated an Accept Hosted payment link, you can send it through any channel. The most common methods include: - Email -- Embed the link in an invoice email or a standalone "Pay Now" email. This is the most common use case for service businesses and B2B companies sending invoices. - SMS -- Text the link to a customer during or after a phone call. Useful for phone orders, appointment deposits, and field service payments. - Chat and messaging -- Share the link in WhatsApp, Facebook Messenger, or live chat. Particularly effective for customer support teams resolving billing issues in real time. - Invoicing software -- If you use QuickBooks with Authorize.net, you can add payment links to your invoices so customers can pay online instead of mailing a cheque. See our guide on maximizing invoice payments with Authorize.net and QuickBooks for a detailed walkthrough. The challenge with Accept Hosted links is the token expiry. If you need links that remain valid for days or weeks -- for example, a payment link in a recurring invoice -- you will need a middleware layer that generates tokens on demand. This is where third-party payment link tools become useful. ## Customising the Authorize.net Hosted Payment Page Accept Hosted gives you some control over the look and feel of the payment form. When you call the API to request a token, you can pass configuration settings that adjust the hosted page: - Show or hide the billing address fields - Show or hide the shipping address fields - Change the header text (e.g. your company name) - Set background colours for the payment form - Choose whether to show the order summary or hide it - Enable or disable email receipts to customers - Define return and cancel URLs for post-payment redirects These options are passed as hostedPaymentSettings in the API request. Each setting is a name-value pair, such as hostedPaymentBillingAddressOptions to control address fields or hostedPaymentStyleOptions to set the CSS for the form container. The branding options are limited compared to modern payment link tools. You cannot upload a logo, change fonts, or fully white-label the checkout experience. The form always carries Authorize.net's styling to some extent. If brand consistency matters to your business, a third-party tool that offers full white-labelling may be a better fit. ## Authorize.net Payment Link Fees and Pricing Authorize.net charges a monthly gateway fee plus a per-transaction fee. The standard pricing is $25 per month for the gateway and 2.9% + 30¢ per transaction on the all-in-one plan. If you have your own merchant account, the gateway-only plan is $25 per month plus 10¢ per transaction (with separate interchange and processor fees on top). There is no additional charge for using Accept Hosted. The hosted payment page is included with your Authorize.net account. You pay the same per-transaction rate whether the payment comes through an API integration, Accept Hosted, or a virtual terminal entry. If you compare this to Stripe's payment links, Stripe charges 2.9% + 30¢ per transaction with no monthly fee. The per-transaction cost is similar, but Authorize.net adds the $25 monthly gateway fee. For low-volume businesses, Stripe may be cheaper overall. For higher-volume merchants who already use Authorize.net, the cost difference is negligible since you are already paying the gateway fee. For a broader comparison of both platforms, see our Authorize.net vs Stripe breakdown. ## Third-Party Payment Link Providers That Work with Authorize.net If Accept Hosted feels too technical or too limited for your needs, several third-party tools can add payment link functionality on top of your Authorize.net account. These services connect to your existing gateway -- your processing rates and merchant account stay the same -- and add a link creation and management layer. Shuttle is one option purpose-built for this use case. Shuttle creates branded payment links that connect to your Authorize.net account. You get a no-code dashboard to create links, fully branded checkout pages with your logo and colours, support for multiple payment methods including Apple Pay and Google Pay, and real-time payment tracking. Because Shuttle sits on top of your existing gateway, your Authorize.net rates do not change, and funds settle to your merchant account as normal. Other approaches include: - Invoicing platforms -- Tools like QuickBooks, FreshBooks, and Xero can connect to Authorize.net and generate pay-by-link invoices. The link is essentially a hosted invoice with an embedded payment form. - Custom-built links -- If you have a development team, you can build a lightweight web app that generates Accept Hosted tokens on demand and wraps them in a branded page. This gives you full control but requires ongoing maintenance. - E-commerce plugins -- WooCommerce, Magento, and other platforms with Authorize.net plugins can generate order-specific payment URLs. These work well if you already run an online store but are overkill for simple link-and-pay workflows. For businesses that want payment links without building anything, Shuttle or an invoicing platform are the fastest paths. Explore Shuttle for platforms to see how it works with Authorize.net and other gateways. ## Limitations of Authorize.net Payment Links While Accept Hosted gets the job done for basic payment collection, it has some real limitations compared to dedicated payment link tools: - Token expiry -- Payment links expire after 15 minutes by default. You can extend this, but there is no option for a permanent link. Every link requires a fresh API call to generate a new token. - No dashboard link creation -- You cannot create a payment link from the Authorize.net merchant dashboard. Every link requires API integration, which means you need a developer. - Limited branding -- You can change colours and toggle fields, but you cannot upload a logo, use custom fonts, or fully white-label the page. The checkout always looks like an Authorize.net form. - No link tracking -- Accept Hosted does not provide analytics on how many people opened the link versus how many paid. You get transaction records in your Authorize.net account, but no funnel visibility. - No recurring or instalment support -- Accept Hosted handles one-time payments only. If you need to set up a payment plan or subscription through a link, you will need to use Authorize.net's ARB (Automated Recurring Billing) feature separately or use a third-party tool. - No multi-channel management -- There is no central place to manage all your payment links, see their status, or resend them. Each link is a standalone API call. For merchants who need a simple one-off payment page, these limitations may not matter. But for businesses sending dozens or hundreds of payment links per month -- or teams that need to track conversions and manage links from a dashboard -- a dedicated payment link provider is the better choice. ## Who Should Use Authorize.net Payment Links? Authorize.net payment links -- whether through Accept Hosted or a third-party tool -- are a good fit for several types of business: - Service businesses -- Plumbers, electricians, consultants, and agencies that complete work first and collect payment after. Send a payment link instead of chasing cheques or waiting for bank transfers. - B2B companies -- Add a "Pay Now" link to your invoices and cut your days-sales-outstanding. Works especially well alongside accounting integrations like QuickBooks. - Phone order businesses -- Take an order over the phone, then send a payment link by SMS so the customer can enter their own card details. This keeps you PCI-compliant because you never handle the card number. - Platforms and software companies -- If you build software that serves merchants on Authorize.net, adding payment link capabilities through a provider like Shuttle lets you offer white-labelled payment links as part of your platform without building the payments infrastructure yourself. ## Frequently Asked Questions ### Can I create payment links from the Authorize.net dashboard? No. Authorize.net does not offer a self-service payment link builder in its merchant dashboard. To create a payment link, you need to use the Accept Hosted API or connect a third-party tool like Shuttle that adds a no-code dashboard on top of your Authorize.net account. ### Do Authorize.net payment links expire? Yes. Accept Hosted tokens expire after 15 minutes by default. You can configure a longer expiry window through the API, but there is no option for a payment link that never expires. If you need persistent links, use a third-party service that generates tokens on demand when the customer clicks. ### Is there an extra fee for Authorize.net payment links? No. Accept Hosted is included with your Authorize.net account at no additional cost. You pay the same per-transaction fees (2.9% + 30¢ on the all-in-one plan, or 10¢ per transaction on the gateway-only plan) regardless of whether the payment comes through an API integration, the virtual terminal, or an Accept Hosted link. ### Can I accept recurring payments through an Authorize.net payment link? Not natively. Accept Hosted handles one-time payments only. For recurring billing, you would need to use Authorize.net's ARB (Automated Recurring Billing) feature through the API, or use a third-party payment link provider that supports subscriptions and instalment plans. ### Can I use Authorize.net payment links on my phone? The Accept Hosted payment page is mobile-responsive, so customers can pay from any device. However, creating the links themselves requires API access -- there is no Authorize.net mobile app for generating payment links on the go. If you need to create and send links from your phone, a third-party tool with a mobile-friendly dashboard is the way to go. Authorize.net payment links are possible, even if the platform does not make it as easy as newer competitors. Accept Hosted gives you a solid foundation for PCI-compliant hosted payments, and third-party tools can fill the gaps in branding, link management, and analytics. If you are already processing through Authorize.net, there is no reason to switch providers -- just add a payment link layer on top. Ready to add payment links to your Authorize.net account? Book a discovery call to see how Shuttle connects to your existing gateway in minutes. ## Related Reading Explore More ### How to Connect Authorize.net to Twilio for Voice & IVR Payments ### Authorize.net + QuickBooks Integration: Accept Invoice Payments Online ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Stripe](/payment-providers/stripe/) - [maximizing invoice payments with Authorize.net and QuickBooks](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [Stripe's payment links](/blog/revolutionize-your-payment-process-with-stripe-payment-links/) - [Authorize.net vs Stripe](/blog/authorize-net-vs-stripe/) - [Explore Shuttle for platforms](/platforms/) - [Shuttle](/discovery/) - [Book a discovery call](/discovery/) - [GuideHow to Connect Authorize.net to Twilio for Voice & IVR Payments→](/guides/authorize-net-twilio-integration/) - [GuideAuthorize.net + QuickBooks Integration: Accept Invoice Payments Online→](/guides/authorize-net-quickbooks/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-braintree/ --- # Payment Links for Braintree: Send Payment Links Through Your Braintree Account | Shuttle > Add payment link capability to Braintree. Send branded checkout links via SMS, email, or chat. Process through your existing Braintree account. # Payment Links for Braintree: Send Payment Links Through Your Braintree Account By Nick Dunse, January 12, 2026 Add payment link capability to Braintree. Send branded checkout links via SMS, email, or chat. Process through your existing Braintree account. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Braintree, owned by PayPal, is a go-to processor for e-commerce and marketplace payments. It powers checkout for some of the world's biggest platforms. The SDK is solid. The documentation is thorough. But Braintree is built for integrated checkout -- not ad-hoc payment collection. There is no native payment links feature. If a Braintree merchant needs to email a customer a link to pay an invoice, collect a deposit over SMS, or take a phone order without handling card numbers, Braintree doesn't have an answer. The workaround most merchants use? Ask for a bank transfer. Or set up a second payment provider just for one-off links. Both are messy. One loses you conversion. The other fragments your payment reporting. Shuttle gives Braintree merchants payment links -- processed through their existing Braintree account. No new provider. No fragmented data. ## How Payment Links Work with Braintree Shuttle connects to your Braintree account using your API keys. Once connected, you can create branded payment links from the Shuttle dashboard. Transactions process through Braintree exactly like any other card-not-present payment. Your merchant ID, processing rates, and settlement schedule stay the same. Shuttle adds the link creation, branding, delivery, and tracking layer that Braintree doesn't provide. Customers see a branded checkout page -- not a generic payment form. They enter their card details, pay, and the transaction appears in your Braintree portal. - Connect your Braintree account with your API keys -- takes a few minutes. - Create a payment link in the dashboard. Set amount, currency, reference, and expiry. - Customise the checkout page with your brand -- logo, colours, messaging. - Send the link via SMS, email, or chat. - Customer pays on the branded page. Braintree processes the transaction. Settlement as normal. ## What You Get - Payment links for Braintree: The capability Braintree doesn't offer natively. - Branded checkout: Your business name, logo, and colours on every payment page. - SMS, email, and chat sending: Send links through any channel from the dashboard. - Link status tracking: Know when links are sent, opened, viewed, completed, or expired. - Cards and PayPal: Accept card payments and PayPal through your Braintree account. - Deposits and partial payments: Collect deposits upfront and send balance links later. - No integration project: Connect with API keys. No developer needed for day-to-day use. ## Who Uses This - E-commerce businesses sending payment links for phone orders and custom quotes. - Marketplace operators collecting manual payments from sellers or service providers. - Subscription businesses sending payment links for failed renewals or account upgrades. - B2B companies attaching payment links to invoices for faster collection. - Customer support teams resolving payment issues by sending a fresh payment link. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No additional transaction fees. Your Braintree rates stay exactly the same. Setup is quick -- enter your Braintree API keys, configure your branding, and start sending links. No integration project, no developer sprints. ## FAQ Do I need to leave Braintree? No. Shuttle processes everything through your Braintree account. Your rates, your merchant ID, your settlement -- all unchanged. Can I accept PayPal through the payment links? Yes. If PayPal is enabled on your Braintree account, customers can pay via PayPal or card through the same link. Will customers see Shuttle? No. The checkout is fully white-labelled with your brand. Customers see your business -- not Shuttle. How does settlement work? Funds settle through Braintree to your bank account on your existing schedule. Shuttle never holds or processes funds. Add payment links to your Braintree account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add payment links to your Braintree account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-bs-payone/ --- # Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants | Shuttle > Add branded payment links to your BS Payone account. Send checkout links via SMS, email, or chat -- keep your existing BS Payone setup. # Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants By Shuttle, February 19, 2026 Add branded payment links to your BS Payone account. Send checkout links via SMS, email, or chat -- keep your existing BS Payone setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: BS Payone Doesn't Do Payment Links Well BS Payone is a major payment provider serving merchants across Germany, Austria, and Switzerland. They offer e-commerce payment gateways, POS terminals, and integrated solutions for the DACH market. While BS Payone handles online checkout and terminal processing well, self-serve payment link creation is not a native feature. DACH merchants who need to send branded payment links for invoices, deposits, or remote collections have to look beyond BS Payone for a solution. ## How Shuttle Payment Links Work with BS Payone You don't need to replace BS Payone. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that BS Payone doesn't offer natively. - Register for Shuttle and configure your branded checkout -- upload your logo and set your brand colours. - Create a payment link from the Shuttle dashboard: set the amount in EUR or CHF, add a description, and include a customer reference. - Send the link to your customer via email, SMS, or messaging apps like WhatsApp or Signal. - Your customer clicks the link and pays on your branded checkout page using their preferred card. - Track the payment in your Shuttle dashboard. Your BS Payone e-commerce gateway and POS terminals continue operating independently. Your BS Payone processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with BS Payone-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard BS Payone card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your BS Payone reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with BS Payone? - German e-commerce merchants -- collecting additional payments for order modifications, returns processing fees, or custom product deposits outside the webshop checkout. - Swiss professional services -- sending payment links for consulting fees, legal retainers, or project milestones to clients across the DACH region. - Austrian tourism and hospitality -- collecting booking deposits, cancellation fees, or activity reservations from guests via email or WhatsApp. - B2B wholesalers -- sending payment links for trade invoices to business customers who want to pay by card instead of Überweisung (bank transfer). - Membership and subscription businesses -- collecting annual dues, event fees, or one-off charges from members who aren't set up for direct debit. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with BS Payone required because Shuttle processes payment link transactions independently. If you're currently using BS Payone and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave BS Payone to use Shuttle payment links? No. Shuttle runs alongside BS Payone. You keep your existing BS Payone setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Does Shuttle work with EUR and CHF currencies? Yes. Shuttle supports Euro and Swiss Franc transactions. Your customers can pay in the currency they expect, and you can manage multiple currencies from a single Shuttle dashboard. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-cardconnect/ --- # Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments | Shuttle > Add branded payment links to your CardConnect account. Send checkout links via SMS, email, or chat -- keep your existing CardConnect setup. # Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments By Shuttle, February 19, 2026 Add branded payment links to your CardConnect account. Send checkout links via SMS, email, or chat -- keep your existing CardConnect setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: CardConnect Doesn't Do Payment Links Well CardConnect, now part of Fiserv, provides card payment processing primarily through Clover terminals and integrated POS solutions. Their strength is in-person card acceptance -- dip, tap, and swipe. But when merchants need to collect payments remotely, CardConnect doesn't offer a standalone payment link feature. You're left keying in card numbers over the phone through a virtual terminal, which is slow, error-prone, and puts PCI compliance burden on your staff. ## How Shuttle Payment Links Work with CardConnect You don't need to replace CardConnect. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that CardConnect doesn't offer natively. - Set up your Shuttle account and add your business branding for a professional checkout experience. - Create a payment link in the dashboard -- enter the amount, add an invoice number or order description. - Send the link to your customer by email, text message, or any messaging platform. - Your customer opens the link, enters their card details on your branded secure checkout, and pays. - You get instant confirmation in Shuttle. Your CardConnect terminals and Clover POS continue processing in-person payments as usual. Your CardConnect processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with CardConnect-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard CardConnect card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your CardConnect reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with CardConnect? - Small retailers -- collecting deposits for special orders, layaways, or custom items when the customer isn't in the store. - Auto repair and service shops -- sending payment links for repair estimates and final invoices so customers can pay before picking up their vehicle. - Professional services -- like accountants, lawyers, and consultants collecting retainers or invoice payments from clients remotely. - Restaurants with catering services -- collecting deposits for catering orders, private events, or large group bookings via payment links. - Home services businesses -- sending payment links after completing work -- cleaning, pest control, handyman services -- for immediate collection. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with CardConnect required because Shuttle processes payment link transactions independently. If you're currently using CardConnect and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave CardConnect to use Shuttle payment links? No. Shuttle runs alongside CardConnect. You keep your existing CardConnect setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Is this more secure than taking card numbers over the phone? Yes. Payment links mean your staff never see or handle card numbers. The customer enters their details directly on a PCI-compliant checkout page. This reduces your PCI scope and eliminates the risk of card data being written down or overheard. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-checkout-com/ --- # Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account | Shuttle > Add a no-code payment links dashboard to Checkout.com. Your operations team can create and send branded payment links without developer involvement. # Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account By Nick Dunse, January 13, 2026 Add a no-code payment links dashboard to Checkout.com. Your operations team can create and send branded payment links without developer involvement. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Checkout.com is a developer-first platform. The APIs are clean. The documentation is thorough. For engineering teams building payment flows into products, it's excellent. But that developer-first approach creates a problem for everyone else. When an operations manager needs to send a payment link to a customer, they can't. When a finance team wants to chase an outstanding invoice with a pay link, they need to file a dev ticket. When customer service needs to take a payment during a call, they're stuck. Checkout.com has a payment links API. But "API" is the key word. Every link requires code. There's no merchant-facing dashboard where non-technical teams can create, send, and track payment links themselves. Shuttle provides that dashboard. Connected to your Checkout.com account. No code required for day-to-day use. ## How Payment Links Work with Checkout.com Shuttle integrates with Checkout.com via REST API. Your Checkout.com account handles payment processing, tokenisation, and settlement. Shuttle handles the no-code layer -- the dashboard, branding, delivery, and tracking. Your team logs into Shuttle, creates a payment link, brands the checkout page, and sends it via SMS, email, or chat. The customer pays. The transaction appears in your Checkout.com Hub. No developer involvement for creating links. No API calls. No webhooks to manage. Just a dashboard. - Connect your Checkout.com account with your API credentials. - Open the Shuttle dashboard and create a payment link -- amount, currency, reference. - Brand the checkout page with your logo, colours, and business name. - Send the link to your customer via SMS, email, or chat. - Customer pays. Transaction processes through Checkout.com. Settlement unchanged. ## What You Get - No-code dashboard: Create and send payment links without developer involvement. - Branded checkout: Professional, on-brand payment pages -- not generic forms. - Multi-channel sending: SMS, email, WhatsApp, chat -- send through any channel. - Real-time tracking: See link status from sent to paid, including opens, views, and drop-offs. - Global payment methods: Cards, wallets, and local methods -- whatever you've configured in Checkout.com. - Team access controls: Give operations, finance, and CS teams access without sharing API keys. - Partial and recurring payments: Deposits, instalments, and subscription links from the dashboard. ## Who Uses This - Operations teams that need to collect payments without waiting for developer support. - Customer service agents resolving billing issues by sending a payment link during the call. - Finance teams chasing overdue invoices with a one-click payment link. - Sales teams closing deals by sending a branded payment link in real time. - Multi-market businesses collecting payments across countries using Checkout.com's local acquiring. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No setup fees, no transaction surcharges. Connect your Checkout.com account in minutes. Your team can start sending branded payment links the same day. No minimum contract. ## FAQ Do I need to leave Checkout.com? No. Shuttle connects to your existing account. Processing, settlement, and risk management stay with Checkout.com. How is this different from Checkout.com's payment links API? Checkout.com's API requires developers to create each link programmatically. Shuttle provides a no-code dashboard so anyone on your team can create and send links. Will customers see Shuttle? No. The checkout page is fully white-labelled with your brand. Can my whole team use it? Yes. Each user gets their own login. You can control permissions and track who sent which links. Add no-code payment links to your Checkout.com account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### How to Connect Checkout.com to Twilio for Voice & IVR Payments ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Payment Links for Hotels & Holiday Accommodation: The Complete Guide ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add no-code payment links to your Checkout.com account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideHow to Connect Checkout.com to Twilio for Voice & IVR Payments→](/guides/checkout-com-twilio-integration/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuidePayment Links for Hotels & Holiday Accommodation: The Complete Guide→](/guides/payment-links-for-hotels/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-cybersource/ --- # Payment Links for Cybersource: Send Branded Checkout Links Without Writing Code | Shuttle > Add branded payment links to your Cybersource account. Send checkout links via SMS, email, or chat -- keep your existing Cybersource setup. # Payment Links for Cybersource: Send Branded Checkout Links Without Writing Code By Shuttle, February 19, 2026 Add branded payment links to your Cybersource account. Send checkout links via SMS, email, or chat -- keep your existing Cybersource setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Cybersource Doesn't Do Payment Links Well Cybersource, owned by Visa, is one of the most established payment gateways in the world. It powers enterprise e-commerce with APIs for payment processing, fraud management, and tokenisation. But Cybersource is built for developers. Every payment capability requires API integration, and there is no simple merchant-facing tool for creating and sending payment links. If you're a business that needs to email a customer a link to pay an invoice, Cybersource expects you to build that capability yourself -- or hire someone who can. ## How Shuttle Payment Links Work with Cybersource You don't need to replace Cybersource. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Cybersource doesn't offer natively. - Sign up for Shuttle -- no developer required. Set up your branding in the dashboard in minutes. - Create a payment link: enter the amount, add a description or invoice reference, and choose an expiry date if needed. - Send the link however you want -- email, SMS, chat, social media, or generate a QR code. - Your customer clicks the link and pays on a secure, branded checkout page. No Cybersource integration needed on their end. - View the payment in your Shuttle dashboard. Your existing Cybersource API integrations for e-commerce continue running separately. Your Cybersource processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Cybersource-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Cybersource card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Cybersource reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Cybersource? - Enterprise finance teams -- collecting outstanding invoice payments from clients without routing everything through the e-commerce checkout built on Cybersource. - Customer support departments -- sending payment links during or after support calls to collect charges, fees, or replacement order payments. - Sales teams -- sending payment links for proposals, quotes, or deposits without waiting for engineering to build a checkout flow. - Non-profit organisations -- collecting donations via shareable links on social media, email campaigns, or at events without complex integrations. - Government and public sector -- sending citizens payment links for permits, fees, fines, or service charges that don't fit into existing online portals. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Cybersource required because Shuttle processes payment link transactions independently. If you're currently using Cybersource and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Cybersource to use Shuttle payment links? No. Shuttle runs alongside Cybersource. You keep your existing Cybersource setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Do I need my IT team or developers to set up Shuttle? No. Shuttle is a no-code platform. You can create an account, configure your branding, and start sending payment links within minutes -- no API integration, no developer time required. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-ecommpay/ --- # Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections | Shuttle > Add branded payment links to your Ecommpay account. Send checkout links via SMS, email, or chat -- keep your existing Ecommpay setup. # Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections By Shuttle, February 19, 2026 Add branded payment links to your Ecommpay account. Send checkout links via SMS, email, or chat -- keep your existing Ecommpay setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Ecommpay Doesn't Do Payment Links Well Ecommpay is a European payment platform offering card acquiring, alternative payment methods, and payouts to merchants across the EU and UK. Their focus is on integrated e-commerce checkout and API-driven payment flows. But if you need to send a simple branded payment link to a customer -- for an invoice, a deposit, or a one-off charge -- Ecommpay doesn't provide a self-serve payment link creation tool. European merchants are left building custom solutions or using separate invoicing software that doesn't integrate cleanly. ## How Shuttle Payment Links Work with Ecommpay You don't need to replace Ecommpay. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Ecommpay doesn't offer natively. - Create your Shuttle account and set up your branded checkout -- your logo, brand colours, and business details. - From the dashboard, create a payment link with the amount, currency (EUR, GBP, or others), and a customer-facing description. - Send the link via email, SMS, WhatsApp, or copy it into any communication channel you use with customers. - Your customer clicks the link, sees your branded checkout page, and pays with their preferred card or payment method. - Payment confirmation appears in Shuttle immediately. Your Ecommpay-processed e-commerce transactions are unaffected. Your Ecommpay processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Ecommpay-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Ecommpay card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Ecommpay reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Ecommpay? - European e-commerce merchants -- collecting additional payments, order adjustments, or custom order deposits outside their standard checkout flow. - Travel and tourism businesses -- sending payment links for booking deposits, trip add-ons, or balance payments to travellers across Europe. - B2B companies -- collecting invoice payments from European business customers who prefer paying by card link rather than bank transfer. - Subscription services -- sending one-off payment links for failed renewal charges or account upgrades outside the regular billing cycle. - Marketplace operators -- collecting fees, deposits, or verification payments from sellers or service providers on their platform. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Ecommpay required because Shuttle processes payment link transactions independently. If you're currently using Ecommpay and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Ecommpay to use Shuttle payment links? No. Shuttle runs alongside Ecommpay. You keep your existing Ecommpay setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Does Shuttle support European payment methods and currencies? Yes. Shuttle supports EUR, GBP, and other European currencies. Customers can pay with Visa, Mastercard, and other major card networks. Regional payment methods may also be available depending on your market. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-fat-zebra/ --- # Payment Links for Fat Zebra: Send Branded Checkout Links for Australian Merchants | Shuttle > Add branded payment links to your Fat Zebra account. Send checkout links via SMS, email, or chat -- keep your existing Fat Zebra setup. # Payment Links for Fat Zebra: Send Branded Checkout Links for Australian Merchants By Shuttle, January 13, 2026 Add branded payment links to your Fat Zebra account. Send checkout links via SMS, email, or chat -- keep your existing Fat Zebra setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Fat Zebra Doesn't Offer Shareable Payment Links Fat Zebra is a solid Australian payment gateway -- reliable card processing, good local acquiring relationships, and decent developer tools. But if you're a merchant who needs to send a customer a payment link for an invoice, deposit, or one-off charge, Fat Zebra doesn't have a native solution. You're stuck sending manual bank transfer details, using a separate invoicing tool, or asking customers to pay via BPAY -- none of which give you a branded, instant checkout experience. ## How Shuttle Payment Links Work with Fat Zebra Shuttle connects to your Fat Zebra gateway account and gives you a payment link layer on top. Transactions still process through Fat Zebra and settle to your existing Australian bank account. - Connect your Fat Zebra gateway credentials to Shuttle (API key setup takes minutes). - Create a payment link -- set the amount in AUD, add your branding, and configure accepted payment methods. - Send the link to your customer via SMS, email, or any messaging app popular in Australia. - Your customer taps the link, sees a branded checkout page, and pays by card or digital wallet. - The payment processes through Fat Zebra. You see it in Shuttle's dashboard and your Fat Zebra reporting. Your Fat Zebra gateway agreement, processing rates, and settlement schedule remain unchanged. Shuttle adds a new capability without disrupting anything. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Fat Zebra reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Fat Zebra? - Professional services firms -- send payment links for consulting invoices, legal retainers, and accounting fees. - Trades and home services -- collect deposits and final payments for plumbing, electrical, and renovation work. - Property managers -- send rent payment links and collect bond payments without manual bank transfers. - Australian ecommerce brands -- offer payment links for phone orders, social media sales, and custom quotes. - Not-for-profits -- collect donations via shareable links without building a full donation page. ## Getting Started Shuttle charges a small per-transaction fee on top of your Fat Zebra processing rates. No monthly fees, no lock-in contracts, and no setup costs. Setup takes less than a day. Connect your Fat Zebra API credentials, upload your logo, and you're ready to send your first payment link. You just need an active Fat Zebra merchant account. Shuttle provides everything else -- hosted checkout pages, link generation, multi-channel sending, and reporting. ## Frequently Asked Questions ### Does this work with Australian bank accounts? Yes. Shuttle processes through your existing Fat Zebra account, so funds settle to your current Australian bank account on your existing schedule. ### Can I accept payment methods other than cards? Yes. Depending on your Fat Zebra configuration, you can accept Visa, Mastercard, American Express, and digital wallets like Apple Pay and Google Pay through Shuttle payment links. ### Do I need developer resources to set this up? No. Shuttle provides a no-code dashboard where you create and send payment links. No development work required -- it's designed for operations and finance teams. ### Is this a replacement for BPAY? It's a modern alternative. Instead of giving customers a BPAY reference and waiting days for reconciliation, you send an instant payment link that settles in real time with automatic reconciliation. ## Related Reading Explore More ### How to Connect Fat Zebra to Twilio for Voice & IVR Payments ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideHow to Connect Fat Zebra to Twilio for Voice & IVR Payments→](/guides/fat-zebra-twilio-integration/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-fortis/ --- # Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations | Shuttle > Add branded payment links to your Fortis account. Send checkout links via SMS, email, or chat -- keep your existing Fortis setup. No migration required. # Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations By Shuttle, February 19, 2026 Add branded payment links to your Fortis account. Send checkout links via SMS, email, or chat -- keep your existing Fortis setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Fortis Doesn't Do Payment Links Well Fortis, formerly known as Payline Data, is a payment technology company focused on providing APIs, SDKs, and integrations for software platforms and merchants in the United States. Their developer-first approach means powerful capabilities for integrated payments, but for merchants who simply need to generate a payment link and send it to a customer, Fortis doesn't offer a straightforward no-code solution. You either build something custom through their API or you go without payment links entirely. ## How Shuttle Payment Links Work with Fortis You don't need to replace Fortis. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Fortis doesn't offer natively. - Sign up for Shuttle and add your business branding -- logo, colours, and company name for your checkout pages. - Open the Shuttle dashboard and click to create a new payment link. Enter the amount, a description, and an optional customer reference. - Copy the generated link or send it directly via email or SMS from within Shuttle. - Your customer receives the link, taps it on any device, and completes payment on your branded checkout page. - Track the payment in real time on your Shuttle dashboard. Your Fortis-processed transactions continue separately as normal. Your Fortis processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Fortis-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Fortis card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Fortis reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Fortis? - Software platforms -- that embed Fortis for in-app payments but need a way to send standalone payment links to end users for one-off charges. - Medical and dental practices -- collecting patient balances, copays, or payment plan instalments without requiring patients to call or visit. - Field service businesses -- sending payment links after completing jobs -- plumbing, HVAC, landscaping -- so customers can pay immediately from their phone. - Property managers -- collecting rent, maintenance fees, or security deposits from tenants via text or email payment links. - Membership organisations -- sending dues renewal links or event registration payment links to members via email campaigns. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Fortis required because Shuttle processes payment link transactions independently. If you're currently using Fortis and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Fortis to use Shuttle payment links? No. Shuttle runs alongside Fortis. You keep your existing Fortis setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### I use Fortis through a software platform -- can I still use Shuttle? Yes. Shuttle is independent of your Fortis integration. Even if Fortis is embedded in your software for standard transactions, you can use Shuttle alongside it for payment link scenarios that your platform doesn't support. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-freedompay/ --- # Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments | Shuttle > Add branded payment links to your FreedomPay account. Send checkout links via SMS, email, or chat -- keep your existing FreedomPay setup. # Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments By Shuttle, February 19, 2026 Add branded payment links to your FreedomPay account. Send checkout links via SMS, email, or chat -- keep your existing FreedomPay setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: FreedomPay Doesn't Do Payment Links Well FreedomPay is a leading enterprise commerce platform built for hospitality, retail, and food service. Their technology powers POS systems in hotels, stadiums, restaurants, and retail chains across North America and Europe. But FreedomPay is designed for in-person, on-premise transactions. When merchants need to collect a payment remotely -- sending a link for a deposit, a no-show charge, or an advance booking fee -- there's no native FreedomPay payment link product. This forces businesses to use manual processes or bolt on unrelated tools. ## How Shuttle Payment Links Work with FreedomPay You don't need to replace FreedomPay. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that FreedomPay doesn't offer natively. - Set up your Shuttle account with your business branding -- this takes about five minutes. - Create a payment link from the dashboard: set the amount, add a description like "Booking deposit" or "Event fee", and optionally pre-fill customer details. - Send the link to your customer via email, SMS, or embed it in a booking confirmation message. - The customer clicks the link on their phone or computer, sees your branded checkout, and pays securely. - Payment confirmation appears in Shuttle instantly. You can reconcile this alongside your FreedomPay POS transactions. Your FreedomPay processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with FreedomPay-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard FreedomPay card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your FreedomPay reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with FreedomPay? - Hotels and resorts -- collecting booking deposits, no-show fees, minibar charges, or event space reservations from guests before or after their stay. - Stadiums and event venues -- sending payment links for premium seating upgrades, catering deposits, or corporate hospitality packages. - Restaurants and catering companies -- collecting deposits for large party bookings, private dining events, or catering orders. - Retail chains -- sending payment links for special orders, custom items, or layaway balances that can't be processed at the POS. - Parking and transportation services -- collecting fees, fines, or reservations via payment links sent to drivers or fleet managers. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with FreedomPay required because Shuttle processes payment link transactions independently. If you're currently using FreedomPay and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave FreedomPay to use Shuttle payment links? No. Shuttle runs alongside FreedomPay. You keep your existing FreedomPay setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Can I send payment links for hotel no-show charges? Yes. You can create a payment link with the no-show fee amount and send it to the guest via email. The guest pays through the branded checkout, and you have a clear record of the charge and payment. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-global-payments/ --- # Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources | Shuttle > Add branded payment links to your Global Payments account. Send checkout links via SMS, email, or chat -- keep your existing Global Payments setup. # Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources By Shuttle, February 19, 2026 Add branded payment links to your Global Payments account. Send checkout links via SMS, email, or chat -- keep your existing Global Payments setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Global Payments Doesn't Do Payment Links Well Global Payments is one of the largest payment technology companies in the world, serving millions of merchants with POS systems, e-commerce gateways, and enterprise payment solutions. However, their focus is on integrated processing -- terminals, online checkouts, and API-driven solutions. If you simply need to send a customer a payment link via email or SMS, Global Payments doesn't offer a straightforward self-serve tool for that. Merchants end up asking developers to build custom solutions or using workarounds that don't match their brand. ## How Shuttle Payment Links Work with Global Payments You don't need to replace Global Payments. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Global Payments doesn't offer natively. - Create your Shuttle account and configure your checkout branding to match your existing Global Payments merchant experience. - In the Shuttle dashboard, create a new payment link with the amount, description, and any reference number you use. - Share the link with your customer -- copy it, email it, text it, or generate a QR code for in-person use. - Your customer clicks through to a branded checkout page, enters their card details, and completes payment. - The transaction appears in your Shuttle dashboard immediately. Your Global Payments processing for other channels continues unchanged. Your Global Payments processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Global Payments-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Global Payments card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Global Payments reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Global Payments? - Enterprise accounts receivable teams -- sending payment collection links for outstanding invoices instead of waiting for cheques or wire transfers. - Hospitality businesses -- collecting deposits, no-show fees, or room upgrade charges from guests who aren't on-site. - B2B suppliers -- sending payment links for purchase orders, making it easier for buyers to pay by card instead of managing bank transfers. - Healthcare providers -- collecting patient balances, co-pays, or elective procedure deposits via secure payment links. - Professional services firms -- collecting retainers, project deposits, or final invoices from clients without building a full e-commerce checkout. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Global Payments required because Shuttle processes payment link transactions independently. If you're currently using Global Payments and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Global Payments to use Shuttle payment links? No. Shuttle runs alongside Global Payments. You keep your existing Global Payments setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Will Shuttle payment links affect my Global Payments merchant account? No. Shuttle operates independently from Global Payments. Your existing merchant account, terminals, and integrations are completely unaffected. Shuttle gives you an additional payment collection channel. ## Related Reading Explore More ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### How to Connect Global Payments to Twilio for Voice & IVR Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuideHow to Connect Global Payments to Twilio for Voice & IVR Payments→](/guides/global-payments-twilio-integration/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-gocardless/ --- # Payment Links for GoCardless: Add Card Payment Links to Your GoCardless Setup | Shuttle > Add one-off card payment links alongside your GoCardless direct debits. Collect deposits, ad-hoc charges, and balance payments by card. # Payment Links for GoCardless: Add Card Payment Links to Your GoCardless Setup By Nick Dunse, January 14, 2026 Add one-off card payment links alongside your GoCardless direct debits. Collect deposits, ad-hoc charges, and balance payments by card. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem GoCardless is the leading platform for direct debit payments. It's brilliant at what it does -- recurring billing, subscription management, and bank-to-bank payments. If you collect regular payments from customers, GoCardless is hard to beat. But direct debit is only part of the picture. Almost every GoCardless merchant has situations where they need a one-off card payment. A deposit before setting up a direct debit. An ad-hoc invoice for additional work. A change fee or cancellation charge. A balance payment that doesn't fit the recurring schedule. GoCardless doesn't do card payments. That's not what it's built for. So merchants end up asking for bank transfers (slow, manual reconciliation), using a completely separate payment provider (fragmented reporting), or worst of all -- just not collecting the payment at all. Shuttle bridges this gap. It lets GoCardless merchants send card payment links for one-off transactions -- alongside their existing direct debit setup. ## How Payment Links Work with GoCardless Shuttle doesn't replace GoCardless -- it complements it. GoCardless continues to handle your recurring direct debit payments. Shuttle adds card payment links for everything else. You connect a card payment account (through any of Shuttle's supported PSPs) and use the Shuttle dashboard to create one-off payment links. Send them via SMS, email, or chat. The customer pays by card on a branded checkout page. Your direct debit collections stay in GoCardless. Your one-off card payments go through Shuttle. One dashboard for your team. Two payment methods for your customers. - Connect a card payment account to Shuttle (Stripe, Worldpay, Adyen, or others). - Create a payment link for the one-off charge -- amount, reference, and expiry. - Brand the checkout page to match your business. - Send the link via SMS, email, or chat. - Customer pays by card. You continue using GoCardless for recurring payments. ## What You Get - Card payments alongside direct debit: Collect one-off payments that GoCardless can't handle. - Branded checkout: Professional payment pages that match your business identity. - SMS and email delivery: Send payment links instantly -- no manual bank transfer requests. - Faster collection: Card payments settle in days, not the 5+ business days of direct debit. - No new provider complexity: Shuttle connects to any major PSP. Your GoCardless setup stays untouched. - Deposit collection: Take a card deposit before setting up the direct debit mandate. - Link tracking: See when links are sent, opened, and paid -- in real time. ## Who Uses This - Membership organisations collecting joining fees by card before setting up monthly direct debits. - Utilities and telecoms taking one-off charges for installation, equipment, or early termination. - Property management companies collecting deposits and ad-hoc maintenance charges. - Gyms and fitness studios taking sign-up fees by card with ongoing membership via GoCardless. - Accountants and bookkeepers collecting one-off project fees alongside regular retainer payments. ## Pricing and Setup Shuttle Payment Links costs $49 per month. Card processing rates depend on the PSP you connect (Stripe, Worldpay, Adyen, etc.). Setup is simple. Connect a card payment account, brand your checkout page, and start sending links. GoCardless continues to run your direct debits unchanged. ## FAQ Do I need to leave GoCardless? Absolutely not. GoCardless keeps handling your direct debits. Shuttle adds card payment links for the one-off transactions GoCardless doesn't cover. Which card processor do I need? Shuttle supports Stripe, Worldpay, Adyen, Braintree, Square, Checkout.com, and others. Use whichever you prefer -- or already have. Will customers see Shuttle? No. The checkout page shows your brand only. Fully white-labelled. Can I send links to existing GoCardless customers? Yes. You can send a card payment link to anyone -- existing GoCardless customers or new contacts. Add card payment links to your GoCardless setup -- without changing your direct debit provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add card payment links to your GoCardless setup](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-instagram-sales/ --- # Does Instagram Require Linking an Email to Receive Payments? (No -- Here's How in 2026) | Shuttle > No -- Instagram does not require linking an email to receive payments. Use payment links to get paid from posts, DMs, Stories and bios in 2026 -- no... # Does Instagram Require Linking an Email to Receive Payments? (No -- Here's How in 2026) By Nick Dunse, January 3, 2026 No -- Instagram does not require linking an email to receive payments. Use payment links to get paid from posts, DMs, Stories and bios in 2026 -- no... Start sending payment links today Accept payments from Instagram DMs, comments, and stories -- no website needed. Just send a link. Instagram has evolved from a photo-sharing app into one of the most powerful sales channels for businesses of every size. With over 2 billion monthly active users and more than 200 million business accounts, the platform now drives real revenue -- but accepting payments on Instagram is not always straightforward. Whether you sell physical products, digital goods, services, or subscriptions, you need a reliable Instagram payment system that works for your customers and your business model. This guide covers every method available in 2026 -- from Instagram's native checkout and Instagram Shop to payment links, third-party gateways, and invoicing tools -- so you can choose the right approach and start collecting payments through Instagram today. ## How Instagram Payments Work Instagram does not function as a standalone payment processor. Instead, it provides several tools and integrations that let businesses collect money from customers directly through the app or by redirecting them to an external checkout page. The Instagram payment method you choose depends on what you sell, where your customers are, and how much control you want over the transaction. There are three broad categories of Instagram payment systems: - In-app checkout: Customers complete the purchase without leaving Instagram. This includes Instagram Checkout (for eligible US businesses) and the built-in payment system for Instagram Shop. - Payment links: You share a hosted checkout link in your bio, Stories, DMs, or captions. The customer taps the link, lands on a payment page, and pays with card, Apple Pay, Google Pay, or other methods. - External checkout: You drive traffic to your own website or e-commerce store where you handle payments through a third-party payment gateway. Each approach has trade-offs around conversion rates, fees, customer data ownership, and geographic availability. We will break down each option in detail below. ## Instagram Checkout and Instagram Shop Instagram Checkout is Meta's native in-app purchasing feature. When a customer sees a product tagged in a post, Reel, or Story, they can tap it, select options like size or colour, and complete the purchase entirely within the Instagram app. No redirect, no external website required. ### How Instagram Checkout Works To use Instagram Checkout, you need an Instagram Shop -- a storefront built into your Instagram business profile. Setting up a Shop involves connecting a product catalogue (typically through Meta Commerce Manager or a platform like Shopify), verifying your business, and enabling checkout. Once approved, your products appear in a dedicated Shop tab on your profile, and they can be tagged in any content you post. When a customer buys through Instagram Checkout, Meta processes the payment, handles the transaction, and takes a selling fee. The customer's payment information is stored by Meta for future purchases, which reduces friction on repeat orders. ### Instagram Checkout Limitations - Geography: Instagram Checkout with in-app payment is currently available only to US-based businesses. Businesses in other countries can set up Instagram Shop but must redirect customers to an external website for checkout. - Product types: Instagram Checkout is designed for physical products. If you sell services, digital products, or subscriptions, you cannot use native checkout. - Customer data: Meta owns the customer relationship. You receive limited buyer information compared to processing payments through your own website or payment gateway. - Fees: Meta charges a selling fee of 5% per shipment (or a flat $0.40 for orders of $8 or less). This is on top of any costs from your e-commerce platform. For businesses outside the US, or those selling services and digital goods, Instagram Checkout is not an option -- but there are several excellent alternatives. ## Payment Links for Instagram: The Most Flexible Option Payment links are the most versatile Instagram payment method available. A payment link is a hosted checkout page with a unique URL -- you share the link, the customer clicks it, and they land on a branded page where they can pay by card, digital wallet, or bank transfer. No website, no app, no coding required. Payment links work everywhere on Instagram: - Bio link: Place your payment link (or a link-in-bio page containing multiple payment links) in your Instagram profile bio. This is the most visible and permanent placement. - Stories: Use the link sticker in Instagram Stories to share a payment link directly. Followers can tap and pay in seconds. - DMs: Send payment links in direct messages for custom orders, quotes, deposits, or one-off invoices. This is particularly effective for service-based businesses. - Captions and comments: While Instagram does not make links in captions clickable, you can include shortened payment URLs or direct followers to your bio link. - Reels: Pair a Reel showcasing your product or service with a Story or bio link pointing to your payment page. ### Best Payment Link Providers for Instagram Several payment processors offer payment link features that work well for Instagram sellers: - Stripe Payment Links -- create no-code checkout pages with custom branding. Supports subscriptions, one-time payments, and multiple currencies. Transaction fee: 2.9% + 30 cents (US cards). - PayPal -- PayPal.me links and PayPal Checkout buttons let customers pay with their PayPal balance, cards, or Pay Later options. High brand recognition reduces checkout anxiety. - Square Online Checkout -- generate shareable payment links from your Square dashboard. Good for businesses that also sell in person, since inventory syncs across channels. - SumUp -- simple payment links aimed at small businesses and sole traders. Competitive flat-rate pricing and a straightforward dashboard. If you also sell on TikTok, most of these payment link providers work across both platforms. See our guide to payment links for TikTok sales for a detailed comparison. ## Instagram Payment Gateway Options An Instagram payment gateway is any third-party payment processor you use to accept payments from Instagram traffic. While Instagram itself is not a payment gateway, it acts as the discovery and engagement layer -- you then route customers to a gateway for the actual transaction. The most common Instagram payment gateway setups include: - Shopify + Instagram Shopping: Connect your Shopify store to Instagram, tag products in posts, and route customers to your Shopify checkout. This is the most popular approach for e-commerce businesses and gives you full control over the checkout experience and customer data. - WooCommerce + Instagram: Similar to Shopify but built on WordPress. Sync your WooCommerce product catalogue with Meta Commerce Manager and tag products in Instagram content. - Stripe Checkout: Create a custom checkout page or use Stripe's hosted checkout. Ideal for businesses selling digital products, services, or subscriptions that Instagram Shop does not support. - PayPal Commerce Platform: Integrate PayPal into your website and link from Instagram. Offers buyer protection that can boost conversion rates for higher-priced items. The right Instagram payment gateway depends on your existing tech stack, the countries you sell to, and how much customisation you need over the checkout flow. ## In-App Checkout vs External Checkout: Pros and Cons One of the biggest decisions for Instagram sellers is whether to keep customers inside the app or send them to an external checkout. Here is how the two approaches compare. ### In-App Checkout Advantages - Lower friction: Customers never leave Instagram, reducing drop-off. Meta reports that in-app checkout can improve conversion by up to 30% compared to external redirects. - Stored payment info: Returning customers can buy in one or two taps since their card details are already saved with Meta. - Discovery: Products tagged in posts appear in the Instagram Shop tab and Explore, giving you additional organic reach. ### In-App Checkout Disadvantages - Limited customer data: You receive the buyer's name, email, and shipping address, but Meta controls the relationship. You cannot retarget these customers as effectively outside of Meta's ad platform. - Selling fees: The 5% per-shipment fee is higher than many standalone payment processors charge. - US only: If your business is based outside the United States, in-app checkout is not available. - Physical products only: Services, consulting, digital downloads, and subscription-based businesses cannot use Instagram Checkout. ### External Checkout Advantages - Full data ownership: You own the customer email, can build your own CRM lists, and run email marketing campaigns independently of Meta. - Lower transaction fees: Most payment gateways charge 1.5-2.9% plus a small fixed fee -- often less than Meta's 5% selling fee. - Works globally: Any business anywhere can use external checkout. - Supports all product types: Services, subscriptions, digital goods, custom orders -- anything you sell. ### External Checkout Disadvantages - Higher friction: Every redirect loses a percentage of potential buyers. The customer has to leave Instagram, wait for a page to load, and potentially enter payment information from scratch. - Requires a website or checkout page: You need somewhere to send the customer, even if it is just a hosted payment link page. For most businesses, the best approach is a combination: use Instagram Shop for product discovery and tagging, but route checkout through your own website or payment link where you control the experience and own the customer data. ## Instagram Payment Fees Compared Understanding the fees for each Instagram payment method is essential for protecting your margins. Here is a breakdown of the most common options: - Instagram Checkout (US only): 5% per shipment or a flat $0.40 fee for orders of $8.00 or less. This covers payment processing, fraud protection, and Meta's facilitation. - Stripe: 2.9% + $0.30 per transaction for US cards. International cards add 1.5%. No monthly fee. - PayPal: 3.49% + $0.49 for standard commercial transactions. PayPal.me and QR code payments may have different rates. - Square: 2.9% + $0.30 for online transactions. No monthly fee for the basic plan. - Shopify Payments: 2.9% + $0.30 on the Basic plan (lower on higher tiers). Monthly Shopify subscription required ($39+/month). For a business doing $10,000 per month in Instagram sales, the difference between Instagram Checkout's 5% fee ($500) and Stripe's ~3.2% effective rate ($320) adds up to $2,160 per year. At higher volumes, external checkout almost always wins on cost. ## How to Receive Payments on Instagram: Step-by-Step Setup Here is a practical walkthrough for setting up payments on Instagram, starting with the simplest option and working up to more advanced setups. ### Option 1: Payment Links (Quickest to Set Up) - Sign up for a payment processor (Stripe, PayPal, or Square). - Create a payment link for your product or service. Add a description, price, and any options (size, quantity, etc.). - Add the link to your Instagram bio, or use a link-in-bio tool like Linktree to host multiple payment links. - Share the link in Stories using the link sticker, and send it via DMs for custom orders. - Test the payment flow yourself before promoting it to customers. ### Option 2: Instagram Shop with External Checkout - Switch to an Instagram Business or Creator account if you have not already. - Connect your e-commerce platform (Shopify, WooCommerce, BigCommerce) to Meta Commerce Manager. - Upload or sync your product catalogue. - Submit your shop for review (typically takes 24-48 hours). - Once approved, start tagging products in your posts, Stories, and Reels. Customers who tap a product tag will be directed to your website to complete the purchase. ### Option 3: Instagram Checkout (US Businesses) - Follow the Instagram Shop setup steps above. - In Commerce Manager, enable on-platform checkout instead of external website checkout. - Provide your US bank account details and tax information. - Once approved, customers can complete purchases without leaving Instagram. ## Instagram Payment Security and Fraud Protection Security is a legitimate concern for both buyers and sellers on Instagram. The platform has had well-publicised issues with scam accounts and fake sellers, which makes it even more important to use a trusted Instagram payment system. ### For Sellers: Protecting Your Business - Use established payment processors: Stripe, PayPal, and Square all offer seller protection programs, chargeback management, and fraud detection tools. Never ask customers to send money via personal bank transfer or cryptocurrency for commercial transactions. - Enable 3D Secure: If your payment gateway supports it, enable 3D Secure (3DS) authentication. This shifts chargeback liability to the card issuer and adds an extra verification step for suspicious transactions. - Keep records: Save screenshots of DM conversations, order confirmations, and shipping tracking numbers. These are essential if a customer files a chargeback or disputes a transaction. ### For Buyers: Staying Safe - Pay through recognised platforms: If a seller asks you to pay via bank transfer, gift cards, or crypto, treat it as a red flag. Legitimate businesses use payment processors that offer buyer protection. - Check the seller's profile: Look for a verified badge, a history of posts, customer reviews, and a linked website. New accounts with no history and too-good-to-be-true prices are common scam indicators. - Use Instagram's Purchase Protection: Orders placed through Instagram Checkout are covered by Meta's Purchase Protection policy, which provides refunds for items that do not arrive or are significantly different from what was described. ## For Platforms: Embedding Payment Links for Instagram Sellers If you are building a platform or SaaS product that serves merchants who sell on Instagram -- think e-commerce tools, social commerce platforms, creator monetisation apps, or marketplace software -- there is a significant opportunity to embed payment collection directly into your product. Rather than asking your merchants to go set up their own Stripe or PayPal accounts and manually generate payment links, you can offer embedded payments as a native feature of your platform. Your merchants get branded payment links they can share on Instagram, and you control the checkout experience and keep your users inside your ecosystem. This is exactly the kind of problem a payment layer like Shuttle solves. Instead of building payment infrastructure from scratch or becoming a payment facilitator yourself, you integrate once and give every merchant on your platform the ability to generate payment links, accept cards and digital wallets, and manage their Instagram sales -- all under your brand. Learn how Shuttle works for platforms or explore the platform to see if it fits your use case. ## Tips to Increase Instagram Payment Conversions Getting someone to follow you on Instagram is one thing. Getting them to pay is another. Here are practical tips to improve your conversion rate: - Reduce steps to payment: Every additional click between discovery and checkout loses customers. Use payment links that go directly to a checkout page rather than a homepage or product listing. - Offer multiple payment methods: Accept cards, Apple Pay, Google Pay, and PayPal at minimum. Customers are more likely to complete a purchase when their preferred payment method is available. - Use urgency and scarcity: Limited-time offers, countdown stickers in Stories, and "only X left" messaging create urgency that drives faster purchasing decisions. - Show social proof: Share customer reviews, unboxing videos, and user-generated content. Real testimonials are more persuasive than any product description. - Optimise your bio link: Your bio is prime real estate. Use a clear call to action ("Shop now", "Book a session", "Get a quote") and make sure the link works on mobile. - Brand your checkout: Customers are more likely to trust a checkout page that matches your Instagram branding. Use your logo, colours, and consistent messaging on your payment link page. - Follow up in DMs: If someone enquires about a product but does not buy, send a polite follow-up DM with a direct payment link. This personal touch can recover a significant number of abandoned sales. ## Instagram Payments FAQ ### Can you accept payments directly on Instagram? Yes, but only in limited circumstances. US-based businesses selling physical products can use Instagram Checkout to accept payments within the app. Everyone else needs to use payment links or redirect customers to an external checkout page. Instagram itself is not a payment processor -- it relies on Meta's infrastructure for in-app purchases and third-party gateways for external transactions. ### What is the best payment method for Instagram sellers? For most Instagram sellers, payment links are the best option. They work globally, support all product types (physical, digital, services, subscriptions), and give you full control over the checkout experience and customer data. Stripe, PayPal, and Square all offer easy-to-create payment links. If you sell physical products in the US and want the lowest-friction checkout, Instagram Checkout is worth considering despite the higher fees. ### How much does Instagram charge for payments? Instagram Checkout charges a 5% selling fee per shipment (or $0.40 for orders under $8). If you use an external payment gateway instead, you pay that gateway's fees -- typically 2.9% + $0.30 for Stripe or Square, or 3.49% + $0.49 for PayPal. Instagram does not charge additional fees for shops that use external checkout; you only pay your payment processor. ### Is it safe to make payments through Instagram? Payments made through Instagram Checkout are protected by Meta's Purchase Protection policy, which covers items that do not arrive or are significantly different from what was advertised. For payments made through external links, your protection depends on the payment processor you use -- Stripe, PayPal, and Square all offer their own buyer and seller protection programs. The key risk on Instagram is buying from unverified sellers through informal channels like DMs with bank transfers. ### Can I sell services on Instagram? Yes, but you cannot use Instagram Shop or Instagram Checkout for services -- those features are limited to physical products. The best approach for service-based businesses (consultants, coaches, freelancers, agencies) is to use payment links. Create a payment link for each service or package you offer, share it in your bio and Stories, and send it directly to prospects via DM. Stripe and Square both let you create payment links for custom amounts, making them ideal for quotes and invoicing. ## Choosing the Right Instagram Payment System There is no single best way to accept payments on Instagram -- the right Instagram payment system depends on your business model, location, and growth plans. If you sell physical products in the US and want frictionless checkout, Instagram's native tools are a solid starting point. If you sell services, digital products, or operate outside the US, payment links give you the most flexibility with the lowest fees. Whatever approach you choose, the fundamentals are the same: make it easy for customers to pay, use a trusted payment processor, and optimise every step between discovery and checkout. Instagram is one of the highest-intent social platforms for commerce -- the businesses that win are the ones that remove friction from the payment experience. Selling through your Instagram bio, DMs, or Stories? Shuttle Links & Checkout gives you a branded, mobile-friendly payment page -- cards, Apple Pay, Google Pay, and local methods through 40+ payment providers. Drop the link into your bio, paste it in a DM, or share it in Stories. No app lock-in, no P2P transfer limits, no email-linked-account workarounds. See how it works. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Stripe](/payment-providers/stripe/) - [PayPal](/payment-providers/paypal-commerce/) - [Square](/payment-providers/square/) - [payment links for TikTok sales](/blog/payment-links-for-tiktok-sales/) - [embedded payments](/guides/what-is-embedded-payments/) - [Learn how Shuttle works for platforms](/platforms/) - [explore the platform](/discovery/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [See how it works](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-liqpay/ --- # Payment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout | Shuttle > Add branded payment links to your LiqPay account. Send checkout links via SMS, email, or chat -- keep your existing LiqPay setup. No migration required. # Payment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout By Shuttle, February 19, 2026 Add branded payment links to your LiqPay account. Send checkout links via SMS, email, or chat -- keep your existing LiqPay setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: LiqPay Doesn't Do Payment Links Well LiqPay, operated by PrivatBank, is the dominant payment platform in Ukraine and serves merchants across the CIS region. While LiqPay handles card processing and mobile payments well within its ecosystem, its payment link features are basic and lack customisation options. Merchants who need branded, multi-currency checkout links for international customers find themselves limited by LiqPay's primarily domestic focus. A dedicated payment link solution lets you extend beyond LiqPay's native capabilities without changing your core processing. ## How Shuttle Payment Links Work with LiqPay You don't need to replace LiqPay. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that LiqPay doesn't offer natively. - Sign up for Shuttle and set up your branded checkout -- upload your logo, choose your colours, and add your business name. - Create a payment link in the dashboard with the amount, currency, and a description your customer will see. - Send the link to your customer via email, SMS, Telegram, Viber, or any messaging app popular in your market. - Your customer opens the link on any device, sees your branded checkout, and pays with their preferred payment method. - You receive instant confirmation in the Shuttle dashboard and can track all payment link activity separately from your LiqPay transactions. Your LiqPay processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with LiqPay-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard LiqPay card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your LiqPay reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with LiqPay? - Ukrainian e-commerce merchants -- selling to international customers who need payment options beyond LiqPay's domestic card processing. - Freelancers and agencies -- invoicing international clients in USD or EUR while keeping LiqPay for local Ukrainian payments. - SaaS companies in the CIS region -- collecting subscription payments from global customers via branded checkout links. - Import/export businesses -- sending payment links to overseas buyers for deposits, balances, or trade invoices. - Event organisers -- selling tickets or collecting registration fees from attendees across multiple countries and currencies. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with LiqPay required because Shuttle processes payment link transactions independently. If you're currently using LiqPay and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave LiqPay to use Shuttle payment links? No. Shuttle runs alongside LiqPay. You keep your existing LiqPay setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Can I use Shuttle for international payments while keeping LiqPay for domestic ones? Absolutely. Many merchants use LiqPay for UAH domestic transactions and Shuttle payment links for international collections in USD, EUR, or other currencies. The two systems run independently. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-mollie/ --- # Payment Links for Mollie: Branded Checkout Links for Mollie Merchants | Shuttle > Enhance Mollie payment links with full branding, SMS and WhatsApp delivery, and detailed tracking. iDEAL, cards, and local methods supported. # Payment Links for Mollie: Branded Checkout Links for Mollie Merchants By Nick Dunse, January 14, 2026 Enhance Mollie payment links with full branding, SMS and WhatsApp delivery, and detailed tracking. iDEAL, cards, and local methods supported. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Mollie is one of Europe's most popular payment providers, particularly in the Netherlands and across the EU. It's known for simplicity, fair pricing, and a clean API. Many small and mid-sized businesses across Europe rely on it. Mollie does offer a basic payment links feature in its dashboard. You can create a link, get a URL, and share it. It works. But the branding is Mollie's. The delivery is manual -- you copy the URL and paste it into whatever channel you're using. Tracking is limited to paid or not paid. For businesses that send more than a handful of payment links per week, those limitations add up. No SMS sending. No ability to track opens versus completions. No brand consistency with your website. No multi-channel delivery from a single dashboard. Shuttle enhances Mollie's payment links with full branding, multi-channel delivery, and detailed tracking -- while keeping Mollie as your payment processor. ## How Payment Links Work with Mollie Shuttle connects to your Mollie account via OAuth. You authorise the connection in Mollie's dashboard, and Shuttle can create payment links that process through your account. The experience for your team is a branded dashboard where they create links, customise the checkout page, and send via SMS, email, or WhatsApp. The experience for your customer is a professional, branded checkout page with their preferred payment method. Transactions appear in your Mollie dashboard as normal. Settlement follows your existing schedule. The only difference is a better experience for your team and your customers. - Connect your Mollie account via OAuth -- two clicks to authorise. - Create a payment link in Shuttle -- set amount, description, and expiry. - Brand the checkout page with your business identity. - Send via SMS, email, or WhatsApp directly from the dashboard. - Customer pays using iDEAL, cards, Bancontact, or other enabled methods. Settlement through Mollie. ## What You Get - Full branding: Your checkout page looks like your business -- not Mollie's default. - SMS and WhatsApp delivery: Send payment links through channels Mollie's native links don't support. - Detailed tracking: Sent, opened, viewed, paid, expired -- full lifecycle visibility. - European payment methods: iDEAL, Bancontact, SOFORT, cards, and every method you've enabled in Mollie. - Multi-language support: Serve Dutch, German, French, and English-speaking customers in their language. - Partial payments: Collect deposits and send follow-up links for the balance. - Multi-PSP option: Use Mollie for EU payments and another PSP for other regions -- same dashboard. ## Who Uses This - Dutch SMEs sending payment links via iDEAL for invoices and services. - E-commerce businesses handling phone orders and manual payments alongside their webshop. - Professional services attaching payment links to email invoices for instant collection. - Subscription businesses recovering failed payments with a simple link. - Multi-country businesses serving customers across the EU with local payment methods. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No transaction surcharges beyond your Mollie rates. Connect your Mollie account in under a minute. Start sending branded payment links the same day. No integration work required. ## FAQ Do I need to leave Mollie? No. Shuttle sits on top of your Mollie account. Everything stays the same -- your rates, your payment methods, your settlement. How is this better than Mollie's built-in links? Full branding, SMS and WhatsApp delivery, detailed open/view/paid tracking, and the ability to combine Mollie with other PSPs in one dashboard. Can customers pay with iDEAL? Yes. Every payment method enabled in your Mollie account is available on the checkout page -- including iDEAL. Will my customers see Shuttle branding? No. Fully white-labelled. Your brand only. Add branded payment links to your Mollie account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add branded payment links to your Mollie account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-moneris/ --- # Moneris Payment Links: Features, Setup & Alternatives (2026) | Shuttle > How to set up Moneris payment links, what they cost, supported features, and how they compare to multi-PSP alternatives. # Moneris Payment Links: Features, Setup & Alternatives (2026) By Shuttle, February 19, 2026 How to set up Moneris payment links, what they cost, supported features, and how they compare to multi-PSP alternatives. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Moneris Doesn't Do Payment Links Well Moneris is the largest payment processor in Canada, trusted by hundreds of thousands of merchants for in-store and online transactions. But when it comes to sending a customer a simple payment link -- a branded URL they can click and pay -- Moneris options are limited to basic virtual terminal functionality. Canadian merchants who want to collect payments via email, SMS, or chat need a purpose-built payment link tool that works alongside their Moneris account without replacing it. ## How Shuttle Payment Links Work with Moneris You don't need to replace Moneris. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Moneris doesn't offer natively. - Create your Shuttle account and configure your branding -- logo, colours, and business details. - Build a payment link in the Shuttle dashboard by entering the amount, description, and optional customer reference. - Choose your delivery method: copy the link manually, or send it directly via email or SMS from Shuttle. - Your customer clicks the link, lands on your branded checkout page, and pays with their preferred card. - Payment is confirmed instantly. You see it in your Shuttle dashboard and can reconcile alongside your Moneris transactions. Your Moneris processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Moneris-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Moneris card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Moneris reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Moneris? - Canadian retail businesses -- collecting deposits or balances for custom orders, layaways, and special requests that happen outside the POS terminal. - Service providers -- like contractors, consultants, and agencies invoicing Canadian clients who want a quick way to pay without mailing cheques. - Property management companies -- sending monthly rent or maintenance fee collection links to tenants across Canada. - Healthcare and dental practices -- collecting patient copays, outstanding balances, or consultation fees remotely. - Non-profits and membership organisations -- collecting donations, dues, or event fees from supporters via email or social media. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Moneris required because Shuttle processes payment link transactions independently. If you're currently using Moneris and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Moneris to use Shuttle payment links? No. Shuttle runs alongside Moneris. You keep your existing Moneris setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Does Shuttle support Canadian dollars and Canadian cards? Yes. Shuttle supports CAD transactions and accepts all major Canadian-issued cards. Your customers pay in the currency they expect, and you receive settlement in Canadian dollars. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-nmi/ --- # Payment Links for NMI: Send Branded Checkout Links for ISOs, Resellers, and Merchants | Shuttle > Add branded payment links to your NMI account. Send checkout links via SMS, email, or chat -- keep your existing NMI setup. No migration required. # Payment Links for NMI: Send Branded Checkout Links for ISOs, Resellers, and Merchants By Shuttle, January 15, 2026 Add branded payment links to your NMI account. Send checkout links via SMS, email, or chat -- keep your existing NMI setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: NMI's Payment Link Capability Is Basic or Non-Existent NMI is the gateway infrastructure behind hundreds of ISOs, resellers, and payment companies across the US. It's powerful under the hood -- flexible APIs, multi-processor support, and solid tokenisation. But the merchant-facing experience is bare-bones. NMI doesn't offer a polished, branded payment link feature that merchants can use without developer help. ISOs end up losing merchants to competitors like Square who offer simple payment links out of the box, even though NMI's processing capabilities are far superior. ## How Shuttle Payment Links Work with NMI Shuttle connects to your NMI gateway and gives every merchant on your portfolio a branded payment link tool -- no development work required. Transactions still process through NMI. - Connect your NMI gateway credentials to Shuttle (works with any NMI-powered reseller or ISO). - Create a payment link -- set the amount, apply merchant branding, and configure accepted payment methods. - Share the link with customers via SMS, email, WhatsApp, or embed it on a website. - The customer clicks the link, sees a branded checkout page, and pays securely. - The payment processes through NMI on the merchant's existing processing setup. Track everything in Shuttle's dashboard. NMI remains your gateway. Your processing relationships, rates, and settlement are unaffected. Shuttle simply adds a modern payment link front-end. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your NMI reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with NMI? - ISOs and resellers -- offer branded payment links as a value-add to your merchant portfolio without building the feature yourself. - B2B merchants on NMI -- send payment links for invoices instead of chasing checks or taking card numbers over the phone. - Service businesses -- collect deposits, appointment fees, and final payments via text message. - SaaS platforms using NMI -- give your sub-merchants a self-serve payment link tool branded to your platform. - Ecommerce merchants -- handle phone orders, social media sales, and custom quotes with shareable payment links. ## Getting Started Shuttle charges a per-transaction fee. For individual merchants, there are no monthly fees or setup costs. ISOs and resellers can access volume pricing for their portfolios. Merchants go live in minutes. Connect NMI gateway credentials, add branding, and start sending payment links -- no integration work needed. You need an active NMI gateway account (through any ISO or reseller). Shuttle provides the payment link layer -- branded checkout, link sharing, analytics, and reporting. ## Frequently Asked Questions ### Does this work with any NMI-powered gateway? Yes. Shuttle connects to NMI regardless of which ISO, reseller, or payment company provides your gateway. If it runs on NMI, Shuttle can add payment links. ### Can ISOs white-label this for their merchants? Yes. Shuttle supports white-labelling, so ISOs and resellers can offer branded payment links as part of their merchant package without building the feature in-house. ### Do I need developer resources? No. Shuttle provides a no-code dashboard for creating and managing payment links. Merchants can be onboarded and sending links within minutes. ### How does pricing work for ISOs with multiple merchants? Shuttle offers volume-based pricing for ISOs and resellers. Contact us for portfolio pricing that scales with your merchant count. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-opayo/ --- # Payment Links for Opayo: Send Branded Checkout Links for UK Merchants | Shuttle > Add branded payment links to your Opayo account. Send checkout links via SMS, email, or chat -- keep your existing Opayo setup. No migration required. # Payment Links for Opayo: Send Branded Checkout Links for UK Merchants By Shuttle, January 16, 2026 Add branded payment links to your Opayo account. Send checkout links via SMS, email, or chat -- keep your existing Opayo setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Opayo Doesn't Have a Payment Link Feature Opayo (formerly Sage Pay) is one of the most trusted payment gateways in the UK. It powers ecommerce checkouts and virtual terminals for thousands of British businesses. But Opayo was designed for traditional card processing -- integrated ecommerce checkout and manual virtual terminal keying. If you need to send a customer a payment link via text or email, Opayo doesn't offer that. Merchants are left taking card numbers over the phone or directing customers to a payment page that requires developer integration. ## How Shuttle Payment Links Work with Opayo Shuttle connects to your Opayo gateway and gives you a self-serve payment link tool. Transactions still process through Opayo -- Shuttle just provides the customer-facing branded checkout. - Connect your Opayo gateway credentials to Shuttle. - Create a payment link in GBP -- add your branding, set the amount, and choose which card types to accept. - Send the link via SMS, email, WhatsApp, or share it on your website. - Your customer clicks the link, lands on a branded checkout page with 3D Secure, and pays instantly. - The payment processes through Opayo. View it in Shuttle's dashboard and your Opayo reporting. Your Opayo gateway agreement, processing rates, and settlement schedule are completely unchanged. Shuttle adds payment links without disrupting your existing setup. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Opayo reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Opayo? - UK ecommerce merchants -- send payment links for phone orders, returns credits, and manual adjustments without the virtual terminal. - Trades and home services -- text a payment link to customers for plumbing, electrical, and building work. - B2B companies -- replace 'pay by bank transfer' with instant payment links on invoices. - Membership organisations -- collect annual fees, event tickets, and donations via shareable links. - Professional services -- send payment links for consulting sessions, legal fees, and accounting retainers. ## Getting Started Shuttle charges a small per-transaction fee on top of your Opayo gateway rates. No monthly fees, no setup costs, and no minimum transaction volumes. Most UK merchants are live within a day. Connect your Opayo gateway credentials, add your branding, and start sending payment links to customers. All you need is an active Opayo (Sage Pay) gateway account. Shuttle provides the payment link infrastructure -- branded checkout, link management, and transaction reporting. ## Frequently Asked Questions ### Do I need to leave Opayo? No. Shuttle works on top of your existing Opayo gateway. All transactions process through Opayo, settle to your bank account on your existing schedule, and appear in your Opayo reports. ### Does this support 3D Secure? Yes. Shuttle's hosted checkout pages fully support 3D Secure authentication, meeting UK Strong Customer Authentication (SCA) requirements under PSD2. ### Can I send links via SMS to UK mobile numbers? Yes. Shuttle generates shareable links that work via SMS, email, WhatsApp, and any other channel. SMS is especially effective for UK service businesses collecting payments from customers. ### Is Sage Pay the same as Opayo? Yes. Opayo is the rebranded name for Sage Pay (now part of Elavon). If you're using Sage Pay or Opayo, Shuttle works with your gateway credentials. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-paypal/ --- # Payment Links for PayPal: Send Professional Payment Links Through PayPal | Shuttle > Replace PayPal.me with branded payment links on your PayPal Commerce account. Accept cards without a PayPal account. # Payment Links for PayPal: Send Professional Payment Links Through PayPal By Nick Dunse, January 16, 2026 Replace PayPal.me with branded payment links on your PayPal Commerce account. Accept cards without a PayPal account. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem PayPal is everywhere. It's the payment method millions of consumers trust. And PayPal.me links offer a quick way to request money -- share a URL, the customer pays via PayPal. But PayPal.me links are extremely limited. The checkout page is a PayPal page. Your brand doesn't appear. The customer must have a PayPal account or create one -- there's no option to just pay by card. There's no tracking beyond "paid" or "not paid". And the experience feels personal, not professional. For businesses that use PayPal Commerce as their payment provider, this is frustrating. PayPal has the infrastructure for card payments, alternative methods, and proper checkout flows. But their payment link product hasn't kept up. Shuttle connects to your PayPal Commerce account and gives you professional, branded payment links that accept cards, PayPal, and other methods -- with full tracking and multi-channel delivery. ## How Payment Links Work with PayPal Shuttle connects to your PayPal Commerce account via OAuth. This means your PayPal account handles processing and settlement, while Shuttle provides the branded checkout, delivery, and tracking layer. When a customer receives your payment link, they see your brand -- not PayPal's. They can pay by card even if they don't have a PayPal account. And if they want to use PayPal, that's available too. Every transaction settles to your PayPal account. You can withdraw to your bank account on your normal schedule. Nothing changes on the PayPal side. - Connect your PayPal Commerce account via OAuth. - Create a payment link in the Shuttle dashboard -- set amount, currency, and reference. - Brand the checkout page with your logo, colours, and business details. - Send the link via SMS, email, or chat. - Customer pays by card or PayPal. Funds go to your PayPal Commerce account. ## What You Get - Your brand, not PayPal's: Professional checkout pages that show your business -- not PayPal's logo and layout. - Card payments without PayPal: Customers can pay by card even if they don't have a PayPal account. - Multi-channel sending: SMS, email, and chat -- send links through whatever channel works. - Link tracking: Sent, opened, viewed, paid, expired -- not just PayPal's binary paid/unpaid status. - Professional appearance: No more PayPal.me links that look like you're a sole trader asking for a Venmo transfer. - Deposits and partial payments: Collect deposits, split payments, or take balances -- all via link. - Dashboard management: Create, send, and track all payment links in one place. ## Who Uses This - Small businesses that use PayPal but want professional payment links that don't scream "PayPal". - E-commerce sellers taking custom orders or deposits that need a payment link rather than a cart checkout. - Freelancers and agencies that want branded invoicing links instead of PayPal.me. - Service businesses collecting payments from clients who may not have PayPal accounts. - International businesses using PayPal's global reach but wanting a more professional payment experience. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No fees on top of your existing PayPal Commerce rates. Connect via OAuth in under a minute. Brand your checkout page. Send your first professional payment link today. ## FAQ Do I need to leave PayPal? No. Shuttle processes through your PayPal Commerce account. Your rates, balance, and PayPal features stay the same. Can customers pay without a PayPal account? Yes. The checkout page accepts card payments from anyone -- no PayPal account required. PayPal is also offered as a payment option. Is this better than PayPal.me? Significantly. Branded checkout, card payments for non-PayPal users, multi-channel delivery, detailed tracking, and professional appearance. Will customers see Shuttle branding? No. Fully white-labelled with your brand. Send professional payment links through your PayPal account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Send professional payment links through your PayPal account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-paysafe/ --- # Payment Links for Paysafe: Send Branded Checkout Links via Paysafe | Shuttle > Add branded payment links to your Paysafe account. Send via SMS, email, or chat with a self-serve dashboard. No code required. # Payment Links for Paysafe: Send Branded Checkout Links via Paysafe By Nick Dunse, January 17, 2026 Add branded payment links to your Paysafe account. Send via SMS, email, or chat with a self-serve dashboard. No code required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Paysafe processes payments for merchants across 36 countries. It's a well-established provider with strong coverage in Europe, North America, and emerging markets. For merchants in regulated industries -- gambling, forex, travel -- Paysafe is often the go-to processor. But Paysafe's merchant-facing tools haven't kept pace with what businesses actually need. There's no self-serve payment links product. If a Paysafe merchant wants to send a customer a link to pay, there's no built-in way to do it. The options are limited: process the payment through an e-commerce integration, use the virtual terminal and key in card numbers manually, or ask for a bank transfer. None of these is practical when you need to SMS a payment link to a customer in the next 30 seconds. Shuttle connects to your Paysafe account and adds branded payment links. Your team can create and send links from a dashboard. Customers pay on a branded checkout page. Transactions process through Paysafe. ## How Payment Links Work with Paysafe Shuttle connects to your Paysafe account using your API keys. Once connected, your team can create branded payment links from the Shuttle dashboard without any developer involvement. Each link generates a checkout page branded to your business. You send it via SMS, email, or chat. The customer pays. The transaction is processed through your Paysafe account with your existing rates and settlement terms. From Paysafe's perspective, it's a standard card-not-present transaction. Your reconciliation and reporting in Paysafe remain unchanged. - Connect your Paysafe account using your API credentials. - Create a payment link in the Shuttle dashboard -- set amount, currency, and reference. - Customise the checkout page with your brand identity. - Send the link via SMS, email, or chat. - Customer pays on the branded page. Transaction processes through Paysafe as normal. ## What You Get - Payment links for Paysafe: A capability Paysafe doesn't offer natively. - Branded checkout: Your logo, colours, and business name on every payment page. - Multi-channel delivery: SMS, email, and chat -- reach customers wherever they are. - Link tracking dashboard: Real-time visibility into link status -- sent, opened, viewed, paid, expired. - Global card acceptance: Visa, Mastercard, Amex, and local card schemes through your Paysafe account. - Deposits and partial payments: Collect deposits, balances, or split payments across links. - No code required: Operations teams create and send links without developer help. ## Who Uses This - Travel companies sending deposit and balance payment links to customers booking trips. - Gaming operators collecting verification deposits or manual top-ups via payment link. - Financial services firms sending payment links for fees, subscriptions, and one-off charges. - Professional services attaching payment links to invoices for immediate collection. - Multi-country businesses using Paysafe's global coverage with branded payment links in each market. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No additional transaction fees beyond your existing Paysafe rates. Connect your Paysafe account in minutes. Brand your checkout page. Start sending payment links the same day. No integration project. ## FAQ Do I need to leave Paysafe? No. Shuttle connects to your existing Paysafe account. Your rates, settlement, and processing all stay with Paysafe. Will my customers see Shuttle? No. The checkout page is fully white-labelled. Your brand only. What payment methods are supported? Cards (Visa, Mastercard, Amex) and any payment methods enabled on your Paysafe account. Can multiple team members use the dashboard? Yes. Each user gets their own login at $49/month. Full tracking of who sent which links. Add payment links to your Paysafe account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Add payment links to your Paysafe account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-paytomorrow/ --- # Payment Links for Paytomorrow: Send Branded Checkout Links Beyond Consumer Financing | Shuttle > Add branded payment links to your Paytomorrow account. Send checkout links via SMS, email, or chat -- keep your existing Paytomorrow setup. # Payment Links for Paytomorrow: Send Branded Checkout Links Beyond Consumer Financing By Shuttle, February 19, 2026 Add branded payment links to your Paytomorrow account. Send checkout links via SMS, email, or chat -- keep your existing Paytomorrow setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Paytomorrow Doesn't Do Payment Links Well Paytomorrow is a consumer financing and buy-now-pay-later platform that lets merchants offer instalment plans at checkout. It's designed for a specific use case: spreading large purchases over time. But merchants who use Paytomorrow for financing also need a way to collect standard card payments -- deposits, down payments, non-financed items, or amounts that don't qualify for BNPL. Paytomorrow doesn't provide standalone payment links for regular card transactions, leaving merchants without a simple way to collect these payments remotely. ## How Shuttle Payment Links Work with Paytomorrow You don't need to replace Paytomorrow. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that Paytomorrow doesn't offer natively. - Create your Shuttle account and set up your branded checkout to match your store's look and feel. - Build a payment link for any amount -- a deposit, a balance payment, or a standard card charge. - Send the link to your customer via email, text, or any messaging channel. - Your customer clicks the link, sees your branded checkout, and pays by card. No financing application needed. - The payment appears in your Shuttle dashboard. Your Paytomorrow financing offers continue working separately for qualifying purchases. Your Paytomorrow processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with Paytomorrow-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard Paytomorrow card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your Paytomorrow reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with Paytomorrow? - Furniture and mattress retailers -- collecting deposits or delivery fees by payment link while offering Paytomorrow financing for the main purchase amount. - Home improvement businesses -- sending payment links for consultation fees, material deposits, or progress payments that don't fit the BNPL model. - Medical and dental practices -- collecting copays, consultation fees, or amounts under the Paytomorrow financing threshold via branded payment links. - Electronics retailers -- collecting payment for accessories, warranties, or items that don't qualify for financing alongside Paytomorrow-financed purchases. - Fitness and wellness businesses -- collecting class fees, membership initiation fees, or product purchases via payment links outside of equipment financing. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with Paytomorrow required because Shuttle processes payment link transactions independently. If you're currently using Paytomorrow and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave Paytomorrow to use Shuttle payment links? No. Shuttle runs alongside Paytomorrow. You keep your existing Paytomorrow setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Can a customer use a payment link for the deposit and Paytomorrow for the rest? Yes. You can send a Shuttle payment link for the deposit or down payment, and then offer Paytomorrow financing for the remaining balance at checkout. The two systems work independently. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-payu/ --- # Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending | Shuttle > Add branded payment links to your PayU account. Send checkout links via SMS, email, or chat -- keep your existing PayU setup. No migration required. # Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending By Shuttle, December 15, 2025 Add branded payment links to your PayU account. Send checkout links via SMS, email, or chat -- keep your existing PayU setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: PayU's Payment Links Are Limited PayU is a major player in emerging markets -- India, Latin America, Central and Eastern Europe. PayU does offer a basic payment link feature, but merchants quickly outgrow it. Branding options are minimal, you can't fully customise the checkout experience, and sending links across multiple channels (WhatsApp, SMS, social) is cumbersome. For merchants who rely on payment links as a primary sales channel, PayU's built-in feature doesn't cut it. ## How Shuttle Payment Links Work with PayU Shuttle upgrades your PayU payment links with full branding control, multi-channel distribution, and a premium checkout experience. Transactions still settle through PayU. - Connect your PayU merchant account to Shuttle using your API credentials. - Create a payment link with full branding -- your logo, colours, custom messaging, and preferred payment methods. - Send the link via WhatsApp, SMS, email, social media, or embed it as a QR code. - Your customer clicks the link and pays on a fully branded checkout page with local payment methods. - The payment processes through PayU. Track it in Shuttle's analytics dashboard and your PayU account. Shuttle enhances your PayU setup -- it doesn't replace it. Local payment methods, settlement, and your PayU merchant agreement all remain the same. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your PayU reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with PayU? - Indian D2C brands -- send branded payment links via WhatsApp for COD-to-prepaid conversions, social commerce sales, and repeat orders. - Latin American ecommerce -- offer a premium checkout experience for customers in Brazil, Colombia, and Mexico. - SaaS companies in emerging markets -- collect subscription payments and one-off charges via link. - Education platforms -- send course payment links to students across India and Latin America. - Marketplace sellers -- collect off-platform payments with branded links that build trust with buyers. ## Getting Started Shuttle charges a small per-transaction fee on top of your PayU processing rates. No monthly fees, no setup costs, and no minimum volumes. Get started in under a day. Connect your PayU credentials, customise your checkout branding, and create your first link. You need an active PayU merchant account in any supported region. Shuttle provides the branded payment link infrastructure on top. ## Frequently Asked Questions ### Does Shuttle support local payment methods? Yes. Shuttle processes through your PayU account, so all payment methods enabled on PayU -- UPI, net banking, local cards, Boleto, PSE, and more -- are available on your Shuttle payment links. ### Can I fully brand the checkout page? Yes. Shuttle gives you complete control over your checkout page -- logo, brand colours, custom fields, and messaging. It looks like your own branded checkout, not a generic PayU page. ### Does this work in all PayU regions? Shuttle works with PayU across supported regions including India, Latin America, and Central/Eastern Europe. The payment methods and currencies match your PayU account configuration. ### How is this different from PayU's built-in payment links? Shuttle offers superior branding, easier multi-channel distribution (WhatsApp, SMS, social), better analytics, and a more polished checkout experience. Think of it as a premium payment link layer on top of PayU. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-quickbooks-payments/ --- # Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices | Shuttle > Add branded payment links to your QuickBooks Payments account. Send checkout links via SMS, email, or chat -- keep your existing QuickBooks Payments setup. # Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices By Shuttle, January 18, 2026 Add branded payment links to your QuickBooks Payments account. Send checkout links via SMS, email, or chat -- keep your existing QuickBooks Payments setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: QuickBooks Payments Is Tied to QuickBooks Invoicing QuickBooks Payments works well if your entire workflow lives inside QuickBooks -- create an invoice, email it, and let the customer pay through the QuickBooks payment portal. But the moment you need to collect a payment outside that flow, you're stuck. Want to text a customer a payment link? QuickBooks can't do that natively. Need to send a link via WhatsApp for a quick deposit? Not an option. QuickBooks Payments is tightly coupled to QuickBooks invoicing, and that's a limitation for merchants who sell through multiple channels. ## How Shuttle Payment Links Work with QuickBooks Payments Shuttle gives QuickBooks Payments merchants a standalone payment link tool. Use QuickBooks for your accounting and invoicing, and use Shuttle when you need to send a quick payment link through any channel. - Sign up for Shuttle and connect your payment processing account. - Create a payment link -- set the amount, add your business branding, and include a reference number that matches your QuickBooks records. - Send the link via SMS, WhatsApp, chat, social media, or email -- wherever your customer prefers. - Your customer clicks the link, sees a branded checkout page, and pays instantly. - Reconcile the payment in Shuttle's dashboard. Match it to your QuickBooks records using the reference number. Keep using QuickBooks for accounting and invoicing as usual. Shuttle handles the payment links that QuickBooks can't -- it's a complement, not a replacement. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your QuickBooks Payments reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with QuickBooks Payments? - Small business owners -- send payment links for quick sales, deposits, and service charges without creating a full QuickBooks invoice. - Contractors and freelancers -- text a payment link to a client on-site instead of emailing an invoice and waiting. - Service-based businesses -- collect deposits and session fees before appointments via SMS or WhatsApp. - Home improvement -- send a payment link when the job is complete so the customer can pay before you leave. - Event planners and caterers -- collect deposits and milestone payments via shareable links. ## Getting Started Shuttle charges a simple per-transaction fee. No monthly subscription, no setup cost, and no commitment. You only pay when you collect a payment. Go live in minutes. Sign up, add your branding, and create your first payment link. No developer needed. You need a payment processing account to connect to Shuttle. From there, Shuttle provides everything -- branded checkout pages, link sharing, and payment tracking. ## Frequently Asked Questions ### Do I need to stop using QuickBooks Payments? No. Keep using QuickBooks Payments for your regular invoicing. Use Shuttle for situations where you need a standalone payment link -- SMS payments, WhatsApp collections, deposits, and quick charges. ### Can I match Shuttle payments to QuickBooks invoices? Yes. Add your QuickBooks invoice number or customer reference to the Shuttle payment link. This makes reconciliation simple when you record the payment in QuickBooks. ### Is Shuttle faster than sending a QuickBooks invoice? Much faster. Creating a QuickBooks invoice, emailing it, and waiting for the customer to open it and pay can take days. A Shuttle payment link can be texted and paid in under a minute. ### Can customers pay with Apple Pay or Google Pay? Yes. Shuttle payment links support card payments, Apple Pay, and Google Pay -- giving your customers a modern checkout experience. ## Related Reading Explore More ### QuickBooks Payment Links: Add a Pay Now Button to Any Invoice ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideQuickBooks Payment Links: Add a Pay Now Button to Any Invoice→](/guides/quickbooks-payment-links/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-shift4/ --- # Payment Links for Shift4: Send Branded Checkout Links for Hospitality and Restaurant Payments | Shuttle > Add branded payment links to your Shift4 account. Send checkout links via SMS, email, or chat -- keep your existing Shift4 setup. No migration required. # Payment Links for Shift4: Send Branded Checkout Links for Hospitality and Restaurant Payments By Shuttle, January 18, 2026 Add branded payment links to your Shift4 account. Send checkout links via SMS, email, or chat -- keep your existing Shift4 setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Shift4 Doesn't Do Payment Links Well Shift4 is the dominant payment processor in hospitality -- powering POS terminals in restaurants, hotels, and stadiums across the US. But when merchants need to collect a payment outside the physical terminal, options dry up fast. There's no native way to text a guest a payment link for a room deposit, send a catering invoice via WhatsApp, or collect a pre-order payment before an event. Merchants end up cobbling together separate invoicing tools or taking card numbers over the phone, which creates PCI headaches and a poor customer experience. ## How Shuttle Payment Links Work with Shift4 Shuttle sits on top of your existing Shift4 merchant account. Transactions still settle through Shift4 -- we just give you a new way to initiate them remotely. - Connect your Shift4 merchant account to Shuttle (takes under five minutes). - Create a payment link in the Shuttle dashboard -- set the amount, add your branding, and choose which payment methods to accept. - Send the link to your customer via SMS, email, WhatsApp, or embed it on your website. - Your customer clicks the link, lands on a branded checkout page, and pays securely. - The payment processes through Shift4 as usual. You see it in both your Shuttle dashboard and your Shift4 reports. Your existing Shift4 rates, settlement schedule, and reporting all stay the same. Shuttle is an add-on, not a replacement. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Shift4 reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Shift4? - Hotels and resorts -- send deposit links for room bookings, event spaces, and group reservations. - Restaurants and catering -- collect deposits for large catering orders, private dining events, and pre-fixe menus. - Stadiums and venues -- sell VIP packages, suite rentals, and merchandise bundles via link before game day. - Food trucks and pop-ups -- take pre-orders and accept payments when the POS terminal isn't practical. - Hotel gift shops and spas -- send payment links for gift cards, spa packages, and room-charge disputes. ## Getting Started Shuttle charges a small per-transaction fee on top of your existing Shift4 processing rates. There are no setup fees, and no long-term contracts. Most merchants are live within a day. Connect your Shift4 account, add your logo and brand colours, and start sending links immediately. All you need is an active Shift4 merchant account. Shuttle handles the rest -- hosted checkout, payment processing, and reporting are all included out of the box. ## Frequently Asked Questions ### Do I need to switch away from Shift4? No. Shuttle works alongside your existing Shift4 account. All transactions still process and settle through Shift4. You keep your current rates and merchant agreement. ### Can I send payment links via text message? Yes. Shuttle lets you send payment links via SMS, email, WhatsApp, or any messaging channel. You can also generate a QR code or embed the link on your website. ### Is this PCI compliant? Absolutely. Shuttle payment links use hosted checkout pages, so card data never touches your systems. This keeps your PCI scope limited. ### What does it cost? Shuttle charges a small per-transaction fee on top of your existing Shift4 processing rates. There are no monthly minimums or setup fees. Contact us for exact pricing. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-square/ --- # Payment Links for Square: Upgrade Your Square Payment Links | Shuttle > Upgrade Square payment links with full branding, detailed tracking, and multi-channel delivery. # Payment Links for Square: Upgrade Your Square Payment Links By Nick Dunse, January 19, 2026 Upgrade Square payment links with full branding, detailed tracking, and multi-channel delivery. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Square's payment links work. They're functional. You create a link, share it, and get paid. For a sole trader doing a few transactions a month, it's adequate. But for growing businesses, the cracks show. Square's payment links are branded as Square -- not your business. The checkout page carries Square's design language. Customisation is limited to a logo and a description. You can't match your website's look and feel. Tracking is basic. You know if someone paid. You don't know if they opened the link, viewed the checkout page, or dropped off before entering their card. For businesses running campaigns or chasing payments, that visibility matters. And if you use Square alongside another payment provider -- or plan to in the future -- Square's links lock you into Square's ecosystem. Shuttle gives Square merchants an upgrade: fully branded links, detailed tracking, multi-channel delivery, and the flexibility to add other PSPs later. ## How Payment Links Work with Square Shuttle connects to your Square account via OAuth. The same secure connection method Square uses for its own app marketplace. Authorise the connection and Shuttle can create payment links that process through your Square account. When a customer pays through a Shuttle-powered link, the transaction shows up in your Square Dashboard. Your existing rates apply. Settlement goes to your bank account on your normal Square schedule. The difference is what the customer sees and what you can track. Fully branded checkout. Real-time link analytics. SMS, email, and chat delivery built in. - Connect your Square account via OAuth -- authorise in two clicks. - Create a payment link with your branding -- logo, colours, custom messaging. - Choose your delivery channel: SMS, email, or share link. - Customer pays on your branded checkout page. - Transaction appears in Square Dashboard. Settlement as normal. ## What You Get - Your brand, not Square's: Fully customised checkout pages that match your website and identity. - Link analytics: Track opens, views, completions, and abandonment in real time. - SMS and email sending: Send links directly from the dashboard -- no copying and pasting. - Multiple payment methods: Cards, Apple Pay, Google Pay -- whatever your Square account supports. - Merchant dashboard: Manage all your payment links in one place with filters, search, and exports. - Deposits and partial payments: Collect deposits upfront or split payments across multiple links. - Multi-PSP flexibility: Use Square now. Add another provider later. Same dashboard. ## Who Uses This - Service-based businesses that outgrew Square's basic links and want professional branding. - Appointment-based businesses sending deposit links via SMS before a booking. - Retailers taking phone orders and sending payment links to complete the sale. - Event organisers collecting payments for tickets, tables, and sponsorships. - Freelancers and consultants who want their payment experience to match their professional brand. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No markup on your Square transaction rates. Connect via OAuth in under a minute. Configure your brand. Send your first link immediately. No contracts, no setup fees. ## FAQ Do I need to leave Square? No. Shuttle enhances your Square account -- it doesn't replace it. Your rates, settlement, and Square Dashboard all stay the same. How is this different from Square's built-in payment links? Full branding control, detailed link analytics (opens, views, conversions), multi-channel sending, and the option to add other PSPs alongside Square. Will customers know I'm using Shuttle? No. The checkout page shows your brand only. It's fully white-labelled. Can I use this alongside Square POS? Yes. Shuttle handles payment links. Square POS handles in-person payments. Both use the same Square account. Upgrade your Square payment links -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Upgrade your Square payment links](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-stripe/ --- # Payment Links for Stripe: Add Branded Checkout Links to Your Stripe Account | Shuttle > Add branded payment links to your Stripe account. Send via SMS, email, or chat with full branding, tracking, and a merchant dashboard. # Payment Links for Stripe: Add Branded Checkout Links to Your Stripe Account By Nick Dunse, January 19, 2026 Add branded payment links to your Stripe account. Send via SMS, email, or chat with full branding, tracking, and a merchant dashboard. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Stripe has its own Payment Links product. On paper that sounds like it solves the problem. In practice, it leaves merchants wanting more. Stripe's payment links are locked to Stripe's template. You can add your logo, but you can't fully brand the checkout page to match your website. The link looks like Stripe -- not your business. For merchants selling premium services or running a professional operation, that matters. Then there's distribution. Stripe gives you a URL. That's it. You copy it, paste it into an email, and hope for the best. There's no native SMS sending. No way to push a link through a chat channel. No tracking to see whether the customer opened the link, viewed the checkout page, or abandoned before paying. Merchants shouldn't have to leave Stripe to fix this. Their rates are negotiated, their reconciliation is set up, and their finance team knows the Stripe Dashboard. What they need is a better payment links layer -- on top of Stripe. ## How Payment Links Work with Stripe Shuttle connects to your Stripe account via OAuth. No API keys to manage, no developer involvement. You authorise the connection, and Shuttle can process payments through your existing Stripe account. Once connected, creating a payment link takes seconds. Set the amount, add a reference, customise the checkout page with your brand, and choose how to send it -- SMS, email, or chat. The customer clicks, pays on a branded page, and the money lands in your Stripe account exactly as it would with any other Stripe transaction. Settlement, reporting, and reconciliation don't change. Shuttle sits on top of Stripe -- it doesn't replace it. - Connect your Stripe account via OAuth -- takes under two minutes. - Create a payment link in the Shuttle dashboard. Set the amount, currency, and reference. - Customise the checkout page with your logo, brand colours, and messaging. - Send the link via SMS, email, or chat -- directly from the dashboard. - Customer pays on a branded checkout page. Funds settle to your Stripe account as normal. ## What You Get - Fully branded checkout: Your logo, colours, and messaging -- not Stripe's default template. - Multi-channel sending: Send payment links via SMS, email, or chat. No copy-pasting URLs. - Real-time tracking: See when a link is sent, opened, viewed, and paid -- or abandoned. - Multiple payment methods: Cards, digital wallets, and local payment methods -- all through your Stripe account. - Merchant dashboard: Create, send, and manage payment links without touching code. - Partial and recurring payments: Take deposits, split payments, or set up subscriptions via link. - No developer required: Connect and start sending in minutes. No integration work. ## Who Uses This - Service businesses sending invoices and collecting deposits from clients. - B2B companies that need to email payment links for outstanding invoices. - Phone order teams that take orders over the phone and need a secure way to collect card details. - Sales teams closing deals remotely who need to send a pay link during the conversation. - Hospitality and events taking deposits and balance payments via SMS. ## Pricing and Setup Shuttle Payment Links costs $49 per month. No setup fees. No transaction surcharges on top of your existing Stripe rates. Connect your Stripe account in under two minutes via OAuth. Create your first branded payment link the same day. There's no minimum contract and no integration work required. ## FAQ Do I need to leave Stripe? No. Shuttle connects to your existing Stripe account. You keep your rates, your dashboard, and your settlement schedule. Nothing changes on the Stripe side. Will my customers see Shuttle branding? No. The checkout page is fully white-labelled with your brand. Customers see your logo, your colours, and your business name. What payment methods are supported? All payment methods enabled on your Stripe account -- cards, Apple Pay, Google Pay, and any local methods you've configured. How does settlement work? Exactly the same as any other Stripe transaction. Funds settle to your Stripe account on your normal schedule. Shuttle never touches the money. Want to add branded payment links to your Stripe account without switching processor? Shuttle Links & Checkout sits on top of your existing Stripe account -- generate payment links with your branding, share them anywhere, and keep your Stripe rates and reporting. Cards, Apple Pay, Google Pay, and local methods all supported. See how it works. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [See how it works](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-tiktok-sales/ --- # Using Payment Links to increase TikTok sales | Shuttle > How to accept payments on TikTok using payment links, TikTok Shop, and third-party checkout. # Using Payment Links to increase TikTok sales By Nick Dunse, February 19, 2026 How to accept payments on TikTok using payment links, TikTok Shop, and third-party checkout. Start sending payment links today Accept payments from TikTok DMs, comments, and live streams -- no website needed. Just send a link. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. ## Payment Links for TikTok sales ### 1. Introduction to TikTok Sales TikTok has become one of the most popular social media platforms in recent years, with millions of users creating and sharing short videos on a wide range of topics. As a result, it's no surprise that many people have started using TikTok as a platform to sell products and services. In this article, we'll explore how payment links can be used to facilitate these transactions and provide a seamless experience for both buyers and sellers. ### 2. Understanding Payment Links Payment links are a convenient way for businesses to accept payments online. They allow customers to make purchases directly from their social media profiles without having to leave the platform. In this section, we will explore what payment links are, how they work, and why they are important for businesses selling on TikTok. ### 3. Setting Up Payment Links for TikTok Sales To set up payment links for TikTok sales, you will need to follow these steps: 1. Create a TikTok account if you haven't already done so. 2. Go to the "Settings" tab on your TikTok profile. 3. Click on the "Linkin.bio" option under the "Account" menu. 4. Enter the link to your payment page in the provided field. 5. Save your changes and test your payment link to ensure it works properly. 6. Share your payment link with your TikTok followers to start making sales. ### 4. Choosing the Right Payment Gateway When it comes to choosing a payment gateway for your TikTok sales, there are several options available. Each payment gateway has its own unique features and benefits, so it's important to choose one that aligns with your business needs. Here are some factors to consider when selecting a payment gateway: 1. Processing Fees: Look for a payment gateway with low processing fees to maximize your profits. 2. Integration Ease: Choose a payment gateway that integrates easily with your TikTok account and website. 3. Security Measures: Make sure the payment gateway you choose offers robust security measures to protect your and your customers' data. 4. Support: Consider the level of support offered by the payment gateway provider, including customer service hours and availability. 5. Customization Options: Some payment gateways offer customizable options for buttons, colors, and logos, which can help brand your payment process. 6. Compatibility: Ensure that the payment gateway you select is compatible with both desktop and mobile devices. 7. International Payments: If you plan on selling products internationally, check if the payment gateway supports international payments and currencies. 8. Fraud Protection: Look for a payment gateway that offers fraud protection tools to minimize the risk of chargebacks and disputes. ### 5. Customizing Your Payment Link Customizing your payment link allows you to personalize it with your own branding and design elements. This can include adding your company logo, changing the color scheme, or even including a custom message. By doing so, you can create a payment link that reflects your brand and makes it easy for customers to identify and trust. Additionally, customizing your payment link can also help increase conversions by making it more visually appealing and engaging. ### 6. Tracking Sales and Analytics Tracking sales and analytics is crucial for any business, and TikTok sales are no exception. By tracking your sales and analytics, you can gain valuable insights into your audience's behavior and preferences, which can help you optimize your marketing strategy and improve your product offerings. Here are some key metrics you should track when it comes to your TikTok sales: 1. Total sales: This is the most basic metric of all, and it tells you how much revenue you have generated from your TikTok sales. 2. Sales per product: This metric shows you which products are selling the best on TikTok, and can help you focus your marketing efforts on those products. 3. Conversion rate: The conversion rate measures the percentage of visitors who complete a desired action, such as making a purchase. It helps you understand how effective your marketing campaigns are in driving conversions. 4. Average order value: This metric tells you how much, on average, customers are spending per order. It can help you identify trends and opportunities for upselling or cross-selling. 5. Repeat customers: Tracking the number of repeat customers can give you insight into customer loyalty and retention rates. 6. Referral sources: Knowing where your customers are coming from (e.g., social media, search engines, etc.) can help you optimize your marketing strategies to attract more traffic and sales. 7. Refunds and returns: Keeping track of refunds and returns can help you identify any issues with your products or services, and address them before they become bigger problems. By tracking these metrics, you can get a better understanding of your TikTok sales performance, and use that data to make informed decisions about how to grow your business. ### 7. Security Measures for Payment Links Security is of utmost importance when it comes to online transactions. As a creator using TikTok to sell products or services, it's crucial to implement various security measures to ensure that your payment links are safe and secure. Here are some steps you can take to enhance the security of your payment links: 1. Use HTTPS: Hypertext Transfer Protocol Secure (HTTPS) is a protocol used to secure communication over the internet. By using HTTPS, you can encrypt the data being transmitted between your website and the user's browser, making it difficult for hackers to intercept sensitive information such as credit card details. 2. Implement Two-Factor Authentication: Two-factor authentication (2FA) adds an extra layer of security by requiring users to provide two forms of identification before accessing their account or making a purchase. This can include a password, fingerprint, or a one-time code sent to their phone. 3. Regularly Update Software: Keeping your software up-to-date with the latest security patches is essential in preventing potential vulnerabilities from being exploited by cybercriminals. Make sure to regularly update your website, payment gateway, and any other relevant software. 4. Monitor Transactions: Keep track of all transactions made through your payment links and look out for any suspicious activity. If you notice any unusual patterns, contact your payment gateway provider immediately. 5. Use a Trusted Payment Gateway: Choose a reputable payment gateway provider that prioritizes security. Look for providers that offer advanced fraud protection tools, such as device fingerprinting, geolocation tracking, and real-time transaction monitoring. By implementing these security measures, you can rest assured that your payment links are secure and protected against potential threats. Remember, the safety of your customers and their financial information should always be your top priority. ### 8. Common Challenges and Solutions When it comes to setting up payment links for TikTok sales, there are several common challenges that businesses may encounter. One of the biggest challenges is ensuring that payments are secure and protected from fraud. This can be achieved through the use of encryption technology and other security measures, such as two-factor authentication. Another challenge is ensuring that payments are processed quickly and efficiently, so that customers receive their products or services in a timely manner. To address this issue, businesses should choose a reliable and efficient payment gateway that is capable of processing transactions quickly and accurately. Additionally, businesses may face challenges with tracking sales and analytics, as well as customizing their payment links to meet their specific needs. To overcome these challenges, businesses should invest in robust sales and analytics tools, as well as customizable payment link options that allow them to tailor their payment process to their unique business requirements. By addressing these common challenges, businesses can set up successful payment links for TikTok sales and provide their customers with a seamless and secure checkout experience. ### 9. Best Practices for Promoting Your Payment Links Promoting your payment links is crucial to ensure that your TikTok sales reach their full potential. Here are some best practices to consider when promoting your payment links: 1. Use clear and concise language: When promoting your payment links, it's important to use language that is easy to understand. Avoid using technical jargon or overly complicated terminology as this can confuse your audience. 2. Provide value: Instead of simply promoting your payment links, try to provide value to your audience first. Share useful tips, tricks, or insights related to your product or service before promoting your payment link. This can increase trust and credibility with your audience. 3. Be consistent: Consistency is key when it comes to promoting your payment links. Develop a consistent messaging strategy across all platforms and channels where you promote your links. This helps to build brand recognition and makes it easier for your audience to remember your payment link. 4. Leverage social proof: Social proof is a powerful tool in influencing buying decisions. Showcase positive reviews, testimonials, or endorsements from satisfied customers to demonstrate the value of your product or service. 5. Offer incentives: Consider offering incentives such as discounts, free trials, or bonuses to encourage people to click on your payment link. These incentives can help to drive more traffic to your payment link and increase conversions. 6. Utilize multiple promotion channels: Don't rely solely on one platform or channel to promote your payment link. Use a variety of methods such as email marketing, social media ads, influencer partnerships, and more to reach a wider audience. 7. Monitor and optimize: Continuously monitor the performance of your payment link promotions and optimize them based on data and feedback. Adjust your messaging, targeting, and incentives to improve conversion rates and maximize revenue. 10. Conclusion In conclusion, payment links for TikTok sales can be a great way to monetize your content and grow your business. By understanding the basics of payment links and choosing the right payment gateway, you can easily set up customized payment links for your TikTok sales. Remember to track your sales and analytics, and take security measures to protect your and your customers' information. With these tips in mind, you should be well on your way to success with payment links for TikTok sales. Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Get Payment Links today](/platforms/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-transbank/ --- # Payment Links for Transbank: Send Branded Checkout Links for Chilean Merchants | Shuttle > Add branded payment links to your Transbank account. Send checkout links via SMS, email, or chat -- keep your existing Transbank setup. # Payment Links for Transbank: Send Branded Checkout Links for Chilean Merchants By Shuttle, January 20, 2026 Add branded payment links to your Transbank account. Send checkout links via SMS, email, or chat -- keep your existing Transbank setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Transbank Lacks Modern Payment Link Features Transbank is the backbone of card processing in Chile -- virtually every merchant that accepts cards uses Transbank's Webpay integration or POS terminals. But Transbank was built for in-store and traditional ecommerce. When Chilean merchants need to send a payment link for a remote sale, a deposit, or a phone order, Transbank doesn't offer a self-serve solution. Merchants end up asking customers to make bank transfers or dictating card numbers over the phone, which is slow, insecure, and unprofessional. ## How Shuttle Payment Links Work with Transbank Shuttle connects to your existing payment infrastructure in Chile and gives you branded payment links that your customers can pay through instantly. No Webpay integration work required. - Sign up for Shuttle and connect your payment processing credentials. - Create a payment link in CLP -- add your business branding, set the amount, and choose payment options. - Send the link to your customer via WhatsApp, SMS, email, or social media -- wherever Chilean consumers communicate. - Your customer taps the link, sees a branded checkout page, and pays with their preferred method. - Track the payment in Shuttle's dashboard with real-time status updates and reconciliation tools. Shuttle works alongside your existing Transbank setup. Your in-store POS and Webpay integrations continue unchanged -- payment links are a new channel, not a replacement. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Transbank reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Transbank? - Chilean retail and ecommerce -- send payment links for phone orders, social media sales, and out-of-stock pre-orders. - Professional services -- collect fees for legal, accounting, and consulting services via link instead of bank transfer. - Restaurants and delivery -- take catering deposits and event payments without cash or in-person terminals. - Education and training -- collect course fees, workshop registrations, and material costs via shareable links. - Healthcare providers -- send payment links for consultations, lab fees, and procedure deposits. ## Getting Started Shuttle charges a simple per-transaction fee. No monthly charges, no setup fees, and no minimum volumes. Pay only when you process payments. Get up and running within a day. Connect your credentials, add your branding, and send your first payment link to a customer. You need active payment processing in Chile. Shuttle provides the payment link infrastructure -- branded checkout, link management, and reporting are included. ## Frequently Asked Questions ### Does this work with Chilean pesos (CLP)? Yes. Shuttle supports CLP transactions through your payment processing setup. Customers see prices and pay in Chilean pesos. ### Can I send links via WhatsApp? Yes. WhatsApp is the most popular messaging app in Chile, and Shuttle generates links that can be shared on WhatsApp, SMS, email, Instagram, or any other channel. ### Do I need to stop using Transbank? No. Keep using Transbank for your POS terminals and Webpay ecommerce integration. Shuttle adds payment links as a new channel for remote and phone-based payments. ### Is this secure? Absolutely. Shuttle uses hosted checkout pages so card data never touches your systems. All transactions are processed on PCI DSS compliant infrastructure. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-trust-payments/ --- # Payment Links for Trust Payments: Send Branded Checkout Links for European Card Processing | Shuttle > Add branded payment links to your Trust Payments account. Send checkout links via SMS, email, or chat -- keep your existing Trust Payments setup. # Payment Links for Trust Payments: Send Branded Checkout Links for European Card Processing By Shuttle, January 21, 2026 Add branded payment links to your Trust Payments account. Send checkout links via SMS, email, or chat -- keep your existing Trust Payments setup. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Trust Payments Doesn't Offer Self-Serve Payment Links Trust Payments is a well-established European PSP -- strong acquiring relationships, multi-currency processing, and solid fraud tools. But if you're a merchant who needs to send a one-off payment link to a customer, Trust Payments doesn't offer a self-serve tool for that. You're stuck building a custom hosted payment page integration or using a separate third-party invoicing tool. For merchants handling phone orders, deposits, or service payments across Europe, this is a significant gap. ## How Shuttle Payment Links Work with Trust Payments Shuttle plugs into your Trust Payments merchant account and gives you an instant payment link tool. Transactions still route through Trust Payments -- Shuttle provides the branded checkout front-end. - Connect your Trust Payments account to Shuttle with your API credentials. - Create a payment link -- set the amount in any supported currency (GBP, EUR, etc.), add your branding, and configure payment methods. - Send the link via email, SMS, WhatsApp, or share it on social media. - Your customer clicks the link, lands on a branded checkout page, and pays securely. - The payment processes through Trust Payments. View transactions in Shuttle's dashboard and your Trust Payments back office. Your Trust Payments merchant agreement, rates, and multi-currency settlement are unaffected. Shuttle is a layer on top -- not a migration. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Trust Payments reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Trust Payments? - European ecommerce merchants -- send payment links for phone orders, returns handling, and manual adjustments. - Travel and hospitality -- collect booking deposits, excursion payments, and ancillary charges across European currencies. - Professional services -- invoice clients in GBP or EUR with a clickable payment link instead of a bank transfer request. - Subscription businesses -- send upgrade or one-off charge links to existing subscribers without building a custom flow. - Charities and membership organisations -- collect donations and membership fees via shareable links across Europe. ## Getting Started Shuttle charges a small per-transaction fee. No monthly fees, no setup costs, and no minimum volume requirements. Go live within a day. Connect your Trust Payments API credentials, set up your branding, and create your first payment link. All you need is an active Trust Payments merchant account. Shuttle provides the hosted checkout, link management, distribution tools, and transaction reporting. ## Frequently Asked Questions ### Does Shuttle support multi-currency payments? Yes. Shuttle uses your Trust Payments account's currency settings. If you process in GBP, EUR, and other currencies through Trust Payments, your Shuttle payment links support those same currencies. ### Is this compliant with European regulations? Yes. Shuttle's hosted checkout supports 3D Secure authentication as required by PSD2/SCA regulations. All card data is handled on PCI-compliant hosted pages. ### Can I customise the checkout page? Absolutely. Add your logo, brand colours, custom fields, and messaging. Your customers see a checkout page that looks and feels like your brand. ### Do I need to change my Trust Payments contract? No. Shuttle works on top of your existing Trust Payments setup. Your acquiring agreement, processing rates, and settlement schedule remain exactly the same. ## Related Reading Explore More ### How to Connect Trust Payments to Twilio for Voice & IVR Payments ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideHow to Connect Trust Payments to Twilio for Voice & IVR Payments→](/guides/trust-payments-twilio-integration/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-usaepay/ --- # Payment Links for USAePay: Send Branded Checkout Links for Remote and Phone Payments | Shuttle > Add branded payment links to your USAePay account. Send checkout links via SMS, email, or chat -- keep your existing USAePay setup. No migration required. # Payment Links for USAePay: Send Branded Checkout Links for Remote and Phone Payments By Shuttle, January 21, 2026 Add branded payment links to your USAePay account. Send checkout links via SMS, email, or chat -- keep your existing USAePay setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: USAePay Doesn't Have a Payment Link Feature USAePay is a reliable US payment gateway that's been around for decades -- popular with merchants who need virtual terminal access and terminal-based processing. But USAePay was built for a different era. If you need to send a customer a clickable payment link via text or email, there's no native feature for that. Your options are the virtual terminal (where you key in card numbers manually), or building a custom integration. Neither is fast, neither is branded, and the virtual terminal approach puts you in PCI scope. ## How Shuttle Payment Links Work with USAePay Shuttle connects to your USAePay gateway and gives you instant payment link capability. Transactions still process through USAePay -- Shuttle just provides the customer-facing checkout experience. - Connect your USAePay gateway to Shuttle using your source key and PIN. - Create a payment link in the Shuttle dashboard -- set the dollar amount, apply your branding, and choose accepted card types. - Send the link to your customer via SMS, email, or any messaging channel. - Your customer clicks the link, sees your branded checkout page, and enters their card details securely. - The payment processes through USAePay on your existing merchant account. View it in Shuttle's dashboard and your USAePay console. Nothing changes on the USAePay side. Your rates, batch settlement, and reporting all work exactly as before. Shuttle simply adds a new way to initiate payments. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your USAePay reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with USAePay? - B2B suppliers and wholesalers -- send payment links for invoices instead of chasing checks or keying in card numbers. - Medical and dental offices -- collect patient copays, outstanding balances, and procedure deposits via link. - Auto repair shops -- send a payment link when the job is done so customers can pay before pickup. - Legal and accounting firms -- collect retainers and invoice payments without taking card numbers over the phone. - Field service companies -- send payment links on the spot for HVAC, plumbing, or electrical work. ## Getting Started Shuttle charges a small per-transaction fee on top of your USAePay gateway rates. No setup fees, and no contracts. Most merchants are live within hours. Plug in your USAePay credentials, customise your checkout page, and send your first link. You need an active USAePay gateway account. Shuttle handles hosted checkout, link generation, and analytics -- no development work needed. ## Frequently Asked Questions ### Do I need to leave USAePay? No. Shuttle is an add-on to your existing USAePay gateway. All transactions process through USAePay using your current merchant account, rates, and settlement schedule. ### Is this more secure than the virtual terminal? Yes. With Shuttle payment links, your customer enters their card data on a hosted checkout page. Card numbers never pass through your systems or staff, which keeps your PCI scope limited. ### Can I use this for recurring payments? Yes. Shuttle supports recurring payment links where customers can authorise ongoing charges. You can also create partial payment links for deposits or instalments. ### What if I already use USAePay's virtual terminal? Keep using it where it makes sense. Shuttle payment links are ideal for situations where you'd rather send a link than key in a card number -- phone orders, email invoices, service appointments, and more. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-veem/ --- # Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections | Shuttle > Add branded payment links to your VEEM account. Send checkout links via SMS, email, or chat -- keep your existing VEEM setup. No migration required. # Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections By Shuttle, February 19, 2026 Add branded payment links to your VEEM account. Send checkout links via SMS, email, or chat -- keep your existing VEEM setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: VEEM Doesn't Do Payment Links Well VEEM is a B2B payment platform designed for international bank transfers. It helps businesses send and receive cross-border payments through its multi-rail network, reducing the cost and complexity of wire transfers. But VEEM is built around bank-to-bank payments, which can take days to settle. When B2B sellers need faster collections -- or when buyers prefer paying by card -- VEEM doesn't offer branded payment links for card transactions. This leaves businesses without a quick, card-based collection option for their B2B invoices. ## How Shuttle Payment Links Work with VEEM You don't need to replace VEEM. Shuttle sits alongside your existing setup and gives you a dedicated payment link capability that VEEM doesn't offer natively. - Sign up for Shuttle and configure your branded checkout with your company logo and colours. - Create a payment link for the invoice amount, add the invoice number or PO reference, and set a due date if needed. - Send the payment link to your business customer via email alongside or instead of your standard VEEM bank transfer request. - Your customer clicks the link and pays by card on your branded checkout page -- settlement is faster than bank transfer. - Track the payment in Shuttle. Continue using VEEM for customers who prefer bank transfers. Your VEEM processing continues as normal. Shuttle handles the payment link checkout experience separately, so there's nothing to migrate and no disruption to your current operations. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic processor page. This builds trust and keeps the experience consistent with VEEM-processed transactions. Multiple payment methods -- accept Visa, Mastercard, American Express, and other card networks. Depending on your region, you can also enable local payment methods alongside your standard VEEM card processing. Send anywhere -- share payment links via email, SMS, WhatsApp, social media, live chat, or QR code. Copy the link and paste it into any channel your customers already use. Dashboard and reporting -- track every payment link from creation to completion. See who paid, who hasn't, and send reminders. This complements your VEEM reporting with payment link-specific analytics. Recurring and partial payments -- set up payment links for subscriptions, deposits, or instalments. Customers can pay a portion upfront and the rest later, all through the same branded link. No code required -- create and send payment links from the Shuttle dashboard without writing any code. If you want to automate link creation, there is also a full API available. ## Who Uses Payment Links with VEEM? - B2B SaaS companies -- giving enterprise clients a card payment option for annual subscriptions or large invoices when bank transfers are too slow. - Import/export businesses -- collecting faster payments from international buyers by offering card payment links alongside traditional VEEM bank transfers. - Wholesale distributors -- sending payment links for urgent orders where waiting for bank transfer settlement would delay shipment. - Consulting and professional services -- collecting project fees and retainers by card when clients can't or won't initiate bank transfers promptly. - Manufacturing and trade businesses -- collecting deposits or progress payments by card to improve cash flow while using VEEM for final balance settlements. ## Getting Started Shuttle payment links are available on all plans. You can start with a free trial to test the checkout experience before going live. Pricing is transaction-based with no monthly minimums. Setup takes less than 15 minutes. You create your Shuttle account, add your branding, and start generating payment links. There's no integration with VEEM required because Shuttle processes payment link transactions independently. If you're currently using VEEM and need a way to send payment links to customers, get in touch with the Shuttle team. We'll walk you through the setup and have you sending branded checkout links the same day. ## Frequently Asked Questions ### Do I need to leave VEEM to use Shuttle payment links? No. Shuttle runs alongside VEEM. You keep your existing VEEM setup for everything it handles today, and use Shuttle specifically for payment links. There's no migration involved. ### How do my customers pay through a payment link? They click the link, land on your branded checkout page, enter their payment details, and pay. The experience works on any device -- desktop, tablet, or mobile. No app download or account creation required. ### Can I track which payment links have been paid? Yes. The Shuttle dashboard shows real-time status for every link: created, viewed, paid, or expired. You can filter by date, amount, or customer, and export data for reconciliation. ### Is it more expensive for B2B customers to pay by card than bank transfer? Card payments do carry processing fees, but the trade-off is speed -- you get settled in days rather than waiting a week or more for international bank transfers. For many B2B sellers, faster cash flow justifies the cost. You can also pass processing fees to the buyer if your terms allow it. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-video-shopping/ --- # How Payment Links can help Video Shopping Platforms | Shuttle > Learn how video shopping platforms use payment links to convert live viewers into buyers with instant, secure checkout during broadcasts. # How Payment Links can help Video Shopping Platforms By Nick Dunse, December 31, 2025 Learn how video shopping platforms use payment links to convert live viewers into buyers with instant, secure checkout during broadcasts. Start sending payment links today Accept payments during live video shopping sessions -- no cart needed. Just send a link. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. ## Payment Links for video shopping 1. Introduction Video shopping has become increasingly popular over the past few years, with more and more people turning to online platforms to purchase products they need or want. One of the key advantages of video shopping is the ability to showcase products in an engaging and interactive way, allowing customers to get a better understanding of what they're buying before making a purchase. However, one of the challenges of video shopping is the need for secure and reliable payment methods. In this article, we'll explore how payment links can be integrated into video shopping platforms to provide a seamless and secure checkout experience for customers. ### 2. What are payment links? Payment links are a type of digital payment solution that allows customers to make purchases directly from a video shopping platform. They provide a seamless and secure way for users to complete transactions without leaving the platform. Payment links are typically generated by the video shopping platform and can be customized with branding elements to match the look and feel of the platform. Once a customer clicks on a payment link, they will be directed to a secure payment page where they can enter their payment details and complete the transaction. Payment links are becoming increasingly popular in the world of e-commerce as they offer a convenient and efficient way for customers to make purchases online. ### 3. Advantages of using payment links in video shopping Payment links offer several advantages for video shopping platforms. Firstly, they provide a seamless checkout experience for customers, allowing them to complete their purchase without leaving the video. This can lead to higher conversion rates and increased sales. Secondly, payment links allow for customization of the checkout process, including the ability to add additional payment options or modify the payment process to suit specific customer needs. Thirdly, payment links can reduce cart abandonment rates by providing a secure and convenient way for customers to complete their purchase. Finally, payment links can also help to increase customer loyalty by providing a positive checkout experience and making it easy for customers to return to the video shopping platform in the future. ### 4. How do payment links work in video shopping? Payment links work in video shopping by allowing customers to purchase products directly from within the video itself. This eliminates the need for customers to leave the video to go to another website or app to complete their purchase. Instead, they can simply click on the payment link and enter their payment information to complete the transaction. This streamlines the purchasing process and makes it more convenient for customers. Additionally, payment links can be customized to include different payment options such as credit card, PayPal, or Apple Pay, giving customers the flexibility to choose how they want to pay. ### 5. Types of payment links used in video shopping Types of payment links used in video shopping include: * Single-use payment links: These links can only be used once and then expire. They are often used for one-time purchases or promotional offers. * Recurring payment links: These links allow customers to set up recurring payments for subscriptions or memberships. * Virtual terminal payment links: These links allow merchants to process payments directly through their own website, rather than relying on a third-party payment processor. * Mobile payment links: These links are optimized for mobile devices and provide a seamless checkout experience for customers shopping on their smartphones or tablets. ### 6. Integrating payment links into your video shopping platform To integrate payment links into your video shopping platform, you need to follow these steps: 1. Choose a payment gateway: First, you need to choose a payment gateway that supports payment links. Some popular options include Stripe, PayPal, and Square. 2. Set up your payment gateway: Once you have chosen a payment gateway, you need to set it up on your video shopping platform. This typically involves adding API keys and configuring payment settings. 3. Generate payment links: With your payment gateway set up, you can generate payment links that customers can use to complete transactions. These links should be easy to share and include all necessary information, such as the item being purchased and the total cost. 4. Test your integration: Before launching your video shopping platform with payment links, it's important to test your integration to ensure that everything is working properly. This includes testing the payment process, as well as any customizations you may have made to your payment gateway. 5. Launch your platform: Once you have tested your integration and are confident that everything is working correctly, you can launch your video shopping platform with payment links. Be sure to promote this feature to your customers to encourage them to use it. ### 7. Best practices for using payment links in video shopping When it comes to using payment links in video shopping, there are several best practices that should be followed to ensure a smooth and secure transaction process. Here are some tips to keep in mind: 1. Clearly display the payment link: The payment link should be clearly displayed within the video shopping experience, so users can easily access it without any confusion. It should be prominently placed and easy to locate. 2. Use descriptive labels: When presenting payment options, use clear and concise language to describe each option. This helps users understand what they are paying for and makes the purchasing process more transparent. 3. Test the payment link before launch: Before launching your video shopping platform, test the payment link thoroughly to ensure it works seamlessly across different devices and browsers. This will help avoid any technical issues during the actual launch. 4. Provide multiple payment options: Offering multiple payment options gives users flexibility and convenience. Accepting various payment methods such as credit cards, debit cards, PayPal, Apple Pay, and Google Pay increases the likelihood of completing a purchase. 5. Implement fraud prevention measures: To protect both your business and your customers, implement fraud prevention measures like two-factor authentication, address verification systems, and chargeback protection. 6. Monitor transactions closely: Regularly monitor transactions to identify any suspicious activity or potential fraud. Address any issues promptly to maintain a secure environment for your customers. 7. Keep customer data secure: Ensure that customer data, including payment information, is stored securely and protected from unauthorized access. Implement encryption protocols and follow data privacy regulations to safeguard sensitive information. 8. Communicate clearly with customers: Maintain open communication with your customers throughout the purchasing process. Provide clear and timely updates on order status, shipping information, and any other relevant details to build trust and improve the overall shopping experience. ### 8. Security considerations when using payment links in video shopping Payment links play a crucial role in ensuring secure transactions in video shopping. As such, it is important to take security measures to protect both the buyer and seller. Here are some security considerations when using payment links in video shopping: 1. SSL Certificates: It is essential to use SSL certificates to encrypt data transmitted between the buyer and seller. This helps prevent unauthorized access and protects sensitive information like credit card details. 2. Fraud Detection: Implementing fraud detection tools can help identify suspicious transactions and prevent fraudulent activities. These tools analyze patterns and behavior to detect anomalies and flag potential fraud cases. 3. Two-Factor Authentication: Adding an extra layer of authentication through two-factor authentication can further enhance security. This requires users to provide additional information beyond their password, such as a one-time code sent to their mobile device or email address. 4. Regular Audits: Conduct regular security audits to identify vulnerabilities and weaknesses in your payment link system. This helps ensure that your platform remains secure and up-to-date with the latest security protocols. 5. Compliance with Regulations: Ensure compliance with relevant regulations, such as PCI-DSS (Payment Card Industry Data Security Standard), to minimize the risk of data breaches and protect customer information. 6. Employee Training: Provide regular training to employees on security best practices and the importance of maintaining a secure environment. This includes educating them on phishing attacks, social engineering tactics, and other common threats. 7. Monitoring and Logging: Implement monitoring and logging tools to track all transactions and activity within your payment link system. This allows you to quickly identify and respond to any suspicious behavior or potential breaches. 8. Data Encryption: Use strong encryption methods to protect sensitive data during transmission and storage. This ensures that even if an attacker gains access to the data, they will not be able to read or interpret it. 9. Secure Hosting: Host your payment link system on secure servers with regular backups and redundancy options. This helps minimize downtime and ensures that your platform remains available and secure. 10. Penetration Testing: Conduct periodic penetration testing to assess the vulnerability of your payment link system. This involves simulating real-world attacks to identify potential weaknesses and areas for improvement. 9. Conclusion In conclusion, payment links provide a seamless and secure way to facilitate transactions in video shopping. By integrating them into your platform, you can enhance the overall user experience and increase sales. It is important to follow best practices and take security measures to ensure the safety of your users' information. As video shopping continues to grow in popularity, payment links will play a crucial role in its success. Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Get Payment Links today](/platforms/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-worldpay/ --- # Payment Links for Worldpay: Send Checkout Links Without Leaving Worldpay | Shuttle > Send branded payment links through your Worldpay account. No switching provider. # Payment Links for Worldpay: Send Checkout Links Without Leaving Worldpay By Nick Dunse, January 22, 2026 Send branded payment links through your Worldpay account. No switching provider. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem Worldpay is the UK's largest payment processor. Millions of merchants rely on it for card-present and card-not-present transactions. The infrastructure is solid. The reach is massive. But when a Worldpay merchant needs to send a payment link to a customer -- for a phone order, an outstanding invoice, or a booking deposit -- the options are limited. Worldpay doesn't offer a simple, merchant-facing payment links product. What Worldpay does offer is a virtual terminal and e-commerce gateway integration. Both require either a developer or someone manually keying in card numbers over the phone. Neither is practical when you just need to text a customer a link to pay. Switching providers isn't the answer. Worldpay merchants have negotiated rates, existing integrations, and finance teams that know the platform. They need payment links added to what they already have -- not a new provider. ## How Payment Links Work with Worldpay Shuttle connects to your Worldpay Access account via REST API. Your payment processing stays with Worldpay. Shuttle adds the payment links capability on top. When you create a payment link in Shuttle, the checkout page is fully branded to your business. You send it via SMS, email, or chat. The customer clicks, enters their card details on your branded page, and the transaction is processed through your Worldpay account. From Worldpay's perspective, it looks like any other card-not-present transaction. Settlement, reconciliation, and reporting all work the same way. Your finance team sees the transactions in the Worldpay portal as normal. - Connect your Worldpay Access account using your API credentials. - Create a payment link in the Shuttle dashboard -- set amount, currency, and reference. - Brand the checkout page with your business logo, colours, and terms. - Send the link to your customer via SMS, email, or chat. - Customer pays on the branded page. Transaction processes through Worldpay. Settlement unchanged. ## What You Get - Branded checkout pages: Your brand on every payment link -- not a generic Worldpay page. - SMS, email, and chat delivery: Send payment links through the channel your customer prefers. - Link tracking dashboard: See link status in real time -- sent, opened, viewed, paid, expired. - Cards and digital wallets: Accept Visa, Mastercard, Amex, Apple Pay, and Google Pay through your Worldpay account. - No developer needed: Operations teams create and send links without writing code. - Partial payments and deposits: Collect deposits, balance payments, or split amounts across multiple links. - PCI compliance built in: Card data never touches your systems. Shuttle's checkout is PCI DSS Level 1. ## Who Uses This - Insurance brokers collecting premiums and policy renewals via SMS. - Travel agents sending deposit and balance payment links to customers booking holidays. - Professional services firms emailing payment links with their invoices. - Phone order businesses that want to stop taking card numbers over the phone. - Field service companies sending payment links on-site via mobile. ## Pricing and Setup Shuttle Payment Links costs $49 per month. Your Worldpay transaction rates stay the same -- Shuttle adds no surcharge on top. Setup takes minutes. Connect your Worldpay Access API credentials, brand your checkout page, and start sending links. No integration project required. No developer needed. ## FAQ Do I need to leave Worldpay? No. Shuttle connects to your existing Worldpay account. You keep your rates, your settlement, and your Worldpay relationship. Will customers see Shuttle? No. The checkout page is fully white-labelled. Customers see your business name, logo, and brand colours. What payment methods can I accept? Cards (Visa, Mastercard, Amex) and digital wallets (Apple Pay, Google Pay) -- all processed through your Worldpay account. How does settlement work? Transactions settle to your bank account through Worldpay on your existing schedule. Nothing changes. Add payment links to your Worldpay account -- without changing provider. Learn more about Payment Links. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Add payment links to your Worldpay account](/contact) - [Learn more about Payment Links](/use-cases/payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-for-xendit/ --- # Payment Links for Xendit: Send Branded Checkout Links for Southeast Asian Merchants | Shuttle > Add branded payment links to your Xendit account. Send checkout links via SMS, email, or chat -- keep your existing Xendit setup. No migration required. # Payment Links for Xendit: Send Branded Checkout Links for Southeast Asian Merchants By Shuttle, January 23, 2026 Add branded payment links to your Xendit account. Send checkout links via SMS, email, or chat -- keep your existing Xendit setup. No migration required. Send payment links with any gateway Connect your existing payment provider and start sending payment links in minutes. ## The Problem: Xendit's Payment Links Are Too Basic Xendit is the go-to payment processor for Southeast Asia -- strong in Indonesia, the Philippines, and across the region. Xendit does offer basic payment links, but merchants quickly hit the limits. Branding options are minimal, multi-channel distribution is clunky, and you can't customise the checkout experience to match your brand. For merchants selling via social media, WhatsApp, or marketplaces, the current Xendit payment link feels like an afterthought rather than a real product. ## How Shuttle Payment Links Work with Xendit Shuttle enhances your Xendit setup with fully branded, customisable payment links. Your transactions still process through Xendit -- Shuttle just upgrades the payment link experience. - Connect your Xendit account to Shuttle using your API keys. - Create a payment link with full branding control -- your logo, colours, custom fields, and preferred payment methods. - Distribute the link via SMS, WhatsApp, Instagram DM, email, or embed it on your website. - Your customer clicks the link and pays on a branded checkout page that supports local SE Asian payment methods. - The payment processes through Xendit. Track it in both Shuttle's dashboard and your Xendit reports. Shuttle enhances Xendit -- it doesn't replace it. Your Xendit rates, local payment method support, and settlement all stay the same. ## What You Get Branded checkout pages -- every payment link opens a checkout page with your logo, colours, and business name. Your customers see your brand, not a generic payment form. Multiple payment methods -- accept cards, digital wallets, and local payment methods through a single link. Customers choose how they want to pay. Send anywhere -- share payment links via SMS, email, WhatsApp, social media, QR codes, or embed them on your website. Meet your customers where they are. Dashboard and reporting -- track every payment link in real time. See who's paid, who hasn't, and export data for reconciliation with your Xendit reports. Recurring and partial payments -- create payment links for deposits, instalments, or recurring charges. Flexible enough for any payment scenario. No code required -- create and send payment links from a simple dashboard. No developers, no API integration, no technical setup. ## Who Uses Payment Links with Xendit? - Social commerce sellers -- send branded payment links via WhatsApp, Instagram, and LINE to close sales from social media conversations. - Indonesian marketplace merchants -- collect payments for off-platform deals and custom orders via link. - Philippine service providers -- send payment links for professional services, tutoring, and freelance work. - Travel agencies -- collect deposits and final payments for tour packages across Southeast Asia. - D2C brands -- offer a premium checkout experience for direct sales, flash sales, and pre-orders. ## Getting Started Shuttle charges a small per-transaction fee on top of your Xendit processing rates. No monthly fees, no setup costs, and no minimum volumes. Go live in under a day. Connect your Xendit API keys, configure your branding, and start creating payment links immediately. All you need is an active Xendit merchant account. Shuttle adds the branded payment link layer -- hosted checkout, distribution tools, and analytics are all included. ## Frequently Asked Questions ### Does Shuttle support local payment methods in Southeast Asia? Yes. Shuttle processes through your Xendit account, so all payment methods enabled on your Xendit setup -- including bank transfers, e-wallets, and local cards -- are available on your payment links. ### Can I send payment links via WhatsApp? Absolutely. Shuttle generates shareable links and QR codes that you can send via WhatsApp, LINE, SMS, email, or any messaging platform your customers use. ### Is the checkout page available in local languages? Shuttle's checkout pages can be configured for your target market. Combined with Xendit's local payment method support, your customers get a familiar, localised payment experience. ### What currencies are supported? Shuttle supports the currencies available through your Xendit account, including IDR, PHP, and other Southeast Asian currencies. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/ --- # Invoice Payment Links: How to Get Paid Faster on Every Invoice | Shuttle > How to add payment links to invoices so customers pay in one click. Covers setup, best practices, and why invoice payment links reduce DSO by 30% or more. # Invoice Payment Links: How to Get Paid Faster on Every Invoice By Nick Dunse, January 23, 2026 How to add payment links to invoices so customers pay in one click. Covers setup, best practices, and why invoice payment links reduce DSO by 30% or more. Talk to us Make enabling payments for your platform and merchant users easy. Late invoice payments cost businesses time and cash flow. The average B2B invoice takes 34 days to get paid, and chasing overdue invoices eats into hours your team could spend on actual work. Invoice payment links fix this by giving your customer a single click path from invoice to payment -- no logging into portals, no phone calls, no cheques in the post. This guide covers what invoice payment links are, how to add them to your invoices, and the practical steps to reduce your days sales outstanding (DSO) by 30% or more. ## What Are Invoice Payment Links? An invoice payment link is a URL embedded in your invoice -- whether it is a PDF, email, or accounting software output -- that takes the customer directly to a hosted checkout page. The customer clicks the link, enters their card details (or selects another payment method), and the payment is processed immediately. Unlike traditional invoicing where the customer has to set up a bank transfer or post a cheque, payment links remove every friction point between receiving an invoice and paying it. The link can be pre-filled with the invoice amount, reference number, and customer details so there is nothing for them to type. A typical invoice payment link includes: - Pre-filled amount -- matches the invoice total so the customer cannot underpay - Invoice reference -- automatically tagged for reconciliation - Multiple payment methods -- card, bank transfer, or digital wallet depending on your provider - Hosted checkout page -- branded to your business, secured by your payment provider ## Why Invoice Payment Links Reduce DSO Days sales outstanding (DSO) measures how long it takes to collect payment after invoicing. For most businesses, the biggest contributor to high DSO is not unwillingness to pay -- it is friction. The customer opens your invoice, intends to pay, but has to find your bank details, log into their banking app, type in the amount and reference, and submit. Each step is an opportunity to get distracted and forget. Payment links compress that entire process into a single click. Here is what the data shows: - 30-50% reduction in DSO -- businesses that add payment links to invoices typically see average payment times drop from 30+ days to under 15 days - 60-70% of link payments happen within 24 hours -- customers pay when the invoice is fresh, not weeks later - Fewer payment errors -- pre-filled amounts and references eliminate miskeyed transfers and missing remittance details - Less time chasing payments -- your accounts team spends less time on follow-up emails and phone calls The principle is simple: the easier you make it to pay, the faster people pay. Payment links are the lowest-friction option available for invoice collection. ## How to Add Payment Links to Invoices The exact process depends on your invoicing software and payment provider, but the general workflow is the same across platforms. ### Step 1: Choose a Payment Link Provider You need a payment provider that supports hosted payment links. This means they generate a unique URL for each payment that lands on a secure, PCI-compliant checkout page. Look for a provider that supports: - Custom branding on the checkout page - Pre-filled amounts and reference fields - Multiple payment methods (card, bank transfer, digital wallets) - API access for automated link generation - Webhook notifications when a payment is completed Shuttle Global provides all of the above through its Payment Links product, with no-code link generation and API integration for businesses that want to automate. ### Step 2: Generate a Payment Link for Each Invoice There are two approaches depending on your volume: Manual (low volume): Log into your payment provider dashboard, create a new payment link, set the amount and reference to match your invoice, and copy the URL. Automated (higher volume): Use your payment provider's API to generate links programmatically. Your invoicing system creates the invoice, calls the API to generate a payment link with the correct amount and reference, and embeds it in the invoice automatically. This is the approach most businesses should aim for once they are sending more than 20-30 invoices per month. ### Step 3: Embed the Link in Your Invoice Where you place the payment link matters. Tested approaches that work: - Email invoices: Add a prominent "Pay Now" button at the top of the email, above the invoice details. Repeat the link at the bottom. A button converts better than a plain text URL. - PDF invoices: Add a clickable hyperlink near the payment terms section. Include a QR code as well -- customers viewing a printed PDF can scan it with their phone to pay. - Accounting software (QuickBooks, Xero, FreshBooks): Most accounting platforms support custom fields or notes on invoices. Add the payment link there. Some platforms like QuickBooks have native payment link integrations. ### Step 4: Set Up Payment Notifications Configure webhooks or email notifications so your team knows the moment an invoice is paid. This closes the loop on reconciliation -- the payment comes in, your system marks the invoice as paid, and nobody has to manually check bank statements. ## Payment Link Best Practices for Invoicing Adding a payment link to your invoice is the first step. These practices will improve your collection rates further: Make the link the most visible element. Use a button with a contrasting colour rather than a plain text URL. The "Pay Now" button should be the first thing the customer sees when they open the invoice. Pre-fill everything. The payment link should already contain the amount, currency, invoice reference, and customer name. The customer should not have to enter anything except their payment details. Set link expiry dates. Align the link expiry with your payment terms. If your terms are net 30, set the link to expire after 35 days. This prevents stale links from being used months later at outdated amounts. Send reminders with the link. If the invoice is not paid within a few days, send a follow-up email with the same payment link. Automated reminders at day 7, 14, and 21 are standard and effective. Brand your checkout page. The hosted checkout should display your company logo, colours, and name. Customers are more likely to complete payment when they recognise the brand on the payment page, and less likely to mistake it for a phishing attempt. Offer multiple payment methods. Card payments are convenient, but some customers prefer bank transfers for larger amounts. A good payment link page gives the customer options rather than forcing a single method. ## Security and PCI Compliance Any time you collect card payments, PCI DSS compliance applies. The advantage of hosted payment links is that your business never touches card data directly -- the payment provider handles that on their PCI-compliant infrastructure. Here is what to verify with your payment link provider: - PCI DSS Level 1 certification -- the highest level, required for providers processing over 6 million transactions annually - HTTPS on all checkout pages -- this should be non-negotiable, but check - Tokenisation -- card details are replaced with a token so sensitive data is never stored on your systems - 3D Secure (3DS) support -- adds an authentication step that reduces fraud and shifts liability to the card issuer Because payment links use hosted checkout pages, your business qualifies for the simplest PCI self-assessment questionnaire (SAQ A). This means minimal compliance overhead compared to collecting card details on your own website or over the phone. For more on how payment gateways handle security, see our glossary. ## Invoice Payment Links vs Traditional Payment Methods How do payment links compare to the methods businesses traditionally include on invoices? Bank transfer (BACS/ACH). The customer has to log into their banking app, find your details, type the amount, and add a reference. Errors are common -- wrong amounts, missing references, payments to the wrong account. Average time to payment: 15-30 days. With a payment link, the customer clicks and pays in under 60 seconds. Cheque. Still used in some industries, but adds days of postal time plus manual processing. Average time to clear: 5-7 business days after receipt, and you might wait weeks for the cheque to arrive. Payment links eliminate this entirely. Phone payment. Taking card details over the phone works but brings PCI compliance complexity and requires staff availability. Payment links let the customer pay at any time without involving your team. Customer portal. Some businesses require customers to log into a portal to view and pay invoices. This adds friction -- the customer needs to remember credentials, navigate the portal, and find the right invoice. Payment links skip straight to payment with a single click. The pattern is consistent: every additional step between "customer sees invoice" and "payment is made" increases the time to collection and the risk of non-payment. Payment links minimise those steps. ## How Shuttle Payment Links Work Shuttle Global provides payment links as part of its payments infrastructure. Here is how they work for invoice collection: - Generate via dashboard or API. Create a payment link manually from the Shuttle dashboard, or use the API to generate links automatically from your invoicing system. - Branded checkout. The hosted payment page carries your branding -- logo, colours, and company name -- so customers know they are paying you, not an unfamiliar third party. - Multi-currency support. Invoice international customers in their local currency. The payment link handles conversion and settlement automatically. - Real-time webhooks. Get notified the instant a payment completes. Integrate with your accounting software to auto-reconcile invoices. - PCI DSS Level 1. Shuttle handles all card data on PCI-compliant infrastructure. Your business stays on SAQ A -- the simplest compliance path. Whether you send 10 invoices a month or 10,000, the setup is the same. Businesses using Shuttle payment links on invoices report average payment times dropping from weeks to days. ## Get Paid Faster on Every Invoice Adding payment links to your invoices is the single most effective change you can make to speed up collections. It takes minutes to set up and the impact on cash flow is immediate. Start collecting payments with Shuttle -- or book a demo to see how payment links work with your invoicing setup. ## Related Reading - How to Add a Pay Now Button to Your Invoices - Payment Reminder Email Templates (With Pay Now Links) - DSO Benchmarks by Industry UK (2026) Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links product](/guides/take-payments-online/payment-links/) - [payment gateways](/glossary/payment-gateway/) - [Start collecting payments with Shuttle](/merchants/) - [book a demo](/discovery/) - [How to Add a Pay Now Button to Your Invoices](/guides/pay-now-button-invoices/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [DSO Benchmarks by Industry UK (2026)](/guides/dso-benchmarks-uk/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/ --- # Travel Payment Solutions: How Agencies Collect Payments Faster | Shuttle > How travel agencies and OTAs collect payments faster -- payment links, phone payments, and multi-currency processing without building a payment stack. # Travel Payment Solutions: How Agencies Collect Payments Faster By Nick Dunse, January 24, 2026 How travel agencies and OTAs collect payments faster -- payment links, phone payments, and multi-currency processing without building a payment stack. Talk to us Make enabling payments for your platform and merchant users easy. Travel agencies handle payments differently from almost every other industry. Deposits, split payments, multi-currency pricing, last-minute phone bookings, supplier payouts in foreign currencies -- the list of edge cases is long, and most payment systems were not built for any of them. The result: agencies lose bookings to payment friction. A customer calls to book a holiday package, but the agent cannot take a card payment over the phone securely. A deposit link gets emailed, but it expires or the customer abandons because the checkout page does not support their preferred currency. A group booking requires three separate payments from different cardholders, and the agency has no way to track which portions are settled. This guide covers practical travel payment solutions -- how agencies and OTAs collect payments faster using payment links, phone payments, and multi-currency processing without building a payment stack from scratch. ## Why Travel Agency Payment Systems Are Different A standard e-commerce checkout assumes a single buyer, a single currency, and a single payment for the full amount. Travel breaks all three assumptions. ### Deposits and Balance Payments Most travel bookings require a deposit at the time of booking -- typically 20-30% of the total -- with the balance due weeks or months before departure. This means every booking generates at least two payment events, often against different cards. Your payment system needs to handle partial payments, track outstanding balances, and send automated reminders when the balance is due. ### Multi-Currency Pricing A UK-based agency selling holidays in Europe, Southeast Asia, and the Caribbean is quoting prices in GBP while paying suppliers in EUR, THB, and USD. Customers increasingly expect to pay in their own currency too. Without multi-currency processing built into the payment flow, agencies either absorb exchange rate margins or pass on poor conversion rates that make their prices look uncompetitive. ### Phone Bookings and Manual Payments Despite the shift to online booking, a significant share of travel is still booked by phone -- particularly complex itineraries, group travel, luxury holidays, and last-minute trips. Many agencies still take card numbers over the phone and key them into a terminal, which is a PCI compliance liability. Others ask customers to call back and pay online, which adds friction and loses conversions. ### Group Bookings and Split Payments Group holidays, stag weekends, and corporate travel often involve multiple people paying separately for a single booking. The organiser books for ten people, then needs nine others to pay their share. Without a system that supports split payments and tracks each contributor, agencies end up chasing payments manually over email and spreadsheets. ## How to Automate Secure Payments in Travel Agencies Automating payment collection does not mean replacing your sales team with a checkout page. It means giving your team better tools so they can close bookings faster and spend less time chasing payments. Here are the three approaches that work best for travel. ### Payment Links for Deposits, Balances, and Group Collections Payment links are the simplest way to collect travel payments without building an online booking engine. An agent creates a payment link for the exact amount due -- a deposit, a balance payment, or an individual share of a group booking -- and sends it to the customer via email, SMS, or WhatsApp. The customer clicks the link, lands on a branded hosted checkout page, pays by card or bank transfer, and gets an instant confirmation. The agent sees the payment arrive in real time. No card numbers exchanged over the phone. No manual reconciliation. For travel agencies specifically, payment links solve several problems at once: - Deposit collection -- Send a link for the deposit amount immediately after the customer confirms they want to book. The booking is secured in minutes, not hours. - Balance reminders -- Generate a new link for the outstanding balance and send it with a reminder email when the due date approaches. No phone call required. - Group payments -- Create individual payment links for each member of a group booking. Send them directly or let the organiser distribute them. Track exactly who has paid. - Multi-currency -- Present the payment in the customer's preferred currency with competitive exchange rates handled at the payment layer. ### Voice and Phone Payment Collection Phone bookings are not going away in travel. Complex itineraries, high-value holidays, and nervous first-time travellers all prefer speaking to a human. The problem is not the phone call -- it is how the payment is collected. There are two modern approaches to collecting secure payments over the phone: DTMF (keypad) payments. The agent stays on the line while the customer enters their card details using the phone keypad. The digits are captured by the payment system, not by the agent. The agent never hears or sees the card number, which keeps you PCI compliant. The call is not interrupted -- the agent can confirm the payment went through and continue the conversation. Mid-call payment links. While on the call, the agent sends a payment link via SMS. The customer taps the link on their phone, completes the payment on a secure checkout page, and the agent gets notified immediately. This works well when customers are uncomfortable entering card details by keypad or when the payment involves 3D Secure authentication. Both approaches eliminate the biggest risk in phone-based travel sales: agents handling raw card data. For agencies processing bookings over the phone, this is not optional -- it is a PCI DSS requirement. ### AI Voice Payments for High-Volume Travel Operations Larger travel companies -- OTAs, tour operators with call centres, and agencies handling hundreds of calls daily -- are starting to use AI voice agents to collect payments. An AI agent can handle balance payment calls, confirm booking details, and collect the payment via DTMF, all without a human agent on the line. This is particularly effective for hotels and travel companies that process large volumes of balance payment calls -- a repetitive task that ties up experienced agents who could be selling instead. The AI handles the routine collection calls while human agents focus on new bookings and complex itineraries. ## B2B Payments for Travel Agencies: Supplier and Platform Complexity Travel payments are not just about collecting from customers. Agencies also need to pay suppliers -- hotels, airlines, ground handlers, insurance providers -- often in different currencies, on different timelines, and through different payment rails. This creates a two-sided payment problem: - Customer-facing: Collect deposits and balances in the customer's currency via card, bank transfer, or payment link. - Supplier-facing: Pay suppliers in their local currency, often via bank transfer, on net-30 or net-60 terms. Many agencies run these two flows through completely separate systems -- one for card payments, another for banking, a spreadsheet for reconciliation. A proper travel payment system connects both sides, so you can see the margin on each booking in real time and automate supplier payouts when customer payments clear. For travel technology platforms building booking systems that other agencies use, this complexity multiplies. You need to handle payments on behalf of your customers (the agencies), split funds between the platform and the agency, and ensure the whole flow is compliant. This is where payment gateway infrastructure matters -- you need a layer that can route payments, handle multi-currency, and manage the commercial split without the platform becoming a regulated payment entity. ## How to Streamline Secure Payments in Travel Agencies Faster payment collection starts with removing the manual steps between a customer saying "yes" and the payment landing in your account. Here is what a streamlined travel payment workflow looks like in practice. ### Step 1: Quote and Confirm The agent finalises the itinerary and price with the customer -- by phone, email, or in person. As soon as the customer confirms, the agent generates a payment link for the deposit amount directly from their booking system or CRM. ### Step 2: Collect the Deposit The payment link is sent immediately via the customer's preferred channel -- email, SMS, or WhatsApp. If the customer is on the phone, the agent sends the link during the call and confirms payment in real time. If the customer prefers to pay by keypad, the agent initiates a DTMF payment flow without leaving the call. ### Step 3: Automate Balance Collection The balance payment date is logged in the system. As the due date approaches, the customer receives an automated reminder with a new payment link for the outstanding balance. No manual follow-up. No phone tag. If the customer does not pay by the deadline, the system escalates -- another reminder, or a flag for the agent to call. ### Step 4: Reconcile and Report Every payment is linked to a booking reference. Deposits, balance payments, refunds, and chargebacks are all tracked in one place. No more cross-referencing bank statements with booking spreadsheets. End-of-month reporting takes minutes instead of days. ## Security and PCI Compliance for Travel Payments Travel agencies are high-value targets for payment fraud. Average transaction values are high (often four figures), bookings are frequently made remotely, and many agencies still handle card data manually. PCI DSS compliance is not optional if you accept card payments. The requirements apply whether you process ten payments a month or ten thousand. For agencies, the fastest route to compliance is to ensure card data never touches your systems: - Payment links route customers to a hosted checkout page. Card data is captured by the payment provider, not your website or booking system. - DTMF phone payments ensure card digits entered by keypad bypass your telephony system entirely. The agent never hears the numbers. - Tokenisation stores a token instead of the actual card number, so repeat payments (like balance collection for the same booking) do not require the customer to re-enter their details. These approaches dramatically reduce your PCI scope. Instead of securing every system that touches card data -- your CRM, your phone system, your email -- you limit the exposure to the payment provider's infrastructure, which is purpose-built for it. ## Choosing Travel Industry Payment Solutions Not every payment provider understands travel. Before committing to a solution, check whether it supports the specific requirements travel agencies face: - Partial payments -- Can you collect a deposit now and the balance later, against the same booking reference? - Multi-currency -- Can customers pay in their own currency? Can you settle with suppliers in theirs? - Phone payments -- Does it support PCI-compliant payment collection over voice channels, not just online? - Payment links -- Can agents generate and send branded payment links in seconds, without developer involvement? - Reconciliation -- Does the system link payments to booking references automatically, or are you still matching transactions manually? - Split payments -- Can multiple people pay towards the same booking independently? - Refund handling -- Can you process partial refunds (e.g. one cancelled flight within a package) without refunding the entire booking? If your current provider cannot tick most of these boxes, you are probably working around its limitations rather than benefiting from it. ## How Shuttle Helps Travel Agencies Collect Payments Shuttle provides the payment infrastructure that travel agencies and travel tech platforms need -- without requiring you to build or maintain a payment stack. - Payment Links -- Generate branded payment links for deposits, balances, and group bookings. Send via email, SMS, or WhatsApp. Customers pay on a hosted checkout page with multi-currency support. - Voice Checkout -- Collect PCI-compliant payments over the phone via DTMF or mid-call payment links. Integrates with your existing phone system or call centre platform. - Embedded Payments -- For travel tech platforms, embed white-label payment processing into your booking system. Handle payments on behalf of your agency customers without becoming a payment facilitator. - Multi-PSP Coverage -- Route transactions through the optimal processor for each currency and region. No single-provider lock-in. Whether you are a travel agency collecting deposits over the phone, an OTA processing thousands of online bookings, or a travel tech platform that needs to embed payments into your product -- Shuttle provides the infrastructure layer so you do not have to build it. Ready to streamline your travel payment collection? Create your Shuttle account and start collecting payments in minutes -- or book a demo to see how Shuttle works for travel. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [PCI compliance](/glossary/pci-dss-level-1/) - [Payment links](/guides/take-payments-online/payment-links/) - [secure payments over the phone](/guides/voice-payments/) - [PCI DSS](/glossary/pci-dss-level-1/) - [DTMF](/guides/dtmf-payments/) - [hotels and travel companies](/guides/ai-voice-payments-hotels-travel/) - [payment gateway](/glossary/payment-gateway/) - [Create your Shuttle account](/merchants/) - [book a demo](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payment-operation/ --- # The Cheapest Operation not the Cheapest Processing | Shuttle > Why the cheapest processing fees don't mean the cheapest operation -- hidden costs of payment infrastructure that merchants overlook. # The Cheapest Operation not the Cheapest Processing By Nick Dunse, January 9, 2023 Why the cheapest processing fees don't mean the cheapest operation -- hidden costs of payment infrastructure that merchants overlook. Running a payments operation within your business, regardless of size, is more than just the acceptance of a payment. We speak to many merchants who think that the cheapest payment processing is working for them, but in reality they have the following issues that are costing them more when you look at their operation holistically: - Hidden fees from from various parts of the payment processing process - Back office processes like reconciliation - Lack of integrations into systems like POS, Order Management, ERP etc - Not acquiring locally when selling internationally - On the wrong pricing model to start with - Not using fee reducing technologies like Network Tokens or fraud prevention tools - Settling in the wrong currency or not leveraging FX opportunities - Acceptance rates - Compliance costs A retail payments operation example of inefficiency We spoke with a retailer who had tens of physical stores, as well as selling online. Let's just say their approach to payments acceptance was 'old skool.' It turned out that in each one of their stores they had dumb terminals that were not connected to the POS, but they had the cheapest tech. and processing rates - hurray... A sales person would manually enter the payment amount (avg. sale was £700) into the terminal, then at the end of the day they would have to reconcile the days sales into the order management and accounting system, then find the payments on their processing statement and reconcile those on a monthly basis. 🤯 So we asked how much does that business process cost on a monthly basis, they had no idea, but clearly it was more expensive than spending a couple more basis points to get a modern connected solution. Consider the overall cost of your payments operation Firstly you want to audit your payment operation, map it out right through to the management accounting work. There will be some black holes that you don't understand, ask other team members and your payment service provider to help you get clarity on what's happening and how much it costs your organisation. Once you have the map, ask yourself and your team is this efficient, could we do it better and cheaper? Fix this first Whether your point of sale is in-store or online. Get your checkout connected to your Order Management system, so that a payment gets recorded against an order. If you have terminal hardware, make sure they're smart and connected to POS and OM system. You need to build a picture of an order and the customer. Second fix Make sure you have automatic accounting reconciliation for payments, typically you want to do this with a management account approach. Basically, sync your settlement from payments into your accounts, deduct fees as cost of sale. Then address the current fee structure that you're paying Get the statements from your payment gateway and or merchant acquire (processor). I would recommend asking a statement of absolutely every fee you're paying to these parties including: - Hardware rental - Payment Gateway fees - Interchange fees - Any silly breakdowns like PCI fees, or whatever your providers are charging you What's the true cost of doing business here? Ask for volume discounts. Look at domestic vs international transactions, should you be on a blended rate or interchange ++ pricing? Finally you can look at clever things Once you've fixed your internal processes, have an understanding of the cost of the current operation and negotiated a better fee structure you can finally consider optimisation - which for some can be a massive game changer. Ask Shuttle about these things they can literally make you money if you know what to do. - Reducing processing fees with fraud prevention - Network tokenisation - Local acquiring - Improving acceptance rates (in everyone's interest!) - Multi-currency accounts - FX forwarding Conclusion Many view payments as a necessary evil to do business, it used to be exciting to get paid but now for many sellers it's become a painful, poorly organised operation. Merchants must look to leverage payments to do business more efficiently at the very least. CFO, COO's and internal payments team need to make it a priority AND payment service providers need to pull their finger out and help their merchants sell more for less. ## Related Reading Explore More ### Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePayment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions→](/guides/payment-operations-at-scale/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payment-reminder-email-templates/ --- # Payment Reminder Email Templates (With Pay Now Links) | Shuttle > 8 copy-paste payment reminder templates for every stage -- from friendly first nudge to letter before action. Each includes a pay-now link. # Payment Reminder Email Templates (With Pay Now Links) By Shuttle Team, March 7, 2026 8 copy-paste payment reminder templates for every stage -- from friendly first nudge to letter before action. Each includes a pay-now link. Talk to us Make enabling payments for your platform and merchant users easy. ## Why Payment Reminders Work Better With a Pay Now Link Most payment reminder emails ask the customer to pay. Very few make it easy. A typical reminder says "Please pay invoice #1234 by bank transfer to sort code XX-XX-XX, account XXXXXXXX, reference INV-1234." That's five pieces of information the customer has to copy into their banking app. Every step is a reason to do it later. Now compare: "Pay invoice #1234 now: [link]." One click. Card, bank transfer, Apple Pay -- whatever they prefer. Done in 60 seconds. Businesses that include payment links in their invoices report 30-50% reductions in Days Sales Outstanding. The reminder email is where this has the biggest impact -- because you're reaching someone who already intended to pay but hasn't got around to it. Remove the friction, and they pay immediately. Every template below includes a payment link placeholder. Replace `[PAYMENT LINK]` with your actual link URL. ## Before the Due Date: Friendly Reminder Send this 3-5 days before the invoice is due. It's not a chase -- it's a courtesy. ### Template 1: Pre-Due Date Reminder > Subject: Invoice #[NUMBER] -- due on [DATE] Hi [NAME], Just a quick reminder that invoice #[NUMBER] for [AMOUNT] is due on [DATE]. You can pay securely online here: [PAYMENT LINK] If you've already arranged payment, please ignore this email. Let me know if you have any questions. Thanks, [YOUR NAME] [COMPANY] Why it works: No pressure. The payment link removes the "I'll do it when I have the bank details in front of me" barrier. ## On the Due Date ### Template 2: Due Today > Subject: Invoice #[NUMBER] -- payment due today Hi [NAME], Invoice #[NUMBER] for [AMOUNT] is due today ([DATE]). Pay now: [PAYMENT LINK] Payment can be made by card, bank transfer, or Apple Pay. If you have any queries about this invoice, please reply to this email. Best regards, [YOUR NAME] [COMPANY] Why it works: Direct, not aggressive. States the fact (due today) and provides the easiest possible route to pay. ## 7 Days Overdue: First Follow-Up This is the most important email in the sequence. Most overdue invoices get paid in response to the first follow-up -- if it's easy enough. ### Template 3: Friendly First Chase > Subject: Friendly reminder -- invoice #[NUMBER] is overdue Hi [NAME], I hope you're well. I wanted to flag that invoice #[NUMBER] for [AMOUNT] was due on [DATE] and is now 7 days overdue. I appreciate things get busy. You can pay online in under a minute here: [PAYMENT LINK] If there's an issue with the invoice or you'd like to discuss payment, just reply to this email and we'll sort it out. Thanks, [YOUR NAME] [COMPANY] Why it works: Assumes good intent. Offers the payment link as a convenience, not a demand. Opens the door for the customer to raise issues. ### Template 4: First Chase (More Formal) > Subject: Payment overdue -- invoice #[NUMBER] ([AMOUNT]) Dear [NAME], Our records show that invoice #[NUMBER] for [AMOUNT], dated [INVOICE DATE], remains unpaid. The payment was due on [DUE DATE]. To make payment, please use the secure link below: [PAYMENT LINK] If payment has already been made, please disregard this email and accept our apologies for the cross-communication. If there are any queries regarding this invoice, please contact us at [EMAIL/PHONE]. Kind regards, [YOUR NAME] [COMPANY] Why it works: Professional tone for B2B relationships where formality matters. Good for professional services -- law firms, accountancies, consultancies. ## 14 Days Overdue: Second Follow-Up The tone shifts from friendly to firm. You're now explicitly asking for payment. ### Template 5: Firm But Fair > Subject: Second reminder -- invoice #[NUMBER] is 14 days overdue Hi [NAME], This is a second reminder regarding invoice #[NUMBER] for [AMOUNT], which was due on [DUE DATE]. We haven't received payment or heard back from you. Please arrange payment at your earliest convenience: [PAYMENT LINK] If there's a reason payment is delayed, I'd appreciate a quick reply so we can work something out. Thank you, [YOUR NAME] [COMPANY] Why it works: Acknowledges this is the second contact. Asks for communication if there's a problem -- this catches genuine disputes before they escalate. At this stage, consider switching channel. If two emails haven't worked, send the payment link by SMS. Text messages have a 98% open rate versus ~20% for email. See our guide on multi-channel payment collection. ## 30 Days Overdue: Escalation ### Template 6: Final Friendly Notice > Subject: Urgent: invoice #[NUMBER] -- 30 days overdue Dear [NAME], Despite previous reminders, invoice #[NUMBER] for [AMOUNT] (due [DUE DATE]) remains outstanding. This invoice is now 30 days overdue. Please make payment immediately using the link below: [PAYMENT LINK] If we do not receive payment or a response within 7 days, we will need to escalate this matter further. We would prefer to resolve this directly. Please contact me at [EMAIL] or [PHONE] if you wish to discuss a payment arrangement. Regards, [YOUR NAME] [COMPANY] Why it works: Clear consequences without being threatening. Offers a way out (payment arrangement). The payment link is still there -- even at 30 days, making it easy to pay converts a surprising number of overdue invoices. ### Template 7: Formal Escalation Warning > Subject: Overdue account -- invoice #[NUMBER] requires immediate attention Dear [NAME], We have contacted you on [NUMBER OF TIMES] occasions regarding the outstanding balance of [AMOUNT] on invoice #[NUMBER], dated [INVOICE DATE]. Payment was due on [DUE DATE]. Under the Late Payment of Commercial Debts (Interest) Act 1998, we are entitled to charge statutory interest of 8% above the Bank of England base rate on overdue commercial debts, plus a fixed compensation of [£40/£70/£100 depending on debt size]. We have not yet applied these charges and would prefer to resolve this amicably. Please arrange payment within 7 days: [PAYMENT LINK] If payment is not received by [DATE + 7 DAYS], we will begin formal recovery proceedings. Yours sincerely, [YOUR NAME] [COMPANY] Why it works: References specific UK legislation. The statutory interest mention is a genuine right under UK law -- not a threat, a fact. Many customers pay immediately once they realise interest can be legally applied. For more on this, see our guide on collecting overdue payments in the UK. Note on statutory compensation: Under the Act, you can claim £40 (debts up to £999.99), £70 (£1,000-£9,999.99), or £100 (£10,000+) as fixed compensation, plus 8% + BoE base rate as interest. ## 60+ Days Overdue: Pre-Legal ### Template 8: Letter Before Action > Subject: FINAL NOTICE -- Invoice #[NUMBER] Dear [NAME], Despite repeated attempts to contact you, invoice #[NUMBER] for [AMOUNT] remains unpaid. This balance has been outstanding since [DUE DATE] -- now [NUMBER] days overdue. This is a formal notice that if payment is not received within 14 days of this letter, we will instruct our solicitors to commence recovery proceedings. Any legal costs incurred will be added to the outstanding balance. To avoid further action, please make payment now: [PAYMENT LINK] Alternatively, if you wish to propose a payment plan, contact [NAME] at [EMAIL/PHONE] within 7 days. This is not a step we take lightly, and we remain open to resolving this matter without legal involvement. Yours faithfully, [YOUR NAME] [COMPANY] Why it works: A Letter Before Action (LBA) is a recognised pre-legal step in the UK. It demonstrates you've made reasonable efforts to collect before pursuing legal remedies. Even at this stage, including a payment link converts a significant percentage -- the formality of the letter motivates action, and the link makes it instant. ## Sequence Summary: The Complete Dunning Timeline Pre-due date reminder (#1) Due today (#2) First chase (#3 or #4) Email + SMS Second reminder (#5) SMS/WhatsApp Resend payment link Escalation warning (#6 or #7) Post + email Dunning letter with QR code Legal-adjacent Letter before action (#8) At every stage, the payment link stays the same. One link, every channel, every reminder. See our guide to multi-channel payment collection for channel-specific best practices. ## Tips for Better Payment Reminder Emails - Put the payment link above the fold. Don't bury it at the bottom. The first thing the reader should see is a way to pay. - Include the amount and invoice number in the subject line. This helps the customer identify the invoice without opening the email. - Send from a person, not a no-reply address. Emails from "Sarah at [Company]" get opened more than emails from "accounts@company.com." - Keep it short. Every extra sentence is a reason to stop reading. State what's owed, when it was due, and how to pay. That's it. - Offer multiple payment methods. If your payment link supports cards, bank transfer, Apple Pay, and Open Banking, mention that in the email. - Escalate channels, not just tone. If email isn't working, switch to SMS or WhatsApp before escalating to formal letters. A text message with a payment link at Day 14 often works better than a stern email at Day 30. ## Common Questions ### How many reminders should I send before escalating? Three to four email reminders over 30 days is standard UK practice. After that, switch to formal letters and consider involving a debt recovery service. The key is to have a consistent, documented process -- this matters if you ever need to pursue legal recovery. ### Should I charge late payment interest? In the UK, you have a legal right to charge 8% + BoE base rate on overdue B2B invoices under the Late Payment of Commercial Debts (Interest) Act 1998. Whether you should depends on the relationship -- many businesses mention the right in their terms but only apply it to persistent late payers. ### Can I automate these reminders? Yes. Most accounting software supports basic email reminders. For multi-channel automation (email → SMS → WhatsApp), you'll need a payment link provider that supports all channels. ### What if the customer disputes the invoice? If a customer replies to a reminder with a dispute, pause the dunning sequence for that invoice. Resolve the dispute first, then restart the sequence. Template #3 and #5 both invite the customer to raise issues -- this is intentional. ## Get Paid Faster Templates are a starting point. The real difference is the payment link -- it turns every reminder from "please pay" into "pay now in one click." Shuttle Payment Links work with 40+ gateways, support white-label branding, and deliver via email, SMS, WhatsApp, and QR code. See how it works. ## Related Reading Explore More ### Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment links in their invoices](/guides/pay-now-button-invoices/) - [B2B relationships](/guides/b2b-payment-collection/) - [professional services](/guides/payment-collection-professional-services/) - [multi-channel payment collection](/guides/multi-channel-payment-collection/) - [collecting overdue payments in the UK](/guides/b2b-payment-collection/) - [Dunning letter](/blog/dunning-letter-templates/) - [cards, bank transfer, Apple Pay, and Open Banking](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [accounting software](/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/) - [multi-channel automation](/guides/multi-channel-payment-collection/) - [40+ gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [GuideMulti-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes→](/guides/multi-channel-payment-collection/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payments-are-sexy-again-and-no-longer-boring-but-are-they-still-a-commodity/ --- # Payments are sexy again. But are they still a commodity? | Shuttle > Are payments still a commodity or the next big opportunity? Explore how modern payment infrastructure is transforming SaaS platforms and merchant... # Payments are sexy again. But are they still a commodity? By Nick Dunse, January 25, 2026 Are payments still a commodity or the next big opportunity? Explore how modern payment infrastructure is transforming SaaS platforms and merchant... Talk to us Make enabling payments for your platform and merchant users easy. The past and the present It's 2005 and I'm working on an online retail project selling men's clothes. We're trying to find the best payment provider and back then it was somewhat harder than it is today due to the lack of options. The retailer is based in Hong Kong but also has a UK entity, PayPal was a 'thing' but it wasn't available in the software we were using. We found the original incarnation of 2Checkout to enable end customers to buy from the website using cards and away we went. There wasn't much choice, who knows what fees were being paid, never mind the need to move money around the world, that was nearly 17 years ago! Oh, how times have changed, card payments are everywhere; as far as the end customer is concerned, the same service, same price, with the odd exclusion of AMEX. Even for merchants, the payment service market can now seem like a myriad of similar offers, which in turn has led to a race to the bottom on price. Sure, merchants just want the cheapest price... What merchants really want Or do they? I speak to many merchants every week and many of them are certainly price sensitive, some of them in certain industries and in the latter stages of their career are aggressive on price, but in my experience, they are a dying breed and perhaps card payments along with them. I can tell you that the first thing that merchants are looking for is availability in the platform that they use (just like me 17 years ago), some of them are even willing to pay these platforms tens of thousands of dollars to get the service enabled, which in most cases erodes any fee-saving they might have spent blood and tears negotiating on. That is only after they've found a provider that will give them what they really need... And that is good customer service, it's not until you've been selling and had your money locked up or your account disabled or even repeated transactions fail that you become aware of the need to speak to someone at your payment provider. Fraud checks are a necessity, failed payments are a reality but someone to talk to resolve these issues is not a commonality it would seem. Customer Service is a differentiator That's our first point to raise, there may be more and more payment service providers, ISOs, PayFacs, Neo-banks etc in the market but they are all the same if they can't serve their customers well, they're all bad and you get what you pay for. With a service that supports such a sensitive topic as payments, you would have thought that greater transparency and customer support would be an obvious requirement, but it really isn't. As payment companies grow, compete more in a crowded market they look to automate their human interactions, the topic for how they can improve is for another time, but one thing is clear, that customer support and success is not the same across the board and it's the number one reason merchants approach us looking for a new service provider. Features / Payment methods differentiators In the last few years, my leather wallet has started gathering dust, a lonely vessel left on the mantlepiece now a part of the furniture lucky enough for the occasional outing in my backpack just in case my driving license is called for (BTW driving licenses and passports in digital wallets, backed by blockchain surely!). The reason my wallet is no longer used is because I have all my payment methods in my mobile wallet or I use Google Pay/Amazon Pay/PayPal on my laptop, it's convenient, why would I want to get my card out and type long numbers into a screen!? Believe it or not there are some big-name payment gateways that still don't accept GPay, Apple Pay and PayPal, and you can forget about them incorporating the latest Buy Now Pay Later method. We're seeing merchants and platform providers needing multiple relationships with payment providers so they can offer the options that the end customer wants, driving up conversion rates through convenience. These alternative payment methods are also beating card payments up due to their lower fees and increasingly convenient checkout process. Card payments will soon become the alternative payment method and already are in parts of Europe and India. The market has really been shaken up with new payment methods coming out every week and as we know the regulatory bodies have had to wake up. It seems they're still having their breakfast and once they've read the paper (analogue reference intended) might start to impose some regulations on the new credit providers. One thing is clear that the new payment methods, fee structures and convenience that is now available to consumers and increasingly businesses payments are becoming sexy and no longer a commodity. Connected systems I've already said it, but not every payment service provider is where merchants need them and they are not connected to the systems the merchants use in a way that improves their business. We've seen payments connected to things like Xero for invoices payments and reconciliation purposes, whilst these connections are good they are still scratching the surface of what's possible, they lack functionality and transparency. Whilst other platforms have no connectivity at all and payments is still considered an offline back-office task of transferring money by logging into your bank account, where is my weird little banking login calculator thing anyway... I heard a couple of payment providers recently waxing lyrical about their upcoming pay by link text service that was nearly ready after many years of development. Just say that again to yourself out loud, PAY BY TEXT. 🤣 I just hope it's compatible with Whatsapp, that's all I'm saying. What is certainly interesting is the opportunity that neo-banks might provide. They already have the customer base, the opportunity and cash to launch all-in-one, convenient payment services to merchants. Their challenge is then about go-to-market and getting that functionality embedded in the platforms that merchants use. I can certainly see someone like Revolut heading in this direction and winning, but time is against them, I feel they're still a bit rigid in the movement. It's also a warning to software that want to offer their own payments services, not only are there greater responsibilities, dubious upsides but there's the chance that you'll be slower to keep up with a fast-moving market because it's not your core competency. Without a doubt, the future of payments is via platforms and so the platforms that are connected to your payments services are going to be a differentiator, therefore with more payment products and platforms appearing, payments are no longer a commodity, they're not the same and they're not everywhere. True price as a differentiator Finally, before we conclude let's talk about money. 'My payment provider is offering me 0.5% can you beat that?' As I mentioned at the start, the commoditisation of payments meant a race to the bottom on price. For smaller merchants the fees are really just the list prices offered, for those with more bargaining power prices can range from provider to provider and across alternative payment methods. But the main point I want to draw out is about holistic cost and the total cost of ownership when it comes to payments. When considering the true cost of a service provider and the products that they offer you need to think about: - The processing fees - The hardware fees - The cost saving of connected systems - The increase in conversion Many merchants are making dumb choices, they're not considering a holistic cost or cost vs benefit. Many new payment players offer some serious efficiencies and increase in conversion rates whilst reducing chargebacks. For platforms, what's the cost of not having the right providers, what value is payments really adding if you're not able to provide anything but a transaction. Shuttle provides platforms and their merchants with centralised payments views and insight into what's happening. A quick word about crypto It's still not hit the mainstream and isn't available as a payment method for many but it's coming and it's sexy, I guess. Still a form of wallet and often backed by traditional currencies, but no doubt the crypto economy will gather self-sufficiency soon enough. Again how's it going to go to market and by who? Somebody ask Jack Dorsey for me. Payments are no longer a commodity They've become a differentiator and it's not a one size fits all anymore. It's likely that merchants will be utilizing many software tools in the cloud whilst using multiple payment services to increase checkout conversion and keep the cost of moving money down. There's an opportunity for payments to be embedded and baked in with greater features sets to software and those that are willing to enable that, we believe, will be the winners. Of course, that's what we're here to help with, the right payment services in the right places, increasing transparency in muddy market. Platforms that want payments features, look no further, payment providers that need go to market and embedding get onboard - your customers expect it. ## Related Reading Explore More ### What Are Voice Payments? The Complete Guide ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideWhat Are Voice Payments? The Complete Guide→](/guides/voice-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payments-cost-saas-platforms/ --- # Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) | Shuttle > SaaS companies spend 5-9% of revenue on payments infrastructure -- engineering, compliance, tax, reconciliation. # Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) By shuttle-team, March 3, 2026 SaaS companies spend 5-9% of revenue on payments infrastructure -- engineering, compliance, tax, reconciliation. Talk to us Make enabling payments for your platform and merchant users easy. ## The Number Nobody Tracks The OpenView and Paddle 2023 SaaS Benchmarks Report surveyed 3,500+ private SaaS companies across seven years. One finding stood out: A quarter of SaaS companies spend 5-9% of annual revenue on payments, billing, tax, and compliance infrastructure. And 27% of respondents said they don't track these costs at all. That second number is the more revealing one. If you don't know what payments cost you, you can't make rational build-vs-buy decisions. You can't compare the cost of your current Stripe integration against the cost of adding multi-PSP support. You can't evaluate whether becoming a PayFac makes financial sense. Most SaaS founders assume payments is "2.9% + 30¢ per transaction." That's the processing fee. It's not the infrastructure cost. ## Where the Money Actually Goes ### Engineering Headcount At $2M ARR with a basic Stripe or PayPal setup, Notion Capital's portfolio analysis found companies typically allocate: - 1-2 full-time developers maintaining payments infrastructure - FTE in Finance for manual processing and reconciliation - FTE for tax-related work That's 3-4 people before you hire a single payments specialist. At a fully-loaded cost of £80-120K per head, that's £240-480K per year -- on a £2M revenue base. As the business grows, so does the payment team. By £35M ARR, companies typically need 2 additional FTEs just for billing support load. ### The PayFac Path When a platform decides to own more of the payment stack -- becoming a Payment Facilitator -- the costs escalate: Visa + Mastercard registration £20,000-£50,000 upfront Annual card network renewal £10,000-£25,000/year PCI Level 1 certification £50,000-£200,000 Engineering build (gateway + onboarding + settlement) £400,000-£2,000,000+ Annual payments engineering team (4+ specialists at £150K) £600,000-£1,000,000/year £10,000-£30,000/year Timeline to go live 12-24 months Bain & Company's analysis found that a full PayFac model requires 10+ full-time employees across product, engineering, operations, support, and risk -- with annual costs of £1-3M. The threshold to make PayFac economics work? Multiple independent analyses -- from Stax, Fiska, Nexio, and Bain -- all converge on the same number: £50M+ in annual processing volume. Below that, the fixed costs outweigh the revenue. ### PCI Compliance PCI DSS compliance is a recurring cost that scales with your payment architecture: - Level 3-4 (under 1M transactions/year): £1,000-£20,000 for self-assessment - Level 2 (1-6M transactions): £10,000-£50,000 for validated assessment - Level 1 (6M+ transactions, or any PayFac): £50,000-£200,000 for on-site QSA audit On top of the certification: - Compliance automation platform (Vanta, Drata, Secureframe): £10,000-£80,000/year - Quarterly vulnerability scans: £400-£800/year - Annual penetration testing: £5,000-£30,000 - Engineering time to maintain controls and gather evidence: £5,000-£20,000/year equivalent And the stick: PCI non-compliance penalties start at £5,000-£10,000 per month and escalate to £100,000/month. The average data breach costs £4.88M (IBM/Ponemon 2024). ### The Full Picture Unipaas published a detailed build analysis for full in-house payment infrastructure: Build Cost Onboarding system Underwriting policies AML/compliance monitoring PCI/compliance licensing Acquirer sponsorship Payment gateway integration Merchant management + reporting Total upfront Up to £8,000,000 Annual maintenance £3,000,000/year Even Stripe's own estimate for building a basic payment gateway MVP is £150,000-£250,000 -- and that's initial development only, with no ongoing maintenance, no compliance, and no staffing. ## The Opportunity Cost Is Worse Than the Cash Cost The cash numbers are striking. But the opportunity cost is what kills platform companies. Every engineer maintaining a Worldpay webhook handler is an engineer not building the feature that would close your next enterprise deal. Every sprint spent on PCI remediation is a sprint not spent on your AI capabilities, your analytics dashboard, or your marketplace matching algorithm. Stripe itself employs approximately 3,400 engineers to build and maintain payment infrastructure. When a SaaS company with 30 engineers allocates 4 of them to payments, that's 13% of engineering capacity -- roughly equivalent to what Stripe allocates as a percentage of its total workforce. Except Stripe is a payments company. You're not. The question isn't "can we afford to outsource payments?" It's "can we afford the engineering distraction of not outsourcing them?" ## What the Alternative Looks Like A payment layer replaces the entire build with a single integration: - Multi-PSP routing -- 40+ payment gateways through one API. No per-PSP engineering projects. - PCI compliance carried by the provider -- your PCI scope drops to the minimum level. - Merchant onboarding pre-built -- white-label, self-service, no custom build required. - New channels without new projects -- voice, links, embedded checkout, AI agent payments through the same integration. Integration timeline: 2-4 weeks. Ongoing maintenance: zero dedicated payment engineers. The platform pays per transaction (or revenue share). The math almost always works: even a modest per-transaction fee is less than the fully-loaded cost of 3-4 payment engineers plus PCI compliance plus PSP maintenance. And the engineering capacity freed up? That goes back to building the product that actually differentiates your platform. ## How to Calculate Your Real Payment Infrastructure Cost Most SaaS companies have never done this exercise. Here's the framework: ### Direct Costs - Processing fees -- what you pay your PSP per transaction (the obvious number) - Payment engineering salaries -- fully-loaded cost of every engineer who touches payment code, pro-rated by time allocation - PCI compliance -- audit fees, tooling, engineering time for controls - PSP maintenance -- time spent on API updates, webhook debugging, error handling, settlement reconciliation ### Indirect Costs - Finance and ops -- FTEs doing manual reconciliation, dispute management, merchant support - Tax compliance -- if you handle it alongside payments - Legal -- merchant agreements, compliance review, licensing ### Opportunity Costs - Features not built -- what would those payment engineers have built instead? - Deals not closed -- enterprise prospects lost because you couldn't support their required PSP - Speed to market -- how much faster would you ship if payments were solved? Add up items 1-7 and divide by annual revenue. If the number surprises you, you're in the 27% who weren't tracking it. ## FAQ Is the 5-9% figure just processing fees? No. Processing fees (the 2.9% + 30¢ you pay Stripe) are one component. The 5-9% figure from the OpenView/Paddle survey includes engineering, billing, tax, compliance, and operations -- the full cost of making payments work inside your platform. Does this apply to early-stage companies? The percentage impact is often higher at early stage. When you have 20 engineers and 2 are on payments, that's 10% of your engineering capacity. The absolute cost is lower, but the proportional impact on product velocity is larger. We're on Stripe Connect -- is that enough? Stripe Connect reduces the build burden compared to raw Stripe integration. But it locks you into Stripe as your only PSP, limits you to Stripe's channels and capabilities, and still requires engineering maintenance. Many platforms outgrow Stripe Connect as they scale -- especially when enterprise customers mandate other PSPs. What's the break-even for building in-house? £50M+ in annual processing volume is the consensus threshold from Bain, Stax, Fiska, and Nexio. Below that, the fixed costs of PayFac infrastructure consistently exceed the revenue. Even above that threshold, the engineering opportunity cost often tips the balance toward outsourcing. How do I justify this to my CFO? Frame it as total cost of ownership. Your current payment infrastructure costs £X per year in direct costs (engineering salaries, PCI compliance, PSP maintenance) plus £Y in opportunity cost (features not built, deals not closed). A payment layer replaces this with per-transaction pricing -- typically resulting in lower total cost and recovered engineering capacity. The savings compound as you scale. ## Related Reading - How to Get Payments Off Your Product Roadmap -- the full case for outsourcing payment infrastructure - Embedded Payments Without Becoming a PayFac -- the middle path between Stripe Connect and full PayFac - How Platforms Monetise Payments Without PSP Lock-In -- turning payment infrastructure from a cost into revenue - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the four categories of payment infrastructure - When Your SaaS Outgrows Stripe Connect -- the migration path when Stripe Connect hits its limits - Shuttle vs Building In-House -- the detailed build-vs-buy comparison - What Happens When Your Only Payment Processor Cuts You Off -- the concentration risk of single-PSP dependency Ready to stop spending engineering on payments? Shuttle replaces your payment infrastructure build with a single integration -- 40+ PSPs, voice payments, payment links, AI agent channels, and PCI DSS Level 1 compliance included. Your team ships product. We handle payments. Calculate Your Savings | See How It Works Explore More ### Embedded Payments for ERP Platforms ### PCI Compliance Cost for Platforms: What It Really Costs in 2026 ### Agentic Payments: What Platforms Need to Know ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ### Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure ### Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure ## Links - [Book a Call →](/discovery/) - [Payment Facilitator](/guides/embedded-payments-without-payfac/) - [PCI DSS](/glossary/pci-dss/) - [payment layer](/guides/payment-layer-explained/) - [PCI scope](/glossary/pci-scope/) - [outgrow Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [What Happens When Your Only Payment Processor Cuts You Off](/guides/single-psp-risk/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Calculate Your Savings](/discovery/) - [See How It Works](/platforms/) - [GuideEmbedded Payments for ERP Platforms→](/guides/payments-for-erp-platforms/) - [GuidePCI Compliance Cost for Platforms: What It Really Costs in 2026→](/guides/pci-compliance-cost-platforms/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [GuidePayments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-invoicing-erp-platforms/) - [GuidePayments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure→](/guides/payments-for-insurance-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/payments-for-marketplaces/ --- # Payments for Marketplaces | Shuttle > How marketplaces handle payments -- from split settlements and seller onboarding to multi-PSP architecture. # Payments for Marketplaces By Nick Dunse, February 17, 2022 How marketplaces handle payments -- from split settlements and seller onboarding to multi-PSP architecture. I've been contacted by four platforms in the past 7 days, all trying to solve the problem. Why is it hard? 1. There are pay-ins and payouts, which most PSPs can't handle 2. If you're in the EU or UK, regulation means that you can't hold the money yourself and pay out later 3. Stripe is an obvious choice but you cannot use them if you need a delay in payout (unless you're in the US) 4. If you're a startup, you have no financial history, no leverage and no back-office processes to get a deal or run the process yourself 5. You have to work with one PSP for a single checkout process, this limits you in terms of acquiring customers 6. If you're merchants are selling high risk you even more limited in terms of PSP options 7. If you're building the platform, you'll have to build most of the payment infrastructure and user experiences 8. If you want to operate internationally then you'll have to deal with cross-border payouts What are the business models? - The marketplace can be the merchant of record - The merchant can be the merchant of record - You can take a % of the transaction at the point of transaction - You can take a % of the transaction post-transaction - You can charge a subscription fee Types of marketplaces: - B2C - B2B - Multi merchant basket - Single merchant basket - Products/Services sold, when it's known at the time of sale who the seller is - Products/Services sold when it's not known at the time of sale who the seller is What are the answers? If you're a startup in the US then Stripe is a good place to start for any model, but you won't be able to do high risk stuff. If you've got traction then you can use Adyen or Braintree as your monolith solution. If you're a startup in Europe, then Stripe could work if you know who the seller is and can payout immediately. If you need to have a number of gateways for pay-in then you can use some marketplace middleware like Payaut or Ryft. If you don't want to be the merchant of record then you can use Payaut. #payments #marketplaces #ecommerce #saas ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/ --- # PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope | Shuttle > PCI DSS compliance requirements for service providers and merchants. Understand the four merchant levels, two service provider levels, SAQ types, costs,... # PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope By Nick Dunse, January 28, 2026 PCI DSS compliance requirements for service providers and merchants. Understand the four merchant levels, two service provider levels, SAQ types, costs,... Talk to us Make enabling payments for your platform and merchant users easy. PCI DSS -- the Payment Card Industry Data Security Standard -- is the security framework that governs how organisations handle cardholder data. If your business stores, processes, or transmits card data, you must comply. If your software or service touches card data on behalf of other businesses, you are a service provider and face stricter requirements. This guide covers what PCI compliance means in practice for both merchants and service providers, the different compliance levels, the SAQ types, what compliance costs, and practical ways to reduce your PCI scope. ## What Is PCI DSS? PCI DSS is maintained by the PCI Security Standards Council (PCI SSC), which was founded by Visa, Mastercard, American Express, Discover, and JCB. The standard defines 12 core requirements across six categories, all designed to protect cardholder data from theft and misuse. The 12 requirements cover: - Network security -- firewalls, secure configurations, no vendor-supplied default passwords - Cardholder data protection -- encryption of stored data and data in transit - Vulnerability management -- antivirus, secure development practices, regular patching - Access control -- role-based access, unique IDs for each user, restricted physical access - Monitoring and testing -- logging, regular security testing, penetration testing - Security policies -- documented policies covering all personnel The current version is PCI DSS v4.0.1, which became mandatory in March 2025. Version 4.0 introduced significant changes including a customised approach to validation, expanded multi-factor authentication requirements, and new e-commerce anti-skimming protections. ## Service Provider vs Merchant: Why It Matters PCI DSS categorises organisations into two groups, each with different compliance obligations: Merchants are businesses that accept card payments for goods or services. A retailer, an online shop, a restaurant -- any entity that takes payment from cardholders. Merchants are assessed based on their annual transaction volume across all channels. Service providers are entities that store, process, or transmit cardholder data on behalf of other businesses -- or that could affect the security of cardholder data. This includes payment gateways, payment processors, hosting providers, managed security services, and software platforms that handle card data for their customers. The distinction matters because service providers face higher compliance requirements at every level. A service provider processing 300,000 transactions requires the same Level 1 assessment (including a Qualified Security Assessor audit) that a merchant would not face until 6 million transactions. ## PCI DSS Service Provider Levels Service providers are classified into two levels based on the number of transactions they store, process, or transmit annually: Transaction Volume Validation Requirements 300,000+ transactions/year Annual Report on Compliance (ROC) by a QSA, quarterly network scans by an ASV, annual penetration test Fewer than 300,000 transactions/year Annual Self-Assessment Questionnaire (SAQ-D), quarterly ASV scans, annual penetration test Level 1 service providers must undergo an on-site assessment by a Qualified Security Assessor (QSA) -- an independent security firm accredited by the PCI SSC. This is the most rigorous form of PCI validation and typically costs £50,000-£250,000+ depending on the complexity of the environment. Level 2 service providers can self-assess using SAQ-D (the most comprehensive self-assessment questionnaire), but must still complete quarterly network vulnerability scans by an Approved Scanning Vendor (ASV) and conduct annual penetration testing. Important: Card brands (Visa, Mastercard) can override these thresholds. A service provider that has experienced a data breach, for example, may be reclassified as Level 1 regardless of volume. ## PCI DSS Merchant Levels Merchants are classified into four levels. The thresholds vary slightly between card brands, but Visa's widely-used definitions are: Annual Visa Transactions 6 million+ Annual ROC by QSA, quarterly ASV scans, attestation of compliance 1-6 million Annual SAQ, quarterly ASV scans, attestation of compliance 20,000-1 million (e-commerce only) Fewer than 20,000 (e-commerce) or up to 1 million (other) Annual SAQ, quarterly ASV scans (recommended), attestation of compliance Most small and mid-sized businesses fall into Level 4. The compliance burden at this level is relatively light -- a Self-Assessment Questionnaire (the specific type depends on how you accept payments) and potentially quarterly vulnerability scans. ## SAQ Types: Which One Applies to You? The Self-Assessment Questionnaire (SAQ) comes in several variants, each designed for a different payment acceptance method. Using the right SAQ is critical -- it determines how many controls you must validate. Applies To Number of Questions Typical Use Case Card-not-present, all cardholder data functions outsourced E-commerce using a hosted payment page (e.g., Stripe Checkout, PayPal hosted) E-commerce merchants with websites that affect transaction security Custom checkout that redirects to payment provider, or uses iframes Imprint-only or standalone dial-out terminals Standalone card terminal with no electronic storage Standalone PTS-approved terminals connected via IP Card terminal connected to network but isolated from other systems Payment application systems connected to the internet POS system connected to internet, no electronic card data storage Virtual terminal (web-based, no electronic card data storage) Agent types card number into web-based virtual terminal All other merchants and all service providers Any scenario not covered by other SAQ types Merchants using validated P2PE solution Hardware-encrypted terminals (most restrictive device requirements) The key insight is the dramatic difference in scope. SAQ A is the short questionnaire. SAQ D is the full one. The choice of how you accept payments -- specifically, whether cardholder data ever touches your systems -- determines which SAQ applies and therefore how much compliance work you face. ## PCI Compliance Costs PCI compliance costs vary enormously based on your level, your payment acceptance method, and the current state of your security infrastructure: Cost Component Typical Range QSA assessment (Level 1) £50,000-£250,000+/year Level 1 merchants and service providers ASV quarterly scans £500-£5,000/year All levels (except some Level 4 merchants) Penetration testing £5,000-£50,000/year Level 1 and Level 2 SAQ completion £0 (self-service) to £10,000 (consultant-assisted) Level 2-4 merchants, Level 2 service providers Remediation £10,000-£500,000+ Any organisation failing assessment PCI compliance software/tools £1,000-£20,000/year All levels Staff training For service providers, costs are consistently at the higher end. Level 1 service providers typically spend £100,000-£300,000 annually on compliance activities, plus the ongoing cost of maintaining compliant infrastructure, training, and monitoring. For merchants, the cost depends almost entirely on scope. A merchant using SAQ A (hosted payment page, no cardholder data on their systems) might spend £1,000-£5,000 per year. A merchant using SAQ D could spend ten times that. ## How to Reduce Your PCI Scope PCI scope reduction is the single most effective way to lower compliance costs and risk. The principle is simple: if cardholder data never touches your systems, the systems are out of scope. Practical scope reduction strategies: ### 1. Use a hosted payment page or iframe The most effective scope reduction for e-commerce. Instead of collecting card details on your own server, redirect customers to a PCI-compliant payment page hosted by your PSP (Stripe Checkout, Adyen Drop-In, etc.). Your server never sees card numbers. This drops you from SAQ D to SAQ A. ### 2. Use tokenisation Replace card numbers with tokens -- random strings that have no value if stolen. Your payment provider stores the actual card data. Your systems only store tokens. This is essential for recurring billing and returning customer scenarios where you need to charge the same card again without collecting details each time. For more on how tokenisation works in the payment chain, see our glossary entry on tokenisation. ### 3. Isolate payment systems If you must handle cardholder data (e.g., for a call centre or virtual terminal), isolate the payment systems from the rest of your network. Use network segmentation -- firewalls, VLANs, separate subnets -- so that a breach in one system does not expose cardholder data. Proper segmentation can reduce the number of in-scope systems from hundreds to a handful. ### 4. Use DTMF masking for phone payments Contact centres that take card payments over the phone traditionally require agents to hear (and potentially record) card numbers -- putting the entire call centre infrastructure in PCI scope. DTMF masking lets callers enter card numbers on their phone keypad, with the tones captured and routed directly to a payment provider. The agent never hears or sees the card data. This can reduce a contact centre from SAQ D to SAQ A scope. See our detailed guide on PCI-compliant contact centre payments. ### 5. Outsource to a Level 1 service provider The most comprehensive scope reduction: outsource payment processing, tokenisation, and cardholder data storage entirely to a PCI DSS Level 1 certified service provider. Your systems never touch cardholder data. Your PCI assessment becomes a matter of confirming that you have outsourced correctly and that your service provider is compliant. For how to evaluate and choose one, see our guide to choosing a PCI compliance service provider. ## PCI DSS v4.0: What Changed PCI DSS v4.0 (effective March 2025) introduced several significant changes: - Customised approach -- organisations can now design their own controls to meet security objectives, rather than following prescriptive requirements. This gives mature security teams more flexibility but requires documented evidence that the custom control achieves the stated objective. - Expanded MFA -- multi-factor authentication is now required for all access into the cardholder data environment, not just remote access. This affects internal network access as well. - E-commerce script management -- new requirements for managing and monitoring scripts (JavaScript) on payment pages. This targets Magecart-style attacks that inject malicious scripts into checkout pages. - Targeted risk analysis -- organisations must conduct targeted risk analyses for specific requirements, documenting why their chosen approach is appropriate for their environment. - Authentication changes -- passwords must now be at least 12 characters (up from 7). Service accounts must have strong authentication and be reviewed regularly. - Automated log review -- manual log review is no longer sufficient for most environments. Automated mechanisms are required to detect anomalies. For service providers, v4.0 also introduced new requirements around detecting and reporting failures of critical security controls, and confirming PCI DSS scope at least every 12 months. ## PCI Compliance for Software Platforms If you are a software platform -- SaaS, marketplace, or vertical software -- that handles payments for your customers, PCI compliance has specific implications: - You are almost certainly a service provider -- if your platform processes, transmits, or stores cardholder data on behalf of your customers, you fall under the service provider classification regardless of transaction volume. - Your customers inherit your scope -- if your platform handles card data insecurely, your customers' PCI assessments are affected. Conversely, if your platform is Level 1 certified with proper tokenisation, your customers' scope is significantly reduced. - Multi-tenant adds complexity -- platforms serving multiple merchants need to demonstrate that one customer's cardholder data cannot be accessed by another. This requires logical or physical separation, access controls, and monitoring per tenant. - Multiple PSPs multiply scope -- each payment processor integration is an additional cardholder data flow that must be documented, secured, and assessed. Platforms using multiple PSPs face broader scope than those using a single processor -- unless payments are routed through an intermediary that consolidates the PCI scope. - Voice and phone channels expand scope further -- if your platform supports phone payments, the call recording, telephony, and agent desktop infrastructure all enter PCI scope. See our guide on voice payments and PCI for the architectural options. The platform PCI architecture decision often comes down to build vs. buy. Building PCI-compliant payment infrastructure in-house means taking on Level 1 service provider obligations -- the QSA assessment, the penetration testing, the ongoing monitoring, and the engineering team to maintain it. Using a PCI-certified payment layer means the compliance surface is outsourced, and the platform operates at SAQ-A scope. ## Frequently Asked Questions ### What is the difference between PCI compliant and PCI certified? PCI compliant means an organisation meets the PCI DSS requirements. PCI certified (or more precisely, "validated") means the compliance has been independently verified -- either by a QSA audit (Level 1) or through a completed SAQ with an Attestation of Compliance (other levels). Card brands require validation, not just a claim of compliance. ### How long does PCI compliance take? For a small merchant using SAQ A, initial compliance can be achieved in days. For a Level 1 service provider, the first QSA assessment typically takes 3-6 months of preparation plus 2-4 weeks for the on-site audit. Annual recertification is faster but still requires several months of preparation and evidence gathering. ### What happens if you are not PCI compliant? Non-compliance can result in fines from card brands (£5,000-£100,000+ per month), increased transaction fees, mandatory forensic investigations after a breach (£20,000-£100,000+), and loss of the ability to accept card payments. In practice, acquiring banks enforce compliance by requiring merchants and service providers to submit attestations of compliance. ### Does using a payment gateway make me PCI compliant? Using a PCI-compliant payment gateway reduces your scope -- potentially to SAQ A -- but does not make you automatically compliant. You still need to complete the appropriate SAQ, ensure your integration is secure, and submit your Attestation of Compliance. The gateway handles the hardest part (storing and processing card data), but you must still validate your own compliance. ### Can I avoid PCI compliance entirely? No. If you accept card payments in any form -- online, in person, or over the phone -- you must comply with PCI DSS. However, you can minimise your compliance burden by choosing payment acceptance methods that keep cardholder data off your systems entirely (SAQ A scope). This is the closest to "avoiding" PCI compliance while still accepting cards. ## Reduce Your PCI Scope With the Right Payment Architecture PCI compliance is a cost of accepting card payments -- but the size of that cost is largely determined by your payment architecture. Organisations that handle cardholder data directly face SAQ D, annual penetration tests, and ongoing infrastructure costs. Organisations that outsource cardholder data handling to a Level 1 certified provider face SAQ A and significantly lower ongoing costs. Shuttle is PCI DSS Level 1 certified, ISO 27001 certified, and SOC 2 compliant. Platforms that connect via Shuttle never handle cardholder data directly -- payments are processed through Shuttle's secure infrastructure, reducing the platform's PCI scope to SAQ-A regardless of how many PSPs, channels, or markets are involved. See how Shuttle handles PCI compliance for platforms · Book a discovery call ## Related Reading Explore More ### PCI Compliance Service Provider: How to Choose One in 2026 ### Twilio PCI Compliance: How to Take Payments Without Handling Card Data ### PCI Compliance Cost for Platforms: What It Really Costs in 2026 ### How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Merchant Account Providers Compared: 12 Best Options for 2026 ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [glossary entry on tokenisation](/glossary/tokenization/) - [DTMF masking](/guides/dtmf-payments/) - [PCI-compliant contact centre payments](/guides/contact-centre-payments/) - [PCI DSS Level 1 certified service provider](/glossary/pci-dss-level-1/) - [PCI compliance service provider](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [voice payments and PCI](/guides/ai-voice-agent-pci-payments/) - [PCI-certified payment layer](/guides/payment-layer-explained/) - [See how Shuttle handles PCI compliance for platforms](/platforms/) - [Book a discovery call](/discovery/) - [GuidePCI Compliance Service Provider: How to Choose One in 2026→](/guides/pci-compliance-service-provider/) - [GuideTwilio PCI Compliance: How to Take Payments Without Handling Card Data→](/guides/twilio-pci-compliance/) - [GuidePCI Compliance Cost for Platforms: What It Really Costs in 2026→](/guides/pci-compliance-cost-platforms/) - [GuideHow to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments→](/guides/salesforce-service-cloud-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideMerchant Account Providers Compared: 12 Best Options for 2026→](/guides/merchant-account-providers/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/pci-dss-v4-implications-for-service-provider-software-vendors/ --- # PCI DSS v4 Implications for Service Provider (software vendors) | Shuttle > PCI DSS v4.0 introduces key changes for software vendors including stricter authentication, enhanced encryption, and new requirements for service... # PCI DSS v4 Implications for Service Provider (software vendors) By Nick Dunse, January 28, 2026 PCI DSS v4.0 introduces key changes for software vendors including stricter authentication, enhanced encryption, and new requirements for service... PCI DSS v4.0, the latest version of the Payment Card Industry Data Security Standard, introduced several changes and enhancements that impact service providers. These changes aim to address emerging threats, provide greater flexibility, and clarify expectations for compliance. Here are the key implications and changes for service providers: ### 1. Expanded Roles and Responsibilities - Clearer Accountability: Service providers now have clearer requirements to define and document their roles and responsibilities in protecting cardholder data. This includes how they interact with and support their clients in meeting PCI DSS requirements. - Service Level Agreements (SLAs): Service providers must ensure that SLAs explicitly address security requirements and include performance metrics related to PCI DSS compliance. ### 2. Risk Management Enhancements - Customized Approach: Service providers can now use a "Customized Approach" to meet certain PCI DSS requirements, offering flexibility in how controls are implemented. However, this requires thorough documentation and validation of the approach by assessors. - Targeted Risk Analysis: Requirements that allow for flexibility, such as frequency of certain activities, must be supported by a risk analysis. Service providers are expected to perform and document these analyses. ### 3. Increased Monitoring and Testing - Continuous Monitoring: There is an emphasis on continuous security monitoring and more frequent testing of controls, particularly for critical systems. - Enhanced Logging and Reporting: Service providers must ensure comprehensive logging of critical activities and be prepared to provide these logs to their customers or auditors when required. ### 4. Stronger Authentication and Access Controls - Multi-Factor Authentication (MFA): MFA requirements have been expanded to apply to all access to the cardholder data environment (CDE), even for administrators. - Granular Access Controls: Service providers must implement more granular controls to ensure that only authorized personnel have access to sensitive data and systems. ### 5. Support for Emerging Technologies - Cloud and Virtualization Requirements: Service providers offering cloud services must comply with specific requirements for securing virtualized environments and ensuring proper segmentation. - Encryption Enhancements: New requirements address the use of stronger encryption algorithms and protocols, as well as the proper management of cryptographic keys. ### 6. Enhanced Security Awareness - Staff Training: There is an increased focus on ensuring that service provider personnel are trained on security policies and procedures relevant to their roles. - Phishing Simulations: Service providers must conduct regular phishing simulations to enhance employees' ability to recognize and respond to phishing attacks. ### 7. Reporting and Validation Changes - Defined Reporting Metrics: Service providers must report compliance status more clearly to their clients, including metrics on control performance. - Quarterly Reviews: Requirements for quarterly reviews of critical security controls, such as vulnerability scans and penetration tests, are emphasized. ### 8. Stricter Penetration Testing Requirements - Updated Methodologies: Service providers must follow stricter penetration testing methodologies and ensure they cover both internal and external threats to the CDE. - Testing Segmentation Controls: More rigorous testing of segmentation controls is required to verify the isolation of the CDE from untrusted networks. ### 9. Deadlines and Phased Implementation - While PCI DSS v4.0 was released in 2022, organizations, including service providers, have until March 31, 2025, to transition fully from PCI DSS v3.2.1. Certain new requirements are designated as "future-dated" and become mandatory after this date. Implications for Service Providers - Operational Changes: Service providers must review and potentially revamp their security practices, especially around authentication, monitoring, and data protection. - Customer Communication: They need to proactively communicate changes in compliance responsibilities and support clients in their compliance efforts. - Increased Costs: Enhanced requirements may lead to increased costs for implementing and maintaining compliance programs, especially for monitoring, testing, and training. Recommendations for Service Providers - Early Gap Analysis: Perform a detailed gap analysis to identify areas requiring changes under v4.0. - Staff Training and Awareness: Update training programs to align with new security requirements and emphasize phishing awareness. - Update Policies and Procedures: Ensure documentation reflects changes in roles, responsibilities, and new compliance requirements. - Leverage Automation: Use tools for continuous monitoring, logging, and reporting to reduce the operational burden. - Collaborate with Clients: Engage with customers to align on compliance strategies and responsibilities, particularly in shared environments. Adapting to PCI DSS v4.0 will require a proactive and structured approach, but the improved security posture will benefit both service providers and their customers. ## Related Reading Explore More ### PCI Compliance Service Provider: How to Choose One in 2026 ### How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### How to Switch Payment Providers Without Losing Customers ### How to Avoid Payment Provider Lock-In: A Platform Guide ### Twilio PCI Compliance: How to Take Payments Without Handling Card Data ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePCI Compliance Service Provider: How to Choose One in 2026→](/guides/pci-compliance-service-provider/) - [GuideHow to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments→](/guides/salesforce-service-cloud-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideHow to Switch Payment Providers Without Losing Customers→](/guides/payment-provider-migration/) - [GuideHow to Avoid Payment Provider Lock-In: A Platform Guide→](/guides/payment-provider-lock-in/) - [GuideTwilio PCI Compliance: How to Take Payments Without Handling Card Data→](/guides/twilio-pci-compliance/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/phygital-commerce-and-help-of-agentic-solutions/ --- # Phygital commerce and help of agentic solutions | Shuttle > Phygital commerce blends physical and digital retail. Learn how agentic AI solutions are powering the next wave of unified commerce and seamless payment... # Phygital commerce and help of agentic solutions By Nick Dunse, February 23, 2026 Phygital commerce blends physical and digital retail. Learn how agentic AI solutions are powering the next wave of unified commerce and seamless payment... Phygital Commerce: How AI Will Connect Online & Offline Shopping The lines between digital and physical shopping are blurring. Consumers are no longer confined to either in-store or online experiences -- they expect seamless, integrated journeys that combine the best of both worlds. Enter phygital commerce: the fusion of physical and digital shopping, now supercharged by AI-driven agentic commerce. ## What Is Phygital Commerce? Phygital commerce bridges the gap between online and offline retail. It leverages technology, AI, and automation to create a unified shopping experience where customers can seamlessly transition between: 🛒 Browsing in-store but purchasing online 📱 Scanning an item in-store for price comparison 🤖 Using AI agents to handle research, reordering, and negotiation This transformation is already happening, but AI-driven agentic commerce will accelerate it. ## How AI Agents Will Reshape Phygital Commerce Imagine walking into a store and seeing a product you like. Instead of searching online for better deals manually, your AI agent does it for you -- instantly. ### 1. AI-Powered In-Store Price Matching 📍 A shopper sees a product in-store 📍 Their AI agent scans barcodes or QR codes 📍 The agent compares prices online and finds the best deal 📍 The purchase is made autonomously -- either in-store or online This eliminates the hassle of searching for deals manually while ensuring the best price in real-time. ### 2. AI Agents Handling Complex Purchases Some purchases -- like travel, electronics, or even B2B procurement -- require research, comparison, and customization. AI can handle these tasks while you focus on other things. Example: A shopper enters a car dealership and uses their AI agent to: ✅ Compare financing options ✅ Check insurance rates ✅ Negotiate pricing based on real-time market data By the time they're ready to buy, their AI has done all the legwork. ### 3. Personalized AI Shopping Assistants Retailers already use AI chatbots to guide customers online. In the phygital era, AI agents will extend into physical stores by: 🛍 Suggesting alternative products (based on past preferences) 📦 Checking stock at nearby locations 🎯 Recommending add-ons or upsells Retailers who integrate AI into their in-store experiences will win customer loyalty and boost conversion rates. ## The Role of Payments in Phygital AI Commerce One major barrier to seamless phygital commerce is payments. Today's payment flows rely on either: 🔹 Physical cards & cash (in-store) 🔹 Manual entry of card details (online) In the AI-powered future: ✅ AI agents will autonomously select payment methods ✅ Biometric authentication will replace traditional checkout steps ✅ Loyalty and financing options will be optimized in real-time This will reduce friction, increase impulse purchases, and drive higher conversion rates. ## How Businesses Can Prepare for AI-Driven Phygital Commerce 1️⃣ Enable AI-Friendly Checkout Experiences - Businesses must optimize their checkout processes for AI-driven purchases. 2️⃣ Adopt Digital & Biometric Payments - Secure authentication methods like face ID and fingerprint scans will replace outdated card entry flows. 3️⃣ Integrate AI Shopping Assistants - Retailers should build AI-powered experiences that help consumers make better buying decisions. 4️⃣ Leverage AI for Dynamic Pricing & Offers - AI will enable real-time price adjustments based on demand, inventory, and competition. ## The Future of AI-Driven Phygital Shopping Phygital commerce isn't just a trend -- it's the future of shopping. As AI agents take over purchasing tasks, they will create frictionless, intelligent, and personalized shopping journeys across both digital and physical environments. Retailers who embrace AI-driven agentic commerce will lead the next era of retail. The question is: Are you ready? ## Related Reading Explore More ### Agentic Commerce: Payment Infrastructure for AI Agents ### HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ### Payment Solutions for Car Dealerships & Auto Finance Platforms ### Agentic Payments: What Platforms Need to Know ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideAgentic Commerce: Payment Infrastructure for AI Agents→](/guides/agentic-commerce/) - [GuideHubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)→](/guides/hubspot-commerce-hub-transaction-fees/) - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [GuidePayment Solutions for Car Dealerships & Auto Finance Platforms→](/guides/car-dealership-payment-solutions/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/preventing-chargebacks-a-guide-for-businesses/ --- # Preventing Chargebacks: A Guide for Businesses | Shuttle > A comprehensive guide to preventing chargebacks. Learn dispute management strategies, fraud prevention tools, and how to protect your merchant account. # Preventing Chargebacks: A Guide for Businesses By Nick Dunse, January 29, 2026 A comprehensive guide to preventing chargebacks. Learn dispute management strategies, fraud prevention tools, and how to protect your merchant account. Talk to us Make enabling payments for your platform and merchant users easy. Chargebacks are a form of consumer protection that allows individuals to dispute a credit card transaction and receive a refund from their bank. This can occur for a variety of reasons, including fraudulent activity, errors in billing, or disputes over the quality of goods or services received. When a chargeback is initiated, the funds from the disputed transaction are temporarily taken from the business's account and held by the bank while the dispute is investigated. If the bank rules in favor of the consumer, the funds are permanently reversed, and the business is responsible for the refunded amount. Chargebacks can have a significant impact on a business's finances and reputation, so it is essential for businesses to understand how they work and take steps to prevent them. ## The Financial Impact of Chargebacks: Costs and Consequences The costs and consequences of chargebacks can have a significant financial impact on businesses. First and foremost, chargebacks result in lost revenue as the funds are returned to the customer. In addition, businesses often incur additional fees from payment processors for chargeback transactions, which can further eat into profits. Furthermore, the time and resources spent on disputing and resolving chargebacks can be a drain on a company's bottom line. From a reputational standpoint, chargebacks can damage a business's relationship with its customers and can even result in higher scrutiny from payment processors or potential partners. All of these factors contribute to the significant financial implications of chargebacks for businesses. ## Exploring the Consequences of a High Chargeback Rate A high chargeback rate can have significant consequences for businesses. Firstly, it can result in financial losses, as businesses may have to refund the disputed transactions and pay chargeback fees. This can impact their bottom line and potentially lead to cash flow problems. Additionally, a high chargeback rate can damage a business's reputation and trust among customers. It can signal to banks and card networks that the business is risky, leading to higher processing fees and even account termination. Furthermore, excessive chargebacks can also result in increased scrutiny from regulatory authorities and potential fines. Overall, a high chargeback rate can have detrimental effects on a business's financial health and sustainability. Unpacking the Reasons Behind Chargebacks Chargebacks happen for a variety of reasons, but they often stem from a failure in the customer-business relationship. One common cause is dissatisfaction with the product or service received, leading the customer to dispute the charge with their bank. Other reasons include unauthorized transactions, fraudulent activity, or processing errors. Additionally, customers may resort to chargebacks if they feel they have been misled or if they did not receive the goods or services they were promised. Understanding the underlying reasons for chargebacks can help businesses take proactive steps to prevent them and build stronger relationships with their customers. Demystifying the chargeback process: A step-by-step guide The chargeback process can be a confusing and frustrating experience for merchants. When a customer disputes a transaction with their bank, a chargeback is initiated. The bank will then investigate the claim, and if they find in favor of the customer, the amount of the transaction is refunded to them, and the merchant is charged a fee. The merchant has the opportunity to provide evidence to refute the claim, and the bank will consider this evidence in their decision. If the chargeback is not successfully contested, it appears as a chargeback on the merchant's account, resulting in financial loss and potential damage to their reputation. Understanding the steps of the chargeback process is crucial for merchants to effectively navigate and minimize the impact of chargebacks on their business. Prioritizing Payment Security: Tips for Businesses In order to prioritize security for online and in-person payments, businesses can implement several key strategies. Firstly, they can invest in secure payment processing systems that use encryption and tokenization to protect sensitive customer data. Additionally, businesses should regularly update their software and hardware to ensure that they are using the latest security technology. It is also important for businesses to train their employees on best practices for handling customer payment information and to implement strict access controls to limit who has access to this data. Lastly, businesses should consider using fraud detection and prevention tools to help identify and stop potentially fraudulent transactions. By taking these proactive measures, businesses can prioritize payment security and reduce the risk of chargebacks. Crafting Clear Return and Refund Policies for Businesses Crafting clear return and refund policies for businesses is essential in order to minimize the risk of chargebacks and customer disputes. Firstly, businesses should clearly outline their return and refund policies on their website and in their terms of service. This includes detailing the timeframe in which returns and refunds are accepted, as well as any conditions or restrictions that may apply. Additionally, businesses should ensure that their policies are easily accessible and understandable to customers by using simple language and providing examples where necessary. It is also important for businesses to train their customer service representatives to effectively communicate and enforce the return and refund policies, thus maintaining consistency and clarity for all customers. By taking these steps, businesses can prevent misunderstandings and reduce the likelihood of chargebacks resulting from unclear return and refund policies. ## Managing Shipping Expectations: A Guide for Businesses Businesses can manage shipping expectations by providing clear and accurate information about shipping times and processes upfront. This means setting realistic delivery timelines and communicating any potential delays as soon as they arise. Offering multiple shipping options to cater to different customer needs and providing tracking information can also help manage expectations. Additionally, being transparent about any potential shipping issues and offering proactive solutions can help instill trust and confidence in customers. By prioritizing communication and transparency, businesses can effectively manage shipping expectations and reduce the likelihood of chargebacks due to shipping issues. ## Exploring Additional Expenses Associated with Chargebacks Chargebacks can incur a myriad of additional expenses for businesses. First and foremost, there are the direct costs of the disputed transaction itself, including the lost revenue from the sale and the associated fees imposed by banks and payment processors. In addition, there are operational costs, such as the time and resources required to investigate and respond to chargebacks, as well as the potential loss of future sales from disgruntled customers. Furthermore, businesses may also face penalties from credit card networks for exceeding certain chargeback thresholds, and the cost of implementing and maintaining fraud prevention measures to mitigate future chargebacks. Lastly, there are the intangible costs of damage to a company's reputation and customer trust, which can have long-term financial impacts. All of these expenses can quickly add up and negatively impact a company's bottom line. ## The Benefits of Chargeback Alerts for Merchants A chargeback alert is a notification that a merchant receives when a customer initiates a chargeback, which is a reversal of a credit card transaction. These alerts allow merchants to be aware of potential chargeback disputes in real-time, allowing them to take proactive measures to prevent them from occurring. They provide merchants with the opportunity to resolve the issue directly with the customer before it escalates into a full chargeback. By addressing customer concerns promptly, merchants can reduce their risk of losing revenue and incurring chargeback fees. Additionally, chargeback alerts provide merchants with valuable information about their customers' purchasing behavior, enabling them to make more informed decisions and improve their business practices. Overall, chargeback alerts are a valuable tool for merchants to minimize the impact of chargebacks and protect their bottom line. ## A Comparison of the Top Chargeback Alert Providers There are two main providers of chargeback alerts that businesses can utilize to protect against potential revenue loss from chargebacks. The key differences between these providers lie in their approach to monitoring and alerting. The first provider, Verifi, offers real-time data and analytics and focuses on preventing chargebacks before they occur. Their platform provides merchants with the tools to identify and address potential issues that could lead to chargebacks. On the other hand, the second provider, Ethoca, focuses on collaboration between merchants and issuers to stop chargebacks after they have been initiated. Their platform allows merchants to receive alerts about potential chargebacks and work with the issuing bank to resolve the issue before it results in a loss. Ultimately, the main difference between these providers lies in their approach to preventing and addressing chargebacks, with Verifi focusing on proactive prevention and Ethoca focusing on reactive resolution. Preventing Chargebacks through Customer Service Optimization and Billing Descriptors Optimizing customer service and billing descriptors can help prevent chargebacks by ensuring clear communication and transparency between the merchant and the customer. Providing exceptional customer service can address any issues or concerns that may arise before a chargeback is initiated. By offering responsive and helpful support, customers are more likely to reach out to the merchant for resolution instead of filing a chargeback. Additionally, using clear and recognizable billing descriptors can reduce confusion and potential disputes over unrecognized charges, ultimately decreasing the likelihood of a chargeback. Improved customer service and billing descriptors contribute to a positive and trustworthy relationship between the merchant and customer, thereby minimizing the need for chargebacks. ## Related Reading Explore More ### The UK Guide to Collecting Overdue Payments ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Pay Now Button for Invoices: The B2B Guide ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ### How to Send Payment Requests: The Complete Guide to Digital Payment Collection ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideThe UK Guide to Collecting Overdue Payments→](/guides/uk-guide-collecting-overdue-payments/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuidePay Now Button for Invoices: The B2B Guide→](/guides/pay-now-button-invoices/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [GuideHow to Send Payment Requests: The Complete Guide to Digital Payment Collection→](/guides/how-to-send-payment-requests/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/project-type/accountants/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/project-type/sage/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/provider_categories/accountant/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/provider_categories/saas-provider/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/provider_categories/sage/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/psp-consolidation-platform-risk/ --- # What PSP Consolidation Means for Your Platform | Shuttle > PSP mergers keep happening. Here's what Global Payments/Worldpay, FIS/Worldpay, and every acquirer consolidation means for platforms that depend on a... # What PSP Consolidation Means for Your Platform By shuttle-team, February 23, 2026 PSP mergers keep happening. Here's what Global Payments/Worldpay, FIS/Worldpay, and every acquirer consolidation means for platforms that depend on a... Talk to us Make enabling payments for your platform and merchant users easy. ## The Consolidation Wave Is Not Slowing Down The payment processing industry has been through a decade of aggressive consolidation, and the pace is accelerating rather than stabilising. The transactions read like a roll call of the industry's biggest names. Fiserv acquired First Data for $22 billion in 2019, creating one of the largest payment technology companies in the world. FIS acquired Worldpay for $43 billion in the same year, in what was then the largest ever fintech acquisition. Global Payments acquired TSYS for $21.5 billion in 2019. Nexi, Nets, and SIA completed a three-way combination in Europe worth roughly €15 billion in 2021. And now: Global Payments is acquiring Worldpay from GTCR for approximately $24 billion, reuniting Worldpay with a major acquirer after FIS divested the business in 2023 following years of integration difficulty. Each of these deals follows the same industrial logic. Acquiring processors need scale to compete on pricing. Network effects create winner-take-most dynamics in specific geographies and verticals. Technology integration promises cost efficiencies that rarely materialise as cleanly as the deal models suggest. Shareholders get a premium. The press release is optimistic. What the press releases rarely discuss is what happens to the software platforms that built their payment infrastructure on top of these businesses. ## What Happens to Platforms When Their PSP Gets Acquired When a PSP gets absorbed into a larger acquirer, the effects on dependent platforms are not immediate. The first few months typically look fine. The existing integration still works. Support channels still respond. The account manager is still in the same role. The structural changes come later, and they compound. ### Roadmap Reprioritisation Post-acquisition, the acquired PSP's engineering organisation gets absorbed into the parent company's technology strategy. Product roadmaps get consolidated. Features that were six months away get pushed to eighteen months, or get cancelled as redundant with the parent's existing capabilities. API versioning commitments made before the deal may or may not survive the integration. For a platform that built a deep integration against a specific PSP's API, roadmap divergence is an operational risk. The features your merchants rely on -- or the ones you were counting on launching -- may simply not be built on the timeline you planned. ### Support Tier Renegotiation Enterprise support agreements are treated as costs to be rationalised in post-merger integration. Support tiers get restructured. SLAs get renegotiated at the enterprise level, and the terms that smaller or mid-market platforms had often come off worse in the standardisation process. The dedicated technical contact who knew your integration gets reassigned to a larger account. ### Pricing Leverage Shifts This is the bluntest mechanism. Before the acquisition, your platform had negotiated pricing based on its volume, its trajectory, and the competitive tension between the PSP and its rivals. After the acquisition, the combined entity has a larger installed base, more cross-sell leverage, and less need to maintain aggressive pricing to win your business. Contract renewals after major acquisitions routinely come back with higher rates, restructured incentives, or terms that push platforms toward the parent company's broader product suite. ### Integration Priorities Get Aligned to the Parent's Strategy The most subtle effect is strategic alignment. The acquired PSP's partnerships team, previously focused on platform distribution, now operates within the parent company's partner strategy. That parent company has its own priorities -- often centred on direct merchant acquisition rather than enabling platforms. Resources that were previously devoted to helping platforms integrate and scale get redirected toward initiatives that are more valuable to the combined business. The platform is not abandoned. It just becomes lower priority. And lower priority, in payment infrastructure, means slower iteration, less responsive support, and reduced leverage in commercial discussions. ## The Multi-PSP Hedging Response -- and Its Costs Experienced platform operators have learned to anticipate this pattern. The response, almost universally, is to add a second PSP. Sometimes a third. The logic is sound. If your business is dependent on a single processor, you are exposed to the full operational and commercial risk of whatever happens to that processor -- whether that is an acquisition, a service disruption, a pricing change, or a strategic pivot away from your segment. Diversifying across two or more PSPs reduces concentration risk. But multi-PSP architectures built by direct integration create their own set of problems. ### The Integration Tax Every PSP integration is custom work. Each processor has its own API design, its own webhook format, its own tokenisation approach, its own quirks in how it handles refunds, disputes, and subscription billing. A platform with three direct PSP integrations has three separate codebases to maintain, three separate sets of API credentials to manage, and three separate upgrade cycles to track. This integration tax compounds over time. When a PSP releases a new API version, your team has to assess the impact on your integration and schedule the upgrade work. When a new payment method becomes commercially relevant -- pay-by-bank, buy now pay later, or a regionally important local method -- it has to be implemented against each PSP separately. Every new PSP you add multiplies the maintenance surface. ### Enterprise PSP Mandates Create Pressure from the Other Direction While acquisitions push platforms toward multi-PSP defensively, enterprise customer requirements push them there commercially. Enterprise customers -- those with negotiated rates, existing compliance certifications, and multi-year contracts with specific processors -- will not switch their PSP to use your platform. If your platform can only accept payments through Stripe, you cannot close the enterprise customer who processes through Worldpay. The practical result: platforms that serve mid-market and enterprise customers find themselves needing to support an expanding list of PSPs. Not because they planned to, but because each major prospect they want to close mandates a different one. ### The Hedged Architecture Still Has a Single Point of Failure Even platforms that have built integrations against two or three PSPs typically have one primary and one backup. The primary handles most volume. The secondary handles edge cases or regional requirements. When the primary PSP gets acquired, the platform is not actually well-positioned -- the secondary integration has seen far less use, may have accumulated technical drift, and is not operationally ready to absorb primary-level volume without significant additional work. ## The Structural Solution: A PSP-Neutral Layer The multi-PSP hedging response addresses the symptom -- concentration risk on a single processor -- without addressing the structural cause, which is that each PSP integration is a bespoke build with its own maintenance cost. The structural solution is to separate the platform's payment interface from the underlying processor. Instead of building directly against each PSP's API, the platform integrates once against a PSP-neutral layer. That layer handles all downstream PSP integrations, maintains API compatibility as processors evolve, and exposes a consistent interface to the platform regardless of which processor is executing the transaction. When a PSP gets acquired and its API changes, that change is absorbed by the payment layer, not by the platform. When an enterprise customer mandates a specific processor the platform hasn't previously used, connecting that processor is a configuration change against an already-existing integration, not a new build project. This architecture makes PSP relationships interchangeable from the platform's perspective. The platform maintains commercial relationships with whichever processors are relevant to its business. The technical dependency on any individual processor's implementation is eliminated. It also changes the nature of the consolidation risk. When Global Payments acquires Worldpay, a platform using a PSP-neutral layer has options. It can continue using Worldpay via the same integration. It can shift volume to a competing processor. It can use the deal as leverage in a pricing conversation. It has optionality that a platform with a direct single-PSP integration does not. This is the commercial insight behind PSP-neutral architecture: processing is commoditised. The pricing pressure and volume economics that drive PSP consolidation are evidence of this. What matters for platforms is not which processor you use -- it is that you have the optionality to use any processor your business requires, without rebuilding your integration every time market structure changes. ## How to Consolidation-Proof Your Payment Stack The consolidation pattern is not going to stop. The economics that drive it -- scale requirements, margin pressure, geographic expansion -- are structural features of the payment processing industry. Platforms that build their payment infrastructure around PSP-neutral architecture are positioning themselves to be resilient to M&A activity that is almost certain to continue. Here is what that looks like in practice. Audit your current PSP dependencies. Map every place in your codebase where you have a direct dependency on a specific processor's API, tokenisation scheme, or webhook format. This is your consolidation exposure surface. The larger it is, the more disruption you absorb when your PSP gets acquired or changes direction. Model the cost of multi-PSP with direct integration. If you are currently on a single PSP and planning to add a second, price the real engineering cost honestly -- initial integration, ongoing maintenance, support for new payment methods, PCI scope expansion, and the operational overhead of managing multiple processor relationships. That is the build cost of multi-PSP resilience. It is usually higher than it appears in initial scoping. Evaluate PSP-neutral architecture as a build vs. buy decision. A purpose-built PSP-neutral layer -- one that already has 40+ processor integrations, handles PCI compliance, and exposes a consistent API regardless of which processor is running underneath -- is not the same cost as building your own multi-PSP integration from scratch. The economics are different. Compare the approaches directly. Treat processor relationships as commercial, not technical. In a PSP-neutral architecture, your relationship with each processor is a commercial negotiation, not a technical dependency. You are free to add processors, change primary processors, and negotiate pricing based on the credible option to move volume elsewhere. That leverage is worth something -- particularly at contract renewal time, when an acquired PSP's parent is restructuring pricing. Plan for PSP mandates in enterprise deals, not around them. If your platform sells to mid-market or enterprise customers, the next major prospect you want to close probably has a mandated processor. Solving for this reactively -- one bespoke integration at a time -- is expensive and slow. Solving for it architecturally is a one-time project that compounds in value with every enterprise deal you close afterward. Assess your channel coverage. PSP consolidation affects not just embedded checkout, but every payment channel your platform operates or plans to operate. Voice, payment links, chat -- all of them have PSP dependencies that follow the same consolidation risk pattern. A platform that solves for multi-PSP in checkout but has a single-processor dependency in voice has not fully addressed its exposure. ## Processing Is Commoditised. Optionality Is Not. The $24 billion that Global Payments is paying for Worldpay is not a bet that processing margins are going to expand. It is a bet on scale, on distribution, and on owning the infrastructure inside which merchants operate. The same logic applies to platforms. Processing margin is not where platform value accrues. Platform value accrues from the workflows, the merchant relationships, and the enterprise deals that flow through your product. Payment processing is a required function, not a differentiator. What is a differentiator -- commercially and competitively -- is the ability to support whatever payment infrastructure your enterprise customers require, without your own engineering team absorbing the cost every time M&A activity reshapes the processor landscape. The platforms that will be most exposed to the next consolidation wave are the ones with the deepest direct dependencies on the processors being acquired. The ones best positioned are the ones for whom the underlying processor is an interchangeable detail. ## Related Reading - PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform? - Worldpay vs Shuttle: What Platforms Need to Know - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways - When Your SaaS Outgrows Stripe Connect - Embedded Payments Without Becoming a PayFac ## Work With Shuttle Shuttle is a PSP-neutral payment layer for platforms. A single integration connects your platform to 40+ payment processors -- with white-label merchant onboarding, a management portal, and PCI DSS Level 1 compliance included. When your PSP gets acquired, you have options. When an enterprise customer mandates a processor you don't currently use, connecting it is a configuration change, not a build project. Book a Discovery Call to discuss your current payment architecture and where consolidation risk sits in your stack. See How Platforms Use Shuttle to understand the integration model and the commercial case. Explore More ### What Happens When Your Only Payment Processor Cuts You Off ### Payment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### Payment Infrastructure for Food Ordering Platforms ## Links - [Book a Call →](/discovery/) - [enterprise customer requirements](/guides/enterprise-psp-mandates/) - [Compare the approaches directly.](/guides/psp-neutral-vs-single-psp/) - [Solving for it architecturally](/guides/enterprise-psp-mandates/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform?](/guides/psp-neutral-vs-single-psp/) - [Worldpay vs Shuttle: What Platforms Need to Know](/vs/worldpay/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Discovery Call](/discovery/) - [See How Platforms Use Shuttle](/platforms/) - [GuideWhat Happens When Your Only Payment Processor Cuts You Off→](/guides/single-psp-risk/) - [GuidePayment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel→](/guides/travel-platform-payments/) - [GuideEnterprise PSP Mandates: Why Platforms Need Multiple Gateways→](/guides/enterprise-psp-mandates/) - [GuidePSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform?→](/guides/psp-neutral-vs-single-psp/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuidePayment Infrastructure for Food Ordering Platforms→](/guides/food-ordering-platform-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/ --- # How to Accept Payments in QuickBooks: Full Guide | Shuttle > Set up QuickBooks Payments to accept cards, ACH, and Apple Pay on invoices and your website. Fees, setup steps, and third-party gateway options. # How to Accept Payments in QuickBooks: Full Guide By Nick Dunse, September 5, 2020 Set up QuickBooks Payments to accept cards, ACH, and Apple Pay on invoices and your website. Fees, setup steps, and third-party gateway options. Talk to us Make enabling payments for your platform and merchant users easy. QuickBooks is the accounting software behind millions of small and mid-sized businesses. But accounting is only half the picture -- you also need a reliable way to collect payments. QuickBooks Payments is Intuit's built-in payment processing solution that lets you accept credit cards, ACH bank transfers, and digital wallets directly inside QuickBooks Online. For many businesses, accepting payments through QuickBooks is the simplest path to getting paid faster. Customers can pay invoices with a single click, and every transaction automatically syncs to your books. But QuickBooks Payments is not the right fit for every scenario -- especially if you need advanced gateway features, multi-currency support, or custom checkout flows. This guide walks through everything you need to know: how to set up QuickBooks Payments, how to accept online payments on invoices and your website, what it costs, and when a third-party gateway is the better choice. ## What Is QuickBooks Payments? QuickBooks Payments is the payment processing feature built into QuickBooks Online. It allows businesses to accept credit card payments, debit card payments, and ACH bank transfers directly through invoices, sales receipts, and online checkout links -- without needing a separate merchant account or payment gateway. When a customer pays an invoice, the money flows through Intuit's payment processing infrastructure and deposits into your linked bank account. The transaction is automatically recorded in QuickBooks, which eliminates manual reconciliation and reduces errors. This is an example of embedded payments -- payment processing built directly into the software you already use, rather than bolted on as a separate tool. The benefit is simplicity: one login, one dashboard, and automatic bookkeeping. QuickBooks Payments supports the following payment methods: - Credit and debit cards -- Visa, Mastercard, American Express, and Discover - ACH bank transfers -- direct debit from the customer's bank account at a lower fee - Apple Pay -- available on supported mobile invoices and online checkout pages - PayPal and Venmo -- optional add-on for invoice payments (US only) ## How to Set Up QuickBooks Payments Setting up QuickBooks Payments takes about 10 minutes if you already have a QuickBooks Online subscription. Here is the step-by-step process: - Step 1: Sign in to QuickBooks Online. Go to Settings (gear icon) and select Account and Settings. - Step 2: Navigate to Payments. In the left sidebar, click Payments. If you have not set up QuickBooks Payments before, you will see an option to "Learn how you can accept online payments." - Step 3: Complete the application. Intuit will ask for your business type, legal name, EIN or SSN, business address, and bank account for deposits. Sole proprietors can use their personal SSN. - Step 4: Verify your identity. Intuit may request additional documents for verification. Most applications are approved within one business day. - Step 5: Configure deposit settings. Choose between standard deposits (next business day, free) or same-day deposits (1% fee, up to $25 per deposit). Link the bank account where you want funds deposited. Once approved, QuickBooks automatically adds a "Pay now" button to your invoices. You can also enable payment reminders to nudge customers who have not paid. ## Accepting Payments on QuickBooks Invoices The most common way to accept online payments in QuickBooks is through invoices. When you send an invoice with QuickBooks Payments enabled, the customer receives an email with a "Review and pay" button that opens a secure payment page. Here is how to configure invoice payments: - Choose accepted payment methods. When creating an invoice, you will see checkboxes for credit/debit cards, ACH bank transfer, and PayPal/Venmo. You can enable or disable methods per invoice. - Set default payment methods. In Account and Settings > Payments, choose which methods are enabled by default on every invoice so you do not have to configure each one manually. - Enable payment reminders. QuickBooks can send automatic reminders before, on, and after the due date. This significantly improves collection rates -- Intuit reports that businesses using automatic reminders get paid up to twice as fast. - Track payment status. The invoice dashboard shows which invoices are open, overdue, or paid. Once a customer pays, the invoice is automatically marked as paid and the payment is recorded in your general ledger. For businesses that send a high volume of invoices and want deeper customisation of the payment experience, integrating a third-party gateway can offer more flexibility. See our guide on maximising invoice payments with Stripe or maximising invoice payments with Authorize.net for alternatives. ## Accepting QuickBooks Payments on Your Website QuickBooks Payments is not limited to invoices. You can also accept payments on your website using QuickBooks' online checkout features: ### Payment Links QuickBooks lets you create shareable payment links for specific products or services. Embed them on your website, share in emails, or post on social media. Each link opens a hosted checkout page where customers enter their payment details, and the transaction records automatically in QuickBooks. Payment links are a fast way to collect payments online without a full ecommerce checkout. However, customisation is limited -- you cannot change the checkout page design, add custom fields, or create multi-step flows. ### QuickBooks Online Store Intuit offers a basic online store feature for QuickBooks Commerce subscribers. This gives you a product catalogue and checkout experience, but it is basic compared to dedicated ecommerce platforms like Shopify or WooCommerce. It works best for service-based businesses that sell a small number of items. ### QuickBooks API for Custom Integrations For businesses with custom websites or SaaS platforms, the QuickBooks Payments API allows you to process payments programmatically and sync transactions to QuickBooks. This requires development resources but gives you full control over the payment experience while keeping your accounting data in sync. ## QuickBooks Payments Fees and Pricing QuickBooks Payments pricing is straightforward -- there is no monthly fee for the payment processing feature itself (you only need a QuickBooks Online subscription). Fees are charged per transaction: - Invoice payments (card): 2.99% per transaction - Invoice payments (ACH/bank transfer): 1% per transaction ($1 minimum) - Online checkout / payment links (card): 2.99% per transaction - In-person / card reader: 2.5% per transaction - Same-day deposits: 1% per deposit (maximum $25) Compared to standalone gateways, QuickBooks Payments pricing is competitive for invoice-based businesses. The 2.99% card rate is slightly higher than Stripe's 2.9% + 30 cents, but the absence of a per-transaction fixed fee benefits businesses processing smaller transactions. ACH at 1% is significantly cheaper than card payments and worth encouraging customers to use. Keep in mind that you need a QuickBooks Online subscription ($35-$235/month depending on tier) to use QuickBooks Payments. If you are only looking for payment processing and do not need accounting software, a standalone gateway may be more cost-effective. ## QuickBooks Payments vs Third-Party Gateways QuickBooks Payments works well for straightforward payment collection, but it is not a full-featured payment gateway. Here is how it compares to popular third-party options: ### QuickBooks Payments vs Stripe Stripe is a developer-first payment platform for businesses that need custom checkout experiences, subscription billing, and multi-currency support. Stripe supports 135+ currencies and dozens of local payment methods. QuickBooks Payments only supports USD. Choose Stripe if: you sell internationally, need subscription billing, want a custom checkout experience, or are building a platform that needs to route payments to multiple parties. Choose QuickBooks Payments if: you primarily invoice US-based customers, want the simplest possible setup, and value automatic accounting reconciliation over customisation. ### QuickBooks Payments vs Authorize.net Authorize.net is a traditional payment gateway that integrates with hundreds of shopping carts, CRMs, and business tools. It supports recurring billing, a fraud detection suite (AFDS), and customer payment profiles for card-on-file transactions. For more detail, see our guide on payment links for Authorize.net. Choose Authorize.net if: you need a standalone gateway with broad integration support, advanced fraud tools, or need to process through a specific merchant account provider. Choose QuickBooks Payments if: you want a zero-setup solution that lives inside your accounting software and do not need advanced gateway features. ### When to Use Both Many businesses use QuickBooks Payments for invoice collection while running a third-party gateway for their website or app. Stripe and Authorize.net both have QuickBooks integrations that sync transactions into your books -- giving you a powerful gateway for online sales and frictionless invoice payments. ## Limitations of QuickBooks Payments QuickBooks Payments is convenient, but it has notable limitations that may push growing businesses toward dedicated payment platforms: - US only. QuickBooks Payments is only available to US-based businesses and only processes transactions in USD. If you have international customers or need multi-currency support, you will need a different gateway. - Limited payment methods. No support for local payment methods like iDEAL, SEPA Direct Debit, Klarna, or Afterpay. Digital wallet support is limited to Apple Pay. - No subscription billing. QuickBooks has recurring invoices, but there is no built-in subscription management with dunning, proration, plan changes, or usage-based billing. - Basic fraud tools. QuickBooks Payments does not offer configurable fraud rules, 3D Secure authentication, or risk scoring. High-risk or high-volume merchants may need more robust fraud prevention. - Minimal checkout customisation. The hosted payment pages and invoice checkout cannot be branded or customised beyond basic logo and colour settings. - Platform and marketplace limitations. QuickBooks Payments does not support split payments, connected accounts, or multi-party payment flows that platforms and marketplaces require. ## Using Payment Links with QuickBooks Payment links are one of the fastest ways to collect payments without building a full checkout. QuickBooks offers its own payment links feature, but you can also use third-party payment link providers for more flexibility. QuickBooks payment links let you create a shareable URL for a fixed amount or a product. Customers click the link, enter their payment details on a hosted page, and the payment records automatically in QuickBooks. They work well for simple use cases: collecting deposits, one-off service fees, or event registrations. For more advanced scenarios -- like branded checkout pages, custom fields, multi-currency payments, or connecting payment collection into automated workflows -- third-party payment links from providers like Stripe or Authorize.net can be integrated with QuickBooks via apps or middleware. If you are a platform or SaaS company that integrates with QuickBooks and needs to offer payment collection to your users, Shuttle provides payment link infrastructure that can connect to QuickBooks workflows. Rather than building and maintaining payment integrations yourself, you can embed payment links into your platform and let Shuttle handle the payment connection and PCI compliance. For a step-by-step walkthrough of connecting your own gateway to QuickBooks invoices, read our full guide: How to Accept Payments on QuickBooks Invoices (Without Switching Provider). ## Tips to Get Paid Faster with QuickBooks Payments Enabling QuickBooks Payments is only the first step. These practices help you reduce days sales outstanding (DSO) and improve cash flow: - Enable ACH payments. Many customers prefer bank transfers, especially for larger invoices. The lower fee (1% vs 2.99%) also saves you money. - Turn on automatic reminders. Set reminders for 7 days before, on the due date, and 7 days after. QuickBooks handles the emails so you do not have to chase payments manually. - Offer multiple payment methods. The more options you give customers, the fewer excuses they have to delay. Enable cards, ACH, and Apple Pay on every invoice. - Send invoices immediately. Do not wait until month-end. Send invoices as soon as work is completed or products are delivered. QuickBooks makes it easy to invoice from your phone. - Use payment links for non-invoice payments. For deposits, retainers, or one-time charges, send a payment link instead of a full invoice. It is faster for both you and the customer. ## Frequently Asked Questions ### How much does QuickBooks Payments cost? There is no additional monthly fee for QuickBooks Payments beyond your QuickBooks Online subscription. You pay per transaction: 2.99% for card payments on invoices and online checkout, 1% for ACH bank transfers ($1 minimum), and 2.5% for in-person card reader transactions. Same-day deposits cost an additional 1% per deposit, capped at $25. ### Can I accept payments through QuickBooks without a website? Yes. QuickBooks Payments works primarily through emailed invoices. When you send an invoice, your customer receives an email with a secure "Pay now" link -- no website required. You can also create standalone payment links to share via email, text message, or social media. ### Does QuickBooks Payments work outside the United States? No. QuickBooks Payments is only available to US-based businesses and processes transactions in USD only. If you need to accept international payments or multiple currencies, you will need a third-party gateway like Stripe. ### Can I use Stripe or Authorize.net with QuickBooks? Yes. Both Stripe and Authorize.net offer QuickBooks integrations that sync payment data into your accounting. You can use a third-party gateway for your website or app checkout while using QuickBooks Payments for invoice collection, or use the third-party gateway exclusively and sync everything to QuickBooks for bookkeeping. ### How long does it take to receive QuickBooks Payments deposits? Standard deposits arrive the next business day at no extra cost. Same-day deposits are available for a 1% fee (maximum $25 per deposit). ACH bank transfer payments take 5-7 business days to process before the funds are deposited. ## Next Steps For most small businesses using QuickBooks Online, enabling QuickBooks Payments is a no-brainer. It takes minutes to set up, costs nothing extra per month, and gets invoices paid significantly faster. If you need more than what QuickBooks Payments offers -- international payments, advanced fraud detection, subscription billing, or custom checkout flows -- explore a third-party gateway like Stripe or Authorize.net and integrate it with your QuickBooks account. And if you are a platform or SaaS company that needs to offer payment collection to your users alongside QuickBooks, book a discovery call with Shuttle to learn how embedded payment links and gateway orchestration can plug into your existing workflows. ## Related Reading Explore More ### QuickBooks Payment Links: Add a Pay Now Button to Any Invoice ### Authorize.net + QuickBooks Integration: Accept Invoice Payments Online ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [embedded payments](/guides/what-is-embedded-payments/) - [maximising invoice payments with Stripe](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [maximising invoice payments with Authorize.net](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [Stripe](/payment-providers/stripe/) - [payment links for Authorize.net](/blog/payment-links-for-authorize-net/) - [embed payment links into your platform](/platforms/) - [How to Accept Payments on QuickBooks Invoices (Without Switching Provider)](/guides/quickbooks-invoice-payments/) - [book a discovery call with Shuttle](/discovery/) - [GuideQuickBooks Payment Links: Add a Pay Now Button to Any Invoice→](/guides/quickbooks-payment-links/) - [GuideAuthorize.net + QuickBooks Integration: Accept Invoice Payments Online→](/guides/authorize-net-quickbooks/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/quickbooks-payment-collection/ --- # QuickBooks Payment Collection: Add Pay Now Links to Every Invoice | Shuttle > Build a complete QuickBooks payment collection workflow with pay-now links, automated reminders, and multi-channel chasing. # QuickBooks Payment Collection: Add Pay Now Links to Every Invoice By Shuttle Team, March 12, 2026 Build a complete QuickBooks payment collection workflow with pay-now links, automated reminders, and multi-channel chasing. Talk to us Make enabling payments for your platform and merchant users easy. ## The QuickBooks Payment Collection Problem QuickBooks is great at creating invoices. It's not great at getting them paid. QuickBooks Payments (formerly Intuit Payments) lets you add a "Pay Now" button to invoices -- but only if you're in the US, and only through QuickBooks' own processing. For UK businesses, Canadian businesses, or anyone who wants to use their own payment gateway, there's no built-in option. Even in the US, QuickBooks Payments has limitations: - Locked to Intuit's processing -- You can't use your existing merchant account. You pay QuickBooks' rates (2.9% + $0.25 for cards, 1% for ACH). - US-only -- QuickBooks Payments isn't available in the UK, Canada, Australia, or most other markets. QuickBooks Online is global; its payment feature isn't. - Limited payment methods -- Cards and ACH only. No Apple Pay, Google Pay, or Open Banking. - No SMS or WhatsApp delivery -- Invoices go out by email. When the email gets buried, you have no other channel. - Basic branding -- The checkout page is QuickBooks-branded, not yours. If you're already using QuickBooks for invoicing and want customers to pay faster, payment links fill the gap. ## How Payment Links Work With QuickBooks We've already covered QuickBooks payment links and accepting payments on QuickBooks invoices in detail. Here's the short version: - Create your invoice in QuickBooks as normal. - Generate a payment link for the invoice amount -- either manually or via API. Include the QuickBooks invoice number as a reference. - Add the link to the invoice -- paste it into the "Message to customer" field or the invoice notes before sending. - Customer receives the invoice with a pay-now link -- they click through to a branded checkout page and pay with their preferred method. - Payment settles to your merchant account -- reconcile in QuickBooks by matching the bank transaction to the invoice. The difference from QuickBooks Payments: you use your own gateway (Worldpay, Stripe, Adyen, Square, Authorize.net, or any of 40+ providers), you get white-label branding, and it works globally. ## Building a Payment Collection Workflow in QuickBooks Adding a payment link to an invoice is step one. Here's how to build a complete collection workflow: ### Day 0: Invoice Sent Send the invoice from QuickBooks with a payment link in the message. The message should be clear and direct: > Hi [Name], please find invoice #1234 for £2,500 attached. You can pay securely online here: [payment link]. The invoice is due on [date]. The payment link should support multiple payment methods -- cards, bank transfer, Apple Pay, Google Pay. More choice means faster payment. See why giving customers payment choice matters. ### Day 7: Email Reminder If unpaid after 7 days, send a friendly payment reminder with the same payment link. QuickBooks has a built-in reminder feature, but it doesn't include payment links -- you'll need to send the reminder manually or via an automation tool. > Hi [Name], just a friendly reminder that invoice #1234 for £2,500 is due on [date]. Pay online now: [payment link]. Let me know if you have any questions. ### Day 14: SMS Follow-Up Email open rates for payment reminders are around 20%. SMS open rates are 98%. If the email reminder didn't work, send the payment link via text message. > [Company]: Invoice #1234 (£2,500) is now overdue. Pay securely here: [payment link] This is where multi-channel payment collection makes a real difference. The same payment link works across every channel. ### Day 30: WhatsApp or Phone Call For invoices 30+ days overdue, escalate to WhatsApp (if the customer uses it) or a phone call. If calling, you can read out the payment link URL or send it by text during the call. For businesses that handle payment collection over the phone regularly, see our guide on contact centre payments. ### Day 45+: Formal Notice At this stage, send a formal dunning letter -- either by email or post. Include the payment link URL and a QR code. Reference your legal rights under the Late Payment of Commercial Debts (Interest) Act 1998 if you're in the UK. ## Automation: Payment Links + QuickBooks API For businesses sending 50+ invoices per month, the manual workflow doesn't scale. Here's how to automate it: ### Option 1: Zapier/Make Integration - Trigger: New invoice created in QuickBooks Online. - Action: Call Shuttle's API to generate a payment link (passing invoice amount, currency, reference). - Action: Update the QuickBooks invoice memo/notes with the payment link URL. - Action: Send the invoice from QuickBooks. No code required. Takes about 30 minutes to set up. ### Option 2: Direct API Integration If you have a developer or use a custom invoicing workflow, connect directly: - QuickBooks Online API creates the invoice and returns the invoice ID + amount. - Your system calls the payment link API to generate a link. - The link is embedded in the invoice email template. - Webhook notifications confirm when the customer has paid. This is the approach most B2B service companies and professional services firms use at scale. ## QuickBooks Payments vs Payment Links: Which Is Right for You? QuickBooks Payments Payment Links (Shuttle) Availability Intuit only 40+ providers -- use your own Card rates 2.9% + $0.25 Your gateway's rates ACH/Bank transfer Via your gateway Apple Pay / Google Pay Open Banking (UK) White-label No (QuickBooks branded) Yes -- your brand SMS / WhatsApp Use QuickBooks Payments if: You're a US-only business, you're happy with Intuit's processing rates, and you don't need multi-channel delivery or white-label branding. Use payment links if: You're outside the US, you want to use your own gateway, you need multiple payment methods, or you want to chase overdue invoices across SMS/WhatsApp. ## Common Questions ### Can I use both QuickBooks Payments and payment links? Yes. QuickBooks Payments handles the built-in pay button on Intuit's invoice viewer. Payment links are a separate URL you add to the email message. Customers can use either route. There's no conflict. ### Does this work with QuickBooks Desktop? Payment links work with any invoicing system -- including QuickBooks Desktop. You generate the link separately and add it to the invoice email or notes. The API automation option requires QuickBooks Online. ### How do I track which invoices have been paid via payment link? Each payment link carries a reference (the invoice number). When the payment settles to your bank account, match it in QuickBooks using that reference. Some providers also offer webhook notifications that can auto-reconcile. ### What about recurring invoices? For recurring invoices (monthly retainers, subscriptions), you can generate a new payment link each month or set up a recurring payment link that stays active. For true recurring billing, you may want to combine payment links with direct debit via GoCardless or similar. ## Get Started QuickBooks handles invoicing. Payment links handle getting paid. Together, they give you a complete invoice-to-payment workflow that works globally, supports multiple payment methods, and lets you chase overdue invoices across every channel. Shuttle Payment Links connect to 40+ gateways, support white-label branding, and integrate with QuickBooks via API or Zapier. See how it works. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices ### Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes ### Secure Payment Collection for Debt Agencies ### Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [QuickBooks payment links](/guides/quickbooks-payment-links/) - [accepting payments on QuickBooks invoices](/guides/quickbooks-invoice-payments/) - [Worldpay](/blog/payment-links-for-worldpay/) - [Stripe](/blog/payment-links-for-stripe/) - [Adyen](/payment-providers/adyen/) - [Square](/blog/payment-links-for-square/) - [Authorize.net](/blog/payment-links-for-authorize-net/) - [any of 40+ providers](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [why giving customers payment choice matters](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [friendly payment reminder](/blog/payment-reminder-email-templates/) - [multi-channel payment collection](/guides/multi-channel-payment-collection/) - [contact centre payments](/guides/contact-centre-payments/) - [dunning letter](/blog/dunning-letter-templates/) - [B2B service companies](/guides/b2b-payment-collection/) - [professional services firms](/guides/payment-collection-professional-services/) - [direct debit via GoCardless](/blog/payment-links-for-gocardless/) - [40+ gateways](/payment-providers/) - [See how it works](/merchants/links-checkout/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuidePayment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices→](/guides/payment-collection-professional-services/) - [GuideMulti-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes→](/guides/multi-channel-payment-collection/) - [GuideSecure Payment Collection for Debt Agencies→](/guides/secure-payment-collection-debt-agencies/) - [GuidePayment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope→](/guides/payment-collection-for-bpos/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/quickbooks_casestudy/ --- # 9k+ QuickBooks users using Shuttle | Shuttle > Over 9,000 QuickBooks users connect Shuttle to accept payments through their preferred gateway. See how embedded payments drive platform growth. # 9k+ QuickBooks users using Shuttle By Nick Dunse, December 20, 2025 Over 9,000 QuickBooks users connect Shuttle to accept payments through their preferred gateway. See how embedded payments drive platform growth. Accounting software serving over 4.5m customers. Enabling payments has added capabilities that are winning and retaining customers for QuickBooks The Challenge Businesses want to improve their cash flow and create convenient methods of payment for their customers. They're using payment providers not only take the payment but so that their processing is centralised, which is convenient. Businesses don't want to deal with antiquated payment processes anymore. Accountants and businesses are struggling to find accounts receivable software that is compatible with their preferred payment providers and improve the health of their respective businesses. It is proven that payments as a feature drives customer acquisition and retention of those customers over time for SaaS vendors. The answer is to ensure that SaaS companies are working with the relevant payment providers, which in turn enables them to onboard more customers. For a SaaS vendor like QuickBooks integrating and maintaining payment integrations is a huge burden. The burden is increased when PCI compliance is included and the scope their systems are brought into the audit. Adding the features that their customers want is difficult, expensive and time-consuming. In two years we've gone from zero to helping 9k+ QuickBooks businesses get their invoices paid online! How Shuttle helped In 2018 we built a payments app for QuickBooks to showcase that it was possible for invoices to get paid online with any of our connected payment providers. In that year QuickBooks shortlisted us for their top 10 apps of 2018 in the infamous App Showdown competition. Sadly we didn't win, but one of the success criteria was about how applicable the app was to the QuickBooks user base. Obviously the majority of QuickBooks users send invoices and would want those paid online where possible. To improve the accounts receivable process for the user our app records the payment against the invoice and changes the status of the invoice to 'PAID'. We also provide added features, for example, the user can receive an email notification on payment and set the invoice to part pay, which means the invoice can take instalments and on appear as paid once the full amount has been paid off. QuickBooks users are utilizing more than six of our connected payment providers to get the invoices paid online. Our dynamic payment form appears on the screen and displays the features that the QuickBooks user has configured. These could be payment methods like ACH, SEPA or PayPal. Or extra levels or fraud checks. Just like most other online payments the end customer can save their card details for faster processing next time. The bulk of the PCI compliance is offloaded to us since we host the process, although it feels part of the experience since our payment form is used in an iframe over the software with the invoicer's logo for extra trust value. "Works perfectly, thank you. It is just what I needed for one of my clients. It was easy to set up and connected Stripe to QBO Online with no problems at all. Thanks..." Zebbies, 01/14/2020 The Result In two years we've helped 9k+ QuickBooks businesses get their invoices paid online! Intuit told us that, since 2018, we were QuickBook's fastest-growing new app and that the usage of our app drove customer retention for QuickBooks. Due to the success of our app we have been invited into all of the QuickBooks success programs and help accountants drive value for their clients, namely teaching them how to improve their cashflow. Intuit knows that adding functionality like payments is a competitive advantage over the competition and attracts savvy business owners. We've seen invoices up to $250k paid online using credit cards! Intuit asked us to support their London Hackathon in 2019 with our payments platform and API for software vendors. It would allow contestants to build on top of the QuickBooks API with the added feature of online payments from the leading payment providers around the globe via Shuttle. 17 out of 40 teams used our API to build everything from mobile apps for hair salons to ecommerce. Since the success of our QuickBooks partnership, other apps in the ecosystem have turned to Shuttle for payments. If you're a software vendor building accounts receivable functionality then making it convenient for businesses to get paid online is a must. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/regulation-is-about-to-shake-up-online-marketplaces/ --- # Regulation is about to shake up online marketplaces | Shuttle > This is a big deal and if you're running an online marketplace in the EU you need to read this... # Regulation is about to shake up online marketplaces By Nick Dunse, April 7, 2024 This is a big deal and if you're running an online marketplace in the EU you need to read this... The Payment Services Directive version 2 (PSD2) will come into force on 14th September 2019 and there are a couple of key areas that will affect software vendors and their merchants who accept payments in Europe. The first area for consideration is called SCA. We've created another post about the SCA (Strong Customer Authentication) and what that means for vendors and their merchants, you can check that out over here, in short, there is going to be more 'friction' at checkout for buyers and compliance requirements for merchants and vendors. Follow the money This post tackles the issue that online software marketplaces face in terms of receiving payments on behalf of merchants and then paying out to those merchants later. Effectively remitting the money or executing a transaction. Online marketplaces have sprung up in recent years and become very successful, some notable examples are: ebay, Amazon, Shopify, Etsy, Kickstarter, Funding Circle & Just Giving. And marketplace startups have not necessarily conformed to the previous mould, as I would argue there are many more 'marketplaces' that are not in the consumers' mind, those in healthtech, proptech and insuretech to name just a few categories; with many platforms providing a multi-merchant checkout process. Think Gym management software, rental property or even insurance policy sales. And of course, good cause marketplaces that manage donations are not exempt by virtue either. We've met lots of software marketplaces that have this model since it enables a number of benefits: 1) They can collect the money 2) They can take a cut of the payment 3) It means that they don't have to integrate multiple payment providers 4) Vendors can receive commissions from some payment processors But here's the kicker - You can no longer collect the money! Unless you are regulated that is. And I don't know any software vendors who want to go through regulation. So just to be clear if you're running a software marketplace that takes payment for a product that you sell on behalf of a merchant and then pay that merchant later, you will be breaking the PSD2 regulation and get investigated from September onwards if you are not registered as regulated. What options do we have? Ok, so what are your options if you're a software vendor providing this marketplace model... In short, you don't want to be touching or holding the money or running the payment process: Option 1 Use a regulated payment provider and don't touch the money. This will certainly alleviate the concern, but as far as I can interpret the legislation this means the provider is the commercial agent not the marketplace. Single payment providers will be limited by region and functionality. Option 2 Find a single processor with 'connected' accounts. Stripe has something called Stripe Connect that means a marketplace can connect other Stripe users accounts and pass the transaction directly from payer to payee, routing the payment straight through. The downside to this is, it's a single processor approach and secondly, you have no control over the transaction. Stripe does allow the marketplace to add in a fee, which will make lots of people happy. Option 3 If you're a marketplace with more complex requirements, like the need to have multiple payment providers, operate in a broader range of countries and offer multiple payment methods you're going to need to find some sort of aggregator or payment provider code library. This is where we can help, our platform provides a consistent payment experience across the leading payment providers and methods. With one integration you can have ongoing access to our compliant payment components and view all transactions and merchants in one place. The question that needs to be answered regardless of which of the above options you choose, as a marketplace, who is your customer? A bit more detail Under PSD2, the definition of a commercial agent has been tightened up and you must decide if you represent the payee (merchant) or the payer (end customer), you cannot represent both. And regardless of whether or not the marketplace is in possession or control of funds. This is where adding fees like in Stripe's Connect solution has to be carefully considered in the flow. It is, therefore still a difficult and grey test to pass for online marketplaces. If you do want to act on behalf of both parties, then under PSD2 you will need to apply for a license. Any platforms which accept payments or donations before passing them to the intended recipient (e.g. online fundraising platforms) should also review their regulatory position. In conclusion, the simplest way around this new directive is to outsource the payment process to compliant solution providers but your position as a marketplace and your processes still need to be considered carefully. ## Related Reading Explore More ### Authorize.net + QuickBooks Integration: Accept Invoice Payments Online ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideAuthorize.net + QuickBooks Integration: Accept Invoice Payments Online→](/guides/authorize-net-quickbooks/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/reselling-payments-is-a-false-economy/ --- # Reselling payments is a false economy | Shuttle > Building your own payment facilitation looks profitable on paper, but the hidden costs of compliance, support, and maintenance make it a false economy. # Reselling payments is a false economy By Nick Dunse, January 30, 2026 Building your own payment facilitation looks profitable on paper, but the hidden costs of compliance, support, and maintenance make it a false economy. Creating that extra revenue line is a good idea, but is offering your own payment services the way to do it? Does it give you all the $$ you think it will - the short answer is, probably not. Here's why: 1. You will lose customers who already have existing relationships and refuse to move, typically larger merchants 2. You can only onboard merchants from countries that are covered by the PSP behind you ### 3. You will be missing many payment methods (e.g. PayPal or BNPL) 4. You will have to do your own KYC and potentially be responsible for chargebacks and support. This is a cost that will have to be considered against the upside 5. If your merchant uses other software to also accept payments, how do they then use your payment gateway in that software? 6. You're not a payment provider, you know nothing about payments, stick to your product, whilst working with Shuttle to monetize payments with no down-side 🙂 ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/revolutionize-your-payment-process-with-stripe-payment-links/ --- # Revolutionize Your Payment Process with Stripe Payment Links | Shuttle > Create Stripe payment links to accept online payments without a website. Share secure checkout links via email, SMS, or social media and get paid fast. # Revolutionize Your Payment Process with Stripe Payment Links By Nick Dunse, January 30, 2026 Create Stripe payment links to accept online payments without a website. Share secure checkout links via email, SMS, or social media and get paid fast. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. Stripe Payment Links have revolutionized the way businesses accept online payments. These links provide a convenient and streamlined payment process for both customers and businesses, making it easier than ever to complete transactions. But before we delve into the benefits and features of Stripe Payment Links, let's take a brief look at the history of Stripe as a payment processor. Founded in 2010 by brothers Patrick and John Collison, Stripe has quickly become one of the leading payment processors in the world. The company's mission is to make it easier for businesses to accept payments online, and they have certainly achieved that goal. With a user-friendly interface, robust security features, and a wide range of payment options, Stripe has gained the trust of businesses big and small. Key Takeaways - Stripe Payment Links simplify the payment process for businesses and customers alike. - Benefits of using Stripe Payment Links include increased efficiency, flexibility, and security. - Creating and customizing a Stripe Payment Link is quick and easy. - Integrating Stripe Payment Links with your website allows for seamless payment processing. - Stripe Payment Links offer robust security features and transparent pricing options. ## Benefits of Using Stripe Payment Links One of the key benefits of using Stripe Payment Links is the convenience it offers to customers. Instead of having to navigate through a complex checkout process, customers can simply click on a link and enter their payment details. This eliminates the need for customers to create an account or remember their login information, making it much more likely that they will complete their purchase. For businesses, Stripe Payment Links offer a streamlined payment process that saves time and reduces friction. By generating a unique link for each transaction, businesses can easily track payments and reconcile them with their records. This eliminates the need for manual data entry and reduces the risk of errors. Additionally, Stripe offers powerful reporting tools that provide valuable insights into sales and revenue trends. Another significant benefit of using Stripe Payment Links is the potential for increased sales and revenue. With a seamless payment process, customers are more likely to complete their purchase, resulting in higher conversion rates. Furthermore, Stripe supports multiple payment methods, including credit cards, digital wallets, and bank transfers, giving customers flexibility in how they pay. This can attract a wider range of customers and ultimately lead to increased sales. In addition to convenience and increased sales, Stripe Payment Links also offer enhanced security features that reduce the risk of fraud. Stripe employs advanced encryption and tokenization technologies to protect sensitive customer data. This ensures that payment information is securely transmitted and stored, giving customers peace of mind when making online purchases. By using Stripe Payment Links, businesses can build trust with their customers and establish a reputation for secure transactions. ## How Stripe Payment Links Work Now that we understand the benefits of using Stripe Payment Links, let's take a closer look at how they actually work. At a high level, the payment process begins with the generation of a unique payment link that is sent to the customer. This link contains all the necessary information for the transaction, including the amount to be paid and any additional details required by the business. To generate a payment link, businesses can use Stripe's API or dashboard. The API allows for programmatic creation of links, while the dashboard provides a user-friendly interface for manual creation. Once the link is generated, it can be shared with customers through various channels such as email, SMS, or social media. When a customer clicks on the payment link, they are directed to a secure payment page hosted by Stripe. Here, they can enter their payment details and complete the transaction. Stripe handles all the necessary processing in the background, including authorization, settlement, and reconciliation. Once the payment is successfully processed, both the business and the customer receive confirmation of the transaction. It's important to note that Stripe plays a crucial role in facilitating the payment process. As a trusted payment processor, Stripe securely handles sensitive customer data and ensures that transactions are processed efficiently. Their robust infrastructure and advanced technology enable businesses to accept payments with confidence. ## Creating a Stripe Payment Link Metrics | Description Conversion Rate | The percentage of visitors who clicked on the payment link and completed the payment process. Click-Through Rate | The percentage of visitors who clicked on the payment link out of the total number of visitors who viewed the page. Average Time to Payment | The average amount of time it takes for a visitor to complete the payment process after clicking on the payment link. Abandonment Rate | The percentage of visitors who clicked on the payment link but did not complete the payment process. Revenue | The total amount of money generated from payments made through the payment link. Creating a Stripe Payment Link is a straightforward process that can be done in just a few simple steps. Whether you prefer to use Stripe's API or dashboard, the process is designed to be user-friendly and intuitive. Here is a step-by-step guide to creating a payment link: 1. Log in to your Stripe account and navigate to the "Payments" section. 2. Click on the "Create Payment Link" button. 3. Enter the details of the transaction, including the amount to be paid, currency, and any additional information required by your business. 4. Customize the appearance of the payment page by adding your logo, brand colors, and other branding elements. 5. Choose the payment methods you want to offer to your customers, such as credit cards, digital wallets, or bank transfers. 6. Review the details of the payment link and make any necessary adjustments. 7. Generate the payment link and copy it to your clipboard. 8. Share the payment link with your customers through email, SMS, or social media. By following these steps, you can quickly create a payment link that is ready to be shared with your customers. However, there are a few tips that can help optimize your payment link for maximum effectiveness. Firstly, it's important to clearly communicate the purpose of the payment link to your customers. Include a brief description or message that explains what the payment is for and any relevant details they need to know. This will help reduce confusion and ensure that customers complete their payments accurately. Secondly, consider adding a sense of urgency to your payment link. By setting an expiration date or offering a limited-time discount, you can encourage customers to complete their purchase sooner rather than later. This can help increase conversion rates and drive more sales. Lastly, make sure to test your payment link before sharing it with customers. This will allow you to identify any issues or errors that may prevent customers from completing their payments. By providing a seamless experience for your customers, you can build trust and loyalty in your brand. ## Customizing Your Stripe Payment Link One of the great advantages of using Stripe Payment Links is the ability to customize them to fit your brand and business needs. Stripe offers a range of customization options that allow businesses to create a payment experience that aligns with their brand identity and enhances the customer's perception of their business. Firstly, businesses can add their logo and brand colors to the payment page. This helps create a cohesive and branded experience for customers, reinforcing their trust in the business. By incorporating familiar branding elements, businesses can also increase brand recognition and recall. Additionally, businesses can customize the messaging on the payment page to provide further information or instructions to customers. This can be particularly useful for businesses that require additional details from customers, such as shipping addresses or order specifications. By clearly communicating these requirements, businesses can ensure a smooth and efficient payment process. Furthermore, Stripe allows businesses to customize the URL of their payment links. This can be particularly useful for businesses that want to maintain a consistent branding experience throughout their customer journey. By using a custom domain or subdomain, businesses can reinforce their brand identity and create a seamless transition from their website to the payment page. Examples of how businesses can use customization to their advantage are plentiful. For instance, an e-commerce store specializing in handmade jewelry could customize their payment link with images of their products, creating an immersive shopping experience for customers. Similarly, a subscription-based service could customize their payment link with information about the benefits and features of their service, helping customers make an informed decision. By leveraging the customization options provided by Stripe Payment Links, businesses can create a unique and engaging payment experience that sets them apart from their competitors. This not only enhances the customer's perception of the business but also increases the likelihood of completing the transaction. ## Integrating Stripe Payment Links with Your Website Integrating Stripe Payment Links with your website is a seamless process that allows you to offer a streamlined payment experience to your customers. By embedding payment links directly into your website, you can eliminate the need for customers to navigate away from your site to complete their purchase. This not only enhances the user experience but also increases the likelihood of conversion. To integrate Stripe Payment Links with your website, you will need to have some basic web development knowledge or work with a developer. Here is an overview of the integration process: 1. Ensure that you have a Stripe account and have set up your payment links as described earlier. 2. Determine where on your website you want to place the payment link. This could be on a product page, a checkout page, or any other relevant location. 3. Generate the payment link as described earlier and copy the HTML code provided by Stripe. 4. Paste the HTML code into the appropriate location on your website. 5. Test the integration by making a test purchase and ensuring that the payment link functions correctly. By following these steps, you can seamlessly integrate Stripe Payment Links into your website and provide a frictionless payment experience for your customers. This integration not only enhances the user experience but also offers several benefits for businesses. Firstly, integrating payment links with your website allows you to maintain a consistent branding experience throughout the customer journey. By embedding payment links directly into your website, you can ensure that customers remain within your brand ecosystem from start to finish. This creates a cohesive and immersive experience that reinforces brand loyalty and trust. Secondly, integrating payment links with your website enables you to gather valuable data and insights about your customers' purchasing behavior. By tracking customer interactions with payment links, you can gain insights into conversion rates, average order value, and other key metrics. This data can help inform business decisions and optimize your marketing strategies. Lastly, integrating payment links with your website simplifies the management of payments and reduces administrative overhead. By centralizing all payment-related activities within your website's backend, you can easily track payments, reconcile transactions, and generate reports. This streamlines your business operations and frees up time for other important tasks. Overall, integrating Stripe Payment Links with your website offers numerous benefits for both businesses and customers. By providing a seamless and convenient payment experience, businesses can increase customer satisfaction, drive sales, and build a strong brand reputation. ## Accepting Payments with Stripe Payment Links Accepting payments with Stripe Payment Links is a straightforward process that offers flexibility and convenience for both businesses and customers. Stripe supports a wide range of payment methods, allowing businesses to cater to the preferences of their customers. Let's take a closer look at how payments are processed using Stripe Payment Links. When a customer clicks on a payment link, they are directed to a secure payment page hosted by Stripe. Here, they can choose their preferred payment method from the options provided by the business. Stripe supports various payment methods, including credit cards, digital wallets (such as Apple Pay or Google Pay), and bank transfers. If the customer chooses to pay by credit card, they will be prompted to enter their card details, including the card number, expiration date, and CVV code. Stripe securely handles this information using advanced encryption and tokenization technologies, ensuring that sensitive data is protected. For customers who prefer to use digital wallets, they can simply select their preferred wallet provider (such as Apple Pay) and authenticate the payment using their device's biometric authentication (such as Touch ID or Face ID). This provides a quick and convenient payment experience for customers while maintaining the highest level of security. In addition to credit cards and digital wallets, Stripe also supports bank transfers as a payment method. Customers can choose to pay directly from their bank account by providing their account details. This option is particularly useful for customers who prefer not to use credit cards or digital wallets. Once the customer has entered their payment details and confirmed the transaction, Stripe handles all the necessary processing in the background. This includes authorization, settlement, and reconciliation. Stripe's robust infrastructure and advanced technology ensure that payments are processed efficiently and accurately. For businesses, accepting payments with Stripe Payment Links offers several advantages. Firstly, Stripe provides real-time notifications for successful payments, allowing businesses to fulfill orders or provide access to digital products immediately. This enhances the customer experience and reduces the time between payment and delivery. Secondly, Stripe offers powerful reporting tools that provide valuable insights into sales and revenue trends. Businesses can access detailed reports that show transaction volumes, average order values, and other key metrics. This data can help inform business decisions and optimize marketing strategies. Lastly, Stripe's comprehensive fraud prevention measures help protect businesses from fraudulent transactions. Stripe employs machine learning algorithms and advanced fraud detection techniques to identify and prevent suspicious activities. This reduces the risk of chargebacks and helps businesses maintain a secure payment environment. ## Managing Your Stripe Payment Links Managing your Stripe Payment Links is made easy with the range of management tools provided by Stripe. These tools allow businesses to keep track of their payment links, monitor payments received, and reconcile transactions with their records. Let's take a closer look at the management tools available. Stripe's dashboard provides a centralized location where businesses can view and manage their payment links. From the dashboard, businesses can access detailed information about each payment link, including the amount paid, the customer's details, and any additional information provided by the customer. Businesses can also generate reports that provide insights into sales trends, revenue performance, and other key metrics. These reports can be customized to suit specific business needs and can be exported in various formats for further analysis or integration with other systems. Additionally, Stripe offers powerful search and filtering capabilities that allow businesses to quickly locate specific payment links or transactions. This is particularly useful for businesses that deal with a high volume of transactions or have complex record-keeping requirements. To further streamline the management process, Stripe provides integration options with popular accounting and bookkeeping software. By integrating Stripe with these systems, businesses can automate the reconciliation process and ensure that their financial records are accurate and up to date. Furthermore, Stripe offers a range of developer tools and APIs that allow businesses to build custom solutions or integrate with existing systems. This provides businesses with the flexibility to tailor their payment management processes to their specific needs. By leveraging these management tools, businesses can efficiently track their payment links, monitor payments received, and reconcile transactions. This not only saves time and reduces administrative overhead but also provides valuable insights into sales performance and revenue trends. ## Security Features of Stripe Payment Links Security is a top priority for both businesses and customers when it comes to online payments. With Stripe Payment Links, businesses can rest assured that their transactions are protected by robust security measures. Stripe employs industry-leading security technologies and adheres to strict compliance standards to ensure the highest level of protection. Stripe uses advanced encryption and tokenization technologies to secure sensitive customer data. When a customer enters their payment details on the payment page, this information is encrypted using industry-standard SSL/TLS protocols. This ensures that the data is securely transmitted over the internet and cannot be intercepted or tampered with. Once the payment details are received by Stripe, they are tokenized. Tokenization replaces sensitive data, such as credit card numbers, with unique tokens that have no intrinsic value. These tokens are used for transaction processing and storage, eliminating the need for businesses to handle or store sensitive customer data. Stripe also employs machine learning algorithms and advanced fraud detection techniques to help identify and prevent fraudulent transactions. By analyzing patterns and behaviors in real-time, Stripe can quickly flag suspicious activity and protect both merchants and customers from potential fraud. This proactive approach to fraud prevention helps ensure the security and integrity of transactions processed through the Stripe platform. ## Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/saas-breakthrough-with-ekms-ceo-antony-chesworth/ --- # SaaS breakthrough with EKM's CEO Antony Chesworth | Shuttle > We hosted EKM, the UK ecommerce shopping cart for a chat about how they achieved breakthrough as one of the UK's leading e-commerce platforms. # SaaS breakthrough with EKM's CEO Antony Chesworth By Nick Dunse, October 19, 2023 We hosted EKM, the UK ecommerce shopping cart for a chat about how they achieved breakthrough as one of the UK's leading e-commerce platforms. We hosted EKM, the UK ecommerce shopping cart for a chat about how they achieved breakthrough as one of the UK's leading e-commerce platforms. Some highlights: - No regrets, do something that you love - Overnight takes years - Employ for the gaps and do what you're good at - Entrepreneurs need to become rounded individuals - Sales is one of the greatest skillsets you can have/learn - Passion drives you forward daily - EKM have differentiated by offering coaching services to their sellers ## Related Reading Explore More ### When Your SaaS Outgrows Stripe Connect: A Migration Playbook ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideWhen Your SaaS Outgrows Stripe Connect: A Migration Playbook→](/guides/when-saas-outgrows-stripe-connect/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/sage-invoice-payments/ --- # Sage Invoice Payments: How to Let Customers Pay Online | Shuttle > Add online payment options to Sage 50, Sage 200, Sage Intacct, and Sage Business Cloud invoices. Use your own gateway, keep your rates. # Sage Invoice Payments: How to Let Customers Pay Online By Shuttle Team, March 14, 2026 Add online payment options to Sage 50, Sage 200, Sage Intacct, and Sage Business Cloud invoices. Use your own gateway, keep your rates. Talk to us Make enabling payments for your platform and merchant users easy. ## Why Sage Users Struggle to Collect Invoice Payments Sage is the UK's most widely used accounting software. Over a million UK businesses run their finances on Sage 50, Sage 200, or Sage Intacct. But when it comes to collecting invoice payments, Sage leaves a gap. Sage's built-in payment options are limited: - Sage 50 (Desktop) -- No built-in online payment option. Invoices go out by email or post with bank details. Customers have to manually pay by bank transfer. - Sage Business Cloud Accounting -- Supports Stripe and PayPal integrations for online payments, but the checkout is Stripe/PayPal-branded and limited to cards or PayPal balance. - Sage Intacct -- Enterprise ERP with no native payment collection. Designed for financial management, not payment processing. - Sage 200 -- On-premise/cloud ERP for mid-market. No built-in payment links or online checkout. In every case, the gap is the same: Sage handles invoicing beautifully, but the "how does the customer actually pay" step is either missing or locked to a single provider with limited options. This is why the average Sage user waits weeks for invoice payments -- not because Sage is slow, but because the payment step adds friction. ## How Payment Links Fill the Gap A payment link is a unique URL tied to a specific invoice amount. You generate the link, add it to your Sage invoice (in the email body, notes field, or as a QR code), and the customer clicks through to a branded checkout page where they can pay instantly. The critical difference: payment links work with your existing payment gateway. If you have a merchant account with Worldpay, Adyen, Authorize.net, or any of 40+ providers, you can use it. No switching gateways, no new processing agreements, no changing your Sage setup. ### The Workflow - Create your invoice in Sage -- line items, VAT, due date, as normal. - Generate a payment link -- enter the invoice amount, currency, and invoice number as a reference. - Add the link to the invoice -- paste it into the email message or invoice notes. For posted invoices, add a QR code. - Send the invoice -- the customer receives it with a clickable pay-now link. - Customer pays -- branded checkout page, multiple payment methods, done in 60 seconds. - Reconcile in Sage -- match the bank receipt to the invoice using the reference number. This works with Sage 50, Sage 200, Sage Intacct, and Sage Business Cloud. The payment link is external to Sage -- it doesn't require any plugins, add-ons, or changes to your Sage configuration. ## What Sage Users Get With Payment Links ### Use Your Existing Gateway Sage's Stripe integration means you're paying Stripe's standard rates (1.4% + 20p for UK cards). If you've negotiated better rates with another provider -- or if your business requires a specific acquirer for regulatory reasons -- payment links let you keep your existing setup. This matters especially for professional services firms (law firms with SRA-compliant trust accounts, accountancies with client money requirements) and B2B companies with enterprise clients who mandate specific PSPs. ### Multiple Payment Methods Sage + Stripe gives you cards. Payment links give you cards, bank transfer, Apple Pay, Google Pay, and Open Banking -- all from the same checkout page. UK businesses especially benefit from Open Banking (instant bank-to-bank, lower fees than cards) and Apple Pay (frictionless on mobile). ### White-Label Branding When your customer clicks a payment link, they see your company name, logo, and brand colours on the checkout page -- not Stripe's or PayPal's. For businesses where trust and professionalism matter (accountants, solicitors, consultancies), this makes a real difference to completion rates. See our guide on white-label payment links. ### Multi-Channel Collection Sage sends invoices by email. When the email gets ignored, payment links let you chase through other channels: - Day 7: Resend the link via email reminder - Day 14: Send via SMS (98% open rate vs ~20% for email) - Day 30: Send via WhatsApp - Day 45: Include in a formal dunning letter as a QR code This multi-channel approach is particularly effective for Sage 50 users who deal with older or less tech-savvy customers -- the same payment link works across every channel, meeting customers where they are. ## Sage 50 vs Sage Business Cloud vs Sage Intacct: Payment Link Setup ### Sage 50 (Desktop) Sage 50 has no native online payment option. This actually makes payment links the simplest upgrade -- there's nothing to conflict with. Setup: Generate a payment link per invoice. Add it to the email body when sending the invoice from Sage 50's "Email Invoice" feature. If posting invoices, add a QR code to the PDF template. Automation: Sage 50 has limited API access, so most businesses generate payment links manually (30 seconds per invoice) or use a CSV export to batch-generate links. ### Sage Business Cloud Accounting Sage Business Cloud has Stripe and PayPal integrations. You can keep these active and add payment links as an additional option. Setup: Paste the payment link into the invoice "Notes" or "Message" field before sending. The customer sees both the Sage/Stripe pay button and your payment link -- they choose whichever they prefer. Automation: Sage Business Cloud has an API. Use it with Zapier/Make to auto-generate a payment link when an invoice is created, then update the invoice notes with the link URL. ### Sage Intacct Sage Intacct is an enterprise ERP with no payment collection features. For Intacct users, payment links are typically integrated via API: Setup: When an invoice is approved in Intacct, trigger a payment link generation via API. The link is included in the invoice email sent from Intacct or your email system. Automation: Intacct's robust API makes this straightforward. Most implementations use webhooks: invoice created/approved in Intacct → payment link generated → added to communication template → sent to customer. ### Sage 200 Similar to Sage Intacct but for mid-market. Sage 200 has an API that supports invoice events. Payment links can be auto-generated and attached to invoice emails. ## Who This Is For Payment links for Sage invoices work best for: - Accounting practices collecting fees from clients -- especially firms using Sage for their own billing. Payment links on invoices reduce "I'll pay it when I remember" to "I'll pay it now." - Construction and trades using Sage 50 -- stage payments, retention releases, and final invoices can all include payment links. The QR code option works well for on-site invoicing. - [Professional services](/guides/payment-collection-professional-services/) (solicitors, surveyors, consultancies) -- where invoices are large, trust matters, and white-label branding is important. - Recruitment agencies -- high-volume invoicing with tight cash flow. Automating payment links on every invoice cuts DSO significantly. - [Property management](/guides/payment-links-property-management/) -- rent collection, service charges, deposit handling. Payment links work alongside existing Sage ledger management. ## Common Questions ### Do I need to change anything in Sage? No. Payment links are external to Sage. You don't install plugins, change settings, or modify your chart of accounts. You simply add a URL to the invoice email or notes. Sage continues to work exactly as it does now. ### How do I reconcile payments in Sage? The same way you reconcile any bank receipt -- match it to the invoice using the reference number. Each payment link carries your invoice number as a reference, so it appears on the bank statement with the right identifier. ### What does it cost? Payment link providers typically charge per transaction (at your gateway's rates, not the link provider's). There's no monthly fee for generating links with most providers. If you're already paying Stripe 1.4% + 20p through Sage's integration, you'd pay your own gateway's rates instead -- which may be lower if you've negotiated. ### Can I offer direct debit through Sage? For recurring payments (retainers, monthly service fees), you can combine payment links with GoCardless direct debit. Payment links handle one-off invoice payments; direct debit handles recurring collections. Both can work alongside Sage. ## Get Started Sage handles your invoicing and accounts. Payment links handle getting paid. You don't need to switch accounting software, change your payment provider, or install anything. Shuttle Payment Links work with 40+ gateways, support white-label branding, and deliver payment links via email, SMS, WhatsApp, and QR code. See how it works. ## Related Reading Explore More ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Worldpay](/blog/payment-links-for-worldpay/) - [Adyen](/payment-providers/adyen/) - [Authorize.net](/blog/payment-links-for-authorize-net/) - [any of 40+ providers](/payment-providers/) - [professional services](/guides/payment-collection-professional-services/) - [B2B companies](/guides/b2b-payment-collection/) - [Open Banking](/blog/what-is-open-banking-and-pisp/) - [white-label payment links](/guides/white-label-payment-links/) - [email reminder](/blog/payment-reminder-email-templates/) - [dunning letter](/blog/dunning-letter-templates/) - [multi-channel approach](/guides/multi-channel-payment-collection/) - [GoCardless](/blog/payment-links-for-gocardless/) - [40+ gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/savour-the-convenience-how-payment-links-are-revolutionizing-food-and-beverage-ordering/ --- # Savour the Convenience: How Payment Links are Revolutionizing Food and Beverage Ordering | Shuttle > Explore how food and beverage businesses use payment links to speed up ordering, reduce queues, and offer flexible payment options to customers. # Savour the Convenience: How Payment Links are Revolutionizing Food and Beverage Ordering By Nick Dunse, February 7, 2022 Explore how food and beverage businesses use payment links to speed up ordering, reduce queues, and offer flexible payment options to customers. Talk to us Make enabling payments for your platform and merchant users easy. Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. Introduction: The Rise of Payment Links in Food and Beverage Ordering In recent years, payment links have become increasingly popular in the food and beverage industry. These links provide a convenient and efficient way for customers to make payments for their orders, whether it's for a meal at a restaurant or a beverage at a café. With the rise of contactless payment and the increasing demand for convenience, payment links have emerged as a game-changer in the industry. The Convenience of Payment Links: A Game-Changer for Customers Payment links offer a level of convenience that was previously unheard of in the food and beverage industry. Customers no longer need to carry cash or wait for the bill to be brought to their table. Instead, they can simply click on a link and make their payment instantly. This not only saves time but also eliminates the need for physical contact, which is especially important in today's world. Payment links can be used in a variety of scenarios to make ordering food and beverages even more convenient. For example, customers can use payment links to order ahead and pay for their meal or drink before they arrive at the restaurant or café. This allows them to skip the line and have their order ready for them when they arrive. Payment links can also be used to split bills among a group of friends, eliminating the need for complicated calculations and awkward conversations. How Payment Links are Streamlining the Ordering Process for Restaurants and Cafes Not only do payment links benefit customers, but they also streamline the ordering process for restaurants and cafes. By integrating payment links into their existing systems, businesses can simplify the entire process from ordering to payment. For example, payment links can be integrated into point-of-sale (POS) systems, allowing customers to make payments directly from their mobile devices. This integration eliminates the need for manual input of payment information, reducing the risk of errors and speeding up the transaction process. It also allows businesses to track and manage payments more efficiently, providing them with valuable data and insights into customer preferences and behavior. Overall, payment links help businesses operate more smoothly and efficiently, saving time and resources. The Benefits of Payment Links for Small Businesses in the Food and Beverage Industry Payment links offer numerous benefits for small businesses in the food and beverage industry. One of the main advantages is cost savings. Small businesses often have limited budgets and resources, and payment links provide a cost-effective solution for accepting payments. They eliminate the need for expensive card terminals or other hardware, reducing upfront costs and ongoing maintenance expenses. Furthermore, payment links level the playing field for small businesses, allowing them to compete with larger chains. By offering a convenient and seamless payment experience, small businesses can attract and retain customers who value convenience and efficiency. This can help them build a loyal customer base and differentiate themselves from their competitors. Contactless Payment: The Future of Food and Beverage Ordering Payment links are perfectly aligned with the trend towards contactless payment in the food and beverage industry. With the increasing popularity of mobile wallets and contactless cards, customers are looking for ways to make payments without physical contact. Payment links provide a secure and convenient solution that meets this demand. By embracing payment links, businesses can adapt to changing customer preferences and stay ahead of the curve. They can offer a seamless contactless payment experience that not only meets customer expectations but also enhances their overall dining or drinking experience. This can help businesses attract new customers and build a positive reputation in the industry. Payment Links and Online Ordering: A Perfect Match for Busy Customers Payment links can be used in conjunction with online ordering systems to provide a seamless and convenient experience for busy customers. Many people today lead busy lives and don't have the time to wait in line or sit down at a restaurant or café. By offering online ordering with payment links, businesses can cater to these customers and provide them with a quick and efficient way to order and pay for their food or beverages. Busy customers can simply browse the menu, select their items, and make their payment using a payment link. They can then pick up their order at a designated time without having to wait in line or interact with staff. This not only saves time but also allows customers to enjoy their meal or drink on their own schedule, whether it's during a lunch break or on the way home from work. How Payment Links are Enhancing the Customer Experience in Food and Beverage Ordering Payment links have the potential to greatly enhance the overall customer experience in food and beverage ordering. By offering a seamless and convenient payment process, businesses can leave a lasting impression on their customers. For example, payment links can be used to personalize the ordering process by allowing customers to save their payment information and preferences for future orders. Furthermore, payment links can be integrated with loyalty programs to provide additional benefits for customers. For example, customers can earn points or rewards for using payment links, encouraging them to return and make repeat purchases. This not only increases customer retention but also helps businesses build a loyal customer base. Payment Links and Loyalty Programs: A Winning Combination for Restaurants and Cafes Payment links can be used in conjunction with loyalty programs to create a winning combination for restaurants and cafes. By integrating payment links with their loyalty programs, businesses can offer a seamless and convenient experience for customers while also increasing customer retention. For example, customers can earn points or rewards for using payment links to make their purchases. These points can then be redeemed for discounts or free items, providing an incentive for customers to return and make repeat purchases. This not only encourages customer loyalty but also helps businesses build a positive reputation and differentiate themselves from their competitors. The Security of Payment Links: Protecting Customers and Businesses Alike One of the main concerns when it comes to online payments is security. However, payment links are designed to be secure and protect both customers and businesses. Payment links use encryption technology to ensure that sensitive payment information is transmitted securely and cannot be intercepted by hackers or other malicious actors. Businesses can further enhance the security of their payment links by implementing additional security measures, such as two-factor authentication or fraud detection systems. By taking these steps, businesses can provide their customers with peace of mind and build trust in their brand. Conclusion: The Bright Future of Payment Links in Food and Beverage Ordering In conclusion, payment links have revolutionized the food and beverage industry by providing a convenient and efficient way for customers to make payments. They streamline the ordering process for businesses, save time and resources, and help small businesses compete with larger chains. Payment links also fit into the trend towards contactless payment and can be used in conjunction with online ordering systems to cater to busy customers. Furthermore, payment links enhance the overall customer experience by providing a seamless and personalized payment process. They can be used in conjunction with loyalty programs to increase customer retention and build a loyal customer base. With their security features, payment links protect both customers and businesses and provide peace of mind. As the demand for convenience and contactless payment continues to grow, payment links are poised to play an even bigger role in the food and beverage industry. They have the potential to continue revolutionizing the industry and providing a seamless and convenient experience for customers. Businesses that embrace payment links will be well-positioned to thrive in the future. Get Payment Links today ## Related Reading Explore More ### Payment Infrastructure for Food Ordering Platforms ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuidePayment Infrastructure for Food Ordering Platforms→](/guides/food-ordering-platform-payments/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/ --- # Secure Payment Links: Card Authorization Made Simple | Shuttle > Learn how secure payment links simplify card authorization, reduce PCI scope, and replace risky phone or email card collection for businesses and... # Secure Payment Links: Card Authorization Made Simple By Nick Dunse, May 26, 2020 Learn how secure payment links simplify card authorization, reduce PCI scope, and replace risky phone or email card collection for businesses and... Talk to us Make enabling payments for your platform and merchant users easy. Taking card details over the phone, through email, or on paper forms is a security risk that exposes businesses to fraud and PCI compliance headaches. Secure payment links solve this by giving customers a hosted checkout page where they can enter their card details directly -- no sensitive data passes through your staff, your systems, or your inbox. Whether you need to pre-authorize a card for a hotel booking, collect a deposit, or set up recurring billing, a secure payment link lets you do it in seconds. You send a URL by email, SMS, or chat. The customer clicks, enters their card details on a PCI-compliant page, and the authorization is complete. This guide covers how payment links work for card authorization, why they are more secure than traditional methods, and how to choose the right provider -- whether you are a single merchant or a platform embedding payments for thousands of sub-merchants. ## What Are Payment Links and How Do They Work? A payment link is a URL that points to a hosted checkout page. When a customer clicks the link, they see a form where they can enter their card number, expiry date, and CVV. The payment is processed through a payment gateway, and the merchant receives confirmation -- all without handling card data themselves. Payment links can be configured for different transaction types: - Full payment -- charge the card immediately for a fixed amount - Pre-authorization -- reserve funds on the card without capturing them (common for hotels and car rentals) - Card-on-file tokenization -- save the card securely for future charges or recurring billing - Deposit collection -- charge a partial amount upfront with the balance due later The hosted page handles all the security: TLS encryption in transit, tokenization of card data, and 3D Secure authentication where required. The merchant never sees or stores the raw card number. ## Why Secure Payment Links Beat Phone and Email Collection Businesses that take card details over the phone or by email face serious security and compliance risks. An agent reading back a card number, a PDF form sitting in an inbox, or a sticky note on a desk -- these are all attack surfaces. A single data breach can result in fines, chargebacks, and reputational damage. Secure payment links eliminate these risks by keeping card data out of your environment entirely. Here is how they compare to traditional methods: - Phone payments -- agents hear and may record card numbers, putting you in scope for PCI DSS call recording requirements. Contact centre payment solutions like DTMF masking exist, but payment links are simpler: send the link mid-call and let the customer self-serve. - Email or PDF forms -- card details sit in plaintext in inboxes and on servers. This violates PCI DSS requirement 3 (protect stored cardholder data) and requirement 4 (encrypt transmission). - Manual card entry terminals -- keying in a card number read over the phone (MOTO transactions) still puts your systems in PCI scope and does not support 3D Secure. With a payment link, the customer enters their own card details on a page hosted by the payment provider. Your staff, your CRM, and your phone system never touch the card number. This is the most effective way to reduce your attack surface. ## PCI Compliance Benefits: Reducing Scope to SAQ-A PCI DSS compliance is mandatory for any business that accepts card payments. The level of effort depends on how much cardholder data your systems handle. There are several Self-Assessment Questionnaires (SAQs), ranging from SAQ-A to SAQ-D. When you use a hosted payment link -- where the entire checkout page is served by your payment provider -- your business typically qualifies for SAQ-A, the lightest compliance tier. This is because card data never enters your environment. It is collected, encrypted, and stored entirely by the provider. For a deeper look at PCI requirements and how they affect different business types, see our introduction to PCI compliance for merchants and service providers. The compliance savings are significant. Businesses that handle card data themselves often need quarterly vulnerability scans, penetration testing, and formal security policies. With payment links and SAQ-A, most of those requirements fall away -- saving time, money, and audit overhead. ## Use Cases for Secure Payment Link Authorization Payment links are versatile. Here are the most common scenarios where they replace manual card collection: Hotel pre-authorizations and deposits. Hotels routinely pre-authorize a guest's card before check-in to guarantee the reservation and cover incidentals. Instead of asking for card details over the phone or through an insecure booking form, the hotel sends a payment link. The guest authorizes their card on a secure page, and the hotel can capture or release the funds as needed. Recurring billing setup. Subscription businesses and membership organizations can use payment links to securely tokenize a customer's card for future charges. The customer clicks the link, enters their card, and the token is stored for recurring use -- no card details ever pass through the merchant's systems. B2B invoicing. Rather than chasing bank transfers or processing cheques, B2B sellers can attach a payment link to each invoice. The buyer clicks, pays by card, and the seller receives funds faster with automatic reconciliation. Service deposits and quotes. Tradespeople, agencies, and professional services firms can send a payment link alongside a quote or contract. The client pays the deposit instantly, confirming the booking without back-and-forth over payment details. Social commerce. Sellers on Instagram and TikTok use payment links to close sales in DMs. Instead of directing buyers to a full ecommerce checkout, a single link completes the transaction. See our guides on payment links for Instagram sales and payment links for TikTok sales for detailed walkthroughs. Debt collection and call centres. Agents can send a payment link via SMS during a call instead of taking card details verbally. This removes PCI scope from the call recording infrastructure and gives the customer a more comfortable payment experience. ## How to Send Secure Payment Links to Clients One of the biggest advantages of payment links is channel flexibility. You can deliver the same secure checkout URL through whatever channel your customer prefers: - Email -- embed the link in an invoice email, a booking confirmation, or a standalone payment request. Most payment providers offer branded email templates. - SMS -- text messages have open rates above 90%, making SMS the most effective channel for time-sensitive payment requests. Ideal for debt collection, appointment deposits, and overdue invoices. - Chat and messaging apps -- WhatsApp, Facebook Messenger, and live chat widgets all support clickable links. Agents can paste the payment URL directly into the conversation. - QR codes -- encode the payment link as a QR code for in-person scenarios. Useful at events, on printed invoices, or at reception desks. Regardless of the channel, the security model is the same: the link points to a hosted page that handles all card data collection and encryption. The channel is just the delivery mechanism. ## Cash App, Venmo, and Consumer Payment Links Consumer payment apps like Cash App and Venmo also offer payment link functionality, though they work differently from business-grade payment links. Understanding the differences matters if you are deciding which approach fits your needs. Cash App payment links (cash.app/$cashtag) let individuals and small businesses receive payments by sharing a simple URL. Senders can pay via their Cash App balance, linked bank account, or card. Cash App supports both personal transfers and Cash App Pay for business, with a 2.75% fee for business transactions. Venmo payment links work similarly through venmo.com/u/username URLs. Venmo business profiles allow merchants to accept payments with buyer protection, at a 1.9% + $0.10 fee. While these consumer apps are convenient for peer-to-peer payments and small businesses, they have limitations for larger operations: - No pre-authorization or tokenization -- you cannot hold funds or set up recurring billing - Limited branding -- the checkout experience is controlled by Cash App or Venmo, not your brand - No API integration -- you cannot generate links programmatically or embed them in your platform's workflow - US-only -- both services are limited to US-based senders and receivers For businesses that need card authorization, pre-auth, or white-labelled checkout experiences, a dedicated payment link provider is the better choice. ## Choosing a Secure Payment Link Provider Not all payment link solutions are equal. When evaluating providers, consider these factors: - Hosted vs embedded -- fully hosted pages (like Stripe Checkout) reduce PCI scope the most. Embedded iframes offer more branding control but may require SAQ A-EP. - Transaction types supported -- can the link handle pre-authorizations, tokenization, and partial captures? Not all providers support these. - Branding and customization -- can you add your logo, colours, and domain? White-label payment links build trust and reduce drop-off. - API and automation -- can you generate links programmatically via API? This is essential for platforms that need to create payment links on behalf of their merchants at scale. - Expiry and security controls -- look for link expiry, single-use enforcement, and fraud screening (AVS, 3D Secure). - Multi-currency and international coverage -- if you operate across borders, ensure the provider supports the currencies and card schemes your customers use. For platforms and SaaS companies that need to offer payment links to their own merchants, the key question is whether you can white-label the experience. Your merchants should see their own brand, not yours or the payment provider's. ## For Platforms: White-Label Secure Payment Links at Scale If you run a platform -- a marketplace, a SaaS product, a booking system, or any software where your customers are businesses that collect payments -- you need more than a single-merchant payment link tool. You need the ability to generate branded, secure payment links on behalf of each merchant, with funds routed to the right destination, and compliance handled centrally. Shuttle Global's embedded payments platform does exactly this. Platforms can offer white-labelled payment links to their merchants via API -- each link is branded to the merchant, processes through the platform's payment stack, and keeps the platform in control of the payment experience. Pre-authorizations, tokenization, and full PCI compliance are built in. This matters because most payment link tools are designed for individual merchants, not for platforms distributing payment capabilities to hundreds or thousands of sub-merchants. If you are evaluating how to add payment links to your platform, book a discovery call to see how it works. ## Best Practices for Sending Secure Payment Links To maximize conversion rates and maintain security, follow these practices when using payment links: - Set expiry dates. Links that never expire are a security risk. Set expiry to match the use case: 24 hours for invoices, 7 days for deposits, 30 minutes for phone-assisted payments. - Use single-use links where possible. A link that can only be paid once prevents accidental double payments and reduces the window for fraud. - Brand the checkout page. Customers are more likely to complete payment when they recognize the business name and logo on the payment page. Generic-looking checkouts raise suspicion. - Include context in the message. Tell the customer what the payment is for, the amount, and any reference number. This reduces support queries and abandoned links. - Enable 3D Secure. 3DS adds a second authentication step (like a bank app approval) that shifts chargeback liability to the card issuer and reduces fraud. - Track link status. Use webhooks or your provider's dashboard to monitor which links have been opened, completed, or expired. Follow up on unpaid links promptly. ## Frequently Asked Questions ### Are payment links safe for customers? Yes. A secure payment link directs customers to a PCI DSS-compliant hosted page that encrypts card data in transit and at rest. The customer's card details are never exposed to the merchant's staff or systems. Look for providers that support HTTPS, 3D Secure authentication, and tokenization to ensure the highest level of protection. ### Can payment links be used for pre-authorization holds? Yes, many payment link providers support pre-authorization (also called auth-only) transactions. The link reserves funds on the customer's card without capturing them. The merchant can later capture the full amount, a partial amount, or release the hold entirely. This is commonly used by hotels, car rental companies, and event venues. ### How do secure payment links reduce PCI compliance scope? When you use a fully hosted payment link, card data is collected and processed entirely by the payment provider. Your business systems never handle, transmit, or store cardholder data. This typically qualifies you for SAQ-A, the simplest PCI self-assessment -- reducing the number of compliance requirements from over 300 (SAQ-D) to just 22. ### What is the difference between a payment link and a payment gateway? A payment gateway is the underlying technology that processes card transactions -- it handles authorization, fraud checks, and settlement. A payment link is a user-facing URL that points to a hosted checkout page powered by a payment gateway. Think of the payment link as the front door and the gateway as the engine behind it. ### Can I send payment links through Cash App or Venmo? Cash App and Venmo both offer payment link-style URLs ($cashtag links and venmo.com/u/ links). These work well for peer-to-peer payments and small business transactions. However, they do not support pre-authorization, card tokenization, or white-label branding -- so they are not suitable for businesses that need card authorization workflows or platform-level payment distribution. ## Related Reading Explore More ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Contact centre payment solutions](/guides/contact-centre-payments/) - [DTMF masking](/guides/dtmf-payments/) - [introduction to PCI compliance for merchants and service providers](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [payment links for Instagram sales](/blog/payment-links-for-instagram-sales/) - [payment links for TikTok sales](/blog/payment-links-for-tiktok-sales/) - [Stripe Checkout](/payment-providers/stripe/) - [embedded payments platform](/platforms/) - [book a discovery call](/discovery/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/should-i-use-account-updater-services-for-card-payments/ --- # Account Updater Service: How It Works for Card Payments | Shuttle > What account updater services do, how Visa VAU and Mastercard ABU work, costs, benefits for recurring billing, and when your business should enable one. # Account Updater Service: How It Works for Card Payments By Nick Dunse, March 25, 2022 What account updater services do, how Visa VAU and Mastercard ABU work, costs, benefits for recurring billing, and when your business should enable one. Talk to us Make enabling payments for your platform and merchant users easy. Every stored card has a shelf life. Cards expire, get replaced after fraud, or are reissued when a bank merges. When that happens, the token or card number your system has on file stops working -- and the next recurring charge declines. Account updater services solve this by automatically refreshing stored card credentials before they go stale. For subscription businesses and platforms managing recurring billing, account updaters are one of the simplest ways to reduce involuntary churn and recover revenue that would otherwise be lost to failed payments. This guide explains what account updater services are, how the major card network programmes work, what they cost, and when they make sense for your business. ## What Is an Account Updater Service? An account updater service is a mechanism provided by the card networks that automatically updates stored card details -- card numbers, expiry dates, and account status -- when an issuing bank replaces or renews a cardholder's card. Without account updater, a merchant storing a card-on-file for recurring billing would need to contact the customer manually when their card details change. Most customers never proactively update their payment method. They only notice when a charge fails -- by which point many have already churned. Account updater runs in the background. Your payment gateway or PSP submits your stored card credentials to the relevant card network on a regular cycle. The network checks with the issuing bank and returns updated details -- a new card number, a new expiry date, or a notification that the account has been closed. Your system then stores the refreshed credentials, and the next recurring charge goes through without the customer doing anything. ## How Account Updaters Work: Visa VAU and Mastercard ABU Each major card network operates its own account updater programme. The two largest are Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU). While they serve the same purpose, there are differences in how they operate. ### Visa Account Updater (VAU) Visa VAU lets acquirers and merchants submit batches of stored Visa card credentials to Visa's database. Visa checks these against issuer records and returns updated account numbers, expiry dates, or closure notifications. VAU supports both batch processing (daily or weekly cycles) and real-time queries. Real-Time VAU lets merchants request an update immediately before processing a transaction, which is useful for high-value charges or dormant cards. ### Mastercard Automatic Billing Updater (ABU) Mastercard ABU works similarly. Merchants or their acquirers submit stored Mastercard credentials, and ABU returns updated details from participating issuers. ABU primarily uses batch processing -- merchants submit files on a regular schedule and receive response files with any updates. ### Other Network Programmes American Express offers a similar service through its Cardrefresher programme, and Discover runs its own account updater. Coverage varies by market -- Visa and Mastercard have the broadest issuer participation globally, while Amex and Discover participation depends more heavily on region. In all cases, the account updater service depends on issuer participation. If a cardholder's bank does not participate in the programme, the update request will return no match and the merchant will need to contact the customer directly. ## Benefits of Using an Account Updater Service The core value of account updater is straightforward: fewer failed payments. But the downstream effects matter more than the headline number. Reduced involuntary churn. Most subscription businesses lose 3-5% of customers each month to payment failures, not cancellations. Account updater addresses the largest cause -- expired or reissued cards. Businesses that enable it typically see a 1-3% improvement in recurring payment success rates. Better customer retention. When a recurring payment fails, the customer receives a notification to update their card. Many never do -- the subscription lapses, and re-acquisition costs far more than retention. Account updater keeps the payment method current without customer action. Lower decline rates. Payment declines affect your merchant account health. Consistently high decline rates can lead to higher processing fees, increased scrutiny, or account reviews from your acquirer. Account updater helps keep your decline ratio in a healthy range. Fewer support tickets. Failed payments generate customer service volume: dunning emails, payment retry notifications, and support tickets from confused customers. Account updater reduces all of these by preventing the failure in the first place. ## Account Updater Costs and Pricing Account updater pricing depends on how you access it. There are generally three cost components to consider. Network fees. Visa and Mastercard charge per-inquiry fees, typically in the range of $0.01 to $0.05 per card checked. These fees apply whether or not an update is returned. If you submit 100,000 stored cards for checking, you pay for 100,000 inquiries. PSP or gateway fees. Most merchants access account updater through their PSP rather than connecting to the card networks directly. PSPs like Stripe and Adyen bundle account updater into their platform. Stripe includes it automatically for saved cards at no additional charge. Adyen charges a small per-update fee. Other gateways may charge a monthly service fee or a per-inquiry fee on top of the network cost. Opportunity cost of not using it. The real question is not whether account updater costs money -- it does -- but whether the cost exceeds the revenue recovered. For most subscription or recurring-billing businesses, the maths works comfortably. If you process 10,000 recurring charges per month and account updater prevents even 1% of those from failing, you're recovering 100 transactions per month for a few hundred pounds in fees. ## When to Use Account Updater Account updater is most valuable when your business relies on stored card credentials that are charged repeatedly over time. The longer the billing relationship, the higher the likelihood that card details will change. Subscription and SaaS businesses. Monthly or annual subscriptions are the classic use case. A customer signs up, enters their card once, and expects to be billed indefinitely. Over a 12-month subscription, there is a meaningful probability that the card on file will be reissued. Recurring billing and instalments. Insurance premiums, loan repayments, membership dues, and instalment plans all depend on the stored card remaining valid throughout the payment schedule. Platforms managing payments for sub-merchants. If you operate a platform that processes recurring payments on behalf of many merchants -- across one or more PSPs -- account updater becomes essential at scale. A 2% failure rate across thousands of sub-merchants compounds into significant revenue loss and operational burden. On-demand and marketplace businesses. Even without a fixed billing schedule, businesses that store cards for future use (ride-hailing, food delivery, marketplaces) benefit. A customer returning after three months may find their stored card has been replaced. If your business only processes one-time payments and does not store cards, account updater provides no benefit. ## Limitations of Account Updater Account updater is effective but not comprehensive. Understanding its limitations helps you build a complete payment recovery strategy rather than relying on a single mechanism. Issuer participation is not universal. Account updater only works when both the acquirer and the issuing bank participate. Major issuers in the US and Europe have high participation rates, but coverage is lower in parts of Asia, Latin America, and Africa. It only covers card-on-file credentials. Account updater does not help with payment methods beyond cards. If you accept direct debit, bank transfers, or digital wallets, you need separate strategies for keeping those methods current. Closed accounts are reported, not recovered. When a cardholder closes their account entirely, account updater returns a "contact cardholder" or "account closed" response. You still need a dunning process to collect an alternative payment method. Timing gaps exist. Batch-based account updater runs on a schedule -- often daily or weekly. If a card is reissued and a payment is attempted before the next cycle, it may still decline. Real-time account updater addresses this where available, but not all PSPs support it. It does not fix insufficient funds. Account updater handles credential staleness, not spending limits or balance. Declines due to insufficient funds, fraud blocks, or velocity limits require a separate retry strategy. ## Alternatives and Complementary Strategies Account updater is one part of a broader payment recovery toolkit. Most businesses that take recurring payments seriously use several of these strategies together. Network tokens. Network tokenisation replaces the card PAN with a token that is automatically updated by the network when card details change. Unlike account updater, which is a periodic batch query, network tokens are "living" credentials that stay current by design. If your PSP supports network tokens, they may reduce or eliminate the need for traditional account updater queries. Smart retries. Intelligent retry logic attempts failed payments at optimal times -- retrying after payday, spreading retries across different times of day, or varying merchant category codes. This addresses declines that account updater cannot fix, such as insufficient funds. Dunning and customer outreach. When automated methods fail, you need a process to contact the customer and request updated payment details -- email, SMS, or in-app notifications. Effective fraud prevention measures also reduce the number of cards that get cancelled and reissued due to fraud in the first place. Multi-PSP routing. Platforms routing payments across multiple PSPs can sometimes recover failed transactions by retrying through a different acquirer. If you manage payments across several providers, a discovery layer that orchestrates routing can combine account updater with smart retries and failover logic in a single workflow. ## Account Updater FAQ ### How much does account updater cost per card? Network inquiry fees typically range from $0.01 to $0.05 per card checked. Some PSPs bundle it at no extra cost (Stripe includes it for saved cards), while others charge a per-update or monthly fee. The cost per successful update is almost always lower than the revenue lost to a single failed recurring payment. ### Does account updater work for all card brands? Visa (VAU), Mastercard (ABU), American Express (Cardrefresher), and Discover each operate their own programmes. Visa and Mastercard have the broadest issuer participation globally. Coverage depends on whether the cardholder's issuing bank participates -- major issuers in the US and Europe generally do, but participation varies elsewhere. ### Can customers opt out of account updater? Yes. Cardholders can contact their issuing bank to opt out of account updater programmes. When they do, updated card details will not be shared with merchants through VAU or ABU. In practice, opt-out rates are very low -- most cardholders are unaware the service exists and benefit from not having to manually update payment details across multiple subscriptions. ### What is the difference between account updater and network tokens? Account updater is a periodic query service -- you submit stored card details and receive updates if anything has changed. Network tokens are fundamentally different: the card network issues a token that replaces the PAN and is automatically kept current. Network tokens generally have higher authorisation rates and do not require batch cycles. Many PSPs support both, and the industry is shifting toward network tokens as the preferred long-term solution for credential lifecycle management. ## Related Reading Explore More ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Gupshup Payments: UPI and WhatsApp Pay vs Multi-PSP Card Capture ### HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies ### Observe.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment gateway](/blog/what-is-a-payment-gateway/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [platform](/platforms/) - [fraud prevention](/blog/a-merchants-guide-to-ecommerce-fraud-prevention/) - [discovery layer](/discovery/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideGupshup Payments: UPI and WhatsApp Pay vs Multi-PSP Card Capture→](/guides/gupshup-payments/) - [GuideHubSpot International Payments: Accepting Cards Outside the Big 5 Currencies→](/guides/hubspot-international-payments/) - [GuideObserve.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres→](/guides/observe-ai-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-brightpearl/ --- # Shuttle and Brightpearl Partner to enable invoice and POS Payments for Global Retailers | Shuttle > 1 December 2019 Brightpearl, a leading retail operations platform for brands and retailers, uses Shuttle to power it's payment features. # Shuttle and Brightpearl Partner to enable invoice and POS Payments for Global Retailers By Nick Dunse, December 1, 2019 1 December 2019 Brightpearl, a leading retail operations platform for brands and retailers, uses Shuttle to power it's payment features. 1 December 2019 Brightpearl, a leading retail operations platform for brands and retailers, uses Shuttle to power it's payment features. With this collaboration, retailers using Brightpearl can now integrate their preferred payment providers and get their invoices paid online. Brightpearl Payments is now able to work with retail clients from almost any country, offering access to a wide range of global payment service providers for both ecommerce and POS. This ensures that retailers can efficiently manage payments for online and in-store sales, offering customers a smooth, secure checkout experience across all sales channels. What is Brightpearl? Brightpearl is a robust operations platform designed to help retailers streamline their back-office operations. From inventory management to order fulfilment, accounting, and customer service, Brightpearl provides an all-in-one solution to help brands scale efficiently. By automating critical processes and centralizing operations, Brightpearl enables retailers to focus on growth, while ensuring their back-end systems run smoothly. With Shuttle's payment integration, Brightpearl users can now offer secure, customisable payment solutions directly within the platform. This includes the ability to track payments in real-time, manage different payment profiles for each sales channel, and offer region-specific payment methods to customers around the world. Whether handling online payments or point-of-sale transactions, Shuttle's solution ensures that retailers can provide a streamlined payment experience while minimising fraud risk. > "We're thrilled to partner with Brightpearl to help retailers and wholesalers accept payments," said Nick Dunse, CRO at Shuttle. "By integrating Shuttle, Brightpearl users can provide a smooth and flexible payment experience for their customers, helping them to scale their businesses globally while ensuring every transaction is safe and efficient." Brightpearl is known for its ability to help retailers optimise and automate their operations, from sales to fulfilment. The integration with Shuttle enhances this by enabling users to seamlessly manage payments across different channels. Retailers can now offer a superior customer experience, with quick and secure payment options that are flexible enough to meet the demands of global markets. This partnership between Shuttle and Brightpearl empowers retailers with the tools they need to manage payments at scale, providing a powerful solution for businesses looking to grow and expand their reach. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Shuttle vs Prommt for Platforms and Merchants ### Shuttle vs Checkout.com for Platforms ### Shuttle vs Adyen for Platforms ### Shuttle vs Gr4vy ### Shuttle vs Worldpay for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [ComparisonShuttle vs Gr4vy→](/vs/gr4vy/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-brightpearl-partner-to-enable-invoice-and-pos-payments-for-global-retailers/ --- # Shuttle and Rezkit Partner to Offer Seamless Payment Solutions for Travel and Tourism Businesses | Shuttle > Rezkit partners with Shuttle to give travel and tourism businesses flexible payment processing with multi-gateway support and automated reconciliation. # Shuttle and Rezkit Partner to Offer Seamless Payment Solutions for Travel and Tourism Businesses By Nick Dunse, February 2, 2026 Rezkit partners with Shuttle to give travel and tourism businesses flexible payment processing with multi-gateway support and automated reconciliation. 1 December 2021 Rezkit, a leading travel technology platform, has announced a strategic partnership with Shuttle to provide travel and tourism businesses with seamless and secure payment solutions. This partnership enables Rezkit users to integrate their preferred payment providers, build custom payment workflows, and access advanced fraud prevention tools, all while offering a variety of convenient payment methods to their customers, no matter where they are in the world. With Shuttle, Rezkit clients can onboard travelers and businesses from nearly any country, as Shuttle offers connections to leading global payment service providers. This ensures travel companies using Rezkit can manage bookings, reservations, and other payments with ease and confidence, streamlining operations and enhancing customer satisfaction. ## What is Rezkit? Rezkit is an all-in-one travel technology platform that helps tour operators, travel agencies, and other businesses in the travel industry manage their operations more efficiently. From booking engines to customer management and inventory control, Rezkit offers a full suite of tools to power the travel and tourism sector. With its flexible, customizable platform, Rezkit enables businesses to offer personalized travel experiences while maintaining full control over their operations. Through its partnership with Shuttle, Rezkit now provides its users with the ability to manage payments directly within the platform. Travel businesses can process payments for bookings, cancellations, and refunds using Shuttle's advanced payment infrastructure, which includes fraud prevention, customizable payment profiles, and real-time transaction tracking. This integration simplifies the payment process for travel companies, making it easier to offer a secure, global payment experience to customers booking vacations, tours, or other travel services. "We're excited to partner with Rezkit and bring secure, streamlined payment capabilities to the travel and tourism industry," said Nick Dunse, CRO at Shuttle. "Our collaboration will help travel companies provide a better experience for their customers by offering reliable and flexible payment solutions that are tailored to the unique needs of the industry." Rezkit distinguishes itself from other travel platforms by offering a comprehensive solution that allows businesses to manage all aspects of travel services in one place. Now, with Shuttle's integrated payment capabilities, travel companies using Rezkit can ensure that payments for bookings, reservations, and additional services are processed quickly and securely, helping to create a seamless experience for travelers around the globe. The partnership between Shuttle and Rezkit is set to transform the way travel companies manage payments, enabling them to scale their operations and enhance customer satisfaction with a robust, global payment infrastructure. ## Related Reading Explore More ### How to Connect Global Payments to Twilio for Voice & IVR Payments ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### Payments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ### Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree ### Single Global PSP vs Multiple Local Acquirers: How to Decide ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Connect Global Payments to Twilio for Voice & IVR Payments→](/guides/global-payments-twilio-integration/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuidePayments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments→](/guides/payments-for-ccaas-implementation-partners/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [GuideBraintree + QuickBooks Integration: Accept Invoice Payments via Braintree→](/guides/quickbooks-braintree-payments/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-classter/ --- # Shuttle and Classter Partner to Offer Seamless Payment Solutions for Educational Institutions | Shuttle > Classter partners with Shuttle to bring secure, flexible payment processing to educational institutions with multi-gateway support and automated billing. # Shuttle and Classter Partner to Offer Seamless Payment Solutions for Educational Institutions By Nick Dunse, January 31, 2026 Classter partners with Shuttle to bring secure, flexible payment processing to educational institutions with multi-gateway support and automated billing. Classter, an all-in-one school management system, is now working with Shuttle, to bring secure, flexible payment capabilities to educational institutions. With this collaboration, Classter users can now integrate their preferred payment providers, set up custom payment workflows, and benefit from enhanced fraud prevention and multiple payment methods. From tuition fees to extracurricular activities, schools can now offer a more streamlined and convenient payment experience for students and parents alike. With Shuttle, Classter can onboard institutions from nearly any country, giving them access to leading global payment service providers. This integration simplifies the complex financial processes educational institutions face, enabling them to efficiently manage payments for registrations, tuition, course content and materials or services within the same platform. One off or recurring payments are possible when need too. ## What is Classter? Classter is a powerful, cloud-based school management solution designed to meet the needs of K-12 schools, universities, and educational institutions worldwide. By offering a comprehensive suite of tools for student management, admissions, grading, and more, Classter helps institutions streamline their operations and enhance the overall learning experience. The platform's flexibility allows schools to customize workflows according to their unique needs, making it easy to manage academic, administrative, and financial processes in one place. Through Shuttle's integration, Classter users can now offer secure and convenient payment options to students, parents, and institutions. Whether processing tuition payments, managing registration fees, or handling payments for extracurricular activities, Shuttle provides advanced fraud protection and real-time tracking. The integration enables educational institutions to manage multiple payment profiles, accept payments in various currencies, and ensure a smooth payment experience across all services. "We're excited to partner with Classter to bring efficient, secure payment solutions to the education sector," said Nick Dunse, CRO at Shuttle. "By integrating our technology with Classter, educational institutions can streamline their payment processes, making it easier for students and parents to complete transactions quickly and securely." Classter distinguishes itself as a comprehensive, all-in-one platform for educational institutions, helping schools and universities optimise administrative tasks and improve student outcomes. Now, with the addition of Shuttle's payment capabilities, Classter users can simplify payment workflows, ensuring that all financial transactions are handled securely and efficiently, with real-time tracking and fraud prevention. The partnership between Shuttle and Classter provides educational institutions with the tools they need to enhance operational efficiency while offering a superior payment experience for students, parents, and administrators. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Shuttle vs Prommt for Platforms and Merchants ### Shuttle vs Checkout.com for Platforms ### Shuttle vs Adyen for Platforms ### Shuttle vs Gr4vy ### Shuttle vs Worldpay for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [ComparisonShuttle vs Gr4vy→](/vs/gr4vy/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/ --- # Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers | Shuttle > Eventsforce partners with Shuttle to offer event organisers flexible payment processing with multi-currency support, fraud protection, and gateway choice. # Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers By Nick Dunse, February 1, 2026 Eventsforce partners with Shuttle to offer event organisers flexible payment processing with multi-currency support, fraud protection, and gateway choice. 1 September 2021 Eventsforce, a leading event management platform, has announced an exciting new partnership with Shuttle, empowering its users with secure, flexible payment workflows. This collaboration enables event organizers to integrate their preferred payment providers and configure payment solutions that include fraud prevention and a variety of convenient payment options. From global conferences to local gatherings, event organizers can now offer a seamless payment experience to their attendees, no matter where they are located. With Shuttle, Eventsforce can onboard clients from nearly any country, as Shuttle connects them to leading payment service providers worldwide. This ensures that Eventsforce customers can manage ticket sales, registrations, and other event-related payments in the most efficient and secure manner. ## What is Eventsforce? Eventsforce is a comprehensive event management platform that provides tools for planning, promoting, and executing events both online and in person. The platform allows organizers to manage everything from registration and ticketing to attendee engagement and post-event analytics. Eventsforce's intuitive interface and customizable features make it easy for users to tailor events to their specific needs, whether they are organizing a small meeting or a large-scale conference. Through Shuttle's integration, Eventsforce clients can now manage event payments directly within the platform. Whether handling ticket purchases, registration fees, or on-site payments, Shuttle's solutions offer fraud prevention, real-time tracking, and customizable payment profiles for each event. This makes it easier for event organizers to offer a localized payment experience for attendees from different regions, ensuring smooth transactions no matter the size or scale of the event. "We're excited to partner with Eventsforce to offer their users seamless payment experiences," said Nick Dunse, CRO at Shuttle. "By integrating Shuttle, Eventsforce clients can simplify payment processes, reduce fraud risk, and provide a more efficient experience for event attendees." Eventsforce has built a reputation for helping event organizers run successful, well-executed events through its user-friendly, scalable platform. The integration with Shuttle enhances this by allowing organizers to offer secure and reliable payment options that can be easily configured for any event. Whether accepting payments for virtual events or managing registrations for large, in-person conferences, Eventsforce users can now streamline their payment processes while ensuring security and convenience for attendees. The partnership between Shuttle and Eventsforce marks a significant step forward for event organizers looking to offer a superior attendee experience while managing secure, global payments with ease. ## Related Reading Explore More ### Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale ### Payment Solutions for Car Dealerships & Auto Finance Platforms ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ### Build vs Buy Payment Infrastructure: A Decision Framework for Platforms ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideMarketplace Payment Solutions: How to Handle Multi-Party Payments at Scale→](/guides/marketplace-payment-solutions/) - [GuidePayment Solutions for Car Dealerships & Auto Finance Platforms→](/guides/car-dealership-payment-solutions/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [GuideBuild vs Buy Payment Infrastructure: A Decision Framework for Platforms→](/guides/build-vs-buy-payment-infrastructure/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-hqrental/ --- # Shuttle Enables HQ Rental Software with Key Payments Connectivity and Features | Shuttle > HQ Rental Software partners with Shuttle to offer fleet rental businesses seamless payment processing with multi-gateway connectivity and automated... # Shuttle Enables HQ Rental Software with Key Payments Connectivity and Features By Nick Dunse, February 3, 2026 HQ Rental Software partners with Shuttle to offer fleet rental businesses seamless payment processing with multi-gateway connectivity and automated... 1 July 2023 Shuttle has announced an exciting partnership with HQ Rental Software, a leading provider of fleet rental management solutions. The collaboration enables HQ Rental Software users to integrate their preferred payment providers, offering secure and flexible payment options while streamlining rental operations. With Shuttle's platform, HQ Rental Software customers can access global payment service providers and automate payment workflows, ensuring secure and efficient transactions across various rental services. ## What is HQ Rental Software? HQ Rental Software is a comprehensive cloud-based solution that helps rental companies manage bookings, fleet availability, agreements, and payments. Designed for businesses of all sizes, it supports car, van, motorbike, and equipment rentals, offering essential features like online reservations, telematics integration, fleet management, and mobile access. The platform is trusted by companies in over 80 countries for its user-friendly interface and robust functionality. By integrating with Shuttle, HQ Rental Software enhances its payment capabilities, allowing businesses to offer flexible payment methods while maintaining control over fraud prevention and transaction tracking. Rental companies can now manage payments seamlessly, whether for deposits, reservations, or long-term rentals, all from within the HQ Rental platform. "We're thrilled to partner with HQ Rental Software to bring enhanced payment options to the rental industry," said Nick Dunse, CRO at Shuttle. "This collaboration empowers rental businesses to simplify their payment processes while delivering a secure, efficient experience for customers, no matter where they're located." Shuttle's advanced payment integration helps HQ Rental Software clients offer localized and global payment options, ensuring businesses can meet the needs of their diverse customer base. Whether renting cars, equipment, or motorbikes, rental businesses can now focus on delivering excellent service while Shuttle ensures payments are handled efficiently and securely. This partnership combines Shuttle's leading payment infrastructure with HQ Rental Software's robust rental management tools, empowering businesses to simplify operations and improve customer satisfaction. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Shuttle vs Prommt for Platforms and Merchants ### Shuttle vs Checkout.com for Platforms ### Shuttle vs Adyen for Platforms ### Shuttle vs Gr4vy ### Shuttle vs Worldpay for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [ComparisonShuttle vs Gr4vy→](/vs/gr4vy/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-instanda/ --- # Shuttle Partners with INSTANDA to Streamline Payments for the Insurance Industry | Shuttle > INSTANDA partners with Shuttle to offer insurance platforms seamless payment processing with multi-gateway support, PCI compliance, and automated billing. # Shuttle Partners with INSTANDA to Streamline Payments for the Insurance Industry By Nick Dunse, February 4, 2026 INSTANDA partners with Shuttle to offer insurance platforms seamless payment processing with multi-gateway support, PCI compliance, and automated billing. 2 January 2020 INSTANDA, the leading no-code insurance platform, now empowers its users with seamless payment options through its partnership with Shuttle. INSTANDA clients can configure custom payment workflows that include advanced fraud prevention and flexible payment methods, making policy purchases, renewals, and claims processing more efficient and secure. With Shuttle, INSTANDA can onboard clients from nearly any country, as Shuttle provides access to leading payment service providers globally. This partnership simplifies the insurance experience for customers and insurers alike by enabling secure, fast, and localized payment solutions. ## What is INSTANDA? INSTANDA is an innovative digital platform that transforms the insurance landscape, allowing insurers to create, manage, and distribute products without the need for complex coding. By enabling insurers to launch tailored insurance products quickly and efficiently, INSTANDA helps companies adapt to the evolving needs of customers and regulations. Whether it's health, life, property, or casualty insurance, INSTANDA's platform supports a wide range of product offerings with the flexibility and speed the insurance market demands. Thanks to its integration with Shuttle, INSTANDA clients can now offer customers secure, region-specific payment options as part of their insurance journey. Whether processing payments for premiums, claims, or policy renewals, insurers can leverage Shuttle's fraud prevention tools and a variety of payment methods to deliver a superior experience. The platform allows companies to track payments in real-time and manage different payment configurations across their product portfolio, all from within INSTANDA's user-friendly interface. "We're excited to partner with INSTANDA to bring best-in-class payment solutions to the insurance industry," said Nick Dunse, CRO at Shuttle. "Our collaboration helps streamline payment processing for insurers, ensuring they can offer a seamless and secure experience to their customers." INSTANDA distinguishes itself from other insurance platforms by providing insurers with a no-code, fully customisable platform that allows for rapid product creation and updates. The ability to integrate with leading payment solutions through Shuttle further enhances this value proposition, enabling insurers to meet customer expectations in a secure, efficient, and localized manner. This partnership between Shuttle and INSTANDA empowers the insurance industry with the tools needed to thrive in a rapidly changing digital landscape, providing insurers with the payment infrastructure to grow and scale globally. ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Shuttle vs Prommt for Platforms and Merchants ### Shuttle vs Checkout.com for Platforms ### Shuttle vs Adyen for Platforms ### Shuttle vs Gr4vy ### Shuttle vs Worldpay for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [ComparisonShuttle vs Gr4vy→](/vs/gr4vy/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-kount-work-together-to-provide-fraud-prevention-at-scale/ --- # Shuttle and Kount work together to provide fraud prevention at scale | Shuttle > 10 February 2023 Merchants can now use Kount fraud and chargeback prevention via their software vendor thanks to Shuttle. # Shuttle and Kount work together to provide fraud prevention at scale By Nick Dunse, February 10, 2023 10 February 2023 Merchants can now use Kount fraud and chargeback prevention via their software vendor thanks to Shuttle. 10 February 2023 Merchants can now use Kount fraud and chargeback prevention via their software vendor thanks to Shuttle. Kount is now available to merchants using any of Shuttle's software vendors, including: QuickBooks Online, MethodCRM, Instanda etc. The partnership has enabled Kount's services in over 30 software vendors, where 6 million merchants could potentially get the benefit from Kount's leading fraud prevention toolkit. A merchant can simply enable Kount for any of their payment processing workflows, for any payment method and for any payment gateway that their using. "Kount is a game changer for protecting merchants from increasing fraud and chargeback risks and we're glad to make it so widely available" said Nick Dunse, CRO at Shuttle. Shuttle has software vendors and merchants in industries where fraud and chargebacks are an increasing problem, ticketing, hospitality and retail have been plagued by the increasing amount of genuine fraud and 'friendly fraud' taking place. The special thing about Shuttle is that once a service like Kount is integrated, it is immediately available to all the connected software vendors and their merchants, there are no limitations from the payment gateway or software UX, merchants can simply access the toolset and configure it per payment method. Which leaves them protected going forward. Vendors can even resell Kount via Shuttle if they want to provide a less tailored setup to their merchants. Kount uses years of data on fraudster behaviour including up to date signals from across it's network to prevent a fraudulent transaction from taking place. Kount offers a comprehensive suite of tools designed to combat fraud and reduce chargebacks effectively. By leveraging advanced machine learning algorithms and extensive data analytics, Kount provides merchants with real-time insights into transaction risk levels. This enables businesses to make informed decisions about which transactions to approve or decline, ultimately minimising the potential for fraudulent activity. "We've already seen merchants in the aftermarket auto parts industry successfully stop fraudulent transactions, to know that a user can simply click a few buttons and be protected is a good feeling" continued Nick Dunse. Merchants who choose to integrate Kount into their payment processing systems will benefit from enhanced security measures that include automated decision-making processes, comprehensive reporting features, and ongoing support from both Shuttle and Kount teams. This partnership not only aims to reduce financial losses associated with fraud but also enhances overall customer experience by ensuring legitimate transactions are processed swiftly and securely. It's another integration and toolset that software vendors don't have to build themselves if they use Shuttle to deliver leading payment and finance services to their merchants. ## Related Reading Explore More ### Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### What Is Twilio Pay? How It Works, Pricing, and Connectors (2026) ### Twilio Pay Connectors: How to Connect Any Payment Provider to Twilio ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ### PCI Compliance Service Provider: How to Choose One in 2026 ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePayment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions→](/guides/payment-operations-at-scale/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideWhat Is Twilio Pay? How It Works, Pricing, and Connectors (2026)→](/guides/what-is-twilio-pay/) - [GuideTwilio Pay Connectors: How to Connect Any Payment Provider to Twilio→](/guides/twilio-pay-connectors/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [GuidePCI Compliance Service Provider: How to Choose One in 2026→](/guides/pci-compliance-service-provider/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-kount-work-together-to-provide-fraud-prevention-at-scale-2/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-ordorite-enable-new-payments-opportunities-for-furniture-retailers/ --- # Shuttle and Ordorite Enable New Payments Opportunities for Furniture Retailers | Shuttle > Ordorite partners with Shuttle to bring flexible payment processing to furniture and bedding retailers with multi-gateway support and seamless... # Shuttle and Ordorite Enable New Payments Opportunities for Furniture Retailers By Nick Dunse, February 1, 2026 Ordorite partners with Shuttle to bring flexible payment processing to furniture and bedding retailers with multi-gateway support and seamless... 1 February 2021 Ordorite, a leading software solution for furniture and bedding retailers, has joined forces with Shuttle to offer seamless payment integration. Through this partnership, Ordorite customers can now access secure payment workflows with advanced fraud prevention and a variety of localized payment methods, providing a smoother experience for both retailers and their customers. With Shuttle, Ordorite is able to onboard clients from nearly any country, leveraging Shuttle's network of leading payment service providers worldwide. This integration allows furniture retailers to manage payments and financial processes with ease, enhancing both the online and in-store experience for their customers. ## What is Ordorite? Ordorite is a comprehensive retail management software designed specifically for the furniture and bedding industry. It offers end-to-end solutions for inventory management, order processing, and customer engagement. By streamlining operations from the warehouse to the sales floor, Ordorite enables retailers to optimize every aspect of their business. The platform provides key features such as real-time inventory tracking, sales analytics, and customer relationship management, ensuring retailers have all the tools they need to thrive in a competitive market. With the integration of Shuttle's payment capabilities, Ordorite clients can offer a variety of payment options directly within their management system. From deposits to final payments, Shuttle provides the security and flexibility needed to manage transactions efficiently, whether they are made online or in-store. Retailers can set up different payment profiles for various stores or locations, and track payment statuses in real time, all through Ordorite's interface. "We're thrilled to partner with Ordorite and bring robust payment solutions to furniture retailers worldwide," said Nick Dunse, CRO at Shuttle. "This partnership allows retailers to offer a smoother customer experience by simplifying payments, reducing fraud risk, and making transactions faster and more reliable." Ordorite's platform stands out in the retail industry for its ability to centralize and automate the many moving parts of furniture retail, from sales orders to delivery logistics. Now, with Shuttle's integrated payment capabilities, furniture retailers using Ordorite can ensure that the entire purchasing process is as seamless as possible, from selection to payment. This partnership between Shuttle and Ordorite marks a significant step forward in the furniture retail industry, enabling businesses to scale more efficiently and deliver a superior shopping experience both online and in-store. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-polyai/ --- # Shuttle and PolyAI - conversational payments | Shuttle > Shuttle and PolyAI partner to bring PCI-compliant voice payments to AI-powered phone agents. # Shuttle and PolyAI - conversational payments By Nick Dunse, October 1, 2024 Shuttle and PolyAI partner to bring PCI-compliant voice payments to AI-powered phone agents. 1 October 2024 Shuttle and PolyAI work together to Enable Seamless Payments and Enhanced Customer Experience Across Industries Users of PolyAI, a leading provider of conversational AI solutions, can now integrate their preferred payment partners, enabling smooth payment workflows. Industries that rely on automated customer service and need secure, streamlined payment options demand both convenient payments and top-tier customer engagement. With Shuttle, PolyAI is now able to onboard businesses from nearly any country, as Shuttle provides access to top payment service providers around the world. This expansion gives PolyAI clients the ability to integrate payments directly into their AI-powered customer service workflows. What is PolyAI? PolyAI delivers cutting-edge conversational AI technology, helping businesses automate and scale customer service with natural, human-like dialogues. Industries from retail to banking and healthcare trust PolyAI to manage complex customer interactions at scale, all while maintaining high levels of satisfaction. The platform supports multiple languages and offers conversational experiences that allow customers to resolve issues, schedule services, or make inquiries without human intervention. By combining AI technology with intuitive conversation design, PolyAI ensures businesses can offer a personalized customer service experience, anytime and anywhere. Now, with Shuttle's integration, PolyAI clients can manage payments within the same conversational experience. This allows for a seamless flow, from customer inquiry to payment processing, with the added benefits of fraud prevention and customizable payment workflows. Clients can configure different payment setups based on geography or service offering, all without the need for complex coding. Payment statuses can be tracked in real-time through the PolyAI platform, giving businesses full visibility over transactions. "We're thrilled to enable PolyAI with powerful payment solutions, creating a seamless blend of advanced conversational AI and secure payment capabilities," said Nick Dunse, CRO at Shuttle. "With this partnership, PolyAI can further simplify customer interactions, ensuring payments are as easy as the conversations themselves." PolyAI sets itself apart with its focus on creating lifelike conversational experiences, transforming how businesses engage with their customers. While many AI platforms offer standard solutions, PolyAI excels in making customer service interactions as natural and efficient as possible. With the addition of Shuttle's payment integration, businesses can now manage both service inquiries and payments in one unified workflow, providing a more streamlined customer experience. Shuttle and PolyAI's partnership represents a new era in automated customer service, allowing businesses to interact with customers on a global scale while managing secure payments in real-time. ## Related Reading Explore More ### How PolyAI Voice Agents Take Payments: PCI-Compliant AI Voice Payments ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation ### Shuttle vs Prommt for Platforms and Merchants ### Shuttle vs Checkout.com for Platforms ### Shuttle vs Adyen for Platforms ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow PolyAI Voice Agents Take Payments: PCI-Compliant AI Voice Payments→](/guides/polyai-payments/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideAI Voice Agents and Payments: How PolyAI Captures Payments in Conversation→](/guides/ai-voice-agents-payments/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/shuttle-and-vfairs-work-together-to-revolutionise-global-event-management/ --- # Shuttle and vFairs work together to revolutionise global event management | Shuttle > vFairs partners with Shuttle to let event organisers accept payments through their preferred gateway with built-in fraud protection. # Shuttle and vFairs work together to revolutionise global event management By Nick Dunse, February 3, 2026 vFairs partners with Shuttle to let event organisers accept payments through their preferred gateway with built-in fraud protection. 1 September 2024 Users of vFairs are now able to use their preferred payments partner, with the ability to create payment workflows that includes fraud prevention and convenient payment methods. Events and ticketing can be a very localised and challenging operation, whilst online events also need the ability to engage a global audience, that might need to pay for a ticket. With Shuttle vFairs is able to onboard customers from almost any country as Shuttle provides access to leading payment service providers around the globe. ## What is vFairs? vFairs is an advanced virtual event platform that enables organisations to host immersive online experiences. With a focus on user engagement and interactivity, vFairs provides tools for hosting webinars, trade shows, and conferences in a fully virtual environment. The platform offers features such as customisable virtual booths, live chat options, and analytics tools that allow event organisers to track attendee engagement in real-time. By facilitating seamless interactions between exhibitors and attendees, vFairs has established itself as a leader in the realm of virtual events. With zero coding a vFairs customer can enable any of the payment services for their events, setting up different payment profiles per event if required. Users can also see the status of a payment from within the vFairs platform. "Shuttle is very happy to support one of the new leading event platforms with seamless payment capabilities" said Nick Dunse, CRO at Shuttle. vFairs distinguishes itself from other event solutions through its commitment to creating highly interactive and visually appealing virtual environments. While many platforms offer basic functionalities for hosting online events, vFairs goes above and beyond by providing a fully customisable experience that reflects the unique branding and objectives of each organisation. The platform's user-friendly interface ensures that both organisers and attendees can navigate events with ease, while its robust analytics tools empower organisers to measure engagement and success effectively. Event management can now be local and global, physical and digital thanks to a winning formula from Shuttle and vFairs combined. ## Related Reading Explore More ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### How to Connect Global Payments to Twilio for Voice & IVR Payments ### Payment Links for Property Management & Lettings Agencies ### What Is Twilio Pay? How It Works, Pricing, and Connectors (2026) ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuideHow to Connect Global Payments to Twilio for Voice & IVR Payments→](/guides/global-payments-twilio-integration/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [GuideWhat Is Twilio Pay? How It Works, Pricing, and Connectors (2026)→](/guides/what-is-twilio-pay/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/simplify-your-sales-cycle-the-benefits-of-using-payment-links-in-quote-to-cash/ --- # Simplify Your Sales Cycle: The Benefits of Using Payment Links in Quote to Cash | Shuttle > Streamline your quote-to-cash process with payment links. Close deals faster by embedding secure payment collection directly into sales workflows. # Simplify Your Sales Cycle: The Benefits of Using Payment Links in Quote to Cash By Nick Dunse, February 7, 2026 Streamline your quote-to-cash process with payment links. Close deals faster by embedding secure payment collection directly into sales workflows. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. In today's fast-paced business landscape, optimizing sales processes is essential for companies to remain competitive. One effective strategy to achieve this is by integrating payment links into the quote-to-cash cycle. This innovative approach enables sales teams to efficiently and securely collect payments from customers, thereby eliminating the need for manual invoicing and payment processing. This streamlined process not only conserves time and resources but also enhances the overall customer experience by providing a seamless and convenient payment method. By incorporating payment links into the sales process, companies can significantly accelerate deal closures. Rather than waiting for customers to manually process payments, sales teams can simply send a payment link alongside the quote, allowing customers to make instant payments. This not only expedites the sales cycle but also mitigates the risk of deals falling through due to payment processing delays. Overall, payment links play a crucial role in streamlining the sales process, rendering it more efficient and effective. Key Takeaways - Payment links simplify the sales cycle by allowing for seamless and efficient payment collection. - Streamlining the sales process with payment links enhances efficiency and improves the customer experience. - Payment links reduce friction and delays in closing deals, leading to improved cash flow and revenue collection. - By minimizing errors and manual work in the quote to cash process, payment links can increase sales conversion rates. - Leveraging technology for a smoother sales cycle can lead to a more streamlined and successful business operation. ## Enhancing Efficiency and Customer Experience Convenience and Security With payment links, customers can easily make payments online, eliminating the need for manual checks or wire transfers. This not only saves time for both the customer and the sales team, but also provides a more convenient and secure payment method. ## Customization and Transparency Payment links can be customized to include important details such as invoice numbers, due dates, and payment amounts, providing customers with all the information they need to make a payment. This level of transparency and convenience not only enhances the customer experience, but also reduces the likelihood of errors or disputes related to payments. ## Enhanced Efficiency and Customer Experience Overall, by incorporating payment links into the quote to cash cycle, companies can enhance efficiency and provide a more seamless and convenient experience for their customers. ## Reducing Friction and Delays in Closing Deals One of the biggest challenges in the sales process is dealing with friction and delays in closing deals. This can be caused by a variety of factors, including manual invoicing and payment processing, as well as delays in receiving payments from customers. However, by using payment links in the quote to cash cycle, companies can significantly reduce friction and delays in closing deals. Payment links allow sales teams to collect payments instantly, eliminating the need for manual invoicing and payment processing. This not only saves time and resources, but also reduces the risk of delays in receiving payments from customers. By providing customers with a convenient and secure way to make payments, companies can minimize friction in the sales process and ensure that deals are closed in a timely manner. ## Improving Cash Flow and Revenue Collection ## Benefits of Using Payment Links in Quote to Cash ### 1. Faster payment processing ### 2. Improved cash flow ### 3. Reduced manual errors ### 4. Enhanced customer experience ### 5. Increased sales conversion Another key benefit of using payment links in the quote to cash cycle is the improvement of cash flow and revenue collection. By allowing customers to make instant payments online, companies can accelerate their cash flow and improve their revenue collection process. This not only provides companies with a steady stream of income, but also reduces the risk of late or missed payments. Furthermore, by streamlining the payment process, companies can also reduce the risk of errors or disputes related to payments. This not only saves time and resources, but also ensures that companies are able to collect payments in a timely and efficient manner. Overall, by incorporating payment links into the quote to cash cycle, companies can improve their cash flow and revenue collection process. Minimizing Errors and Manual Work in Quote to Cash Manual invoicing and payment processing can be time-consuming and error-prone, leading to delays and inefficiencies in the quote to cash cycle. However, by using payment links, companies can minimize errors and reduce the need for manual work in the sales process. Payment links allow sales teams to easily collect payments from customers, eliminating the need for manual invoicing and payment processing. This not only saves time and resources, but also reduces the risk of errors related to payments. By providing customers with a secure and convenient way to make payments online, companies can minimize the risk of errors or disputes related to payments. Overall, by incorporating payment links into the quote to cash cycle, companies can minimize errors and reduce the need for manual work in the sales process. Increasing Sales Conversion Rates with Seamless Payments ## Boosting Sales Conversion Rates One of the key benefits of using payment links in the quote to cash cycle is the ability to increase sales conversion rates. By providing customers with a seamless and convenient way to make payments online, companies can reduce friction in the sales process and improve their chances of closing deals. This not only accelerates the sales cycle, but also increases the likelihood of converting leads into paying customers. ## Enhancing the Customer Experience Furthermore, by streamlining the payment process, companies can also provide a more seamless and convenient experience for their customers. This not only enhances the overall customer experience, but also increases customer satisfaction and loyalty. ## Improving the Bottom Line Overall, by incorporating payment links into the quote to cash cycle, companies can increase their sales conversion rates and improve their bottom line. ## Leveraging Technology for a Smoother Sales Cycle In today's digital age, it's crucial for companies to leverage technology in order to stay competitive. By using payment links in the quote to cash cycle, companies can leverage technology to streamline their sales processes and improve their overall efficiency. Payment links allow sales teams to easily collect payments from customers, eliminating the need for manual invoicing and payment processing. This not only saves time and resources, but also provides a more seamless and convenient experience for both the sales team and their customers. By leveraging technology to streamline the sales process, companies can improve their efficiency and provide a more convenient experience for their customers. Overall, by incorporating payment links into the quote to cash cycle, companies can leverage technology to achieve a smoother sales cycle and stay ahead of the competition. In conclusion, using payment links in the quote to cash cycle offers a wide range of benefits for companies looking to streamline their sales processes. From enhancing efficiency and customer experience to reducing friction and delays in closing deals, payment links provide a convenient and secure way for sales teams to collect payments from customers. By leveraging technology to minimize errors and manual work in the sales process, companies can increase their sales conversion rates and improve their cash flow and revenue collection process. Overall, by incorporating payment links into the quote to cash cycle, companies can achieve a smoother sales cycle and stay competitive in today's fast-paced business environment. ## What are payment links in Quote to Cash? Payment links in Quote to Cash are secure and convenient ways to collect payments from customers. They are URLs that can be sent to customers, allowing them to make payments online using various payment methods such as credit cards, debit cards, and digital wallets. ## How do payment links simplify the sales cycle? Payment links simplify the sales cycle by streamlining the payment process. Instead of waiting for checks or manual bank transfers, customers can simply click on the payment link and complete the transaction online. This reduces the time and effort required to collect payments, leading to faster revenue recognition and improved cash flow. What are the benefits of using payment links in Quote to Cash? Using payment links in Quote to Cash offers several benefits, including: - Faster payment collection - Improved cash flow - Reduced administrative burden - Enhanced customer experience - Increased security and fraud protection How can businesses integrate payment links into their Quote to Cash process? Businesses can integrate payment links into their Quote to Cash process by using a payment gateway or a payment processing platform that offers this feature. They can generate payment links directly from their invoicing or quoting system and include them in their communications with customers. Additionally, businesses can customize payment links to include specific invoice details and branding elements. ## Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/smart-rules/ --- # Introducing Smart Rules: Streamlined Checkouts and Smarter Fraud Prevention | Shuttle > Shuttle Smart Rules let merchants customise checkout flows and automate fraud prevention. # Introducing Smart Rules: Streamlined Checkouts and Smarter Fraud Prevention By Nick Dunse, January 4, 2026 Shuttle Smart Rules let merchants customise checkout flows and automate fraud prevention. At Shuttle, we're on a mission to help merchants optimise payments -- not just for security, but for cost and conversion. That's why we're continuing to expand our Smart Rules feature set: tools that give sellers more control, more flexibility, and more value from their checkout process. We launched our first Smart Rule in partnership with Kount, bringing fraud prevention at scale to our merchants. And now we're launching the second Smart Rule in the series: Amount-Based Rules, a simple but powerful feature that allows merchants to hide specific payment methods based on the total amount of a transaction. ## What Are Smart Rules? Smart Rules are dynamic settings that merchants can use to customise the checkout experience based on predefined conditions -- no coding required. They're embedded into Shuttle's Merchant Setup and Checkout components, allowing merchants to experiment with their payment flow without relying on developers or technical integrations. These features are available to any merchant using more than one payment method, and they're exclusive to Shuttle. ## Smart Rule #1: Fraud Rules (Powered by Kount) The first Smart Rule we released integrated directly with Kount, the industry leader in fraud prevention. It allows merchants to create fraud rules within their payment workflow -- flagging, rejecting, or escalating suspicious activity before a transaction is completed. From blocking high-risk geographies to setting thresholds for velocity or transaction frequency, these no-code fraud controls empower merchants to protect themselves without compromising on user experience. 📖 Learn more about our fraud toolset with Kount:Shuttle and Kount Work Together to Provide Fraud Prevention at Scale ## Smart Rule #2: Amount-Based Rules Now, we're adding another powerful lever: Amount Filters. With this Smart Rule, merchants can hide certain payment methods based on the value of a transaction. For example, you can automatically hide the option to pay by card for any order over $10,000 -- helping you avoid expensive card processing fees on large transactions. ## Why This Matters Merchants operating across a range of price points -- from low-ticket to high-ticket sales -- often want to encourage cost-effective payment methods without creating friction for customers. This feature makes that easy. Common Use Cases: Hide cards for high-value B2B transactions and promote bank transfers or open banking ## Streamline checkout for specific customer segments based on value thresholds Encourage cheaper payment rails where possible to improve margin and cash flow ## What Problems Does It Solve? ✅ Avoid High Payment Processing Fees✅ Create a Simpler, More Tailored Checkout Experience✅ Drive Higher Conversions by Matching Checkout to Customer Expectations Some merchants are happy to show all payment methods at all times -- but many want to test new ways of reducing cost and improving conversion. Smart Rules provide the flexibility to do just that. And the best part? No other payment provider offers this level of control today. For Our Platform Partners If you've integrated Shuttle's Merchant Setup or Checkout components, you'll see some updates as we roll this out. Here's what you need to know: No code changes are required. These rules are managed entirely within the Merchant Setup interface. Smart Rules only apply to checkouts initiated via the front-end user interface -- not one-off or recurring API payments. Merchants will need to have at least two payment methods enabled to use these rules. We've also created a demonstration video showing how the Amount Rule works in practice. ## A Unique Advantage for Your Platform As a platform partner, offering Smart Rules through Shuttle gives your merchants a competitive edge they can't get elsewhere. Whether it's cutting costs, reducing fraud, or improving the buyer journey, Smart Rules are designed to deliver tangible benefits -- without adding complexity. These tools help make every payment smarter, safer, and more profitable. Want to see what it looks like inside the Merchant Setup UI?👇 Here's a preview of what merchants will see when they configure Smart Rules: Smart Rules are just the beginning of a new wave of intelligent checkout features we're building at Shuttle. With more options for optimisation, experimentation, and automation, merchants can take control of their payments in ways that were previously only possible through custom development. Ready to reduce fees, stop fraud, and convert more sales?Smart Rules are live now. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Shuttle and Kount Work Together to Provide Fraud Prevention at Scale](/blog/shuttle-and-kount-work-together-to-provide-fraud-prevention-at-scale/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/ --- # Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared | Shuttle > Which payment providers offer the fastest settlement? Compare settlement speeds for Stripe (T+2), Adyen (T+1), Square (next day), Worldpay, Checkout.com,... # Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared By Nick Dunse, June 11, 2024 Which payment providers offer the fastest settlement? Compare settlement speeds for Stripe (T+2), Adyen (T+1), Square (next day), Worldpay, Checkout.com,... Talk to us Make enabling payments for your platform and merchant users easy. Settlement speed -- how quickly funds from card transactions reach your bank account -- directly affects cash flow. For businesses operating on thin margins, the difference between same-day settlement and a 7-day hold can determine whether you can pay suppliers, cover payroll, or take on new orders. This guide compares settlement times across the major payment providers in 2026, explains what affects settlement speed, and covers how to get faster payouts. ## What Is Settlement in Payment Processing? Settlement is the process of transferring funds from a completed card transaction to the merchant's bank account. It involves several steps: - Authorisation -- the customer's card is checked for available funds and the transaction is approved - Capture -- the merchant confirms the transaction (this can happen immediately or later, e.g., when goods are shipped) - Clearing -- the card network (Visa, Mastercard) processes the transaction between the issuing and acquiring banks - Settlement -- funds are deposited into the merchant's bank account, minus processing fees The time from capture to settlement is what most businesses care about. It can range from same-day to 7+ business days depending on the provider, the merchant's risk profile, and the payment method used. ## Settlement Speed Comparison: Major Providers Here is how the leading payment providers compare on standard and fast settlement options in 2026: Standard Settlement Fast Payout Option Fast Payout Fee T+2 (UK/EU), T+2 (US) Instant Payouts 1% (min 50p/50¢) UK, US, EU, AU, CA, SG T+1 to T+3 (configurable) Same-day (for qualifying volumes) Global (30+ direct) T+2 to T+3 Next-day available Global (146 countries) T+1 to T+2 Instant Transfer US, UK, CA, AU, JP, FR, IE, ES Checkout.com Same-day for enterprise Instant (to PayPal balance) Instant to bank 1% (max £10) GoCardless T+3 to T+5 (Direct Debit) Not available UK, EU, US, AU, NZ Key: T+1 = next business day after capture. T+2 = two business days. "Instant" = within minutes but at a fee. ## What Affects Settlement Speed? Settlement speed is not purely a provider choice. Several factors determine how quickly you receive funds: ### 1. Provider and Plan Tier Enterprise merchants with higher volumes typically negotiate faster settlement terms. Providers like Adyen and Checkout.com offer T+1 or same-day settlement for qualifying accounts. Small businesses on standard plans usually receive T+2 or T+3. ### 2. Payment Method Different payment methods have different settlement characteristics: - Card payments -- typically T+1 to T+3, depending on the provider and card network - Direct Debit -- slower (T+3 to T+5) because of the multi-day clearing process and chargeback window - Open Banking / Pay by Bank -- potentially same-day since funds move bank-to-bank - Digital wallets (Apple Pay, Google Pay) -- same settlement speed as the underlying card - Buy Now, Pay Later -- varies by provider. Some fund merchants at T+1, others after the customer's first instalment ### 3. Merchant Risk Profile New merchants, businesses in higher-risk categories, and accounts with chargeback histories may face longer settlement holds. Providers use risk-based settlement -- if your chargeback rate exceeds thresholds, your settlement window may be extended as a safeguard. ### 4. Geography Settlement speed varies by country due to banking infrastructure: - UK Faster Payments enables near-instant bank transfers, supporting same-day merchant settlement - US ACH is batch-processed, making same-day settlement harder (though Same Day ACH is expanding) - SEPA in Europe settles within one business day for most transfers - Some developing markets have longer clearing cycles due to banking infrastructure limitations ### 5. Weekends and Holidays Settlement is measured in business days, not calendar days. A transaction captured on Friday afternoon may not settle until Tuesday (or later if Monday is a bank holiday). This is universal across all providers. ## How to Get Faster Settlement If settlement speed is critical to your business, here are practical steps: - Negotiate settlement terms -- if you process significant volume, use it as leverage. Many providers will move from T+3 to T+1 for accounts processing £50K+/month. - Use instant payout features -- Stripe (1%), Square (1.5%), and PayPal (1%) all offer instant transfers for a fee. The maths depends on your cash flow needs: if faster access to £10,000 saves you a late payment penalty or lets you fulfil an order, 1% (£100) may be worth it. - Choose the right payment method -- if you can steer customers toward Open Banking payments rather than cards, you may settle faster and pay lower fees. - Maintain low chargebacks -- keep your chargeback rate below 0.5% (ideally below 0.3%). High chargeback rates trigger risk holds that delay settlement. - Capture transactions promptly -- if you use auth-and-capture (common in e-commerce), capture quickly. Settlement starts from capture, not authorisation. ## Settlement Speed for Platforms and Marketplaces Settlement becomes more complex when you are a platform serving multiple merchants. Each merchant may have different settlement requirements, different risk profiles, and different geographies. Key considerations: - Split settlements -- platforms that take a commission need the PSP to split funds between the platform and merchant accounts. Not all providers handle this cleanly. - Merchant-level settlement -- each merchant on your platform may need different settlement speeds. A low-risk merchant might get T+1 while a new merchant starts at T+3. - Multi-PSP settlement -- if your platform uses different PSPs for different merchants or markets, you need a unified reconciliation view across all providers. See our guide on choosing a payment platform for more on this. - Reserve requirements -- platforms operating under PayFac or marketplace models may need to hold reserves for chargebacks and refunds, which affects net settlement timing. For platforms that need to manage settlement across multiple PSPs, a PSP-neutral payment layer provides a single reconciliation and reporting view regardless of which PSP processes the underlying transaction. ## Frequently Asked Questions ### What is the fastest settlement payment provider? For instant payouts, Stripe, Square, and PayPal all offer same-day transfers to your bank account for a fee (1-1.5%). For standard settlement without extra fees, Mollie (T+1 in EU) and Square (T+1 in some markets) are among the fastest. ### Why does my payment provider hold my funds? Holds typically happen because of high chargeback rates, a sudden spike in transaction volume, a new account without established processing history, or transactions flagged by the provider's risk system. Contact your provider's support team to understand the specific reason. ### Does settlement speed affect my customers? No. Settlement is the transfer of funds to the merchant. Customers see the charge on their account immediately (or within hours) regardless of when the merchant receives the funds. ### Can I get same-day settlement without paying extra? Some providers offer T+1 as standard (Mollie in EU, Square in some cases). True same-day settlement without fees is rare but possible at enterprise volume with negotiated terms from providers like Adyen or Checkout.com. ### How does settlement work with refunds? Refunds are typically deducted from future settlements rather than clawed back from your bank account. If your refund volume exceeds your settlement volume, the provider may debit your account or hold funds to cover the difference. ## Choose the Right Payment Provider for Your Settlement Needs Settlement speed is one factor in choosing a payment provider -- but it should not be the only one. Processing fees, authorisation rates, geographic coverage, and integration complexity all matter. The fastest settlement is worthless if the provider does not support your market or payment methods. For businesses and platforms that need flexibility across providers, see how Shuttle connects to 40+ PSPs with a single integration -- giving you the option to route transactions through whichever provider offers the best combination of speed, cost, and coverage for each market. Compare payment providers · Book a discovery call ## Related Reading Explore More ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ### How to Send Payment Requests: The Complete Guide to Digital Payment Collection ### How to Switch Payment Providers Without Losing Customers ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [choosing a payment platform](/guides/how-to-choose-payment-platform/) - [PSP-neutral payment layer](/guides/payment-layer-explained/) - [see how Shuttle connects to 40+ PSPs](/platforms/) - [Compare payment providers](/payment-providers/) - [Book a discovery call](/discovery/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [GuideHow to Send Payment Requests: The Complete Guide to Digital Payment Collection→](/guides/how-to-send-payment-requests/) - [GuideHow to Switch Payment Providers Without Losing Customers→](/guides/payment-provider-migration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/streamline-your-booking-process-with-payment-links-a-guide-for-travel-agents/ --- # Streamline Your Booking Process with Payment Links: A Guide for Travel Agents | Shuttle > Travel agents can streamline bookings with payment links. Collect deposits and full payments remotely via email or SMS without manual card processing. # Streamline Your Booking Process with Payment Links: A Guide for Travel Agents By Nick Dunse, February 8, 2026 Travel agents can streamline bookings with payment links. Collect deposits and full payments remotely via email or SMS without manual card processing. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. ## Introduction: The Importance of Streamlining Your Booking Process In the travel industry, time is of the essence. Travel agents are constantly juggling multiple bookings, managing client requests, and ensuring that everything runs smoothly. However, the traditional booking process can be time-consuming and prone to errors. This is where streamlining the booking process with payment links can make a significant difference. Traditionally, travel agents would have to manually collect payment information from clients, process the payment through a separate payment gateway, and then confirm the booking. This process not only takes up valuable time but also increases the risk of errors and fraud. By streamlining the booking process with payment links, travel agents can save time, increase efficiency, and provide a better experience for their clients. ## What are Payment Links and How Do They Work? Payment links are a simple and convenient way for travel agents to collect payments from their clients. A payment link is essentially a URL that can be sent to clients via email or messaging platforms. When the client clicks on the link, they are directed to a secure payment page where they can enter their payment details and complete the transaction. Payment links work by integrating with a payment gateway or payment processor. When the client makes a payment through the link, the payment is securely processed and the funds are transferred to the travel agent's account. This eliminates the need for manual payment collection and reduces the risk of errors or fraud. There are several payment link providers available in the market, each offering their own set of features and benefits. Some popular payment link providers include PayPal, Stripe, and Square. These providers offer easy-to-use platforms that allow travel agents to create and customize payment links, track payments, and manage their finances. ## Benefits of Using Payment Links for Travel Agents Using payment links can bring numerous benefits to travel agents. Here are some of the key advantages: 1. Faster and more efficient booking process: By streamlining the payment process, travel agents can save time and complete bookings more quickly. With payment links, clients can make payments instantly, eliminating the need for manual payment collection and processing. This allows travel agents to focus on other aspects of their business and provide a faster and more efficient service to their clients. 2. Increased convenience for clients: Payment links offer a convenient and hassle-free way for clients to make payments. Clients can simply click on the link, enter their payment details, and complete the transaction. This eliminates the need for clients to provide their payment information over the phone or through email, reducing the risk of errors or miscommunication. Additionally, payment links can be accessed from any device with an internet connection, making it easy for clients to make payments on the go. 3. Reduced risk of errors and fraud: Manual payment collection can be prone to errors and fraud. By using payment links, travel agents can reduce the risk of errors in payment processing and ensure that all payments are securely processed. Payment links are encrypted and secure, protecting both the travel agent and the client's sensitive payment information. 4. Improved cash flow management: Payment links allow travel agents to receive payments instantly, improving cash flow management. With traditional payment methods, travel agents may have to wait for checks to clear or for manual payments to be processed. This can cause delays in receiving funds and managing finances. With payment links, travel agents can have better control over their cash flow and have access to funds immediately. ## How to Create Payment Links for Your Clients Creating payment links for your clients is a straightforward process. Here is a step-by-step guide to creating payment links: 1. Choose a payment link provider: Select a payment link provider that suits your needs and sign up for an account. Popular providers include PayPal, Stripe, and Square. 2. Set up your account: Follow the instructions provided by the payment link provider to set up your account. This may involve providing some basic information about your business and linking your bank account for payment processing. 3. Create a payment link: Once your account is set up, you can start creating payment links. Most payment link providers offer a user-friendly interface where you can customize the payment link with your branding and specify the amount to be paid. 4. Share the payment link with your clients: Once the payment link is created, you can share it with your clients via email or messaging platforms. Include clear instructions on how to use the payment link and any additional information that may be required. ## Tips for customizing payment links for your brand: - Use your logo and brand colors to customize the payment page and make it consistent with your brand identity. - Add a personalized message or thank you note to the payment page to enhance the client experience. - Include any additional information or instructions that may be relevant to the payment, such as cancellation policies or refund procedures. ## Integrating Payment Links into Your Booking Process Integrating payment links into your existing booking process is a seamless process. Here are some best practices for incorporating payment links into your workflow: 1. Determine the appropriate stage to send the payment link: Consider at what point in the booking process it makes sense to send the payment link to your clients. This could be after confirming the availability of the desired travel arrangements or after providing a quote. 2. Communicate clearly with your clients: When sending the payment link, clearly communicate the purpose of the link and any additional information that may be required. Provide clear instructions on how to use the payment link and what to expect after making the payment. 3. Follow up with clients: After sending the payment link, follow up with your clients to ensure that they have received and understood the link. Address any questions or concerns they may have and provide any necessary support. ## Best practices for communicating payment links to clients: - Use clear and concise language in your communication to avoid confusion. - Provide multiple channels for communication, such as email, phone, or messaging platforms, to accommodate different client preferences. - Include a deadline for payment to encourage prompt action from your clients. Ensuring Security and Privacy for Your Clients When using payment links, it is crucial to prioritize the security and privacy of your clients' information. Here are some tips for ensuring secure payment processing: 1. Choose a reputable payment link provider: Select a payment link provider that has a strong reputation for security and privacy. Look for providers that offer encryption and other security measures to protect sensitive payment information. 2. Use secure communication channels: When sending payment links to your clients, use secure communication channels such as encrypted email or messaging platforms. Avoid sending payment links through unsecured channels such as regular email or social media. 3. Educate your clients on security best practices: Provide your clients with information on how to protect their personal and payment information when making online payments. Encourage them to use secure networks and to avoid sharing sensitive information over unsecured channels. ## Best Practices for Using Payment Links To maximize the benefits of payment links, it is important to follow best practices. Here are some tips to keep in mind: 1. Keep payment links up to date: Regularly review and update your payment links to ensure that they are accurate and reflect any changes in pricing or terms. 2. Test the payment process: Before sending payment links to clients, test the payment process yourself to ensure that it is working correctly. This will help you identify any issues or errors that may arise. 3. Provide clear instructions: When sending payment links, provide clear instructions on how to use the link and what to expect after making the payment. This will help minimize confusion and ensure a smooth payment process. Common Mistakes to Avoid When Using Payment Links While payment links can greatly simplify the booking process, there are some common mistakes that travel agents should avoid. Here are a few examples: 1. Sending payment links without proper context: It is important to provide clear context when sending payment links to clients. Make sure to explain why the payment is required and what it covers. This will help avoid confusion and ensure that clients understand the purpose of the payment. 2. Not customizing payment links for your brand: Customizing payment links with your branding can help enhance the client experience and build trust. Avoid using generic payment links that do not reflect your brand identity. 3. Failing to follow up with clients: After sending a payment link, it is important to follow up with your clients to ensure that they have received and understood the link. Failing to follow up can lead to delays in payment and potential misunderstandings. Tracking and Managing Payments with Payment Links Tracking and managing payments made through payment links is essential for staying organized and efficient. Here are some tips for effectively managing payments: 1. Use a dedicated system or software: Consider using a dedicated system or software to track and manage payments made through payment links. This can help you stay organized and easily access payment information when needed. 2. Keep detailed records: Maintain detailed records of all payments made through payment links, including the date, amount, and client information. This will help you reconcile payments and provide accurate financial reports. 3. Regularly reconcile payments: Regularly reconcile payments made through payment links with your bank statements to ensure that all payments have been received and processed correctly. ## Conclusion: Simplify Your Booking Process with Payment Links Streamlining the booking process is crucial for travel agents to save time, increase efficiency, and provide a better experience for their clients. Payment links offer a simple and convenient way for travel agents to collect payments, reducing the risk of errors and fraud. By using payment links, travel agents can benefit from a faster and more efficient booking process, increased convenience for clients, reduced risk of errors and fraud, and improved cash flow management. By following best practices and avoiding common mistakes, travel agents can maximize the benefits of payment links and simplify their booking process. In conclusion, payment links are a valuable tool for travel agents looking to streamline their booking process and provide a better experience for their clients. By embracing this technology, travel agents can save time, increase efficiency, and improve their cash flow management. So why wait? Start using payment links today and simplify your booking process. ## Get Payment Links today ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Payment Links for Hotels & Holiday Accommodation: The Complete Guide ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuidePayment Links for Hotels & Holiday Accommodation: The Complete Guide→](/guides/payment-links-for-hotels/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/streamline-your-booking-process-with-payment-links-a-guide-for-travel-agents-2/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/streamline-your-online-business-with-square-payment-links-and-checkout/ --- # Square Payment Links: How to Create, Send & Customise (2026 Guide) | Shuttle > Learn how to create and send Square payment links, what they cost, and when you might need a more flexible alternative for multi-gateway payment links. # Square Payment Links: How to Create, Send & Customise (2026 Guide) By Nick Dunse, February 8, 2026 Learn how to create and send Square payment links, what they cost, and when you might need a more flexible alternative for multi-gateway payment links. Talk to us Make enabling payments for your platform and merchant users easy. Square payment links let you accept payments without a website or checkout page. You create a link in your Square Dashboard, share it via email, SMS, or social media, and your customer pays through a Square-hosted checkout page. It is one of the simplest ways to collect payments online, especially if you already use Square for in-person sales. This guide covers how Square payment links work, what they cost, how to set them up, and when you might need a more flexible alternative. ## What Are Square Payment Links? Square payment links are shareable URLs that direct customers to a hosted checkout page. When a customer clicks the link, they see an order summary and can pay by card -- no account or app required on their end. Key features of Square payment links: - No website needed -- the checkout page is hosted by Square - Shareable anywhere -- email, SMS, WhatsApp, social media, QR codes - Customisable items -- add product name, description, image, and price - Built-in tipping -- optional tip collection at checkout - Automatic receipts -- customers receive email receipts after payment - Real-time tracking -- see payment status in your Square Dashboard Square payment links work with Square's existing ecosystem -- inventory, invoicing, and reporting all sync automatically. ## How to Create a Square Payment Link Creating a payment link in Square takes less than two minutes: - Log into Square Dashboard -- go to Online Checkout → Payment Links - Click "Create a link" -- choose between a single item, multiple items, or a donation - Add item details -- name, price, description, and optional image - Configure options -- set quantity limits, add custom fields, enable tipping - Generate and share -- copy the link or download a QR code You can also create payment links directly from the Square Point of Sale app on mobile, which is useful for sending links on the go. ## Square Payment Links Pricing Square payment links use the same processing rates as Square Online: Card-Present Rate Online/Link Rate Monthly Fee 2.6% + 10¢ 2.9% + 30¢ There is no monthly subscription for payment links -- you only pay per transaction. This makes Square attractive for low-volume sellers or businesses that use payment links occasionally alongside in-person sales. ## When Square Payment Links Work Well Square payment links are a strong fit in specific situations: - You already use Square POS -- everything stays in one ecosystem. Inventory, reporting, and customer data sync automatically. - You sell a small number of items -- services, appointments, or one-off products where a full e-commerce site is overkill. - You need to collect payments in person and online -- Square's unified dashboard shows both channels side by side. - You are a sole trader or small team -- no developer needed, no integration work, live in minutes. ## Limitations of Square Payment Links Square payment links have some constraints that matter as your business grows: - Single gateway -- you can only process through Square. If you want to use a different payment provider -- or give your customers a choice -- you cannot. - Limited customisation -- the checkout page uses Square's branding and layout. You can add your logo but cannot fully white-label the experience. - No multi-currency support -- links are priced in your account's home currency. International customers see the price in your currency and their bank handles conversion. - No recurring payments via links -- you cannot create subscription payment links. For recurring billing, you need Square Invoices or a separate subscription tool. - Account stability risk -- Square uses an aggregated model. High-volume or high-risk businesses occasionally face account holds or freezes, which affects all payment channels including links. ## Square Payment Links vs Other Payment Link Providers Here is how Square compares to other payment link options: Setup time Minutes (needs Stripe account) Processing rate (UK) 1.5% + 20p 2.9% + 30p Varies by PSP White-label checkout Multiple payment gateways No (Square only) No (Stripe only) No (PayPal only) Yes (40+ PSPs) Recurring payments No (via links) Custom fields QR code generation Voice / phone payments PCI compliance scope Handled by Square Handled by Stripe Handled by PayPal SAQ-A (handled) For more detail on how Shuttle payment links work with Square and other providers, see Payment Links for Square. ## When You Need More Than Square Payment Links Square payment links work well for small businesses that process exclusively through Square. But several scenarios push businesses toward more flexible alternatives: - You want to use your existing payment provider -- if you process through Worldpay, Adyen, or another PSP, Square payment links are not an option. You need payment links that connect to your gateway, not someone else's. - You are a platform serving merchants -- if your software serves businesses that each have their own payment providers, you need multi-PSP payment links that let each merchant use their own gateway. - You need white-label checkout -- if your brand experience matters, a checkout page with someone else's branding creates friction. White-label payment links display your brand throughout. - You collect payments over the phone -- Square payment links are digital-only. For businesses that need to take payments during phone calls, voice payments combined with payment links provide both channels. - You operate across multiple countries -- Square operates in a limited number of markets. Businesses serving customers globally need payment links that work with local payment methods and acquirers in each market. ## Frequently Asked Questions ### Are Square payment links free? There is no monthly fee for using Square payment links. You pay standard Square processing rates per transaction -- 2.5% in the UK or 2.9% + 30¢ in the US for online transactions. ### Can I customise the checkout page? You can add your logo and change colours, but the checkout page is hosted by Square and uses their layout. Full white-label customisation is not available. ### Do Square payment links expire? By default, Square payment links do not expire. You can set a custom expiration if you want to create time-limited offers. ### Can I use Square payment links internationally? Square payment links work in the countries where Square operates (US, UK, Canada, Australia, Japan, France, Ireland, Spain). Customers outside those countries can still pay, but the price is in your local currency and they may incur conversion fees. ### Can I track who opened my payment link? Square does not provide open tracking. You can see when a payment is completed, but not how many people viewed the checkout page without paying. ## Get Payment Links That Work With Any Provider Square payment links are a solid starting point for businesses already in the Square ecosystem. But if you need payment links that work with your existing payment provider -- or with multiple providers across different markets -- Shuttle payment links connect to 40+ PSPs through a single integration. For platforms and software companies that serve merchants, Shuttle provides white-label payment links, voice payments, and embedded checkout -- all under your brand, all PSP-neutral. See how Shuttle payment links work · Book a discovery call ## Related Reading Explore More ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Payment Links for Square](/blog/payment-links-for-square/) - [multi-PSP payment links](/platforms/links-checkout/) - [voice payments](/platforms/voice-checkout/) - [Shuttle payment links](/platforms/links-checkout/) - [See how Shuttle payment links work](/platforms/links-checkout/) - [Book a discovery call](/discovery/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/stripe-connect-limitations/ --- # 5 Stripe Connect Limitations That Force Platforms to Switch | Shuttle > Stripe Connect works well for early-stage platforms. But at scale, these 5 limitations -- from country coverage to proprietary tokens -- force a rethink. # 5 Stripe Connect Limitations That Force Platforms to Switch By shuttle-team, March 22, 2026 Stripe Connect works well for early-stage platforms. But at scale, these 5 limitations -- from country coverage to proprietary tokens -- force a rethink. Talk to us Make enabling payments for your platform and merchant users easy. Stripe Connect is the default starting point for platforms embedding payments. The developer experience is excellent. The documentation is best-in-class. For most early-stage platforms, it is the right choice. This is not a hit piece on Stripe. Stripe is very good at what it does -- processing payments through its own acquiring network with a developer-first API. But Stripe Connect is a product built to serve Stripe's business model: every transaction processed through Stripe's rails, every merchant onboarded to Stripe's ecosystem. That alignment works perfectly when your platform is small. It starts to break when your platform scales, your merchants diversify, and your payment requirements extend beyond what a single PSP can cover. Here are five specific limitations that platforms consistently hit. Not theoretical concerns -- real constraints that force architectural decisions. ## 1. The 46-Country Ceiling Stripe operates in 46+ countries. For a US or European platform, that coverage feels comprehensive. For a platform with global ambitions, it is a hard boundary. The problem. Stripe's coverage is concentrated in North America, Europe, and selected APAC markets. Significant commercial markets -- including much of the Middle East, Africa, Southeast Asia, and Latin America -- either have no Stripe presence or limited acquiring capability. Even within supported countries, Stripe may not have local acquiring relationships. Processing a transaction in a Stripe-supported country through a foreign acquirer means higher interchange fees, lower authorisation rates, and a worse experience for the end customer. Why it matters. If your platform serves merchants in 60 countries, you cannot route all of them through Stripe. You need local acquirers in markets Stripe does not cover -- which means building separate integrations, managing multiple PSP relationships, and maintaining parallel payment infrastructure. What platforms do. Some build bespoke integrations with regional PSPs alongside Stripe Connect. This works but creates maintenance overhead -- two (or more) payment codepaths, two reconciliation systems, two sets of webhooks. Others move to a PSP-neutral architecture that handles multi-PSP routing through a single integration. ## 2. Complex, Unpredictable Pricing at Scale Stripe's pricing is transparent at the headline level: 2.9% + 30p in the UK (1.5% + 20p for European cards). Below the surface, the cost structure is significantly more complex. The problem. Connected account fees ($2/month per active account), payout fees, identity verification charges, Stripe Tax fees, dispute fees, Instant Payouts surcharges, and cross-border fees all add up. For a platform with thousands of connected accounts, the blended cost per transaction can be materially higher than the headline rate. Pricing also changes. Stripe has historically adjusted fee structures with limited advance notice. For platforms that have built financial models around specific unit economics, a pricing change from a sole PSP is an existential risk -- not just a cost increase. Why it matters. Platforms that take a revenue share on payments (application fees in Stripe's model) earn the margin between what the merchant pays and what Stripe charges. As Stripe's blended cost rises, the platform's margin compresses. At scale, even a 0.2% increase across millions of transactions significantly affects profitability. What platforms do. The typical response is to negotiate. Stripe offers custom pricing for high-volume platforms, but negotiating leverage is limited when Stripe is your only option. Platforms with multi-PSP capability can benchmark Stripe's rates against Adyen, Worldpay, or regional acquirers -- and route volume to the most competitive provider for each transaction type and geography. ## 3. No PSP Flexibility Stripe Connect routes every transaction through Stripe's acquiring network. There is no mechanism to process through a third-party PSP. The problem. Enterprise merchants frequently mandate their own PSP. A hotel chain with a global Worldpay contract, an insurance company with an existing Adyen relationship, or a retailer with negotiated interchange rates through a specific acquirer -- none of these can use their preferred provider through Stripe Connect. For the platform, the answer to "can you process through our PSP?" is "no." That answer costs deals. Why it matters. This is the most common trigger for platforms outgrowing Stripe Connect. Enterprise PSP mandates are not preferences -- they are procurement requirements. A platform that cannot accommodate them is excluded from enterprise RFPs. The constraint also limits strategic flexibility. If Stripe experiences an outage, your entire payment capability goes down. If a competitor PSP offers better authorisation rates for a specific card type or region, you cannot take advantage of it. Every transaction, regardless of context, routes through one provider. What platforms do. Some build parallel integrations -- Stripe Connect for most merchants, plus direct integrations with Adyen or Worldpay for enterprise accounts. This is expensive to maintain and fragments the merchant experience. Others adopt a payment layer that abstracts PSP routing, allowing the platform to add or remove gateways without touching their core integration. ## 4. Support Quality Degrades at Scale Stripe's developer documentation and self-serve tooling are genuinely excellent. For a platform processing a few hundred transactions per month, the support experience is good. The problem. At enterprise scale -- thousands of connected accounts, complex payout structures, multi-currency settlement, high-risk merchant categories -- support needs change. Issues become more nuanced. Response times matter more. And the support experience does not always scale with the platform. Common pain points include: - Account reviews and holds. Stripe's automated risk systems can freeze connected accounts or hold funds with limited explanation. For a platform responsible for thousands of merchants, a single account freeze can trigger cascading support tickets. - Dispute handling. At volume, chargeback management becomes operationally complex. Stripe's dispute tools are functional but not designed for platforms managing disputes across thousands of sub-merchants. - Onboarding friction. Stripe's Know Your Customer (KYC) process is automated, which is fast for straightforward businesses. For merchants in complex or regulated industries -- insurance, travel, financial services -- the automated process can stall, and escalation paths are not always clear. - Custom requirements. Enterprise platforms often need bespoke settlement schedules, custom reporting, or specific compliance configurations. These requests require human support, and response times for custom work can extend to weeks. Why it matters. For early-stage platforms, Stripe's self-serve model is a feature. For platforms processing significant volume with enterprise merchants, it becomes a constraint. The mismatch between the platform's support needs and Stripe's support model creates operational friction that compounds over time. What platforms do. Some platforms assign internal engineering resource to manage Stripe-specific issues -- effectively building an internal Stripe support team. Others negotiate dedicated account management as part of custom pricing agreements. Platforms that move to a multi-PSP architecture gain leverage: if one provider's support is inadequate, they can shift volume to another. ## 5. Proprietary Tokens Lock You In When a customer saves a card through Stripe, Stripe creates a proprietary token. That token works with Stripe and only with Stripe. The problem. If you decide to switch away from Stripe -- or even add a second PSP alongside Stripe -- those tokens cannot be used with the new provider. Every stored card becomes inaccessible. For a platform with 50,000 stored payment methods, this means one of two things: - Ask every customer to re-enter their card details. Industry data suggests 20-40% will not complete this. That is 10,000-20,000 customers who may churn, fail to renew, or simply stop paying. - Run Stripe indefinitely for legacy cards while routing new transactions through a different provider. This means maintaining two integrations, two reconciliation processes, and two support relationships -- permanently. Neither option is acceptable. Both impose significant cost on the platform. Why it matters. Proprietary tokens are the strongest form of payment provider lock-in. They turn a commercial relationship into a technical dependency. The longer you stay, the more tokens accumulate, and the harder it becomes to leave. Stripe supports network tokenisation in some configurations, but network tokens are not the default, and not all card types or regions support them. The majority of Stripe Connect platforms are holding proprietary tokens. What platforms do. The cleanest solution is to adopt portable tokens from the start -- either network tokens or provider-agnostic tokens issued by a payment abstraction layer. For platforms already holding proprietary Stripe tokens, gradual migration through natural re-entry points (subscription renewals, checkout sessions) is the least disruptive path. The full playbook is covered in our payment provider migration guide. ## What PSP-Neutral Architecture Actually Looks Like The common thread across all five limitations is architectural: Stripe Connect is a single-PSP integration, and single-PSP architectures create single points of failure, single points of negotiation, and single points of lock-in. The alternative is a PSP-neutral architecture -- a single integration that connects to multiple PSPs and routes transactions based on geography, cost, merchant preference, or performance. In practice, this means: - One API for your platform, regardless of which PSP processes the transaction - Multi-PSP routing -- Stripe for US merchants, Adyen for Europe, a local acquirer for Southeast Asia - Portable tokens that work across providers, eliminating lock-in - Failover capability -- if one PSP goes down, transactions route to another - Commercial leverage -- you can benchmark and negotiate rates because switching cost is near zero Shuttle provides this architecture out of the box. A single integration connects your platform to 40+ PSPs across voice, links, chat, and embedded checkout. Tokens are portable. Adding a gateway is configuration, not code. Platforms that use Shuttle do not face the five limitations above -- because they are not locked into any single provider. If you are hitting one or more of these constraints, the question is not whether to move away from Stripe Connect. It is whether to move to another single-PSP dependency, or to an architecture that makes the question irrelevant. ## Further Reading - Shuttle vs Stripe Connect -- Detailed Comparison - Shuttle vs Stripe - When Your SaaS Outgrows Stripe Connect - Payment Provider Lock-In: How It Happens and How to Avoid It - Embedded Payments Without Becoming a PayFac ## Related Reading Explore More ### When Your SaaS Outgrows Stripe Connect: A Migration Playbook ### Shuttle vs Stripe Connect ### Stripe Connect Alternatives for Platforms ### Twilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ## Links - [Book a Call →](/discovery/) - [PSP-neutral architecture](/guides/psp-neutral-vs-single-psp/) - [multi-PSP capability](/guides/psp-neutral-vs-single-psp/) - [outgrowing Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Enterprise PSP mandates](/guides/enterprise-psp-mandates/) - [payment provider lock-in](/guides/payment-provider-lock-in/) - [payment provider migration guide](/guides/payment-provider-migration/) - [Shuttle vs Stripe Connect -- Detailed Comparison](/alternatives/stripe-connect/) - [Shuttle vs Stripe](/vs/stripe-connect/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Payment Provider Lock-In: How It Happens and How to Avoid It](/guides/payment-provider-lock-in/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [GuideWhen Your SaaS Outgrows Stripe Connect: A Migration Playbook→](/guides/when-saas-outgrows-stripe-connect/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [AlternativeStripe Connect Alternatives for Platforms→](/alternatives/stripe-connect/) - [GuideTwilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative→](/guides/twilio-stripe-pay-connector/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/stripe-unbundling-multi-psp/ --- # What Stripe's Unbundling Tells Us About the Future of Payments | Shuttle > Stripe opened Checkout, Billing, and Radar to merchants on other processors. Here's why that confirms multi-PSP is the new default -- and what platforms... # What Stripe's Unbundling Tells Us About the Future of Payments By shuttle-team, February 23, 2026 Stripe opened Checkout, Billing, and Radar to merchants on other processors. Here's why that confirms multi-PSP is the new default -- and what platforms... Talk to us Make enabling payments for your platform and merchant users easy. ## What Stripe Actually Did In a move that received surprisingly little attention given its strategic weight, Stripe began opening Checkout, Billing, and Radar to merchants processing on other payment providers -- Adyen, PayPal, and others. To be clear about what this means technically: a merchant could previously only use Stripe Checkout if they were processing transactions through Stripe. The checkout UI, the billing engine, the fraud tooling -- all of it was bundled with Stripe's processing stack. Use Stripe's services, use Stripe's rails. That was the deal. The unbundling changes that. Merchants can now access Stripe's value-added service layer without routing transactions through Stripe. Stripe Checkout on top of Adyen processing. Stripe Radar's fraud signals on top of PayPal. The experience layer and the processing layer become independently selectable. This is not a minor product update. It is a structural repositioning -- and it signals something important about where the payments market is heading. ## Why Stripe Unbundled: The Strategic Logic Stripe built one of the most successful lock-in strategies in the history of fintech. The logic was elegant: make the developer experience so good that switching becomes unthinkable. Bind the checkout UI to the billing engine. Bind the billing engine to the fraud tooling. Bind all of it to Stripe's processing rails. Every layer of the stack reinforces the others. Leaving one means leaving all. That strategy worked exceptionally well -- right up to the point where it started costing Stripe enterprise deals. Enterprise customers mandate their PSPs. They have negotiated rates, compliance frameworks, and treasury infrastructure tied to existing gateway relationships. A CTO at an enterprise insurance carrier is not switching from Worldpay to Stripe because the checkout experience is nicer. A procurement team at a large travel operator is not unwinding a multi-year PSP contract to access Stripe's billing engine. Stripe's response to this reality -- for years -- was to improve the product and wait for enterprise adoption to follow. But enterprise payment infrastructure is sticky in a way that developer-led adoption is not. The lock-in that protected Stripe's merchant base from leaving also protected enterprise customers from joining. The unbundling is an acknowledgement of that reality. Stripe is saying: if you won't come to our rails, we'll bring our services to yours. It is a concession that the vertical integration strategy has a ceiling -- and Stripe is choosing to grow through the ceiling rather than stay inside it. There is also a competitive logic. Adyen, Checkout.com, and Worldpay are not standing still. Enterprise payment infrastructure has improved materially. The processing layer is increasingly commoditised at the high end. Stripe's genuine differentiation has always been in the experience layer -- Checkout's conversion optimisation, Radar's fraud accuracy, Billing's subscription management. Unbundling these services lets Stripe compete on the dimensions where it is strongest, rather than trying to win processing volume against entrenched enterprise PSPs on their home turf. ## What This Means for Platforms The immediate read on Stripe's unbundling is merchant-centric: more flexibility for merchants who want Stripe's UX without Stripe's rails. That is true. But the deeper implication is about platforms. If Stripe -- the company that built the most successful vertically integrated payments stack in history -- is decoupling its experience layer from its processing layer, it is because the market is forcing that decoupling. Stripe is not doing this out of generosity. It is doing it because the alternative is losing the market. That market signal should inform how platforms think about their own payment architecture. A platform that standardises on a single PSP is making a bet that the vertically integrated model still holds -- that bundling checkout, processing, and value-added services through one provider is the right architecture for the next five years. Stripe's own move suggests that bet is getting riskier, not safer. Enterprise customers are increasingly unwilling to accept payment infrastructure they did not choose. PSP mandates are a real and growing force in enterprise sales cycles. A platform that cannot support a customer's existing PSP relationship does not win that deal. This is already the reality -- Stripe's unbundling is simply the market's most prominent player adapting to it publicly. For platforms, the implication is direct: the architecture that protects your enterprise revenue is not the one that locks you to a single PSP. It is the one that separates the experience layer from the processing layer -- so that when an enterprise customer arrives with a Worldpay mandate, the answer is "no problem" rather than "three months of engineering work." ## The Horizontal Payment Layer Stripe's unbundling reveals a structural shift in how payment infrastructure is being organised. The question it forces is: if the experience layer and the processing layer are separable, what sits between them? The answer is what we would call a horizontal payment layer -- infrastructure that connects across PSPs rather than within a single one. The vertically integrated model -- one PSP owning checkout, billing, fraud, and processing -- made sense when the payments market was fragmented and the primary problem was developer friction. Stripe solved that problem better than anyone. But the next problem is different: how do you manage payment infrastructure across multiple PSPs, channels, and geographies without rebuilding everything for each one? That problem is horizontal, not vertical. It is not about making one PSP's stack better. It is about making any PSP's stack accessible through a consistent interface. A horizontal payment layer: - Connects to 40+ PSPs through a single integration point - Abstracts the processing layer so that changing or adding a PSP is configuration, not engineering - Applies consistent merchant onboarding, checkout experience, and compliance standards regardless of which PSP is underneath - Covers multiple payment channels -- embedded checkout, voice, payment links, chat, AI agents -- through the same infrastructure - Handles PCI scope so that neither the platform nor the merchant inherits it This is structurally different from what either Stripe or an orchestration tool offers. Stripe unbundling its services layer still presupposes that the merchant has a Stripe relationship. An orchestration tool optimises routing between PSPs but does not handle merchant onboarding, channel expansion, or platform distribution. The horizontal payment layer does all of it -- it makes PSPs portable into software platforms. Stripe's move validates this model. When the market's most vertically integrated player starts unbundling, the market is telling you that horizontal infrastructure is the durable architecture. The control point in multi-PSP payments is not any individual PSP's stack. It is what sits across all of them. ## What Platforms Should Do Now Stripe's unbundling is a market signal, not a tactical instruction. Here is what it should change about how platforms think: ### Stop assuming a single PSP is the safe default The conventional wisdom -- "standardise on Stripe and keep it simple" -- was defensible when the market rewarded vertical integration. It is less defensible now. Stripe's own strategy is moving away from the all-or-nothing model. Platforms should move before enterprise deal losses force them to. ### Separate your experience layer from your processing layer This is the structural move Stripe is making at the PSP level. Platforms should make the same move at the platform level. Your checkout UI, your merchant onboarding, your payment configuration -- these should not be tightly coupled to any single PSP's API. When you need to add a gateway, it should be a configuration change, not an engineering project. If you are currently building direct PSP integrations one by one, you are building technical debt that compounds with every new enterprise customer mandate. The comparison between PSP-neutral and single-PSP architectures is no longer primarily about flexibility as a nice-to-have. It is about whether your platform can compete for enterprise customers. ### Think in channels, not just checkout Multi-PSP is part of the answer. But the broader shift is that payments are no longer a checkout event. Enterprise merchants are increasingly processing payments over voice calls, via SMS links, through AI agent conversations, and across embedded channels that have nothing to do with a web checkout page. A horizontal payment layer covers these channels through the same integration. A direct PSP integration -- even with multiple PSPs -- typically covers online checkout only. Adding voice, links, or AI agent payment capture is a separate project. Stripe's unbundling is, at its core, about separating the channel from the processor. Platforms should apply the same logic more broadly: payment infrastructure that works across all channels regardless of which PSP is underneath. ### Treat PSP relationships as merchant assets, not platform constraints One of the clearest signals from Stripe's move: PSP relationships increasingly belong to merchants, not platforms. Merchants want to keep their existing PSP relationships -- their negotiated rates, their compliance certifications, their treasury integrations. A platform that forces merchants onto its chosen PSP is not winning on the basis of better payments. It is winning on the basis of convenience -- and that advantage erodes as enterprise merchants become less willing to accept payment constraints from their software vendors. Platforms that monetise payments without PSP lock-in capture more of the enterprise market and generate more durable payment revenue. PSP choice becomes a competitive differentiator in enterprise sales, not a concession. ### Move before your competitors do The platforms that recognise this shift early get to design their architecture for the multi-PSP world. The platforms that wait get forced into a costly migration when the first enterprise PSP mandate kills a deal they needed to close. Stripe's unbundling tells you the direction of travel. The question is whether your platform's payment infrastructure is built for where the market is going -- or where it was five years ago. ## The Bigger Picture There is a tempting read of Stripe's unbundling as a sign of weakness -- that Stripe is losing ground and unbundling is a defensive measure. That reading misses the point. Stripe is one of the most strategically sophisticated companies in payments. The unbundling is not a retreat. It is a recognition that the market is multi-PSP, and that Stripe's best position in a multi-PSP world is as a services layer -- not as a monolithic stack that forces an all-or-nothing choice. That is a smart move. But it validates something that PSP-neutral infrastructure providers have been building toward for years: the processing layer is separating from the experience layer, and the infrastructure that connects them horizontally is where durable value accumulates. The multi-PSP world is not a transition phase on the way back to a winner-takes-all processing market. It is the destination. Payment infrastructure is becoming horizontal. The control point -- for platforms, for PSPs, and for the companies that sit between them -- is what connects across all providers. Stripe's unbundling is the most visible signal yet that the market knows this. ## Related Reading - Shuttle vs Stripe Connect -- how single-PSP constraints play out in practice - PSP-Neutral vs Single-PSP: Which Approach Is Right? -- the architectural decision for platforms - How Platforms Monetise Payments Without PSP Lock-In -- why PSP flexibility drives more revenue - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways -- the business case for multi-PSP - Shuttle vs Stripe Connect (Alternatives) -- evaluating your options Shuttle is the PSP-neutral payment layer for platforms. 40+ PSP integrations through a single API. White-label checkout, merchant onboarding, and PCI DSS Level 1 compliance included. Your merchants keep their PSP. Your platform keeps its roadmap. Book a Demo | See Platforms Explore More ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### Twilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative ### Enterprise PSP Mandates: Why Platforms Need Multiple Gateways ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### How to Take Payments on ElevenLabs Agents: Native Stripe vs Multi-PSP ### How to Take Payments on Synthflow Voice Agents: Native Stripe vs Multi-PSP ## Links - [Book a Call →](/discovery/) - [PSP mandates are a real and growing force in enterprise sales cycles](/guides/enterprise-psp-mandates/) - [comparison between PSP-neutral and single-PSP architectures](/guides/psp-neutral-vs-single-psp/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Shuttle vs Stripe Connect (Alternatives)](/alternatives/stripe-connect/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Demo](/discovery/) - [See Platforms](/platforms/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuideTwilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative→](/guides/twilio-stripe-pay-connector/) - [GuideEnterprise PSP Mandates: Why Platforms Need Multiple Gateways→](/guides/enterprise-psp-mandates/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideHow to Take Payments on ElevenLabs Agents: Native Stripe vs Multi-PSP→](/guides/elevenlabs-payments/) - [GuideHow to Take Payments on Synthflow Voice Agents: Native Stripe vs Multi-PSP→](/guides/synthflow-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/tag/stripe/ --- # Redirecting to: /blog/ ## Links - [Redirecting from to](/blog/) --- URL: https://www.shuttleglobal.com/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/ --- # QuickBooks ACH Payments: Setup, Fees & Tips | Shuttle > Learn how to accept ACH payments in QuickBooks Online. Compare fees, setup steps, processing times, and alternatives for collecting bank transfers. # QuickBooks ACH Payments: Setup, Fees & Tips By Nick Dunse, May 31, 2024 Learn how to accept ACH payments in QuickBooks Online. Compare fees, setup steps, processing times, and alternatives for collecting bank transfers. Talk to us Make enabling payments for your platform and merchant users easy. ACH payments are one of the most cost-effective ways to collect money through QuickBooks. Rather than paying 2.9% on every credit card transaction, you can accept direct bank transfers at a fraction of the cost -- QuickBooks charges just 1% per ACH transaction, capped at $10. This guide covers everything you need to know about QuickBooks ACH payments: how to enable them, what they cost, how they compare to card payments, and when you might need an alternative approach. ## What Are ACH Payments? ACH (Automated Clearing House) payments are electronic bank-to-bank transfers processed through the ACH network. When a customer pays an invoice via ACH, the funds move directly from their bank account to yours -- no card network involved. There are two types of ACH transactions relevant to QuickBooks users: - ACH debit -- you pull funds from the customer's bank account (used for invoice payments) - ACH credit -- the customer pushes funds to you from their bank (used for direct deposit, vendor payments) When customers pay QuickBooks invoices via ACH, they are authorizing an ACH debit. QuickBooks Payments handles the transaction, verifies the bank account, and deposits funds into your linked account. ## Why Accept ACH Payments in QuickBooks? For businesses that invoice clients regularly, ACH payments offer significant advantages over credit card payments: - Lower transaction fees. ACH costs 1% per transaction (capped at $10) compared to 2.9% + $0.25 for credit cards. On a $5,000 invoice, that is $10 vs $145.25. - Lower chargeback risk. ACH disputes are less common than credit card chargebacks and follow a different, more merchant-friendly process. - Better for large invoices. The $10 fee cap means ACH is dramatically cheaper for invoices over $1,000. Credit card fees scale linearly with no cap. - No card expiration issues. Bank accounts do not expire the way credit cards do, which reduces failed payments for recurring invoices. - Automatic reconciliation. ACH payments received through QuickBooks are automatically matched to the corresponding invoice, saving bookkeeping time. If you are new to accepting online payments in QuickBooks, start with our step-by-step guide to accepting online payments in QuickBooks for the full setup walkthrough. ## How to Set Up ACH Payments in QuickBooks Online Enabling ACH payments in QuickBooks Online requires a QuickBooks Payments account. Here is how to get started: ### Step 1: Activate QuickBooks Payments If you do not already have QuickBooks Payments enabled, navigate to Settings > Payments in QuickBooks Online and follow the prompts to apply. You will need to provide your business details, bank account information, and verify your identity. Approval typically takes 1-2 business days. ### Step 2: Enable ACH on Invoices Once QuickBooks Payments is active, go to Settings > Account and settings > Payments. Under "Payment methods," make sure "Bank transfer (ACH)" is toggled on. This allows customers to pay invoices using their bank account details. ### Step 3: Send an Invoice with ACH Enabled Create a new invoice as you normally would. At the bottom, you will see the online payment options. Ensure "Bank transfer" is checked. When you send the invoice, your customer will see a "Pay now" button that includes the option to pay via bank transfer alongside any other enabled payment methods. ### Step 4: Customer Completes Payment The customer clicks the payment link in the invoice email, selects "Bank transfer," and enters their bank routing and account numbers. QuickBooks verifies the account via micro-deposits (two small transactions the customer confirms) for first-time payers. Subsequent payments from the same account skip this step. ## QuickBooks ACH Fees: What You Will Pay QuickBooks Payments charges a flat 1% fee on ACH transactions, with a maximum of $10 per transaction. There is no monthly fee specifically for ACH -- the cost is included in your QuickBooks Payments account. Here is how the fee breaks down at different invoice amounts: - $100 invoice -- $1.00 ACH fee (1%) - $500 invoice -- $5.00 ACH fee (1%) - $1,000 invoice -- $10.00 ACH fee (capped) - $5,000 invoice -- $10.00 ACH fee (capped) - $25,000 invoice -- $10.00 ACH fee (capped) The $10 cap is what makes QuickBooks ACH particularly attractive for B2B businesses and anyone sending invoices over $1,000. Compare that to credit card processing, where a $5,000 invoice would cost $145.25 in fees at the standard 2.9% + $0.25 rate. ## ACH vs Credit Card Payments in QuickBooks Both ACH and credit card payments can be enabled on QuickBooks invoices simultaneously. Here is how they compare across the factors that matter most: Transaction fees: ACH charges 1% capped at $10. Credit cards charge 2.9% + $0.25 with no cap. For a $2,000 invoice, ACH costs $10 while a credit card costs $58.25. Processing speed: Credit card payments typically deposit within 1-2 business days. ACH payments take 5-7 business days to fully clear and deposit. If cash flow timing is critical, cards are faster. Customer experience: Credit cards are more familiar to most customers and require less information (card number vs routing and account numbers). ACH requires bank details, which some customers may not have readily available. Disputes and chargebacks: Credit card chargebacks are common and typically favor the cardholder. ACH returns are less frequent and follow NACHA rules with more defined timelines. Transaction limits: Credit cards are limited by the cardholder's credit limit. ACH pulls directly from a bank account, making it better suited for large B2B payments. The best practice for most businesses is to enable both payment methods and let customers choose. You save on fees when they select ACH, but you do not lose the sale if they prefer to pay by card. Integrating a payment gateway like Stripe with QuickBooks can give you even more flexibility -- see our guide on maximizing invoice payments with Stripe integration. ## ACH Payment Processing Times in QuickBooks ACH payments in QuickBooks do not settle instantly. Here is the typical timeline: - Day 0: Customer submits payment. QuickBooks initiates the ACH debit request. - Days 1-3: The ACH network processes the transfer between banks. The invoice status in QuickBooks shows as "Payment pending." - Days 5-7: Funds are deposited into your linked bank account. The invoice is marked as paid. First-time payers may experience an additional 1-2 day delay for micro-deposit verification. QuickBooks sends two small deposits (usually under $1 each) to the customer's bank account, and the customer must confirm the exact amounts before the payment can process. Keep in mind that ACH processing only occurs on business days. Payments submitted on a Friday afternoon will not begin processing until Monday, so the total calendar time can stretch to 9-10 days. ## Limitations of QuickBooks ACH Payments While QuickBooks ACH is a solid option for many businesses, it has some constraints worth knowing about: - US-only. QuickBooks ACH payments are limited to US bank accounts. If you have international clients, they cannot pay via ACH through QuickBooks. - Slow settlement. The 5-7 business day processing window is a real downside if you need funds quickly. Same-day ACH is not available through QuickBooks Payments. - Requires QuickBooks Payments. You cannot accept ACH on QuickBooks invoices using a third-party processor alone. You need an active QuickBooks Payments subscription. - No recurring ACH automation. QuickBooks does not support automatic recurring ACH debits. You can set up recurring invoices, but the customer must manually approve each payment. - Limited payment page customization. The QuickBooks invoice payment page uses a standard Intuit-branded template. You cannot fully customize the payment experience to match your brand. - Insufficient funds risk. Unlike credit cards, ACH payments can fail after the initial submission if the customer's bank account has insufficient funds. QuickBooks charges a $25 returned payment fee in these cases. For businesses that need more control over their payment experience, or that serve international clients, third-party integrations can fill the gaps. Our guide to QuickBooks integration with Authorize.Net covers one popular alternative setup. ## Using Payment Links for ACH Collection If QuickBooks ACH does not fully meet your needs -- whether due to branding limitations, international requirements, or integration constraints -- payment links offer a flexible alternative for collecting ACH payments. A payment link is a hosted checkout page that you can send to customers via email, SMS, or any messaging channel. The customer clicks the link, enters their bank details, and the ACH transfer is initiated -- all outside of QuickBooks. This approach is particularly useful for: - Businesses that want branded payment pages instead of the standard Intuit template - Companies that need to collect ACH payments from customers who are not part of the QuickBooks invoicing workflow - Platforms and SaaS businesses that want to embed ACH collection into their own product Read more about how ACH payment links can streamline collection for small businesses. If you are a platform looking to embed payment collection directly into your software, explore how Shuttle can help. ## Frequently Asked Questions ### How much does QuickBooks charge for ACH payments? QuickBooks charges 1% of the transaction amount for ACH payments, with a maximum fee of $10 per transaction. This means any invoice over $1,000 costs the same $10 to process via ACH, making it significantly cheaper than credit card processing for larger amounts. ### How long does an ACH payment take to process in QuickBooks? ACH payments in QuickBooks typically take 5-7 business days to fully process and deposit into your bank account. First-time payers may experience an additional 1-2 days for micro-deposit verification. Payments submitted on weekends or holidays will not begin processing until the next business day. ### Can I accept ACH payments on QuickBooks invoices without QuickBooks Payments? No. To accept ACH payments directly on QuickBooks invoices, you need an active QuickBooks Payments account. However, you can use third-party payment processors alongside QuickBooks and manually record the payments. Payment links from providers like Stripe also let you collect ACH payments independently and reconcile them in QuickBooks afterward. ### What happens if an ACH payment fails in QuickBooks? If an ACH payment fails -- usually due to insufficient funds, an invalid account number, or a closed account -- QuickBooks will notify you and the invoice will revert to unpaid status. Intuit charges a $25 returned payment fee for failed ACH transactions. You will need to contact your customer to arrange an alternative payment method or retry the ACH transfer. ### Should I offer ACH and credit card payments on the same invoice? Yes. Offering both ACH and credit card options on the same invoice gives your customers flexibility and can improve your payment collection rate. Customers who prefer lower fees or who are paying large invoices will gravitate toward ACH, while those who want faster processing or rewards points will choose credit cards. You benefit either way -- the invoice gets paid. Want to use your existing gateway with QuickBooks invoices instead of QuickBooks Payments? See our guide: How to Accept Payments on QuickBooks Invoices (Without Switching Provider). ## Getting Started QuickBooks ACH payments are one of the simplest ways to reduce processing costs on your invoices. The setup takes minutes, the 1% capped fee is hard to beat, and most B2B customers are comfortable paying via bank transfer. Start by enabling ACH in your QuickBooks Payments settings, then toggle it on for your next invoice. If you also want branded payment links you can send by email, WhatsApp, or SMS -- accepting cards, Apple Pay, Google Pay, and ACH on a checkout page that looks like your business -- try Shuttle Links & Checkout. Works alongside QuickBooks, no replacement needed. ## Related Reading Explore More ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ### Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay ### PayPal + QuickBooks Integration: Add PayPal to QuickBooks Invoices ### How to Accept Payments on QuickBooks Invoices (Without Switching Provider) ### How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments ### Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [step-by-step guide to accepting online payments in QuickBooks](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) - [Stripe](/payment-providers/stripe/) - [maximizing invoice payments with Stripe integration](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [QuickBooks integration with Authorize.Net](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [ACH payment links can streamline collection for small businesses](/blog/maximizing-efficiency-with-ach-payment-links-tips-for-small-businesses/) - [explore how Shuttle can help](/platforms/) - [How to Accept Payments on QuickBooks Invoices (Without Switching Provider)](/guides/quickbooks-invoice-payments/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [GuideWorldpay + QuickBooks Integration: Pay Invoices Through Worldpay→](/guides/quickbooks-worldpay-payments/) - [GuidePayPal + QuickBooks Integration: Add PayPal to QuickBooks Invoices→](/guides/quickbooks-paypal-payments/) - [GuideHow to Accept Payments on QuickBooks Invoices (Without Switching Provider)→](/guides/quickbooks-invoice-payments/) - [GuideHow to Connect QuickBooks Payments to Twilio for Voice & IVR Payments→](/guides/quickbooks-payments-twilio-integration/) - [GuideStripe + QuickBooks Integration: Accept Invoice Payments via Stripe→](/guides/quickbooks-stripe-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-future-of-in-store-payments-why-payment-links-are-here-to-stay/ --- # In-Store Payment Links: The Future of Phygital Payments | Shuttle > Learn how in-store payment links replace POS hardware with QR codes, NFC taps, and SMS checkout. Cut costs, bust queues, and simplify PCI compliance. # In-Store Payment Links: The Future of Phygital Payments By Nick Dunse, August 28, 2023 Learn how in-store payment links replace POS hardware with QR codes, NFC taps, and SMS checkout. Cut costs, bust queues, and simplify PCI compliance. Talk to us Make enabling payments for your platform and merchant users easy. Brick-and-mortar retailers have relied on dedicated POS terminals for decades. But the hardware is expensive, the contracts are rigid, and every additional lane or pop-up location means another terminal to provision, certify, and maintain. In-store payment links offer a different model. Instead of swiping or tapping a card on a terminal, the customer scans a QR code, taps an NFC tag, or receives an SMS -- and completes checkout on a hosted payment page from their own phone. No POS hardware required. Limited PCI scope on the merchant's network. The payment is processed through the same infrastructure that powers online checkout. This guide covers how in-store payment links work, where they outperform traditional POS, and why platforms serving physical retailers should pay attention. ## What Are In-Store Payment Links? A payment link is a URL that opens a hosted checkout page. Online merchants already use them in emails, invoices, and chat conversations. In-store payment links bring the same concept into physical retail by presenting that URL to a customer who is standing in front of you. There are three common delivery methods for in-store payment links: - QR code at the point of sale -- A dynamic QR code is generated for the transaction amount. The customer scans it with their phone camera, which opens the hosted checkout page. They pay with Apple Pay, Google Pay, or enter card details directly. - NFC tap -- An NFC tag or tap-to-pay prompt on a tablet or phone triggers the payment page on the customer's device. This works well for counter service and kiosk environments. - SMS or WhatsApp at the register -- The staff member enters the customer's phone number, and a payment link is sent instantly via text message. The customer pays on their phone without any physical device interaction. In every case, the payment is processed through a PCI-compliant hosted page. The merchant never touches card data. The transaction settles through their existing payment provider, with the same reporting and reconciliation they use for online orders. ## Why Retailers Are Adopting Payment Links In-Store The shift toward in-store payment links is not about replacing every POS terminal overnight. It is about solving specific pain points that traditional hardware cannot address efficiently. Queue busting. During peak hours, long checkout queues cost retailers sales. A staff member with a tablet can generate a payment link for customers waiting in line, letting them pay and leave without reaching the register. No additional POS terminal needed -- just a device that can display a QR code or send a text. No POS hardware dependency. POS terminals cost £300-£1,200 per unit, plus monthly fees, PCI certification costs, and maintenance contracts. Payment links require no hardware beyond what merchants already own -- a phone, tablet, or laptop. This makes them ideal for pop-up shops, market stalls, seasonal locations, and any environment where provisioning a full POS terminal is impractical. Line-item flexibility. Payment links can carry metadata -- order reference, line items, customer ID, tip amounts. This is harder to achieve with a basic card terminal, which only captures an amount. For merchants who need itemised receipts or want to pass order context back to their platform, payment links offer richer data capture than a tap-and-go terminal. Unified online and in-store payments. Many retailers already accept payment links for remote orders, phone orders, and invoicing. Using the same payment link infrastructure in-store means one reconciliation flow, one settlement process, and one set of reports -- regardless of whether the customer was online or in the shop. Platforms that serve both channels benefit from a single integration that handles every scenario. ## How In-Store Payment Links Work The technical flow is straightforward and mirrors online payment link processing: - The merchant's system (POS software, platform dashboard, or staff app) creates a payment link via API, specifying the amount, currency, and any metadata such as order reference or customer ID. - The link is presented to the customer -- as a QR code on screen, an NFC tap prompt, or an SMS/WhatsApp message. - The customer opens the link on their own device. The hosted checkout page loads with the pre-filled amount and any branding configured by the merchant. - The customer pays using Apple Pay, Google Pay, saved card, or manual card entry. 3D Secure authentication runs if required by the card issuer. - The platform receives a webhook confirming payment. The merchant's dashboard updates in real time, and a receipt is sent to the customer. The entire process takes 15-30 seconds from scan to confirmation. Because the checkout page is hosted by the payment provider, the merchant's in-store network never handles card data -- which dramatically simplifies PCI compliance and security. ## In-Store Payment Link Use Cases Payment links are not limited to traditional retail. Any business that collects payments face-to-face can benefit. Retail and high street. Clothing stores, electronics retailers, and department stores use QR-based payment links for queue busting during peak periods. Staff on the shop floor generate links from a tablet, letting customers pay and collect their items without waiting at the till. Hospitality. Restaurants, hotels, and bars use payment links for tableside checkout, room charges, and split bills. A server sends a QR code or SMS link to the table -- the customer pays and tips on their own phone. No card machine changes hands, and the tip is captured digitally rather than in cash. Events and festivals. Pop-up vendors at festivals, trade shows, and markets often lack reliable Wi-Fi for POS terminals. Payment links work over the customer's mobile data connection, so the vendor only needs a printed QR code or a phone to send an SMS. No terminal connectivity issues, no declined taps due to offline mode. Field service. Plumbers, electricians, delivery drivers, and repair technicians collect payments on-site. Instead of carrying a card reader or invoicing later, they send a payment link by SMS before leaving the job. The customer pays immediately, and the platform records the payment against the job automatically. Healthcare and professional services. Clinics, dental practices, and consultancies use payment links to collect co-pays, deposits, or session fees at reception. The patient scans a QR code while checking out, avoiding the need for a dedicated payment terminal at the front desk. ## Phygital Payments: Blending Online and In-Store The term phygital describes the convergence of physical and digital commerce. Customers browse online and buy in-store. They reserve in-app and pick up at the counter. They return in-store items purchased online. Every one of these journeys involves a payment that crosses the online/offline boundary. In-store payment links are a core enabler of phygital commerce because they use the same payment infrastructure for both channels. A customer who pays via payment link in-store and later pays via payment link online has a single payment history, a single refund flow, and a single set of stored credentials. For the platform, this means one integration, one ledger, and one compliance surface. This matters for platforms building multi-channel experiences. Rather than maintaining separate POS integrations (Stripe Terminal, Adyen in-person, Square hardware) alongside their online payment stack, they can route all transactions through payment links -- whether the customer is on a website, in a mobile app, on a phone call, or standing at the counter. ## Payment Links vs Traditional POS Systems Payment links do not replace POS systems in every scenario. High-volume supermarkets processing thousands of transactions per hour still need dedicated hardware. But for many merchants, payment links handle 80% of in-store payment needs at a fraction of the cost. Here is how they compare: Hardware cost. A standard POS terminal costs £300-£1,200 upfront, plus monthly rental or leasing fees. Payment links require no dedicated hardware -- merchants use devices they already own. Setup time. POS terminal provisioning takes days to weeks, including PCI certification, network configuration, and software installation. A payment link integration can be live in hours through an API, with no on-site hardware configuration. Scalability. Adding a new checkout lane or location with POS means ordering, shipping, and configuring another terminal. With payment links, scaling means printing another QR code or giving another staff member access to the link generator. There is no per-location hardware constraint. Transaction speed. Contactless tap on a POS terminal is faster for a single item purchase -- under 3 seconds. Payment links take 15-30 seconds including the QR scan and checkout page load. For complex transactions with line items, tips, or split payments, payment links are often faster because they handle all of that in the hosted page rather than requiring manual terminal input. Maintenance. POS terminals need firmware updates, hardware replacements, and periodic PCI re-certification. Payment links are maintained by the payment provider -- the merchant has no terminal to manage. For platforms that serve merchants across multiple locations -- particularly those in hospitality, field service, or pop-up retail -- payment links dramatically reduce the operational burden of in-person payments. If you are evaluating in-store payment infrastructure, compare what Stripe Terminal and similar POS solutions require against what a payment link API delivers out of the box. ## Cost Comparison: Payment Links vs POS Hardware The cost advantage of in-store payment links becomes clearest when you look at total cost of ownership across a multi-location deployment. Consider a platform serving 50 merchant locations, each needing two checkout points: - POS route: 100 terminals at £500 each = £50,000 upfront. Add monthly fees of £20-£40 per terminal (£24,000-£48,000/year), PCI certification costs per location, shipping and provisioning logistics, and hardware replacement for damaged or outdated units. - Payment link route: One API integration. Per-transaction pricing only -- no hardware costs, no monthly terminal fees, no on-site provisioning. Merchants use existing phones or tablets. QR code stands cost under £10 each if the merchant wants a physical display. Transaction fees for payment links are typically in line with standard card-not-present rates (1.5%-2.9% depending on the provider and card type). POS terminals benefit from lower card-present interchange rates (0.2%-0.3% lower in the UK). For merchants processing high volumes of low-value transactions, the interchange saving on POS may offset hardware costs. For merchants with moderate volume, seasonal spikes, or multiple locations, the payment link model is significantly cheaper. ## Security and PCI Compliance Benefits PCI compliance is one of the strongest arguments for in-store payment links. With a traditional POS setup, the merchant's network handles card data -- which means PCI DSS requirements apply to the in-store network, the terminal, the connection between them, and any systems that store or transmit cardholder data. With payment links, card data never touches the merchant's infrastructure. The customer enters payment details on a hosted page served by the payment provider. The merchant's in-store system only receives a payment confirmation webhook -- no card numbers, no CVVs, no sensitive data. This reduces the merchant's PCI scope from SAQ D (the most comprehensive self-assessment) to SAQ A (the simplest). For platforms, this means their merchants face fewer compliance requirements, lower audit costs, and reduced liability for data breaches. Learn more about how payment links simplify PCI compliance and card authorisation. Additional security benefits include: - 3D Secure authentication runs automatically on the hosted checkout page, reducing fraud and chargeback liability. - Payment links can be set to expire after a defined period, preventing stale links from being reused. - Each link is unique to a transaction, so there is no risk of amount tampering or replay attacks. - No card data is stored on the merchant's local network, eliminating the primary vector for in-store data breaches. ## How Platforms Can Offer In-Store Payment Links If you are a platform serving merchants with physical locations, adding in-store payment links to your product is simpler than integrating POS hardware -- and it gives your merchants a payment method that works across every channel. The integration path looks like this: - Generate payment links via API -- Your platform creates a payment link for each in-store transaction, passing the amount, currency, merchant ID, and any order metadata. - Present to the customer -- Render the link as a QR code on a screen, send it via SMS, or trigger it via NFC. Your merchant-facing app handles the presentation layer. - Handle webhooks -- When the customer pays, your platform receives a webhook with the payment status, transaction ID, and metadata. Update the merchant's order system and trigger any downstream workflows. - White-label the checkout -- The hosted payment page can carry the merchant's branding, so the customer experience is seamless. No redirect to a third-party site. Shuttle's embedded payment infrastructure lets platforms generate white-labelled payment links across any channel -- online, in-store, over the phone, or via chat. One API integration covers every payment scenario your merchants need. Explore how it works for platforms, or book a discovery call to see it in action. ## FAQ: In-Store Payment Links ### Can payment links replace POS terminals completely? For many merchants, yes. Businesses with moderate transaction volumes, pop-up locations, field service operations, or seasonal retail can run entirely on in-store payment links. High-volume environments like supermarkets still benefit from dedicated POS hardware for speed, but even those retailers use payment links for queue busting and supplementary checkout points. ### Are in-store payment links PCI compliant? Yes. Because the customer enters card details on a hosted checkout page operated by the payment provider, the merchant never handles card data. This reduces PCI scope to SAQ A -- the simplest compliance level. The merchant's in-store network only receives payment confirmations, not cardholder data. ### Do customers need to download an app to pay? No. Payment links open in the customer's default mobile browser. They scan a QR code or tap an NFC tag, and the checkout page loads in Safari, Chrome, or whatever browser they use. Apple Pay and Google Pay work natively on the page without any additional app. ### What happens if the customer's phone has no internet? The customer needs a mobile data or Wi-Fi connection to load the hosted checkout page. In practice, most customers have mobile data. For venues with poor signal (underground locations, large warehouses), providing guest Wi-Fi solves this. POS terminals face the same connectivity requirement -- they need a network connection to authorise payments in real time. ### How fast is checkout with an in-store payment link? From QR scan to payment confirmation, the process typically takes 15-30 seconds. This is slower than a contactless tap on a POS terminal (under 3 seconds) but faster for complex transactions involving line items, tips, or split payments. For queue-busting scenarios where customers pay while walking the shop floor, the total time saved is significant because they skip the checkout queue entirely. ## Related Reading Explore More ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [a single integration](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [PCI compliance and security](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [phygital commerce](/blog/phygital-commerce-and-help-of-agentic-solutions/) - [Stripe Terminal and similar POS solutions](/payment-providers/stripe/) - [payment links simplify PCI compliance and card authorisation](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [Explore how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-future-of-payments/ --- # The Future of Platform Payments: From Gateways to Agentic Commerce | Shuttle > For twenty years, payments in software have been treated as a side project.Platforms bolt on a gateway, ship an API, and hope merchants figure it out. # The Future of Platform Payments: From Gateways to Agentic Commerce By Nick Dunse, September 10, 2025 For twenty years, payments in software have been treated as a side project.Platforms bolt on a gateway, ship an API, and hope merchants figure it out. The Problem: Gateways Are Pipes Gateways are pipes: single-channel, single-purpose. They move money, but they don't create experiences. They lock platforms into endless integrations, support nightmares, and lost revenue. Meanwhile, merchants churn. Developers burn months reinventing the wheel. CFOs lose patience. The gateway era is collapsing. The Shift: Commerce Has Changed Commerce is no longer a static checkout at the end of a transaction.It's everywhere: Invoices, links, calls, and chats. Bookings, subscriptions, and workflows. AI agents generating transactions dynamically in real time. The world is moving from e-commerce to agentic commerce -- where payments are created, adapted, and optimised automatically by platforms, workflows, and AI. But gateways can't keep up. They were built for yesterday. The New Category: The Payments Layer What the world needs now isn't another gateway.It's a layer -- a foundation above PSPs and rails that: Unifies access to 40+ PSPs globally. Governs compliance, policy, and routing. Provides ready-made components: links, voice, agentic checkouts. Integrates natively into workflows, platforms, and AI agents. This is The Payments Layer:The infrastructure that lets platforms, merchants, and AI agents build payment experiences instantly and compliantly. The easy on ramp: Link Checkout Every new category needs an obvious first proof. For us, it's Link Checkout.The simplest way for a platform to give its merchants modern payments -- no code, no integration debt, live in days. But Link Checkout is just the beginning.Voice checkouts, AI-generated payment links, automated invoice flows -- all are natural extensions of The Payments Layer. The Enemy: The Old Way Gateways are pipes. Orchestration is narrow. Marketplaces confuse. All of them keep platforms in the plumbing business instead of letting them own the payments experience. The enemy is integration debt, churn, and lost revenue. The Call: Build on The Payments Layer Platforms that cling to the gateway model will lose merchants to competitors who can deliver instant, global, agentic payments. Platforms that embrace The Payments Layer will own the future: Faster onboarding. More revenue per merchant. Payments that adapt to any channel, any workflow, any AI. This is the moment.The shift from Gateways to Agentic Commerce is underway. And Shuttle is leading it. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-future-of-subscriptions/ --- # The future of subscriptions with Chargebee and GoCardless | Shuttle > Nick hosted a discussion with Chargebee and GoCardless via SaaStock Local. # The future of subscriptions with Chargebee and GoCardless By Nick Dunse, May 23, 2024 Nick hosted a discussion with Chargebee and GoCardless via SaaStock Local. ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-future-of-voice-commerce/ --- # The Future of Voice Commerce: From IVR to Intelligent Payments | Shuttle > Twenty years ago, voice was the channel of human connection. Call centres were the heartbeat of customer experience. AI agents are replacing scripts. # The Future of Voice Commerce: From IVR to Intelligent Payments By Nick Dunse, October 17, 2025 Twenty years ago, voice was the channel of human connection. Call centres were the heartbeat of customer experience. AI agents are replacing scripts. Twenty years ago, voice was the channel of human connection. Call centres were the heartbeat of customer experience. And IVR -- the interactive voice response system -- was the workhorse that scaled it. Today, voice is being reborn. Not as a clunky keypad experience, but as an intelligent, data-driven interface. AI agents are replacing scripts. Conversations are becoming contextual. Yet one piece of the journey still feels oddly stuck in time: the payment. The Payment That Time Forgot Think about the moment that matters most -- when a customer says, "I'll pay now." In most IVR systems, that moment still triggers a mess of legacy processes: - Agents read card numbers aloud. - Systems transfer callers to third-party portals. - Compliance hoops slow everything down. For the customer, it's friction. For the business, it's risk. For the brand, it's a missed opportunity to make the payment feel as effortless as the conversation. That's why a new era is emerging -- one where voice itself becomes a payment channel. From IVR to Intelligent Payment Journeys Intelligent voice commerce is not about replacing the human. It's about completing the moment. Imagine a customer calling about an overdue balance. The IVR identifies the caller, validates the account, and -- without transferring or reading numbers -- securely takes payment there and then. No agent intervention. No compliance risk. No loss of momentum. That's the future Shuttle is powering -- turning every voice interaction into a revenue moment. Voice as a Payment Layer At the heart of this shift is the Payment Layer -- a connective layer that sits above gateways and processors, abstracting away complexity. Rather than hard-coding payment logic into every IVR or AI workflow, the Payment Layer handles: - PCI-compliant tokenisation - Multi-processor routing - Multi-merchant management - Fallback channels (voice → link checkout) It's voice-native, processor-agnostic, and built to fit into your existing stack -- especially if you're already using Twilio. The Rise of Agentic Commerce Voice payments are not just a compliance feature. They're the foundation of something much bigger: agentic commerce -- where conversational agents, IVRs, and AI systems can autonomously initiate, authorise, and complete payments. In this new world: - Every "Pay Now" moment is automated. - Every channel (voice, chat, or link) shares one payment logic. - Every merchant or brand operates consistently, regardless of processor. This isn't the future of IVR -- it's the next generation of commerce infrastructure. Twilio and the New Voice Stack For businesses building on Twilio, this evolution is already within reach. Shuttle connects directly into Twilio's programmable voice stack, enabling: - Secure DTMF capture for IVR payments - Automated voice-to-pay workflows - Instant fallback to Shuttle Payment Links for SMS or chat It's the fastest way to turn your contact centre into a payment centre -- without rebuilding your compliance or integration stack. From Call Centre to Revenue Centre BPOs, insurers, and utilities have long viewed contact centres as cost lines. Voice payments flip that model. Now, every call can become a checkout. Every "resolved query" can become a transaction. Every conversation can become cash flow. That's the power of connecting voice and payments through a single programmable layer. A Simpler Future for Voice Commerce IVR systems were built to direct calls. Now they can direct cashflow. By embedding payments directly into your voice flows, you remove friction, risk, and delay -- the three forces that quietly kill conversion. Voice commerce isn't a trend; it's a return to what made voice powerful in the first place: immediacy, trust, and action. Explore Shuttle's Voice Payment Layer If you're building contact-centre or voice-automation experiences, you don't need a new gateway -- you need a Payment Layer. A layer that connects your existing processors, automates compliance, and gives you programmable control across voice, chat, and links. Learn more about Shuttle's IVR & Voice Payments here. ## Related Reading Explore More ### HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) ### How Voice AI Ordering Platforms Handle Payments -- And Why It's Broken ### Agentic Commerce: Payment Infrastructure for AI Agents ### What Are Voice Payments? The Complete Guide ### How AI Voice Agents Take PCI-Compliant Payments ### AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [DTMF capture](/guides/dtmf-payments/) - [Learn more about Shuttle's IVR & Voice Payments here](/platforms/voice-checkout/) - [GuideHubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)→](/guides/hubspot-commerce-hub-transaction-fees/) - [GuideHow Voice AI Ordering Platforms Handle Payments -- And Why It's Broken→](/guides/voice-ai-ordering-payments/) - [GuideAgentic Commerce: Payment Infrastructure for AI Agents→](/guides/agentic-commerce/) - [GuideWhat Are Voice Payments? The Complete Guide→](/guides/voice-payments/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [GuideAI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk→](/guides/ai-voice-payments-insurance/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-missing-piece-in-modern-bpo-automating-the-payment-moment/ --- # The Missing Piece in Modern BPO: Automating the Payment Moment | Shuttle > BPOs have automated conversations but not payments. Discover how payment automation closes the loop, reduces handle time, and improves collection rates. # The Missing Piece in Modern BPO: Automating the Payment Moment By Nick Dunse, February 11, 2026 BPOs have automated conversations but not payments. Discover how payment automation closes the loop, reduces handle time, and improves collection rates. You've automated the conversation. Now it's time to automate the payment. Discover how leading BPOs use Shuttle to turn every "I'll pay now" into instant revenue. You've Automated the Conversation. Now It's Time to Automate the Payment. Leading BPOs are using Shuttle to turn every "I'll pay now" into revenue -- instantly.👉 Explore Shuttle Payment Links ### 1. The Conversation Revolution Twenty years ago, BPOs won the customer-experience game by industrialising the conversation.They built the contact centres, chatbots, and offshore teams that kept the world talking -- and listening. Today, those same BPOs are reinventing themselves again. Voice is turning digital. Chatbots are becoming human. Conversations are becoming data. Yet one part of the experience still feels oddly manual: the payment. ### 2. The Moment That Matters Most Every BPO leader knows this scene.A customer is on the line, problem solved, ready to pay.The agent smiles -- and then everything slows down. "Let me just open another screen.""Can I read your card details?""Sorry, I'll send you a separate link." Momentum dies. Trust erodes. The customer disappears into a maze of forms and systems that don't talk to each other. In that single moment, the conversation stops being intelligent. It becomes inconvenient. That's where revenue is lost -- not because the customer won't pay, but because the system can't keep up. ### 3. Why Payments Got Left Behind In the rush to digitise everything from voice to analytics, payments became an afterthought. Every client had their own PSP. Every PSP had their own API.Compliance rules grew. PCI-DSS hardened. And so, payments were left to IT projects -- long, fragile, and expensive. The irony?BPOs already handle some of the most sensitive customer interactions on earth.Yet to process a simple £100 payment, they often need to hand the customer off to a third-party portal, breaking continuity and trust. ### 4. The Category Shift: From Gateways to Layers The payment landscape has evolved -- but unevenly.Gateways gave us pipes. PSPs gave us options.But what BPOs really need is connection -- a way to make payments feel like a natural part of the interaction, not an obstacle to it. That's what Shuttle calls the Payment Layer. Not another gateway. Not a PSP.A connective layer that sits between your CX systems and any payment provider -- so your agents, bots, or workflows can collect money instantly and securely, without ever leaving the conversation. 💡 See Shuttle Payment Links in action:https://www.shuttleglobal.com/payment-links ### 5. How Shuttle Works Imagine this:Your agent in AWS Connect finishes a call and clicks "Send payment link."In seconds, a branded checkout appears on the customer's phone. They pay.The transaction posts back into your client's CRM automatically. No coding. Limited PCI scope. No human error. That's Shuttle in motion -- the invisible infrastructure that makes payments seamless across voice, chat, and AI. ### 6. The BPO Use Cases Voice Collections Agents send payment links directly from the call interface -- no redirects, no shared credentials.Ideal for service desks, utilities, insurance claims, and debt recovery. Chatbot Conversions AI agents don't need to stop at support.Shuttle turns them into revenue engines by embedding secure links within the chat flow. ## Client On-Boarding & Billing Spin up a new client instance in minutes.Each has its own logo, domain, and PSP -- fully isolated yet managed through one Shuttle dashboard. ### 7. Security Without Friction BPOs live under constant compliance scrutiny.Shuttle is PCI-DSS Level 1 certified -- meaning card data never touches your environment. We handle the sensitive part, so you can focus on the experience. And for your clients, that means every payment looks and feels like their brand -- not a third-party redirection. ### 8. Proof in Practice Leading BPOs and AI-workflow builders use Shuttle to automate their payment moments. One BPO migrated from a legacy stack to Shuttle's Twilio Pay Connector and Payment Links, enabling agents to collect securely within conversations for some of the biggest brands in the world. Where once it took months to deploy a new payment flow, Shuttle cut that down to days.Where reconciliation once meant spreadsheets, it now happens automatically. Speed. Security. Simplicity.That's the Shuttle difference. ### 9. The Economic Impact Let's be clear: the goal isn't just convenience -- it's conversion.Every failed or delayed payment is a missed opportunity for your clients. By embedding Shuttle, BPOs can: Reduce time-to-collection by up to 60 % Eliminate manual reconciliation Decrease PCI scope and compliance costs Offer clients new, branded revenue channels In competitive tenders, that capability becomes a differentiator -- not a feature. ### 10. From Contact to Contract BPOs are evolving from "outsourced service providers" into experience partners.That shift requires more than automation -- it requires intimacy. Shuttle gives you that: the power to close the loop inside the same conversation. From first contact to final contract, the experience stays connected, branded, and seamless. ### 11. The Future: Agentic Payments AI is already transforming BPO operations.Soon, bots won't just talk -- they'll transact. The next frontier is agentic payments -- workflows where AI agents can decide, trigger, and reconcile payments automatically within compliance boundaries. Shuttle is building that future now:A Payment Layer that allows AI agents to act as financial participants, safely and instantly. ### 12. The New Standard for BPO Payments You've automated conversations.Now, automate the payment. With Shuttle, you can unify every channel, client, and PSP under one Payment Layer.Collect instantly, reconcile automatically, and deliver the payment experience your clients didn't know was possible. BPOs have mastered communication.Now it's time to master conversion. 🚀 Ready to automate your payment moments?Discover how Shuttle Payment Links help BPOs collect instantly across voice, chat, and AI. You've automated the conversation.Shuttle automates the payment. ## Related Reading Explore More ### Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [Explore Shuttle Payment Links](/platforms/links-checkout/) - [GuidePayment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope→](/guides/payment-collection-for-bpos/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-australia/ --- # Payment Methods in Australia: Cards, PayPal & Afterpay (2026) | Shuttle > Explore Australia's most popular payment methods from credit and debit cards to PayPal, Afterpay, Apple Pay, and BPAY for online and in-store commerce. # Payment Methods in Australia: Cards, PayPal & Afterpay (2026) By Nick Dunse, February 11, 2026 Explore Australia's most popular payment methods from credit and debit cards to PayPal, Afterpay, Apple Pay, and BPAY for online and in-store commerce. Start collecting payments today Send payment links to your customers in Australia -- no card machine, no website, no fuss. The Australian online shopping landscape is characterized by a strong inclination towards international brands and products, driving the prominence of cross-border e-Commerce. Consumers frequently opt for overseas retailers, attracted by a broader product range and competitive pricing, particularly in categories such as fashion, electronics, beauty, and health products. The surge in mobile commerce is notable, with a growing number of Australians using smartphones and tablets for online purchases, leading to a substantial share of e-Commerce sales. Retailers are adapting to this trend by investing in mobile-friendly websites and apps. Social media platforms, including Facebook, Instagram, and Pinterest, serve as significant marketing channels, with influencers playing a key role in product promotion. Australia's well-established logistics infrastructure facilitates efficient e-Commerce operations, supported by major providers offering fast and reliable shipping services, including same-day or next-day delivery in major cities. Overall, the tech-savvy population, high internet penetration, and a preference for global brands make the Australian e-Commerce market an attractive prospect for businesses seeking to expand their online presence. ## Popular offline payment methods in Australia ### Cash ### Debit Cards ### Mobile Payments Electronic Funds Transfer at Point of Sale (EFTPOS) ### Cheques ### BPAY ### Direct Bank Transfers ## List of payment methods in Australia ### Mastercard Mastercard is extensively embraced as a versatile payment method, accepted by a wide range of businesses such as supermarkets, restaurants, hotels, and retail stores, both for in-store and online transactions, as well as cash withdrawals from ATMs. Users can simply present their Mastercard to merchants or input card details for online purchases, with some vendors also accommodating contactless payments via Mastercard-enabled devices. The payment system incorporates robust security measures, including EMV chip technology and tokenization, and offers zero liability protection against unauthorized transactions. Despite its widespread acceptance, it's advisable to carry cash for backup, as certain smaller establishments in Australia may solely accept cash or have limited payment alternatives. ### EFTPOS EFTPOS (Electronic Funds Transfer at Point of Sale) is a prevalent payment system in Australia, enabling customers to electronically pay for purchases directly from their bank accounts at the point of sale. To utilize EFTPOS, individuals require a debit card issued by an Australian bank or financial institution. During a transaction, customers can choose the EFTPOS option at the payment terminal, input their PIN, and authorize the transfer of funds from their bank account to the merchant's account. Widely accepted across various businesses, including retail stores, supermarkets, and restaurants, EFTPOS provides a secure and convenient alternative to cash or checks. Its versatility extends to online transactions, allowing users to select the EFTPOS option during checkout and input the necessary card details. Overall, EFTPOS stands as a popular and trusted payment method in Australia, catering to the needs of both customers and merchants by offering a reliable and secure financial transaction solution. Visa stands out as a highly prevalent and favored payment method, widely acknowledged for its widespread acceptance and convenience. It is among the most commonly utilized payment cards in the country, with applications spanning online shopping, in-store transactions, and bill payments. The versatility of Visa cards is evident in their acceptance at various establishments, including supermarkets, restaurants, hotels, and retail stores, while also enabling cash withdrawals from ATMs nationwide. Australians not only rely on physical Visa cards but also frequently utilize virtual Visa cards for secure online transactions, seamlessly linked to their Visa accounts. With a diverse range of card options such as credit cards, debit cards, and prepaid cards, Visa provides consumers with the flexibility to choose a card tailored to their specific preferences and requirements. Overall, Visa emerges as a widely embraced and user-friendly payment solution in Australia, facilitating convenient purchases across both online and offline platforms. ### PayPal PayPal is a widely accepted payment method in Australia, providing users with a secure and convenient way to make online payments. It is commonly used for purchases on various online platforms, including e-commerce websites, online marketplaces, and select brick-and-mortar stores accepting mobile payments. To utilize PayPal in Australia, users must create an account and link it to their bank account or credit card. Once set up, PayPal can be selected as a payment option during checkout. Notably, PayPal offers buyer protection, granting users the possibility of a refund in case of issues like non-receipt or damaged items, enhancing the overall security of transactions. Beyond purchases, PayPal facilitates money transfers between friends and family, serving practical purposes such as bill splitting or sending gifts. In summary, PayPal is a widely trusted and popular payment method in Australia, known for its convenience and security in online transactions. ### American Express American Express is widely embraced as a payment method throughout Australia, finding acceptance at major retailers, restaurants, hotels, and online merchants across the country. Cardholders can conveniently use their American Express cards for in-store, online, and phone transactions. Beyond its widespread acceptance, American Express provides a range of benefits and rewards to its Australian cardholders, such as travel insurance, purchase protection, airport lounge access, and rewards programs. Despite its popularity, it's essential to be aware that certain smaller merchants or businesses may choose not to accept American Express due to higher transaction fees. Therefore, it is advisable to confirm acceptance with merchants beforehand. In summary, American Express stands as a popular and extensively accepted payment option in Australia, offering both convenience and perks to its users. Afterpay and Clearpay are prominent buy now, pay later (BNPL) services, originating from Australia and providing a convenient method for customers to shop by allowing them to split payments into four installments. Founded in 2014, Afterpay has gained global prominence, permitting customers to make the first payment at the time of purchase and subsequent ones every two weeks, without interest or fees if payments are punctual. Clearpay, established in 2019 and owned by Afterpay, follows a similar model. Both services are widely accepted in online and physical stores, offering consumers the option to choose them as payment methods during checkout. The Afterpay and Clearpay apps facilitate managing payments, enabling users to monitor schedules and submit payments. Despite their popularity for providing financial flexibility, customers must be vigilant about meeting repayment obligations to avoid potential late fees and adverse effects on their credit scores. ### Apple Pay Apple Pay enables iPhone and Apple Watch users to make contactless payments through major banks such as ANZ, Commonwealth Bank, Westpac, NAB, and various smaller banks and credit unions. To utilize the service, users must add their eligible debit or credit cards to the Wallet app, subsequently making payments by holding their device near a contactless terminal and confirming the transaction through Touch ID or Face ID. With widespread acceptance, Apple Pay is usable at various retailers, including supermarkets, department stores, restaurants, and cafes, both in-store and online. Beyond payments, the platform allows users to store loyalty cards and boarding passes for easy access. The popularity of Apple Pay in Australia stems from its convenience and robust security features, offering a swift and secure payment method for a range of transactions. ### Zip Zip is a widely-used payment method in Australia, offering customers the flexibility to buy items immediately and pay for them later through interest-free installments, akin to services like Afterpay and Klarna. To utilize Zip, customers must establish an account, linking it to their debit or credit card, and can then employ it at participating online and physical stores. At the point of purchase, customers can opt for Zip and select their preferred installment plan, which includes interest-free options over typically 4 or 8 weeks, or extended plans with interest. After completing a purchase with Zip, customers receive an invoice detailing their installment plan and can manage payments through the Zip app or website, tracking spending and viewing upcoming payments. Additionally, Zip provides a digital wallet feature known as Zip Pay, enabling users to make purchases up to a specified credit limit without card linkage, catering particularly to younger consumers without credit cards. Overall, Zip offers a convenient and adaptable payment solution for Australian consumers, facilitating the spreading of purchase costs over time without incurring interest charges. ### JCB JCB, or Japan Credit Bureau, serves as a popular payment method in Australia, finding broad acceptance among merchants and retailers, particularly those catering to international clientele. JCB cards are versatile, usable for both online and offline transactions throughout the country, including at various physical retail locations such as restaurants, hotels, department stores, and tourist attractions. This widespread acceptance facilitates the convenience of everyday purchases and activities for JCB cardholders visiting Australia. To utilize a JCB card, customers can simply present it at the point of sale or input card details for online transactions, with the transaction processed through the JCB network and the corresponding amount deducted from the cardholder's account. While JCB may not be as commonly used as other methods like Visa or Mastercard, its broad acceptance makes it a secure and convenient payment option for both local and international customers in Australia, though users are advised to check with merchants beforehand to ensure JCB acceptance. ### Alipay Alipay, a widely used mobile payment platform in China, has expanded its presence to Australia through partnerships with local retailers and businesses. The platform enables Chinese tourists and residents in Australia to make convenient payments for various purposes such as shopping, dining, transportation, and accommodation. With acceptance in popular tourist destinations like Sydney, Melbourne, and Gold Coast, Alipay has become a preferred payment method for many establishments. To utilize Alipay in Australia, users must have an account linked to their bank or credit card, allowing them to make payments by scanning merchant-provided QR codes with the Alipay app on their mobile phones. This integration provides Chinese visitors with the convenience of making transactions in their preferred currency, eliminating the need for cash or credit cards. For Chinese residents in Australia, Alipay offers a familiar and secure payment option. Overall, Alipay's adoption in Australia enhances the ease of financial transactions for both Chinese tourists and residents in the country. ### UnionPay UnionPay is a widely accepted payment method in Australia. It is accepted at most major retailers, hotels, restaurants, and online merchants. UnionPay cards can be used for both in-store and online purchases. ### Klarna Klarna has gained popularity in Australia as a widely-used payment method, offering customers the flexibility to make purchases and defer payments. This service allows users to buy now and pay later, with options such as interest-free installment plans and the ability to split payments into four equal parts. To utilize Klarna, customers can choose it at the checkout of participating online stores, redirecting them to the Klarna website for completion. At this point, customers can opt to pay in full or select from Klarna's installment choices. The convenience extends to a dedicated mobile app that enables users to manage payments, track purchases, and receive notifications and reminders about upcoming payments, enhancing financial control for Australian customers. Overall, Klarna provides a convenient and adaptable payment solution, allowing users to make purchases without the immediate burden of full payment. ### WeChat Pay WeChat Pay, a widely used mobile payment method in China, is gaining traction in Australia, finding acceptance at various establishments, including retail stores, restaurants, hotels, and online platforms. To utilize WeChat Pay in Australia, users must link their Australian bank accounts or credit cards to their WeChat app, enabling them to make secure and convenient payments through QR code scanning or by providing their WeChat ID. This payment option not only eliminates the need for physical cards or cash but also provides users with additional perks such as discounts and promotions at participating merchants. Particularly popular among Chinese tourists and residents familiar with the app, WeChat Pay is contributing to the transformation of payment experiences in Australia, offering both users and businesses increased convenience and opportunities for engagement. ### Diners Club Diners Club is a highly accepted payment method in Australia, widely used across numerous restaurants, hotels, and retail outlets, including major establishments like Coles, Woolworths, Myer, and David Jones. The flexibility of Diners Club extends to both in-person and online transactions, allowing customers to easily present their card at the point of sale or input details for online purchases. In addition to its widespread acceptance, Diners Club offers various benefits to cardholders in Australia, such as exclusive offers and discounts at partner merchants. The cards often include travel insurance and other perks, catering to the needs of frequent travelers. Overall, Diners Club stands out as a convenient and popular payment choice for both locals and tourists in Australia. ### Google Pay Google Pay is a payment platform available in Australia, enabling users to make transactions with their Android devices, including smartphones and smartwatches, at participating merchants. Users can add their credit or debit cards to the Google Pay app and utilize it for contactless payments both in-store and online. To use Google Pay, a compatible Android device with NFC capabilities is required, and users must download the app from the Google Play Store, adding their payment cards during setup. Once configured, users can make payments by unlocking their device and holding it near a contactless terminal, securely transmitting payment information. Google Pay also supports additional features like loyalty card integration and peer-to-peer payments, enhancing its convenience and security for users in Australia. ### Discover Discover is a credit card brand that is widely accepted as a mode of payment in Australia. It is accepted at most major retailers, restaurants, and online merchants in the country. Discover cards can be used for both in-person and online transactions, making it a convenient payment option for Australians. Additionally, Discover offers various rewards and benefits to cardholders, such as cashback on purchases and travel perks. Overall, Discover is a popular choice for those looking for a reliable and widely accepted credit card in Australia. PaySafeCard is a popular prepaid payment solution in Australia, offering users a convenient way to make online purchases without the need for a credit card or bank account. Available for purchase at various retail locations like convenience stores and supermarkets, the card comes with a unique 16-digit PIN code used for online transactions. Users can deduct the purchase amount from the card's balance by selecting PaySafeCard as the payment method. If the balance is insufficient, multiple cards can be combined. Widely accepted across online platforms, including gaming, e-commerce, and digital services, PaySafeCard ensures secure transactions without sharing personal or financial information. While it provides an alternative for those without traditional banking access, users should be aware of associated fees, such as those for currency conversion or refunds, by reviewing the terms and conditions beforehand. Overall, PaySafeCard serves as a secure and practical payment option in Australia. ### Samsung Pay Samsung Pay is a mobile payment service available in Australia, enabling users to make payments with their Samsung devices at any merchant accepting contactless payments. To use the service, users add their credit or debit card information to the Samsung Pay app, facilitating easy payments by holding their device near a contactless terminal. The technology employed, Magnetic Secure Transmission (MST), allows compatibility with both contactless and traditional magnetic stripe terminals, making it versatile across various merchants. Samsung Pay also incorporates features like loyalty card integration, gift card storage, transaction history access, and card management within the app, providing users with a convenient and secure payment solution in Australia. ## Accepting International Card Payments in Australia Whether you sell to customers in Australia from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Card payments are universal in Australia but PayID, BPAY, and Afterpay are now standard checkout expectations. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Australia, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Australia as a Platform For software platforms serving merchants in Australia, supporting local payment methods like BPAY, PayTo, and domestic card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Australia? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-brazil/ --- # Brazil Payment Methods: Top 8 Ways Brazilians Pay (2026) | Shuttle > How do Brazilians pay online? From Pix (used by 150M+) to Boleto and installment cards -- here are the payment methods you need to accept in Brazil. # Brazil Payment Methods: Top 8 Ways Brazilians Pay (2026) By Nick Dunse, January 16, 2023 How do Brazilians pay online? From Pix (used by 150M+) to Boleto and installment cards -- here are the payment methods you need to accept in Brazil. Start collecting payments today Send payment links to your customers in Brazil -- no card machine, no website, no fuss. In Brazil, a diverse range of payment methods, including local options like Boleto Bancario and SafetyPay, alongside international methods such as credit cards and digital wallets (PayPal, Apple Pay, Google Pay), are widely used in e-commerce. Businesses must provide multiple payment choices to accommodate various customer preferences. Ensuring the security and reliability of payment systems is crucial, involving measures like secure gateways, two-factor authentication, and vigilant monitoring for fraud prevention. Despite the promising opportunities in Brazil's e-commerce market, understanding and adapting to local payment preferences are essential for success. ## Popular offline payment methods in Brazil ### Boleto Bancario ### Bank Transfers ### Cash ### Debit Cards ### Carne ### Cheques ### Mobile Payments ## List of payment methods in Brazil ### Mastercard Mastercard is extensively used for payments in Brazil, both online and in-person at various establishments such as retail stores, restaurants, and hotels. Online transactions require entering card details, while in-person payments can be made by presenting the card or using contactless methods. Mastercard in Brazil provides benefits like cashback, discounts, and travel insurance, but specific perks vary by issuer. While widely accepted, some smaller businesses in Brazil may prefer cash, so it's advisable to carry some as a backup when traveling. ### Visa Visa is a highly popular and widely accepted payment method, both online and offline. It is commonly used in various establishments such as supermarkets, restaurants, hotels, and retail stores. Visa offers contactless payment options, enhancing convenience. Besides physical cards, virtual cards are available for added security during online transactions, allowing easy cancellation or replacement if needed. Visa also provides cardholders in Brazil with benefits and rewards, including cashback, airline miles, and discounts at partner merchants. Overall, Visa is a convenient and versatile payment option, catering to the needs of both residents and visitors in Brazil. ### PIX PIX is a recently introduced instant payment system by the Central Bank of Brazil, enabling 24/7 instant payments using various identifiers like phone numbers, email addresses, or QR codes. Users register their bank accounts with their financial institutions, linking them to a unique identifier. To make a payment, users provide the recipient's identifier or scan their QR code, confirming and authorizing the transaction. PIX is versatile, catering to person-to-person payments, online purchases, bill payments, and interbank transfers. It offers speed, security, and convenience compared to traditional methods, gaining widespread adoption since its November 2020 launch. Businesses and the government incentivize PIX usage, further boosting its popularity and reshaping Brazil's payment landscape. ### Maestro Maestro is a popular payment method in Brazil, functioning as a debit card issued by various banks for both online and offline transactions. To use it online, you select Maestro at checkout, enter card details, and proceed with payment. For offline transactions, you swipe or insert the card at the point of sale, possibly entering a PIN for authorization. Maestro cards are linked to a bank account, ensuring direct fund deduction, adding to its convenience and security in Brazil. However, its international acceptance is not as widespread as Visa or Mastercard, so checking with merchants beforehand is advisable when using it abroad. ### Elo Elo is a prominent payment method in Brazil, established in 2011 by major banks like Banco do Brasil, Bradesco, and Caixa Econômica Federal. It includes credit, debit, and prepaid cards accepted widely across the country for various transactions, both online and offline. Elo has expanded its reach through partnerships with international networks like Discover, enabling its cards to be used globally. With its convenience and security, Elo has become a popular choice for Brazilians, serving as a versatile payment option for domestic and international use. Boleto Bancário, commonly known as boleto, is a widely used payment method in Brazil. It functions as a payment slip, enabling consumers to make purchases or settle bills without requiring a bank account or credit card. Upon selecting boleto at the checkout, a unique slip is generated with a barcode and necessary details. Payment can be made at various locations, including banks, post offices, and online through internet or mobile banking. While offering accessibility to those without traditional banking services, boleto's main drawbacks include a processing delay of one to three days and an expiration date, necessitating timely payments. Despite these limitations, boleto remains popular in Brazil for its inclusivity and added security by not requiring sensitive financial information during transactions. ### Hipercard Hipercard is a well-established credit card brand in Brazil, originating in 1969 and widely accepted by merchants throughout the country. Renowned for its lower interest rates compared to other Brazilian credit cards, it appeals to consumers seeking to avoid high interest fees. Hipercard provides additional perks such as cashback on purchases, discounts at partner stores, and exclusive promotions through its rewards programs. To obtain and use Hipercard, customers must apply through participating banks, receive a physical card, and can also opt for a virtual card for online transactions. The card's popularity in Brazil can be attributed to its advantageous financial terms, rewards, and broad acceptance. ### American Express American Express is accepted as a payment method in Brazil. It is one of the major credit card companies in the country and is widely accepted at various merchants, including restaurants, hotels, and retail stores. American Express cardholders can use their cards to make purchases and payments at these establishments, both online and offline. Additionally, American Express offers various benefits and rewards programs for its cardholders in Brazil. ### Apple Pay Apple Pay has been introduced as a payment option in Brazil, enabling iPhone, Apple Watch, iPad, and Mac users to make secure and convenient payments. To use Apple Pay, users in Brazil can add their credit or debit cards to the Wallet app on their device and make payments by holding the device near a contactless terminal. The platform employs tokenization technology to enhance security by replacing card numbers with unique tokens, reducing the risk of fraud. Apple Pay is widely accepted at various merchants in Brazil, including supermarkets and restaurants, and can also be used for online purchases within apps and websites. Additionally, users can digitally store and access loyalty cards and boarding passes through Apple Pay, offering a convenient and secure payment experience. ### Google Pay Google Pay is a digital wallet and online payment system developed by Google, available in Brazil. Users can make payments using their NFC-enabled mobile devices by installing the Google Pay app and adding their credit or debit card information. The service supports various payment scenarios, including in-store and online purchases, peer-to-peer payments, and public transportation payments. Google Pay aims to provide a convenient and secure alternative to traditional payment methods, simplifying the payment process for users in Brazil. Diners Club International operates as a global payment network, providing credit cards to consumers and businesses worldwide. In Brazil, these cards, issued by Banco do Brasil, are widely accepted in various establishments like restaurants, hotels, and retail stores. Diners Club cards in Brazil come with benefits such as cashback, travel insurance, and airport lounge access. Payments can be made physically by presenting the card, swiping, or inserting it into a reader, with some places accepting contactless payments. Additionally, virtual payment solutions enable online purchases using Diners Club card details. Overall, Diners Club is a popular and convenient payment method in Brazil, ensuring security for both consumers and businesses. ### Discover Discover is not widely accepted as a payment method, with credit cards (Visa, Mastercard, American Express), debit cards, and cash being more commonly used. While some establishments may accept Discover, it is not as prevalent as other card brands. Apple Pay, a mobile payment service by Apple, is currently not available in Brazil, although there have been rumors about its potential launch. Other mobile payment services like Samsung Pay and Google Pay are available in the country. The timeline for Apple Pay's potential introduction in Brazil remains uncertain, but considering the popularity of mobile payments and smartphone adoption, there is a possibility of its expansion in the future. ### Meal vouchers Meal vouchers, also known as vale-refeição or ticket alimentação in Brazil, are widely used by employers to offer meal benefits to their employees. These vouchers, issued by specialized companies, can be redeemed at various establishments, including restaurants, cafeterias, and grocery stores. Provided as part of the employee benefits package, the voucher value is determined by the employer and issued monthly. Accepted at a range of establishments, employees can use them for food and non-alcoholic beverages. The process involves presenting the voucher at the time of payment, with any excess beyond the voucher value covered by other payment methods. In Brazil, meal vouchers are tax-exempt, making them an attractive and efficient option for both employers and employees. Overall, they serve as a convenient and popular means of facilitating access to meals for employees while providing tax benefits for employers in Brazil. ### PayPal PayPal is a widely used online payment platform enabling secure transactions globally, including in Brazil. Users in Brazil can create a PayPal account, link it to their bank account or credit card, and use it for online purchases. During a transaction, users select PayPal as the payment option, log in, confirm the payment on the PayPal website, and funds are transferred to the merchant. PayPal provides buyer protection for dispute resolution in case of issues with purchases. Beyond online shopping, PayPal facilitates money transfers between individuals using email addresses or mobile numbers associated with their accounts, offering a convenient and secure payment method in Brazil. ## Accepting International Card Payments in Brazil Whether you sell to customers in Brazil from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Pix has overtaken cards as the dominant payment method in Brazil, with Boleto Bancário still essential for higher-value transactions. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Brazil, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Brazil as a Platform For software platforms serving merchants in Brazil, supporting local payment methods like Pix, Boleto Bancário, and domestic card networks like Elo is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Brazil? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-canada/ --- # Payment Methods in Canada: Credit Cards, Interac, PayPal & More (2026) | Shuttle > Explore Canada's most popular payment methods including credit cards, Interac debit, PayPal, Apple Pay, and e-transfers for online and in-store commerce. # Payment Methods in Canada: Credit Cards, Interac, PayPal & More (2026) By Nick Dunse, September 27, 2020 Explore Canada's most popular payment methods including credit cards, Interac debit, PayPal, Apple Pay, and e-transfers for online and in-store commerce. Start collecting payments today Send payment links to your customers in Canada -- no card machine, no website, no fuss. In Canada, alongside traditional card payments, alternative methods such as PayPal and Amazon Pay are prevalent, providing online shoppers with convenient and secure transaction options. The adoption of mobile payments is on the rise, with services like Apple Pay and Google Pay widely accepted by merchants, streamlining the checkout process through smartphone transactions. To meet customer preferences and enhance sales potential, businesses in Canada must diversify their payment options, encompassing major credit cards, debit cards, and popular alternative methods. This comprehensive approach ensures adaptability to varying customer needs, fostering a broader customer base and maximizing sales opportunities for businesses in the Canadian market. ## Popular offline payment methods in Canada ### Cash ### Debit Cards ### Cheques ### Money Orders ### Bank Transfers ### Mobile Wallets ### Interac e-Transfers ## List of payment methods in Canada ### Visa Visa is widely accepted as a payment method in Canada. It is one of the most popular and commonly used credit card brands in the country. Visa cards can be used at a wide range of merchants, including retail stores, restaurants, online retailers, and more. Additionally, many banks and financial institutions in Canada offer Visa credit cards to their customers. Visa also offers contactless payment options, such as Visa payWave, which allows users to make quick and easy payments by simply tapping their card or mobile device on a contactless payment terminal. Overall, Visa is a convenient and widely accepted payment method for Canadians. ### Interac Interac is a widely utilized payment method in Canada, functioning as a secure and convenient platform for electronic transactions. The network links financial institutions across the country, facilitating the transfer of funds. Interac offers various payment options, including Interac Debit, allowing direct purchases from bank accounts; Interac e-Transfer, enabling money transfers via email or mobile numbers; Interac Flash, allowing contactless payments through card or mobile taps; and Interac Online, facilitating secure online purchases directly from bank accounts. Accepted at numerous retail and online establishments, Interac is supported by major banks and institutions in Canada, providing users with encrypted transactions for heightened security. In essence, Interac plays a crucial role in offering Canadians a secure and convenient means of payment for both in-store and online transactions. ### Mastercard Mastercard is a highly accepted payment method in Canada, with widespread usability at various retailers, encompassing both online and in-store transactions nationwide. It finds acceptance in major grocery stores, department stores, restaurants, gas stations, and numerous other businesses. Beyond traditional card payments, Mastercard offers the convenience of contactless transactions through tap-to-pay technology, a feature embraced by many Canadian merchants. This technology allows users to seamlessly complete transactions by tapping their Mastercard on payment terminals. Additionally, Mastercard provides a range of benefits and rewards programs for cardholders, including cashback rewards, travel perks, and other incentives based on the specific credit card. Overall, Mastercard stands out as a convenient and broadly accepted payment option in Canada, simplifying the purchasing process for consumers in both online and physical retail settings. ### PayPal PayPal is widely accepted as a payment method in Canada. It can be used for online purchases on various websites, including e-commerce platforms, online marketplaces, and individual sellers. PayPal can also be used for sending and receiving money between individuals or businesses. Additionally, many Canadian businesses accept PayPal as a payment option in their physical stores or for services rendered. To use PayPal in Canada, individuals need to create a PayPal account and link it to their bank account or credit card. ### American Express American Express is widely accepted as a payment method in Canada. It is accepted at most major retailers, restaurants, and online merchants across the country. American Express also offers a range of credit cards specifically designed for Canadian consumers, with various rewards programs and benefits. Additionally, American Express has a strong presence in the travel industry in Canada, with many travel agencies and airlines accepting American Express for bookings and purchases. Overall, American Express is a popular and widely accepted payment method in Canada. ### Discover Discover is a payment method that is accepted in Canada. Discover cards can be used at any merchant that accepts Discover, both online and in-store. Discover is widely accepted in Canada, especially at larger retailers and online merchants. However, it may not be accepted at smaller or local businesses, so it is always a good idea to check with the merchant beforehand. Additionally, some merchants may charge a foreign transaction fee for using a Discover card in Canada, so it is important to be aware of any potential fees before making a purchase. Afterpay and Clearpay are both buy now, pay later services allowing consumers to make purchases and pay in installments. Afterpay is operational in Canada, offering a convenient four-payment plan without interest or fees if payments are timely. Accepted by diverse retailers, Afterpay spans industries like fashion, beauty, and electronics. Users create an account, link their debit or credit cards, and select Afterpay at checkout to complete purchases with a payment schedule. In contrast, Clearpay is not currently available in Canada, primarily serving the UK and Australia, though potential expansion into Canada has been discussed. In essence, while Afterpay is accessible in Canada, Clearpay is not, giving Canadian consumers the option of Afterpay for flexible payments at participating retailers. Diners Club International operates as a global payment network, providing credit cards for both consumers and businesses. Although Diners Club cards are accepted at various establishments in Canada, including retailers, restaurants, and hotels, their acceptance is not as widespread as that of Visa or Mastercard. To use a Diners Club card in Canada, individuals simply present the card at the point of sale, where the merchant processes the payment through their terminal or online system. However, acceptance may vary among merchants, and some may require additional identification or a signature for verification. It is advisable to confirm a merchant's acceptance of Diners Club cards beforehand and to have an alternative payment method on hand in case it is not accepted at a particular establishment. ### Apple Pay Apple Pay was introduced in Canada in November 2015, marking one of the early expansions of the mobile payment service outside the United States. Available on iPhone, iPad, and Apple Watch, users can add their credit or debit cards to the Wallet app, either manually or by taking a photo. Transactions are authenticated using Touch ID or Face ID, with payments made by holding the device near a contactless terminal. Widely accepted at major Canadian retailers like Tim Hortons, McDonald's, and Petro-Canada, as well as online merchants, Apple Pay has gained popularity for its convenience and security. Beyond payments, the service supports loyalty cards and rewards programs, allowing users to streamline purchases and access their loyalty cards effortlessly. Overall, Apple Pay has established itself as a preferred payment method in Canada, offering a secure and convenient solution for both in-store and online transactions. ### JCB JCB, or Japan Credit Bureau, is a prominent credit card issuer in Japan that has been actively working to expand its acceptance network in Canada. Although not as universally accepted as Visa or Mastercard, JCB has formed partnerships with payment processors and acquiring banks to increase its presence among Canadian merchants. This effort has led to a growing number of businesses in Canada now accepting JCB cards for both online and in-store transactions. Customers can use their JCB cards by presenting them or entering card details at checkout, with some merchants requiring additional verification. While acceptance is on the rise, it's advisable for users to verify a merchant's acceptance of JCB beforehand, as it may still be limited compared to other major credit card brands. This expansion benefits Japanese tourists and residents in Canada who hold JCB cards by providing them with an additional payment option. ### Klarna Klarna, a widely used payment method in numerous countries, including Canada, enables online shoppers to defer payment for their purchases through installment plans. Particularly beneficial for customers facing financial constraints, Klarna offers various payment options such as Pay in 4 and Pay Later in the Canadian market. Pay in 4 permits customers to divide their payments into four equal parts, with the first due at the time of purchase and subsequent payments scheduled every two weeks. Alternatively, Pay Later allows customers to pay for their entire purchase within 30 days. To utilize Klarna in Canada, customers can choose it as their payment method during checkout on participating websites, providing personal information and agreeing to Klarna's terms. However, it's crucial to note that not all online retailers in Canada accept Klarna, prompting customers to check for the Klarna logo or available payment options at checkout. In summary, Klarna serves as a convenient payment solution for Canadian customers seeking to manage and extend the payment of their online purchases. ### UnionPay UnionPay is a highly accepted payment method in Canada, particularly among businesses catering to Chinese tourists and residents. Numerous merchants, including retailers, restaurants, hotels, and various establishments, acknowledge UnionPay cards for transactions. Beyond physical card payments, UnionPay provides mobile payment alternatives, such as QR code and mobile wallet payments, enabling users to make payments via their smartphones. To utilize UnionPay in Canada, individuals need a UnionPay card issued by a supportive bank, and they should verify with their bank to confirm availability. While UnionPay enjoys widespread acceptance, it's advisable to check with merchants beforehand, as not all may support this payment method. ### WeChat Pay WeChat Pay, a prominent mobile payment system in China, has limited acceptance in Canada, though some businesses are adapting to the growing Chinese tourist and resident demographic by incorporating it as a payment option. To utilize WeChat Pay in Canada, users must connect their WeChat account to a bank account or credit card and can then make payments at participating establishments through the WeChat app by scanning QR codes or providing their WeChat ID. Notable businesses embracing WeChat Pay in Canada include luxury retailers, hotels, and restaurants catering to Chinese clientele, along with certain online platforms and e-commerce sites. Despite its increasing popularity, WeChat Pay is not as universally accepted as other payment methods like credit cards or mobile wallets, prompting the need to verify a merchant's acceptance before using WeChat Pay. ### Google Pay Google Pay in Canada is a widely accepted digital wallet and payment method available on compatible Android devices with NFC capabilities. Users can download the Google Pay app, sign in with their Google account, and add a payment method by scanning or manually entering card details. After verifying the card, payments can be made at various retailers, restaurants, and online platforms displaying the contactless payment symbol. Additionally, Google Pay offers features like loyalty card and ticket storage, as well as peer-to-peer payments. Users should be aware that not all merchants in Canada accept Google Pay, so it's advisable to confirm acceptance before attempting to use it as a payment method. ### Alipay Alipay, a popular mobile payment platform in China, is not extensively embraced as a payment method in Canada, where credit cards and mobile platforms like Apple Pay and Google Pay are more commonly used. While some Canadian merchants may accept Alipay, its usage is not as widespread, and individuals visiting Canada are advised to check with establishments to ascertain its acceptance. Certain businesses catering to Chinese tourists or specific tourist destinations may be more inclined to accept Alipay. Despite Alipay's efforts to expand internationally and collaborate with local payment providers, its partnership with SnapPay in Canada is limited, available only at select merchants. Consequently, while Alipay can be utilized in specific scenarios in Canada, it is not as universally accepted as other payment methods, prompting the recommendation to have alternative payment options when visiting the country. Zip payment is not widely used in Canada. It is primarily used in Australia and New Zealand. In Canada, popular payment methods include credit cards, debit cards, and mobile payment apps like Apple Pay and Google Pay. PaySafeCard is a widely used prepaid payment option in Canada, enabling users to conduct online transactions without requiring a credit card or bank account. Available for purchase at diverse retail outlets like convenience stores and supermarkets, the physical card contains a unique 16-digit PIN code that users input during online transactions. The purchase amount is deducted from the card's balance. Versatile in its applications, PaySafeCard is accepted by numerous online merchants in Canada, spanning gaming sites, e-commerce platforms, and digital content providers, ensuring a secure and convenient payment process without divulging personal or financial details. For those who prefer a virtual approach, an online PaySafeCard account can be established, facilitating fund loading through various methods like credit cards or bank transfers and enabling online payments without the necessity of a physical card. Overall, PaySafeCard stands out as a popular and secure payment method in Canada, offering a straightforward solution for online purchases without the reliance on traditional banking methods. ### Samsung Pay Samsung Pay is a mobile payment service available for select Samsung devices in Canada, including the Galaxy S21, Galaxy Note20, Galaxy S20, and Galaxy A series. Users can securely store credit and debit card information on their devices through the Samsung Pay app, downloaded from the Google Play Store. The service supports both NFC and MST technologies, enabling contactless payments at various terminals. Samsung Pay goes beyond basic functionality by integrating loyalty cards, allowing users to store and use them directly from the app. Additionally, users can track transaction history and manage payment cards within the application, providing a convenient and secure payment experience with broad compatibility across terminals in Canada. ## Accepting International Card Payments in Canada Whether you sell to customers in Canada from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards and Interac are universal in Canada but PayPal and Apple Pay are increasingly expected for online checkout. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Canada, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. Need to collect payments in Canada? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-china/ --- # Payment Methods in China: Alipay, WeChat Pay & UnionPay (2026) | Shuttle > Alipay and WeChat Pay dominate Chinese digital payments. Explore the most popular payment methods in China including UnionPay and cross-border options for... # Payment Methods in China: Alipay, WeChat Pay & UnionPay (2026) By Nick Dunse, October 27, 2023 Alipay and WeChat Pay dominate Chinese digital payments. Explore the most popular payment methods in China including UnionPay and cross-border options for... Start collecting payments today Send payment links to your customers in China -- no card machine, no website, no fuss. ### Alipay Alipay, a subsidiary of Ant Group, stands as the foremost online payment platform in China since its establishment in 2004, achieving dominance in the market. Offering a diverse array of services, including online payments, money transfers, bill settlements, and wealth management, Alipay boasts a user base surpassing 1 billion and widespread acceptance among millions of both online and offline merchants. ### WeChat Pay WeChat Pay, under Tencent's ownership, presents another influential mobile payment platform in China, seamlessly integrated into the WeChat messaging app with over 1 billion monthly active users. WeChat Pay facilitates in-app payments for various services, encompassing shopping, dining, transportation, and more. ### UnionPay UnionPay, the largest card scheme in China, enjoys widespread acceptance, providing both debit and credit cards, with an extensive network of ATMs and point-of-sale terminals. Additionally, alternative platforms such as JD Pay, Baidu Wallet, and Apple Pay contribute to the diverse landscape. The prevalence of mobile-based payment platforms, owing to their convenience and integration with other services, establishes them as the favored method for online transactions in China. As smartphone usage proliferates and access to banking services expands, the trajectory of robust growth in the Chinese e-Commerce market is anticipated to persist. ## Popular offline payment methods in China ### Cash ### Bank Cards ### Mobile Payment Apps ## List of payment methods in China WeChat Pay, an extensively used mobile payment service in China, seamlessly integrated into the WeChat messaging app with a user base exceeding 1 billion monthly active users, facilitates a broad spectrum of online and offline transactions. Users can link their bank accounts or credit cards to their WeChat accounts, enabling payments through QR code scanning or direct transfers to other WeChat users. Widely embraced by merchants, both online and offline, WeChat Pay is a prevalent choice for everyday activities like shopping, dining, and transportation. Beyond its payment functionality, WeChat Pay offers additional features such as money transfers, bill payments, and the storage of loyalty cards and coupons. Its pervasive acceptance and user-friendly features have transformed it into an indispensable payment method in China, reshaping the landscape of transactions and diminishing the dependence on cash. UnionPay serves as a prominent payment method in China and stands as the exclusive interbank network in the country. Widely accepted by a multitude of merchants encompassing online and offline establishments, hotels, restaurants, and transportation services, UnionPay cards facilitate diverse transactions such as purchases, cash withdrawals, and money transfers. These cards, whether linked to bank accounts or utilized as prepaid options, also provide mobile payment services through a dedicated app, enabling users to conduct transactions seamlessly via smartphones. Notably advantageous for both domestic and international users, UnionPay's broad acceptance among merchants, including those catering to tourists, ensures convenient payment options without the reliance on cash. ### Mastercard Mastercard is accepted as a payment method in China, but it is not as widely used as other payment methods such as Alipay and WeChat Pay. Mastercard has been working to expand its presence in China and has partnered with several Chinese banks to issue Mastercard-branded cards. However, the use of these cards is still relatively limited compared to domestic payment methods. Additionally, foreign-issued Mastercards may not be accepted at all merchants in China, especially smaller businesses that may only accept local payment methods. Therefore, it is recommended to have alternative payment options when traveling to China. PayPal serves as a viable payment option, albeit with restricted functionality when contrasted with its capabilities in other nations. Chinese users can employ PayPal for cross-border transactions, facilitating international online purchases. However, the platform lacks support for domestic transactions within China. To utilize PayPal in the country, users must possess a verified PayPal account linked to a Chinese bank account or credit card. This enables them to make payments on international websites that accept PayPal. It's important to recognize that Alipay and WeChat Pay dominate the digital payment landscape in China, boasting larger user bases and wider merchant acceptance. These local platforms offer more extensive services and are widely embraced for both online and offline transactions within China. Consequently, while PayPal is an available payment method in China, its utilization is constrained compared to the prevalence of local digital payment giants like Alipay and WeChat Pay. Visa serves as a widely recognized and accepted mode of payment across China, particularly among merchants in major urban centers and popular tourist destinations. This includes hotels, restaurants, retail stores, and online vendors. The versatility of Visa cards extends to point-of-sale terminals in urban areas and facilitates online transactions on Chinese websites and mobile applications. Despite this widespread acceptance, it's crucial to be aware that certain smaller establishments may exclusively accommodate local payment methods like UnionPay. To ensure a seamless experience, it's advisable to carry some cash or an alternative payment option in case Visa is not viable. Additionally, travelers are encouraged to inform their bank or card issuer of their travel plans to prevent potential disruptions due to security measures. In essence, Visa proves to be a convenient and prevalent payment solution in China, streamlining the purchasing process for travelers throughout their stay. In February 2016, Apple Pay was introduced in China, marking its fifth global expansion. The service, supported by UnionPay, the largest payment network in the country, is widely accepted at various establishments, including retail outlets, restaurants, and online platforms. To utilize Apple Pay in China, users must add their UnionPay credit or debit card to the Wallet app on their iPhone or Apple Watch. Payments can then be made by holding the device near a contactless terminal and verifying the transaction with Touch ID or Face ID. Notably, Apple Pay in China extends its support to transit cards for public transportation in cities like Beijing and Shanghai, and users can also make in-app purchases. ## Accepting International Card Payments in China Whether you sell to customers in China from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. International cards rarely work in mainland China -- Alipay and WeChat Pay are the only realistic options for accepting payments from Chinese consumers. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for China, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in China as a Platform For software platforms serving merchants in China, supporting local payment methods like Alipay, WeChat Pay, and UnionPay is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in China? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-egypt/ --- # Egypt Payment Methods: 8 Ways Egyptians Pay (2026) | Shuttle > Fawry kiosks, Vodafone Cash, Meeza cards and cash on delivery -- how do 100M+ Egyptians actually pay? The complete guide to payment methods in Egypt. # Egypt Payment Methods: 8 Ways Egyptians Pay (2026) By Nick Dunse, October 28, 2021 Fawry kiosks, Vodafone Cash, Meeza cards and cash on delivery -- how do 100M+ Egyptians actually pay? The complete guide to payment methods in Egypt. Start collecting payments today Send payment links to your customers in Egypt -- no card machine, no website, no fuss. The rising prevalence of digital payments and e-commerce in Egypt offers a lucrative opportunity for merchants seeking to establish and enhance their online presence. With a sizable and youthful population, there is a robust demand for online shopping, facilitated by the convenience of mobile money platforms. Nevertheless, entering the Egyptian market poses challenges, notably the relatively low internet penetration rate, emphasizing the need for mobile optimization to reach a broader audience. Additionally, robust cybersecurity measures are imperative to counter the escalating risk of cybercrime accompanying the surge in digital payments. Merchants are urged to invest in secure payment gateways and enforce stringent security protocols to safeguard customer data and thwart fraud. Despite these hurdles, the growth potential in Egypt's e-commerce sector remains substantial. As internet access expands and digital payment adoption rises, merchants can capitalize on this momentum by adapting to mobile-first strategies, understanding the local market, and prioritizing cybersecurity to ensure success in this burgeoning market. ## Popular offline payment methods in Egypt ### Cash ### Bank Transfers ### Cheques ### Mobile Wallets ### Debit Cards ### Fawry ## List of payment methods in Egypt ### Meeza Meeza, launched by the Egyptian government in 2017, Meeza has become a popular payment method in Egypt, offering a mobile wallet service enabling users to conduct various financial transactions through their smartphones. Supported by major mobile network operators like Vodafone, Orange, and Etisalat, Meeza allows users to link their mobile numbers to their accounts for payments at retail stores, restaurants, and online platforms. Users download the Meeza app, register, and load funds through bank transfers or cash deposits at authorized agents. Beyond basic transactions, Meeza facilitates bill payments, money transfers, and cash withdrawals, promoting financial inclusion by extending digital financial services to a broader population. Its widespread acceptance by merchants and its role in reducing reliance on physical cash contribute to Meeza's popularity as a secure and convenient payment solution in Egypt. Easycash is a prevalent mobile payment service in Egypt, enabling users to conduct transactions and money transfers through their smartphones. The process involves downloading the Easycash app, creating an account, and linking a bank account or credit card for fund transfer. Users can make payments by scanning QR codes or entering the merchant's phone number. Easycash facilitates various transactions, including bill payments, online shopping, and peer-to-peer transfers, offering a secure and convenient alternative to cash transactions. The service's popularity is attributed to its widespread acceptance among merchants, its loyalty programs rewarding users with points for transactions, which can be redeemed for discounts or freebies, and its overall ease of use, making it a favored choice for managing finances via mobile devices in Egypt. Fawry, established in 2008, has emerged as a leading digital payment method in Egypt, offering users a secure and convenient way to make payments for a diverse range of services and products. Operating through online, mobile, and physical payment points, Fawry allows users to pay bills, top up mobile credit, transfer money, purchase tickets, and conduct online transactions. To utilize Fawry, users create an account, linking it to their bank account or credit card, and can then make instant payments through the app or website. Fawry's extensive network of partnerships with businesses and service providers ensures broad service coverage, encompassing utility companies, telecom operators, government agencies, and e-commerce platforms. Notably, Fawry's accessibility is enhanced by its 100,000 payment points located in retail stores, pharmacies, post offices, and banks throughout Egypt, contributing to its transformative impact on the country's payment landscape and its sustained popularity among businesses and individuals alike. Aman, launched in 2019 in Egypt as a collaboration between the National Bank of Egypt (NBE) and Telecom Egypt, is a mobile payment service facilitating various financial transactions through smartphones. Users can download the Aman app, register, and link their bank accounts or credit cards to make payments, transfer money, and settle bills. Cash deposits are also possible at authorized Aman agents. The service supports payments through QR codes or phone numbers and permits fund transfers and cash withdrawals. Aman enjoys widespread acceptance among merchants, including supermarkets, restaurants, cafes, and online stores, and is integrated with government services for utility and tax payments. Offering a secure and cashless alternative, Aman incentivizes users with discounts and cashback rewards, contributing to its popularity in Egypt and fostering financial inclusion by extending digital financial services to a broad demographic. InstaPay, a widely used payment method in Egypt, enables users to execute instant transactions via their mobile phones. By downloading the InstaPay app and linking their bank accounts or credit cards, users can fund their InstaPay wallet and make various payments, such as bill settlements and online purchases, securely. Transactions are conducted by scanning QR codes or entering the recipient's phone number, with the deducted amount instantly transferred from the user's wallet to the recipient's InstaPay account. The system's versatility extends to utility bill payments, mobile phone credit top-ups, and money transfers to friends and family. Notably, InstaPay enhances safety and convenience by eliminating the need for cash transactions, providing users with detailed transaction histories and easy expense tracking. Widely accepted by a growing number of merchants in Egypt, InstaPay is poised for continued popularity and adoption. Sympl is a mobile payment platform operating in Egypt, enabling users to make convenient and secure payments through their smartphones. The app, available on the App Store and Google Play Store, requires users to create an account and link their bank account or credit card to add funds. Payments can be made by scanning QR codes or entering the merchant's phone number, with the amount deducted from the user's Sympl balance or linked financial accounts. Sympl serves as a versatile payment method for various services such as utility bills, mobile top-ups, online shopping, transportation, and person-to-person transfers among Sympl users. The platform eliminates the need for cash, offering a digital wallet accessible at any time and location, enhancing the overall efficiency and accessibility of payment transactions in Egypt. ValU is a digital wallet and payment service available in Egypt, provided by the Commercial International Bank (CIB) in collaboration with the Egyptian government. It enables users to make both online and offline payments through their mobile phones for various purposes, including bill payments, online shopping, and in-store purchases. Users can link their ValU account to their bank account or credit card, facilitating easy funding for transactions. The process involves downloading the ValU app, creating an account, and adding funds through methods like bank transfers or credit card payments. ValU emphasizes security with features such as biometric authentication and transaction alerts, while also allowing users to monitor their spending and access transaction history within the app. Overall, ValU offers a secure and convenient payment solution, enhancing accessibility for individuals in Egypt to conduct transactions swiftly and securely using their mobile devices. Khazna, established in Egypt in 2019 as a collaborative effort between the National Bank of Egypt and Telecom Egypt, is a mobile payment service designed to offer a secure and convenient payment solution for individuals and businesses. Users can utilize the Khazna mobile app by registering and linking their bank accounts or credit cards, enabling them to make various transactions, including bill payments, online shopping, money transfers, and in-store purchases, through QR code scans or entering the merchant's phone number. Khazna's strength lies in its extensive acceptance network, featuring partnerships with numerous merchants across Egypt, spanning supermarkets, restaurants, cafes, and online retailers. Beyond convenience, the service prioritizes security, incorporating features like transaction notifications and the option to lock or unlock the app with a PIN or fingerprint. With these attributes, Khazna emerges as a compelling alternative to traditional payment methods, ensuring both ease of use and safeguarding users' financial information. Mobile Network Transfer (MNT) is gaining traction as a popular payment method in Egypt, offering users a convenient and secure way to transfer money through their mobile phones. Its accessibility is a key advantage, as nearly everyone in the country owns a mobile phone, allowing for widespread adoption. MNT accommodates both banked and unbanked individuals, circumventing the need for a traditional bank account. Transactions, facilitated by mobile network operators like Vodafone, Orange, and Etisalat, enable users to transfer funds or make payments swiftly and efficiently, eliminating the reliance on cash transactions. Notably, the speed of MNT transactions is advantageous for businesses handling large transaction volumes. The method also prioritizes security, incorporating PIN or biometric authentication, encrypted transactions, and monitoring by mobile network operators to prevent fraud. As digital payments gain momentum, MNT is anticipated to continue growing in popularity in Egypt, fueled by its accessibility, speed, and robust security features. Halan is a popular digital payment method in Egypt, offering users a convenient and secure way to make cashless transactions through their mobile phones. It functions as a digital wallet that can be utilized for various services such as transportation, food delivery, and online shopping. Users can download the Halan app, create an account, and link their bank account or credit card to fund their digital wallet. Payments are made by scanning QR codes or entering the merchant's phone number, with the amount deducted from the user's wallet balance. A confirmation message is sent to both the user and the merchant upon successful transactions. Additionally, Halan features "Halan Pay," enabling instant money transfers between users, facilitating bill splitting and transactions with friends and family. Overall, Halan plays a significant role in reducing reliance on physical cash and promoting financial inclusion in Egypt. Shahry, a mobile payment service in Egypt offered by the National Bank of Egypt (NBE), facilitates transactions through users' mobile phones. Open to both NBE customers and non-customers, it requires the download of the Shahry mobile app for account registration. Users can link their bank accounts or credit cards to the app, deposit cash at NBE branches, or use alternative methods like Fawry or Vodafone Cash to add funds to their Shahry wallet. The service supports various payments, including bills, online purchases, and person-to-person transfers, and enables cash withdrawals from ATMs without a physical debit card. Shahry stands out for its secure and convenient payment process, eliminating the need for physical currency or cards, and offers additional features like transaction history, balance inquiry, and notifications for enhanced user convenience. Overall, Shahry is a widely embraced mobile payment method in Egypt, providing a secure and user-friendly means for conducting transactions via mobile phones. MyFawry is a widely embraced payment method in Egypt, enabling users to make online and offline payments for diverse services and products. Easily accessible through the MyFawry website or mobile app, users can link their bank accounts or credit cards to add funds, facilitating seamless transactions. Accepted by a broad spectrum of merchants, service providers, and government entities, MyFawry covers utility bills, mobile top-ups, internet subscriptions, transportation fees, online shopping, and government payments, including taxes and fines. The platform stands out for its convenience, allowing users to make payments anytime, anywhere, while also offering the advantage of secure transactions. Utilizing encryption technology and employing a one-time password (OTP) sent to registered mobile numbers for each transaction, MyFawry ensures the protection of users' personal and financial information. In summary, MyFawry is a widely accepted and secure payment solution in Egypt, providing users with the convenience of flexible transactions and robust security features. The CIB Smart Wallet, offered by the Commercial International Bank (CIB) in Egypt, is a digital financial solution that allows users to efficiently manage their finances and conduct transactions through their mobile devices. This payment method brings unparalleled convenience by enabling users to make payments anytime and anywhere, eliminating the need for physical cash or cards. Notably, the CIB Smart Wallet prioritizes security through PIN or biometric authentication, mitigating the risks of fraud or unauthorized access. Its widespread acceptance at various merchants, including retail stores, restaurants, online platforms, and utility bill payments, makes it a versatile option for diverse transactions. The wallet further enhances the user experience by offering exclusive rewards and discounts, such as cashback, loyalty points, and special promotions with partner merchants. Additionally, users can leverage the app's financial management tools to monitor spending, review transaction history, and establish budgeting goals. The CIB Smart Wallet also facilitates instant money transfers among users, providing a comprehensive and secure digital payment solution for individuals in Egypt. Qatar National Bank (QNB), a major financial institution in the Middle East, extends its services to Egypt, offering a comprehensive range of banking services, particularly focusing on various payment methods. QNB customers in Egypt can conduct transactions through their accounts using online banking, mobile banking, and ATMs. The bank facilitates purchases at merchants accepting QNB cards, enables money transfers to individuals or businesses, and allows customers to link their accounts to digital wallets like Apple Pay or Samsung Pay for secure mobile payments. Going beyond conventional methods, QNB introduces innovative solutions like QR code payments, empowering customers to generate QR codes through the mobile app and seamlessly make payments at participating merchants. Overall, QNB provides a convenient and secure payment ecosystem, enhancing the efficiency of transactions for its Egyptian clientele. ALAHLI E-Wallet, provided by the National Bank of Egypt (NBE), is a digital payment solution enabling users to conduct online and mobile transactions through their smartphones. Users must download the ALAHLI E-Wallet app, available on the App Store or Google Play Store, and register an account, linking their bank accounts or credit cards. This e-wallet facilitates payments at diverse merchants, covering online retailers, restaurants, and utility bills. Additionally, users can transfer funds to other ALAHLI E-Wallet users. Making a payment involves selecting the ALAHLI E-Wallet option at the merchant's checkout or scanning a provided QR code, with the amount deducted from the user's ALAHLI E-Wallet account. Offering a secure and convenient alternative to cash or physical cards, ALAHLI E-Wallet provides real-time transaction notifications, transaction history tracking, and account management features. Its popularity in Egypt stems from its user-friendly interface, widespread merchant acceptance, and the trust associated with being backed by the National Bank of Egypt. Etisalat Cash, a mobile wallet service from the prominent telecommunications company Etisalat in Egypt, facilitates seamless payments and money transfers via mobile phones. To utilize this service, individuals must register for an Etisalat Cash account at an authorized location, presenting required identification documents. Following registration, users can load funds into their accounts through various channels such as Etisalat stores, authorized agents, or bank transfers. The loaded amount can be used for payments at participating merchants or transferred to other Etisalat Cash users. Payments are made by providing the mobile number and PIN at the merchant's point of sale, deducting the amount from the user's Etisalat Cash balance. Accepted for bill payments, online shopping, and in-store purchases, Etisalat Cash offers a convenient and secure alternative to carrying cash or physical cards, providing users in Egypt with a streamlined payment experience across a diverse range of merchants. ## Accepting International Card Payments in Egypt Whether you sell to customers in Egypt from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Card adoption is growing fast in Egypt but Fawry, mobile wallets, and cash on delivery still handle most consumer transactions. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Egypt, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Egypt as a Platform For software platforms serving merchants in Egypt, supporting local payment methods like local bank transfers and mobile money is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Egypt? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-ethiopia/ --- # Redirecting to: /blog/the-most-popular-payment-methods-in-ethopia/ ## Links - [Redirecting from to](/blog/the-most-popular-payment-methods-in-ethopia/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-ethopia/ --- # Ethiopia Payment Methods: 6 Key Options for 2026 | Shuttle > Telebirr dominates with 40M+ users, but it's not the only option. See all the payment methods used in Ethiopia, from mobile money to bank transfers. # Ethiopia Payment Methods: 6 Key Options for 2026 By Nick Dunse, February 12, 2026 Telebirr dominates with 40M+ users, but it's not the only option. See all the payment methods used in Ethiopia, from mobile money to bank transfers. Start collecting payments today Send payment links to your customers in Ethiopia -- no card machine, no website, no fuss. The growth of digital payments in Ethiopia is fueled by multiple factors. The government's active promotion of digital payments, as part of its broader modernization and financial inclusion efforts through initiatives like the National Payment System Vision 2025, is a significant driver. The popularity of mobile money services such as M-Pesa and HelloCash has played a crucial role, especially in rural areas where traditional banking services are limited. The COVID-19 pandemic has further accelerated this trend as lockdowns and social distancing measures increased the demand for contactless payment options, pushing businesses and individuals to embrace digital solutions. However, challenges like limited internet connectivity and low smartphone penetration rates need addressing for widespread adoption. Despite these hurdles, the Ethiopian digital payments market is poised for substantial growth, supported by government initiatives and the increasing acceptance of mobile money services. ## Popular offline payment methods in Ethiopia ### Cash ### Mobile Money ### Bank Transfers ### Cheques ### Debit Cards ### Money Orders ## List of payment methods in Ethiopia ### AND PayPal and Payoneer, can be used for international transactions in Ethiopia. However, these platforms are not widely used for domestic transactions. ### Visa Visa is a widely embraced payment method in Ethiopia, with numerous businesses, including hotels, restaurants, and shops, accepting Visa cards. The country also features a widespread network of ATMs for cash withdrawals by Visa cardholders. Despite its broad acceptance, it's advisable for travelers, especially in remote areas, to carry some cash as a contingency since Visa may not be universally accepted. Additionally, some businesses may levy an extra fee, usually a small percentage of the transaction, for using a Visa card. Despite these considerations, Visa proves to be a convenient and prevalent means of payment in Ethiopia, facilitating easy transactions and cash access for travelers throughout their stay. MasterCard is widely accepted in Ethiopia and can be used for both online and offline payments ### American Express American Express cards are accepted at some establishments in Ethiopia, although acceptance may be more limited compared to Visa and MasterCard. Diners Club International cards are accepted at select locations in Ethiopia, but acceptance may be limited. ### UnionPay UnionPay is a widely accepted payment method in Ethiopia. It is accepted at various merchants, including hotels, restaurants, and retail stores. UnionPay cards can also be used to withdraw cash from ATMs in Ethiopia. To use UnionPay in Ethiopia, you will need to have a UnionPay card issued by a bank that is affiliated with UnionPay. You can check with your bank to see if they offer UnionPay cards. When making a payment with UnionPay, you will need to insert your card into the card reader and enter your PIN. Some merchants may also require you to provide additional identification, such as a passport or driver's license. It is important to note that while UnionPay is widely accepted in Ethiopia, not all merchants may accept it. It is always a good idea to carry some cash as a backup payment method. ### CBE Birr CBE Birr is a mobile payment service offered by the Commercial Bank of Ethiopia. It allows users to make payments using their mobile phones. ### HelloCash HelloCash is another mobile payment service available in Ethiopia. It allows users to send and receive money, pay bills, and make purchases using their mobile phones. ### Amole Amole is a mobile payment service offered by the Ethiopian Telecommunications Corporation (Ethio Telecom). It allows users to make payments, transfer money, and pay bills using their mobile phones. ### Dashen Bank Dashen Bank offers a mobile banking service that allows customers to make payments, transfer money, and perform other banking transactions using their mobile phones. Wegagen Bank also offers a mobile banking service that allows customers to make payments, transfer money, and perform other banking transactions using their mobile phones. ## Accepting International Card Payments from Ethiopia If you run a business in Ethiopia -- freelancer, agency, exporter, or online seller -- and need to invoice or sell to international clients, local payment methods alone aren't enough. PayPal has limited functionality in Ethiopia, Payoneer charges 2-3% plus withdrawal fees, and bank wires are slow. A hosted payment link gives you a branded checkout page that accepts cards, Apple Pay, and Google Pay from clients anywhere in the world. Shuttle Links & Checkout connects you to a payment provider that supports international card payments, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Ethiopia as a Platform For software platforms serving merchants in Ethiopia, supporting local payment methods like mobile money services like CBE Birr and HelloCash is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Ethiopia? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-france/ --- # Payment Methods in France: Carte Bancaire, PayPal & Wallets (2026) | Shuttle > Carte Bancaire leads French payments. Explore the most popular payment methods in France including PayPal, Apple Pay, Klarna, and bank transfers. # Payment Methods in France: Carte Bancaire, PayPal & Wallets (2026) By Nick Dunse, January 31, 2022 Carte Bancaire leads French payments. Explore the most popular payment methods in France including PayPal, Apple Pay, Klarna, and bank transfers. Start collecting payments today Send payment links to your customers in France -- no card machine, no website, no fuss. French consumers exhibit distinct preferences and behaviors in the realm of online shopping. Notably, the use of bank cards, encompassing both credit and debit cards, stands out as the predominant payment method, with the local Cartes Bancaires system and international players like Visa and Mastercard being widely embraced. Despite the popularity of smartphones in France, the majority of online shoppers still favor using laptops or desktops for their transactions. The e-commerce market in the country is poised for robust growth, with projections indicating a value of $106.50 billion by 2023. Furthermore, French online shoppers display a noteworthy spending pattern, averaging over 2,200 EUR per year on their digital purchases. These trends collectively signify a mature and thriving e-commerce landscape in France, underscored by a strong inclination towards card payments, presenting a substantial opportunity for businesses to capitalize on this flourishing market. ## Popular offline payment methods in France ### Cash ### Cheques ### Carte Bancaire ### Bank Transfers ### Meal Vouchers ### Mobile Payments ### Prepaid Cards ### Mandate ## List of payment methods in France ### Cartes Bancaires Cartes Bancaires (CB), the predominant payment method in France, functions as a versatile debit and credit card system issued by French banks. Employing chip and PIN technology for enhanced security, CB cards are widely embraced by merchants for both online and in-person transactions. To complete a payment, users simply insert their card into a terminal and enter their PIN, while online purchases can be facilitated through card details entry on websites or secure payment gateways. CB cards enjoy broad acceptance at major establishments like retailers, restaurants, hotels, and ATMs, making them a convenient choice for diverse financial transactions. While other international options like Visa and Mastercard are also prevalent, it is prudent to confirm with merchants in advance regarding their preferred payment methods. ### Visa Visa is widely accepted as a payment method in France. It can be used at most retail stores, restaurants, hotels, and online merchants. Visa cards are also accepted at ATMs for cash withdrawals. ### Mastercard Mastercard is widely accepted as a payment method in France. It can be used at most retail stores, restaurants, hotels, and online merchants throughout the country. Mastercard is also accepted at ATMs for cash withdrawals. ### PayPal PayPal is widely accepted as a payment method in France. Many online retailers and service providers in France offer PayPal as an option for customers to make payments. Additionally, PayPal can be used for international transactions, making it convenient for French customers to shop from overseas websites. PayPal offers secure and easy payment processing, allowing customers to make purchases without sharing their financial information with the merchant. Overall, PayPal is a popular and trusted payment method in France. ### Maestro Maestro is a widely accepted payment method in France. It is a debit card issued by Mastercard and can be used for both online and offline purchases. Maestro cards are accepted at most merchants in France, including supermarkets, restaurants, and shops. They can also be used to withdraw cash from ATMs. To use Maestro as a payment method, simply present your card at the point of sale or enter the card details when making an online purchase. ### American Express American Express is widely accepted as a payment method in France. Many merchants, including restaurants, hotels, and retail stores, accept American Express cards. However, it is worth noting that American Express may not be as widely accepted as Visa or Mastercard in some smaller establishments or outside of major cities. It is always a good idea to carry an alternative form of payment, such as a Visa or Mastercard, when traveling in France. In France, meal vouchers, known as tickets restaurant, are a widespread method of payment for meals, often included in employees' benefits packages. These vouchers, usually provided in paper form, can be used at various establishments such as restaurants, cafes, food delivery services, and even grocery stores. The value of these vouchers, determined by the employer, is generally tax-exempt up to a specified amount and has an expiration date. When used, the voucher is presented to the cashier or server, who deducts its value from the total bill; any remaining amount can be paid with other forms of payment. It's important to note that meal vouchers can't be converted to cash and must be used for their designated purpose. However, not all establishments accept them, necessitating prior confirmation. Overall, meal vouchers offer a convenient and popular tax-free benefit for employees, facilitating the enjoyment of meals at a variety of places in France. ### Klarna Klarna is a popular payment method in France, allowing customers to buy now and pay later. It offers flexible payment options, such as paying in installments or deferring payments for a certain period of time. Klarna is accepted by many online retailers in France, making it convenient for customers to shop and pay for their purchases. The payment process is simple and secure, with customers being able to complete their transactions quickly and easily. Klarna also provides customer support in France, ensuring that any issues or questions are addressed promptly. Overall, Klarna is a convenient and popular payment method for customers in France. Oney is a prominent payment method in France, serving as a financial services company that delivers a range of payment solutions, encompassing credit cards, installment payments, and revolving credit. Renowned for its wide acceptance, Oney credit cards are utilized for both online and in-store transactions, providing users with advantages like cashback rewards, discounts, and adaptable payment choices. Beyond credit cards, Oney facilitates installment payment plans for substantial purchases, enabling customers to distribute the expense over several months. Furthermore, the company extends revolving credit, permitting users to borrow within a specified limit and repay gradually with added interest. In essence, Oney stands out as a versatile and widely embraced payment option in France, offering customers diverse means to manage payments and enhance the affordability of their purchases. Diners Club International operates as a global payment network, providing credit cards to customers worldwide, including in France. In the country, Diners Club cards are widely accepted at various establishments such as restaurants, hotels, and retail stores. To use the card, customers can present it at the point of sale, where it can be swiped or inserted into a card reader, and additional authorization may be required through a PIN or signature. While Diners Club cards enjoy broad acceptance in France, particularly at larger and international establishments, it is advisable for customers to verify acceptance with specific merchants. In addition to physical locations, Diners Club cards can also be utilized for online purchases on e-commerce websites, offering customers a convenient and secure payment option for transactions in both physical and virtual settings. Amazon Pay is a popular payment method in France. It allows customers to make purchases on Amazon.fr and other participating websites using their Amazon account information. With Amazon Pay, customers can securely pay for their purchases without having to enter their payment and shipping information each time. This makes the checkout process quick and convenient. Additionally, Amazon Pay offers buyer protection and fraud detection measures to ensure a safe shopping experience for customers. Overall, Amazon Pay is a trusted and widely used payment method in France. ### UnionPay UnionPay is accepted as a payment method in France. It is widely accepted at many merchants, including hotels, restaurants, and retail stores. UnionPay cards can be used for both online and in-store purchases. Additionally, UnionPay has partnered with local banks in France to offer cardholders additional benefits and services. ### Discover Discover is not widely accepted as a payment method in France. The most commonly accepted payment methods in France are cash, debit cards (Carte Bleue), and credit cards (Visa and Mastercard). Some businesses may accept Discover cards, but it is not as widely accepted as other card networks. It is always a good idea to have alternative payment methods available when traveling to France. ### Apple Pay Apple Pay, a mobile payment and digital wallet service by Apple Inc., is widely accepted in France at numerous retailers, online merchants, and apps, including Carrefour, Fnac, Sephora, Monoprix, Uber, Deliveroo, Airbnb, and Booking.com. To utilize Apple Pay, users in France must add their credit or debit cards to the Wallet app on their Apple devices, either through the app directly or via the Settings app. Once added, payments can be made in-store by holding the device near a contactless terminal and authenticating with Touch ID or Face ID. For online transactions, users select Apple Pay and authenticate using the same biometric features. The service extends to person-to-person payments through the Messages app with Apple Pay Cash. Overall, Apple Pay offers a secure and convenient payment method for users in France across a diverse range of transactions. ### JCB JCB, or Japan Credit Bureau, serves as a popular payment method in France, finding acceptance across various establishments such as restaurants, hotels, and retail stores. To utilize JCB for transactions in the country, one needs a JCB card issued by a supporting financial institution, which can be verified with one's bank or credit card provider. Once in possession of a JCB card, transactions are straightforward -- present the card at the point of sale, follow merchant instructions, and, if necessary, enter a PIN or sign a receipt. While JCB enjoys broad acceptance, there may still be occasional non-participating merchants, underscoring the importance of checking in advance or having an alternative payment option on hand. Overall, the convenience and widespread acceptance of JCB in France make it a favored choice for both residents and visitors. ### Alipay Alipay, the widely-used Chinese mobile payment platform, has expanded its reach to France, enabling Chinese tourists and residents in the country to utilize the app for purchases at participating merchants. To avail this service, users must possess a registered Alipay account and link it to a bank card, after which they can scan a merchant-provided QR code through the Alipay app to complete transactions. This move aligns with Alipay's global expansion strategy, aiming to serve the increasing number of Chinese tourists abroad by allowing them to make transactions in their preferred currency without the need for physical cash. Beyond payments, Alipay offers diverse services such as money transfers, bill payments, and travel bookings, consolidating its position as a comprehensive platform for Chinese users. French merchants accepting Alipay stand to gain by attracting more Chinese customers, tapping into the lucrative Chinese market, and leveraging Alipay's marketing tools for promotions and discounts, ultimately creating a mutually beneficial scenario that enhances convenience for Chinese users and boosts sales for local businesses. ### WeChat Pay WeChat Pay, a widely used mobile payment method in China, has limited acceptance in France, primarily found in establishments catering to Chinese tourists or possessing a substantial Chinese clientele. To utilize WeChat Pay in France, users must have a WeChat account linked to their bank account or credit card, enabling payments through the app by scanning QR codes or entering payment codes. Notable locations accepting WeChat Pay include luxury retailers such as Galeries Lafayette and Printemps, prominent tourist sites like the Louvre Museum and the Palace of Versailles, as well as select hotels, restaurants, and transportation services. However, its acceptance remains less pervasive compared to traditional methods like credit cards or cash in France, necessitating alternative payment options for travelers in the country. ### Google Pay Google Pay is available as a payment method in France. Users can add their credit or debit cards to the Google Pay app and use it to make payments at participating merchants. They can also use Google Pay to make online purchases and send money to friends and family. Google Pay is supported by a wide range of banks and financial institutions in France, making it a convenient and secure way to make payments. PaySafeCard is a prepaid online payment method available in France, offering a secure and anonymous option for users to make payments without requiring a bank account or credit card. Users can purchase physical cards from authorized retailers, each equipped with a unique 16-digit PIN code for transactions on various online platforms, including gaming, gambling, and e-commerce websites. Additionally, an online account with PaySafeCard allows users to buy virtual cards or vouchers directly from the website, eliminating the need for a physical card. Widely accepted in France, PaySafeCard provides a convenient and secure means of online payment on popular platforms like Amazon, eBay, and Steam, ensuring privacy by not requiring the sharing of personal or financial information. SEPA Direct Debit is a prevalent payment method in France, enabling businesses to effortlessly collect payments directly from customers' bank accounts, particularly for recurring expenses like utility bills and subscriptions. Businesses secure a mandate from customers, granting authorization for direct debit collection, obtainable through either a paper form or electronically. Transactions are facilitated via the SEPA system, ensuring smooth cross-border payments within the Eurozone. This method streamlines payment processes for businesses, enhancing security, efficiency, and cash flow management while reducing administrative costs and minimizing the risks associated with cash and checks. Customers benefit from the convenience of automatic deductions on due dates, eliminating concerns about late fees and the need to remember payment deadlines. Overall, SEPA Direct Debit is a trusted and widely adopted payment option in France, offering advantages for both businesses and customers in the realm of recurring payments. ## Accepting International Card Payments in France Whether you sell to customers in France from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Carte Bancaire dominates French card payments alongside PayPal -- international card-only checkouts often have lower conversion. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for France, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in France as a Platform For software platforms serving merchants in France, supporting local payment methods like Cartes Bancaires, SEPA Direct Debit, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in France? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-germany/ --- # Payment Methods in Germany: PayPal, SEPA & Klarna (2026) | Shuttle > PayPal leads German online payments alongside SEPA direct debit, Klarna, and giropay. # Payment Methods in Germany: PayPal, SEPA & Klarna (2026) By Nick Dunse, October 7, 2021 PayPal leads German online payments alongside SEPA direct debit, Klarna, and giropay. Start collecting payments today Send payment links to your customers in Germany -- no card machine, no website, no fuss. With a population of 11.6 million individuals, a significant portion of whom are already well-acquainted with online payment methods, Belgium emerges as a mature and enticing e-commerce market for online enterprises. Anticipated figures indicate that the number of e-commerce consumers in the country is poised to reach 8.6 million users by 2025. The e-commerce sector is forecasted to achieve a total revenue of $12.46 billion by the conclusion of 2023, showcasing an annual growth rate of 4.57%. This growth trajectory is expected to culminate in a market volume of $8.067 million by 2025. ## Popular offline payment methods in Belgium ### Cash ### Bank Transfers ### Direct Debit ### Prepaid Cards ### Cheques ### Mobile Payments ### Vouchers and Gift Cards ### Electronic Meal Vouchers ## List of payment methods in Belgium ### Bancontact Bancontact is a widely-used payment method in Belgium, both for online and in-store purchases. It utilizes customers' bank cards and is accepted by various types of merchants. To use Bancontact, customers select the option at checkout, enter their card details, and the payment is securely processed through their bank. It's considered a safe and convenient payment solution in Belgium. ### Mastercard Mastercard is a highly popular and widely accepted payment method in Belgium, suitable for both online and in-person transactions at a diverse range of businesses, such as retail stores, restaurants, and online platforms. It is known for providing convenience and security, making it the preferred choice for many in Belgium when making payments. ### Maestro Maestro is a widely accepted payment method in Belgium, functioning as a debit card system. Issued by banks, it enables customers to make purchases, withdraw cash from ATMs, and is usable both online and in physical stores. Linked to the customer's bank account, transactions lead to immediate fund deductions. Maestro enjoys broad acceptance at various Belgian merchants, encompassing supermarkets, restaurants, shops, and is frequently utilized for public transportation and parking payments. ### Visa Visa is a highly accepted and versatile payment method. It is widely used across various retail establishments, restaurants, and online merchants, and also allows for cash withdrawals at ATMs. Visa offers a range of card options, including credit, debit, and prepaid cards, each catering to different needs and offering distinct features and advantages. Visa is among the most favored payment methods in Belgium, alongside other major card networks like Mastercard and Maestro. ### PayPal PayPal is widely accepted in Belgium, with many online retailers and service providers offering it as a payment option. It is also convenient for international transactions, enabling Belgian customers to shop on overseas websites. To use PayPal in Belgium, customers must create an account, link it to their bank account or credit card, and select the PayPal option at checkout. It's a popular and trusted payment method in the country. ### Klarna Klarna is a widely used payment method in Belgium, enabling customers to shop online and defer payments through installments or paying in full later. It provides flexibility by allowing users to split payments into multiple installments. This is advantageous for those looking to manage their expenses or lacking immediate funds. Numerous online retailers in Belgium accept Klarna, ensuring its widespread availability for Belgian consumers. ### American Express American Express is accepted as a payment method in Belgium, but its acceptance is not as widespread as Visa or Mastercard. While many major retailers, hotels, and restaurants in Belgium do accept American Express, smaller businesses and local establishments may not. It's advisable to confirm with the merchant in advance if they accept American Express. Moreover, American Express cardholders may have the option to use their cards for cash advances at specific ATMs in Belgium. ### Discover Discover is not widely accepted in Belgium as a payment method. The more commonly used payment options in the country include cash, debit cards like Bancontact/Maestro, and credit cards such as Visa and Mastercard. While some businesses may accept Discover cards, it is less common than the mentioned methods. It's advisable to confirm with the specific establishment beforehand if you intend to use a Discover card for payment. ### Google Pay Google Pay is accessible in Belgium and functions as a convenient payment method. Users can link their credit or debit cards to the Google Pay app, facilitating payments at participating stores. Google Pay is compatible with contactless transactions via NFC technology, permitting users to complete purchases by tapping their phone on a payment terminal. Furthermore, it supports online shopping by enabling payments on websites and apps that accept this method. Diners Club International is a global credit card payment network with acceptance in Belgium, encompassing various merchants like restaurants, hotels, and retail stores. Customers can use their Diners Club cards by presenting them at the point of sale and signing for their purchases, with some merchants also supporting contactless payments. Additionally, these cards are suitable for online shopping in Belgium, where customers can input their card details during checkout on compatible websites. While Diners Club is accepted in Belgium, it might not be as prevalent as Visa or Mastercard, so it's advisable to confirm a merchant's acceptance before using this payment method. ### JCB JCB, also known as Japan Credit Bureau, is a popular payment method in Belgium, widely accepted by both physical and online retailers. Customers can use their JCB credit card by presenting it at the point of sale or entering card details during online checkout, similar to other credit card transactions. JCB offers benefits like cashback rewards, travel insurance, and discounts at partner merchants. The payment method is secure, with features like fraud protection and 24/7 customer support, making it a reliable and convenient option for purchases in Belgium, appealing to both locals and tourists. Amazon Pay is a payment option in Belgium, allowing Belgian customers to conveniently make purchases on participating websites. They can use their Amazon account credentials to log in and select Amazon Pay during the checkout process. ### UnionPay UnionPay is a commonly accepted payment method, particularly in popular tourist areas. Many merchants and some ATMs in the country readily accept UnionPay cards for both purchases and cash withdrawals. To use UnionPay, present your card at the point of sale or ATM and follow the on-screen prompts, which may require entering a PIN or signing a receipt, depending on the merchant's policies. It's important to note that while UnionPay is widely accepted in Belgium, it might not be as universally recognized as other international payment methods like Visa or Mastercard. Therefore, it's advisable to have alternative payment options, such as cash or another credit card, on hand as a backup. SOFORT is a widely-used payment method in Belgium, enabling customers to make online payments directly from their bank accounts, eliminating the need for a credit card. To use SOFORT, customers select it at checkout, choose their bank, and are redirected to their bank's online banking platform. They securely log in and authorize the payment, resulting in a direct transfer of funds from their bank account to the merchant's account. Many major Belgian banks, such as Belfius, BNP Paribas Fortis, ING, and KBC, support SOFORT, making it a convenient choice for those who prefer bank account payments. This method is favored for its convenience, security, and extensive bank network, providing an alternative to credit card payments for online purchases. PaySafeCard is a widely used prepaid payment method in Belgium, offering an alternative for online payments without requiring a bank account or credit card. Users can obtain a physical card from various retail locations, featuring a unique 16-digit PIN code for online transactions. By selecting PaySafeCard as the payment method and entering the PIN code, users can make secure payments, deducting the amount from their card balance. This payment method is accepted on various websites, including gaming platforms, e-commerce sites, and digital content providers. PaySafeCard offers a secure and convenient way to make online payments while safeguarding personal and financial information. However, it has limitations, such as a maximum card balance of €250 and some online merchants not accepting it. In summary, PaySafeCard is a popular and trusted payment option in Belgium, providing a safe and convenient means of making online purchases without the need for a bank account or credit card. ### Alipay Alipay, a widely used mobile payment platform in China, has limited acceptance in Belgium. While a few Belgian merchants may take Alipay, it is not as prevalent as more conventional payment options like credit cards or cash. When visiting Belgium and intending to use Alipay, it's advisable to verify with each establishment if they support Alipay payments. Having alternative payment methods, such as credit cards or cash, on hand is also recommended in case Alipay is not an option. ### WeChat Pay WeChat Pay is a popular mobile payment method in China but has limited acceptance in Belgium. However, certain Belgian merchants, especially those serving Chinese tourists or with a significant Chinese customer base, do accept WeChat Pay. To use it in Belgium, you need a WeChat account linked to your bank account or credit card. Payments can be made through the WeChat app by scanning QR codes or providing your WeChat ID. Examples of Belgian merchants accepting WeChat Pay include luxury retailers, hotels, and Chinese-tourist-oriented restaurants. Some online platforms and e-commerce websites also support WeChat Pay. It's important to note that while WeChat Pay is not widespread in Belgium, other mobile payment methods like Apple Pay and Google Pay enjoy broader acceptance among a wider range of merchants. ### Apple Pay Apple Pay was introduced in Belgium, accessible to customers of major banks like BNP Paribas Fortis, Fintro, and Hello Bank. To utilize Apple Pay in Belgium, users need an iPhone 6 or newer with iOS 11.2 or later, along with the addition of their eligible credit or debit card to the Wallet app. Once the card is added, payments can be made at contactless terminals by simply placing the iPhone near the terminal and verifying the transaction with Touch ID or Face ID. Apple Pay is also usable for online and in-app purchases on various Apple devices, including iPhone, iPad, and Mac. Notably, Apple Pay prioritizes security and convenience, safeguarding card information through tokenization and abstaining from storing transaction data on the device or Apple servers. SEPA Debit Card is a widely accepted payment method in Belgium, enabling customers to make payments directly from their bank accounts using their debit cards. SEPA stands for Single Euro Payments Area, an EU initiative aimed at harmonizing electronic payments across the region. To use a SEPA Debit Card in Belgium, customers must have an account with a participating bank and link their debit card to it. These cards are accepted at most retail stores, restaurants, and online platforms for shopping and bill payments. SEPA Debit Cards offer security, convenience, and protection against fraud. They support contactless payments, enhancing the speed and ease of small purchases. Overall, the popularity of SEPA Debit Cards in Belgium stems from their widespread acceptance and their ability to provide secure and efficient payment options directly from bank accounts. ## Accepting International Card Payments in Germany Whether you sell to customers in Germany from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards have low penetration in Germany compared to SEPA Direct Debit, PayPal, and Klarna -- multi-method checkout is essential. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Germany, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Germany as a Platform For software platforms serving merchants in Germany, supporting local payment methods like SEPA, Giropay, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Germany? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-indonesia/ --- # Payment Methods in Indonesia: GoPay, OVO & Bank Transfers (2026) | Shuttle > Discover Indonesia's top payment methods including GoPay, OVO, bank transfers, virtual accounts, and credit cards for Southeast Asia's largest digital... # Payment Methods in Indonesia: GoPay, OVO & Bank Transfers (2026) By Nick Dunse, January 25, 2022 Discover Indonesia's top payment methods including GoPay, OVO, bank transfers, virtual accounts, and credit cards for Southeast Asia's largest digital... Start collecting payments today Send payment links to your customers in Indonesia -- no card machine, no website, no fuss. Indonesia, a vibrant hub of digital innovation, showcases a rich tapestry of popular digital payment methods that cater to diverse consumer needs. The landscape extends beyond e-wallets, with online banking and bank transfers playing a pivotal role. Major players like Bank Mandiri, Bank Central Asia (BCA), and Bank Rakyat Indonesia (BRI) lead the charge, offering robust digital services for payments and transfers. For businesses eyeing the Indonesian market, a strategic imperative emerges - the integration of these local payment methods into their e-commerce platforms or mobile applications. This move ensures a frictionless payment experience for consumers, positioning businesses to harness the vast potential of Indonesia's burgeoning e-commerce sector. As the digital payment ecosystem continues to evolve, embracing these diverse options is key to unlocking success in one of Southeast Asia's most dynamic markets. ## Popular offline payment methods in Indonesia ### Cash ### Bank Transfers ### ATM Transfers Over-the-Counter Transfers (OTC) ### Mobile Banking ### Payment at Convenience Stores ### Payment via Agents ### Cheques ### Convenience Stores ## List of payment methods in Indonesia Convenience stores are prevalent in nearly every neighborhood, offering accessibility that enables quick and easy payments without the need for extensive travel. Not only do they provide a variety of products such as groceries, snacks, beverages, household items, and mobile phone credits, but they also cater to different payment preferences. Customers can conveniently pay in cash or opt for electronic methods like debit cards, credit cards, and mobile payment apps like GoPay or OVO. This flexibility accommodates diverse financial situations. Beyond retail, these stores act as payment hubs for bills and utilities, allowing customers to settle electricity, water, internet, and phone bills. This service proves beneficial for those without online banking access or those who prefer in-person bill payments. Additionally, convenience stores often collaborate with e-commerce platforms and delivery services, offering customers the option to pay at a nearby store when picking up online orders. In summary, Indonesia's convenience stores serve as a widely accessible and convenient payment solution, boasting widespread availability, versatile payment options, and the capability to facilitate various transactions, making them a preferred choice among consumers in the country. DOKU VA (Virtual Account) stands out as a widely embraced payment solution in Indonesia, finding extensive usage among individuals and businesses engaging in online transactions. Facilitating payments through diverse channels such as internet banking, mobile banking, and ATMs, DOKU VA enhances the online shopping experience. Users opting for DOKU VA select it as their preferred payment method during the checkout process, receiving a unique virtual account number to transfer funds seamlessly from their bank account to the merchant's account. This method delivers numerous benefits for both consumers and merchants. Consumers appreciate its secure and convenient alternative to credit cards, enabling them to monitor payment history and receive real-time notifications. Merchants value DOKU VA for its reliability, easy integration into existing systems, and access to a vast customer base in Indonesia, supported by most major banks in the country. Overall, DOKU VA has evolved into a pivotal payment method in Indonesia, contributing significantly to the growth of e-commerce and establishing itself as a crucial component of the digital economy. DOKU Wallet, widely embraced in Indonesia, stands out as a favored payment solution for online transactions and payments, enjoying broad acceptance across various e-commerce platforms, online merchants, and service providers in the country. To utilize DOKU Wallet, individuals must establish an account and link it to their bank account or credit card, thereafter replenishing their wallet balance through diverse methods like bank transfer, ATM transfer, or cash deposit at designated locations. Once funded, users can employ DOKU Wallet for payments on websites or mobile apps supporting this method, simply opting for it during checkout and providing their DOKU Wallet login details to finalize the transaction. Boasting security and convenience, DOKU Wallet eliminates the necessity of entering bank or credit card details for every transaction, offering users additional features such as bill payments, money transfers, and mobile top-ups. Overall, DOKU Wallet stands as a trusted and convenient payment avenue in Indonesia, ensuring a secure online payment experience for users. Go Pay, a widely embraced digital wallet and payment solution in Indonesia, is under the ownership of Gojek, a versatile platform providing services ranging from ride-hailing to food delivery. This digital wallet facilitates seamless transactions for a diverse array of products and services, both online and offline. Users can employ Go Pay to settle expenses related to transportation, including Gojek rides and GoCar rentals, as well as for ordering food from restaurants affiliated with Gojek. Its versatility extends to in-store purchases at establishments accepting Gojek payments, requiring users to scan the merchant's QR code through the Gojek app and confirm the transaction. Beyond transport and dining, Go Pay accommodates bill payments, phone credit top-ups, online shopping, and peer-to-peer transfers to fellow Go Pay users. To utilize Go Pay, individuals must download the Gojek app, establish an account, and link their bank account or credit card to fund their Go Pay account. Topping up balances is convenient through various outlets, such as convenience stores or online banking. Overall, Go Pay presents a user-friendly and widely embraced payment alternative in Indonesia, streamlining the payment process for a myriad of goods and services. ### DANA DANA, introduced in 2018 by PT Elang Mahkota Teknologi Tbk (Emtek Group), has emerged as a widely embraced digital wallet and payment solution in Indonesia. Enabling a spectrum of transactions, including online and offline payments, money transfers, bill settlements, and mobile top-ups, DANA allows users to connect their accounts to banks or credit cards for easy fund additions. For online transactions, users can opt for DANA as their payment method on participating platforms, redirecting to the DANA app to finalize the payment with a PIN or biometric verification. Offline payments involve scanning QR codes at affiliated merchants, deducting the specified amount from the DANA wallet. The platform extends beyond payments, featuring DANA Cashback, providing users with rewards for future use or transfer to their bank accounts. Beyond payments, DANA collaborates with various financial institutions to offer services like loans, insurance, and investment products. Its popularity in Indonesia stems from its user-friendly nature, broad acceptance among merchants, and enticing promotions, positioning it as a prominent player alongside competitors like GoPay and OVO in the country's digital wallet landscape. ### Mastercard Mastercard is widely embraced as a payment option across Indonesia, with acceptance spanning retail stores, restaurants, hotels, and online platforms. Its utilization ensures transactional convenience and security, applicable not only at local but also international establishments. Employing Mastercard in Indonesia is a straightforward process, involving the presentation of the card to the merchant or online input of card details, with some vendors requiring a PIN for added security. The card extends beyond basic functionality, featuring additional perks such as cashback incentives, discounts, travel insurance, and access to airport lounges for cardholders in Indonesia. It's essential to recognize that, despite Mastercard's extensive acceptance, smaller vendors or remote areas may still prefer cash. Carrying some cash as a backup is advised. In summary, opting for Mastercard as a payment method in Indonesia ensures a secure and convenient means of conducting both in-store and online transactions. ### Visa Visa is widely acknowledged as a prevalent payment option, accepted at numerous hotels, restaurants, and stores that facilitate credit card transactions. Additionally, Visa cards prove useful for online acquisitions and cash withdrawals from ATMs. To utilize Visa in Indonesia, one must possess a Visa card issued by a bank or financial institution, and it is advisable to notify the bank about travel plans to prevent any complications while using the card overseas. When conducting Visa transactions, individuals may be prompted to input their PIN or furnish a signature for authentication. Some establishments might also necessitate presenting identification, such as a passport or driver's license, when utilizing a Visa card. Although Visa is broadly embraced in major cities and tourist destinations in Indonesia, smaller establishments and remote areas may only accept cash. Therefore, it is prudent to carry Indonesian Rupiah for such situations. Overall, employing Visa as a payment method in Indonesia is convenient and widely accepted, facilitating seamless transactions for travelers throughout their stay. ### PayPal PayPal, a widely utilized online payment service facilitating secure transactions over the internet, is popular in numerous countries, including neighboring ones like Singapore and Malaysia. Regrettably, it is currently unavailable as a payment option in Indonesia. Nevertheless, Indonesia has embraced alternative online payment methods like GoPay, OVO, and DANA, which serve as digital wallets enabling users to conduct online transactions and money transfers securely. Although PayPal isn't a prevalent local payment option, some Indonesian online merchants and e-commerce platforms may offer it for international transactions. In such instances, users can link their PayPal accounts to local bank accounts or credit cards for seamless payments. It's essential to note that the availability of PayPal in Indonesia may evolve in the future as the service continues its global expansion. ## Accepting International Card Payments in Indonesia Whether you sell to customers in Indonesia from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. GoPay, OVO, DANA, and bank transfers dominate Indonesian e-commerce -- international cards alone leave most customers unable to pay. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Indonesia, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Indonesia as a Platform For software platforms serving merchants in Indonesia, supporting local payment methods like GoPay, OVO, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Indonesia? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-italy/ --- # Payment Methods in Italy: Cards, PostePay & Bancomat (2026) | Shuttle > Explore Italy's most popular payment methods from credit cards and PostePay to Bancomat, PayPal, and the growing adoption of digital wallets and BNPL... # Payment Methods in Italy: Cards, PostePay & Bancomat (2026) By Nick Dunse, February 13, 2026 Explore Italy's most popular payment methods from credit cards and PostePay to Bancomat, PayPal, and the growing adoption of digital wallets and BNPL... Start collecting payments today Send payment links to your customers in Italy -- no card machine, no website, no fuss. French consumers exhibit distinct preferences and behaviors in the realm of online shopping. Notably, the use of bank cards, encompassing both credit and debit cards, stands out as the predominant payment method, with the local Cartes Bancaires system and international players like Visa and Mastercard being widely embraced. Despite the popularity of smartphones in France, the majority of online shoppers still favor using laptops or desktops for their transactions. The e-commerce market in the country is poised for robust growth, with projections indicating a value of $106.50 billion by 2023. Furthermore, French online shoppers display a noteworthy spending pattern, averaging over 2,200 EUR per year on their digital purchases. These trends collectively signify a mature and thriving e-commerce landscape in France, underscored by a strong inclination towards card payments, presenting a substantial opportunity for businesses to capitalize on this flourishing market. ## Popular offline payment methods in France ### Cash ### Cheques ### Carte Bancaire ### Bank Transfers ### Meal Vouchers ### Mobile Payments ### Prepaid Cards ### Mandate ## List of payment methods in France ### Cartes Bancaires Cartes Bancaires (CB), the predominant payment method in France, functions as a versatile debit and credit card system issued by French banks. Employing chip and PIN technology for enhanced security, CB cards are widely embraced by merchants for both online and in-person transactions. To complete a payment, users simply insert their card into a terminal and enter their PIN, while online purchases can be facilitated through card details entry on websites or secure payment gateways. CB cards enjoy broad acceptance at major establishments like retailers, restaurants, hotels, and ATMs, making them a convenient choice for diverse financial transactions. While other international options like Visa and Mastercard are also prevalent, it is prudent to confirm with merchants in advance regarding their preferred payment methods. ### Visa Visa is widely accepted as a payment method in France. It can be used at most retail stores, restaurants, hotels, and online merchants. Visa cards are also accepted at ATMs for cash withdrawals. ### Mastercard Mastercard is widely accepted as a payment method in France. It can be used at most retail stores, restaurants, hotels, and online merchants throughout the country. Mastercard is also accepted at ATMs for cash withdrawals. ### PayPal PayPal is widely accepted as a payment method in France. Many online retailers and service providers in France offer PayPal as an option for customers to make payments. Additionally, PayPal can be used for international transactions, making it convenient for French customers to shop from overseas websites. PayPal offers secure and easy payment processing, allowing customers to make purchases without sharing their financial information with the merchant. Overall, PayPal is a popular and trusted payment method in France. ### Maestro Maestro is a widely accepted payment method in France. It is a debit card issued by Mastercard and can be used for both online and offline purchases. Maestro cards are accepted at most merchants in France, including supermarkets, restaurants, and shops. They can also be used to withdraw cash from ATMs. To use Maestro as a payment method, simply present your card at the point of sale or enter the card details when making an online purchase. ### American Express American Express is widely accepted as a payment method in France. Many merchants, including restaurants, hotels, and retail stores, accept American Express cards. However, it is worth noting that American Express may not be as widely accepted as Visa or Mastercard in some smaller establishments or outside of major cities. It is always a good idea to carry an alternative form of payment, such as a Visa or Mastercard, when traveling in France. In France, meal vouchers, known as tickets restaurant, are a widespread method of payment for meals, often included in employees' benefits packages. These vouchers, usually provided in paper form, can be used at various establishments such as restaurants, cafes, food delivery services, and even grocery stores. The value of these vouchers, determined by the employer, is generally tax-exempt up to a specified amount and has an expiration date. When used, the voucher is presented to the cashier or server, who deducts its value from the total bill; any remaining amount can be paid with other forms of payment. It's important to note that meal vouchers can't be converted to cash and must be used for their designated purpose. However, not all establishments accept them, necessitating prior confirmation. Overall, meal vouchers offer a convenient and popular tax-free benefit for employees, facilitating the enjoyment of meals at a variety of places in France. ### Klarna Klarna is a popular payment method in France, allowing customers to buy now and pay later. It offers flexible payment options, such as paying in installments or deferring payments for a certain period of time. Klarna is accepted by many online retailers in France, making it convenient for customers to shop and pay for their purchases. The payment process is simple and secure, with customers being able to complete their transactions quickly and easily. Klarna also provides customer support in France, ensuring that any issues or questions are addressed promptly. Overall, Klarna is a convenient and popular payment method for customers in France. Oney is a prominent payment method in France, serving as a financial services company that delivers a range of payment solutions, encompassing credit cards, installment payments, and revolving credit. Renowned for its wide acceptance, Oney credit cards are utilized for both online and in-store transactions, providing users with advantages like cashback rewards, discounts, and adaptable payment choices. Beyond credit cards, Oney facilitates installment payment plans for substantial purchases, enabling customers to distribute the expense over several months. Furthermore, the company extends revolving credit, permitting users to borrow within a specified limit and repay gradually with added interest. In essence, Oney stands out as a versatile and widely embraced payment option in France, offering customers diverse means to manage payments and enhance the affordability of their purchases. Diners Club International operates as a global payment network, providing credit cards to customers worldwide, including in France. In the country, Diners Club cards are widely accepted at various establishments such as restaurants, hotels, and retail stores. To use the card, customers can present it at the point of sale, where it can be swiped or inserted into a card reader, and additional authorization may be required through a PIN or signature. While Diners Club cards enjoy broad acceptance in France, particularly at larger and international establishments, it is advisable for customers to verify acceptance with specific merchants. In addition to physical locations, Diners Club cards can also be utilized for online purchases on e-commerce websites, offering customers a convenient and secure payment option for transactions in both physical and virtual settings. Amazon Pay is a popular payment method in France. It allows customers to make purchases on Amazon.fr and other participating websites using their Amazon account information. With Amazon Pay, customers can securely pay for their purchases without having to enter their payment and shipping information each time. This makes the checkout process quick and convenient. Additionally, Amazon Pay offers buyer protection and fraud detection measures to ensure a safe shopping experience for customers. Overall, Amazon Pay is a trusted and widely used payment method in France. ### UnionPay UnionPay is accepted as a payment method in France. It is widely accepted at many merchants, including hotels, restaurants, and retail stores. UnionPay cards can be used for both online and in-store purchases. Additionally, UnionPay has partnered with local banks in France to offer cardholders additional benefits and services. ### Discover Discover is not widely accepted as a payment method in France. The most commonly accepted payment methods in France are cash, debit cards (Carte Bleue), and credit cards (Visa and Mastercard). Some businesses may accept Discover cards, but it is not as widely accepted as other card networks. It is always a good idea to have alternative payment methods available when traveling to France. ### Apple Pay Apple Pay, a mobile payment and digital wallet service by Apple Inc., is widely accepted in France at numerous retailers, online merchants, and apps, including Carrefour, Fnac, Sephora, Monoprix, Uber, Deliveroo, Airbnb, and Booking.com. To utilize Apple Pay, users in France must add their credit or debit cards to the Wallet app on their Apple devices, either through the app directly or via the Settings app. Once added, payments can be made in-store by holding the device near a contactless terminal and authenticating with Touch ID or Face ID. For online transactions, users select Apple Pay and authenticate using the same biometric features. The service extends to person-to-person payments through the Messages app with Apple Pay Cash. Overall, Apple Pay offers a secure and convenient payment method for users in France across a diverse range of transactions. ### JCB JCB, or Japan Credit Bureau, serves as a popular payment method in France, finding acceptance across various establishments such as restaurants, hotels, and retail stores. To utilize JCB for transactions in the country, one needs a JCB card issued by a supporting financial institution, which can be verified with one's bank or credit card provider. Once in possession of a JCB card, transactions are straightforward -- present the card at the point of sale, follow merchant instructions, and, if necessary, enter a PIN or sign a receipt. While JCB enjoys broad acceptance, there may still be occasional non-participating merchants, underscoring the importance of checking in advance or having an alternative payment option on hand. Overall, the convenience and widespread acceptance of JCB in France make it a favored choice for both residents and visitors. ### Alipay Alipay, the widely-used Chinese mobile payment platform, has expanded its reach to France, enabling Chinese tourists and residents in the country to utilize the app for purchases at participating merchants. To avail this service, users must possess a registered Alipay account and link it to a bank card, after which they can scan a merchant-provided QR code through the Alipay app to complete transactions. This move aligns with Alipay's global expansion strategy, aiming to serve the increasing number of Chinese tourists abroad by allowing them to make transactions in their preferred currency without the need for physical cash. Beyond payments, Alipay offers diverse services such as money transfers, bill payments, and travel bookings, consolidating its position as a comprehensive platform for Chinese users. French merchants accepting Alipay stand to gain by attracting more Chinese customers, tapping into the lucrative Chinese market, and leveraging Alipay's marketing tools for promotions and discounts, ultimately creating a mutually beneficial scenario that enhances convenience for Chinese users and boosts sales for local businesses. ### WeChat Pay WeChat Pay, a widely used mobile payment method in China, has limited acceptance in France, primarily found in establishments catering to Chinese tourists or possessing a substantial Chinese clientele. To utilize WeChat Pay in France, users must have a WeChat account linked to their bank account or credit card, enabling payments through the app by scanning QR codes or entering payment codes. Notable locations accepting WeChat Pay include luxury retailers such as Galeries Lafayette and Printemps, prominent tourist sites like the Louvre Museum and the Palace of Versailles, as well as select hotels, restaurants, and transportation services. However, its acceptance remains less pervasive compared to traditional methods like credit cards or cash in France, necessitating alternative payment options for travelers in the country. ### Google Pay Google Pay is available as a payment method in France. Users can add their credit or debit cards to the Google Pay app and use it to make payments at participating merchants. They can also use Google Pay to make online purchases and send money to friends and family. Google Pay is supported by a wide range of banks and financial institutions in France, making it a convenient and secure way to make payments. PaySafeCard is a prepaid online payment method available in France, offering a secure and anonymous option for users to make payments without requiring a bank account or credit card. Users can purchase physical cards from authorized retailers, each equipped with a unique 16-digit PIN code for transactions on various online platforms, including gaming, gambling, and e-commerce websites. Additionally, an online account with PaySafeCard allows users to buy virtual cards or vouchers directly from the website, eliminating the need for a physical card. Widely accepted in France, PaySafeCard provides a convenient and secure means of online payment on popular platforms like Amazon, eBay, and Steam, ensuring privacy by not requiring the sharing of personal or financial information. SEPA Direct Debit is a prevalent payment method in France, enabling businesses to effortlessly collect payments directly from customers' bank accounts, particularly for recurring expenses like utility bills and subscriptions. Businesses secure a mandate from customers, granting authorization for direct debit collection, obtainable through either a paper form or electronically. Transactions are facilitated via the SEPA system, ensuring smooth cross-border payments within the Eurozone. This method streamlines payment processes for businesses, enhancing security, efficiency, and cash flow management while reducing administrative costs and minimizing the risks associated with cash and checks. Customers benefit from the convenience of automatic deductions on due dates, eliminating concerns about late fees and the need to remember payment deadlines. Overall, SEPA Direct Debit is a trusted and widely adopted payment option in France, offering advantages for both businesses and customers in the realm of recurring payments. ## Accepting International Card Payments in Italy Whether you sell to customers in Italy from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards and PayPal are common in Italy but PostePay, Bancomat, and Klarna are increasingly important at online checkout. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Italy, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Italy as a Platform For software platforms serving merchants in Italy, supporting local payment methods like SEPA, Bancomat, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Italy? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-japan/ --- # Payment Methods in Japan: Credit Cards, Konbini & IC Cards (2026) | Shuttle > Discover Japan's most popular payment methods from credit cards and convenience store payments to mobile wallets, IC cards, and bank transfers. # Payment Methods in Japan: Credit Cards, Konbini & IC Cards (2026) By Nick Dunse, February 13, 2026 Discover Japan's most popular payment methods from credit cards and convenience store payments to mobile wallets, IC cards, and bank transfers. Start collecting payments today Send payment links to your customers in Japan -- no card machine, no website, no fuss. The e-Commerce market in Japan is flourishing, marked by extensive internet and online banking usage. To successfully penetrate this market, businesses should prioritize incorporating popular payment methods like credit cards (including JCB), online banking, and cash payments through convenience stores. The key to success lies in accommodating the diverse preferences of Japanese consumers, enhancing accessibility, and thereby capitalizing on the substantial consumer base in the country. ## Popular offline payment methods in Japan ### Cash ### Debit Cards ### Prepaid Cards ### Convenience Stores ### Smartphone Payments ### Electronic Money (e-Money) ## List of payment methods in Japan ### Visa Visa is extensively recognized as a widely accepted payment method in Japan, applicable at major retailers, restaurants, hotels, and various establishments. Even smaller businesses and local shops often welcome Visa, although cash or alternative payment methods may be required in some instances. Visa cards are versatile for both in-person and online transactions, with the customary requirement of inserting or swiping the card and entering a PIN for verification; contactless payments via Visa payWave or payPass are also options in some places. While widespread, it's essential to be aware that certain establishments may not accept credit cards or may impose minimum purchase requirements. Carrying cash is advisable, particularly in smaller towns or rural areas where card acceptance may be limited. It's prudent to notify your bank or credit card company about your travel plans beforehand to prevent potential issues with fraud protection measures. ### Mastercard Mastercard is widely accepted as a payment method in Japan. It can be used at most major retailers, restaurants, hotels, and other establishments throughout the country. Many smaller shops and businesses may not accept credit cards, so it is always a good idea to carry some cash as well. Additionally, some places may only accept certain types of Mastercards, such as those with an EMV chip. It is always a good idea to check with the establishment beforehand to ensure that they accept Mastercard as a form of payment. ### JCB JCB (Japan Credit Bureau) stands out as a prominent payment method in Japan, being one of the largest credit card issuers with broad acceptance across the country. The versatile JCB cards facilitate transactions ranging from online shopping and in-store purchases to cash withdrawals at ATMs. Widely embraced by diverse merchants, including department stores, supermarkets, restaurants, and convenience stores, JCB cards offer cardholders enticing benefits such as discounts, cashback, and exclusive event access. Beyond transactional perks, JCB extends additional services like travel insurance, concierge assistance, and airport lounge access, catering to the needs of both local and international users. Notably, JCB has expanded its global footprint, with millions of merchants worldwide now accepting their cards, enhancing the convenience for Japanese travelers abroad. Overall, JCB's extensive acceptance network, coupled with its array of benefits, establishes it as a popular and practical payment choice in Japan for domestic and international transactions alike. ### American Express American Express is widely accepted as a payment method in Japan. Many merchants, including hotels, restaurants, and shops, accept American Express cards. However, it is worth noting that not all businesses in Japan accept American Express, especially smaller establishments or local shops. It is always a good idea to carry alternative payment methods, such as cash or other major credit cards like Visa or Mastercard, just in case. Additionally, it is recommended to inform your bank or credit card company of your travel plans to ensure that your card will work smoothly while you are in Japan. Pay Easy is a widely embraced online banking payment method in Japan, enabling customers to conduct transactions directly from their bank accounts, eliminating the necessity for credit cards or cash. Accepted by a diverse array of online merchants, including e-commerce platforms, utility companies, and government agencies, Pay Easy requires users to possess an online banking account with a participating bank. During the checkout process, customers can opt for Pay Easy as their payment method, initiating a secure redirection to their bank's online portal for authentication and authorization. The completed transaction redirects the customer back to the merchant's site. This method not only furnishes customers with a secure and hassle-free means of online payment but also allows for easy tracking and management of transactions through their online banking accounts. For merchants, incorporating Pay Easy enhances sales opportunities by providing a popular alternative payment option in Japan, while concurrently mitigating the risks of chargebacks and fraud associated with credit card payments. Ultimately, Pay Easy stands out as a favored and convenient online banking payment solution with mutual benefits for both customers and merchants in the Japanese market. ### UnionPay UnionPay is a highly prevalent and convenient payment method in Japan, accepted at major retailers, hotels, restaurants, and tourist attractions for both online and offline transactions. To utilize UnionPay, individuals can look for the UnionPay logo or inquire with the merchant about its acceptance. The process involves presenting the UnionPay card to the cashier or following specified instructions for online payments. Additionally, some merchants in Japan support UnionPay mobile payments like QuickPass and Apple Pay, enabling contactless transactions through smartphones. Despite its widespread acceptance, there might be smaller establishments that do not accommodate UnionPay, emphasizing the importance of carrying cash or having alternative payment methods. Overall, UnionPay facilitates seamless transactions for travelers in Japan, enhancing their convenience and enjoyment during their stay. ### WeChat Pay WeChat Pay, a widely used mobile payment service in China, has expanded its reach to countries such as Japan, where it is gaining popularity, particularly among Chinese tourists and residents. In Japan, WeChat Pay is accepted at various establishments, including retail stores, restaurants, and online platforms. To utilize this payment method, users must have a WeChat account and link their bank card to it. Transactions are facilitated through the WeChat app by scanning QR codes at participating merchants. Additionally, users can transfer money locally or internationally within the WeChat network. The convenience and security of WeChat Pay have made it a favored choice in Japan, particularly for individuals familiar with the app from their home country or those who frequently travel to China. As a result, many businesses in popular tourist areas and shopping districts now embrace WeChat Pay to meet the payment preferences of Chinese customers. ### Alipay Alipay, the widely used Chinese mobile payment platform, has extended its services to Japan through partnerships with local merchants and businesses. To utilize Alipay in Japan, users must have a registered Alipay account and download the mobile app, linking it to their Japanese bank account or credit card for transactions. Accepted at diverse locations including retail stores, restaurants, hotels, and tourist attractions, Alipay streamlines payments through QR code scans and confirmation within the app. The platform also offers perks in Japan, such as discounts from participating merchants and access to services like transportation and ticketing. Overall, Alipay provides a convenient and secure payment solution for Chinese tourists and residents in Japan, enabling seamless transactions through their preferred mobile payment method. Apple Pay quickly established itself as a leading mobile payment service in the country. Enabling users to make seamless transactions with their iPhone, Apple Watch, or iPad, the service is supported by major credit card companies and prominent banks such as Visa, Mastercard, American Express, Sumitomo Mitsui, Mizuho, and Rakuten. A notable feature is its integration with Suica, a popular contactless payment system used for public transportation and retail in Tokyo and other major cities. Users can add their Suica card to Apple Pay, facilitating payments for transportation and purchases at various outlets. Beyond physical stores, the service extends to online platforms, allowing users to make secure transactions with the ease of Touch ID or Face ID authentication. The success of Apple Pay in Japan is attributed to its convenience, security, and the country's existing adoption of contactless payment systems like Suica, contributing to the widespread acceptance of mobile payments through Apple devices. Diners Club International is a widely embraced payment option in Japan, accepted at numerous restaurants, hotels, and retail establishments both online and offline. The convenience of Diners Club cards makes them a popular choice for both residents and travelers. To utilize the card in Japan, one can simply present it at the point of sale or enter the details for online purchases, with many establishments displaying the Diners Club logo to signify acceptance. However, it's important to note that while Diners Club is widely accepted, it may not be as pervasive as major credit cards like Visa or Mastercard, emphasizing the importance of carrying alternative payment methods when in Japan. Additionally, users are advised to check with their bank or credit card issuer beforehand to ensure there are no foreign transaction fees or other restrictions associated with international card usage. ### Discover Discover, the American payment system, has recently made its way into the Japanese market. This move is expected to provide more options for consumers and merchants alike. With Discover's arrival, Japanese consumers can now enjoy the benefits of using a globally recognized payment system that offers cashback rewards and other perks. For merchants, Discover's presence means access to a wider customer base and increased revenue. This development is a significant step towards promoting cashless transactions in Japan, which has been a long-standing goal of the government. As Discover continues to expand its reach in Japan, it is expected to bring about positive changes in the country's payment landscape. ### Google Pay Google Pay is available as a payment method in Japan. Users can link their credit or debit cards to their Google Pay account and use it to make payments at various merchants and online platforms that accept Google Pay. Additionally, users can also add their Suica or WAON cards to Google Pay for contactless payments at compatible terminals. Google Pay also supports in-app purchases and peer-to-peer transfers within Japan. ### PayPal PayPal is widely embraced as a versatile payment method, accepted by numerous online retailers, both domestic and international. It serves as a convenient option for customers to make purchases, extending its utility beyond online transactions to encompass peer-to-peer payments and domestic money transfers. To leverage PayPal's services in Japan, individuals must establish a PayPal account, linking it to their bank account or credit card. Once set up, users can seamlessly make payments by choosing the PayPal option during checkout on participating websites or by directly transferring funds to another PayPal user. The availability of a mobile app for iOS and Android devices further enhances accessibility, enabling users to make payments and transfers on the move. Overall, PayPal offers a secure and user-friendly solution for facilitating online transactions and monetary transfers in Japan. ## Accepting International Card Payments in Japan Whether you sell to customers in Japan from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Credit cards are widespread in Japan but Konbini convenience-store payments and Pay-easy are still expected for many online transactions. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Japan, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Japan as a Platform For software platforms serving merchants in Japan, supporting local payment methods like Konbini payments, JCB, and bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Japan? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-japan-2/ --- # Redirecting to: /blog/the-most-popular-payment-methods-in-japan/ ## Links - [Redirecting from to](/blog/the-most-popular-payment-methods-in-japan/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-kenya/ --- # Payment Methods in Kenya: M-Pesa, Cards & Mobile Money (2026) | Shuttle > M-Pesa dominates payments in Kenya. Discover all popular payment methods including mobile money, bank transfers, and digital wallets for East African... # Payment Methods in Kenya: M-Pesa, Cards & Mobile Money (2026) By Nick Dunse, February 14, 2026 M-Pesa dominates payments in Kenya. Discover all popular payment methods including mobile money, bank transfers, and digital wallets for East African... Start collecting payments today Send payment links to your customers in Kenya -- no card machine, no website, no fuss. Transitioning from cash to digital payments in Kenya's e-commerce sector offers significant advantages. Digital payments provide convenience, enhance safety and security, promote financial inclusion, result in cost savings for businesses, generate valuable data insights, facilitate cross-border trade, and improve government revenue collection through a digital trail. To make this transition successful, collaboration among government agencies, financial institutions, e-commerce platforms, and mobile network operators is essential. Overcoming challenges such as infrastructure development, consumer education, and regulatory frameworks will unlock the full potential of Kenya's e-commerce sector, fostering economic growth. ## Popular offline payment methods in Kenya ### Cash ### Mobile Money ### Bank Transfers ### Cheques ### Point of Sale (POS) Machines ### Prepaid Cards Electronic Funds Transfer (EFT) Paybill and Buy Goods Services ## List of payment methods in Kenya M-PESA is a mobile money transfer service that allows users to send and receive money, pay bills, and make purchases using their mobile phones. Airtel Money is a mobile money transfer service offered by Airtel Kenya. Equitel is a mobile banking platform offered by Equity Bank. Users can send and receive money, pay bills, and access other banking services through their Equitel SIM card. Co-operative Bank of Kenya offers a mobile banking service that allows users to access their bank accounts, transfer funds, pay bills, and make purchases using their mobile phones. This is a partnership between Kenya Commercial Bank (KCB) and Safaricom's M-Pesa. Users can access banking services such as savings accounts, loans, and insurance through their KCB M-Pesa account. PesaLink is a real-time interbank money transfer service that allows users to send and receive money between different banks in Kenya. ### PayPal PayPal is an online payment platform that allows users to make payments and transfer funds internationally. Kenyan users can link their PayPal accounts to their local bank accounts for easy withdrawal and deposit of funds. ### Visa Visa is widely accepted as a payment method in Kenya. It can be used for both online and offline transactions, including shopping, dining, and other services. Many businesses, including hotels, restaurants, and retail stores, accept Visa cards. Additionally, Visa cards can be used to withdraw cash from ATMs in Kenya. MasterCard is extensively utilized as a payment option in Kenya, accepted at diverse establishments including supermarkets, restaurants, hotels, and online retailers. Numerous banks in the country issue MasterCard debit and credit cards, facilitating easy payments. The process involves presenting the card at the point of sale or entering details for online transactions, with some merchants supporting contactless payments. MasterCard prioritizes security, incorporating features like EMV chip technology and tokenization to safeguard against fraud and unauthorized transactions. Beyond retail transactions, MasterCard can be used to withdraw cash from ATMs in Kenya, though fees may apply. In essence, MasterCard offers a secure and convenient payment solution for individuals in Kenya, enabling both local and international purchases. ### American Express American Express is another popular payment method in Kenya, similar to Visa. It offers credit cards and allows users to make payments at a wide range of merchants and service providers. Diners Club International is a payment method that is accepted at select merchants in Kenya. It offers credit cards that can be used for making payments both online and offline. ### UnionPay UnionPay is a popular payment method in Kenya, especially among Chinese tourists and businesses. It allows users to make payments using UnionPay cards at various merchants and service providers. Equity Bank EazzyPay is a mobile payment platform offered by Equity Bank in Kenya. It allows users to make payments using their mobile phones at various merchants and service providers. Co-operative Bank MCo-op Cash is a mobile payment platform offered by Co-operative Bank of Kenya. It allows users to make payments using their mobile phones at various merchants and service providers. ### Google Pay Google Pay is a digital wallet platform that allows users to make payments using their mobile phones. It is accepted at select merchants in Kenya. ### Apple Pay Apple Pay is a mobile payment and digital wallet service offered by Apple. It allows users to make payments using their iPhones, iPads, and Apple Watches at select merchants in Kenya. ### Samsung Pay Samsung Pay is a mobile payment and digital wallet service offered by Samsung. It allows users to make payments using their Samsung smartphones at select merchants in Kenya. ## Accepting International Card Payments in Kenya Whether you sell to customers in Kenya from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. M-Pesa is the default for most Kenyan consumers -- but international card acceptance still matters for cross-border sales. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Kenya, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Kenya as a Platform For software platforms serving merchants in Kenya, supporting local payment methods like M-Pesa and mobile money is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Kenya? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-malaysia/ --- # Payment Methods in Malaysia: FPX, GrabPay & Credit Cards (2026) | Shuttle > Discover Malaysia's top payment methods including FPX online banking, GrabPay, Boost, credit cards, and e-wallets driving digital commerce growth. # Payment Methods in Malaysia: FPX, GrabPay & Credit Cards (2026) By Nick Dunse, April 6, 2021 Discover Malaysia's top payment methods including FPX online banking, GrabPay, Boost, credit cards, and e-wallets driving digital commerce growth. Start collecting payments today Send payment links to your customers in Malaysia -- no card machine, no website, no fuss. In Malaysia, alongside traditional payment methods, the adoption of mobile payment solutions is on the rise, with popular apps like GrabPay, Boost, Touch 'n Go eWallet, and Samsung Pay gaining prominence. The country's e-commerce sector is experiencing rapid growth, with platforms such as Lazada, Shopee, and Zalora becoming increasingly popular and offering a diverse range of products and services. Malaysians are also turning to online platforms for convenient bill payments, including utilities and insurance premiums, allowing for efficient financial management from home. Despite the surge in digital payments, cash remains widely used for everyday transactions, particularly among small businesses and street vendors who favor its convenience and lower transaction fees. The payments landscape in Malaysia is characterized by a diverse mix of traditional methods like credit cards and cash alongside newer options, and as technology advances and consumer preferences evolve, digital payment methods are expected to continue gaining traction in the country. ## Popular offline payment methods in Malaysia ### Cash ### Cheques ### Direct Bank Transfers ### ATM Transfers ### Bank Drafts ### Money Orders ### Prepaid Cards ### QR Code Payments ### Debit Cards ## List of payment methods in Malaysia ### Visa Visa is widely accepted as a payment method in Malaysia. It can be used at most retail stores, restaurants, hotels, and online merchants. Visa cards are also accepted at ATMs for cash withdrawals. Additionally, many Malaysians use Visa for online shopping and bill payments. ### Apple Pay Apple Pay, a mobile payment and digital wallet service by Apple Inc., was introduced in Malaysia in May 2019, supported by major banks such as Maybank, CIMB, Public Bank, Hong Leong Bank, and RHB Bank. Users can add credit or debit cards from these banks to their Apple Wallet and make contactless payments at participating merchants using iPhone, Apple Watch, iPad, or Mac devices. Compatibility requires the latest iOS or watchOS version, and after adding cards, transactions are authenticated with Touch ID or Face ID. Apple Pay enhances security by using Near Field Communication (NFC) technology, tokenization, and encryption, minimizing the risk of fraud. Its elimination of the need for physical cards and widespread support has contributed to its popularity in Malaysia, offering a secure and convenient alternative to traditional payment methods. ### Mastercard Mastercard is extensively utilized as a payment method in Malaysia, accepted for both online and offline transactions across a variety of establishments, including retail stores, restaurants, hotels, and online platforms. Making a payment with Mastercard involves either presenting the card to the merchant or entering card details for online purchases, with some vendors supporting contactless payments through the tap-and-go feature. The range of Mastercard offerings in Malaysia encompasses credit cards, debit cards, and prepaid cards, each featuring distinct benefits like rewards programs, cashback offers, and travel perks. In addition to physical cards, Mastercard provides virtual cards for secure online transactions, linked to existing accounts. Enhanced security measures, such as EMV chip technology to combat counterfeit fraud and customizable alerts, further contribute to Mastercard's popularity, solidifying its status as a convenient and widely embraced payment option in the Malaysian market. Atome is a buy now, pay later (BNPL) service available in Malaysia, enabling consumers to split their payments into three equal installments over time. To utilize Atome, users must download the app, create an account, and select it as the payment method during checkout at participating merchants. The total purchase amount is divided into three installments, with the first paid upfront and the subsequent two automatically deducted monthly from the user's linked debit or credit card. Atome does not impose interest or fees for its BNPL service, although late payments may result in additional charges. The Atome app facilitates payment management and installment tracking for users. Essentially, Atome serves as an interest-free and fee-free payment alternative, granting Malaysian consumers flexibility in managing their purchases through installment payments. ### GrabPay GrabPay is a widely utilized mobile wallet and payment method in Malaysia, offering a secure and convenient way to pay for services such as transportation, food delivery, and online shopping. To access GrabPay, users must download the Grab app, create an account, and link their bank account or credit/debit card to their GrabPay wallet. Additionally, users can top up their wallet through cash at specified locations or online banking. Once loaded, GrabPay can be used to pay for rides, order food, make online purchases, and transfer money to other GrabPay users. The platform provides users with various promotions, including cashback and transaction discounts, as well as the opportunity to earn GrabRewards points for every transaction, redeemable for discounts or freebies. Overall, GrabPay offers Malaysians a seamless and rewarding payment experience across a diverse array of services. 7-Eleven, a widely popular convenience store chain in Malaysia, provides a range of services, including bill payment for utilities, telecommunications, and credit cards. Customers can make payments by following a simple process: visiting any 7-Eleven store, informing the cashier of their intention to pay a bill, providing necessary details, and paying the amount in cash. The cashier generates a payment slip as proof of payment, which should be retained until the biller confirms receipt. This payment method offers convenience for those without online banking access or who prefer cash transactions. With 7-Eleven's 24/7 availability, customers can make payments outside regular banking hours, enhancing accessibility for a diverse range of users. ### JCB JCB, or Japan Credit Bureau, is a widely embraced payment method in Malaysia, accepted by numerous merchants and online retailers throughout the country. Users can employ JCB credit or debit cards at the point of sale in physical stores, with many establishments prominently displaying JCB logos to signify their acceptance of these cards. The convenience extends to online shopping, where customers can opt for JCB as their payment method and input card details for seamless transactions. JCB cardholders in Malaysia enjoy various perks, including exclusive discounts and promotions at participating merchants, along with special privileges like airport lounge access and travel insurance coverage. Boasting widespread acceptance and offering numerous benefits, JCB has become a favored payment option for both locals and tourists in Malaysia. ### DuitNow DuitNow, offered by Payments Network Malaysia (PayNet), is a prominent payment method in Malaysia enabling users to conduct secure and instantaneous transactions using either their mobile phone numbers or National Registration Identity Card (NRIC) numbers. Users register this information with their respective banks to utilize the service, facilitating swift and hassle-free person-to-person transfers, bill payments, online purchases, and merchant payments. DuitNow's key advantage lies in its user-friendly approach, allowing individuals to make payments without the necessity of sharing or memorizing bank account details, instead relying on their mobile numbers or NRIC numbers. This not only enhances convenience but also bolsters security by minimizing the risk of fraud and unauthorized access to sensitive information. Additionally, DuitNow contributes to financial inclusion by enabling those without a traditional bank account to receive funds directly through their mobile numbers, fostering participation in the digital economy and easing access to financial services. Overall, DuitNow stands as a rapid, convenient, and secure payment solution, streamlining money transfers for Malaysians. ### WeChat Pay WeChat Pay, a widely popular mobile payment method in China, has extended its services to Malaysia, allowing users to make seamless payments through the WeChat app. To utilize WeChat Pay in Malaysia, individuals must have a WeChat account and link their bank or credit card to their WeChat wallet. The payment process involves scanning QR codes at participating merchants, including retail stores, restaurants, online platforms, and utility bill payments. Notable establishments like Watsons, Guardian, and KK Super Mart accept WeChat Pay. While offering convenience for Chinese tourists and residents familiar with the app, WeChat Pay may not be as universally accepted as local alternatives like credit cards or e-wallets such as GrabPay or Touch 'n Go. Therefore, users are advised to confirm a merchant's acceptance of WeChat Pay before making transactions. Touch 'n Go Digital is a widely embraced payment solution in Malaysia, functioning as a digital wallet accessible through a mobile app. Enabling cashless transactions, the system permits users to pay for diverse services, including retail purchases, mobile credit top-ups, and highway tolls. To utilize Touch 'n Go Digital, individuals must download the Touch 'n Go eWallet app, register, and link their bank accounts or credit cards to add funds. Payments are executed by scanning a merchant-provided QR code, deducting the amount from the user's digital wallet with a receipt generated for reference. Accepted at various Malaysian establishments, from retail outlets and restaurants to online platforms and public transportation, the system also facilitates fund transfers and cash withdrawals. Its appeal lies in the convenience of eliminating the need for physical currency or cards, promoting ease of use, and offering enticing promotions and discounts. Touch 'n Go Digital has significantly contributed to the adoption of cashless transactions in Malaysia, reducing reliance on tangible currency throughout the country. ### PayPal PayPal is a widely utilized payment method in Malaysia, offering users a secure and convenient means of making online payments. Users can link their PayPal accounts to their bank accounts or credit cards, enabling them to easily make purchases on various online platforms. To use PayPal in Malaysia, individuals must create and verify their accounts by linking them to their bank accounts or credit cards. Once verified, users can seamlessly utilize PayPal for transactions. Numerous online merchants in Malaysia accept PayPal, allowing users to select it as a payment option during checkout and complete transactions securely without divulging sensitive financial information. Beyond online purchases, PayPal serves as a platform for sending and receiving money between individuals using email addresses or mobile numbers associated with their PayPal accounts. In essence, PayPal provides Malaysians with a secure and hassle-free method for online payments and money transfers, with widespread acceptance among online merchants in the country. Boost Wallet is a popular mobile payment solution in Malaysia, enabling users to conveniently make transactions using their smartphones at a diverse range of merchants, including online stores, physical shops, and street vendors. To utilize Boost Wallet, users must download the app, create an account, and can then fund their wallet by linking it to their bank account or purchasing credits at select retail outlets. Payments are made by scanning the merchant's QR code with the app's built-in scanner, deducting the amount from the user's wallet balance, and generating a receipt for reference. The wallet ensures convenience, security through encryption and optional PIN/biometric authentication, and often rewards users with cashback and discounts at participating merchants, making it an appealing choice for consumers seeking a versatile and incentivized payment method in Malaysia. ### Alipay Alipay, developed by Alibaba Group, is a widely used mobile payment platform in China that has expanded its services to Malaysia. Accepted at various establishments catering to Chinese tourists and expatriates, such as shopping malls, restaurants, hotels, and tourist attractions, Alipay facilitates both in-store and online transactions. Users in Malaysia must register an Alipay account, link it to their bank account or credit card, and can then make payments by scanning QR codes or entering the merchant's Alipay ID. Alipay offers a secure and convenient payment method, with additional perks like promotions and discounts from participating merchants. Despite its growing acceptance, not all Malaysian merchants currently support Alipay, though its popularity is anticipated to rise as more businesses recognize its appeal to Chinese customers. Diners Club International operates as a global payment network providing credit cards to consumers and businesses, with widespread acceptance in Malaysia across various merchants, including restaurants, hotels, retail outlets, and online retailers. To make a payment, cardholders can simply present their Diners Club card at the point of sale, where it can be swiped, inserted into a card reader, or used for contactless transactions. The cards come with benefits such as reward points, travel insurance, and airport lounge access, along with exclusive privileges and discounts at specific merchants. Besides in-store transactions, Diners Club cards are also commonly used for online purchases on e-commerce platforms in Malaysia. Overall, Diners Club serves as a convenient and widely embraced payment method, offering flexibility for both in-person and online transactions in the country. ### Google Pay Google Pay is a digital wallet and online payment system developed by Google, enabling users in Malaysia to make payments through their compatible Android devices. Accessible to various online merchants and service providers, Google Pay requires users to have the app installed, a Google account, and linked payment cards. Accepted cards include credit, debit, and prepaid cards from participating banks. The setup process involves adding payment cards to the app. Once set up, Google Pay facilitates seamless online transactions at supported merchants, allowing users to select it as their payment method during checkout and authenticate payments using device security features. Additionally, Google Pay supports peer-to-peer payments, enabling users to send money to friends and family by entering the recipient's details and amount in the app. Overall, Google Pay provides a secure and convenient solution for digital payments in Malaysia, eliminating the reliance on physical cash or cards and offering a centralized platform for managing payment information. ### UnionPay UnionPay is a highly prevalent and convenient payment method in Malaysia, accepted at major retailers, hotels, restaurants, and online merchants for both offline and online transactions. The widespread acceptance of UnionPay cards facilitates seamless purchases for both locals and tourists. Beyond its broad usability, UnionPay provides cardholders in Malaysia with various promotions and discounts, spanning shopping, dining, travel, and entertainment. To use UnionPay, one simply presents the card at the point of sale or inputs card details for online transactions, with some merchants requiring additional verification like a PIN or signature. In summary, UnionPay's extensive acceptance and promotional offerings make it a user-friendly choice for individuals in Malaysia, ensuring ease and accessibility in their payment experiences. ## Accepting International Card Payments in Malaysia Whether you sell to customers in Malaysia from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. FPX bank transfers and GrabPay dominate Malaysian online payments alongside cards. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Malaysia, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Malaysia as a Platform For software platforms serving merchants in Malaysia, supporting local payment methods like FPX, GrabPay, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Malaysia? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-mexico/ --- # Payment Methods in Mexico: OXXO, SPEI & Credit Cards (2026) | Shuttle > Explore Mexico's top payment methods including OXXO cash payments, SPEI bank transfers, credit cards, and digital wallets for the booming e-commerce... # Payment Methods in Mexico: OXXO, SPEI & Credit Cards (2026) By Nick Dunse, February 14, 2026 Explore Mexico's top payment methods including OXXO cash payments, SPEI bank transfers, credit cards, and digital wallets for the booming e-commerce... Start collecting payments today Send payment links to your customers in Mexico -- no card machine, no website, no fuss. Mexico is the 15th largest e-commerce market in the world, with a growth rate of 27% in 2021. The country is projected to have a growth rate of 17% per year, well above the global average. Credit and charge cards are the most common payment method, with Visa, Mastercard, American Express, Banamex, and Carnet being popular options. Localized credit cards that can only be used for domestic purchases make up 67% of payments. Other popular payment platforms include Apple Pay, Google Pay, PayPal, and SafetyPay. Oxxo, a convenience store chain in Mexico, has partnered with Amazon to allow its prepaid debit cards to be used as a payment method on the e-commerce platform. OxxoPay, a payment service offered by Oxxo for utility bills, can also be used for online purchases. ## Popular offline payment methods in Mexico ### Cash ### Bank Transfers ### OXXO Pay ### Wire Transfers ### Cheques ### Mobile Wallets ## List of payment methods in Mexico OXXO is a popular convenience store chain in Mexico that offers a payment service allowing customers to make diverse payments, such as utility bills, online purchases, and international remittances. To use OXXO for payments, customers choose it during online checkout, receive a barcode or reference number, and then pay in cash at any OXXO store, where the cashier scans the code and issues a receipt. This method is convenient for those without traditional banking services or those who prefer cash payments, and it is widely accepted by online merchants in Mexico, providing a secure and accessible payment option for a variety of products and services. ### Mastercard Mastercard is extensively accepted as a payment method in Mexico, applicable at most retail stores, restaurants, hotels, and online merchants. It is also usable at ATMs across the country for cash withdrawals in Mexican pesos. To use a Mastercard, present it to the cashier or insert it into a chip-enabled terminal, possibly requiring a PIN or signature. Some places allow contactless payments through Mastercard's tap-and-go technology. However, cash may be necessary in smaller establishments or rural areas. Travelers are advised to inform their bank or credit card issuer about their Mexico trip to avoid potential issues with card security. Overall, Mastercard is a convenient and widely embraced payment option in Mexico for both locals and tourists. ### Visa Visa is extensively accepted for both in-person and online transactions, including major retailers like Walmart and Liverpool, as well as local businesses. Visa cards can be used at restaurants, cafes, and ATMs, but some ATMs may charge fees. Travelers are advised to inform their bank of travel plans, use secure ATMs, and monitor transactions for security. Overall, Visa is a convenient and widely accepted payment method in Mexico, providing ease of use for purchases and cash withdrawals. ### American Express American Express is widely accepted as a payment method in Mexico. Many businesses, including hotels, restaurants, and retail stores, accept American Express cards for payment. Additionally, American Express has a strong presence in Mexico and offers a variety of credit card options for Mexican consumers. Cardholders can use their American Express cards to make purchases both online and in-person throughout the country. ### Apple Pay Apple Pay is available and can be used in Mexico. It was launched in the country in 2017, allowing users to make contactless payments using their iPhone, Apple Watch, or iPad at supported merchants. ## Accepting International Card Payments in Mexico Whether you sell to customers in Mexico from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. OXXO cash payments and SPEI bank transfers handle most Mexican online purchases -- card-only checkouts miss a large segment. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Mexico, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Mexico as a Platform For software platforms serving merchants in Mexico, supporting local payment methods like OXXO, SPEI, and local card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Mexico? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-morocco/ --- # Morocco Payment Methods: Top 7 for Online & In-Store | Shuttle > Cash on delivery still leads, but digital is growing fast. From CMI cards to m-wallet -- every payment method merchants need in Morocco. # Morocco Payment Methods: Top 7 for Online & In-Store By Nick Dunse, March 10, 2022 Cash on delivery still leads, but digital is growing fast. From CMI cards to m-wallet -- every payment method merchants need in Morocco. Start collecting payments today Send payment links to your customers in Morocco -- no card machine, no website, no fuss. Despite the increasing prevalence of e-commerce and online payments in Morocco, cash continues to be the primary payment method, mainly driven by a substantial unbanked population, cultural preferences favoring cash transactions, and challenges in accessing digital payment infrastructure. Approximately 60% of Moroccan adults are unbanked, relying on cash for financial transactions. The cultural and historical significance of cash in the country further reinforces its popularity, as it is perceived as a tangible and secure form of payment. Additionally, limited access to digital payment infrastructure, particularly in rural areas lacking reliable internet connections, contributes to the prevalence of cash transactions. Despite these obstacles, the Moroccan government and financial institutions are actively working to enhance financial inclusion and encourage digital payment adoption through initiatives like mobile banking and mobile money services, signaling potential for future growth in digital payments in the country. ## Popular offline payment methods in Morocco ### Cash ### Bank Transfers ### Cheques ### Postal Money Orders ### Mobile Payments Point of Sales (POS) Terminals ## List of payment methods in Morocco ### Visa Visa is extensively accepted for payments in Morocco, particularly in tourist-centric establishments like hotels, restaurants, and shops, with broad usage in major cities such as Marrakech and Casablanca. To utilize Visa in the country, travelers must possess a Visa card issued by a bank or financial institution and inform their bank about their travel plans to ensure smooth transactions. When using Visa, identification like a passport or driver's license may be required, and some places may request a PIN for added security. Although Visa is widely embraced, it's advised to carry local currency (Moroccan dirham) as there might be instances, particularly in smaller businesses or rural areas, where cash remains the preferred payment method. Overall, Visa offers a convenient and widely accepted payment option in Morocco, facilitating seamless transactions for travelers throughout their stay. ### Mastercard Mastercard is a widely accepted payment method throughout Morocco, with most hotels, restaurants, shops, and online retailers accepting it. Many ATMs also allow for cash withdrawals using Mastercard. However, it is advisable to carry some cash as not all establishments may accept card payments. Furthermore, it is recommended to inform your bank or credit card provider of your travel plans to Morocco to avoid any potential issues when using your Mastercard abroad. ### American Express American Express is accepted as a payment method in Morocco, but it may not be as widely accepted as Visa or Mastercard. It is recommended to carry an alternative payment method, such as a Visa or Mastercard, in case American Express is not accepted at certain establishments. It is also advisable to inform your bank or credit card company of your travel plans to Morocco to avoid any issues with using your card abroad. ### Diners Club Diners Club is accepted as a payment method in Morocco. It is one of the major international credit card networks and is widely accepted at hotels, restaurants, and shops in the country. However, it is always a good idea to check with the specific establishment beforehand to ensure that they accept Diners Club as a form of payment. ### Discover Discover cards are not widely accepted in Morocco. Visa and Mastercard are the most commonly accepted credit cards in the country. It is recommended to carry alternative payment methods, such as cash or a Visa/Mastercard, when traveling to Morocco. ### JCB JCB, or Japan Credit Bureau, is not extensively utilized as a payment method, unlike in many other countries where it is popular. The country predominantly relies on the Moroccan dirham (MAD) as its currency, with cash and major credit cards like Visa and Mastercard being widely accepted by most businesses. Although some establishments in Morocco may accept JCB, it is not as prevalent as other payment options. Travelers planning to use JCB are advised to carry alternative forms of payment, such as cash or internationally recognized credit cards. Prior confirmation with specific businesses is recommended to ensure they accept JCB, as its usage is not widespread and may vary across establishments in the country. Overall, while JCB may have limited acceptance in certain places in Morocco, it is not a commonly recognized or utilized primary payment method in the country. ### UnionPay UnionPay is a highly prevalent payment option in Morocco, accepted at various major retailers, hotels, restaurants, and establishments that support credit card transactions, both online and offline. To utilize UnionPay in Morocco, individuals must possess a UnionPay card issued by an affiliated bank, and transactions can be conducted at any point of sale terminal displaying the UnionPay logo. The payment process typically involves entering a PIN, with some places requiring additional identification like a passport or driver's license. Although UnionPay is widely embraced, there might be exceptions among smaller vendors, prompting the recommendation to carry cash or alternative methods like Visa or Mastercard. Overall, UnionPay proves to be a convenient and widely accepted payment method in Morocco, appealing to both locals and tourists alike. Mobiamo is a mobile payment platform operating in Morocco, enabling users to make purchases and payments through their mobile phones. To use Mobiamo, individuals must have a mobile phone with a SIM card from a supported network operator and create an account on the Mobiamo website or app. Once registered, users can link their mobile numbers to their Mobiamo accounts and select the platform as a payment option at participating merchants. Payments are confirmed through an SMS verification code, deducting the amount from the user's mobile phone balance or adding it to their monthly phone bill, depending on the network operator. Mobiamo supports multiple payment methods, such as credit cards, debit cards, and carrier billing, offering a secure and convenient solution for a variety of services and products in Morocco. Onecard is a prepaid payment method in Morocco, offering a secure and convenient alternative to traditional banking and credit cards. Users purchase the card with a specific amount loaded onto it, which can be used until the balance is exhausted. Accepted at various merchants, both online and in physical stores, Onecard simplifies transactions by presenting the card at the point of sale. It enhances security by eliminating the need for personal or financial information during purchases, reducing the risk of fraud or identity theft. The card can be easily reloaded at authorized retailers or online, providing flexibility for users. Overall, Onecard serves as a reliable and adaptable solution for making purchases in Morocco, catering to the growing demand for efficient and secure payment options. NeoSurf is a popular prepaid card payment method widely embraced in Morocco, allowing users to conduct online transactions without the necessity of a bank account or credit card. Available for purchase at authorized retailers or online platforms, the NeoSurf card features a unique 10-digit code enabling payments on websites that accept NeoSurf. To utilize this method, users select NeoSurf at the checkout, input the 10-digit code, and confirm the payment, deducting the amount from the card balance. Suitable for various online purchases, including gaming and e-commerce, NeoSurf ensures secure transactions without divulging personal or financial details. Users should be mindful of card expiration dates and potential fees on certain websites. Overall, NeoSurf provides a reliable and convenient payment option in Morocco, combining accessibility and security for online transactions. Ticket Premium is a prepaid payment solution available in Morocco, offering a convenient method for transactions without the need for a bank account or credit card. Purchased as a voucher from various retail locations, including supermarkets and online platforms, it contains a unique code that users input when making online purchases or transactions at participating merchants. The voucher's credited amount is deducted upon validation, facilitating secure payments for a range of services such as gaming, entertainment, and e-commerce. Users should be mindful of the vouchers' expiration dates and check for specific terms imposed by merchants. In essence, Ticket Premium serves as an accessible alternative for individuals in Morocco who prefer non-traditional banking methods or credit cards. MINT is a popular payment method in Morocco, offering users a secure and convenient way to make online purchases and payments through their mobile phones, eliminating the need for a credit card or bank account. To use MINT, individuals can purchase vouchers of different denominations from authorized resellers or the MINT website, which can then be used to top up their MINT accounts. Once the account is loaded, users can seamlessly make payments on diverse online platforms by selecting MINT as their preferred option during checkout. Widely accepted by e-commerce sites, online gaming platforms, and digital content providers, MINT has also formed partnerships with some physical stores and businesses in Morocco. A key advantage of MINT is its accessibility, as it caters to individuals without access to traditional banking services, offering a broad user base a secure and straightforward means of conducting online transactions. Overall, MINT stands out as a convenient and widely accepted payment solution in Morocco, providing accessibility to a diverse range of users. ## Accepting International Card Payments in Morocco Whether you sell to customers in Morocco from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards and bank transfers are well established in Morocco but mobile money and cash on delivery remain common for online purchases. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Morocco, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Morocco as a Platform For software platforms serving merchants in Morocco, supporting local payment methods like local bank transfers and domestic card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Morocco? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-new-zealand/ --- # Payment Methods in New Zealand: Cards, POLi & Afterpay (2026) | Shuttle > Explore New Zealand's most popular payment methods from debit and credit cards to POLi online banking, Afterpay, and digital wallets like Apple Pay. # Payment Methods in New Zealand: Cards, POLi & Afterpay (2026) By Nick Dunse, July 12, 2021 Explore New Zealand's most popular payment methods from debit and credit cards to POLi online banking, Afterpay, and digital wallets like Apple Pay. Start collecting payments today Send payment links to your customers in New Zealand -- no card machine, no website, no fuss. In the realm of online shopping in New Zealand, credit and debit cards reign supreme as the preferred payment methods for consumers, aligning with the payment habits observed in Australia. For e-commerce ventures eyeing the New Zealand market, it is crucial to incorporate credit and debit card payment options. Beyond cards, the popularity of e-Wallets, exemplified by options such as PayPal and POLi, is on the rise, offering a secure and convenient avenue for online transactions. Despite New Zealand's comparatively modest population, its e-commerce sector is steadily expanding, boasting 3 million shoppers in 2020 and a $3 billion online market. Projections indicate a 10% annual growth rate in the e-commerce market from 2019 to 2024. To effectively tap into this burgeoning market, businesses should prioritize providing credit and debit card options, alongside well-received e-Wallets like PayPal and POLi, thereby aligning with consumer preferences and capitalizing on the country's growing e-commerce landscape. ## Popular offline payment methods in New Zealand ### Cash Electronic Funds Transfer at Point of Sale (EFTPOS) ### Mobile Payments ### Cheques ### Direct Bank Transfers ## List of payment methods in New Zealand ### Visa Visa is a widely accepted payment method, usable at retail stores, restaurants, hotels, and online merchants, as well as for cash withdrawals at ATMs. The range of Visa cards available includes credit, debit, and prepaid cards, issued by various banks and financial institutions. Payment with a Visa card involves presenting it to the merchant or using a card reader for contactless transactions, with some requiring a PIN for added security. Visa provides additional security features like Verified by Visa for online purchases, requiring a password or a one-time code via SMS. While widely accepted, it's advised to carry some cash for situations where smaller merchants or businesses may only accept cash or have limited card acceptance in New Zealand. ### Mastercard Mastercard is extensively recognized as a preferred payment method in New Zealand, accepted at numerous retail establishments, restaurants, hotels, and online vendors across the country. Utilizing Mastercard involves presenting the card to the merchant or inserting it into chip-enabled terminals, with PIN entry possibly required for verification. Online purchases require entering card details, including the card number, expiration date, and CVV code. While Mastercard's acceptance is widespread, some smaller businesses or rural areas may have limited card payment options, prompting the recommendation to carry cash as a backup. Mastercard offers additional features like contactless payments and rewards programs, and users are advised to consult their specific provider for details on these features and associated fees. Overall, Mastercard's convenience and broad acceptance make it a popular choice for both residents and visitors in New Zealand. ### American Express American Express is accepted as a payment method in New Zealand. Many merchants, including restaurants, hotels, and retailers, accept American Express cards for payment. Additionally, American Express has its own network of ATMs in New Zealand, allowing cardholders to withdraw cash. However, it is worth noting that not all merchants in New Zealand accept American Express, so it is always a good idea to check with the merchant beforehand or have an alternative form of payment available. Afterpay and Clearpay are popular buy now, pay later services in New Zealand, offering customers a flexible approach to managing payments. Available both online and in-store, Afterpay enables users to divide their purchases into four equal installments, with the initial payment made at the time of purchase and subsequent payments interest-free if made on time. Clearpay operates similarly, providing customers the option to split payments into four parts at various New Zealand retailers. Both services necessitate an account creation and credit check, but once approved, customers can immediately utilize Afterpay or Clearpay for convenient and interest-free installment payments, making them practical choices for those looking to spread out the cost of their purchases in New Zealand. ### Maestro Maestro, a popular payment method in New Zealand, functions as a debit card issued by various banks and financial institutions across the country. Accepted widely, Maestro cards facilitate online and in-store transactions, as well as cash withdrawals from ATMs. To utilize Maestro for online purchases, users must select it as their payment option and input card details, including the card number, expiry date, and CVV code. In physical stores, Maestro cards can be used wherever debit cards are accepted. Boasting contactless payment technology, these cards enable quick and convenient transactions through a simple tap on contactless-enabled terminals. Despite its broad acceptance, some merchants may have specific debit card preferences or may not accept international Maestro cards, necessitating prior confirmation or an alternative payment method. Overall, Maestro stands out as a convenient and widely embraced payment solution in New Zealand, catering to the needs of both residents and visitors for seamless online and in-store purchases. ### Alipay Alipay, a widely used mobile payment platform in China, has extended its reach to businesses in New Zealand, with a notable focus on the tourism and retail sectors. Various establishments catering to Chinese tourists, such as hotels, restaurants, retail stores, and tourist attractions like Skyline Queenstown and Auckland Zoo, now accept Alipay as a payment method. To utilize Alipay in New Zealand, customers must have the Alipay app installed on their mobile devices, linked to their bank account or credit card. The payment process involves scanning a QR code provided by the merchant. This strategic move benefits businesses by accessing the growing Chinese tourist market, offering a convenient payment option, and potentially attracting more customers, thereby boosting sales. Although Alipay's acceptance is not universal across all businesses in New Zealand, its prevalence is on the rise, particularly in areas frequented by Chinese tourists. ### UnionPay UnionPay is a highly accepted payment method in New Zealand, particularly in popular tourist areas, where numerous merchants such as hotels, restaurants, shops, and attractions welcome UnionPay cards. To utilize UnionPay, individuals can present their cards at the point of sale, following the merchant's instructions, often indicated by a displayed UnionPay logo. The versatility of UnionPay extends to online transactions, with many e-commerce websites and online retailers accommodating this payment option. While widely accepted, it is advisable to carry an alternative form of payment, like cash or another credit card, as UnionPay may not be universally accepted. Overall, UnionPay provides a convenient and accessible means for visitors, especially from China, to make purchases in New Zealand during their stay. ### Apple Pay Apple Pay is now widely available in New Zealand, allowing users to make contactless payments with ease. The service was introduced to the country in October 2016 and has since been embraced by major banks and retailers. With Apple Pay, customers can simply hold their iPhone or Apple Watch near a contactless payment terminal to complete their transaction. This convenient and secure payment method has quickly become a popular choice for Kiwis who are always on the go. Whether you're shopping for groceries or grabbing a coffee on the way to work, Apple Pay makes it easy to pay quickly and securely. ### JCB JCB, or Japan Credit Bureau, is a widely embraced payment method in New Zealand, accepted by a plethora of merchants including restaurants, hotels, retail stores, and online platforms. Utilizing JCB is straightforward, as customers only need to present their JCB credit cards at the point of sale. The cards come with various perks for users, ranging from reward programs to travel insurance coverage and exclusive discounts at partner establishments. Additionally, JCB prioritizes security, implementing advanced fraud prevention measures to ensure a high level of protection for cardholders. In keeping with technological trends, JCB also provides digital payment solutions, allowing users to make contactless payments through their cards or mobile wallets at compatible terminals. Overall, JCB stands out as a convenient and widely accepted payment option in New Zealand, offering a seamless and secure transaction experience for customers. PaySafeCard is a widely used prepaid payment solution in New Zealand, offering a convenient alternative for online purchases without requiring a credit card or bank account. Available for purchase in various denominations, ranging from $10 to $100, at retail locations like supermarkets and convenience stores, PaySafeCard provides users with a 16-digit PIN code that can be used during online checkout processes. This secure payment method caters to a diverse range of transactions, including gaming, entertainment, and e-commerce. For added flexibility, users can either opt for physical cards or create an online account with PaySafeCard, utilizing a digital wallet to manage funds and seamlessly conduct online transactions while safeguarding personal and financial information. In essence, PaySafeCard stands out as a popular and secure payment solution in New Zealand, offering an accessible and privacy-conscious means of conducting online transactions. ### Zip Zip is a widely used payment method in New Zealand, offering a buy now, pay later service akin to Afterpay and Laybuy. To utilize Zip, customers must create an account, linking it to their bank account or credit card. During a purchase, Zip can be selected as the payment option, with customers choosing the number of installments, typically ranging from 4 to 6, in which they wish to pay. Following the transaction, an invoice is sent by Zip, detailing the purchase and installment due dates. Early payment is an option without additional fees or interest. Additionally, Zip provides a digital wallet feature called Zip Pay, enabling purchases at participating stores through a unique QR code. Overall, Zip presents a convenient and flexible payment solution, allowing New Zealand customers to manage their finances effectively by spreading payments over time. ### WeChat Pay WeChat Pay, a widely used mobile payment method in China, has extended its services to New Zealand, allowing users to make payments through the WeChat app. To utilize WeChat Pay in New Zealand, users must have a WeChat account linked to their bank account or credit card. Payments at participating merchants can be made by scanning a QR code provided by the merchant through the WeChat app, where users enter the payment amount and confirm the transaction, with funds deducted from the linked account. Accepted at various establishments in New Zealand, including retail stores and restaurants, WeChat Pay offers convenience for Chinese tourists and residents, although its acceptance may vary, prompting users to check with merchants in advance. Overall, WeChat Pay provides a secure and convenient mobile payment solution in New Zealand for those familiar with the app's use in China. PayPal serves as a widely accepted and convenient payment method, embraced by numerous online retailers and service providers. The platform facilitates both domestic and international transactions, enabling users to make purchases from overseas websites that support PayPal. To utilize this service, individuals in New Zealand must create a PayPal account and link it to their bank account or credit card. At the time of checkout on participating websites, users can opt for PayPal, leading them to the PayPal website for login and payment confirmation. Notably, PayPal extends buyer protection for eligible purchases, offering security by covering instances where items are not received or significantly differ from the provided description. Overall, PayPal is a popular and secure choice for online transactions in New Zealand, streamlining the payment process for users domestically and abroad. ### Google Pay Google Pay is available as a payment method in New Zealand. Users can add their credit or debit cards to the Google Pay app and use it to make payments at participating merchants. Google Pay can be used for in-store purchases, online payments, and peer-to-peer transfers. To use Google Pay, users need to have a compatible Android device with NFC capabilities and the Google Pay app installed. ### Diners Club Diners Club is a widely accepted payment method in New Zealand, usable at various merchants such as restaurants, hotels, and retail stores, both in-person and online. To use the card, one simply presents it to the merchant, who swipes or inserts it into their payment terminal, prompting the user to enter a PIN or sign for the transaction. Additionally, Diners Club provides a mobile app enabling smartphone payments at participating merchants that accept mobile payments. Despite its widespread acceptance, it's advisable to confirm with the merchant beforehand, as Diners Club may not be accepted universally. ## Accepting International Card Payments in New Zealand Whether you sell to customers in New Zealand from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Card payments dominate New Zealand but POLi bank transfers and Afterpay are common consumer expectations. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for New Zealand, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in New Zealand as a Platform For software platforms serving merchants in New Zealand, supporting local payment methods like POLi, local bank transfers, and domestic card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in New Zealand? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-nigeria/ --- # Payment Methods in Nigeria: Cards, Bank Transfers & Mobile Money (2026) | Shuttle > Discover Nigeria's top payment methods including bank transfers, debit cards, USSD payments, and mobile money platforms for Africa's largest e-commerce... # Payment Methods in Nigeria: Cards, Bank Transfers & Mobile Money (2026) By Nick Dunse, April 20, 2024 Discover Nigeria's top payment methods including bank transfers, debit cards, USSD payments, and mobile money platforms for Africa's largest e-commerce... Start collecting payments today Send payment links to your customers in Nigeria -- no card machine, no website, no fuss. In Nigeria, a plethora of digital payment solutions facilitates businesses' entry into the burgeoning e-commerce market. Leading the pack is Interswitch, a prominent payment processing company offering diverse solutions, including card payments, mobile payments, and online transactions through a dedicated payment gateway. Flutterwave, a fintech firm, provides comprehensive payment infrastructure, supporting card payments, bank transfers, and mobile money, extending its reach to international transactions. Paystack, a Nigerian payment gateway, enables businesses to accept online payments, manage subscriptions, and handle recurring payments seamlessly. Paga, a mobile payment platform, facilitates money transfers, bill payments, and purchases, with an API for business integration. Remita, developed by SystemSpecs, serves as an e-payment platform, allowing versatile payment channels such as banks, cards, and mobile wallets. Quickteller offers a digital payment platform for various transactions, including bill payments and fund transfers, along with business-friendly API integration. Opay, a mobile wallet by Opera Software, supports money transfers, bill payments, and additional services like ride-hailing and food delivery. The collective impact of these solutions has simplified payment acceptance for businesses targeting Nigerian customers, aligning with the country's growing e-commerce landscape driven by increased smartphone adoption and internet connectivity. The demand for digital payment solutions is anticipated to further escalate in Nigeria. ## Popular offline payment methods in Nigeria ### Cash Payments ### Bank Transfers ### Mobile Money ### POS (Point of Sale) Terminals ### Bank Cheques ### Payment Cards ### USSD Banking ### Agent Banking ### Remittance Services ### Electronic Funds Transfers ## List of payment methods in Nigeria While not widely accepted yet, cryptocurrencies such as Bitcoin can be used as a form of payment in Nigeria. Verve is a Nigerian payment card brand owned by Interswitch Group. It is widely accepted in Nigeria and can be used for online and offline transactions. ### UnionPay UnionPay is a Chinese payment card brand that is accepted in many countries, including Nigeria. It can be used for online and offline transactions. ### American Express American Express (Amex) cards are accepted at some merchants in Nigeria, particularly high-end establishments. However, acceptance may be limited compared to Visa and Mastercard. ### Discover Discover cards are accepted at some merchants in Nigeria, but acceptance may be limited compared to Visa and Mastercard. ### JCB JCB is a Japanese payment card brand that is accepted at some merchants in Nigeria, particularly those catering to international tourists. eTranzact is a Nigerian payment platform that offers prepaid cards and mobile banking services. It can be used for online and offline transactions. Verve eCash is a digital payment solution offered by Interswitch Group. It allows users to make payments using their mobile phones or other devices. Paystack is a Nigerian online payment platform that allows users to make payments using their debit or credit cards, including Visa and Mastercard. Flutterwave is another Nigerian online payment platform that supports various card payment methods, including Visa and Mastercard. Quickteller is a Nigerian online payment platform that supports various card payment methods, including Visa and Mastercard. ### Visa Visa is a widely accepted payment method, applicable for various transactions such as shopping, dining, and other services, both online and offline. Businesses including supermarkets, restaurants, hotels, and online retailers recognize and facilitate payments through Visa cards. To utilize Visa in Nigeria, one must possess a Visa card issued by a bank, either as a debit or credit card, and it can be used at any point of sale terminal accepting Visa payments. Secure payment processing and fraud protection measures are inherent to Visa transactions, emphasizing the importance of maintaining card details' confidentiality. Some Nigerian banks also offer Visa prepaid cards, functioning like regular Visa cards and allowing loading of funds for purchases. Overall, Visa stands out as a convenient and extensively embraced payment method in Nigeria, facilitating easy transactions for individuals across various platforms. ### Mastercard Mastercard is widely accepted for payments in Nigeria, catering to both online and offline transactions across various establishments such as retail stores, restaurants, hotels, and online platforms. To utilize a Mastercard in Nigeria, one must ensure that the card is enabled for international transactions, with activation requirements varying among Nigerian banks. Once international transactions are enabled, the card can be used at any Mastercard-accepting merchant. Online payments necessitate entering card details, while offline transactions involve swiping or inserting the card and entering a PIN if required. It's worth noting that some Nigerian merchants may impose additional fees for Mastercard usage, prompting the recommendation to check for such charges beforehand. Overall, employing Mastercard in Nigeria provides a secure and convenient payment method for diverse transactions. ## Accepting International Card Payments in Nigeria Whether you sell to customers in Nigeria from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Card adoption is growing in Nigeria but bank transfers and USSD payments still drive most consumer transactions. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Nigeria, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Nigeria as a Platform For software platforms serving merchants in Nigeria, supporting local payment methods like bank transfers, USSD payments, and mobile money is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Nigeria? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-poland/ --- # Payment Methods in Poland: BLIK, Przelewy24 & Cards (2026) | Shuttle > BLIK and Przelewy24 dominate Polish online payments. Explore all popular payment methods in Poland including cards, digital wallets, and bank transfers. # Payment Methods in Poland: BLIK, Przelewy24 & Cards (2026) By Nick Dunse, March 18, 2021 BLIK and Przelewy24 dominate Polish online payments. Explore all popular payment methods in Poland including cards, digital wallets, and bank transfers. Start collecting payments today Send payment links to your customers in Poland -- no card machine, no website, no fuss. Poland has a high internet penetration rate, with over 80% of the population having access to the internet. This, combined with the increasing popularity of smartphones, has led to a significant growth in online shopping in recent years. The COVID-19 pandemic has further accelerated the growth of e-commerce in Poland, as consumers turned to online shopping due to lockdowns and social distancing measures. This trend is expected to continue even after the pandemic, as consumers have become more comfortable with online shopping and have experienced the convenience it offers. When it comes to payment methods, direct payment through bank transfer has traditionally been the most popular option in Poland. However, alternative payment systems like PayPal and card payments are gaining popularity, especially among younger consumers. These payment methods offer convenience and security, which are important factors for online shoppers. For merchants looking to expand into the Polish market, it is recommended to offer popular local payment methods like Przelewy24 and BLIK. Przelewy24 is a popular online payment system that allows users to make payments directly from their bank accounts. BLIK is a mobile payment system that allows users to make payments using their smartphones. In conclusion, Poland is a growing e-commerce market with a high internet penetration rate. The COVID-19 pandemic has further accelerated the growth of online shopping in the country. Offering popular local payment methods like Przelewy24 and BLIK can help merchants localize their checkouts and cater to the preferences of Polish consumers. ## Popular offline payment methods in Poland ### Cash ### Bank Transfers ### Payment Cards ### Mobile Payments ### Cheques ### Postal Money Orders ### Cash On Delivery ### Vouchers and Gift Cards ## List of payment methods in Poland Online Banking Poland is a widely embraced payment method in Poland, allowing customers to make online payments directly from their bank accounts without the requirement of credit or debit cards. Users must have an account with one of the participating banks, such as PKO Bank Polski, mBank, ING Bank Śląski, or Alior Bank. When opting for Online Banking Poland during an online purchase, customers are redirected to their bank's secure online banking platform, where they can authenticate the payment. The process is swift, with funds instantly transferred from the customer's bank account to the merchant's account. This method enhances security by eliminating the need for card details and necessitating authentication through online banking credentials. Overall, Online Banking Poland stands out as a secure and convenient option, widely accepted in the country, streamlining online payments directly from users' bank accounts. ### Visa Visa is a highly favoured payment method throughout Poland, accepted at a vast array of retail stores, restaurants, hotels, and online merchants. Additionally, Visa cards can be used at ATMs for cash withdrawals. In Poland, Visa offers a range of card types, including debit, credit, and prepaid cards, which can be issued by local banks or international financial institutions. To utilise a Visa card in Poland, simply present it to the merchant or insert it into a card reader. Some merchants may require a PIN for security purposes. For online payments with Visa, it is typically necessary to enter the card number, expiration date, and CVV code. It is worth noting that although Visa is widely accepted in Poland, some smaller merchants or establishments may only accept cash or specific local payment methods. Therefore, it is advisable to carry some cash as a backup. Overall, utilising Visa as a payment method in Poland is a convenient and widely accepted option, making it effortless for both travellers and residents to make purchases and access funds. ### BLIK BLIK, introduced in 2015 by a consortium of Polish banks, has emerged as a leading mobile payment method in Poland, gaining substantial popularity among both consumers and merchants. To utilize BLIK, users must download the mobile app and link it to their bank account, enabling them to make payments by scanning QR codes or entering unique codes generated by merchants. The versatility of BLIK extends to both online and offline transactions, with acceptance spanning various sectors, including supermarkets, restaurants, online retailers, and public transportation providers. Its appeal lies in the convenience it offers, allowing users to swiftly and easily make payments via their mobile phones, eliminating the need for physical cash or cards. The app's additional features, such as bill splitting and fund transfers among BLIK users, contribute to its attractiveness. Notably, BLIK prioritizes security, requiring transaction authentication through PIN codes or biometric data, enhancing protection against unauthorized use and safeguarding users' financial information. Overall, BLIK's success in Poland stems from its convenience, security measures, and widespread acceptance, playing a pivotal role in driving the adoption of mobile payments and reducing dependence on cash transactions in the country. ### Mastercard Mastercard is widely accepted as a payment method in Poland. It can be used at most retail stores, restaurants, and online merchants in the country. Additionally, Mastercard can be used to withdraw cash from ATMs throughout Poland. Many banks in Poland issue Mastercard debit and credit cards to their customers, making it a convenient and popular payment option for both locals and tourists. ### Maestro Maestro is a widely accepted payment method in Poland. It is a debit card issued by banks and can be used for both online and offline transactions. Maestro cards are accepted at most merchants, including supermarkets, restaurants, and shops. They can also be used to withdraw cash from ATMs. Maestro cards in Poland are typically linked to the customer's bank account and require a PIN for authorization. Overall, Maestro is a convenient and secure payment option for consumers in Poland. ### American Express American Express is a viable payment option, albeit not as ubiquitous as Visa or Mastercard. In major cities like Warsaw, Krakow, and Gdansk, American Express cards are accepted at numerous hotels, restaurants, and shops. Nevertheless, it is prudent to have a backup payment method, such as Visa or Mastercard, as some smaller establishments may not accommodate American Express. Moreover, it is advisable to notify your bank or credit card provider of your travel itinerary to guarantee seamless card usage overseas and to preclude any possible complications with fraud alerts. Diners Club International is a widely embraced payment option in Poland, with acceptance extending to diverse businesses like restaurants, hotels, and retail establishments. The versatility of Diners Club is evident in its applicability to both online and offline transactions. Utilizing the card is straightforward for customers who only need to present it at the point of sale, where the payment is processed either through a Diners Club card terminal or an online payment gateway. In Poland, Diners Club provides cardholders with enticing perks, including reward points, travel insurance, and access to airport lounges, along with exclusive discounts at select merchants. Beyond local use, Diners Club cards are internationally recognized, making them a practical choice for both residents traveling abroad and foreign visitors in Poland. Overall, Diners Club stands out as a widely accepted and convenient payment method in Poland, offering users a host of benefits and rewards. ### Apple Pay Apple Pay, introduced in Poland on June 19, 2018, is a mobile payment and digital wallet service enabling users to make transactions via their iPhone, Apple Watch, iPad, or Mac. Adding credit or debit cards to the Wallet app is a straightforward process, allowing users to make secure payments by holding their device close to a contactless terminal and using Touch ID or Face ID for authentication. Widely accepted at various establishments, including supermarkets, restaurants, gas stations, and online stores, Apple Pay is versatile, extending its utility to public transportation and compatible apps. Beyond payments, the service offers features like loyalty card and boarding pass storage in the Wallet app, providing a convenient and secure payment solution for users in Poland. ### Discover Discover is not widely accepted as a payment option in Poland. The most commonly accepted credit cards in Poland are Visa and Mastercard. However, some merchants may accept Discover cards, especially in larger cities or tourist areas. It is always best to check with the specific merchant or establishment before attempting to use a Discover card for payment. ### JCB JCB, or Japan Credit Bureau, is a widely accepted payment method in Poland, available for both online and offline transactions. To utilize JCB, customers must possess a JCB card issued by their bank, which can be used at various merchants, including restaurants, hotels, retail stores, and online platforms. Presenting the JCB card at the point of sale or entering its details for online purchases allows customers to benefit from its advanced security features like EMV chip technology and tokenization, guarding against fraud. The use of JCB in Poland also grants customers access to special discounts and promotions offered by merchants, enhancing its appeal. Additionally, customers can earn rewards points or cashback on purchases, redeemable for travel vouchers or gift cards. In summary, JCB serves as a popular, secure, and convenient payment method in Poland, offering users not only a reliable transactional tool but also various perks such as discounts and rewards. ### UnionPay UnionPay has gained popularity as a widely accepted payment method in Poland, particularly among Chinese tourists and residents. The increasing influx of Chinese tourists and the growing presence of Chinese businesses in the country have contributed to the rise in the number of merchants accepting UnionPay cards. To use UnionPay, customers can simply present their card at the point of sale, where the payment is processed using UnionPay terminals or POS systems. Beyond physical card payments, UnionPay also offers mobile payment options such as QR code and contactless payments, which are gaining traction, especially among younger consumers. This convenience and acceptance are expected to continue expanding as more merchants in Poland recognize the significance of meeting the payment preferences of Chinese customers. ### Google Pay Google Pay is available as a payment method in Poland. Users can add their credit or debit cards to the Google Pay app and use it to make payments at participating merchants. Google Pay also supports contactless payments using NFC technology, allowing users to simply tap their phone on a payment terminal to complete a transaction. Additionally, Google Pay can be used for online purchases on websites and apps that accept this payment method. ### Alipay Alipay, a popular Chinese mobile payment platform, faces limited acceptance in Poland, with its usage primarily concentrated among businesses catering to Chinese tourists or those with partnerships with Chinese companies. Certain hotels, restaurants, and shops in major tourist destinations like Warsaw and Krakow may accommodate Alipay transactions. Additionally, online travel agencies and e-commerce platforms may offer Alipay as a payment option. To utilize Alipay in Poland, users must have a registered account linked to their bank account or credit card, enabling them to make mobile payments or scan QR codes at participating merchants. Despite these options, Alipay's recognition and prevalence in Poland lag behind more conventional payment methods such as credit cards or cash. As a result, travelers are advised to have alternative payment methods on hand when making purchases or transactions in the country. ### PayPal PayPal is widely accepted as a payment method in Poland. Many online stores and service providers in the country offer PayPal as an option for customers to make payments. Additionally, individuals can also use PayPal to send and receive money from friends and family or make online purchases from international websites that accept PayPal. To use PayPal in Poland, individuals need to create a PayPal account and link it to their bank account or credit card. Once the account is set up, they can use PayPal to make payments by selecting the PayPal option at checkout on participating websites or by sending money directly to another PayPal user. PaySafeCard is a prevalent prepaid payment solution in Poland, providing a convenient method for online transactions without the necessity of a bank account or credit card. Users can acquire a prepaid card in denominations ranging from 10 PLN to 100 PLN at authorized retailers, obtaining a unique 16-digit PIN code upon purchase. To execute a payment, users simply select PaySafeCard as their payment method on the desired website, enter the PIN code when prompted, and the payment is deducted from the card balance. This method is secure and does not require the sharing of personal or financial information. PaySafeCard extends its usability beyond online purchases, enabling users to top up digital wallets, prepaid cards, and make mobile payments through its dedicated app. Overall, PaySafeCard is widely embraced in Poland, offering a secure and hassle-free means for online transactions. ### Klarna Klarna is a widely used payment method in Poland, enabling customers to effortlessly make online purchases and defer payment to a later date, whether in full or through installments. The checkout process is seamless, requiring only a few clicks for completion. To utilize Klarna, customers must select it at the online store's checkout, leading them to the Klarna website to choose their preferred payment option and, in some cases, undergo a credit check. Klarna provides numerous advantages in Poland, such as the option to divide payments, interest-free financing, and a secure checkout experience. With widespread acceptance among online retailers, Klarna stands out as a popular and convenient choice for Polish online shoppers, offering flexibility and ease in their online transactions. ## Accepting International Card Payments in Poland Whether you sell to customers in Poland from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. BLIK and Przelewy24 dominate Polish e-commerce -- card-only checkouts leave most consumers unable to complete a purchase. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Poland, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Poland as a Platform For software platforms serving merchants in Poland, supporting local payment methods like BLIK, Przelewy24, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Poland? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-south-africa/ --- # Payment Methods in South Africa: Cards, EFT & Mobile Wallets (2026) | Shuttle > Explore South Africa's most popular payment methods from debit cards and EFT bank transfers to SnapScan, Zapper, and the growing digital payment... # Payment Methods in South Africa: Cards, EFT & Mobile Wallets (2026) By Nick Dunse, February 17, 2021 Explore South Africa's most popular payment methods from debit cards and EFT bank transfers to SnapScan, Zapper, and the growing digital payment... Start collecting payments today Send payment links to your customers in South Africa -- no card machine, no website, no fuss. The expansion of e-commerce in South Africa can be attributed to various factors. The increased accessibility and affordability of internet services have simplified online shopping for consumers. The prevalence of smartphones has further facilitated this trend, providing more individuals with internet access and the ability to make on-the-go purchases. The COVID-19 pandemic has significantly accelerated the adoption of online shopping as lockdowns and social distancing measures restricted physical store visits, fostering a surge in virtual transactions. The pandemic has also boosted consumer confidence in online purchases. Additionally, the allure of convenience and time savings associated with e-commerce has resonated with South African consumers who can explore and buy products from their homes. The preference for specific product categories, such as clothing, footwear, electronics, and household appliances, mirrors consumer tastes and needs. As a result, the trajectory of e-commerce growth in South Africa is anticipated to persist, offering opportunities for both local and international retailers to tap into this expanding market. ## Popular offline payment methods in South Africa ### Cash ### Cheques ### Bank Transfer ### Mobile Banking ### Electronic Funds Transfer ### Debit Cards ### Prepaid Cards ### Money Orders ### Cryptocurrencies ### Retail- Specific Cards ## Accepting International Card Payments in South Africa Whether you sell to customers in South Africa from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Card payments lead in South Africa but EFT, instant EFT, and SnapScan are essential for full coverage. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for South Africa, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in South Africa as a Platform For software platforms serving merchants in South Africa, supporting local payment methods like Instant EFT, SnapScan, and local card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in South Africa? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-tanzania/ --- # Payment Methods in Tanzania: M-Pesa, Tigo Pesa & Banks (2026) | Shuttle > Mobile money leads payments in Tanzania with M-Pesa and Tigo Pesa. Explore all popular payment methods including bank transfers and digital wallets. # Payment Methods in Tanzania: M-Pesa, Tigo Pesa & Banks (2026) By Nick Dunse, February 15, 2026 Mobile money leads payments in Tanzania with M-Pesa and Tigo Pesa. Explore all popular payment methods including bank transfers and digital wallets. Start collecting payments today Send payment links to your customers in Tanzania -- no card machine, no website, no fuss. The outlook for e-commerce in Tanzania appears promising, driven by several key factors. The steady increase in internet penetration, with over 23 million users as of 2020, establishes a substantial potential customer base for online businesses. The widespread adoption of mobile money services, notably M-Pesa, facilitates online transactions and builds trust in digital payments. The expanding middle class in Tanzania, characterized by rising disposable income and increased consumer spending, creates a growing market for e-commerce ventures. Government support, as evidenced by initiatives like the National E-Commerce Strategy, further encourages the sector's development. The surge in smartphone usage and the popularity of online marketplaces like Jumia and Kilimall contribute to the industry's momentum. Additionally, Tanzania's strategic location in East Africa presents cross-border e-commerce opportunities, allowing businesses to extend their reach beyond domestic borders. Despite challenges, such as improving infrastructure and fostering online payment confidence, the overall potential for significant e-commerce growth in Tanzania is evident, with expectations of rapid expansion in the coming years. ## Popular offline payment methods in Tanzania ### Cash ### Mobile Money ### Bank Transfers ### Cheques ### POS (Point of Sale) Terminals ### Direct Debit ### QR Code Payments ### Prepaid Cards ### Pay-by-SMS ## List of payment methods in Tanzania ### Visa Visa is widely accepted as a payment method in Tanzania. It can be used at most hotels, restaurants, and shops that cater to tourists. Additionally, many ATMs in Tanzania accept Visa cards for cash withdrawals. ### Mastercard Mastercard is extensively accepted as a payment method throughout Tanzania, encompassing major retailers, hotels, restaurants, and online transactions. To utilize Mastercard in the country, travelers need to ensure their cards are enabled for international transactions, a process that involves notifying their issuing bank of travel plans to Tanzania. Despite its widespread acceptance, it is prudent to carry local currency, particularly in smaller establishments or rural areas where cash may be the preferred payment mode. Vigilance in monitoring transactions and regular checks of account statements are recommended, along with informing the bank about travel plans to mitigate potential issues. In summary, Mastercard serves as a convenient and widely embraced means of payment in Tanzania, enhancing the ease of transactions for travelers across various establishments. ### American Express American Express is not widely accepted as a payment method in Tanzania. While some hotels, restaurants, and larger retailers may accept American Express, it is not as commonly accepted as Visa or Mastercard. It is recommended to carry an alternative form of payment, such as cash or a Visa/Mastercard credit or debit card, when traveling to Tanzania. ### Diners Club Diners Club, the renowned payment method, has now expanded its reach to Tanzania. This means that customers in Tanzania can now enjoy the convenience and security of using their Diners Club card to make purchases at various merchants across the country. With its global recognition and acceptance, Diners Club offers a reliable and efficient payment solution for both locals and tourists alike. Whether you're shopping for groceries, dining out at a restaurant, or booking a hotel room, Diners Club provides a hassle-free payment experience that is both safe and convenient. So if you're in Tanzania and looking for a trusted payment method, look no further than Diners Club. ### UnionPay UnionPay is a widely recognized payment method that has recently been introduced in Tanzania. This payment system has gained popularity among Tanzanians due to its convenience and reliability. Union Pay is accepted by a large number of merchants, making it easy for consumers to make purchases without worrying about carrying cash. This payment method is also secure, as it uses advanced technology to protect users' personal and financial information. With Union Pay, Tanzanians can now enjoy hassle-free transactions and a seamless shopping experience. As the popularity of Union Pay continues to grow in Tanzania, it is expected to become one of the most widely used payment methods in the country. ### JCB JCB, or Japan Credit Bureau, is a prevalent payment method in Tanzania, accepted by a diverse range of merchants, including hotels, restaurants, and retail stores. To utilize JCB for transactions, customers must possess a JCB card issued by their respective banks, enabling usage at any point of sale terminal that supports JCB payments. This method extends to online purchases from Tanzanian merchants, offering a secure and convenient cashless alternative. JCB cardholders enjoy various benefits, such as reward points and discounts at participating establishments, while the company provides robust customer support services to address inquiries or concerns. Overall, JCB stands out as a dependable and widely embraced payment solution in Tanzania, affording customers a seamless and secure experience for both in-store and online transactions. ### RuPay RuPay, a domestic card scheme in India comparable to Visa and Mastercard, has gained widespread acceptance in Tanzania. Tanzanians can use RuPay cards at a range of merchant outlets, including hotels, restaurants, supermarkets, and online platforms, following partnerships between many Tanzanian banks and RuPay. To utilize RuPay in Tanzania, individuals must possess a RuPay card issued by an Indian bank, swiping or inserting it into payment terminals for secure transactions. This payment method offers a secure and convenient alternative to carrying large sums of cash for both Indian travelers to Tanzania and Tanzanians with RuPay cards, making it a popular choice for various transactions in the country. ### Maestro Maestro, a debit card brand owned by Mastercard, is a popular and widely accepted payment method in Tanzania. To utilize Maestro in the country, individuals need a Maestro debit card issued by a supporting bank, and they can inquire with their bank about the availability of Maestro cards. With a Maestro card, users can withdraw cash from ATMs or make purchases at various points of sale that accept Maestro. The process involves inserting the card, entering a PIN, and following on-screen prompts. While Maestro is convenient and broadly accepted, it's advisable to carry cash as a backup, especially at smaller merchants that may not accept card payments. Overall, Maestro facilitates seamless transactions for both residents and travelers in Tanzania. Verve is a highly popular payment method in Tanzania, widely embraced by merchants both online and offline. It offers a secure and convenient way for users to make transactions, with acceptance at various establishments such as supermarkets, restaurants, hotels, and online retailers. To utilize Verve in Tanzania, individuals must possess a Verve card issued by a supporting bank. Payment typically involves card insertion or swiping, accompanied by entering a PIN, and some vendors may also facilitate contactless payments with Verve cards. Although widely accepted at major retailers and businesses with card facilities, it is advisable to confirm a merchant's acceptance beforehand. Overall, Verve provides residents and visitors in Tanzania with a trusted, flexible, and secure payment solution for their diverse transactional needs, blending convenience with peace of mind. ### UPI UPI (Unified Payments Interface) is used in Tanzania. UPI is a real-time payment system developed by the National Payments Corporation of India (NPCI) that allows users to link multiple bank accounts to a single mobile application. It enables users to make instant money transfers, pay bills, and make online purchases. UPI has gained popularity in Tanzania and is widely used for digital payments. ### Paytm Paytm is a popular mobile payment platform that is widely used in India, but it has also expanded its services to other countries, including Tanzania. In Tanzania, Paytm can be used for various purposes such as mobile recharges, bill payments, money transfers, and online shopping. ### M-Pesa M-Pesa, initially introduced in Kenya in 2007 and subsequently extended to various nations, including Tanzania, is a mobile money transfer service currently managed by Vodacom Tanzania, a subsidiary of Vodafone, in the Tanzanian market. Renowned for its convenience and accessibility, M-Pesa in Tanzania enables users to effortlessly conduct financial transactions through their mobile phones, encompassing activities such as money transfers, bill payments, and purchases. Additionally, the service facilitates cash withdrawals from authorized agents or ATMs, contributing to its widespread adoption as a popular and versatile payment method in the region. ### Tigo Pesa Tigo Pesa is a prominent mobile money service in Tanzania, operated by the telecommunications company Tigo. It enables users to send, receive, and store money through their mobile phones, serving as a versatile payment method for goods and services, including retail transactions, bill payments, airtime purchases, and online shopping. To utilize Tigo Pesa, users need an account with sufficient funds in their mobile wallet, and payments can be swiftly initiated by entering the recipient's phone number and the desired amount. The service guarantees instant processing, with both sender and recipient receiving confirmation messages. Tigo Pesa not only eliminates the need for cash but also offers a secure and convenient digital wallet accessible anytime, anywhere. Widely accepted across the country, it facilitates payments at various merchants and enables users to withdraw cash from authorized agents or ATMs. Overall, Tigo Pesa is a popular and widely embraced digital payment solution in Tanzania, offering accessibility, security, and convenience for both individuals and businesses. ### Airtel Money Airtel Money, offered by Airtel Tanzania, is a prominent mobile money service in the country, allowing users to conduct diverse financial transactions through their mobile phones. To utilize Airtel Money for payments, customers must first register for an account at an Airtel Money agent or Airtel shop. Deposits into the account can be made through agents, bank transfers, or mobile banking. The service enables payments at participating merchants, as well as money transfers between Airtel Money users. Initiating a payment involves dialing a USSD code, entering the recipient's details, amount, and a personal PIN for authentication. Airtel Money serves as a versatile payment option for utilities, groceries, transportation, online purchases, and more, promoting a secure and convenient alternative to cash or physical cards. Beyond payments, the service offers features like money transfers to bank accounts, cash withdrawals, airtime top-ups, and savings accounts, with transaction history and balances accessible through the Airtel Money app or USSD code. Overall, Airtel Money is a widely embraced and user-friendly mobile payment solution in Tanzania. ## Accepting International Card Payments from Tanzania If you run a business in Tanzania -- freelancer, agency, exporter, or online seller -- and need to invoice or sell to international clients, local payment methods alone aren't enough. M-Pesa and other local methods are unbeatable for domestic payments, but they don't accept overseas cards. A hosted payment link gives you a branded checkout page that accepts cards, Apple Pay, and Google Pay from clients anywhere in the world. Shuttle Links & Checkout connects you to a payment provider that supports international card payments, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Tanzania as a Platform For software platforms serving merchants in Tanzania, supporting local payment methods like M-Pesa and mobile money is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Tanzania? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-thailand/ --- # Thailand Payment Methods: 7 Essential Options (2026) | Shuttle > PromptPay, TrueMoney, Rabbit LINE Pay and more -- the complete list of payment methods Thai consumers actually use for online and in-store purchases. # Thailand Payment Methods: 7 Essential Options (2026) By Nick Dunse, June 20, 2023 PromptPay, TrueMoney, Rabbit LINE Pay and more -- the complete list of payment methods Thai consumers actually use for online and in-store purchases. Start collecting payments today Send payment links to your customers in Thailand -- no card machine, no website, no fuss. The growth of e-commerce in Thailand is propelled by increasing internet penetration and the widespread use of mobile devices, providing consumers with easier access to online shopping platforms. Government initiatives to promote the digital economy further contribute to a favorable environment for online businesses. Despite this growth, challenges persist. Trust issues in online transactions hinder consumer confidence, necessitating investments in secure payment systems and customer protection measures. Logistics infrastructure improvements are crucial to ensure timely and efficient product delivery. Additionally, raising awareness and providing education to small and medium-sized enterprises (SMEs) about the benefits of e-commerce is essential, as many lack the necessary skills and resources to establish an online presence. Despite these challenges, the future of e-commerce in Thailand appears promising, with the potential for significant regional market influence through strategic investments in infrastructure, technology, and education. ## Popular offline payment methods in Thailand ### Cash ### Bank Transfers ### Counter Service at Banks ### ATM Transfers ### Cheques ### Payment Cards ### Mobile Payments ### Debit Cards ### Payment by QR Code ### Convenience Stores ### Money Transfers ## List of payment methods in Thailand ### Mastercard Mastercard is widely accepted as a payment method in Thailand. It can be used at most hotels, restaurants, shops, and online retailers. Many ATMs also accept Mastercard for cash withdrawals. However, it is always a good idea to carry some cash as well, as there may be some smaller establishments that only accept cash payments. Additionally, it is important to notify your bank or credit card company before traveling to Thailand to ensure that your card will work internationally and to avoid any potential issues with using your Mastercard abroad. ### Visa Visa is widely accepted as a payment method in Thailand, making it a convenient option for tourists and locals alike. Whether you're shopping at a street market, dining at a restaurant, or booking a hotel room, you can use your Visa card to make a secure and hassle-free payment. Many merchants in Thailand also offer contactless payment options, allowing you to simply tap your card on the terminal to complete your transaction. Visa's acceptance in Thailand is a testament to the country's modern and progressive economy, which values convenience and accessibility for all consumers. So if you're planning a trip to Thailand, be sure to bring your Visa card along for a seamless payment experience. ### UnionPay UnionPay is a highly popular payment method in Thailand, widely accepted at major retailers, hotels, restaurants, and tourist attractions for both online and offline transactions. Users can simply present their UnionPay card at the point of sale or input card details for online purchases, with some merchants requiring a PIN for verification. The UnionPay mobile app offers an alternative payment option, enabling users to link their card to their mobile device and make payments through QR code scanning or contactless terminals. Despite its broad acceptance, there may be instances where smaller merchants do not support UnionPay, prompting the recommendation to carry cash or an alternative method like Visa or Mastercard. Overall, UnionPay provides travelers with a convenient and prevalent payment solution throughout their stay in Thailand. ### JCB JCB, or Japan Credit Bureau, serves as a prevalent payment method in Thailand, finding acceptance across a spectrum of establishments such as restaurants, hotels, department stores, and online retailers. To utilize JCB in the country, individuals need a JCB credit card issued by a supportive bank or financial institution, attainable through local banks or online application. With a JCB credit card, users can make purchases at any JCB-logo-displaying merchant by presenting the card to the cashier or inputting details for online transactions. The payment process occurs through the JCB network, and charges are applied to the credit card. JCB provides cardholders in Thailand with various perks, including discounts, cashback, and exclusive promotions, with some cards offering additional benefits like travel insurance for frequent travelers. It is essential to be aware that while widely accepted, not all merchants may support JCB, necessitating confirmation with the establishment or searching for the JCB logo. Overall, employing JCB as a payment method in Thailand affords convenience and versatility for both locals and tourists. ### PromptPay PromptPay, a government-backed initiative in Thailand, has become a popular payment method, facilitating instant and convenient transactions via mobile phones to promote cashless payments and financial inclusion. Users link their phone number or national ID to their bank account and can transfer money instantly to others by entering the recipient's details. This method is widely accepted by various merchants, including supermarkets, restaurants, online retailers, and street vendors, for both person-to-person and person-to-merchant transactions. The system's key advantages include its convenience, eliminating the need for cash and allowing payments anytime, anywhere. With over 60 million registered users as of 2021, PromptPay has gained widespread adoption, aided by government incentives, and has significantly transformed the payment landscape in Thailand, fostering a faster, more convenient, and secure digital economy. ### Alipay Alipay, the widely used Chinese mobile payment platform, has expanded its services to Thailand through partnerships with local banks and merchants. To utilize Alipay in Thailand, users must have a registered account linked to their Thai bank accounts. The Alipay app facilitates payments at various establishments, such as retail stores, restaurants, hotels, and online platforms, by allowing users to scan merchants' QR codes and input the payment amount. Beyond transactions, Alipay offers additional features, including money transfers, bill payments, and mobile phone credit top-ups. This integration provides a convenient and secure payment solution for both Chinese tourists and residents in Thailand, offering them the flexibility to make transactions without the need for cash or currency exchange. ### Google Pay Google Pay is available as a payment method in Thailand. Users can link their credit or debit cards to their Google Pay account and use it to make payments at participating merchants. Google Pay also supports peer-to-peer payments, allowing users to send money to friends and family. Additionally, Google Pay can be used for online purchases on websites and apps that accept Google Pay as a payment option. ### PayPal PayPal is a highly utilized payment method in Thailand, offering a secure and convenient means for users to make online payments and transfer money. Various online merchants in the country, spanning e-commerce, travel bookings, and digital services, accept PayPal as a payment option. To use PayPal in Thailand, individuals must create an account and link it to their bank account or credit card. Once set up, users can select the PayPal option at checkout on participating websites, where they will be redirected to the PayPal site to log in and confirm the payment. PayPal's buyer protection is an added advantage, enabling users to address issues like damaged or incorrect items through the resolution center. Beyond online payments, PayPal facilitates money transfers to friends and family domestically or internationally, accomplished through the website or mobile app by entering the recipient's email address or mobile number. Overall, PayPal provides a secure and user-friendly solution for online transactions in Thailand, with widespread acceptance and additional features like buyer protection and international money transfers. ## Accepting International Card Payments in Thailand Whether you sell to customers in Thailand from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. PromptPay is now the default for most Thai consumers -- but international card acceptance still matters for tourists and cross-border buyers. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Thailand, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Thailand as a Platform For software platforms serving merchants in Thailand, supporting local payment methods like PromptPay, local bank transfers, and QR code payments is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Thailand? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-the-netherlands/ --- # Payment Methods in the Netherlands: iDEAL, Cards & Klarna (2026) | Shuttle > iDEAL dominates Dutch online payments with over 60% market share. Explore all popular payment methods in the Netherlands including cards, PayPal, and... # Payment Methods in the Netherlands: iDEAL, Cards & Klarna (2026) By Nick Dunse, February 27, 2024 iDEAL dominates Dutch online payments with over 60% market share. Explore all popular payment methods in the Netherlands including cards, PayPal, and... Start collecting payments today Send payment links to your customers in the Netherlands -- no card machine, no website, no fuss. In the Netherlands, iDeal reigns supreme as the go-to online payment system, supported by major banks and constituting over 60% of online transactions. Alongside iDeal, credit cards and digital wallets like Visa, Mastercard, and PayPal are widely accepted, ensuring convenience and security for online shoppers. The country is also witnessing a surge in mobile payment solutions through apps like Tikkie and Bunq, particularly popular among younger generations. As e-commerce flourishes, the dynamic Dutch payment landscape is poised for further evolution to meet consumer demands. ## Popular offline payment methods in Netherlands ### Cash ### Mobile Payments ### Debit cards ## List of payment methods in Netherlands ### iDEAL iDEAL, a leading online payment method in the Netherlands, enables secure and direct transactions from users' bank accounts. Supported by major Dutch banks, it streamlines the payment process during online checkout. Customers select iDEAL, authenticate the payment through their bank's online platform, and promptly finalize the purchase. Widely embraced by online merchants, it eliminates the need for credit cards, offering a convenient and secure option. iDEAL dominates the Dutch online payment landscape, constituting over 50% of transactions, providing a seamless and trusted experience for both consumers and merchants. ### Maestro Maestro is a widely accepted payment method in the Netherlands. It is a debit card service that allows customers to make payments directly from their bank accounts. Maestro cards are issued by most Dutch banks and can be used at a wide range of merchants, including supermarkets, restaurants, and online retailers. The use of Maestro is particularly popular for small, everyday purchases. To make a payment with Maestro, customers simply need to insert their card into a card reader and enter their PIN code. SEPA Direct Debit is a prevalent payment method in the Netherlands, allowing businesses to collect recurring payments directly from customers' bank accounts. Customers provide their IBAN and BIC, authorizing businesses to initiate transactions. This method offers convenience and cost-effectiveness for businesses, reducing manual invoicing and administrative costs. Customers benefit from a hassle-free, timely payment process without manual intervention. Businesses require a valid SEPA Direct Debit mandate to use this method, obtainable through various channels. Transactions are initiated through online banking or third-party providers, processed nationally, and settled within a few days. Overall, SEPA Direct Debit is widely accepted and favored for recurring payments in the Netherlands. V Pay is a popular payment method in the Netherlands. It is a debit card that is accepted at most merchants and can be used for both online and in-store purchases. V Pay cards are issued by various banks in the Netherlands, including ING, Rabobank, and ABN AMRO. It is widely accepted and can be used at a variety of merchants, including supermarkets, restaurants, and online retailers. Additionally, V Pay cards are equipped with chip and PIN technology, providing an extra layer of security for cardholders. ### Mastercard Mastercard is widely accepted in the Netherlands at retail stores, restaurants, and online merchants. Issued by many Dutch banks, it's a popular payment choice. To use it, present the card or enter details for online purchases. Some places accept contactless payments. While widely accepted, smaller businesses may prefer cash. Carry some, especially in rural areas. Check with your bank about foreign transaction fees before using Mastercard abroad in the Netherlands. ### Visa Visa is widely used for payments in the Netherlands, accepted at retail stores, restaurants, hotels, and online merchants. Dutch banks issue Visa debit and credit cards, making it convenient for locals and tourists. Contactless payments with Visa cards are also gaining popularity for quick and convenient transactions. ### PayPal PayPal is widely accepted as a payment method in the Netherlands. Many online retailers, both local and international, offer PayPal as an option for customers to make purchases. Additionally, PayPal can also be used for peer-to-peer payments and money transfers within the country. To use PayPal in the Netherlands, individuals need to create a PayPal account and link it to their bank account or credit card. Once the account is set up, they can use PayPal to make secure and convenient online payments. ### Apple Pay Apple Pay is a digital wallet service by Apple that lets users make secure mobile payments with their Apple devices. While currently unavailable in the Netherlands, there are indications that it might launch soon. Dutch banks like ING, Rabobank, and ABN Amro are reportedly working on integrating Apple Pay. Although no official launch date has been announced, expectations are set for 2020. Once introduced, users can add cards to their Apple Wallet for contactless payments at participating merchants, offering a secure and convenient alternative to physical cards or cash, with features like tokenization technology and authentication through Touch ID or Face ID. ### American Express American Express is accepted as a payment method in the Netherlands. Many merchants, including restaurants, hotels, and retail stores, accept American Express cards for payment. Additionally, American Express has its own network of ATMs in the Netherlands, where cardholders can withdraw cash. However, it is worth noting that American Express may not be as widely accepted as other payment methods such as Visa or Mastercard. It is always a good idea to check with the merchant beforehand to ensure that they accept American Express as a form of payment. ### Discover Discover is not widely accepted as a payment method in the Netherlands. The most commonly accepted payment methods in the Netherlands are debit cards (such as Maestro) and credit cards (such as Visa and Mastercard). Some businesses may accept Discover, but it is not as common as other card brands. It is always best to check with the specific business or establishment to see if they accept Discover before attempting to use it as a payment method. ### Google Pay Google Pay is currently available as a payment method in the Netherlands. Users can add their credit or debit cards to the Google Pay app and use it to make payments at participating merchants. Google Pay also supports contactless payments using NFC technology, allowing users to simply tap their phone on a payment terminal to complete a transaction. Additionally, Google Pay can be used for online purchases and in-app payments on compatible websites and apps. ### Klarna Klarna is a popular payment method in the Netherlands. It allows customers to make purchases online and pay for them later, either in full or in installments. Klarna offers a smooth and convenient checkout process, making it a preferred choice for many Dutch consumers. With Klarna, customers can shop at various online stores and select Klarna as their payment option at checkout. They can then choose to pay immediately, pay later within 14 days, or split their payment into monthly installments. Klarna also provides buyer protection and customer support, ensuring a secure and reliable payment experience for Dutch shoppers. SOFORT is a widely used payment method in the Netherlands, enabling customers to make online payments directly from their bank accounts without needing a credit card. Users choose SOFORT at checkout, select their bank, and are redirected to their bank's online platform to securely authorize the payment. This method is favored by those who don't use or have credit cards. It's a popular and secure option for various online transactions, from e-commerce to travel bookings. ### JCB JCB, also known as Japan Credit Bureau, is a popular payment method in Japan. However, it is not widely accepted in the Netherlands. Most merchants in the Netherlands do not accept JCB cards for payment. Therefore, if you are traveling to the Netherlands and plan to use your JCB card, it is advisable to carry an alternative payment method such as Visa or Mastercard, which are widely accepted in the country. ### UnionPay UnionPay is accepted as a payment method in the Netherlands. Many merchants, especially those that cater to tourists, accept UnionPay cards for payment. Additionally, some ATMs in the Netherlands also accept UnionPay cards for cash withdrawals. However, it is important to note that not all merchants and ATMs in the Netherlands accept UnionPay, so it is advisable to carry an alternative payment method such as a Visa or Mastercard as a backup. Amazon Pay in the Netherlands is a secure and convenient payment option that enables users to make purchases on external websites using their Amazon account. This method streamlines the checkout process by allowing customers to utilize saved payment methods and shipping addresses from their Amazon account. It ensures a seamless experience, offering the same security and buyer protection as on Amazon itself. With the option to use one account across multiple websites, Amazon Pay provides a trusted and reliable solution for online transactions in the Netherlands. ### Alipay Alipay, a popular mobile payment platform in China, is accepted in the Netherlands, particularly at merchants catering to Chinese tourists or those partnered with Chinese companies. To use Alipay, you need an account and a linked bank card. After setting up the account, payments can be made at participating merchants by scanning QR codes and confirming with a PIN or biometric authentication. Not all merchants accept Alipay, so it's advisable to check beforehand. While convenient for Chinese tourists and Alipay users, alternative payment methods may be needed due to varying merchant acceptance. Diners Club International provides a global credit card network, including in the Netherlands. Accepted at various establishments, these cards offer benefits like travel insurance, purchase protection, and access to airport lounges. Users can make both in-person and online purchases, earning rewards points for redemption. While widely accepted, it's advisable to confirm merchant acceptance beforehand. ### WeChat Pay WeChat Pay is a widely used mobile payment method in China but not commonly accepted in the Netherlands. However, some Dutch merchants catering to Chinese customers do accept it. Merchants interested in accepting WeChat Pay can contact the service directly for information on integration and requirements. Since WeChat Pay is mainly used by Chinese consumers, businesses targeting or having a customer base from China may benefit more from accepting it. ### Trustly Trustly is a popular payment method in the Netherlands. It allows users to make secure online payments directly from their bank accounts. Trustly is widely accepted by online merchants and is a convenient and safe way to make payments without the need for credit cards or e-wallets. Many Dutch consumers prefer Trustly because it offers fast and easy transactions, with funds being transferred instantly from the user's bank account to the merchant. Additionally, Trustly is regulated by the Swedish Financial Supervisory Authority, providing an extra layer of security for users. Overall, Trustly is a trusted and widely used payment method in the Netherlands. PaySafeCard is a widely-used prepaid payment option in the Netherlands, offering a secure and convenient way for users to make online purchases without needing a bank account or credit card. Users can buy physical cards with unique 16-digit PIN codes from various retail locations and use them to pay on websites across different categories, including gaming, e-commerce, and digital content. The system provides anonymity and security, and users can also opt for managing their balance online without the need for a physical card. ## Accepting International Card Payments in the Netherlands Whether you sell to customers in the Netherlands from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. iDEAL handles around 60% of Dutch online payments -- card-only checkouts lose most Dutch shoppers. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for the Netherlands, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in The Netherlands as a Platform For software platforms serving merchants in the Netherlands, supporting local payment methods like iDEAL, SEPA, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe, Adyen and Mollie -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in the Netherlands? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Mollie](/payment-providers/mollie/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-the-philippines/ --- # Payment Methods in the Philippines: GCash, Cards & COD (2026) | Shuttle > GCash and cash on delivery lead Filipino payments. Explore all popular payment methods in the Philippines including Maya, cards, and bank transfers. # Payment Methods in the Philippines: GCash, Cards & COD (2026) By Nick Dunse, May 11, 2021 GCash and cash on delivery lead Filipino payments. Explore all popular payment methods in the Philippines including Maya, cards, and bank transfers. Start collecting payments today Send payment links to your customers in the Philippines -- no card machine, no website, no fuss. Cash on delivery (COD) is a widely favored payment method in the Philippines, particularly for online purchases, as there is a prevailing lack of trust in digital transactions and apprehensions about potential fraud. This method enables customers to settle their payments in cash upon receiving their orders, instilling a sense of security and confidence in the transaction process. Additionally, the remittances sent by overseas Filipino workers (OFWs) significantly contribute to the country's payment ecosystem, with services like Western Union, MoneyGram, and Xoom being commonly utilized for these financial transfers. Despite the potential for the future popularity of e-Wallets, the current landscape is predominantly shaped by online banking and traditional cash transactions, encompassing COD and remittances. ## Popular offline payment methods in the Philippines ### Cash ### Bank Transfers ### Over-the-Counter (OTC) ### Mobile Payments ### Remittance Centers ### Cheques ### Debit Cards ### Barter or Trade ### Convenience Stores ## List of payment methods in the Philippines ### Visa Visa is widely accepted as a payment method in the Philippines. It can be used for various transactions, including shopping, dining, and online purchases. Many establishments, such as malls, restaurants, and hotels, accept Visa cards. Additionally, Visa cards can also be used to withdraw cash from ATMs in the Philippines. Mastercard enjoys widespread acceptance as a versatile payment method for both online and offline transactions. Whether you're shopping at retail stores, dining at restaurants, staying at hotels, or making online purchases, Mastercard is a convenient choice. To utilize Mastercard for payments, one must possess a credit or debit card issued by a bank or financial institution, and the application process can be initiated through the bank or its website. Once you have a Mastercard, it can be used at various merchants, and for online transactions, you simply choose Mastercard as your payment option and input your card details. In-store purchases can be completed by either swiping the card or using contactless payment if supported. Gcash, operated by Globe Telecom, stands as a prominent mobile wallet in the Philippines, facilitating users in conducting diverse financial transactions through their mobile phones. Renowned for its convenience and security, Gcash serves as a versatile payment method, enabling users to effortlessly settle payments for a myriad of goods and services both online and offline by scanning QR codes or entering merchant mobile numbers. Accepted widely by various merchants, including supermarkets, restaurants, and online shops, Gcash extends its utility to bill payments and government services. Beyond payments, the platform offers additional financial services, such as money transfers, cash withdrawals, and savings accounts. Users can link their Gcash accounts to bank accounts or credit cards for seamless top-ups. To initiate Gcash usage, users download the app, register, and load funds through diverse channels like bank transfers or remittance centers. As a catalyst in transitioning Filipinos from traditional cash transactions to digital payments, Gcash has emerged as a favored choice, rendering financial transactions more accessible and efficient. PayPal stands as a widely embraced payment method, facilitating secure online transactions, money transfers, and receipt of payments. Numerous online merchants and service providers in the country acknowledge PayPal, offering users a convenient means to make online purchases or settle service payments. To utilize PayPal in the Philippines, individuals must create an account and link it to their bank account or credit card. Once the account is established, users can effortlessly execute payments by opting for PayPal on supported websites or applications. The process involves being redirected to the PayPal website to log in and confirm the payment. Additionally, PayPal extends its functionality through a mobile app, empowering users to make payments on the move by downloading the app on their smartphones and linking it to their PayPal account. Beyond facilitating online payments, PayPal enables users in the Philippines to receive payments from other PayPal users or businesses, proving especially beneficial for freelancers and small business operators engaging with international clients. In essence, PayPal serves as a reliable and secure avenue for individuals and businesses in the Philippines to conduct seamless online transactions. ### GrabPay GrabPay is a mobile wallet and payment method that can be used in the Philippines. It is accepted as a payment option in various merchants, including restaurants, shops, and online platforms. To use GrabPay, you need to download the Grab app on your smartphone and create an account. You can then link your credit or debit card to your GrabPay wallet or top up your wallet using cash at selected locations. Once your GrabPay wallet is funded, you can use it to make payments by scanning the merchant's QR code or entering the merchant's mobile number. GrabPay also offers various promotions and rewards for using their service. ## Accepting International Card Payments in the Philippines Whether you sell to customers in the Philippines from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. GCash, Maya, and cash on delivery drive most Filipino online payments -- card-only checkouts convert poorly. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for the Philippines, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in The Philippines as a Platform For software platforms serving merchants in the Philippines, supporting local payment methods like GCash, Maya, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in the Philippines? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-the-united-kingdom/ --- # Payment Methods in the UK: Cards, Open Banking & Digital Wallets (2026) | Shuttle > Explore the UK's most popular payment methods from debit and credit cards to open banking, Apple Pay, Google Pay, and buy-now-pay-later services like... # Payment Methods in the UK: Cards, Open Banking & Digital Wallets (2026) By Nick Dunse, December 24, 2022 Explore the UK's most popular payment methods from debit and credit cards to open banking, Apple Pay, Google Pay, and buy-now-pay-later services like... Start collecting payments today Send payment links to your customers in the United Kingdom -- no card machine, no website, no fuss. The United Kingdom leads the way in Europe's e-commerce market, thanks to its nearly 69 million population and widespread internet access in 97% of households, as per IBISWorld. In terms of online payments, PayPal and debit/credit cards are dominant, with broad acceptance among all demographics. Research by Marqeta indicates that 77% of UK consumers have adopted digital wallets and mobile payments, with PayPal being a top choice. ## Popular offline payment methods in the UK ### Direct Debit ### Cash ### Cheque ### Bank Transfers ### Postal Orders ### Banker's Drafts ### Mobile Payments ### Payment Cards ## List of payment methods in the UK ### Visa Visa is widely accepted as a payment method in the United Kingdom. It can be used for various types of transactions, including in-store purchases, online shopping, and bill payments. Most retailers, restaurants, and service providers in the UK accept Visa cards. Visa cards issued by banks and financial institutions around the world are generally accepted in the UK. ### Mastercard Mastercard is one of the largest card schemes in the world and has a strong presence in the United Kingdom. It is widely accepted by merchants across the country and is a popular choice for consumers when it comes to credit card payments. In addition to its regular credit cards, Mastercard also offers a range of co-branded credit cards in partnership with various banks and financial institutions in the UK. These co-branded cards often come with additional benefits and rewards, such as cashback, airline miles, or loyalty points. ### PayPal PayPal is widely accepted as a payment method in the United Kingdom. It is used by individuals and businesses for online purchases, as well as for sending and receiving money. Many online retailers and service providers offer PayPal as a payment option at checkout, making it convenient for customers to make secure transactions. Additionally, PayPal offers buyer protection and dispute resolution services, which can provide added peace of mind for both buyers and sellers. ### American Express American Express is widely accepted as a payment method in the United Kingdom. It can be used at most major retailers, restaurants, hotels, and online merchants. However, it is worth noting that American Express may not be accepted at some smaller establishments or businesses that have a lower volume of transactions. BACS Direct Debit is a popular payment method in the United Kingdom. It allows individuals and businesses to make regular payments directly from their bank account to another bank account. This can be used for various types of payments, such as utility bills, subscriptions, and loan repayments. BACS Direct Debit offers several benefits for both payers and payees. Diners Club International is a global payment network that offers credit cards to consumers and businesses. While Diners Club cards are accepted at millions of locations worldwide, including in the United Kingdom, they are not as widely accepted as other major credit card brands like Visa and Mastercard. Some smaller businesses or establishments may not accept Diners Club cards due to higher transaction fees or limited familiarity with the brand. ### Discover Discover is not widely accepted as a payment method in the United Kingdom. While Discover is a major credit card network in the United States, it has limited acceptance outside of the US. Some merchants in the UK may accept Discover, but it is not as commonly accepted as other credit cards. ### Apple Pay Apple Pay allows users to make payments using their iPhone, Apple Watch, iPad, or Mac devices. Users can add their credit or debit cards to the Apple Wallet app and then use their device to make contactless payments at participating retailers. Apple Pay is accepted at a wide range of retailers in the United Kingdom, including supermarkets, restaurants, clothing stores, and more. It can also be used for online purchases within apps and websites that support Apple Pay. ### Maestro Maestro is a popular payment method in the United Kingdom. It is widely accepted by most retailers, both online and offline. Maestro cards are issued by various banks and can be used for making purchases, withdrawing cash from ATMs, and making online payments. In addition to physical cards, Maestro also offers virtual cards that can be used for online purchases. Maestro is a convenient and widely accepted payment method in the United Kingdom, offering customers a secure way to make purchases both online and offline. Afterpay and Clearpay are both popular buy now, pay later payment methods that allow customers to make purchases and pay for them in installments. These payment options are available in the United Kingdom and are accepted by a wide range of retailers. They provide convenient and flexible payment options for customers in the United Kingdom, allowing them to make purchases and pay for them in installments without incurring interest or fees if payments are made on time. UnionPayU is a popular payment method in the United Kingdom. It is widely accepted by merchants and retailers across the country. UnionPay cards can be used for various types of transactions, including online shopping, in-store purchases, and cash withdrawals from ATMs. Many major retailers, including department stores, supermarkets, and luxury brands, accept UnionPay as a form of payment. Additionally, UnionPay is accepted at a large number of hotels, restaurants, and entertainment venues in the UK. UnionPay provides a secure payment platform and offers various features such as contactless payments and mobile payments through its mobile app. ### Klarna Klarna is a popular payment method in the United Kingdom. It allows customers to make purchases online and pay for them later in installments. Klarna offers flexible payment options, including the ability to split the cost into three equal payments or to pay in full 30 days after the purchase. Klarna also offers a mobile app that allows customers to manage their payments, view their purchase history, and make additional purchases using Klarna's Pay later feature. ### JCB JCB is a popular payment method in the United Kingdom. JCB cards are widely accepted at various merchants, including retail stores, restaurants, and online platforms. JCB is known for its secure and convenient payment process, making it a preferred choice for many consumers in the UK. Additionally, JCB offers various benefits and rewards programs to its cardholders, further enhancing its popularity as a payment method in the country. ### Alipay Alipay, the popular Chinese mobile payment platform, is now accepted as a payment method in the United Kingdom. This means that Chinese tourists and residents in the UK can use Alipay to make purchases at participating merchants. In addition to making payments, Alipay also offers other services such as money transfers, bill payments, and even booking flights and hotels. Amazon Pay is a popular payment method in the United Kingdom. It allows customers to make purchases on various websites using their Amazon account information. This means that customers can use their saved payment methods and shipping addresses from Amazon to complete their purchases quickly and securely. ### Google Pay Google Pay is a popular digital wallet and payment method that allows users to make purchases and send money using their mobile devices. In the United Kingdom, Google Pay is widely accepted at various retailers, online merchants, and service providers. It can be used for in-store purchases at supermarkets, restaurants, shops, and other businesses that accept contactless payments. It can also be used for online purchases on websites and apps that support Google Pay as a payment option. In addition to making payments, Google Pay also allows users to send money to friends and family members. ### WeChat Pay WeChat Pay is a popular mobile payment method in China, but it is not widely accepted in the United Kingdom. While some businesses may accept WeChat Pay as a form of payment, it is not as commonly used or supported as other payment methods like credit cards or mobile payment apps such as Apple Pay or Google Pay. PaySafeCard is a popular prepaid payment method in the United Kingdom. It allows users to make online purchases without the need for a bank account or credit card. PaySafeCard vouchers can be purchased at various retail locations, such as supermarkets, convenience stores, and petrol stations. It is accepted by a wide range of online merchants in the UK, including gaming sites, online retailers, and digital service providers. In addition to online payments, it can also be used to top up e-wallets and prepaid cards, making it a versatile payment option for UK consumers. ### Samsung Pay Samsung Pay is a mobile payment service that allows users to make payments using their Samsung smartphones or smartwatches. It is widely accepted at most major retailers and businesses that accept contactless payments. Samsung Pay also supports loyalty cards and gift cards, allowing users to store and use these cards digitally within the app. This eliminates the need to carry physical cards and makes it easier for users to earn rewards and redeem offers. ### Trustly Trustly is a popular payment method in the United Kingdom. It allows users to make secure online payments directly from their bank accounts. Users can easily transfer funds from their bank accounts to pay for goods and services, without the need for credit cards or other payment methods. ## Accepting International Card Payments in the UK Whether you sell to customers in the UK from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards are universal in the UK but Open Banking and digital wallets are increasingly expected at checkout. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for the UK, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in The UK as a Platform For software platforms serving merchants in the UK, supporting local payment methods like BACS Direct Debit, Open Banking, and Faster Payments is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe, Adyen and Worldpay -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in the United Kingdom? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-the-usa/ --- # Payment Methods in the USA: Cards, ACH, Venmo & Wallets (2026) | Shuttle > Explore the most popular payment methods in the USA from credit and debit cards to ACH transfers, Venmo, Apple Pay, and buy-now-pay-later options. # Payment Methods in the USA: Cards, ACH, Venmo & Wallets (2026) By Nick Dunse, December 14, 2022 Explore the most popular payment methods in the USA from credit and debit cards to ACH transfers, Venmo, Apple Pay, and buy-now-pay-later options. Start collecting payments today Send payment links to your customers in the USA -- no card machine, no website, no fuss. The e-commerce payment landscape underwent substantial transformations driven by the surge in mobile payments and the adoption of digital wallets such as Apple Pay, Google Pay, and Samsung Pay. The COVID-19 pandemic further accelerated the shift towards contactless payments, encompassing both card and mobile methods. Alternative payment methods, notably Buy Now, Pay Later (BNPL) and cryptocurrency payments, gained prominence. Heightened security concerns led to the implementation of advanced measures like two-factor authentication and biometric verification. Subscription-based models, particularly in streaming services and software-as-a-service, influenced payment preferences. Regulatory changes, including updates to data protection laws, underscored the importance of adherence to standards like PCI DSS. Enhancing user experience became a focal point, with streamlined checkouts, one-click payments, and guest checkout options gaining popularity. Cross-border e-commerce transactions expanded, necessitating payment providers to offer solutions for currency conversion and localized payment options. Artificial Intelligence (AI) and Machine Learning (ML) played pivotal roles in fraud detection, risk management, and personalizing payment experiences. Additionally, a growing consumer emphasis on sustainability prompted e-commerce businesses to explore eco-friendly payment options. ## Popular offline payment methods in the US ### Cash ### Debit Cards ### Cheques ### Money Orders ### Wire Transfers ### Mobile Payments ## List of payment methods in the US Visa stands as a highly prevalent and favored payment method in the United States, holding a prominent position among credit card networks. With widespread acceptance at millions of locations, encompassing retail outlets, restaurants, and online platforms, Visa offers users a versatile and convenient means of payment. The array of credit and debit card options, ranging from traditional to rewards and prepaid cards, caters to diverse consumer preferences. Ensuring flexibility, Visa cards can be utilized for both in-person and online transactions. Beyond its ubiquity, Visa extends additional advantages to cardholders, such as fraud protection, purchase security, and extended warranties. As a result, Visa not only simplifies transactions but also enhances the overall security and convenience of financial transactions for consumers in the United States. ### Mastercard Mastercard is widely accepted as a payment method in the United States. It can be used at millions of locations, including retail stores, restaurants, online merchants, and more. Mastercard offers various types of cards, including credit cards, debit cards, and prepaid cards, which can be used for making purchases and accessing cash at ATMs. Additionally, many banks and financial institutions in the US issue Mastercard-branded cards to their customers. Mastercard also provides additional benefits and features to cardholders, such as rewards programs, purchase protection, and travel insurance. Overall, Mastercard is a convenient and widely accepted payment method in the USA. Affirm is a payment method that can be used in the USA. Affirm allows customers to make purchases and pay for them over time with fixed monthly payments. It is available at a wide range of retailers and online stores in the USA. Please refer to > https://www.affirm.com/how-it-works ### American Express American Express is widely accepted as a payment method in the United States. It is accepted at millions of merchants, including restaurants, retailers, online stores, and more. American Express cards can be used for both in-person and online purchases, making it a convenient payment option for consumers. Additionally, American Express offers various rewards and benefits to cardholders, such as cash back, travel rewards, and purchase protection. Overall, American Express is a popular and trusted payment method in the USA. Diners Club International, established in 1950, stands as one of the pioneering credit card companies in the United States, renowned for introducing the concept of charge cards. Presently, it operates as a subsidiary under Discover Financial Services. Diners Club cards serve as a globally accepted payment method, usable at millions of locations worldwide, encompassing restaurants, hotels, airlines, and retail stores. Cardholders enjoy diverse benefits, including travel insurance, airport lounge access, and rewards programs, while also benefiting from security features like fraud protection and zero liability for unauthorized charges. Utilizing a Diners Club card in the United States involves presenting the card at the point of sale or entering card information for online transactions, with merchants processing payments through the extensive Diners Club network. Overall, Diners Club remains a widely embraced and versatile payment option in the United States, offering a range of advantages to its users. ### Klarna Klarna, a Swedish fintech company, has gained prominence for its buy now, pay later payment solution, allowing customers to make online purchases and pay in installments. Recently expanding to the United States, Klarna is now a payment option on various American online retailers' websites. Users can choose Klarna at checkout and opt for installment plans, ranging from four equal payments to extending over six to 36 months. To use the service, customers must create an account, undergo a quick credit check, and, if approved, proceed with their purchase, adhering to the agreed-upon installment schedule. Klarna's appeal in the U.S. is amplified by additional features such as price drop notifications, enabling users to request refunds for decreased item prices within a specific timeframe. Overall, Klarna offers a flexible payment option, gaining popularity as more U.S. retailers adopt it. ### Discover Discover is a widely accepted payment method in the United States, ranking among major credit card networks like Visa, Mastercard, and American Express. With the ability to make purchases at numerous merchants, including online retailers, brick-and-mortar stores, and restaurants, Discover offers cardholders various benefits such as cashback rewards, exclusive discounts, and access to special events. The card also provides essential features like fraud protection and 24/7 customer service support. To utilize Discover for payments, users can present their card at the point of sale or enter card information for online transactions, potentially requiring additional verification like a signature or PIN. Its popularity stems from its broad acceptance, rewards program, and customer-centric advantages. ### Apple Pay Apple Pay, a mobile payment and digital wallet service by Apple Inc., facilitates seamless transactions using iPhones, Apple Watches, iPads, or Mac devices at various retailers, online stores, and apps in the United States. Users add credit or debit cards, loyalty, and gift cards to the Wallet app for easy access. Payments are authorized through contactless terminals, Face ID, or Touch ID. Major retailers like Walmart, Target, Best Buy, and Starbucks accept Apple Pay, which is also applicable for online purchases. The service extends beyond payments, enabling users to send and receive money instantly through the Messages app via Apple Cash. Not only does Apple Pay provide convenience, but it also enhances security with biometric authentication and tokenization, eliminating the need for physical cards. ACH Direct Debit is a prevalent payment method in the United States, allowing businesses to automatically collect payments from customers' bank accounts for recurring expenses like subscriptions and utility bills. Customers provide their bank details, and after authorization, businesses securely store this information to initiate seamless payment transactions. Regulated by the National Automated Clearing House Association (NACHA), ACH Direct Debit follows established rules to ensure secure and efficient processing. This method streamlines payment processes, eliminating the need for manual monthly payments and providing both businesses and customers with a convenient and hassle-free financial solution. ### PayPal PayPal is a widely accepted payment method in the United States. It allows users to make online payments, send money to friends and family, and receive payments from others. PayPal can be used to make purchases on various e-commerce websites, including popular retailers like Walmart, Target, and Amazon. Additionally, many small businesses and independent sellers also accept PayPal as a payment option. Users can link their bank accounts, credit cards, or debit cards to their PayPal account to fund their transactions. PayPal offers buyer protection and dispute resolution services, providing an added layer of security for online transactions. Overall, PayPal is a convenient and secure payment method for individuals and businesses in the United States. ### Google Pay Google Pay, developed by Google, is a versatile digital wallet and online payment system designed for Android devices. In the United States, users can employ Google Pay in various ways, including contactless in-store payments by tapping their Android devices on supported terminals using linked credit or debit cards. Additionally, the platform facilitates online purchases on websites and apps, offering a streamlined checkout process with saved payment information. Google Pay enables peer-to-peer payments, allowing users to transfer money directly from their bank accounts or Google Pay balance to friends and family. Moreover, in select cities, the service extends to transit payments, where users can utilize Google Pay to pay for public transportation fares by adding their transit card to the app. To access these features, users need to download the app, set up an account, and add their preferred payment methods for a seamless payment experience wherever Google Pay is accepted. ### JCB JCB, or Japan Credit Bureau, is a prominent credit card issuer in Japan, globally recognized but less commonly accepted in the United States. Despite its limited acceptance, certain U.S. merchants, particularly those catering to international clientele or in partnership with JCB, do support it as a payment method. To locate such merchants, JCB offers a merchant locator tool on its website, enabling users to search by location and filter based on specific services or industries. Some online retailers also accept JCB, identifiable by the JCB logo or inclusion in the list of accepted payment methods during online checkout. It's essential to acknowledge that JCB may not have as widespread acceptance as major credit card brands like Visa or Mastercard in the United States, emphasizing the importance of having alternative payment methods when making purchases or traveling in the country. Cash App Pay is a mobile payment service available in the United States, enabling users to send and receive money through their smartphones. Accessed via the Cash App mobile app, users can link their bank accounts or debit cards to facilitate transactions. Payments are made by scanning QR codes or entering a merchant's identifier, offering a secure and convenient alternative to cash or credit cards. The service supports bill splitting and facilitates sending money to friends and family. Beyond payments, Cash App provides features like buying and selling Bitcoin, stock investments, and direct deposits. Users can also opt for a Cash Card, a customizable debit card linked to their Cash App account for purchases and ATM withdrawals. With its user-friendly interface, security measures, and additional financial functionalities, Cash App Pay has gained popularity as a versatile payment method in the United States. ### UnionPay UnionPay is a prevalent Chinese payment method widely embraced in China and across Asia but is less commonly accepted in the United States compared to mainstream options like Visa or Mastercard. While some US merchants may support UnionPay, its availability is not as widespread, making it advisable for visitors to check with merchants in advance. Some US banks do issue UnionPay cards, enabling their use at establishments that accept UnionPay. Despite its acceptance at select locations, UnionPay is not as ubiquitous or widely utilized as other payment methods in the United States. ### Samsung Pay Samsung Pay is a mobile payment service available in the United States, enabling users to make payments through their Samsung smartphones or smartwatches at any contactless payment-accepting merchant. To use the service, users add credit or debit card information, either by taking a photo or entering details manually. Employing both Near Field Communication (NFC) and Magnetic Secure Transmission (MST) technologies, Samsung Pay allows contactless payments at NFC-enabled terminals and traditional magnetic stripe card terminals. The platform extends support to loyalty and gift cards, providing users with a comprehensive digital wallet experience. Samsung Pay offers additional features such as transaction history, rewards programs, and special offers, allowing users to earn points or cash back on purchases redeemable for various rewards. Overall, Samsung Pay presents a secure and convenient payment solution with widespread acceptance in the United States, coupled with enticing benefits like rewards and exclusive offers. ### Maestro Maestro is not widely embraced as a payment method in the United States. Although Maestro is a well-known debit card brand in numerous countries, it is not as prevalent in the US. The majority of merchants in the US primarily accept credit cards, such as Visa, Mastercard, American Express, and Discover. A few merchants may accept debit cards with the Visa or Mastercard logo, but the acceptance of Maestro specifically is restricted. It is always advisable to verify with the merchant beforehand to ascertain if they accept Maestro as a form of payment. ### Alipay Alipay, a widely used mobile payment platform in China, faces limited acceptance in the United States, with its usage primarily concentrated among merchants catering to Chinese tourists or having ties with Chinese companies. Despite this, Alipay has been actively expanding its presence in the US by forming partnerships with payment processors and financial institutions. The company has introduced a mobile app for US users, facilitating payments at participating merchants. Although Alipay's adoption in the US is currently overshadowed by more established payment methods like credit cards and popular mobile wallets, such as Apple Pay and Google Pay, its growth is anticipated as more merchants recognize the opportunity to attract Chinese consumers accustomed to utilizing Alipay for their daily transactions. ### WeChat Pay WeChat Pay, a widely used mobile payment platform in China, faces limited acceptance in the United States. While some US merchants, particularly luxury retailers such as Bloomingdale's and Saks Fifth Avenue, along with certain restaurants and hotels catering to Chinese tourists, do accept WeChat Pay, its availability is not as extensive as other mobile payment options like Apple Pay or Google Pay. To utilize WeChat Pay in the US, individuals must have a WeChat account linked to their bank account or credit card, allowing them to make transactions through the WeChat app at participating locations. Despite its presence, WeChat Pay may not be a convenient choice for everyday purchases in the US due to its relatively limited acceptance compared to other more prevalent mobile payment methods. Amazon Pay is a digital wallet service by Amazon, allowing users to employ their Amazon account for payments on external websites and apps. Available in the USA, it streamlines the online purchase process by enabling customers to select the Amazon Pay option at checkout, where they can log in with their Amazon credentials and choose from associated payment methods like credit cards or bank accounts. This not only ensures security but also enhances convenience by eliminating the need to input payment details on multiple platforms. Amazon Pay is renowned for its reliability, offering a familiar and trusted method for users to make online transactions, utilizing the same payment methods and shipping addresses associated with their Amazon accounts, ultimately expediting the checkout process. ### Zip Zip is a buy now, pay later service available at participating online and in-store retailers in the United States. Customers can sign up for an account on the Zip website or app, select Zip as their payment option during checkout, and, if approved, choose a repayment plan that suits them. The service offers flexible options, including interest-free plans for smaller purchases and interest-bearing plans for larger ones, with weekly, bi-weekly, or monthly payment choices. Zip aims to give customers greater financial flexibility, enabling them to manage their budget by spreading out the cost of purchases over time. It's important to be aware that Zip may entail fees or interest charges, depending on the chosen repayment plan, necessitating a careful review of terms and conditions before use. Overall, Zip serves as an alternative payment method for U.S. customers seeking installment-based payment options. Afterpay and Clearpay are leading buy now, pay later services that enable consumers to make purchases and divide payments into four equal installments, with the first payment due at the time of purchase and subsequent payments every two weeks. Afterpay, established in Australia in 2015 and later expanding to the United States in 2018, is prominent in the U.S. market, while Clearpay, launched in the United Kingdom in 2015, has a stronger presence in the UK and Europe. Both services operate on interest-free models, providing an appealing option for budget-conscious shoppers seeking to avoid immediate full payments and credit card debt. The user process involves selecting Afterpay or Clearpay at checkout, creating an account, providing payment information, and, upon approval, completing the purchase with the first installment. As these services gain popularity, an increasing number of retailers are expected to adopt them to attract customers and enhance sales. PaySafeCard, a popular prepaid payment method, enables users to make online purchases without requiring a bank account or credit card. Despite its popularity, PaySafeCard faces limited acceptance in the United States, where credit cards, debit cards, and digital wallets like PayPal dominate the market. The prevalence of these alternative payment methods, coupled with regulatory variations among states, contributes to PaySafeCard's restricted availability. Some online stores and gaming platforms in the US do accept PaySafeCard, but its usage remains comparatively limited. Interested users can verify merchant acceptance through the PaySafeCard website or customer support, emphasizing the importance of checking with individual retailers before using PaySafeCard for online transactions. ## Accepting International Card Payments in the US Whether you sell to customers in the USA from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. Cards dominate the US but ACH, Venmo, Apple Pay, and BNPL are standard checkout expectations for online businesses. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for the USA, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in The USA as a Platform For software platforms serving merchants in the USA, supporting local payment methods like ACH, Venmo, and domestic card networks is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Stripe and Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in the USA? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-most-popular-payment-methods-in-vietnam/ --- # Payment Methods in Vietnam: MoMo, Cards & Bank Transfers (2026) | Shuttle > Discover Vietnam's top payment methods including MoMo wallet, bank transfers, credit cards, and cash on delivery as digital payments grow rapidly. # Payment Methods in Vietnam: MoMo, Cards & Bank Transfers (2026) By Nick Dunse, January 21, 2021 Discover Vietnam's top payment methods including MoMo wallet, bank transfers, credit cards, and cash on delivery as digital payments grow rapidly. Start collecting payments today Send payment links to your customers in Vietnam -- no card machine, no website, no fuss. With the surge in digital payments and the expanding e-commerce landscape, Vietnam presents numerous opportunities for fintech companies. Key areas for potential innovation in the fintech sector include mobile payments, where newcomers can introduce inventive solutions alongside established players like MoMo and ZaloPay. Digital wallets are gaining traction, offering users a convenient means of managing their finances, and fintech firms can enhance these solutions with features like loyalty programs or integration with other financial services. Online lending platforms could address the persistent challenge of limited access to credit for individuals and small businesses. In the remittance sector, Vietnam's status as a major recipient offers room for fintech companies to develop faster, more cost-effective, and secure transfer solutions. The rapidly growing insurance market in Vietnam calls for technology-driven solutions to make insurance products more accessible and affordable. Despite increased banking penetration, segments of the population remain underserved, presenting an opportunity for fintech firms to create tailored solutions such as microfinance or savings platforms. Collaboration between fintech companies and traditional financial institutions, seen in partnerships between banks and fintech firms to enhance digital banking services, is also on the rise. Overall, Vietnam's fintech sector is poised for growth, driven by digital adoption, government support, and the flourishing e-commerce market, offering success potential for firms delivering innovative solutions tailored to the local market's unique needs. ## Popular offline payment methods in Vietnam ### Cash ### Bank Transfers ### Cheques ### Mobile Payments ### Debit Cards ### Cash on Delivery (COD) ## List of payment methods in Vietnam MoMo is a highly popular mobile wallet and payment platform in Vietnam, allowing users to conduct various financial transactions through their smartphones. Users download the MoMo app, link it to their bank accounts or credit cards, and load money into their MoMo wallet for payments and transfers. The platform is versatile, enabling users to pay for groceries, bills, transportation, and online shopping. Its key advantage lies in the convenience it offers, allowing users to make transactions anytime, anywhere without the need for physical cash or cards. The app includes features like bill splitting, QR code scanning, and loyalty rewards. Beyond payments, MoMo provides additional financial services such as savings accounts, loans, and insurance products. Users can also withdraw cash from their MoMo wallets at partner banks or ATMs. ### Visa Visa is a widely accepted payment method, recognized for various transactions such as shopping, dining, and hotel bookings, particularly in major cities and tourist areas. To use Visa, one can simply present the card to the cashier or insert it into a chip-enabled card reader, with some establishments requiring a PIN for added security. However, it's important to note that smaller businesses or local vendors may only accept cash, so carrying Vietnamese Dong is advisable. Travelers are also encouraged to inform their bank or credit card provider about their Vietnam travel plans to prevent potential issues with card usage or security concerns abroad. Overall, Visa provides a convenient and broadly accepted means for travelers to conduct transactions in Vietnam. ### Mastercard Mastercard is extensively acknowledged as a preferred payment method in Vietnam, with acceptance at major retailers, hotels, restaurants, and online merchants, as well as availability at ATMs for cash withdrawals in Vietnamese dong. The process of using Mastercard involves presenting the card to the merchant or using a card reader, possibly requiring a PIN for security. Online transactions necessitate entering card details, including the card number, expiration date, and CVV code. Despite widespread acceptance, some smaller establishments in Vietnam may only accept cash, underscoring the importance of carrying local currency. Travelers are advised to inform their bank or credit card issuer about their Vietnam travel plans to avoid potential card issues due to security concerns. Overall, Mastercard is a convenient and popular choice for payments in Vietnam, offering a seamless experience for travelers in the country. ## Accepting International Card Payments in Vietnam Whether you sell to customers in Vietnam from abroad -- or run a business there selling to international clients -- accepting the right payment methods is critical for conversion. MoMo, ZaloPay, and VNPay dominate consumer payments in Vietnam alongside bank transfers -- cards alone aren't enough. A hosted payment link gives you a branded checkout page that supports cards, Apple Pay, Google Pay, and local methods so customers anywhere can pay. Shuttle Links & Checkout connects you to a payment provider that supports the right mix of methods for Vietnam, gives you a branded payment page, and lets you share the link by email, WhatsApp, or SMS. Talk to us about coverage in your region. ## Accepting Payments in Vietnam as a Platform For software platforms serving merchants in Vietnam, supporting local payment methods like MoMo, ZaloPay, and local bank transfers is essential for conversion. A PSP-neutral payment layer lets platforms connect to local acquirers alongside international processors like Adyen -- without building each integration individually. Shuttle connects platforms to 40+ payment providers across multiple countries. See how it works for platforms or book a discovery call. Need to collect payments in Vietnam? Send payment links via email, SMS, or chat -- no card machine or website needed. Get paid faster with Shuttle. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [See Links Checkout →](/merchants/links-checkout/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [Talk to us about coverage in your region](/contact/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Adyen](/payment-providers/adyen/) - [See how it works for platforms](/platforms/) - [book a discovery call](/discovery/) - [Explore Payment Services →](/merchants/payment-services/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [See Links Checkout](/merchants/links-checkout/) --- URL: https://www.shuttleglobal.com/blog/the-power-of-payment-links-enhancing-financial-management-in-practice-management-software/ --- # The Power of Payment Links: Enhancing Financial Management in Practice Management Software | Shuttle > Practice management software with payment links improves cash flow, reduces admin, and gives clients a seamless way to pay invoices instantly. # The Power of Payment Links: Enhancing Financial Management in Practice Management Software By Nick Dunse, February 16, 2026 Practice management software with payment links improves cash flow, reduces admin, and gives clients a seamless way to pay invoices instantly. Talk to us Make enabling payments for your platform and merchant users easy. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. In today's fast-paced and digital world, the use of practice management software has become increasingly popular among businesses of all sizes. These software solutions are designed to streamline various aspects of business operations, including scheduling, billing, and financial management. One of the key features that has revolutionized the way businesses handle their finances is the integration of payment links within practice management software. Payment links offer a convenient and efficient way for businesses to collect payments from their clients. By incorporating payment links into their practice management software, businesses can streamline their payment processes and improve their cash flow. This not only enhances the overall efficiency of financial management but also provides a seamless experience for both the business and its clients. Key Takeaways - Payment links enhance financial management by streamlining payment processes and improving cash flow in practice management software. - Integrated payment links enhance efficiency and simplify financial management for businesses, maximizing revenue and client convenience. - Practice management software with payment links can help businesses leverage technology to improve their financial processes. - Integrated payment links can help businesses maximize revenue and improve cash flow by making it easier for clients to make payments. - Payment links in practice management software can help businesses streamline their financial management processes and improve efficiency. ## Streamlining Payment Processes The integration of payment links within practice management software streamlines the payment process for businesses. Instead of relying on traditional methods such as checks or manual credit card processing, businesses can now send payment links directly to their clients, allowing them to make payments with just a few clicks. This not only saves time and effort for both the business and its clients but also reduces the risk of errors and delays in the payment process. Furthermore, payment links can be customized to include specific details such as invoice numbers, due dates, and payment amounts, making it easier for clients to understand and process their payments. This level of customization not only enhances the professionalism of the business but also provides a more transparent and convenient payment experience for clients. As a result, businesses can improve their cash flow by receiving payments in a timely manner, ultimately contributing to their financial stability and growth. ## Improving Cash Flow with Payment Links The use of payment links within practice management software can significantly improve a business's cash flow. By providing clients with a quick and easy way to make payments, businesses can reduce the time it takes to receive funds, ultimately accelerating their cash flow. This is particularly beneficial for businesses that rely on regular payments from clients to cover their operational expenses and invest in growth opportunities. Moreover, the integration of payment links can help businesses minimize the risk of late or missed payments. With the ability to send automated reminders and notifications to clients, businesses can ensure that payments are made on time, thus avoiding any disruptions to their cash flow. This level of control and visibility over the payment process allows businesses to better manage their finances and make informed decisions about their future investments and expenditures. ## Enhancing Efficiency in Practice Management Software Metrics | Results Increased Revenue | 20% increase in revenue after implementing payment links Improved Cash Flow | Reduced average payment collection time by 30% Enhanced Patient Satisfaction | 90% of patients reported satisfaction with the convenience of payment links Streamlined Financial Management | 50% reduction in time spent on manual payment processing The integration of payment links within practice management software enhances the overall efficiency of financial management for businesses. By consolidating payment processing within the software, businesses can eliminate the need for manual data entry and reconciliation, saving time and reducing the risk of errors. This allows businesses to focus on more strategic tasks and decision-making, ultimately improving their operational efficiency. Furthermore, the seamless integration of payment links with other features of practice management software, such as invoicing and reporting, provides businesses with a comprehensive view of their financial performance. This level of integration not only simplifies the overall financial management process but also enables businesses to make data-driven decisions that can drive their growth and success. As a result, businesses can optimize their resources and maximize their profitability, ultimately enhancing their competitive edge in the market. ## The Benefits of Integrated Payment Links The integration of payment links within practice management software offers a wide range of benefits for businesses. One of the key benefits is the ability to provide clients with a convenient and secure way to make payments. With the increasing preference for digital transactions, businesses that offer payment links can cater to the evolving needs and expectations of their clients, ultimately enhancing their customer satisfaction and loyalty. Additionally, integrated payment links can help businesses reduce their administrative burden by automating various aspects of the payment process. From generating invoices to reconciling payments, businesses can save time and resources by leveraging the capabilities of practice management software. This not only improves the overall efficiency of financial management but also allows businesses to focus on delivering value to their clients and growing their business. ## Simplifying Financial Management for Businesses The integration of payment links within practice management software simplifies financial management for businesses. By centralizing payment processing within the software, businesses can streamline their financial operations and gain better control over their cash flow. This level of simplification not only reduces the complexity of managing payments but also provides businesses with greater visibility and transparency into their financial performance. Moreover, integrated payment links enable businesses to track and reconcile payments more effectively, ultimately reducing the risk of errors and discrepancies in their financial records. This level of accuracy not only enhances the reliability of financial reporting but also ensures compliance with regulatory requirements. As a result, businesses can mitigate potential risks and liabilities associated with financial mismanagement, ultimately safeguarding their reputation and credibility in the market. ## Leveraging Payment Links for Client Convenience The integration of payment links within practice management software allows businesses to leverage this feature as a competitive advantage. By offering clients a convenient and secure way to make payments, businesses can differentiate themselves from their competitors and attract new clients. This level of client convenience not only enhances the overall customer experience but also strengthens the business's reputation as a modern and forward-thinking organization. Furthermore, integrated payment links can help businesses build stronger relationships with their clients by providing them with a seamless and hassle-free payment experience. This level of convenience not only fosters trust and loyalty but also encourages repeat business and referrals. As a result, businesses can expand their client base and increase their revenue potential, ultimately driving their long-term success and sustainability. ## Maximizing Revenue with Payment Links in Practice Management Software The integration of payment links within practice management software can help businesses maximize their revenue potential. By providing clients with an easy and convenient way to make payments, businesses can reduce barriers to payment and increase the likelihood of receiving funds in a timely manner. This not only accelerates cash flow but also ensures that businesses can capitalize on every revenue opportunity. Moreover, integrated payment links enable businesses to offer flexible payment options to their clients, such as credit card or ACH payments. This level of flexibility not only accommodates the diverse needs and preferences of clients but also expands the business's revenue streams. By providing clients with multiple payment options, businesses can capture a larger share of the market and increase their overall revenue potential, ultimately driving their financial growth and success. In conclusion, the integration of payment links within practice management software offers numerous benefits for businesses looking to enhance their financial management processes. From streamlining payment processes to improving cash flow and maximizing revenue potential, integrated payment links provide businesses with a powerful tool to drive their growth and success. By leveraging this feature effectively, businesses can simplify financial management, enhance client convenience, and optimize their operational efficiency, ultimately positioning themselves as leaders in their respective industries. As technology continues to evolve, it is essential for businesses to embrace innovative solutions such as integrated payment links to stay ahead of the competition and thrive in today's digital economy. ## Get Payment Links today ## Related Reading Explore More ### Payment Links for Property Management & Lettings Agencies ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-state-of-open-banking-payments-in-may-2023/ --- # The state of Open Banking Payments in May 2023 | Shuttle > The state of Open Banking payments -- adoption rates, merchant benefits, challenges, and what account-to-account payments mean for UK businesses. # The state of Open Banking Payments in May 2023 By Nick Dunse, May 24, 2023 The state of Open Banking payments -- adoption rates, merchant benefits, challenges, and what account-to-account payments mean for UK businesses. I know a bit about Open Banking and after I attended a panel session yesterday it became clearer to me the true state of things in the UK/EU. There's a lot of hype around Open Banking payments, some would tout that it will bring the end of card based commerce, direct debits and other payment methods. Well, if this does happen (which I don't think it will), it won't be for a long time yet. Here's my summary of the issues that I can see: We're all waiting on the banks to add features and improve their own customer digital experiences. This is a massive bottleneck, but nobody else in the chain can implement recurring payments etc until they provide a consistent way to achieve it. Which brings me to probably the biggest underlying issue - nobody is mandating the payment method feature set or setting standards for things like customer experience. If we look at India and UPI, it's phenomenal what they've done in terms of traction and rollout, but it all comes down to the National Payments Corporation setting the agenda and the form. Open Banking payments in the UK and EU is a dribbling mess in comparison, so beyond the above the question is why?.. Well firstly, because there's no commercial incentivisation, there are a number of players in the chain and yet OB payments might be charged at 5p. And if they run over Faster Payment rails, this might cost 75p, but who's going to work to consolidate and accept these ? In reality we actually need something like the interchange ++ model that the card schemes use. Again, it's about standardisation. The go-to-market approach for OB payments is clearly going after B2C channels. I get the idea that if you get consumer adoption you get salience and businesses will follow. But is there any point trying to disrupt consumer card usage in markets like the UK? OB payments seems better suited to accelerating the B2B space. Improving digital transformation and cashflow for businesses. Not to mention that the B2B commerce opportunity is larger and can actually leap frog the consumer state. The major missing feature is VRP (Variable Recurring Payments) - the ability to save the payment method and charge it later. Natwest have a merchant live with VRP, but they're the only bank (apparently) that have the functionality and therefore how can an Open Banking Fintech roll this out? They can't. I did discover, however that you can schedule future payments on the initial authentication; this is helpful, but it requires the merchant to know the value of those future payments plus the schedule. Seems like a good fit for B2B SaaS - no?! In truth, VRP is two years away, or until the banks sort themselves out. Wallet adoption doesn't exist yet (which is how I pay for everything now), UPI has been so successful IMO because of the adoption by Google Pay. I spoke to some Indian guys I met at Web Summit, they told me that they pay for EVERYTHING via their Google Wallet. It's all recorded in one central ledger, it was amazing. Their utility bills, their shopping, all consolidated within the wallet and with payment method choice. It's difficult to imagine Open Banking in the UK/EU hitting this state any time soon. Open Banking payments aren't running on some new super highway, they're running over existing networks, hence there's technical and commercial complexity when dealing with different networks, something already solved by card schemes... You can't pass enough data points via Open Banking. For example, you can't pass basket items like you can with cards over the network... Again, why are you going after B2C retail when you fall short of the requirements?! Security, hyped as a major benefit to Open Banking, but already fraudsters are getting around the SCA mandate in the EU with AI. Not to mention accounts need to be KYC'd in the first place. This problem has birthed some new security players, but of course, this comes at a cost... 'Oh but OB is so cheap!' Well, it won't be for long. I hope you found this helpful and demystifying, there's a lot of fog out there. Open Banking - great idea, left to a load of bankers to lead with no commercial incentive results in a waining rollout and lack of customer centricity. But yeh, 7m people in the UK have used it, not sure if 7m people love it. Let me know if you think the state of Open Banking payments right now is any different. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-top-5-reasons-why-your-business-needs-to-accept-card-payments/ --- # Accept Card Payments: A Complete Guide for Businesses | Shuttle > Learn how to accept card payments in-person, online, and over the phone. Compare fees, providers, and security requirements for your business. # Accept Card Payments: A Complete Guide for Businesses By Nick Dunse, February 23, 2023 Learn how to accept card payments in-person, online, and over the phone. Compare fees, providers, and security requirements for your business. Talk to us Make enabling payments for your platform and merchant users easy. Card payments now account for over 80% of retail transactions in the UK. If your business doesn't accept card payments, you're turning away the vast majority of your potential customers. Whether you sell in-store, online, or take orders over the phone, accepting cards is no longer optional -- it's the baseline expectation. This guide covers everything you need to know about accepting card payments: why it matters, how to get set up, what it costs, and how to choose the right provider for your business. ## Why Your Business Needs to Accept Card Payments The shift from cash to cards has been accelerating for years, and the trend isn't slowing down. Here are the core reasons every business should accept card payments. ### Customer Expectations Have Changed Consumers expect to pay by card everywhere. Contactless payments, Apple Pay, and Google Pay have made tapping a card or phone the default. If a customer reaches the till and sees a "cash only" sign, many will simply leave. The same applies online -- shoppers abandon carts when their preferred payment method isn't available. ### Increased Sales and Higher Transaction Values Research consistently shows that customers spend more when paying by card. Without the physical constraint of cash in their wallet, average transaction values increase by 20-30%. Accepting cards also means you never lose a sale because a customer doesn't have enough cash on them. ### Faster Payments and Better Cash Flow Card payments settle directly into your bank account, typically within 1-3 business days. There's no counting cash, no bank runs, and no risk of theft or loss. For businesses that invoice clients, offering card payment means you can get paid immediately rather than waiting 30-60 days. ### Reduced Cash Handling Costs Cash isn't free. There are costs associated with counting, storing, transporting, and depositing cash -- plus the risk of human error and theft. Card payments eliminate these overheads and give you a clear, automatic record of every transaction for accounting and reconciliation. ## How to Accept Card Payments There are three main ways businesses accept card payments, depending on whether the customer is physically present or not. ### In-Person Card Payments For face-to-face transactions, you need a card machine (also called a card terminal or PDQ machine). Modern terminals support chip and PIN, contactless, and mobile wallets. Options range from standalone countertop terminals to mobile card readers that connect to your smartphone via Bluetooth. Popular providers include Square, SumUp, and Zettle, all offering pay-as-you-go pricing with no monthly fees -- making them ideal for small businesses and sole traders. ### Online Card Payments To accept card payments on your website, you need a payment gateway. This is the software that securely captures card details, encrypts them, and routes the transaction to the card networks for authorisation. Most e-commerce platforms like Shopify, WooCommerce, and Wix have built-in payment gateway integrations. For businesses that don't have a website, payment links offer a simpler alternative. You generate a link and send it to your customer via email, SMS, or messaging app. They click the link, enter their card details on a hosted checkout page, and the payment is processed -- no website required. ### Card Payments Over the Phone Phone payments (also called MOTO -- mail order / telephone order) are common for service businesses, call centres, and any business that takes orders by phone. Traditionally, an agent keys the card number into a virtual terminal. However, this creates PCI compliance challenges because the agent hears and handles the card data. A more modern approach is to send the caller a payment link via SMS during the call. The customer completes payment on their own device, keeping card data out of your phone system entirely and significantly reducing your PCI scope. ## Card Payment Processing Fees Explained Every card payment involves several parties -- the card networks (Visa, Mastercard), the issuing bank (the customer's bank), and the acquiring bank (your bank). Each takes a small cut, which is why card processing fees exist. The main components of card processing fees are: - Interchange fee: Paid to the customer's bank. Typically 0.2% for debit cards and 0.3% for credit cards in the UK (capped by regulation). - Scheme fee: Paid to Visa or Mastercard for using their network. Usually a few pence per transaction. - Acquirer/processor markup: The margin charged by your payment provider on top of interchange and scheme fees. In practice, most small businesses pay a blended rate of 1.4-2.5% per transaction, depending on their provider and whether the transaction is in-person (lower risk, lower fee) or online (higher risk, higher fee). Some providers charge a flat rate -- for example, Stripe charges 1.5% + 20p for UK cards online. Others use interchange-plus pricing, which passes through the actual interchange cost plus a fixed markup. Watch out for additional fees like monthly minimums, PCI non-compliance fees, chargeback fees, and early termination penalties. Always read the full fee schedule before signing a contract. ## Card Machines vs Payment Links The traditional way to accept card payments in person is with a card machine. But payment links are increasingly being used as a flexible alternative -- or complement -- to physical terminals. - Card machines are best for high-volume retail environments where speed matters. Contactless tap-and-go takes seconds. However, terminals involve upfront hardware costs (£19-£300+), may require a contract, and need maintenance. - Payment links are best for service businesses, remote payments, phone orders, and situations where you don't have (or don't want) a terminal. There's no hardware cost, and the customer completes payment on their own device. They're also ideal for taking payments in-store without a card machine -- for example, using QR codes at the point of sale. Many businesses use both: card machines for walk-in customers and payment links for phone orders, deposits, and remote payments. ## How to Choose a Card Payment Provider Choosing the right provider depends on your business model, transaction volume, and how you sell. Here's what to evaluate: - Pricing model: Flat-rate pricing (e.g. 1.75% per transaction) is simple and predictable. Interchange-plus is usually cheaper at higher volumes but more complex to understand. - Contract terms: Some providers lock you into 12-36 month contracts with early termination fees. Others are rolling monthly or pay-as-you-go. - Settlement speed: How quickly do funds reach your bank account? Next-day settlement is now common, but some providers still take 3-5 days. - Payment channels: Does the provider support all the ways you take payments -- in-person, online, over the phone, and via payment links? - Integration: If you run a platform or software product, look for providers with strong APIs that let you embed payments directly into your product. - Support: When payments stop working, you need someone to pick up the phone. Check whether support is UK-based, what hours they operate, and what channels are available. You can compare popular payment providers on our directory to see how they stack up across features, pricing, and supported payment methods. ## Security and PCI Compliance Any business that accepts card payments must comply with the Payment Card Industry Data Security Standard (PCI DSS). This is a set of security requirements designed to protect cardholder data. The good news is that for most small businesses, PCI compliance is straightforward if you use a reputable payment provider. Here's why: - Hosted checkout pages and payment links mean card data never touches your servers. The provider handles capture, encryption, and storage. - Card machines are PCI-certified hardware. As long as you use them as intended and don't store card data separately, compliance is handled. - Phone payments are the exception. If agents read card numbers aloud and key them into a system, your call recordings may contain card data -- putting you in scope for more stringent PCI requirements. Using payment links sent via SMS during the call avoids this entirely. Most providers will charge a PCI non-compliance fee (typically £5-30/month) if you don't complete their annual PCI self-assessment questionnaire. Make sure you complete it -- it's usually a simple online form. ## Accepting Card Payments on a Platform or Marketplace If you operate a platform, marketplace, or SaaS product where your users need to accept card payments, the challenge is different. You're not just processing your own transactions -- you need to enable embedded payments for potentially thousands of merchants. This means handling merchant onboarding, KYC (know your customer), split payments, settlement to multiple bank accounts, and compliance -- all within your product experience. Solutions like Stripe Connect, Adyen for Platforms, and Shuttle's payment infrastructure are designed for this use case. The key considerations for platforms include: - White-label vs redirect: Can your merchants accept payments under your brand, or are customers redirected to a third-party checkout? - Payment method coverage: Beyond card payments, do your merchants need direct debit, bank transfers, or local payment methods? - Revenue share: Can you earn a margin on payment processing, turning payments into a revenue stream for your platform? ## Frequently Asked Questions ### How much does it cost to accept card payments? For most small businesses, card processing fees range from 1.4% to 2.5% per transaction. The exact rate depends on your provider, the type of card (debit vs credit, UK vs international), and whether the payment is in-person or online. Some providers also charge monthly fees or require a minimum monthly spend. Pay-as-you-go providers like Square and SumUp charge a flat percentage with no monthly commitment. ### Can I accept card payments without a card machine? Yes. Payment links let you accept card payments without any hardware. You generate a link through your payment provider and send it to the customer via email, SMS, WhatsApp, or any other channel. They tap the link, enter their card details on a secure hosted page, and the payment is processed. This works for remote payments, phone orders, invoices, and even in-person transactions using QR codes. ### How long does it take to set up card payments? With modern providers, you can start accepting card payments within minutes. Services like Square and Stripe offer instant onboarding -- you create an account, verify your identity, and you're ready to take payments. Traditional merchant accounts from banks can take 1-2 weeks to set up due to underwriting and compliance checks. ### Do I need PCI compliance to accept card payments? Yes, all businesses that accept card payments must be PCI compliant. However, if you use a hosted checkout, payment links, or a card machine from a PCI-certified provider, the heavy lifting is done for you. You'll typically need to complete an annual self-assessment questionnaire (SAQ) to confirm you're following basic security practices. Read our guide to PCI compliance for a full breakdown of what's required. ## Getting Started Accepting card payments is essential for any modern business. The barriers to entry are lower than ever -- you can be up and running in minutes with no upfront costs and no long-term contract. For individual businesses, the choice comes down to how you sell and what you're willing to pay in fees. For platforms and software companies looking to enable card payments for their users, the decision is more nuanced -- you need infrastructure that handles onboarding, compliance, and settlement at scale. Start by comparing payment providers to find the right fit, or explore embedded payment solutions if you're building payments into a platform. ## Related Reading Explore More ### How to Get Payments Off Your Product Roadmap ### HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment gateway](/blog/what-is-a-payment-gateway/) - [payment link](/blog/the-future-of-in-store-payments-why-payment-links-are-here-to-stay/) - [Stripe](/payment-providers/stripe/) - [taking payments in-store without a card machine](/blog/the-future-of-in-store-payments-why-payment-links-are-here-to-stay/) - [embed payments directly into your product](/platforms/) - [compare popular payment providers](/discovery/) - [PCI DSS](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [embedded payments](/platforms/) - [guide to PCI compliance](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [comparing payment providers](/discovery/) - [explore embedded payment solutions](/platforms/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideHubSpot International Payments: Accepting Cards Outside the Big 5 Currencies→](/guides/hubspot-international-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideHow to Accept ACH Payments in QuickBooks (Without Intuit's Processor)→](/guides/quickbooks-ach-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-truth-about-payments-orchestration/ --- # The truth about payments orchestration | Shuttle > Payments orchestration promises to simplify multi-gateway management. This article breaks down what it really means and whether it is right for your... # The truth about payments orchestration By Nick Dunse, February 16, 2026 Payments orchestration promises to simplify multi-gateway management. This article breaks down what it really means and whether it is right for your... Talk to us Make enabling payments for your platform and merchant users easy. The question is - if you're a merchant or a software platform do you really need payments orchestration? - Does working with the "right payments provider" and platforms negate the need? - Is payments orchestration even possible under new legislation? - What is really meant by payments orchestration? There's a new term in the payments space that's defining an entire category of business, that term is payments orchestration. The idea is that you can dictate how payments are collected through to where they settle, and most specifically who processes those payments. In the next five minutes, I'll break down payments orchestration and give you an idea of its viability and whether its right for you. ## What is payments orchestration? Payments orchestration is performed by a new breed of middleware payment technology companies who connect to multiple payment service providers (PSPs), fraud technology, acquirers and banks. These technology solutions are likely to be focussed on the specific product/angle that they sell; this might be a universal optimized checkout, fraud software, smart payment routing, cross border payments or all four. Payments orchestration is about deciding how best to route a payment from checkout through to bank settlement, increasing the payment conversion and therefore making more money for merchants. For example, if you get a cheaper deal with Payment Provider X you want to route those qualifying transactions via them, or if Payment Provider X declines a card then you want to automatically try and provider and capture the payment/ ## Stage 1 - Checkout Does my checkout present the payment options that the end customer wants? Can I increase my chance of that customer actually paying? Software vendors creating this universal checkout are making it possible to offer the payment methods that the end customer (regardless of location) want to use. Increasing conversions by giving the customer the choices they need to convert. Credit options from the likes of Klarna are rapidly appearing in checkout. A checkout might include card, wallet, bank to bank, crypto or financing options; I'm yet to see a bartering option appear though (watch this space - lol). Intelligent presentation of payment options is based on a rule that is set by the merchant. For example, all larger transactions need to go via cheaper payment processing options and therefore saving the merchant money on fees. Orchestration at this level requires the merchant to have a payment service provider who offers multiple payment methods or multiple providers; plus third party fraud services and a checkout provider that can integrate them. ## Stage 2 - Routing Once the payment option has been chosen it's then up to the software behind the checkout to decide how this payment will be routed and if there are any pre-processing requirements like fraud checks to go through. Most payment orchestration platforms are also offering the ability to save a card in third party vault (more on that later). After fraud services and vaulting has happened the payment needs to be processed; using the data presented by the end customer, fraud checks and the preferences that were set by the merchant the payment will be sent to a payment gateway or acquirer. If this payment fails there might be a retry policy or a policy to try this payment via another payment gateway. There are either hard or soft rules implemented by the merchant and the routing engine; it might be that a merchant with multiple entities and provider relationships decides to route certain currencies through a particular provider. Or in time the orchestration platform learns the highest converting routes for certain types of payments and their respective merchants and increases future conversion rates. Orchestrating at the routing level requires the merchant to have multiple payment providers and even merchant account relationships that can work independently without financial penalty. Routing is where most payment orchestration vendors sit. ## Stage 3 - Settlement Eventually, money has to end up in a bank account and merchants want the least amount skimmed off whilst maximising the greatest number of sales and reducing chargebacks. This is where the choice of merchant account and the adoption of multi-currency accounts come in. It's going to be cheaper to transfer money across a number of currencies if you can pay it out in the local currency and not have to pay for the currency conversion (FOREX). Then you can move the money back to your base currency when you want to at a rate that you're happy with. Orchestration at this level is about ensuring you can control how the money gets from the payment processor to your bank account in the right currencies at the right rates. ## Saving payment preferences and vaulting cards We all want to make it simpler for the customer to checkout in future and even charge the customer automatically when we can. But saving payment preferences and vaulting cards goes one step further when a vendor is trying to route a payment via the optimized payment channel. For example, a customer pays, a card gets vaulted (saved) that card gets processed and fails via one gateway and therefore another gateway is used to process the card successfully. Or perhaps the rates with a cross border payment provider has been reduced to zero this week and so we want to prioritize this routing over another provider. This requires the end customers' payment method to be securely saved and if it is to be used with multiple processors then either it needs to be saved with each processor or it has to be saved in a third party vault so that it can be re-used. What you should be aware of about card vaulting solutions is that very few, if any are insured against cyber attacks and breaches of personal information. They may be PCI DSS Level 1 compliant but this is just a card industry standard for dealing with card information. Any serious merchant is putting themselves in danger if you don't do you due diligence with a vaulting service. ## When Payments Orchestration fails There are some clear and an increasing number of scenarios where payments orchestration falls down. - If you can't get multiple providers to work with you, you can't manage multiple providers or you can't build a checkout with multiple providers. - When you can't save/tokenise/vault a payment method from a customer. Therefore you can only run a payment attempt once through one routing. - Where security measures prevent the payment from being processed. The EU is implementing PSD2 and SCA (strong customer authentication) which requires payments to meet certain criteria and present a challenge to the end customer. How can you convert a payment orchestration if a customer is required to authenticate the payment at every attempt?! This has to be one of the most commonly overlooked realities. There are only a few scenarios where SCA is not presented: the customer is either present, has whitelisted the merchant to perform the same regular payment or the value of the payment is low. See our blog on SCA for more info. Software platforms are able to use third party 3DS service providers but the payment gateway may not accept or want to work with them. - When you can't choose or alternate the account that your money settles into. If can't add multiple bank accounts to your PSP then you can't decide where money gets paid out to. - When the end customer wants to pay via a particular payment method that has limited routing options. - If the merchant needs to use a software platform that doesn't support payments orchestration. Increasingly merchants sell on SaaS platforms, I can't see that Shopify (or any others for that matter) support payments orchestration beyond a multi-gateway solution. - Network tokenisation is being introduced by VISA, Mastercard and AMEX, this allows the card to be tokenised at the root level instead of in a third party vault. This erodes some of the need for orchestration where failover happens or card vaulting is required since it's the card schemes controlling the latest card. ## Is Payments Orchestration for me? If you're a larger merchant, operating across borders with a lot of transactions happening outside of the EU then payments orchestration is likely to add a lot of value to your business. Even if you just optimized your checkout and chose a multi-currency account provider you would increase conversions and reduce fees. If you're currently a US-based merchant with customers based in the US you will be able to take advantage of sending transactions to the PSP you configured. If you're a platform then enabling payments orchestration is going to be complicated and difficult, you'll need to employ one of the vendors to enable this within your software and decide what your merchants can and can't do. Ideally, as minimum presenting multiple choices at checkout is the minimum. If you're a wanting to route EU transactions through different PSPs then you're going to struggle to achieve your goals with a routing strategy but can certainly take advantage of optimizing your checkout and reducing foreign exchange fees. If you're a merchant selling on a platform like Shopify with in-flexible control over how your payments come in and go out then you're not going to be able to take advantage. It's up to the platform to make this work for you. Payments orchestration works for now and is undoubetly part of the consolidation of the fragmented payments industry. It's likely to come under pressure in its present form and will have to take a more holistic approach than is currently enabled by the vendors that say they are payments orchestrators. Regulation, the platforms and the payments giants are likely to have the final word unless the consumer market can force a wider change and unification of systems, which is happening with certain tokenisation services, to a degree. PSD2 creates the top-down opportunity but it only polices adherence to policy. The question that any merchant should ask themselves is - is payments orchestration between PSPs really necessary if I have selected the optimal processors in the first place and maximise the opportunity at checkout? Software vendors need to make sure they have enabled merchants to build and convert at checkout, they are the ones with the optimisation knowledge. If you like to find out about any of the things mentioned in this article just drop us an email at support@shuttleglobal.com, we can connect you with PSPs, cross border specialists and great solutions to maximise your payments acceptance. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Links - [Book a Call →](/discovery/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/the-ultimate-guide-to-integrating-a-payment-gateway-into-your-app/ --- # Payment Gateway Integration: How to Add Payments to Your App or Platform | Shuttle > How to integrate a payment gateway into your app or platform. Covers API integration, hosted checkout, PCI compliance, testing, and go-live -- with... # Payment Gateway Integration: How to Add Payments to Your App or Platform By Nick Dunse, December 4, 2020 How to integrate a payment gateway into your app or platform. Covers API integration, hosted checkout, PCI compliance, testing, and go-live -- with... Talk to us Make enabling payments for your platform and merchant users easy. Payment gateway integration connects your application to a payment service provider so you can accept, authorize, and settle card payments. The decisions you make during integration shape your PCI scope, your ability to switch providers, and how much engineering time you'll spend on payments for years to come. This guide covers the full integration process -- from choosing an integration method through to testing and go-live. It's written for developers and technical product managers building payments into apps, SaaS platforms, and marketplaces. ## What Is Payment Gateway Integration? A payment gateway is the service that sits between your application and the acquiring bank. It encrypts card data, routes authorization requests to the card networks (Visa, Mastercard, etc.), and returns an approval or decline response -- typically in under two seconds. Integration means connecting your checkout flow, backend, or payment surface to that gateway's API. The result: your users can pay with cards, digital wallets, and local payment methods without leaving your product experience. The scope of a gateway integration typically includes: - Client-side -- collecting card details securely (via iframes, hosted fields, or redirect) - Server-side -- creating payment intents, processing charges, handling 3D Secure callbacks - Webhooks -- receiving asynchronous notifications for settlement, disputes, refunds - Reconciliation -- matching gateway transactions to your internal records For platforms that need to support multiple merchants or payment providers, the integration also includes merchant onboarding, payout splitting, and multi-PSP routing -- which is where it gets complex fast. ## Payment Gateway Integration Methods There are three primary integration patterns. Each makes a different trade-off between control, PCI scope, and development effort. ### API / Direct Integration You call the gateway's REST API directly from your backend. Card data is collected via tokenized client-side fields (Stripe Elements, Adyen Web Components) so raw card numbers never touch your server. A typical server-side charge request looks like this: POST /v1/payments Headers: Authorization: Bearer sk_live_xxx, Content-Type: application/json, Idempotency-Key: order_12345_attempt_1 Body: "amount": 4999, "currency": "GBP", "payment_method": "tok_abc123", "capture": true, "metadata": "order_id": "12345" Best for: teams that need full control over the checkout UX and have the engineering capacity to manage PCI SAQ A-EP compliance. PCI scope: SAQ A-EP (if using client-side tokenization) or SAQ D (if raw card data hits your server -- avoid this). ### Hosted Checkout / Redirect The gateway hosts the entire payment page. You redirect the user to the gateway's URL, they enter card details there, and the gateway redirects them back with a transaction result. The flow is: your app creates a checkout session via API → receives a redirect URL → sends the customer to that URL → gateway processes the payment → customer returns to your success/failure URL → you verify the result via webhook or API callback. Best for: teams that want the simplest possible integration with limited PCI scope. Trade-off: you lose control of the payment page design. PCI scope: SAQ A -- the lowest level. Card data never touches your infrastructure. ### Embedded / Drop-in Components This is the middle ground. The gateway provides pre-built UI components (iframes or web components) that you embed in your checkout page. The components handle card input, validation, and tokenization -- your page never sees raw card data. Examples include Stripe Elements, Adyen Drop-in, and Braintree Hosted Fields. You style them with CSS to match your brand, but the actual input fields are rendered inside the gateway's iframe. Best for: most applications. You get a branded checkout experience with SAQ A PCI scope. This is the default recommendation for teams that don't have a specific reason to go fully direct. PCI scope: SAQ A. ## Requirements for Payment Gateway Integration Before you write any integration code, you need four things in place. 1. PCI DSS compliance path Any entity that stores, processes, or transmits cardholder data must comply with PCI DSS. Your integration method determines your SAQ level: hosted checkout or drop-in components typically qualify for SAQ A, the short questionnaire. If card data touches your servers, you're looking at SAQ D, the full one (questions) or a QSA audit. 2. TLS/SSL certificate All payment pages must be served over HTTPS. Gateways reject API calls from non-TLS origins, and browsers flag insecure checkouts. Use TLS 1.2 or higher. 3. Merchant account or PSP agreement You need a merchant account with an acquiring bank or a direct agreement with a PSP like Stripe or Adyen. For platforms with sub-merchants, you'll need either a PayFac license, a PayFac-as-a-service arrangement, or a payment layer that handles merchant onboarding for you. 4. Sandbox / test environment Every major gateway provides a sandbox with test API keys and simulated card numbers. Set this up before touching production -- you should be able to run your full checkout flow, including 3DS challenges and webhook delivery, in test mode. ## Step-by-Step Payment Gateway Integration Process Here's the integration process broken down into concrete engineering steps. Timelines assume a team of 1-2 developers working with a modern gateway API. Step 1: Create your gateway account and get API keys (Day 1) Sign up with your chosen PSP. You'll receive a publishable key (safe for client-side code) and a secret key (server-side only, never exposed to the browser). Store your secret key in environment variables or a secrets manager -- never commit it to source control. Step 2: Install the SDK or configure HTTP client (Day 1) Most gateways offer server-side SDKs (Node.js, Python, Ruby, PHP, Go, Java) that wrap the REST API with authentication, retries, and serialization. If you prefer raw HTTP, use a client with retry logic and exponential backoff. Step 3: Build the client-side payment form (Days 2-3) Mount the gateway's drop-in component or hosted fields in your checkout page. The component collects card details and returns a token (a one-time-use reference to the card). Send this token to your backend -- never the card number. Key implementation details: - Load the gateway's JavaScript library from their CDN -- never self-host it, or you'll break PCI scope - Initialize the component with your publishable key - Handle validation errors (expired card, invalid CVV) in the UI before submitting - Disable the submit button after the first click to prevent duplicate charges Step 4: Create the server-side payment endpoint (Days 3-4) Your backend receives the token and calls the gateway's charge or payment-intent API. Set the amount, currency, and metadata here. Critical patterns to implement: - Idempotency keys. Every payment request should include an idempotency key (typically your order ID + attempt number). If a network timeout causes a retry, the gateway will return the original response instead of creating a duplicate charge. Example header: Idempotency-Key: order_12345_attempt_1 - Amount validation. Never trust client-side amounts. Re-calculate the total from your server-side cart/order state before sending to the gateway. - Error handling. Distinguish between card-declined errors (show to user), validation errors (fix and retry), and gateway errors (retry with backoff or fail gracefully). - Authorize vs. capture. For orders that ship later, authorize the card at checkout and capture when you fulfil. Authorizations expire (typically 7 days), so capture promptly. Step 5: Handle 3D Secure authentication (Days 4-5) 3D Secure (3DS) adds cardholder authentication -- typically a bank-issued challenge. In the EU, SCA regulations make 3DS mandatory for most transactions. The pattern: attempt payment → gateway returns "requires_action" with a redirect URL → redirect the customer or open an iframe → customer authenticates → gateway redirects back → confirm via API. Step 6: Set up webhooks (Days 5-6) Webhooks notify you about asynchronous events -- settlements, failed captures, chargebacks, refunds. Register an HTTPS endpoint with the gateway, and it POSTs event payloads to that URL. Webhook implementation rules: - Verify signatures. Every webhook payload should include an HMAC signature. Verify it using your webhook secret before processing. This prevents replay attacks and forged events. - Respond with 200 fast. Acknowledge the webhook immediately and process asynchronously. If your endpoint takes too long, the gateway will retry -- potentially causing duplicate processing. - Make handlers idempotent. Gateways retry failed deliveries. Your handler should check whether you've already processed a given event ID before taking action. - Handle key events. At minimum, subscribe to: payment.succeeded, payment.failed, refund.created, dispute.created, and payout.paid. Step 7: Build refund and dispute handling (Days 6-7) Integrate the refund API for full and partial refunds. For disputes, set up webhook handlers to flag affected orders and collect evidence for representment automatically. Step 8: Go live (Day 8-10) Swap test keys for production keys. Run a real transaction with a small amount, verify it in the dashboard, then refund it. Monitor your first 100 transactions for elevated decline rates, webhook failures, and 3DS drop-offs. ## PCI Compliance and Security PCI DSS compliance is not optional -- it's a contractual requirement from the card networks. The good news: modern integration methods dramatically reduce your scope. Here's how your integration method maps to PCI scope: - SAQ A (hosted checkout, drop-in components): 22 questions. Card data stays entirely with the gateway. This is where you want to be. - SAQ A-EP (API integration with client-side tokenization): ~140 questions. Your website controls the payment page, but card data is tokenized before reaching your server. - SAQ D (direct server-side card handling): 300+ questions plus quarterly ASV scans. Avoid this unless you have a dedicated security team and a reason to handle raw card data. Beyond PCI, implement these security fundamentals: - Use tokenization for stored payment methods -- never store raw card numbers in your database - Enforce TLS 1.2+ on all payment endpoints - Log payment events without logging card data (mask PAN to last 4 digits) - Set Content-Security-Policy headers to restrict which domains can embed scripts on your payment pages - Rotate API keys regularly and use separate keys per environment (test, staging, production) ## Testing Your Payment Gateway Integration Payment testing should cover more than the happy path. Here's a testing checklist organized by category. Authorization testing - Successful charge with test card (Visa: 4242 4242 4242 4242) - Declined card (use gateway-specific decline test numbers) - Insufficient funds decline - Expired card - Invalid CVV - 3D Secure challenge flow (successful and failed authentication) Post-payment testing - Full refund - Partial refund - Void (cancel an authorized but uncaptured payment) - Chargeback/dispute simulation Edge case testing - Network timeout during payment (verify idempotency key prevents double charge) - Webhook delivery failure and retry - Currency mismatch between frontend and backend - Zero-amount or negative-amount edge cases - Concurrent payments from the same user - Browser back button during 3DS flow Use the gateway's webhook testing tools (e.g. Stripe CLI's "stripe trigger") to simulate events locally during development. ## Common Integration Challenges (and How to Solve Them) Multi-currency support. Handle presentment currency (what the customer sees) vs. settlement currency (what you receive), and minor-unit formatting (GBP uses pence, JPY has no minor unit). Pass the correct ISO 4217 currency code and amount format for each gateway. Webhook reliability. Webhooks can arrive out of order, be delayed, or be duplicated. Make webhook processing idempotent and always verify payment status via a synchronous API call as a fallback -- never rely solely on webhooks for critical state transitions. Gateway-specific error codes. Every gateway returns errors differently (Stripe: "card_declined"; Adyen: refusal reason codes). Build an abstraction layer that maps gateway-specific errors to your internal error taxonomy for consistent UI messages. Mobile app integration. Native mobile apps need Apple Pay and Google Pay SDKs alongside card payments. These use device-level tokenization with their own certification requirements. Plan for this early -- retrofitting mobile wallets later is expensive. Subscription and recurring billing. Store tokenized payment methods and implement dunning logic (retry schedules for failed recurring charges). Notify customers before cards expire to reduce involuntary churn. Migrating between gateways. Switching gateways means migrating stored tokens (via network tokenization), updating webhook endpoints, and running both gateways in parallel during transition. This is the most underestimated cost of direct integration -- and a strong argument for using a payment abstraction layer from the start. ## When to Use a Payment Layer Instead of Direct Integration For a single-product app with one PSP, direct gateway integration is fine. But the calculus changes when you're building a platform. Consider a payment layer if: - You need to support multiple PSPs -- enterprise customers often mandate specific gateways. Maintaining 3-5 separate codepaths for payments, webhooks, and reconciliation is expensive. - You need payments across multiple channels -- voice, chat, email, and messaging alongside web checkout need a unified payment API, not separate integrations per channel. - You don't want to become a PayFac -- direct integration with sub-merchants means becoming a PayFac (6-12 months, heavy compliance) or using PayFac-as-a-service. A payment layer handles merchant onboarding for you. - Payments aren't your core product -- every week your team spends maintaining payment infrastructure is a week not spent on your actual product. Embedded payment infrastructure lets you ship payment features without the ongoing maintenance burden. Shuttle Global provides exactly this -- a single integration point to accept payments across 40+ PSPs and multiple channels, with PCI Level 1 compliance and merchant onboarding included. If payments are a required step in your platform but not your core IP, explore this before committing to multi-gateway direct integration. Learn how Shuttle works for platforms or book a technical walkthrough. ## FAQ ### How long does payment gateway integration take? A basic single-gateway integration using drop-in components typically takes 1-2 weeks for an experienced developer. That covers client-side form, server-side API, webhooks, and testing. Multi-PSP or marketplace integrations can take 4-8 weeks. If you need SAQ D or a QSA audit, add 2-6 months for the compliance process. ### Do I need PCI certification to integrate a gateway? Yes, but the level varies. If you use hosted checkout or drop-in components (SAQ A), you complete a short self-assessment questionnaire -- no external audit required. If raw card data touches your servers, you need SAQ D or a QSA audit, which is significantly more involved. Most applications should use tokenized client-side collection to stay at SAQ A. ### Can I integrate multiple gateways? Yes, but each gateway has its own API schema, error codes, webhook format, and reconciliation flow. You'll need an abstraction layer to normalize these differences. For platforms needing multi-PSP support, a payment layer provides this abstraction out of the box -- giving you one API and one webhook format regardless of the underlying PSP. Payment gateway integration starts simple and accumulates complexity. Get the fundamentals right -- tokenization, idempotency, webhook verification, proper PCI scoping -- and you'll avoid significant rework later. If you're building payments into a platform and want to skip the multi-gateway integration work, talk to Shuttle. We handle the gateway integrations, PCI compliance, and merchant onboarding so your team can focus on the product. ## Related Reading Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment gateway](/glossary/payment-gateway/) - [tokenization](/glossary/tokenization/) - [PCI DSS](/glossary/pci-dss-level-1/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [payment layer that handles merchant onboarding](/guides/what-is-embedded-payments/) - [Embedded payment infrastructure](/guides/what-is-embedded-payments/) - [accept payments](/guides/take-payments-online/) - [Learn how Shuttle works for platforms](/platforms/) - [book a technical walkthrough](/discovery/) - [payment layer](/guides/what-is-embedded-payments/) - [talk to Shuttle](/discovery/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/transforming-business-with-payments/ --- # Transforming business with payments | Shuttle > How modern payment infrastructure transforms business operations. Covers embedded payments, payment orchestration, and why the right payment stack drives... # Transforming business with payments By Nick Dunse, November 28, 2020 How modern payment infrastructure transforms business operations. Covers embedded payments, payment orchestration, and why the right payment stack drives... Talk to us Make enabling payments for your platform and merchant users easy. Nick: Mike Mann, Finance Director over at Williams Trade Supplies Limited, the leading plumbing merchants. Mike, welcome. I would love you to tell us what on earth is a man of your great experience doing at a plumbing merchant. Mike: Hi Nick. It's to be honest, Williams is one of those weird companies that are just, that just attracts, I think, slightly left field people. It's as close as you can get to be family owned without actually being family owned. It's a 50 year old business. The original founder, Mick Williams is still a non exec director on our board. And it's a business of individuals, if I'm honest with you, it's not a kind of grey, there's no one size fits all at Williams, so I think I kind of fit in, fit in quite well in terms of payment experience, I had Almost no payment experience before I joined Williams other than, the standard thing you'd find in any finance environment. Most of my previous companies have been strict B2B. So there wasn't very much much to go after there in that kind of market. But moving to Williams where, though we are technically B2C, we are we are dealing with, 10, 000 trade customers. But these are trades people who act like a hybrid between a business and a consumer. So there's a lot more interest in terms of both user journey payment behavior, payment cost as well, obviously. Yeah, so payments become much more interesting in a business like Williams. Nick: Yeah, and we'll get into some of those things as we have our conversation. Today I obviously met you through the context of payments, and that was via LinkedIn, you talking and commenting on payment operations and what you guys are doing over there at Williams to improve your receivables and operational processes. Tell us a little bit more about how you've accelerated your own knowledge in the payment space and that journey that you've been on since starting at this position at Mike: Williams. Both the big kind of step changes for us in payments and for me in my in knowledge came out of absolute necessity or bafflement, perhaps is a better word. We used to take an awful lot of card not present payments from our customers for things like credit control and also for remote deliveries for, from branches. And that was obviously, as everybody knows, but I didn't know at the time, is a very risky approach to to taking. Card payments of people and we were suffering six figure losses each year in card fraud and chargebacks. So that was a, it originally started as a fraud question. How can we stop this? And that led us to, okay, maybe we need to stop taking payments over the phone. I'd spoken to a couple of security people at our card PSP who basically said, If you're prepared, if a customer of yours is prepared to do that, they should be prepared to. Shout their card details across a busy pub and that kind of resonated. So we moved to, we investigated and then moved to a pay by link service. It managed to be actually called pay by link to Dutch company. And as I say, that was simply originally to avoid or to reduce those fraud costs, which we did. Not overnight. There was initial resistance, as you can imagine, from customers who'd spent years and years paying over the phone. But we were, that was 2019. We were enormously helped by COVID in that, just the fact that everybody started, compromising on, what was seen as compromising on, on, or changing accepted procedures for things. And we'd never look back tonight, back and I don't think we have a single issue now with any customer saying I'm not prepared to. To pay you your links. And then, yeah, so that was the first step, but it was, as I say, more borne out of how do we stop this one thing from happening than any kind of great strategy and payments. Nick: You recognize that you had a big problem. And I think going back to that kind of comment about bafflement, you and I have talked before about the bafflement with kind of the lack of adoption for online payments or digitization of processes in the industry. And I suppose plumbing and trade merchants is on the less innovative end of the spectrum. But you as a finance director recognized you had a problem and you went after a solution . For those who might be listening, who don't even know that they might have a fraud problem, dive into what was your problem? What kind of fraud, what was going on with taking payments over the phone and why was it a problem? Mike: So we, we would, our typical or our average transaction value is about 500 quid. But obviously that, that can be, that ranges from anything from a couple of bits of copper fittings, which might only be a few pounds, to thousands of pounds for multiple boiler order or a big system or something like that. And our branches, not unreasonably, were always taught to mistrust people wanting, or not mistrust, but be wary of people wanting things on credit. And that, there were always processes involved in protecting the business from that kind of fraud. But typically, whenever somebody phoned up with a card number, I think there was a degree of trust placed there to go they're paying us by card, it must be. a genuine transaction. And of course, sadly, there wasn't in many cases. First we would know about we'd take a card payment for let's say a thousand pounds. The first we would know about it was four weeks later, we'd get the statement through from our card PSP, which would have a huge charge back on it. Obviously we would question that. Dig into it a bit and find out this was never a customer. This was just somebody who realized we didn't have a good process for preventing that fraud. And of course, the moment that happens, it happens again and again in very quick succession. So we had to put Nick: in place. Okay. So this is genuine fraud. Mike: This was genuine fraud. Yes, this was undeniably genuine fraud. These were. Customers that simply were not customers. Unfortunately, they were boilers that were boilers and they left us and went to them. Nick: He went out the store. Yeah. Mike: Anytime this occurred, if we knew it we got our branches to the point that our branch staff to the point where they were very alert to this, any attempt to do that from a customer they didn't recognize or something that's, we, usual phrasing, if it looks like a fish and smells like a fish, there's a good chance it's a fish. They would get, they would alert all the other branches in their area instantly. And we would see repeated attempts at the same thing. Because at the end of the day, if you're a business with a weak control, people will push that button every opportunity they get. Nick: And you don't necessarily think that this stuff happens in semi slow moving, boring B2B worlds, right? You think, oh, this is happening on fast moving consumer goods. This is where people, try cards, try and get their products delivered. But this is happening to you guys, shipping out. Mike: Yeah, boilers is possibly a bad example. It does happen with boilers. You might be surprised or even horrified at the number of boilers that probably chained hands in the local pub or on the local motorway services. But things like copper, for example, if we're selling copper tube, that is an immensely saleable commodity. So yeah, it does happen. I believe it happens in every business. It was certainly happening in ours. Nick: It's become apparent to me that even in any kind of sector, even if you're sending out invoices or you've got credit accounts with your customers, there is the opportunity for fraud that you don't even know that's happening to you. And if you're not on top of it, it's going to cause you problems. It's going to, you're going to, you're going to be. losing stock out the door and paying the cost of it. And you're also potentially paying for the chargebacks Mike: as well. This is it. Yes. So it's a, and it's an area that people have historically considered reasonably safe. It's not selling on credit, so it must be okay, but it wasn't. So thankfully I'm pleased to say in the last year we have done somewhere in the region of 220, 000 card. Transactions and we have had one charge back. And that was an error. This is part of my bafflement. Any company doing this will be suffering from that because fraudsters will know the moment you, they call you and you say, give us your card details. They absolutely know that you would be liable for this if it was a fraud, so they will try it. So The bafflement comes from, are people not doing their research about this and finding out how they, maybe it's just the fact, being cynical about it, that card card PSP statements are so completely opaque in what they actually show the average finance person, that you just pay the bill and move on. Nick: I've seen enough of those statements to be continually baffled myself. Never mind the hidden fees. There's all of those chargebacks that are happening. So you've got your, you had your problem with fraud. Was there any other kind of business challenges that you had that You've been able to resolve with working on the payment operation within Mike: the business. Yes, I think things like, , obviously a lot of very large proportion of our customers have credit accounts with us. Credit controls a big part of that and chasing debtors is is always great fun in a business like ours. One of the solutions to that was a semi automation of the process. We don't want to take the humans out of that. They're a very necessary part of that credit control process for us. It's part of customer service, albeit on the slightly less less than the front end of customer service. But the idea that, again, being able to do things like upload. 3, 000 payment reminder requests and not just send those out. We could previously we were emailing or contacting people even by post for to chase them. But being able to put in a payment link to that gives an immediacy to the response mechanism as well. It feels absolutely old fashioned now to me to send out a reminder that someone needs to pay us without giving them a method of paying us. But we were doing that up until four years ago. And the improvement in response to, to speed of response of people, most of our customers are not, do not deliberately set out to pay us late. That's not part of their way of working, they're not big organized business that might deliberately spread payments over as long as they could possibly get away with. But most of our customers are also not natural business people. So they'll forget or they will, they will let stuff slip or whatever it is. And, but the reverse is also true. If we. For example, using pay by link, we now send out on day minus three, so three days before the month end, we'll send out remind, a gentle reminder to all our credit customers who owe us anything at that point to say, just so you, just in case you've forgotten, this much is going to be due on Friday. If you want to pay it now, that's absolutely great. Here's a link. You can use the link anytime between now and Friday. And the number of customers who are clearly grateful for that clearly also respond to it and pay us. early is staggering because this isn't about, as I say, a relationship where you spin things out to the, as far as you can take them. This is about just, in my way of thinking, us helping them run their businesses better. It's and that that's also enabled us to Spread the timing of things like those chases and so on. So it's a much more cohesive approach to Collecting amounts due to us. Nick: No one wants to be desperately chasing debt and people who have the debt don't want to be desperately chased either So I think it makes a lot of sense in your world And we'll look at a broader kind of idea in a second, but your world you've got Plumbers, coming in and ordering parts and walking out with parts and goods. And then they're off to their job, right? And they're very, they're keen to get on to doing the actual job. So they're busy people. They probably parked outside on a single yellow or something, and, they want to take that product on on credit usually. And they just don't have time to actually go and make that payment right there and Mike: then. No, and also, they're because most of our customers are independents, they are fighting the very big guys who are all offering credit who make it much easier for the householder to buy from them. So they, they can't necessarily be in a position to say, I need a hundred percent of that upfront or even I need 50 percent of that upfront because people will just. not use them. So they're in a credit trap themselves because their customers want to pay at the end of the job and not before. So yes, it's a credit is a very important part of our relationship with them. Nick: Tell us a little bit more about the kind of specifics that you've got going on. You've mentioned some of them already where you've Got a link that you can send out and someone can pay that link, really quickly instead of waiting 72 days, because they forgot about the invoice or however it worked. Tell us like what you've implemented in terms of the process and how that's improved things. And then tell us about some of the other payment methods as well as card that you've got going on. Cause I know you've been innovating around open banking, for example. Mike: Yeah, I think the first thing we were very concerned to do with sending links to people was to make them as credible as they have to be in an environment where people are now being quite rightly taught to be suspicious of requests for money over, over any electronic means. Doing things like using our own. Email using our own domain name clearly personalizing things to the customer. One of the things we love about the pay by link product is that it is hugely customizable. To the extent that we we issued completely different messaging to those customers, whether by SMS or by email, depending on what the event is. So it might be, as I said before, a gentle reminder is very different from a third reminder that you are late. We've customized, or we have something like 25 different messages that we've set up. Even the landing pages that people arrive at when they've been, when they've clicked on the link that they get by text, we've customized those to the extent that we can pre select a payment method for people so that it reduces their clicks by one. And also hopefully nudges them towards the payment method they'd like to use, which we'll come on to. But there's a whole lot, there's a whole lot we, You have to be careful with something like this. You can overdo it. We I did a pre Christmas reminder, change, change the normal wording of the pre Christmas reminder. And I thought it might be fun to, to say to, people don't get on Santa's naughty list. Make sure you pay us on time. We had seven complaints. I think we touched a nerve somewhere, but the fact is, if you can't mess about with Father Christmas, Mike, no, exactly, it's all, it's that credibility and also it is part of our. It's a marketing term, but it's part of the Williams voice. If you are communicating with your customers the way you normally communicate, possibly not the way we communicate in a rough and tough builder's merchant branch, but certainly the way you communicate with them online, it certainly adds a lot of trust to that relationship. We could, we then took that, a stage further by saying okay, we can, if we can customise the messaging, we can also. Customize the other content of that to the customer. Things like Amex, for example, we do accept Amex very reluctantly. But, and we have a process whereby customers can. Basically say, I'd like to use Amex, there's a little form to fill in, don't tell Amex for goodness sake, but but we'll get that form, we'll go, okay, you are now you now have Amex added to your account, so when you get a link, it will include Amex, whereas nobody else's will partly because I'm fearful of a mass migration from, already expensive cards to an even more expensive card. But as I say, that kind of thing, allowing people different payment methods is an absolute advantage of having an integration piece in the middle of that kind of relationship. So the fact we've got pay by link sat there means we can add things, if we chose to take, I don't know, love to shop vouchers or something like that at a future date, we could probably integrate that. Nick: You've got your payment service. This is connected to your pay by link service, which you're sending links out via SMS, WhatsApp, email Mike: channels, email. Yeah, at the moment. We're not using WhatsApp at the moment, yeah, so then we then Having got that integrator in place the we almost to be honest We almost stumbled across open banking as a or open banking payments It was a again. There was a There's a blindingly obvious problem, which was that, as I look down, I'm a finance director, as I look down my very neat P& L statement, I like to have all the big numbers at the top, sales, gross profit, staff costs, rent, that kind of stuff, and I like it to gradually taper in a very neat way to, down to the little things, and down at the bottom little things should be things like bank charges. But the problem with our P& L was it did conform to that, and there was suddenly this enormous number sat near the bottom of the P& L, which was card processing costs. And obviously the vast majority of that was interchange. And it wasn't so much that it was just big. It was the fact that it was growing out of seemingly out of all control. Because unlike retailers, we, the vast majority of our customers use corporate debit or credit cards. They don't use personal ones. So they're in a space that wasn't regulated. back in 2016. Clearly Visa and MasterCard saw fit at the time not to scare the horses and not really do anything with those particular card types. But since then we've seen increase upon increase. We've seen caps removed to the point where a transaction, a thousand pound transaction in 2018 that would have cost us 1. 50 in Cat fees is now costing us 15 and the cost of that boiler that represents that 1, 000 payment has not increased in that time on average. And for that massive increase, which is beyond all level of possible comprehensible inflation, we haven't seen a single improvement in service or there is no service to improve. It's just a tax. So again we're victims of our vertical. If you like, if we were in retail, I would have. a fifth of the problem that I have, but we're not and neither is any other trade merchant Nick: So you found open banking and open banking payments made possible by the kind of improved networks and connectivity of banks and parties and service providers in the industry. What is open banking? For anyone who doesn't know in terms of open banking payments and talk a little bit about how you've begun to implement that. Mike: Okay. Without going into the long and. to me somewhat tedious history of how open banking came to be. It's essentially a, an account to account payment system that uses faster payments to get. Our customers money to us or my money to you using a bank to bank method rather than via the card system. So by avoiding the card system, you avoid the interchange fee. That is our big issue here. And the major nine, but the nine major banks in the UK were forced into this by a competition of markets authority review. Following some EU legislation back in, I think, 2016. They did this with, I think, a degree of reluctance, because the people who benefit most from this interchange charge are the banks. And They were basically being asked to eat their own lunch by the CMA. But as far as we were concerned, this was a customers, especially if a customer is paying us on a corporate debit card, the money's leaving their account today anyway. So it's no different from a cashflow perspective from their point of view. My cashflow improves because I receive that cash instantly or close to instantly, rather than having for it to wait, having to wait for it to go through the card rails. And also from a customer point of view, it's far more secure than using your card in almost any environment because you're authorizing a payment using a banking app. And if you believe that your banking app is secure, that is a secure payment. And I think most people would probably. Trust their banking app more than they would trust their credit card, you know banking app is I wouldn't say impossible But it's nigh on impossible to clone or to spoof the card is very easy So I think from the customer point of view you improved security from a merchant point of view far lower cost faster, generally faster settlement. And there's, there are also some other side fringe benefits as well. Things like referencing and stuff. So we can, because if somebody is paying on a card on a normal card terminal, there's very little idea actually who the payment came from or, there's a very limited amount of information you get. If we're instigating the payment request, we can put in a reference that sits with that payment all the way along. So we can easily reconcile it. When it comes in, so it's a fringe benefit, but it's a nice one. Nick: You've got your open banking payment method or your payment service. You've got your pay by link. Your customer gets a link. They open it up. They are forced to or they can choose pay by bank or account to account option. It opens up their banking app, confirm the amount paid and they're done. You get the money, they get their receipt all automatically. And they have that high level of trust. And then as you mentioned, what's quite interesting is and this is something that I talk about. By having an e commerce flow as opposed to an in person flow, you're able to capture some more information about that customer and then do things with that, like automatic receipting straight to their email address, for example, but also you can do some digital customer management and satisfaction through that process. Is that something you guys do and are keen for? Mike: It is. So we were very conscious of the fact that an open banking payment is not as slick as a face to face or chip and pin card payment. It's certainly not as slick as contactless, but most of our customers aren't in that kind of contactless. bracket, their spend is higher than that. It's still not as good as waving your card or waving your phone over a card terminal. So as well as there being the resistance to any kind of change in our kind of market, there was also the real fact that we were asking people to spend a little more time doing something than they would otherwise have. have done, make it, making the payment. So we decided we had to incentivize them. And again, this was part of actually the pay by link process of generating these open banking payments as links means that we could then tack on. Effectively a gamification piece at the end of it to I'd say, you might be winning, you might win a voucher at the end of this or, and we've got a huge degree of control over that. So we've, in, in one space, we've got the payment method itself, plus the incentive mechanism to, to help people. Move people over to that payment method Initially when we started this we weren't quite so sophisticated We had a prize draw for every customer who used open banking payments during the month and you could win a very sexy Gas powered barbecue at the end of the month, but which was great. It was a nice visible prize It was gas powered. So all the heating engineers loved it and so on But it wasn't immediate, it wasn't instant gratification, and you could only give away so many of them before you weren't saving any money at all. So moving to vouchers was actually, to be honest, just inspired by what people like Cafe Nero do for their retail customers. You go in there at Easter time and you get to tap a little Easter egg and see what comes out. And I wanted something that was that kind of, It's not a real game or anything, but that, it's a game of chance that the something that would engage our customers as well in the process of paying. Because the one thing we, I think, have all probably agreed on, and I think every PSP and all the open banking providers have, I think, finally now realized is customers don't care about payments. It is not a thing that features in their mind at all. Necessary evil. Yeah. It's a non, it's a non thing. It's, Nick, we, we've spent, or I've spent time with you and I've spent time around the, in the open banking ecosystem for a couple of years. Everybody is absolutely fascinated by payments because it's their job. But nobody else is, and to try and get a customer to move their payment behavior is really boring to them, but we had to make it, we had to make it interesting. So as I say, directly incentivizing them, giving them a, giving them vouchers or whatever it is, we've now got a mechanism whereby we can do that Nick: It is really boring. And as you say, unless it's deeply painful, a lot of friction for the end customer, they don't care how it happens. They just care that they can get on with their lives. And you care that you can collect the money. What I like about what you've just is quite often with the digital payment experience we've taken some of that human touch out of it. And in fact, it's become even more transactional than it ever was, because you're not handing physical cash over to someone and looking them in the eye and walking out with some goods. But you're by adding almost a game in there your. You're creating some element of delight into this purchase. It's quite, I like it. It's very good. And as you say, you've incentivized open banking Mike: with it. Yeah, and through messaging and so on when we send out a payment request to people when they receive a text in one of our branches, you've got that, it's not just the reward at the end of it, we can also give them, we can give the messaging up front, we've even put messaging on emails explaining why we're doing this, because It is costing us a fortune if we don't and actually, a lot of our customers, when we've talked to them face to face, have said fine, if it saves you money, I'll do it. They didn't even really need incentivising, necessarily. Some of them would, obviously, but I think anybody, any of our trade customers who themselves takes card payments knows what this means. The numbers might be different, but it's still painful. Nick: Absolutely. You mentioned some customers will come in and historically pay in store with a terminal. Are you sending any of those customers an SMS with a payment link who are in person there as well? And how has that kind of gone? Because you'd think that might add some friction into the process. Mike: Yes, 80 percent of our business is transacted in branch face to face. Like you say, it's a human thing. Our customers like being in our branches. That's they like bricks and mortar service. We offer very high standard of service and that's why they use us. So whatever we did had to work in branch. Otherwise we were only ever going to hit a percentage of 20 percent of our customers. About available market. We knew that was going to be the hardest one to crack. But equally, we knew we had 300 and something people in our branches who were our ambassadors for this potentially who could present it to customers in a way we can't do online. The time we, the only thing that was available to us was SMS or or email. So we opted for the SMS route. So now in our branches that the one of our guys who goes behind the till can simply tap in a customer account number, put in the amount they're due to pay the system knows what kind of customer this is. Are they a call only customer? Are they a returning open banking? Customer. If they're returning open banking customer, they get the text as a preference. This is still done by defaults and nudges, but we can get, we can encourage people quite strongly in branches to, to do that. Because there is still a human element in it. In terms of our teams initiating that, they could just hand them the card terminal and just keep quiet about open banking because there is that human element. And because our branches are run semi autonomously. There's a lot of different ways of running a plumbers merchant branch. We do get success rates. very variable success rate. So we have some branches where they're achieving more than 50 percent of all their payments are being done on pay it, which is the open banking product we use from now west. And, but we have other branches where it's less than 5%. The customers are largely the same. So this is a, there's a big team education and team. Buying peace in this, which I've come to understand over the last couple of years is actually every bit as big as the customer buying. We have a kind of trust relationship with our customers. Anyway, they're not walk ins off the street. We are trade only. They're in our branches every day or every week. You've built a big, good relationship with them, they trust you to advise them on, the correct flu to go on this boiler. So if we advise them on a payment method, they're also, to some extent, trusting, and that really helps. It's still not as slick as the card process, 50 years to, to develop. Nick: I think consumers are very Used to that car process as well. What is. Interesting for me is what open banking is doing to challenge the manual bank transfer methods in the B2B world. So Williams could send an invoice or a statement out and just stick some bank details on the bottom of that invoice, right? For their UK based customers and hope that someone's going to go and pay that. You've been talking about transforming this both with the kind of link service and now using an account to account method that they used to, but actually it's digital it's on their phones and it's secure. It seems to me, I don't know whether you can talk about this, but there's this huge opportunity. Where in the UK, something like the average invoice is paid after 72 days. We can get those invoices paid a lot sooner and faster with some more transparency about what's going on. Mike: Yeah, I think that's absolutely true. And I think the. One of the problems with manual transfers it's a worse situation than with card payments, is there's so little connectivity between that transfer being done and you requesting the payment and you reconciling the payment. It's a, it's, for us, it's our highest burden. method of somebody paying, not financial burden, but in terms of admin. Our customer makes a manual transfer from their bank account to us, they make up the reference, we ask them to put the right reference on, they never do. We've got, we've written our own script, which is hundreds and hundreds of references that customers have used in the past. It's a very early form of machine learning that we wrote. Three or four years ago that says, Oh if I put that reference in, there's a very strong probability that this is that customer. And if that customer happens to owe that amount, then you've probably got, you've probably got the right one. But that's it's not a very it's not a very robust method of determining who's paid what. It works, but it's very time consuming, especially time consuming when it goes wrong. Whereas with open banking, as I said before, the reference flies through with the payment. It's, we can leave the customer number on there with a customer account number on there, which is absolutely perfect. So it does streamline that Nick: process. That sounds like chat GBT version zero. Yes, absolutely. Yes, Mike: yes, before that was even a thing, to be honest. But they and it's, from our point of view, I would rather, like you said, I would absolutely rather somebody responded to a request for them to pay us. In a method that with the health that helps us, that doesn't hurt them, importantly. I think one of the limitations is that Open Banking is very mobile friendly and not particularly PC friendly. So if you are a larger. Some of our larger customers, they will actually have a proper person doing payments. It's not the norm for us. Average, I think the average number of employees of our customers is probably about two and a half. But so true B2B, I think there is a more of a hill to climb there because you'll have a, you're not using a banking app to pay at all normally. That's not to say it can't be done. You will be using your online banking. But it's a different, it's a different environment. And as I say, for us, that's those customers tend to be on the fringes of where we deal. And if I'm honest from a pure cost point of view, if they're already paying us by a low cost method, I'm okay with that. Our larger customers who insist on paying us by Amex, I would far rather move to open banking. That's a separate story. Nick: Two gas barbecues you can have. Yes. I like that. Get the caravan as well. And you've got this template now for how you've done it at Williams. And it sounds to me like this is, if you look at this in a very generic way. It feels like you could apply this to other businesses. They don't have to be, trades merchants. What, where do you see the other opportunities or businesses that you can almost cookie cut this with a bit of, bespoking? Mike: I think the opportunity, the opportunities are absolutely enormous. I think the it's almost better to look at it the other way around and say, where would it not work? Because it will work everywhere else. So where it wouldn't work, I think at the moment in its current form and not talking about future developments, but its current form, anything that requires a very high speed checkout process is this is going to feel like a lot of friction now in our environment. We love customers to dwell in our. In our branches, because we've got beautiful displays of lovely, sexy power tools and work wear and things that they may or may not need, but the longer they spend in branch, the more opportunity there is to serve them that we are renowned in our vertical for having the best coffee of any builders merchant in the country. And that is a huge cost to us every year. It's a proper, bean to cup system and stuff in every branch. But that is so that customers will stay there and because we want to say thank you for, spending money with us. We've moved a long way from the kind of ghost ghastly little brown clicks cups and the equally ghastly brown liquid that used to go into them. So for us dwell time not actually a problem in an environment. In a much more, in a much faster moving environment, it would be a problem. There are other ways to solve it, but at the moment, single immediate payments is a slow process. But and obviously where transaction values are lower, because the card fees will, so the interchange is based on a percentage of the value, as that drops the card fee itself drops away as well, in equal proportion. Whereas, depending on what, The commercials are for your particular open banking deal. They may not, it may be a fixed fee. There is a point at which open banking becomes more expensive than taking a card. But for us, it's a very low point indeed. It's well below our average. Certain types of retail, absolutely. Other types, would you expect to see this appearing at Tesco's at the checkout? I don't know. I think you might if you incentivize people, there are all sorts of experiments going on in, in that kind of market in supermarkets at the moment. I think there's a Dutch chain that has now introduced slow lanes for older, this is post COVID, older people who want to have a chat. I'm sorry, that's not meant to be older people. That's any people who want to have a chat. But people who don't want to feel pressured into completing their transcript in the most efficient way possible. No, I think the combination of any business. The combination of having a lower cost payment method, that is more secure for your customers. If you can then combine that with the link based approach or even a QR code based approach that allows you messaging to your customer. It takes the payment part of the journey from utterly dull or not even a thing to potentially a positive thing. I think that could be. If I go to the local, to my local garage, which is an Asda store, they've got a point of sale display facing me, tells me what my order is at the moment that they're keying in. But also, the moment I've done my payment asks me for a, gives me a satisfaction survey about the queue length and this kind of thing. There's no reason why you can't build that into a. That is viewed as a payment method, perhaps even on a payment device, and make it much more of a, to come back to your point, much more like handing cash over to the person. You can have a little con, almost a conversation with them. And I think that may be a trick that is being missed by the payment payments industry because everyone's so focused on the payment itself. You don't realize you are in a customer service environment. Whatever the business is, it doesn't matter if it's a builder's merchant or a plumber's merchant or a retail environment. I think that's, that ability to personalize that kind of thing, that's not a function of open banking, but it, but the fact that you are making people wait. necessarily could be turned to your advantage. Nick: I think there's a great opportunity to improve the buying experiences and actually innovate and look at. These older experiences and actually move them forward. We're trying to get this hybrid model of digital and physical, this digital model and work it to our advantages where we've got all the convenience and safety of digital transactions, but also the potential to have really good human interactions and improve our customer service and making it less transactional actually. So I, I really liked that. I was just going to summarize some of your key points there actually. So I, I like looking at the idea of where isn't open banking going to work. And we know that it, as you said, it's going to work in high ticket items where there's effectively a fairly slow kind of checkout process appreciated. And where it's B2B because you may be dealing with corporate cards, which are very expensive. Some of these opportunities that are out there are like corporate travel. The booking process is slow. Your corporate cards, there's this great opportunity for B2B travel merchants or in your case, trade merchants. Mike: We're talking about about an, also we're talking about the current version of what open banking looks like and that it, because it was in initially viewed as an e-commerce something that works in the e-commerce environment. The first conversation we ever had with the guys that pay it. Was about, was not about e commerce. It was about, as I say, the other 80 percent of our business. And I think everyone's very skeptical about whether this would ever work in that kind of environment. And my view was the integration costs, because we already have pay by link as an integrator, the integration costs were not high. So cost of failure, not really a, not really an issue. Potential upside, absolutely enormous. But this is mark one. This is a process we know to be in a journey. We know to be inferior to the very slick card journey, move it forward another couple of years and we should have, a much slicker, potentially a one click or even no click checkout process. But there's a lot of work to do for that, but I think the industry seems very focused on that goal. Whereas actually, I think there would be a, there's a huge advantage in focusing on what we currently have. And I sound like a really boring FD when I say that. But we've got this thing that can be made to work. Now it might not supplant cards, I don't think it will. They've got decades of experience and some very high powered brains making cards work better for people. But if it sits alongside cards as a viable but mainstream alternative, then you actually get the funding and you get the level of engagement and the level of recognition from the market to make that next step even easier. It's an absolute hobby horse of mine that open banking payments, don't have a brand and we use Pay It. Other people use True Layer or, you name it any of the very imaginatively named open banking providers. There are very many of them. And I don't think that inspires confidence in the end user. If I go into any old store and I put my card on the card terminal, I don't care or know if the card terminal comes from Ingenico or Dojo, if the acquiring is done by Fiserv or Lloyd's Cardnet, I don't care. I'm just paying by card. Pay by card. It's a phrase. So the industry and everybody has been very focused on the mechanics of it, on the technology. I absolutely get that. That's done. It's there. Works. Then really, to me, there just needs to be a brand for this. And I think again, people are, we're focusing on, Oh, we're now moving from open banking to open finance or open something else. And you go yeah, but from a customer point of view, open banking would, for example, enable you to see your Barclays account on your NatWest app. Fantastic. That's got nothing to do with payments as far as. The average consumer is concerned. It's a complete, they don't need to know. It comes from the same tech stack and the same piece of development. It's not, it's just that one's a payment method. One is accounting information. So don't try and create a brand for the entire thing. Cause you'll never do it. Cause if open banking is the brand in, in, in my recent. Survey of about a small number of customers, zero percent could explain what open banking was. And that's after, what, eight years in the development? So even my own customers, even our own customers at William, we don't talk about open banking. We never talk about the banking now, but if I change that to pay by bank tomorrow. I think our customers would be okay with it, especially if they saw that pay by bank brand appear on HMRC's website or the NS& I website or, another big merchant or something like that. It's that universality, contactless, direct debit. They're all really well, they're not understood that nobody understands the technology behind that except the payments geeks, but customers, but consumers think they understand what it means. And that's the important bit so the next step is not the technical one. To me, the next step is that is the universal recognition of what this is that will drive adoption. Nick: I can agree more. I think you've got two sides of that coin there. One is, as you say we need a brand for recognition. So everyone knows what it is that we're talking about, even if they don't know how it works, but also we need a brand for trust. Because if you've got all of these other wild brand names in the mix, you're like I don't know what these things are. And are they part of this open banking thing or not? But I just want to associate. This type of payment method which I find really convenient with a brand or a name that I trust on. And you're right. We are still very early on in that journey, and it's going to be a difficult one. But I'm very interested in And getting that sorted out, but also having businesses adopt it, because ultimately we're all consumers nowadays. And if you get, if you solve some of these B2B problems where it's really ripe for solving, and then you drive this brand awareness into that space. It will be much easier in my opinion to roll it out to consumers trying to get consumer adoption first at a very fast moving consumer goods level is very difficult. Mike: Yeah. And I think, we made the mistake, not the mistake, but we made exactly that comment originally, but the other way around to go it would be, wouldn't it be great if there was, I don't know, one of the big utility providers or, mobile phone company or something like that. would take this on. But I think you're right. I think that there is less of a, there's less of a, less of an urgency for them to do that. They're not being hit by the same level of card fees that, or the same percentage level of card fees that, that trade or business, the B2B businesses are. And the kind of B2B we're talking about is not. Huge corp paying huge corp, this is individual trades people or, nail people, nail bar people or whatever it is being paid by and paying other small businesses. And there are many more of those around and they come much closer to people's personal lives. I think that kind of, the one, one of the things that I'm very excited about was people being offered. or apps being offered to very small micro businesses like, nail salons and that kind of thing where it's, it might even be an individual so that they can accept open banking payments and free themselves from the card. from the cartel, if you like both, both my daughters run micro businesses. One is a Pilates instructor, the other one does wedding styling and they both benefit from the fact that I can get their customers to pay them using open banking. It's much better for them than And taking cards financially, and it's much slicker for them than for their customers. Doing manual, manual bank transfers. Nick: I think it'll probably be those cartels that end up owning all these open banking companies and the brand anyway, I wholeheartedly agree with everything that you've just said. Very interesting. Coming back around to your business and what you've done operationally and to transform your business. You've mentioned saving, saving six figure sums because you were getting all of these sort of chargebacks and fraud problems. And then operationally. Improvements there. What would you say to any business that has recognized that they've got an issue with payments? What would your advice be? Mike: I think actually my advice would be to the people who haven't recognised they've got an issue with payments. I think the I think if you have recognised it you're almost certainly doing something about it. And I think the idea, the thing I would say is there are enough companies out there, there are enough businesses out there, there are enough people out there who are experts in the field to get good advice on this. I think, but the problem is it's a move from a very traditional Kind of one to one relationship with your card, PSP or acquirer, where might even have been the people who provided you with the card terminals, who then said, Oh, we can also do the payments because it's just the same thing. It's moving away from that into an environment where you've got slightly, you've got more choice. You've got more You got more at your disposal. So the hence why people like, the guys at pay by link that we talked to or prompt or other people like that who are in the, in that middle space are, I think, critical to this because if everybody has to do an integration one to one with an open banking provider and that doesn't sit properly with their card. Provider and blah, blah, blah. It'll never happen. But generally, from our point of view, we had to do all this blind. We didn't really know what we were doing at all. Some would say we still don't, but we did it. And the ROI on this, coming back to me as an FD, is absolutely astronomical. It's not expensive to do. Yes, it took time. If we'd found the right people quickly, it would have taken less time and been less expensive. But it's perfectly doable. There are lots of businesses out there doing it now. And just do it. It's as I say, if you can't persuade large quantities of your customers to do this. You won't have spent a huge amount of getting there. But if you can, the difference to the bottom line is enormous. Nick: Awesome. Thank you, Mike, FD over at Williams. Innovator in payments and open banking transforming the business over there. It sounds huge, the difference that you've made. So I really appreciate you coming on, having a conversation with me. Lots we could talk about, but we'll save it for another section on open banking. Specifically, perhaps maybe we'll get a picket line at some of the open banking conferences. Really appreciate your time and your conversation with me today, Mike. Thank you so much. Mike: It's been an absolute pleasure, Nick. ## Related Reading Explore More ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent→](/guides/ach-payments-over-the-phone/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/ --- # Twilio chooses Shuttle to provide payment connectivity | Shuttle > Twilio partners with Shuttle to provide PCI-compliant payment connectivity over voice and messaging channels using programmable APIs. # Twilio chooses Shuttle to provide payment connectivity By Nick Dunse, February 17, 2026 Twilio partners with Shuttle to provide PCI-compliant payment connectivity over voice and messaging channels using programmable APIs. 1 June 2024 Twilio chooses Shuttle to provide connectivity to 30+ payment gateways via their Twilio Pay solution. Shuttle was chosen to provide a secure payment processing solution integrated into Twilio's pay verb, designed to enable businesses to accept payments via voice calls or other communication channels. It leverages Twilio's programmable voice and messaging APIs, allowing customers to securely input their payment information through their phone during a call or through other communications, such as SMS. Use Cases for Twilio Pay: - Call Center Payments: Customers can securely pay bills, purchase services, or make donations during a phone call. - Automated Billing: Businesses can set up automated voice systems for recurring payments. - Phone Orders: Retailers or service providers can take customer payments securely during a phone order. - The merchant can send SMS with a payment link to the customer to make a convenient payment. By combining Twilio's flexible communication platform with Shuttle's payment technology, Twilio Pay enables businesses to provide a streamlined, secure, and scalable payment experience over voice or messaging channels. > "We're already seeing large merchants, call centres and platforms wanting to use our turn-key solution. And who wouldn't want this, it's fast to deploy, allows the use of the preferred payment partner and allows the option of getting paid over the phone. We know that the phone can provide the best best customer experience and now that is coupled with secure, scalable payments acceptance" says Nick Dunse, CRO at Shuttle. The service is billed via Twilio for simplicity. Shuttle's connector allows for IVR, voice payments and also provides the ability to send a payment link if that is more convenient for the customer. Merchants and call centres can deploy this solution without any upfront fees in a matter of days. And technology solution providers can build on top of the connector to add call centre functionality or enable AI voice agents to utilise Twilio and Shuttle. A winning combination. ## Related Reading Explore More ### Twilio Pay Connectors: How to Connect Any Payment Provider to Twilio ### Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle ### Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) ### How to Connect LiqPay to Twilio for Voice & IVR Payments ### How to Connect USAePay to Twilio for Voice & IVR Payments ### How to Connect FreedomPay to Twilio for Voice & IVR Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideTwilio Pay Connectors: How to Connect Any Payment Provider to Twilio→](/guides/twilio-pay-connectors/) - [GuideBest Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle→](/guides/best-payment-link-providers/) - [GuideStripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)→](/guides/stripe-twilio-integration/) - [GuideHow to Connect LiqPay to Twilio for Voice & IVR Payments→](/guides/liqpay-twilio-integration/) - [GuideHow to Connect USAePay to Twilio for Voice & IVR Payments→](/guides/usaepay-twilio-integration/) - [GuideHow to Connect FreedomPay to Twilio for Voice & IVR Payments→](/guides/freedompay-twilio-integration/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/uncovering-the-limitations-of-spreedly-for-software-platforms-2/ --- # Uncovering the Limitations of Spreedly for Software Platforms | Shuttle > Spreedly has limitations for software platforms including restricted gateway support and pricing complexity. # Uncovering the Limitations of Spreedly for Software Platforms By Nick Dunse, February 17, 2026 Spreedly has limitations for software platforms including restricted gateway support and pricing complexity. Ditching Spreedly? Here Are 5 Better Alternatives for Your Business Spreedly is a popular payment gateway that allows businesses to securely store and process credit card information. It is known for its flexibility and ease of use, making it a popular choice for many businesses. However, Spreedly does have its limitations. One of the main drawbacks of Spreedly is its lack of support for certain payment methods, such as digital wallets and alternative payment options. This can be a major issue for businesses that want to offer their customers a wide range of payment options. Additionally, some users have reported issues with Spreedly's customer support, citing long wait times and unhelpful responses. These limitations have led many businesses to look for alternative payment gateway solutions that offer more features and better support. Key Takeaways - Spreedly has limitations such as lack of direct payment processing and limited payment gateway options - Factors to consider when looking for a Spreedly alternative include payment gateway options, flexibility, global expansion, and advanced features - Stripe is a robust payment gateway alternative with a wide range of features and global reach - Braintree offers a flexible payment processing solution with advanced features and support for various payment methods - Adyen is a global payment platform suitable for expanding businesses with its wide range of payment methods and global reach - Authorize.Net is a reliable payment gateway with advanced features such as fraud detection and recurring billing - When choosing the best Spreedly alternative, consider factors such as your business needs, global expansion plans, and desired payment features Factors to consider when looking for a Spreedly alternative When searching for a Spreedly alternative, there are several factors to consider. First and foremost, it's important to look for a payment gateway that supports a wide range of payment methods, including digital wallets, alternative payment options, and international currencies. This will ensure that your business can cater to a diverse customer base and provide a seamless payment experience. Additionally, it's important to consider the fees associated with each payment gateway, as well as any additional features or integrations that may be beneficial for your business. Finally, it's crucial to consider the level of customer support offered by each payment gateway, as responsive and helpful support can make a big difference in the event of any issues or technical difficulties. ## Shuttle: A payments platform built for software vendors Everything you need to deliver payment features to your merchants. Shuttle is working with leading SaaS vendors in invoicing, booking, shopping cart and telephony services. Shuttle is used by small booking platforms and large enterprises like Twilio to enable payment features for all types of merchants. Shuttle has many payment methods and components available to software vendors and their merchants. Shuttle partners with payment service providers so software vendors can offer them without building each integration. This is why Shuttle is the best option for software vendors compared to Spreedly or many of the other payment orchestration solutions. Stripe: A robust payment gateway alternative Stripe is a popular payment gateway that offers a wide range of features and integrations, making it a great alternative to Spreedly. One of the main advantages of Stripe is its support for a wide range of payment methods, including digital wallets like Apple Pay and Google Pay, as well as alternative payment options like ACH and SEPThis makes it an ideal choice for businesses looking to offer their customers a variety of payment options. Additionally, Stripe offers competitive pricing with transparent fees and no setup or monthly fees. It also provides advanced features such as subscription billing, invoicing, and customizable reporting, making it a comprehensive solution for businesses of all sizes. Furthermore, Stripe is known for its excellent customer support, with 24/7 phone and email support available to assist with any issues or questions. Another alternative to Spreedly is Braintree, a flexible payment processing solution that offers a wide range of features and integrations. Braintree is known for its ease of use and seamless integration with popular e-commerce platforms like Shopify and WooCommerce. One of the main advantages of Braintree is its support for a wide range of payment methods, including digital wallets, credit and debit cards, and alternative payment options like PayPal and Venmo. This makes it an ideal choice for businesses looking to offer their customers a variety of payment options. Additionally, Braintree offers competitive pricing with no setup fees and transparent transaction fees. It also provides advanced features such as recurring billing, fraud protection, and customizable reporting, making it a comprehensive solution for businesses of all sizes. Furthermore, Braintree offers responsive customer support with phone and email assistance available to help with any issues or questions. Adyen: A global payment platform for expanding businesses Category | Value Revenue | 1,000,000 Profit | 500,000 Expenses | 500,000 Adyen is another alternative to Spreedly that offers a comprehensive payment platform for businesses looking to expand internationally. One of the main advantages of Adyen is its support for over 200 payment methods and 150 currencies, making it an ideal choice for businesses looking to reach customers around the world. Adyen also offers advanced features such as risk management, subscription billing, and real-time reporting, making it a comprehensive solution for businesses of all sizes. Additionally, Adyen provides competitive pricing with transparent fees and no setup or monthly fees. It also offers responsive customer support with 24/7 phone and email assistance available to help with any issues or questions. ## Choosing the best Spreedly alternative for your business In conclusion, there are several alternatives to Spreedly that offer more features and better support for businesses looking to expand their payment options. Stripe, Braintree, Adyen, and Authorize.Net are all robust payment gateway solutions that offer a wide range of features and integrations, making them ideal choices for businesses of all sizes. When choosing the best Spreedly alternative for your business, it's important to consider factors such as supported payment methods, pricing, additional features, and customer support. By carefully evaluating these factors, you can find the best payment gateway solution that meets the unique needs of your business and provides a seamless payment experience for your customers. ## Related Reading Explore More ### Embedded Payments for ERP Platforms ### PCI Compliance Cost for Platforms: What It Really Costs in 2026 ### PCI-Compliant Payment Architecture for Insurance Platforms ### Agentic Payments: What Platforms Need to Know ### How PSPs Get Distribution Into Enterprise Software ### Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideEmbedded Payments for ERP Platforms→](/guides/payments-for-erp-platforms/) - [GuidePCI Compliance Cost for Platforms: What It Really Costs in 2026→](/guides/pci-compliance-cost-platforms/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [GuidePayments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure→](/guides/payments-for-travel-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/understand-online-payments-transform-your-business/ --- # Understand Online Payments - Transform your business | Shuttle > A comprehensive guide to online payments for businesses. Understand payment gateways, processors, and how to choose the right solution for your needs. # Understand Online Payments - Transform your business By Nick Dunse, February 18, 2026 A comprehensive guide to online payments for businesses. Understand payment gateways, processors, and how to choose the right solution for your needs. Talk to us Make enabling payments for your platform and merchant users easy. An online payment is a payment that is made by a customer to a merchant for a service or product. This payment is routed through various services to ultimately settle in the merchant's (the seller's) bank account and be deducted from the customer's bank or credit account. The service or product does not have to be digital for an online payment. I'm sure you already knew all that but if you're a merchant or an accountant who provides services for merchants what do you need in place to accept online payments? Additionally, how are online payments transforming traditional business payments and bank transfers? Firstly, if you want to withdraw money from sales into a place you can spend it freely you'll need a bank account, this might be a traditional bank account or one of the new digital-only accounts that are springing up like Monzo, Starling or Tide (the only digital business account); basically, you need somewhere for your money to end up. But, if you don't want to withdraw it, you may not even need a bank account, you can keep it within the ecosystem of your payment gateway and spend it with other compatible merchants and traders, think PayPal balance and then spending your PayPal balance on Ebay or another retailer that accepts PayPal. What is a payment gateway? Well, first up I'll address what is a merchant account because that's where things started. A merchant account is an account that creates an agreement between you (the merchant) and the credit card issuing companies (VISA, Mastercard etc), this allows you to accept these types of payments. Many merchant account providers also provide payment gateway solutions and as the name suggests this is the entry point for taking a payment. A payment gateway is the point at which you want to transact a payment with your customer, an example of a payment gateway that most people will know is PayPal, but traditional banks also offer payment gateway solutions for their merchant accounts, it's just that traditionally, these have been expensive to use and not particularly compatible with online software like e-commerce solutions. So a typical setup and chain of payment events would look like this: Customer - Online shop - Payment Gateway - Card issuer - Merchant account/Bank account - Merchant You could have a much simpler online payments setup, for example, if you wanted to take payment over the phone for a product then you could use Stripe's Checkout service and key in the customer's card details directly into this via the Stripe online payments page (called Stripe Checkout). Stripe is a payment gateway (in simplest terms); this is still an online payment since the payment details were entered into an online form. This removes the need to have a physical point of sale terminal sitting on a desk connected to a phone line. So it could look like this: Merchant - Phone call - Payment Gateway - Bank account - Customer So what are the current challenges with online payments? - Which merchant account or payment gateway do you choose? - How do these payment gateways work with my other software e.g. accounting, e-commerce, CRM etc? - Do I need a merchant account or any other technology in the payments chain? - Reconciling seemingly anonymous online transactions for accounting purpose can be a nightmare. Imagine you've got lots of transactions hitting your bank account from online sales with no further information. To help you decide which merchant account or payment gateway you choose for your business depends on a few things and for some businesses they have a pre-existing relationship that makes sense to continue with, purely from a convenience point of view. Firstly, which territories do you want to sell in? This will be the biggest limiting factor to employing a payment gateway since not all accounts/gateways are available in all territories across the world, this might be due to higher risk territories being less desirable and certain regulations in a territory. Secondly, The type of product or service you sell will limit what gateways you can use, if you sell something that is deemed as high risk or politically dubious then you will need to find a friendly gateway who will charge you higher fees for the privilege, someone like Skrill can be considered. Thirdly, consider the fees and services that are attached to each payment gateway, these differ wildly from provider to provider and are different depending on what territories you want to sell in. Fourthly, what payment methods do you want to offer or are relevant for your customers? Do you just want to accept cards or do you want to accept another form of payment: e-check, Direct Debit or SEPA for example? There are further payment twists offered by companies like Klarna, who think they can increase conversion by letting customers pay later. Fifthly, what's the experience that you'd like your customers to have and what in-house resource do you have for deploying these solutions? Do you want customers to pay on your website or on a PayPal page for example, what are the advantages for your business sector? Sometimes sending customers to a payment page can enlist greater trust in the payment process, but often a frictionless, seamless, branded payment process is preferable to convert a sale. Then there's the challenge of finding a payment gateway that integrates with your existing technologies, you'd think this would be easier than it is, for example, if you're using QuickBooks Online and you would like to have your invoices paid online you can only use QuickBooks merchant services, PayPal or GoCardless payment gateways. This is highly restrictive but you can understand why QuickBooks doesn't offer any more options since they'd have to have relationships with all these gateways and create and maintain the technology. Selling into the territories that you want to reach may require you have more than one payment gateway in place because a single gateway might provide cheaper rates but not have a presence in a territory or currency you need so you need another, the problem here is that it's not always possible to run multiple gateways with your other software, or the gateway you need is simply not integrated. Do you need other elements in the chain, do you need a separate merchant account or another point of sale device and payment gateway? It's really a cost-benefit equation you need to weigh up, would it increase your sales and would that outweigh the costs of cutting in these other elements plus the integration overhead? Reconciling online payments is often an afterthought that comes too late in the day and your left clearing up a mess with a string of bookkeepers and accountants at your side. On one hand, a series of anonymous payments hitting your bank account isn't a bad thing. But if you ever need to refund one of these, or work out why the payment amount is different to the invoice, split out the fees and shipping or do any kind of customer service or intelligence from this then you're in trouble. The 'paper' trail isn't there and management accounting brings a whole new benefit to your world. To compare merchant accounts and payment gateways to find out which ones might be right for your business you can google 'payment gateway comparison'. Before you do that here are some handy tips on what to look out for: - Security: PCI DSS Compliance Level - Ease of Integration - Uptime & Reliability Record - The Right Level of Fraud Detection - Payment Options Accepted - Multiple Currencies Accepted - Real-Time Reporting And you should look out for these associated costs: - One time Set-up Fee: - Monthly Fee: - Transaction Fee: - Transaction Rate: (may be charged by your merchant account provider rather than payment gateway provider) In conclusion, online payments are here to stay and according to a UK YouGov survey, 50% of respondents would end a sale if their preferred payment option wasn't available so improving your customers' payment experience as well as your back office administration goes hand-in-hand and is a must. ## Related Reading Explore More ### How to Get Payments Off Your Product Roadmap ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Virtual Terminal Payments: PCI Rules and Secure Alternatives ### PCI Compliant Phone Payments: How to Take Card Payments Over the Phone ### Agent-Assisted Payments: Secure Card Capture on Live Calls ### IVR Payments: PCI Compliant Self-Service Phone Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [Monzo](https://monzo.com/) - [Starling](https://www.starlingbank.com/) - [Tide](https://www.tide.co/) - [PayPal](https://www.paypal.com/) - [Stripe Checkout](https://stripe.com/checkout) - [Skrill](https://www.skrill.com/) - [Klarna](https://www.klarna.com/) - [QuickBooks Online](https://quickbooks.intuit.com/) - [GoCardless](https://gocardless.com/) - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideVirtual Terminal Payments: PCI Rules and Secure Alternatives→](/guides/virtual-terminal-payments/) - [GuidePCI Compliant Phone Payments: How to Take Card Payments Over the Phone→](/guides/pci-compliant-phone-payments/) - [GuideAgent-Assisted Payments: Secure Card Capture on Live Calls→](/guides/agent-assisted-payments/) - [GuideIVR Payments: PCI Compliant Self-Service Phone Payments→](/guides/ivr-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/ --- # Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It | Shuttle > What is payment gateway aggregation? How SaaS platforms use a single integration to connect to multiple PSPs -- reducing cost, improving reliability, and... # Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It By Nick Dunse, February 19, 2026 What is payment gateway aggregation? How SaaS platforms use a single integration to connect to multiple PSPs -- reducing cost, improving reliability, and... Talk to us Make enabling payments for your platform and merchant users easy. Most SaaS platforms start with a single payment gateway. Stripe, Adyen, Worldpay -- pick one, integrate it, move on. It works fine until it doesn't. The cracks appear when enterprise customers demand a specific PSP. Or when your single gateway has an outage and every merchant on your platform stops taking payments. Or when you expand into a new region and discover your gateway doesn't support local acquiring there. Suddenly one integration isn't enough, and building a second means weeks of dev time, a new contract, and another set of webhooks to maintain. Payment gateway aggregation solves this. Instead of integrating with each PSP individually, your platform connects to a single aggregation layer that routes transactions to whichever gateway is appropriate -- based on geography, merchant preference, cost, or availability. One integration. Multiple PSPs. No lock-in. This guide covers what payment gateway aggregation is, how it works technically, and when it makes sense for SaaS platforms to adopt it. ## What Is Payment Gateway Aggregation? Payment gateway aggregation is the practice of connecting to multiple payment service providers (PSPs) through a single integration point. Rather than building and maintaining separate integrations for each gateway, a platform uses an aggregation layer that normalises the APIs, handles credential management, and sends each transaction to the PSP the platform configured. Think of it as an abstraction layer for payment gateways. Your platform sends a payment request to the aggregator. The aggregator translates it into the format required by the target PSP, submits it, and returns a standardised response. Your platform doesn't need to know whether the transaction was processed by Stripe, Worldpay, or a regional acquirer in Southeast Asia. One API, many providers underneath. For SaaS platforms, aggregation addresses a structural problem. As your customer base grows, payment requirements diversify. Different merchants want different PSPs. Different regions need different acquirers. Without aggregation, each requirement becomes a separate integration project competing for engineering time with your core product. ## How Payment Gateway Aggregation Works The architecture has three layers: the inbound API, the routing and transformation layer, and the outbound PSP connections. 1. Single inbound API. Your platform integrates once with the aggregator's API. This API accepts payment requests in a standardised format -- amount, currency, card or payment method token, merchant identifier, and any metadata your platform needs to pass through. The format stays the same regardless of which PSP ultimately processes the transaction. 2. Routing and transformation layer. When a payment request arrives, the aggregation layer determines which PSP should handle it. Routing can be based on: - Merchant configuration -- The merchant has specified which PSP they want to use, either globally or per payment method. This is common in enterprise scenarios where merchants have negotiated rates with a specific acquirer. - Geography -- The transaction is routed to a PSP with local acquiring capability in the cardholder's country. A payment from a German cardholder might route to a European acquirer, while a payment from a US cardholder routes to a US-based PSP. - Payment method -- Some PSPs handle cards well but don't support local bank transfers. Others specialise in alternative payment methods like iDEAL, Boleto, or UPI. The aggregation layer routes each payment method to a PSP that supports it. - Availability -- If a PSP is experiencing downtime or degraded performance, you can move the affected payment types to a backup provider. The aggregation layer then transforms the request into the format the target PSP expects -- mapping field names, applying PSP-specific authentication, and handling the quirks in each provider's API. 3. Outbound PSP connections. The aggregation layer maintains pre-built, tested, and certified connections to each PSP. These connections handle authentication, request formatting, response parsing, error handling, and webhook reconciliation. When a new PSP is added to the aggregator's network, every platform using the aggregator gains access to it without writing a single line of code. Responses flow back through the same layers in reverse. The PSP returns a result, the aggregation layer normalises it, and your platform receives a standard response. Refunds, chargebacks, and settlement data follow the same path. ## Benefits of Payment Gateway Aggregation for SaaS The case for aggregation strengthens as your platform scales. Here are the specific benefits that matter most to SaaS companies. PSP flexibility without integration overhead. Enterprise customers have existing PSP relationships with negotiated rates. They won't switch providers just because your platform only supports Stripe. With aggregation, you can support whatever PSP the merchant already uses. "We need you to support our gateway" stops being a six-month engineering project and becomes a configuration change. Redundancy across providers. Every PSP has outages. Stripe, Adyen, Worldpay -- all of them. If your platform relies on a single gateway and it goes down, your merchants stop taking payments. With multiple gateways connected through an aggregation layer, transactions reroute to a backup PSP automatically. Your merchants may not even notice. Local acquiring across regions. Processing a UK cardholder's payment through a US-based acquirer incurs cross-border fees and lower authorisation rates. Aggregation lets you route transactions to acquirers with local presence in the cardholder's region. A European payment routes to a European acquirer. An APAC payment routes to a regional processor. The result is lower costs and higher approval rates for your merchants. Merchant choice as a competitive advantage. Letting merchants choose or bring their own PSP is a competitive differentiator. It signals that your platform is open and not locking merchants into a payment stack they didn't choose. This matters in verticals like insurance, travel, and enterprise field services where PSP mandates are common. Reduced PCI scope. When the aggregation layer handles card data and tokenisation, your platform never touches sensitive payment information. PCI DSS compliance sits with the aggregation provider, not your engineering team. This eliminates the need for a costly embedded payments build that would bring PCI scope in-house -- typically a $2M+ compliance investment. Negotiating leverage. When your platform is locked into a single PSP, that PSP has all the leverage on pricing. When you can switch PSPs or split volume across multiple providers, the dynamic shifts. Aggregation gives platforms the ability to negotiate from a position of optionality rather than dependency. ## Payment Aggregation vs Payment Orchestration These terms get used interchangeably, but they describe different things. Understanding the distinction helps you choose the right approach for your platform. Payment gateway aggregation is about connectivity. It gives your platform a single integration point to multiple PSPs. The primary value is reducing the number of integrations you need to build and maintain. Routing decisions tend to be configuration-driven: this merchant uses PSP A, that merchant uses PSP B. Payment orchestration builds on top of aggregation by adding intelligent, real-time routing logic. An orchestration layer might analyse each transaction and route it to the PSP with the highest expected authorisation rate for that card type and geography. It might implement cascading retries -- if PSP A declines a transaction, automatically retry on PSP B. It might split a single payment across multiple providers for risk distribution. In practice, the relationship looks like this: - Aggregation = multi-PSP connectivity through one API (the foundation) - Orchestration = aggregation + smart routing + retry logic + transaction-level optimisation (the layer on top) Not every platform needs full orchestration. If your primary requirement is multi-PSP support so merchants can choose their provider, aggregation delivers most of the value. Orchestration matters when you're processing high volumes and want to optimise authorisation rates at the transaction level. For a deeper comparison, see our guide on PSP-neutral vs single-PSP architectures. ## When Your SaaS Needs a Payment Aggregation Platform Not every platform needs multi-PSP support from day one. A direct integration with one PSP is fine early on. Aggregation becomes necessary when you hit specific growth triggers. Enterprise customers are asking for specific PSPs. This is the most common trigger. A prospect says: "We use Worldpay and we're not switching." If your platform only supports Stripe, you lose the deal or start a three-month integration project. You're expanding into new regions. Different markets have different preferred payment methods and acquirers. Expanding into Europe might require local acquiring in Germany, France, and the Nordics. Latin America might require Boleto or PIX in Brazil. Each new region potentially means a new PSP integration. Gateway outages are hurting your merchants. If you've experienced a PSP outage with no fallback, you know the cost. Merchants lose revenue, your support queue floods, and your platform looks unreliable. Aggregation makes adding a backup PSP practical without doubling integration maintenance. Payment integrations are consuming your roadmap. If your engineering team spends more time maintaining PSP integrations than building your core product, something is wrong. Aggregation offloads that complexity so your team can focus on what makes your product unique. You want one integration across every PSP. Many SaaS platforms treat payments as a feature. Platforms that think bigger treat payments as a revenue stream -- taking a share of transaction volume or charging for premium payment features. An aggregation layer with embedded payment infrastructure makes it possible to white-label a full payments experience for your merchants without becoming a PayFac yourself. ## How Shuttle Provides Gateway Aggregation Shuttle is a payment layer for software platforms that includes gateway aggregation as a core capability. Through a single integration, your platform connects to 40+ PSPs -- including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and dozens of regional acquirers. Here is how it works in practice: - One API, many PSPs. Your platform integrates with Shuttle's API once. Shuttle handles the translation, routing, and communication with each PSP. When a new PSP is added to the network, your platform gets access automatically. - Merchant-level PSP selection. Each merchant on your platform can be configured to use a different PSP. One merchant can process through Worldpay while another uses Adyen. Merchants can even bring their own PSP credentials -- Shuttle onboards them and manages the connection. - Multi-channel payment capture. Shuttle's aggregation extends beyond checkout pages. The same integration supports voice payments (IVR and agent-assisted), payment links via SMS, email, or chat, and embedded checkout flows. All channels route through the same PSP connections. - White-label merchant onboarding. Shuttle provides a branded merchant portal where your merchants sign up, configure their PSP, and manage transactions. It looks like your product. End users never see Shuttle. - PCI DSS Level 1 compliance included. Shuttle is a PCI DSS Level 1 certified service provider with ISO 27001 and SOC 2 certifications. Your platform never handles card data directly, which means limited PCI scope on your side. Platforms typically go live with Shuttle in weeks, not months. There is no need to build separate integrations for each PSP, handle PCI compliance, or staff a payments engineering team. The gateway aggregation model means your platform gets multi-PSP support from day one, and adding new gateways as your merchants require them is a matter of configuration, not code. ## FAQ ### Is a payment aggregator the same as a PayFac? No. A PayFac (payment facilitator) is a regulated entity that processes payments on behalf of sub-merchants. The PayFac assumes liability, maintains reserves, and handles KYC/KYB for every merchant. Becoming a PayFac typically takes 6-12 months and costs millions in compliance. A payment aggregator provides connectivity to multiple PSPs but does not process payments itself. The PSP remains the processor of record. The aggregator routes transactions to the correct PSP and normalises the integration. Platforms using an aggregation layer like Shuttle can offer multi-PSP payments without taking on PayFac regulatory burden. ### How many gateways can I connect through an aggregator? It depends on the provider's network. Shuttle connects to over 40 PSPs globally, covering Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and regional acquirers across Europe, APAC, and the Americas. If you need a PSP that isn't already connected, new gateways can typically be added on request. ### Does aggregation increase PCI scope? It should reduce it. A well-architected aggregation layer handles all card data, tokenisation, and secure communication with PSPs on your behalf. Your platform never receives, transmits, or stores cardholder data directly. Shuttle is PCI DSS Level 1 certified, which means the compliance burden sits with Shuttle, not with your platform. If you're currently integrating directly with a PSP and handling card data, moving to an aggregation layer will likely reduce your PCI scope rather than increase it. ## Related Reading Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ## Links - [Book a Call →](/discovery/) - [payment gateway](/glossary/payment-gateway/) - [embedded payments](/guides/what-is-embedded-payments/) - [Payment orchestration](/guides/what-is-payment-orchestration/) - [PSP-neutral vs single-PSP architectures](/guides/psp-neutral-vs-single-psp/) - [embedded payment infrastructure](/platforms/) - [Shuttle](/discovery/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [gateway aggregation model](/blog/what-is-payment-gateway-aggregation/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/updates-from-the-uk-payment-systems-regulator-for-2023/ --- # Updates from the UK Payment Systems Regulator for 2023 | Shuttle > Key updates from the UK Payment Systems Regulator (PSR) -- including APP fraud protections, interchange regulation, and the impact on merchants and payment... # Updates from the UK Payment Systems Regulator for 2023 By Nick Dunse, May 25, 2022 Key updates from the UK Payment Systems Regulator (PSR) -- including APP fraud protections, interchange regulation, and the impact on merchants and payment... Talk to us Make enabling payments for your platform and merchant users easy. I. Introduction The UK payment systems regulator has released its annual report for 2023, providing updates on key highlights from the UK payments strategy, the implementation of the new payments system, open banking compliance, fraud prevention measures, digital identity verification solutions, cross-border payments, and international collaboration. In this article, we will examine each of these areas in detail and provide insights into the latest developments in the UK payment landscape. II. Key Highlights from the UK Payments Strategy The UK payments strategy has been a topic of discussion for several years now. In March 2021, the UK Payments Strategy was published as part of the government's response to the pandemic. The document outlines the key highlights of the strategy, including the introduction of new payment systems and increased focus on digital transformation. One of the most significant changes outlined in the strategy is the implementation of the New Payments System (NPS). This system is designed to improve the speed and efficiency of payments processing in the UK. Additionally, the strategy emphasizes the importance of open banking compliance and fraud prevention measures. The document also discusses digital identity verification solutions and cross-border payments, highlighting the need for international collaboration in these areas. Overall, the UK Payments Strategy is a significant step towards modernizing the country's payment infrastructure and ensuring that it remains competitive in the global marketplace. III. Update on the New Payments System (NPS) Implementation The UK government has made significant progress towards implementing its new payments system, known as the New Payments System (NPS). The NPS aims to modernize the country's payment infrastructure and enhance the speed, security, and efficiency of payments processing. To date, several key milestones have been achieved in the implementation of the NPS. These include the launch of a sandbox environment for testing new payment applications, the release of technical specifications for NPS-enabled devices, and the development of a comprehensive education and awareness campaign to inform stakeholders about the benefits of the new system. In addition, the UK Payments Strategy has identified the need to address the growing threat of cybercrime in the financial sector. As part of this effort, the regulator is working closely with industry stakeholders to develop new fraud prevention measures and improve the resilience of the UK payment systems. Overall, the implementation of the NPS represents a major milestone in the evolution of the UK's payment infrastructure. By enhancing the speed, security, and efficiency of payments processing, the new system will enable businesses and individuals to conduct transactions more easily and securely than ever before. IV. Focus on Open Banking 2.0 Compliance Open Banking 2.0 compliance has become a crucial aspect of financial services in the UK since its introduction in 2018. The UK payments systems regulator, the Financial Conduct Authority (FCA), has been working closely with stakeholders to ensure that businesses comply with the regulations set out under this framework. In particular, the FCA has focused on improving customer outcomes through increased transparency, competition, and innovation in the sector. This includes measures such as requiring firms to provide clear and concise information about their products and services, ensuring that customers have control over their data, and promoting competition among providers. As the industry continues to evolve, the FCA will continue to monitor compliance with Open Banking 2.0 regulations to ensure that consumers remain protected. V. Discussion on Fraud Prevention Measures in the UK The UK payments industry has seen significant growth over the years, and with this growth, there have been increasing concerns around fraud prevention measures. The UK Payment Systems Regulator (PSR), which oversees the regulation of payment systems in the country, has taken several steps to address these concerns. One of the key areas of focus has been on improving authentication methods for customers making payments. This includes the implementation of biometric authentication such as facial recognition technology or voice recognition. Additionally, the PSR has introduced new rules requiring banks to verify the identity of their customers before allowing them to open accounts. These measures are aimed at reducing the risk of fraud and ensuring that customers can trust the security of their transactions. However, the regulator acknowledges that the fight against fraud is an ongoing challenge and that continued innovation and collaboration between industry stakeholders will be necessary to stay ahead of emerging threats. Overall, the PSR remains committed to working closely with industry players to ensure that the UK continues to have one of the most secure and reliable payment systems in the world. VI. Examination of Digital Identity Verification Solutions The UK payments industry has seen significant changes in recent years, with the introduction of new payment systems and regulations aimed at improving security and reducing fraud. One area that has received particular attention is digital identity verification solutions. Digital identity verification solutions use advanced technology to verify the identity of individuals or businesses making transactions online or through mobile devices. This helps to prevent fraudulent activities such as identity theft, money laundering, and cybercrime. The UK Payments Systems Regulator has been working closely with industry stakeholders to develop and implement digital identity verification solutions that meet regulatory requirements and provide greater protection for consumers and businesses. One example of a digital identity verification solution is biometric authentication, which uses unique physical characteristics such as fingerprints, facial recognition, or voice recognition to confirm the identity of individuals. Another solution is multi-factor authentication, which requires users to provide additional evidence of their identity beyond a simple username and password. In addition to these solutions, the UK Payments Systems Regulator is also exploring the use of artificial intelligence and machine learning algorithms to improve the accuracy and speed of digital identity verification processes. As cross-border payments and international collaboration continue to grow, digital identity verification solutions will become increasingly important for ensuring the security of financial transactions. The UK Payments Systems Regulator will continue to work with industry stakeholders to ensure that digital identity verification solutions meet the highest standards of security and compliance. VII. Outlook on Cross-Border Payments and International Collaboration The UK payments industry has been at the forefront of innovation in cross-border payments and international collaboration. The UK Payments Strategy 2021-2025 emphasizes the importance of facilitating seamless and efficient cross-border payments, particularly in light of Brexit. The strategy aims to enhance the UK's position as a global leader in fintech and digital payments by leveraging its strengths in open data, innovative technologies, and regulatory expertise. One key area of focus is the development of new payment methods such as real-time gross settlement (RTGS), which can facilitate faster and more secure cross-border payments. Additionally, the UK is exploring the use of distributed ledger technology (DLT) to streamline international payments and reduce the risk of fraud. Looking ahead, the UK will continue to collaborate with international partners to ensure a smooth transition after Brexit. The UK Payments Strategy recognizes the need for continued dialogue with European Union counterparts to ensure continuity of payments services across borders. Overall, the outlook for cross-border payments and international collaboration in the UK remains positive, with opportunities for growth and innovation in the years to come. VIII. Conclusion In conclusion, the UK payment systems regulator has made significant strides towards ensuring a secure and efficient payments ecosystem in the country. The implementation of the NPS, compliance with Open Banking 2.0, fraud prevention measures, digital identity verification solutions, cross-border payments, and international collaboration are all important areas that require attention. As we move forward into 2023, it is essential to continue to prioritize these areas to ensure a safe and reliable payments environment for all consumers and businesses in the UK. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)→](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/voice-ai-payment-infrastructure-gap/ --- # Voice AI Is Booming -- But Can It Take a Payment? | Shuttle > The voice AI market hit $47.5B. Every CCaaS vendor is deploying AI agents. But when a customer needs to pay, most voice AI hits a wall. # Voice AI Is Booming -- But Can It Take a Payment? By shuttle-team, February 23, 2026 The voice AI market hit $47.5B. Every CCaaS vendor is deploying AI agents. But when a customer needs to pay, most voice AI hits a wall. Talk to us Make enabling payments for your platform and merchant users easy. ## The Voice AI Boom Is Real The voice AI market is valued at $47.5 billion and accelerating. That figure isn't a projection built on wishful extrapolation -- it reflects what's already deployed in enterprise contact centres today, and what's being fast-tracked for the next 18 months. Every major CCaaS vendor is executing the same playbook. Genesys has rebuilt its routing engine around generative AI, positioning AI-native agents as a core product rather than an add-on. NICE has rolled out Enlighten AI across its CXone platform, replacing scripted IVR flows with conversational models. Amazon Connect launched its Q in Connect capability, letting contact centre operators deploy large language models on top of existing telephony infrastructure without a full platform replacement. The fundraising signals are just as clear. PolyAI raised $86 million at a $750 million valuation, making it one of the best-capitalised AI voice companies in the market. Their thesis is straightforward: voice AI is the new front door to customer experience. The phone is not dead -- it's being rebuilt from scratch. Operators agree. Gartner estimates that by 2027, AI voice agents will handle a majority of routine customer service contacts that previously required a human agent. The transition from IVR to generative voice AI is not incremental -- it's a wholesale replacement of the old call routing model with something that can hold a real conversation. The channel is validated. Enterprises are committed. The investment has been made. And yet, when a customer says "I'd like to make a payment" -- most voice AI hits a wall. ## The Wall Picture the scenario. A customer calls their insurance company to renew a policy. The AI voice agent handles the call fluently. It retrieves the customer's account, confirms the renewal terms, answers a question about the coverage details, and moves naturally toward close. Then: "Great. Would you like to pay by card today?" This is where the architecture breaks. The customer says yes. The AI agent has no secure mechanism to capture card data over the live voice channel. It cannot request card digits without exposing them to systems that are not PCI-certified. It cannot pause the conversation and hand off to a DTMF capture environment without either disrupting the call flow or exposing sensitive audio to its own speech-to-text pipeline. The most common outcomes in production today: - The agent hands off to a human agent to take the payment -- defeating the automation case entirely - The agent sends a payment link via SMS and asks the customer to pay separately -- killing the in-call conversion - The platform instructs the agent to decline payment capture entirely and redirect customers to a website -- turning a potential end-to-end automated transaction into a multi-step, multi-session process - The agent processes payment through an insecure channel, unknowingly putting the platform out of PCI compliance None of these are acceptable at scale. None of them reflect the promise of AI voice as a customer experience channel. The channel has been rebuilt. The payment infrastructure hasn't. ## Why This Is an Infrastructure Problem, Not a Software Problem There is a tempting assumption among voice AI product teams: that PCI compliance for voice payments is a software configuration question. Add a library, enable a flag, toggle a setting in the conversation flow -- and the payment works. This is wrong, and it's wrong in ways that matter. PCI DSS scope is architectural, not configurational. PCI DSS Level 1 -- the certification required for any platform processing significant card volume -- governs how cardholder data is stored, transmitted, and processed. An AI voice agent that processes card audio through its speech-to-text pipeline (even momentarily, even without storing it) is in scope. An AI model that receives card digits as part of a conversation transcript is in scope. Scope is determined by whether card data touches a system, not by whether the system is "trying" to handle card data. DTMF capture requires purpose-built infrastructure. The standard for PCI-compliant voice payments is DTMF (Dual-Tone Multi-Frequency) capture -- the customer enters card digits via their phone's keypad rather than reading them aloud. The DTMF tones must be captured by a PCI-certified environment that is architecturally separated from the AI voice agent. The AI agent's audio stream is paused during card entry. Card data never reaches the speech-to-text engine or the language model. Confirmation is returned to the agent without card data crossing the boundary. This requires the voice platform and the payment layer to integrate at the telephony layer -- not just at the API layer. It is a non-trivial integration that requires a payment partner with voice-specific infrastructure. Secure card capture over live voice is not the same as online card capture. Web-based PCI compliance (SAQ A, hosted checkout pages) is relatively well-understood. Voice PCI compliance is different. The card capture environment must integrate with the voice channel's telephony infrastructure, handle DTMF tone detection, manage real-time call state, route the captured data to the PSP, and return a payment confirmation -- all within the window of an active phone call. Latency, call drops, and DTMF detection errors are operational realities that don't exist in online checkout. The infrastructure must be built for voice, not adapted from web. Fraud detection and identity verification over voice require separate consideration. A web checkout has device fingerprinting, IP analysis, and behavioural signals to inform fraud scoring. A voice call has caller ID and the customer's spoken responses. Voice-specific fraud signals -- caller ID spoofing, synthetic voice detection, call velocity -- need to be integrated at the payment layer. This is not a capability that ships with a generic payment API. The software problem -- getting the AI agent to understand that a payment is needed and to manage the conversation flow around it -- is largely solved. The infrastructure problems underneath it are not. ## The CCaaS Gap: Incumbents and Startups Both Face It The infrastructure gap exists across the full CCaaS market, but for different reasons depending on whether you're talking about the incumbents or the AI-native entrants. The incumbents (Genesys, NICE, Amazon Connect) built their payment flows for human agents. The existing payment infrastructure in enterprise CCaaS was designed around agent-assisted payment capture: a human agent stays on the line while the customer enters card details via DTMF, or reads card numbers to an IVR after the agent has handed off the sensitive portion of the call. PCI compliance was maintained because the human agent was removed from the card capture environment -- the call was transferred to a separate, certified IVR system. When AI voice agents replace human agents, this architecture doesn't simply carry over. The AI agent is not a drop-in replacement for the human in the existing flow. It needs its own integration to the PCI-certified capture environment, its own handling of the call state transition, and its own mechanism for receiving payment confirmation and continuing the conversation. Most CCaaS platforms have not rebuilt this flow for AI-native agents yet -- they've shipped the AI conversation capabilities and left the payment integration as a gap for the customer to solve. The AI-native startups are inheriting the same gap without the institutional knowledge. Companies like PolyAI, Parloa, Bland.ai, and the growing field of AI voice platforms have solved the hard problem -- building conversational AI that can handle enterprise customer service at scale. Most of them have not yet built, or are in the process of building, production-grade voice payment infrastructure. The challenge is predictable: voice payment infrastructure is not their core competency, and it shouldn't be. Building PCI DSS Level 1 infrastructure requires dedicated compliance investment, annual audits, specialised engineering, and ongoing operational overhead. For a voice AI company whose core product is conversational AI, turning a significant portion of engineering capacity toward PCI certification is a serious detour. The result is that many AI voice platforms ship without payment capability, or with a payment capability that works for simple use cases but fails the compliance bar required by enterprise CCaaS customers in regulated industries. Voice AI without embedded payment capture is a lobby without a checkout counter. You can greet customers, answer their questions, and move them through a conversation -- but you cannot close the transaction. ## What Payment-Ready Voice AI Actually Looks Like The architecture for production-grade AI voice payments is not theoretical. It is deployed and handling real enterprise transactions today. The separation model is foundational. The AI voice agent handles the conversation. The payment layer handles card data. These two systems are architecturally separated, with a clearly defined handoff: the AI agent triggers a payment request (amount, currency, merchant context), the payment layer captures card data via DTMF, processes the transaction through the merchant's PSP, and returns a payment confirmation. Card data never enters the AI agent's environment. DTMF capture is the proven standard. When payment is required, the voice channel temporarily routes the customer's keypad input to the PCI-certified payment environment. The AI agent's speech-to-text processing is suspended. The customer enters card digits via keypad. The payment layer confirms the transaction. The call returns to the AI agent with a payment reference. The agent confirms payment and continues the conversation. From the customer's perspective, this is a brief, natural pause -- equivalent to typing card details on a website. PSP-neutral infrastructure is a hard requirement at enterprise scale. An AI voice agent platform serving multiple enterprise customers will encounter a different PSP at each account. One customer uses Worldpay. Another uses Adyen. A third has a regional acquirer with bespoke API requirements. The payment layer must support each PSP through a single integration -- the AI platform cannot maintain individual PSP integrations for each customer. PSP-neutral architecture, with 40+ providers available through a single API, is the only operationally viable approach. Real-time confirmation is part of the product. The AI agent's conversation flow depends on knowing whether the payment succeeded immediately. A successful payment triggers a confirmation message and next steps. A decline triggers a retry flow or alternative payment option. A timeout triggers a graceful fallback. This requires the payment layer to return a webhook confirmation within the window of the live call -- typically under two seconds for a good customer experience. Infrastructure that processes payments asynchronously or with significant latency will break the voice conversation. Compliance is a platform-level requirement, not a customer problem. Enterprise CCaaS customers in regulated industries -- insurance, financial services, healthcare, utilities -- cannot deploy AI voice agents that handle payments unless the payment flow meets PCI DSS Level 1 requirements. This is not an optional certification tier. Platforms that cannot demonstrate Level 1 compliance, alongside ISO 27001 and SOC 2, will not get through enterprise procurement. The compliance must be in the payment layer, and it must be demonstrable at the point of sale. ## For CCaaS Providers and Voice AI Companies: What to Look for in a Payment Partner If you are building AI voice capability and payment is a required flow for your target customers, these are the non-negotiable criteria for a payment infrastructure partner: PCI DSS Level 1 certification -- specific to voice. Many payment providers carry PCI certification for online transactions. Voice payment certification is different and less common. Confirm the provider's certification explicitly covers DTMF capture over telephony channels. Ask for their Attestation of Compliance (AOC) and confirm the scope includes voice payment flows. Native DTMF integration, not a workaround. Some providers attempt to handle voice payments by routing customers to a separate IVR system mid-call. This breaks the customer experience and defeats the purpose of AI-native voice. The DTMF capture should integrate with your voice infrastructure at the telephony layer, not require a call transfer to a third-party system. PSP breadth. The payment partner needs to support the PSPs your enterprise customers already use. A partner with one or two PSPs will create blockers in enterprise sales. Confirm the provider's PSP coverage map before committing to an integration. Latency and reliability at enterprise scale. Voice payments fail in ways that web payments don't. Call drops, DTMF detection failures, and latency-induced timeouts create customer experience problems that are hard to recover from on a live call. Ask for SLA commitments on payment confirmation latency and uptime, and reference production deployments in enterprise CCaaS environments. Multi-channel coverage. Payment requirements in CCaaS don't stop at voice. Chat agents need payment links. SMS follow-ups need trackable checkout pages. Agents handling escalations need to transfer payment context across channels. A payment partner whose coverage is limited to voice will require additional integrations as your platform grows. Commercial model. Per-transaction pricing is standard for voice payments, but the commercial model varies significantly. Confirm whether the provider's pricing scales reasonably for enterprise volumes and whether there are revenue-share mechanisms for platforms that are embedding payments as a product feature for their customers. ## The Gap Is Closing -- But Slowly The voice AI market has moved faster than the payment infrastructure supporting it. That asymmetry is temporary -- enterprise deployments in regulated industries will force the payment capability question, and platforms that cannot answer it will lose deals to those that can. The good news is that the infrastructure model is proven. AI voice agents processing PCI-compliant payments through PSP-neutral payment layers is not a whiteboard concept. PolyAI processes payments at enterprise scale today. The architecture described in this guide -- DTMF capture, payment layer separation, PSP-neutral routing, real-time confirmation -- is production infrastructure, not a roadmap. The gap is not "can AI voice agents take payments." The answer is yes. The gap is between the voice AI platforms that have integrated production-grade payment infrastructure and those that have not. For CCaaS providers and voice AI companies evaluating where to direct engineering resources, the build-vs-partner decision on voice payments is clear: building PCI DSS Level 1 voice payment infrastructure in-house typically takes 12 to 18 months and consumes compliance resources that most voice AI companies do not have on staff. Integrating with a purpose-built payment layer takes weeks. The voice AI lobby has been built. The checkout counter is the next required addition. ## Related Reading - AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI -- the detailed architecture for keeping card data out of AI voice models - Agentic Payments in 2026: The Infrastructure Guide for Platforms -- the broader infrastructure landscape for AI agent payments across voice, chat, and machine-to-machine - AI Voice Payments for Insurance -- how regulated industries are deploying voice AI payments in production - Chat Agent Payments: How AI Chat Agents Take Payments Mid-Conversation -- extending the payment infrastructure model to AI chat - Agentic Payments for Platforms -- the platform-level case for embedding agentic payment infrastructure - Embedded Payments for CCaaS -- the CCaaS operator's guide to adding PCI-compliant payments Ready to close the payment gap in your voice AI platform? Shuttle powers PCI-compliant voice payments for AI voice agents and CCaaS platforms -- DTMF capture, PSP-neutral processing, real-time confirmation, 40+ PSPs through a single integration. Book a Demo | See How Platforms Use Shuttle Explore More ### Build vs Buy Payment Infrastructure: A Decision Framework for Platforms ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### How Voice AI Ordering Platforms Handle Payments -- And Why It's Broken ### What Are Voice Payments? The Complete Guide ### How AI Voice Agents Take PCI-Compliant Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI](/guides/ai-payment-security/) - [Agentic Payments in 2026: The Infrastructure Guide for Platforms](/blog/agentic-payments-infrastructure-2026/) - [AI Voice Payments for Insurance](/guides/ai-voice-payments-insurance/) - [Chat Agent Payments: How AI Chat Agents Take Payments Mid-Conversation](/guides/chat-agent-payments/) - [Agentic Payments for Platforms](/guides/agentic-payments-for-platforms/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [Book a Demo](/discovery/) - [See How Platforms Use Shuttle](/platforms/) - [GuideBuild vs Buy Payment Infrastructure: A Decision Framework for Platforms→](/guides/build-vs-buy-payment-infrastructure/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideHow Voice AI Ordering Platforms Handle Payments -- And Why It's Broken→](/guides/voice-ai-ordering-payments/) - [GuideWhat Are Voice Payments? The Complete Guide→](/guides/voice-payments/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/voice-payments-architecture-decision/ --- # Voice Payments Are an Architecture Decision, Not a Feature Request | Shuttle > Why CPaaS, CCaaS, and AI voice platforms need an embedded payment layer -- not another bolt-on integration. # Voice Payments Are an Architecture Decision, Not a Feature Request By Shuttle Team, February 26, 2026 Why CPaaS, CCaaS, and AI voice platforms need an embedded payment layer -- not another bolt-on integration. Talk to us Make enabling payments for your platform and merchant users easy. ## The shift Payments moved inside the call. Not "after the call." Not "we'll send you a link." Inside it. The customer says a number, the system captures it, the payment confirms, and the conversation continues. No handoff. No second session. No human in the loop. This happened because voice platforms matured. IVR gave way to intelligent routing. Intelligent routing gave way to AI agents. And AI agents hit the same wall every time. The ones handling collections, renewals, order confirmations, insurance claims. The customer is ready to pay, and the platform has nowhere to send them. For CPaaS providers, CCaaS vendors, and AI voice platforms, this is no longer a feature request. It's an architecture decision. And the wrong one costs years. ## Why platforms can't ignore this Your customers are already solving this problem. They're solving it badly. Collections teams are saying "I'll send you a link" and losing 30-40% of payment commitments in the handoff. Contact centres are asking callers to read card numbers over open lines, pulling PCI scope into systems that were never designed for it. AI agents are hitting a dead end the moment money enters the conversation, because there's no payment surface inside the call flow. These aren't edge cases. They're the default experience for any platform running voice at scale. The question for platform teams isn't whether your customers need payments inside voice. They do. The question is whether they solve it inside your platform or outside it. Outside means third-party bolt-ons, compliance risk you can't control, and a customer experience your platform gets blamed for but can't fix. Inside means you own the integration point. You control the experience. And you capture value on every transaction. ## Three architecture patterns Every platform that confronts this problem lands on one of three approaches. Two of them fail at scale. ### Pattern 1: Transfer-out The call hits a payment moment. The system transfers the caller to a separate IVR. A standalone payment line operated by a third party. The caller re-authenticates, enters card details, and either gets transferred back or hangs up. This is the legacy model. It works for low-volume, low-expectation use cases. It fails everywhere else. Transfer-out breaks the conversation. The AI agent loses context. The caller loses patience. Completion rates drop below 50% on most implementations because the friction of being bounced between systems is enough to make people give up. For AI voice platforms, transfer-out is structurally incompatible. The entire value proposition of an AI agent is that it handles the conversation end-to-end. Transferring to a separate IVR for payment is an admission that the agent can't do its job. ### Pattern 2: Bolt-on The platform integrates a single PSP's payment API directly into the call flow. Stripe, or Worldpay, or whichever PSP the first customer required. Card capture happens inline, maybe via DTMF, maybe via a pause-and-link flow. It works for that one PSP. Then the second customer needs Adyen. The third needs Checkout.com. The enterprise prospect mandates their existing acquirer relationship and won't negotiate. Bolt-on creates a linear scaling problem. Every new PSP requires a separate integration, a separate certification process, and ongoing maintenance as APIs change. By the third PSP, payments are consuming product and engineering resources that should be building the platform's core product. Worse, bolt-on usually means the platform is handling card data. Or at minimum, sitting in the PCI scope chain in ways that weren't planned for. One PSP integration is manageable. Five is a compliance programme. ### Pattern 3: Embedded layer A dedicated payment layer sits between the voice platform and any PSP. The platform makes one integration. The layer handles PSP routing, PCI compliance, card capture, and settlement across every gateway the customer needs. The voice platform never touches card data. The AI agent never sees a card number. The layer handles DTMF capture in a PCI-certified environment, confirms the payment in real time, and returns the result to the call flow. The agent says "your payment of £247 has been confirmed" and the conversation moves on. This is the only pattern that scales across customers, PSPs, and compliance requirements without turning payments into a permanent line item on the product roadmap. ## The PCI wall PCI compliance is where most platform teams underestimate the problem. The moment card data touches any system, even transiently, that system is in PCI scope. The voice platform, the call recording infrastructure, the AI model, the logging pipeline. All of it. For voice, the architecture has to enforce hard boundaries. DTMF capture must be separated. When a caller enters card digits via keypad tones, those tones must be intercepted and processed in a PCI-certified environment before they reach the platform's audio stream. The platform receives silence or flat tones during capture. The digits never reach the AI agent. The recording captures nothing. AI agents must never process card data. The language model handles the conversation. The payment layer handles the card. These two systems must be architecturally isolated. Not just logically separated, but running in different environments with different compliance boundaries. An AI model that has access to card data is a PCI problem that no QSA will sign off on. The real question is scope reduction, not scope management. The difference between SAQ-A and SAQ-D is the difference between a compliance checkbox and a six-figure annual audit programme. Platform teams that build payment capture in-house inherit SAQ-D. Platform teams that use an embedded layer operate at SAQ-A. This isn't a configuration decision. It's an architectural boundary that determines your compliance posture for years. ## The multi-tenant PSP problem Voice platforms are multi-tenant by nature. You don't serve one customer. You serve hundreds or thousands, each with their own payment stack. The mid-market customer uses Stripe because it was easy to set up. The enterprise customer mandates Worldpay because they negotiated rates across their entire business. The regulated customer requires a specific acquirer for compliance reasons. The international customer needs local acquiring in markets where your default PSP doesn't operate. A platform that supports one PSP serves one segment. A platform that supports any PSP serves the entire market. This is the multi-tenant PSP problem, and it's unique to platforms. A single merchant picks one PSP and moves on. A platform must support whatever PSP each of its merchants requires, without building and maintaining each integration. In voice, this compounds. Each PSP has different tokenisation flows, different API patterns for authorisation, different webhook formats for confirmation. Building DTMF capture that works with Stripe is one project. Making it work with Stripe, Adyen, Worldpay, Checkout.com, Braintree, and 35 others is a programme. The embedded layer pattern solves this. The platform integrates once. Each merchant is configured against their own PSP. Adding a new PSP for a new customer is configuration, not engineering. ## Build vs partner: the real numbers Every platform team's first instinct is to build it. "We'll integrate Stripe's API, add DTMF capture, handle PCI ourselves." The instinct is understandable. The maths isn't. Timeline: 12-18 months to production for a single PSP with PCI-compliant voice capture. That's not a guess. It's the consistent timeline reported by platform teams that have done it. DTMF integration, PCI audit preparation, acquirer certification, production hardening, edge case handling. Each step takes longer than expected. Cost: $2M+ fully loaded. Engineering time, PCI QSA assessment ($50-150k annually), infrastructure for a PCI-certified capture environment, ongoing maintenance as PSP APIs evolve. For a second PSP, add another 4-6 months and $500k+. Compliance burden: PCI DSS Level 1 assessment is not a one-time event. It's an annual cycle. Audit preparation, evidence gathering, remediation, assessor engagement. The internal team required to maintain certification is typically 2-3 dedicated headcount. The build path makes sense in exactly one scenario: payments are your core product and PSP integration is your competitive advantage. For every other platform, it's a misallocation of engineering resources toward a solved problem. This is what Shuttle does. One integration. 40+ PSPs. Voice capture via DTMF with architectural separation. The integration takes weeks, not quarters. The platform stays out of the cardholder data environment. ## What production looks like In production, the payment confirms inside the natural pause of the conversation. Under two seconds. The agent says "please enter your card number on your keypad." The caller enters digits. The tones are intercepted by the payment layer before reaching the platform's audio stream. The digits never reach the agent. The recording captures nothing. The payment processes. The agent confirms and moves on. No transfers. No separate IVR. No card data in the platform's environment. The platform receives structured webhook events. Payment initiated, payment confirmed, payment failed, refund processed. Enough to update CRM records, order status, customer accounts. The payment layer handles the transaction. The platform handles the business logic. The customer never knows the layer exists. The experience is branded as the platform's. The merchant portal is the platform's. The infrastructure is invisible. ## The revenue model platforms miss Most platform teams think about payments as a cost centre. Infrastructure to build, compliance to manage, PSPs to wrangle. A tax on the product roadmap. They're missing the revenue line. Every payment processed through your platform is a transaction you can monetise. Revenue share on payment volume. Paid by the PSP or the payment layer, not by the merchant. The platform's cut comes from the infrastructure it provides, not from charging its customers more. This is incremental revenue on existing call volume. No new sales motion. No new product to market. Customers are already making calls. They're already trying to pay. The platform just captures value on the transactions it's already facilitating. For a voice platform processing 100,000 payment transactions per month, even modest per-transaction economics generate a meaningful revenue line, with zero engineering investment after the initial integration. The payment layer handles PCI, PSP routing, and settlement. The platform collects a share. That's the model. ## Decision framework - Payments are your core product, not an adjacent feature - You need exactly one PSP and will never need another - You have dedicated PCI compliance staff and budget for annual assessment - You're prepared for a 12-18 month timeline before first production transaction Partner if: - Your customers use different PSPs and you need to support all of them - You want payments live in weeks, not quarters - PCI compliance is a cost you'd rather eliminate than manage - Your engineering team should be building your core product, not payment infrastructure Do nothing if: - You're comfortable with customers solving payments outside your platform - You don't mind the revenue leaking to third parties - You're not competing with platforms that have embedded payments Doing nothing is a valid choice. It just becomes less valid every quarter as more platforms ship native payment capabilities and your customers start asking why you haven't. Shuttle is the payment layer for voice, links, and embedded checkout. PCI DSS Level 1. 40+ PSPs. One integration. shuttleglobal.com ## Related Reading Explore More ### How Voice AI Ordering Platforms Handle Payments -- And Why It's Broken ### What Are Voice Payments? The Complete Guide ### How AI Voice Agents Take PCI-Compliant Payments ### AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk ### AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent ### AI Voice Payments for Debt Collection: Capture Payments at the Moment of Agreement ## Links - [Book a Call →](/discovery/) - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [GuideHow Voice AI Ordering Platforms Handle Payments -- And Why It's Broken→](/guides/voice-ai-ordering-payments/) - [GuideWhat Are Voice Payments? The Complete Guide→](/guides/voice-payments/) - [GuideHow AI Voice Agents Take PCI-Compliant Payments→](/guides/ai-voice-agent-pci-payments/) - [GuideAI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk→](/guides/ai-voice-payments-insurance/) - [GuideAI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent→](/guides/ai-voice-payments-hotels-travel/) - [GuideAI Voice Payments for Debt Collection: Capture Payments at the Moment of Agreement→](/guides/ai-voice-payments-debt-collection/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-a-merchant-account/ --- # What is a merchant account? | Shuttle > What is a merchant account and how does it work? Covers the difference between merchant accounts and payment service providers, fees, application process,... # What is a merchant account? By Nick Dunse, August 10, 2021 What is a merchant account and how does it work? Covers the difference between merchant accounts and payment service providers, fees, application process,... The Acquirer / Merchant account provider Looking from the point of purchase, the acquirer plays the critical role of holding the merchant account and receiving payments from a customer's bank. This comes with its own range of fees and terms, however, is typically defined by the specific features and rates desired by merchants. Different PSPs will often base their rates on merchant transaction volume, although merchants can negotiate bespoke agreements with their PSPs. Since the bigger margins are made by the acquirers this is typically where partnership deals are done, something that isn't really possible with incumbent, legacy players. Another deciding factor is the service for seasonal or other cyclical business models. Merchants might experience challenges communicating with larger PSPs, whereas a smaller PSP would be able to provide more specialized solutions. Saving Money with your PSP The trick to saving money with your PSP is to understand your needs and adjust accordingly. A large number of merchants simply don't know what options are out there, so they stay with large players, not knowing the opportunities offered by smaller competitors. Outside of simple education, actively communicating with PSPs will shine a light on options that aren't on their listed pages. A simple conversation could save you money every year. As the payments industry modernizes, we see some PSPs offering both acquiring and gateway services. This provides the advantage of centralized services for merchants, although, this can mean less flexibility than choosing two distinct service providers. When choosing a PSP, a merchant should know what they want to prioritize, be that customization/integration, rates or centralization. Merchants might see the perceived cost of overall services increase with the inclusion of gateway options. In reality, it eliminates the cost for an external gateway service and can in fact save money! Comparing PSPs with Shuttle If you're looking to find a better or cheaper service then we can consider your needs and help you compare the market for free. ## Related Reading Explore More ### Merchant Account Providers Compared: 12 Best Options for 2026 ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### Stripe Froze My Account: What to Do and How to Prevent It ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices ### Shuttle vs Prommt for Platforms and Merchants ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideMerchant Account Providers Compared: 12 Best Options for 2026→](/guides/merchant-account-providers/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideStripe Froze My Account: What to Do and How to Prevent It→](/guides/stripe-account-frozen/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuidePayment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices→](/guides/payment-collection-professional-services/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-a-payment-gateway/ --- # What Is a Payment Gateway? How It Works, Costs & Top Providers | Shuttle > A payment gateway securely captures card details and routes them to a processor for authorisation. # What Is a Payment Gateway? How It Works, Costs & Top Providers By Nick Dunse, August 9, 2022 A payment gateway securely captures card details and routes them to a processor for authorisation. Talk to us Make enabling payments for your platform and merchant users easy. A payment gateway is the technology that securely captures a customer's payment details and passes them to a payment processor for authorisation, then returns the approve-or-decline result to the merchant. It is the connective layer between a checkout and the card networks and banks behind it. Every time someone enters card details on a website, taps a phone at a terminal, or reads a card number to an agent over the phone, a payment gateway is encrypting and routing that data in the background. For any business accepting digital payments it is essential infrastructure: it protects sensitive card data, sends each transaction to the processor it is configured for, and enforces security standards like PCI DSS before money moves. This guide covers how payment gateways work, the main types, what they cost in 2026, how to evaluate one, and the infrastructure model platforms use to offer payments across many gateways at once. Shuttle connects software platforms to 40+ gateways, so the sections below reflect what matters in production, not just the textbook flow. ## How Does a Payment Gateway Work? A payment gateway runs in the background of every digital payment. The flow takes one to three seconds end to end: - Customer initiates payment. The buyer enters card details on a checkout page, taps a contactless terminal, or provides a card over the phone. - Gateway encrypts and tokenises the data. The gateway secures the card details in transit (TLS) and usually replaces the raw card number with a token, so sensitive data never sits on the merchant's servers. - Data goes to the processor. The encrypted request is forwarded to the payment processor (the acquirer), which talks to the relevant card network (Visa, Mastercard, Amex). - Card network contacts the issuing bank. The network routes the authorisation request to the customer's bank, which checks funds, fraud signals, and account status. - Authorisation response. The issuing bank returns an approval or decline back through the network, the processor, and the gateway to the merchant. - Settlement. If approved, the order is fulfilled and the funds settle to the merchant's account, typically within one to three business days. The gateway's job is specifically the secure capture, tokenisation, and transmission of payment data. It does not hold funds, run settlement, or maintain the banking relationships. That distinction is the source of most confusion in payments, which the next section clears up. ## Payment Gateway vs Payment Processor vs Merchant Account These three components are routinely confused because modern providers bundle them. They are not the same thing: What It Does Payment gateway Captures, tokenises and encrypts card data, then routes it to the processor Stripe, Braintree, Authorize.Net Payment processor Talks to card networks and issuing banks to authorise and settle Worldpay, Fiserv, Global Payments Merchant account The account where funds settle before reaching your business bank account Acquiring banks, or bundled by PSPs Modern payment service providers (PSPs) like Stripe and Adyen bundle all three into one integration, which is why people use "gateway" and "processor" interchangeably. Traditional setups contract each component separately, which gives more pricing control at the cost of more complexity. The practical point: when you compare providers you are usually comparing bundles, not gateways in isolation. What matters is the total cost and the flexibility the bundle gives you. ## Types of Payment Gateways Gateways come in three architectures. The right one depends on your engineering resources, the PCI scope you can accept, and the checkout experience you want. Hosted gateways redirect the customer to the provider's checkout page to enter card details. The provider carries PCI compliance and your site never touches card data. Examples: PayPal Standard, Stripe Checkout. Best when you want limited PCI scope and fast setup. Self-hosted (on-site) gateways keep the checkout on your own site and submit card data to the gateway by API. You control the full UI but you take on more PCI responsibility. Common for larger merchants with dedicated engineering. API-based gateways expose payment processing through REST APIs and client-side SDKs. The front end captures card data inside a secure iframe or tokenisation library (so raw numbers never reach your servers) and the back end completes the payment by API. This is the model most modern PSPs use, including Stripe, Adyen and Braintree. A fourth option matters for software platforms specifically: rather than integrating a gateway directly, you access one (or many) through a payment layer that abstracts the integration and adds white-label tooling. That model is the focus of the next section. ## Payment Gateway as a Service: The Infrastructure Model For a single business taking its own payments, one gateway integration is enough. For a software platform that needs to offer payments to its own customers, or for a high-volume merchant operating across markets, the unit of decision is no longer a single gateway. It is the infrastructure that sits across several of them. This is what "payment gateway as a service" and gateway-as-infrastructure describe: a layer that exposes payment acceptance to your application while managing the underlying gateway connections, tokens, compliance, and routing for you. Single-gateway vs multi-gateway. A single gateway is simple but fragile. If it has an outage, payments stop. If it lacks local acquiring in a market, approval rates fall. If a large customer mandates a specific PSP, you cannot serve them. A multi-gateway setup removes those single points of failure. Payment gateway routing. With more than one gateway connected, transactions can be routed by rule: send domestic cards to a local acquirer, switch to a backup gateway during an outage, or direct a specific merchant's volume to the PSP they are contracted with. This routing is the core of payment orchestration. Embedded and white-label. Platforms that want payments to feel native (their brand, their dashboard, their onboarding) embed the gateway rather than redirecting merchants off to a third party. A payment layer provides the checkout, payment links, and reporting under the platform's own brand while connecting to the gateways underneath. Why platforms choose this over building it. Connecting to one gateway is a few weeks of work. Connecting to many, keeping tokens portable across them, maintaining PCI scope, and keeping each integration current is a permanent engineering commitment. Most platforms would rather not become a payments company, so they consume gateway connectivity as infrastructure. We cover that trade-off in why platforms don't want to be payment companies. If you are evaluating this model, the deciding factors are usually the number of PSPs supported, whether tokens are portable across them, and whether the checkout can be fully white-labelled. ## How Much Does a Payment Gateway Cost in 2026? Gateway pricing depends on the provider, the pricing model, and your volume. The components to add up: Transaction fees are the main cost: a percentage of the amount plus a fixed fee. Typical 2026 UK rates: - Stripe: 1.5% + 20p (UK domestic cards), 2.5% + 20p (European cards) - PayPal: around 1.2% + 30p (standard UK checkout) - Worldpay: custom, volume-based (broadly 0.75% to 2.5%) - Adyen: interchange++ (interchange plus scheme fee plus a small per-transaction markup) Monthly fees apply to some gateways. Authorize.Net charges a monthly platform fee; many modern PSPs such as Stripe and Braintree charge none. Setup fees are now uncommon, but some traditional providers still charge them, from nothing up to several hundred pounds depending on integration complexity. Chargeback fees apply when a customer disputes a transaction, usually £15 to £25 per dispute regardless of outcome. Cross-border and currency fees add roughly 1% to 2% when the card's country differs from yours or currency conversion is involved. For most UK businesses on standard card payments, the all-in effective cost lands between 1.5% and 3.0% per transaction, driven mainly by the domestic-versus-international card mix and the pricing model. Above a certain volume interchange++ almost always beats flat-rate pricing, which is why scaling merchants move to it. ## Key Features to Look For These features separate a basic gateway from production-ready infrastructure: - PCI DSS compliance at Level 1 (the highest), which reduces your own compliance scope. - Tokenisation for repeat payments, subscriptions, and one-click checkout without re-entering card numbers. If you may switch providers later, ask whether tokens are portable. - Multi-currency support in the currencies your customers actually pay in. - Fraud detection: scoring, 3D Secure (SCA), and configurable risk rules. - Payment method breadth beyond cards: wallets (Apple Pay, Google Pay), bank transfers (SEPA, BACS), and the local methods your markets expect. - Recurring billing if you run subscriptions. - Developer experience: clear APIs, SDKs, sandboxes, and reliable webhooks. - Reporting and reconciliation: dashboards, settlement reports, and clean data exports. ## Top Payment Gateway Providers Compared Pricing Model Key Strength Developers, SaaS, platforms % + fixed per txn API quality, ecosystem Enterprise, global commerce Interchange++ Global acquiring, one platform UK/EU high-volume merchants Local acquiring, volume pricing Marketplaces, mobile apps PayPal integration, vault Small business, quick setup Brand trust, buyer reach In-person and online Flat rate per txn Omnichannel, hardware Checkout.com High-growth, enterprise Performance, flexibility % per txn, no monthly Simplicity, local methods No single provider wins on every axis, which is exactly why larger merchants and platforms abstract the choice behind a payment layer that connects to several at once and lets each merchant use the provider that fits them. You can see the full list of connected providers on the Shuttle PSP network. ## How to Choose a Payment Gateway Match the gateway to your stage and model rather than chasing the lowest headline rate: - Early-stage or low volume: prioritise speed and simplicity. A bundled PSP with flat-rate pricing and a hosted checkout gets you live fastest with limited PCI scope. - Scaling or high volume: move to interchange++ and look hard at local acquiring in your top markets. Basis points matter at volume. - International: check local acquiring and local payment method support market by market, not just headline currency coverage. - Enterprise or regulated buyers: expect PSP mandates in procurement. The ability to route to a specified gateway is often a deal requirement. - Software platforms: the decision is not which gateway, but which infrastructure lets your merchants use any gateway. See how to choose a payment platform for the full evaluation framework. ## How to Integrate a Payment Gateway The typical process for an API-based gateway: - Create a sandbox account and get test credentials (usually instant). - Install the SDK or API client (server-side SDKs for Node, Python, PHP, Ruby, Java, plus client-side libraries). - Build the client-side form with hosted fields or a secure iframe so raw card numbers never touch your server. - Build the server-side flow: endpoints that take the tokenised card data, create the charge or payment intent, and handle the response. - Handle 3D Secure / SCA for European transactions using the provider's 3DS libraries. - Set up webhooks for charges, failures, disputes, and refunds. - Test thoroughly with the provider's test cards, including declines, 3DS challenges, and refunds. - Go live on production credentials and watch the first live transactions closely. A basic integration takes a developer one to two days. A production-ready one with full error handling, retries, and webhook processing is usually one to two weeks per gateway. That per-gateway cost is why platforms supporting multiple merchants tend to consume gateway connectivity as a single integration across many PSPs rather than building each one. ## Frequently Asked Questions Is a payment gateway the same as a payment processor? No. A gateway captures and encrypts card data and routes it to a processor. A processor talks to card networks and banks to authorise and settle. Modern PSPs like Stripe and Adyen bundle both, which is why the terms get conflated. Do I need a payment gateway for my website? Yes, to accept card payments online. The gateway is what securely transmits card data between your checkout and the processor. Without one you cannot take digital card payments. What is payment gateway as a service? It is consuming gateway connectivity as managed infrastructure rather than integrating a gateway yourself. The service provides payment acceptance to your application while handling the underlying gateway connections, tokens, compliance, and routing. Platforms use this to offer payments to their own customers without becoming a payments company. What is payment gateway routing? Provider selection is set by rule: a local acquirer for domestic cards, a different provider for a merchant contracted to it, and a switch you can make during an outage. It requires more than one connected gateway and is the core of payment orchestration. How long does it take to set up a payment gateway? With a modern PSP, a basic integration can run in a few hours. A production-ready setup with error handling, webhooks, and testing typically takes one to two weeks per gateway. What is the cheapest payment gateway? It depends on volume and transaction profile. For low volume, flat-rate providers like Stripe are simplest. For high volume, interchange++ from Adyen or Worldpay is usually cheaper per transaction. Can I use multiple payment gateways? Yes. Businesses run multiple gateways for redundancy, cost routing, and geographic coverage. Managing them through one integration is called payment orchestration or multi-PSP routing. What is the difference between a payment gateway and a payment link? A gateway processes payments through a checkout integrated into your site. A payment link is a hosted page you send by email, SMS, or chat, where the customer pays without any site integration. Payment links use a gateway behind the scenes. *Building payments into a software platform? Shuttle connects platforms to 40+ payment gateways through one integration, with white-label checkout, payment links, and voice payments included. See how it works or book a discovery call.* ## Related Reading Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment service providers (PSPs)](/payment-providers/) - [payment layer](/guides/what-is-embedded-payments/) - [payment orchestration](/guides/what-is-payment-orchestration/) - [why platforms don't want to be payment companies](/blog/why-platforms-dont-want-to-be-payment-companies/) - [local methods](/guides/take-payments-online/) - [Shuttle PSP network](/payment-providers/) - [how to choose a payment platform](/guides/how-to-choose-payment-platform/) - [single integration across many PSPs](/guides/what-is-embedded-payments/) - [payment link](/guides/take-payments-online/payment-links/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-chargeback-fraud-and-how-merchants-can-avoid-it/ --- # What is chargeback fraud and how merchants can avoid it | Shuttle > What is chargeback fraud, how it impacts merchants, and practical steps to prevent friendly fraud and dispute losses. # What is chargeback fraud and how merchants can avoid it By Nick Dunse, April 13, 2023 What is chargeback fraud, how it impacts merchants, and practical steps to prevent friendly fraud and dispute losses. Talk to us Make enabling payments for your platform and merchant users easy. 1. Introduction to Chargeback Fraud Chargeback fraud occurs when a customer disputes a charge on their credit or debit card and requests a refund from their bank, despite having already received the product or service they paid for. This type of fraud can have serious consequences for merchants, who may be left with a financial loss and damage to their reputation. In this article, we will explore the different types of chargeback fraud and how merchants can protect themselves from these fraudulent claims. 2. Types of Chargeback Fraud Chargeback fraud refers to illegal activities where scammers use stolen credit card numbers to make purchases, then request a chargeback from the issuer to get their money back. There are several types of chargeback fraud, including friendly fraud, criminal fraud, and merchant fraud. Friendly fraud occurs when a customer initiates a chargeback despite having received the product or service they paid for. Criminal fraud involves the use of stolen credit card information to make purchases, while merchant fraud involves merchants intentionally submitting false chargeback claims. It's important for merchants to understand the different types of chargeback fraud in order to protect themselves and their customers. 3. Common Scenarios Leading to Chargebacks Chargebacks are a common issue faced by merchants, and there are several scenarios that can lead to them. Understanding these scenarios is crucial for merchants to take steps to prevent chargebacks from occurring. Here are some of the most common scenarios leading to chargebacks: 1. Unauthorized Charges: When a customer disputes a charge on their credit card statement, they may claim that the transaction was unauthorized. This can happen when a merchant processes a payment without the customer's knowledge or consent, such as when a customer accidentally clicks "pay" during a trial period or when a merchant enters the wrong billing information. 2. Duplicate Charges: Customers may dispute charges if they believe they have been charged twice for the same item or service. This can occur when a merchant accidentally charges the same customer twice, or when a customer's account is charged multiple times due to a technical error. 3. Shipping Issues: Disputes over shipping charges are another common reason for chargebacks. If a customer believes that they were overcharged for shipping, they may request a refund or chargeback. 4. Product Not Received: Customers may request a chargeback if they never received the product they paid for. This can happen when a merchant fails to ship an order or ships the wrong item. 5. Product Not as Described: Customers may dispute charges if they believe that the product they received did not match the description provided by the merchant. This can occur when a merchant misrepresents the product or its features. 6. Expired Cards: Customers may request a chargeback if they discover that their credit card has expired and the merchant processed the transaction anyway. To avoid chargebacks, merchants should implement policies and procedures to minimize the risk of unauthorized charges, duplicate charges, shipping issues, products not received, and products not as described. Additionally, using technology solutions such as fraud detection tools and chargeback protection services can help merchants identify and prevent chargebacks before they occur. 4. The Impact of Chargebacks on Merchants Chargebacks can have a significant impact on merchants, both financially and reputationally. When a customer initiates a chargeback, the merchant loses the money they were expecting to receive from the sale, as well as any associated fees. This can result in lost revenue and decreased profitability for the merchant. In addition, chargebacks can damage a merchant's reputation, making it harder for them to attract new customers and maintain relationships with existing ones. Furthermore, repeated chargebacks can lead to the merchant being placed on blacklists, which can prevent them from processing transactions through certain payment processors. As a result, it is crucial for merchants to take steps to prevent chargebacks and protect their business. 5. How Chargebacks Happen Chargebacks occur when a customer disputes a transaction with their issuing bank, usually due to unauthorized charges or products not received. The process begins when the customer contacts their bank and reports the issue. The bank then initiates a chargeback request, which the merchant must respond to within a specific time frame. If the merchant fails to provide adequate evidence of the transaction or prove that the product was delivered, the bank will side with the customer, and the funds will be returned to them. This process can result in lost revenue and damaged reputation for the merchant. To prevent chargebacks, merchants should ensure they have a clear and transparent refund policy, accurately represent the product being sold, and provide tracking information for shipments. 6. The Role of Banks in Chargebacks Banks play a crucial role in the chargeback process. When a customer disputes a charge, they must first contact their bank to initiate the dispute. The bank then investigates the claim and determines whether or not the transaction was authorized by the customer. If the bank determines that the transaction was unauthorized, it will issue a refund to the customer and initiate a chargeback against the merchant. This means that the merchant will have to repay the amount of the transaction to the bank, which can result in significant financial losses for the merchant. As such, it is important for merchants to understand the role of banks in the chargeback process and take steps to prevent chargebacks from occurring in the first place. 7. How Merchants Can Reduce Chargebacks Merchants can take several steps to reduce the risk of chargeback fraud and protect their business from financial loss. Here are some strategies that merchants can implement: 1. Implement clear and concise refund policies: Providing clear and transparent refund policies can help prevent customer confusion and disputes, which can lead to chargebacks. 2. Use secure payment processing systems: Choosing a reputable payment processor with robust security measures can help minimize the risk of fraudulent transactions and chargebacks. 3. Verify customer information: Double-checking the accuracy of customer information, such as billing address and phone number, can help identify potential fraud and prevent chargebacks. 4. Monitor transaction activity: Regularly reviewing transaction activity and promptly addressing any suspicious behavior can help detect and prevent chargebacks before they occur. 5. Communicate effectively with customers: Keeping open lines of communication with customers and addressing their concerns promptly can help prevent misunderstandings and disputes that may lead to chargebacks. 6. Offer flexible return policies: Allowing customers to return or exchange products within a reasonable timeframe can help reduce the likelihood of chargebacks due to dissatisfaction with a product or service. 7. Participate in chargeback prevention programs: Some payment processors offer chargeback prevention programs that provide additional support and resources to merchants to help them reduce the risk of chargebacks. 8. Strategies for Preventing Chargeback Fraud There are several strategies that merchants can implement to prevent chargeback fraud. Here are some effective ones: 1. Implement a clear refund policy: Having a clear and concise refund policy can help reduce disputes and chargebacks. Be sure to include details such as the timeframe for requesting a refund, the types of items eligible for a refund, and any conditions that apply. 2. Monitor transactions closely: Regularly review transaction activity and flag any suspicious behavior. This includes monitoring for large transactions, multiple transactions from the same customer, or transactions made using stolen credit card information. 3. Verify customer information: Double-check the information provided by customers during the checkout process. This includes verifying the billing address, phone number, and email address. 4. Provide excellent customer service: Respond promptly to customer inquiries and resolve issues quickly. This can help build trust with customers and reduce the likelihood of chargebacks. 5. Use fraud detection tools: Utilize tools such as fraud screeners and address verification systems (AVS) to identify potentially fraudulent transactions. 6. Partner with reputable payment processors: Choose a payment processor that offers advanced fraud protection tools and has a proven track record of reducing chargebacks. 7. Offer flexible payment options: Allow customers to pay using various methods, including credit cards, debit cards, and alternative payment methods like PayPal. This can help reduce the risk of chargebacks associated with specific payment methods. 8. Educate employees: Train employees on chargeback fraud and how to spot it. This can help identify potential fraud before it leads to a chargeback. 9. Technology Solutions for Chargeback Protection In this section, we will explore the various technology solutions available to merchants to protect themselves from chargeback fraud. These solutions range from payment gateways and fraud detection tools to advanced machine learning algorithms. By utilizing these technologies, merchants can significantly reduce their exposure to chargebacks and improve their overall profitability. 10. Conclusion In conclusion, chargeback fraud can have serious consequences for merchants, including financial losses and damage to their reputation. However, there are steps that merchants can take to reduce the risk of chargebacks and protect themselves from this type of fraud. By implementing strong anti-fraud measures, using technology solutions, and staying informed about industry trends and best practices, merchants can minimize their exposure to chargeback fraud and ensure the long-term success of their businesses. It is important for merchants to take charge of their payment processing security and prioritize the protection of their customers' sensitive information. With the right strategies and tools, merchants can safeguard their businesses against chargeback fraud and maintain the trust of their customers. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ### How to Avoid Payment Provider Lock-In: A Platform Guide ### How to Add Payments to Replicant AI: Voice Agent Payment Integration ### Shuttle vs Prommt for Platforms and Merchants ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [GuideHow to Avoid Payment Provider Lock-In: A Platform Guide→](/guides/payment-provider-lock-in/) - [GuideHow to Add Payments to Replicant AI: Voice Agent Payment Integration→](/guides/replicant-payments/) - [ComparisonShuttle vs Prommt for Platforms and Merchants→](/vs/prommt/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-open-banking-and-aisp/ --- # What Is an AISP? Open Banking Account Information Explained | Shuttle > What is an AISP (Account Information Service Provider)? How AISPs work under Open Banking, the difference from PISPs, real examples, and why AISP services... # What Is an AISP? Open Banking Account Information Explained By Nick Dunse, July 22, 2021 What is an AISP (Account Information Service Provider)? How AISPs work under Open Banking, the difference from PISPs, real examples, and why AISP services... Talk to us Make enabling payments for your platform and merchant users easy. An AISP (Account Information Service Provider) is a regulated entity that can access a customer's bank account data -- with their explicit consent -- and present it in a useful way. AISPs are one of the two core third-party provider types created by Open Banking regulation in the UK and PSD2 in Europe. The other is the PISP (Payment Initiation Service Provider), which can initiate payments but cannot read account data. If you have ever connected a bank account to a budgeting app, had a lender verify your income digitally, or used an accounting tool that pulls in transactions automatically -- you have used an AISP service. This guide covers exactly what AISPs are, how the data flow works, who the major AISP companies are, how AISPs differ from PISPs, and the regulatory framework that makes it all possible. ## What Is an AISP? AISP stands for Account Information Service Provider. It is a type of third-party provider (TPP) authorised under the Payment Services Directive 2 (PSD2) in Europe and the Open Banking framework in the UK. An AISP has the legal and technical ability to access a customer's bank account information -- balances, transaction history, and account details -- through secure APIs provided by the customer's bank. In practical terms, an AISP connects to one or more of a customer's bank accounts, reads the data, and aggregates or analyses it. The customer must give explicit consent before any data is accessed, and that consent is typically renewed every 90 days. The AISP can only read data -- it cannot move money, make payments, or modify the account in any way. The key distinction: an AISP is read-only. It can see your balances and transactions, but it cannot spend a single penny. This is what separates it from a PISP, which has write access to initiate payments. ### AISP Meaning in Simple Terms Think of an AISP as a secure, regulated window into your bank account. Before Open Banking, only your bank could see your transaction data. If you wanted to share financial information with a mortgage broker, a budgeting app, or an accountant, you had to download PDF statements, share login credentials (a practice called screen scraping), or manually re-enter data. None of these methods were secure, standardised, or real-time. PSD2 changed that. It required banks (known as ASPSPs -- Account Servicing Payment Service Providers) to open up secure APIs so that authorised third parties like AISPs could access account information on behalf of customers. The customer stays in control at all times: they choose which accounts to share, with which provider, and can revoke access whenever they want. In short: an AISP is a regulated, API-powered way for a third party to read your bank data -- with your permission -- so it can provide a useful service on top of that data. ## How AISPs Work The technical flow behind an AISP service follows a standardised consent-and-access model defined by Open Banking standards. Here is how it works step by step: Step 1: The customer initiates a connection. The user opens an app or service powered by an AISP (for example, a budgeting tool) and chooses to link their bank account. They select their bank from a list of supported institutions. Step 2: The customer authenticates with their bank. The customer is redirected to their bank's authentication flow. This typically involves logging in to their online banking portal or mobile app and approving the data-sharing request. This is known as Strong Customer Authentication (SCA) -- the same two-factor verification used for online banking. Step 3: The bank issues an access token. Once the customer approves, the bank generates a secure access token. This token allows the AISP to call the bank's Open Banking API and retrieve the agreed data -- typically account balances and transaction history. The token is time-limited (usually 90 days) and scoped to the specific data the customer consented to share. Step 4: The AISP retrieves and processes the data. The AISP calls the bank's API using the access token and receives structured data: account name, sort code, balance, and a list of recent transactions. The AISP then processes this data according to its use case -- categorising transactions, calculating spending patterns, verifying income, or populating an accounting ledger. Step 5: Ongoing access with re-consent. Under PSD2 rules, an AISP can continue accessing data for up to 90 days before the customer must re-authenticate. Some implementations request longer-lived consent through variable recurring consents (VRPs) or rely on the customer re-authenticating periodically within the app. At no point does the AISP receive the customer's banking login credentials. The entire flow uses OAuth 2.0-based redirection, meaning the credentials stay with the bank. The AISP only ever sees an access token and the account data it was authorised to read. ## AISP vs PISP: What's the Difference? AISPs and PISPs are the two third-party provider types defined under PSD2 and Open Banking. They are often discussed together because they were introduced by the same regulation, but they do fundamentally different things: - AISP = read access. An AISP can view account balances, transaction history, and account holder details. It cannot move money. - PISP = write access. A PISP can initiate a payment from the customer's bank account to a merchant. It cannot read transaction history or account balances beyond what is needed to complete the payment. Here is a direct comparison: - Permission type: AISP has read-only access to account data. PISP has write access to initiate payments. - Data accessed: AISP sees balances, transactions, and account details. PISP sees only what is necessary to initiate and confirm a payment. - Money movement: AISP cannot move money. PISP initiates bank-to-bank transfers. - Consent duration: AISP consent lasts up to 90 days and can be renewed. PISP consent is typically one-time per payment. - Primary use case: AISP powers account aggregation, budgeting, and data verification. PISP powers direct bank payments at checkout. - Regulation: Both require FCA authorisation in the UK and national competent authority registration in the EU under PSD2. For a deep dive on how PISPs work and who the major players are, see our companion guide: What Is a PISP? Open Banking Payment Initiation Explained. ### Can a Company Be Both AISP and PISP? Yes. Many Open Banking providers hold both AISP and PISP authorisations. Companies like TrueLayer, Yapily, and Token.io are registered as both, which allows them to offer end-to-end services: they can verify a customer's account details (AISP) and then initiate a payment from that account (PISP) in a single flow. This dual registration is increasingly common because many commercial use cases require both capabilities. For example, a lending platform might use AISP access to verify an applicant's income and spending, and then use PISP access to collect loan repayments directly from their bank account -- all through the same Open Banking provider. ## AISP Examples The AISP ecosystem includes both infrastructure providers (companies that offer AISP APIs to other businesses) and consumer-facing services (apps that use AISP access to deliver products directly to end users). Here are the most notable players in each category. ### Platform AISPs (Infrastructure) These companies provide AISP connectivity as an API service. They handle the bank integrations, consent management, and data normalisation so that other businesses can build Open Banking features without connecting to each bank individually. - Plaid -- the largest account data platform globally. Originally US-focused (using screen scraping), Plaid expanded into the UK and EU with native Open Banking AISP connectivity. Used by thousands of fintechs for account linking, identity verification, and transaction data. - TrueLayer -- a UK-headquartered Open Banking platform with both AISP and PISP authorisation. Provides account data APIs alongside payment initiation, making it one of the most complete Open Banking infrastructure providers in Europe. - Tink (Visa) -- acquired by Visa in 2022 for €1.8 billion. Tink connects to over 3,400 banks across Europe and provides AISP data services alongside payment initiation and personal finance tools. Formerly the technology behind Yolt (now discontinued as a consumer app). - Yapily -- a developer-focused Open Banking API platform covering the UK, EU, and select global markets. Provides both AISP and PISP capabilities with a strong emphasis on raw API access and flexibility for technical teams. - Moneyhub -- a UK-based Open Banking and Open Finance platform. Provides AISP data aggregation alongside financial wellness tools, pension dashboards, and wealth management APIs. Used by financial advisers, employers, and fintech apps. ### Consumer-Facing AISP Services These are apps and services that use AISP access to deliver products directly to consumers. Rather than offering APIs, they present account data through their own user interfaces. - Snoop -- a UK personal finance app that connects to bank accounts via Open Banking and analyses spending to suggest money-saving switches (energy, broadband, insurance). Uses AISP access to categorise transactions and identify savings opportunities. - Emma -- a budgeting and financial tracking app that aggregates accounts from multiple banks. Uses AISP connectivity to give users a single view of their finances, track subscriptions, and set budgets. - Money Dashboard -- one of the original UK account aggregation services, now powered by Open Banking. Provides a consolidated view of bank accounts, credit cards, savings, and investments in a single dashboard. - Credit Kudos (Apple) -- acquired by Apple in 2022. Credit Kudos used AISP data to build alternative credit scores based on actual bank transaction patterns rather than traditional credit bureau data. This approach gave a more accurate picture of affordability for lenders. ## AISP Use Cases AISP access underpins a wide and growing range of financial services. Here are the most significant use cases in 2026: Personal finance management. Budgeting and spending apps use AISP data to aggregate accounts from multiple banks into a single view. Users can see all their balances, track spending by category, identify recurring subscriptions, and set savings goals. This was the original and most visible AISP use case. Lending and affordability checks. Lenders use AISP access to verify income and assess affordability in real time. Instead of relying on payslips, self-reported income, or credit bureau scores (which can be weeks out of date), a lender can pull 3-6 months of transaction data directly from the applicant's bank account. This gives a far more accurate picture of income stability, regular outgoings, and gambling or high-risk spending patterns. Account verification and onboarding. Businesses use AISP data to verify that a customer owns a particular bank account before setting up direct debits, payroll, or payouts. The AISP confirms the account holder name, sort code, and account number match -- reducing fraud and failed payments. This is sometimes called "confirmation of payee" or "account ownership verification." Accounting and reconciliation. Accounting software (Xero, FreeAgent, QuickBooks) uses AISP feeds to pull in bank transactions automatically. This replaces manual CSV imports and means that small businesses can reconcile their books in near real-time. It also reduces errors from manual data entry and speeds up month-end close. Debt advice and financial wellness. Debt charities and financial wellness platforms use AISP access to build a complete picture of a client's financial situation. Organisations like StepChange use Open Banking data to automate income-and-expenditure assessments, making it faster and less stressful for people seeking debt advice. Insurance and switching. Some insurance and comparison platforms use AISP data to identify what products a customer already pays for (energy, broadband, subscriptions) and suggest cheaper alternatives. Snoop is a prominent example of this switching model. The common thread across all these use cases: AISP access replaces manual, slow, and error-prone ways of sharing financial data with a secure, real-time, and standardised API-based approach. For businesses building payment and financial infrastructure, understanding where AISP data fits is increasingly important. If you are evaluating how payments and data services integrate within a broader platform, our guide to payment orchestration covers how different payment capabilities are coordinated at scale. ## AISP Regulation: PSD2 and FCA AISPs operate within a well-defined regulatory framework. The specifics depend on whether the AISP operates in the UK, the EU, or both -- but the core principles are the same. PSD2 (EU). The revised Payment Services Directive, which came into force in January 2018, is the legislation that created the AISP and PISP categories. PSD2 requires banks (ASPSPs) to provide secure APIs that allow authorised third parties to access account data (with customer consent). AISPs must be authorised or registered with their national competent authority -- for example, the BaFin in Germany, the ACPR in France, or De Nederlandsche Bank in the Netherlands. PSD3 and PSR (EU, upcoming). The European Commission published proposals for PSD3 and the Payment Services Regulation (PSR) in 2023, expected to be finalised in 2025-2026. Key changes for AISPs include: stronger data-sharing obligations on banks, clearer liability frameworks, and an extension of Open Banking principles toward Open Finance (covering savings, pensions, insurance, and investments -- not just payment accounts). Open Banking (UK). The UK implemented PSD2 through its own legislation and went further with the Open Banking Implementation Entity (OBIE), which mandated a common API standard for the nine largest UK banks (the CMA9). AISPs in the UK must be authorised or registered with the FCA (Financial Conduct Authority). The FCA maintains a public register where consumers and businesses can verify that a company is genuinely authorised as an AISP. Key regulatory requirements for AISPs: - Explicit consent. The customer must actively consent to their data being accessed. Consent must be informed, specific, and revocable. - Strong Customer Authentication (SCA). The customer must authenticate with their bank using at least two of three factors: something they know (password), something they have (phone), or something they are (biometrics). - 90-day re-authentication. Under current PSD2 rules, AISP access tokens expire after 90 days and the customer must re-authenticate. This is one of the most-discussed friction points in the industry. - Data minimisation. AISPs can only access data that is necessary for the service they provide. They cannot harvest or store data beyond what the customer has consented to. - GDPR compliance. Because AISPs process personal financial data, they must comply with GDPR (or the UK equivalent, UK GDPR). This includes data subject rights, breach notification, and lawful basis for processing. - Professional indemnity insurance. AISPs must hold professional indemnity insurance or a comparable guarantee to cover their liability in case of unauthorised or fraudulent data access. ## Limitations of AISP Services Despite significant growth, AISP services still face practical limitations: The 90-day re-consent requirement. Under PSD2, customers must re-authenticate every 90 days to maintain AISP access. This creates friction and drop-off -- users forget to re-consent, apps lose their data connection, and the service degrades. PSD3 proposals aim to relax this requirement, but it remains a significant pain point today. Inconsistent bank API quality. Not all banks implement Open Banking APIs to the same standard. Some return limited transaction categories, inconsistent date formats, or incomplete merchant names. This makes it harder for AISPs to normalise data across banks and deliver a consistent experience. The CMA9 in the UK generally offer better API quality than many smaller banks and building societies. Limited account coverage. Open Banking mandates currently cover payment accounts (current accounts and some savings accounts). They do not cover mortgages, pensions, investments, or insurance products. The move toward Open Finance aims to extend data-sharing to these categories, but adoption is still early and varies by market. Consumer awareness and trust. Many consumers still do not understand what Open Banking is or are reluctant to grant third-party access to their bank data. A 2024 survey by the Open Banking Implementation Entity found that while usage is growing (over 10 million users in the UK), many people are still uncomfortable with the concept. Clear consent journeys and trusted branding are essential. Read-only by design. An AISP cannot move money. If a service needs to both view account data and initiate payments, it must hold separate PISP authorisation -- or partner with a PISP provider. This adds complexity for businesses building end-to-end financial products. ## Frequently Asked Questions ### Is my bank an AISP? No. Your bank is an ASPSP (Account Servicing Payment Service Provider) -- the institution that holds your account and provides the APIs that AISPs connect to. An AISP is a separate, third-party company that has been authorised by a regulator (such as the FCA in the UK) to access your bank data through those APIs. Your bank provides the data; the AISP reads it. Some banks do also operate AISP services for their own customers (for example, showing balances from other banks within their app), but this is a separate function from their core banking role. ### Can an AISP access my bank account without permission? No. An AISP can only access your bank data after you have explicitly consented. The consent process requires you to authenticate directly with your bank (using your normal banking login and any additional security like biometrics or one-time codes). Your bank will clearly show you which data the AISP is requesting and ask you to approve. You can revoke consent at any time -- either through the AISP's app or directly through your bank's Open Banking settings. ### What data can an AISP see? An AISP can typically see: your account holder name, account number and sort code, account balance (available and current), and transaction history (including dates, amounts, merchant names, and sometimes categories). An AISP cannot see your banking login credentials, your PIN, your card number, or any data from accounts you have not explicitly consented to share. The data is also limited to what is necessary for the service -- an AISP cannot request blanket access to everything. ### Are AISPs safe? AISPs that are properly authorised or registered with a regulator (such as the FCA) are subject to strict security and data protection requirements. They must use encrypted connections, comply with GDPR, hold professional indemnity insurance, and pass ongoing regulatory scrutiny. The key safety check is to verify that the company is listed on the FCA register (or equivalent regulator) before granting access. If a company claims to be an AISP but is not on the register, do not proceed. Legitimate AISPs never ask for your banking password -- the authentication always happens directly with your bank. AISPs are a foundational component of Open Banking -- and as the ecosystem evolves toward Open Finance, the range of data they can access and the services they can power will only grow. Whether you are a platform evaluating how account data fits into your product, or a business exploring the broader payments landscape, understanding AISPs is essential context. For the payment side of Open Banking, read our companion guide on PISPs (Payment Initiation Service Providers). To understand how modern platforms manage multiple payment methods and providers, see our guide to payment orchestration. And if you are building payment capabilities into a platform and want to see how the payment layer approach works, book a discovery call with the Shuttle team. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [PISP (Payment Initiation Service Provider)](/blog/what-is-open-banking-and-pisp/) - [PISPs](/blog/what-is-open-banking-and-pisp/) - [What Is a PISP? Open Banking Payment Initiation Explained](/blog/what-is-open-banking-and-pisp/) - [payment orchestration](/guides/what-is-payment-orchestration/) - [PISPs (Payment Initiation Service Providers)](/blog/what-is-open-banking-and-pisp/) - [book a discovery call](/discovery/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-open-banking-and-pisp/ --- # What Is a PISP? Open Banking Payment Initiation Explained | Shuttle > What is a PISP (Payment Initiation Service Provider)? How PISPs work under Open Banking, the difference from AISPs, real examples, and why PISP payments... # What Is a PISP? Open Banking Payment Initiation Explained By Nick Dunse, March 1, 2022 What is a PISP (Payment Initiation Service Provider)? How PISPs work under Open Banking, the difference from AISPs, real examples, and why PISP payments... Talk to us Make enabling payments for your platform and merchant users easy. A PISP (Payment Initiation Service Provider) is a regulated entity that can initiate a payment directly from a customer's bank account on behalf of a merchant. PISPs are one of the two core third-party provider types created by Open Banking regulation in the UK and PSD2 in Europe. The other is the AISP (Account Information Service Provider), which can read account data but cannot move money. If you have ever paid for something online and been redirected to your banking app to approve the payment -- rather than entering card details -- you have almost certainly used a PISP. This guide covers exactly what PISPs are, how the payment flow works, who the major PISP companies are, and where PISP payments fit in the broader payments landscape. ## What Is a PISP? PISP stands for Payment Initiation Service Provider. It is a type of third-party provider (TPP) authorised under the Payment Services Directive 2 (PSD2) in Europe and the Open Banking framework in the UK. A PISP has the legal and technical ability to initiate a payment from a consumer's bank account -- with the consumer's explicit consent -- and send it directly to a merchant or payee. In practical terms, a PISP sits between the customer and their bank. Instead of the customer logging into their banking app, finding the merchant's account details, and manually sending a bank transfer, the PISP handles the entire flow. The customer simply authenticates (usually via their banking app or biometrics), confirms the amount and recipient, and the payment is initiated instantly. The key distinction: the PISP never holds the funds. Money moves directly from the customer's bank account to the merchant's bank account. The PISP is an initiator, not an intermediary. ### PISP Meaning in Simple Terms Think of a PISP as a secure, regulated bridge between the "pay now" button on a checkout page and the customer's bank. Before Open Banking, the only entities allowed to interact with a bank account were the bank itself and the account holder. PSD2 changed that. It required banks (known as ASPSPs -- Account Servicing Payment Service Providers) to open up secure APIs so that authorised third parties like PISPs could initiate payments on behalf of customers. This was a deliberate regulatory move to increase competition, reduce reliance on card networks, and give consumers more control over how they pay. ## How PISP Payments Work A PISP payment follows a specific technical flow. Understanding this flow is important because it explains why PISP payments are faster, cheaper, and more secure than traditional card payments. ### Step-by-Step PISP Payment Flow Here is how a typical PISP payment works from start to finish: - 1. Customer selects "Pay by Bank" at checkout. The merchant's checkout page presents bank payment as an option alongside card payment. The customer chooses to pay directly from their bank account. - 2. Customer selects their bank. The PISP presents a list of supported banks (e.g. Barclays, HSBC, Lloyds, Revolut). The customer picks theirs. - 3. PISP sends a payment initiation request to the bank (ASPSP). Via the bank's Open Banking API, the PISP sends the payment amount, merchant details, and a unique reference. This is a server-to-server API call. - 4. Customer authenticates with their bank (SCA). The customer is redirected to their banking app or online banking portal. They authenticate using Strong Customer Authentication (SCA) -- typically biometrics, a PIN, or a one-time passcode. - 5. Customer confirms the payment. The banking app shows the exact amount and recipient. The customer taps to confirm. - 6. Bank executes the payment. The bank (ASPSP) processes the payment via the Faster Payments scheme (in the UK) or SEPA Instant (in the EU). Funds arrive in the merchant's account within seconds. - 7. PISP confirms payment status to the merchant. The merchant receives a webhook or callback confirming the payment was successful. The customer is redirected back to the merchant's confirmation page. The entire process typically takes under 15 seconds. No card numbers are entered, no card network is involved, and the merchant receives the funds almost immediately -- compared to the 1-3 business day settlement window typical of card payments. ## PISP vs AISP: What's the Difference? PSD2 and Open Banking created two types of third-party providers. They serve fundamentally different purposes, and a company can hold one or both licences. PISP (Payment Initiation Service Provider) -- Can initiate payments from a customer's bank account. Used for checkout, bill payment, and account-to-account transfers. The PISP writes to the bank account (it sends a payment instruction). AISP (Account Information Service Provider) -- Can read account data (balances, transaction history) with the customer's consent. Used for personal finance management, credit scoring, affordability checks, and account aggregation. The AISP reads from the bank account but cannot move money. A useful analogy: a PISP has the key to send payments out of your account (with your permission each time). An AISP has a window to view your account balance and transactions (with your ongoing consent). Many Open Banking companies hold both licences -- for example, TrueLayer and Plaid operate as both PISP and AISP. ### When Would You Use an AISP vs a PISP? - AISP use cases: Bank account verification for onboarding, income verification for lending, personal finance dashboards (like Emma or Plum), and affordability assessments. - PISP use cases: E-commerce checkout ("pay by bank"), invoice payments, subscription billing, payroll disbursements, and any scenario where you need to collect or send a payment without cards. ## PISP Examples: Companies and Platforms The PISP landscape has matured significantly since PSD2 came into force. Here are the major PISP companies operating today, along with what they do: ### Infrastructure PISPs (APIs for Developers) - TrueLayer -- One of the largest European Open Banking platforms. Provides PISP and AISP APIs. Used by Revolut, Wise, and thousands of merchants for instant bank payments. FCA-regulated. - Yapily -- Connectivity-focused Open Banking infrastructure. Connects to 2,000+ banks across Europe. Offers payment initiation and data APIs. Used by American Express, Intuit, and Volvo Financial Services. - Token.io -- Enterprise-grade PISP infrastructure. Powers HSBC's PayMe and other large bank integrations. Covers 6,000+ banks and offers multi-rail payment initiation across SEPA, Faster Payments, and other schemes. - Plaid -- Originally a US-focused AISP (account aggregation), Plaid expanded into payment initiation in the UK and EU. Now offers both PISP and AISP capabilities. - Volt -- A global real-time payments network built on Open Banking. Operates as a PISP with coverage across Europe, UK, Brazil, and Australia. Focused on e-commerce and gaming merchants. ### Consumer-Facing Services Powered by PISPs - Trustly -- One of the pioneers in account-to-account payments. Trustly processes PISP payments for e-commerce, financial services, and iGaming across Europe and North America. - GoCardless -- Traditionally a Direct Debit provider, GoCardless now offers Instant Bank Pay powered by Open Banking PISP rails. Used for invoicing and subscription collection. - Banked -- A PISP focused on checkout payments. Powers "pay by bank" at merchants including the Premier League (for ticket purchases). Direct bank-to-bank payments at checkout. It is worth noting that many traditional payment service providers (PSPs) and payment gateways are now integrating PISP capabilities into their offerings -- either by building their own Open Banking connections or partnering with the infrastructure PISPs listed above. ## Benefits of PISP Payments PISP payments offer significant advantages over traditional card-based payments, both for merchants and consumers. These benefits are structural -- they stem from the fact that PISP payments bypass card networks entirely. ### For Merchants - Lower transaction fees. Card payments typically cost 1.5-3% per transaction (interchange + scheme fees + acquirer margin). PISP payments usually cost a flat fee or a much lower percentage -- often 0.1-0.5% -- because there is no card network in the middle. - Instant settlement. Card payments settle in 1-3 business days (sometimes longer). PISP payments via Faster Payments settle within seconds. The merchant has the money immediately, improving cash flow. - No chargebacks. Card payments carry chargeback risk -- the customer can dispute the charge and the card network reverses the funds. PISP payments are irrevocable once authenticated. The customer explicitly confirmed the payment in their banking app. - No card data to handle. Because no card numbers are entered, the merchant has no PCI DSS scope for these transactions. This eliminates the cost and complexity of card data security compliance. - Higher payment success rates for high-value transactions. Card payments frequently fail for large amounts due to fraud checks and credit limits. Bank payments authenticate directly with the customer's bank, so success rates are typically higher for large-ticket items. ### For Consumers - No need to enter card details. The customer authenticates with their banking app. No card numbers, expiry dates, or CVVs to type in -- reducing friction and eliminating the risk of card details being stolen. - Payment comes directly from bank balance. For consumers who prefer to pay from available funds rather than credit, PISP payments offer a direct debit-like experience without the delayed collection timeline. - Bank-grade security. Authentication happens within the customer's own banking app using the same biometrics or credentials they already trust. The PISP never sees the customer's banking credentials. ## PISP Regulation: PSD2, FCA, and Open Banking PISPs do not operate in a regulatory grey area. They are among the most tightly regulated entities in payments. Understanding the regulatory framework is important for any business evaluating PISP payments. ### PSD2 (EU) The revised Payment Services Directive (PSD2) came into force across the EU in January 2018. PSD2 created the legal category of PISP and required all banks to provide secure APIs for third-party access. Key requirements for PISPs under PSD2: - Must be authorised or registered with a national competent authority (e.g. BaFin in Germany, DNB in the Netherlands) - Must hold professional indemnity insurance or comparable guarantee - Must use Strong Customer Authentication (SCA) for every payment - Must not hold customer funds at any point - Must communicate with banks via secure, standardised APIs (not screen scraping) PSD3, currently being drafted, is expected to further strengthen Open Banking rules and extend PISP access to instant payment rails across all EU member states. ### FCA and Open Banking UK In the UK, PISPs are regulated by the Financial Conduct Authority (FCA). The UK's Open Banking Implementation Entity (OBIE) went further than PSD2 by mandating a standardised API specification that all CMA9 banks (the nine largest UK banks) must support. This made the UK the most advanced Open Banking market globally. As of 2025, the FCA register lists over 100 firms authorised as PISPs in the UK. The Joint Regulatory Oversight Committee (JROC) has taken over stewardship of Open Banking from the OBIE, with a focus on expanding Variable Recurring Payments (VRP) -- a form of ongoing PISP payment that could eventually replace Direct Debit. ## Limitations of PISP Payments PISP payments are not a universal replacement for cards. There are genuine limitations that merchants and platforms need to consider: - No recurring payments (yet). Standard PISP payments are one-off. Each payment requires the customer to authenticate again. Variable Recurring Payments (VRP) are being rolled out in the UK, but coverage is still limited to sweeping use cases (transferring between your own accounts). Commercial VRP -- which would enable subscription billing via PISP -- is still in pilot stages. - Consumer awareness is still growing. Many consumers are unfamiliar with "pay by bank" and may not trust it at checkout. Conversion rates depend on how well the payment option is presented and explained. - Bank coverage varies. While the major UK and EU banks all support Open Banking APIs, smaller banks, building societies, and international banks may have inconsistent or limited API support. This means some customers may not be able to use PISP payments depending on who they bank with. - No native buyer protection. Card payments come with Section 75 and chargeback protections in the UK. PISP payments are irrevocable -- which benefits merchants but means consumers have fewer dispute mechanisms. Some PISPs are building refund capabilities to address this. - UK and EU focused. Open Banking regulation is most mature in the UK, EU, and a few other markets (Brazil, Australia). The US, Middle East, and most of Asia do not yet have equivalent PISP regulation, limiting global applicability. ## PISP and the Future of Payments PISP payments are growing rapidly. UK Open Banking payment volumes exceeded 11 million per month in 2024, up from under 1 million in 2021. The trajectory is clear: account-to-account payments are becoming a mainstream alternative to cards. Several developments are accelerating this: - Variable Recurring Payments (VRP). Commercial VRP will allow PISPs to set up ongoing payment mandates -- like Direct Debit, but instant and with more granular consumer controls. This would unlock subscriptions, utility billing, and regular invoicing via PISP rails. - PSD3 and PSR. The EU is drafting PSD3 alongside a new Payment Services Regulation (PSR) that will extend Open Banking requirements, improve API reliability, and create a level playing field across all member states. - Embedded finance and payment orchestration. Platforms that embed payments into their software can now offer PISP payments alongside card payments, giving merchants a choice. Payment orchestration layers make it straightforward to route transactions to the optimal payment method -- whether that is a card acquirer or a PISP -- based on cost, speed, or geography. - Global expansion. Brazil's Pix system and Australia's Consumer Data Right are building their own PISP equivalents. India's UPI is already the world's largest real-time payment network. The direction of travel is clear, even if the specific regulatory frameworks differ. For platforms and merchants, the practical implication is that PISP payment acceptance is no longer experimental. It is a production-grade payment method that should be evaluated alongside cards, especially for UK and EU transaction volumes. ## Frequently Asked Questions ### Is PayPal a PISP? Not exactly. PayPal holds an e-money licence and operates as a payment institution, but it is not primarily a PISP in the Open Banking sense. PayPal acts as an intermediary -- it holds funds in PayPal wallets and processes payments through its own network. A true PISP initiates a direct bank-to-bank payment without holding funds. That said, PayPal does use Open Banking (AISP) to allow users to connect bank accounts for top-ups, and it has experimented with PISP-style "pay by bank" flows in some markets. ### Do PISPs Need a Licence? Yes. In the UK, a PISP must be authorised or registered with the FCA as a Payment Institution. In the EU, PISPs must be authorised by the relevant national competent authority under PSD2. The licensing requirements include minimum capital (or professional indemnity insurance), robust IT security, and compliance with Strong Customer Authentication (SCA) requirements. Operating as a PISP without authorisation is a criminal offence. ### What Is the Difference Between a PISP and a Payment Gateway? A payment gateway securely transmits card details from the customer to the acquiring bank and card network. It facilitates card-based payments. A PISP bypasses cards entirely -- it initiates a bank-to-bank payment via Open Banking APIs. A merchant might use both: a payment gateway for card transactions and a PISP for "pay by bank" transactions. Increasingly, payment platforms offer both under one integration. ### Can a PISP Access My Bank Account Without Permission? No. Every PISP payment requires explicit consent from the account holder via Strong Customer Authentication (SCA). This typically means authenticating in your banking app using biometrics or a PIN. The PISP cannot initiate a payment without this authentication step. Additionally, PISPs never have access to your banking credentials -- authentication happens entirely within your bank's own app or website. ### How Much Do PISP Payments Cost? Pricing varies by provider, but PISP payments are typically significantly cheaper than card payments. Most PISPs charge either a flat fee per transaction (often 0.20-0.50 GBP/EUR) or a low percentage (0.1-0.5%). Compare this to card payments, which typically cost 1.5-3% per transaction when you factor in interchange, scheme, and acquirer fees. For high-value transactions, the savings from PISP payments can be substantial. ## Building Payments Infrastructure? Talk to Shuttle Shuttle Global provides embedded payment infrastructure for platforms, SaaS companies, and enterprises. Whether you are integrating account-to-account payments, card processing, or voice-initiated payments, Shuttle gives you a single API for payment flows across multiple providers and methods. Book a discovery call to learn how Shuttle can simplify your payment stack. ## Related Reading Explore More ### Payment Collection for Builders Merchants: Links, Voice & Open Banking ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [payment gateways](/glossary/payment-gateway/) - [Payment orchestration layers](/guides/what-is-payment-orchestration/) - [payment gateway](/glossary/payment-gateway/) - [Book a discovery call](/discovery/) - [GuidePayment Collection for Builders Merchants: Links, Voice & Open Banking→](/guides/builders-merchant-payment-collection/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/what-is-payment-gateway-aggregation/ --- # Payment Providers: How They Work & How to Choose (2026) | Shuttle > Compare payment providers and understand how they work. Learn the difference between gateways, aggregators, and PSPs -- and how to choose the right one for... # Payment Providers: How They Work & How to Choose (2026) By Nick Dunse, February 21, 2026 Compare payment providers and understand how they work. Learn the difference between gateways, aggregators, and PSPs -- and how to choose the right one for... Every business that accepts digital payments relies on a payment provider -- also known as a payment service provider (PSP) -- to process transactions. Payment providers handle the infrastructure that moves money from a customer's card or bank account to a merchant's account, managing everything from card authorisation to fraud screening to settlement. But as businesses grow, the relationship with payment providers gets more complex. A single provider might not cover every market, support every payment method, or offer the best rates for every transaction type. That is where payment gateway aggregation becomes relevant -- and why understanding the landscape of payment providers matters for any growing business. This guide explains what gateway aggregation is, why it exists, and how to choose the right payment provider for your needs. ## What Is Payment Gateway Aggregation? Payment gateway aggregation is the practice of connecting to multiple payment gateways (PSPs) through a single integration point, rather than integrating with each gateway individually. Instead of building and maintaining separate connections to Stripe, Adyen, Worldpay, and other processors, a business uses an aggregation layer that routes transactions to the appropriate gateway based on rules like geography, cost, card type, or performance. The key benefits of aggregation are: - Redundancy -- If one PSP has downtime, you can move the affected payment types to another connected PSP. This is critical for high-volume merchants where even minutes of payment downtime mean lost revenue. - Cost optimisation -- Different PSPs offer different rates for different card types, currencies, and regions. Aggregation lets you route each transaction to the cheapest available processor. - Geographic coverage -- No single PSP has the best local acquiring rates in every country. Aggregation lets you use local processors in each market for higher approval rates and lower fees. - Flexibility -- Adding or removing a PSP doesn't require rebuilding your checkout. The aggregation layer abstracts the underlying connections. Gateway aggregation is sometimes called payment orchestration, though orchestration platforms typically add features like smart routing algorithms, PSP-agnostic tokenisation vaults, and unified reporting on top of the basic aggregation capability. ## How Payment Providers Work Behind the Scenes When a customer pays online, the payment provider handles a multi-step process in seconds: - The customer enters card details (or selects a wallet like Apple Pay) - The payment provider encrypts the data and submits an authorisation request to the card network (Visa, Mastercard) - The card network forwards the request to the customer's issuing bank - The issuing bank approves or declines based on available funds, fraud checks, and account status - The response flows back through the network to the merchant - Settlement occurs 1-3 business days later, with the payment provider transferring funds (minus fees) to the merchant Payment providers that bundle gateway, processing, and merchant account services -- like Stripe, Adyen, and Checkout.com -- handle this entire flow. Traditional setups separate each component across different providers. ## How to Choose a Payment Provider Selecting the right payment provider is one of the most consequential infrastructure decisions a business makes. Switching providers means migrating card tokens, re-integrating APIs, and potentially disrupting live payment flows. Here are the factors that matter most: Transaction pricing. Understand the total cost per transaction, not just the headline rate. Factor in scheme fees, cross-border surcharges, currency conversion, chargeback fees, and any monthly minimums. For high-volume merchants, interchange++ pricing (from providers like Adyen or Worldpay) is almost always cheaper than flat-rate pricing. Geographic coverage. If you sell internationally, check whether the provider offers local acquiring in your key markets. Local acquiring typically delivers higher authorisation rates and lower fees compared to cross-border processing. Payment method support. Beyond cards, consider which local payment methods matter to your customers -- SEPA in Europe, BACS in the UK, Pix in Brazil, iDEAL in the Netherlands. Not all providers support the same methods. Developer experience. API documentation quality, SDK availability, sandbox environments, and webhook reliability vary significantly between providers. Test the integration experience before committing. Fraud and risk tools. Built-in fraud scoring, 3D Secure support, and configurable risk rules can meaningfully reduce chargeback rates and false declines. Contract terms. Watch for long-term lock-in, volume commitments, and early termination fees -- particularly with traditional acquiring banks and legacy processors. Scalability. Ensure the provider can handle your projected transaction volumes, particularly during peak periods (Black Friday, end-of-month billing runs). Ask about uptime SLAs and historical performance. For a structured evaluation framework covering all 12 criteria, see our how to choose a payment platform guide. ## Why Aggregation Matters for Growing Businesses Early-stage businesses typically start with a single PSP -- usually whichever is fastest to integrate. This works until it doesn't. The common trigger points for needing aggregation are: - International expansion -- Entering new markets where your current PSP has poor approval rates or doesn't support local payment methods - Volume growth -- Processing enough volume that routing optimisation saves meaningful basis points - Enterprise customers -- Serving clients who mandate specific PSPs as part of their procurement requirements - Risk management -- Needing redundancy after experiencing PSP outages that cost revenue For software platforms that need to embed payments for their merchants, gateway aggregation is built into the infrastructure layer. A PSP-neutral payment layer connects to 40+ gateways and lets each merchant use their preferred provider -- without the platform building each integration individually. ## Related Reading - What Is a Payment Gateway? -- how gateways work, costs, and integration - What Is Payment Orchestration? -- smart routing, failover, and multi-PSP management - How to Choose a Payment Platform -- the 12-criteria evaluation checklist - PSP-Neutral vs Single-PSP Architecture -- when multi-PSP flexibility matters - Shuttle PSP Network -- 40+ connected payment providers *Shuttle helps software platforms embed payments across multiple gateways -- one integration, 40+ PSPs, white-label tools. See how it works or book a discovery call.* Explore More ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ### How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [payment orchestration](/guides/what-is-payment-orchestration/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Checkout.com](/payment-providers/checkout-com/) - [Worldpay](/payment-providers/worldpay-access/) - [local payment methods](/guides/take-payments-online/) - [how to choose a payment platform](/guides/how-to-choose-payment-platform/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [What Is a Payment Gateway?](/blog/what-is-a-payment-gateway/) - [What Is Payment Orchestration?](/guides/what-is-payment-orchestration/) - [How to Choose a Payment Platform](/guides/how-to-choose-payment-platform/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Shuttle PSP Network](/payment-providers/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [GuideHow Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs→](/guides/payment-gateway-cost/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)→](/guides/hubspot-payment-link-branding/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/where-psp-distribution-actually-lives/ --- # Where PSP Distribution Actually Lives | Shuttle > PSP distribution is shifting from direct sales to embedded platform infrastructure. # Where PSP Distribution Actually Lives By shuttle-team, February 20, 2026 PSP distribution is shifting from direct sales to embedded platform infrastructure. Processing has been commoditised for years. Every major PSP offers roughly the same core capability. Accept cards. Settle funds. Provide a dashboard. The margins are thin and getting thinner. The PSPs that win the next decade won't win on processing. They'll win on distribution. And most of them don't have a distribution strategy for where commerce is actually heading. ## The distribution problem PSPs have historically distributed through two channels: direct sales and developer adoption. Direct sales works for enterprise merchants with dedicated payments teams. Developer adoption works for startups and SMBs building their first checkout flow. Neither works for the fastest-growing segment of payment volume: software platforms. Platforms own the workflow. They control the merchant relationship. They decide which payment providers their customers can access. And increasingly, they're the ones building the payment experience, not the merchant. If a PSP isn't embedded inside the platform where the merchant operates, that PSP is invisible. This is already happening. CCaaS platforms are embedding payments into voice workflows. Insurance platforms are embedding payments into policy management. ERP systems are embedding payments into invoicing. AI agents are embedding payments into conversations. The payment moment is moving inside software. And PSPs need a way to follow it there. ## Why PSPs can't solve this alone The obvious answer is: PSPs should build platform integrations themselves. Offer APIs. Create partnerships. Get embedded. Some are trying. The challenge is scale. There are thousands of software platforms across dozens of verticals. Each has its own integration requirements, compliance context, and channel mix. A PSP building one-to-one integrations with every platform that matters will never keep pace. And there's a deeper structural issue. Platforms don't want to be locked into a single PSP. Their enterprise customers demand provider choice. A platform that integrates directly with Worldpay still needs to support Adyen for the next customer, and their regional acquirer for the one after that. PSPs competing for direct integration slots inside platforms are playing a zero-sum game. The platform can only maintain so many direct integrations. Every slot a PSP wins is a slot another one loses. That's the wrong game entirely. ## The layer changes the math What if PSPs didn't need to build and maintain individual platform integrations? What if there was a distribution layer that already sat inside platforms, already supported the channels those platforms operate in, and already handled the compliance burden? That's what a multi-PSP payment layer creates. Not routing logic. Not failover. Distribution infrastructure. Shuttle connects to 40+ PSPs and sits inside platforms across voice, links, chat, and embedded checkout. When a platform integrates Shuttle, every connected PSP gains access to that platform's merchants without building a custom integration. The math changes fundamentally. Instead of building one-to-one integrations with platforms, a PSP connects to Shuttle once and gains distribution across every platform on the layer. For the PSP, Shuttle isn't a competitor. It's a distribution channel. The PSP keeps the merchant relationship, the processing revenue, and the commercial terms. Shuttle provides the rail that gets the PSP into the platform in the first place. ## The channels that matter next Distribution isn't just about being inside platforms. It's about being inside the right channels. Voice is one of the fastest-growing payment surfaces. AI voice agents are handling sales calls, insurance claims, and service bookings. Every one of those conversations can include a payment moment. The PSP that's connected to the voice payment layer captures that volume. The one that isn't, doesn't. Payment links are another. Platforms are sending branded checkout links via SMS, email, and chat. It's not ecommerce. It's operational commerce. Invoice collection, appointment deposits, service payments. High volume, high frequency, and entirely controlled by the platform. These channels didn't exist five years ago. They're growing faster than traditional checkout. And they require infrastructure that most PSPs haven't built for. A PSP that's connected to a multi-channel payment layer is present wherever commerce happens. A PSP that's only distributed through direct sales and developer docs is limited to wherever merchants actively choose to implement them. ## The strategic question For PSPs evaluating their distribution strategy, the question is straightforward: Where are your merchants going to be in three years? Inside platforms. Inside AI agents. Inside voice and chat flows. Are you going to build individual integrations with every platform that matters? Or connect to the layer that's already there? Stripe is building up the stack, trying to own more of the merchant relationship. That's one strategy. Shuttle is building sideways across the stack, connecting PSPs to the platforms and channels where commerce is moving. That's a different strategy. And for PSPs that want to maintain their merchant relationships while gaining embedded distribution, it's the one that scales. The leverage lives in the layer. The PSPs that understand distribution as an infrastructure problem, not a sales problem, will be the ones still growing when processing margins hit zero. ## Related Reading - The First Agentic Payments Went Live -- What the infrastructure looks like behind Razorpay's live agentic payments - The Payment Layer for AI Agents -- Why AI agents need a payment layer, not a payment provider - Why Platforms Don't Want to Be Payment Companies -- The PayFac trap and why platforms need a payment layer instead - Agentic Commerce -- The hub for agentic commerce and AI-driven payment infrastructure - Agentic Payments Infrastructure in 2026 -- The full landscape of agentic payment infrastructure - The Voice AI Payment Infrastructure Gap -- Why voice AI companies can't solve payments alone - Embedded Payments for CCaaS -- How contact centre platforms are embedding payments into voice workflows Explore More ### How PSPs Get Distribution Into Enterprise Software ### Single Global PSP vs Multiple Local Acquirers: How to Decide ### Enterprise PSP Mandates: Why Platforms Need Multiple Gateways ### PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform? ### What Happens When Your Only Payment Processor Cuts You Off ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [The First Agentic Payments Went Live](/blog/agentic-payments-go-live/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Why Platforms Don't Want to Be Payment Companies](/blog/why-platforms-dont-want-to-be-payment-companies/) - [Agentic Commerce](/guides/agentic-commerce/) - [Agentic Payments Infrastructure in 2026](/blog/agentic-payments-infrastructure-2026/) - [The Voice AI Payment Infrastructure Gap](/blog/voice-ai-payment-infrastructure-gap/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [GuideHow PSPs Get Distribution Into Enterprise Software→](/guides/how-psps-get-distribution-into-software/) - [GuideSingle Global PSP vs Multiple Local Acquirers: How to Decide→](/guides/global-psp-vs-local-acquirers/) - [GuideEnterprise PSP Mandates: Why Platforms Need Multiple Gateways→](/guides/enterprise-psp-mandates/) - [GuidePSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform?→](/guides/psp-neutral-vs-single-psp/) - [GuideWhat Happens When Your Only Payment Processor Cuts You Off→](/guides/single-psp-risk/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/why-platforms-dont-want-to-be-payment-companies/ --- # Why Platforms Don't Want to Be Payment Companies | Shuttle > The PayFac model traps platforms into owning payment infrastructure they never wanted. Here's why platforms need a payment layer, not a PayFac licence. # Why Platforms Don't Want to Be Payment Companies By shuttle-team, February 18, 2026 The PayFac model traps platforms into owning payment infrastructure they never wanted. Here's why platforms need a payment layer, not a PayFac licence. Nobody starts a platform company thinking about payments. They think about the workflow. The vertical. The problem their software solves. Payments are assumed. A box to tick, not a business to build. Then the first enterprise customer shows up and asks which PSPs you support. That's when it gets complicated. ## The conversation nobody planned for Enterprise buyers don't just want payments to work. They want specific providers. They have existing contracts with Worldpay, or Adyen, or their regional acquirer. They have procurement rules. Compliance requirements. Treasury mandates. And they expect the platform to support all of it. For the platform, this creates a problem that gets worse with every new customer. Each PSP integration is a six-month project. Each one adds PCI scope. Each one drags engineering resources away from the product roadmap. Multiply that by five enterprise customers with different PSP requirements, and suddenly payments aren't a box to tick. They're a roadmap tax. ## The PayFac trap The conventional answer is: become a PayFac. Register as a payment facilitator. Own the merchant onboarding. Control the funds flow. Take a cut of every transaction. On paper, it looks like a revenue opportunity. In practice, it's a trap for most platforms. Becoming a PayFac means taking on regulatory obligations. KYC. AML. PCI DSS compliance at the highest level. Ongoing audits. A payments team you never planned to hire. And here's the part nobody mentions upfront: it locks you into a single PSP relationship. Your enterprise customers don't get choice. They get whatever provider you chose when you became a PayFac. That works for SMB merchants who don't have existing PSP relationships. It breaks the moment you sell to enterprise. The platform that becomes a PayFac optimises for payment revenue. The platform that stays PSP-neutral optimises for enterprise deal velocity. Those are very different strategies. ## What platforms actually want Talk to any platform CTO or Head of Product about payments, and the same themes come up: "We don't want to become a payments company." They want to ship payment features without taking on the operational weight of running payment infrastructure. "Enterprise deals demand specific PSPs." Their customers already have provider relationships. The platform needs to support them, not replace them. "Payments keep hijacking the roadmap." Every new PSP integration pulls engineers off product work. The cost isn't just development time. It's the features that don't get built. "We need it live in weeks, not quarters." The platform market moves fast. A 12-month payments build project is a competitive disadvantage. These aren't edge cases. This is the standard experience for any platform selling to mid-market and enterprise buyers. ## The layer that solves this What platforms need isn't a PSP. It's a layer between their software and PSPs. A single integration point that connects to the providers their customers already use. That handles PCI compliance so the platform doesn't have to. That supports payments across every channel the platform operates in, whether that's embedded checkout, voice, links, or chat. That's what Shuttle built. One integration. 40+ PSPs. PCI DSS Level 1, ISO 27001, SOC 2. Voice, links, chat, and embedded checkout on the same layer. White-label merchant onboarding and a management portal included. Platforms ship payment features in weeks. Enterprise customers keep their existing PSP. The platform roadmap stays focused on the product, not on payments plumbing. Invoice Stack integrated Shuttle and went live across multiple PSPs without building a payments team. As Harry Bevan put it: "Shuttle let us add payments without having to own or manage payments ourselves. Our customers can bring their own gateways, and we were able to improve the payment experience and scale without hiring a payments or finance team." Brightpearl did the same for commerce. INSTANDA for insurance. The pattern is the same: platform integrates Shuttle, enterprise customers bring their PSPs, payments ship fast. ## The real cost of doing nothing Some platforms delay the decision. They build one PSP integration, usually Stripe, and figure they'll deal with multi-PSP when it becomes a problem. It becomes a problem faster than they expect. The first enterprise deal that requires a non-Stripe provider forces a build-or-lose-the-deal decision. The second one makes it clear this isn't going away. By the third, the platform is maintaining multiple bespoke integrations with no abstraction layer, and every new one takes longer than the last. The average platform that builds this themselves spends $360k per year maintaining payment infrastructure. That's before the $2M in PCI compliance costs and 12 months of development time that could have gone into product. Doing nothing is also a strategy. It just shows up as lost deals and a slower roadmap. ## The question to ask If your platform is heading upmarket, selling to enterprise, or expanding into new channels like voice and chat, the question isn't whether you'll need a payment layer. The question is whether you build it yourself or plug into one that already exists. ## Related Reading - The First Agentic Payments Went Live -- What the infrastructure looks like behind Razorpay's live agentic payments - The Payment Layer for AI Agents -- Why AI agents need a payment layer, not a payment provider - Where PSP Distribution Actually Lives -- How PSP distribution is shifting to embedded platform infrastructure - Agentic Commerce -- The hub for agentic commerce and AI-driven payment infrastructure - Agentic Payments Infrastructure in 2026 -- The full landscape of agentic payment infrastructure - The Voice AI Payment Infrastructure Gap -- Why voice AI companies can't solve payments alone - Embedded Payments for CCaaS -- How contact centre platforms are embedding payments into voice workflows Explore More ### Embedded Payments for ERP Platforms ### Build vs Buy Payment Infrastructure: A Decision Framework for Platforms ### How B2B Service Companies Collect Payments Faster ### Payment Solutions for Car Dealerships & Auto Finance Platforms ### PCI-Compliant Payment Architecture for Insurance Platforms ### Agentic Payments: What Platforms Need to Know ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [The First Agentic Payments Went Live](/blog/agentic-payments-go-live/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Where PSP Distribution Actually Lives](/blog/where-psp-distribution-actually-lives/) - [Agentic Commerce](/guides/agentic-commerce/) - [Agentic Payments Infrastructure in 2026](/blog/agentic-payments-infrastructure-2026/) - [The Voice AI Payment Infrastructure Gap](/blog/voice-ai-payment-infrastructure-gap/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [GuideEmbedded Payments for ERP Platforms→](/guides/payments-for-erp-platforms/) - [GuideBuild vs Buy Payment Infrastructure: A Decision Framework for Platforms→](/guides/build-vs-buy-payment-infrastructure/) - [GuideHow B2B Service Companies Collect Payments Faster→](/guides/b2b-payment-collection/) - [GuidePayment Solutions for Car Dealerships & Auto Finance Platforms→](/guides/car-dealership-payment-solutions/) - [GuidePCI-Compliant Payment Architecture for Insurance Platforms→](/guides/pci-payments-insurance-platforms/) - [GuideAgentic Payments: What Platforms Need to Know→](/guides/agentic-payments-for-platforms/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/why-we-built-the-payment-layer/ --- # Why We Built The Payment Layer | Shuttle > Software platforms shouldn't have to become payment companies. The Payment Layer is the infrastructure that sits between software and PSPs -- so platforms... # Why We Built The Payment Layer By Nick Dunse, February 27, 2026 Software platforms shouldn't have to become payment companies. The Payment Layer is the infrastructure that sits between software and PSPs -- so platforms... Talk to us Make enabling payments for your platform and merchant users easy. Something broke in payments and nobody talks about it. Every software platform that gets big enough eventually hits the same wall. A customer says "we need to take payments inside this." Could be a voice call. Could be an invoice workflow. Could be an AI agent having a conversation with a customer who's ready to pay. And the platform team sits down and asks: how do we do this? The answers they get are all bad. ## The Three Bad Options Option one: pick a PSP and build the integration. Stripe, usually. It works for the first customer. Then the second customer needs Adyen because that's their existing contract. The third needs Worldpay because their compliance team mandates it. By the fifth customer, payments are eating the product roadmap alive. Every new provider is a separate integration, a separate certification process, a separate maintenance burden. The engineering team that was supposed to be building the platform is now building payment plumbing. Option two: become a payment company yourself. Get a PayFac licence. Build the compliance infrastructure. Hire a payments team. This takes 12-18 months and costs millions. And at the end of it, you're no longer a software company with payments. You're a payment company that happens to have software. The thing that made you valuable -- the platform, the workflow, the customer relationship -- is now secondary to the thing you were forced to build. Option three: do nothing. Tell customers to figure it out themselves. This works until it doesn't. Until a competitor offers payments natively. Until the enterprise deal falls through because you can't support their PSP. Until the AI agent you spent two years building hits a dead end the moment money is involved. Every platform team picks one of these three doors. Every one of them regrets it. ## The Problem Isn't That Payments Are Hard The problem is that the infrastructure doesn't exist. Gateways process transactions. They're designed for merchants, not platforms. They don't handle multi-tenancy. They don't span channels. They lock you into one provider. Orchestrators route between gateways. Better, but still merchant-facing. Still checkout-page-centric. Still require heavy integration. They optimise transaction routing -- useful for a merchant with three gateways, irrelevant for a platform that needs to support whatever PSP each of its customers already uses. PayFac models -- Stripe Connect, Adyen for Platforms -- make you the payment company. That's not a solution. That's a career change. What's missing is a layer. ## Three Shifts That Created the Gap ### 1. Software owns distribution Vertical SaaS platforms control merchant workflows now. Talkdesk controls the contact centre. INSTANDA controls insurance operations. The merchant lives inside the software. Whoever controls the software controls the payment moment. But the payment industry still sells to merchants one by one -- not through the software that already has them. ### 2. PSPs can't get inside software PSPs have money and processing capability. Platforms have distribution and the customer relationship. The two sides need each other. But there's no clean way to connect them. Embedding a PSP inside a platform requires significant integration work. Supporting multiple PSPs requires multiples of that work. The math doesn't work. ### 3. Commerce is escaping checkout pages Payments are moving into voice calls, AI agent conversations, messaging, field workflows, embedded finance flows. A customer calls a contact centre and wants to pay mid-conversation. An AI agent handles a collections call and needs to close the payment before the caller hangs up. None of these are checkout pages. None of them work with infrastructure designed for checkout pages. ## The Payment Layer What's missing is simple to describe: a thin piece of infrastructure that sits between software platforms and PSPs. The platform integrates once. The layer handles PSP routing per customer, PCI compliance, merchant onboarding, and payment capture across every channel -- voice, links, chat, embedded checkout, workflows. The platform doesn't become a payment company. The PSP gets distribution inside software it couldn't reach before. The end customer uses whatever payment provider they already have. This is The Payment Layer. It's to payments what the CDN was to content delivery, or what Twilio was to communications. Portable, modular, usage-based infrastructure that software platforms plug into -- not projects they build. ## What Makes The Payment Layer Different Orchestrator Payment Layer What it does Processes transactions Routes between PSPs Makes you the PSP Embeds payments inside software PSP relationship Is the PSP Sits above PSPs Replaces the PSP Distributes PSPs Who it serves Platforms wanting to be PayFacs Platforms wanting to NOT be PayFacs Checkout page Voice, links, chat, embedded, workflows Time to live 6-12 months Days to weeks Merchant owns it Platform owns it Layer owns it The Payment Layer is not a better gateway. It's not a better orchestrator. It's a different thing -- designed for a different problem. For the full comparison, see our Gateway vs Orchestrator vs PayFac vs Payment Layer guide. ## Why We Built It We built Shuttle because we kept watching the same pattern repeat. A platform would win an enterprise deal. The customer wanted embedded payments. The platform would start with Stripe Connect or build a direct PSP integration. It would work for three months. Then the next customer needed a different PSP. Then the contact centre team needed voice payments. Then the AI voice agent needed to take a card number mid-conversation. Each of these moments was a separate project. A separate integration. A separate compliance exercise. By the time the platform had covered three PSPs and two channels, they'd spent a year and burned through engineering budget that was supposed to build their core product. The Payment Layer collapses all of that into one integration. 40+ PSPs. Voice, links, chat, embedded checkout. PCI DSS Level 1 handled by the layer. White-label merchant onboarding and portals. The platform stays a platform. We're live on Twilio's Marketplace. We power AI voice payments for PolyAI. We support platforms across CCaaS, insurance, field service, travel, and fintech. Every one of them integrated once and ships new payment capabilities without new projects. ## What Happens Next The category is forming whether any single company defines it or not. The market forces are too strong. Software owns distribution. PSPs need access. Commerce is escaping checkout pages. Something has to sit in between. Platforms that adopt The Payment Layer ship payments in weeks. They support any PSP their customers need. They expand into voice, links, AI agents -- without new integration projects. They stay platforms. Platforms that don't adopt it keep building. Keep hiring. Keep diverting engineering resources from their core product into payment infrastructure that someone else should own. The only question is who builds the layer and who gets left building plumbing. *Shuttle is The Payment Layer for software platforms. One integration. 40+ PSPs. Voice, links, chat, and embedded checkout. See how it works or book a discovery call.* ## Related Reading Explore More ### Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? ### The Payment Layer for AI Agents ### Payment Orchestration vs Payment Layer: Why They're Not the Same ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### HubSpot Payment Gateway Integration: Every Option Compared (2026) ## Links - [Book a Call →](/discovery/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [building payment plumbing](/guides/get-payments-off-your-roadmap/) - [a payment company that happens to have software](/guides/embedded-payments-without-payfac/) - [Gateways](/blog/what-is-a-payment-gateway/) - [Orchestrators](/guides/what-is-payment-orchestration/) - [Stripe Connect](/vs/stripe-connect/) - [Adyen for Platforms](/vs/adyen/) - [The math doesn't work](/guides/psp-neutral-vs-single-psp/) - [close the payment before the caller hangs up](/guides/agentic-payments-for-platforms/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Shuttle](/platforms/) - [40+ PSPs](/payment-providers/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [GuideGateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?→](/guides/payment-layer-explained/) - [GuideThe Payment Layer for AI Agents→](/guides/the-payment-layer-for-ai-agents/) - [GuidePayment Orchestration vs Payment Layer: Why They're Not the Same→](/guides/payment-orchestration-vs-payment-layer/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHubSpot Payment Gateway Integration: Every Option Compared (2026)→](/guides/hubspot-payment-gateway/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/why-you-should-have-a-backup-payment-service-provider-psp/ --- # Why You Should Have a Backup Payment Service Provider (PSP) | Shuttle > Having a backup PSP protects your business from payment outages. Learn why redundancy in payment processing is essential for business continuity. # Why You Should Have a Backup Payment Service Provider (PSP) By Nick Dunse, February 21, 2026 Having a backup PSP protects your business from payment outages. Learn why redundancy in payment processing is essential for business continuity. At Shuttle, we continuously monitor our payment partners' uptime and understand that payment gateways and services experience occasional outages. While brief downtimes of around 10 minutes may be acceptable, longer disruptions can significantly impact businesses. Having a backup payment provider that you can switch to quickly is a smart move for any merchant. Some payment providers are less transparent about their service availability, sometimes taking hours to acknowledge an incident. Shuttle's uptime page categorizes provider statuses using GREEN, AMBER, or RED indicators. Additionally, platform users can request access to real-time alerts, which may be subject to an additional fee. Recent Payment Service Downtime Examples: - Authorize.net - Down for 36 hours - Mollie - Unavailable for several days over a week - Square - Completely offline for seven days While downtime is a significant reason to have multiple PSPs, there are additional benefits to consider. Beyond Downtime: Why You Need Another PSP ## When it comes to payments, merchants should focus on two key factors: - Processing Costs - The fees associated with each transaction and the overall cost of payment operations. - Acceptance Rates - The percentage of successfully processed transactions (or, conversely, the cost of failed payments). Comparing costs and acceptance rates can be challenging without actually processing payments through multiple providers. PSP contracts may include various hidden fees, and acceptance rates are best measured through real transactions. Additionally, if a PSP is unavailable, your acceptance rate drops to 0%. A backup PSP is also essential for businesses operating in markets where their primary provider lacks coverage or does not support common local payment methods. Many Shuttle merchants opt to connect PayPal separately alongside another provider. This setup can reduce PayPal processing costs and ensure access to the latest PayPal features. Shuttle is also evolving to allow Apple Pay and Google Pay to be connected independently from the primary PSP. ## Choosing a Backup Payment Provider ## When selecting a backup PSP, consider the following factors: - Cost & Acceptance Rates - Compare transaction fees and success rates. - Technology & Features - Evaluate dashboards, value-added services, and ease of integration. - Customer Support - Do you prefer a dedicated account manager or are you comfortable with online chat support? Newer PSPs often provide advanced technology and user-friendly dashboards but may offer limited personal support. If improving acceptance rates is your priority, having access to knowledgeable support staff is crucial. ## How Backup PSPs Work with Shuttle Connecting a new PSP via Shuttle is straightforward. However, to maintain a seamless checkout experience, we do not allow merchants to run two concurrent PSPs with the same payment method within a single checkout instance. This prevents customer confusion over choosing between multiple card gateways. Instead, Shuttle enables merchants to route transactions based on predefined workflow rules. For example, PayPal wallet transactions can be directed exclusively to PayPal. For merchants using a backup PSP, payment methods can be manually toggled on and off between connected providers. But, saved payment methods will not be automatically available across different gateways unless manually stored in both. This can be a challenge for merchants processing recurring payments. Shuttle is exploring the use of Network Tokens to enable seamless transaction processing across multiple PSPs, though this feature may incur additional costs. For one-off payments, Shuttle offers a quick and simple way to enable a new PSP or payment method. Merchants looking for deeper cost and performance comparisons can set up an additional Shuttle account to process a portion of their payments through a separate instance. Future Solutions Shuttle is evaluating the best ways to support backup PSPs for both one-off and recurring transactions, as well as for PSP performance comparisons. Since card vaults have not been a full-proof and soon to be outdated solution. Potential solutions include: - Network Tokens - To securely store payment details across multiple PSPs - And Automated Switching Rules - To dynamically route transactions based on real-time conditions A backup PSP is not just a safeguard against downtime -- it's a strategic move to optimize costs, improve acceptance rates, and ensure business continuity. Shuttle makes it easy for merchants to integrate multiple PSPs and stay in control of their payment operations. ## Related Reading Explore More ### PCI Compliance Service Provider: How to Choose One in 2026 ### How to Switch Payment Providers Without Losing Customers ### How to Avoid Payment Provider Lock-In: A Platform Guide ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments ### How to Reduce Payment Processing Fees Without Switching Providers ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuidePCI Compliance Service Provider: How to Choose One in 2026→](/guides/pci-compliance-service-provider/) - [GuideHow to Switch Payment Providers Without Losing Customers→](/guides/payment-provider-migration/) - [GuideHow to Avoid Payment Provider Lock-In: A Platform Guide→](/guides/payment-provider-lock-in/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideHow to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments→](/guides/salesforce-service-cloud-payments/) - [GuideHow to Reduce Payment Processing Fees Without Switching Providers→](/guides/reduce-payment-processing-fees/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/why-your-ar-team-is-drowning-in-manual-work-and-how-to-fix-it/ --- # Why Your AR Team Is Drowning in Manual Work (And How to Fix It) | Shuttle > Your AR team is stuck in spreadsheets while revenue grows. Discover how payment automation eliminates manual follow-ups and speeds up cash collection. # Why Your AR Team Is Drowning in Manual Work (And How to Fix It) By Nick Dunse, February 22, 2025 Your AR team is stuck in spreadsheets while revenue grows. Discover how payment automation eliminates manual follow-ups and speeds up cash collection. ## Our Payment Links are different Shuttle Payment Links are not limited like others. We recognise that businesses need flexibility and control to improve their payment collection processes. Our payment links are not tied to any one payment provider, they can let the customer define the amount or you can be very specific about what and how much they're for. Use your Payment Gateway Connect from 30+ Payment Providers. This means you can use your preferred provider with the rates that you have agreed. No more 5% fees just because you're using a hosted solution that doesn't support your preferred payment gateway. Use Multiple Payment Gateways/Methods Get paid via PayPal, Buy Now Pay Later, Financing or Bank to Bank. Payment links that are from your payment provider are limited to that provider and their features. Not tied to any product, invoice or amount Use one link for everything or organise your links by creating many for each use case. Other providers make you create a product or invoice just so you can create a payment link. That's missing the point. Pre-authorize, capture payment or save a card Take a payment now or just authorize the card or save the payment method for later. Other payment link products don't empower the seller, they are merely designed for a simple use case. Your business is growing. Revenue's up, invoices are flying out the door, and your customers are solid. So why does it feel like your Accounts Receivable (AR) team is stuck in the mud? Because they are. If you're still relying on spreadsheets, manual email reminders, and a patchwork of payment methods, your AR team is spending too much time on admin -- and not enough time on strategy. In this article, we'll break down what's holding your AR process back, and how mid-sized businesses are using smart payment links to unlock faster payments, cleaner workflows, and scalable growth. 💥 The Reality for Most Mid-Sized AR Teams If you have 50 to 500 employees, you've likely outgrown the startup chaos -- but haven't yet reached enterprise-level automation. That's where the problems creep in: Invoices go out... and then sit unpaid Customers forget, delay, or don't understand how to pay Your team chases manually via email or phone Payments arrive by bank transfer, card, ACH... with no context Finance spends days trying to match payments to invoices This isn't just time-consuming -- it's expensive. You're burning people-hours, delaying cash flow, and risking errors. 🧱 Why This Happens Let's break it down: ### 1. Fragmented systems Your invoicing, CRM, payment gateway, and accounting tools often don't talk to each other. That means the burden falls on your AR team to fill the gaps. ### 2. Rigid payment methods If you only offer bank transfer, your customers have to switch apps, look up reference numbers, and guess what they're paying for. That friction kills speed. ### 3. No automation or tracking You don't know if someone saw the invoice, clicked a link, or started a payment -- until the money (hopefully) lands. 🚧 The Cost of Manual AR Here's what it costs mid-sized companies in real terms: Issue | Cost Manual chasing | Hours per week per AR staff Delayed payments | 5-12 day increase in DSO Poor reconciliation | Errors, missed revenue, write-offs Admin-heavy growth | Hiring more AR staff just to cope This isn't just a finance issue. It affects cash flow, ops, forecasting, and customer experience. ✅ The Fix: Smart Payment Links Smart payment links let you streamline collections without replacing your entire finance stack. Instead of relying on static invoices and bank transfers, you send a branded, trackable payment link that's: Pre-filled with invoice data Delivered via email, SMS, or WhatsApp Offers cards, Open Banking (UK), ACH (US), or Pay by Bank Tracked in real-time Auto-reconciled with your invoice system No logins. No portals. No chasing. 🔗 Real Example: What This Looks Like Let's say you send 200 invoices a month. With Shuttle, those invoices are turned into smart payment links -- sent via your CRM, accounting tool, or messaging system. Your customer clicks the link, pays via card or bank, and you get notified immediately. The payment is automatically matched to the invoice. Your AR team? Free to focus on strategy, exceptions, and scale. ⚙️ Works With the Tools You Already Use Smart payment links integrate with: Xero, QuickBooks, NetSuite, Sage Zapier, Make.com, Salesforce, HubSpot Twilio, WhatsApp, Email platforms No dev work required. No new portals for your team or your clients. 🚀 Scale Without the Headcount The real win? You can scale collections without scaling the team. Mid-sized companies using Shuttle typically: Reduce manual chasing by 30-50% Collect payments 5-12 days faster Improve reconciliation speed by up to 80% All while keeping your existing systems in place. 💬 Final Word Manual AR isn't just inefficient -- it's a growth blocker.Smart payment links are the simplest way to transform your receivables process without a painful systems overhaul. If your finance team is stretched and your DSO is rising, maybe it's time to make your AR team smarter -- not bigger. ## Related Reading Explore More ### How to Get Payments Off Your Product Roadmap ### Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope ### Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals ### Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem ### What Is Twilio Pay? How It Works, Pricing, and Connectors (2026) ### Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [GuideHow to Get Payments Off Your Product Roadmap→](/guides/get-payments-off-your-roadmap/) - [GuideTwilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope→](/guides/twilio-generic-pay-connector/) - [GuideField Agent Payment Collection: Why Your Team Doesn't Need Card Terminals→](/guides/field-agent-payment-collection/) - [GuideTake Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem→](/guides/take-payments-on-behalf-of-clients/) - [GuideWhat Is Twilio Pay? How It Works, Pricing, and Connectors (2026)→](/guides/what-is-twilio-pay/) - [GuideTwilio Pay Error Codes Explained: What Your Pay Connector Actually Supports→](/guides/twilio-pay-error-codes/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/why-your-ivr-needs-a-backup-payment-links-as-fallback-for-voice/ --- # Why Your IVR Needs a Backup: Payment Links as Fallback for Voice | Shuttle > Even the smartest IVR can fail. Learn how payment links serve as a reliable fallback for voice payments, reducing drop-off and recovering failed calls. # Why Your IVR Needs a Backup: Payment Links as Fallback for Voice By Nick Dunse, October 24, 2025 Even the smartest IVR can fail. Learn how payment links serve as a reliable fallback for voice payments, reducing drop-off and recovering failed calls. Even the smartest IVR can fail. A customer mistypes a card digit. Background noise interferes with DTMF tones. The call drops just as the payment is about to complete. In voice commerce, these moments don't just cost convenience -- they cost revenue. That's why every voice payment journey needs a safety net. And in 2025, that safety net is a Payment Link fallback. The Fragility of Voice-Only Payments IVR payments are elegant when they work. The customer stays in flow, the payment is taken instantly, and compliance remains intact. But voice is inherently unpredictable -- mobile reception, background sound, and human error all create points of failure. When the customer's payment attempt fails, they're often forced to start again or wait for a callback. That friction breaks trust and erodes completion rates. Every retry is an invitation for drop-off. For contact centres and BPOs managing high call volumes, even a small drop in conversion can translate into significant lost revenue. Voice + Link = Complete Coverage Shuttle solves this with a simple concept: if the voice channel fails, fall back to a payment link. When a DTMF capture is interrupted or a customer requests to pay later, Shuttle automatically sends a secure, branded payment link by SMS or chat -- continuing the same transaction in a digital channel. This means the payment experience never breaks. The customer simply switches from voice to link, with all context preserved. - No lost intent -- the customer is still mid-payment. - No re-entry of data -- the system already knows who they are and what they owe. - No additional integrations -- it's all powered by the same Payment Layer. The Psychology of Continuity Payment completion is about momentum. Once a customer has agreed to pay, every second counts. The longer the delay, the higher the abandonment rate. By providing a frictionless backup -- a link that arrives instantly when voice payment fails -- Shuttle keeps that momentum alive. It turns an interruption into a continuation, preserving trust and intent in the process. That's not just smart technology. It's human psychology, applied to commerce. One Payment Layer, Many Channels The brilliance of this approach is its simplicity. Shuttle's architecture treats voice, link, and chat as different doors into the same payment layer. Whether a customer pays via IVR, chatbot, or link, the underlying logic remains consistent: - Same merchant configuration - Same processor routing - Same PCI compliance boundaries - Same reporting and tokenisation framework This multi-channel parity is what makes Shuttle unique. It's not just a voice payments solution -- it's a platform for programmable payments across every conversational interface. When Voice Meets Digital In practice, the voice-link interplay creates a new kind of resilience in your customer experience. It allows every conversation -- no matter the channel -- to end with a completed payment. Consider these scenarios: - A customer speaking to an agent prefers to complete payment privately via SMS. - An AI voice bot offers a follow-up payment link if the call disconnects. - A debt recovery IVR transitions to link when tone recognition fails. Each time, Shuttle's Payment Layer ensures the flow continues -- without friction or compliance risk. Reducing PCI Scope, Increasing Conversion Every fallback reduces the chance of manual data handling and re-entry -- both of which increase PCI exposure. By centralising payments in Shuttle's compliant layer, you not only protect your business but also increase successful payment rates across channels. For most BPOs and contact centres, introducing link fallback improves conversion by 8-15% within the first quarter. That's measurable revenue recovered through continuity. Twilio-First Integration For teams already building on Twilio, Shuttle's Payment Links can be triggered directly from your IVR or contact-centre flows using simple API calls or Studio webhooks. No new infrastructure, no new compliance overhead -- just one more capability added to your voice stack. It's the fastest way to unify your voice and digital payment channels without disrupting your existing setup. Build Resilience Into Every Payment Journey Resilient customer experiences aren't just about uptime -- they're about continuity. Shuttle gives you that continuity by connecting voice, link, and chat into a single, intelligent payment fabric. So when the line goes silent, the payment doesn't. Learn more about Shuttle's IVR & Voice Payments and discover how fallback links can transform your contact-centre payment experience. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### White-Label Payment Links: Why Your Brand on the Checkout Matters ### QuickBooks Payment Links: Add a Pay Now Button to Any Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Talk to us Make enabling payments for your platform and merchant users easy. ## Links - [DTMF tones](/guides/dtmf-payments/) - [Learn more about Shuttle's IVR & Voice Payments](/platforms/voice-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideWhite-Label Payment Links: Why Your Brand on the Checkout Matters→](/guides/white-label-payment-links/) - [GuideQuickBooks Payment Links: Add a Pay Now Button to Any Invoice→](/guides/quickbooks-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/blog/xero-payment-links/ --- # Xero Payment Links: Collect Invoice Payments Faster | Shuttle > Add payment links to Xero invoices using your own gateway -- not just Stripe or GoCardless. White-label, multi-channel, 40+ providers. # Xero Payment Links: Collect Invoice Payments Faster By Shuttle Team, March 10, 2026 Add payment links to Xero invoices using your own gateway -- not just Stripe or GoCardless. White-label, multi-channel, 40+ providers. Talk to us Make enabling payments for your platform and merchant users easy. ## The Problem With Xero's Built-In Payment Options Xero lets you add a "Pay Now" button to invoices -- but only through Stripe or GoCardless. That's fine if you already use one of those providers and don't mind the limitations. But for many businesses, it creates problems: - You're locked to one gateway -- If you have a merchant account with Worldpay, Adyen, or another provider, you can't use it through Xero's built-in payments. You either switch providers or miss out on pay-now functionality. - No white-label branding -- The Stripe or GoCardless checkout page shows their branding, not yours. For professional services and B2B businesses where trust matters, this is a problem. - Limited payment methods -- Xero + Stripe gives you cards and Apple Pay. Xero + GoCardless gives you direct debit. You can't offer both from the same invoice without connecting both providers. - No SMS or WhatsApp delivery -- Xero sends invoices by email. If a customer ignores your email (and 80% of payment reminder emails go unread), you have no other channel. Payment links solve all of these problems without replacing Xero. ## How Payment Links Work With Xero A payment link is a unique URL that takes your customer to a hosted checkout page for a specific amount. You generate the link, add it to your Xero invoice, and the customer clicks through to pay. The key difference from Xero's built-in options: the payment link connects to your own payment gateway -- not Stripe or GoCardless. You keep your existing provider, your negotiated rates, and your merchant account. Here's the workflow: - Create your invoice in Xero as normal -- line items, tax, due date. - Generate a payment link for the invoice amount. Include the Xero invoice number as a reference. - Add the link to the invoice email -- paste it into the "Message" field or the invoice notes. You can format it as "Pay this invoice now: [link]". - Send the invoice from Xero -- the customer receives the invoice with a clickable payment link. - Customer pays -- they click through to a branded checkout page, choose their payment method, and pay. - Reconcile in Xero -- match the payment to the invoice using the reference number. For businesses sending more than 20-30 invoices per month, you can automate steps 2-3 using an API integration that generates a payment link automatically when a Xero invoice is created. ## What You Get That Xero Alone Doesn't Offer ### Use Any Payment Gateway Xero locks you to Stripe or GoCardless. Payment links work with 40+ gateways -- including Worldpay, Adyen, Square, Authorize.net, and more. If you've spent years building a relationship with your payment provider and have negotiated rates, you don't have to give that up to add a pay-now button. ### White-Label Checkout Pages When a customer clicks your payment link, they see your company name, logo, and colours -- not a third-party brand. This matters more than most people think. Customers are more likely to complete payment on a page that looks like it belongs to the business they're paying. See our guide on white-label payment links. ### Multiple Payment Methods on One Link A single payment link can offer cards, bank transfer, Apple Pay, Google Pay, and Open Banking -- all on the same checkout page. The customer picks what works for them. More choice means faster payment. See how payment choice reduces DSO. ### Multi-Channel Chasing When an emailed invoice goes unpaid, you can resend the same payment link via SMS, WhatsApp, or even print it as a QR code on a dunning letter. Xero only supports email. A multi-channel collection strategy typically doubles your first-touch payment rate. ### Automated Payment Reminders Set up automated payment reminder sequences that include the payment link. Day 1: invoice sent. Day 7: friendly email reminder with link. Day 14: SMS with link. Day 30: WhatsApp with link. Each message makes it easy to pay in one click. ## Xero Payment Links vs Paidnice vs Chaser If you're looking for Xero AR automation, you've probably come across Paidnice and Chaser. Here's how they compare to using payment links: Xero Built-In Payment Links (Shuttle) Gateway choice Stripe or GoCardless only Stripe only No payment processing 40+ gateways -- use your own White-label No (Stripe/GC branding) Yes -- your brand on checkout Payment methods Cards OR direct debit Cards only N/A (chasing only) Cards, bank, Apple Pay, Google Pay, Open Banking SMS/WhatsApp Email only Email, SMS, WhatsApp, QR Late fee automation No (invoicing software handles this) Credit checking Yes (via Creditsafe) Per transaction (Stripe/GC rates) From $15/mo + Stripe fees From £35/mo Per transaction (your gateway rates) The key difference: Paidnice and Chaser are AR automation tools that add features around Xero. Payment links are payment infrastructure -- they solve the "how does the customer actually pay" problem, which is the part that has the biggest impact on how fast you get paid. You can use Chaser or Paidnice for chasing and reminders, and use Shuttle payment links for the actual payment step. They're complementary, not competing. ## Setting It Up: Step by Step ### Quick Setup (Manual, 5 Minutes) - Sign up for a payment link provider that supports your gateway. Shuttle works with 40+ providers. - Create a payment link for your next invoice -- enter the amount, currency, and invoice number as a reference. - Copy the link and paste it into the Xero invoice email message field: "Pay this invoice securely: [paste link]" - Send the invoice from Xero as normal. This takes about 30 seconds extra per invoice. For businesses sending 10-20 invoices per month, that's all you need. ### Automated Setup (API, 30 Minutes) For higher volumes, use the payment link provider's API to auto-generate links when invoices are created in Xero: - Connect to Xero's API (or use a middleware like Zapier/Make). - Trigger: When a new invoice is created in Xero. - Action: Call the payment link API to generate a link with the invoice amount and reference. - Action: Update the Xero invoice notes field with the payment link URL. - Action: Send the invoice from Xero. This removes all manual work. Every invoice goes out with a pay-now link automatically. ## Common Questions ### Will this affect my Xero workflow? No. You still create, send, and manage invoices in Xero. The payment link is an addition, not a replacement. Your chart of accounts, reporting, and reconciliation all stay the same. ### Can I use this alongside Xero's Stripe integration? Yes. You can keep Stripe connected for customers who prefer cards, and add payment links for customers who want bank transfer, Open Banking, or a different payment method. The link is just a URL -- it doesn't interfere with anything else. ### How do I reconcile payments in Xero? When a customer pays via a payment link, the funds settle to your merchant account (via your chosen gateway). You reconcile in Xero the same way you do any bank transaction -- match it to the invoice using the reference number. Some payment link providers also offer webhook integrations that can auto-mark invoices as paid. ### What about direct debits? If you're collecting recurring payments (monthly retainers, subscription fees), GoCardless via Xero is still a good option for direct debit. Payment links are better suited for one-off invoice payments where the customer needs to actively pay. ## Get Started If Xero's built-in payment options are too limited -- wrong gateway, no branding, one payment method -- payment links give you everything Xero doesn't, without changing your workflow. Shuttle Payment Links connect to 40+ payment gateways, support white-label branding, and work across email, SMS, WhatsApp, and QR codes. See how it works. ## Related Reading Explore More ### Build vs Buy: Should Your Platform Build Its Own Payment Links? ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) ### Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments ### Payment Links for Method CRM: Collect Field Payments Without Card Terminals ### Payment Links for Property Management & Lettings Agencies ## Find the Right Payment Provider Compare payment gateways, merchant accounts, and more. We help you find the best deal, whether you're processing your first transaction or your millionth. ## Links - [Book a Call →](/discovery/) - [professional services](/guides/payment-collection-professional-services/) - [B2B businesses](/guides/b2b-payment-collection/) - [40+ gateways](/payment-providers/) - [Worldpay](/blog/payment-links-for-worldpay/) - [Adyen](/payment-providers/adyen/) - [Square](/blog/payment-links-for-square/) - [Authorize.net](/blog/payment-links-for-authorize-net/) - [white-label payment links](/guides/white-label-payment-links/) - [Open Banking](/blog/what-is-open-banking-and-pisp/) - [how payment choice reduces DSO](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [dunning letter](/blog/dunning-letter-templates/) - [multi-channel collection strategy](/guides/multi-channel-payment-collection/) - [payment reminder sequences](/blog/payment-reminder-email-templates/) - [Shuttle works with 40+ providers](/payment-providers/) - [40+ payment gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [GuideBuild vs Buy: Should Your Platform Build Its Own Payment Links?→](/guides/build-vs-buy-payment-links/) - [GuideInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/guides/invoice-payment-links/) - [GuideHubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)→](/guides/hubspot-payment-links/) - [GuidePayment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments→](/guides/payment-links-for-car-dealerships/) - [GuidePayment Links for Method CRM: Collect Field Payments Without Card Terminals→](/guides/payment-links-method-crm/) - [GuidePayment Links for Property Management & Lettings Agencies→](/guides/payment-links-property-management/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/brand/ --- # Brand Assets: Logos, Symbol & Guidelines | Shuttle > Download official Shuttle logos, symbol mark, and company description. Available in PNG and SVG, colour and white variants. Brand Assets # Shuttle Logo & Identity Download our official logos and symbol for use in press, partner materials, and integrations. Please use the assets as provided. Don't alter colours, proportions, or add effects. ## About Shuttle ### Short description Shuttle is the payment layer for software platforms and AI agents, providing embedded checkout, voice payments, and payment link infrastructure with PCI DSS Level 1 compliance built in. ### Full description Shuttle Global is the payment layer for software platforms and AI agents. Shuttle provides white-label embedded payments infrastructure (including checkout UI, voice checkout, payment links, and a full merchant management portal) so platforms can offer payments to their customers without building or maintaining their own payment stack. Shuttle connects to 40+ payment service providers globally, is PCI DSS Level 1 certified, ISO 27001 certified, and SOC 2 compliant. Founded in London, Shuttle powers payments for platforms across insurance, retail, hospitality, and professional services. ## Logos & Symbol Download official assets ### Full Logo: Colour Blue logo. Available on transparent or gold background. ### Full Logo: White White logo on transparent background. For use on dark or coloured surfaces. ### Symbol: Colour Blue symbol mark. Available on transparent or gold background. ### Symbol: White White symbol mark on transparent background. For use on dark or coloured surfaces. ## Brand Colours Shuttle Blue Shuttle Navy Shuttle Gold ## Usage Guidelines - Use the colour logo on light or white backgrounds - Use the white logo on dark or coloured backgrounds - Maintain clear space around the logo equal to the height of the symbol - Link back to shuttleglobal.com when using our logo ### Don't - Alter the logo colours or apply gradients - Stretch, rotate, or distort the logo - Place the colour logo on busy or low-contrast backgrounds - Recreate or approximate the logo using other typefaces ## Links - [Transparent PNG](/brand/shuttle-logo-colour.png) - [Gold PNG](/brand/shuttle-logo-gold.png) - [PNG](/brand/shuttle-logo-white.png) - [Transparent PNG](/brand/shuttle-symbol-colour.png) - [Gold PNG](/brand/shuttle-symbol-gold.png) - [PNG](/brand/shuttle-symbol-white.png) --- URL: https://www.shuttleglobal.com/de/platforms/ --- # Embedded Payments für Software-Plattformen | Shuttle > Binden Sie Zahlungen in Ihre Plattform ein, ohne PayFac zu werden. Shuttle vereint Design, Deployment, Entwicklung und Support in einer Zahlungsschicht. # Payment-Roadmap erledigt Für Software-Plattformen Ihre Plattform braucht eine Zahlungsschicht, die mitwächst - kein 12-monatiges Bauprojekt. Shuttle liefert alles, um Zahlungen über jeden Kanal einzubinden, ohne PayFac zu werden oder die Kontrolle zu verlieren. ## Führende Plattformen vertrauen darauf ## Das Problem Ihre Plattform wächst, doch Zahlungen bremsen Sie aus. Enterprise-Kunden verlangen eingebettete Zahlungsfunktionen, Ihr Produktteam ertrinkt in PSP-Integrationen, und jeder Monat ohne Lösung ist liegen gelassener Umsatz. ## Warum Plattformen zu Shuttle kommen - Enterprise-Deals verlangen plötzlich bestimmte PSPs Sie einzeln anzubinden sprengt die Roadmap. - Eingebettete Zahlungen werden unvermeidbar PayFac zu werden bringt Risiko, Compliance und operativen Ballast mit sich. - Zahlungen sickern in Produktgespräche ein Shuttle nimmt diesen Druck - ohne Plattformen zu Kompromissen zu zwingen, die sie später bereuen. Nichts zu tun ist ebenfalls eine Entscheidung - und sie zeigt sich meist als verlorene oder verzögerte Deals. ## Warum Plattformen mit Zahlungen kämpfen Schmerzpunkte ### Enterprise-Deals verlangen PSPs Ihre wichtigsten Interessenten fordern Zahlungsfunktionen, die Sie nicht haben. Jeder verlorene Deal ist Umsatz, den stattdessen Ihre Wettbewerber einsammeln. ### Eingebettete Zahlungen sind unvermeidbar Ihre Nutzer erwarten Zahlungen direkt im Workflow, keine Weiterleitung zu Dritten. Die Plattformen, die Zahlungen einbetten, gewinnen den Markt. ### Zahlungen dringen ins Produkt ein Ihr Produktteam beantwortet Zahlungsfragen. Ihre Roadmap wird von PSP-Integrationen gekapert. Zahlungen verschlingen Ressourcen, die für Ihr Kernprodukt gedacht sind. ## Eine Zahlungsschicht, vier Säulen Die Shuttle-Lösung ### Design White-Label-Checkout- und Händlererlebnisse passend zu Ihrer Marke. Ihre Nutzer erfahren nie, dass es Shuttle gibt. ### Bereitstellung In Wochen live, nicht in Monaten. Vorgefertigte Komponenten und gemanagte Infrastruktur lassen Ihr Team sich auf das Produkt konzentrieren, nicht auf die technische Komplexität der Zahlungen. ### Entwicklung RESTful-APIs, SDKs und Webhooks für Plattformteams. Erweitern und individualisieren Sie jeden Aspekt des Zahlungserlebnisses. ### Support Dedizierte Success Manager, Händlersupport und Compliance-Expertise. Shuttle hält die eigene PCI-DSS-Level-1-Zertifizierung und verfolgt regulatorische Änderungen, damit Ihr Scope begrenzt bleibt. ## Für Multi-Tenant-Plattformen, Single-Tenant und On-Premises ### Multi-Tenant Geteilte Infrastruktur, isolierte Daten ### Single-Tenant Dedizierte Instanz pro Kunde ### On-Premises Selbst gehostet, volle Datenhoheit ## Warum Plattformen sich für Shuttle entscheiden ### Stärkere Plattformbindung Händler, die über Ihre Plattform bezahlen, bleiben. Zahlungen werden zum Kleber, der Kunden hält. ### Höherer Vertragswert Eingebettete Zahlungen erhöhen den durchschnittlichen Vertragswert bei Enterprise-Deals durch eine zusätzliche Zahlungsposition. ### Weniger Abwanderung Beseitigen Sie den häufigsten Grund, warum Plattformen Händler an Wettbewerber verlieren: fragmentierte Zahlungserlebnisse. ### Begrenzter PCI-Scope Kartendaten gehen direkt an das Gateway und berühren Ihre Plattform nie, Ihr PCI-Scope bleibt minimal. Shuttle hält PCI DSS Level 1, SOC 2 Type 2 und ISO 27001. ### Schnellere Markteinführung Liefern Sie die Zahlungsfunktionen, die Ihr Vertrieb längst verspricht. In Wochen, nicht in Quartalen. ## Die Plattform-Komponenten Das bekommen Sie ### Onboarding Eine einbettbare Komponente, mit der Händler ihre bevorzugten Zahlungsabwickler durchsuchen, auswählen und verbinden - mit integrierter OAuth- oder API-Key-Authentifizierung. - Über 40 Zahlungsabwickler per Ein-Klick-Verbindung - OAuth- und API-Key-Authentifizierung - Länderspezifisch gefilterte Verfügbarkeit der Abwickler - Betrugsprävention & 3D-Secure-Konfiguration ### Checkout Ein einbettbares Zahlungsformular als iFrame in Ihrem Produkt. Unterstützt Karten, Wallets und lokale Zahlungsmethoden - vollständig im Händler-Branding. - Inline- oder Modal-Darstellung - Karten, Wallets & lokale Zahlungsmethoden - PCI DSS Level 1 konform ### Express Checkout Zeigen Sie Express-Zahlungsmethoden wie Apple Pay, Google Pay und PayPal direkt im Checkout. Wallet-Buttons erscheinen automatisch, wenn ein verbundener Abwickler Network-Tokens unterstützt. - Apple-Pay- & Google-Pay-Wallet-Buttons - PayPal, Affirm & Buy-Now-Pay-Later - Einbettbare BNPL-Werbebotschaften jedes Anbieters - Lädt im obersten Frame für nativen Wallet-Zugriff ### Händler-Aktivitätsansicht Geben Sie Händlern Echtzeit-Einblick in Transaktionen, Auszahlungen und Zahlungsperformance über eine einbettbare Dashboard-Komponente. - Transaktionsliste mit Filtern & Suche - Konto- & Kundenverwaltung - Überwachung geplanter Zahlungen - Exportierbare Berichte ### Händlerportal Ein White-Label-Portal, das Händler eigenständig nutzen, um Zahlungen zu verwalten, Berichte einzusehen, Rückerstattungen abzuwickeln und Einstellungen zu konfigurieren. - Mehrstufige Organisationsstruktur - Konfiguration & Regeln der Zahlungsabwickler - Teamverwaltung mit rollenbasiertem Zugriff - Modulare App-Marketplace-Architektur ### Übersetzungen Die einbettbaren Komponenten von Shuttle lassen sich in jede Sprache übersetzen: Checkout auf Deutsch, Onboarding auf Japanisch oder Express-Zahlungen auf Portugiesisch. - Einbettbare Komponenten in jede Sprache übersetzen - Ihre Plattform, Ihre Sprache Die Zahlen ## Warum Shuttle statt Eigenbau Eine Zahlungsinfrastruktur zu bauen ist teuer, komplex und langsam. Shuttle beseitigt alle drei. Durchschnittliche jährliche Ersparnis pro Plattform gegenüber dem Aufbau und Betrieb einer eigenen Zahlungsinfrastruktur. Typische Kosten für das Erreichen und Aufrechterhalten der PCI-DSS-Level-1-Zertifizierung. Shuttle hält sie bereits, Ihre Plattform baut sie nicht. Durchschnittlich eingesparte Entwicklungszeit mit Shuttle gegenüber dem Bau von Zahlungsintegrationen von Grund auf. ## Einfache, transparente Preise PCI-konforme Zahlungen über jeden Sprachkanal - Twilio Pay - IVR, menschlicher Agent & KI-Agent - PCI-konforme Sprach-Erfassung - Kostenlose 30-Tage-Sandbox-Testphase, dann 245 Transaktionen inklusive, ab $0.20 pro Transaktion - Weitere Carrier folgen in Kürze Zahlungslinks per SMS, E-Mail oder Chat senden - Gebrandete Zahlungslinks - Versand per SMS, E-Mail & Chat - Echtzeit-Zahlungsverfolgung Vollständige White-Label-Zahlungsinfrastruktur - Beliebig viele Kanäle und Instanzen, keine Gebühren pro App - Teamverwaltung mit rollenbasierten Rechten - White-Label-Checkout & -Portal Vollständigen Funktionsvergleich ansehen ## Bereit, Zahlungen einzubinden? Sprechen Sie mit unserem Plattform-Team und sehen Sie, wie Shuttle Sie in Wochen statt Monaten live bringt. ## Links - [Termin buchen](/discovery/) - [Jetzt Shuttle nutzen](/discovery/) - [Mehr erfahren](/platforms/voice-checkout/#pricing) - [Mehr erfahren](/de/platforms/links-checkout/) - [Sprechen Sie uns an](/discovery/) - [Vollständigen Funktionsvergleich ansehen](/pricing/) --- URL: https://www.shuttleglobal.com/de/platforms/links-checkout/ --- # Payment Links für Plattformen: ohne Code | Shuttle > Starten Sie Zahlungslinks für Ihre Händler ohne Integrationsaufwand. Verbinden Sie 40+ Zahlungsdienste, gebrandete Checkout-Seiten und Echtzeit-Tracking. PCI DSS Level 1. # Payment Links für Plattformen Integration ohne Code verfügbar Für Multi-Tenant-Software-Plattformen, die Zahlungsanbindung und -funktionen bereitstellen müssen. Kein Checkout-Umbau. Kein „Connect"-Aufwand. Keine neuen PSP-Verträge. ## Vertraut von ## Die Chance Sie wollen gar nichts tun? Wir übernehmen alles mit unserem White-Glove-Programm. Oder Sie integrieren über unsere API bzw. No-Code-Connectoren und starten in Tagen. ## Das bekommen Sie Plattform-Funktionen ### Zahlungsanbindung Jeder Händler verbindet seinen Zahlungsanbieter selbst aus der Liste von Shuttle, in einer UX-Komponente, ganz ohne Entwicklung auf Plattformseite. ### Checkout-Seiten Händler gestalten eigene Checkout-Seiten, gerendert über die Shuttle-Checkout-Komponente, mit eigener Botschaft und eigenem Branding. ### Sichtbarkeit Echtzeit-Transaktionsverlauf und Live-Checkout-Monitoring zeigen die Aktivität der Zahlungslinks. ## Wählen Sie Ihren Integrationsweg Integrationsoptionen Schnelle Integration über die API von Shuttle. Shuttle stellt UX-Komponenten bereit und übernimmt die PCI-Konformität. Verbinden über Workflow-Engines: Cyclr, Make.com und Zapier. Shuttle stellt UX-Komponenten bereit und übernimmt die PCI-Konformität. Ein vollständig gemanagtes Launch-Programm ohne Integration. Wir scopen, gestalten, konfigurieren und betreiben die Zahlungslink-Automatisierung für jeden Händler. ## Für Ihre Branche gemacht Branchenlösungen ### Reise-Software Buchungsmaschinen, Channel-Manager und PMS. Fügen Sie jedem Buchungsflow Zahlungslinks hinzu. ### Rechnungs-Software Verbessern Sie den Cashflow Ihrer Kunden und die Back-Office-Effizienz mit Ein-Klick-Zahlungslinks auf jeder Rechnung. ### Inkasso Beharrlichkeit und Komfort erhöhen die Einzugsquote. Versenden Sie Zahlungslinks per SMS und E-Mail in großem Umfang. ### Formular-Builder Fügen Sie den Zahlungseinzug bei der Formularübermittlung hinzu, ohne eigenen Checkout. ### CX-Plattformen Vervollständigen Sie das Zahlungserlebnis direkt in Kundengesprächen, für mehr Zufriedenheit und Conversion. ### Außendienst-Software Agenten kassieren vor Ort per Zahlungslink, ganz ohne manuelle Nachverfolgung. ### Chatbot-Software Ermöglichen Sie Transaktionsabschlüsse und Upsells in automatisierten Chat-Flows. ### CRM-Software Erweitern Sie Ihr Customer-Engagement-Center um Zahlungsfunktionen. Machen Sie aus CRM-Aktionen Umsatz. ## Smarte Zahlungslinks Funktionen Ein Link. Jede Zahlungsmethode. Karte, Open Banking (UK), ACH (US), alles in einem. ### Echtzeit-Tracking Kennen Sie Status, Zeitpunkt und Methode jeder Zahlung. Beseitigt den Abstimmungsaufwand. ### Low-Code-Integration Lösen Sie Links über CRM, ERP oder Messaging-Tools mit Zapier und Make.com aus. ### Gebrandeter Checkout Eigene Domain, Logo, Kundenname und vorausgefüllte Rechnungsdaten auf jeder Checkout-Seite. ### Enterprise-Sicherheit PCI DSS Level 1, SOC 2 und ISO 27001: die höchsten Zertifizierungen der Zahlungssicherheit. ### Multi-PSP-App-Store Händler verbinden ihren eigenen Anbieter aus über 40 Diensten. Keine neuen PSP-Verträge nötig. ## Plattform-Dashboard Sichtbarkeit & Kontrolle ### Checkout-Monitor Echtzeit-Einblick in laufende Zahlungen. Agenten können hängengebliebenen Kunden helfen, indem sie den Checkout-Fortschritt beobachten. ### Link-Generator Erstellen Sie Vorlagen für eine konsistente Link-Generierung. Mehrere Generatoren decken verschiedene Szenarien und Händlertypen ab. ### Link-Branding Vertrauenswürdige Zahlungserlebnisse mit eigenem Branding, eigenen Botschaften und eigenen URLs für jeden Händler. ## Funktioniert mit Ihren Tools Integrationen ### Jede Software-Plattform Nutzen Sie den Link-Generator eigenständig mit jeder Software. Teilen Sie Zahlungslinks per SMS, E-Mail oder Chat. ### AWS Connect Betten Sie die Zahlungslink-Erstellung direkt in die Amazon-Connect-Agent-Workspaces ein. ### Xero Fügen Sie Xero-Rechnungen Zahlungslinks hinzu. Betrag und Rechnungsnummer werden automatisch vorausgefüllt. ### Deep Embed Betten Sie den Link-Generator direkt in Ihre Plattform ein. In Stunden einsatzbereit. ## In Aktion sehen ### Selbst ausprobieren Sie können in diesem Test beliebige Daten eingeben, es wird keine Zahlung ausgelöst. Erleben Sie das vollständig gebrandete Checkout-Erlebnis, das Ihre Händler bieten können. Kartennummer: 4242 4242 4242 4242 Ablaufdatum: 11/27 ### Mehrere Zahlungsmethoden Karte, Open Banking, ACH: Kunden wählen, wie sie zahlen möchten. Gespeicherte Zahlungsmethoden lassen wiederkehrende Kunden in Sekunden zahlen. ### Echtzeit-Aktivität Überwachen Sie jede Transaktion aller Händler in Echtzeit. Status, Beträge, Methoden und Zeitpunkt, mit vollständigem Audit-Trail für jede Transaktion. ## Das komplette Produkt im Überblick Produkttour ## Compliance auf Enterprise-Niveau ### PCI DSS Level 1 Höchste Zertifizierungsstufe für Kartensicherheit. Kartendaten berühren weder Ihre Systeme noch die Ihrer Händler. ### ISO 27001 Internationaler Standard für das Management der Informationssicherheit ### SOC 2 Auditierte Kontrollen für Sicherheit, Verfügbarkeit und Vertraulichkeit > Ohne Shuttle hätten wir unseren Enterprise-Kunden Zahlungslink-Funktionen niemals so schnell und mit so großer Sicherheit liefern können ## Einfache, transparente Preise Für Plattformen mit Entwicklerressourcen - Mehrere Händler - Eigene Zahlungsseiten - Eigene URLs - PCI-Konformität übernommen - Entwicklerdoku & SDKs No-Code über Zapier, Make.com, Cyclr - Gleiche API-Funktionen - Zapier- & Make.com-Connectoren - Cyclr-Integrations-Engine - Kein Entwickler nötig - Vorlagenbibliothek - Geführte Einrichtung Vollständig gemanagtes Programm - Alles aus Workflow - Managed Service - Scoping & Design - Händler-Onboarding - Dedizierter Account Manager - Individuelle Automatisierung ## Häufig gestellte Fragen **Warum Zahlungslinks statt eingebettetem Checkout?** Links nutzen Kanäle, in denen Ihre Kunden bereits aktiv sind (E-Mail, SMS, Chat) und erfordern kaum Frontend-Änderungen. Einen eingebetteten Checkout können Sie später ohne Schwung­verlust ergänzen. **Auf welche Zahlungsanbieter können Händler zugreifen?** Shuttle unterstützt über 40 Zahlungsdienste, darunter Adyen, Authorize.net, CardConnect, Checkout.com, Global Payments, Moneris, NMI, Opayo, PayPal, PaySafe, PayU, Stripe, USAePay, Worldpay und viele mehr. Jeder Händler verbindet seinen bestehenden Anbieter selbst. **Müssen wir die PCI-Konformität übernehmen?** Kartendaten verbleiben auf den von Shuttle gehosteten Seiten und erreichen Ihre Plattform nie, sodass Ihr PCI-Scope begrenzt bleibt. Sie validieren weiterhin Ihre eigene Konformität, aber auf einer deutlich leichteren Basis. Shuttle ist PCI DSS Level 1 zertifiziert. **Werden SCA und 3D Secure unterstützt?** Ja. Shuttle verwaltet alle SCA- und 3D-Secure-Prozesse automatisch über alle unterstützten Gateways. **Wie funktionieren Rückerstattungen und Disputes?** Rückerstattungen lassen sich in der Händleransicht per Klick auslösen oder programmatisch über die API bzw. die Workflow-Engine. **Können Händler die Checkout-Seiten white-labeln?** Ja. Händler können die Seiten mit Logo, Farben und Botschaften branden und eigene URLs nutzen. Für vollständig eingebettete Zahlungen sprechen Sie den Vertrieb auf die Plattform-Lösung an. ## Bereit, Zahlungslinks zu starten? Sprechen Sie mit unserem Team über Zahlungslink-Funktionen für Ihre Plattform. Vom No-Code-Connector bis zur vollen API-Integration finden wir die passende Lösung. ## Links - [Entwicklerdoku ansehen](https://docs.shuttleglobal.com) - [Leitfaden ansehen](/platforms/links-checkout/workflows/) - [Termin buchen](/discovery/?product=payment-links) - [Jede Software-Plattform Nutzen Sie den Link-Generator eigenständig mit jeder Software. Teilen Sie Zahlungslinks per SMS, E-Mail oder Chat.](https://docs.shuttleglobal.com/docs/works-with-generic) - [AWS Connect Betten Sie die Zahlungslink-Erstellung direkt in die Amazon-Connect-Agent-Workspaces ein.](https://docs.shuttleglobal.com/docs/works-with-aws-connect) - [Xero Fügen Sie Xero-Rechnungen Zahlungslinks hinzu. Betrag und Rechnungsnummer werden automatisch vorausgefüllt.](https://docs.shuttleglobal.com/docs/works-with-xero) - [Deep Embed Betten Sie den Link-Generator direkt in Ihre Plattform ein. In Stunden einsatzbereit.](https://docs.shuttleglobal.com/docs/works-with-integration-guide) - [Loslegen](/discovery/?product=payment-links) --- URL: https://www.shuttleglobal.com/de/platforms/voice-checkout/ --- # Voice Checkout für Plattformen: Sprachzahlungen über jedes Gateway | Shuttle > Ergänzen Sie Ihre Plattform um PCI-konforme Sprachzahlungen. Eine Integration abstrahiert über 30 Gateways und Ihren Carrier - mit mandantenfähiger Kontrolle über jeden Händler. PCI DSS Level 1. # Voice Checkout Eine Sprach-Zahlungsschicht über jedem Gateway und Carrier Geben Sie jedem Händler auf Ihrer Plattform PCI-konforme Telefonzahlungen, ohne für jedes Gateway eine neue Integration zu bauen. Shuttle abstrahiert über 30 Gateways und Ihren Carrier hinter einer Integration und lässt Sie die Zahlungsaktivität jedes Händlers über eine einzige Steuerungsebene verwalten. Kartendaten berühren nie Ihre Systeme. ## Voice Checkout in Aktion Der Kunde zahlt per IVR. DTMF-Töne werden entfernt, bevor sie den Agenten oder Ihre Systeme erreichen. Der Agent bleibt in der Leitung, während der Kunde seine Kartendaten sicher eingibt. ## Vertraut von ## Das Problem Sprachzahlungen in Ihr Produkt zu integrieren bedeutet, Kartendaten zu verarbeiten, die PCI-Verantwortung zu tragen und für jedes von Ihren Händlern gewünschte Gateway eine eigene Integration zu bauen. Pro Händler und pro Gateway hört diese Arbeit nie auf. ## So funktioniert Voice Checkout Drei Schritte - Der Kunde ruft Ihr Unternehmen an Der Kunde erreicht Ihr IVR-System, spricht mit einem Agenten oder interagiert mit einem KI-Agenten. Zum Bezahlen tritt Shuttle nur für das sichere Erfassungssegment in den Anruf ein. - Shuttle erfasst die Zahlung sicher Der Kunde gibt seine Kartendaten über die Tastatur (DTMF) ein. Die Töne werden aus dem Audio entfernt, sodass der Agent sie nie hört. Alternativ wird ein Zahlungslink per SMS oder E-Mail gesendet - mit Wallet-Unterstützung. - Die Zahlung wird über Ihr Gateway verarbeitet Shuttle leitet die Transaktion an das von Ihnen gewählte Gateway, tokenisiert die Karte für die spätere Nutzung oder autorisiert für eine spätere Erfassung. Nur maskierte Daten werden zurückgegeben - Ihre Systeme sehen nie sensible Daten. ## Sofort einsatzbereiter Funktionsumfang Funktionen ### Vorgefertigter Checkout Checkout, Gateway-Connector und Payment-UI sofort einsatzbereit zur Integration in Ihre Sprach-Flows. ### IVR-kompatibel Funktioniert mit automatisierten IVR-Systemen und agentengestützten Anrufen. Erfassen Sie Zahlungen per DTMF-Tastatur. ### Keine Kartendaten gespeichert Kartendaten berühren nie Ihre Infrastruktur. Shuttle tokenisiert die Karte bei Ihrem Gateway, sodass Ihr PCI-Scope begrenzt bleibt. ### Zahlungslinks per SMS Wenn die Telefonzahlung nicht möglich ist, senden Sie per SMS einen sicheren Zahlungslink, den der Kunde auf seinem Gerät abschließt. ### Über 30 Payment-Gateways Verbinden Sie Ihren bevorzugten Payment-Stack. Unterstützung für Stripe, Worldpay, Adyen, Checkout.com und mehr, mit Multi-Gateway-Konfiguration. ### Echtzeit-Aktivität Sehen Sie Zahlungsaktivität ein, erstatten Sie ganz oder teilweise und verwalten Sie mehrere Zahlungsprofile über ein einziges Dashboard. ### Tokenisieren & wiederverwenden Tokenisieren Sie Zahlungsmittel während eines Anrufs und autorisieren Sie Kartendaten für jeden Kanal: Web, Mobil oder Sprache. ### Smarte Checkout-Profile Betreiben Sie mehrere Zahlungsprofile mit unterschiedlichen Gateway-Konfigurationen. Wählen Sie, welches Gateway welchen Zahlungstyp verarbeitet. ### Keine Einrichtungsgebühren Keine Einrichtungsgebühren und keine versteckten Kosten. Preise und Mengenstaffeln unter /pricing/. ### DTMF-Sicherheit Bei der sicheren Kartenerfassung werden DTMF-Töne aus dem Audiostream entfernt, sodass der Agent nie Kartendaten hört. Der Sprachkanal bleibt für das Gespräch offen. ### Tokenisieren & autorisieren Tokenisieren Sie Zahlungsdaten für später, autorisieren und erfassen Sie später oder verarbeiten Sie sofort - für Einmalzahlungen, Pre-Auth-Holds und wiederkehrende Szenarien. ### Agenten-Zahlungsoberfläche Echtzeit-Agent-Assist-UI zum Erstellen und Senden von Zahlungslinks während Live-Anrufen. Felder vorausfüllen, Zahlungen auslösen und Status verfolgen, ohne das Gespräch zu verlassen. ## Carrier-Connectoren Sprachkanäle Shuttle verbindet Twilios Sprach- und Chat-Flows mit über 30 Zahlungs-Gateways. Shuttle funktioniert heute mit Twilio, und mit jedem Carrier in Kürze. ## Akzeptierte Zahlungsmethoden Zahlungsmethoden ### Karten Visa, Mastercard, Amex und mehr, sicher per DTMF-Tastatur während des Anrufs erfasst - mit Echtzeit-BIN-Prüfung und Luhn-Check. ### ACH & Banküberweisungen Akzeptieren Sie ACH (US), BACS und Lastschrift (UK) mit Bankleitzahl-Prüfung, um Bankdaten in Echtzeit zu bestätigen. ### Zahlungslinks & Wallets Senden Sie während oder nach dem Anruf einen gebrandeten Zahlungslink per SMS oder E-Mail. Unterstützt Apple Pay, Google Pay und PayPal. Kunden schließen auf ihrem Gerät mit ihrem bevorzugten Wallet ab. ## Unterstützte Payment-Gateways ## Compliance auf Enterprise-Niveau ### PCI DSS Level 1 Höchste Zertifizierungsstufe für Kartensicherheit. Die Kartendaten Ihrer Kunden berühren nie Ihre Systeme. ### ISO 27001 Internationaler Standard für das Management der Informationssicherheit ### SOC 2 Auditierte Kontrollen für Sicherheit, Verfügbarkeit und Vertraulichkeit > Mit Shuttle konnten wir etablierte Zahlungsanbieter wie einen modernen SaaS-Dienst behandeln. So konnten wir die von unseren Kunden geforderten Gateways unterstützen und hochwertige Transaktionen in regulierten Branchen vollständig automatisieren. ## Einfache, transparente Preise Schnellstart über Twilio Marketplace Abrechnung über Twilio - Installation aus dem Twilio Marketplace - Abrechnung über Ihr Twilio-Konto - PCI-konforme Sprach-Zahlungserfassung - Echtzeit-Transaktionsreporting - Demo-App-Code & Blueprint inklusive - Go-live-Checkliste & Zertifizierung Volle Kontrolle - KI-Sprach- und menschliche Agentenunterstützung - Granulare Erfassungs-API auf Feldebene - Agent-UX & Payment-Builder - Tokenisierung mit Ihrem Gateway - Multi-Währung & Multi-Gateway Installation über Shuttle Checkout - Kostenlose 30-Tage-Sandbox-Testphase - Merchant-Portal-Konto inklusive - Transaktionen pro Monat inklusive - Volle $49/Monat zurück als Guthaben, einlösbar zum Staffelpreis (nicht für von Twilio abgerechnete Nutzung) - Ab $0.20 pro Transaktion, sinkend mit dem Volumen - Teamverwaltung mit rollenbasierten Rechten - Gebrandeter Checkout mit eigener Domain - Links Checkout App für $49/Monat hinzufügen Sie entwickeln ein mandantenfähiges Produkt für Ihre eigenen Händler? Das ist unser Embedded Payment Layer, bei dem Sie beliebig viele Kanäle und Instanzen betreiben, ohne Gebühren pro App. ## Häufig gestellte Fragen **Was ist Shuttle Voice Checkout?** Shuttle Voice Checkout verbindet Ihre Sprach- und Chat-Flows mit führenden Zahlungsabwicklern wie Worldpay, Checkout.com, Opayo und Stripe, ohne dass Sie Kartendaten verarbeiten. Kunden zahlen sicher per Tastatur (DTMF) oder per SMS gesendetem Zahlungslink. **Welche Payment-Gateways werden unterstützt?** Shuttle unterstützt über 30 Gateways, darunter ACI Speedpay, Adyen, Authorize.Net, BS Pay One, CardConnect, Checkout.com, Cybersource, Ecommpay, FatZebra, Fortis, FreedomPay, Global Payments, GoCardless, Liqpay, Moneris, NAB, NMI, Opayo/Elavon, PaySafe, QuickBooks Payments, Stripe, Trust Payments, USAePay, Worldpay Access und Xendit, unter anderem. **Welche Zahlungsmethoden werden unterstützt?** Karten (Visa, Mastercard, Amex), ACH-Banküberweisungen und weitere Zahlungsmethoden über gebrandete, per SMS gesendete Zahlungslinks. **Welche PCI-Compliance-Pflichten habe ich?** Shuttle ist PCI DSS Level 1 konform. Da Kartendaten nie Ihre Systeme berühren, sind Ihre PCI-Pflichten deutlich reduziert. Ihre eigene Selbstbewertung führen Sie weiterhin selbst durch. **Wie lange dauert die Einrichtung?** Mit einem Demo-Skript sind Sie innerhalb von Stunden startklar. Eine maßgeschneiderte Einrichtung ist mit einem Entwickler meist innerhalb einer Woche abgeschlossen. **Welche Sprach-Carrier werden unterstützt?** Heute ist Twilio der Live-Connector. Shuttle funktioniert heute mit Twilio, und mit jedem Carrier in Kürze. **Was ist der Unterschied zwischen dem Shuttle-Connector und einem generischen Connector auf Twilio?** Auf Twilio ist der Shuttle-Connector vorgefertigt und für bestimmte Abwickler optimiert - mit durchgängiger Payment-Orchestrierung, produktionsreifem Monitoring und Multi-Merchant-Management. Der generische Connector ist Twilios leichtgewichtiger, offener Connector, bei dem Sie die PSP-Integration selbst übernehmen - nützlich für individuelle Anbieter und Tests. ## Bereit für Sprachzahlungen? Sprechen Sie mit unserem Team und sehen Sie, wie Shuttle Voice Checkout Sie in Tagen statt Monaten Telefonzahlungen annehmen lässt. ## Links - [Mehr erfahren →](/integrations/twilio-pay/) - [Jetzt installieren](https://merchant.shuttleglobal.com/signup/twilio) - [Sprechen Sie uns an](/discovery/) - [Loslegen](https://merchant.shuttleglobal.com/) - [Embedded Payment Layer](/de/platforms/) - [Termin buchen](/discovery/) --- URL: https://www.shuttleglobal.com/discovery/ --- # Shuttle | Book a Discovery Call > See how Shuttle can deliver payments fast. Book a call to discuss your payments roadmap and go-to-market strategy. ### A discovery call will help you: - ✓ Accelerate your go-to-market with embedded payments - ✓ Deliver effectively on your payments roadmap Please note that our calls are for our Shuttle payments platform only. > "Partnering with Shuttle enables us to deliver consistent workflows for our customers, making the process of managing payments simple, regardless of payment processor or channel." Scott Hill, VP Product at Brightpearl --- URL: https://www.shuttleglobal.com/es/platforms/ --- # Plataforma de pagos integrados para software | Shuttle > Integra los pagos en tu plataforma sin convertirte en PayFac. Shuttle reúne diseño, despliegue, desarrollo y soporte en una sola capa de pagos. # Tu hoja de ruta de pagos, resuelta Para plataformas de software Tu plataforma necesita una capa de pagos que escale contigo, no un proyecto de 12 meses. Shuttle te da todo lo necesario para integrar pagos en cualquier canal, sin convertirte en PayFac ni perder el control. ## La confianza de las plataformas líderes ## El problema Tu plataforma crece, pero los pagos te frenan. Los clientes corporativos exigen capacidades de pago integradas, tu equipo de producto se ahoga en integraciones de PSP y cada mes sin solución son ingresos que dejas sobre la mesa. ## Por qué las plataformas eligen Shuttle - Los grandes acuerdos empiezan a exigir PSP concretos Integrarlos uno a uno rompe la hoja de ruta. - Los pagos integrados se vuelven inevitables Convertirse en PayFac introduce riesgo, cumplimiento y carga operativa. - Los pagos se filtran en las conversaciones de producto Shuttle existe para quitar esa presión, sin obligar a las plataformas a concesiones que lamentarán después. No hacer nada también es una decisión, y suele manifestarse como acuerdos perdidos o retrasados. ## Por qué las plataformas sufren con los pagos Puntos de dolor ### Grandes acuerdos que exigen PSP Tus mejores prospectos piden capacidades de pago que no tienes. Cada acuerdo perdido son ingresos que capta tu competencia. ### Los pagos integrados son inevitables Tus usuarios esperan pagos integrados en su flujo de trabajo, no una redirección a un tercero. Las plataformas que integran pagos ganan el mercado. ### Los pagos invaden el producto Tu equipo de producto atiende dudas de pagos. Tu hoja de ruta queda secuestrada por integraciones de PSP. Los pagos consumen recursos destinados a tu producto principal. ## Una capa de pagos, cuatro pilares La solución Shuttle ### Diseñar Experiencias de checkout y de comercio en marca blanca, fieles a tu marca. Tus usuarios nunca saben que Shuttle existe. ### Desplegar Lanza en semanas, no en meses. Los componentes prediseñados y la infraestructura gestionada permiten a tu equipo centrarse en el producto, no en la complejidad técnica de los pagos. ### Desarrollar API REST, SDK y webhooks pensados para equipos de plataforma. Extiende y personaliza cada aspecto de la experiencia de pago. ### Dar soporte Gestores de éxito dedicados, soporte al comercio y experiencia en cumplimiento. Shuttle mantiene su propia certificación PCI DSS nivel 1 y sigue los cambios regulatorios, para que tu alcance siga siendo mínimo. ## Para plataformas multitenant, single-tenant y on-premise Despliegue ### Multitenant Infraestructura compartida, datos aislados ### Single-tenant Instancia dedicada por cliente ### On-premise Autoalojado, plena soberanía de los datos Beneficios ### Mayor fidelización Los comercios que pagan a través de tu plataforma no se van. Los pagos se convierten en el pegamento que retiene a los clientes. ### Mayor valor de contrato Los pagos integrados aumentan el valor medio de los contratos corporativos al añadir una línea de pagos. ### Menos abandono Elimina la principal razón por la que las plataformas pierden comercios ante la competencia: experiencias de pago fragmentadas. ### Alcance PCI limitado Los datos de tarjeta van directamente a la pasarela y nunca tocan tu plataforma, así que tu alcance PCI se mantiene mínimo. Shuttle mantiene PCI DSS nivel 1, SOC 2 Type 2 e ISO 27001. ### Salida al mercado más rápida Lanza las funciones de pago que tu equipo comercial ya promete. En semanas, no en trimestres. ## Los componentes de la plataforma Lo que obtienes ### Incorporación Un componente integrable que permite a los comercios explorar, seleccionar y conectar sus procesadores de pago preferidos, con autenticación OAuth o por clave API incluida. - Más de 40 procesadores con conexión en un clic - Flujos de autenticación OAuth y por clave API - Disponibilidad de procesadores filtrada por país - Prevención del fraude y configuración 3D Secure ### Checkout Un formulario de pago listo para integrar, mostrado como iFrame dentro de tu producto. Admite tarjetas, wallets y métodos de pago locales con la marca del comercio. - Modos de visualización en línea o modal - Tarjetas, wallets y métodos de pago locales - Conforme con PCI DSS nivel 1 ### Express Checkout Muestra métodos de pago exprés como Apple Pay, Google Pay y PayPal directamente en tu flujo de pago. Los botones de wallet aparecen automáticamente cuando un procesador conectado admite network tokens. - Botones de wallet Apple Pay y Google Pay - Opciones PayPal, Affirm y pago a plazos - Mensajes promocionales BNPL integrables de cada proveedor - Se carga en el frame superior para acceso nativo a wallets ### Vista de actividad del comercio Ofrece a los comercios visibilidad en tiempo real de transacciones, liquidaciones y rendimiento de pagos mediante un panel integrable. - Lista de transacciones con filtros y búsqueda - Gestión de cuentas y clientes - Supervisión de pagos programados - Informes exportables ### Portal del comercio Un portal en marca blanca que los comercios usan de forma autónoma para gestionar pagos, ver informes, tramitar reembolsos y configurar sus ajustes. - Estructura organizativa multinivel - Configuración y reglas de procesadores de pago - Gestión de equipos con acceso por roles - Arquitectura modular de marketplace de apps ### Traducciones Los componentes integrables de Shuttle se pueden traducir a cualquier idioma: tu checkout en alemán, la incorporación en japonés o los pagos exprés en portugués. - Traduce los componentes integrables a cualquier idioma - Tu plataforma, tu idioma Las cifras ## Por qué usar Shuttle en lugar de construirlo tú mismo Construir una infraestructura de pagos es caro, complejo y lento. Shuttle elimina los tres. Ahorro anual medio por plataforma frente a construir y mantener tu propia infraestructura de pagos. Coste típico de lograr y mantener la certificación PCI DSS nivel 1. Shuttle ya la tiene, así que tu plataforma no la construye. Tiempo de desarrollo medio ahorrado al usar Shuttle en vez de construir integraciones de pago desde cero. ## Precios simples y transparentes Pagos conformes con PCI en cualquier canal de voz - Twilio Pay - IVR, agente humano y agente de IA - Captura de voz conforme con PCI - Prueba sandbox gratuita de 30 días, luego 245 transacciones incluidas, desde $0.20 por transacción - Más operadores próximamente Envía enlaces de pago por SMS, correo o chat - Enlaces de pago con tu marca - Envío por SMS, correo y chat - Seguimiento de pagos en tiempo real Infraestructura de pagos completa en marca blanca - Tantos canales e instancias como necesites, sin costes por app - Gestión de equipos con permisos por rol - Checkout y portal en marca blanca Ver la comparativa completa de funciones ## ¿Listo para integrar pagos? Habla con nuestro equipo de plataformas y descubre cómo Shuttle puede ponerte en marcha en semanas, no en meses. ## Links - [Reservar una llamada](/discovery/) - [Empieza con Shuttle](/discovery/) - [Más información](/platforms/voice-checkout/#pricing) - [Más información](/es/platforms/links-checkout/) - [Hablar con nosotros](/discovery/) - [Ver la comparativa completa de funciones](/pricing/) --- URL: https://www.shuttleglobal.com/es/platforms/links-checkout/ --- # Enlaces de pago para plataformas: sin código | Shuttle > Lanza enlaces de pago para tus comercios sin trabajo de integración. Conecta más de 40 servicios de pago, páginas de checkout con tu marca y seguimiento en tiempo real. PCI DSS nivel 1. # Enlaces de pago para plataformas Integración sin código disponible Para plataformas de software multitenant que necesitan ofrecer conectividad y funciones de pago. Sin rehacer el checkout. Sin sobrecarga de «Connect». Sin nuevos contratos con PSP. ## Confían en nosotros ## La oportunidad ¿No quieres hacer nada? Lo hacemos todo por ti con nuestro programa White-Glove. O integra con nuestra API o conectores no-code y lanza en días. ## Lo que obtienes Funciones de plataforma ### Conectividad de pago Cada comercio conecta él mismo su proveedor de pago desde la lista de Shuttle, en un componente UX, sin desarrollo por parte de la plataforma. ### Páginas de checkout Los comercios definen páginas de checkout personalizadas, renderizadas con el componente Shuttle Checkout, con su propio mensaje y marca. ### Visibilidad Historial de transacciones en tiempo real y monitorización del checkout en directo que muestra la actividad de los enlaces de pago. ## Elige tu vía de integración Opciones de integración Integración rápida con la API de Shuttle. Shuttle aporta los componentes UX y gestiona la conformidad PCI. Conecta mediante motores de workflow: Cyclr, Make.com y Zapier. Shuttle aporta los componentes UX y gestiona la conformidad PCI. Un programa de lanzamiento totalmente gestionado, sin integración. Definimos, diseñamos, configuramos y operamos la automatización de enlaces de pago para cada comercio. ## Diseñado para tu sector Soluciones por sector ### Software de viajes Motores de reservas, channel managers y PMS. Añade enlaces de pago a cualquier flujo de reserva. ### Software de facturación Mejora el flujo de caja de tus clientes y la eficiencia del back-office con enlaces de pago de un clic en cada factura. ### Recobro de deudas La constancia y la comodidad aumentan las tasas de cobro. Envía enlaces de pago por SMS y correo a gran escala. ### Creadores de formularios Añade el cobro al enviar el formulario, sin checkout personalizado. ### Plataformas CX Completa la experiencia de pago dentro de las conversaciones con clientes, para más satisfacción y conversión. ### Software de agentes de campo Los agentes cobran in situ mediante enlace de pago, eliminando el seguimiento manual. ### Software de chatbot Permite completar transacciones y ventas adicionales dentro de los flujos de chat automatizados. ### Software CRM Añade capacidades de pago a tu centro de interacción con clientes. Convierte las acciones de CRM en ingresos. ## Enlaces de pago inteligentes Un enlace. Cualquier método de pago. Tarjeta, Open Banking (Reino Unido), ACH (EE. UU.), todo en uno. ### Seguimiento en tiempo real Conoce el estado, el momento y el método de pago. Elimina la carga de conciliación. ### Integración low-code Lanza enlaces desde CRM, ERP o herramientas de mensajería con Zapier y Make.com. ### Checkout con tu marca Dominio propio, logo, nombre del cliente y datos de factura precargados en cada página de checkout. ### Seguridad empresarial PCI DSS nivel 1, SOC 2 e ISO 27001: las máximas certificaciones de seguridad en pagos. ### App store multi-PSP Los comercios conectan su propio proveedor entre más de 40 servicios. Sin nuevos contratos con PSP. ## Panel de la plataforma Visibilidad y control ### Monitor de checkout Visibilidad en tiempo real de los pagos en curso. Los agentes pueden ayudar a clientes bloqueados observando el progreso del checkout. ### Generador de enlaces Crea plantillas para generar enlaces de forma coherente. Varios generadores cubren distintos escenarios y tipos de comercio. ### Personalización de enlaces Experiencias de pago de confianza con marca, mensajes y URLs personalizadas para cada comercio. ## Funciona con tus herramientas Integraciones ### Cualquier plataforma de software Usa el generador de enlaces de forma independiente con cualquier software. Comparte enlaces de pago por SMS, correo o chat. ### AWS Connect Integra la creación de enlaces de pago directamente en los espacios de agente de Amazon Connect. ### Xero Añade enlaces de pago a las facturas de Xero. Importe y número de factura precargados automáticamente. ### Integración profunda Integra el generador de enlaces directamente en tu plataforma. Operativo en horas. ## Míralo en acción ### Pruébalo tú mismo Puedes introducir cualquier dato en esta prueba; no se cobra ningún pago. Descubre la experiencia de checkout con marca que tus comercios pueden ofrecer. Credenciales de prueba Número de tarjeta: 4242 4242 4242 4242 Fecha de caducidad: 11/27 ### Varios métodos de pago Tarjeta, Open Banking, ACH: los clientes eligen cómo pagar. Los métodos de pago guardados permiten a los clientes recurrentes pagar en segundos. ### Actividad en tiempo real Monitoriza cada transacción de todos los comercios en tiempo real. Estado, importes, métodos y momento, con pista de auditoría completa en cada transacción. ## Descubre el producto completo Tour del producto ## Conformidad de nivel empresarial ### PCI DSS nivel 1 El máximo nivel de certificación de seguridad de tarjetas. Los datos de tarjeta nunca tocan tus sistemas ni los de tus comercios. ### ISO 27001 Norma internacional para la gestión de la seguridad de la información ### SOC 2 Controles auditados de seguridad, disponibilidad y confidencialidad > No habríamos podido entregar funciones de enlaces de pago a nuestros clientes empresariales tan rápido y con tanta garantía de no ser por Shuttle ## Precios simples y transparentes Para plataformas con recursos de desarrollo - Varios comercios - Páginas de pago personalizadas - URLs personalizadas - Conformidad PCI gestionada - Doc para desarrolladores y SDKs No-code vía Zapier, Make.com, Cyclr - Las mismas funciones que la API - Conectores Zapier y Make.com - Motor de integración Cyclr - Sin necesidad de desarrollador - Biblioteca de plantillas - Configuración guiada Programa totalmente gestionado - Todo lo de Workflow - Servicio gestionado - Definición y diseño - Onboarding de comercios - Gestor de cuenta dedicado - Automatización a medida ## Preguntas frecuentes **¿Por qué enlaces de pago en lugar de checkout integrado?** Los enlaces reutilizan los canales que tus clientes ya usan (correo, SMS, chat) y casi no requieren cambios en el front-end. Puedes añadir checkout integrado más adelante sin perder impulso. **¿A qué proveedores de pago pueden acceder los comercios?** Shuttle admite más de 40 servicios de pago, incluidos Adyen, Authorize.net, CardConnect, Checkout.com, Global Payments, Moneris, NMI, Opayo, PayPal, PaySafe, PayU, Stripe, USAePay, Worldpay y muchos más. Cada comercio conecta él mismo su proveedor existente. **¿Tenemos que gestionar la conformidad PCI?** Los datos de tarjeta permanecen en las páginas alojadas por Shuttle y nunca llegan a tu plataforma, así tu alcance PCI se mantiene reducido. Sigues validando tu propia conformidad, pero sobre una base mucho más ligera. Shuttle está certificado en PCI DSS nivel 1. **¿Se admiten SCA y 3D Secure?** Sí. Shuttle gestiona automáticamente todos los procesos de SCA y 3D Secure en todas las pasarelas compatibles. **¿Cómo funcionan los reembolsos y las disputas?** Los reembolsos se pueden iniciar desde la vista del comercio con un clic, o de forma programática mediante la API o el motor de workflow. **¿Pueden los comercios personalizar las páginas de checkout con su marca?** Sí. Los comercios pueden personalizar las páginas con su logo, colores y mensajes, y usar URLs propias. Para pagos totalmente integrados, contacta con ventas sobre la solución de Plataforma. ## ¿Listo para lanzar enlaces de pago? Habla con nuestro equipo sobre añadir funciones de enlaces de pago a tu plataforma. Desde conectores no-code hasta integración completa por API, encontraremos el encaje adecuado. ## Links - [Ver doc para desarrolladores](https://docs.shuttleglobal.com) - [Ver guía](/platforms/links-checkout/workflows/) - [Reservar una llamada](/discovery/?product=payment-links) - [Cualquier plataforma de software Usa el generador de enlaces de forma independiente con cualquier software. Comparte enlaces de pago por SMS, correo o chat.](https://docs.shuttleglobal.com/docs/works-with-generic) - [AWS Connect Integra la creación de enlaces de pago directamente en los espacios de agente de Amazon Connect.](https://docs.shuttleglobal.com/docs/works-with-aws-connect) - [Xero Añade enlaces de pago a las facturas de Xero. Importe y número de factura precargados automáticamente.](https://docs.shuttleglobal.com/docs/works-with-xero) - [Integración profunda Integra el generador de enlaces directamente en tu plataforma. Operativo en horas.](https://docs.shuttleglobal.com/docs/works-with-integration-guide) - [Empezar](/discovery/?product=payment-links) --- URL: https://www.shuttleglobal.com/es/platforms/voice-checkout/ --- # Voice Checkout para plataformas: pagos por voz sobre cualquier pasarela | Shuttle > Añade pagos por voz conformes con PCI a tu plataforma. Una sola integración abstrae más de 30 pasarelas y tu operador, con control multiinquilino sobre cada comercio. PCI DSS nivel 1. # Voice Checkout Una capa de pagos por voz sobre cualquier pasarela y operador Ofrece a cada comercio de tu plataforma pagos por teléfono conformes con PCI, sin crear una integración nueva para cada pasarela. Shuttle abstrae más de 30 pasarelas y tu operador tras una sola integración, y te permite gestionar la actividad de pago de cada comercio desde un único centro de control. Los datos de tarjeta nunca tocan tus sistemas. ## Voice Checkout en acción Demo en directo El cliente paga por el IVR. Los tonos DTMF se eliminan antes de llegar al agente o a tus sistemas. El agente permanece en la línea mientras el cliente introduce los datos de su tarjeta de forma segura. ## Confían en nosotros ## El problema Añadir pagos por voz a tu producto implica manejar datos de tarjeta, asumir el cumplimiento PCI y crear una integración distinta para cada pasarela que pidan tus comercios. Comercio a comercio y pasarela a pasarela, el trabajo no termina nunca. ## Cómo funciona Voice Checkout Tres pasos - El cliente llama a tu empresa El cliente llega a tu IVR, habla con un agente o interactúa con un agente de IA. Cuando llega el momento de pagar, Shuttle se une a la llamada solo para el segmento de captura segura. - Shuttle captura el pago de forma segura El cliente introduce los datos de la tarjeta con el teclado (DTMF). Los tonos se eliminan del audio para que el agente nunca los oiga. También se puede enviar un enlace de pago por SMS o correo, con soporte para wallets. - El pago se procesa a través de tu pasarela Shuttle enruta la transacción a la pasarela que elijas, tokeniza la tarjeta para usos futuros o autoriza para capturar más tarde. Solo se devuelven datos enmascarados, así tus sistemas nunca ven información sensible. ## Conjunto de funciones listo para usar ### Checkout listo para usar Checkout, conector de pasarela e interfaz de pago listos para integrar en tus flujos de voz. ### Compatible con IVR Funciona con IVR automatizados y llamadas asistidas por agente. Captura pagos con teclado DTMF. ### Sin registrar datos de tarjeta Los datos de tarjeta nunca tocan tu infraestructura. Shuttle tokeniza la tarjeta en tu pasarela, así tu alcance PCI se mantiene limitado. ### Enlaces de pago por SMS Cuando el pago por teléfono no es posible, envía un enlace de pago seguro por SMS para que el cliente lo complete en su dispositivo. ### Más de 30 pasarelas Conecta tu stack de pago preferido. Soporte para Stripe, Worldpay, Adyen, Checkout.com y más, con configuración multipasarela. ### Actividad en tiempo real Consulta la actividad de pagos, aplica reembolsos totales o parciales y gestiona varios perfiles de pago desde un único panel. ### Tokeniza y reutiliza Tokeniza los métodos de pago durante una llamada y autoriza los datos de tarjeta para usarlos en cualquier canal: web, móvil o voz. ### Perfiles de checkout inteligentes Ejecuta varios perfiles de pago con configuraciones de pasarela distintas. Elige qué pasarela gestiona cada tipo de pago. ### Sin cuotas de alta Precio directo por transacción, sin cuotas de alta, sin mínimos mensuales ni costes ocultos. Pagas solo por lo que usas. ### Seguridad DTMF Durante la captura segura de la tarjeta, los tonos DTMF se eliminan del audio para que el agente nunca oiga los datos. El canal de voz sigue abierto para la conversación. ### Tokeniza y autoriza Tokeniza los datos de pago para más adelante, autoriza y captura después o procesa al instante: pagos únicos, retenciones de preautorización y escenarios recurrentes. ### Interfaz de pago para agentes Interfaz de asistencia al agente en tiempo real para generar y enviar enlaces de pago durante las llamadas. Rellena campos, lanza pagos y haz seguimiento del estado sin salir de la conversación. ## Conectores de operador Canales de voz Shuttle conecta los flujos de voz y chat de Twilio con más de 30 pasarelas de pago. Shuttle funciona hoy con Twilio, y con cualquier operador muy pronto. ## Métodos de pago aceptados Métodos de pago ### Tarjetas Visa, Mastercard, Amex y más, capturadas de forma segura con el teclado DTMF durante la llamada, con validación de BIN y comprobación de Luhn en tiempo real. ### ACH y transferencias bancarias Acepta ACH (EE. UU.), BACS y domiciliación (Reino Unido) con verificación de datos bancarios en tiempo real. ### Enlaces de pago y wallets Envía un enlace de pago con tu marca por SMS o correo durante o después de la llamada. Compatible con Apple Pay, Google Pay y PayPal. El cliente completa en su dispositivo con su wallet preferido. ## Pasarelas de pago compatibles ## Conformidad de nivel empresarial ### PCI DSS nivel 1 El máximo nivel de certificación de seguridad de tarjetas. Los datos de tarjeta de tus clientes nunca tocan tus sistemas. ### ISO 27001 Norma internacional para la gestión de la seguridad de la información ### SOC 2 Controles auditados de seguridad, disponibilidad y confidencialidad > Shuttle nos permitió tratar a proveedores de pago heredados como un servicio SaaS moderno. Pudimos dar soporte a las pasarelas que nuestros clientes exigían y automatizar por completo transacciones de alto valor en sectores regulados. ## Precios simples y transparentes Inicio rápido vía Twilio Marketplace Facturado a través de Twilio - Instalación desde Twilio Marketplace - Facturado a través de tu cuenta de Twilio - Captura de pagos por voz conforme con PCI - Informes de transacciones en tiempo real - Código de la app de demo y blueprint incluidos - Checklist de puesta en marcha y certificación Control total - Soporte para voz con IA y agente humano - API de captura granular a nivel de campo - UX para agentes y generador de pagos - Tokenización con tu pasarela - Multidivisa y multipasarela Se instala vía Shuttle Checkout - Prueba sandbox gratuita de 30 días - Cuenta de Merchant Portal incluida - transacciones incluidas cada mes - Los $49/mes devueltos como crédito, para gastar según la tarifa por volumen (no en el uso facturado por Twilio) - Desde $0.20 por transacción, decreciente con el volumen - Gestión de equipos con permisos por rol - Checkout con tu marca y dominio propio - Añade la app Links Checkout por $49/mes ¿Creas un producto multiinquilino para tus propios comercios? Eso es nuestro Embedded Payment Layer, donde ejecutas tantos canales e instancias como necesites, sin costes por app. ## Preguntas frecuentes **¿Qué es Shuttle Voice Checkout?** Shuttle Voice Checkout conecta tus flujos de voz y chat con los principales procesadores de pago como Worldpay, Checkout.com, Opayo y Stripe, sin que manejes datos de tarjeta. Los clientes pagan de forma segura con el teclado (DTMF) o mediante un enlace de pago enviado por SMS. **¿Qué pasarelas de pago son compatibles?** Shuttle admite más de 30 pasarelas, incluidas ACI Speedpay, Adyen, Authorize.Net, BS Pay One, CardConnect, Checkout.com, Cybersource, Ecommpay, FatZebra, Fortis, FreedomPay, Global Payments, GoCardless, Liqpay, Moneris, NAB, NMI, Opayo/Elavon, PaySafe, QuickBooks Payments, Stripe, Trust Payments, USAePay, Worldpay Access y Xendit, entre otros. **¿Qué métodos de pago son compatibles?** Tarjetas (Visa, Mastercard, Amex), transferencias bancarias ACH y métodos de pago adicionales mediante enlaces de pago con tu marca enviados por SMS. **¿Cuáles son mis obligaciones de conformidad PCI?** Shuttle cumple con PCI DSS nivel 1. Como los datos de tarjeta nunca tocan tus sistemas, tus obligaciones PCI se reducen notablemente. Sigues realizando tu propia autoevaluación. **¿Cuánto se tarda en configurarlo?** Un script de demo te permite estar operativo en horas. Una configuración a medida suele completarse en una semana con un desarrollador. **¿Qué operadores de voz son compatibles?** Hoy, Twilio es el conector en producción. Shuttle funciona hoy con Twilio, y con cualquier operador muy pronto. **¿Cuál es la diferencia entre el conector de Shuttle y un conector genérico en Twilio?** En Twilio, el conector de Shuttle está prediseñado y optimizado para procesadores concretos, con orquestación de pagos de extremo a extremo, monitorización lista para producción y gestión multicomercio. El conector genérico es el conector ligero y abierto de Twilio: te deja gestionar tú mismo la integración del PSP, útil para proveedores personalizados y pruebas. ## ¿Listo para añadir pagos por voz? Habla con nuestro equipo y descubre cómo Shuttle Voice Checkout puede ponerte a cobrar pagos por teléfono en días, no en meses. ## Links - [Más información →](/integrations/twilio-pay/) - [Instalar ahora](https://merchant.shuttleglobal.com/signup/twilio) - [Hablar con nosotros](/discovery/) - [Empezar](https://merchant.shuttleglobal.com/) - [Embedded Payment Layer](/es/platforms/) - [Reservar una llamada](/discovery/) --- URL: https://www.shuttleglobal.com/ethiopia/payment-methods/ --- # Redirecting to: /blog/the-most-popular-payment-methods-in-ethopia/ ## Links - [Redirecting from to](/blog/the-most-popular-payment-methods-in-ethopia/) --- URL: https://www.shuttleglobal.com/fr/platforms/ --- # Embedded Payments pour plateformes logicielles | Shuttle > Intégrez les paiements sur votre plateforme sans devenir PayFac. Shuttle réunit conception, déploiement, développement et support dans une seule couche de paiement. # Vos paiements, déjà en place Pour les plateformes logicielles Votre plateforme a besoin d'une couche de paiement qui évolue avec elle, pas d'un projet de 12 mois. Shuttle vous donne tout le nécessaire pour intégrer les paiements sur n'importe quel canal, sans devenir PayFac ni perdre le contrôle. ## La confiance des plus grandes plateformes ## Le problème Votre plateforme grandit, mais les paiements vous freinent. Les clients grands comptes exigent des capacités de paiement intégrées, votre équipe produit croule sous les intégrations PSP, et chaque mois sans solution représente du chiffre d'affaires perdu. ## Pourquoi les plateformes choisissent Shuttle - Les grands comptes commencent à exiger des PSP précis Les intégrer un par un casse la feuille de route. - Les paiements intégrés deviennent incontournables Devenir PayFac introduit des risques, de la conformité et une lourdeur opérationnelle. - Les paiements envahissent les discussions produit Shuttle existe pour lever cette pression, sans imposer aux plateformes des compromis qu'elles regretteront. Ne rien faire est aussi une décision, et cela se traduit généralement par des contrats perdus ou retardés. ## Pourquoi les plateformes peinent avec les paiements Points de friction ### Des grands comptes qui exigent des PSP Vos meilleurs prospects réclament des capacités de paiement que vous n'avez pas. Chaque contrat perdu est du chiffre d'affaires capté par vos concurrents. ### Les paiements intégrés sont inévitables Vos utilisateurs attendent des paiements intégrés à leur flux de travail, pas une redirection vers un tiers. Les plateformes qui intègrent les paiements gagnent le marché. ### Les paiements débordent sur le produit Votre équipe produit répond à des questions de paiement. Votre feuille de route est détournée par des intégrations PSP. Les paiements consomment des ressources destinées à votre cœur de produit. ## Une couche de paiement, quatre piliers La solution Shuttle ### Concevoir Des expériences de paiement et marchand en marque blanche, fidèles à votre identité. Vos utilisateurs ne savent jamais que Shuttle existe. ### Déployer Lancez-vous en quelques semaines, pas en quelques mois. Des composants prêts à l'emploi et une infrastructure gérée laissent votre équipe se concentrer sur votre produit, pas sur la complexité technique des paiements. ### Développer Des API REST, des SDK et des webhooks pensés pour les équipes de plateformes. Étendez et personnalisez chaque aspect de l'expérience de paiement. ### Accompagner Des responsables de la réussite dédiés, un support marchand et une expertise en conformité. Shuttle détient sa propre certification PCI DSS niveau 1 et suit les évolutions réglementaires : votre périmètre reste restreint. ## Pour les plateformes multi-tenant, mono-tenant et sur site Déploiement ### Multi-tenant Infrastructure partagée, données isolées ### Mono-tenant Instance dédiée par client ### Sur site Hébergement interne, pleine souveraineté des données ### Fidélisation de la plateforme Les marchands qui paient via votre plateforme ne partent pas. Les paiements deviennent le ciment qui retient vos clients. ### Valeur contractuelle accrue Les paiements intégrés augmentent la valeur moyenne des contrats grands comptes en ajoutant une ligne « paiements ». ### Moins de désabonnement Éliminez la première raison de perte de marchands au profit de la concurrence : des expériences de paiement fragmentées. ### Périmètre PCI limité Les données de carte vont directement à la passerelle et ne touchent jamais votre plateforme : votre périmètre PCI reste minimal. Shuttle maintient PCI DSS niveau 1, SOC 2 Type 2 et ISO 27001. ### Mise sur le marché accélérée Livrez les fonctionnalités de paiement que vos commerciaux promettent déjà. En quelques semaines, pas en trimestres. ## Les composants de la plateforme Ce que vous obtenez ### Intégration Un composant intégrable qui permet aux marchands de parcourir, choisir et connecter leurs prestataires de paiement préférés, avec authentification OAuth ou par clé API. - Plus de 40 prestataires connectables en un clic - Flux d'authentification OAuth et par clé API - Disponibilité des prestataires filtrée par pays - Prévention de la fraude et configuration 3D Secure ### Checkout Un formulaire de paiement prêt à intégrer, affiché en iFrame dans votre produit. Prend en charge cartes, wallets et moyens de paiement locaux, entièrement à vos couleurs. - Affichage en ligne ou en modale - Cartes, wallets et moyens de paiement locaux - Conforme PCI DSS niveau 1 ### Express Checkout Affichez des moyens de paiement express comme Apple Pay, Google Pay et PayPal directement dans votre tunnel. Les boutons wallet apparaissent automatiquement lorsqu'un prestataire connecté gère les network tokens. - Boutons wallet Apple Pay et Google Pay - Options PayPal, Affirm et paiement fractionné - Messages promotionnels BNPL intégrés de chaque prestataire - Chargement dans la frame principale pour un accès natif aux wallets ### Vue d'activité marchand Offrez aux marchands une visibilité en temps réel sur les transactions, les règlements et la performance des paiements via un tableau de bord intégrable. - Liste des transactions avec filtres et recherche - Gestion des comptes et des clients - Suivi des paiements programmés - Rapports exportables ### Portail marchand Un portail en marque blanche que les marchands utilisent en autonomie pour gérer les paiements, consulter les rapports, traiter les remboursements et configurer leurs paramètres. - Structure organisationnelle multi-niveaux - Configuration et règles des prestataires de paiement - Gestion des équipes avec accès basé sur les rôles - Architecture modulaire de places de marché d'applications ### Traductions Les composants intégrables de Shuttle peuvent être traduits dans n'importe quelle langue : votre checkout en allemand, votre onboarding en japonais ou vos paiements express en portugais. - Traduisez les composants intégrables dans n'importe quelle langue - Votre plateforme, votre langue Les chiffres ## Pourquoi choisir Shuttle plutôt que tout construire vous-même Construire une infrastructure de paiement est coûteux, complexe et lent. Shuttle élimine ces trois obstacles. Économie annuelle moyenne par plateforme par rapport à la construction et la maintenance de sa propre infrastructure de paiement. Coût typique pour obtenir et maintenir la certification PCI DSS niveau 1. Shuttle la détient déjà : votre plateforme ne la construit pas. Temps de développement moyen économisé en utilisant Shuttle plutôt qu'en construisant les intégrations de paiement de zéro. ## Une tarification simple et transparente Paiements conformes PCI sur n'importe quel canal vocal - Twilio Pay - SVI, agent humain et agent IA - Capture vocale conforme PCI - Essai sandbox gratuit de 30 jours, puis 245 transactions incluses, à partir de $0.20 par transaction - Autres opérateurs bientôt disponibles Envoyez des liens de paiement par SMS, e-mail ou chat - Liens de paiement à vos couleurs - Envoi par SMS, e-mail et chat - Suivi des paiements en temps réel Infrastructure de paiement complète en marque blanche - Autant de canaux et d'instances que nécessaire, sans frais par app - Gestion des équipes avec permissions par rôle - Checkout et portail en marque blanche Voir le comparatif complet des fonctionnalités ## Prêt à intégrer les paiements ? Parlez à notre équipe plateformes et découvrez comment Shuttle peut vous lancer en quelques semaines, pas en quelques mois. ## Links - [Réserver un appel](/discovery/) - [Adopter Shuttle](/discovery/) - [En savoir plus](/platforms/voice-checkout/#pricing) - [En savoir plus](/fr/platforms/links-checkout/) - [Nous contacter](/discovery/) - [Voir le comparatif complet des fonctionnalités](/pricing/) --- URL: https://www.shuttleglobal.com/fr/platforms/links-checkout/ --- # Liens de paiement pour plateformes : sans code | Shuttle > Lancez des liens de paiement pour vos marchands sans intégration. Connectez plus de 40 services de paiement, des pages de checkout à vos couleurs et un suivi en temps réel. PCI DSS niveau 1. # Liens de paiement pour plateformes Intégration sans code disponible Pour les plateformes logicielles multi-tenant qui doivent offrir connectivité et fonctionnalités de paiement. Pas de refonte du checkout. Pas de surcharge « Connect ». Aucun nouveau contrat PSP. ## Ils nous font confiance ## L'opportunité Vous ne voulez rien faire ? Laissez-nous tout gérer avec notre programme White-Glove. Ou intégrez via notre API ou nos connecteurs no-code et lancez-vous en quelques jours. ## Ce que vous obtenez Fonctionnalités plateforme ### Connectivité de paiement Chaque marchand connecte lui-même son prestataire de paiement depuis la liste de Shuttle, dans un composant UX, sans aucun développement côté plateforme. ### Pages de checkout Les marchands définissent des pages de checkout personnalisées, rendues via le composant Shuttle Checkout, avec leur propre message et identité. ### Visibilité Historique des transactions en temps réel et suivi du checkout en direct montrant l'activité des liens de paiement. ## Choisissez votre voie d'intégration Options d'intégration Intégration rapide avec l'API de Shuttle. Shuttle fournit les composants UX et gère la conformité PCI. Connectez-vous via des moteurs de workflow : Cyclr, Make.com et Zapier. Shuttle fournit les composants UX et gère la conformité PCI. Un programme de lancement entièrement géré, sans intégration. Nous cadrons, concevons, configurons et exploitons l'automatisation des liens de paiement pour chaque marchand. ## Conçu pour votre secteur Solutions par secteur ### Logiciels de voyage Moteurs de réservation, channel managers et PMS. Ajoutez des liens de paiement à tout parcours de réservation. ### Logiciels de facturation Améliorez la trésorerie de vos clients et l'efficacité du back-office avec des liens de paiement en un clic sur chaque facture. ### Recouvrement La persévérance et la simplicité augmentent les taux de recouvrement. Envoyez des liens de paiement par SMS et e-mail à grande échelle. ### Créateurs de formulaires Ajoutez l'encaissement à la soumission du formulaire, sans checkout personnalisé. ### Plateformes CX Complétez l'expérience de paiement au sein des conversations clients, pour plus de satisfaction et de conversion. ### Logiciels pour agents terrain Les agents encaissent sur place via un lien de paiement, sans relance manuelle. ### Logiciels de chatbot Permettez la finalisation des transactions et les ventes additionnelles dans les flux de chat automatisés. ### Logiciels CRM Ajoutez des capacités de paiement à votre centre d'engagement client. Transformez les actions CRM en revenus. ## Des liens de paiement intelligents Fonctionnalités ### Liens de paiement intelligents Un seul lien. Tout moyen de paiement. Carte, Open Banking (UK), ACH (US), réunis. ### Suivi en temps réel Connaissez le statut, le moment et le moyen de paiement. Fini la charge de rapprochement. ### Intégration low-code Déclenchez les liens via CRM, ERP ou outils de messagerie avec Zapier et Make.com. ### Checkout à vos couleurs Domaine personnalisé, logo, nom du client et détails de facture pré-remplis sur chaque page. ### Sécurité entreprise PCI DSS niveau 1, SOC 2 et ISO 27001 : les plus hautes certifications de sécurité des paiements. ### App store multi-PSP Les marchands connectent leur propre prestataire parmi plus de 40 services. Aucun nouveau contrat PSP. ## Tableau de bord plateforme Visibilité et contrôle ### Moniteur de checkout Visibilité en temps réel sur les paiements en cours. Les agents peuvent aider un client bloqué en observant la progression du checkout. ### Générateur de liens Créez des modèles pour générer des liens de façon cohérente. Plusieurs générateurs couvrent différents scénarios et types de marchands. ### Personnalisation des liens Des expériences de paiement de confiance avec identité, messages et URL personnalisés pour chaque marchand. ## Compatible avec vos outils Intégrations ### Toute plateforme logicielle Utilisez le générateur de liens en autonomie avec n'importe quel logiciel. Partagez les liens par SMS, e-mail ou chat. ### AWS Connect Intégrez la création de liens de paiement directement dans les espaces agents d'Amazon Connect. ### Xero Ajoutez des liens de paiement aux factures Xero. Montant et numéro de facture pré-remplis automatiquement. ### Intégration profonde Intégrez le générateur de liens directement dans votre plateforme. Opérationnel en quelques heures. ## Voir en action ### Essayez par vous-même Vous pouvez saisir n'importe quelles données dans ce test, aucun paiement n'est prélevé. Découvrez l'expérience de checkout à vos couleurs que vos marchands peuvent offrir. Identifiants de test Numéro de carte : 4242 4242 4242 4242 Date d'expiration : 11/27 ### Plusieurs moyens de paiement Carte, Open Banking, ACH : les clients choisissent comment payer. Les moyens de paiement enregistrés permettent aux clients fidèles de payer en quelques secondes. ### Activité en temps réel Suivez chaque transaction de tous vos marchands en temps réel. Statut, montants, moyens et horodatage, avec une piste d'audit complète sur chaque transaction. ## Découvrez le produit complet Visite du produit ## Conformité de niveau entreprise ### PCI DSS niveau 1 Le plus haut niveau de certification de sécurité des cartes. Les données de carte ne touchent jamais vos systèmes ni ceux de vos marchands. ### ISO 27001 Norme internationale de gestion de la sécurité de l'information ### SOC 2 Contrôles audités de sécurité, de disponibilité et de confidentialité > Nous n'aurions jamais pu livrer des fonctionnalités de liens de paiement à nos clients grands comptes aussi vite et avec autant d'assurance sans Shuttle ## Une tarification simple et transparente Pour les plateformes avec des développeurs - Plusieurs marchands - Pages de paiement personnalisées - URL personnalisées - Conformité PCI gérée - Doc développeur et SDK No-code via Zapier, Make.com, Cyclr - Mêmes fonctionnalités que l'API - Connecteurs Zapier et Make.com - Moteur d'intégration Cyclr - Aucun développeur requis - Bibliothèque de modèles - Configuration guidée Programme entièrement géré - Tout ce qui est inclus dans Workflow - Service géré - Cadrage et conception - Onboarding des marchands - Responsable de compte dédié - Automatisation sur mesure ## Questions fréquentes **Pourquoi des liens de paiement plutôt qu'un checkout intégré ?** Les liens réutilisent les canaux que vos clients utilisent déjà (e-mail, SMS, chat) et ne demandent presque aucun changement front-end. Vous pourrez ajouter un checkout intégré plus tard sans perdre d'élan. **À quels prestataires de paiement les marchands ont-ils accès ?** Shuttle prend en charge plus de 40 services de paiement, dont Adyen, Authorize.net, CardConnect, Checkout.com, Global Payments, Moneris, NMI, Opayo, PayPal, PaySafe, PayU, Stripe, USAePay, Worldpay et bien d'autres. Chaque marchand connecte lui-même son prestataire existant. **Devons-nous gérer la conformité PCI ?** Les données de carte restent sur les pages hébergées par Shuttle et n'atteignent jamais votre plateforme : votre périmètre PCI reste restreint. Vous validez toujours votre propre conformité, mais sur une base bien plus légère. Shuttle est certifié PCI DSS niveau 1. **La SCA et 3D Secure sont-ils pris en charge ?** Oui. Shuttle gère automatiquement tous les processus SCA et 3D Secure sur toutes les passerelles prises en charge. **Comment fonctionnent les remboursements et les litiges ?** Les remboursements peuvent être lancés depuis la vue marchand en un clic, ou par programmation via l'API ou le moteur de workflow. **Les marchands peuvent-ils personnaliser les pages de checkout ?** Oui. Les marchands peuvent personnaliser les pages avec leur logo, leurs couleurs et leurs messages, et utiliser des URL personnalisées. Pour des paiements entièrement intégrés, contactez le service commercial au sujet de la solution Plateforme. ## Prêt à lancer vos liens de paiement ? Parlez à notre équipe de l'ajout de liens de paiement à votre plateforme. Du connecteur no-code à l'intégration API complète, nous trouverons la bonne formule. ## Links - [Voir la doc développeur](https://docs.shuttleglobal.com) - [Voir le guide](/platforms/links-checkout/workflows/) - [Réserver un appel](/discovery/?product=payment-links) - [Toute plateforme logicielle Utilisez le générateur de liens en autonomie avec n'importe quel logiciel. Partagez les liens par SMS, e-mail ou chat.](https://docs.shuttleglobal.com/docs/works-with-generic) - [AWS Connect Intégrez la création de liens de paiement directement dans les espaces agents d'Amazon Connect.](https://docs.shuttleglobal.com/docs/works-with-aws-connect) - [Xero Ajoutez des liens de paiement aux factures Xero. Montant et numéro de facture pré-remplis automatiquement.](https://docs.shuttleglobal.com/docs/works-with-xero) - [Intégration profonde Intégrez le générateur de liens directement dans votre plateforme. Opérationnel en quelques heures.](https://docs.shuttleglobal.com/docs/works-with-integration-guide) - [Commencer](/discovery/?product=payment-links) --- URL: https://www.shuttleglobal.com/fr/platforms/voice-checkout/ --- # Voice Checkout pour plateformes : paiements vocaux sur toutes les passerelles | Shuttle > Ajoutez des paiements vocaux conformes PCI à votre plateforme. Une seule intégration abstrait plus de 30 passerelles et votre opérateur, avec un contrôle multi-locataire sur chaque marchand. PCI DSS niveau 1. # Voice Checkout Une couche de paiement vocal au-dessus de chaque passerelle et opérateur Offrez à chaque marchand de votre plateforme des paiements par téléphone conformes PCI, sans développer une intégration par passerelle. Shuttle abstrait plus de 30 passerelles et votre opérateur derrière une seule intégration, et vous permet de gérer l'activité de paiement de chaque marchand depuis un poste de contrôle unique. Les données de carte ne touchent jamais vos systèmes. ## Voice Checkout en action Démo en direct Le client paie via le SVI. Les tonalités DTMF sont supprimées avant d'atteindre l'agent ou vos systèmes. L'agent reste en ligne pendant que le client saisit ses informations de carte en toute sécurité. ## Ils nous font confiance ## Le problème Ajouter des paiements vocaux à votre produit implique de manipuler des données de carte, d'assumer la conformité PCI et de développer une intégration distincte pour chaque passerelle demandée par vos marchands. À l'échelle de chaque marchand et de chaque passerelle, ce travail n'a pas de fin. ## Comment fonctionne Voice Checkout Trois étapes - Le client appelle votre entreprise Le client joint votre SVI, parle à un agent ou interagit avec un agent IA. Au moment de payer, Shuttle ne rejoint l'appel que pour le segment de capture sécurisée. - Shuttle capture le paiement en toute sécurité Le client saisit ses informations de carte au clavier (DTMF). Les tonalités sont retirées de l'audio pour que l'agent ne les entende jamais. Un lien de paiement peut aussi être envoyé par SMS ou e-mail, avec prise en charge des wallets. - Le paiement est traité par votre passerelle Shuttle achemine la transaction vers la passerelle de votre choix, tokenise la carte pour un usage ultérieur ou autorise pour une capture différée. Seules des données masquées sont renvoyées : vos systèmes ne voient jamais de données sensibles. ## Un ensemble de fonctionnalités prêt à l'emploi Fonctionnalités ### Checkout prêt à l'emploi Checkout, connecteur de passerelle et interface de paiement prêts à intégrer à vos flux vocaux. ### Compatible SVI Fonctionne avec les SVI automatisés et les appels assistés par un agent. Capturez les paiements au clavier DTMF. ### Aucune donnée de carte enregistrée Les données de carte ne touchent jamais votre infrastructure. Shuttle tokenise la carte auprès de votre passerelle : votre périmètre PCI reste restreint. ### Liens de paiement par SMS Quand le paiement par téléphone n'est pas possible, envoyez un lien de paiement sécurisé par SMS, que le client règle sur son appareil. ### Plus de 30 passerelles Connectez votre stack de paiement préférée. Prise en charge de Stripe, Worldpay, Adyen, Checkout.com et bien d'autres, avec configuration multi-passerelle. ### Activité en temps réel Consultez l'activité des paiements, appliquez des remboursements totaux ou partiels et gérez plusieurs profils de paiement depuis un seul tableau de bord. ### Tokenisation et réutilisation Tokenisez les moyens de paiement pendant un appel et autorisez les cartes pour un usage sur tout canal : web, mobile ou vocal. ### Profils de checkout intelligents Exécutez plusieurs profils de paiement avec des configurations de passerelle différentes. Le smart checkout achemine les transactions selon vos règles. ### Sans frais de mise en place Tarification directe à la transaction, sans frais de mise en place, sans minimum mensuel ni coût caché. Vous ne payez que ce que vous utilisez. ### Sécurité DTMF Pendant la capture sécurisée, les tonalités DTMF sont retirées du flux audio pour que l'agent n'entende jamais les données de carte. Le canal vocal reste ouvert pour la conversation. ### Tokenisation et autorisation Tokenisez les données de paiement pour plus tard, autorisez et capturez ultérieurement ou traitez immédiatement : paiements ponctuels, pré-autorisations et scénarios récurrents. ### Déploiement multi-régions Infrastructure de téléphonie déployée localement par région pour réduire la latence audio. Disponible aux États-Unis, au Canada et au Royaume-Uni, autres régions sur demande. ### Interface de paiement agent Interface d'assistance agent en temps réel pour générer et envoyer des liens de paiement pendant les appels. Pré-remplissez les champs, déclenchez les paiements et suivez le statut sans quitter la conversation. ## Connecteurs opérateurs Canaux vocaux Shuttle connecte les flux voix et chat de Twilio à plus de 30 passerelles de paiement. Shuttle fonctionne avec Twilio aujourd'hui, et avec n'importe quel opérateur bientôt. ## Moyens de paiement acceptés Moyens de paiement ### Cartes Visa, Mastercard, Amex et plus, capturées en toute sécurité au clavier DTMF pendant l'appel, avec validation BIN et contrôle de Luhn en temps réel. ### ACH et virements bancaires Acceptez l'ACH (US), BACS et le prélèvement (UK) avec vérification des codes guichet/banque pour confirmer les coordonnées en temps réel. ### Liens de paiement et wallets Envoyez un lien de paiement à vos couleurs par SMS ou e-mail pendant ou après l'appel. Prise en charge d'Apple Pay, Google Pay et PayPal. Le client règle sur son appareil avec son wallet préféré. ## Passerelles de paiement prises en charge ## Conformité de niveau entreprise ### PCI DSS niveau 1 Le plus haut niveau de certification de sécurité des cartes. Les données de carte de vos clients ne touchent jamais vos systèmes. ### ISO 27001 Norme internationale de gestion de la sécurité de l'information ### SOC 2 Contrôles audités de sécurité, de disponibilité et de confidentialité > Shuttle nous a permis de traiter des prestataires de paiement historiques comme un service SaaS moderne. Nous avons pu prendre en charge les passerelles exigées par nos clients et automatiser entièrement des transactions à forte valeur dans des secteurs réglementés. ## Une tarification simple et transparente Démarrage rapide via Twilio Marketplace Facturé via Twilio - Installation depuis Twilio Marketplace - Facturé via votre compte Twilio - Capture vocale conforme PCI - Reporting des transactions en temps réel - Code de l'app de démo et blueprint inclus - Checklist de mise en production et certification Contrôle total - Prise en charge voix IA et agent humain - API de capture granulaire au niveau du champ - UX agent et générateur de paiement - Tokenisation avec votre passerelle - Multi-devise et multi-passerelle À installer via Shuttle Checkout - Essai sandbox gratuit de 30 jours - Compte Merchant Portal inclus - transactions incluses chaque mois - Les $49/mois restitués en crédit, à dépenser au tarif dégressif (hors usage facturé par Twilio) - À partir de $0.20 par transaction, dégressif selon le volume - Gestion des équipes avec permissions par rôle - Checkout à vos couleurs avec domaine personnalisé - Ajoutez l'app Links Checkout pour $49/mois Vous créez un produit multi-locataire pour vos propres marchands ? C'est notre Embedded Payment Layer, où vous exploitez autant de canaux et d'instances que nécessaire, sans frais par app. ## Questions fréquentes **Qu'est-ce que Shuttle Voice Checkout ?** Shuttle Voice Checkout connecte vos flux voix et chat aux principaux processeurs de paiement comme Worldpay, Checkout.com, Opayo et Stripe, sans que vous manipuliez de données de carte. Les clients paient en toute sécurité au clavier (DTMF) ou via un lien de paiement envoyé par SMS. **Quelles passerelles de paiement sont prises en charge ?** Shuttle prend en charge plus de 30 passerelles, dont ACI Speedpay, Adyen, Authorize.Net, BS Pay One, CardConnect, Checkout.com, Cybersource, Ecommpay, FatZebra, Fortis, FreedomPay, Global Payments, GoCardless, Liqpay, Moneris, NAB, NMI, Opayo/Elavon, PaySafe, QuickBooks Payments, Stripe, Trust Payments, USAePay, Worldpay Access et Xendit, entre autres. **Quels moyens de paiement sont pris en charge ?** Les cartes (Visa, Mastercard, Amex), les virements ACH et des moyens de paiement supplémentaires via des liens de paiement à vos couleurs envoyés par SMS. **Quelles sont mes obligations de conformité PCI ?** Shuttle est conforme PCI DSS niveau 1. Comme les données de carte ne touchent jamais vos systèmes, vos obligations PCI sont fortement réduites. Vous réalisez toujours votre propre auto-évaluation. **Combien de temps faut-il pour la mise en place ?** Un script de démo vous permet d'être opérationnel en quelques heures. Une mise en place sur mesure prend généralement une semaine avec un développeur. **Quels opérateurs vocaux sont pris en charge ?** Aujourd'hui, Twilio est le connecteur en production. Shuttle fonctionne avec Twilio aujourd'hui, et avec n'importe quel opérateur bientôt. **Quelle est la différence entre le connecteur Shuttle et un connecteur générique sur Twilio ?** Sur Twilio, le connecteur Shuttle est préconçu et optimisé pour des processeurs spécifiques, avec une gestion de paiement de bout en bout, supervision prête pour la production et gestion multi-marchands. Le connecteur générique est le connecteur léger et ouvert de Twilio : il vous laisse gérer vous-même l'intégration PSP, utile pour des prestataires personnalisés et les tests. ## Prêt à ajouter les paiements vocaux ? Parlez à notre équipe et voyez comment Shuttle Voice Checkout peut vous faire encaisser des paiements par téléphone en quelques jours, pas en quelques mois. ## Links - [En savoir plus →](/integrations/twilio-pay/) - [Installer](https://merchant.shuttleglobal.com/signup/twilio) - [Nous contacter](/discovery/) - [Commencer](https://merchant.shuttleglobal.com/) - [Embedded Payment Layer](/fr/platforms/) - [Réserver un appel](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/3d-secure/ --- # What Is 3D Secure? | Shuttle Glossary > 3D Secure is an authentication protocol that adds a verification step during online card payments, reducing fraud and shifting chargeback liability from the merchant to the card issuer. # What Is 3D Secure? 3D Secure is an authentication protocol that adds a verification step during online card payments, reducing fraud and shifting chargeback liability from the merchant to the card issuer. 3D Secure (3DS) is an authentication protocol designed to reduce fraud in card-not-present transactions -- that is, online and phone payments where the physical card is not swiped or tapped. Originally introduced by Visa under the brand name "Verified by Visa," and adopted by Mastercard as "Mastercard SecureCode," the protocol adds an extra verification step between the cardholder and their issuing bank during checkout. The "3D" refers to the three domains involved: the merchant (acquirer domain), the card network (interoperability domain), and the issuing bank (issuer domain). The current version, 3D Secure 2 (3DS2), represents a significant improvement over the original. Where 3DS1 typically redirected the customer to a separate bank page to enter a static password -- causing high cart abandonment -- 3DS2 uses a risk-based approach. It passes over 100 data points to the issuing bank, including device fingerprint, transaction history, and shipping address. If the bank considers the transaction low-risk, the authentication happens silently in the background with no customer interaction at all. This "frictionless flow" can approve transactions in under a second. Only higher-risk transactions trigger a challenge, which now usually takes the form of a one-time passcode sent via SMS or a push notification to the customer's banking app. Beyond fraud prevention, 3D Secure has a critical business implication: liability shift. When a transaction is successfully authenticated via 3DS, liability for fraudulent chargebacks shifts from the merchant to the card-issuing bank. This means the merchant is protected from losses on authenticated transactions that later turn out to be fraudulent. In the European Economic Area, 3DS2 is also a primary mechanism for meeting Strong Customer Authentication (SCA) requirements under PSD2, making it not just beneficial but legally required for most online card payments in that region. Shuttle Global supports 3D Secure across its payment products, handling the protocol complexity so platforms do not have to build and maintain their own 3DS integration. Through Embedded Payments, Shuttle manages the 3DS2 authentication flow within the checkout experience -- initiating the challenge when required by the issuer and processing the frictionless flow when conditions allow. Because Shuttle connects to over 40 PSPs, it normalises the differences in how each processor implements 3DS2, giving platforms a single consistent integration regardless of which acquirer sits behind the transaction. For Payment Links, the 3DS flow is handled entirely within Shuttle's hosted checkout page. This means platforms gain the fraud protection and liability shift benefits of 3D Secure without adding any authentication logic to their own codebase. ## Related Terms ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ### PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. ### SCA (Strong Customer Authentication) Strong Customer Authentication (SCA) is a European regulatory requirement under PSD2 that mandates multi-factor authentication for most electronic payments to reduce fraud. ## See how Shuttle handles 3D Secure Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [SCA (Strong Customer Authentication) Strong Customer Authentication (SCA) is a European regulatory requirement under PSD2 that mandates multi-factor authentication for most electronic payments to reduce fraud.](/glossary/sca) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/aml/ --- # What Is AML (Anti-Money Laundering)? | Shuttle Glossary > AML (Anti-Money Laundering) refers to the laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income through the financial system. # What Is AML (Anti-Money Laundering)? AML (Anti-Money Laundering) refers to the laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income through the financial system. Anti-Money Laundering (AML) is the framework of laws, regulations, and operational procedures that financial institutions and payment companies must follow to detect and prevent money laundering. Money laundering is the process by which criminals move illicitly obtained funds through legitimate financial channels to obscure their origin -- typically through three stages known as placement (introducing dirty money into the system), layering (moving it through multiple transactions to create confusion), and integration (withdrawing it as apparently clean funds). AML regulations exist to disrupt this process at every stage and are enforced by financial regulators and law enforcement agencies worldwide. The practical requirements of AML compliance include customer due diligence (KYC), transaction monitoring, suspicious activity reporting, record keeping, and employee training. Transaction monitoring systems analyse payment flows in real time or near-real time, flagging patterns that may indicate laundering -- such as rapid movement of funds through multiple accounts, transactions just below reporting thresholds (known as structuring), or payments to and from high-risk jurisdictions. When suspicious activity is identified, the organisation is required to file a Suspicious Activity Report (SAR) with the relevant financial intelligence unit, such as FinCEN in the United States or the National Crime Agency in the UK. For payment companies and the platforms they serve, AML obligations create a layered responsibility structure. The PSP or acquirer is regulated and must have its own AML programme. But platforms that facilitate payments -- particularly those that onboard merchants or sub-merchants -- also bear responsibility for the transactions flowing through their systems. A marketplace that allows sellers to receive payments is, in regulatory terms, facilitating money transmission, and regulators expect it to have appropriate controls in place. Ignorance of what merchants are doing on the platform is not a defence. Shuttle Global operates within this regulatory framework as a PCI DSS Level 1 certified payments infrastructure provider connecting platforms to over 40 PSPs. Shuttle's architecture supports the AML compliance needs of both the platform and the downstream processors. Transaction data flowing through Shuttle's payment layer can be monitored and flagged according to the risk rules established by the platform and its PSP partners. During merchant onboarding via Embedded Payments, Shuttle facilitates the due diligence steps that PSPs require before activating a merchant account. By centralising the payment flow through a single infrastructure layer, Shuttle gives platforms clearer visibility into transaction patterns across all their PSP connections -- which is materially easier to monitor and audit than fragmented payment data spread across multiple direct integrations. ## Related Terms ### KYC (Know Your Customer) KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide. ### Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. ## See how Shuttle handles AML (Anti-Money Laundering) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [KYC (Know Your Customer) KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide.](/glossary/kyc) - [Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor.](/glossary/merchant-onboarding) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/capture/ --- # What Is Capture? | Shuttle Glossary > Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement. # What Is Capture? Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement. Capture is the second half of the authorize-and-capture payment model. After a merchant obtains a pre-authorization -- confirming that the cardholder has sufficient funds and placing a hold on the transaction amount -- the capture step signals to the acquiring bank that the merchant is ready to collect those funds. Once captured, the transaction enters the settlement queue and the held amount is transferred from the cardholder's issuing bank to the merchant's account through the normal clearing and settlement cycle. Without capture, an authorisation will eventually expire and the held funds will be released back to the cardholder. Most payment gateways and processors support both manual and automatic capture. With automatic capture, the authorisation and capture occur in a single step -- the payment is finalised immediately at the point of sale. Manual capture separates these steps, giving the merchant explicit control over when funds are collected. This is critical for business models where fulfilment is deferred: an online retailer might authorise payment when the order is placed but only capture when the warehouse confirms the item has shipped. Similarly, service-based businesses may authorise a deposit at booking and capture the remaining balance upon completion. Capture also supports partial amounts. If a customer orders three items but only two are available for shipment, the merchant can capture the amount corresponding to the shipped items and void or reduce the remaining authorisation. This flexibility reduces customer friction and avoids the need for post-settlement refunds. However, not all PSPs handle partial captures identically -- some require the remaining authorised amount to be explicitly voided, while others release it automatically after a timeout period. Shuttle Global normalises capture behaviour across its network of 40+ PSPs, so platforms using Embedded Payments or Payment Links can issue captures through a single API call without worrying about processor-specific nuances. For Voice Checkout scenarios -- such as a contact centre agent confirming a telephone order -- Shuttle allows the capture to be triggered programmatically once the order is verified, keeping the payment flow seamless for both the agent and the customer. By abstracting the differences in how each PSP handles full captures, partial captures, and authorisation expiry, Shuttle ensures that platforms can build consistent payment workflows regardless of the underlying processor. ## Related Terms ### Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment. ### Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. ### Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees. ## See how Shuttle handles Capture Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment.](/glossary/pre-authorization) - [Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account.](/glossary/settlement) - [Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees.](/glossary/void) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/chargeback/ --- # What Is a Chargeback? | Shuttle Glossary > A chargeback is a forced reversal of a payment transaction, initiated by the cardholder's bank, that returns funds to the customer and debits the merchant. # What Is a Chargeback? A chargeback is a forced reversal of a payment transaction, initiated by the cardholder's bank, that returns funds to the customer and debits the merchant. A chargeback occurs when a cardholder disputes a transaction with their issuing bank, and the bank forcibly reverses the payment. Unlike a refund -- which the merchant initiates voluntarily -- a chargeback is imposed on the merchant, often without prior notice. The issuing bank withdraws the disputed amount from the merchant's acquiring bank, which in turn debits the merchant's account. In addition to losing the transaction revenue, the merchant is typically charged a chargeback fee ranging from $15 to $100 or more, depending on the acquirer and the merchant's chargeback history. Chargebacks were originally designed as a consumer protection mechanism, giving cardholders recourse when goods were not delivered, when a charge was unauthorised, or when a transaction was fraudulent. However, the system is frequently exploited through what the industry calls "friendly fraud" -- cases where the cardholder received the goods or service but disputes the charge anyway, perhaps because they do not recognise the merchant name on their statement, regret the purchase, or are deliberately abusing the process. Card networks track each merchant's chargeback ratio, and exceeding thresholds (typically 1% of transactions) can trigger monitoring programmes, increased processing fees, or even termination of the merchant's processing agreement. Managing chargebacks effectively requires a combination of prevention and response. Prevention strategies include using clear billing descriptors, sending order confirmation and shipping notifications, implementing strong authentication (such as 3D Secure), and maintaining responsive customer service so disputes are resolved before they escalate to chargebacks. When a chargeback does occur, merchants can submit a representment -- a formal rebuttal with evidence that the transaction was legitimate -- though success rates vary and the process is time-consuming. For platforms that process payments on behalf of sub-merchants, chargebacks present additional complexity. The platform must decide how chargeback liability is allocated, manage the representment process across potentially thousands of merchants, and ensure that chargeback monitoring thresholds are maintained at both the platform and sub-merchant level. Shuttle Global helps platforms manage this complexity by providing unified chargeback data and dispute handling across all connected PSPs. Whether a transaction originated through Embedded Payments, a Payment Link, or Voice Checkout, Shuttle surfaces chargeback notifications and dispute details through a single integration, enabling platforms to respond quickly and maintain healthy chargeback ratios without juggling multiple processor-specific dispute workflows. ## Related Terms ### Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. ### Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment. ## See how Shuttle handles Chargeback Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment.](/glossary/pre-authorization) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/dtmf/ --- # What Is DTMF? | Shuttle Glossary > DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents. # What Is DTMF? DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents. DTMF stands for Dual-Tone Multi-Frequency, the technical standard behind the tones you hear when pressing keys on a telephone keypad. Each key press generates a unique combination of two audio frequencies -- one from a high-frequency group and one from a low-frequency group -- which the telephone network decodes to identify the digit pressed. DTMF replaced the older pulse dialling system decades ago and remains the foundation of telephone-based input, from navigating automated phone menus to entering PINs and account numbers. In the payments industry, DTMF has taken on a specialised and critical role: enabling secure card payment capture during telephone calls. When a customer needs to pay over the phone, DTMF masking (also called DTMF suppression or DTMF clamping) allows the caller to key their card number directly on their phone's keypad while the tones are intercepted and stripped from the audio stream before they reach the contact centre agent or call recording system. The digits never reach the agent, and the call recording captures no card data. The digits are routed securely to the payment processor, and the transaction is completed without any cardholder data entering the contact centre environment. This technique is fundamental to PCI DSS compliance for telephone payments. Without DTMF masking, any call centre that takes card payments over the phone brings its entire telephony infrastructure, call recording systems, and agent workstations into PCI scope -- requiring costly security controls, regular audits, and significant operational restrictions. DTMF masking removes cardholder data from the contact centre environment entirely, dramatically reducing PCI scope and the associated compliance burden. Shuttle Global's Voice Checkout product is built on DTMF masking technology. When a platform's contact centre agent needs to collect a payment during a call, Shuttle's integration with Twilio (via Pay Connectors) and other telephony providers intercepts the caller's key presses, securely captures the card data within Shuttle's PCI DSS Level 1 certified environment, and processes the payment through the appropriate PSP -- all while the agent remains on the line but never hears or sees the card number. This approach keeps card data out of the platform and its contact centre, which is what shrinks their PCI scope, turning what would otherwise be a major compliance project into a simple API integration. ## Related Terms ### IVR (Interactive Voice Response) IVR is a telephony technology that allows callers to interact with an automated system using voice commands or keypad inputs to navigate menus, retrieve information, or complete transactions. ### PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. ## See how Shuttle handles DTMF (Dual-Tone Multi-Frequency) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [DTMF masking](/guides/dtmf-payments/) - [Pay Connectors](/guides/twilio-pay-connectors/) - [IVR (Interactive Voice Response) IVR is a telephony technology that allows callers to interact with an automated system using voice commands or keypad inputs to navigate menus, retrieve information, or complete transactions.](/glossary/ivr) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/embedded-payments/ --- # What Are Embedded Payments? | Shuttle Glossary > Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. # What Are Embedded Payments? Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. Embedded payments refer to the integration of payment processing capabilities directly into a software platform, application, or digital experience so that paying becomes a seamless part of the user workflow rather than a separate step handled by an external payment page. Instead of redirecting customers to a third-party checkout, the platform presents payment fields, processes transactions, and manages the payment lifecycle within its own interface. For the end user, the payment feels native to the product they are already using. The shift toward embedded payments has been driven by two converging forces. First, platforms and vertical SaaS companies have recognised that payments are not just a utility but a strategic asset -- owning the payment experience increases user engagement, reduces churn, and opens new revenue streams through transaction fees. Second, modern APIs and white-label payment infrastructure have made it technically feasible for non-financial companies to embed payments without becoming regulated payment institutions themselves. A property management platform can let landlords collect rent in-app; a healthcare scheduling tool can process co-pays at booking; a logistics platform can settle carrier payments automatically. However, embedding payments is not as simple as dropping in a payment form. The platform must consider PCI compliance, multi-currency support, regulatory requirements across geographies, reconciliation, dispute handling, and the ability to support multiple payment methods. Building this infrastructure from scratch requires deep payments expertise and significant ongoing maintenance. Many platforms initially integrate directly with a single PSP, only to discover that they are locked into that provider's limitations -- a single acquirer's approval rates, a single set of supported payment methods, a single settlement currency. Shuttle Global's Embedded Payments product is designed specifically for platforms that want to own the payment experience without building the underlying infrastructure. Shuttle provides a white-label payment layer that connects to 40+ PSPs through a single integration, so platforms can offer their merchants the best possible payment coverage without managing multiple PSP relationships. The platform's branding remains front and centre -- end users see only the platform's checkout, not Shuttle's -- while Shuttle handles PCI compliance and tokenisation behind the scenes. , the months or years a direct build would require. ## Related Terms ### Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship. ### Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations. ### White-Label Payments White-label payments allow a platform to offer branded payment processing to its users by reselling or embedding another company's payment infrastructure under its own brand. ## See how Shuttle handles Embedded Payments Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship.](/glossary/payment-facilitator) - [Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations.](/glossary/payment-layer) - [White-Label Payments White-label payments allow a platform to offer branded payment processing to its users by reselling or embedding another company's payment infrastructure under its own brand.](/glossary/white-label-payments) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/ --- # Payments & Compliance Glossary | Shuttle > Learn key payment processing, compliance, and fintech terms. From PCI DSS to payment orchestration -- plain-language definitions with real-world context. # Payments & Compliance Glossary Plain-language definitions for the payment processing, compliance, and fintech terms you'll encounter when building or managing payment infrastructure. ## Have a question about payments? Our team can help you make sense of payment processing and compliance. ## Links - [3D Secure 3D Secure is an authentication protocol that adds a verification step during online card payments, reducing fraud and shifting chargeback liability from the merchant to the card issuer.](/glossary/3d-secure) - [AML (Anti-Money Laundering) AML (Anti-Money Laundering) refers to the laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income through the financial system.](/glossary/aml) - [Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement.](/glossary/capture) - [Chargeback A chargeback is a forced reversal of a payment transaction, initiated by the cardholder's bank, that returns funds to the customer and debits the merchant.](/glossary/chargeback) - [DTMF (Dual-Tone Multi-Frequency) DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents.](/glossary/dtmf) - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [IVR (Interactive Voice Response) IVR is a telephony technology that allows callers to interact with an automated system using voice commands or keypad inputs to navigate menus, retrieve information, or complete transactions.](/glossary/ivr) - [KYC (Know Your Customer) KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide.](/glossary/kyc) - [Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor.](/glossary/merchant-onboarding) - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship.](/glossary/payment-facilitator) - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations.](/glossary/payment-layer) - [Payment Links Payment links are unique URLs that direct a customer to a hosted checkout page where they can complete a payment without the merchant needing a website or integrated checkout.](/glossary/payment-links) - [Payment Monetization Payment monetization is the strategy of generating revenue from payment transactions processed through a platform, typically by charging fees or earning margin on each transaction.](/glossary/payment-monetization) - [Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience.](/glossary/payment-orchestration) - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [PCI DSS Level 1 PCI DSS Level 1 is the highest tier of PCI compliance, required for organisations processing over six million card transactions annually and validated through an on-site audit by a Qualified Security Assessor.](/glossary/pci-dss-level-1) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Platform Payments Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants.](/glossary/platform-payments) - [Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment.](/glossary/pre-authorization) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [PSP-Neutral PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration.](/glossary/psp-neutral) - [Reconciliation Reconciliation is the process of matching payment transaction records against bank deposits and processor reports to ensure every payment is accounted for.](/glossary/reconciliation) - [Refund A refund is a merchant-initiated reversal that returns funds from a settled payment transaction back to the cardholder's account.](/glossary/refund) - [SCA (Strong Customer Authentication) Strong Customer Authentication (SCA) is a European regulatory requirement under PSD2 that mandates multi-factor authentication for most electronic payments to reduce fraud.](/glossary/sca) - [Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account.](/glossary/settlement) - [Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments.](/glossary/tokenization) - [Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees.](/glossary/void) - [White-Label Payments White-label payments allow a platform to offer branded payment processing to its users by reselling or embedding another company's payment infrastructure under its own brand.](/glossary/white-label-payments) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/ivr/ --- # What Is IVR? | Shuttle Glossary > IVR is a telephony technology that allows callers to interact with an automated system using voice commands or keypad inputs to navigate menus, retrieve information, or complete transactions. # What Is IVR? IVR is a telephony technology that allows callers to interact with an automated system using voice commands or keypad inputs to navigate menus, retrieve information, or complete transactions. IVR stands for Interactive Voice Response, a technology that enables automated telephone systems to interact with callers through pre-recorded voice prompts and DTMF keypad inputs (and increasingly, through speech recognition). When you call a business and hear "Press 1 for sales, press 2 for support," you are interacting with an IVR system. These systems route calls, collect information, authenticate callers, and in many cases resolve enquiries entirely without involving a human agent. IVR has been a cornerstone of contact centre operations for decades, handling everything from account balance enquiries to appointment scheduling. In the context of payments, IVR systems serve as a channel for collecting payment card details over the telephone without requiring a live agent. A caller navigating an IVR can be prompted to enter their card number, expiry date, and CVV using their phone's keypad, and the system processes the payment automatically. This self-service payment model is widely used by utility companies, government agencies, healthcare providers, and subscription services -- any organisation that needs to collect payments at scale over the phone while minimising agent involvement and labour costs. However, IVR payment systems introduce significant PCI compliance considerations. If the IVR environment stores, processes, or transmits cardholder data, the entire telephony infrastructure -- servers, network components, and call recording systems -- falls within PCI scope. The security requirements for PCI compliance in a telephony environment are substantial, and many organisations struggle to maintain them. This is why modern IVR payment solutions increasingly rely on techniques like DTMF masking and secure handoff to external payment processors to keep cardholder data out of the organisation's own infrastructure. Shuttle Global's Voice Checkout can operate in both agent-assisted and IVR-driven payment flows. In an IVR scenario, the caller is routed to Shuttle's secure payment environment where they enter their card details via DTMF. Shuttle captures the data within its PCI DSS Level 1 certified infrastructure, processes the payment through the provider configured for that payment type, and returns the result to the IVR system -- all without cardholder data ever touching the platform's telephony environment. For platforms that need both automated and agent-assisted payment collection, Shuttle provides a single integration that covers both modes, eliminating the need to maintain separate PCI-compliant IVR infrastructure alongside agent-facing payment tools. ## Related Terms ### DTMF (Dual-Tone Multi-Frequency) DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents. ### PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. ## See how Shuttle handles IVR (Interactive Voice Response) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [DTMF (Dual-Tone Multi-Frequency) DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents.](/glossary/dtmf) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/kyc/ --- # What Is KYC (Know Your Customer)? | Shuttle Glossary > KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide. # What Is KYC (Know Your Customer)? KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide. KYC, or Know Your Customer, is the set of procedures that financial institutions and payment companies use to verify the identity of their customers and assess the risk they may pose. At its core, KYC answers three questions: who is this customer, are they who they claim to be, and do they present any risk of involvement in financial crime? The process typically involves collecting identity documents, verifying them against trusted data sources, screening the individual or business against sanctions lists and politically exposed persons (PEP) databases, and making an ongoing assessment of whether the customer's transaction patterns are consistent with their stated profile. KYC is not optional. It is mandated by financial regulations in virtually every jurisdiction, including the EU's Anti-Money Laundering Directives, the US Bank Secrecy Act, and the UK's Money Laundering Regulations. These laws require regulated entities to perform due diligence on their customers before establishing a business relationship and to maintain that diligence throughout the relationship. The depth of diligence scales with the perceived risk -- a sole trader processing low-value domestic payments will undergo lighter checks than a cross-border marketplace handling high-value transactions in high-risk jurisdictions. Failure to meet KYC obligations can result in regulatory fines, criminal liability for officers, and loss of banking or payment processing relationships. For platforms that onboard merchants or sub-merchants, KYC is one of the most friction-heavy parts of the process. Merchants must submit documents, those documents must be verified, screening must be performed, and risk assessments must be documented -- all before the merchant can begin processing payments. Done poorly, KYC creates delays that cause merchant drop-off. Done without sufficient rigour, it exposes the platform to regulatory action and financial crime liability. Shuttle Global's infrastructure supports the merchant onboarding workflows that platforms need to meet KYC obligations efficiently. When a platform uses Shuttle's Embedded Payments to offer payment processing to its own customers, Shuttle's onboarding layer can facilitate the collection, verification, and risk assessment steps required by the downstream PSPs. Because Shuttle connects to over 40 payment service providers, each with their own KYC requirements, the platform benefits from a normalised onboarding experience rather than having to implement bespoke KYC flows for every processor. This reduces onboarding friction for merchants while ensuring the platform and its PSP partners remain compliant with their regulatory obligations. ## Related Terms ### AML (Anti-Money Laundering) AML (Anti-Money Laundering) refers to the laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income through the financial system. ### Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. ## See how Shuttle handles KYC (Know Your Customer) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [AML (Anti-Money Laundering) AML (Anti-Money Laundering) refers to the laws, regulations, and procedures designed to prevent criminals from disguising illegally obtained funds as legitimate income through the financial system.](/glossary/aml) - [Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor.](/glossary/merchant-onboarding) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/merchant-onboarding/ --- # What Is Merchant Onboarding? | Shuttle Glossary > Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. # What Is Merchant Onboarding? Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. Merchant onboarding is the process by which a business is registered, verified, and approved to accept card payments. It encompasses everything from collecting the merchant's business details and banking information to performing identity verification, risk assessment, and regulatory compliance checks before the merchant can begin processing transactions. For a standalone business working directly with an acquiring bank, onboarding can take days or weeks and involve extensive paperwork. For platforms onboarding sub-merchants at scale, the process must be streamlined, automated, and compliant -- all while maintaining the security and risk controls that card networks and regulators require. The core of merchant onboarding is Know Your Customer (KYC) and Know Your Business (KYB) verification. The platform or acquirer must confirm that the merchant is a legitimate business, that its principals are who they claim to be, and that the business does not pose unacceptable risk -- for example, operating in a prohibited industry, having a history of excessive chargebacks, or being associated with fraud or money laundering. These checks typically involve verifying government-issued identification, cross-referencing sanctions and watchlists, validating business registration documents, and assessing the merchant's financial history and processing volume expectations. For platforms facilitating payments on behalf of many merchants, onboarding speed and conversion rate are critical metrics. Every additional step, form field, or day of waiting in the onboarding process increases the risk that the merchant will abandon the process and take their business elsewhere. The best platform payment experiences make onboarding feel effortless -- collecting the minimum required information upfront, performing verification checks asynchronously, and activating the merchant for processing as quickly as possible while layering in additional monitoring and stepped limits as the merchant builds a transaction history. Shuttle Global supports merchant onboarding as part of its platform payments infrastructure. When a platform integrates Shuttle's Embedded Payments, Shuttle manages the onboarding workflow for sub-merchants -- collecting required information, performing KYC/KYB checks, and activating merchants for processing across Shuttle's network of 40+ PSPs. Because Shuttle is PSP-neutral, a merchant onboarded through Shuttle is not locked into a single acquirer; the platform can route that merchant's transactions through whichever PSP offers the best performance, cost, or payment method coverage for their specific needs. This approach combines onboarding speed with long-term commercial flexibility, letting platforms grow their merchant base without the regulatory complexity of becoming a registered payment facilitator themselves. ## Related Terms ### KYC (Know Your Customer) KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide. ### Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship. ### Platform Payments Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants. ## See how Shuttle handles Merchant Onboarding Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [KYC (Know Your Customer) KYC (Know Your Customer) is the process of verifying the identity of customers and assessing their risk profile before and during a business relationship, required by financial regulations worldwide.](/glossary/kyc) - [Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship.](/glossary/payment-facilitator) - [Platform Payments Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants.](/glossary/platform-payments) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/multi-psp/ --- # What Is Multi-PSP? | Shuttle Glossary > Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. # What Is Multi-PSP? Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. Multi-PSP refers to a payment architecture in which a business maintains active connections to more than one payment service provider, using each for the scenarios where it performs best. Instead of relying on a single PSP for all transaction processing, a multi-PSP strategy allows the business to route payments to different providers based on criteria such as geographic region, card type, payment method, currency, transaction value, or real-time performance. The goal is to maximise authorisation rates, reduce processing costs, expand payment method coverage, and eliminate single points of failure. The case for multi-PSP becomes clear when a business analyses its transaction data at a granular level. Authorisation rates -- the percentage of transactions that the issuing bank approves -- vary significantly depending on which PSP routes the transaction, which acquiring bank is used, and whether the transaction is domestic or cross-border. A 2-3 percentage point improvement in authorisation rate might sound small, but on a high-volume platform processing millions of transactions, it translates directly into millions in recovered revenue. Similarly, processing costs vary between PSPs based on their acquiring relationships, interchange optimisation capabilities, and fee structures. A multi-PSP approach lets the business route each transaction through the most cost-effective path. The challenge of multi-PSP is operational complexity. Each PSP has its own API specification, authentication method, webhook format, error taxonomy, and settlement cycle. Maintaining multiple direct integrations means duplicated engineering effort, fragmented reporting, and complex reconciliation. This is why many businesses that adopt a multi-PSP strategy do so through a payment orchestration layer rather than through direct integrations -- the orchestration layer manages the connections and normalises the differences. Shuttle Global's entire infrastructure is built around the multi-PSP model. With connections to over 40 payment service providers, Shuttle gives platforms immediate access to a diverse network of processors and acquirers through a single integration. The platform does not need to negotiate contracts with each PSP, build separate integrations, or manage multiple settlement streams. The platform configures which connected provider handles each payment type, with minimum amount, maximum amount and currency filters. Euro transactions can settle with one acquirer and dollar transactions with another. If a PSP declines a transaction or experiences downtime, Shuttle can automatically cascade to an alternative provider. This multi-PSP capability is embedded into every product: Embedded Payments, Voice Checkout, and Payment Links all route through the same orchestration engine, ensuring that every transaction has the best possible chance of being approved regardless of which channel it originates from. ## Related Terms ### Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience. ### PSP-Neutral PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration. ### PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. ## See how Shuttle handles Multi-PSP Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience.](/glossary/payment-orchestration) - [PSP-Neutral PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration.](/glossary/psp-neutral) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-facilitator/ --- # What Is a Payment Facilitator (PayFac)? | Shuttle Glossary > A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship. # What Is a Payment Facilitator (PayFac)? A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship. A Payment Facilitator, commonly abbreviated as PayFac, is a type of merchant services provider that processes payments on behalf of other businesses -- called sub-merchants -- under its own master merchant account. Instead of each sub-merchant establishing a direct relationship with an acquiring bank, the PayFac acts as the merchant of record and takes responsibility for onboarding, underwriting, transaction monitoring, and fund settlement to its sub-merchants. This model was popularised by companies like Square and Stripe, which made it possible for small businesses to start accepting payments in minutes rather than the days or weeks required by traditional merchant account applications. The PayFac model carries significant responsibility. Because the PayFac is the merchant of record with the acquiring bank, it bears liability for the transactions processed by its sub-merchants. If a sub-merchant commits fraud, generates excessive chargebacks, or violates card network rules, the PayFac is on the hook. This is why PayFacs must perform their own KYC (Know Your Customer) due diligence, implement transaction monitoring and risk management, and maintain reserves to cover potential losses. Becoming a registered PayFac requires approval from the card networks, compliance with PCI DSS, and ongoing regulatory obligations. For platforms and marketplaces, the PayFac model is attractive because it gives them control over the merchant experience -- onboarding, pricing, branding, and payout timing can all be customised. However, building and maintaining a full PayFac operation is a substantial undertaking. It requires regulatory registration, compliance infrastructure, risk and underwriting teams, reserve capital, and ongoing audits. Many platforms discover that the operational burden of being a PayFac exceeds what they anticipated, particularly as they scale into new markets with different regulatory requirements. Shuttle Global offers an alternative path for platforms that want PayFac-like control without the full PayFac burden. Through Shuttle's Embedded Payments, platforms can white-label the payment experience, control merchant onboarding flows, and offer payment acceptance to their customers -- while Shuttle handles the underlying PSP connectivity, PCI compliance, and transaction routing across 40+ providers. Platforms that have already registered as PayFacs can use Shuttle as their processing and routing infrastructure. Platforms that have not can leverage Shuttle's connections to PSPs that offer managed PayFac or marketplace solutions, gaining many of the same benefits without the regulatory registration. Either way, Shuttle's PSP-neutral layer means the platform is not locked into a single acquirer's PayFac programme. ## Related Terms ### Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. ### Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. ### PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. ## See how Shuttle handles Payment Facilitator (PayFac) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor.](/glossary/merchant-onboarding) - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-gateway/ --- # What Is a Payment Gateway? | Shuttle Glossary > A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. # What Is a Payment Gateway? A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. A payment gateway is the technology layer that captures payment information from a customer and securely transmits it to the payment processor or acquirer for authorisation. It is the digital equivalent of the card terminal in a physical shop. When a customer enters their card details on a checkout page, the payment gateway encrypts that data, sends it through the card networks to the issuing bank for approval, and returns the authorisation response -- approved or declined -- back to the merchant's system, typically within one to three seconds. Payment gateways operate at the front line of transaction security. They are responsible for encrypting cardholder data in transit, validating card numbers using algorithms like the Luhn check, supporting fraud screening rules, and initiating authentication protocols like 3D Secure. Because they handle raw card data, gateways must be PCI DSS compliant. Many modern gateways minimise the merchant's PCI scope by providing hosted payment fields or redirect-based checkout flows so that card data is captured directly by the gateway without ever touching the merchant's servers. It is worth distinguishing between a payment gateway and a payment processor, as the terms are often confused. The gateway handles the data capture and communication -- it is the messenger. The processor handles the actual movement of the transaction through the card network and the settlement of funds -- it is the engine. Some companies, particularly large PSPs, operate both a gateway and a processing platform. Others specialise in one layer. A merchant might use one company's gateway with a different company's processing and acquiring infrastructure, though bundled solutions are more common for smaller merchants. Shuttle Global operates as a payment infrastructure layer that sits above individual gateways and processors. When a platform integrates Shuttle's Embedded Payments, the checkout experience uses Shuttle's secure hosted fields as the gateway layer -- capturing and tokenizing card data within Shuttle's PCI Level 1 environment. But Shuttle is not tied to a single downstream processor. It routes the tokenized transaction to whichever PSP or acquirer is configured for that platform, market, or transaction type, drawing on its network of over 40 connected providers. Payment Links function the same way -- Shuttle's hosted checkout page acts as the gateway, with the flexibility to send each payment type to the processor you configured. This architecture means platforms do not need to integrate, certify, and maintain connections to multiple gateways themselves. They get one gateway experience with multi-processor routing built in. ## Related Terms ### Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. ### PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. ### Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments. ## See how Shuttle handles Payment Gateway Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments.](/glossary/tokenization) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-layer/ --- # What Is a Payment Layer? | Shuttle Glossary > A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations. # What Is a Payment Layer? A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations. A payment layer is the software infrastructure that sits between a platform's application and the payment service providers (PSPs), acquirers, and banking systems that actually move money. It provides a unified interface -- typically a single API -- through which the platform can initiate payments, manage refunds, handle disputes, and access transaction data, regardless of which underlying provider is processing any given transaction. The payment layer abstracts away the differences between providers, normalising their varied APIs, data formats, error codes, and settlement behaviours into a consistent experience for the platform. The concept of a payment layer becomes important when a business outgrows the single-PSP model. Early on, integrating directly with one PSP is straightforward. But as the business expands into new markets, adds new payment methods, or needs better authorisation rates, it inevitably needs multiple providers. Without a payment layer, each new PSP means a new integration, a new set of webhooks to handle, a new reconciliation process, and a new dashboard to monitor. The engineering and operational cost compounds quickly, and the business ends up maintaining a fragmented payments stack that is difficult to manage and slow to change. A well-designed payment layer solves this by centralising all payment logic in one place. The platform's application makes a single API call to create a payment, and the layer determines which PSP to route it to, handles tokenization and authentication, manages retries and failover, and returns a normalised response. Reporting and reconciliation are unified across all providers. Adding a new PSP does not require changes to the platform's codebase -- it is a configuration change in the payment layer. Shuttle Global describes itself as a unified payment layer, and this is the architectural pattern it implements. Platforms integrate with Shuttle's API once and gain access to over 40 connected PSPs. The payment layer handles everything downstream: provider selection, tokenization, 3DS authentication and settlement normalisation. Shuttle's Embedded Payments product exposes this layer as a white-label checkout that platforms can embed directly into their applications. Voice Checkout uses the same layer to process phone payments captured via DTMF masking. Payment Links provide a hosted checkout backed by the same multi-PSP infrastructure. In each case, the platform interacts with one consistent layer while Shuttle manages the complexity of the underlying provider network. This is the core value proposition: the platform gets the flexibility of multiple PSPs with the simplicity of a single integration. ## Related Terms ### Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. ### Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. ### Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience. ## See how Shuttle handles Payment Layer Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience.](/glossary/payment-orchestration) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-links/ --- # What Are Payment Links? | Shuttle Glossary > Payment links are unique URLs that direct a customer to a hosted checkout page where they can complete a payment without the merchant needing a website or integrated checkout. # What Are Payment Links? Payment links are unique URLs that direct a customer to a hosted checkout page where they can complete a payment without the merchant needing a website or integrated checkout. A payment link is a URL that a merchant generates and shares with a customer -- via email, SMS, messaging app, or any other channel -- to collect a payment. When the customer clicks the link, they are taken to a hosted checkout page where they can enter their payment details and complete the transaction. The merchant does not need a website, an e-commerce storefront, or a complex payment integration to collect the payment. Payment links effectively turn any communication channel into a payment channel. Payment links have become a critical tool for businesses that operate outside traditional e-commerce workflows. Service-based businesses use them to invoice clients after completing work. Sales teams send them to close deals during or after a phone conversation. Field service operators use them to collect payment on-site without card terminals. In B2B contexts, payment links replace the slow cycle of issuing invoices and waiting for bank transfers, enabling immediate card payment with a single click. Their simplicity makes them accessible to businesses of any size and technical sophistication. Despite their apparent simplicity, payment links involve the same underlying complexity as any card payment -- authorisation, fraud screening, PCI compliance, multi-currency support, and settlement. The hosted checkout page must be secure, mobile-responsive, and capable of presenting the right payment methods for the customer's location and preferences. For platforms generating payment links on behalf of their merchants, the link must also be brandable, configurable, and tied back to the platform's reconciliation and reporting systems. Shuttle Global's Payment Links product provides platforms with a fully hosted, white-label checkout that can be generated programmatically via API or manually through a dashboard. Each link is tied to Shuttle's multi-PSP infrastructure, meaning the checkout page can present the optimal payment methods and route the transaction through the best-performing processor for that geography and card type. For platforms, this extends the same PSP-neutral coverage they get from Embedded Payments into scenarios where a full checkout integration is not practical -- telephone sales follow-ups, email invoicing, or customer support interactions. Combined with Voice Checkout, Payment Links give platforms a way to convert any customer interaction into a completed payment without building or maintaining their own hosted checkout infrastructure. ## Related Terms ### Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ## See how Shuttle handles Payment Links Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-monetization/ --- # What Is Payment Monetization? | Shuttle Glossary > Payment monetization is the strategy of generating revenue from payment transactions processed through a platform, typically by charging fees or earning margin on each transaction. # What Is Payment Monetization? Payment monetization is the strategy of generating revenue from payment transactions processed through a platform, typically by charging fees or earning margin on each transaction. Payment monetization refers to the practice of generating revenue directly from the payment transactions that flow through a platform. Rather than treating payments as a cost centre -- a necessary utility that enables the core product -- platforms that monetize payments turn every transaction into a revenue event. The most common approach is adding a markup to the processing fee: the platform charges its merchants or end users a per-transaction fee that exceeds the cost charged by the underlying payment processor, and the platform retains the difference as margin. This revenue model has become a defining characteristic of successful platform businesses. Companies like Shopify, Toast, and Mindbody generate significant portions of their total revenue from payments, often rivalling or exceeding their software subscription income. The economics are compelling: a platform processing $1 billion in annual payment volume with a 50-basis-point margin on each transaction generates $5 million in payment revenue -- recurring, scalable, and growing in lockstep with the platform's transaction volume. For investors and acquirers, payment monetisation signals platform stickiness and a high-quality revenue stream. However, capturing payment margin requires the platform to control the payment experience and the commercial relationship with the processor. Platforms that simply redirect users to an external checkout or let merchants connect their own Stripe or PayPal accounts have no visibility into -- and no margin on -- those transactions. Meaningful payment monetisation requires the platform to sit in the payment flow: processing transactions through its own merchant account, a payment facilitator model, or a white-label payment infrastructure that routes transactions on the platform's behalf. Shuttle Global lets platforms offer payments without becoming a payment facilitator or building their own processing infrastructure. Through Shuttle's Embedded Payments, platforms process transactions through Shuttle's multi-PSP layer and earn margin on every payment -- online transactions, Payment Links, and Voice Checkout payments alike. Shuttle handles the underlying PSP relationships, PCI compliance, and transaction routing, while the platform defines its own pricing and retains the spread. Because Shuttle connects to 40+ PSPs, platforms can optimise not just their revenue but also their cost basis -- routing transactions through the most cost-effective processor for each payment method and geography, thereby maximising the margin available to monetise. ## Related Terms ### Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. ### Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship. ### Platform Payments Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants. ## See how Shuttle handles Payment Monetization Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [Payment Facilitator (PayFac) A Payment Facilitator (PayFac) is a company that onboards and underwrites sub-merchants under its own master merchant account, enabling platforms and marketplaces to offer payment acceptance without each merchant needing their own acquiring relationship.](/glossary/payment-facilitator) - [Platform Payments Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants.](/glossary/platform-payments) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-orchestration/ --- # What Is Payment Orchestration? | Shuttle Glossary > Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience. # What Is Payment Orchestration? Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience. Payment orchestration is the practice of managing and routing payment transactions across multiple payment service providers, acquirers, and payment methods through a single unified layer. Rather than being locked into a single PSP for all transactions, an orchestration approach enables a business to route each transaction to the provider most likely to process it successfully -- based on factors like the card's issuing country, the transaction currency, the payment method, the provider's real-time performance, and the cost of processing. The orchestration layer acts as a central nervous system for payments, making routing decisions, handling failover, normalising data, and aggregating reporting across all connected providers. The need for payment orchestration emerged as businesses began operating across multiple markets and discovered that no single PSP delivers optimal performance everywhere. A PSP with strong authorisation rates for UK-issued cards may underperform on German transactions. A provider with excellent credit card processing may lack support for popular local payment methods like iDEAL, PIX, or GrabPay. Without orchestration, the business faces an unpleasant choice: accept suboptimal performance from a single provider, or build and maintain separate integrations to multiple providers -- each with its own API, data format, settlement process, and reporting dashboard. Payment orchestration solves this by providing a single integration point that abstracts the complexity of multi-provider management. The business integrates once with the orchestration layer, which handles the downstream connections to each PSP. When a transaction comes in, the orchestration engine evaluates the available routes and selects the optimal one. If the primary route fails -- whether due to a soft decline, a processor outage, or a risk flag -- the engine can automatically retry the transaction through an alternative provider. This cascade logic alone can recover a meaningful percentage of transactions that would otherwise be lost. Shuttle Global is a payment layer connecting to over 40 PSPs through a single API. What distinguishes Shuttle's approach is that multi-PSP connectivity is not an add-on -- it is the foundation of every product. When a platform deploys Shuttle's Embedded Payments, every transaction runs through the provider the platform configured for that payment type. When a contact centre uses Voice Checkout, the payment captured via DTMF masking runs through the same connected providers. Payment Links, similarly, are not tied to a single processor. This means platforms using Shuttle are not just getting a payment gateway -- they are getting a payment layer where they configure which provider handles each payment type, without any additional integration work on the platform's side. ## Related Terms ### Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. ### Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations. ### PSP-Neutral PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration. ## See how Shuttle handles Payment Orchestration Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations.](/glossary/payment-layer) - [PSP-Neutral PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration.](/glossary/psp-neutral) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/payment-processor/ --- # What Is a Payment Processor? | Shuttle Glossary > A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. # What Is a Payment Processor? A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. A payment processor is the company that handles the technical execution of a payment transaction. When a customer taps their card or submits their details online, it is the processor that routes the transaction data through the card network to the issuing bank, receives the authorisation response, and later facilitates the settlement of funds from the issuing bank to the acquiring bank and ultimately to the merchant's account. Processors operate the rails on which electronic payments travel -- they are the infrastructure behind the scenes of every card transaction. There are two main categories: front-end processors and back-end processors. Front-end processors connect to card networks on behalf of acquiring banks and handle the real-time authorisation of transactions. Back-end processors handle settlement -- the batch process of moving approved funds between banks at the end of each business day. Many large payment companies act as both front-end and back-end processors, but the distinction matters because authorisation speed and settlement timing are affected by different parts of the chain. A processor with fast authorisation but slow settlement still creates cash flow challenges for merchants. Processor performance varies meaningfully across geographies, card types, and industries. A processor with strong domestic routing in the US may have poor authorisation rates for cross-border European transactions. A processor optimised for e-commerce may lack support for MOTO (mail order/telephone order) transaction types that contact centres require. These performance differences are not always visible to platforms at integration time -- they emerge over time as transaction volumes grow and diversify. Shuttle Global addresses this variability by abstracting the processor layer entirely. Platforms integrate with Shuttle's unified API, and Shuttle handles the connection to over 40 processors and acquirers across multiple regions. This architecture lets a platform choose which connected provider handles each payment type, with minimum amount, maximum amount and currency filters. Shuttle makes no per-transaction decision on the platform's behalf. If a processor has an outage, the platform can point that payment type at another connected provider. There is no automatic failover. For platforms using Embedded Payments, Voice Checkout, or Payment Links, this means one integration to maintain instead of one per provider, without managing multiple processor relationships directly. ## Related Terms ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ### PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. ### Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. ## See how Shuttle handles Payment Processor Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account.](/glossary/settlement) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/pci-dss/ --- # What Is PCI DSS? | Shuttle Glossary > PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. # What Is PCI DSS? PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. PCI DSS stands for Payment Card Industry Data Security Standard. It is a set of security requirements created by the major card networks -- Visa, Mastercard, American Express, Discover, and JCB -- and administered by the PCI Security Standards Council. Any organisation that stores, processes, or transmits credit card information must comply with PCI DSS, regardless of its size or transaction volume. The standard exists to protect cardholder data from breaches and fraud, and non-compliance can result in heavy fines, increased processing fees, or the loss of the ability to accept card payments altogether. The standard is organised into twelve core requirements spanning areas such as network security, access control, encryption, vulnerability management, and monitoring. These requirements are not optional suggestions -- they are enforced through regular assessments, and the rigour of those assessments scales with the volume of transactions a company handles. Organisations processing the highest volumes must undergo an annual on-site audit by a Qualified Security Assessor (QSA), while smaller merchants may self-assess using standardised questionnaires. For platforms and SaaS companies that embed payments into their products, PCI DSS compliance is one of the most significant technical and operational hurdles. Every component that touches cardholder data -- from the checkout form to the backend server that routes the transaction -- falls within PCI scope. This is why many businesses choose to offload as much of that burden as possible to a certified payments infrastructure partner rather than building and maintaining compliance in-house. Shuttle Global is PCI DSS Level 1 certified, the highest tier of compliance. This means platforms that integrate Shuttle's Embedded Payments, Voice Checkout, or Payment Links have card data captured inside Shuttle's certified environment and tokenised with the merchant's own gateway, rather than shouldering the full compliance burden themselves. With Voice Checkout, for example, Shuttle uses DTMF masking so that card numbers spoken or keyed over the phone never reach the platform's contact centre environment -- keeping the platform's PCI scope limited. By handling tokenization, secure data routing, and PSP connectivity within its own certified infrastructure, Shuttle lets its customers focus on their core product while knowing the payments layer meets the industry's strictest security standard. ## Related Terms ### PCI DSS Level 1 PCI DSS Level 1 is the highest tier of PCI compliance, required for organisations processing over six million card transactions annually and validated through an on-site audit by a Qualified Security Assessor. ### PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. ### Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments. ## See how Shuttle handles PCI DSS Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [PCI DSS Level 1 PCI DSS Level 1 is the highest tier of PCI compliance, required for organisations processing over six million card transactions annually and validated through an on-site audit by a Qualified Security Assessor.](/glossary/pci-dss-level-1) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments.](/glossary/tokenization) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/pci-dss-level-1/ --- # What Is PCI DSS Level 1? | Shuttle Glossary > PCI DSS Level 1 is the highest tier of PCI compliance, required for organisations processing over six million card transactions annually and validated through an on-site audit by a Qualified Security Assessor. # What Is PCI DSS Level 1? PCI DSS Level 1 is the highest tier of PCI compliance, required for organisations processing over six million card transactions annually and validated through an on-site audit by a Qualified Security Assessor. PCI DSS Level 1 is the most stringent tier of compliance within the Payment Card Industry Data Security Standard framework. It applies to any service provider or merchant that processes, stores, or transmits more than six million card transactions per year -- or any entity that the card brands designate as Level 1 regardless of volume. Unlike lower tiers, which may permit self-assessment questionnaires, Level 1 compliance demands an annual on-site audit conducted by an independent Qualified Security Assessor (QSA), along with quarterly network vulnerability scans performed by an Approved Scanning Vendor (ASV). The audit process for Level 1 is extensive. Assessors examine everything from physical access controls in data centres to the encryption algorithms used in transit and at rest. They review code deployment practices, incident response plans, logging and monitoring infrastructure, employee training programmes, and vendor management policies. The resulting Report on Compliance (ROC) provides a detailed, evidence-backed attestation that the organisation meets all twelve PCI DSS requirements. This is not a checkbox exercise -- it requires ongoing investment in security operations, architecture, and governance. For platforms evaluating a payments partner, PCI DSS Level 1 certification is one of the clearest signals that a provider takes data security seriously at an enterprise scale. It means the provider's entire payment-handling infrastructure has been independently verified to meet the same standard applied to the world's largest banks and processors. If the provider is not Level 1 certified, downstream customers may inherit additional compliance obligations or face greater exposure in the event of a breach. Shuttle Global holds PCI DSS Level 1 certification, which directly benefits every platform that integrates its payment infrastructure. When a SaaS company uses Shuttle's Embedded Payments to offer white-label checkout to its end users, that checkout is running on Level 1 certified rails. When a contact centre deploys Shuttle's Voice Checkout, the DTMF masking and secure token handling happen inside Shuttle's Level 1 environment -- not the call centre's. This architectural choice means the platform dramatically reduces its own PCI scope, avoids the six-figure cost of pursuing Level 1 certification independently, and can confidently tell its customers and auditors that cardholder data is handled by infrastructure held to the industry's highest standard. ## Related Terms ### PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. ### PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. ## See how Shuttle handles PCI DSS Level 1 Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/pci-scope/ --- # What Is PCI Scope? | Shuttle Glossary > PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. # What Is PCI Scope? PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. PCI scope refers to the boundary around all systems, network segments, personnel, and processes that are involved in -- or could affect the security of -- cardholder data. If a server handles card numbers, it is in scope. If a workstation sits on the same network segment as that server, it is likely in scope too. Even employees who never directly see card data may fall within scope if they have access to systems that do. Determining PCI scope is the critical first step in any compliance effort, because everything inside that boundary must meet the full set of PCI DSS requirements. The challenge for most organisations is that PCI scope tends to expand in ways that are not immediately obvious. A CRM system that logs call recordings where customers read out their card numbers is in scope. A database that caches transaction details containing the primary account number is in scope. A developer's laptop that can SSH into a production payment server is, potentially, in scope. The larger the scope, the more expensive and complex compliance becomes -- more systems to harden, more people to train, more audit evidence to gather. This is why scope reduction is one of the most important goals in any payment architecture. Techniques like tokenization, network segmentation, and the use of hosted payment fields are all designed to shrink the number of systems that ever touch raw cardholder data. The smaller the scope, the lower the compliance cost, the faster the audit, and the smaller the attack surface. Shuttle Global's architecture is purpose-built to minimise PCI scope for its customers. With Embedded Payments, card data is captured in Shuttle's hosted payment fields and tokenized before it ever reaches the platform's backend -- meaning the platform's own servers never see or store a card number. With Voice Checkout, Shuttle's DTMF masking technology intercepts keypad tones on the telephony layer so that the contact centre agent, the call recording system, and the platform's infrastructure are all kept out of scope. Payment Links work similarly: the entire checkout is hosted on Shuttle's PCI-certified domain. In every product, the design principle is the same -- Shuttle absorbs the PCI scope so the platform does not have to. ## Related Terms ### DTMF (Dual-Tone Multi-Frequency) DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents. ### PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. ### Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments. ## See how Shuttle handles PCI Scope Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [DTMF (Dual-Tone Multi-Frequency) DTMF is the signalling system that generates tones when a caller presses keys on a telephone keypad, widely used in secure voice payment systems to capture card details without exposing them to agents.](/glossary/dtmf) - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [Tokenization Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments.](/glossary/tokenization) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/platform-payments/ --- # What Are Platform Payments? | Shuttle Glossary > Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants. # What Are Platform Payments? Platform payments refers to the payment infrastructure and flows that enable a software platform to process, manage, and monetise transactions on behalf of its users or merchants. Platform payments describe the payment infrastructure, flows, and commercial models that allow a software platform or marketplace to process transactions on behalf of the businesses and individuals that use it. Unlike a single merchant accepting payments for its own goods or services, a platform facilitates payments between its users -- connecting buyers with sellers, patients with providers, tenants with landlords, or any other parties that transact within the platform's ecosystem. The platform sits in the middle of these transactions, managing the payment lifecycle from authorisation through settlement and often earning revenue on each payment processed. The complexity of platform payments stems from the multi-party nature of the transactions. A marketplace might need to split a single payment between a seller, a shipping provider, and the platform's own commission. A vertical SaaS platform might process payments on behalf of hundreds of small businesses, each requiring its own merchant account, settlement schedule, and tax reporting. The platform must handle onboarding, identity verification, compliance, and ongoing monitoring for each of these sub-merchants -- responsibilities that grow linearly with the number of merchants on the platform. Historically, platforms have approached this challenge in one of three ways: becoming a registered payment facilitator (PayFac), using a managed PayFac service like Stripe Connect, or building on top of payment infrastructure that handles the complexity on their behalf. The PayFac model offers maximum control but requires significant regulatory investment. Managed PayFac services simplify compliance but lock the platform into a single PSP and limit commercial flexibility. The third option -- leveraging a PSP-neutral payment layer -- is increasingly attractive because it provides the control and flexibility of the PayFac model without the regulatory overhead or single-provider lock-in. Shuttle Global is purpose-built for platform payments. Through its Embedded Payments product, Shuttle gives platforms a complete payment infrastructure -- merchant onboarding, multi-PSP transaction routing, PCI DSS Level 1 compliance, settlement, and reconciliation -- without requiring the platform to register as a PayFac or commit to a single processor. Platforms can collect payments across online, remote (Payment Links), and telephone (Voice Checkout) channels, all through one integration. Shuttle's PSP-neutral architecture means platforms can offer their merchants the best payment coverage and approval rates by configuring the processor that suits each merchant, while the platform retains commercial flexibility and earns margin on every payment processed. ## Related Terms ### Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. ### Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor. ### Payment Monetization Payment monetization is the strategy of generating revenue from payment transactions processed through a platform, typically by charging fees or earning margin on each transaction. ## See how Shuttle handles Platform Payments Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [Merchant Onboarding Merchant onboarding is the process of registering, verifying, and activating a new business to accept payments through a platform, acquirer, or payment processor.](/glossary/merchant-onboarding) - [Payment Monetization Payment monetization is the strategy of generating revenue from payment transactions processed through a platform, typically by charging fees or earning margin on each transaction.](/glossary/payment-monetization) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/pre-authorization/ --- # What Is Pre-Authorization? | Shuttle Glossary > Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment. # What Is Pre-Authorization? Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment. Pre-authorization (also called an "auth-only" or simply "pre-auth") is a two-step payment process in which the merchant first requests approval from the cardholder's issuing bank to confirm that sufficient funds or credit are available, and the bank places a temporary hold on that amount. No money changes hands at this stage -- the hold simply earmarks the funds, preventing the cardholder from spending them elsewhere. The merchant then has a defined window, typically seven to thirty days depending on the card network, to either capture the payment and complete the transaction or void the authorization and release the hold. This pattern is essential for businesses where the final charge amount may differ from the initial estimate, or where there is a delay between the commitment to pay and the delivery of goods or services. Hotels, car rental companies, and petrol stations routinely pre-authorise an estimated amount at the start of a booking or fuelling session and capture the actual amount later. E-commerce merchants often pre-authorise at the time of order placement and capture only when the item ships, reducing the risk of charging customers for products that turn out to be out of stock. Pre-authorization also plays an important role in fraud prevention and payment risk management. Because the hold verifies the card's validity and the cardholder's available balance, it provides an early signal that the payment method is legitimate. If subsequent fraud checks or order reviews raise concerns, the merchant can void the pre-authorization without incurring the fees and complications associated with refunding a captured payment. This makes the auth-and-capture model significantly cleaner from both a financial and operational standpoint. Shuttle Global supports pre-authorization flows across its entire product suite. Platforms using Embedded Payments can initiate pre-authorisations through Shuttle's unified API and capture or void them later, regardless of which underlying PSP processes the transaction. For Voice Checkout, pre-authorization is particularly valuable in scenarios such as telephone booking for travel or hospitality -- the agent can confirm availability and hold funds during the call, then capture once the reservation is finalised. Shuttle's PSP-neutral architecture ensures that the auth-and-capture lifecycle behaves consistently across processors, sparing platforms from managing the subtle differences in how each PSP handles hold durations, partial captures, and expiration policies. ## Related Terms ### Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement. ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ### Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees. ## See how Shuttle handles Pre-Authorization Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement.](/glossary/capture) - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees.](/glossary/void) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/psp/ --- # What Is a PSP (Payment Service Provider)? | Shuttle Glossary > A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. # What Is a PSP (Payment Service Provider)? A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. A Payment Service Provider (PSP) is a company that enables businesses to accept electronic payments -- including credit cards, debit cards, bank transfers, and alternative payment methods. PSPs act as intermediaries between the merchant, the card networks (Visa, Mastercard, etc.), and the acquiring and issuing banks. They provide the technical infrastructure to capture, authorise, and settle transactions, and they often bundle additional services such as fraud detection, reporting, currency conversion, and merchant onboarding. Well-known PSPs include companies like Adyen, Stripe, Worldpay, and Checkout.com. The term PSP is often used interchangeably with payment gateway or payment processor, but there are meaningful distinctions. A PSP is typically a broader category -- it may operate its own gateway and processing infrastructure, or it may aggregate multiple underlying processors and acquirers. Some PSPs hold acquiring licences and settle funds directly to merchants, while others rely on banking partners for settlement. The specific capabilities, geographic coverage, supported payment methods, and pricing models vary significantly between PSPs, which is why many businesses -- particularly those operating across multiple markets -- end up integrating with more than one. Choosing a PSP is one of the most consequential infrastructure decisions a platform or merchant makes. The PSP directly affects authorisation rates (how many transactions are approved), settlement speed (how quickly the merchant receives funds), payment method coverage (which local methods are available in each market), and cost (interchange, scheme fees, and the PSP's own margin). A PSP that performs well in one market may perform poorly in another. A PSP with strong card processing may lack support for the bank transfer methods that dominate in markets like Germany or the Netherlands. This is where Shuttle Global's PSP-neutral architecture becomes relevant. Rather than forcing platforms to choose a single PSP and live with its limitations, Shuttle provides a unified payment layer that connects to over 40 PSPs. A platform integrates once with Shuttle's API, and Shuttle handles the routing, tokenization, and normalisation across all connected processors. If one PSP delivers better authorisation rates in a particular market, Shuttle can route transactions accordingly. If a platform wants to add a new PSP for a new region, there is no new integration to build. Shuttle's Embedded Payments, Voice Checkout, and Payment Links all operate across this multi-PSP layer, so the platform's products all run on the providers the platform configured, without any additional engineering work. ## Related Terms ### Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ### Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. ## See how Shuttle handles PSP (Payment Service Provider) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/psp-neutral/ --- # What Does PSP-Neutral Mean? | Shuttle Glossary > PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration. # What Does PSP-Neutral Mean? PSP-neutral describes a payment infrastructure approach that is not tied to any single payment service provider, allowing businesses to connect to multiple PSPs through one integration. PSP-neutral (or processor-agnostic) describes a payment infrastructure design philosophy in which the technology layer that manages transactions is not commercially, technically, or architecturally tied to any single payment service provider. A PSP-neutral platform can connect to multiple processors, route transactions dynamically based on performance, cost, or geography, and add or remove PSPs without re-engineering its payment stack. The opposite of PSP-neutral is single-PSP dependency -- where a business's entire payment capability is built on one provider's API, SDK, and commercial terms. Single-PSP dependency is the default starting point for most businesses. When a company first integrates payments, it typically selects one processor -- often Stripe, Adyen, or Braintree -- and builds its payment flow around that provider's specific API. This works well initially, but over time the limitations emerge. The PSP may not support a payment method the business needs in a new market. Its approval rates may underperform in certain regions. Its pricing may become uncompetitive as the business scales. Outages at the PSP mean downtime for the business. And migrating to a new provider means rebuilding the integration from scratch, re-certifying for PCI compliance, and managing a complex data migration. A PSP-neutral architecture avoids these constraints by inserting an abstraction layer between the business and its PSPs. This layer normalises the API interface, tokenisation, settlement reporting, and dispute handling across all connected processors. The business integrates once with the abstraction layer and gains access to multiple PSPs without additional engineering work. Transactions can be routed intelligently -- by geography, payment method, cost, or performance -- and if one PSP experiences issues, traffic can be shifted to another without any customer-facing disruption. Shuttle Global is built on a PSP-neutral architecture from the ground up. Rather than acting as a PSP itself, Shuttle serves as a payment layer that connects platforms to 40+ PSPs through a single API. Platforms using Shuttle's Embedded Payments, Payment Links, or Voice Checkout are never locked into a single processor. They can onboard new PSPs as they expand into new markets, shift volume based on performance data, and maintain business continuity even when individual PSPs experience downtime. This neutrality also means Shuttle's incentives are aligned with the platform's: Shuttle succeeds when the platform's payments work optimally, not when traffic is directed to a preferred processor. ## Related Terms ### Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. ### Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience. ### PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement. ## See how Shuttle handles PSP-Neutral Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Payment Orchestration Payment orchestration is the practice of routing transactions across multiple payment service providers through a single integration layer to optimise authorisation rates, reduce costs, and increase resilience.](/glossary/payment-orchestration) - [PSP (Payment Service Provider) A PSP (Payment Service Provider) is a company that enables merchants to accept electronic payments by connecting them to payment networks, handling transaction processing, and managing settlement.](/glossary/psp) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/reconciliation/ --- # What Is Reconciliation? | Shuttle Glossary > Reconciliation is the process of matching payment transaction records against bank deposits and processor reports to ensure every payment is accounted for. # What Is Reconciliation? Reconciliation is the process of matching payment transaction records against bank deposits and processor reports to ensure every payment is accounted for. Reconciliation in payment processing is the practice of comparing transaction records from different sources -- typically the merchant's internal systems, the payment processor's reports, and the bank's deposit statements -- to verify that every transaction has been correctly captured, settled, and deposited. The goal is to identify discrepancies: missing transactions, duplicate charges, incorrect amounts, failed settlements, or fees that do not match the agreed-upon rate schedule. Without regular reconciliation, businesses risk undetected revenue leakage, accounting errors, and unresolved customer disputes. At its simplest, reconciliation involves matching each transaction ID from the merchant's records against the corresponding entry in the processor's settlement file, then confirming that the net deposited amount aligns with what was expected after fees and adjustments. In practice, this becomes far more involved. Chargebacks, refunds, currency conversions, rolling reserves, and timing differences between authorisation and settlement all create discrepancies that must be investigated and resolved. For businesses processing thousands of transactions daily, manual reconciliation is impractical and error-prone. The challenge intensifies dramatically for platforms and marketplaces that route payments through multiple PSPs. Each processor delivers settlement data in a different format, on a different schedule, with different fee structures and reporting conventions. A platform using three PSPs might receive three separate settlement files, each with its own transaction identifiers, currency handling, and deduction logic. Reconciling across these sources without a normalisation layer requires significant engineering investment and ongoing maintenance as each PSP updates its APIs or reporting formats. Shuttle Global addresses this fragmentation by providing a single reconciliation surface across all connected PSPs. Because every transaction -- whether processed via Embedded Payments, Payment Links, or Voice Checkout -- flows through Shuttle's unified payment layer, platforms receive consistent, normalised transaction and settlement data regardless of which underlying PSP handled the payment. This eliminates the need to build and maintain separate reconciliation pipelines for each processor, reducing both engineering overhead and the risk of unreconciled transactions slipping through the cracks. ## Related Terms ### Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor. ### Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. ## See how Shuttle handles Reconciliation Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Multi-PSP Multi-PSP is a payment strategy where a business connects to multiple payment service providers to optimise authorisation rates, expand geographic coverage, and reduce dependency on any single processor.](/glossary/multi-psp) - [Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account.](/glossary/settlement) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/refund/ --- # What Is a Refund? | Shuttle Glossary > A refund is a merchant-initiated reversal that returns funds from a settled payment transaction back to the cardholder's account. # What Is a Refund? A refund is a merchant-initiated reversal that returns funds from a settled payment transaction back to the cardholder's account. A refund is a transaction in which the merchant returns some or all of the funds from a previously settled payment back to the cardholder. Unlike a void, which cancels a transaction before settlement, a refund applies after the money has already been transferred to the merchant's account. The refund creates a new transaction that flows back through the payment network -- from the merchant's acquiring bank, through the card network, to the cardholder's issuing bank -- and typically takes five to ten business days to appear on the customer's statement, depending on the card network and issuing bank. Refunds can be full or partial. A full refund returns the entire transaction amount, while a partial refund returns a portion -- useful when a customer returns one item from a multi-item order or when a service was only partially delivered. From a processing standpoint, most acquirers charge the merchant a per-transaction fee on refunds, and the original interchange fees paid on the initial transaction are generally not returned (though some card networks have begun offering interchange refund credits for certain transaction types). This cost structure is why voiding is preferable when the transaction has not yet settled. Refund policies and execution speed are a significant factor in customer satisfaction and brand trust. Customers expect to see their money returned promptly, and delays in processing refunds are a common trigger for chargebacks -- cardholders who do not see a refund may escalate the dispute to their bank rather than waiting. For this reason, businesses benefit from automating refund workflows and providing customers with clear communication about expected timescales. Shuttle Global enables platforms to process refunds through a single API regardless of which PSP handled the original transaction. For platforms using Embedded Payments, this means a consistent refund experience across all payment methods and processors -- no need to build separate refund logic for each PSP integration. Payment Links transactions and Voice Checkout payments are handled the same way, with Shuttle routing the refund to the correct processor and returning status updates through its unified webhook system. This consistency is especially important for platforms managing refunds across multiple geographies and currencies, where each PSP may have different refund processing times, currency conversion rules, and fee structures. ## Related Terms ### Chargeback A chargeback is a forced reversal of a payment transaction, initiated by the cardholder's bank, that returns funds to the customer and debits the merchant. ### Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. ### Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees. ## See how Shuttle handles Refund Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Chargeback A chargeback is a forced reversal of a payment transaction, initiated by the cardholder's bank, that returns funds to the customer and debits the merchant.](/glossary/chargeback) - [Settlement Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account.](/glossary/settlement) - [Void A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees.](/glossary/void) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/sca/ --- # What Is SCA (Strong Customer Authentication)? | Shuttle Glossary > Strong Customer Authentication (SCA) is a European regulatory requirement under PSD2 that mandates multi-factor authentication for most electronic payments to reduce fraud. # What Is SCA (Strong Customer Authentication)? Strong Customer Authentication (SCA) is a European regulatory requirement under PSD2 that mandates multi-factor authentication for most electronic payments to reduce fraud. Strong Customer Authentication (SCA) is a regulatory requirement introduced under the European Union's revised Payment Services Directive (PSD2). It mandates that electronic payments within the European Economic Area must be authenticated using at least two of three independent factors: something the customer knows (such as a password or PIN), something the customer has (such as a phone or hardware token), and something the customer is (such as a fingerprint or facial recognition). The requirement applies to customer-initiated online payments, contactless transactions above certain thresholds, and other electronic payment actions. It took full effect in 2021, and non-compliant transactions are declined by issuing banks. SCA is not a technology -- it is a legal obligation. The technology most commonly used to fulfil it for online card payments is 3D Secure 2 (3DS2), which passes rich transaction data to the issuing bank so it can perform risk-based authentication. However, SCA also recognises several exemptions that allow certain transactions to bypass the challenge flow. These include low-value transactions under 30 euros, recurring payments of the same amount to the same merchant, transactions flagged as low-risk by the acquirer's fraud analysis (known as Transaction Risk Analysis or TRA exemptions), and payments to merchants the customer has whitelisted as trusted beneficiaries. Knowing when and how to apply these exemptions is critical, because unnecessary challenges increase cart abandonment while missing a required challenge results in a declined payment. For platforms operating internationally, SCA compliance adds meaningful complexity. The rules apply whenever both the acquirer and the issuer are in the EEA, but the specifics of how issuers enforce them vary by country and bank. Some issuers are stricter than others. Some have better support for frictionless 3DS2 flows. A platform selling across multiple European markets needs its payment infrastructure to handle these variations gracefully -- requesting exemptions where appropriate, falling back to full authentication when required, and interpreting soft declines that signal an SCA retry is needed. Shuttle Global manages SCA compliance within its payment infrastructure so that platforms do not need to build and maintain this logic themselves. When a transaction routed through Shuttle's Embedded Payments or Payment Links requires SCA, Shuttle triggers the appropriate 3DS2 flow, applies eligible exemptions where they will improve conversion, and handles the back-and-forth with the issuing bank. Because Shuttle sits between the platform and 40+ PSPs across multiple geographies, it normalises the inconsistencies in how different processors and issuers implement SCA. The platform sends a single payment request; Shuttle ensures the right authentication path is followed based on the transaction amount, the customer's location, the issuer's requirements, and the acquirer's capabilities. This is especially valuable for platforms expanding into European markets from regions where SCA does not apply -- Shuttle absorbs the regulatory complexity so the platform's integration stays the same regardless of where the transaction originates. ## Related Terms ### 3D Secure 3D Secure is an authentication protocol that adds a verification step during online card payments, reducing fraud and shifting chargeback liability from the merchant to the card issuer. ### PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. ## See how Shuttle handles SCA (Strong Customer Authentication) Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [3D Secure 3D Secure is an authentication protocol that adds a verification step during online card payments, reducing fraud and shifting chargeback liability from the merchant to the card issuer.](/glossary/3d-secure) - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/settlement/ --- # What Is Settlement? | Shuttle Glossary > Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. # What Is Settlement? Settlement is the process by which funds from a completed payment transaction are transferred from the acquiring bank to the merchant's bank account. Settlement is the final stage of a payment transaction's lifecycle -- the point at which money actually moves from the cardholder's issuing bank, through the card network and acquiring bank, into the merchant's bank account. Although a customer may see a charge appear on their statement within seconds of a purchase, the underlying funds typically take one to three business days to settle, depending on the card network, the acquirer's schedule, and the merchant's agreement terms. Until settlement occurs, the transaction exists as a pending obligation rather than received revenue. The settlement process begins after a transaction has been captured -- that is, after the merchant has confirmed they want to collect the funds from an authorised payment. At the end of each business day, the acquirer or payment processor batches all captured transactions and submits them to the card networks for clearing. During clearing, the issuing bank transfers the transaction amount (minus interchange fees) to the acquiring bank, which then deposits the net amount into the merchant's account. This batching cycle is why settlement is sometimes called "batch settlement." Settlement timing matters enormously for cash flow management. A business that processes high volumes but settles on a weekly cycle may face liquidity challenges, while one that settles daily can reinvest revenue faster. Settlement delays can also arise from risk holds, chargeback reserves, or compliance reviews -- all of which tie up funds that the merchant has technically earned. For platforms managing payments on behalf of sub-merchants, the complexity multiplies, because each sub-merchant may have different settlement schedules, reserve requirements, and currency considerations. Shuttle Global simplifies settlement complexity for platforms by acting as a unified payment layer across 40+ PSPs. Rather than reconciling settlement reports from multiple acquirers and processors independently, platforms using Shuttle's Embedded Payments receive normalised transaction data and settlement reporting through a single integration. Whether payments originate from an online checkout, a Payment Link, or a Voice Checkout session, Shuttle ensures that settlement data flows back consistently -- giving platforms the visibility they need to manage payouts to their own merchants without building bespoke reconciliation logic for every PSP they connect to. ## Related Terms ### Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement. ### Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds. ### Reconciliation Reconciliation is the process of matching payment transaction records against bank deposits and processor reports to ensure every payment is accounted for. ## See how Shuttle handles Settlement Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement.](/glossary/capture) - [Payment Processor A payment processor is the entity that handles the technical routing and communication of payment transactions between merchants, card networks, and banks to authorise and settle funds.](/glossary/payment-processor) - [Reconciliation Reconciliation is the process of matching payment transaction records against bank deposits and processor reports to ensure every payment is accounted for.](/glossary/reconciliation) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/tokenization/ --- # What Is Tokenization? | Shuttle Glossary > Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments. # What Is Tokenization? Tokenization replaces sensitive payment card data with a non-sensitive substitute token, reducing security risk and PCI scope for organisations that process payments. Tokenization is a data security technique that replaces a sensitive value -- such as a credit card number -- with a randomly generated, non-sensitive substitute called a token. The token has no exploitable value on its own. It cannot be reversed to reveal the original card number without access to the secure token vault maintained by the tokenization provider. This is fundamentally different from encryption, where the original data can be recovered with the correct key. A token is not mathematically derived from the card number; it is simply a reference that maps back to the original value in a tightly controlled, isolated system. In payment processing, tokenization serves two critical purposes. First, it protects cardholder data. If an attacker breaches a system that only holds tokens, they gain nothing usable -- the tokens are meaningless outside the tokenization provider's vault. Second, it dramatically reduces PCI scope. Because the platform's servers, databases, and logs never contain actual card numbers -- only tokens -- those systems fall outside the boundary of PCI DSS requirements. This translates directly into lower compliance costs, simpler audits, and a smaller attack surface. Tokenization also enables practical functionality that would otherwise require storing sensitive data. A platform can support saved cards, recurring billing, one-click checkout, and refunds by storing tokens instead of card numbers. When a returning customer checks out, the platform sends the token to the payment provider, which looks up the original card data in its vault and processes the transaction. The customer experience is seamless, but the platform never handles raw card data. Shuttle Global tokenizes card data at the earliest possible point in the transaction flow. In Embedded Payments, card details entered in Shuttle's hosted payment fields are tokenized before any data reaches the platform's backend. In Voice Checkout, DTMF tones are captured and tokenized within Shuttle's PCI Level 1 environment, so the card number never passes through the contact centre's telephony infrastructure. Payment Links operate on the same principle -- data is captured and tokenized on Shuttle's hosted checkout page. Because Shuttle connects to over 40 PSPs, these tokens can then be routed to whichever processor the platform uses, with Shuttle handling the secure de-tokenization and PSP-specific formatting behind the scenes. The result is that platforms get full payment functionality with none of the card data liability. ## Related Terms ### Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal. ### PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data. ### PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data. ## See how Shuttle handles Tokenization Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Payment Gateway A payment gateway is the technology that securely captures and transmits payment data from the customer to the payment processor for authorisation, acting as the digital equivalent of a point-of-sale terminal.](/glossary/payment-gateway) - [PCI DSS PCI DSS (Payment Card Industry Data Security Standard) is the global security standard that governs how organisations store, process, and transmit cardholder data.](/glossary/pci-dss) - [PCI Scope PCI scope defines which systems, people, and processes within an organisation are subject to PCI DSS requirements because they store, process, or transmit cardholder data.](/glossary/pci-scope) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/void/ --- # What Is a Void? | Shuttle Glossary > A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees. # What Is a Void? A void cancels a payment transaction after authorisation but before settlement, releasing the held funds back to the cardholder without incurring processing fees. A void is the cancellation of a payment transaction that has been authorised but not yet settled. When a merchant voids a transaction, the hold placed on the cardholder's funds during authorisation is released, and the payment is effectively erased as though it never happened. Because the funds were never actually transferred -- they were only reserved -- a void does not trigger the interchange and processing fees that apply to settled transactions. This makes voiding the cleanest and most cost-effective way to cancel a payment, provided it is done before the settlement batch closes. The window for voiding a transaction is limited. Once a payment has been captured and submitted for settlement, it can no longer be voided -- at that point, the merchant must issue a refund instead, which is a separate transaction that incurs its own processing costs and takes additional time to appear on the cardholder's statement. Because of this, merchants benefit from building void logic into their order management systems so that cancellations, inventory issues, or fraud flags detected before settlement can be handled as voids rather than refunds. Common scenarios for voiding include order cancellations where the customer changes their mind before shipment, duplicate transactions caused by technical errors or double-clicks, and fraud prevention workflows where a risk engine flags a transaction after authorisation but before capture. In each case, voiding avoids the downstream complications of refunding a settled payment -- no negative settlement entries, no impact on chargeback ratios, and no waiting period for the customer to receive their money back. Shuttle Global supports void operations consistently across all connected PSPs, whether the original transaction was processed through Embedded Payments, a Payment Link, or Voice Checkout. Platforms can issue voids through Shuttle's unified API without needing to know which PSP handled the original authorisation or how that PSP's specific void mechanics work. This is particularly valuable in contact centre environments using Voice Checkout, where an agent may need to cancel a payment mid-call -- Shuttle ensures the void is executed immediately and the hold is released, regardless of the underlying processor. ## Related Terms ### Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement. ### Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment. ### Refund A refund is a merchant-initiated reversal that returns funds from a settled payment transaction back to the cardholder's account. ## See how Shuttle handles Void Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Capture Capture is the step in payment processing where a previously authorised transaction is finalised and funds are submitted for settlement.](/glossary/capture) - [Pre-Authorization Pre-authorization is a payment request that verifies a cardholder's funds and places a temporary hold without immediately capturing the payment.](/glossary/pre-authorization) - [Refund A refund is a merchant-initiated reversal that returns funds from a settled payment transaction back to the cardholder's account.](/glossary/refund) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/glossary/white-label-payments/ --- # What Are White-Label Payments? | Shuttle Glossary > White-label payments allow a platform to offer branded payment processing to its users by reselling or embedding another company's payment infrastructure under its own brand. # What Are White-Label Payments? White-label payments allow a platform to offer branded payment processing to its users by reselling or embedding another company's payment infrastructure under its own brand. White-label payments describe a model in which a technology provider builds and operates payment processing infrastructure that other businesses can rebrand and present as their own. The platform's end users interact with a checkout experience that carries the platform's name, logo, and visual identity, while the underlying transaction processing, security, compliance, and PSP connectivity are handled by the white-label provider behind the scenes. The term "white-label" comes from the broader practice of selling unbranded products or services that the buyer rebrands for their own market. This model has become the standard approach for platforms and SaaS companies that want to embed payments without building a payments operation from the ground up. Developing payment infrastructure in-house requires PCI DSS certification, direct relationships with acquiring banks and card networks, ongoing compliance maintenance, fraud management systems, and engineering teams with specialised payments expertise. White-label payments bypass this complexity -- the platform gains a fully functional payment capability while the provider assumes the technical and regulatory burden. The quality of a white-label solution varies enormously depending on how deeply it can be customised and how much of the payment lifecycle it covers. A shallow integration might offer a branded checkout page but leave the platform to manage reconciliation, disputes, and PSP failover independently. A comprehensive white-label solution covers the entire payment stack -- from tokenisation and transaction routing through to settlement reporting and chargeback management -- all under the platform's brand. The depth of the white-labelling determines whether the platform truly owns its payment experience or merely skins someone else's checkout. Shuttle Global provides enterprise-grade white-label payments as the core of its Embedded Payments product. Platforms integrating Shuttle present a fully branded payment experience to their users -- every touchpoint, from the checkout form to the payment confirmation, reflects the platform's identity. Under the surface, Shuttle manages PCI DSS Level 1 compliance, connections to 40+ PSPs, smart transaction routing, and unified reporting. This extends across all channels: online payments through embedded forms, remote payments via Payment Links, and telephone payments through Voice Checkout all operate under the platform's brand while Shuttle handles the infrastructure. The result is a payment experience that looks and feels native to the platform, backed by the resilience and coverage of a multi-PSP payment layer. ## Related Terms ### Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application. ### Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations. ## See how Shuttle handles White-Label Payments Talk to our team about how Shuttle's payment infrastructure addresses your needs. ## Links - [Embedded Payments Embedded payments integrate payment processing directly into a software platform's user experience, allowing end users to pay without leaving the application.](/glossary/embedded-payments) - [Payment Layer A payment layer is the abstraction between a platform's application and the underlying payment service providers, enabling unified payment processing without direct PSP integrations.](/glossary/payment-layer) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/guides/3cx-payments/ --- # How to Take Payments in 3CX: PCI-Compliant Phone Payments | Shuttle > 3CX is an open-platform software PBX used by tens of thousands of businesses worldwide. # How to Take Payments in 3CX: PCI-Compliant Phone Payments By Shuttle Team, May 31, 2026 3CX is an open-platform software PBX used by tens of thousands of businesses worldwide. It runs voice calls, live chat, WhatsApp, SMS, and video from a single system, and it deploys either self-hosted or in the cloud. Most 3CX environments are built and managed by IT resellers and MSPs, who configure the system and keep it running for their end customers across industries from professional services to field service, retail, and healthcare. What 3CX does not do is process payments. The platform's Call Flow Designer (CFD) includes a Credit Card Component, but that component is a DTMF digit collector: it gathers the numbers a caller keys into their phone and hands them to whatever external API you wire up. The responsibility for securing those digits, meeting PCI DSS requirements, and keeping them out of call recordings and the call-flow log is entirely yours. 3CX holds no PCI DSS certification. Its "PCI Compliance mode" setting enforces TLS 1.2 on connections, which is transport security, not payment security. This guide is written for two readers. The first is a business running 3CX that wants to take card payments over the phone or via payment links. The second is the IT reseller or MSP that deploys and manages 3CX for end customers and needs a clean way to add payment capability to client environments. Shuttle is a PCI DSS Level 1 certified payment provider that captures card data in its own certified environment, keeping it out of 3CX entirely, and routes to 30+ payment gateways. ## The Payment Challenge in 3CX Taking card payments over the phone creates PCI scope the moment a card number is spoken or entered. Every system that touches, stores, transmits, or could potentially access cardholder data falls into that scope, and passing the audit is expensive and time-consuming. The CFD Credit Card Component adds a specific risk on top of the general compliance burden. When verbose logging is enabled in 3CX, the call-flow log can capture the DTMF digits a caller keys in, including the card number, expiry, and CVV. Call recordings made during the DTMF entry phase carry a similar risk unless tone suppression is applied. These are not theoretical edge cases: they are documented behaviours that put cardholder data into system logs where it was never meant to be. The DIY route through the CFD is not a certified payment path. Building a compliant solution yourself means taking on PCI DSS Level 1 certification, which typically costs upwards of $500,000 in initial work and $200,000 or more per year to maintain. For most businesses and the MSPs serving them, that cost and complexity is entirely out of scope for what should be a standard feature of their phone system. ## How Shuttle Adds Payments to 3CX Shuttle adds PCI-compliant card capture to your 3CX payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your 3CX recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for 3CX specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your 3CX call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running 3CX have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent workflow The agent keeps the customer on the 3CX call. When payment is needed, the agent triggers a Shuttle session, which takes a few seconds. The customer hears a prompt and enters their card details on their phone keypad, captured inside Shuttle's certified environment via Twilio Pay, so the digits never reach the 3CX recording system or the call-flow log. The agent sees only the masked card result and confirms the outcome with the customer. For follow-up or digital payments, the agent sends a payment link and waits for the confirmation. ### Customer experience The customer is not transferred to a different number for the capture. On voice, the process takes roughly the same time as reading a card number aloud, with the added reassurance that no one on the line can capture the digits. For a payment link, the customer taps a hosted link, completes payment on a branded page, and returns to the conversation. No app install, no account creation. ## Multi-PSP Support Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. For MSPs managing 3CX deployments across multiple client businesses, this is particularly useful: each client can keep their existing gateway relationship, or be set up with a new one, and switching is configuration, not a re-integration. Per-client configuration means each business runs on its own gateway. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, the highest level of certification available. Card data is captured in the secure Twilio Pay call and handled inside Shuttle's certified environment and never enters 3CX, its infrastructure, its call recordings, or its system logs. For the Twilio side of the compliance picture, see Twilio PCI Compliance. For most businesses, adding Shuttle moves their payment card environment from a complex SAQ-D self-assessment toward SAQ-A scope, a significantly smaller and simpler compliance burden. The contrast with the CFD DIY approach is direct: using the Credit Card Component without a certified intermediary leaves the business responsible for the full scope of wherever those DTMF digits travel, including the call-flow log when verbose logging is active. Shuttle closes that gap by design. ## Beyond Voice: Payment Links Payment links are the most turnkey path, and they do not require Twilio. Shuttle generates a hosted payment link and sends it via SMS or email, including mid-call to a customer still on the line. The customer taps the link, completes payment on a branded hosted page with no app required, and confirmation returns in real time. Links also work with gateways that do not support voice capture, so they are a reliable fallback when a client's preferred gateway can't take raw card data over voice. Shuttle provides the link interfaces out of the box. ## For IT Resellers and 3CX Partners 3CX is sold and delivered almost entirely through its Channel Partner Programme, which runs from Bronze through to Titanium tiers. Resellers and MSPs are not just the sales channel: they configure the system, integrate it with other business tools, and take ongoing responsibility for the platform on behalf of their clients. Adding a payment layer is a natural extension of that role. Shuttle's voice capture runs on Twilio Pay, so the client needs to be a Twilio customer, and the agent-side interface is built against Shuttle's APIs as part of your delivery. There is no pre-built 3CX widget today, though we can build a native 3CX integration as a paid project for a specific deployment. Voice payments are $0.20 per successful transaction with no per-seat pricing, no monthly platform fee, and no setup charge, which scopes cleanly into managed-service delivery. Links Checkout is a separate app; see [pricing](/pricing/). Each client keeps or chooses their own payment gateway from 40+ options, and you can build a proof of concept against Shuttle's sandbox gateway and demo app before deploying for a client. For resellers serving clients across healthcare, professional services, or collections, where payment over the phone is a regular need, this is a differentiator that adds real value to the deployment. ## Use Cases ### Bill-Pay and Collections Utility providers, financial services firms, and collections agencies using 3CX can accept card and direct debit payments on inbound or outbound calls without transferring the customer or switching systems. ### Order Taking and Card-Not-Present Businesses that take telephone orders, from food service to retail, can complete the card transaction while the customer is still on the line, with a full PCI-compliant audit trail. ### Account Payments Professional services firms, clinics, and subscription businesses can handle account payments and outstanding balances on the same call used to discuss the account, without routing to a separate payment IVR. ### Bookings and Deposits Hotels, event organisers, and service businesses that take deposits by phone can capture payment at the point of booking, reducing no-shows and follow-up friction. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged 3CX plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for 3CX specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your 3CX call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running 3CX have already done it. - A native 3CX integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does 3CX process payments natively? No. 3CX does not include a payment processing product. The Credit Card Component in the Call Flow Designer collects DTMF digits from the caller's keypad and passes them to an external API of your choice. Securing those digits, routing them to a payment gateway, and meeting PCI DSS requirements are all handled outside 3CX. Is the 3CX Call Flow Designer Credit Card Component PCI compliant? Not by itself. The component collects DTMF digits, but when verbose logging is active in 3CX, those digits can be written to the call-flow log. Call recordings during the DTMF entry phase may also capture the tones. This brings significant PCI scope into the 3CX environment and requires careful scoping, logging controls, and an integration with a certified payment provider to resolve. The component is a building block, not a certified payment path. Does Shuttle have a native 3CX integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in 3CX. For voice you'll need to be a Twilio customer and to build the agent-side trigger for your workflow against Shuttle's APIs. Payment links require no Twilio relationship. We can build a native 3CX integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? For voice capture, yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. How do I take PCI-compliant payments in 3CX? Agents trigger a Shuttle session from your workflow. On voice, the card is captured in a secure Twilio Pay call inside Shuttle's PCI DSS Level 1 environment; for follow-up or digital payments, Shuttle sends a hosted link via SMS or email. Card data does not enter 3CX at any point, which reduces your PCI scope substantially. Which gateways does Shuttle support? Shuttle connects to 30+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You can keep your existing gateway relationship or set up a new one, and switching is configuration, not a re-integration. Can Shuttle handle outbound payment collection in 3CX? Yes. Agents making outbound calls from 3CX can trigger a Shuttle payment session in the same way as on inbound calls. For outbound collections, Shuttle payment links can be sent via SMS or email. ## Related Reading - Contact centre payments: how payment capture works across inbound and outbound contact centre environments - Embedded payments for CCaaS: adding a payment layer to cloud contact centre and communications platforms - DTMF payments: DTMF clamping, masking, and suppression explained, with PCI compliance context - Payment collection for BPOs: multi-client payment routing for outsourced contact centre operations - Payments for CCaaS implementation partners: how SIs and resellers add embedded payment capability to CCaaS deployments ## Take Payments in Your 3CX Phone System Shuttle adds PCI-compliant card capture to a 3CX-based operation, via Twilio for voice and via payment links over SMS or email, with no platform fees and routing to 30+ gateways. We'll walk you through what's live today and the path for your setup. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [PCI scope](/glossary/pci-scope/) - [book a call](/contact/) - [Twilio PCI Compliance](/guides/twilio-pci-compliance/) - [$0.20 per successful transaction](/pricing/) - [40+ options](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [DTMF payments](/guides/dtmf-payments/) - [Payment collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [30+ gateways](/payment-providers/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/8x8-payments/ --- # How to Take Payments on 8x8: PCI-Compliant Contact Centre Payments | Shuttle > 8x8 Contact Center is a strong mid-market and enterprise CCaaS platform. 8x8 XCaaS combines UCaaS and CCaaS in a single platform, with AI-powered features... # How to Take Payments on 8x8: PCI-Compliant Contact Centre Payments By Shuttle Team, March 28, 2026 8x8 Contact Center is a strong mid-market and enterprise CCaaS platform. 8x8 XCaaS combines UCaaS and CCaaS in a single platform, with AI-powered features including Intelligent Customer Assistant (ICA) for conversational AI and workforce engagement management. For payments, 8x8 offers "Secure Pay", a branded DTMF-based integration for card capture during calls. For enterprise and BPO use cases, gaps remain around multi-PSP gateway support, pricing flexibility, and AI agent handoff. This guide covers how to add comprehensive payment infrastructure to 8x8 using Shuttle. ## The Payment Gap in 8x8 8x8 Secure Pay handles DTMF masking for card capture during calls. For many enterprise and BPO use cases, additional capability is needed: - Multi-PSP routing. Enterprise customers and BPOs need to route payments to different gateways for different merchants, regions, or card types. - Per-transaction pricing. For contact centres with high agent counts but moderate payment volumes, transaction-based pricing can be more cost-effective than seat-based pricing. - AI agent payment handoff. 8x8's Intelligent Customer Assistant can handle conversational AI, but autonomous payment capture requires an API-driven handoff between the AI flow and a payment layer. - Multi-tenant architecture for BPOs. BPOs running multiple clients need per-client gateway routing, routing Client A's payments to their own PSP and Client B's to theirs, from a single integration. ## How Shuttle Adds Payments to 8x8 Shuttle adds PCI-compliant card capture to your 8x8 payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your 8x8 recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for 8x8 specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your 8x8 call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running 8x8 have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When payment is triggered, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. 8x8 recordings and ICA analytics receive no card data. See the Twilio IVR & Agent Assist payment docs. ### Payment Links This is the most turnkey path. Shuttle generates payment links sent via SMS or email, including mid-call while the customer is on the line. Links work even with gateways that don't support voice capture. See the Payment Links docs. ### AI Agent Payment Handoff When 8x8's Intelligent Customer Assistant detects payment intent, Shuttle's API can initiate the secure Twilio Pay capture within the call and return the result to the AI conversation, without a human in the loop. You build this handoff against Shuttle's APIs. ## How a voice payment works - The call proceeds on 8x8 Contact Center as normal. - Payment is triggered from your agent interface, or ICA triggers it via API. - Card captured securely in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. - Result returned to your interface or the ICA flow. - No card data in 8x8. The card digits never touch your 8x8 recordings, analytics, or agent workstations. ## Multi-PSP Support Shuttle supports 30+ payment gateways with configurable routing: - By merchant: each client or business unit routes to its own gateway - By region: route by geography for optimal settlement and fees - By switching: automatic backup if the primary gateway is unavailable - By card type: route specific card brands through preferred processors Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This routing flexibility is the key differentiator from a single-gateway DTMF integration. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, card data never enters your 8x8 environment. Recordings, transcriptions, ICA analytics, and agent workstations are all out of PCI scope, keeping you on the lighter SAQ-A path. Full detail is in the security docs. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Insurance Insurance contact centres on 8x8 handle premium collections and renewal payments. Shuttle captures payment during the conversation without creating PCI exposure. ### Debt Collection Collections teams need to capture payment when the debtor agrees. Any delay loses the commitment. Shuttle captures immediately, in-call. ### Utilities High-volume bill payment calls can be handled autonomously with 8x8 ICA + Shuttle, reducing cost per interaction. ### BPO and Outsourcers BPOs running multiple clients on 8x8 route each client's payments to their own gateway through a single Shuttle integration. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged 8x8 plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for 8x8 specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your 8x8 call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running 8x8 have already done it. - A native 8x8 integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native 8x8 integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in 8x8. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running 8x8 have already done. We can build a native 8x8 integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can Shuttle work with 8x8's Intelligent Customer Assistant? Yes. Shuttle provides an API that ICA can trigger to start the Twilio Pay capture within AI-handled calls. You build the handoff against that API. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ## Related Reading - PCI-Compliant Payments for Contact Centres, the complete guide - Talkdesk Payments, PCI-compliant payment capture for Talkdesk - Genesys Cloud Payments, voice and IVR payments for Genesys Cloud - NICE CXone Payments, payment capture for NICE CXone - Voice Payments, comprehensive guide to voice payment capture ## Get Started Add PCI-compliant payments to 8x8 without per-seat licensing or gateway lock-in. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Talkdesk Payments](/guides/talkdesk-payments/) - [Genesys Cloud Payments](/guides/genesys-payments/) - [NICE CXone Payments](/guides/nice-cxone-payments/) - [Voice Payments](/guides/voice-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/ach-payments-over-the-phone/ --- # ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent | Shuttle > Quick answer: yes, you can take ACH payments over the phone. The caller keys their bank routing number and account number into the keypad, the digits are... # ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent By Shuttle Team, July 4, 2026 Quick answer: yes, you can take ACH payments over the phone. The caller keys their bank routing number and account number into the keypad, the digits are captured inside a PCI-compliant environment, and the payment is debited directly from their US bank account. The catch is connector support: some Twilio Pay Connectors can tokenise a bank account in-call but cannot actually charge it. This guide covers how phone ACH capture works, which connectors do what, and the compliance points to get right. ## What Is ACH, Briefly ACH is the US bank-to-bank payment network, governed by NACHA. Instead of a card number, the payer provides two things: a bank routing number and an account number. The debit pulls funds directly from their checking or savings account. Three properties make ACH interesting for phone payments: - Lower cost. ACH fees are typically flat or capped rather than a percentage of the transaction, so the saving over cards grows with the amount. On a $5,000 invoice, the difference is real money. - No card expiry churn. Bank accounts don't expire every three years. For payment plans and recurring billing, an ACH mandate keeps working long after a card on file would have failed. - Slower settlement. ACH is not instant. Debits typically settle in one to a few business days, and a payment can still be returned after that (insufficient funds, closed account, disputed authorisation). ACH has a defined set of return codes for these cases, so your reconciliation needs to treat "submitted" and "cleared" as different states. None of this changes on a phone call. What changes is how you capture the account details securely, which is the rest of this guide. ## Why Take ACH by Phone Most phone payment guides assume cards. But there are call types where ACH is the better default: Bill pay and utilities. Callers paying a monthly bill often prefer their bank account, and billers prefer the lower processing cost on high-volume, repeat payments. Collections and payment plans. Debt collection agencies live on multi-month instalment plans. A card set up on a collections call has a meaningful chance of expiring, being reissued, or being cancelled before the plan completes. A bank account rarely does. Lower fees also matter when margins on recovered debt are thin. Insurance premiums. Annual and monthly premium payments are large, recurring, and price-sensitive on fees. Premium finance especially suits ACH mandates agreed on a call. Large B2B amounts. When a customer phones to settle a $20,000 invoice, 2.9% card fees are hard to justify. A flat ACH fee is not. The common thread: high amounts, repeat payments, or both. That is exactly where ACH's economics beat cards, and exactly the kind of payment that often happens on a phone call with an agent or an IVR. ## How Phone ACH Capture Works The mechanics mirror card capture over the phone, with bank details in place of a PAN. On Twilio, the verb supports . The flow: - The call reaches the payment step. Your IVR flow, Studio flow, or agent screen triggers with the ACH payment method. - The caller keys in their details. They enter their bank routing number, then their account number, on the phone keypad (DTMF). No reading digits aloud. - The tones are suppressed. The DTMF tones are captured inside Twilio's PCI-compliant environment and suppressed from the agent's audio and from call recordings. The agent stays on the line but never hears or sees the account number. - The connector processes the payment. The captured bank details pass to your Pay Connector, which either charges the account or tokenises it for later use. Your systems receive a result and a redacted reference, never the raw account number. ### Agent-assisted vs IVR Both modes use the same capture flow: - Agent-assisted: the agent stays on the call, triggers the payment step, and talks the caller through it while the keypad entry is masked. Best for collections and negotiated payment plans, where the payment follows a conversation. - IVR / self-service: the caller pays without an agent, prompted by the IVR. Best for bill pay lines that run 24/7. ACH prompts in Twilio are available in English language variants. One practical note for ACH specifically: routing plus account number is more digits than a card number, and callers are less likely to know their account number from memory than to have a card in hand. Good prompt design ("you'll find both numbers at the bottom of a check, or in your banking app") measurably improves completion rates. ## Connector Support: The Part That Bites This is where most "twilio pay ach" research ends up, because ACH support varies sharply by Pay Connector. Twilio's verb defines two operations: creating a charge, and tokenising a payment method for later use. For cards, most connectors support both. For ACH, they diverge: Stripe Pay Connector. The Twilio Marketplace listing for the Stripe connector supports ACH tokenisation in-call, but marks ACH "Creating a Charge" as not supported. So you can capture and tokenise a bank account during the call, but the debit itself has to be created afterwards through Stripe's API, from your own systems. The listing also requires `AVSName`, `AVSCountry`, and `AVSCurrency` parameters when creating ACH tokens, so budget for the extra plumbing. We cover this connector in depth in the Twilio Stripe Pay Connector guide. Braintree Pay Connector. Braintree's Marketplace listing does not list ACH support at all. Cards only. If your gateway is Braintree and you need phone ACH, you need a different connector in front of it or a different rail. Shuttle Pay Connector. Shuttle supports both ACH charge and ACH tokenisation in-call. Twilio's changelog for the Shuttle connector describes support for "credit card and ACH-debit payment methods", and Shuttle's own docs cover the `ach-debit` flow, including the `bankAccountType` parameter for consumer or business checking and savings accounts. The caller keys in their details, and the debit is created on the same call, with the confirmation read back before they hang up. ACH bank debits through Shuttle are US only; cards work internationally through 30+ gateways from the same connector. The difference matters operationally. Tokenise-only means you build and maintain a second leg: a service that takes the token after the call and creates the charge, handles failures, and reports back to the agent or CRM. Charge-in-call means the payment either succeeds or fails while the caller is still on the line, which is precisely when you want to know. If none of the managed connectors fit and you're considering Twilio's Generic Pay Connector, note that for ACH it posts the raw `bankaccountnumber` and `routingnumber` to an endpoint you host. That endpoint is now handling sensitive bank data, with the scope implications covered in our Generic Pay Connector guide. ## ACH Payment Plans on a Call The strongest phone ACH pattern is not the one-off payment. It's the plan. A collections agent agrees a plan on the call: $200 a month for 12 months. With Shuttle's connector, the agent captures the bank account once via , and the recurring schedule is set in the same TwiML using values: The first debit is taken on the call, the remaining eleven run on schedule, and no one re-keys anything. Because it's a bank account rather than a card, the plan is not exposed to expiry churn: no month-seven failure because the card was reissued. The same pattern fits premium finance (monthly instalments on an annual premium agreed with an agent), utility budget plans, and B2B instalment agreements. For teams running this at scale, BPOs and contact centres can run card and ACH plans through the same connector, choosing the rail per merchant or per call. Alternatively, tokenise the account without charging it (omit the charge amount), store the vaulted token, and drive the schedule from your own billing system via Shuttle's API. Shuttle also supports ACH via payment link if the caller would rather complete the details after the call. ## Compliance Notes Two regimes apply to phone ACH, and they cover different things. PCI DSS covers the capture environment. Strictly, PCI scope is about card data, but the same architecture question applies: where do the sensitive digits land? With Twilio `` plus a certified connector, DTMF capture and suppression happen in Twilio's PCI-compliant environment, processing happens in Shuttle's (PCI DSS Level 1), and your systems only ever see redacted references. For card payments through the same flow, that keeps you at SAQ-A, the lightest self-assessment. The full picture is in our Twilio PCI compliance guide. NACHA rules cover the authorisation. ACH debits initiated over the phone come with authorisation requirements under NACHA's operating rules. In broad terms: the caller must clearly and unambiguously authorise the debit, and an oral authorisation must be recorded or confirmed in writing, with the authorisation evidence retained. The exact requirements depend on the entry type and your setup, so confirm the specifics with your payment processor or ODFI before you launch. Practically, most teams handle this with a scripted authorisation statement on the call plus either the (payment-redacted) call recording or a follow-up confirmation email. Neither regime is a reason to avoid phone ACH. Both are solved problems, but they're solved by design decisions you make before the first call, not after. ## Phone ACH Payments FAQ Can you take ACH payments over the phone? Yes. The caller keys their routing number and account number into the phone keypad, the digits are captured in a PCI-compliant environment with tones suppressed from agents and recordings, and the debit is processed against their US bank account. Both agent-assisted and self-service IVR flows work. Does Twilio Pay support ACH? Yes. Twilio's verb supports , capturing the routing and account number via DTMF. But charge and tokenisation support varies by Pay Connector, so check your connector's Marketplace listing before you design the flow. Why can't the Stripe connector charge ACH in-call? The Twilio Stripe Pay Connector's Marketplace listing supports ACH tokenisation but marks ACH "Creating a Charge" as not supported. It's a boundary of that connector's design: you tokenise the bank account during the call, then create the debit afterwards through Stripe's API from your own systems. Shuttle's connector supports both operations in-call. Is phone ACH PCI compliant? The PCI DSS framework is card-focused, but the capture architecture is the same one PCI demands: with Twilio and a certified connector, bank details are keyed via DTMF, suppressed from agents and recordings, and never touch your systems. Separately, NACHA rules require that oral authorisations for phone ACH debits be recorded or confirmed in writing; confirm specifics with your processor. Can I set up recurring ACH from a call? Yes. With Shuttle's connector you capture the bank account once via and set the schedule in the same TwiML using values for frequency and occurrences, for example monthly for 12 payments. Because bank accounts don't expire like cards, ACH plans avoid mid-plan card-expiry failures. ## Related Reading - PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - the card-side companion to bank payments by phone - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to connectors, including the Generic Pay Connector's data implications - Twilio Stripe Pay Connector: Setup and Limits: what the Stripe connector supports, in detail - Twilio Pay Error Codes Explained: diagnosing failed captures and declined payments - Secure Payment Collection for Debt Agencies: compliant collections payments across channels - Payment Collection for BPOs: multi-client payment operations at scale - Contact Centre Payments: the full guide to taking payments in a contact centre - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Take ACH and card payments over the phone with Shuttle's Pay Connector: PCI DSS Level 1, $0.20 per successful transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### DTMF vs Payment Links: Which is More Secure for Phone Payments? ### QuickBooks ACH Payments: Setup, Fees & Tips ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ## Links - [Debt collection agencies](/guides/secure-payment-collection-debt-agencies/) - [DTMF](/guides/dtmf-payments/) - [Twilio Stripe Pay Connector guide](/guides/twilio-stripe-pay-connector/) - [30+ gateways](/payment-providers/) - [Generic Pay Connector guide](/guides/twilio-pay-connectors/) - [BPOs](/guides/payment-collection-for-bpos/) - [contact centres](/guides/contact-centre-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI compliance guide](/guides/twilio-pci-compliance/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [Twilio Stripe Pay Connector: Setup and Limits](/guides/twilio-stripe-pay-connector/) - [Twilio Pay Error Codes Explained](/guides/twilio-pay-error-codes/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogDTMF vs Payment Links: Which is More Secure for Phone Payments?→](/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) --- URL: https://www.shuttleglobal.com/guides/aci-speedpay-twilio-integration/ --- # How to Connect ACI Speedpay to Twilio for Voice & IVR Payments | Shuttle > ACI Speedpay doesn't natively connect to Twilio for voice payments. If you want to process Speedpay transactions during a phone call (via IVR... # How to Connect ACI Speedpay to Twilio for Voice & IVR Payments By Shuttle Team, June 13, 2026 ACI Speedpay doesn't natively connect to Twilio for voice payments. If you want to process Speedpay transactions during a phone call (via IVR self-service, agent-assisted, or AI voice agent) you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects ACI Speedpay (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why ACI Speedpay + Twilio Don't Connect Directly ACI Speedpay is ACI Worldwide's biller-direct payment solution, built for US organisations that collect bills at scale: utilities, insurers, lenders, healthcare providers, higher education, and government agencies. It handles one-off and recurring bill payments across web, mobile, IVR, and agent channels, with support for major card brands and ACH bank debits. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. ACI Speedpay isn't one of Twilio's built-in connectors. Twilio's early changelogs referenced ACI among the first supported processors back in 2019, but ACI appears in no current Twilio connector documentation, so there's no native path between the two platforms today. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to ACI Speedpay for processing. One integration connects the two platforms. For billers, that combination matters. Your customers already call to pay: overdue balances, instalments on a payment plan, a bill they'd rather settle with a person on the line. Connecting Speedpay to Twilio means those calls complete the payment then and there, in the same biller-direct rails you already use for web and mobile. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the verb. That might be a self-service bill-pay line or an agent transferring the caller into a secure payment step. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via ACI Speedpay. The connector creates a Speedpay payment request, processes the transaction through your ACI account, and handles the response. - Result returned to your call flow. Your webhook receives the confirmation reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An ACI Speedpay account with API credentials supplied by ACI - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add ACI Speedpay Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: ACI Speedpay - Credentials: The API credentials supplied by ACI - Currency: USD - Environment: Live or Test Save the profile. Shuttle now has a live connection to your ACI Speedpay account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to reconcile the transaction against the account or invoice in your billing system. Update the balance, confirm to the caller, and continue the flow. ### Step 5: Test Use your ACI test credentials in Shuttle and Twilio's test setup to verify the flow end-to-end before going live: successful payment, declined card, and caller abandonment mid-entry. ## What You Can Do With ACI Speedpay + Twilio ### IVR Self-Service Bill Payment A fully automated pay-by-phone line. The caller enters their account number, hears the balance, and pays by card without ever speaking to an agent. This is the classic Speedpay use case, now running on your Twilio number. ### Agent-Assisted Collections An agent works a collections call, agrees an amount, and triggers the secure payment step. DTMF tones are suppressed, so the agent never hears or sees card details. This is the standard pattern for debt collection agencies and any biller running an outbound recovery team. ### Payment Plans and Recurring Collection Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token, so subsequent instalments on a payment plan run without another call. The same token works across web, mobile, voice, and payment links; the card data is never stored in your systems. ### Follow Up by Text If a caller can't pay in full on the call, send a payment link by SMS through the same Twilio account for the remaining balance. One conversation, multiple ways to settle. ## Multi-PSP: Beyond ACI Speedpay One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: route bill payments to Speedpay and other transaction types to a different acquirer - Serve clients who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway is unavailable, you can move the affected payment types to another connected gateway - Route by amount or region when different processors give better rates or authorisation performance You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly useful for BPOs and outsourced collection teams that serve multiple billers. Each client can use their own Speedpay account (or any other gateway) through the same Twilio integration. ## PCI Compliance The ACI Speedpay + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing ACI Speedpay Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to ACI Speedpay. Your application only receives redacted data (last four digits, card brand, confirmation reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. That matters for utilities, insurers, and lenders whose call centres would otherwise sit squarely in scope. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect ACI Speedpay to Twilio without Shuttle? ACI Speedpay isn't among Twilio's current built-in Pay Connectors. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI DSS Level 1 certified connector that handles this. Which payment methods does ACI Speedpay support through Shuttle? Card payments across the major brands (Visa, Mastercard, American Express, Discover, and more). ACI Speedpay also supports ACH bank debits for US merchants; see the ACI Speedpay gateway page for current coverage. Is this US only? ACI Speedpay is a US-focused biller-direct solution, so the Speedpay side is US-centric. If you collect payments in other markets, Shuttle can route those transactions to a different gateway through the same Twilio integration. Can I take payments on outbound collection calls? Yes. The verb works on inbound and outbound calls alike, so outbound collections and payment-plan reminder calls can complete payment in the same call. What does it cost? Shuttle charges $0.20 per successful transaction. ACI Speedpay's fees apply on top per your agreement with ACI. No Shuttle setup fees or monthly minimums. Can I switch from ACI Speedpay to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - Secure Payment Collection for Debt Agencies: compliant collections across voice, SMS, and links - Payment Collection for BPOs: multi-client payment routing for outsourced teams - Contact Centre Payments: the hub guide to taking payments on every contact centre platform - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect ACI Speedpay to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ### Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [debt collection agencies](/guides/secure-payment-collection-debt-agencies/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs and outsourced collection teams](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [ACI Speedpay gateway page](/payment-providers/aci-speedpay/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) - [BlogPayment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations→](/blog/payment-links-for-fortis/) --- URL: https://www.shuttleglobal.com/guides/ada-payments/ --- # How to Take Payments on Ada: PCI-Compliant AI Agent Payments | Shuttle > Ada (ada.cx) is an enterprise AI customer service platform built around what the company calls Agentic Customer Experience. # How to Take Payments on Ada: PCI-Compliant AI Agent Payments By Shuttle Team, June 2, 2026 Ada (ada.cx) is an enterprise AI customer service platform built around what the company calls Agentic Customer Experience. Launched as a chat-first product, Ada now runs AI agents across web chat, messaging apps (WhatsApp, Messenger, Instagram, SMS), email, and a Voice AI channel that connects to telephony platforms including Twilio, Genesys, Amazon Connect, Aircall, and NICE CXone. Large enterprises in retail, financial services, telecoms, and SaaS use Ada to automate a significant portion of inbound support volume before a human agent ever picks up. Payments are a different matter. Ada explicitly states that its services are not PCI DSS compliant and that Ada is not a payment card processor. Its only card-adjacent feature is a data redaction capability that scrubs payment card digits pasted into a chat window. That is a safety net, not a payment product. Ada agents can surface billing information held in your systems, or hand a conversation off via API, but they cannot capture a card number, tokenise it, or route a transaction to a payment gateway. If your Ada agents need to complete a payment, you need a compliant layer working alongside Ada to do it. This guide is for customer experience and payments teams at companies running Ada, and for solution integrators building on the Ada Partner Ecosystem. It explains how Shuttle slots in alongside Ada to handle card capture, processing, and routing across Ada's voice and chat channels, without any card data passing through Ada itself. ## The Payment Challenge for Ada Agents Ada's compliance posture is SOC 2 Type II, SOC 3, and HIPAA certified. That is a strong enterprise security baseline for a CX platform. PCI scope is simply outside its design: Ada is built to understand intent, resolve queries, and orchestrate next actions. Capturing and processing payment card data is a specialised, highly regulated function that carries its own audit and certification requirements. The practical consequence is that any Ada agent workflow that touches a payment hits a wall. The agent can confirm an outstanding balance, tell a customer which cards are on file, or explain a billing dispute. The moment you need to capture new card details, process a transaction, or collect a payment on a call, the conversation needs to hand off to something that is PCI certified to handle it. Without that handoff, your team ends up interrupting the agent flow to move the customer to a separate process, which introduces drop-off and friction at exactly the wrong moment. Shuttle is built to be that layer. It handles the card capture moment in isolation, keeps card data entirely out of Ada, processes through your chosen gateway, and returns a clean result to your application. ## How Shuttle Works with Ada Today Shuttle has no native integration with Ada. Instead, you invoke Shuttle's Twilio-based payment setup. The handoff is API-driven: your application code triggers the Shuttle payment handoff at the point of payment. To use the voice capture path, you must be a Twilio customer. - The Ada agent runs the conversation. Intent is identified, the customer's account is looked up, and the payment amount or requirement is confirmed. Ada handles all of this natively. - Your application triggers Shuttle at the payment moment. Via a webhook or API call from Ada's custom action or escalation flow, your application passes the transaction context (amount, currency, customer reference) to Shuttle. - Shuttle captures the card in isolation. On voice, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, where the customer enters card digits on the keypad and they never reach Ada or the recording. On chat and messaging channels, Shuttle sends a hosted payment link. In both cases, card data is captured within Shuttle's PCI DSS Level 1 certified environment and never enters Ada's infrastructure or the LLM. - Shuttle processes and routes to your gateway. The card is tokenised, the transaction is routed to your configured payment gateway, and the result (authorised, declined, reference number) is returned via API. - Your application receives the clean result. The agent flow continues with the payment confirmed. No card numbers, no PANs, no sensitive authentication data have touched Ada at any point. This is consistent with Ada's own position as a non-processor. You build the orchestration and agent-side wiring yourself. Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app. Honest caveat: secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Ada agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. A native Ada integration is possible only as a paid project. ## Multi-PSP Support Shuttle connects to 30+ gateways through a single configuration. You do not need to build and maintain separate connectors for each gateway. Supported processors include Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie, among others. For organisations operating across multiple brands, geographies, or client accounts, Shuttle supports per-tenant routing: different clients or business units can transact through different gateways. If you have an existing gateway relationship you want to keep, bring your own credentials. Backup gateway is also available, so a gateway outage does not take down the payment capability across your Ada agents. Switching gateways is configuration, not re-integration. A few gateways (for example, Braintree) do not work for voice capture but do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, the highest certification tier. It undergoes annual on-site QSA assessment and quarterly network scans. From a compliance architecture perspective, this matters for Ada deployments because it solves the scope problem cleanly. Card data captured via Shuttle never flows through Ada's environment. For merchants, this reduces PCI scope significantly: rather than bringing Ada's entire infrastructure into your cardholder data environment, the scope is limited to your integration with Shuttle. Most merchants can stay on a lighter SAQ-A posture as a result. Shuttle's PCI Level 1 posture is additive to Ada's SOC 2 and SOC 3 certifications. Ada provides assurance around data handling, availability, and confidentiality for CX data. Shuttle provides the cardholder data environment. The two sit alongside each other without overlap, which is precisely the architecture Ada's own design anticipates. ## Beyond Voice: Payment Links Payment links are the turnkey path, and they work even with gateways that do not support voice capture. Shuttle's payment capture is not limited to voice. Ada's strongest channel is still chat and messaging, and Shuttle generates hosted payment links that work across every channel Ada supports. An Ada chat agent can send a payment link inline in a WhatsApp message, an SMS, a Messenger thread, or an email, including mid-conversation. The customer taps the link, completes payment on a Shuttle-hosted page (branded to your organisation), and your application receives confirmation via webhook. The card data never enters the messaging channel. For businesses where Ada handles a high volume of billing queries across messaging apps, this is the most direct way to convert a resolved query into a completed payment without requiring a channel switch or agent handover. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Bill-Pay and Account Payments Ada agents already handle a large share of billing enquiries: outstanding balance lookups, payment history, invoice queries. With Shuttle connected, the same agent flow can collect the payment rather than ending with a hand-off. The customer confirms the amount, the call is handed to Shuttle's secure capture (voice) or the agent sends a payment link (chat), and the transaction is processed against the balance. ### Subscription and Renewal Payments For SaaS and subscription businesses using Ada to manage renewals and failed payment recovery, Shuttle enables a new card capture inline. Dunning flows that previously required an outbound call or a manual payment page can be handled within the Ada conversation. ### Order and E-commerce Support Retail and e-commerce deployments often use Ada to handle order queries, returns, and re-orders. When a re-order or a replacement order requires card capture, Shuttle provides the compliant capture layer. Per-tenant gateway routing means different brands or storefronts can transact through their own accounts within the same Ada deployment. ### Collections and Payment Plans Contact centre deployments using Ada for collections use cases (debt management, overdue accounts, payment arrangements) need a compliant voice capture path. Shuttle's secure capture handles card capture on outbound or inbound voice calls, and supports split payments and payment plan arrangements where a series of transactions are scheduled from a single card capture event. ## FAQ Does Ada process payments natively? No. Ada explicitly states that its services are not PCI DSS compliant and that Ada is not a payment card processor. Ada's only card-adjacent feature is a redaction function that scrubs card digits from chat transcripts. To process a payment within an Ada agent flow, you need a third-party payment layer. Does Shuttle have a native Ada integration? No. Shuttle has no native Ada integration. You invoke Shuttle's Twilio-based setup, and your application code triggers the payment handoff at the point of payment. A native Ada integration is possible only as a paid project. Does this require Twilio? Yes, for the voice capture path today. The secure capture runs via Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Payment links do not require Twilio. How do I take PCI-compliant payments on Ada? Invoke Shuttle's Twilio-based setup alongside your Ada deployment. Your application triggers Shuttle via webhook or API at the payment moment. On voice, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay; on chat, Shuttle sends a hosted payment link. Shuttle processes through your gateway and returns the result to your application. Card data never enters Ada's environment. Which gateways does Shuttle support? Shuttle connects to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie. You can bring your own gateway credentials or use per-tenant routing to send different clients or business units through separate processors. A few gateways (for example, Braintree) do not work for voice but do work for payment links. Does this work across Ada's voice and chat channels? Yes. On Ada's Voice AI channel, the call is handed to Shuttle's secure Twilio Pay capture at the point of payment. On Ada's chat and messaging channels (web chat, WhatsApp, Messenger, SMS, Instagram, email), Shuttle generates hosted payment links the agent sends inline. Can I build payment capture into Ada myself? You could use Ada's custom API actions to redirect to a payment page you build and host. However, that page and its infrastructure would fall within PCI scope and require its own certification. Shuttle provides a pre-certified capture layer at $0.20 per successful transaction that scopes you out of the cardholder data environment assessment burden. ## Related Reading - The Payment Layer for AI Agents: how AI agent platforms and payment processing fit together architecturally. - AI Voice Agent PCI Payments: secure capture and PCI scope reduction explained for compliance teams. - Voice Payments: end-to-end guide to PCI-compliant payment capture on voice channels. - Intercom Payments: the same gap-fill pattern for Intercom's AI agent and messaging platform. - Zendesk Payments: how to add compliant payment capture to Zendesk's AI agents and Talk channel. ## Add Payments to Your Ada Agents Shuttle is a PCI DSS Level 1 Service Provider. It adds compliant card capture to Ada's voice and chat agents across 30+ gateways, via a secure Twilio Pay handoff and payment links, at $0.20 per successful transaction with no setup fee, no monthly fee, and no per-seat charge (see pricing). Read the Twilio setup docs, the payment links docs, and the security overview. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [Intercom Payments](/guides/intercom-payments/) - [Zendesk Payments](/guides/zendesk-payments/) - [see pricing](/pricing/) - [Twilio setup docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links docs](https://docs.shuttleglobal.com/docs/links-intro) - [security overview](https://docs.shuttleglobal.com/docs/org-security) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/adyen-twilio-integration/ --- # How to Connect Adyen to Twilio for Voice & IVR Payments | Shuttle > Adyen doesn't natively connect to Twilio for voice payments. If you want to process Adyen transactions during a phone call -- via IVR, agent-assisted, or... # How to Connect Adyen to Twilio for Voice & IVR Payments By Shuttle Team, March 20, 2026 Adyen doesn't natively connect to Twilio for voice payments. If you want to process Adyen transactions during a phone call -- via IVR, agent-assisted, or AI voice agent -- you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Adyen (and 30+ other gateways) to Twilio's `` verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Adyen + Twilio Don't Connect Directly Adyen is built for omnichannel commerce -- online, in-app, in-store, and platform payments. Its APIs handle payment sessions, tokenisation, and split payments across merchant accounts. Twilio is built for voice and messaging. Its `` verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's `` needs a Pay Connector to route captured card data to a payment gateway. Adyen isn't one of Twilio's built-in connectors -- Twilio has no native Adyen integration. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's `` verb and routes it to Adyen's API for processing. One integration connects the two platforms. ## How It Works ``` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Adyen (processing) → Result ``` - Caller reaches payment step. Your Twilio call flow -- IVR, Studio, or custom TwiML -- triggers the `` verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Adyen. The connector creates an Adyen payment request, processes the transaction through your Adyen merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the Adyen PSP reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An Adyen account with API credentials (API key + merchant account) - A Shuttle account (free to create -- you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Adyen Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Adyen - API key: Your Adyen API key - Merchant account: Your Adyen merchant account name - Currency: Set your default (GBP, USD, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Adyen account. ### Step 3: Configure Your Twilio Call Flow Add the `` verb to your TwiML or Twilio Studio flow: ```xml Please enter your card number followed by the hash key. ``` Key parameters: - `paymentConnector` -- set to `shuttle-pay-connector` - `chargeAmount` -- the amount to charge - `currency` -- ISO currency code - `action` -- your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your `action` URL with the payment result: ```json "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-1234", "PaymentCardType": "visa", "PaymentConfirmationCode": "ADYEN-PSP-REF-123...", "ProfileId": "your-shuttle-profile-id" ``` Use the `PaymentConfirmationCode` to look up the transaction in Adyen if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Use Adyen's test environment and Twilio's test credentials to verify the flow end-to-end before going live. Adyen test card numbers: `4111 1111 1111 1111` (Visa), `5500 0000 0000 0004` (Mastercard). ## What You Can Do With Adyen + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Adyen processes, done. ### Authorise Now, Capture Later Place a hold on the card during the call. Capture the payment later through Adyen's management API -- useful for bookings, deposits, or variable-amount transactions. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Adyen and returns a reusable token (Adyen's `storedPaymentMethodId`). Use it for future payments across any channel -- web, mobile, voice, or payment links. The card data is never stored in your systems. ### Multi-Merchant via Adyen for Platforms If you use Adyen for Platforms (formerly MarketPay), Shuttle can route voice payments to the correct sub-merchant account. Each merchant's transactions go through their own Adyen account while you manage everything through a single Twilio integration. ## Multi-PSP: Beyond Adyen One of the key advantages of using Shuttle rather than an Adyen-only connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway -- serve your UK merchants with Adyen and your US merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway -- if Adyen is down, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The `` verb always points to `shuttle-pay-connector` -- Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Adyen account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Adyen + Twilio integration via Shuttle limits your PCI scope: Layer | PCI handled by DTMF capture & suppression | Twilio Card data processing | Shuttle (PCI DSS Level 1) Payment processing | Adyen (PCI DSS Level 1) Your systems | No card data -- SAQ-A Card data flows from Twilio → Shuttle → Adyen. Your application only receives redacted data (last 4 digits, card brand, PSP reference). You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Adyen to Twilio without Shuttle? Twilio doesn't have a built-in Adyen Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework -- which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the `` widget. Configure it with `shuttle-pay-connector` as the connector and the payment flow works within your Studio flow. Can I use Adyen for Platforms with this? Yes. If you're a platform using Adyen for Platforms, Shuttle can route payments to your sub-merchant accounts. Each merchant's transactions go through their own Adyen account. What about Adyen's test environment? Fully supported. Use your Adyen test API key and test merchant account in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Adyen's standard fees apply on top (interchange++ or your negotiated rate). No Shuttle setup fees or monthly minimums. Can I switch from Adyen to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same -- no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments -- step-by-step Stripe + Twilio setup - How to Connect Worldpay to Twilio for Voice Payments -- step-by-step Worldpay + Twilio setup - How to Connect Checkout.com to Twilio for Voice Payments -- step-by-step Checkout.com + Twilio setup - Shuttle vs Adyen for Platforms -- comparing payment infrastructure approaches - Adyen vs Worldpay: Which PSP for Platforms? -- head-to-head comparison - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup Connect Adyen to Twilio in minutes with Shuttle's Pay Connector -- PCI DSS Level 1, $0.20/transaction, no setup fees. [Install on Twilio](/integrations/twilio-pay/) or [book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Shuttle vs Adyen for Platforms ### Adyen for Platforms Alternatives ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Adyen: Branded Payment Links on Your Adyen Account ### QuickBooks Stripe Integration: Full Setup Guide (2026) ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Worldpay to Twilio for Voice Payments](/guides/worldpay-twilio-integration/) - [How to Connect Checkout.com to Twilio for Voice Payments](/guides/checkout-com-twilio-integration/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [Adyen vs Worldpay: Which PSP for Platforms?](/guides/adyen-vs-worldpay/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Adyen: Branded Payment Links on Your Adyen Account→](/blog/payment-links-for-adyen/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) --- URL: https://www.shuttleglobal.com/guides/adyen-vs-checkout-com/ --- # Adyen vs Checkout.com: Pricing, Features & Platform Comparison (2026) | Shuttle > Adyen vs Checkout.com compared: pricing, features, platform support, multi-PSP flexibility. Independent breakdown for platforms choosing between the two biggest enterprise PSPs. # Adyen vs Checkout.com: Which PSP for Your Platform? By Shuttle Team, February 23, 2026 Adyen and Checkout.com are the two enterprise payment processors that come up in almost every platform's PSP evaluation. Both serve large, global merchants. Both offer direct acquiring. Both claim to solve the same problem: reliable, high-performance payment processing at scale. So which is right for your platform? The honest answer: both are strong. They're built for different priorities, and the right choice depends on what your platform values most. This guide covers the real differences -- geography, pricing, product depth, and commercial flexibility -- without the usual vendor spin. There is also a third option that most comparisons skip: using both simultaneously through a PSP-neutral infrastructure layer. More on that below. ## Adyen vs Checkout.com: Side-by-Side Comparison ## Where Adyen Wins ### 1. Unified Platform Architecture Adyen's single-platform philosophy is genuinely differentiated. Processing, acquiring, risk, data, and value-added services run on the same infrastructure. There is no patchwork of acquired products or third-party dependencies behind the facade. For platforms, this matters because it eliminates the data fragmentation that plagues multi-vendor payment stacks. Settlement data, dispute management, and analytics all live in one place, under one API contract. ### 2. Adyen for Platforms Adyen's dedicated platform product handles the complexity of onboarding sub-merchants, managing split settlements, and distributing funds. It was designed for marketplaces and SaaS platforms that want to embed payments without becoming a payment company themselves. The product has matured significantly since launch. Platforms building on Adyen for Platforms get access to Adyen's acquiring network, risk tools, and reporting -- all surfaced through a single integration. ### 3. Transparent Interchange++ Pricing Adyen publishes its processing fees. The Interchange++ model means platforms pay card network interchange (set by Visa and Mastercard), plus a small, disclosed markup. There are no surprises, no bundled rates obscuring margin, and no renegotiation needed every year. For finance teams and CFOs who want predictable cost of revenue, this pricing model is considerably easier to model than opaque enterprise quotes. ### 4. Public Company Stability Adyen is publicly traded on Euronext Amsterdam. Quarterly earnings, audited financials, and public accountability are part of the package. For enterprise procurement and vendor risk teams, that transparency reduces perceived counterparty risk compared to a privately held alternative. This matters less for early-stage platforms, but becomes a meaningful consideration when the platform itself is enterprise-grade or publicly traded. ## Where Checkout.com Wins ### 1. Aggressive Commercial Terms Checkout.com built its reputation partly by being commercially flexible in ways that larger, more bureaucratic processors would not match. Negotiated rates, volume-based incentives, and custom commercial structures are a known part of their enterprise sales approach. For high-volume platforms with leverage in commercial negotiations, this flexibility can translate into meaningfully lower per-transaction costs compared to a more standardised pricing model. ### 2. Performance Optimisation Focus Checkout.com has invested heavily in intelligent routing, authorisation optimisation, and real-time analytics built around conversion improvement. Their product positioning is explicitly performance-oriented: the claim is that routing intelligence and issuer relationships produce higher authorisation rates. For platforms where basis-point improvements in approval rates compound at scale, this focus is a genuine differentiator. A 0.5% improvement in authorisation rate across €5B in annual volume is worth tens of millions. ### 3. Broader Direct Acquiring Coverage Checkout.com offers direct acquiring in 50+ markets, compared to Adyen's 30+. For platforms with significant payment volume in emerging markets, Southeast Asia, or markets where Adyen's direct acquiring is not available, Checkout.com's geographic footprint may cover more of the relevant territory. Direct acquiring -- rather than using third-party acquirers -- generally produces better data, faster settlement, and more control over dispute handling. ### 4. Enterprise Flexibility Checkout.com's privately held structure gives it commercial agility that a public company trading on quarterly earnings cannot always match. Large custom deals, bespoke integration support, and flexibility on contract structure are areas where Checkout.com's sales organisation has historically moved quickly. ## Why Platforms Are Moving Beyond the Adyen-vs-Checkout Question Here is the frame that most comparisons skip. Both Adyen and Checkout.com are excellent PSPs. The question is not which is objectively better -- it is whether locking your platform into any single PSP makes strategic sense. Platforms that process payments on behalf of merchants or sub-users face a specific set of constraints that single-PSP architectures handle poorly: Coverage gaps. No single PSP covers every market, every payment method, and every merchant type equally well. Adyen is stronger in some verticals; Checkout.com in others. A platform serving merchants across multiple verticals and geographies will find edge cases where the chosen PSP underperforms. Negotiating leverage. Platforms locked into a single PSP have no credible alternative when renewal time arrives. PSPs know this. Platforms with multi-PSP infrastructure -- even if they route 90% of volume through one provider -- can negotiate from a fundamentally different position. Resilience. Single-PSP platforms carry concentration risk. When a PSP has an outage (and they do), the platform's entire payment capability goes down. Multi-PSP routing removes that single point of failure. Merchant preference. Some large merchants have existing PSP relationships and pricing they are not willing to abandon. A platform that can accommodate merchant-side PSP preferences -- rather than forcing a switch -- has a material advantage in enterprise merchant acquisition. PSP-neutral infrastructure allows platforms to connect multiple PSPs behind a single integration, unified checkout experience, and common data layer. Adyen and Checkout.com both become options in the routing logic rather than existential commitments. ## When to Choose Adyen Adyen is the stronger default for platforms that: - Want a single consolidated stack with no third-party dependencies in the critical path - Are building on Adyen for Platforms and need the full suite of sub-merchant management tools - Value pricing transparency and want predictable, auditable cost of revenue - Operate primarily in markets where Adyen has strong direct acquiring coverage - Are enterprise procurement-led, where public-company financial stability simplifies vendor risk ## When to Choose Checkout.com Checkout.com is the stronger default for platforms that: - Have significant volume and commercial leverage to negotiate aggressive rates - Are optimisation-focused and want to squeeze authorisation rate improvements from intelligent routing - Operate in geographies where Checkout.com's direct acquiring coverage exceeds Adyen's - Need commercial flexibility that a larger, publicly traded processor is not positioned to offer - Are digital-native businesses where Checkout.com's enterprise team has deep vertical knowledge ## When to Use Both Platforms that have reached meaningful scale -- typically processing over £50M annually on behalf of merchants -- frequently find that the Adyen-vs-Checkout.com choice is a false one. The answer is both, routed intelligently based on merchant type, geography, transaction characteristics, and conversion performance. This is not a theoretical architecture. It is how the most sophisticated platforms operate. The infrastructure that makes it practical is a PSP-neutral layer that sits between the platform and its PSPs, handling routing decisions, unified settlement, and a single integration surface. Shuttle Global supports both Adyen and Checkout.com -- alongside 38+ other PSPs -- under a single white-label integration. Platforms connect once to Shuttle's infrastructure and get access to the full PSP network, with routing decisions made programmatically based on real performance data. ## Frequently Asked Questions Is Adyen or Checkout.com cheaper? Adyen publishes Interchange++ pricing, which is transparent and auditable. Checkout.com pricing is custom and enterprise-negotiated, which can result in better rates for high-volume platforms with leverage. Without a specific volume and commercial negotiation in hand, a direct cost comparison is not meaningful. Platforms processing over £50M annually should negotiate with both. Which PSP has better authorisation rates? Both Adyen and Checkout.com invest significantly in authorisation optimisation. Performance varies by market, card type, merchant category, and transaction profile. The honest answer is that neither is universally better -- which is an argument for testing both rather than assuming one outperforms. Can a platform use both Adyen and Checkout.com at the same time? Yes. PSP-neutral infrastructure like Shuttle allows platforms to route transactions across multiple PSPs simultaneously. This is increasingly common among large platforms for resilience, optimisation, and commercial leverage. Does Adyen for Platforms replace the need for a separate platform infrastructure layer? Adyen for Platforms handles sub-merchant onboarding and split settlements within the Adyen ecosystem. It does not provide PSP-neutral routing, multi-channel payments (voice, chat, AI agents), or the ability to use non-Adyen processors. For platforms that need flexibility beyond the Adyen stack, a neutral layer sits alongside rather than replacing Adyen for Platforms. How is Checkout.com's financial stability? Checkout.com is privately held. Its valuation fell from a peak of approximately $40B to around $11B following broader fintech market corrections. It remains a significant, well-capitalised business. Platforms running vendor risk assessments should review Checkout.com's financial disclosures available through their enterprise sales process. Which PSP is better for voice and AI agent payments? Neither Adyen nor Checkout.com provides native voice checkout or AI agent payment capability out of the box. Platforms building multi-channel payment flows -- including voice, chat, and agent-initiated payments -- typically add a specialised layer on top of their PSP. See our guide on agentic payments for platforms. ## Related Reading - Adyen for Platforms: Full Review - Checkout.com for Platforms: Full Review - Alternatives to Adyen for Platforms - Alternatives to Checkout.com - PSP-Neutral vs Single-PSP Architecture - Enterprise PSP Mandates Explained ## Work With Both -- Without Locking Into Either Shuttle Global is the PSP-neutral payments infrastructure for platforms. Connect Adyen, Checkout.com, and 38+ other processors through a single integration. White-label checkout, voice payments, AI agent support, and unified settlement data -- without rebuilding your payment stack every time your PSP strategy changes. Book a Discovery Call | See Platform Solutions ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Shuttle vs Checkout.com for Platforms ### Checkout.com Alternatives for Platforms ### Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### Agentic Commerce: How AI Will Rewrite the Checkout ### Shuttle vs Adyen for Platforms ## Links - [Shuttle Global](/platforms/) - [agentic payments for platforms](/guides/agentic-payments-for-platforms/) - [Adyen for Platforms: Full Review](/vs/adyen/) - [Checkout.com for Platforms: Full Review](/vs/checkout-com/) - [Alternatives to Adyen for Platforms](/alternatives/adyen-for-platforms/) - [Alternatives to Checkout.com](/alternatives/checkout-com/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates Explained](/guides/enterprise-psp-mandates/) - [Book a Discovery Call](/discovery/) - [See Platform Solutions](/platforms/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [AlternativeCheckout.com Alternatives for Platforms→](/alternatives/checkout-com/) - [BlogPayment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account→](/blog/payment-links-for-checkout-com/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) --- URL: https://www.shuttleglobal.com/guides/adyen-vs-worldpay/ --- # Adyen vs Worldpay: Which PSP for Your Platform? | Shuttle > Adyen vs Worldpay: an honest 2026 comparison for platforms and enterprise merchants. # Adyen vs Worldpay: Which PSP for Your Platform? By Shuttle Team, February 23, 2026 Adyen vs Worldpay: an honest 2026 comparison for platforms and enterprise merchants. We cover pricing, settlement speed, global acquiring reach, platform products, and the trade-offs nobody else writes down -- including why a growing number of platforms now reject the framing entirely. The honest answer is that they are genuinely different -- optimised for different use cases, different geographies, and different platform architectures. This guide breaks down exactly where each one wins, where each one falls short, and why a growing number of platforms have concluded the comparison is the wrong frame entirely. ## Who Are These Two PSPs? Adyen is a Dutch payments company listed on Euronext Amsterdam. It processes over €1.6 trillion annually and holds direct acquiring licences in more than 30 countries -- meaning it owns the acquiring relationship rather than routing through a third party. Adyen built its platform from scratch as a single unified stack: one API, one contract, one reporting layer covering processing, acquiring, and value-added services like issuing and capital. Adyen for Platforms is its dedicated product for marketplaces and software platforms that want to embed payments. Worldpay is one of the world's largest acquirers by volume, now owned by Global Payments following a $24 billion acquisition completed in 2024. Its heritage is deep in card-present and card-not-present acquiring, with reach across 146+ countries and support for 135+ currencies. Worldpay has strong incumbent relationships in enterprise financial services, travel, gaming, and retail. It has changed hands multiple times in recent years -- from Vantiv to FIS to spinout to Global Payments -- which has introduced some organisational complexity. ## Side-by-Side Comparison Annual processing volume ~$2T+ (est.) Countries supported 30+ (direct acquiring) 146+ (mix of direct + indirect) Currencies Pricing model Interchange++ (transparent) Custom enterprise (negotiated) Acquiring model Direct (owns licences) Mix of direct and indirect Platform / marketplace product Adyen for Platforms Worldpay for Enterprise Card-present strength Very strong (heritage) Card-not-present strength Voice / AI agent payments Not native Payment links Embedded checkout Yes (via Adyen Drop-In) Reporting & reconciliation Unified, excellent Solid, multiple portals API quality Good (improving post-FIS) Ownership stability Public company, stable Recently acquired (Global Payments) PCI DSS Level 1 ## Where Adyen Wins Direct acquiring in 30+ markets. Adyen's most significant structural advantage is that it owns acquiring licences directly. This removes intermediaries from the payment chain, which typically means higher authorisation rates, faster settlement, and cleaner economics. For platforms processing high volumes across Europe, North America, and key APAC markets, this matters. A genuinely unified platform. Adyen built one stack. There is no patchwork of acquired products, no legacy gateway bolted onto a modern API. When you integrate Adyen, you get processing, risk, reconciliation, and issuing from the same codebase. For platforms that value operational simplicity, this is a meaningful advantage. Adyen for Platforms. Adyen's dedicated marketplace and platform product handles sub-merchant onboarding, split settlements, and payout management within a single integration. Platforms that want to go deep on embedded finance -- including issuing cards to sub-merchants -- have a clear roadmap within the Adyen ecosystem. Transparent interchange-plus pricing. Adyen prices on interchange++ by default, which means you see exactly what the card networks charge and what Adyen adds. For finance and procurement teams, this transparency simplifies cost modelling and removes the uncertainty of opaque blended rates. Strong in omnichannel and unified commerce. Adyen's single-stack approach extends to point-of-sale, making it well-suited for platforms that serve merchants with both online and physical channels. ## Where Worldpay Wins Broader geographic coverage. Worldpay's 146-country footprint is genuinely wider than Adyen's. For platforms serving merchants in Southeast Asia, Latin America, the Middle East, or Central and Eastern Europe at scale, Worldpay's established presence in those corridors is a practical advantage. Legacy enterprise relationships. Worldpay has been processing payments for major enterprises for decades. In sectors like financial services, travel and hospitality, and gaming, many large merchants already have Worldpay contracts, technical integrations, and account teams in place. Platforms serving those verticals will encounter Worldpay as the default at the merchant level. Competitive interchange on high-volume deals. Worldpay negotiates rates for enterprise accounts, and at high volume its effective rates can be competitive. Platforms with significant negotiating leverage may find the economics work in their favour. Card-present and in-person heritage. Worldpay's roots are in physical acquiring. Platforms that serve brick-and-mortar merchants or need robust card-present infrastructure in markets outside Adyen's direct acquiring footprint will find Worldpay's coverage useful. Resilience of a larger parent. Global Payments is a large, listed company with significant resources. Post-integration, Worldpay has the backing of a group that processes roughly 50 billion transactions annually. For platforms that weight financial stability and infrastructure scale, this matters. ## Why Many Platforms Choose Not to Choose Here is where the comparison gets more interesting. Platforms are not merchants. A merchant picks one PSP, integrates it, and processes on it. A platform serves dozens, hundreds, or thousands of merchants -- each with different geographies, business types, volumes, and existing PSP relationships. Locking your platform to a single PSP means every one of your merchants inherits that constraint. The practical consequences: - A merchant in a market where your chosen PSP has weaker coverage gets worse authorisation rates. - A merchant who already uses the other PSP faces an unnecessary migration. - Your platform has a single point of failure -- if your PSP has an outage, every merchant on your platform is affected simultaneously. - Expanding into new verticals or geographies may require renegotiating or re-integrating your PSP entirely. Platforms that have worked through these constraints often reach the same conclusion: the goal is not to pick the best PSP, it is to build a payment layer that is not dependent on one PSP's strengths or limited by one PSP's weaknesses. This is the logic behind PSP-neutral infrastructure. ## The PSP-Neutral Alternative Shuttle is The Payment Layer for platforms. Instead of building directly on Adyen or Worldpay, platforms integrate Shuttle once and get access to both -- and 38+ other PSPs -- through a single API and a single contract. What this means in practice: Use both simultaneously. Route UK merchants through Adyen for its direct acquiring advantage. Route Latin American merchants through a local PSP with better in-country coverage. Route merchants in sectors where Worldpay has legacy relationships through Worldpay. All of this happens within one integration, one dashboard, and one reconciliation layer. White-label checkout and onboarding. Shuttle provides the platform layer -- branded checkout, sub-merchant onboarding, portals, payment links -- on top of whichever underlying PSPs you choose. Your merchants see your brand. The PSP selection is invisible to them. Multi-channel from day one. Shuttle supports payments via web checkout, payment links, voice (Twilio, Genesys, and compatible CCaaS platforms), and chat and AI agent integrations. Neither Adyen nor Worldpay natively supports voice or agent-initiated payments at the channel level. PSP redundancy. If one PSP has an outage or rate change, you can move the affected payment types to another connected PSP. Single-PSP platforms have no fallback. PCI DSS Level 1, ISO 27001, and SOC 2. Shuttle handles the compliance surface so platforms do not take on additional PCI scope when adding payment channels. The economics work differently too. Rather than negotiating with each PSP separately -- a process that typically favours larger platforms -- Shuttle's relationships across the PSP network mean platforms access competitive terms without having to reach Adyen or Worldpay's volume thresholds on their own. ## Decision Framework Choose Adyen directly if: - You process very high volume predominantly in Europe, North America, or key APAC markets where Adyen holds direct acquiring licences - You want a single-vendor unified commerce stack including point-of-sale - You plan to build deeply into Adyen for Platforms and Adyen Issuing - You value interchange-plus pricing transparency above all else - Your platform serves a single vertical where Adyen is dominant Choose Worldpay directly if: - Your platform's merchant base is concentrated in regions where Worldpay has stronger in-country coverage - You serve enterprise merchants who already have Worldpay contracts and relationships - Card-present infrastructure is a core requirement for your vertical - You are in financial services, travel, or gaming with established Worldpay integrations at the merchant level Use both via a PSP-neutral layer if: - Your platform serves merchants across multiple geographies with different PSP needs - You want the flexibility to add, remove, or swap PSPs without re-integrating your payment stack - You are adding payment channels beyond web checkout -- voice, AI agents, payment links - You want white-label checkout and sub-merchant management on top of PSP infrastructure - PSP redundancy and failover are operational requirements ## Frequently Asked Questions Is Adyen better than Worldpay? Neither is universally better. Adyen leads on direct acquiring, unified platform design, and transparent pricing. Worldpay leads on geographic breadth, card-present heritage, and enterprise relationships in certain verticals. The right answer depends on your platform's merchant base and geographic footprint. Can a platform use both Adyen and Worldpay? Yes, and many do -- but doing so with direct integrations to both creates significant technical and operational complexity. A PSP-neutral layer like Shuttle provides a single integration that routes to both without duplicating your payment stack. How does Adyen for Platforms compare to Worldpay for Enterprise? Adyen for Platforms is purpose-built for marketplace and platform use cases with sub-merchant onboarding, split settlements, and issuing built into a single stack. Worldpay's enterprise offering is more focused on large merchant acquiring. For platforms building embedded payments products, Adyen for Platforms is typically the more complete native product -- though it comes with Adyen's geographic constraints. Is Worldpay stable after being acquired by Global Payments? The acquisition closed in 2024. Global Payments has made integration commitments, though any major acquisition introduces a period of organisational transition. Platforms evaluating Worldpay should model what integration into the Global Payments stack means for API continuity, account team stability, and product roadmap. Does Shuttle replace Adyen or Worldpay? No. Shuttle sits above the PSP layer. It uses Adyen, Worldpay, and other PSPs as the underlying acquiring infrastructure. Platforms that already have Adyen or Worldpay relationships can typically bring those into Shuttle rather than replacing them. What does PSP-neutral pricing look like? Shuttle's pricing is transparent and designed to work alongside PSP interchange. Contact us for a model based on your platform's volume and merchant mix. ## Related Reading - Adyen for Platforms: Alternatives and Considerations - Worldpay Alternatives for Platforms - Shuttle vs Adyen - Shuttle vs Worldpay - PSP Consolidation and Platform Risk - PSP-Neutral vs Single-PSP: Which Architecture Fits Your Platform? - Payment Links for Hotels & Holiday Accommodation -- payment collection for the travel and hospitality vertical ## Work with Shuttle If you are comparing Adyen and Worldpay, you are probably building something at scale. Shuttle works with platforms that need payments infrastructure to flex across PSPs, channels, and geographies -- without rebuilding every time requirements change. Book a Discovery Call to talk through your PSP architecture. See How Shuttle Works for Platforms ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Shuttle vs Adyen for Platforms ### Shuttle vs Worldpay for Platforms ### Adyen for Platforms Alternatives ### Payment Links for Worldpay: Send Checkout Links Without Leaving Worldpay ### Payment Links for Adyen: Branded Payment Links on Your Adyen Account ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [travel and hospitality](/guides/payment-links-for-hotels/) - [Adyen for Platforms: Alternatives and Considerations](/alternatives/adyen-for-platforms/) - [Worldpay Alternatives for Platforms](/alternatives/worldpay/) - [Shuttle vs Adyen](/vs/adyen/) - [Shuttle vs Worldpay](/vs/worldpay/) - [PSP Consolidation and Platform Risk](/blog/psp-consolidation-platform-risk/) - [PSP-Neutral vs Single-PSP: Which Architecture Fits Your Platform?](/guides/psp-neutral-vs-single-psp/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Book a Discovery Call](/discovery/) - [See How Shuttle Works for Platforms](/platforms/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Adyen for Platforms→](/vs/adyen/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) - [AlternativeWorldpay Alternatives for Platforms→](/alternatives/worldpay/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogPayment Links for Worldpay: Send Checkout Links Without Leaving Worldpay→](/blog/payment-links-for-worldpay/) - [BlogPayment Links for Adyen: Branded Payment Links on Your Adyen Account→](/blog/payment-links-for-adyen/) --- URL: https://www.shuttleglobal.com/guides/agent-assisted-payments/ --- # Agent-Assisted Payments: Secure Card Capture on Live Calls | Shuttle > Quick answer: agent-assisted payments keep a live agent on the call while the caller types their card number on their phone keypad. # Agent-Assisted Payments: Secure Card Capture on Live Calls By Shuttle Team, July 14, 2026 Quick answer: agent-assisted payments keep a live agent on the call while the caller types their card number on their phone keypad. The digits route directly to the payment gateway, the agent sees only masked progress on screen, and the card number never enters your phone system, call recordings or agent desktops. The conversation keeps going, the recording keeps running, and the systems that used to carry card data no longer do. Agent-assisted payment capture is one of the established patterns for PCI compliant phone payments, and it is the one built for a specific moment: the payment that happens inside a conversation. This guide covers why the pattern exists, how it works for the agent and the caller, how it compares to the alternatives, what to do when a payment fails mid-call, and what changes when the "agent" is an AI. ## Why agent-assisted payments exist Payments don't arrive on a call as standalone events. They arrive at the end of something else: a dispute gets resolved and the balance is due, a renewal call turns into an upgrade, an agent talks a caller through their options and they agree an amount. The payment is the last step of a conversation that a person just did the work to get right. The traditional ways of taking that payment break the moment. Transfer the caller to an automated line and some of them don't survive the transfer: they get lost in the menu, mistype a reference, or hang up and mean to call back. Send them away to pay online and the payment leaves the call entirely, along with any certainty it will complete. Either way, the person who built the agreement is gone at the exact point the caller is ready to pay. The old alternative, keeping the agent on and having the caller read their card number aloud, solves the completion problem and creates a compliance one. The agent hears the number, the recording captures it, and the phone system carries it, which pulls all of them into PCI DSS scope. Agent-assisted payments exist to resolve that tension. The pattern keeps the conversation and removes the card data. The agent who agreed the amount stays on the line to the confirmation; the card number goes somewhere your systems never see. ## How an agent-assisted payment works ### The agent's side - The agent triggers the capture. When the caller is ready to pay, the agent starts the secure payment step from their screen, with the amount already agreed on the call. - The caller enters their card on the keypad. The keypad tones route directly to the payment gateway rather than through the agent's audio path. - The agent sees masked progress. Their screen shows that digits are arriving, masked, not the digits themselves. The agent stays on the line and keeps talking: they can reassure the caller, answer questions, or prompt them if they stall on the expiration date. - The confirmation lands in the agent's screen. Approved or declined, with a tokenized reference. The agent confirms the result to the caller and the conversation carries on, to a receipt, a follow-up, or a goodbye. The mechanics underneath (how the tones are intercepted, and the difference between clamping, masking and suppression) are covered in our guide to DTMF payment capture. For the buyer's purposes, the important property is the outcome: the agent participates in the payment without ever having access to the card. ### The caller's side From the caller's seat, the experience is close to invisible. Nobody asks them to read a card number to a stranger. Nobody transfers them to a robot. They type their card into their own phone, the way they'd type a PIN at an ATM, while the person they were just talking to stays with them. If they hesitate or mistype, the agent is right there. And because the card number never enters the call audio, the recording can keep running through the whole payment. Quality monitoring and dispute evidence stay intact, with no gap in the recording and no card data in it. ## Agent-assisted payments vs the alternatives Three other patterns compete for the same job. Each has a place; the differences matter. Versus IVR payments. An IVR payment is fully automated: the caller pays through a keypad flow with no agent on the line. It's the right tool for high-volume, routine payments (bills, balances, renewals), and the wrong one for payments that need a human first. If the amount had to be negotiated, explained or agreed, an IVR can't do that part, and transferring a caller into one after the conversation risks losing them at the handoff. Versus pause-and-resume recording. In this pattern the agent pauses the call recording while the caller reads their card number aloud, then resumes it. The pattern is workable and widely deployed. Its weakness is operational: the protection depends on the pause happening on every call, and a missed pause means a recording with a card number in it. The spoken number also still travels through your phone system and your agent's ears, so those stay in scope even when the pause works perfectly. The critique here is of the operating model, not any particular product: a control that relies on a human action repeating correctly on every call is a fragile control. Versus a virtual terminal. With a virtual terminal, the caller reads the card aloud and the agent types it into a payment screen. It's the simplest thing to set up and the heaviest to live with: the agent hears and handles the card, the workstation processes it, and the desktop, its network and the people using it all sit inside PCI DSS scope. Agent-assisted capture IVR payment Pause-and-resume Virtual terminal Agent on the call Agent hears or sees the card Yes (hears) Yes (hears and types) Recording runs throughout No (must pause) No (captures spoken card data) Card data enters your systems Yes (spoken) Yes (spoken and typed) Payments inside conversations High-volume routine payments Legacy operations Very low volume, accepted scope ## When the payment goes wrong mid-call Live-call payments fail in predictable ways, and the recoveries are worth designing in advance, because the compliant answer is never "just read me the number". - The call drops mid-payment. The caller was two digits from done and the line went. Rather than hoping they call back and queue again, send a payment link by SMS or email: they finish the payment on their own device, against the same amount the agent already set up. - The caller has no card to hand. The card is in another room, expired, or they'd simply rather not use one. Take a bank payment on the same call instead. See ACH and bank payments over the phone. An operation that treats these as designed paths rather than exceptions collects more of the payments it has already earned on the call. ## When the agent isn't human The "agent" in agent-assisted no longer has to be a person. The same secure capture pattern works when an AI voice agent is running the call: the AI handles the conversation, invokes the secure payment step when the caller is ready, and receives only the result, so card data never reaches the AI platform, its transcripts or its recordings. The compliance logic is identical; the thing being kept away from the card just happens to be a model instead of a person. If your roadmap includes automated voice, it's worth choosing a capture approach that supports both from the start. See AI voice agents and PCI compliant payments. ## How Shuttle handles agent-assisted payments Shuttle provides agent-assisted capture as part of one payment layer across voice, links and bank payments: - It runs on Twilio's voice infrastructure. Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. - Card details are tokenized with the payment gateway itself. Shuttle holds no card vault of its own, so the capture doesn't create a new place where card data accumulates. - Your gateway, not ours. Shuttle works with 40+ payment gateways, so agent-assisted payments settle through the merchant account you already have. Voice capture works on many supported gateways; payment links cover the rest. - The recoveries are built in. Payment links by SMS or email for the dropped call, bank payments for the caller without a card, so a failed card moment doesn't become a lost payment. - Multi-client routing. If you collect for many clients, each with their own merchant account (answering services, billing services, collections servicers), every payment routes to the right client's account automatically. See taking payments on behalf of your clients. ## Agent-assisted payments FAQ ### What are agent-assisted payments? Agent-assisted payments are card payments taken on a live call where the caller enters their card number on their phone keypad instead of reading it aloud. The agent stays on the call throughout, the digits route directly to the payment gateway, and the card number stays out of the phone system, the recording and the agent's screen. ### Does the agent hear the card number? No. The caller types the number rather than speaking it, and the keypad tones are kept out of the agent's audio path. The agent's screen shows masked progress, enough to see the caller is entering digits, never the digits themselves. ### Does agent-assisted capture work with call recording? Yes, and that's one of its main advantages. Because the card number never enters the call audio, the recording can run through the entire payment without capturing card data. There's no pause to remember and no gap in the recording. ### What does it do to our PCI scope? Implemented correctly, agent-assisted capture keeps card data out of your phone system, call recordings and agent desktops, which typically takes those systems out of PCI DSS scope and supports the lighter self-assessment routes. Where your operation lands exactly depends on the details of your environment, so confirm your SAQ level with your acquirer or assessor. ### Can an AI agent take the payment instead of a human? Yes. The same secure capture works when an AI voice agent is on the call: the AI triggers the payment step and receives only the result, so card data never reaches the AI platform or its transcripts. See AI voice agents and PCI compliant payments. ### Do we have to change payment providers? Not with a gateway-agnostic capture layer. Shuttle works with 40+ payment gateways, so agent-assisted payments settle through your existing merchant account rather than forcing a switch. Voice capture works on many supported gateways; payment links cover the rest. ## Related reading - PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking - IVR Payments: PCI Compliant Self-Service Phone Payments - Virtual Terminal Payments: PCI Rules and Secure Alternatives - AI Voice Agents and PCI Compliant Payments - Contact Centre Payments: The Complete Guide Taking payments on live calls without the card data? Talk to us. If you'd rather explore the technical side first, docs.shuttleglobal.com covers the flows, with sandbox accounts available for testing. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Agentic Payments Isn't Solved Yet ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. ## Links - [PCI compliant phone payments](/guides/pci-compliant-phone-payments/) - [DTMF payment capture](/guides/dtmf-payments/) - [IVR payment](/guides/ivr-payments/) - [virtual terminal](/guides/virtual-terminal-payments/) - [ACH and bank payments over the phone](/guides/ach-payments-over-the-phone/) - [AI voice agents and PCI compliant payments](/guides/ai-voice-agent-pci-payments/) - [40+ payment gateways](/payment-providers/) - [taking payments on behalf of your clients](/guides/take-payments-on-behalf-of-clients/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking](/guides/dtmf-payments/) - [IVR Payments: PCI Compliant Self-Service Phone Payments](/guides/ivr-payments/) - [Virtual Terminal Payments: PCI Rules and Secure Alternatives](/guides/virtual-terminal-payments/) - [AI Voice Agents and PCI Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [Contact Centre Payments: The Complete Guide](/guides/contact-centre-payments/) - [Talk to us](/contact/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogThe First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.→](/blog/agentic-payments-go-live/) --- URL: https://www.shuttleglobal.com/guides/agent-native-checkout/ --- # Agent-Native Checkout: Why AI Commerce Needs New Payment APIs | Shuttle > Every AI agent that tries to buy something on the open web hits the same wall. The checkout was built for a human with a browser, not software with... # Agent-Native Checkout: Why AI Commerce Needs New Payment APIs By Shuttle Team, March 9, 2026 Every AI agent that tries to buy something on the open web hits the same wall. The checkout was built for a human with a browser, not software with credentials. Agent-native checkout is the missing piece -- direct programmatic payment APIs that let agents authenticate, select items, and complete transactions without navigating UI. It doesn't exist at scale yet. Understanding why tells you where agentic commerce actually is versus where the demos suggest it is. ## Why current checkouts break agents Modern checkout flows are optimised for human psychology. Progress bars, trust badges, upsell carousels, multi-step forms with CAPTCHA challenges. Every element serves a conversion purpose for human shoppers. For an AI agent, every one of those elements is an obstacle. ### The DOM fragmentation problem No two checkout pages share the same structure. Shopify's checkout differs from WooCommerce's, which differs from custom builds, which differ from marketplace flows. An agent navigating these surfaces needs either: - Browser automation -- Selenium, Playwright, or a vision model interpreting screenshots. Brittle, slow, and actively blocked by bot detection. - Per-merchant integrations -- Custom scrapers for every merchant. Doesn't scale. - A universal checkout API -- The thing that doesn't exist yet. Even when agents can parse a checkout form, they face 3D Secure challenges, dynamic CAPTCHA walls, and session tokens that expire. The failure rate for automated checkout on the open web is measured in the tens of percents, not fractions. ### Bot detection is working against agents Merchants invest heavily in preventing automated purchases -- for good reason. Scalping bots, credential stuffing, and card testing attacks all use the same browser automation techniques that legitimate AI agents would use. There's no standardised way for a merchant to distinguish a legitimate AI agent acting on behalf of an authorised user from a malicious bot. IP reputation, browser fingerprinting, and behavioural analysis all treat agent traffic as suspicious by default. This creates a structural conflict. Merchants want to prevent automated checkout. AI agents need to automate checkout. Without a new protocol, one side loses. ## What agent-native checkout actually requires Agent-native checkout is a direct API between the agent and the merchant's payment system. No UI rendering. No form filling. No browser simulation. Four capabilities are non-negotiable: - Product discovery -- A structured catalogue the agent can query. Not a web page to scrape. GraphQL or REST endpoints that return products, prices, availability, and variants. - Cart management -- Programmatic add-to-cart, quantity updates, and coupon application. Stateful or stateless, but machine-readable. - Identity and authorisation -- The agent proves it represents an authorised buyer. OAuth tokens, signed JWTs, or a new agent-identity standard. The critical requirement is that the merchant can verify the buyer independently of the agent. - Payment execution -- Direct transaction initiation with a payment credential. Tokenised cards, bank-initiated transfers, or wallet authorisations. No form fields. The agent never sees raw card data -- it passes a token, the PSP handles the rest. This is actually simpler than traditional e-commerce from a PCI compliance perspective, because the agent never needs to render a payment form or handle card details in transit. ## Where the fragments are Some of this exists, but none of it constitutes a standard: Shopify Storefront API supports headless cart and checkout operations. An agent could theoretically complete a purchase entirely through API calls. But Shopify's fraud detection still flags automated traffic, and 3DS challenges require human interaction. Stripe's Agent Toolkit provides an SDK for agent-initiated payments, but it assumes the agent is operating within a platform's own checkout -- not across the open web. It's a developer tool, not a merchant-facing protocol. Google's A2A protocol proposes agent-to-agent communication standards, including payment handoffs. But the protocol is pre-production and requires merchant adoption that isn't happening yet. Amazon's programmatic ordering APIs (for business accounts) offer something close to agent-native checkout, but they're limited to Amazon's ecosystem. Each is either merchant-specific, platform-locked, or pre-production. The universal layer doesn't exist. ## The chicken-and-egg problem Merchants won't build agent checkout APIs until agent commerce represents meaningful revenue. Agent commerce can't generate meaningful revenue until merchants expose programmatic checkout surfaces. This isn't a technology problem. It's an incentive alignment problem. ### Three forces that could break the deadlock Payment processor adoption. If Stripe, Adyen, or other major PSPs build agent-native checkout into their hosted payment pages, merchants get the capability without custom development. The processor becomes the translation layer between agent requests and merchant checkout. This is the most likely path -- processors are already investing in agentic payment infrastructure. Marketplace consolidation. If a critical mass of commerce flows through platforms that already have APIs (Amazon, Shopify, Uber Eats), agents can reach meaningful purchasing power without universal merchant adoption. The long tail of merchants follows once the economics are proven. A new protocol standard. Something like an "Agent Checkout Protocol" -- a machine-readable checkout specification that any merchant can expose alongside their human checkout. Similar to how standardised crawler access, or how Open Banking standardised payment initiation. The W3C, IETF, or a consortium of payment processors would need to drive this. ## What works right now The universal agent checkout doesn't exist. But agents aren't stuck doing nothing. Three patterns work today within defined boundaries: Platform-controlled checkout. If the platform owns both the agent and the checkout (a food ordering app with its own AI ordering, a CCaaS platform with voice agents taking payments), there is no DOM fragmentation problem. The platform builds a direct API between its agent and its own payment flow. This is where most production agentic payments actually happen -- voice agents taking card payments, chat agents collecting payment details, AI ordering within closed marketplaces. Payment links as the bridge. When an agent can't complete checkout programmatically, it generates a payment link and sends it to the human. The human clicks, pays on a hosted checkout page, and the agent gets a webhook confirmation. It's not autonomous -- the human is still in the loop for payment -- but it works across any merchant that accepts links. This is the pragmatic pattern for agents operating in voice and messaging channels today. API-first merchants. Some merchants already expose the APIs agents need. Shopify (Storefront API), Amazon Business (Purchase Orders API), most B2B SaaS with billing APIs. Agents can complete purchases with these merchants today. The coverage is narrow, but it's real. Agent commerce will grow merchant by merchant as more platforms expose programmatic checkout, not as a single protocol switch. The honest picture: agentic payments works well in closed environments where one company controls both sides. It barely works on the open web. The gap between the demos and production reality is the checkout surface -- and that gap closes slowly, one merchant API at a time. ## Related reading - Agentic Payments Isn't Solved Yet - The AI Payment Consent Problem Nobody Is Talking About - Agentic Commerce: Payment Infrastructure for AI Agents - How AI Voice Agents Take PCI-Compliant Payments - Agentic Payments in 2026: The Infrastructure Guide for Platforms ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Checkout.com Alternatives for Platforms ### Agentic Commerce: How AI Will Rewrite the Checkout ### Shuttle vs Checkout.com for Platforms ### Can You Take Card Payments on a Retell AI Voice Agent? ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ### Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account ## Links - [PCI compliance](/guides/ai-payment-security/) - [agentic payment infrastructure](/blog/agentic-payments-infrastructure-2026/) - [voice agents taking card payments](/guides/ai-voice-agent-pci-payments/) - [chat agents collecting payment details](/guides/chat-agent-payments/) - [voice](/guides/voice-payments/) - [Agentic Payments Isn't Solved Yet](/blog/agentic-payments-not-solved/) - [The AI Payment Consent Problem Nobody Is Talking About](/blog/ai-agent-payment-consent/) - [Agentic Commerce: Payment Infrastructure for AI Agents](/guides/agentic-commerce/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [Agentic Payments in 2026: The Infrastructure Guide for Platforms](/blog/agentic-payments-infrastructure-2026/) - [Book a Call](/discovery/) - [AlternativeCheckout.com Alternatives for Platforms→](/alternatives/checkout-com/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) - [BlogPayment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account→](/blog/payment-links-for-checkout-com/) --- URL: https://www.shuttleglobal.com/guides/agentic-commerce/ --- # Agentic Commerce: Payment Infrastructure for AI Agents | Shuttle > AI Agents Are Starting to Transact. The Infrastructure Isn't Ready. Something shifted in early 2026. # Agentic Commerce: Payment Infrastructure for AI Agents By Shuttle Team, February 22, 2026 ## AI Agents Are Starting to Transact. The Infrastructure Isn't Ready. Something shifted in early 2026. AI agents stopped being assistants and started being participants in commerce. Not in theory. Not in research papers. In production. Razorpay connected Claude to its payment stack via Anthropic's Model Context Protocol. PolyAI's voice agents started processing insurance payments without human intervention. Google published the Agent-to-Agent protocol. Visa and Mastercard began piloting agent-initiated transaction frameworks with banks. The pattern is clear: AI agents are gaining the ability to initiate, negotiate, and complete purchases on behalf of customers. And the payment infrastructure most businesses rely on was built for a world where a human sits at a screen and clicks "Pay Now." That gap -- between what AI agents can do and what the payment stack supports -- is what agentic commerce is really about. Not the AI part. The infrastructure part. This guide covers what agentic commerce actually is, how the payment layer needs to work, where it's happening today, and what platforms need to build (or buy) to be ready. ## What Is Agentic Commerce? Agentic commerce is commerce where an AI agent handles the transaction flow -- not just the conversation. The agent understands what the customer wants, determines the right product or service, and processes the payment. The customer never sees a checkout page, never gets redirected, never fills in a form. This is different from AI-assisted commerce, where an AI helps a customer navigate to a traditional checkout. In agentic commerce, the agent is the checkout. Three characteristics define it: Intent-driven. The agent interprets what the customer needs from natural language -- spoken or typed -- rather than from a structured product catalogue or shopping cart. Autonomous execution. The agent doesn't hand off to a human or redirect to a payment page. It processes the payment within the conversation or workflow, subject to whatever authorisation rules the business has set. Multi-channel. Agentic commerce happens wherever AI agents operate: voice calls, chat interfaces, messaging apps, embedded platform workflows. It's not tied to a website or an app. The simplest way to think about it: agentic commerce removes the checkout from commerce. The agent handles the entire flow, from intent to settlement. ## How Agentic Payments Work Every agentic payment -- regardless of channel or use case -- passes through three layers. ### Layer 1: The AI Agent (Intent) The AI agent handles the customer interaction. It understands what the customer wants, confirms the details, and decides that a payment needs to happen. This is the intelligence layer -- the LLM, the voice model, the conversational AI platform. The agent knows what needs to be paid. It doesn't know how to process the payment. ### Layer 2: The Translation Layer (Payment Logic) This is the layer most people skip when they talk about agentic commerce, and it's the one that matters most. The translation layer sits between the AI agent and the payment rail. It handles: - Payment method selection -- card, bank transfer, digital wallet, depending on the customer and the channel - PSP routing -- sending the transaction to the right payment processor for that merchant, currency, or region - PCI compliance -- ensuring card data is captured and transmitted without the AI agent ever touching it - Tokenisation and authentication -- 3DS, SCA, biometric verification where required - Transaction orchestration -- retries, fallback routing, reconciliation This is the hard part. Not because the technology is exotic, but because the existing infrastructure assumes a human-driven checkout flow. The translation layer has to make an AI-initiated transaction look like a compliant, well-routed payment to the PSP on the other end. ### Layer 3: The Payment Rail (Settlement) The PSP, acquirer, and card network that actually moves the money. Stripe, Adyen, Worldpay, Checkout.com -- whatever the merchant already uses. The critical insight: most merchants and platforms don't want to change their PSP. They want their AI agents to work with the payment stack they already have. This is why the translation layer needs to be PSP-agnostic. When Razorpay connected Claude to its payment stack -- making the first live agentic payments -- this three-layer model is exactly what they built. The AI understood the intent. The MCP server translated it into payment API calls. Razorpay processed the transaction. Three layers, cleanly separated. ## Where Agentic Commerce Is Happening Agentic commerce isn't a single market. It's showing up wherever AI agents interact with customers -- and that means multiple channels, each with different infrastructure requirements. ### Voice Commerce This is where agentic payments are most mature. AI voice agents from companies like PolyAI and SoundHound are already handling customer calls in insurance, travel, hospitality, and debt collection. When those calls involve a payment -- a policy renewal, a hotel booking, a payment plan setup -- the voice agent needs to process it in real time. The infrastructure challenge is specific: voice commerce infrastructure requires DTMF capture (the customer enters their card number on the keypad), PCI-compliant audio handling, and integration with telephony platforms like Twilio and Genesys. None of this exists in a standard payment gateway. Voice is also where regulatory pressure is highest. Insurance and financial services regulators care deeply about how card data is captured over the phone. The compliance bar isn't optional -- it's the reason most voice AI companies can't just bolt on a payment API and ship. ### Chat Commerce AI chat agents -- in web chat, WhatsApp, SMS, or messaging platforms -- handle transactions differently. Instead of DTMF, they typically generate secure payment links mid-conversation. The customer clicks the link, enters their card details on a hosted payment page, and returns to the conversation. This sounds simple, but the orchestration isn't. The payment link needs to be generated dynamically, tied to the correct merchant and PSP, pre-populated with the right amount and reference, and tracked back to the conversation for reconciliation. The AI agent needs to know when the payment completes so it can continue the workflow. Chat-based agentic commerce is growing fastest in customer support (processing refunds, taking payments for service changes) and in sales workflows where an agent closes a deal conversationally. ### Embedded Agent Workflows The third channel is less visible but arguably more significant: AI agents embedded in platform workflows. An AI procurement agent that negotiates and pays for services. An AI billing agent that collects overdue invoices. An AI booking agent inside a SaaS platform that handles reservations and payments without the end customer ever leaving the platform. These embedded agents don't interact with customers directly -- they operate within business logic. But they still need payment infrastructure: PSP connections, compliance, routing, reconciliation. The requirements are the same; the interface is different. ## Why Existing Payment Infrastructure Doesn't Work The payment stack that most businesses use today was designed around a specific interaction model: a human customer, sitting at a screen, filling in a form on a checkout page. That model bakes in assumptions that don't hold in agentic commerce: Single-channel assumption. Most payment integrations are built for web or mobile. They don't support voice, chat, or programmatic agent workflows. Adding a new channel usually means a new integration, a new compliance review, and a new vendor relationship. Single-PSP assumption. A typical integration connects one application to one payment processor. But enterprise merchants often use multiple PSPs -- Adyen in Europe, Worldpay in the US, a local acquirer in specific markets. An AI agent operating across a platform's merchant base needs to route to whichever PSP each merchant uses. Most payment integrations can't do this. Human-in-the-loop assumption. PCI DSS compliance frameworks, 3DS authentication flows, and fraud screening rules all assume a human cardholder is present. When an AI agent initiates a transaction, these frameworks need to be satisfied differently. The agent can't enter a 3DS password. The agent shouldn't see card data. The compliance model has to work around the agent, not through it. Redirect-based flows. Hosted payment pages, iFrame embeds, and redirect-based checkouts all assume a browser. An AI voice agent doesn't have a browser. An embedded workflow agent doesn't have a UI. The payment infrastructure needs to support headless, API-driven transaction flows that work in any context. This is why how platforms are preparing for agentic commerce matters now, not later. The platforms that embed AI agents into their products -- CCaaS, insurance, travel, ERP -- need payment infrastructure that was designed for agent-initiated transactions. Retrofitting a checkout page integration doesn't work. ## What AI Agents Need From Payment Infrastructure If you're building a platform where AI agents will process payments -- or you're evaluating infrastructure to support it -- here's what AI agents need from payment infrastructure in concrete terms. ### PSP Optionality Enterprise merchants don't all use the same payment processor. A platform serving thousands of merchants needs to route transactions to whichever PSP each merchant uses -- Stripe for one, Adyen for another, a regional acquirer for a third. The payment layer can't be locked to a single PSP. This is the most underappreciated requirement. In a direct-to-consumer model, you pick your PSP and integrate once. In a platform model -- which is where most agentic commerce will happen -- the payment layer needs to support 20, 30, 40+ PSPs through a single integration. ### Multi-Channel Support The same payment infrastructure needs to work across voice, chat, payment links, and embedded workflows. Not four separate integrations. One layer that adapts to the channel the agent is operating in. For voice: DTMF capture, PCI-compliant audio, telephony integration. For chat: dynamic payment link generation, conversation-aware status tracking. For embedded: API-driven transaction initiation, webhook-based completion notifications. ### PCI Compliance Without Agent Access The AI agent must never see, store, or process raw card data. Full stop. The payment layer has to capture card details through a compliant mechanism -- DTMF for voice, hosted payment page for chat, tokenised vault for embedded -- and process the transaction without the agent touching sensitive data. This is non-negotiable in regulated industries. Insurance, financial services, healthcare, and debt collection all have additional data handling requirements on top of PCI DSS. The payment infrastructure needs to satisfy all of them. ### Platform Neutrality The payment layer should be invisible to the end customer and non-disruptive to the platform's existing architecture. No redirects to a third-party domain. No branding from the payment provider. No lock-in that prevents the platform from switching AI vendors, adding PSPs, or changing their workflow. The best payment infrastructure for agentic commerce is infrastructure the customer never sees and the platform barely notices -- it just works, behind the agent, across channels. ## The Platforms Building for Agentic Commerce Agentic commerce isn't being driven by payment companies. It's being driven by the platforms where AI agents are being deployed. ### CCaaS Platforms Genesys, NICE, Five9, and Talkdesk have all shipped AI Agent Studios or equivalent products in the past 12 months. These platforms handle hundreds of millions of customer interactions per year. When their AI agents can process payments mid-call or mid-chat, every one of those interactions becomes a potential transaction. The CCaaS market is arguably the fastest path to scale for agentic commerce. The agents are already deployed. The customer interactions are already happening. The missing piece is the payment layer. ### AI Voice Companies PolyAI, SoundHound, Parloa, and others are building AI voice agents for specific verticals -- hospitality, insurance, healthcare, quick-service restaurants. These agents handle inbound calls, automate customer service, and increasingly need to process payments as part of the call flow. The challenge for AI voice companies is that payment infrastructure isn't their core competency. They build exceptional conversational AI. They don't want to become PCI-compliant payment processors. They need a partner that handles the payment layer so they can focus on the voice experience. ### Vertical Software Platforms Insurance platforms (INSTANDA, Duck Creek), travel booking systems, ERP and invoicing platforms, property management systems -- all of these are integrating AI agents into their workflows. And all of them will eventually need those agents to handle payments. The vertical software market is where agentic commerce gets specific. An AI agent processing an insurance premium renewal has different compliance requirements than one booking a hotel room. The payment infrastructure needs to adapt to each vertical's regulatory and workflow requirements. This is how agentic commerce is reshaping checkout -- not through a single platform or protocol, but through hundreds of vertical and horizontal platforms adding AI agents to existing workflows and discovering they need a payment layer that doesn't exist yet. ## Who's Building the Rails The infrastructure layer for agentic commerce is being built from multiple directions simultaneously. ### Card Networks Visa has published its Intelligent Commerce framework, including pilots for agent-initiated transactions with issuing banks. Mastercard is working on similar standards. Both are focused on ensuring that agent-initiated payments meet the same authentication and fraud prevention standards as human-initiated ones. This matters because card networks set the rules. Until Visa and Mastercard define how agent-initiated transactions should be authenticated, every implementation is working around undefined standards. ### Big Tech Google's Agent-to-Agent (A2A) protocol and Universal Checkout Protocol (UCP) are attempts to standardise how AI agents discover, negotiate with, and pay each other. Stripe's Agent Toolkit and A2A Commerce Suite provide the payment APIs that AI agents can call directly. These are platform-level building blocks, not finished products. ### Crypto and Stablecoins Coinbase has launched Agentic Wallets, purpose-built for machine-to-machine payments using USDC. The logic is straightforward: stablecoins don't require card network authentication, don't need PCI compliance, and settle instantly. For autonomous agent-to-agent transactions, crypto rails may be simpler than card rails. This is early, but it's worth watching. Machine-to-machine commerce may not use traditional payment rails at all. ### PSP Integration Layers And then there's the infrastructure that connects AI agents to the PSPs merchants already use. This is the translation layer -- the part that makes agent-initiated transactions work with existing payment processors, across channels, compliantly. The networks are defining standards. Big tech is building protocols. But the practical question for most platforms is simpler: how do I let my AI agent process a payment through Adyen, or Worldpay, or Stripe, without rebuilding my payment integration from scratch? That's PSP distribution in an agentic world -- the infrastructure layer that sits between the agent and the rail, connecting each merchant to their own PSP. ## How Shuttle Fits Shuttle is a payment infrastructure company. We built a single integration layer that connects to 40+ PSPs across voice, chat, payment links, and embedded workflows. That architecture -- PSP-agnostic, multi-channel, PCI Level 1 compliant -- was originally designed for platforms that needed to offer payments without becoming payment companies. CCaaS platforms, insurance technology providers, travel companies. Businesses that wanted to embed payment processing into their products without building and maintaining 20 separate PSP integrations. It turns out that the same architecture is exactly what agentic commerce requires. When PolyAI needed to process payments through their AI voice agents, the requirements were specific: DTMF card capture over voice, PCI compliance, integration with whatever PSP the end merchant already used. Shuttle provided the payment layer. PolyAI's voice agent handles the conversation. Shuttle handles the payment. The merchant's PSP processes the transaction. Three layers, cleanly separated. That same model works for chat agents generating payment links, for embedded agents processing transactions programmatically, and for platforms that need to offer payment processing across their entire merchant base without locking into a single PSP. This is why platforms need a payment layer -- not because payments are hard to start, but because they're hard to scale across PSPs, channels, and compliance requirements. And when you add AI agents to the mix, the complexity multiplies. We're not building the AI. We're not building the protocols. We're building the infrastructure between the agent and the PSP -- the translation layer that makes agentic payments work with the payment stack businesses already have. ## What Comes Next Agentic commerce is early. The standards are being defined. The protocols are being tested. Most AI agents can't process payments today. But the trajectory is set. Every major AI platform, card network, and enterprise software company is investing in agent-initiated transactions. The question isn't whether AI agents will process payments -- it's when, and on what infrastructure. The platforms that move first will have an advantage. Not because the AI is better, but because the payment infrastructure is ready. An AI agent is only as capable as the rails it can access. If the payment layer supports one PSP, one channel, and one authentication method, the agent is constrained. If the payment layer supports 40+ PSPs, multiple channels, and compliant card capture across all of them, the agent can operate wherever the customer is. That's the bet we're making at Shuttle: that the value in agentic commerce isn't in the AI layer -- it's in the infrastructure layer that connects AI agents to the payment stack the world already uses. If you're building a platform where AI agents will process payments, talk to us. We'll show you how the infrastructure works. ## Related Reading - Agentic Payments in 2026: The Infrastructure Guide for Platforms -- how agentic commerce is reshaping checkout - The First Agentic Payments Went Live -- what happened when Razorpay connected Claude to its payment stack - The Payment Layer for AI Agents -- what AI agents need from payment infrastructure - Why Platforms Don't Want to Be Payment Companies -- why platforms need a payment layer, not a PSP - Where PSP Distribution Actually Lives -- PSP distribution in an agentic world - The Voice AI Payment Infrastructure Gap -- voice commerce infrastructure - Embedded Payments for CCaaS -- how platforms are preparing for agentic commerce - Payment Solutions for Travel Platforms -- multi-PSP, multi-currency payment infrastructure for travel booking systems - AI Voice Payments for Hotels & Travel -- agentic voice payments applied to travel and hospitality - Payment Links for Hotels & Holiday Accommodation -- how payment links work for hotel deposit and upsell collection - Agentic Payments Isn't Solved Yet -- virtual cards, consent models, and checkout surfaces -- the unsolved problems - Agent-Native Checkout: Why AI Commerce Needs New Payment APIs -- direct programmatic checkout interfaces for AI agents - The AI Payment Consent Problem Nobody Is Talking About -- why approval prompts controlled by agents are a social engineering surface ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Phygital commerce and help of agentic solutions ### Agentic Commerce: How AI Will Rewrite the Checkout ### Agentic Commerce White Paper ### Agentic Payments Isn't Solved Yet ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. ## Links - [first live agentic payments](/blog/agentic-payments-go-live/) - [voice commerce infrastructure](/blog/voice-ai-payment-infrastructure-gap/) - [DTMF capture](/guides/dtmf-payments/) - [how platforms are preparing](/guides/embedded-payments-for-ccaas/) - [what AI agents need from payment infrastructure](/guides/the-payment-layer-for-ai-agents/) - [booking a hotel room](/guides/payment-links-for-hotels/) - [how agentic commerce is reshaping checkout](/blog/agentic-payments-infrastructure-2026/) - [PSP distribution in an agentic world](/blog/where-psp-distribution-actually-lives/) - [why platforms need a payment layer](/blog/why-platforms-dont-want-to-be-payment-companies/) - [talk to us](/contact/) - [Agentic Payments in 2026: The Infrastructure Guide for Platforms](/blog/agentic-payments-infrastructure-2026/) - [The First Agentic Payments Went Live](/blog/agentic-payments-go-live/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Why Platforms Don't Want to Be Payment Companies](/blog/why-platforms-dont-want-to-be-payment-companies/) - [Where PSP Distribution Actually Lives](/blog/where-psp-distribution-actually-lives/) - [The Voice AI Payment Infrastructure Gap](/blog/voice-ai-payment-infrastructure-gap/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [Payment Solutions for Travel Platforms](/guides/travel-platform-payments/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Agentic Payments Isn't Solved Yet](/blog/agentic-payments-not-solved/) - [Agent-Native Checkout: Why AI Commerce Needs New Payment APIs](/guides/agent-native-checkout/) - [The AI Payment Consent Problem Nobody Is Talking About](/blog/ai-agent-payment-consent/) - [Book a Call](/discovery/) - [BlogPhygital commerce and help of agentic solutions→](/blog/phygital-commerce-and-help-of-agentic-solutions/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [BlogAgentic Commerce White Paper→](/blog/agentic-commerce-white-paper/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogThe First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.→](/blog/agentic-payments-go-live/) --- URL: https://www.shuttleglobal.com/guides/agentic-payments-for-platforms/ --- # Agentic Payments: What Platforms Need to Know | Shuttle > Your Platform's AI Agents Need to Take Payments Your platform runs conversations. Customer service calls. Sales chats. Support tickets. # Agentic Payments: What Platforms Need to Know By Shuttle Team, February 22, 2026 ## Your Platform's AI Agents Need to Take Payments Your platform runs conversations. Customer service calls. Sales chats. Support tickets. Booking confirmations. Renewal discussions. Increasingly, AI agents handle these conversations -- voice agents on the phone, chat agents on websites and messaging platforms. They're good at it. They qualify leads, answer questions, resolve issues, and guide customers to decisions. But when the customer says "yes" -- yes to the renewal, yes to the upgrade, yes to the purchase -- the AI agent hits a wall. It can't take a payment. The conversation that the AI handled flawlessly now needs a handoff. The customer is transferred to a human agent, redirected to a checkout page, or sent a payment link by email. The momentum breaks. The conversion drops. This is the agentic payments problem. AI agents are creating new transaction surfaces -- conversations where payment intent is expressed and should be captured -- but most platforms don't have the infrastructure to close the loop. ## What "Agentic Payments" Actually Means Strip away the buzzwords. Agentic payments means: an AI agent initiates, captures, and confirms a payment during a conversation -- without human involvement and without the customer leaving the conversational context. The AI handles the dialogue. A payment layer handles the money. Card data never touches the AI. This works across two channels: Voice: The AI voice agent prompts the customer to enter card details via phone keypad (DTMF). Tones are captured in a PCI-certified environment, stripped from the audio. Payment processed. Conversation continues. See What Are Voice Payments? for the full mechanics. Chat: The AI chat agent renders a secure payment form inline (on web) or sends a payment link (on WhatsApp, SMS, messaging platforms). Card data is captured in a PCI-certified iframe or hosted checkout. Payment processed. Chat continues. See Chat Agent Payments for details. The underlying architecture is the same for both. For a technical deep dive, see How AI Agents Process Payments: The Infrastructure Guide. ## The 2026 Landscape: Protocols Are Forming The payments industry has recognised that AI agents need payment capability. The announcements are landing fast: Stripe launched its Agentic Commerce Suite and x402 protocol -- focused on agent-to-agent commerce, where software systems pay each other for APIs and services. Google announced AP2 (Agent Payments Protocol) with 60+ partners including Adyen, Mastercard, and PayPal -- designed to let AI agents initiate payments on behalf of consumers. Worldline connected AI agents to its payment ecosystem via MCP (Model Context Protocol) servers -- bridging LLMs and payment APIs. Visa completed the first voice-enabled agentic payment transaction. These are protocol-level developments. They define how AI agents express payment intent. What they don't provide is the infrastructure that sits between the AI and the PSP -- handling PCI compliance, multi-gateway routing, DTMF capture for voice, secure forms for chat, and the operational reality of enterprise deployments where different merchants use different PSPs. That infrastructure layer is what platforms need to build or buy. And it's needed now -- before the AI agents are ready, not after. ## Why Platforms Can't Bolt This On Later Most platforms approach AI agent payments as a "Phase 2" feature: deploy the AI agent first, add payments later. This seems reasonable but creates three problems: ### 1. Architecture Constraints Compound If your AI agent is built without a payment-aware architecture, adding payments later means retrofitting PCI isolation, audio stream modification (for voice), secure form rendering (for chat), and real-time result handling into a system that wasn't designed for it. The longer you wait, the more expensive the retrofit. ### 2. The Revenue Channel Stays Closed Every conversation your AI agent handles where a customer expresses payment intent -- and can't pay -- is a missed transaction. For renewals, upgrades, sales, and collections, the AI-to-payment gap costs real revenue every day it remains open. ### 3. Enterprise Customers Are Already Asking If your platform serves insurance companies, utilities, financial services, or other transaction-heavy industries, your enterprise customers are already asking: "Can the AI take payments?" If your answer is "not yet," they're evaluating alternatives. ## What Platforms Need in Agentic Payment Infrastructure ### PCI-Compliant Capture Across Channels The payment capture environment must be PCI DSS Level 1 certified. For voice, this means DTMF capture with tone masking. For chat, it means secure iframes and hosted checkout pages. The AI agent -- and the platform's infrastructure -- must never touch card data. This isn't negotiable. If card data enters your AI model's context window, your platform's logging systems, or your customers' recordings, the PCI scope expands to cover all of those systems. The compliance cost alone can exceed $2M. ### PSP-Neutral Architecture Your platform serves multiple customers. Those customers have different PSP relationships. The insurance carrier uses Worldpay. The utility company uses Adyen. The travel operator uses a regional acquirer. Your AI agent infrastructure needs a payment layer that routes each transaction to the correct PSP based on the customer's configuration. A single integration that supports 40+ gateways. Adding a new PSP should be a configuration change, not an engineering project. This is the requirement that separates platform-grade payment infrastructure from single-merchant solutions. See Enterprise PSP Mandates for why this matters. ### Voice and Chat Through a Single Integration Your AI agents may operate on voice today and expand to chat tomorrow -- or vice versa. The payment layer should support both channels through a single integration. DTMF capture for voice. Secure forms and payment links for chat. Same tokenisation, same PSP routing, same reporting. Building separate payment integrations for each channel creates fragmentation: different PCI surfaces, different merchant configurations, different token vaults. A unified multi-channel approach avoids this. ### Real-Time Results AI conversations happen in real time. The payment layer must return results fast enough that the conversational flow isn't disrupted. If the AI agent goes silent for five seconds waiting for a payment result, the customer thinks the call dropped or the chat froze. Sub-second session creation. Transaction results within the normal processing window. Error handling that the AI can respond to conversationally: "I'm sorry, that card was declined. Would you like to try a different card?" ### Tokenisation for Repeat Transactions A card captured during an AI conversation should produce a reusable token. That token works for: future payments in the same channel, payments in a different channel, scheduled recurring payments, and delayed capture. Cross-channel tokenisation is particularly valuable for platforms. A customer pays via AI voice agent today, and the token is available if they later interact via chat, web, or payment link. One capture, every channel. ### White-Label Operation Your customers' end users should never see the payment infrastructure provider. The payment experience should feel native to the platform. For voice, the payment prompts are spoken by the AI agent -- no "you're being transferred to our payment partner." For chat, the secure form carries the platform's branding. ## Platform Types and Agentic Payment Use Cases ### CCaaS / Contact Centre Platforms The opportunity: Your platform already handles voice conversations. AI agents are automating routine calls. Adding payment capture turns those AI agents from cost centres into revenue channels. Use cases: Renewal collection, payment arrangement, claims excess, subscription upgrades -- all handled within the AI conversation. What your customers ask: "Can the AI take a payment during the call?" See How CCaaS Platforms Add Payment Capabilities for the platform perspective. ### AI Voice Agent Platforms The opportunity: Your AI agents are production-ready, handling millions of conversations. Payment capture is the feature that turns conversational AI into transactional AI. Use cases: End-to-end autonomous sales, renewal, and collections calls with payment at the point of agreement. The proof point: PolyAI processes payments across regulated industries with a 75% completion rate and zero handoffs. ### Insurance and Financial Services Platforms The opportunity: Your platform manages policy administration, claims, or financial workflows. Payments are a required step in many of these workflows, and the phone is still the primary customer channel. Use cases: Premium collection, claims excess, instalment plans, mid-term adjustments. See AI Voice Payments for Insurance and Payments for Insurance Platforms. ### E-Commerce and SaaS Platforms The opportunity: AI chat agents on your platform handle pre-sale questions, support, and account management. Payment capture inline turns support interactions into revenue opportunities. Use cases: Upsells during support, subscription renewals, quote-to-purchase in chat. ### BPOs and Collections The opportunity: Your agents -- human and AI -- negotiate payment arrangements daily. Capturing payment at the moment of agreement (not after) maximises recovery rates. Use cases: Outbound collections, payment plan setup and auto-collection, failed payment recovery. See AI Voice Payments for Debt Collection. ## Build vs. Buy for Agentic Payments The build-vs-buy question for agentic payment infrastructure is even more weighted toward buy than for standard payment infrastructure. Building in-house requires: - PCI DSS Level 1 certification ($2M+) - DTMF capture engineering at the telephony layer (specialised skill set) - Secure iframe / hosted form infrastructure for chat - Multi-PSP integration (each gateway is months of work) - Ongoing compliance maintenance ($500K+/year) Using a payment layer provides: - PCI DSS Level 1 included - DTMF capture and tone masking pre-built - Chat payment forms and hosted checkout ready - 40+ PSPs through a single integration - Compliance certifications maintained by the provider - How Voice AI Ordering Platforms Handle Payments -- AI agents in food ordering and the payment capture gap - Payment Infrastructure for Food Ordering Platforms -- multi-PSP payment infrastructure for food ordering AI platforms The total cost of building agentic payment infrastructure in-house typically exceeds $3M in the first year and $1M+ annually thereafter. For platforms whose core product is conversations -- not payments -- this is engineering capacity better spent elsewhere. For the full cost analysis, see Build vs Buy Payment Infrastructure. ## Getting Started Agentic payments isn't a future initiative. AI agents are handling production conversations today, and the payment infrastructure gap is costing platforms revenue with every call and chat that ends without a transaction. The sequence: - Evaluate your AI agent conversations. How many involve payment intent? Renewals, sales, upgrades, collections -- each is a transaction opportunity. - Assess your PSP landscape. Do your customers use different PSPs? If yes, you need PSP-neutral infrastructure from day one. - Choose voice, chat, or both. Voice requires DTMF capture. Chat requires secure forms. Both should run through a single payment layer. - Integrate once. A single API integration to a payment layer that supports all channels and all PSPs. Weeks of work, not months. - Go live. AI agents with payment capability. Revenue from conversations that previously ended with "I'll send you a link." Most CCaaS platforms -- Talkdesk, Genesys, Five9, NICE CXone, RingCentral, Amazon Connect, Avaya, Cisco -- share the same core gap: they were built for conversation management, not card capture. For the platform-by-platform breakdown of how merchants and implementation partners are closing that gap, see the contact centre payments guide. See Payments for CCaaS Implementation Partners for the SI-led delivery model. ## FAQ What's the difference between agentic payments and conversational commerce? Conversational commerce is the broader concept -- commerce that happens within conversations. Agentic payments is the specific mechanism: an AI agent initiating and capturing a payment autonomously during a conversation. Agentic payments is how conversational commerce actually works at the infrastructure level. Do I need different infrastructure for voice agents and chat agents? The capture mechanism differs (DTMF for voice, secure forms for chat), but the underlying payment layer should be the same. One integration covers both channels with shared PSP routing, tokenisation, and reporting. How does this work with my existing payment infrastructure? A payment layer sits alongside your existing payment stack. If you already have web checkout via Stripe, adding agentic payments doesn't require replacing Stripe. The payment layer handles the voice and chat capture, routing to whichever PSP each transaction requires -- including Stripe. What if my AI agent platform already has a basic payment integration? Basic integrations (e.g., sending a Stripe payment link) work for simple cases but break at enterprise scale. Enterprise customers mandate their PSP. Voice agents need DTMF capture, not payment links. Chat agents need inline secure forms. If your basic integration doesn't support multi-PSP, multi-channel, and PCI-compliant capture, it's a ceiling on your growth. How quickly can we add payment capability to our AI agents? Weeks. The payment layer provides pre-built DTMF capture, hosted forms, payment link generation, and PSP routing. Your integration work is connecting the AI agent's "capture payment" trigger to the payment layer's API and handling the result. Give your AI agents the ability to close the deal. Shuttle connects AI voice and chat agents to 40+ payment gateways -- with PCI DSS Level 1 compliance, DTMF capture, secure forms, tokenisation, and multi-channel support. One integration. Every channel. Every PSP. Book a Call | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Agentic Payments Isn't Solved Yet ### The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### The Future of Platform Payments: From Gateways to Agentic Commerce ## Links - [DTMF](/guides/dtmf-payments/) - [What Are Voice Payments?](/guides/voice-payments) - [Chat Agent Payments](/guides/chat-agent-payments) - [How AI Agents Process Payments: The Infrastructure Guide](/guides/ai-agent-payments) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates) - [unified multi-channel approach](/guides/multi-channel-payments) - [How CCaaS Platforms Add Payment Capabilities](/guides/how-ccaas-platforms-add-payments) - [75% completion rate and zero handoffs](/guides/ai-voice-agents-payments) - [AI Voice Payments for Insurance](/guides/ai-voice-payments-insurance) - [Payments for Insurance Platforms](/guides/payments-for-insurance-platforms) - [AI Voice Payments for Debt Collection](/guides/ai-voice-payments-debt-collection) - [How Voice AI Ordering Platforms Handle Payments](/guides/voice-ai-ordering-payments/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [Build vs Buy Payment Infrastructure](/guides/build-vs-buy-payment-infrastructure) - [contact centre payments guide](/guides/contact-centre-payments/) - [Payments for CCaaS Implementation Partners](/guides/payments-for-ccaas-implementation-partners/) - [Book a Call](/contact) - [See How It Works](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogThe First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.→](/blog/agentic-payments-go-live/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogThe Future of Platform Payments: From Gateways to Agentic Commerce→](/blog/the-future-of-payments/) --- URL: https://www.shuttleglobal.com/guides/ai-agent-payments/ --- # How AI Agents Process Payments: The Infrastructure Guide | Shuttle > Payments Meet AI Agents AI agents are no longer just answering questions. They're closing sales, collecting debts, processing renewals, and taking... # How AI Agents Process Payments: The Infrastructure Guide By Shuttle Team, December 29, 2025 ## Payments Meet AI Agents AI agents are no longer just answering questions. They're closing sales, collecting debts, processing renewals, and taking payments -- all without a human in the loop. This shift is happening across voice and chat simultaneously. AI voice agents handle phone conversations end-to-end. Chat agents guide customers through purchases on websites and messaging platforms. In both cases, the moment the customer is ready to pay, the agent needs a way to securely capture payment details and process the transaction. That's the infrastructure problem. The AI handles the conversation. Something else has to handle the money. ## The Infrastructure Stack An AI agent that processes payments needs four things working together: ### 1. Conversational Layer The AI model that handles the dialogue -- understanding intent, guiding the customer, and recognising when a payment should happen. This is the agent itself (built on large language models, purpose-built voice AI, or a combination). The critical rule: The conversational layer must never see, process, or store card data. PCI compliance requires a clean separation between the AI and the payment capture environment. ### 2. Payment Trigger The mechanism that transitions from conversation to payment capture. When the AI determines the customer is ready to pay, it triggers a handoff to the payment layer. This isn't a "transfer" in the traditional sense -- the conversation continues. The payment capture happens in parallel, within a PCI-certified environment. In voice: the AI triggers a DTMF capture sequence or sends an SMS payment link. In chat: the AI presents a secure payment form or redirects to a hosted checkout. ### 3. PCI-Compliant Capture Environment A certified environment where card data is captured, tokenised, and processed. This environment sits between the AI agent and the payment gateway. It handles: - Card data entry (DTMF tones, secure form, or speech-to-text within a PCI boundary) - Tokenisation (so the card can be reused without re-entering details) - Gateway routing (sending the transaction to the right PSP) - Response handling (confirming success or failure back to the AI) The AI agent communicates with this environment via API -- it sends a "capture payment" request and receives a result. It never touches the card data itself. ### 4. Payment Gateway(s) The PSP that actually processes the transaction -- Stripe, Worldpay, Adyen, Checkout.com, or whichever gateway the business uses. In enterprise deployments, this often means multiple gateways, with routing based on geography, transaction type, or merchant preference. ## How It Works in Practice Here's the flow for an AI voice agent processing a payment: Step 1: Customer is on a call with an AI voice agent. They've selected a product or confirmed an amount to pay. Step 2: The AI agent says: "I can take your payment now. Please enter your card number using your phone keypad." The agent triggers the payment layer. Step 3: The customer enters card digits via DTMF. The tones are captured within the PCI environment -- stripped from the audio stream so they never reach the AI model or any recording system. Step 4: The payment layer validates the card (BIN check, Luhn validation), routes the transaction to the appropriate gateway, and processes it. Step 5: The payment layer returns a result to the AI agent: approved, declined, or requiring additional action (like 3D Secure). Step 6: The AI agent confirms the result in natural language: "Your payment of $247.50 has been processed. You'll receive a confirmation by email." Total time: seconds. Human involvement: zero. For chat agents, the flow is similar but the capture mechanism differs -- a secure payment form is rendered inline or the customer is sent to a hosted checkout page, with the result returned to the chat agent for confirmation. ## The PCI Problem (and Why It's Non-Negotiable) Every AI agent payment implementation must solve the same fundamental problem: keeping card data away from the AI. Large language models process tokens. If card data enters the model's context window -- even transiently -- you've created a PCI compliance issue. The card number has been "processed" by a system that isn't PCI certified, stored in a context that may be logged, and potentially exposed through model outputs. The architecture must enforce a hard boundary: - The AI agent orchestrates the payment flow (decides when, how much, which gateway) - The PCI-compliant payment layer handles the sensitive data (captures, tokenises, routes) - The two communicate via API -- the agent sends instructions, the payment layer returns results - Card data never crosses the boundary This isn't optional. It's the architectural foundation that makes the entire system work. Any voice payment, chat payment, or autonomous payment flow that allows card data to reach the AI model is fundamentally broken from a compliance perspective. ## What's Happening in 2026 The infrastructure for AI agent payments is being built right now -- by some of the biggest names in payments: Stripe launched its Agentic Commerce Suite and x402 protocol, enabling AI agents to make payments for APIs, data, and digital services. Their focus is agent-to-agent commerce -- software systems paying each other. Google announced AP2 (Agent Payments Protocol) with over 60 partners including Adyen, American Express, Mastercard, and PayPal. AP2 is designed to let AI agents initiate payments on behalf of consumers. Worldline connected AI agents to its global payment ecosystem via MCP (Model Context Protocol) servers -- creating a bridge between LLMs and payment APIs. Visa completed the first voice-enabled agentic payment transaction, with cardholders using an AI agent to pay real estate service charges. The common thread: these are protocol-level and API-level developments. They define how AI agents request, authorise, and confirm payments. What they don't provide is the infrastructure layer that sits between the AI and the PSP -- handling PCI compliance, multi-gateway routing, and the actual capture of payment credentials. That infrastructure layer is where the real implementation work happens. ## Voice vs. Chat: Different Channels, Same Architecture The underlying architecture is the same whether the AI agent operates over voice or chat. The capture mechanism changes, but the pattern doesn't: Voice Agent | Chat Agent Payment trigger | AI triggers DTMF capture or sends SMS link | AI renders secure form or sends checkout link Card capture | Keypad tones within PCI environment | Secure hosted form within PCI environment Agent interaction with card data | None -- tones stripped from audio | None -- form is sandboxed Result returned to AI | Transaction status via API | Transaction status via API Conversation continues | Yes -- voice stays connected | Yes -- chat continues in same thread The principle is identical: the AI handles the conversation, the payment layer handles the money, and card data never crosses the boundary. ## Multi-PSP: Why AI Agents Need Gateway Flexibility AI agents are deployed by platforms, contact centres, and software companies -- businesses that often serve multiple merchants, operate across regions, or have enterprise customers with specific PSP requirements. A single-gateway integration creates immediate limitations: - Merchant A uses Stripe, Merchant B uses Worldpay -- the AI can't serve both - US transactions need one acquirer, UK transactions need another -- regional routing fails - An enterprise customer mandates Adyen -- you lose the deal The AI agent doesn't care which gateway processes the payment. It cares that the payment succeeds. A PSP-neutral payment layer abstracts the gateway choice away from the agent, routing transactions based on rules the business defines. This is especially relevant for platforms embedding AI agents for their customers. Each customer may have different PSP relationships, and the platform needs a payment layer that supports all of them through a single integration. ## What to Look For in AI Payment Infrastructure If you're building or deploying AI agents that need to process payments, evaluate the infrastructure layer on: ### PCI Certification The payment capture environment must be PCI DSS Level 1 certified. This is the highest level. No exceptions for "AI-first" or "low-volume" deployments. ### Separation of Concerns Card data must never enter the AI model's environment. The architecture must enforce this at the infrastructure level, not rely on application-level controls. ### Gateway Coverage How many PSPs does the layer support? Can you add gateways without re-engineering the agent's payment flow? Can merchants bring their own PSP? ### Channel Support Does it work for voice (DTMF, speech-to-text) and chat (hosted forms, inline capture) or only one? ### Tokenisation Can you tokenise a card during an AI conversation and reuse it later -- across channels, for recurring payments, or for delayed capture? ### Latency AI conversations happen in real time. Payment processing that adds seconds of delay breaks the conversational flow. The payment layer needs to be fast enough that the customer doesn't notice the transition. For contact-centre-specific AI agent deployments -- where the AI sits inside Talkdesk Autopilot, Genesys AI Experience, Five9 IVA, or similar -- see the contact centre payments guide for the platform-specific implementation patterns. ## FAQ Can AI agents legally process payments? Yes. The regulatory question isn't whether an AI can initiate a payment -- it's whether card data is handled in a PCI-compliant way. If the AI never touches card data and a certified payment layer handles capture and processing, the transaction is compliant. What about fraud and authorisation controls? AI agents should operate with defined limits -- maximum transaction amounts, velocity controls, and the ability to escalate to a human for unusual transactions. The payment layer should support pre-authorisation and capture-later flows for high-value transactions. Do I need different infrastructure for voice agents and chat agents? The capture mechanism differs (DTMF vs. hosted form), but the underlying payment layer is the same. A good infrastructure layer supports both channels through a single integration. What happens if the payment fails mid-conversation? The payment layer returns a decline or error status to the AI agent, which handles it conversationally -- offering retry, alternative payment methods, or escalation to a human agent. Is this actually in production, or still theoretical? It's in production. AI voice agents are processing payments today in regulated industries including insurance, utilities, and financial services. PolyAI's agents achieve a 75% voice payment completion rate with zero human handoffs. Building AI agents that need to take payments? See how Shuttle connects AI voice and chat agents to 16+ payment gateways -- with PCI DSS Level 1 compliance and zero card data in your environment. [Talk to Us] | [See Voice Checkout] ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Agentic Payments Isn't Solved Yet ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. ## Links - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [contact centre payments guide](/guides/contact-centre-payments/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogThe First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.→](/blog/agentic-payments-go-live/) --- URL: https://www.shuttleglobal.com/guides/ai-payment-security/ --- # AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI | Shuttle > The Security Question Nobody's Asking Loudly Enough AI agents are processing real payments. Voice agents take card details over the phone. # AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI By Shuttle Team, February 20, 2026 ## The Security Question Nobody's Asking Loudly Enough AI agents are processing real payments. Voice agents take card details over the phone. Chat agents send payment links mid-conversation. Agentic systems initiate transactions on behalf of customers. And the security conversation hasn't caught up. Most of the "agentic payments" content in 2026 focuses on protocols, commerce frameworks, and revenue opportunities. Almost none of it addresses the fundamental question: how do you let an AI agent process a payment without exposing card data to the AI model? This isn't theoretical. If an AI voice agent hears a customer read their card number, that audio is being processed somewhere. If an AI chat agent receives a card number in a message, that text is being handled by an LLM. If the architecture doesn't explicitly prevent it, card data will flow through systems that aren't PCI-certified -- and probably into training data. The payment industry spent decades building PCI DSS to protect card data from humans. Now it needs to protect card data from AI. ## The Core Principle: AI Agents Must Never See Card Data This is non-negotiable. The AI agent -- the LLM, the conversation engine, the decision-making model -- must never: - Hear card numbers (in audio form) - Read card numbers (in text form) - Store card data (in any form) - Process card data (through any model) - Log card data (in conversation transcripts) The AI agent decides when to initiate a payment and what to say about it. The payment infrastructure handles the how -- card capture, tokenisation, PSP routing, and transaction processing. These two systems must be architecturally separated with no card data crossing the boundary. ## Three Architectures for AI Agent Payments ### 1. DTMF Capture (Voice Agents) How it works: The AI voice agent's audio processing is paused during card capture. The customer enters card digits via their phone's keypad (DTMF tones). These tones are captured directly by the PCI-certified payment layer -- the audio never reaches the AI model. The agent says: "Please enter your card number using your keypad." The voice channel switches to DTMF mode. Card digits are captured by the PCI-certified payment layer (NOT the AI agent). Payment is processed. The agent continues: "Thank you, your payment has been confirmed." Why it works: DTMF capture is an established PCI-compliant pattern used in IVR systems for decades. The innovation is integrating it seamlessly into an AI voice agent conversation so the customer experience feels natural, not like a transition to a clunky IVR. PCI scope: The AI voice agent is out of PCI scope. The payment layer (which handles DTMF capture) is in PCI scope and holds PCI DSS Level 1 certification. ### 2. Payment Links (Chat Agents) How it works: The AI chat agent determines payment is needed. It generates a payment link via the payment layer API (passing amount, merchant ID, and reference -- no card data). The link is sent to the customer within the chat. The customer clicks the link and pays on a PCI-certified hosted checkout page. A payment confirmation webhook notifies the agent. The agent says: "Payment received. Your booking is confirmed." Why it works: Payment links are the cleanest separation possible. The chat platform, the LLM, and the conversation logs never contain card data. The only data the agent sees is a payment confirmation (paid/not paid, amount, reference). PCI scope: The AI chat agent and the entire chat platform are out of PCI scope. The hosted checkout page (payment layer) is in PCI scope. ### 3. Tokenised Card-on-File (Automated Agents) How it works: The customer has previously stored a card via a PCI-certified flow. The AI agent sends a payment request to the payment layer with a customer token (NOT card data). The payment layer uses the stored token to process with the PSP. Confirmation is returned to the agent. Why it works: Tokenisation is a foundational PCI concept. The AI agent has the same access as any other system that processes token-based payments -- it can initiate a charge but cannot access the underlying card data. PCI scope: The AI agent is out of PCI scope (it only handles tokens). The tokenisation vault and payment processing layer are in PCI scope. ## What Could Go Wrong (and How to Prevent It) ### Risk 1: Card Data in Conversation Transcripts The problem: A customer reads their card number aloud to a voice agent, or types it into a chat. If the conversation is transcribed and stored, card data ends up in logs that aren't PCI-certified. Prevention: - Voice agents: DTMF mode suppresses audio capture during card entry. The AI's speech-to-text engine never receives the card number audio. - Chat agents: Payment links eliminate this risk entirely -- customers never type card data into the chat. - If a customer volunteers card data in conversation (unprompted), the system must detect and redact it from transcripts. Pattern matching for 13-19 digit sequences is the minimum. ### Risk 2: Card Data in LLM Training Data The problem: If card data flows through an LLM's inference pipeline, it could theoretically appear in model outputs or influence training (for fine-tuned models). - Architectural separation: card data never reaches the LLM. DTMF capture and payment links keep card data in the payment layer. - If using third-party LLMs (OpenAI, Anthropic, Google), ensure card data never appears in prompts or conversation context. This is enforced by the architecture, not by policy. ### Risk 3: The AI Agent Asks for Card Data The problem: An improperly configured AI agent might ask the customer to read their card number aloud (voice) or type it into the chat -- creating a card data exposure even with proper payment infrastructure. - Agent conversation design must explicitly prevent card data solicitation in text or voice channels where the agent processes the data. - DTMF capture requires the agent to redirect to keypad entry -- the agent should never say "please read me your card number." - Chat agents should always send a payment link -- never ask for card details in the chat. ### Risk 4: Spoofing and Social Engineering The problem: A malicious actor could attempt to trick an AI agent into revealing payment information, processing unauthorised transactions, or bypassing payment controls. - AI agents should have strict guardrails on payment actions: maximum transaction amounts, customer authentication requirements, and refund limits. - Payment actions should require customer verification (OTP, biometric, or SCA challenge) -- initiated by the payment layer, not the AI agent. - Transaction anomaly detection at the payment layer level catches patterns the AI agent might not recognise. ## PCI DSS and AI Agents: Where We Are ### What PCI DSS 4.0 Says PCI DSS 4.0 (effective March 2025) doesn't specifically address AI agents. The standard focuses on protecting cardholder data wherever it's stored, processed, or transmitted -- regardless of the technology. The principles apply directly: - Requirement 3: Protect stored account data. AI agents must not store card data. - Requirement 4: Protect cardholder data with strong cryptography during transmission. Card data flowing to the payment layer must be encrypted. - Requirement 7: Restrict access to system components and cardholder data by business need to know. AI agents have no business need to access card data. - Requirement 10: Log and monitor all access to system components and cardholder data. Payment transactions initiated by AI agents must be auditable. ### What's Coming The PCI Security Standards Council hasn't published AI-specific guidance yet. Industry expectations: - Guidance on AI agent payment architectures (likely validating the separation model described here) - Requirements for AI conversation transcript handling (redaction, retention) - Standards for AI-initiated transaction authentication - Clarification on PCI scope boundaries between AI platforms and payment infrastructure Platforms that architect the separation now will be ahead when formal guidance arrives. ## Audit Trail Requirements AI-initiated payments need stronger audit trails than human-initiated ones because: - There's no human judgment to fall back on if something goes wrong - Dispute resolution needs to prove the customer consented - Regulators will scrutinise AI-processed transactions more closely Minimum audit trail for AI agent payments: - Conversation transcript (with card data redacted) - Customer consent record (verbal for voice, click-through for links) - Payment request timestamp and parameters - PSP response (approval/decline code, reference) - Agent decision logic (why the payment was initiated) - SCA/authentication result (if applicable) ## FAQ Can we use our own LLM and still be PCI compliant? Yes -- as long as card data never reaches the LLM. The LLM handles conversation logic. The payment layer handles card data. If these are architecturally separated (DTMF for voice, payment links for chat, tokens for stored cards), the LLM and its hosting environment are out of PCI scope. What about voice biometrics for payment authentication? Voice biometrics can be used as one factor in customer authentication -- but it's not sufficient alone for payment authorisation under SCA requirements. Combine with a second factor (OTP, device confirmation) where SCA applies. Do we need a separate PCI certification for AI agent payments? If your AI agent never touches card data (and the architecture enforces this), the agent itself doesn't need PCI certification. The payment layer that handles card data does. This is the same model as any application that uses a PCI-certified payment provider -- the application is out of scope if card data doesn't flow through it. What if the customer insists on reading their card number to the voice agent? The agent should redirect: "For your security, I'll ask you to enter your card details using your phone's keypad." If the customer speaks card details despite this, the system must: (1) not process the spoken data as payment input, (2) redact the card number from any transcript, and (3) still route to DTMF capture for the actual payment. ## Related Reading - Agentic Payments in 2026: The Infrastructure Guide -- the broader infrastructure landscape for AI agent payments - How to Get Payments Off Your Product Roadmap -- why building PCI-compliant payment infrastructure in-house is a roadmap trap - Shuttle vs Building In-House -- the real cost of building payment infrastructure yourself - What is PCI DSS? | What is PCI DSS Level 1? | What is PCI Scope? | What is DTMF? | What is Tokenisation? | What is SCA? - The AI Payment Consent Problem Nobody Is Talking About -- why approval prompts controlled by agents are a social engineering surface - Agentic Payments Isn't Solved Yet -- virtual cards, consent models, and checkout surfaces -- the unsolved problems Building AI agents that handle payments? Shuttle's payment layer is PCI DSS Level 1 certified and purpose-built for AI agent payment flows -- DTMF voice capture, payment links, and tokenised payments. Your AI agent stays out of PCI scope. Every transaction is secure and auditable. See the Architecture | Talk to Our Team ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ## Links - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Agentic Payments in 2026: The Infrastructure Guide](/blog/agentic-payments-infrastructure-2026/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/glossary/pci-dss-level-1/) - [PCI Scope](/glossary/pci-scope/) - [DTMF](/glossary/dtmf/) - [Tokenisation](/glossary/tokenization/) - [SCA](/glossary/sca/) - [The AI Payment Consent Problem Nobody Is Talking About](/blog/ai-agent-payment-consent/) - [Agentic Payments Isn't Solved Yet](/blog/agentic-payments-not-solved/) - [See the Architecture](/platforms/) - [Talk to Our Team](/discovery/) - [Book a Call](/discovery/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) --- URL: https://www.shuttleglobal.com/guides/ai-voice-agent-pci-payments/ --- # How AI Voice Agents Take PCI-Compliant Payments | Shuttle > Your AI voice agent is impressive. It handles intent recognition, sentiment analysis, conversational routing, customer lookup against your CRM,... # How AI Voice Agents Take PCI-Compliant Payments By Shuttle Team, February 19, 2026 Your AI voice agent is impressive. It handles intent recognition, sentiment analysis, conversational routing, customer lookup against your CRM, scheduling, and escalation -- all in real time, all without a human agent. Then the customer says: "Yes, I'd like to pay now." And your stack hits a wall. Taking a card payment during a live AI voice call isn't a product problem or a UX problem. It's an infrastructure and compliance problem. This guide explains exactly what the architecture looks like, why the naive approaches don't work, and what a correct integration actually involves. ## The Problem: AI Can Do Everything Except Take a Payment The moment a customer agrees to pay, your voice agent needs to capture a 16-digit card number, a 4-digit expiry, and a 3-digit CVV. That's sensitive cardholder data under PCI DSS. And PCI DSS has a very clear rule: any system that stores, processes, or transmits cardholder data is in scope for full compliance. Here's what that means in practice for a CCaaS platform: If card data enters your AI model -- even as audio that gets transcribed -- your entire voice infrastructure is in PCI scope. That includes your ASR pipeline, your LLM inference layer, your call recording system, your data lake, your transcription storage, your model training pipelines, and every network segment they touch. PCI DSS Level 1 certification for that kind of footprint costs roughly $500,000 in the first year. Ongoing annual costs run $200,000 or more, plus quarterly vulnerability scans, annual penetration testing, and a Qualified Security Assessor (QSA) who will not be cheap or fast. That's the compliance burden of getting this wrong. Most CCaaS companies -- even well-funded ones -- cannot absorb it, nor should they. The goal is to keep cardholder data out of your platform entirely. ## The Architecture: Secure Payment Handoff The correct architecture is a clean handoff: your AI agent orchestrates the conversation, a separate payment layer handles all card data capture, and your platform never sees, stores, or processes cardholder data. Here's the step-by-step flow: - Intent recognition -- The AI agent identifies payment intent from the customer's speech ("I'd like to pay my bill" / "Can I settle this now?"). - Amount confirmation -- The agent confirms the payment amount with the customer and explains that they'll be prompted to enter their card details via their keypad. - Session initiation -- Your platform makes an API call to the payment layer: `POST /payment-session` with the amount, currency, and the end-customer's PSP configuration. The payment layer returns a session token and signals that it's ready to capture. - Secure capture takes over at the point of payment -- When it's time to pay, a secure, PCI DSS Level 1 card capture takes over the payment step. Today this runs over Twilio Pay, with the payment layer as the certified capture and gateway connector, so the card is captured inside the certified environment rather than inside your platform. - Card data entry -- The payment layer plays a secure prompt to the caller ("Please enter your 16-digit card number followed by the hash key"). The caller enters digits via their phone keypad. - Card captured in isolation -- The card is captured exclusively inside the payment layer's certified environment. The digits do not enter your CCaaS platform. They do not reach your AI model. They do not appear in call recordings. - Tokenisation and authorisation -- The payment layer tokenises the card data and sends it to the customer's PSP for authorisation. This entire operation happens within the payment layer's PCI DSS Level 1 certified environment. - Result returned -- The PSP returns an auth result to the payment layer. The payment layer fires a webhook to your platform: `payment_completed` with success/failure, a transaction ID, and a masked card reference (e.g., `**4242`). No card data. - Your application continues -- Your platform reads the result and your AI agent continues, for example: "Your payment of £150 has been processed. Your reference number is TXN-9821." (See the note below on returning the caller to the same agent.) The entire card capture happens in a certified environment your platform never touches. Your PCI scope is limited to the API calls between your platform and the payment layer, which is a dramatically smaller, more defensible surface area. ### What's live today (the honest version) The secure card capture at the point of payment is available now, and today it runs on Twilio Pay (so using it for voice means being a Twilio customer). Returning the caller to the same AI agent afterwards works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes the conversation with context. What is not yet turnkey: the payment layer being present for the entire call. Today the secure capture is scoped to the point of payment, not the whole conversation. Shuttle works with Twilio today, and any carrier coming soon. Where building the return leg isn't viable for your flow, payment links sent mid-call by SMS are the turnkey alternative. ## DTMF vs Speech Recognition for Card Capture When engineers first think about AI voice agent payments, the obvious question is: "Why can't the AI just listen to the customer read out their card number?" It understands speech. It can transcribe numbers. It can, technically. But compliance architecture doesn't care what the AI can do -- it cares what data flows where. If a customer reads their card number aloud and your ASR pipeline transcribes it, that audio and that transcript both contain cardholder data. Your entire ASR infrastructure is now in PCI scope. Your call recording system is in scope. Your transcription storage is in scope. Your model training data -- if you're using call audio for fine-tuning -- is in scope. DTMF (Dual-Tone Multi-Frequency) keypad entry solves this at the architecture level: - Captured inside the certified environment: the card is captured by the payment layer at the point of payment, so the decodable digits never enter your call audio, your platform, or your recordings. - No card data in recordings: because the card is captured inside the payment layer rather than your stack, your call recordings contain no decodable card data for the card-entry window. - No transcription: There's no speech-to-text step for card data. The payment layer decodes the tones directly. No LLM, no ASR, no transcript. - Caller familiarity: Customers are used to entering card details via keypad. It's the standard IVR flow they've been doing for 20 years. There's no UX friction. Speech capture of card numbers is a compliance anti-pattern. Keypad capture inside a certified environment is the industry-standard, compliance-correct approach. Any architecture that routes spoken card numbers through your AI pipeline is building a very expensive PCI scope problem. ## PCI Scope: What Changes and What Doesn't This is worth being precise about, because "PCI compliance" gets hand-waved in a lot of vendor conversations. Without a payment handoff architecture: If your agents -- human or AI -- hear or process card numbers, PCI DSS scope expands to include: - All call recording infrastructure - All transcription services and storage - All ASR pipelines - All AI model inference infrastructure - All data warehouses or lakes that receive call data - All networks connecting these systems - All personnel with access to those systems That's essentially your entire platform. PCI DSS Level 1 certification for a footprint that size is not a checkbox exercise -- it's a multi-year program with dedicated compliance staff. With a payment handoff architecture: Your PCI scope shrinks to: - The API connection between your platform and the payment layer (TLS in transit -- table stakes) - The payment layer itself (which carries its own PCI DSS Level 1 certification) You don't handle card data. You don't store it. You don't transmit it. You send a payment session request and receive a success/failure webhook. Your QSA scope is minimal. Your compliance burden is minimal. The payment layer -- Shuttle, in this context -- carries the PCI DSS Level 1 certification. That's the certification that covers the card capture, tokenisation, vault, and PSP routing. You inherit the compliance posture without the certification cost. For a detailed walkthrough of how this works specifically on Twilio infrastructure, see Twilio PCI Compliance: How to Take Payments Without Handling Card Data. ## Multi-PSP: Why Your Customers' Gateway Matters Here's a practical problem that most "just add Stripe" thinking ignores: your enterprise CCaaS customers already have PSP relationships. An insurance company processing 50,000 premium collections a month has a negotiated rate with their acquirer. A utility company has a direct integration with a specific gateway. A debt collection agency is contractually required to process through a particular payment provider. None of them want to move off their existing PSP to use whatever you've embedded. A correct payment layer needs to be PSP-agnostic. When a payment session is initiated for a given end-customer, the payment layer routes to that customer's configured PSP -- not to a single hardcoded gateway. This is why "add Stripe" doesn't solve the problem for CCaaS operators. Stripe is a single gateway. Your enterprise customers need their own gateway. The payment infrastructure needs to support multi-tenancy at the PSP level: each customer of your platform routes through their own PSP, using their own merchant credentials, with their own settlement. Shuttle supports 40+ PSPs. When you initiate a payment session, you pass the end-customer's PSP configuration and the payment layer handles the routing, so you never need to build a new PSP integration for a new customer. (One caveat: a few gateways, such as Braintree, won't allow raw card data over voice, so they work for payment links but not for keypad capture.) If you're building on Twilio, Pay Connectors make this simpler: a single Marketplace install connects Twilio to a supported gateway. ## Build vs Buy Let's be direct about what building this in-house actually requires: - DTMF capture with audio stream isolation (non-trivial telephony engineering) - PCI DSS Level 1 certification: ~$500K in year one, $200K+ annually thereafter - Tokenisation vault design, implementation, and auditing - PSP integrations: each one is 2-4 weeks of engineering, plus ongoing maintenance as PSP APIs change - Ongoing quarterly vulnerability scans, annual penetration tests, key rotation schedules - A dedicated compliance function or expensive external QSA relationship - Timeline to first production payment: 12-18 months minimum Buy (integrate a payment layer): - A single integration against the payment layer's capture, IVR, and APIs, where you build your own agent-side interface (effort depends on your stack) - PCI compliance carried by the payment layer, so you stay out of scope - 40+ PSP integrations available without building them yourself (a few gateways, such as Braintree, work for links but not voice) - Compliance, auditing, pen testing, key rotation: the payment layer's problem - Far faster than the build path, though the exact timeline depends on your platform, so ask for a scoped estimate rather than a headline number For a CCaaS company under 500 people, and most CCaaS companies are, this calculus is not close. The build path is a multi-year distraction from your core product. The buy path lets you ship a payments feature, close enterprise deals that require payment capabilities, and keep your engineering team focused on the AI and conversation capabilities that actually differentiate your product. ## What the Integration Actually Looks Like Stripped to its essentials, the integration is three API calls and a webhook: - POST /payment-session Body: amount, currency, merchant_id, psp_config Response: session_id, dtmf_ready: true - [Secure card capture handled by the payment layer at the point of payment] - Webhook received: POST /your-webhook-endpoint Body: event: "payment_completed", session_id: "sess_abc123", status: "success", transaction_id: "txn_xyz789", masked_card: "**4242", amount: 15000, currency: "GBP" - [Your application reads the status from the webhook and continues] No card data flows through your system at any point. The session ID ties the payment to the conversation. The webhook fires within seconds of the PSP authorisation. Your application reads the status and continues. (To return the caller to the same AI agent afterwards, program the return route in your Twilio flow and pass the conversation ID.) The same secure capture and APIs serve both your AI and human-agent channels. Same API, same PCI boundary. You build your own agent-side interface once and it serves both. ## Summary AI voice agents are capable of taking payments, but the architecture has to be right, and the honest current state matters. The LLM cannot hear or process card data. Speech recognition of card numbers creates a compliance catastrophe. Capturing the card inside a dedicated, certified payment layer keeps card data entirely out of your platform. The architecture is: - AI agent handles conversation and identifies payment intent - Platform initiates a payment session via API - The payment layer captures the card inside its certified environment at the point of payment (today, via Twilio Pay) - Card data never enters your platform, your recordings, or your AI pipeline - Payment layer handles tokenisation and PSP routing - Webhook returns success/failure and your application continues PCI scope stays with the payment layer. Your engineering team stays focused on your product. Your enterprise customers use their existing PSPs. One honest caveat: the secure capture at the point of payment is live now (on Twilio Pay today); returning the caller to the same AI agent after payment is return-route wiring you build in your Twilio flow (pass a conversation ID). Shuttle works with Twilio today, and any carrier coming soon. ## FAQ: AI Voice Agents and PCI-Compliant Payments ### Can AI agents handle PCI-compliant payments? Yes. An AI voice agent can take a card payment during a call and stay PCI-compliant, as long as the card data never enters the AI pipeline. The agent runs the conversation, then hands off to a PCI DSS Level 1 certified payment layer that captures the card from the phone keypad via Twilio Pay today, charges it against your gateway, and returns only a masked result. The card number never reaches the AI model, the transcript or the recording. ### Can voice agents process payments and complete transactions? Yes. A voice agent can take the customer through to a completed, authorised payment in the same call. The agent confirms the amount, the payment layer captures the card via the keypad, the transaction is authorised against your gateway, and the agent confirms success once the call returns to it (return routing you wire in your Twilio flow). No separate IVR line, no callback. Where no agent or voice bot is needed at all, an automated keypad flow does the same job: see IVR Payments. ### Which voice AI tools support PCI-compliant payments over the phone? Voice AI platforms generally leave card capture to a separate payment layer. Retell, Vapi and Bland have no native way to take a caller's card; ElevenLabs and Synthflow offer Stripe-only native payments; Cognigy routes capture to external payment tools inside its own PCI-assessed environment. In each case a dedicated payment layer handles the card. Shuttle adds PCI-compliant in-call payment capture alongside these platforms, on Twilio today, taking the card via the keypad or an SMS payment link and sending it to whichever of the 30+ voice-capable payment gateways you use. See the per-platform guides in Related Reading below. ### Do PCI DSS and PSD2/PSD3 apply to AI agent payments? PCI DSS applies the moment cardholder data is captured, whether a human or an AI agent is on the call. In Europe, PSD2's strong customer authentication rules apply to online payments such as a payment link sent by SMS, while keypad payments taken on a call are processed as MOTO transactions, which fall outside SCA; PSD3 and the Payment Services Regulation will build on this once they apply. Using a PCI-certified payment layer keeps the card data, and most of the compliance burden, off your systems; you still validate your own compliance. ### What PCI rules should I watch out for when letting an AI agent collect payments? The main risks are card data landing in call recordings or transcripts, keypad tones reaching your transcription or LLM, and card numbers being written to your CRM or logs. Avoid all three by capturing the card in an isolated PCI-certified environment so the digits never reach the audio and systems your stack sees. Done correctly, you can usually validate under SAQ A rather than SAQ D; your acquirer confirms which SAQ applies. ### Can an AI voice agent split a past-due balance into a payment plan during the call? Yes. For collections and bill-pay, the agent can agree a payment plan, take the first instalment immediately on the keypad, and save the card with your gateway so the remaining instalments your system schedules can be charged without asking for the card again. See AI Voice Payments for Debt Collection for the collections-specific workflow. ## Related Reading - Embedded Payments for CCaaS -- the business case for CCaaS operators - The CCaaS Payments Revenue Opportunity -- the math on monetising payment volume through your platform - AI Payment Security: How AI Agents Handle Card Data -- broader AI agent PCI guide - Voice AI Is Booming -- But Can It Take a Payment? -- the market context - Agentic Payments in 2026: The Infrastructure Guide -- the broader infrastructure landscape for AI agent payments - Chat Agent Payments -- the chat channel equivalent - What Is Embedded Payments? -- the fundamentals - PCI-Compliant Payments for Contact Centres -- the broader contact centre payment guide (human agents, AI agents, evaluation criteria) - Secure Payment Collection for Debt Agencies -- AI agent payments applied to debt collection - PCI-Compliant Payment Architecture for Insurance Platforms -- limited-scope architecture for insurance voice payments - What Are Voice Payments? -- the complete guide to IVR, agent-assisted, and AI voice payments - AI Voice Payments for Hotels & Travel -- voice payment architecture for hotel chains and OTAs - How Voice AI Ordering Platforms Handle Payments -- PCI challenges specific to restaurant voice AI (SoundHound, ConverseNow, Kea) - Twilio Pay Connectors: How to Connect Any Payment Gateway to Twilio -- connecting Twilio to any PSP for voice agent payments - Twilio PCI Compliance: How to Take Payments Without Handling Card Data -- PCI scope and compliance architecture for Twilio-based voice agents - How to Connect Stripe to Twilio for Voice & IVR Payments -- Stripe + Twilio integration for voice payments - Twilio Pay -- Connect Any Payment Gateway to Twilio -- install the Pay Connector to connect your gateway - Vapi Payments: PCI-compliant payment capture for Vapi voice agents - Bland AI Payments: secure payment capture for Bland AI phone agents - ElevenLabs Payments: native Stripe vs multi-PSP for ElevenLabs agents - Synthflow Payments: native Stripe vs multi-PSP for Synthflow voice agents - Phonely Payments: PCI-compliant payment capture for Phonely AI phone agents - Sierra AI Payments: native Level 1 PCI payments vs a multi-PSP layer - Parloa Payments: native Payment Skill vs multi-PSP capture - Decagon Payments: verified PCI-compliant capture for Decagon AI agents - Kore.ai Payments: PCI-compliant in-call capture for Kore.ai agents - Yellow.ai Payments: in-call DTMF capture vs payment links on VoiceX - Regal.ai Payments: in-call capture for outbound collections calls - Voiceflow Payments: PCI-compliant capture for Voiceflow voice and chat agents - Thoughtly Payments: in-call card capture for Thoughtly AI voice agents - boost.ai Payments: multi-PSP capture for boost.ai virtual agents - Gupshup Payments: native UPI and WhatsApp Pay vs multi-PSP card capture - Ada Payments: PCI-compliant capture for Ada AI voice and chat agents - Lindy Payments: in-call capture for Lindy Gaia phone agents Ready to add PCI-compliant payments to your voice agents? Install on Twilio | Book a Demo | See How It Works ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Voice Payments Are an Architecture Decision, Not a Feature Request ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [payment links](/merchants/links-checkout/) - [DTMF](/guides/dtmf-payments/) - [Twilio PCI Compliance: How to Take Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Pay Connectors](/guides/twilio-pay-connectors/) - [DTMF capture](/guides/dtmf-payments/) - [IVR Payments](/guides/ivr-payments/) - [30+ voice-capable payment gateways](/payment-providers/) - [AI Voice Payments for Debt Collection](/guides/ai-voice-payments-debt-collection/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI Payment Security: How AI Agents Handle Card Data](/guides/ai-payment-security/) - [Voice AI Is Booming -- But Can It Take a Payment?](/blog/voice-ai-payment-infrastructure-gap/) - [Agentic Payments in 2026: The Infrastructure Guide](/blog/agentic-payments-infrastructure-2026/) - [Chat Agent Payments](/guides/chat-agent-payments/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [PCI-Compliant Payment Architecture for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [What Are Voice Payments?](/guides/voice-payments/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [How Voice AI Ordering Platforms Handle Payments](/guides/voice-ai-ordering-payments/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway to Twilio](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice & IVR Payments](/guides/stripe-twilio-integration/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [ElevenLabs Payments](/guides/elevenlabs-payments/) - [Synthflow Payments](/guides/synthflow-payments/) - [Phonely Payments](/guides/phonely-payments/) - [Sierra AI Payments](/guides/sierra-payments/) - [Parloa Payments](/guides/parloa-payments/) - [Decagon Payments](/guides/decagon-payments/) - [Kore.ai Payments](/guides/kore-ai-payments/) - [Yellow.ai Payments](/guides/yellow-ai-payments/) - [Regal.ai Payments](/guides/regal-ai-payments/) - [Voiceflow Payments](/guides/voiceflow-payments/) - [Thoughtly Payments](/guides/thoughtly-payments/) - [boost.ai Payments](/guides/boost-ai-payments/) - [Gupshup Payments](/guides/gupshup-payments/) - [Ada Payments](/guides/ada-payments/) - [Lindy Payments](/guides/lindy-payments/) - [Install on Twilio](/integrations/twilio-pay/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) --- URL: https://www.shuttleglobal.com/guides/ai-voice-agents-payments/ --- # AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation | Shuttle > AI Voice Agents Are Creating a New Payment Channel AI voice agents are no longer novelty. They're production infrastructure. # AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation By Shuttle Team, December 21, 2025 ## AI Voice Agents Are Creating a New Payment Channel AI voice agents are no longer novelty. They're production infrastructure. Companies in insurance, financial services, utilities, and healthcare are deploying AI agents that handle entire phone conversations -- from greeting to resolution -- without a human involved. What changed in the last 18 months isn't the quality of the conversation. It's the scope. These agents aren't just answering FAQs or routing calls. They're renewing policies. Collecting outstanding balances. Processing upgrade orders. Booking appointments with a deposit. Taking a card number and completing a transaction before the customer hangs up. This is a net-new payment channel. It didn't exist three years ago. AI voice agents aren't replacing web checkout or point-of-sale terminals. They're creating payment surfaces in places where payment capture was previously impossible without a human agent. Think about what that means for industries where the phone is still the primary channel. Insurance renewals. Utility payments. Debt collection. Appointment scheduling. These are high-volume, high-value transaction environments where customers call in, and where -- until now -- either a human agent processed the payment or the customer was told to "visit our website." The AI voice agent eliminates that friction. The customer calls in, the AI handles the conversation, and payment happens inside that same call. No transfer. No website redirect. No callback. But enabling this creates a hard technical problem. The AI can talk. It can understand. It can reason about what the customer owes and offer options. What it cannot do -- and must never do -- is handle a credit card number. ## The Payment Problem for AI Voice Agents AI voice agents are built on large language models and speech-to-text engines. They excel at understanding natural language and generating fluid responses. They were not built to handle payment card data. Here's the problem, broken down: The agent can't "see" a card number. Even if a customer reads their card details aloud, routing that audio through a speech-to-text model and into the AI agent's context window creates an immediate PCI compliance violation. Card data has been processed by an uncertified system. Every model log, every debug trace, every piece of training data is now in scope. DTMF capture needs integration. The standard approach for card entry over phone is DTMF -- the customer types their card number on their phone keypad. But DTMF capture has to be integrated into the voice flow at the telephony level. The tones must be intercepted before they reach the AI's audio stream. This isn't a simple API call -- it's a real-time audio stream modification within a PCI-certified environment. PCI compliance is non-negotiable. PCI DSS Level 1 is the standard for any system that processes, stores, or transmits card data. If the AI platform is handling payment capture, the entire platform is in PCI scope -- every server, every log, every employee with access. No AI voice platform wants that. Enterprise customers mandate their PSP. This is the one most people miss. PolyAI doesn't process payments for itself. It processes payments on behalf of its enterprise customers -- insurance companies, utilities, financial institutions. Each of those enterprises has existing PSP relationships. They use Worldpay, or Adyen, or a regional acquirer mandated by their compliance team. The AI voice platform doesn't get to choose Stripe because it's easier. Tokenisation for repeat transactions. If a customer pays once through the AI agent, the business wants to store a token for next time. Not the card number -- a token that can be reused across future calls, future channels, and future transactions. That token needs to be PSP-compatible and stored in a PCI-certified vault. Multi-currency for international deployments. Enterprise AI voice agents are deployed globally. A UK utility collects in GBP. An American insurer collects in USD. A European telco collects in EUR. The payment layer needs to handle currency, regional PSP routing, and local compliance requirements. None of these problems are solved by the AI itself. They require dedicated payment infrastructure that operates alongside the voice agent -- integrated tightly enough to feel seamless, but isolated completely from the conversational AI environment. ## How PolyAI Solved It PolyAI builds enterprise-grade AI voice agents. Their customers include some of the most regulated industries in the world -- insurance carriers, financial services firms, utility providers. These aren't small businesses experimenting with AI. They're large enterprises deploying voice agents at scale, handling thousands of calls per day. For many of these enterprises, the AI voice agent isn't just handling enquiries. It's handling transactions. An insurance customer calls to renew a policy -- the agent needs to collect payment. A utility customer calls about an overdue bill -- the agent needs to process the balance. A patient calls to book a procedure -- the agent needs to take a deposit. Each of these scenarios requires the AI to capture a payment mid-conversation. And each of PolyAI's enterprise customers has their own PSP, their own compliance requirements, and their own audit expectations. PolyAI chose Shuttle as their payment infrastructure layer. > "Shuttle let us treat legacy payment providers as a modern SaaS service. It enabled us to support the gateways our customers required and fully automate high-value transactions across regulated industries." -- Nathan Liu, PolyAI That quote captures two things. First, "treat legacy payment providers as a modern SaaS service" -- PolyAI's enterprise customers don't all use modern API-first PSPs. Some use legacy gateways with decades-old integration specs. Shuttle abstracts those differences away behind a single, modern API. PolyAI integrates once and supports all of them. Second, "support the gateways our customers required" -- PolyAI doesn't dictate which PSP an enterprise uses. The enterprise keeps its existing payment relationships. Shuttle routes through whichever gateway the enterprise mandates. This is the architecture that makes enterprise deals close. ## The Architecture: How It Actually Works Here is the technical flow for a payment captured within a PolyAI AI voice agent conversation, powered by Shuttle: 1. The AI agent handles the conversation. PolyAI's voice agent is on the call. It has identified the customer, confirmed the amount owed, and determined that payment should happen now. The AI is running on PolyAI's infrastructure -- large language models, speech synthesis, real-time audio processing. 2. The AI agent triggers Shuttle's payment session. When payment is needed, PolyAI's system makes an API call to Shuttle: "Start a payment session. Amount: $247.50. Currency: USD. PSP: the enterprise customer's configured gateway." Shuttle returns a session identifier and the voice flow is prepared for secure capture. 3. The voice flow transitions to secure capture mode. The AI agent tells the customer: "I can take your payment now. Please enter your 16-digit card number using your phone keypad." At the telephony level, the audio stream is now being intercepted by Shuttle's PCI-certified capture environment. 4. The customer enters card details via DTMF. The customer types their card number, expiry date, and CVV on their phone keypad. The DTMF tones are captured within Shuttle's PCI DSS Level 1 environment. Critically, the tones are stripped from the audio stream -- they never reach PolyAI's AI models, never appear in call recordings, never enter any log outside the PCI boundary. 5. Shuttle tokenises the card and routes to the enterprise's PSP. Shuttle validates the card (BIN check, Luhn validation), tokenises it, and routes the transaction to whichever PSP the enterprise customer has configured -- Worldpay, Adyen, Stripe, a regional acquirer, or any of 40+ supported gateways. The token is held with the enterprise's own gateway for future use. 6. The transaction result is returned to the AI agent. Shuttle sends the result back to PolyAI via API: approved, declined, or requiring additional action. No card data crosses this boundary. The AI agent receives only the transaction outcome. 7. The AI agent confirms payment and continues the conversation. The voice agent says: "Your payment of $247.50 has been processed successfully. You'll receive a confirmation email shortly. Is there anything else I can help with?" The call continues naturally. The customer may not even register that a system transition occurred. 8. No card data touches PolyAI's or the enterprise's infrastructure. At no point did card data enter PolyAI's AI models, PolyAI's servers, the enterprise's systems, the call recording, or any environment outside Shuttle's PCI-certified boundary. PolyAI's PCI scope: zero. The enterprise's PCI scope for this channel: zero. Total elapsed time from "please enter your card number" to "payment confirmed": seconds. Human involvement: none. ## Why This Can't Be Built with Standard Payment APIs Standard payment APIs were designed for the web. Stripe Checkout renders a payment form in a browser. Adyen Drop-In embeds a card capture widget in a web page. PayPal opens a redirect flow. These all assume one thing: the customer is looking at a screen. AI voice agents don't have a screen. There's no browser to render a checkout form. There's no webpage to embed a widget. The customer is on a phone call. The "interface" is audio and keypad tones. Building payment capture for AI voice agents requires: DTMF capture within a PCI-certified environment. The keypad tones have to be intercepted at the telephony layer, decoded, validated, and processed -- all within a PCI DSS Level 1 boundary. Standard payment APIs don't provide this. They expect card data to arrive via HTTPS POST from a browser, not as audio frequency tones from a phone call. Voice-native payment flows. The payment sequence needs to integrate with the conversational flow -- prompting for card number, then expiry, then CVV, handling re-entry if a digit is missed, confirming the amount before processing. This is a fundamentally different UX pattern from a web form. Real-time integration with the conversational AI engine. The payment layer needs to signal back to the AI agent in real time: "card captured," "processing," "approved," "declined." The agent needs these signals to continue the conversation naturally. Latency kills the experience -- if the AI goes silent for five seconds while waiting for a payment result, the customer thinks the call dropped. PSP-neutral routing. The AI voice platform doesn't get to mandate a PSP. Its enterprise customers bring their own. The payment layer must route to whichever gateway the enterprise has configured, through a single integration that the AI platform maintains once. Tone masking. DTMF tones must be stripped from the audio stream in real time so they never reach the AI model, call recording systems, or analytics platforms. This is a real-time audio processing requirement that sits at the intersection of telephony engineering and payment security. None of this exists in Stripe's API. Or Adyen's. Or any standard payment gateway. It's specialised infrastructure built for a specific problem: capturing payments inside a voice conversation. ## The Regulated Industry Factor PolyAI's customers aren't e-commerce companies. They're regulated enterprises. Insurance carriers operating under FCA oversight. Financial services firms subject to PSD2 and state-level regulations. Utility companies with OFGEM compliance requirements. Healthcare providers operating under HIPAA. These aren't companies that move fast and figure out compliance later. They have legal teams that review every vendor. They have compliance officers who audit every data flow. They have specific, non-negotiable requirements about where card data goes, which PSP processes it, and who has access to transaction records. For the payment layer inside an AI voice agent, this means: PSP mandates are real. An insurance carrier doesn't switch PSPs because an AI vendor prefers Stripe. They use Worldpay, or a specific acquirer, because their compliance team approved it and their existing reconciliation systems depend on it. The payment infrastructure must support that PSP -- not ask the enterprise to change. Audit trails matter. Regulated enterprises need to demonstrate exactly how card data was handled during an AI voice agent call. They need to show auditors that card data never entered the AI's environment, never appeared in call recordings, and was processed through a PCI DSS Level 1 certified system. The payment layer must provide this documentation. Data residency and sovereignty. European enterprises may require that card data is processed within the EU. UK financial services firms may require UK-based processing. The payment layer needs to support these geographic constraints. Compliance certifications compound. PCI DSS Level 1 is the baseline. But regulated enterprises also ask about ISO 27001, SOC 2, and sector-specific certifications. The payment layer carries these certifications so the AI platform and the enterprise don't have to. Shuttle holds PCI DSS Level 1, ISO 27001, and SOC 2 certifications. For PolyAI's enterprise customers, this means the payment component of their AI voice agent deployment arrives pre-certified. No additional compliance burden. No new audit scope. The payment infrastructure is already approved. ## The Market Context: Agentic Commerce in 2026 The payments industry has woken up to AI agents. The announcements are coming fast. Stripe launched its Agentic Commerce Suite -- tools for AI agents to discover, negotiate, and pay for digital services. Their x402 protocol enables machine-to-machine payments. The focus is agent-to-agent commerce: software systems paying each other for APIs, data, and compute. Google announced AP2, the Agent Payments Protocol, with over 60 partners including Adyen, American Express, Mastercard, and PayPal. AP2 is designed to let AI agents initiate payments on behalf of consumers -- a protocol-level standard for how agents request authorisation. Worldline connected AI agents to its payment ecosystem via MCP (Model Context Protocol) servers, creating bridges between large language models and payment APIs. Visa completed the first voice-enabled agentic payment transaction, demonstrating a cardholder using an AI agent to pay real estate service charges. These announcements share a common focus: enabling AI agents to initiate and authorise payments. They're solving the protocol problem -- how an AI agent expresses "I want to pay" in a way a payment system understands. What they don't address is the infrastructure problem for voice. Stripe's Agentic Commerce Suite assumes a digital/API context. Google's AP2 is a web-first protocol. Visa's demonstration was a proof of concept. None of them solve DTMF capture within a PCI boundary. None of them address PSP-neutral routing for enterprise customers who mandate their gateway. None of them provide the voice-native payment flow that production AI voice agents require. Voice is the harder problem. Web-based AI agents can render a checkout form. Chat agents can send a link. Voice agents operate in an audio-only environment where the customer's phone keypad is the input device and compliance requires that tones never reach the AI. It's also the bigger opportunity. In insurance, financial services, utilities, and healthcare -- industries with trillions of dollars in annual transaction volume -- the phone is still the primary customer channel. AI voice agents are automating those calls. The payment infrastructure that powers them is critical. ## What AI Voice Agent Platforms Need If you're building an AI voice agent platform that needs to process payments -- or you're an enterprise evaluating AI voice agents for transaction-heavy workflows -- here's what the payment infrastructure must provide: PSP-neutral architecture. Your enterprise customers will mandate their PSP. The payment layer must support 40+ gateways through a single integration, routing each transaction to the correct provider based on the enterprise's configuration. This is not optional -- it's the requirement that makes or breaks enterprise deals. PCI DSS Level 1 certification within the voice flow. Not PCI compliance for a web form that gets sent via SMS as a fallback. PCI compliance for the actual DTMF capture that happens while the customer is on the call with the AI agent. The entire capture, tokenisation, and processing chain must sit within a Level 1 certified environment. DTMF capture with tone masking. Real-time interception of keypad tones at the telephony layer, with simultaneous stripping of those tones from the audio stream. The AI model, call recording, and analytics systems must never see the raw DTMF data. This is the technical mechanism that keeps the AI platform out of PCI scope. API-triggered payment sessions. The AI agent needs to initiate a payment session programmatically -- specifying amount, currency, PSP, and any metadata -- and receive a real-time result. The API must be fast enough that the conversational flow isn't disrupted. Sub-second response times for session creation. Transaction results returned within the normal payment processing window. Tokenisation for repeat payments. First-time card capture should produce a reusable token. That token should work for future transactions across channels -- if the customer calls back, if a payment link is sent, if a web portal is used later. One capture, multiple uses. Multi-currency support. Enterprise deployments span geographies. The payment layer must handle currency conversion, regional PSP routing, and local regulatory requirements without requiring the AI platform to build separate integrations per market. Compliance documentation for regulated customers. Enterprise compliance teams will audit the payment flow. The payment layer must provide clear documentation of data flows, certifications (PCI DSS Level 1, ISO 27001, SOC 2), and architecture diagrams showing the separation between AI and payment environments. White-label operation. The payment flow should be invisible. The enterprise's customers should experience the payment as part of the enterprise's service. No third-party branding. No redirects to external platforms. The payment layer sits quietly underneath, powering the transaction while the enterprise owns the customer experience. ## Building the Payment Layer for AI Voice AI voice agents represent a fundamental shift in how payments happen. Not a new checkout button. Not a new form factor. A new channel -- one where transactions occur inside conversations, where the input device is a phone keypad, and where enterprise compliance requirements shape every architectural decision. The platforms building these voice agents -- PolyAI and others -- need payment infrastructure that was designed for this environment. Not web checkout repurposed for voice. Not a single-PSP integration that locks out enterprise customers. Purpose-built infrastructure that handles DTMF capture, PCI compliance, multi-PSP routing, and real-time AI integration as a single, unified layer. That's what Shuttle provides. A single integration point for AI voice platforms to support 40+ payment gateways, with PCI DSS Level 1 compliance, DTMF capture and tone masking, tokenisation, multi-currency, and white-label operation -- all designed to sit inside the conversational flow without the customer or the AI ever touching card data. For the chat-side of this equation -- how AI agents capture payments on websites, WhatsApp, and messaging platforms -- see Chat Agent Payments: How AI Closes Sales Without a Human Handoff. For the broader architecture covering both channels, see How AI Agents Process Payments: The Infrastructure Guide. If your AI voice agent platform needs payment infrastructure -- or your enterprise is deploying AI voice agents that handle transactions -- [book a call with Shuttle](https://shuttleglobal.com/contact). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Voice Payments Are an Architecture Decision, Not a Feature Request ### Sage Invoice Payments: How to Let Customers Pay Online ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### The Future of Voice Commerce: From IVR to Intelligent Payments ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ## Links - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Chat Agent Payments: How AI Closes Sales Without a Human Handoff](/guides/chat-agent-payments) - [How AI Agents Process Payments: The Infrastructure Guide](/guides/ai-agent-payments) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogThe Future of Voice Commerce: From IVR to Intelligent Payments→](/blog/the-future-of-voice-commerce/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) --- URL: https://www.shuttleglobal.com/guides/ai-voice-payments-debt-collection/ --- # AI Voice Payments for Debt Collection: Capture Payments at the Moment of Agreement | Shuttle > The Collections Problem: Agreements Without Payments Debt collection runs on a simple loop: contact the debtor, negotiate a payment arrangement, collect... # AI Voice Payments for Debt Collection: Capture Payments at the Moment of Agreement By Shuttle Team, December 21, 2025 ## The Collections Problem: Agreements Without Payments Debt collection runs on a simple loop: contact the debtor, negotiate a payment arrangement, collect the money. The first two steps have been optimised heavily. Diallers reach more people. Analytics predict the best time to call. Scripts are tested and refined. AI voice agents are now handling the conversations themselves -- negotiating payment plans, confirming balances, and reaching agreements at scale. But the third step -- collecting the money -- is where the loop breaks. A human agent or AI negotiates a payment arrangement. The debtor agrees to pay £150 today and £150 next month. The agent says: "Great, I'll send you a link to make the payment." Or: "You can pay on our website." Or: "I'll transfer you to our payment line." The debtor hangs up. The commitment cools. The link sits unopened in an inbox. The website visit doesn't happen. The transfer drops. Industry data tells the story: the gap between "agreement to pay" and "payment received" is where collections operations lose 30-50% of promised revenue. Every step between the verbal commitment and the actual transaction is a leak. The fix is architectural, not motivational. Capture the payment during the call, at the exact moment the debtor agrees. No handoff. No link. No second step. ## How AI Voice Agents Collect Payments An AI voice agent handles the entire collections call -- from identifying the debtor to confirming the payment. Here's an outbound collection: AI Agent: "Good morning. I'm calling from ABC Collections regarding an outstanding balance of £312.40 on your account. Am I speaking with James?" Debtor: "Yes, that's me. What's this about?" AI Agent: "You have an outstanding balance of £312.40 from your account with XYZ Services, originally due on 15 January. I can help you resolve this today. Would you like to pay the full amount, or set up a payment plan?" Debtor: "I can do £150 now and the rest next month." AI Agent: "I can arrange that. £150 today and £162.40 on 18 March. I can take the first payment now. Please enter your 16-digit card number using your phone keypad." The debtor types their card number. DTMF tones are captured within the PCI-certified payment layer -- stripped from the audio stream. The AI never sees the card data. Neither does the collections agency or the original creditor. AI Agent: "Thank you. I'm processing £150 now." The payment layer validates the card, routes to the creditor's configured PSP, and processes the transaction. A token is stored for the scheduled second payment. AI Agent: "Your payment of £150 has been processed. Your next payment of £162.40 is scheduled for 18 March using the same card. You'll receive a confirmation by text. Is there anything else?" Payment captured at the moment of agreement. Card tokenised for the scheduled instalment. Human involvement: none. PCI exposure for the collections agency: none. ## Why This Matters for Collections ### The Commitment Window Is Narrow Behavioural economics is clear: the probability of payment drops rapidly with time after a verbal agreement. A debtor who agrees to pay during a call has the highest likelihood of following through in that exact moment. Every minute, hour, or day between agreement and payment reduces the probability. Collections operations that capture payment during the call -- not after -- maximise recovery rates from every contact. The AI agent doesn't say "I'll send you a link." It says "I can take your payment now." ### Scale Without Headcount Collections is labour-intensive. Human agents make calls, negotiate arrangements, and process payments -- one at a time. Scaling means hiring more agents, more training, more management, more compliance oversight. AI voice agents scale differently. They handle thousands of concurrent calls. They work evenings and weekends. They don't need breaks, supervision, or performance reviews. They follow compliance scripts perfectly, every time. For BPOs handling collections on behalf of multiple creditors, AI voice agents with payment capability transform the unit economics of the business. ### PCI Compliance Is a Persistent Liability Collections environments handle card data constantly. Agents hear card numbers. Recordings capture them. CRM systems store them. Every one of these touchpoints is a PCI surface. The compliance cost is real: maintaining PCI DSS across a collections contact centre means monitoring agent behaviour, securing recording systems, segmenting networks, and conducting annual audits. For BPOs serving multiple clients, the compliance burden multiplies. AI voice payments eliminate this exposure. Card data is captured in a PCI-certified environment that's completely isolated from the collections agency's infrastructure. The agency's PCI scope drops to SAQ-A. Recordings are clean. No card data enters any system the agency controls. ### Multi-Client, Multi-PSP Reality BPOs and collections agencies serve multiple creditors. Creditor A uses Worldpay. Creditor B uses Stripe. Creditor C uses a regional processor mandated by their treasury team. The collections agency can't standardise on one PSP. Each creditor's payments must route to their configured gateway. A PSP-neutral payment layer handles this through a single integration -- the AI agent triggers a payment, the layer routes to the correct PSP based on the creditor's configuration. ## Payment Plan Automation Collections isn't just about one-off payments. Most arrangements involve payment plans -- agreed schedules of instalment payments over weeks or months. AI voice agents with tokenisation capability automate the entire plan: 1. Negotiate the arrangement. The AI agent confirms the balance, discusses options, and agrees a payment schedule with the debtor. 2. Capture the first payment. Payment is taken during the call via DTMF. The card is tokenised. 3. Schedule future payments. The stored token is used for scheduled instalment payments. No need for the debtor to re-enter card details. 4. Handle failed payments. If an instalment fails (expired card, insufficient funds), the AI agent can call the debtor proactively: "Your scheduled payment of £162.40 didn't process. Would you like to update your card details now?" 5. Confirm completion. When the balance is cleared, the AI agent (or an automated message) confirms the account is settled. This loop -- negotiate, capture, schedule, retry, confirm -- runs autonomously. Human agents only need to intervene for disputed balances, complaints, or complex hardship cases. ## Compliance and Regulatory Considerations Debt collection is heavily regulated. The Consumer Credit Act, FCA debt collection guidelines, OFCOM rules on automated calling, and PCI DSS all apply. AI voice payment systems must satisfy all of them. ### FCA Debt Collection Rules AI voice agents must comply with the same standards as human agents: treating customers fairly, recognising signs of financial difficulty, offering appropriate forbearance, and not applying inappropriate pressure. The AI's conversational logic must include these safeguards -- escalating to a human agent when the debtor indicates hardship, providing required regulatory disclosures, and maintaining records of the interaction. ### OFCOM and Automated Calling Outbound AI calling must comply with OFCOM rules on automated and predictive diallers. This includes abandoned call rates, caller ID presentation, and opt-out mechanisms. AI voice agents must identify themselves clearly and provide a way for the debtor to speak to a human if requested. ### PCI DSS Card data captured during the call must be processed within a PCI DSS Level 1 certified environment. The collections agency's systems -- diallers, CRM, recording platforms, analytics -- must never see raw card data. DTMF tones are stripped from the audio before reaching any system outside the PCI boundary. ### Call Recording Collections calls are typically recorded for quality assurance and dispute resolution. With DTMF tone masking, recordings contain the full conversation but no card data -- the payment segment sounds like silence or masking tones where the debtor entered their card number. This satisfies both QA requirements (the conversation is captured) and PCI requirements (no card data in recordings). ## The Architecture Collections AI voice payments use the same foundational architecture as other AI agent payment deployments, with specific requirements for the collections use case: ### DTMF Capture with Tone Masking Card data entered via keypad, captured in PCI-certified environment, tones stripped from audio. Same mechanism as voice payments in any context -- but critical here because collections calls are almost always recorded and audited. ### Multi-PSP Coverage Each creditor's payments route to their configured PSP. The collections agency integrates once; the payment layer handles routing per creditor. ### Tokenisation and Scheduling Cards tokenised on first capture. Tokens reused for scheduled instalment payments without the debtor needing to re-enter details or receive follow-up calls for each payment. ### SMS Payment Link Fallback For debtors who prefer not to use the keypad, the AI sends a branded payment link via SMS. The debtor pays on their device while the call continues. This is particularly useful for mobile-only debtors who may find keypad entry difficult on a smartphone. ### Real-Time Balance Updates The payment result must feed back into the collections management system immediately. The debtor's balance updates in real time. The scheduled arrangement is recorded. The account status changes from "active" to "arrangement in place." ## Inbound vs. Outbound ### Outbound Collections The AI agent calls debtors proactively. This is where the highest volume and biggest opportunity exists. Outbound AI calls can cover thousands of accounts per day -- far more than a human agent team. The call flow: identify the debtor, confirm the balance, negotiate an arrangement, capture payment. All in one call. The AI can adapt its approach based on the account -- amount owed, age of debt, previous contact attempts, and the debtor's responses. ### Inbound Payment Calls Debtors call in to make a payment. The AI agent answers, identifies the account, confirms the balance, and processes the payment. This replaces the IVR payment line with a conversational experience -- the debtor can ask questions, discuss their balance, and pay in the same interaction. ### Failed Payment Follow-Up When a scheduled payment fails, the AI calls the debtor to collect. "Your payment of £162.40 scheduled for today didn't process. Would you like to update your card details?" This is a high-value automation -- failed payment recovery is typically manual and time-sensitive. ## What BPOs and Collections Agencies Need If you're evaluating AI voice payment infrastructure for debt collection: PCI DSS Level 1 -- non-negotiable for any system handling card data. The certification must cover the DTMF capture environment, not just a web form. Multi-PSP routing -- you serve multiple creditors with different PSP relationships. The payment layer must route per creditor without separate integrations. Tokenisation and scheduling -- capture a card once, use the token for scheduled instalments. Failed payment retry logic should be built in. Regulatory compliance tooling -- the AI must support FCA-compliant conversation flows, hardship escalation, and OFCOM-compliant outbound calling. Recording-safe capture -- DTMF tone masking must produce clean recordings with no card data. This is audited. Real-time integration -- payment results must feed back into your collections management system immediately for balance updates and arrangement tracking. SMS fallback -- payment links for debtors who prefer visual checkout or can't use their keypad. ## FAQ Can AI voice agents really negotiate debt payments? Yes. AI voice agents can confirm balances, discuss payment options, negotiate instalment plans, and capture payments -- all in a single call. For complex hardship cases or disputes, the AI escalates to a human agent. Is automated debt collection calling legal? Yes, subject to OFCOM and FCA regulations. AI voice agents must identify themselves, provide required disclosures, offer a route to a human agent, and comply with abandoned call rate limits. The technology is compliant when properly configured. What about vulnerable customers? AI voice agents should be programmed to recognise indicators of vulnerability or financial hardship -- language patterns, tone, explicit statements -- and escalate to a trained human agent. This is both a regulatory requirement and an ethical obligation. How does multi-creditor PSP routing work? The collections agency integrates once with a PSP-neutral payment layer. Each creditor is configured with their preferred PSP. When the AI captures a payment, the layer routes the transaction to the correct gateway based on which creditor the debt belongs to. No per-creditor payment integration required. What completion rates can we expect? Industry benchmarks for AI voice payment capture in collections aren't yet standardised, but the principle is clear: capturing payment at the moment of agreement consistently outperforms post-call payment links or portal redirects. PolyAI's 75% completion rate across regulated industries provides a reference point. Can the same infrastructure handle inbound and outbound? Yes. The payment capture mechanism (DTMF, SMS link) is the same regardless of call direction. The AI agent's conversational logic adapts -- inbound calls focus on processing an intended payment; outbound calls include negotiation and arrangement. Automate collections payment capture -- at the moment of agreement. Shuttle connects AI voice agents to 40+ payment gateways with PCI DSS Level 1 compliance, DTMF capture, tokenisation for payment plans, and multi-creditor PSP routing. Book a Call | See Voice Checkout ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Voice Payments Are an Architecture Decision, Not a Feature Request ### Sage Invoice Payments: How to Let Customers Pay Online ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### The Future of Voice Commerce: From IVR to Intelligent Payments ## Links - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [AI agent payment](/guides/ai-agent-payments) - [voice payments](/guides/voice-payments) - [Book a Call](/contact) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogThe Future of Voice Commerce: From IVR to Intelligent Payments→](/blog/the-future-of-voice-commerce/) --- URL: https://www.shuttleglobal.com/guides/ai-voice-payments-hotels-travel/ --- # AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent | Shuttle > Hotels Are Replacing Call Centres. The Payment Moment Is the Gap. Over 70% of hotel executives are now prioritising AI investment. # AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent By Shuttle Team, December 22, 2025 ## Hotels Are Replacing Call Centres. The Payment Moment Is the Gap. Over 70% of hotel executives are now prioritising AI investment. Voice agents are leading the charge -- deployed across major hotel chains, handling reservations, billing inquiries, concierge requests, and guest services. Some properties report 80% fewer missed calls. Others are handling 50% or more of inbound volume without a human agent. The automation story is real. But it has a hole in it. The moment a guest says "yes, I'd like to book that" or "go ahead and upgrade me," the AI agent hits a wall. It can quote the price. It can check availability. It can confirm dates and room types. But when it's time to capture a card payment, most deployments do one of three things: - Transfer to a human agent. The guest waits on hold. Conversion drops. The human agent re-establishes context. The upsell moment -- where the guest was ready to pay -- has cooled. - Send a follow-up email or link. "I'll send you a payment link by email." The guest hangs up, intending to pay later. Some do. Many don't. The hotel has converted an intent into a maybe. - Skip the payment entirely. The reservation is confirmed without a deposit. The no-show rate climbs. The revenue isn't secured. Each of these is revenue leakage. The guest was on the phone, ready to pay, and the system couldn't close. AI voice payment infrastructure solves this. The AI agent handles the conversation. A PCI-certified payment layer captures the card details via the guest's phone keypad -- mid-call, mid-conversation, without a human ever touching card data. The booking is confirmed and paid in a single interaction. This is already working in production across regulated industries. Hotels and travel are the next vertical where it scales. ## What AI Voice Payments Look Like in Hospitality A guest calls a hotel. The AI voice agent answers. Guest: "I have a reservation for next weekend. I'd like to upgrade to a suite if one's available." AI Agent: "I can see your reservation for March 7th to 9th. We have a deluxe suite available at an additional £85 per night -- that's £170 for your stay. Would you like to upgrade?" Guest: "Yes, go ahead." AI Agent: "I can take your payment now. Please enter your 16-digit card number using your phone keypad." The guest types their card number. The DTMF tones are intercepted by a PCI DSS Level 1 certified payment environment -- stripped from the audio stream before they reach the AI model, any recording system, or the hotel's infrastructure. The agent prompts for expiry and CVV. Each entry is captured securely. AI Agent: "Thank you. I'm processing the upgrade payment of £170 now." The payment layer validates the card, routes the transaction to the hotel chain's configured PSP, and processes the charge. A result is returned to the AI agent. AI Agent: "Your upgrade is confirmed. You're now in the Deluxe Suite for March 7th to 9th. You'll receive a confirmation by email. Is there anything else I can help with?" Total call duration: under 2 minutes. Human involvement: none. Card data in the hotel's systems: none. Revenue captured at the moment of intent. Now compare that to the current state: "I'll transfer you to the front desk to handle the payment." Guest waits. Context is lost. Half the time, the upgrade doesn't happen. ## Why Hospitality Needs This Now ### Revenue Leakage on Upsells Is Massive Hotels generate a significant share of revenue from ancillary sales -- room upgrades, late checkout, early check-in, spa bookings, dining reservations, experience packages, airport transfers. These are high-margin, time-sensitive transactions. The conversion window is narrow. A guest calls to confirm their reservation. They're engaged, thinking about their trip, open to suggestions. If the AI agent can offer an upgrade and capture payment in the same breath, conversion rates are dramatically higher than any follow-up email or portal prompt. Every "I'll transfer you" or "I'll send you a link" is a lost upsell. Multiply that across thousands of calls per week across a hotel chain, and the revenue impact is material. Hotels using AI voice agents for guest interactions report up to 25% higher ancillary revenue -- but only when the agent can close. An AI agent that can describe the offer but can't take the money is half a solution. ### Call Volumes Are Not Decreasing Despite the shift to online booking, hotels handle enormous call volumes. Reservations. Modifications. Billing questions. Concierge requests. Group bookings. Corporate travel arrangements. Loyalty programme inquiries. A mid-size hotel chain handles thousands of calls daily. A large chain handles tens of thousands. AI voice agents reduce missed calls by up to 80% and handle the majority of routine inquiries without human intervention. But payment-related calls -- the ones that actually generate revenue -- still require a human in most deployments. Add the multi-language requirement. International hotels serve guests in 15+ languages. Staffing human payment agents across that many languages, across time zones, is prohibitively expensive. An AI voice agent with payment capture handles any language, any time, at consistent quality. ### PCI Compliance Across Hotel Voice Channels Is a Liability Every time a front desk agent or call centre agent takes a card number over the phone, the hotel's PCI scope expands. The telephony system, call recordings, agent workstations, the property management system, and the network infrastructure all enter PCI scope. For a single hotel, this is manageable. For a chain with hundreds of properties -- each with their own telephony, their own front desk, their own call handling -- PCI compliance becomes a multi-million-pound liability. SAQ-D compliance (the full 300+ requirement assessment) applies to any environment where card data is spoken, heard, or recorded. AI voice payments with DTMF capture change the equation entirely. Card data is entered via the guest's keypad and captured in a PCI-certified environment. It never enters the hotel's audio stream, recordings, or systems. PCI scope for voice payments drops from SAQ-D to SAQ-A. For hotel chains operating across jurisdictions, this isn't just a cost saving. It's a compliance architecture that actually scales. ### Hotel Chains Mandate Specific PSPs Per Region This is where hospitality payment complexity mirrors the broader travel industry. Global hotel groups negotiate enterprise-level PSP agreements that vary by region, by brand, and sometimes by property. European properties settle through Adyen. North American properties use Worldpay or Chase. APAC properties use regional acquirers with local payment method coverage. These aren't preferences. They're corporate treasury mandates. A hotel chain's CFO has negotiated rates and settlement terms with specific acquirers per region. Any payment infrastructure -- including AI voice payment infrastructure -- must use the PSP each property has contracted. Single-PSP payment solutions break the moment the chain operates across geographies. An AI voice agent that can only process payments through Stripe can't serve a hotel chain that requires Adyen in Europe and Worldpay in the US. The payment layer must be PSP-neutral. Route to whatever gateway the hotel mandates. Add new PSPs through configuration, not code. This is the same multi-PSP challenge that travel platforms face at the infrastructure level -- now applied to the AI voice agent layer. ## Hotel & Travel Payment Scenarios ### Reservation Deposits and Prepayment A guest calls to book a room. The AI agent checks availability, quotes the rate, and when the guest confirms, captures a deposit or full prepayment mid-call. For flexible-rate bookings: pre-authorisation at booking, full capture at check-in. For non-refundable rates: full capture at the point of booking. For peak-season or high-demand dates: deposit captures that secure the reservation. Multi-currency applies immediately. A Japanese guest calling a London hotel pays in yen. The hotel settles in pounds. The chain reports in dollars. Three currencies in a single phone call -- handled by the payment layer, transparent to the AI agent. ### Room Upgrades and Upsells The highest-converting moment in hospitality: the guest is already on the phone, already thinking about their stay, already open to spending more. The AI agent checks availability, quotes the upgrade price, and captures the difference. Suite upgrade. Ocean view. Club floor access. Early check-in. Late checkout. Each is a revenue opportunity that dies the moment the guest hangs up. DTMF payment capture makes this instant. No transfer to a human. No "check your email for a payment link." The guest says yes, types their card, and the upgrade is confirmed before the call ends. ### Ancillary Services AI concierge agents handle bookings for hotel services -- spa appointments, restaurant reservations, experience packages, airport transfers, event tickets. Each is a payment moment. A guest calls the concierge line: "Can you book me a couples' massage for Saturday?" The AI agent checks availability, quotes the price, captures payment, and confirms the booking. One call. One interaction. Revenue secured. This extends to experience packages sold by OTAs and travel platforms. A post-booking call offering a guided tour, a wine tasting, a cooking class -- with payment captured inline -- turns every guest interaction into a revenue opportunity. ### Booking Modifications and Change Fees Guest calls to change dates. The AI agent calculates the fare difference -- additional charges for peak dates, refunds for off-peak shifts, change fees where applicable -- and captures or processes the adjustment mid-call. For OTAs handling multi-leg itineraries, this gets complex. Flight date changes that trigger airline change fees. Hotel rebooking at a different rate. Transfer rescheduling. Each component may involve a different supplier and a different PSP. The payment layer handles the routing; the AI agent handles the conversation. ### Group Bookings and Corporate Travel High-value transactions that traditionally require dedicated sales staff. A corporate travel manager calls to book 30 rooms for a conference. An event planner arranges accommodation for a wedding party. AI voice agents handle the initial booking and deposit capture. For transactions where DTMF isn't practical -- the caller is on a conference phone, or company policy requires invoice-based payment -- the AI agent sends a branded payment link via SMS or email. The caller completes payment on their device while the conversation continues. Split payments across multiple cost centres, purchase order references, and corporate billing requirements are handled through the payment layer's configuration. ### Late Checkout, Early Check-In, and Incidentals Operational payments that happen post-booking -- during the stay or at departure. A guest calls the front desk AI: "Can I get a late checkout until 2pm?" The AI agent checks availability, quotes the fee, captures payment, and confirms. No queue at reception. No "please come to the front desk." The guest's checkout is extended before they've finished their coffee. Minibar settlements, room service charges, parking fees -- each can be captured by the AI agent when the guest calls to inquire. Incremental authorisations handle the variable nature of these charges: an initial hold at check-in, with additional captures as services are used. ## AI Voice Payments for Online Travel Agencies OTAs face a different version of the same problem -- but at platform scale, with multi-supplier complexity layered on top. A hotel chain deploys AI agents across its own properties. An OTA deploys AI agents across thousands of suppliers it doesn't control -- airlines, hotels, car rentals, transfers, experience providers -- each with their own PSP requirements, settlement terms, and cancellation policies. The payment moment is even more critical for OTAs. They're intermediaries. They don't own the inventory. Every failed payment, every dropped conversion, every "I'll email you a link" is revenue that walks to a competitor who can close faster. ### The OTA Payment Problem Is Multi-Supplier by Default A customer calls an OTA to modify a trip. The AI agent needs to: - Rebook a flight -- the airline mandates payment through its designated acquirer (this isn't optional; IATA BSP/ARC requirements dictate which processors handle ticket sales) - Adjust the hotel reservation -- the hotel chain requires processing through its corporate PSP - Reschedule a transfer -- the local transfer operator settles through a regional payment provider - Recalculate the package price -- the customer owes an additional £340 across three suppliers in two currencies Without AI voice payment infrastructure, the agent says: "I've updated your itinerary. You'll receive an email with a payment link for the additional charges." The customer hangs up. Maybe they pay. Maybe they abandon the modification. Maybe they call back to a competitor. With AI voice payment infrastructure, the agent captures the £340 mid-call. The payment layer splits and routes: airline portion to the airline's mandated acquirer, hotel portion to the hotel's PSP, transfer portion to the local provider. One DTMF entry from the customer. Three transactions behind the scenes. Booking confirmed before the call ends. ### Cancellations and Refund Processing OTAs handle enormous volumes of cancellations and modifications -- weather disruptions, schedule changes, personal emergencies, flexible booking policies. An AI voice agent can handle the entire cancellation flow: confirm the booking, explain the cancellation policy, process the refund (full or partial depending on the policy), and confirm the refund timeline. For modifications that result in a fare difference, the agent captures the additional payment or confirms the refund amount -- all in a single call. The payment layer handles refunds back through the original PSP, manages partial refunds across multi-supplier bookings, and ensures the reconciliation is clean. No manual intervention. No back-office queue. For mass disruption events -- an airline cancels 200 flights, a hotel closes for emergency renovation -- AI agents handle the inbound call surge. Each call: confirm the affected booking, explain the options (refund, rebook, credit), process the customer's choice, capture any fare differences if rebooking. Human agents focus on complex cases and escalations. ### High-Value Phone Bookings Despite the dominance of online booking, a significant percentage of OTA revenue comes from phone bookings -- particularly for complex itineraries. Multi-city trips. Round-the-world tickets. Honeymoon packages with multiple hotels and experiences. Corporate travel with specific airline and hotel requirements. Group bookings for conferences and events. These are high-value transactions -- often £5,000 to £50,000+ -- where the customer wants to talk through options. AI voice agents handle the availability checks, pricing, and itinerary assembly. When the customer is ready, payment is captured mid-call: deposit for the package, with balance payments scheduled via tokenised card. The alternative -- "I'll send you an invoice" -- introduces days of delay on a high-value booking that a competitor could close in minutes. ### Multi-Currency at OTA Scale An OTA serves customers globally. A German customer books a Bali resort through a UK-based OTA. The customer pays in euros. The OTA takes commission in pounds. The resort settles in Indonesian rupiah. Now multiply that across thousands of bookings per day, dozens of currencies, and hundreds of suppliers. Each currency conversion is either a cost centre or a margin opportunity. A 50-basis-point difference on FX across £100M in annual bookings is £500K in margin. AI voice payment infrastructure must handle dynamic currency conversion at the point of capture -- the customer hears the price in their home currency, the payment layer converts and routes to the supplier's PSP in the supplier's currency, and the OTA's commission is calculated and settled in the OTA's reporting currency. ### OTA-Specific Architecture Requirements Beyond the core architecture (DTMF capture, multi-PSP routing, payment link fallback), OTAs need: - Split payments across suppliers -- a single customer payment distributed to multiple parties (airline, hotel, transfer, insurance provider) with different settlement terms and currencies - Airline acquirer mandates -- IATA BSP/ARC compliance requires specific acquirers for ticket sales; the payment layer must route airline ticket payments to the mandated processor regardless of the OTA's preferred PSP - Supplier-level PSP configuration -- each hotel chain, airline, and supplier may require a different gateway; configuration at the supplier level, not just the region level - Tokenisation for instalment payments -- deposit now, balance later; the card captured during the AI voice call produces a token used for scheduled balance payments without the customer calling again - Chargeback management across PSPs -- travel has among the highest chargeback rates in e-commerce; the payment layer must support dispute evidence submission and representment across whichever PSP processed the original transaction For the complete picture of OTA and travel platform payment infrastructure beyond AI voice, see Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure. ## The Architecture Hotel and travel AI voice payments require a specific architecture. Generic payment APIs -- designed for web checkout -- don't work in a voice context. ### DTMF Capture with Tone Masking Card data is entered via the guest's phone keypad during the AI conversation. DTMF tones are captured within a PCI DSS Level 1 certified environment and stripped from the audio stream in real time. The AI model never sees card data. Call recordings are clean. The hotel's property management system, CRM, and telephony infrastructure stay outside PCI scope for cardholder data. Tone masking must happen at the telephony layer -- real-time, before the audio reaches any other system. Post-processing approaches (stripping tones from recordings after the fact) don't satisfy PCI requirements. The tones must never be in the stream in the first place. For the guest, the experience is seamless. They hear the AI agent's voice throughout. They type on their keypad. The conversation continues without interruption. ### Multi-PSP Coverage Per Property and Region The payment layer routes each transaction to the correct PSP based on the hotel chain's configuration: - By region: European properties route to Adyen, US to Worldpay, APAC to a regional acquirer - By brand: A hotel group's luxury brand may use a different acquirer than its economy brand - By payment method: Card transactions to one PSP, local payment methods (Alipay, iDEAL, PIX) to another - By supplier: OTAs routing airline payments to the airline's mandated acquirer, hotel payments to the hotel's PSP New PSPs are added through configuration, not code. The AI agent doesn't know which PSP is processing a given payment -- and doesn't need to. It calls the payment API; the layer handles the routing. This is what it means to be PSP-neutral at the AI agent layer. The hotel keeps its existing PSP relationships. The AI agent works with all of them. ### Multi-Currency Handling Travel is inherently cross-border. A French guest booking a Thai hotel through a UK OTA involves three currencies. The payment layer handles: - Guest-facing: Dynamic currency conversion -- the guest pays in their home currency - Property-level: Settlement in the property's local currency - Chain/OTA level: Reporting in the group's reporting currency Each conversion is transparent. FX rates are visible in the merchant portal. Competitive rates matter -- a 50-basis-point difference on currency conversion across millions of bookings directly impacts margin. ### Pre-Authorisation, Delayed Capture, and Incremental Auth Hotels don't work like e-commerce. Payment flows are multi-step: - Pre-auth at booking: Hold funds for the room deposit without capturing - Capture at check-in: Charge the confirmed amount when the guest arrives - Incremental auth during stay: Additional holds for incidentals (minibar, room service, damage deposit) - Partial capture at checkout: Final charge may differ from the original hold - Auto-release: Unused holds expire based on configurable timeouts Any payment infrastructure that only supports simple charge-and-capture is fundamentally incomplete for hospitality. Pre-auth, delayed capture, incremental auth, and partial capture are the default flow -- not edge cases. ### SMS Payment Link Fallback When DTMF isn't practical -- guest on a landline without a keypad, poor international line quality, guest preference for visual checkout -- the AI agent sends a branded payment link via SMS during the call. "I've just sent a payment link to your mobile. You can complete the payment there while we're on the line." The guest taps the link, sees a branded checkout page (hotel's brand, not a third-party page), and pays using cards, Apple Pay, Google Pay, or local payment methods. The result is returned to the AI agent. The conversation continues. This covers the full range of voice-to-payment scenarios without any card data entering the hotel's environment. For more on this approach, see PCI-Compliant Payments for Contact Centres. ### PMS and Booking System Integration Payment events -- authorisation, capture, refund, chargeback -- are pushed to the hotel's property management system via webhooks. Real-time folio updates when a deposit is captured. Automatic reconciliation across properties, brands, and PSPs through a single dashboard. The AI agent's booking system knows that a payment was successful before the call ends. The guest's folio is updated before they hang up. No manual reconciliation. No overnight batch processing. For OTAs and travel platforms, webhook integration connects to the booking engine -- payment status drives booking confirmation, ticket issuance, and supplier notification automatically. ## How It Works in Practice AI voice agent platforms integrate Shuttle's Voice Checkout via a single API. The voice agent handles the conversation. Shuttle handles the payment capture. The architecture is vendor-neutral on both sides: - Any AI voice agent platform. Shuttle works with whatever voice AI the hotel or travel platform deploys -- the same way it works with any telephony provider. Single API integration. No vendor lock-in on the AI side. - Any PSP. 40+ payment gateways supported through one integration. The hotel's treasury team keeps their existing PSP relationships. Regional routing, brand-level configuration, supplier mandates -- all handled through configuration. This is already proven in production across AI voice agent deployments in regulated industries -- where PCI compliance, multi-PSP routing, and audit requirements are at least as demanding as hospitality. The integration typically takes a single developer one to two weeks. PSP configuration and testing add another week. Compare that to building DTMF capture, PCI-certified infrastructure, and multi-PSP routing from scratch. ## What Hotels and Travel Platforms Should Evaluate If you're a hotel chain, OTA, or travel platform evaluating AI voice payment infrastructure: PCI DSS Level 1 certification -- the payment capture environment must be certified at the highest level. Not Level 2. Not "PCI compliant" without specifying the level. Level 1 -- the same standard that applies to Visa and Mastercard themselves. Hotel chains processing card data across hundreds of properties need this. PSP flexibility -- can your properties keep their existing PSP relationships? Can you route to different gateways per region, brand, or supplier? 40+ gateway support through a single integration prevents lock-in and satisfies corporate treasury mandates. DTMF capture quality -- tone suppression must happen in real time at the telephony layer. Not post-processing. Real-time masking ensures card data never enters the audio stream, recordings, or any hotel system. Multi-currency -- does it handle guest-pays-in-home-currency, property-settles-in-local-currency, chain-reports-in-reporting-currency? Travel payments are inherently multi-currency. Competitive FX rates that don't eat margin on every booking. Pre-authorisation and delayed capture -- can it handle hotel payment flows? Deposit at booking, capture at check-in, incremental auth during stay, partial capture at checkout. If the payment infrastructure only supports simple charge-and-capture, it doesn't work for hotels. SMS payment link fallback -- can the AI agent send a branded payment link during the call for guests who prefer visual checkout? This bridges voice and digital channels. PMS integration -- real-time webhook notifications to the property management system. Automatic folio updates. Cross-property reconciliation. White-label checkout -- guests see the hotel's brand throughout the payment experience. No redirects to third-party pages. Consistent with the booking flow. Scale -- can it deploy across hundreds of properties without per-property integration? Chain-level configuration that applies to all properties, with overrides where needed. Compliance documentation -- audit-ready data flows showing exactly where card data was captured and processed. ISO 27001 and SOC 2 alongside PCI DSS Level 1. ## FAQ How do AI voice agents capture hotel payments securely? The guest enters card details via their phone keypad (DTMF) during the AI conversation. The tones are intercepted by a PCI DSS Level 1 certified payment environment and stripped from the audio stream in real time. The AI model, call recordings, and hotel systems never see card data. The hotel's PCI scope for voice payments drops from SAQ-D to SAQ-A (roughly 20). What happens if the guest can't use DTMF? The AI agent sends a branded payment link via SMS. The guest completes payment on their device -- using cards, digital wallets, or local payment methods -- while the conversation continues. This handles guests on landlines without keypads, poor line quality situations, and guests who simply prefer a visual checkout. Can AI voice payments work with our existing hotel PSP? Yes. The payment layer supports 40+ PSPs through a single integration. Your existing PSP relationships stay intact. Different properties, regions, and brands can use different gateways -- all configured centrally, not coded per property. How does multi-currency work for international hotel guests? The guest pays in their preferred currency. The property settles in local currency. The chain reports in its reporting currency. Currency conversion is handled by the payment layer with transparent, competitive FX rates visible in the merchant portal. What PCI compliance level is needed for AI voice payments in hotels? PCI DSS Level 1 -- the highest certification tier. This is the standard for service providers handling card data. It ensures the DTMF capture environment meets the strictest security requirements. Hotels using a Level 1 certified payment layer for voice payments keep their own PCI scope at SAQ-A. How long does it take to deploy AI voice payments across a hotel chain? The payment layer integration takes one to two weeks for a single developer. PSP configuration and testing add another week. This is a single integration that works across all properties -- not a per-property deployment. Compare that to 12+ months and $2M+ for building PCI-certified voice payment infrastructure in-house. Does this work with our existing AI voice agent? Yes. The payment layer integrates with any AI voice agent platform via API. It's vendor-neutral -- the same way it's PSP-neutral. Whatever voice AI you've deployed (or plan to deploy), the payment capture infrastructure works alongside it. How do OTAs handle multi-supplier payment splitting with AI voice agents? The customer makes a single DTMF payment entry. The payment layer splits and routes the transaction behind the scenes -- airline portion to the airline's mandated acquirer, hotel portion to the hotel's PSP, transfer portion to the local provider. Each supplier's PSP requirements, settlement terms, and currency are handled through configuration. The AI agent and the customer see one payment; the payment layer handles the complexity. Can AI voice agents handle airline acquirer mandates for OTAs? Yes. Airlines operating through IATA require ticket payments to be processed through specific acquirers (BSP/ARC). The payment layer routes airline ticket payments to the mandated processor -- regardless of the OTA's preferred PSP for other transactions. This is configured at the supplier level, so each airline's requirements are met automatically. Capture payments in AI voice conversations -- across any hotel, any PSP, any currency. See how Shuttle connects AI voice agents to 40+ payment gateways with PCI DSS Level 1 compliance, DTMF capture, multi-currency, and pre-authorisation support. Live in weeks. Book a Call | See Voice Checkout ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Voice Payments Are an Architecture Decision, Not a Feature Request ### Navigating the Future of Travel Booking and Payments ### Sage Invoice Payments: How to Let Customers Pay Online ### Travel Payment Solutions: How Agencies Collect Payments Faster ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ## Links - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [travel platforms face at the infrastructure level](/guides/payments-for-travel-platforms) - [Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure](/guides/payments-for-travel-platforms) - [PSP-neutral](/guides/psp-neutral-vs-single-psp) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments) - [Book a Call](/contact) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) - [BlogNavigating the Future of Travel Booking and Payments→](/blog/navigating-the-future-of-travel-booking-and-payments/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogTravel Payment Solutions: How Agencies Collect Payments Faster→](/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) --- URL: https://www.shuttleglobal.com/guides/ai-voice-payments-insurance/ --- # AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk | Shuttle > Insurance Runs on Phone Calls. Phone Calls Don't Run on Payments. Insurance is one of the last industries where the phone is still the dominant customer... # AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk By Shuttle Team, December 23, 2025 ## Insurance Runs on Phone Calls. Phone Calls Don't Run on Payments. Insurance is one of the last industries where the phone is still the dominant customer channel. Renewals, claims, policy changes, new quotes -- customers call in. In the UK alone, insurers handle over 100 million customer calls annually. Every one of those calls is a potential payment moment. A renewal that could be confirmed and paid. A claims excess that could be collected. A policy adjustment that generates an additional premium. A new quote that could convert to a sale. But most of those payment moments are wasted. The agent discusses the amount, confirms the customer wants to pay, and then says: "I'll send you a link by email" or "You can pay on our website." The customer hangs up, intending to pay later. Some do. Many don't. Renewal rates drop. Collections extend. Revenue sits in limbo. The alternative -- agents taking card numbers verbally -- is worse. It works operationally but creates PCI exposure across the entire telephony environment. Call recordings contain card data. Agent workstations are in scope. The compliance cost alone can exceed $2M annually. AI voice agents change both sides of this equation. They handle the conversation and capture the payment -- without a human agent ever touching card data. ## What AI Voice Payments Look Like in Insurance An AI voice agent handles the entire interaction. Here's a renewal call: The phone rings. The AI agent answers: "Good morning, this is Acme Insurance. How can I help?" Customer: "I got a letter about my home insurance renewal. Policy HI-2847291." AI Agent: "I've found your policy. Your renewal quote is £342.50 for the year, with the same cover level as last year. Would you like to renew now?" Customer: "Yes, that's fine." AI Agent: "I can take your payment now. Please enter your 16-digit card number using your phone keypad." The customer types their card number on the keypad. The DTMF tones are intercepted by the PCI-certified payment layer -- stripped from the audio stream before they reach the AI model or any recording system. The agent prompts for expiry and CVV. Each entry is captured securely. AI Agent: "Thank you. I'm processing your payment of £342.50 now." The payment layer validates the card, routes the transaction to the insurer's configured PSP (Worldpay, in this case), and processes the payment. A result is returned to the AI agent via API. AI Agent: "Your payment has been processed. Policy HI-2847291 is renewed through 15 March 2027. You'll receive a confirmation by email. Is there anything else I can help with?" Total call duration: under 3 minutes. Human involvement: none. Card data in the insurer's systems: none. ## Why Insurance Needs This Now ### Renewal Rates Are Under Pressure The moment between "your renewal is due" and "payment received" is where insurers lose customers. Every friction point in that gap -- logging into a portal, navigating a website, calling back during business hours -- reduces the probability of renewal. AI voice agents compress that gap to zero. The customer calls about their renewal (or the AI calls them), the amount is confirmed, and payment happens in the same conversation. No second step. No follow-up email. No "I'll do it later." For insurers processing millions of renewals annually, even a small improvement in renewal completion rates translates to significant premium retention. ### Contact Centre Costs Are Escalating Insurance contact centres are expensive to run. Agent salaries, training, compliance monitoring, quality assurance -- and a significant portion of call volume is routine payment collection that doesn't require human judgement. AI voice agents handle these calls at a fraction of the cost. Renewals, top-ups, instalment payments, excess collection -- all automatable. The human agents focus on complex claims, complaints, and high-value conversations where empathy and expertise matter. ### Regulatory Scrutiny on PCI Is Increasing The FCA, PRA, and insurance regulators are increasingly focused on data handling practices. PCI non-compliance isn't just a payment industry problem -- it's a regulatory risk that can trigger broader supervisory action. AI voice payments with proper architecture (card data captured in a PCI-certified environment, never entering the insurer's systems) provide a clean compliance posture. The insurer's PCI scope for voice payments drops to SAQ-A. Auditors can see exactly where card data flows and where it doesn't. ### The Phone Isn't Going Away Despite digital transformation efforts, insurance customers continue to prefer the phone for complex interactions. Policy questions, claims, renewals with coverage changes -- these conversations benefit from dialogue, not forms. The question isn't whether to invest in phone-based customer service. It's whether those phone interactions can also capture payments efficiently and compliantly. AI voice agents make the answer yes. ## Insurance Payment Scenarios ### Premium Renewals (Inbound and Outbound) Inbound: Customer calls about a renewal notice. AI agent confirms the quote, answers questions about coverage, and captures payment. Outbound: AI agent calls customers approaching renewal date. "Hi, this is Acme Insurance calling about your home insurance renewal due on 28 February. Your renewal quote is £342.50 -- would you like to renew now?" Outbound AI calls for renewals are a significant opportunity. Most insurers send letters and emails. Few call proactively. An AI agent that calls, confirms, and collects payment in a single interaction can dramatically improve renewal rates. ### Claims Excess Collection A policyholder calls to report a claim. The AI agent captures claim details, confirms the excess amount, and collects it during the same call. No separate payment step. No delay waiting for an invoice. The excess is paid before the claim begins processing. ### Instalment Payments Monthly premium instalments fail -- cards expire, insufficient funds, account changes. AI voice agents can handle failed payment follow-up: call the customer, confirm the outstanding amount, capture an updated card, and re-establish the payment schedule. Automated, PCI-compliant, and faster than waiting for a customer to respond to a dunning email. ### Mid-Term Adjustments A policyholder adds a driver, increases coverage, or changes their vehicle. The adjustment generates an additional premium. The AI agent can calculate (or retrieve) the adjustment amount and collect it during the same call -- closing the loop immediately. ### New Business Quote-to-Bind An AI chat or voice agent handles a new business enquiry, presents a quote, and when the customer accepts, captures payment to bind the policy. This is the highest-value scenario -- converting a quote to a paying policy in a single interaction with zero human involvement. For how this works on chat channels, see Chat Agent Payments: How AI Closes Sales Without a Human Handoff. ## The Architecture for Insurance Insurance AI voice payments require a specific architecture. Generic payment APIs -- designed for web checkout -- don't work. ### PCI-Certified DTMF Capture Card data is entered via the customer's phone keypad. DTMF tones are captured within a PCI DSS Level 1 certified environment and stripped from the audio stream. The AI model, call recordings, analytics systems, and the insurer's infrastructure never see raw card data. This is the mechanism that limits the insurer's PCI scope. Without it, every system that touches the audio stream is a PCI surface. ### PSP-Neutral Routing Enterprise insurers mandate their PSP. Carrier A uses Worldpay. Carrier B uses Adyen. Carrier C uses a regional acquirer mandated by their treasury team. The payment layer must route each transaction to the correct PSP based on the insurer's configuration -- without the AI agent or the platform needing to know which gateway is processing a given payment. This is handled through a single integration to a PSP-neutral layer that supports 40+ gateways. For insurance platforms serving multiple carriers (like INSTANDA), this is non-negotiable. See Payments for Insurance Platforms for the broader platform perspective. For the wider payment surface beyond voice -- premium collection, mandates and claims disbursement -- see Payments for Insurance Carriers and MGA Platforms. ### Tokenisation for Recurring Payments A card captured during an AI voice call should produce a reusable token. That token is used for future instalment payments, renewal auto-collection, and cross-channel transactions (if the customer later pays via web or payment link). One capture, multiple uses. ### SMS Payment Link Fallback Not every customer will use their keypad. For customers who prefer a visual checkout, the AI agent sends a branded payment link via SMS during the call: "I've just sent a payment link to your mobile. You can complete payment there while we're on the line." The customer pays on their device. The result is returned to the AI agent. The conversation continues. ### Compliance Documentation Regulated insurers need audit trails. The payment layer must provide clear documentation of: where card data was captured, which PCI-certified environment processed it, which PSP handled the transaction, and confirmation that no card data entered the insurer's systems. This documentation supports FCA, PRA, and PCI audit requirements. ## The PolyAI Proof Point This isn't theoretical. AI voice agents are processing payments in regulated industries today. PolyAI -- whose AI voice agents handle hundreds of millions of conversations across insurance, financial services, and utilities -- uses Shuttle as their payment infrastructure layer. The results: - 75% voice payment completion rate -- customers who are asked to pay, do - Zero human handoffs -- the AI handles the entire conversation including payment - Multi-PSP support -- each enterprise customer's preferred gateway is supported - PCI DSS Level 1 compliance -- card data never enters PolyAI's or the enterprise's systems > "Shuttle let us treat legacy payment providers as a modern SaaS service. It enabled us to support the gateways our customers required and fully automate high-value transactions across regulated industries." -- Nathan Liu, PolyAI For the full technical deep dive on PolyAI's architecture, see AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation. ## What to Evaluate If you're an insurer, MGA, or insurance platform evaluating AI voice payment infrastructure: PCI DSS Level 1 certification -- the payment capture environment must be certified at the highest level. Insurance regulators will ask. PSP flexibility -- can your enterprise carriers bring their own PSP? 40+ gateway support through a single integration prevents lock-in. DTMF capture quality -- tone suppression must happen at the telephony layer, not in post-processing. Real-time masking ensures clean call recordings. Tokenisation -- cards captured via voice should produce tokens usable across channels and for recurring payments. SMS fallback -- payment links sent mid-call for customers who prefer visual checkout. Compliance documentation -- audit-ready data flows showing exactly where card data was captured and processed. ISO 27001 and SOC 2 alongside PCI DSS Level 1. Integration speed -- weeks, not months. Insurance platforms can't afford 12-month payment infrastructure projects. ## FAQ Can AI voice agents handle complex insurance payment scenarios? Yes. AI voice agents can process renewals, collect claims excesses, handle instalment payments, and capture mid-term adjustment premiums. The AI manages the conversation; the payment layer handles the transaction. Complex scenarios like multi-policy renewals or split payments are handled through the AI's conversational logic. Is this compliant with FCA and insurance regulations? The payment architecture is designed for regulated industries. Card data is captured in a PCI DSS Level 1 certified environment and never enters the insurer's systems. The insurer's PCI scope drops to SAQ-A. Compliance documentation supports FCA, PRA, and PCI audit requirements. What about customers who don't want to pay over the phone? The AI agent sends a branded payment link via SMS. The customer completes payment on their device -- using cards, Apple Pay, Google Pay, or bank transfer -- while the conversation continues. This bridges voice and digital channels. How does this work with existing contact centre infrastructure? AI voice payment infrastructure integrates with existing telephony -- Twilio, SIP-based carriers, and major CCaaS platforms. It doesn't require replacing your phone system. It sits alongside your existing infrastructure, adding payment capture capability to AI-handled calls. What completion rates can we expect? PolyAI achieves a 75% voice payment completion rate with zero human handoffs in production deployments across regulated industries. Rates vary by scenario, but the key driver is capturing payment at the moment of intent -- during the conversation, not after. Automate insurance payment collection -- without the compliance burden. See how Shuttle connects AI voice agents to 40+ payment gateways with PCI DSS Level 1 compliance, DTMF capture, tokenisation, and multi-currency support. Live in weeks. Book a Call | See Voice Checkout ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Voice Payments Are an Architecture Decision, Not a Feature Request ### Why Insurance Call Centres Still Can't Take a Secure Payment ### Sage Invoice Payments: How to Let Customers Pay Online ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### The Future of Voice Commerce: From IVR to Intelligent Payments ## Links - [DTMF tones](/guides/dtmf-payments/) - [Chat Agent Payments: How AI Closes Sales Without a Human Handoff](/guides/chat-agent-payments) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payments for Insurance Platforms](/guides/payments-for-insurance-platforms) - [Payments for Insurance Carriers and MGA Platforms](/guides/payments-for-insurance-carriers-mga/) - [AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation](/guides/ai-voice-agents-payments) - [Book a Call](/contact) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) - [BlogWhy Insurance Call Centres Still Can't Take a Secure Payment→](/blog/insurance-call-centre-payments/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogThe Future of Voice Commerce: From IVR to Intelligent Payments→](/blog/the-future-of-voice-commerce/) --- URL: https://www.shuttleglobal.com/guides/aircall-payments/ --- # How to Take Payments on Aircall: Secure Voice Payment Processing | Shuttle > Aircall is a cloud phone system popular with sales and support teams, particularly in the SMB and mid-market segments. # How to Take Payments on Aircall: Secure Voice Payment Processing By Shuttle Team, March 26, 2026 Aircall is a cloud phone system popular with sales and support teams, particularly in the SMB and mid-market segments. It integrates deeply with CRMs like HubSpot, Salesforce, and Zendesk, making it a go-to for teams that want call centre functionality without a full enterprise CCaaS platform. Aircall does not have native PCI-compliant payment processing. Marketplace DTMF options exist but are typically designed for small-scale operations and don't cover multi-PSP routing, multi-tenant operations, or enterprise-scale volumes. This guide covers how an Aircall-based operation can add enterprise-grade, PCI-compliant payment capture using Shuttle. Some of the world's biggest brands use Shuttle for voice payments. ## How Shuttle Adds Payments to Aircall Shuttle adds enterprise-grade, PCI-compliant card capture to your Aircall calls. When the customer is ready to pay, they enter their card on their phone keypad, the digits are captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Aircall recordings, your connected CRM, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Aircall specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Aircall call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Aircall have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Aircall recordings, your connected CRM, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Aircall, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Aircall have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on Aircall as normal. - Payment is triggered from your agent interface when the customer is ready to pay. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. - Result returned to your interface and your systems via webhook. - No card data in Aircall. The card digits never touch your Aircall recordings, your CRM, or your agent workstations. ## Multi-PSP Support Shuttle supports 30+ payment gateways with configurable routing: - By merchant: different clients or business units route to different gateways - By region: route by geography for optimal settlement and fees - By switching: automatic backup if the primary gateway is unavailable - By card type: route specific card brands through preferred processors Switching processors later is straightforward; gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, card data never enters your Aircall recordings, CRM data, transcriptions, or agent workstations. They stay out of PCI scope, keeping you on the lighter SAQ-A path. Full compliance documentation, including the AOC scope, is in the security docs. This is especially important for Aircall users with deep CRM integrations. Without a secure capture, card data from calls flows into HubSpot, Salesforce, or whatever CRM you've connected. With Shuttle, your CRM stays clean. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Professional Services Accountants, solicitors, and consultants using Aircall for client calls can collect invoice payments during the conversation. The client enters card details, payment confirms, and the call wraps up with everything handled. ### Insurance Brokers Small and mid-sized insurance brokers on Aircall handle premium collections and renewals. Shuttle captures payment during the call without PCI exposure. ### E-commerce Support E-commerce support teams on Aircall handling order issues, refunds, and re-orders can take replacement payments securely during the support call. ### Debt Collection Collections teams using Aircall capture payment at the moment of commitment, while the customer is still on the line. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Aircall plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Aircall specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Aircall call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Aircall have already done it. - A native Aircall integration is available as a paid project. If you would rather not build the bridge yourself, we were in talks to put a Shuttle app in the Aircall marketplace, and we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire Aircall conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Aircall integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Aircall. You'll need to be a Twilio customer and to build a small bridge connecting your workflow to Twilio, which customers running Aircall have already done. We can build a native Aircall integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### Does Shuttle affect my Aircall CRM integrations? No, and this is a key benefit. The card is captured in the secure Twilio Pay call, so your HubSpot, Salesforce, or Zendesk integrations never see card data. ### What does Shuttle cost? $0.20 per successful transaction for voice, no setup fees and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres: the complete guide - Talkdesk Payments: PCI-compliant payment capture for Talkdesk - RingCentral Payments: secure voice payments for RingCX and RingEX - Zendesk Payments: payment collection for Zendesk support teams - Voice Payments: comprehensive guide to voice payment capture ## Get Started Shuttle adds PCI-compliant payments to an Aircall-based operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Talkdesk Payments](/guides/talkdesk-payments/) - [RingCentral Payments](/guides/ringcentral-payments/) - [Zendesk Payments](/guides/zendesk-payments/) - [Voice Payments](/guides/voice-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/amazon-connect-payments/ --- # How to Take Payments on Amazon Connect: PCI-Compliant Voice Payments | Shuttle > Amazon Connect Has No Built-In Payment Capture Amazon Connect is AWS's cloud contact centre platform. # How to Take Payments on Amazon Connect: PCI-Compliant Voice Payments By Shuttle Team, March 2, 2026 ## Amazon Connect Has No Built-In Payment Capture Amazon Connect is AWS's cloud contact centre platform. It handles routing, IVR via Contact Flows, agent desktops, and integrates natively with the AWS ecosystem, Lambda, Lex, DynamoDB, S3. What it does not have is PCI-compliant payment capture. When a customer calls to pay a bill, renew a subscription, or settle an invoice, Amazon Connect has no native mechanism to securely collect card details during the call. The platform was built for conversation management, not payment processing. Some businesses have attempted to solve this with custom Lambda functions that capture DTMF input during Contact Flows. This technically works, but it creates a serious compliance problem. The card data passes through your AWS environment. It touches your Lambda execution context. It may be logged. It may be stored in CloudWatch. And your entire AWS infrastructure is now in PCI scope. That is not a payment solution. It is a liability. ## The Payment Gap in Amazon Connect Amazon Connect excels at what it was designed for: scalable, cloud-native contact centre operations with pay-per-minute pricing and deep AWS integration. But payment capture was never part of the design. Here is what is missing: No DTMF isolation. Amazon Connect can capture DTMF input in Contact Flows, but those tones are not isolated from the audio stream. If an agent is on the line, they hear the keypad tones. If the call is being recorded, and Amazon Connect records by default, the card number is in the recording. If you are using Contact Lens for analytics, card data is flowing through speech-to-text processing. No PCI-certified payment vault. There is no built-in mechanism to route card data to a secure, PCI-certified environment. Any card data captured via DTMF or speech is processed within your AWS account, which means your entire Connect instance and associated infrastructure falls into PCI scope. No multi-PSP routing. Even if you build a custom payment integration, it connects to a single gateway. Enterprise customers with existing relationships with Worldpay, Adyen, or Stripe cannot route transactions through their preferred PSP without additional custom development. No agent-assist payment flow. There is no mechanism for an agent to trigger a secure payment capture mid-call while staying on the line. The agent either takes the card details verbally (PCI nightmare) or transfers the customer to a separate IVR (customer experience nightmare). The result: most Amazon Connect deployments either avoid phone payments entirely, sending payment links after the call, or accept the PCI risk of handling card data in their AWS environment. ## How Shuttle Adds Payments to Amazon Connect Shuttle adds PCI-compliant card capture to your Amazon Connect payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Amazon Connect recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Amazon Connect specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Amazon Connect call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Amazon Connect have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Amazon Connect recordings, Contact Lens analytics, or your AWS environment. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Amazon Connect, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Amazon Connect have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on Amazon Connect as normal. The agent handles the conversation, resolves queries, and reaches the point where payment is needed. - Payment is triggered from your agent interface when the customer is ready to pay. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay, the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. Provider selection can be set per merchant and payment type. - Result returned to your interface and your systems via webhook. A tokenised reference is logged, no card data stored. - No card data in Amazon Connect. The card digits never touch your Connect recordings, Contact Lens, your CRM, or your AWS environment. ## Multi-PSP Support Enterprise Amazon Connect deployments typically serve multiple business units, brands, or regions, each with their own PSP relationship. Shuttle supports this. With 40+ PSP integrations, you can route transactions to different gateways based on: - Merchant identity: different business units use different PSPs - Region: UK transactions to Worldpay, European transactions to Adyen, US transactions to Stripe - Failover: if the primary gateway is down, you can move the affected payment types to another connected gateway - Card type: Shuttle does not route by card scheme; provider selection is per payment type Switching processors later is straightforward, gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification in the payment card industry. Because the card is captured in the secure Twilio Pay call, your PCI scope can drop to SAQ-A: the lightest self-assessment questionnaire. This is because: - Card data never enters your AWS environment - Card digits never reach Amazon Connect recordings - Call recordings contain no cardholder data - Contact Lens and other analytics tools process no card information - Your agents never hear, see, or handle card numbers Compare this to the alternative: building custom Lambda functions that process card data puts your entire Amazon Connect instance, your AWS account, your network, and your agent workstations in scope for SAQ-D: 300+ requirements, annual QSA audits, and significant ongoing compliance costs. The cost difference between SAQ-A and SAQ-D compliance is typically six figures annually. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). Full compliance documentation is in the security docs. ## Use Cases ### Insurance Premium Collection Insurance contact centres handle thousands of premium payments daily. Customers call to renew policies, adjust cover, or make one-off payments. With Shuttle on an Amazon Connect operation, agents collect payments mid-call without breaking the conversation, with no PCI exposure. ### Utility Bill Payments Utility companies running Amazon Connect can add secure bill payment to their agent flows. Customers call about a query, the agent resolves it, and payment happens on the same call. ### Debt Collection Collections agencies need to capture payment commitments while the debtor is engaged. Transferring to a separate system loses the moment. Shuttle allows agents to take immediate payment or set up payment plans during the collection call, all PCI-compliant. ### Travel and Hospitality Travel companies processing bookings, upgrades, and ancillary purchases through Amazon Connect can capture payment at the point of commitment. The customer confirms, enters their card via keypad, and the booking is confirmed in one call. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Amazon Connect plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Amazon Connect specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Amazon Connect call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Amazon Connect have already done it. - A native Amazon Connect integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Amazon Connect integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Amazon Connect. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Amazon Connect have already done. We can build a native Amazon Connect integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can I use Shuttle with Amazon Connect's AI features? Because card data is captured in the Twilio Pay call and never enters your AWS environment, Contact Lens can continue processing call recordings without PCI concerns. The card capture itself runs via Twilio Pay, not inside Connect. ### What happens if the payment fails? The agent sees the decline reason in real time and can prompt the customer to retry with a different card or payment method. ### Is there a per-seat or per-agent fee? No. Shuttle charges $0.20 per successful transaction with no setup fees and no per-seat fees. You pay only for successful payment captures. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the complete guide to secure contact centre payments - Twilio Pay Connectors, how Shuttle works with Twilio's payment infrastructure - Voice Payments, the definitive guide to taking payments over voice channels - AI Voice Agent PCI Payments, adding payment capture to AI-powered voice agents - Voice Checkout, Shuttle's voice payment product ## Get Started Shuttle adds PCI-compliant payments to an Amazon Connect operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. Talk to our team about adding secure payment capture to your Amazon Connect deployment, or explore Voice Checkout to see how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Shuttle vs Stripe Connect ### Stripe Connect Alternatives for Platforms ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### 5 Stripe Connect Limitations That Force Platforms to Switch ### Sage Invoice Payments: How to Let Customers Pay Online ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [40+ PSP integrations](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Checkout](/platforms/voice-checkout/) - [Talk to our team](/contact/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [AlternativeStripe Connect Alternatives for Platforms→](/alternatives/stripe-connect/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [Blog5 Stripe Connect Limitations That Force Platforms to Switch→](/blog/stripe-connect-limitations/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) --- URL: https://www.shuttleglobal.com/guides/authorize-net-quickbooks/ --- # Authorize.net + QuickBooks Integration: Accept Invoice Payments Online | Shuttle > Authorize.net is one of the most widely used payment gateways in the United States -- and a significant number of Authorize.net merchants also run their... # Authorize.net + QuickBooks Integration: Accept Invoice Payments Online By Shuttle Team, February 16, 2026 Authorize.net is one of the most widely used payment gateways in the United States -- and a significant number of Authorize.net merchants also run their books on QuickBooks Online. But connecting the two has always been harder than it should be. QuickBooks doesn't natively support Authorize.net as a payment processor. If you want a "Pay Now" button on your invoices, Intuit wants you to use QuickBooks Payments -- their own gateway. That means running two payment processors, two sets of fees, and two reconciliation workflows. This guide shows how to connect Authorize.net directly to QuickBooks Online through Shuttle -- so customers can pay invoices by card, and payments are automatically recorded in QuickBooks. No second gateway. No manual matching. ## Why QuickBooks and Authorize.net Don't Connect Natively QuickBooks Payments is Intuit's proprietary payment processor. It's the only gateway that gets native "Pay Now" button treatment on QuickBooks invoices. This creates a problem for businesses that already use Authorize.net: - You're paying two sets of processing fees -- Authorize.net for most transactions, QuickBooks Payments for invoice payments - Reconciliation is split -- some payments come through Authorize.net, others through Intuit, and you're manually matching both - You lose your negotiated rates -- Authorize.net merchants often have custom pricing built over years; QuickBooks Payments charges its standard rates - Your reporting is fragmented -- transaction history lives in two places The typical workaround is either accepting manual bank transfers (slow, no auto-reconciliation) or switching fully to QuickBooks Payments (losing your Authorize.net relationship). Neither is good. ## The Solution: Shuttle Connects Authorize.net to QuickBooks Shuttle's QuickBooks Online Invoice Payments app bridges the gap. It connects your Authorize.net account to QuickBooks and adds a payment link to your invoices. How it works: - Install the app and connect to QuickBooks Online - Enter your Authorize.net API credentials (API Login ID and Transaction Key) - Configure features (saved cards, partial payments, email notifications) - Paste the payment link into your QuickBooks invoice template - Customers click the link, pay by card on a secure checkout page - Payment is processed through Authorize.net - Payment is auto-recorded in QuickBooks against the correct invoice Your Authorize.net account, rates, and settlement remain exactly as they are. Shuttle sits between QuickBooks and Authorize.net, handling the payment capture and reconciliation. ## Setup Guide: Authorize.net + QuickBooks via Shuttle ### Prerequisites - A QuickBooks Online account (Simple Start, Essentials, Plus, or Advanced) - An active Authorize.net merchant account - Your Authorize.net API Login ID and Transaction Key ### Step 1: Install the Shuttle App Go to shuttleglobal.com/quickbooks-online and click "Get App." You'll be redirected to authorise QuickBooks access -- standard OAuth flow. Grant the required permissions. ### Step 2: Connect Authorize.net In the Shuttle dashboard, select Authorize.net as your payment gateway. Enter: - API Login ID -- found in your Authorize.net account under Account → Settings → API Credentials & Keys - Transaction Key -- generated from the same location Shuttle validates the credentials immediately. If they're correct, you'll see a green confirmation. ### Step 3: Configure Payment Settings Enable the features that matter to your business: - Saved cards -- let repeat customers save card details for faster future payments. Tokenised securely via Authorize.net's Customer Information Manager (CIM). - Partial payments -- accept deposits or instalment payments against invoices. The outstanding balance updates in QuickBooks automatically. - Email notifications -- get an email the moment a payment is received. Configurable to any email address. - Custom branding (Basic plan, $16/month) -- add your logo to the checkout page and use a custom payment URL. ### Step 4: Add Payment Link to Invoices Copy your unique payment link from the Shuttle dashboard. In QuickBooks Online: - Go to Settings → Custom Form Styles - Edit your invoice template - In the message/notes section, paste: "Pay online: [your payment link]" Every invoice you send now includes a clickable payment link. Customers on desktop or mobile can tap and pay. Alternatively, paste the link into individual invoices when you want to offer online payment selectively. ## What Happens When a Customer Pays - Customer opens your QuickBooks invoice via email - They click the payment link - A secure checkout page opens (Shuttle-hosted, PCI DSS Level 1) - They enter card details or use a saved card - Transaction is processed through your Authorize.net account - Funds settle to your Authorize.net merchant account (your usual rates and timeline) - The payment is automatically recorded in QuickBooks -- invoice marked as "Paid" The entire flow from customer click to QuickBooks reconciliation is automatic. No manual intervention. ## Authorize.net Features That Work Through Shuttle Authorize.net Feature Supported via Shuttle Card processing (Visa, MC, Amex, Discover) Customer Information Manager (saved cards) Address Verification Service (AVS) Card code verification (CVV) Fraud detection suite Yes -- your Authorize.net fraud settings apply Recurring billing via Authorize.net ARB Not directly -- use Shuttle's partial payments for instalments eCheck / ACH Depends on configuration Level 2/3 data Yes -- passed through where applicable Your existing Authorize.net fraud filters, velocity checks, and security settings remain active. Shuttle processes the transaction through your account -- it's your Authorize.net configuration that governs the rules. ## Pricing Shuttle Free plan: - Auto-record payments in QuickBooks - Saved cards - Partial payments - Email notifications - PCI DSS Level 1 compliant - No Shuttle transaction fee (your Authorize.net rates apply) Shuttle Basic plan ($16/month): - Everything in Free - Your logo on the checkout page - Custom payment URL - No advertising on checkout - Email support - 25% discount if paid annually Authorize.net fees remain yours. Shuttle doesn't add to or change your Authorize.net processing rates. Your standard per-transaction fees apply as normal. ## Common Questions ### Will this affect my Authorize.net account? No. Shuttle processes transactions through your existing Authorize.net account using the standard payment gateway API. Your account, rates, settlement, and reporting remain unchanged. Transactions processed via Shuttle appear in your Authorize.net reporting alongside all other transactions. ### Can I use both QuickBooks Payments and Authorize.net via Shuttle? Technically yes -- QuickBooks Payments for native "Pay Now" button and Authorize.net via Shuttle for payment links. But this creates the dual-stack problem. Most merchants find it cleaner to use Shuttle exclusively, since it provides auto-reconciliation through your preferred gateway. ### Does this work with Authorize.net sandbox/test accounts? Yes. You can connect a sandbox Authorize.net account for testing before going live. Process test transactions, verify auto-reconciliation in QuickBooks, then switch to your production credentials. ### What if I also use Authorize.net for my website or POS? No conflict. The Shuttle integration uses your Authorize.net account for invoice payment links only. Your existing website checkout, POS, or any other Authorize.net integrations continue to work independently. ### Is Authorize.net CIM (saved cards) PCI compliant through Shuttle? Yes. Shuttle is a PCI DSS Level 1 service provider. Card data is tokenised during the checkout flow. Saved card tokens are stored via Authorize.net's Customer Information Manager -- the most secure tokenisation method available through Authorize.net. ### I'm in the UK/EU -- can I use this? Authorize.net primarily serves the US market. If you process payments internationally, check whether your Authorize.net account supports international transactions. Alternatively, if you use a gateway like Worldpay or Stripe for international transactions, Shuttle connects to those as well -- see our QuickBooks invoice payments guide for the full list. ## Related Guides - How to Accept Payments on QuickBooks Invoices - QuickBooks Payment Links: Add Pay Now to Any Invoice - Payment Links for Authorize.net - Links Checkout for Merchants - What Is Embedded Payments? - Authorize.net vs Stripe: Which Payment Gateway? - Stripe + QuickBooks Integration -- accept invoice payments via Stripe - Worldpay + QuickBooks Integration -- pay invoices through Worldpay - Braintree + QuickBooks Integration -- accept payments via Braintree (PayPal + cards) - PayPal + QuickBooks Integration -- add PayPal to QuickBooks invoices ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### Authorize.net QuickBooks Integration: Full Guide ### Authorize.net Payment Links: Create & Send Payment Links ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### QuickBooks ACH Payments: Setup, Fees & Tips ## Links - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [QuickBooks invoice payments guide](/guides/quickbooks-invoice-payments/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Payment Links for Authorize.net](/blog/payment-links-for-authorize-net/) - [Links Checkout for Merchants](/merchants/links-checkout/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [Authorize.net vs Stripe: Which Payment Gateway?](/guides/authorize-net-vs-stripe/) - [Stripe + QuickBooks Integration](/guides/quickbooks-stripe-payments/) - [Worldpay + QuickBooks Integration](/guides/quickbooks-worldpay-payments/) - [Braintree + QuickBooks Integration](/guides/quickbooks-braintree-payments/) - [PayPal + QuickBooks Integration](/guides/quickbooks-paypal-payments/) - [See Links Checkout](/merchants/links-checkout/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogAuthorize.net Payment Links: Create & Send Payment Links→](/blog/payment-links-for-authorize-net/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) --- URL: https://www.shuttleglobal.com/guides/authorize-net-twilio-integration/ --- # How to Connect Authorize.net to Twilio for Voice & IVR Payments | Shuttle > Authorize.net doesn't natively connect to Twilio for voice payments. If you want to process Authorize.net transactions during a phone call -- via IVR,... # How to Connect Authorize.net to Twilio for Voice & IVR Payments By Shuttle Team, March 22, 2026 Authorize.net doesn't natively connect to Twilio for voice payments. If you want to process Authorize.net transactions during a phone call -- via IVR, agent-assisted, or AI voice agent -- you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Authorize.net (and 30+ other gateways) to Twilio's `` verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Authorize.net + Twilio Don't Connect Directly Authorize.net is one of the most widely deployed payment gateways in the US, powering hundreds of thousands of small and mid-size businesses. It handles card-present and card-not-present transactions, recurring billing, and eCheck processing. Twilio is built for voice and messaging. Its `` verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's `` needs a Pay Connector to route captured card data to a payment gateway. Authorize.net isn't one of Twilio's built-in connectors -- there's no native integration between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's `` verb and routes it to Authorize.net's API for processing. One integration connects the two platforms. ## How It Works ``` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Authorize.net (processing) → Result ``` - Caller reaches payment step. Your Twilio call flow -- IVR, Studio, or custom TwiML -- triggers the `` verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Authorize.net. The connector creates an Authorize.net transaction request, processes the payment, and handles the response. - Result returned to your call flow. Your webhook receives the Authorize.net transaction ID, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An Authorize.net account with API credentials (API Login ID + Transaction Key) - A Shuttle account (free to create -- you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Authorize.net Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Authorize.net - API Login ID: Your Authorize.net API Login ID - Transaction Key: Your Authorize.net Transaction Key - Currency: Set your default (USD) - Environment: Live or Sandbox Save the profile. Shuttle now has a live connection to your Authorize.net account. ### Step 3: Configure Your Twilio Call Flow Add the `` verb to your TwiML or Twilio Studio flow: ```xml Please enter your card number followed by the pound key. ``` ### Step 4: Handle the Payment Result Twilio sends a POST to your `action` URL with the payment result: ```json "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-3456", "PaymentCardType": "visa", "PaymentConfirmationCode": "AUTHNET-TXN-123...", "ProfileId": "your-shuttle-profile-id" ``` Use the `PaymentConfirmationCode` to look up the transaction in Authorize.net's Merchant Interface. ### Step 5: Test Use Authorize.net's sandbox environment and Twilio's test credentials to verify the flow end-to-end. Authorize.net sandbox test card: `4111 1111 1111 1111` (Visa). ## What You Can Do With Authorize.net + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Authorize.net processes, done. Ideal for service payments, account top-ups, and bill pay. ### Authorise Now, Capture Later Place a hold on the card during the call. Capture the payment later via Authorize.net -- useful for deposits or variable-amount transactions. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Authorize.net's Customer Information Manager (CIM) and returns a reusable token. Use it for future payments across any channel. The card data is never stored in your systems. ### Recurring Billing Combine tokenisation with Authorize.net's Automated Recurring Billing (ARB). Capture the card securely over a phone call, then use the token for ongoing charges without the customer needing to call again. ## Multi-PSP: Beyond Authorize.net One of the key advantages of using Shuttle rather than an Authorize.net-only connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway -- route transactions to Authorize.net for US customers and a different gateway for international - Serve enterprise customers who mandate a specific PSP - Want a backup gateway -- if Authorize.net is down, you can move the affected payment types to another connected gateway - Expand internationally where Authorize.net isn't available You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. ## PCI Compliance The Authorize.net + Twilio integration via Shuttle limits your PCI scope: Layer | PCI handled by DTMF capture & suppression | Twilio Card data processing | Shuttle (PCI DSS Level 1) Payment processing | Authorize.net (PCI DSS Level 1) Your systems | No card data -- SAQ-A Card data flows from Twilio → Shuttle → Authorize.net. Your application only receives redacted data (last 4 digits, card brand, transaction ID). You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Authorize.net to Twilio without Shuttle? Twilio doesn't have a built-in Authorize.net Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework -- handling PCI compliance yourself. Shuttle provides a pre-built, PCI-certified connector. Does this work with Twilio Studio? Yes. Twilio Studio supports the `` widget. Configure it with `shuttle-pay-connector` as the connector and the payment flow works within your Studio flow. Can I use Authorize.net's Customer Information Manager (CIM)? Yes. When tokenising cards via Shuttle, the token integrates with Authorize.net's CIM for stored payment methods, enabling future recurring or on-demand charges. What does it cost? Shuttle charges $0.20 per successful transaction. Authorize.net's standard gateway fees apply on top ($0.10/transaction + $25/month, or your negotiated rate). No Shuttle setup fees or monthly minimums. Can I process eChecks/ACH via Twilio? Shuttle's Twilio Pay Connector handles card payments captured via DTMF. For ACH/eCheck, you'd typically collect bank details through a different channel and process via Authorize.net directly. Can I switch from Authorize.net to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same -- no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments -- step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice Payments -- step-by-step Adyen + Twilio setup - How to Connect Worldpay to Twilio for Voice Payments -- step-by-step Worldpay + Twilio setup - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup Connect Authorize.net to Twilio in minutes with Shuttle's Pay Connector -- PCI DSS Level 1, $0.20/transaction, no setup fees. [Install on Twilio](/integrations/twilio-pay/) or [book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Authorize.net QuickBooks Integration: Full Guide ### Authorize.net Payment Links: Create & Send Payment Links ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [How to Connect Worldpay to Twilio for Voice Payments](/guides/worldpay-twilio-integration/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Book a Call](/discovery/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogAuthorize.net Payment Links: Create & Send Payment Links→](/blog/payment-links-for-authorize-net/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/authorize-net-vs-stripe/ --- # Authorize.net vs Stripe: Gateway Comparison for Businesses & Platforms | Shuttle > Authorize.net and Stripe are two of the most compared payment gateways. Here's the honest breakdown -- features, pricing, limitations, and when each one fits. # Authorize.net vs Stripe: Which Payment Gateway Should You Choose? By Shuttle Team, February 26, 2026 Authorize.net and Stripe are two of the most widely used payment gateways in North America -- but they were built in different eras, for different customers, with fundamentally different philosophies. Authorize.net has been processing payments since 1996. Now owned by Visa, it's a traditional gateway that connects to a separate merchant account. It's the default choice for many established businesses, especially those using accounting software like QuickBooks or working with a bank that provides a merchant account. Stripe launched in 2010 as an API-first platform that bundles gateway, processing, and merchant account into one service. It's become the default for developers, startups, and software platforms that want to embed payments. Choosing between them comes down to your technical capabilities, business model, and whether you need a standalone gateway or a full-stack payment platform. ## Side-by-Side Comparison ## Where Authorize.net Wins ### Existing merchant account relationships If your business already has a merchant account with favourable rates from an acquiring bank, Authorize.net lets you keep those rates. Stripe bundles its own processing, which means you're locked into Stripe's pricing. For high-volume merchants who have spent years negotiating interchange-plus rates with their acquirer, this is a genuine advantage. ### Lower effective cost at high volume Authorize.net's $25/month fee is offset by the fact that your processing costs are determined by your merchant account agreement, not by Authorize.net. At high transaction volumes, a well-negotiated merchant account plus Authorize.net's gateway fee can be meaningfully cheaper than Stripe's flat 2.9% + 30¢. ### QuickBooks and legacy integrations Authorize.net has deep integrations with QuickBooks, Sage, Xero, and other accounting/ERP systems. For businesses that rely on these integrations, Authorize.net slots in without disruption. Switching to Stripe would mean rebuilding those connections. ### Simplicity for non-technical teams Authorize.net's Virtual Terminal and merchant dashboard are designed for business operations teams, not developers. If your team needs to process phone orders, manage recurring billing, or handle refunds without touching code, Authorize.net's interface is more accessible than Stripe's developer-centric approach. ### Established trust with traditional businesses Authorize.net has processed payments for nearly 30 years. Many traditional businesses -- retail, professional services, healthcare -- trust it because they've used it for a decade or more. Switching costs are real, and "it works" is a valid reason to stay. ## Where Stripe Wins ### Developer experience This is Stripe's defining advantage. The API documentation, SDKs, test mode, webhooks, and developer tools are the industry benchmark. If you're building a custom checkout, embedding payments in a SaaS product, or integrating payments into a mobile app, Stripe gets you to production faster than any alternative. ### Global payment method coverage Authorize.net supports cards and ACH in the US and Canada. Stripe supports 40+ payment methods across 47+ countries -- including SEPA Direct Debit, iDEAL, Bancontact, BACS, Klarna, Afterpay, Apple Pay, and Google Pay. If you sell internationally or serve customers who prefer non-card payment methods, Stripe is the clear choice. ### All-in-one platform Stripe bundles gateway, processing, merchant account, billing, invoicing, fraud detection, issuing, and financial reporting into one platform. No separate merchant account application, no additional contracts, no integration between disparate systems. For businesses that want to move fast and minimise vendor management, this simplicity is valuable. ### Platform and marketplace tools Stripe Connect lets platforms onboard sub-merchants, split payments, and manage payouts -- which is why it's the default for many SaaS companies and marketplaces. Authorize.net has no equivalent. If you're building a platform that processes payments on behalf of other businesses, Stripe is purpose-built for this. ### Fraud detection Stripe Radar uses machine learning trained on billions of data points across the Stripe network to score transactions in real time. It's more sophisticated than Authorize.net's rule-based AFDS, particularly for card-not-present e-commerce transactions. ### Modern checkout experience Stripe's Payment Element and Checkout automatically adapt to the customer's location, device, and preferred payment method. The UX is polished and conversion-optimised. Authorize.net's hosted checkout works but feels dated by comparison. ## The Real Decision Framework The Authorize.net vs Stripe question often comes down to three factors: ### 1. Are you a developer or a business operations team? If you have engineers who will integrate and maintain the payment system, Stripe's API-first approach is almost always preferred. If payments are managed by a finance or operations team using dashboards and built-in tools, Authorize.net may be more practical. ### 2. Do you sell internationally? If your customers are exclusively in the US and Canada, Authorize.net works fine. The moment you need to accept SEPA payments in Europe, support Pix in Brazil, or offer local methods in Asia, Stripe is the only option of the two. ### 3. Do you already have a merchant account? If you have an existing merchant account with negotiated rates that beat Stripe's 2.9% + 30¢, Authorize.net lets you keep those economics. If you're starting fresh or processing low-to-moderate volume, Stripe's bundled approach is simpler and often comparable in total cost. ## When to Choose Authorize.net - You have an existing merchant account with competitive processing rates - Your business operates exclusively in the US or Canada - You need QuickBooks integration without rebuilding workflows - Your team prefers dashboard-based management over API integration - You process phone orders via Virtual Terminal regularly - You're in a vertical (healthcare, professional services) where Authorize.net is already the standard ## When to Choose Stripe - You're building a custom checkout or embedding payments in a software product - You sell internationally or need non-card payment methods - You want a platform/marketplace solution (Stripe Connect) - Developer experience and time-to-production matter - You need advanced fraud detection and analytics - You don't want to manage a separate merchant account ## When You Don't Need to Choose For platforms and software companies that serve merchants with diverse payment needs, the "Authorize.net vs Stripe" question becomes moot. Some merchants prefer Authorize.net because of existing integrations. Others want Stripe for its modern checkout. Enterprise clients may mandate Adyen or Worldpay. A PSP-neutral payment layer connects to both Authorize.net and Stripe -- and 40+ other gateways -- through a single integration. Merchants keep their preferred PSP, the platform keeps one integration across all transactions, and nobody has to compromise on their gateway choice. This is particularly relevant for platforms that have outgrown single-PSP solutions like Stripe Connect and need to support enterprise PSP mandates. ## Frequently Asked Questions Is Authorize.net cheaper than Stripe? It depends on volume. Authorize.net charges $25/month plus your merchant account's processing rates, which can be lower than Stripe's 2.9% + 30¢ at high volume. For low-volume businesses, Stripe's no-monthly-fee structure is often cheaper overall. Calculate the total cost for your specific transaction profile. Can I switch from Authorize.net to Stripe? Yes, but you'll need to migrate stored card tokens (which requires coordination between both providers), update your checkout integration, and potentially rebuild accounting integrations. Most migrations take 2-4 weeks of development time. Does Authorize.net work with Shopify? Authorize.net can work with Shopify via third-party integrations, but Shopify's native checkout uses Shopify Payments (powered by Stripe). For most Shopify merchants, using the native payment processing is simpler and cheaper than adding Authorize.net. Is Authorize.net secure? Yes. Authorize.net is PCI DSS validated, supports tokenisation via Customer Information Manager (CIM), and offers an Advanced Fraud Detection Suite. It's been processing payments securely since 1996. However, because it requires a separate merchant account, your total security posture depends on both Authorize.net and your acquiring bank's practices. Can I use both Authorize.net and Stripe? Yes. Some businesses use Authorize.net for phone orders and legacy integrations while using Stripe for their web checkout. Platforms that serve merchants using both can connect to each via a PSP-neutral payment layer rather than maintaining separate integrations. ## Related Reading - Authorize.net + QuickBooks Integration Guide - PSP-Neutral vs Single-PSP: Which Architecture Fits Your Platform? - When Your SaaS Outgrows Stripe Connect - Shuttle vs Stripe Connect - What Is Embedded Payments? - How to Choose a Payment Platform - Shuttle PSP Network -- including Authorize.net and Stripe Need a payment gateway? Shuttle connects to Authorize.net, Stripe, and 40+ other payment providers. Whether you're a merchant looking for payment links and checkout or a platform that needs to embed multi-PSP payments, we can help. For Merchants | For Platforms | Book a Discovery Call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Authorize.net Payment Links: Create & Send Payment Links ### Authorize.net QuickBooks Integration: Full Guide ### Stripe Connect Alternatives for Platforms ### 5 Stripe Connect Limitations That Force Platforms to Switch ### What Stripe's Unbundling Tells Us About the Future of Payments ## Links - [payment gateways](/blog/what-is-a-payment-gateway/) - [QuickBooks](/guides/authorize-net-quickbooks/) - [Stripe Connect](/payment-providers/stripe/) - [QuickBooks integration](/guides/authorize-net-quickbooks/) - [PSP-neutral payment layer](/guides/what-is-embedded-payments/) - [Stripe Connect](/vs/stripe-connect/) - [enterprise PSP mandates](/guides/enterprise-psp-mandates/) - [Authorize.net + QuickBooks Integration Guide](/guides/authorize-net-quickbooks/) - [PSP-Neutral vs Single-PSP: Which Architecture Fits Your Platform?](/guides/psp-neutral-vs-single-psp/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [How to Choose a Payment Platform](/guides/how-to-choose-payment-platform/) - [Shuttle PSP Network](/payment-providers/) - [Authorize.net](/payment-providers/authorize-net/) - [Stripe](/payment-providers/stripe/) - [payment links and checkout](/merchants/) - [embed multi-PSP payments](/platforms/) - [For Merchants](/merchants/) - [For Platforms](/platforms/) - [Book a Discovery Call](/discovery/) - [Book a Call](/discovery/) - [BlogAuthorize.net Payment Links: Create & Send Payment Links→](/blog/payment-links-for-authorize-net/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [AlternativeStripe Connect Alternatives for Platforms→](/alternatives/stripe-connect/) - [Blog5 Stripe Connect Limitations That Force Platforms to Switch→](/blog/stripe-connect-limitations/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) --- URL: https://www.shuttleglobal.com/guides/avaya-payments/ --- # How to Take Payments on Avaya: PCI-Compliant Contact Centre Payments | Shuttle > Avaya Does Not Have Native PCI-Compliant Payment Capture Avaya has been the backbone of enterprise contact centres for decades. # How to Take Payments on Avaya: PCI-Compliant Contact Centre Payments By Shuttle Team, February 28, 2026 ## Avaya Does Not Have Native PCI-Compliant Payment Capture Avaya has been the backbone of enterprise contact centres for decades. Avaya Aura, Avaya OneCloud CCaaS, and the Communication Manager platform handle millions of calls daily across some of the largest contact centre operations in the world. But Avaya was built for call management, not payment processing. There is no built-in mechanism to securely capture card details during a live call without exposing your agents, recordings, and infrastructure to PCI scope. This is a particularly acute problem for Avaya customers because many operate in heavily regulated industries (financial services, insurance, utilities, government) where PCI compliance is not optional and audit scrutiny is intense. ## The Payment Gap in Avaya Avaya environments range from fully on-premises Aura deployments to hybrid architectures mixing on-prem and cloud, to the newer Avaya Cloud Office and OneCloud CCaaS platforms. The payment gap exists across all of them. No secure card capture in the call flow. Avaya can route calls, queue them, record them, and provide IVR menus, but when a customer enters card digits via keypad during a call, those tones are audible to the agent and captured in the call recording. There is no native mechanism to keep card data out of the recorded stream while keeping the agent connected. Recording infrastructure captures everything. Avaya's call recording, whether through Avaya Workforce Engagement or third-party recorders like Verint or NICE, records the full audio stream by default. Pause-and-resume recording is technically possible, but it relies on agents remembering to pause at the right moment and resume after. In practice, compliance teams consistently find gaps: agents who forget, who pause late, or who resume too early. And even with pause-and-resume, the agent still hears the card number. Legacy infrastructure complicates payments. Many Avaya deployments run on older infrastructure: Session Border Controllers, Avaya Media Servers, proprietary SIP implementations. Bolting card capture directly onto this stack is not trivial and varies significantly between deployments. Migration uncertainty. Avaya's corporate restructuring has left many customers evaluating migration paths. Some are moving to Avaya's cloud offerings. Others are migrating to Genesys, Five9, or Amazon Connect. In either case, investing in a deeply coupled, Avaya-specific payment integration carries risk. You need a payment approach that works for your operation today and travels with you to whatever platform comes next. ## How Shuttle Adds Payments to Avaya Shuttle adds PCI-compliant card capture to your Avaya payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Avaya recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Avaya specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Avaya call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Avaya have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Avaya recordings, your recorder (Verint, NICE, or Avaya Workforce Engagement), or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links via SMS or email This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer completes payment on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Avaya, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Avaya have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - Call is handled normally. The customer calls in, is routed through Avaya, and speaks with an agent. The conversation proceeds as usual. - Payment is needed. The agent identifies that payment is required (a bill, a premium, a balance, a booking) and triggers payment from the Shuttle interface. - Card is captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card number, expiry, and CVV on the keypad, and the digits are captured inside Shuttle's certified environment, never your Avaya recordings. - Transaction is processed. Shuttle routes the payment to the appropriate PSP (Stripe, Adyen, Worldpay, Checkout.com, or any of 30+ supported gateways). Provider selection is configured per merchant and payment type. - Agent sees the result. The transaction result (approved, declined, error) is returned in real time via webhook. A tokenised reference is available for CRM logging. - Call continues. The agent confirms payment to the customer and continues the conversation. ## Multi-PSP Support Avaya is disproportionately deployed in large enterprises and regulated industries, organisations that typically have existing, long-standing PSP relationships. Migrating to a new payment gateway is rarely an option. Shuttle supports 40+ PSPs and allows provider selection to be configured per merchant or per business unit. This is critical for Avaya environments that serve multiple brands or divisions. Typical routing configurations for Avaya deployments: - UK operations route to Worldpay, European operations to Adyen - Different business divisions use different PSPs based on existing contracts - Backup gateway: if the primary gateway returns errors, you can move the affected payment types to another connected gateway - Card scheme routing: Amex transactions processed through a different gateway than Visa/Mastercard No PSP migration required. Your existing payment relationships stay intact. Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. For Avaya contact centres, this changes the compliance picture fundamentally: Without Shuttle: Card data passes through your Avaya infrastructure, telephony, recording, agent desktops, and network. Your entire environment is in PCI scope. You face SAQ-D, annual QSA audits, penetration testing, and significant ongoing compliance costs. For on-premises Avaya deployments with complex infrastructure, this is particularly burdensome. With Shuttle: Because the card is captured in the secure Twilio Pay call, card data never enters your Avaya environment. Recordings contain no card data. Agents never hear card numbers. Your PCI scope drops to SAQ-A, the lightest level, with minimal requirements. Full compliance documentation is in the security docs. This is especially important for Avaya customers in regulated industries where compliance audits are frequent and thorough. SAQ-A versus SAQ-D is typically a six-figure annual cost difference. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Financial Services Banks and building societies running Avaya handle card payments for loan repayments, account top-ups, and service fees. PCI compliance in financial services is subject to FCA oversight, and regulators increasingly scrutinise how card data is handled in contact centres. Shuttle removes the risk entirely. ### Insurance Insurance companies are among Avaya's largest customer base. Premium collection, policy renewals, and claims payments happen over the phone daily. Shuttle allows agents to collect payments mid-call without breaking the conversation or creating PCI exposure, critical for maintaining retention during renewal calls. ### Utilities Utility companies processing bill payments through Avaya contact centres need high-volume, reliable payment capture. Shuttle handles automated IVR payments for self-service callers and agent-assisted payments for more complex interactions, all via the same Twilio Pay capture. ### Government and Public Sector Local councils, NHS trusts, and government agencies running Avaya can add secure payment collection for council tax, parking fines, prescription charges, and service fees. Shuttle's SAQ-A compliance model simplifies the procurement and audit process significantly. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Avaya plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Avaya specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Avaya call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Avaya have already done it. - A native Avaya integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Avaya integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in your Avaya stack. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Avaya have already done. We can build a native Avaya integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### What if we are migrating away from Avaya? The payment leg runs through Twilio Pay, not coupled into your Avaya infrastructure, so the approach is independent of your telephony platform. If you are migrating from Avaya to Genesys, Five9, Amazon Connect, or another CCaaS platform, your Shuttle setup is not Avaya-specific and travels with you (provided you remain a Twilio customer for voice capture). ### How does Shuttle keep card data out of Avaya's call recording? The card is captured in a separate, secure Twilio Pay call rather than in the Avaya-recorded audio, so your recording platform (Avaya Workforce Engagement, Verint, NICE, or another solution) never receives card data. No pause-and-resume configuration is needed. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### What is the cost? $0.20 per successful transaction for voice, no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the complete guide to secure contact centre payments - Twilio Pay Connectors, how Shuttle integrates with Twilio's payment infrastructure - Voice Payments, the definitive guide to taking payments over voice channels - AI Voice Agent PCI Payments, adding payment capture to AI-powered voice agents - Voice Checkout, Shuttle's voice payment product ## Get Started Adding PCI-compliant payments to an Avaya operation does not require replacing your telephony infrastructure. Shuttle provides a Twilio-based payment layer that works alongside your existing Avaya deployment (on-prem, hybrid, or cloud) and your existing PSP relationships. We'll walk you through what's live today and the path for your setup. Talk to our team about adding secure payment capture to your Avaya contact centre, or explore Voice Checkout to see how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [40+ PSPs](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Checkout](/platforms/voice-checkout/) - [Talk to our team](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/b2b-payment-collection/ --- # How B2B Service Companies Collect Payments Faster | Shuttle > The B2B Payment Problem B2B service companies have a cash flow problem that nobody talks about openly. You send an invoice. You wait. # How B2B Service Companies Collect Payments Faster By Shuttle Team, February 28, 2026 ## The B2B Payment Problem B2B service companies have a cash flow problem that nobody talks about openly. You send an invoice. You wait. Then you wait some more. Standard B2B payment terms are 30 to 60 days. But the actual time between invoice sent and payment received is closer to 45 to 90 days. That gap is where cash flow goes to die. The reasons stack up. The invoice arrives in someone's inbox on a Friday afternoon. It sits there. The accounts payable person is on holiday. Then the approver needs to sign off. Then the payment run is next Thursday. Then a bank holiday pushes it another week. For a recruitment agency placing 20 candidates a month or a marketing agency billing retainers plus project work, that delay means you're funding your clients' working capital. You delivered the service in January. You might see the money in April. The real cost isn't just the cash flow squeeze. It's the time your team spends chasing. Finance people sending "friendly reminder" emails. Account managers making awkward phone calls to clients they want to keep happy. A mid-market services business can easily burn 15 to 20 hours a month on payment follow-ups. That's a hidden headcount cost that never shows up on anyone's P&L. ## Why Invoices Alone Don't Work The standard B2B payment process looks like this: you generate an invoice in your accounting software, export it as a PDF, attach it to an email, and send it with "please find attached" in the subject line. Now look at what your client has to do to pay you. Open the email. Download the PDF. Note the amount and reference number. Log into their online banking. Add you as a new payee (if they haven't already). Enter your sort code, account number, and payment reference. Get approval from someone with payment authority. Wait for the next payment run. Every one of those steps is a friction point. Every friction point adds days. Compare that to how the same person buys something personally. They tap a link, see the amount, tap Apple Pay, done. Sixty seconds. No reference numbers. No bank logins. No approval chains for a subscription renewal. B2B payments are stuck in 2005. The service has changed, the delivery model has changed, the client relationship has changed. But the payment mechanism is still "PDF attached to an email, please transfer when convenient." That's why invoice payment terms are a fiction. The terms say 30 days. The process takes 60. ## Payment Links: The Fix That Actually Works A payment link is a URL that opens a branded checkout page. Your client clicks it, sees the amount and description, picks their payment method (card, bank transfer, or digital wallet), and pays. The whole thing takes under 60 seconds. Instead of attaching a PDF and hoping for the best, you include a "Pay Now" link directly in the invoice email. The client clicks it on their phone between meetings. Payment done. This isn't a new concept for consumer payments. Every Uber receipt has a payment link. Every SaaS subscription renewal is a link. But B2B service companies have been slow to adopt it because most payment link tools are built for retail and ecommerce, not for service businesses billing clients on account. What makes a payment link work for B2B is different from retail: - Custom amounts. You're not selling a product at a fixed price. Every invoice is different. - Reference matching. The payment needs to carry your invoice number so you can reconcile it automatically. - Branding. Your client sees your logo and colours on the checkout page, not some third-party payment provider's branding. - Multiple payment methods. Some clients want to pay by card. Others prefer bank transfer. Government clients might require a specific method. The link should support all of them. - PSP flexibility. You might process through Stripe today but want to switch to Worldpay next quarter. Or your client's procurement team mandates a specific provider. Your payment links should work with whatever PSP you or your client needs. The result: clients pay faster because paying is easy. You spend less time chasing because there's nothing to chase. The link is the nudge and the mechanism in one. ## Multi-Channel Collection for B2B A single payment link in an invoice email is good. A multi-channel collection strategy is better. Here's what that looks like in practice. Day 0: Invoice email with payment link. The invoice goes out with a "Pay Now" button. No PDF attachment needed (though you can include one for records). The link is the primary call to action. Day 7: SMS reminder. A short text message: "Invoice #1247 for £4,200 is due in 23 days. Pay now: [link]." SMS open rates are above 90%. Your client sees this on their phone, taps, pays. No email hunting required. Day 14: Second reminder. Another SMS or email, depending on the client's preference. The link is the same. The message is slightly more direct. Day 30: WhatsApp follow-up for key accounts. For your bigger clients, a WhatsApp message from their account manager feels personal without being pushy. "Hi Sarah, just flagging invoice #1247 is due today. Here's the link if it's easier: [link]." It lands differently from a generic accounts receivable email. Day 45+: Phone follow-up with voice payment. For overdue invoices, your team calls the client. If the client says "I'll pay it now," your team can take the payment right there on the call using PCI-compliant voice payment. No "I'll send you the bank details again" loop. No waiting another two weeks. This multi-channel approach works because it meets clients where they are. Some people live in their email. Some respond to texts. Some need a phone call. The payment link is the constant. The channel is the variable. ## Industry-Specific Payment Patterns B2B services aren't all the same. The payment challenge varies by sector. ### Recruitment Agencies Recruitment has a unique billing structure. Placement fees are typically 15 to 25% of the candidate's first-year salary, invoiced on start date. That's a large one-off payment, often £8,000 to £25,000, from a client who might only hire through you once or twice a year. The problem: your client's hiring manager approved the placement but has no authority over payments. The invoice goes to accounts payable, who have never heard of you. The approval chain is long because the amount is high. Payment links help because they reduce the admin burden on AP. Instead of processing a manual bank transfer, AP clicks a link, pays by card or bank transfer, and the reference matches automatically. For temp billing with weekly or monthly invoices, recurring payment links cut the chasing cycle entirely. Split billing adds another wrinkle. When a placement fee is split across departments or entities, you can send separate payment links for each portion with the correct reference and amount. No confusion, no partial payments sitting in limbo. ### Marketing Agencies Marketing agencies juggle retainers and project work. The retainer is predictable but still needs collecting. Project milestones are variable and often disputed ("we haven't signed off that deliverable yet"). For retainers, a monthly payment link sent on the same date with the same amount becomes routine. Clients expect it, click it, pay it. It's as close to a direct debit as you can get without the setup hassle. For project milestones, payment links tied to specific deliverables work well. "Phase 2 website build complete. £12,000 due. [Pay Now]." The link arrives at the moment of delivery, when the value is fresh and the client is most willing to pay. ### IT Services and MSPs IT services companies deal with two payment types: recurring managed service contracts and ad-hoc support tickets. The managed service is straightforward. The ad-hoc work causes payment delays because clients don't expect the invoice and often query it. Sending a payment link at the point of ticket closure, with the ticket reference in the description, reduces queries. The client sees "Support ticket #4892: server migration, 3.5 hours at £120/hr = £420" and pays immediately. No surprises. No "what was this for?" emails three weeks later. ### Facilities Management Facilities management companies have contract payments (fixed monthly amounts for ongoing maintenance) and call-out charges (variable, often urgent). Contract payments are predictable and suit automated monthly links. Call-out charges are the problem. A burst pipe at 2am generates a £600 emergency call-out charge. The engineer fixes the problem. The invoice goes out three days later. The client, already annoyed about the burst pipe, puts the invoice at the bottom of the pile. Sending a payment link by SMS immediately after the job is completed, while the client is still grateful the problem is fixed, dramatically improves collection speed. "Emergency call-out completed. £600 due. [Pay now]." Context and timing do the heavy lifting. ## What to Look for in a B2B Payment Collection Tool Not all payment link tools are built for B2B service companies. Here's what matters. PSP flexibility. You should be able to use your existing payment provider. If you're processing through Worldpay or Barclaycard, you shouldn't have to switch to Stripe just because your payment link tool only supports Stripe. Look for a tool that works with 40+ PSPs and lets you bring your own gateway. White-label branding. Your clients should see your logo, your colours, your domain on the checkout page. Third-party branding erodes trust, especially for high-value B2B invoices. If a client is paying £15,000 and the checkout page says "Powered by [some company they've never heard of]," they'll hesitate. Reference matching and reconciliation. Every payment link should carry a reference (your invoice number) that flows through to your bank statement and accounting software. Manual reconciliation of "mystery payments" kills the efficiency you gained by collecting faster. Team access and permissions. Your account managers need to create and send payment links. Your finance team needs to see payment status and reporting. Your MD needs a dashboard. Per-user access with role-based permissions matters when you have 10 or 20 people involved in billing. Multi-channel delivery. Email alone isn't enough. You need SMS, WhatsApp, and the ability to send links during phone calls. The more channels you cover, the faster you collect. Reporting and audit trail. For every payment link, you should see: when it was sent, when it was opened, when it was paid, which method was used, and who on your team sent it. This data feeds back into your collection strategy. PCI compliance. You're handling payment data. Your tool needs to be PCI DSS compliant so you don't carry that burden yourself. PCI DSS Level 1 is the highest standard. Anything less is a risk for a service business handling high-value B2B transactions. ## How Shuttle Fits Shuttle's Links Checkout is built for exactly this use case. It connects to 40+ PSPs (bring your existing provider or switch later without changing your payment workflow), supports white-label branding, and delivers payment links across email, SMS, and WhatsApp. Your team creates payment links from a shared dashboard at $49 per month. Each link carries your invoice reference, your branding, and your choice of payment methods. Clients pay on a checkout page that looks like yours, not like a third party's. For phone follow-ups on overdue invoices, Shuttle's Voice Checkout lets your team take PCI-compliant payments during the call. The client says "I'll pay now" and actually pays now, instead of promising to "sort it this week." Everything is PCI DSS Level 1 compliant, so your team never sees or handles card data. See how it works for your business ## FAQ ### Do B2B clients prefer to pay by card or bank transfer? It depends on the amount. For invoices under £1,000, card is common because it's instant and many businesses have company cards. For invoices over £5,000, bank transfer is more typical because card processing fees are a factor and corporate card limits may not cover it. The best approach is to offer both options on every payment link and let the client choose. ### What about clients who insist on 60-day payment terms? Payment links don't change your agreed terms. They change how quickly your client acts once the invoice is due. A client on 60-day terms still has 60 days. But instead of paying on day 85 because the bank transfer was a hassle, they pay on day 60 because clicking a link takes 30 seconds. You can also send the payment link at the start of the term so it's ready when the payment date arrives. ### Can payment links integrate with our accounting software? Yes. Most B2B payment collection tools integrate with Xero, QuickBooks, Sage, and other accounting platforms. The integration typically means that when a payment is made through a link, it's automatically marked as paid in your accounting system with the correct reference. This eliminates the manual reconciliation step. ### What if a client disputes the amount? Payment links for a specific amount actually reduce disputes. The client sees exactly what they're paying and for what before they click "Pay." If there's a query, it happens before payment rather than after. For milestone-based billing, sending the link with a clear description of the deliverable ("Phase 2 website build, as per SOW dated 15 Jan") pre-empts most disputes. ### Is it secure enough for high-value B2B transactions? With a PCI DSS Level 1 certified provider, yes. This is the same security standard used by the largest banks and payment processors. The payment page is hosted on secure infrastructure, card data is encrypted and tokenised, and your business never touches sensitive payment information. For a £20,000 invoice payment, this is actually more secure than a client reading their card number over the phone to your accounts team. ### How quickly do we receive the funds? Settlement times depend on your PSP and the payment method used. Card payments typically settle within 1 to 3 business days. Faster Payments bank transfers in the UK settle the same day or next business day. This is dramatically faster than waiting for a client to initiate a manual bank transfer "sometime this week." ## Related Reading - Best Payment Link Providers - Payment Collection for Professional Services - Payment Links for Property Management - Accounts Receivable - Invoice Payment Links - Payment Collection for Field Service Teams - Payment Links for Method CRM Users - Payment Reminder Email Templates (With Pay Now Links) - Overdue Invoice Email Templates UK - How to Reduce Debtor Days: 10 Strategies That Actually Work - The UK Guide to Collecting Overdue Payments ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### What Is Local Acquiring? How It Cuts International Payment Costs ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [See how it works for your business](/merchants/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [Payment Collection for Professional Services](/guides/payment-collection-professional-services/) - [Payment Links for Property Management](/guides/payment-links-property-management/) - [Accounts Receivable](/guides/b2b-payment-collection/) - [Invoice Payment Links](/guides/b2b-payment-collection/) - [Payment Collection for Field Service Teams](/guides/field-agent-payment-collection/) - [Payment Links for Method CRM Users](/guides/payment-links-method-crm/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [Overdue Invoice Email Templates UK](/blog/overdue-invoice-email-templates-uk/) - [How to Reduce Debtor Days: 10 Strategies That Actually Work](/guides/reduce-debtor-days/) - [The UK Guide to Collecting Overdue Payments](/guides/uk-guide-collecting-overdue-payments/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) --- URL: https://www.shuttleglobal.com/guides/best-payment-link-providers/ --- # Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle | Shuttle > Looking for the right payment link provider in 2026? We compare Stripe, Square, PayPal, GoCardless and Shuttle on fees, branding control, multi-PSP... # Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle By Shuttle Team, March 6, 2026 Looking for the right payment link provider in 2026? We compare Stripe, Square, PayPal, GoCardless and Shuttle on fees, branding control, multi-PSP support and what each one is best suited for ## Why Payment Links Are Replacing Invoices Payment links are the fastest way to collect money from a customer without building a checkout page, mailing an invoice, or setting up a card terminal. You create a link. You send it via SMS, email, WhatsApp, or embed it on a webpage. The customer clicks, enters their card details on a hosted checkout page, and pays. The money lands in your account within 1-3 business days. For businesses that collect payments outside of a traditional e-commerce checkout, payment links have become the default. Professional services firms send them after consultations. Property managers collect rent and deposits. Field service companies close payments after completing jobs. B2B companies attach them to invoices to accelerate collection. The question is no longer whether to use payment links. It's which provider to use and what trade-offs matter for your business. ## What to Look For in a Payment Link Provider Before comparing specific providers, here's what actually matters when choosing one. These are the criteria that separate a provider that works for a sole trader from one that works for a business with a team. ### Branding Does the checkout page show your brand or the provider's? When a customer clicks a link from your business and lands on a page that says "Stripe" or "GoCardless," there's a trust gap. Branded (white-label) checkout pages maintain the customer relationship and convert better. ### PSP Flexibility Are you locked into one payment processor? Most payment link providers are also the payment processor. Stripe Payment Links only process through Stripe. GoCardless links only process through GoCardless. If your business already has a preferred gateway (Worldpay, Adyen, or a regional processor), most payment link providers force you to add a second PSP relationship or switch entirely. ### Team Features Can multiple people on your team create and send links? For a sole trader, single-user access is fine. For a business with a sales team, finance team, or multiple offices, you need multi-user access with visibility into who sent what and which payments are outstanding. ### Channels How can you deliver the link? Email-only is limiting. The best providers support SMS, email, WhatsApp, QR codes, and embedding links in existing workflows or CRM tools. ### Payment Methods Does the checkout page support cards, bank transfers, digital wallets, and local payment methods? Offering more ways to pay increases completion rates. ### Pricing Transaction fees matter, but so do monthly costs, per-user fees, and hidden charges for features like SMS delivery or recurring payments. ## Payment Link Providers Compared ### Stripe Payment Links Stripe Payment Links let you create a hosted checkout page without code. You generate a link from the Stripe Dashboard, share it, and payments process through Stripe. Strengths: - No monthly fee. Transaction-based pricing only (2.9% + 30c US / 1.4% + 20p UK) - Supports cards, wallets (Apple Pay, Google Pay), and bank debits - Connects to the full Stripe ecosystem (subscriptions, invoicing, Connect) - QR codes included Limitations: - Only works with Stripe as the processor. If you already use Worldpay, Adyen, or another gateway, you need a second PSP relationship - Checkout page is Stripe-branded by default. Custom branding requires Stripe Checkout (developer integration) - No built-in SMS or WhatsApp delivery. You copy a URL and send it yourself - Single-user focus. No team dashboard for managing who sent which link Best for: Developer-led businesses already using Stripe who need simple one-off payment collection. ### GoCardless GoCardless is primarily a Direct Debit provider but offers payment links for one-off and recurring bank-to-bank payments. - Low transaction fees for Direct Debit (1% + 20p, capped at £4) - Strong for recurring payments and subscriptions - Open Banking support for instant bank-to-bank payments - Good for UK and European businesses - Does not support card payments on payment links. Bank transfers only - Checkout page is GoCardless-branded - Limited to GoCardless as the processor - No SMS or WhatsApp delivery built in Best for: Businesses collecting recurring payments via bank transfer (memberships, subscriptions, rent). ### Square Square offers payment links through its Point of Sale and Invoicing products. - No monthly fee on the basic plan - Clean checkout experience - Supports cards and digital wallets - Integrates with Square POS for businesses with physical and remote sales - Only processes through Square - Checkout is Square-branded - Limited to Square's supported countries and currencies - Team features are basic compared to dedicated payment link tools Best for: Small retail or service businesses already using Square POS. ### PayPal.me / PayPal Payment Links PayPal offers shareable payment links through PayPal.me and its invoicing tools. - Massive consumer recognition. Customers trust PayPal - Supports 200+ markets and 25+ currencies - Buyer protection increases customer confidence - No monthly fee (transaction fees of 2.9% + fixed fee) - Checkout requires the customer to have or create a PayPal account (guest checkout exists but is buried) - PayPal-branded only. No white-label option - Funds land in PayPal balance, not directly in your bank account (requires withdrawal) - Limited team and reporting features Best for: Freelancers and international sellers whose customers already use PayPal. ### Adyen Pay by Link Adyen offers payment links as part of its enterprise payment platform. - Supports 250+ payment methods globally (cards, wallets, local methods) - Strong customisation options for the checkout page - Enterprise-grade reporting and reconciliation - Multi-currency with intelligent routing - Enterprise pricing. Not accessible for small or mid-market businesses - Requires Adyen as the processor - Implementation needs developer involvement - Minimum processing volume requirements Best for: Enterprise businesses already on the Adyen platform. ### Checkout.com Pay by Link Checkout.com provides payment links through its enterprise payment infrastructure. - Global coverage with local acquiring in key markets - Customisable checkout pages - Strong API and reporting - Competitive interchange++ pricing for high-volume merchants - Enterprise-focused. Not designed for SMEs - Only processes through Checkout.com - Requires technical setup - Pricing is custom and opaque Best for: High-volume businesses already processing through Checkout.com. ### Shuttle Links Checkout Shuttle takes a different approach. Instead of being both the payment link provider and the processor, Shuttle is the payment link layer that works with your existing PSP. You connect your Stripe, Worldpay, Adyen, Braintree, or any of 40+ supported gateways. Then you create and send branded payment links that process through your chosen gateway. - Works with 40+ payment gateways. Keep your existing PSP relationship - Fully white-label. The checkout page carries your brand, not Shuttle's - Multi-channel delivery: SMS, email, WhatsApp, QR codes - Built for teams ($49/mo). Multi-user dashboard with link tracking, payment status, and team activity - PCI DSS Level 1 compliant. Limited PCI scope for your business - Supports cards, bank transfers, and digital wallets through connected PSPs - Monthly per-user pricing. Not free for low-volume use - Requires connecting at least one payment gateway (not a standalone processor) - Not designed for consumer-facing marketplaces or e-commerce checkout Best for: Mid-market businesses with teams that need branded payment links, already have a PSP relationship, and want multi-channel delivery without switching processors. ## Comparison Table Checkout.com Card payments Yes (via PSP) Bank transfers Digital wallets White-label checkout PSP flexibility Stripe only GoCardless only Square only PayPal only Adyen only Checkout.com only SMS delivery WhatsApp delivery Team features Enterprise Yes (included) Monthly cost Stripe users DD/recurring POS + remote International Teams with existing PSPs ## How to Choose the Right Provider ### You're a sole trader or freelancer Go with what's simplest. If you already use Stripe, use Stripe Payment Links. If your clients prefer bank transfer, look at GoCardless. If you sell in person and remotely, Square works well. Don't pay for team features you don't need. ### You're a business with a small team (5-20 people) Team features matter now. You need visibility into which links were sent, by whom, and whether they've been paid. You also need branded checkout pages because your customers expect a professional payment experience. Stripe's free tier might still work, but you'll feel the limitations around branding and team workflows quickly. ### You're a mid-market business with an existing PSP This is where PSP flexibility becomes the deciding factor. If you process through Worldpay and your payment link provider only works with Stripe, you now have two PSP relationships to manage, two reconciliation streams, and two sets of transaction fees. Shuttle is built for this exact scenario. You connect your existing gateway and get branded payment links without adding a second processor. ### You process high volume and need enterprise features Adyen and Checkout.com are built for this, but only if you're already on their platform. If you need payment links across multiple PSPs or channels (voice, SMS, chat), you need a payment layer approach rather than a single-PSP link tool. ## FAQ What is a payment link? A payment link is a URL that takes a customer to a hosted checkout page where they can enter payment details and pay. The business creates the link, sends it to the customer (via SMS, email, WhatsApp, or any channel), and the customer pays on a secure page without needing to visit a website or download an app. Are payment links secure? Yes. Reputable payment link providers host the checkout page on PCI-compliant infrastructure. The customer's card data is captured on a secure page and never touches your systems. This is significantly more secure than taking card details over the phone or via email. Can I send payment links via SMS? Some providers support SMS delivery natively (Shuttle). Most others (Stripe, Square, GoCardless, PayPal) generate a URL that you then copy and send via whatever channel you choose. This means you handle the SMS delivery yourself, which may require a separate SMS provider. Do I need a website to use payment links? No. That's the point. Payment links are hosted checkout pages. The customer clicks the link and lands on a page hosted by the payment provider. You don't need a website, e-commerce platform, or developer to start collecting payments. Can I use payment links with my existing payment processor? With most providers, no. Stripe Payment Links only work with Stripe. GoCardless links only work with GoCardless. Shuttle is the exception: it connects to 40+ payment gateways, so you can create branded payment links that process through your existing Worldpay, Adyen, Braintree, or other PSP account. What do payment links cost? Costs vary. Stripe and Square charge per-transaction fees with no monthly cost. GoCardless charges per Direct Debit. Shuttle charges $49/month. Enterprise providers like Adyen and Checkout.com have custom pricing. The right comparison isn't just the fee per transaction but the total cost including monthly fees, team user fees, and the operational cost of managing multiple PSP relationships. ## Related Reading - Payment Links Glossary -- what payment links are and how they work - How to Take Payments Online -- the complete guide for service businesses - Prommt Alternatives -- comparing Prommt with Shuttle and other payment link providers - Payment Links for Stripe -- using Stripe's native payment links - Payment Links for Hotels -- industry-specific guide for hospitality - Payment Collection for Professional Services - Payment Links for Property Management - How B2B Service Companies Collect Payments Faster - Payment Collection for Field Service Teams Want a payment link provider that works with your existing payment processor instead of forcing you onto a new one? Shuttle Links & Checkout connects to 40+ PSPs -- Stripe, Worldpay, Adyen, Authorize.Net and more -- so you can generate branded payment links through whichever provider you already have. Cards, Apple Pay, Google Pay, and local payment methods, on a checkout page that looks like your brand. See how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Best UK Payment Providers - The definitive guide ### How to Launch a Payment Link Feature in Weeks, Not Months ### Maximize Efficiency: The Best Payment Gateways for Facilities Management ### Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared ### Best Payment Gateways UK 2026: Fees, Features & Integration Compared ### The best orders were always conversations. Now AI can have them, and take the payment. ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payment Links Glossary](/glossary/payment-links/) - [How to Take Payments Online](/guides/take-payments-online/) - [Prommt Alternatives](/alternatives/prommt/) - [Payment Links for Stripe](/blog/payment-links-for-stripe/) - [Payment Links for Hotels](/guides/payment-links-for-hotels/) - [Payment Collection for Professional Services](/guides/payment-collection-professional-services/) - [Payment Links for Property Management](/guides/payment-links-property-management/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [Payment Collection for Field Service Teams](/guides/field-agent-payment-collection/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [See how it works](/merchants/links-checkout/) - [Book a Call](/discovery/) - [BlogBest UK Payment Providers - The definitive guide→](/blog/best-uk-payment-providers-the-definitive-guide/) - [BlogHow to Launch a Payment Link Feature in Weeks, Not Months→](/blog/how-to-launch-a-payment-link-feature-in-weeks-not-months/) - [BlogMaximize Efficiency: The Best Payment Gateways for Facilities Management→](/blog/maximize-efficiency-the-best-payment-gateways-for-facilities-management-2/) - [BlogFastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared→](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [BlogBest Payment Gateways UK 2026: Fees, Features & Integration Compared→](/blog/best-payment-gateways-for-uk-businesses-comparison/) - [BlogThe best orders were always conversations. Now AI can have them, and take the payment.→](/blog/best-orders-were-always-conversations/) --- URL: https://www.shuttleglobal.com/guides/bland-ai-payments/ --- # How to Take Payments on Bland AI Phone Agents: PCI-Compliant Payments | Shuttle > Bland AI is a platform for building AI phone agents that handle real conversations at scale, inbound and outbound, on its own telephony infrastructure. # How to Take Payments on Bland AI Phone Agents: PCI-Compliant Payments By Shuttle Team, May 25, 2026 Bland AI is a platform for building AI phone agents that handle real conversations at scale, inbound and outbound, on its own telephony infrastructure. It is used heavily for outbound work: cold calling, appointment reminders, lead qualification, and collections, alongside inbound call handling. Outbound calling is where payments show up most. A reminder call turns into a bill payment. A collections call ends with the customer agreeing to settle. A sales call closes. But when a Bland agent reaches that moment, card data cannot be allowed to enter the AI pipeline. This guide covers how to take PCI-compliant payments on Bland AI phone agents using Shuttle, so your agents can collect card payments mid-call without putting your application or Bland's platform in PCI scope. Bland AI holds PCI DSS certification at the platform level, but it has no native payment-capture product: no built-in way to actually take a card payment during a call. The agent can detect payment intent and follow a conversational pathway, but it cannot capture and process a card itself. If card digits enter the audio stream unprotected, your whole stack falls into PCI scope. Shuttle provides the payment layer that closes that gap. Shuttle has no native integration with Bland AI. Instead, your application code invokes Shuttle's Twilio-based payment setup. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The card digits are captured inside Shuttle's certified environment and never reach Bland, the LLM, or the agent. To use this path, you need to be a Twilio customer, and your team builds the orchestration that triggers the handoff. ## The Payment Challenge for Bland AI Outbound agents are payment-rich, which makes the compliance problem more acute, not less. Card data cannot enter the AI pipeline. DTMF tones entered during a Bland call are cardholder data under PCI DSS. If they flow through the audio path, your call logs, your analytics, and your backend are all in PCI scope. Building card capture yourself is not realistic. PCI DSS Level 1 certification costs $500,000+ upfront and $200,000+ per year, with a Qualified Security Assessor, quarterly scans, and annual penetration testing. That is not where an outbound calling operation wants to spend its time. Sending people elsewhere to pay loses the moment. In collections and outbound sales especially, the commitment is fragile. Telling the customer to call a payment line or wait for a link to arrive is how an agreed payment becomes an uncollected one. The answer is a payment layer that captures the card in-call, in an isolated environment, and hands a clean result back to your agent. ## How Shuttle Works with Bland AI Today Shuttle has no native integration with Bland AI. The handoff is API-driven: your application code triggers the Shuttle payment handoff, and the card is captured by Shuttle inside its PCI DSS Level 1 certified environment, never by Bland. To use the secure voice capture, you must be a Twilio customer, because today the capture runs over Twilio Pay. Shuttle provides ready-made interfaces for payment links plus the capture/IVR and the APIs. Your team builds the agent-side orchestration that triggers the handoff. You can build and validate the flow against Shuttle's sandbox gateway and demo app before going live. A deeper, native Bland integration is possible only as a paid project. - Your Bland agent runs the conversation: the pathway or prompt drives intent recognition, customer interaction, and amount confirmation. - Your backend triggers Shuttle: when payment is due, your server calls Shuttle's API to create a payment session with the amount, currency, and gateway configuration. - The call is handed to a secure PCI capture: at the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The customer enters their card on the keypad, and Shuttle captures the digits inside its certified environment, so they never reach Bland, the LLM, or your application. - Payment is processed: Shuttle tokenises the card and routes it to your configured gateway. Authorisation happens entirely inside Shuttle's certified environment. - Result returned to your agent: Shuttle sends a webhook with the outcome, a transaction reference, and a masked card number. Your application records the result, and your Bland agent confirms the payment. One honest caveat to set expectations on up front: the secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Bland agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. ## How It Works: Step by Step Step 1: Payment intent recognised. Your Bland agent reaches the payment step in the pathway, or your application logic determines payment is due. Step 2: Amount confirmed. The agent states the total and tells the customer they'll be connected to a secure line to enter their card. Step 3: Payment session created. Your backend calls Shuttle's API with the amount, currency, and gateway config. Shuttle returns a session token. Step 4: Secure capture triggered. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, with Shuttle as the certified connector. The card capture happens inside that secure environment, not inside Bland. Step 5: Card details entered. Shuttle plays a secure prompt and the customer enters card number, expiry, and CVV on the keypad. Step 6: Digits captured in isolation. Shuttle captures the card inside its PCI DSS Level 1 certified environment. The digits never reach Bland, the LLM, or your application. Step 7: Payment processed. Shuttle tokenises the card and routes it to your gateway for authorisation. Step 8: Webhook received. Shuttle sends the result: outcome, transaction reference, masked card number. Step 9: Agent confirms. Your application records the result, and your Bland agent confirms the payment. The customer stays on the line throughout. To return the caller to the same Bland agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## Multi-PSP Support Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. - Per-client gateway configuration: each client or business unit can route to its own PSP - Single integration: integrate with Shuttle once; switching gateways is configuration, not re-integration - Multi-PSP routing: route by currency, region, card type, or custom rules - Failover: automatic fallback to a secondary gateway if the primary is unavailable One gateway caveat worth knowing: a few gateways (Braintree, for example) do not work for voice capture, because they will not allow raw card data to be passed, but they do work for payment links. For agencies and BPOs running outbound campaigns for multiple clients on Bland, per-client routing is essential, and it is configuration rather than code. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. What stays in your application / Bland: conversation logic, amount calculation, session initiation, and handling of non-sensitive webhook results. None of this is cardholder data, so your application and Bland's platform stay out of PCI scope. What stays in Shuttle: card capture during the secure Twilio Pay handoff, card tokenisation, gateway communication, and secure prompt playback, all inside the certified environment. Call recordings: because the card is entered during the secure PCI capture, the card details are never part of the audio Bland processes or records. Any recordings you store contain no cardholder data, so there are no card digits in your recordings, logs, or analytics. With Shuttle handling all card data, your application typically qualifies for SAQ-A rather than the SAQ-D obligations that handling card data yourself would trigger. This matters for collections and outbound operations, where call volumes and recording retention make in-house card handling especially risky. ## Beyond Voice: Payment Links The secure in-call capture is one method, but Shuttle also supports payment links, and they are the turnkey path. Mid-call, your Bland agent can say it has sent a secure link by SMS or email; the customer opens a hosted checkout page, pays, and the result returns to your application in real time. Links suit higher-value payments, mobile-first callers, and post-call payment plans, which are common in collections. They also work even with gateways that do not support voice capture, such as Braintree. ## Use Cases ### Collections Collections agents need to capture payment the instant the debtor agrees. Shuttle takes the card in-call, and payment links handle agreed instalment plans, so commitments convert into collected funds. ### Outbound Sales Outbound sales agents close and collect in the same call, with no callback and no link left unclicked. ### Appointment Reminders and Bill-Pay Reminder calls that prompt a bill payment can take the card in-call instead of directing the customer to a portal. ### Order and Renewal Confirmations Agents confirming orders or renewals can collect payment at the point of confirmation, optionally tokenising the card for future charges. ## Developer Integration API-driven. Create payment sessions, configure gateways, and receive webhooks via REST API. Your team builds the agent-side orchestration; Shuttle provides the capture, IVR, links, and APIs. Twilio required today. The secure voice capture runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Pathway and prompt friendly. Trigger Shuttle at the payment step of a conversational pathway or from a prompt-driven flow, and resume on the result webhook. Build a POC against the sandbox. Validate the full payment flow against Shuttle's sandbox gateway and demo app before going live. A native Bland integration is possible only as a paid project. [$0.20 per successful transaction](/pricing/) for voice. No setup fees, no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). For technical detail, see the Shuttle docs: Twilio setup, payment links, and security and PCI. ## FAQ Does Shuttle have a native Bland AI integration? No. Shuttle has no native integration with Bland. The handoff is API-driven: your application code triggers Shuttle's Twilio-based payment setup, and at the point of payment the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. A native Bland integration is possible only as a paid project. Does this require Twilio? Yes, for the secure in-call capture. The capture runs over Twilio Pay today, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Can I build PCI-compliant payment capture myself on Bland? Technically, but PCI DSS Level 1 certification runs $500,000+ upfront and $200,000+/year. Shuttle provides the same capability at $0.20 per successful transaction. What payment gateways does Shuttle support? 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. Switching gateways is configuration, not re-integration. A few gateways (Braintree, for example) do not work for voice capture but do work for payment links. Does this work for outbound campaigns? Yes. Bland is outbound-heavy, and the same secure handoff captures payment during outbound calls for sales, collections, and reminders. Can I take instalment or payment-plan payments? Yes. Payment links and tokenisation support agreed payment plans, which is common in collections. Does the customer hear the agent during card entry? During the secure capture, Shuttle plays the prompts and the agent's voice is paused. Once payment is complete, your application resumes the conversation. To return the caller to the same agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## Related Reading - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents - Vapi Payments: secure payment capture for Vapi voice agents - How AI Voice Agents Take PCI-Compliant Payments: the technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared - The Payment Layer for AI Agents: why AI agents need a dedicated payment layer - Phonely Payments: PCI-compliant payment capture for Phonely AI phone agents ## Add Payments to Your Bland AI Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're building phone agents on Bland AI and need PCI-compliant payment capture: See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS](/glossary/pci-dss/) - [30+ payment gateways](/payment-providers/) - [Twilio setup](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](https://docs.shuttleglobal.com/docs/links-intro) - [security and PCI](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [30+ gateways](/payment-providers/) - [Retell AI Payments](/guides/retell-ai-payments/) - [Vapi Payments](/guides/vapi-payments/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Phonely Payments](/guides/phonely-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/boost-ai-payments/ --- # How to Take Payments on boost.ai: PCI-Compliant Virtual Agent Payments | Shuttle > boost.ai is a Gartner-recognised leader in conversational AI for the enterprise, with a particularly strong footprint across banking, insurance, financial... # How to Take Payments on boost.ai: PCI-Compliant Virtual Agent Payments By Shuttle Team, May 30, 2026 boost.ai is a Gartner-recognised leader in conversational AI for the enterprise, with a particularly strong footprint across banking, insurance, financial services, and public sector. Founded in Norway and widely deployed across the Nordics and beyond, boost.ai powers virtual agents that handle everything from account queries and loan applications to insurance renewals and public service requests. Its compliance posture is serious: SOC 2 Type II, ISO 27001, ISO 27701, and ISAE 3402 certifications make it a credible choice in regulated industries where audit requirements are non-negotiable. Payment capability is a different matter. boost.ai handles the conversation exceptionally well but has no native payment product of its own. For PCI-compliant payment capture, boost.ai relies on third-party integrations, including an established contact-centre payments partner and a Vipps connector for Nordic markets. That works in many contexts, but banks and insurers running contact centres at scale often need more flexibility: a broader choice of payment gateways, per-client routing across a multi-tenant portfolio, the ability to bring their own acquirer, and a consistent compliance posture across channels. This guide is for regulated-sector teams running boost.ai virtual agents who need to add payment capture, and it explains exactly what that involves with Shuttle today. If your compliance team needs to minimise PCI scope while your operations team needs multi-PSP flexibility, this is the pattern that achieves both. Some of the world's biggest brands use Shuttle for voice payments. ## How Shuttle Adds Payments to boost.ai Shuttle adds PCI-compliant card capture to your boost.ai payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your boost.ai recordings, transcription, or your agents. ai-based operations today. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for boost.ai specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your boost.ai call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running boost.ai have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your boost.ai deployment, your call recordings, your CRM, your agents, or the conversational LLM. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-conversation. The customer taps the link, enters card details on a secure hosted page served from Shuttle's PCI-certified environment, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that do not support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for boost.ai, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running boost.ai have already built this. There is more in the "What to Expect" section below. ## The Payment Challenge for boost.ai Agents boost.ai's architecture separates conversation intelligence from back-end execution cleanly, which is one of its strengths. That same separation means payment capture has to be handled by an external layer rather than natively within the platform. For many deployments this is not a problem: the partner integration handles the transaction, and the agent continues the conversation once payment is confirmed. The friction appears when requirements get more specific. A bank with an existing acquirer relationship needs to settle through their mandated processor, not through a capture tool's built-in flow. An insurer running across multiple brands or subsidiaries needs per-client routing so that each premium settlement lands in the correct merchant account. A financial services firm running both voice and chat channels needs a consistent compliance behaviour and the same card-data isolation, regardless of which channel the customer used. PCI DSS Level 1 compliance for a service provider is a significant undertaking, and it is not part of boost.ai's current certification set. boost.ai's certifications are strong for data protection and information security, but card data handling requires a separate compliance layer. The question for regulated-sector teams is how to add that layer without complicating the boost.ai deployment or expanding cardholder data scope across systems that should not be in scope at all. ## How a voice payment works - The boost.ai agent runs the conversation: it identifies the customer, confirms the payment amount, and collects intent. - Payment is triggered from your agent interface, via API or webhook, at the point where card details are needed. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. - Result returned to the boost.ai agent and your systems via webhook, so the conversation continues accordingly. - No card data in boost.ai. The card digits never touch your boost.ai deployment, your call recordings, your CRM, or the conversational LLM. ## Multi-PSP Support Shuttle connects to 30+ gateways through a single integration. That list includes Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, and many others across Europe, North America, and APAC. You can bring your own acquirer rather than being channelled through a capture tool's preferred processor. For organisations running boost.ai across multiple clients, brands, or subsidiaries, Shuttle supports per-client and per-tenant routing. Each conversation flow can route to a different merchant account and gateway configuration, with no shared cardholder data between tenants. This is particularly relevant for insurers managing multiple underwriting entities, for banks with distinct product divisions, and for system integrators delivering white-label contact centre deployments at scale. The contrast with a single third-party capture tool tied to its own processing flow is straightforward. If your organisation has an existing gateway relationship, wants to negotiate its own interchange rates, or is bound by a procurement decision to use a specific acquirer, a gateway-neutral layer like Shuttle accommodates that from the start. Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. Shuttle also handles multi-currency routing and can direct transactions to the appropriate regional processor, which matters for boost.ai deployments spanning the Nordics, broader Europe, and international markets. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified service provider, the highest level of certification available. Card data is captured and processed entirely within Shuttle's certified environment and is never transmitted to boost.ai, your call recordings, your CRM, or any other system in your stack. This matters for your compliance posture in two ways. First, it means your boost.ai deployment does not acquire PCI scope by adding payment capability. The conversation platform stays exactly where it is in your architecture, with the same certifications and the same audit perimeter. Second, it moves your contact centre environment from the more demanding SAQ-D scope toward SAQ-A, the lightest possible assessment, because card data capture happens outside your systems entirely. boost.ai's own compliance certifications (SOC 2 Type II, ISO 27001, ISO 27701, ISAE 3402) are strong and appropriate for a platform handling sensitive customer data in regulated industries. Shuttle's PCI DSS Level 1 status complements rather than duplicates that posture: it addresses the one compliance requirement that boost.ai's certifications do not cover, without requiring any change to how boost.ai itself is deployed or audited. Full compliance documentation, including the AOC scope, is in the security docs. ## Beyond Voice: Payment Links boost.ai supports both voice and chat channels, and the most turnkey path with Shuttle works across both. On voice, the card is captured securely via Twilio Pay. On chat, SMS, and WhatsApp, Shuttle generates hosted payment links: secure, single-use URLs served from Shuttle's PCI-certified environment, returned inline to the conversation for the customer to complete. This means a customer can start a query in the boost.ai chat widget, receive a payment link, complete the transaction in a browser tab, and return to the chat for confirmation, with no card data crossing the chat session at any point. The same applies to outbound SMS flows where boost.ai triggers a follow-up message after a conversation: the payment link opens to a Shuttle-hosted form, completing the PCI scope isolation in that channel too. ## Use Cases ### Bill-Pay and Account Payments Customers contacting a bank or utility through a boost.ai virtual agent can make account payments, settle outstanding balances, or set up payment arrangements without being transferred to a human agent. Shuttle handles card capture, with the result returned to the agent to confirm and update the account. ### Insurance Premiums and Renewals Insurers using boost.ai for renewal conversations can collect premium payments at the point of renewal confirmation, within the same interaction. Per-client routing means each underwriting entity or brand can settle into its own merchant account, with a consistent compliance posture across the portfolio. ### Collections and Payment Plans For collections workflows, Shuttle supports instalment arrangements and recurring card authorisations alongside one-off capture. The boost.ai agent negotiates the plan; Shuttle handles the card data and charges the agreed schedule without the customer needing to re-engage. ### Customer Support Payments Banks and financial services firms using boost.ai for general customer support can offer fee payments, top-ups, and charges within the support conversation rather than redirecting customers to a separate payment journey. Completing the transaction in-conversation reduces drop-off and improves resolution rates. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged boost.ai plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for boost.ai specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your boost.ai call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running boost.ai have already done it. - A native boost.ai integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Shuttle have a native boost.ai integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in boost.ai. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running boost.ai have already done. We can build a native boost.ai integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle works with Twilio today, and any carrier coming soon. Does boost.ai process payments natively? No. boost.ai has no native payment product. For PCI-compliant card capture it partners with third parties, including a specialist contact-centre payments provider and Vipps for Nordic markets. A gateway-neutral layer like Shuttle is the alternative for teams needing broader PSP coverage or per-client routing. How is Shuttle different from boost.ai's partner payment integrations? boost.ai's payment partners are capable within their own approaches. Shuttle's difference is gateway neutrality and routing flexibility: 40+ PSPs on a single integration, per-client routing for multi-tenant deployments, and BYO acquirer support. If you want to compare options, see Voice Checkout for how Shuttle's approach works. Which gateways does Shuttle support? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, and many regional processors. You can use your existing acquirer relationship and configure routing per client or per use case. Switching gateways later is configuration, not re-integration. Does this keep our bank or contact centre out of PCI scope? Yes. Card data is captured and processed within Shuttle's PCI DSS Level 1 environment and never transmitted to boost.ai, your call recordings, or your CRM. This removes those systems from PCI scope and moves your contact centre assessment from SAQ-D toward SAQ-A. ## Related Reading - The Payment Layer for AI Agents: how a gateway-neutral payment layer fits across any conversational AI platform - AI Voice Agent PCI Payments: technical guide to secure voice capture, PCI scope reduction, and SAQ-A qualification for voice agents - Voice Payments: end-to-end guide to taking card payments over voice channels - Cognigy Payments: same pattern applied to Cognigy.AI virtual agents, including contact centre and voice use cases - Kore.ai Payments: multi-PSP payment capture for Kore.ai virtual agent deployments ## Add Payments to Your boost.ai Agents Shuttle is a PCI DSS Level 1 service provider offering payment capture across 30+ gateways via Twilio, at $0.20 per successful transaction with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). We'll walk you through what's live today and the path for your setup. See pricing. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Builders who accept cards for payment are better off ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [PCI DSS](/glossary/pci-dss/) - [30+ supported gateways](/payment-providers/) - [30+ gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [Voice Checkout](/platforms/voice-checkout/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [Cognigy Payments](/guides/cognigy-payments/) - [Kore.ai Payments](/guides/kore-ai-payments/) - [See pricing](/pricing/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogBuilders who accept cards for payment are better off→](/blog/building-success-how-accepting-card-payments-can-boost-your-business/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/braintree-twilio-integration/ --- # How to Connect Braintree to Twilio: Voice Payments & Payment Links | Shuttle > Braintree, PayPal's full-stack payment gateway, is one of the few PSPs that Twilio supports natively. # How to Connect Braintree to Twilio: Voice Payments & Payment Links By Shuttle Team, June 25, 2026 Braintree, PayPal's full-stack payment gateway, is one of the few PSPs that Twilio supports natively. Twilio launched a first-party Braintree Pay Connector in November 2019, so you can wire Braintree straight into Twilio's verb and take PCI-compliant card payments during phone calls, IVR flows, and agent-assisted conversations. One thing to know up front: the native connector is the standard in-call keypad (DTMF) path for Braintree. Braintree only accepts raw card data, which is what DTMF capture requires, on merchant accounts specifically configured for it, so Shuttle does not offer Braintree as a standard voice-capture gateway. What Shuttle offers instead is a different and often better-converting path: secure payment links sent by SMS or email mid-call, processed by Braintree's own hosted checkout, plus 30+ voice-capable gateways if in-call capture is a hard requirement. This guide explains both paths, when the native connector is the right choice, and when the payment-links route (or a different voice gateway) fits better. ## Two Ways to Connect Braintree to Twilio ### Path 1: Twilio's native Braintree Pay Connector (in-call DTMF) Twilio ships branded Pay Connectors for a handful of gateways. Its support docs have named Stripe, Braintree, CardConnect, Base Commerce, Chase Paymentech, and Adyen among them, and Braintree also appears in Twilio's Ireland (IE1) and Australia (AU1) regional documentation for . You install the Braintree connector in the Twilio Console, add your Braintree credentials, and point at it. The caller keys in their card details, tones are suppressed from agent audio and recordings, and the transaction lands in your Braintree account. Native connectors are single-gateway by design: one connector instance links to one gateway account. Through Twilio, exposes , , , and . Anything beyond that (refunds, splitting authorisation and capture, statement descriptors, transaction metadata) is handled directly in the Braintree Control Panel or API, not through Twilio. ### Path 2: Shuttle payment links, with Braintree processing Shuttle's connector, listed on the Twilio Marketplace since December 2023 and also available in Twilio's IE1 and AU1 regions, takes a different route for Braintree merchants. Instead of keypad entry, the agent (or IVR, or AI voice agent) triggers a secure payment link, sent to the caller by SMS or email while they are still on the line. The customer pays on Braintree's hosted, tokenised checkout, where PayPal and Venmo can appear alongside card entry. Braintree processes the payment as normal, and your systems never touch card data. And because Shuttle is multi-gateway, the same integration gives you 30+ voice-capable PSPs (Stripe, Adyen, Worldpay, Cybersource, and more) if you also need true in-call DTMF capture on some calls or for some clients. ### Comparison Twilio's native Braintree connector Shuttle (links + multi-gateway) In-call DTMF capture with Braintree No (Braintree does not accept raw card data from third parties) Payment links mid-call Yes, by SMS or email, on Braintree's hosted checkout PayPal and Venmo as payment options No (card capture only) Yes, via Braintree's hosted checkout on the link Gateway coverage Braintree only 30+ gateways behind one connector Multi-PSP routing and failover Yes (by merchant, region, amount, or failover) Multi-merchant management One Braintree account per connector Many merchants and gateways behind one integration Twilio usage fees $0.20 per successful transaction (tiering to $0.05 above 1M/month) ### When the native connector is the right choice If you have a single Braintree account, in-call keypad capture is a hard requirement, and you have no plans for other gateways or merchants, Twilio's native Braintree connector is a clean, first-party option. It is fully supported by Twilio and there is no extra layer to configure. ### When Shuttle fits better Choose Shuttle when the payment-link experience suits your callers (it usually converts well, and it unlocks PayPal and Venmo), or when you need more than one gateway or merchant behind the same call flow: BPOs and platforms serving multiple clients, enterprise customers that mandate a specific PSP, failover to a backup gateway, or in-call DTMF via a voice-capable gateway alongside Braintree links. ## How the Shuttle Path Works - Caller reaches the payment step. The agent clicks a button, or your IVR or AI agent triggers Shuttle via API. - Shuttle sends a payment link. The caller receives it by SMS or email while still on the line. - Customer pays on Braintree's hosted page. Card, PayPal, or Venmo. Card data goes straight to Braintree; it never passes through your systems or the call. - Result returned in real time. Your webhook receives the transaction reference and status. The agent sees confirmation and the call continues. For the full walkthrough of this pattern, see How to Take PayPal / Braintree Payments Alongside Twilio Voice Calls. ## Step-by-Step Setup (Shuttle + Braintree Links) ### Prerequisites - A Twilio account with voice (and SMS if you want in-call link delivery) - A Braintree account with API credentials (Merchant ID, Public Key, Private Key, all found under Settings, then API in the Braintree Control Panel) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Connect Braintree to Shuttle In the Shuttle dashboard, go to Payment Profiles and create a new profile with your Braintree credentials. Braintree issues separate credentials for sandbox and production, so keep two profiles if you want a permanent test path. ### Step 2: Configure your payment link template Set currency, branding, and which payment methods appear (card, PayPal, Venmo via Braintree's hosted checkout). ### Step 3: Trigger links from your call flow Agents can send links from the Shuttle dashboard, or your IVR and AI voice agents can trigger them via Shuttle's API mid-call. ### Step 4: Handle the result Shuttle sends a webhook with the transaction reference and status. Use it to update your order and confirm to the caller before they hang up. ### Step 5: Test with Braintree sandbox Point a test payment profile at your Braintree sandbox credentials and run the flow end-to-end. Braintree's standard test card (Visa) works in sandbox. ## What You Can Do With Braintree + Twilio via Shuttle ### Take Payment While the Caller Is on the Line The link arrives by SMS in seconds. The agent stays on the call, sees the payment land in real time, and confirms before hanging up. ### Offer PayPal and Venmo, Not Just Card This is something no DTMF flow can do: Braintree's hosted checkout on the link presents PayPal and Venmo alongside card entry, which often lifts conversion for consumer callers. ### Tokenise for Future Use Braintree's Vault stores the customer's payment method from the link checkout, so repeat payments do not need a new link each time. Card data never enters your systems. ### Mix Channels and Gateways Use Braintree links for some calls and true in-call DTMF through a voice-capable gateway for others, all behind one Shuttle integration. Routing rules decide per merchant, region, or amount. ## Multi-PSP: Beyond Braintree The structural difference between the two paths shows up as soon as you need a second gateway. With Shuttle, your Twilio integration stays the same when you: - Add another gateway, for example routing UK transactions to one acquirer while Braintree handles PayPal-heavy consumer flows - Serve enterprise customers who mandate a specific PSP - Want a backup gateway, automatically routing to a backup gateway if one is unavailable - Need in-call DTMF capture on some flows, via any of Shuttle's 30+ voice-capable gateways Routing rules live in Shuttle's dashboard. This matters most for BPOs and platforms collecting on behalf of many merchants, each with their own gateway account, behind one Twilio integration. ## PCI Compliance Both paths keep card data out of your systems. On the native connector, Twilio's PCI-compliant capture passes card data to Braintree. On the Shuttle path, the customer enters card details directly on Braintree's hosted checkout page, so cardholder data goes straight to Braintree: PCI handled by Call and link delivery Twilio (no card data in the call) Payment link orchestration Shuttle (PCI DSS Level 1 Service Provider) Card entry and processing Braintree (PCI DSS Level 1) Your systems No card data, SAQ-A Your application only ever sees redacted data (last four digits, payment method, transaction reference), which keeps your PCI scope at SAQ-A, the lightest self-assessment. For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Does Twilio have a native Braintree Pay Connector? Yes. Twilio launched a first-party Braintree Pay Connector in November 2019, and Braintree appears in Twilio's IE1 and AU1 regional documentation. It is the only way to do in-call keypad capture with Braintree. Can Shuttle capture card details over the phone into Braintree? Not as standard. Braintree only permits raw card data, which DTMF capture requires, on merchant accounts specifically configured for it, so it is a merchant account configuration question rather than a Shuttle limitation. Shuttle's standard Braintree path uses payment links on Braintree's own hosted checkout instead. Why use Shuttle instead of the native Braintree connector? Payment links that support PayPal and Venmo, multi-gateway coverage from one integration, routing by merchant, region, amount, or failover, and multi-merchant management for BPOs and platforms. If you only need single-account keypad capture, the native connector may be all you need. Can I refund a voice payment through Twilio? No. Twilio's has no refund API. Refunds are issued in the Braintree Control Panel or via Braintree's API, or through Shuttle's dashboard and APIs if you are on the Shuttle path. Does this work with Braintree's sandbox? Yes. Braintree issues separate sandbox credentials; add them as a test payment profile in Shuttle and verify the full flow before going live. What does it cost? Shuttle charges $0.20 per successful transaction for the first 50K per month, tiering down to $0.05 above 1M. Braintree's standard processing fees apply on either path, and Twilio's usage fees apply on the native path. ## Related Reading - How to Take PayPal / Braintree Payments Alongside Twilio Voice Calls: the full payment-links walkthrough for PayPal and Braintree - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - Braintree: Braintree on Shuttle, channels, features, and coverage - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Take Braintree payments on Twilio calls with Shuttle payment links: PayPal and Venmo included, PCI DSS Level 1, $0.20/transaction. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Braintree: Send Payment Links Through Your Braintree Account ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### Authorize.net QuickBooks Integration: Full Guide ## Links - [DTMF capture](/guides/dtmf-payments/) - [Shuttle](/guides/twilio-pay-connectors/) - [payment links](/merchants/links-checkout/) - [mandate a specific PSP](/guides/enterprise-psp-mandates/) - [How to Take PayPal / Braintree Payments Alongside Twilio Voice Calls](/guides/paypal-twilio-integration/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [Braintree](/payment-providers/braintree/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Braintree: Send Payment Links Through Your Braintree Account→](/blog/payment-links-for-braintree/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) --- URL: https://www.shuttleglobal.com/guides/bs-payone-twilio-integration/ --- # How to Connect BS Payone to Twilio for Voice & IVR Payments | Shuttle > BS Payone (now branded PAYONE) doesn't natively connect to Twilio for voice payments. # How to Connect BS Payone to Twilio for Voice & IVR Payments By Shuttle Team, June 17, 2026 BS Payone (now branded PAYONE) doesn't natively connect to Twilio for voice payments. If you want to process PAYONE transactions during a phone call, whether via IVR, agent-assisted, or an AI voice agent, you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects BS Payone (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. For German and DACH merchants, this matters. PAYONE is one of the region's largest payment providers: a joint venture between Worldline and the DSV Group (Deutscher Sparkassenverlag), with deep roots in the German Sparkassen network. If your business already processes EUR card payments through PAYONE, whether you're an insurer collecting premiums, a utility taking bill payments, or a subscription business recovering failed charges, this guide shows you how to extend that same account to the phone channel. ## Why BS Payone + Twilio Don't Connect Directly BS Payone is built for card acceptance across e-commerce and point of sale in Germany, Austria, and the wider DACH market. Its Server API handles authorisations, captures, refunds, and recurring payments against your PAYONE merchant account. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. BS Payone isn't one of Twilio's built-in connectors, so there is no direct path between the two platforms. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to BS Payone's API for processing. One integration connects the two platforms, and your existing PAYONE merchant account, acquiring relationship, and settlement arrangements stay exactly as they are. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via BS Payone. The connector creates a payment request against your PAYONE account, processes the transaction, and handles the response. - Result returned to your call flow. Your webhook receives the PAYONE transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website", and no reading card numbers aloud to an agent. ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A BS Payone account with API credentials (Merchant ID, Portal ID, Account ID, and key) - A Shuttle account (free to create: you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add BS Payone Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: BS Payone - Merchant ID: Your PAYONE merchant ID (mid) - Portal ID: Your PAYONE portal ID (portalid) - Account ID: Your PAYONE account ID (aid) - Key: Your portal key - Currency: EUR (or your default) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your PAYONE account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code (EUR for most PAYONE merchants) - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in your PAYONE merchant interface if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Use BS Payone's test mode and Twilio's test credentials to verify the flow end-to-end before going live. Run a full test transaction, check it appears against your test portal, and confirm your webhook handles both success and failure results. ## What You Can Do With BS Payone + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, PAYONE processes, done. Ideal for one-off bill payments, arrears collection, and phone orders. ### Authorise Now, Capture Later Place a hold on the card during the call and capture the payment later. Useful for bookings, deposits, or transactions where the final amount is confirmed after the call. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token, so future payments run without the customer re-entering details. Use it across any channel: web, mobile, voice, or payment links. This is the pattern subscription businesses and insurers use to set up recurring collection from a single phone call. The card data is never stored in your systems. ### Agent-Assisted and AI Voice Payments The same connector works whether the payment step is triggered by an IVR menu, a live agent transferring the caller into a secure capture flow, or an AI voice agent handling the whole conversation. German-language IVR prompts work exactly as you'd expect: Twilio captures the digits, Shuttle routes them to PAYONE. ## Multi-PSP: Beyond BS Payone One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your EUR merchants with PAYONE and your UK or US merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Adyen, Worldpay, etc.) - Want a backup gateway: if one gateway is unavailable, you can move the affected payment types to another connected gateway - Expand beyond DACH to markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, with minimum amount, maximum amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own PAYONE account (or any other gateway) through the same Twilio integration. ## PCI Compliance The BS Payone + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to BS Payone. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For regulated DACH businesses such as insurers and utilities, that means the phone channel adds no new card-data footprint to audit. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect BS Payone to Twilio without Shuttle? Twilio doesn't have a built-in BS Payone Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports . Configure it with as the connector and the payment step runs inside your Studio flow. Which credentials do I need from PAYONE? Your Merchant ID (mid), Portal ID (portalid), Account ID (aid), and portal key. These are the standard BS Payone Server API credentials, available in your PAYONE merchant interface. Can I take payments in German-language IVR flows? Yes. The language of your prompts is entirely up to your Twilio flow. DTMF capture and processing work the same regardless of the call language. What does it cost? Shuttle charges $0.20 per successful transaction. Your standard BS Payone fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from BS Payone to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - BS Payone with Shuttle: gateway details and supported features - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect BS Payone to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [BS Payone with Shuttle](/payment-providers/bs-payone/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants→](/blog/payment-links-for-bs-payone/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/build-vs-buy-payment-infrastructure/ --- # Build vs Buy Payment Infrastructure: A Decision Framework for Platforms | Shuttle > The Case for Building Every platform CTO who considers building payment infrastructure in-house has good reasons. # Build vs Buy Payment Infrastructure: A Decision Framework for Platforms By Shuttle Team, March 14, 2026 ## The Case for Building Every platform CTO who considers building payment infrastructure in-house has good reasons. You want full control over the payment experience. You don't want to depend on a vendor for a mission-critical flow. You've been burned by third-party APIs before -- the latency, the breaking changes, the support tickets that go nowhere. Your engineering team is strong. Payments are "just APIs." How hard can it be? These are reasonable instincts. And for a small number of companies, building is the right call. But for most platforms, the build decision is based on an incomplete understanding of what "payment infrastructure" actually means. The gap between "integrate a PSP's API" and "run production payment infrastructure" is where the real cost lives -- and it's dramatically larger than most CTOs estimate. ## What You're Actually Building The misconception is that payment infrastructure is primarily an API integration exercise. Connect to Stripe's API, handle webhooks, store transaction records. A senior engineer could prototype it in a sprint. That prototype handles the happy path. Production payment infrastructure handles everything else. ### The Integration Layer A single PSP integration is straightforward. But platforms rarely stay on a single PSP. Enterprise customers mandate their own gateways. Geographic expansion requires region-specific providers. Pricing optimisation demands routing between providers. Each PSP has its own API design, authentication model, error handling, webhook format, and idiosyncratic behaviour. Worldpay's API looks nothing like Adyen's, which looks nothing like Checkout.com's. Building an abstraction layer that normalises these differences -- so your core platform doesn't need to know which PSP is processing a given transaction -- is a significant engineering investment. ### Tokenisation and Card Storage If you're storing card data -- or even passing it through your systems -- you're in PCI scope. Most platforms use tokenisation to avoid this, but token management across multiple PSPs adds complexity. Tokens from Stripe don't work with Adyen. Network tokens behave differently than PSP-specific tokens. Managing token lifecycle, migration, and multi-PSP portability is non-trivial. ### PCI Compliance PCI DSS compliance is not a checkbox exercise. At service provider level -- which is where platforms sit -- the threshold for Level 1 is 300,000 transactions, six times lower than the merchant threshold of six million. Level 1 requires a Qualified Security Assessor (QSA) audit, penetration testing, vulnerability scanning, and ongoing monitoring. The cost isn't just the audit. It's the infrastructure changes required to pass it. Network segmentation, encryption at rest, key management, access controls, logging, monitoring -- and maintaining all of it continuously, not just at audit time. PCI DSS 4.0, enforced since March 2025, raised the bar further with requirements for stronger encryption, mandatory multi-factor authentication, and continuous monitoring. ### Reconciliation and Settlement Every PSP settles differently. Different formats, different timelines, different fee structures. Building automated reconciliation that matches transactions to settlements across multiple PSPs -- and catches discrepancies -- is a substantial data engineering problem. At scale, this becomes the dominant operational cost. ### Chargeback and Dispute Handling Each PSP has its own dispute process, evidence requirements, response deadlines, and notification mechanisms. Building a unified dispute management layer that works across PSPs -- with automated deadline tracking and evidence compilation -- is its own product. ### Multi-Currency and Regulatory Compliance International payments introduce currency conversion, cross-border fees, local payment method support, and country-specific regulatory requirements (SCA in Europe, local acquiring in certain markets). Each adds a dimension of complexity. ## The Real Cost ### Time A basic single-PSP integration takes 2-5 months to production-ready. That includes webhooks, error handling, retry logic, idempotency, reporting, and edge cases. Building a multi-PSP abstraction layer -- the kind that lets you add or remove PSPs as configuration rather than code -- takes 6-12 months with a dedicated team. Becoming a PayFac (processing payments on behalf of sub-merchants) takes 12-18 months and requires merchant underwriting, KYC/AML, fraud monitoring, and regulatory reporting. ### Money The initial build cost varies widely, but directionally: Cost Range Core integration (single PSP) £50K-£150K Multi-PSP abstraction layer £200K-£500K PCI DSS Level 1 compliance £500K-£1.1M initial Ongoing PCI maintenance £100K-£200K/year Reconciliation & reporting £100K-£250K Dispute management £50K-£100K Total (Year 1) These are engineering costs. They don't include the opportunity cost -- what those engineers would have built for your core product instead. ### The Maintenance Tax The build cost is front-loaded, but the maintenance cost is permanent. PSPs change their APIs. New PCI requirements come into force. Payment regulations evolve. Security vulnerabilities need patching. Each of these requires your team's attention, indefinitely. Large payment companies employ teams of hundreds dedicated to maintaining payment infrastructure. They can amortise that cost across thousands of customers. A platform maintaining its own payment infrastructure carries the full burden alone. ## When to Build Building makes sense when payments ARE your core product -- when the competitive advantage of your business comes from owning the payment flow end-to-end. Specifically, build if: - You are a payment company. If your primary revenue model is payment processing, building proprietary infrastructure is defensible. Stripe built their own infrastructure because they ARE a payment company. - You need sub-transaction-level control. If your business model requires manipulating payment flows at a level of granularity that no third party can provide (custom routing algorithms, proprietary risk scoring), building may be necessary. - Payment infrastructure is your moat. If owning the payment flow creates a competitive advantage that justifies the ongoing investment, the build decision is strategic. For most platforms, none of these apply. Payments are infrastructure that enables the core product. They're important, but they're not the product itself. ## When to Buy Buy when payments are a required capability of your platform but not your competitive differentiator. This applies to the majority of software platforms. The signals: - Your engineers are building payment features instead of core product. If your roadmap keeps getting hijacked by payment integrations, you're spending engineering capital on the wrong problem. - Enterprise customers are demanding PSPs you don't support. Every custom PSP integration is 2-5 months of engineering time. A payment layer gives you 40+ PSPs through one integration. - PCI compliance is consuming security resources. If your security team is spending months on PCI audits rather than securing your core application, you're carrying compliance burden that can be eliminated. - You're evaluating becoming a PayFac. In most cases, the economics that drove the PayFac model have changed. Managed models now offer comparable economics without the regulatory burden. ## The Middle Path: PSP-Neutral Abstraction The build vs buy framing suggests a binary choice. In practice, there's a middle path that gives platforms the benefits of both: integrate with a PSP-neutral payment layer that provides the abstraction you'd build, without the cost of building it. This is how Shuttle works. Platforms integrate once. That single integration connects to 40+ PSPs. Adding or removing a PSP is configuration, not a code change. PCI compliance is handled at the layer -- card data never enters the platform's environment, keeping the platform at SAQ-A (the lightest compliance level). The platform retains full control over the payment experience. White-label checkout, merchant onboarding, and transaction management are branded as the platform's own. The end merchant never sees Shuttle. Crucially, this approach eliminates vendor lock-in rather than creating it. Because the layer is PSP-neutral, the platform can switch the underlying PSP at any time. The integration is with the layer, not with any individual PSP. That's more flexibility than building direct integrations, not less. ## The Decision Framework Buy (Payment Layer) Time to live 6-18 months Year 1 cost Usage-based, no upfront Full Level 1 SAQ-A (minimal) Multi-PSP support Each integration is a project 40+ PSPs included Ongoing maintenance Permanent engineering cost Handled by provider Control over UX Full (white-label) PSP flexibility Limited by what you've built Add/remove as config Core product impact Engineers diverted Engineers stay focused The question isn't whether your team CAN build payment infrastructure. Most strong engineering teams can. The question is whether they SHOULD -- whether the 12+ months and £1M+ investment produces more value than spending those resources on the product your customers actually pay for. For platforms where payments are infrastructure, not product, the answer is almost always to buy. ## Further Reading - Get Payments Off Your Roadmap - Embedded Payments Without Becoming a PayFac - When SaaS Outgrows Stripe Connect - What Is Embedded Payments? - Payment Layer Explained ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Shuttle vs Building Payment Infrastructure In-House ### Voice AI Is Booming -- But Can It Take a Payment? ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations ### 5 Reasons you shouldn't build payments integrations in-house ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Links - [mandate their own gateways](/guides/enterprise-psp-mandates/) - [the threshold for Level 1 is 300,000 transactions](/guides/pci-compliance-cost-platforms/) - [At scale, this becomes the dominant operational cost](/guides/payment-operations-at-scale/) - [add or remove PSPs as configuration rather than code](/guides/psp-neutral-vs-single-psp/) - [merchant underwriting, KYC/AML, fraud monitoring, and regulatory reporting](/guides/embedded-payments-without-payfac/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [hijacked by payment integrations](/guides/get-payments-off-your-roadmap/) - [40+ PSPs through one integration](/guides/what-is-embedded-payments/) - [the economics that drove the PayFac model have changed](/guides/embedded-payments-without-payfac/) - [payments are infrastructure, not product](/guides/payment-layer-explained/) - [Get Payments Off Your Roadmap](/guides/get-payments-off-your-roadmap/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [When SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [Payment Layer Explained](/guides/payment-layer-explained/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Building Payment Infrastructure In-House→](/vs/build-in-house/) - [BlogVoice AI Is Booming -- But Can It Take a Payment?→](/blog/voice-ai-payment-infrastructure-gap/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogPayment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations→](/blog/payment-links-for-fortis/) - [Blog5 Reasons you shouldn't build payments integrations in-house→](/blog/5-reasons-you-shouldnt-build-payments-integrations-in-house/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) --- URL: https://www.shuttleglobal.com/guides/build-vs-buy-payment-links/ --- # Build vs Buy: Should Your Platform Build Its Own Payment Links? | Shuttle > If you run a software platform, you almost certainly built your own payment links. # Build vs Buy: Should Your Platform Build Its Own Payment Links? By Shuttle Team, June 9, 2026 If you run a software platform, you almost certainly built your own payment links. You are a tech company with engineering resource, the payment companies hand you hosted elements that do the heavy lifting, and stitching them into a links layer is a few days of work. Payments did not feel hard, so you built the minimum, shipped it, and moved on to the product that actually differentiates you. That is a completely reasonable instinct, and for a real subset of platforms it remains the right one. But the minimum has a ceiling most teams never price in. Hosted elements solve the one thing that is genuinely easy, capturing a card on the happy path. They do not solve the parts that are actually hard, and they leave the most valuable part of payments, the economics, entirely on the table. This guide is the build-vs-buy decision for platforms that already have a basic links layer. It is written for product leaders, founders, and engineering managers who think of payments as a solved feature, and want to sanity-check whether the minimum they built is quietly capping the platform. If you have not built anything yet, the same framework tells you where the line is. ## Why Building the Minimum Feels Right It is worth stating plainly why the minimum is the default, because the decision later only makes sense if you respect the logic that got you here. - You have the tech resource. Building is what your team does well, so building feels cheaper and safer than buying. - Hosted elements make payments look solved. The PSPs give you drop-in components that handle the card capture, so the visible problem is small. You aggregate a couple of payment APIs, put a links layer on top, and it works. - The happy path is genuinely easy. A single processor, one currency, a hosted page. That part really is a few days. - Payments is not your product. A "good enough" payment experience is a rational trade when your roadmap is full of things that actually differentiate you. None of that is a mistake. The gap is not in the decision to build the minimum. It is in assuming the minimum is the whole problem. ## What the Hosted-Element Happy Path Hides Hosted elements solve capturing a card. Everything below is what they do not solve, and what the minimum links layer leaves on the table. None of this shows up on day one, which is exactly why it is easy to miss. - Payment revenue you are not capturing. Your links move money for your customers and you earn nothing on it. Payments can be a margin line, not just a feature, and the platforms treating it that way are pulling ahead. This is usually the single biggest thing the minimum costs you. See how platforms monetise payments. - One PSP, until you need more. The moment a customer has their own acquirer, a negotiated rate, or a region your processor does not serve, you need a second integration, then a third. Hosted elements do not give you multi-PSP routing. Each one is a fresh build. - No per-customer routing. Each of your customers may want their own processor and their own merchant account. A hardcoded PSP behind a hosted element cannot route per tenant. - Multi-currency and cross-border. The minimum works in one currency and one country. Expansion turns into payments engineering instead of go-to-market. - Compliance you did not plan for. Even with hosted elements, the way most teams build means card data or its handling drifts into your logs, support tooling, or other channels, which pulls your platform toward the expensive end of PCI DSS scope. See the cost of PCI compliance for platforms. - Channels the link cannot reach. Customers increasingly want to pay over the phone, inside an AI voice or chat agent, or through agentic checkout. A link-only layer has no path there. - A payment experience you deprioritised. The minimum ships a mediocre flow. You are fine with that today, but it is a real conversion and trust gap that compounds as you scale. The point is not that you are in pain. Most platforms at this stage feel fine, because the costs above are invisible or deferred. The point is that the minimum is a local maximum: it solved the easy 20% and stopped, and the other 80% is where both the risk and the upside live. ## The Minimum Is Cheap to Build and Expensive to Do Well Build-vs-buy goes wrong when teams compare the cost of buying against the cost of the minimum they already built, rather than the cost of doing payments properly. The minimum is cheap precisely because hosted elements did the hard capture work for you. But production-grade payments across processors, currencies, channels, and compliance is real engineering: multi-PSP routing, tokenisation, retries, refunds, reconciliation, per-tenant configuration, and a permanent compliance burden. That work never ends, because processors change APIs and compliance requirements shift. So the honest choice is not "build a links layer for a few days" versus "buy." It is: either keep pointing your engineering resource at payments depth that is not your differentiator, or stop at the minimum and live with its ceiling. An embedded layer removes that dichotomy. See build vs buy payment infrastructure for the fuller cost model. ## Build vs Buy: A Decision Framework As a tech company your default is to build, and for your core product that default is correct. Payments is the specific exception, because the depth is large and it is not what differentiates you. Use these questions to decide where the line sits for you. Keep building makes sense when: - You serve one market, one currency, and one processor, and expect that to hold. - You have no near-term need for multi-PSP routing, per-customer routing, or new channels. - You do not intend to treat payments as a revenue line. - You genuinely want to own payments as a product and will staff it as one. Buy an embedded layer when: - You want payments to be a margin line, not money you move for free. - You need more than one PSP, or expect to, including letting customers bring their own gateway. - Your customers each need their own processor and merchant account. - You operate or plan to operate across currencies or regions. - You want card data out of your scope so PCI stops being your concern. - You need to take payments across channels: links, phone, AI voice and chat agents, agentic checkout. - You would rather your engineers ship your product than maintain payment depth. ## DIY Payment Links vs an Embedded Payment Layer Dimension | DIY links layer (hosted elements) | Embedded payment layer Card capture | Solved by hosted elements | Solved, plus everything below Payment revenue | None, you move money for free | Revenue share built in Processors | One per integration you build | 40+ via one integration, bring your own gateway Per-customer routing | Hardcoded, hard to vary | Route each tenant to their own processor Multi-currency / region | Build per market | Routed by currency, region, or customer PCI scope | Drifts into yours | Held by a PCI Level 1 provider, kept out of yours Channels | Hosted link only | Links, phone/DTMF, AI voice and chat agents, agentic checkout Engineering focus | Your team maintains payments | Your team ships your product ## What an Embedded Payment Layer Gives You An embedded payment layer sits underneath your platform and owns the depth, so your team keeps building your product. Shuttle is one such payment layer: you keep the customer relationship and the experience, the layer handles processing, routing, compliance, and the economics. - Payments as revenue, not a free feature. Capture economics on the payments your platform already enables. For most platforms this is the line that changes the build-vs-buy maths on its own. - Your engineers back on your product. The depth that is not your differentiator becomes the layer's job. See get payments off your roadmap. - Multi-PSP from one integration. Connect to 40+ gateways once, add or switch processors without re-integrating, and let each customer bring their own gateway. - Per-tenant routing. Route each customer's transactions to their own processor and merchant account. - PCI scope lifted off you. Card data flows through the layer's PCI DSS Level 1 environment, not your servers, logs, or support screens, keeping your platform out of PCI scope. - One layer across channels. The same integration covers links, phone payments, AI voice and chat agents, and agentic checkout, so new channels are configuration, not a new build. Buying is not conceding that payments is too hard for your team. It is the opposite: it frees the team that could build it to build your actual product, while you finally capture the part of payments that pays. ## Frequently Asked Questions We are a tech company with engineering resource. Why would we buy instead of build? Because the part you can build cheaply (card capture via hosted elements) is not where the value or the difficulty is. The value is in payment revenue, multi-PSP routing, per-customer configuration, compliance, and new channels, all of which are real ongoing engineering that is not your differentiator. Buying redirects your resource to your product and captures payment economics you currently give away. Should my platform build or buy payment links? Build when you serve one market, one currency, and one processor, you do not need per-customer routing or new channels, and you do not intend to monetise payments. Buy an embedded layer when you want payment revenue, multiple PSPs, per-tenant routing, multi-currency, additional channels, or card data out of your PCI scope. Isn't a basic links layer with hosted elements good enough? For a narrow, stable scope, yes. The risk is that "good enough" is a ceiling: it captures no payment revenue, ships a mediocre experience, and stops short of multi-PSP, per-tenant routing, compliance at scale, and new channels. Those costs are deferred, not absent. Can we keep our existing PSP if we adopt an embedded layer? Yes. A gateway-neutral layer lets you keep your current acquirer and pricing, and lets each customer bring their own. You are not forced onto a single provider. See single-PSP risk. How does buying help us monetise payments? A DIY links layer moves money for your customers and earns nothing on it. An embedded layer is built to share payment revenue with the platform, turning payments from a free feature into a margin line. ## Related Reading - What is embedded payments: the category this decision sits inside. - Build vs buy payment infrastructure: the fuller cost model behind the decision. - When SaaS outgrows Stripe Connect: the same ceiling, told through one common starting point. - The payment layer explained: what an embedded layer is and how it differs from a gateway or PayFac. - How platforms monetise payments: turning payments from a feature into a revenue line. ## Decide With the Full Picture, Not Just the Happy Path If your links layer captures no payment revenue and stops at the happy path, it is worth pressure-testing build-vs-buy properly before the next processor, currency, or compliance request lands. Talk to our team about embedded payments ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ## Links - [multi-PSP](/guides/what-is-payment-orchestration/) - [PCI DSS](/glossary/pci-dss/) - [the cost of PCI compliance for platforms](/guides/pci-compliance-cost-platforms/) - [build vs buy payment infrastructure](/guides/build-vs-buy-payment-infrastructure/) - [DTMF](/guides/dtmf-payments/) - [payment layer](/guides/payment-layer-explained/) - [get payments off your roadmap](/guides/get-payments-off-your-roadmap/) - [40+ gateways](/payment-providers/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [single-PSP risk](/guides/single-psp-risk/) - [What is embedded payments](/guides/what-is-embedded-payments/) - [Build vs buy payment infrastructure](/guides/build-vs-buy-payment-infrastructure/) - [When SaaS outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [The payment layer explained](/guides/payment-layer-explained/) - [Talk to our team about embedded payments](/contact/) - [Book a Call](/discovery/) - [BlogPayment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations→](/blog/payment-links-for-fortis/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) --- URL: https://www.shuttleglobal.com/guides/builders-merchant-payment-collection/ --- # Payment Collection for Builders Merchants: Links, Voice & Open Banking | Shuttle > The Builders Merchant Cash Flow Problem Builders merchants and trade suppliers operate on tight margins with long payment cycles. # Payment Collection for Builders Merchants: Links, Voice & Open Banking By Shuttle Team, April 1, 2026 ## The Builders Merchant Cash Flow Problem Builders merchants and trade suppliers operate on tight margins with long payment cycles. The typical flow: - Tradesperson places an order -- on account, by phone, or in the branch - Goods are delivered or collected - An invoice is sent -- 30, 60, or 90 day terms - The merchant chases payment -- phone calls, emails, statements - Payment arrives -- eventually -- via bank transfer or cheque This cycle creates predictable problems: overdue accounts, manual chasing, disputed invoices, and cash flow gaps that constrain the business. The payment infrastructure most builders merchants rely on -- card terminals at the counter, phone payments where staff take card numbers verbally, and bank transfers that need manual reconciliation -- hasn't kept up with the volume and complexity of trade account management. ## Three Improvements That Change the Cash Flow Picture ### 1. Payment Links for Trade Accounts Instead of sending a paper or PDF invoice and waiting, send a payment link alongside it. The customer gets an SMS or email with a branded checkout page. They tap to pay -- by card, open banking, Apple Pay, or Google Pay. The payment is confirmed instantly. No chasing. No waiting for bank transfers to clear. Where this makes the biggest difference: - Statement payments -- send a monthly payment link alongside the account statement. One tap to pay the balance rather than writing a cheque or setting up a bank transfer. - COD and pro-forma orders -- send a payment link before dispatch. Goods only ship when payment is confirmed. Eliminates bad debt on new accounts. - Overdue accounts -- instead of another phone call or letter, send a payment link with a clear amount and due date. Lower friction means faster payment. - Delivery surcharges and ad-hoc charges -- send a quick link for one-off amounts without generating a full invoice cycle. ### 2. Open Banking for High-Value Orders Builders merchants regularly process high-value transactions -- bulk materials, project orders, large account balances. A £10,000 timber order at 2% card processing fees costs £200 in fees. Across 200 high-value transactions per month, that's £40,000/year in card fees alone. Pay by Bank (open banking) lets the customer pay directly from their bank account. Near-instant confirmation. No card fees. No chargebacks. Shuttle supports Pay by Bank alongside card payments on the same payment link. The customer chooses their payment method at checkout. For high-value transactions, a simple nudge -- "Save on this order with Pay by Bank" -- can shift a significant percentage of volume away from card rails. For builders merchants doing £5M+ in annual revenue, the card fee savings from open banking alone can be £50,000-£100,000 per year. ### 3. Voice Checkout for Phone Orders Trade customers order by phone constantly. A plumber needs pipe fittings delivered to site. A builder calls to add to their running account. A project manager orders materials for next week's job. When these calls include a payment -- COD, pro-forma, or settling an overdue balance -- most merchants either: - Take card details verbally (PCI compliance risk) - Ask the customer to call back and pay at the branch (friction) - Send a link after the call and hope they pay (drop-off) Voice checkout captures payment during the call. The customer enters card details via keypad while the staff member stays on the line. Card tones are masked -- staff never hear the numbers. Payment completes in seconds. For merchants handling 50+ phone orders per day, this eliminates the gap between "order placed" and "payment collected" for phone-based transactions. ## Replacing Manual Credit Control The real cost for builders merchants isn't payment processing fees -- it's the people and time spent chasing overdue accounts. A credit controller making 30 calls per day to chase payments is expensive and inefficient. Most of those calls end with "I'll pay it next week" -- which means another call next week. Payment links shift this from human-chasing to digital nudging: - Automated reminders -- send an SMS payment link 7 days before due date, on due date, and 7 days overdue - Escalation sequences -- email → SMS → WhatsApp, each with a payment link - Self-service -- the customer pays when it suits them, without scheduling a call with your credit team The credit controller's time shifts from chasing payments to managing exceptions -- the 10% of accounts that genuinely need human intervention rather than the 90% that just need a convenient way to pay. ## What to Evaluate ### Multi-channel delivery Trade customers vary. Younger tradespeople prefer SMS and WhatsApp. Established builders prefer email. Accounts departments prefer email with PDF attachment plus payment link. Your payment solution should support all of these. ### Branding Payment pages should carry your merchant brand. MKM, Jewson, Travis Perkins -- customers recognise and trust the brand. A generic third-party checkout page for a £5,000 payment creates unnecessary doubt. ### Account integration Can payment links be triggered from your ERP or trade account system? Integration with systems like Intact, K8, Merlin, or industry-specific platforms eliminates manual link creation. API access and workflow connectors (Zapier, Make.com) bridge the gap without custom development. ### Payment method mix Cards for small transactions. Open banking for high-value orders. Apple Pay and Google Pay for speed. The checkout should present all options and let the customer choose. ### Reconciliation Payment activity should reconcile automatically with trade accounts. At minimum, transaction reference mapping (invoice number → payment) should be automated so the accounts team isn't manually matching bank statements. ### PCI compliance If your staff take card details over the phone -- which most branch and telesales teams do -- you have a PCI compliance exposure. A PCI DSS Level 1 certified payment provider removes card data from your environment entirely. ## FAQ Can I send payment links for trade account balances? Yes. Generate a payment link for any amount -- a single invoice, a monthly statement balance, or a custom amount. Send via SMS, email, or WhatsApp. The customer pays in one tap. Will this work with our existing ERP / trade account system? Shuttle provides API access and integrations with Zapier and Make.com. Most ERP systems can trigger a payment link via webhook or API call when an invoice is generated or an account reaches a threshold. No custom development needed for standard integrations. What about customers who don't have smartphones? Email payment links work on any device with a web browser. For customers who genuinely prefer phone payment, voice checkout captures card details via keypad during the call -- PCI-compliant and no smartphone required. How much can we save with open banking? Depends on your transaction volume and average order value. A builders merchant processing £500,000/month in card payments at 2% fees pays £10,000/month. If 50% of high-value transactions shift to Pay by Bank, the annual saving is roughly £60,000. The higher your average transaction value, the bigger the saving. Is this suitable for branch counter payments too? Yes. QR codes displayed at the counter link to a branded checkout page. Customers scan and pay from their phone -- useful for busy branches where terminal queues slow things down, or for card declines where an immediate alternative is needed. Can I use this for new customer deposits / pro-forma? Absolutely. This is one of the strongest use cases. Send a payment link before dispatching goods. Payment is confirmed instantly. No risk of goods-on-account for unproven customers. ## Related Reading - How to Send Payment Requests -- the complete guide to digital payment collection - Shuttle vs Prommt -- comparing payment link providers for high-value transactions - Prommt Alternatives for Platforms -- the landscape of payment request providers - Best Payment Link Providers (2026) -- ranked comparison of payment link services - What Are Voice Payments? -- how voice checkout works for phone-based payment collection - UK Guide to Collecting Overdue Payments -- the legal and practical framework for UK debt collection - QuickBooks Payment Links -- if your accounting runs on QuickBooks - Xero Payment Links -- if your accounting runs on Xero - Payment Links on Invoices -- why adding payment links to invoices accelerates collection Collect faster. Chase less. Save on card fees. Shuttle gives builders merchants payment links, voice checkout, and open banking -- from $49/month. Stop chasing payments manually and start collecting digitally. See Payment Links | Book a Demo ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### 5 Payment Workflows That Work Better With Payment Links ### What Is Local Acquiring? How It Cuts International Payment Costs ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants ## Links - [Voice checkout](/platforms/voice-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [voice checkout](/platforms/voice-checkout/) - [How to Send Payment Requests](/guides/how-to-send-payment-requests/) - [Shuttle vs Prommt](/vs/prommt/) - [Prommt Alternatives for Platforms](/alternatives/prommt/) - [Best Payment Link Providers (2026)](/guides/best-payment-link-providers/) - [What Are Voice Payments?](/guides/voice-payments/) - [UK Guide to Collecting Overdue Payments](/guides/uk-guide-collecting-overdue-payments/) - [QuickBooks Payment Links](/guides/quickbooks-payment-links/) - [Xero Payment Links](/blog/xero-payment-links/) - [Payment Links on Invoices](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [See Payment Links](/merchants/links-checkout/) - [Book a Demo](/discovery/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [Blog5 Payment Workflows That Work Better With Payment Links→](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants→](/blog/payment-links-for-bs-payone/) --- URL: https://www.shuttleglobal.com/guides/car-dealership-payment-solutions/ --- # Payment Solutions for Car Dealerships & Auto Finance Platforms | Shuttle > The Problem With Car Dealership Payments Car dealerships process some of the highest-value consumer transactions outside of property -- and they do it with... # Payment Solutions for Car Dealerships & Auto Finance Platforms By Shuttle Team, February 25, 2026 ## The Problem With Car Dealership Payments Car dealerships process some of the highest-value consumer transactions outside of property -- and they do it with some of the worst payment infrastructure in any industry. A typical car purchase involves: - A deposit -- often £500-£2,000, collected to secure the vehicle - A balance payment -- £5,000-£50,000+, collected before or at handover - Part-exchange adjustment -- the difference after trade-in valuation - Finance deposit contribution -- if the customer is financing, a cash element paid to the dealer Each of these payments currently involves one of: - A bank transfer (manual, slow, error-prone, no instant confirmation) - A card payment over the phone (PCI compliance risk, staff time, card limits) - A card payment in person (customer must visit the dealership) - A cheque (still happens, incredibly) For a dealership selling 200+ vehicles per month, the admin burden of chasing bank transfers, reconciling payments against stock, and handling declined cards is substantial. Finance teams spend hours every day on payment follow-up that should be automatic. ## What Modern Automotive Payment Infrastructure Looks Like ### Payment Links A payment link is a URL sent to the customer via email, SMS, or WhatsApp that opens a branded payment page. The customer clicks, pays, and both parties get instant confirmation. For car dealerships, payment links transform the collection process: Deposits. Customer agrees to buy a car. The salesperson sends a payment link from their phone or CRM. The customer pays the deposit in 30 seconds. The car is marked as sold in the DMS. No bank transfer, no phone call, no trip to the dealership. Balance payments. Before collection day, the dealership sends a link for the outstanding balance. The customer pays from home. By the time they arrive to collect the car, the payment has already cleared. Service and parts. The service department diagnoses an issue and needs approval for additional work. Send a payment link with the quote. Customer approves and pays in one step. Auction and trade purchases. Dealers buying at auction or from other dealers can receive payment links for immediate settlement -- faster than waiting for bank transfers between trade accounts. ### Pay by Bank (Open Banking) For high-value automotive transactions, Pay by Bank is a significant shift. Instead of the customer entering card details, they authenticate directly with their bank and authorise the payment. The money moves via Faster Payments (in the UK) -- settling in seconds, not days. Why this matters for dealerships: - No card processing fees on large transactions. A 2.5% fee on a £30,000 car is £750. Pay by Bank typically costs a flat fee or a fraction of a percent. The saving is substantial at volume. - Higher payment limits. Card transactions are often limited to £10,000-£25,000 depending on the card and issuer. Bank transfers have much higher limits -- critical for prestige and commercial vehicle sales. - Instant settlement. Unlike card payments that settle in 2-3 business days, Faster Payments settle immediately. The dealer has the funds before the customer drives away. - No chargebacks. Bank transfers are irrevocable. For dealerships that have experienced chargeback fraud on high-value card transactions, this eliminates the risk. One major UK dealership group (Motorpoint, 20+ stores) reported saving over £100,000 in card processing fees within 8 months of adopting Pay by Bank for vehicle purchases. ### Multi-PSP Flexibility Dealer groups -- 5, 20, 100+ locations -- often have complex payment setups. Different sites may have different acquiring banks. The group may have a centrally negotiated rate with one PSP but individual franchises mandate a different processor. A single-PSP payment solution forces every site onto one gateway. A PSP-neutral approach lets each site use its preferred processor while the group gets unified reporting and a consistent customer experience. This is especially relevant for franchise dealer networks, where each franchise is independently owned but operates under a shared brand and technology stack. ## Use Cases by Dealership Type ### Independent Dealers Independent dealers (1-3 sites) need simplicity: a way to send payment links from their DMS or CRM, collect deposits and balances, and reconcile against vehicle stock. Key requirements: - Payment links via email and SMS - Pay by Bank for high-value transactions - Integration with their DMS (CDK, Keyloop, Pinewood, etc.) - Branded payment pages (dealer's logo, not a third-party brand) ### Dealer Groups Groups (10-200+ sites) need everything above plus: - Centralised reporting across all sites - Per-site PSP configuration -- different processors for different locations - Role-based access -- salespeople create links, finance managers approve refunds, group finance sees everything - Consistent branding with per-site customisation (different logos/addresses per location) ### Auto Finance Platforms Software platforms that serve dealerships -- DMS providers, finance origination systems, dealer management platforms -- need to embed payment collection into their product. Rather than each dealer integrating their own payment solution, the platform provides it as a built-in feature. Dealers get payment links, Pay by Bank, and card processing through the platform they already use -- branded as the platform, not as a third-party payment provider. ### Vehicle Auction Houses Auction houses collect high-value payments from trade buyers -- often under time pressure. Payment links sent immediately after the hammer falls, with Pay by Bank for instant settlement, replace the slow bank transfer process that delays vehicle release. ## DMS and CRM Integration Payment links are most effective when they're triggered from the systems dealers already use. DMS integration (CDK, Keyloop, Pinewood, Dealerweb) means a salesperson can generate a payment link directly from the vehicle record. The payment amount auto-populates from the deal. When the customer pays, the DMS record updates automatically. No manual entry, no reconciliation. CRM integration means payment links can be part of automated follow-up sequences. A customer completes an online reservation -- the CRM sends a deposit link automatically. Balance due in 7 days -- the CRM sends a balance link with a reminder. Accounting integration means payments reconcile against invoices without manual matching. The finance team sees which vehicles have been paid for and which are outstanding, in real time. The depth of integration depends on the payment solution. API-based solutions offer the most flexibility for platform-level integrations. Dashboard-based solutions (create links manually, send via copy-paste) work for smaller dealers but don't scale. ## PCI Compliance for Dealerships Car dealerships that take card payments over the phone are in PCI scope. This means: - Staff handling card data need PCI training - Phone systems may need call recording pause/resume functionality - Card details must never be written down, emailed, or stored in CRM notes - Annual PCI compliance validation is required Many dealerships are unknowingly non-compliant. A salesperson jotting down a card number on a Post-it note to process later is a PCI violation -- and it happens constantly. Payment links eliminate this risk entirely. The customer enters their card details on a PCI-compliant hosted payment page. Card data never touches the dealership's systems, phones, or networks. The dealership's PCI scope drops to the minimum level. For dealer groups, this is a significant compliance simplification. Instead of ensuring PCI compliance across 50 sites with hundreds of staff, the payment link provider carries the PCI burden. ## Comparing Payment Approaches for Car Dealerships Bank Transfer Phone Card Payment In-Person Card Pay by Bank Customer experience Poor -- manual process Moderate -- time on phone Good -- but requires visit Excellent -- 30-second mobile Excellent -- bank app auth Settlement speed 2-3 days (card) / instant (bank) Payment limits £10-25K typical Card limits apply High (bank limits) Processing cost Free (but admin cost) 1.5-2.5% (card) Flat fee / low % PCI burden None (hosted page) Reconciliation Semi-automated Chargeback risk Yes (card) / None (bank) For most dealerships, the optimal approach is a mix: payment links with Pay by Bank as the default for high-value transactions, and card payment as a fallback. ## FAQ What does Pay by Bank cost compared to card processing? Card processing for automotive typically runs 1.5-2.5% per transaction (interchange plus acquirer margin). On a £20,000 vehicle, that's £300-£500 in fees. Pay by Bank providers typically charge a flat fee (£0.50-£2.00 per transaction) or a very low percentage (0.1-0.3%). The saving on a single high-value transaction can be hundreds of pounds. Can customers still pay by card? Yes. Payment links typically offer both card and bank transfer options on the same page. The customer chooses their preferred method. For lower-value payments (service bills, parts, deposits under £1,000), card payment is often the path of least resistance. How do payment links work with finance deals? For financed purchases, the customer typically pays a cash deposit to the dealer, with the finance company paying the balance. The payment link collects the customer's cash element. The finance payout is handled separately between the finance provider and the dealer's account. What about refunds? Payment link solutions support refunds through the same system -- full or partial refunds processed back to the original payment method. For Pay by Bank transactions, refunds are typically processed as outbound bank transfers. Is this PCI compliant? Yes. Payment links hosted by a PCI DSS Level 1 provider limit the dealership's PCI scope for those transactions. The customer enters card data on the provider's hosted page. No card data touches the dealer's systems, which is a significant improvement over phone-based collection. ## Related Reading - PSP-Neutral vs Single-PSP -- why dealer groups need multi-PSP flexibility - What Are Payment Links? -- payment link fundamentals - Contact Centre Payments -- PCI-compliant phone payments for dealership call centres - Enterprise PSP Mandates -- when franchise groups mandate specific processors - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the four categories of payment infrastructure - Embedded Payments Without Becoming a PayFac -- for platforms adding payments without the regulatory burden - How B2B Service Companies Collect Payments Faster - Payment Collection for Field Service Teams Building a platform for car dealerships or auto finance? Talk to Us | See How It Works ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments ### Payment Methods in Mexico: OXXO, SPEI & Credit Cards (2026) ### Payment Methods in Kenya: M-Pesa, Cards & Mobile Money (2026) ## Links - [PSP-neutral approach](/guides/psp-neutral-vs-single-psp/) - [PCI-compliant](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PSP-Neutral vs Single-PSP](/guides/psp-neutral-vs-single-psp/) - [What Are Payment Links?](/glossary/payment-links/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [Payment Collection for Field Service Teams](/guides/field-agent-payment-collection/) - [Talk to Us](/discovery/) - [See How It Works](/platforms/) - [See Links Checkout](/merchants/links-checkout/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [BlogShuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers→](/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments→](/blog/payment-links-for-cardconnect/) - [BlogPayment Methods in Mexico: OXXO, SPEI & Credit Cards (2026)→](/blog/the-most-popular-payment-methods-in-mexico/) - [BlogPayment Methods in Kenya: M-Pesa, Cards & Mobile Money (2026)→](/blog/the-most-popular-payment-methods-in-kenya/) --- URL: https://www.shuttleglobal.com/guides/cardconnect-twilio-integration/ --- # How to Connect CardConnect to Twilio for Voice & IVR Payments | Shuttle > CardConnect is one of the few gateways Twilio supports natively. Alongside Stripe, Braintree, Base Commerce, Chase Paymentech, and Adyen, Twilio ships a... # How to Connect CardConnect to Twilio for Voice & IVR Payments By Shuttle Team, June 28, 2026 CardConnect is one of the few gateways Twilio supports natively. Alongside Stripe, Braintree, Base Commerce, Chase Paymentech, and Adyen, Twilio ships a first-party CardConnect Pay Connector that plugs straight into the verb. If you process with CardConnect and want to take card payments during phone calls, you have a genuine choice of two integration paths. This guide covers both: Twilio's native CardConnect connector, and Shuttle's Pay Connector, which supports CardConnect as one of 30+ other gateways. Which one fits depends on how many gateways and merchant accounts you run, and what you need beyond a simple in-call charge. ## Two Ways to Connect CardConnect to Twilio Twilio's native CardConnect connector Shuttle's Pay Connector CardConnect only CardConnect plus 30+ others through one connector Payment types Card charge and tokenise Card and ACH debit, charge and tokenise Twilio-side fees Usage-based per-transaction billing since 13 October 2025 $0.20 per successful transaction, tiering down to $0.05 above 1M/month Multi-merchant routing One gateway per connector instance Route per merchant, client, or region from one integration Failover and PSP switching Not applicable (single gateway) Configure in the Shuttle dashboard, no TwiML changes Token reuse CardConnect tokens for your CardConnect integration Tokens reusable across voice, web, and payment links Regional availability Available in Twilio's IE1 and AU1 regions Your PCI scope SAQ-A (Twilio captures, CardConnect processes) SAQ-A (Shuttle is a PCI DSS Level 1 Service Provider) Short version: a single CardConnect account and a straightforward in-call charge or tokenise flow is exactly what the native connector was built for. Multiple gateways or merchant accounts, cross-channel token reuse or enterprise PSP requirements point to Shuttle. ## About CardConnect CardConnect is a Fiserv company built around the CardPointe platform, with a large US merchant base and a strong ISV channel that integrates payments through the CardPointe Gateway API. Its CardSecure service handles tokenisation, storing card numbers in a PCI-compliant vault and returning tokens so merchants keep raw card data out of their systems. For voice payments, the pieces you need are your CardConnect merchant ID (MID) and API credentials. Both integration paths below use them; the difference is where you configure them. ## Path 1: Twilio's Native CardConnect Pay Connector Twilio's branded CardConnect connector is installed from the Twilio Console. Enable PCI mode on your account, install the connector, give the instance a unique name, and add your CardConnect credentials. Your TwiML then points at that connector instance, and Twilio routes captured card data to CardConnect for processing. A few characteristics to plan around: - Single gateway. Twilio's native connectors each talk to one gateway. Your CardConnect connector instance processes through CardConnect, full stop. - Charge and tokenise only. exposes , , , and . There is no refund API and no auth/capture split through Twilio; you handle those directly in CardPointe. - MOTO treatment. Twilio tags payments through its Stripe and CardConnect connectors as MOTO (telephone order) transactions, which are exempt from PSD2's SCA requirements. There is no 3DS flow in . - Billing changed in October 2025. The CardConnect Pay Connector was previously free of Twilio-side fees. Twilio moved it to usage-based per-transaction billing effective 13 October 2025, so factor the per-transaction cost into your comparison rather than assuming the native path is free. If that shape matches your setup (one CardConnect account, in-call charges or tokenisation, refunds handled in CardPointe), the native connector is a solid, first-party choice. ## Path 2: CardConnect via Shuttle's Pay Connector Shuttle's Pay Connector launched on Twilio in December 2023 and treats CardConnect as one gateway among 30+. The flow looks like this: Card data passes from Twilio's PCI-compliant environment to Shuttle, a PCI DSS Level 1 Service Provider, which processes the transaction through your CardConnect merchant account. Your systems only ever see redacted results. ### Step 1: Install Shuttle's Pay Connector Install the Shuttle Pay Connector from the Twilio Marketplace. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add CardConnect as a Payment Profile In the Shuttle dashboard, create a payment profile with CardConnect as the gateway, using your CardConnect merchant ID and API credentials. Set your default currency and choose the test (UAT) or live environment. If you run multiple merchant accounts, create a profile for each. ### Step 3: Point at Shuttle ### Step 4: Handle the Result Your webhook receives the transaction status, card brand, last four digits, and a confirmation reference you can look up in CardPointe. Confirm to the caller and continue the call flow. ### Step 5: Test, Then Go Live Run the full flow against CardConnect's UAT environment before switching your Shuttle profile to production credentials. ## What Shuttle Adds on Top of CardConnect - Card and ACH debit. Shuttle's connector supports ACH debit alongside cards, useful for larger invoice values where card fees bite. - Charge and tokenisation. Capture a card once on a call, then reuse the token across channels: another call, a web checkout, or a payment link sent by SMS or email. - Multi-gateway routing. Keep CardConnect for your US volume and route other regions or clients to different gateways. The TwiML never changes; provider selection lives in Shuttle's dashboard. - Failover. If one gateway has an outage, route to a backup without touching your call flows. That last group matters most for two audiences. BPOs and outsourced contact centres collecting for many clients can give each client their own gateway and merchant account behind one Twilio integration. And platforms serving enterprise customers often hit PSP mandates, where a customer's procurement team dictates the gateway. A multi-gateway connector absorbs those mandates without new integration work. One caveat to note when scoping either path: Twilio Studio's Capture Payments widget is documented as Stripe-only, so plan on TwiML or your own call orchestration rather than Studio for CardConnect flows. ## PCI Compliance Both paths keep card data out of your systems. With Shuttle in the chain, scope splits like this: PCI handled by DTMF capture and suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing CardConnect (Fiserv) Your systems No card data: SAQ-A Your application only receives redacted data, which keeps you at SAQ-A, the lightest self-assessment and the smallest possible PCI scope. For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Does Twilio have a native CardConnect Pay Connector? Yes. CardConnect is one of Twilio's branded Pay Connectors, alongside Stripe, Braintree, Base Commerce, Chase Paymentech, and Adyen. It is also available in Twilio's IE1 and AU1 regions. Is the native CardConnect connector free? Not any more. Twilio moved the CardConnect Pay Connector to usage-based per-transaction billing effective 13 October 2025. It was previously free of Twilio-side fees. Why use Shuttle if Twilio already supports CardConnect? Multi-gateway flexibility. Shuttle connects CardConnect and 30+ other gateways through one connector, adds ACH debit, reuses tokens across channels, and routes per merchant or client. If you only ever need one CardConnect account and in-call charges, the native connector is the simpler choice. Can I take refunds or do auth/capture through Twilio ``? No. supports charge and tokenise (, , , ). Refunds and captures happen in your gateway tooling, such as CardPointe. What about SCA and 3DS on phone payments? Twilio tags payments through its Stripe and CardConnect connectors as MOTO (telephone order) transactions, which are exempt from PSD2 SCA. There is no 3DS flow in . What does Shuttle cost? $0.20 per successful transaction on the first 50,000 transactions per month, tiering down to $0.05 above 1 million. CardConnect's processing fees apply on top. No setup fees or monthly minimums. Can I switch gateways later without changing my Twilio integration? With Shuttle, yes. Change the gateway in your payment profile and the verb keeps pointing at . With the native connector, moving off CardConnect means installing and configuring a different connector. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway covers every connector option and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data explains how to stay at SAQ-A - How to Connect Stripe to Twilio for Voice Payments compares the other native-connector path - How to Connect Braintree to Twilio for Voice Payments covers Twilio's Braintree option - CardConnect on Shuttle lists supported features and channels - Twilio Pay: Connect Any Payment Gateway to Twilio has all supported gateways, pricing, and setup *Connect CardConnect to Twilio your way: native for a single account, Shuttle for everything else. PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [CardConnect Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [CardConnect](/payment-providers/cardconnect/) - [payment links](/merchants/links-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [payment link](/merchants/links-checkout/) - [BPOs and outsourced contact centres](/guides/payment-collection-for-bpos/) - [PSP mandates](/guides/enterprise-psp-mandates/) - [DTMF capture](/guides/dtmf-payments/) - [PCI scope](/glossary/pci-scope/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Braintree to Twilio for Voice Payments](/guides/braintree-twilio-integration/) - [CardConnect on Shuttle](/payment-providers/cardconnect/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments→](/blog/payment-links-for-cardconnect/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/chat-agent-payments/ --- # Chat Agent Payments: How AI Closes Sales Without a Human Handoff | Shuttle > The Checkout Redirect Is Killing Your Conversion A customer is mid-conversation with your AI chat agent. # Chat Agent Payments: How AI Closes Sales Without a Human Handoff By Shuttle Team, December 26, 2025 ## The Checkout Redirect Is Killing Your Conversion A customer is mid-conversation with your AI chat agent. They've asked questions, compared options, and decided to buy. The agent says: "Great -- here's a link to complete your purchase." The customer clicks through to a checkout page. They re-enter information the agent already knows. They get distracted. They abandon. This is the checkout redirect problem. Every time a chat agent pushes a customer out of the conversation to complete a payment, you lose a percentage of them. Industry data puts chat-to-checkout drop-off between 40-60% depending on the category and friction involved. The customer was ready to pay. The process made them stop. The fix isn't a better checkout page. It's removing the redirect entirely. Payment capture happens inside the conversation -- the customer never leaves the chat thread. AI chat agents that can capture payments inline convert at fundamentally higher rates than agents that redirect to external checkout. The customer stays in context. The payment feels like part of the conversation, not a separate transaction. But building this creates a hard technical problem -- the same one AI voice agents face, expressed differently. ## Why Chat Payments Are Different from Web Checkout Web checkout assumes a browser. The customer is on a product page, clicks "buy," and a checkout form appears. The entire flow is built around a screen, a form, and a submit button. Chat payments break that assumption. The customer isn't on a product page. They're in a conversation -- on a website widget, on WhatsApp, on Facebook Messenger, on SMS, or inside a platform's messaging system. The "interface" is a chat thread, not a web form. This creates three specific challenges: 1. Context lives in the conversation, not the page. In web checkout, the product, price, and customer intent are expressed by the page itself. In chat, they're expressed through dialogue. The AI agent has built context over multiple messages -- what the customer wants, which option they've chosen, what the price is. Redirecting to a checkout page throws that context away and forces the customer to rebuild it. 2. The capture mechanism must fit the channel. A full-page checkout form doesn't work inside a WhatsApp message. A Stripe Elements embed doesn't render in an SMS thread. The payment capture mechanism has to be native to the messaging channel -- a secure inline form, a compact payment card within the chat, or a branded payment link that opens a minimal hosted checkout. 3. Card data must never enter the chat. This is the PCI compliance constraint. If a customer types their card number into a chat message -- even if the AI agent tells them not to -- that card data is now in the chat log, the AI model's context window, the message database, and potentially the analytics pipeline. Every one of those systems is now in PCI scope. The architecture must make it impossible for card data to enter the chat flow. Payment capture happens in a separate, PCI-certified environment that the chat agent triggers but never sees into. ## The Architecture: How Chat Agent Payments Work An AI chat agent that captures payments needs the same four-layer architecture as a voice agent -- with a different capture mechanism. ### 1. Conversational Layer The AI chat agent handles the dialogue. It understands what the customer wants, guides them through options, confirms pricing, and recognises when a payment should happen. This runs on the platform's AI infrastructure -- LLMs, intent classifiers, or purpose-built conversational AI. The rule is absolute: The conversational layer never sees card data. Not in a message. Not in a form field. Not in a webhook payload. ### 2. Payment Trigger When the customer is ready to pay, the AI agent triggers the payment layer via API. It sends the transaction details -- amount, currency, customer reference, PSP configuration -- and receives back a payment capture mechanism appropriate to the channel: - Website chat widget: A secure iframe or payment form rendered inline within the chat window - WhatsApp / messaging platforms: A branded payment link that opens a minimal hosted checkout - SMS: A payment link sent as a message - Platform messaging: An embedded payment card or secure form, depending on the platform's capabilities The customer sees a seamless transition. Behind the scenes, the payment capture has moved to a PCI-certified environment. ### 3. PCI-Compliant Capture Environment The customer enters card details within this environment -- not within the chat. On web, this is typically a secure iframe that renders inside the chat widget but is hosted by the payment layer. On messaging platforms, it's a hosted checkout page accessed via link. The capture environment handles: - Card data entry and validation (BIN check, Luhn) - Tokenisation (for future transactions) - 3D Secure authentication (if required) - Gateway routing (to the correct PSP) - Transaction processing The chat agent's systems never see raw card data. They receive a transaction result: approved, declined, or pending authentication. ### 4. Payment Gateway(s) The transaction routes to whichever PSP the business uses -- Stripe, Worldpay, Adyen, or any of 40+ supported gateways. For platforms serving multiple merchants, routing is based on the merchant's configured PSP, geography, or business rules. For a deeper look at how this architecture works across both voice and chat, see How AI Agents Process Payments: The Infrastructure Guide. ## How It Works: A Practical Example A customer messages an insurance platform's AI chat agent on the company website: Customer: "I need to renew my home insurance. Policy number HI-2847291." AI Agent: "I've found your policy. Your renewal quote is £342.50 for the year, with the same cover level. Would you like to renew now?" Customer: "Yes, go ahead." AI Agent: "I'll take your payment now. Please enter your card details in the secure form below." A secure payment form appears inline within the chat widget. The form is an iframe hosted by the PCI-certified payment layer -- visually integrated with the chat but completely isolated from the AI agent's environment. The customer enters card details in the secure form and clicks "Pay £342.50." Behind the scenes: the payment layer validates the card, routes the transaction to the insurer's configured PSP (Worldpay), processes the payment, and returns the result to the chat agent via API. AI Agent: "Your payment of £342.50 has been processed. Your policy HI-2847291 is renewed through 15 March 2027. I've sent a confirmation to your email on file. Is there anything else I can help with?" Total time from "yes, go ahead" to payment confirmed: under 30 seconds. Human involvement: none. Card data in the chat system: none. ## The PCI Problem for Chat Chat creates a unique PCI risk that doesn't exist in web checkout: the customer can type their card number into the chat. In web checkout, there's no text input where a customer could accidentally (or intentionally) enter card data outside the secure form. In chat, there is -- the message input field. If a customer responds to "please enter your card details" by typing "4532 1234 5678 9012" into the chat, that card number is now: - In the chat message history - In the AI model's context window - In the platform's message database - Potentially in analytics, logging, and monitoring systems - Potentially in training data - How Voice AI Ordering Platforms Handle Payments -- the voice channel equivalent for food ordering platforms - Payment Infrastructure for Food Ordering Platforms -- multi-channel payment capture for food platforms (voice, chat, links) Every one of those systems is now in PCI scope. The remediation cost is enormous. ### How to Prevent It 1. Never ask for card data in the chat. The AI agent should say "please enter your card details in the secure form below" -- never "please type your card number." The language must direct the customer to the secure capture mechanism, not the chat input. 2. Intercept and redact. Implement a real-time filter on incoming chat messages that detects card number patterns (sequences of 13-19 digits passing Luhn validation) and redacts them before they enter the AI model's context or any logging system. This is a safety net, not a primary control. 3. Render the secure form immediately. Don't make the customer wait for the payment form to load. If there's a delay between the agent saying "I'll take your payment" and the secure form appearing, the customer may type their card number into the chat as a shortcut. 4. Design the UI to make the right action obvious. The secure payment form should be visually prominent within the chat. The chat input should be de-emphasised or temporarily disabled during payment capture. Make it easier to use the secure form than to type a card number. 5. Audit chat logs. Regularly scan stored chat transcripts for card number patterns. If any are found, redact them immediately and investigate how they bypassed the interception layer. This is defence in depth. The primary control is the architecture -- card data is captured in a PCI-certified iframe, not in the chat. The secondary controls (interception, redaction, UI design) catch the edge cases. ## Chat vs. Voice: Same Problem, Different Mechanics Chat and voice agents face the same fundamental challenge -- capturing payment during a conversation without card data touching the AI. The mechanics differ: Chat Agent | Voice Agent Capture mechanism | Secure iframe / hosted form / payment link | DTMF keypad tones within PCI environment Card data risk | Customer types card into chat message | Customer speaks card aloud / tones reach AI audio Mitigation | Iframe isolation + message redaction | DTMF tone stripping from audio stream Channel variants | Website, WhatsApp, Messenger, SMS, platform chat | IVR, agent-assisted, AI voice Visual feedback | Form shows card type, validation in real time | Audio confirmation only 3D Secure | Renders inline or in new tab -- seamless | Requires SMS link fallback or phone-based auth Conversion advantage | Customer sees total + form in context | Customer hears amount, no visual confirmation Chat has one significant advantage over voice for payment capture: the customer has a screen. This means secure forms can render inline, 3D Secure authentication can happen within the same session, and the customer gets visual confirmation of the amount and card details before submitting. Voice has a different advantage: no risk of the customer typing card data into the wrong field. The capture mechanism (DTMF) is inherently separate from the conversational channel (speech). Both channels benefit from the same underlying payment infrastructure -- a PCI-certified layer that handles capture, tokenisation, and gateway routing. Platforms that support both voice and chat agents should use a single payment layer for both, rather than building separate integrations. For a detailed look at how voice payment capture works, see AI Voice Agents and Payments: The PolyAI Deep Dive. ## Where Chat Payments Create the Most Value Chat agent payments aren't a horizontal feature. They create outsized value in specific scenarios: ### Quote-to-Bind in Insurance The AI chat agent qualifies the customer, presents a quote, answers questions about coverage -- and when the customer says "yes," captures payment and binds the policy. No email follow-up. No "log into your account to complete." The sale closes in the conversation where the intent was expressed. ### Upsell During Support A customer contacts support about their subscription. The AI agent resolves their issue and identifies an upgrade opportunity. "Based on your usage, the Pro plan would save you £40/month. Would you like to upgrade now?" Payment captured inline. No redirect to the billing page. ### Debt Collection and Payment Plans A collections agent (AI or human-assisted) negotiates a payment arrangement. When the customer agrees to a payment, the agent captures it immediately -- while the commitment is fresh. Sending a payment link "after the call" or "via email" introduces delay and reduces follow-through. ### E-Commerce Pre-Sale and Consultation A customer asks an AI agent about product sizing, compatibility, or availability. The agent answers their questions and offers to complete the purchase: "I have that in stock in your size. Shall I process the order?" Payment captured in the chat. The customer never navigates to a product page or cart. ### Booking and Deposits Travel, healthcare, professional services -- any business that takes bookings with deposits. The AI agent confirms the appointment or reservation and captures the deposit payment inline. No separate booking confirmation email with a payment link that gets ignored. ### B2B Invoice Payment An AI agent on a supplier's platform helps a buyer locate an invoice, confirms the amount, and captures payment on the spot. Faster than logging into a portal. Faster than downloading a PDF and paying via bank transfer. The conversation resolves the query and the payment in one interaction. ## Multi-PSP: The Same Enterprise Requirement The multi-PSP problem is identical in chat and voice. Platforms serving multiple merchants can't mandate a single PSP. An AI chat agent deployed by an insurance platform needs to route payments to whichever PSP each insurer uses. A chat agent embedded in a SaaS platform needs to support Stripe for one merchant and Worldpay for another. An enterprise customer evaluating your platform will ask: "Can we use our existing PSP?" The chat agent doesn't know or care which gateway processes the payment. It triggers a payment session. The payment layer routes to the correct PSP based on the merchant's configuration. This is why a PSP-neutral payment layer matters for chat just as much as for voice. The alternative -- hardcoding Stripe into your chat payment flow -- works until the first enterprise customer says "we use Adyen." ## Messaging Platforms: Channel-Specific Considerations Chat agent payments aren't limited to website chat widgets. AI agents operate across messaging platforms, each with its own constraints. ### Website Chat Capture method: Secure iframe rendered inline within the chat widget. Advantage: Full control over the UI. Can render rich payment forms with card type detection, inline validation, and Apple Pay / Google Pay buttons. Consideration: The iframe must be hosted by the PCI-certified payment layer, not by the chat platform. Same-origin restrictions apply. ### WhatsApp Business Capture method: Branded payment link sent as a message. Customer taps the link, completes payment on a hosted checkout page, and returns to the chat. Advantage: Massive global reach. WhatsApp has 2+ billion users. Businesses are already using it for customer communication. Consideration: WhatsApp doesn't support embedded iframes or rich payment forms within the chat. Payment links are the primary mechanism. The hosted checkout page must be mobile-optimised and fast-loading. ### Facebook Messenger / Instagram DMs Capture method: Payment link or webview. Meta's platform supports webviews that can host a payment form within the Messenger app. Advantage: Rich media support. Webviews can provide a near-native payment experience. Consideration: Meta's commerce policies apply. Webview behaviour can change with platform updates. ### SMS Capture method: Payment link sent via text message. Advantage: Universal reach -- works on every phone, no app required. Consideration: SMS is one-way for payment capture. The customer completes payment on a hosted page and the result is returned to the chat agent via webhook. The conversation can continue once payment is confirmed. ### Platform-Native Messaging Capture method: Varies by platform. Could be embedded forms, payment cards, or links depending on the platform's extensibility. Advantage: Deeply integrated experience. The payment feels native to the platform. Consideration: Each platform has different capabilities. A payment layer that supports multiple output formats (iframe, hosted page, payment link) adapts to each platform without requiring custom integration per channel. ## What to Look For in Chat Payment Infrastructure If you're building AI chat agents that need to process payments -- or embedding chat payment capability into a platform -- evaluate on: ### PCI-Certified Capture The payment form or hosted checkout must be hosted within a PCI DSS Level 1 certified environment. Card data must never enter your chat infrastructure, AI model, or message storage. ### Channel Flexibility Does the payment layer support inline iframes (for web chat), hosted checkout pages (for messaging platforms), and payment links (for SMS)? Or is it built for one channel only? ### Gateway Coverage How many PSPs are supported? Can your merchants or enterprise customers bring their own PSP? Adding a gateway shouldn't require re-engineering your chat payment flow. ### Tokenisation Can a card captured via chat be reused for future payments -- including payments initiated through other channels (voice, web, payment link)? Cross-channel tokenisation means the customer enters their card once. ### 3D Secure Support Strong Customer Authentication (SCA) is mandatory for many European transactions. The payment form must support 3D Secure challenges inline -- without breaking the chat flow or forcing the customer into a separate browser session. ### Latency Chat is real-time. If the payment form takes seconds to load, or the transaction result takes too long to return, the customer's attention moves elsewhere. The payment layer must be fast enough to feel instant within a chat conversation. ### Card Data Interception Does the payment layer provide tooling to detect and redact card numbers accidentally typed into the chat? This is a safety net that reduces PCI risk from customer behaviour. ## FAQ Can customers really pay inside a chat conversation? Yes. On website chat, a secure payment form renders inline within the chat widget. On messaging platforms like WhatsApp, a branded payment link opens a hosted checkout. In both cases, the customer completes payment without leaving the conversation context. Is it PCI compliant to take payments in a chat? It is -- if the architecture ensures card data never enters the chat system. Payment capture happens in a PCI-certified iframe or hosted checkout, not in the chat message flow. The AI agent and chat platform never see card data. What if a customer types their card number into the chat? This is the primary PCI risk for chat payments. Mitigation includes: directing customers to the secure form (never asking for card data in chat), implementing real-time card number detection and redaction on incoming messages, and designing the UI to make the secure form the obvious input method. Do chat payments work on WhatsApp? Yes, via payment links. The AI agent sends a branded payment link within the WhatsApp conversation. The customer taps the link, completes payment on a mobile-optimised hosted checkout, and the result is confirmed back in the chat. Can I use the same payment infrastructure for chat and voice agents? Yes -- and you should. A PSP-neutral payment layer that supports both DTMF capture (for voice) and hosted forms / payment links (for chat) means one integration covers all conversational channels. Cards tokenised via voice can be reused in chat, and vice versa. What about Apple Pay and Google Pay in chat? Supported via the secure payment form on web chat (where the browser supports wallet APIs) and via the hosted checkout page for messaging platforms. The payment layer handles wallet transactions through the same PSP routing as card payments. How does this work with 3D Secure / SCA? 3D Secure challenges render within the secure payment form (on web) or the hosted checkout page (on messaging platforms). The chat agent doesn't need to handle authentication -- the payment layer manages the full SCA flow and returns the final transaction result. Ready to add payments to your AI chat agents? See how Shuttle connects chat agents to 40+ payment gateways -- with PCI DSS Level 1 compliance, inline secure forms, hosted checkout, and payment links across every messaging channel. Talk to Us | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Agentic Payments Isn't Solved Yet ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### The First Agentic Payments Went Live. Here's What the Infrastructure Looks Like. ## Links - [voice agent](/guides/voice-payments) - [How AI Agents Process Payments: The Infrastructure Guide](/guides/ai-agent-payments) - [How Voice AI Ordering Platforms Handle Payments](/guides/voice-ai-ordering-payments/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [DTMF](/guides/dtmf-payments/) - [AI Voice Agents and Payments: The PolyAI Deep Dive](/guides/ai-voice-agents-payments) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Talk to Us](/contact) - [See How It Works](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogThe First Agentic Payments Went Live. Here's What the Infrastructure Looks Like.→](/blog/agentic-payments-go-live/) --- URL: https://www.shuttleglobal.com/guides/checkout-com-twilio-integration/ --- # How to Connect Checkout.com to Twilio for Voice & IVR Payments | Shuttle > Checkout.com doesn't natively connect to Twilio for voice payments. If you want to process Checkout.com transactions during a phone call -- via IVR,... # How to Connect Checkout.com to Twilio for Voice & IVR Payments By Shuttle Team, March 21, 2026 Checkout.com doesn't natively connect to Twilio for voice payments. If you want to process Checkout.com transactions during a phone call -- via IVR, agent-assisted, or AI voice agent -- you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Checkout.com (and 30+ other gateways) to Twilio's `` verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Checkout.com + Twilio Don't Connect Directly Checkout.com is a cloud-native payment processor built for high-growth businesses and enterprise platforms. Its APIs handle payment sessions, intelligent routing, and performance-optimised processing across global markets. Twilio is built for voice and messaging. Its `` verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's `` needs a Pay Connector to route captured card data to a payment gateway. Checkout.com isn't one of Twilio's built-in connectors -- there's no native integration. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's `` verb and routes it to Checkout.com's API for processing. One integration connects the two platforms. ## How It Works ``` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Checkout.com (processing) → Result ``` - Caller reaches payment step. Your Twilio call flow -- IVR, Studio, or custom TwiML -- triggers the `` verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Checkout.com. The connector creates a Checkout.com payment request, processes the transaction, and handles the response. - Result returned to your call flow. Your webhook receives the Checkout.com payment ID, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Checkout.com account with API credentials (secret key + processing channel ID) - A Shuttle account (free to create -- you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Checkout.com Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Checkout.com - Secret key: Your Checkout.com secret key (`sk_...`) - Processing channel ID: Your Checkout.com channel ID - Currency: Set your default (GBP, USD, EUR, etc.) - Environment: Live or Sandbox Save the profile. Shuttle now has a live connection to your Checkout.com account. ### Step 3: Configure Your Twilio Call Flow Add the `` verb to your TwiML or Twilio Studio flow: ```xml Please enter your card number followed by the hash key. ``` Key parameters: - `paymentConnector` -- set to `shuttle-pay-connector` - `chargeAmount` -- the amount to charge - `currency` -- ISO currency code - `action` -- your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your `action` URL with the payment result: ```json "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-9012", "PaymentCardType": "visa", "PaymentConfirmationCode": "pay_abc123...", "ProfileId": "your-shuttle-profile-id" ``` Use the `PaymentConfirmationCode` to look up the transaction in Checkout.com's Dashboard or API. ### Step 5: Test Use Checkout.com's sandbox environment and Twilio's test credentials to verify the flow end-to-end. Checkout.com test card: `4242 4242 4242 4242` (Visa, always approved). ## What You Can Do With Checkout.com + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Checkout.com processes, done. ### Authorise Now, Capture Later Place a hold on the card during the call. Capture the payment later via the Checkout.com API -- useful for bookings, pre-orders, or transactions where the final amount may change. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Checkout.com and returns a reusable token. Use it for future payments across any channel -- web, mobile, voice, or payment links. The card data is never stored in your systems. ### Marketplace & Platform Payments If you use Checkout.com's marketplace or sub-entity model, Shuttle can route voice payments to the correct sub-entity. Each merchant's transactions are processed and settled through their own Checkout.com configuration. ## Multi-PSP: Beyond Checkout.com One of the key advantages of using Shuttle rather than a Checkout.com-only connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway -- serve your European merchants with Checkout.com and your US merchants with Stripe - Serve enterprise customers who mandate a specific PSP -- some require Checkout.com, others require Adyen or Worldpay - Want a backup gateway -- if Checkout.com is down, you can move the affected payment types to another connected gateway - Expand to new regions where a local acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. This is particularly important for platforms and BPOs serving multiple merchants -- each with their own Checkout.com account or alternative gateway. ## PCI Compliance The Checkout.com + Twilio integration via Shuttle limits your PCI scope: Layer | PCI handled by DTMF capture & suppression | Twilio Card data processing | Shuttle (PCI DSS Level 1) Payment processing | Checkout.com (PCI DSS Level 1) Your systems | No card data -- SAQ-A Card data flows from Twilio → Shuttle → Checkout.com. Your application only receives redacted data (last 4 digits, card brand, payment ID). You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Checkout.com to Twilio without Shuttle? Twilio doesn't have a built-in Checkout.com Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework -- handling PCI compliance yourself. Shuttle provides a pre-built, PCI-certified connector. Does this work with Twilio Studio? Yes. Twilio Studio supports the `` widget. Configure it with `shuttle-pay-connector` as the connector and the payment flow works within your Studio flow. Can I use Checkout.com's Flow (intelligent routing) with this? Checkout.com's intelligent routing applies at the processing level. Transactions sent via Shuttle go through your Checkout.com account and benefit from any routing optimisations configured there. What does it cost? Shuttle charges $0.20 per successful transaction. Checkout.com's processing fees apply on top (your negotiated rate). No Shuttle setup fees or monthly minimums. Can I switch from Checkout.com to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same -- no code changes needed. Does this support 3D Secure? Voice payments via DTMF are card-not-present transactions. 3D Secure requires browser-based authentication, so it doesn't apply to phone payments. Your Checkout.com risk settings handle fraud screening for voice transactions. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments -- step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice Payments -- step-by-step Adyen + Twilio setup - How to Connect Worldpay to Twilio for Voice Payments -- step-by-step Worldpay + Twilio setup - Shuttle vs Checkout.com for Platforms -- comparing payment infrastructure approaches - Adyen vs Checkout.com for Platforms -- head-to-head comparison - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup Connect Checkout.com to Twilio in minutes with Shuttle's Pay Connector -- PCI DSS Level 1, $0.20/transaction, no setup fees. [Install on Twilio](/integrations/twilio-pay/) or [book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Shuttle vs Checkout.com for Platforms ### Checkout.com Alternatives for Platforms ### Payment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### Agentic Commerce: How AI Will Rewrite the Checkout ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [How to Connect Worldpay to Twilio for Voice Payments](/guides/worldpay-twilio-integration/) - [Shuttle vs Checkout.com for Platforms](/vs/checkout-com/) - [Adyen vs Checkout.com for Platforms](/guides/adyen-vs-checkout-com/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Book a Call](/discovery/) - [ComparisonShuttle vs Checkout.com for Platforms→](/vs/checkout-com/) - [AlternativeCheckout.com Alternatives for Platforms→](/alternatives/checkout-com/) - [BlogPayment Links for Checkout.com: No-Code Payment Links on Your Checkout.com Account→](/blog/payment-links-for-checkout-com/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) --- URL: https://www.shuttleglobal.com/guides/cisco-webex-payments/ --- # How to Take Payments on Cisco Webex Contact Centre: Secure Voice Payments | Shuttle > Cisco Webex Contact Centre Has No Native Payment Capture Cisco Webex Contact Centre, formerly Cisco Contact Center Enterprise (UCCE) and Cisco Unified... # How to Take Payments on Cisco Webex Contact Centre: Secure Voice Payments By Shuttle Team, February 24, 2026 ## Cisco Webex Contact Centre Has No Native Payment Capture Cisco Webex Contact Centre, formerly Cisco Contact Center Enterprise (UCCE) and Cisco Unified Contact Center Express (UCCX), is one of the most widely deployed enterprise contact centre platforms in the world. It handles complex routing, multi-channel interactions, workforce optimisation, and integrates with the broader Cisco collaboration ecosystem. What it does not do is securely capture card payments during a live call. Cisco Webex Contact Centre was built for communication management. When a customer needs to pay during a call, the platform offers no built-in mechanism to collect card details without exposing your agents, recordings, and infrastructure to cardholder data, and the full weight of PCI compliance that comes with it. For enterprises running Cisco Webex Contact Centre in financial services, insurance, utilities, healthcare, and government, this is not a minor gap. It is a compliance and operational problem that affects thousands of calls daily. ## The Payment Gap in Cisco Webex Contact Centre Cisco's contact centre platform has evolved through multiple generations, from UCCE and UCCX to the current cloud-native Webex Contact Centre. Across all versions, payment capture remains absent from the core product. No secure card capture built in. Cisco Webex Contact Centre processes DTMF for IVR menu navigation, but there is no built-in mechanism to capture card entry securely while keeping the digits out of the agent audio stream and call recording. When a customer reads or keys in card digits, the agent hears them and the recording captures them. Recording infrastructure is always in scope. Cisco Webex Contact Centre uses Webex Recording or integrates with enterprise recording platforms like Verint, NICE, or Calabrio. All of these record the full audio stream. Pause-and-resume is available but unreliable at scale, it depends on agent compliance and introduces human error. Even when executed correctly, the agent still hears the card number spoken or toned. Enterprise complexity compounds the problem. Cisco deployments tend to be large, complex, and deeply integrated with enterprise infrastructure, Active Directory, CRM systems, WFM platforms, analytics suites. Adding PCI scope to this environment means every connected system must be assessed, segmented, and potentially hardened. The compliance burden is proportional to the complexity of the deployment. No multi-gateway support. Cisco's platform has no native payment routing. If you build a custom payment integration, it connects to one gateway. Large enterprises with multiple PSP relationships across divisions or regions need a solution that routes to different gateways based on business rules, something Cisco does not provide. AI and analytics exposure. Cisco Webex Contact Centre includes AI-powered features, virtual agents, conversation analysis, agent assist. If card data enters the audio stream, it flows through these AI systems. Transcriptions contain card numbers. Analytics dashboards may surface them. The same AI capabilities that add value to the platform amplify the PCI risk. ## How Shuttle Adds Payments to Cisco Webex Contact Centre Shuttle adds PCI-compliant card capture to your Cisco Webex Contact Centre payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Cisco Webex Contact Centre recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Cisco Webex Contact Centre specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Cisco Webex Contact Centre call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Cisco Webex Contact Centre have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment, they never reach your Cisco recordings, your connected CRM, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links via SMS or email This is the most turnkey path. The agent triggers a payment link sent to the customer's mobile via SMS or email, including mid-call to a customer still on the line. The customer completes payment on a hosted, PCI-compliant checkout page, and the result is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Cisco Webex Contact Centre, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Cisco Webex Contact Centre have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - Standard call handling. The customer calls in and is routed through Cisco Webex Contact Centre as normal. The agent handles the conversation, account queries, service requests, issue resolution. - Agent initiates payment. When payment is required, the agent triggers the capture from the interface you've built against Shuttle's APIs. The customer is prompted to enter their card details. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay, the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. The digits never reach the agent. - Transaction processing. Shuttle routes the payment to the configured PSP, any of 30+ supported gateways. Provider selection can be set per merchant and payment type. - Result returned. The transaction outcome (approved, declined, or error) appears in your interface in real time. A tokenised payment reference is available for logging to your CRM or Cisco Finesse. - No card data in Cisco. The card digits never touch your Cisco recordings, your CRM, or your agent workstations. ## Multi-PSP Support Enterprise Cisco Webex Contact Centre deployments frequently serve multiple business units, divisions, or regions, each with established PSP relationships. Shuttle supports 30+ payment gateways with flexible routing: - By division: different business units route payments to their contracted PSP - By geography: UK transactions to Worldpay, European transactions to Adyen, US transactions to a domestic processor - By switching: automatic fallback to a secondary gateway if the primary is unavailable - By payment type: card, ACH and other payment types can each go to a different connected provider For large enterprises with complex payment architectures, this multi-PSP capability is essential. Shuttle does not require you to consolidate to a single gateway, your existing PSP relationships remain intact. Switching gateways later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification in the payment card industry. Because the card is captured in the secure Twilio Pay call, your PCI scope drops to SAQ-A: - Card data never enters your Cisco infrastructure - Card digits are captured inside Shuttle's certified environment, not your Webex Contact Centre, recording platform, or analytics systems - Call recordings contain no cardholder data - AI transcription and conversation analysis process no card information - Agents never hear, see, or handle card numbers - Your CUBE/SBC, network infrastructure, and CRM remain out of PCI scope The alternative, handling card data within your Cisco environment, puts your entire contact centre infrastructure in scope for SAQ-D: 300+ requirements, annual QSA audits, network segmentation, encryption mandates, and compliance costs that scale with the complexity of your deployment. For enterprise Cisco environments, this typically means seven-figure annual compliance programmes. Full compliance documentation, including the AOC scope, is in the security docs. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Financial Services Banks, building societies, and financial institutions running Cisco Webex Contact Centre handle card payments for loan repayments, account top-ups, and fee collection. PCI compliance in financial services is subject to regulatory scrutiny from the FCA and PRA. Shuttle keeps card data out of the contact centre environment entirely, simplifying compliance and reducing audit scope. ### Insurance Large insurers are among Cisco's core enterprise customer base. Premium collection, policy renewals, excess payments, and claims settlements happen over the phone daily. Shuttle allows agents to collect payment during the conversation, maintaining the personal touch that drives retention, without PCI exposure. ### Healthcare NHS trusts, private healthcare providers, and health insurers running Cisco Webex Contact Centre can collect payments for prescriptions, appointments, excess fees, and premium payments. Shuttle's SAQ-A compliance model simplifies healthcare's already demanding regulatory environment. ### Government and Public Sector Local authorities, central government agencies, and public bodies use Cisco contact centre platforms extensively. Council tax, parking fines, licence fees, and service charges can be collected securely during calls, meeting both PCI DSS requirements and government procurement security standards. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Cisco Webex Contact Centre plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Cisco Webex Contact Centre specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Cisco Webex Contact Centre call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Cisco Webex Contact Centre have already done it. - A native Cisco Webex Contact Centre integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Cisco Webex integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Cisco Webex Contact Centre. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Cisco Webex Contact Centre have already done. We can build a native Cisco Webex integration as a paid project, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work even with gateways that don't support voice capture. ### How does Shuttle keep card data out of Cisco's call recording? The card is captured in the secure Twilio Pay call, not within your Cisco audio stream, so the digits never reach your recording infrastructure. Whether you use Webex Recording, Verint, NICE, Calabrio, or another platform, recordings contain no cardholder data. No pause-and-resume configuration is needed. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### What does it cost? $0.20 per successful transaction for voice. No setup fees, no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the complete guide to secure contact centre payments - Twilio Pay Connectors, how Shuttle works with Twilio's payment infrastructure - Voice Payments, the definitive guide to taking payments over voice channels - AI Voice Agent PCI Payments, adding payment capture to AI-powered voice agents - Voice Checkout, Shuttle's voice payment product ## Get Started Shuttle adds PCI-compliant payments to a Cisco Webex Contact Centre operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. Talk to our team about adding secure payment capture to your Cisco Webex Contact Centre deployment, or explore Voice Checkout to see how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Checkout](/platforms/voice-checkout/) - [Talk to our team](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/cognigy-payments/ --- # How to Add Payments to Cognigy AI Agents: Voice & Chat Payment Integration | Shuttle > Cognigy is one of the leading enterprise conversational AI platforms. Its AI agents handle complex multi-turn conversations across voice and digital... # How to Add Payments to Cognigy AI Agents: Voice & Chat Payment Integration By Shuttle Team, March 16, 2026 Cognigy is one of the leading enterprise conversational AI platforms. Its AI agents handle complex multi-turn conversations across voice and digital channels, integrating with contact centre infrastructure from NICE, Genesys, Avaya, and others. Cognigy agents can authenticate customers, look up account details, process service requests, and escalate to human agents when needed. What they can't do natively is take a card payment. That's not a gap in Cognigy's product. It's a fundamental constraint of how AI systems and PCI compliance interact. The AI model must never see, hear, or process cardholder data. If it does, the entire platform -- Cognigy's infrastructure, your contact centre stack, your call recordings, your data pipelines -- enters PCI DSS scope. The cost of that is $500,000+ in the first year and $200,000+ annually, plus the operational burden of maintaining Level 1 certification across a complex AI infrastructure. Shuttle provides the payment layer that lets Cognigy agents capture payments without any cardholder data touching Cognigy's platform. Shuttle has no native integration with Cognigy. Instead, your application code invokes Shuttle's Twilio-based payment setup. On voice, at the point of payment the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, so the card digits are captured inside Shuttle's certified environment and never reach Cognigy, the LLM, or the agent. On chat, Shuttle sends a hosted payment link. To use the secure voice capture, you must be a Twilio customer, and your team builds the orchestration that triggers the handoff. ## The Payment Challenge for Cognigy Cognigy's strength is orchestration. Its Flow Editor lets enterprises build sophisticated conversational workflows that span voice and chat, integrate with CRMs and ERPs, and handle complex business logic. But payments introduce a requirement that sits outside the conversational AI stack entirely. When a customer says "I'd like to pay," the Cognigy agent needs to: - Capture a 16-digit card number, expiry date, and CVV - Tokenise that data and send it to a payment gateway - Process the authorisation - Return the result to the conversation Every one of those steps involves cardholder data. If that data flows through Cognigy's infrastructure -- even as audio in a voice call or text in a chat message -- the entire platform is in PCI scope. For voice channels, the challenge is acute. DTMF tones (keypad presses) carry card digits. If those tones enter Cognigy's audio processing pipeline, they're cardholder data. If they appear in call recordings, those recordings are cardholder data. If they're transcribed by the AI model, the transcription is cardholder data. For chat channels, the same principle applies. If a customer types their card number into a Cognigy chat widget, that message is cardholder data. It must never be stored, logged, or processed by Cognigy's systems. The solution is a clean architectural boundary: Cognigy handles the conversation, a separate PCI-compliant system handles the payment, and cardholder data never crosses from one to the other. ## How Shuttle Works with Cognigy Today Shuttle has no native integration with Cognigy. The handoff is API-driven: your application code triggers the Shuttle payment handoff, and the card is captured by Shuttle inside its PCI DSS Level 1 certified environment, never by Cognigy. To use the secure voice capture, you must be a Twilio customer, because today the capture runs over Twilio Pay. Shuttle provides ready-made interfaces for payment links plus the capture/IVR and the APIs. Your team builds the agent-side wiring that triggers the handoff. You can build and validate the flow against Shuttle's sandbox gateway and demo app before going live. A deeper, native Cognigy integration is possible only as a paid project. The handoff works across both of Cognigy's primary channels: ### Voice Channel - Cognigy agent triggers payment -- The AI agent identifies payment intent and confirms the amount. Cognigy's flow makes an API call to Shuttle to initiate a payment session. - Call handed to secure capture -- At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, with Shuttle as the certified connector. The card capture happens inside that secure environment, not inside Cognigy. - Card details entered -- Shuttle plays a secure prompt and the customer enters their card on the keypad. Shuttle captures the digits inside its certified environment, so they never reach Cognigy, the LLM, or any recording. - Payment processed -- Shuttle tokenises the card data and routes it to the merchant's configured gateway. The authorisation happens entirely within Shuttle's environment. - Result returned -- Shuttle sends the outcome back to Cognigy via webhook: success/failure, transaction reference, masked card number. The Cognigy agent confirms the payment in natural language. One honest caveat: the secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Cognigy agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. ### Chat Channel - Cognigy agent triggers payment -- Same as voice: the agent confirms the amount and initiates a Shuttle payment session. - Payment link generated -- Shuttle creates a secure hosted checkout page and returns a URL. The Cognigy agent sends this link to the customer within the chat conversation. - Customer completes payment -- The customer taps the link, enters their card details on Shuttle's hosted page, and submits. No card data enters Cognigy's chat infrastructure. - Result returned -- Shuttle fires a webhook with the transaction result. The Cognigy agent picks up: "Your payment has been processed. Your reference is TXN-4471." Both channels use the same Shuttle infrastructure, the same PCI-compliant environment, and the same gateway routing logic. ## How It Works: Step by Step A typical voice payment flow with Cognigy and Shuttle: Step 1: Payment intent recognised. The Cognigy agent detects that the customer wants to pay. This could be triggered by a specific utterance, a flow condition, or a backend lookup that identifies an outstanding balance. Step 2: Amount confirmed. The agent says: "I can see you have an outstanding balance of €89.00. Would you like to pay that now?" The customer confirms. Step 3: Payment context set. The agent explains the process: "I'll connect you to our secure payment line to take your card details." Step 4: Shuttle session created. Cognigy's flow executes an HTTP Request node to Shuttle's API, passing the amount, currency, and merchant configuration. Shuttle returns a session token. Step 5: Secure capture begins. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. Shuttle plays the card entry prompts, the customer enters their card on the keypad, and Shuttle captures the digits inside its certified environment. Step 6: Card data processed. Shuttle tokenises the card, sends it to the gateway, and receives the authorisation response. All within Shuttle's PCI DSS Level 1 certified perimeter. Step 7: Result returned. Shuttle sends the result to Cognigy. The flow reads the webhook payload and branches on success or failure. Step 8: Conversation continues. On success: "Your payment of €89.00 has been processed. Your reference number is TXN-7293. Is there anything else I can help with?" On failure: "I'm sorry, the payment wasn't successful. Would you like to try a different card?" The customer stays on the line throughout. To return the caller to the same Cognigy agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## Multi-PSP Support Cognigy serves large enterprises that have existing payment gateway relationships. A retail company might use Adyen. A utilities provider might process through Worldpay. A telecoms company might route through Checkout.com. Cognigy can't require its customers to switch PSPs -- and with Shuttle, it doesn't need to. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, GoCardless, and others. Each Cognigy deployment can be configured with the merchant's preferred gateway, and switching gateways is configuration, not re-integration. Advanced routing options include: - Multi-PSP routing -- Route transactions to different gateways based on currency, region, or card type - Backup gateway -- if the primary gateway is unavailable, you can move the affected payment types to another connected gateway - Per-merchant configuration -- In multi-tenant Cognigy deployments, each end merchant can have their own gateway setup This means Cognigy can offer payment capability to any customer regardless of which PSP they use. One integration with Shuttle covers all of them. One gateway caveat worth knowing: a few gateways (Braintree, for example) do not work for voice capture, because they will not allow raw card data to be passed, but they do work for payment links. ## PCI Compliance The architecture is designed to keep Cognigy and its customers out of PCI scope for cardholder data. What stays in Cognigy: - Conversation management and flow orchestration - Payment intent detection and amount confirmation - Session initiation (API call to Shuttle with amount, currency, merchant config) - Transaction result handling (success/failure, reference numbers, masked card details) None of this is cardholder data. None of it expands PCI scope. What stays in Shuttle: - Card capture during the secure Twilio Pay handoff (voice channel) - Hosted checkout page (chat channel / payment links) - Card data tokenisation - Gateway communication and authorisation - Transaction logging with full card data isolated in Shuttle's environment Shuttle is a PCI DSS Level 1 certified Service Provider. The certification covers the entire card capture, tokenisation, and routing pipeline. For Cognigy's customers: Because card data never enters Cognigy's infrastructure, end merchants can self-assess under SAQ-A -- the simplest PCI compliance questionnaire. No penetration testing requirements, no quarterly ASV scans on their systems, no on-site QSA audits for payment processing. Call recordings: On voice channels, the card is entered during the secure PCI capture, so the card details are never part of the audio Cognigy processes or records. Recordings contain no cardholder data, and nothing sensitive is stored anywhere in Cognigy's infrastructure. ## Beyond Voice: Payment Links Payment links bridge Cognigy's voice and digital channels. During any Cognigy conversation -- voice or chat -- the AI agent can send a payment link via SMS or directly in the chat window. The customer receives a link to a Shuttle-hosted checkout page. They enter their card details on a secure page, complete the payment, and the result is returned to the Cognigy agent in real time. Payment links are particularly useful for Cognigy deployments because: - Omnichannel consistency -- The same payment method works across voice, webchat, WhatsApp, and other Cognigy-supported channels - Higher-value transactions -- Customers may prefer visual confirmation for larger payments - Accessibility -- Customers who struggle with keypad entry can use the payment link instead - Chat-first flows -- On text-based channels where keypad entry isn't available, payment links are the primary method - Gateway coverage -- Links work even with gateways that do not support voice capture, such as Braintree Payment links are the turnkey path, delivered by SMS or email, including mid-call. Both in-call capture and payment link transactions are processed through the same Shuttle infrastructure, the same PCI-compliant environment, and the same multi-PSP routing. ## FAQ Does Shuttle have a native Cognigy integration? No. Shuttle has no native integration with Cognigy. The handoff is API-driven: your application code triggers Shuttle's Twilio-based payment setup, and on voice, at the point of payment the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The flow uses Cognigy's standard HTTP Request nodes and webhook handling, configured at the flow level. A deeper, native Cognigy integration is possible only as a paid project. Does this require Twilio? Yes, for the secure in-call voice capture. The capture runs over Twilio Pay today, so you must be a Twilio customer. The chat payment-link path does not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Can existing Cognigy flows add payment capability? Yes. Adding payment capture to an existing flow requires adding the Shuttle API call, the handoff to the secure capture, and the result handling. It's additive -- it doesn't require rebuilding the flow. What happens if the payment fails? Shuttle returns a failure reason to Cognigy. The AI agent can offer to retry with a different card, send a payment link as an alternative, or escalate to a human agent -- whatever the flow logic dictates. What does it cost? Shuttle charges $0.20 per successful transaction for voice, with no setup fees, and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). For technical detail, see the Shuttle docs: Twilio setup, payment links, and security and PCI. ## Related Reading - How AI Voice Agents Take PCI-Compliant Payments -- The technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide -- IVR, agent-assisted, and AI voice payment models compared - Twilio Pay Connectors -- How Shuttle connects to Twilio's payment infrastructure - The Payment Layer for AI Agents -- Why AI agents need a dedicated payment layer - Contact Centre Payments -- PCI-compliant payment capture for contact centres ## Add Payments to Your Cognigy Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're building conversational AI with Cognigy and need PCI-compliant payment capture, talk to us about Voice Checkout or see how it works for platforms. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [DTMF tones](/guides/dtmf-payments/) - [30+ payment gateways](/payment-providers/) - [Twilio setup](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](https://docs.shuttleglobal.com/docs/links-intro) - [security and PCI](https://docs.shuttleglobal.com/docs/org-security) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [talk to us about Voice Checkout](/platforms/voice-checkout/) - [see how it works for platforms](/platforms/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/content-guru-payments/ --- # Content Guru storm Payments: Native storm LOCK vs Multi-PSP Capture | Shuttle > Content Guru is a UK enterprise CCaaS provider. Its storm platform powers mission-critical contact centre operations across regulated and public sector... # Content Guru storm Payments: Native storm LOCK vs Multi-PSP Capture By Shuttle Team, May 29, 2026 Content Guru is a UK enterprise CCaaS provider. Its storm platform powers mission-critical contact centre operations across regulated and public sector environments: NHS 999 and 111 services, utilities, financial services, government agencies, and FedRAMP High deployments. If uptime, compliance, and security are non-negotiable, storm is built for exactly those requirements. storm is also one of a small number of CCaaS platforms that ships its own fully certified native payment product. Most contact centre platforms leave payment collection to third parties by default. Content Guru built storm LOCK and storm PADLOCK in-house, and both carry PCI DSS Level 1 / v4.0 certification. That is a meaningful differentiator worth understanding before reaching for a separate payment layer. This guide covers what storm's native payment capabilities actually give you, and the specific scenarios where a dedicated multi-PSP layer like Shuttle fits alongside. The answer is not either/or. For enterprises with multiple acquirer relationships, platform operators running storm across many client organisations, or operations that need cross-channel payment links beyond DTMF voice, the two complement each other rather than compete. Whether you are an enterprise running storm for your own contact centre or an SI or platform operator implementing storm for multiple clients, the framing here is: start with what storm provides natively, then assess where Shuttle adds reach. ## storm's Native Payments: What You Get Content Guru's native payment suite is genuinely strong. Before evaluating anything else, it is worth understanding the full capability: - storm LOCK (automated IVR/DTMF, no agent): fully automated payment collection over IVR. Customers key card details into the keypad at any time of day or night, with no agent involved. Suited to self-service bill-pay, top-ups, and any payment journey where the customer does not need assistance. - storm PADLOCK (agent-assisted, full PCI DSS masking): the agent remains on the call and guides the customer through the payment. Card tones are masked so the agent hears monotones rather than card digits, and the screen displays asterisks rather than the number. The agent experience stays intact; the card data does not enter the agent's environment. - PCI DSS Level 1 / v4.0 certified: storm holds the highest level of payment security certification under the current version of the standard. For regulated sectors, this is the baseline requirement, and storm meets it without additional third-party dependencies. - Multi-acquirer routing via the storm Marketplace: storm integrates with multiple payment acquirers including Worldpay, Barclaycard, GlobalPayments, Pay360, SagePay/Opayo, Cashflows, and others available through the storm Marketplace. Enterprise clients can route payments through their existing acquirer relationships. - Omnichannel reporting: payment transactions are reported alongside contact centre activity in storm's reporting suite, giving operations a single view across interactions and payment outcomes. For an enterprise standardised on storm and operating within a standard acquirer arrangement, the native payment suite handles the full requirement. There is no gap to fill. ## When You Need a Multi-PSP Payment Layer The scenarios where Shuttle adds value alongside storm are specific, not general. They tend to arise when the acquirer configuration, client structure, or channel requirements go beyond what storm's Marketplace pre-integrations address directly: - Per-client PSP switching and enterprise mandate handling: large enterprises and regulated organisations sometimes carry contractual requirements to use a named acquirer, or to route by entity, brand, or cost centre. Where those requirements span multiple clients with different mandates, a gateway-neutral orchestration layer can handle the routing logic without requiring separate storm integrations per client. - Broader PSP network beyond storm's current acquirer list: storm's Marketplace covers the major UK acquirers. If a client operates internationally, uses a gateway not on the storm Marketplace, or needs connectivity to a PSP added after their storm deployment, Shuttle's 30+ gateways extend the acquirer reach from a single integration point. - Cross-channel hosted payment links across web, SMS, and email: storm LOCK and PADLOCK are voice-channel payment methods. Where your contact centre also handles digital inbound (chat, email, web callbacks), or where agents want to send a secure payment link by SMS mid-call rather than collecting card via DTMF, a hosted payment link capability adds a channel that the native voice product does not cover. - Embedded payment orchestration for platform operators: SIs and platform operators running storm across multiple client organisations face a different challenge from a single enterprise. Managing acquirer credentials, gateway routing, and payment reporting per client organisation, across a multi-tenant deployment, is an orchestration problem. Shuttle handles per-tenant gateway configuration from one integration rather than one-per-client. - Channel-agnostic payment infrastructure: for operations that may extend beyond storm over time, or that run storm alongside other channels or platforms, a payment layer that is independent of the contact centre platform simplifies the stack. ## How Shuttle Adds Payments to Content Guru Shuttle adds PCI-compliant card capture to your Content Guru payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Content Guru recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Content Guru specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Content Guru call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Content Guru have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## Multi-PSP Support Shuttle connects to 30+ payment gateways from one integration, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. For multi-client or mandate-driven deployments, that means: - Per-tenant gateway configuration: each client organisation can use its own PSP, with provider selection and credentials managed at the tenant level inside Shuttle. - Single integration point: integrate Shuttle once at the platform level; gateway routing is configuration rather than separate code per client. - Multi-PSP configuration: select a provider per payment type, with amount and currency filters. If a gateway is unavailable you can move the affected payment types to another connected gateway. - Gateway additions without re-integration: adding a new acquirer for a new client mandate is a Shuttle configuration change, not a storm integration project. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider. Card data passes through Shuttle's certified environment and does not enter storm, your agent desktop, or your wider infrastructure. For organisations that already rely on storm's PCI-certified payment posture, Shuttle operates as a complementary layer rather than a replacement. The key distinction is ownership of the payment relationship: some deployments benefit from storm owning the full certified stack; others, particularly multi-client platform operators, benefit from a separate certified layer that handles gateway connectivity independently of the CCaaS. From a PCI scope perspective, Shuttle's architecture pushes your organisation toward SAQ-A for card-present-equivalent collections rather than the full SAQ-D obligations that would apply if card data touched your own systems. storm's own PADLOCK masking approach achieves a comparable scope reduction through a different route; the right answer depends on how your acquirer relationship and platform architecture are structured. ## Beyond DTMF: Cross-Channel Payment Links storm LOCK and PADLOCK serve the voice channel. For contact centres that also handle digital inbound, or where agents want to give customers an alternative to keypad entry, Shuttle's hosted payment links add a cross-channel option. An agent can send a secure payment link by SMS or email mid-call. The customer opens the hosted checkout on their phone or desktop, enters their card details in a standard web form, and the payment result returns to the agent in real time. The call does not need to be held for DTMF capture; the customer pays on the device they prefer. Payment links are also suited to post-call billing, written correspondence follow-up, and digital self-service journeys that originate outside the voice channel altogether. ## For Platform Operators and Content Guru Partners SIs and platform operators who implement storm for multiple clients face different commercial and technical requirements from a single enterprise running its own contact centre. The storm Marketplace and the Content Guru Partner Programme provide the integration and commercialisation framework for partners. Shuttle fits within that structure as the gateway-neutral payment layer for multi-client deployments: - Per-client PSP routing: each client organisation can bring its own acquirer relationship or use Shuttle's gateway connections directly. - One integration across all clients: instrument Shuttle once at the platform layer; manage per-client gateway configuration from Shuttle's API. - No per-seat or per-client licensing overhead: Shuttle charges $0.20 per successful transaction for voice, with no setup fees, monthly minimums, or per-seat costs. Links Checkout is a separate app; see [pricing](/pricing/). The commercial model scales with payment volume, not client headcount. - Consistent payment infrastructure if the CC platform changes: Shuttle sits below the contact centre layer, so a platform migration does not require rebuilding the payment integration. For partners operating in regulated verticals (NHS, financial services, utilities, government), Shuttle's Level 1 certification and the ability to document the payment boundary cleanly are practical assets during client procurement and compliance review. ## Use Cases ### Multi-Client and Multi-Brand Operations Platform operators running storm across multiple clients, or enterprises with several brands on a shared storm deployment, can use Shuttle to route each entity's payments to its own acquirer. Per-tenant configuration in Shuttle means no shared payment credentials across clients and a clean audit trail per organisation. ### Enterprise PSP Mandates Large regulated enterprises sometimes carry existing acquirer contracts or procurement requirements that name a specific gateway. Where that gateway is not yet on storm's Marketplace, or where the mandate requires routing logic that sits outside storm's configuration, Shuttle can handle the gateway connectivity and provider selection without a storm-layer integration project. ### Cross-Channel Bill-Pay Contact centres handling inbound billing queries across voice, chat, and email can use storm LOCK/PADLOCK for voice-channel payments and Shuttle's hosted payment links for digital channels. Customers who prefer not to enter card details on a keypad receive a link by SMS or email instead; the result feeds back to the agent in the same interaction. ### Public Sector and Regulated Collections NHS, utilities, and government contact centres have specific requirements around data residency, audit trail, and acquirer relationships. Shuttle's certified environment, per-client routing, and clean PCI boundary documentation fit the procurement language these sectors use. storm's own PCI posture handles the CCaaS layer; Shuttle handles the acquirer routing and cross-channel collection. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Content Guru plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Content Guru specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Content Guru call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Content Guru have already done it. - A native Content Guru integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Content Guru storm process payments natively? Yes. storm ships two native payment products: storm LOCK for fully automated IVR/DTMF collection with no agent, and storm PADLOCK for agent-assisted collection with full card masking. Both carry PCI DSS Level 1 / v4.0 certification and route to multiple acquirers via the storm Marketplace. This is a genuine, in-house payment capability, not a white-label resell. Why use Shuttle if storm has native payments? For most enterprises standardised on storm, the native suite handles the requirement. Shuttle adds value in specific scenarios: per-client acquirer configuration across a multi-tenant deployment, connectivity to gateways beyond storm's Marketplace, cross-channel hosted payment links for digital channels, and embedded payment orchestration for SIs managing storm for multiple client organisations. Does Shuttle have a native storm integration? Not today. Shuttle is not a storm native or Marketplace payment product. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup; you'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Content Guru have already done. We can build a native storm integration as a paid project, and a carrier-agnostic version is on our roadmap. For most storm enterprises, storm's own LOCK and PADLOCK already handle the in-platform voice experience. Does this require Twilio? Yes, today, for voice card capture. The secure capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links for digital channels don't require a Twilio voice call. The carrier-agnostic version that removes the voice Twilio requirement is on our roadmap. Which gateways does Shuttle support? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and others. Gateway coverage and provider selection are maintained at the Shuttle layer, independent of the contact centre platform. A small number (for example Braintree) work for payment links but not for voice capture, because they won't accept raw card data. Can Shuttle route per client to different acquirers? Yes. Per-tenant gateway configuration is a core part of Shuttle's multi-client architecture. Each client organisation can use its own PSP credentials, with provider selection and currency handling configured independently per tenant. Does Shuttle add payment links beyond DTMF voice? Yes. Alongside in-call DTMF capture, Shuttle supports hosted payment links sent by SMS or email. The agent triggers a secure link mid-call, the customer pays on their device, and the result returns in real time. This covers digital channel payments and customers who prefer not to use keypad entry. ## Related Reading - Contact centre payments: the full guide to PCI-compliant payment collection across voice and digital contact centre channels - Embedded payments for CCaaS: how CCaaS platforms and SIs embed multi-PSP payment capability into their deployments - What is payment orchestration?: how payment orchestration layers work and why platform operators use them - Payment collection for BPOs: PCI-compliant payment collection in multi-client BPO and outsourced contact centre environments - Payments for CCaaS implementation partners: how SIs and CCaaS implementation partners add embedded payment capability across client deployments ## Add Multi-PSP Payments Alongside storm Shuttle is a PCI DSS Level 1 certified Service Provider. It adds gateway-neutral multi-PSP capture across 30+ gateways (voice via Twilio Pay), per-client routing, and cross-channel payment links alongside storm's native payment suite. Voice is $0.20 per successful transaction, Links Checkout is a separate app; see /pricing/, with no setup fees, monthly minimums, or per-seat costs (see pricing). See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [DTMF](/guides/dtmf-payments/) - [30+ gateways](/payment-providers/) - [book a call](/contact/) - [30+ payment gateways](/payment-providers/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [$0.20 per successful transaction](/pricing/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [What is payment orchestration?](/guides/what-is-payment-orchestration/) - [Payment collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [see pricing](/pricing/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/credit-card-processing-fees/ --- # Credit Card Processing Fees Explained: What You Actually Pay | Shuttle > Every time a customer pays by card, the merchant pays a fee. That fee isn't a single charge -- it's a stack of costs from three different parties, each... # Credit Card Processing Fees Explained: What You Actually Pay By Shuttle Team, February 28, 2026 Every time a customer pays by card, the merchant pays a fee. That fee isn't a single charge -- it's a stack of costs from three different parties, each taking a cut before the money reaches the merchant's account. Most businesses know they pay "around 2-3%." Few understand where that money goes, why the rate varies between transactions, or what they can actually control. This guide breaks down exactly what credit card processing fees are, who charges them, how much they cost, and what you can do to reduce them -- whether you're a merchant, a platform, or a SaaS company embedding payments. ## What Are Credit Card Processing Fees? Credit card processing fees are the costs charged to a merchant every time they accept a card payment. The total fee -- often called the merchant discount rate (MDR) -- is deducted from the transaction amount before the merchant receives their funds. A customer pays £100 by card. The merchant receives £97.50. The £2.50 difference is the processing fee, split between three parties: - The card-issuing bank (the customer's bank) - The card network (Visa, Mastercard, Amex) - The payment processor / acquirer (the merchant's payment gateway or provider) Each takes a portion, and the size of each portion depends on the card type, transaction method, merchant category, and the processor's pricing model. ## The Three Components of Card Processing Fees ### 1. Interchange Fees Interchange is the largest component -- typically 70-80% of the total processing fee. It's set by the card networks (Visa, Mastercard) and paid to the card-issuing bank. Interchange compensates the issuing bank for the risk of extending credit to the cardholder. The rate varies based on: - Card type -- rewards cards and corporate cards carry higher interchange than standard debit cards - Transaction type -- card-present (in-store, chip and PIN) is cheaper than card-not-present (online, phone) - Merchant category -- supermarkets and utilities get preferential rates; higher-risk categories pay more - Region -- EU interchange is capped by regulation; US interchange is set by the networks Typical interchange rates: Consumer debit 0.2% (capped) 0.05% + $0.22 Consumer credit 0.3% (capped) 1.5% - 2.5% Commercial / corporate 1.0% - 1.9% 2.0% - 3.0% Rewards / premium 0.3% (EU cap applies) 2.0% - 2.5% In the EU, the Interchange Fee Regulation (IFR) caps consumer card interchange at 0.2% for debit and 0.3% for credit. This is why card processing is significantly cheaper in Europe than in the US, where no such cap exists. ### 2. Assessment Fees (Scheme Fees) Assessment fees are charged by the card networks themselves -- Visa, Mastercard, American Express. These cover the network's infrastructure, brand, and transaction routing. Assessment fees are small relative to interchange -- typically 0.02% to 0.15% per transaction. They're non-negotiable and applied uniformly. Visa and Mastercard also charge additional scheme fees for specific scenarios: cross-border transactions, currency conversion, high-value transactions, and specific merchant categories. These "miscellaneous scheme fees" have been increasing year on year and now represent a growing cost for merchants processing international transactions. ### 3. Processor Markup The processor markup is what your payment provider charges on top of interchange and assessment fees. This is the only component that's negotiable. Processor markup covers the provider's costs: fraud screening, payment gateway infrastructure, settlement, reporting, customer support, and their profit margin. The markup varies significantly between providers and pricing models. A small business on a flat-rate plan might pay 1.4% + 20p per transaction all-in, while a high-volume merchant on interchange-plus pricing might pay interchange + 0.15% + 5p. ## Pricing Models: How Processors Package These Fees Not all processors present fees the same way. The pricing model determines how transparent your costs are and how much room you have to optimise. ### Flat Rate How it works: One fixed percentage (and sometimes a fixed pence/cent amount) per transaction, regardless of card type or transaction method. Example: 1.4% + 20p for EU cards, 2.9% + 20p for non-EU cards. Who uses it: Stripe, Square, PayPal -- most self-service processors default to flat rate. Pros: Simple and predictable. Easy to budget. Cons: You overpay on debit transactions (where interchange is low) and subsidise rewards/corporate card transactions. At scale, the overpayment adds up. ### Interchange Plus (IC+) How it works: You pay the actual interchange fee + the actual assessment fee + a fixed processor markup. Example: Interchange + 0.2% + 10p. Pros: Full transparency. You pay exact cost on every transaction, plus a known markup. Debit transactions are genuinely cheap. Cons: Monthly statements are harder to read. You need to understand interchange categories to verify your bills. Who uses it: Most traditional acquirers, plus processors like Adyen and Checkout.com for higher-volume merchants. ### Blended Rate How it works: The processor groups transactions into a few categories (domestic, international, corporate) and charges a blended rate for each. Simpler than IC+ but less transparent than true interchange pass-through. Example: 1.0% for domestic consumer cards, 1.8% for international, 2.5% for corporate. Pros: Easier to understand than IC+, cheaper than flat rate. Cons: The processor pockets the difference when actual interchange is below the blended rate. ## Average Fee Ranges by Card Type and Scenario Here's what credit card processing fees look like in practice, combining all three components: Typical total fee UK debit card, in-store 0.4% - 0.7% UK credit card, in-store 0.6% - 1.0% UK debit card, online 0.5% - 0.9% UK credit card, online 0.8% - 1.5% US credit card, online 2.5% - 3.5% Corporate / purchasing card 1.5% - 3.0% American Express 1.5% - 3.5% International (cross-border) 2.0% - 4.0% For a detailed breakdown of UK-specific rates across major providers, see our guide on card processing fees and rates for UK merchants. ## In-Person vs Online: Why Online Transactions Cost More Card-not-present (CNP) transactions -- online, phone, and mail order -- consistently cost more than card-present (in-store, terminal) transactions. The reason is risk. Card-present transactions are verified at the point of sale. The chip is read, the PIN is entered (or contactless is tapped), and the card network can confirm with high confidence that the cardholder is present. Fraud rates are low. Chargebacks are rare. Card-not-present transactions rely on the card number, expiry date, and CVV -- all of which can be obtained without physical access to the card. Fraud rates are 2-3x higher than card-present. Chargebacks are more common. The issuing bank takes on more risk, so interchange rates are higher. The difference adds 0.1% to 0.5% to the transaction cost, depending on the card network and region. For businesses that take payments over the phone, there's an added layer: PCI compliance. Phone payments -- whether through IVR, live agents, or AI voice payments -- require secure handling of card data that never touches the merchant's systems. ## How Platforms and SaaS Companies Handle Processing Fees If you're building a platform where your users (merchants, sellers, service providers) accept payments, the fee picture changes. ### The Markup Stack Your merchants pay card processing fees. You, as the platform, can layer on your own markup -- either absorbing part of the processing cost or adding a fee on top. The structure depends on how you've set up your payment infrastructure. Single PSP model (e.g. Stripe Connect): Stripe charges the processing fee. You take a platform fee (application fee) from the payout. Your merchants see one combined rate. Simple, but you're locked to Stripe's pricing and can't offer merchants their own PSP choice. Multi-PSP model: Your merchants connect their own payment provider or choose from supported options. Processing fees vary by PSP. Your platform fee is independent of the processing cost. This gives merchants more flexibility and often lower total costs. For a breakdown of this approach, see how platforms monetise payments. ### What "Revenue Share" Means on Processing Fees Many platforms earn revenue on payments through a share of the processing margin -- the difference between what the platform charges the merchant and what the PSP charges the platform. With a single PSP, this margin is fixed. With multiple PSPs, you can optimise by routing merchants to the most cost-effective provider for their transaction profile. Platforms using a payment layer like Shuttle can support 40+ payment providers through a single integration, giving merchants PSP choice while maintaining a consistent platform fee structure. The platform keeps one integration regardless of which provider processes the transaction. ## How to Reduce Credit Card Processing Fees You can't eliminate processing fees, but you can reduce them significantly. Here's what actually moves the needle: ### 1. Negotiate Your Processor Markup Interchange and assessment fees are set by the card networks -- you can't change them. But your processor's markup is negotiable, especially once you have meaningful transaction volume (£50K+ monthly). Ask for interchange-plus pricing. If your processor won't offer it, get quotes from others who will. The processor markup is where the biggest savings are. ### 2. Reduce Your Effective Interchange Rate You can't negotiate interchange directly, but you can influence which interchange category your transactions fall into: - Use Address Verification (AVS) and 3D Secure -- transactions that pass additional fraud checks qualify for lower interchange categories - Submit complete transaction data -- Level 2 and Level 3 data (line items, tax amounts, customer codes) qualifies B2B transactions for lower interchange in the US - Settle quickly -- authorisations that aren't captured within 24-48 hours can be downgraded to a higher interchange tier - Avoid manual key entry -- keyed transactions are more expensive than chip, contactless, or tokenised payments ### 3. Encourage Lower-Cost Payment Methods Debit cards cost significantly less to process than credit cards (especially in the US). Some strategies: - Display debit as the default payment option - Offer bank transfer (open banking) as an alternative -- no card processing fees at all - For recurring payments, direct debit is far cheaper than recurring card charges ### 4. Review Your Statements Monthly Processors sometimes misclassify transactions into higher interchange categories, charge fees for services you don't use, or apply rate increases buried in contract amendments. Monthly review catches this. - Downgrades -- transactions that should qualify for lower interchange but were classified higher - PCI non-compliance fees -- £50-100/month charged if you haven't completed your PCI SAQ - Dormant fees -- charged if your account has low or no activity - Statement fees, gateway fees, batch fees -- fixed monthly costs that may be negotiable ### 5. Choose the Right Provider for Your Volume Small businesses (under £25K monthly) often do best on flat-rate pricing -- the simplicity is worth the slight overpayment. Above that threshold, interchange-plus pricing almost always saves money. High-volume merchants (£500K+ monthly) should explore payment provider options and consider working with multiple acquirers. Different providers offer better rates for different card types, regions, and transaction profiles. For platforms processing across multiple merchants, a payment layer approach lets you route transactions to the most cost-effective provider for each scenario -- without building and maintaining individual PSP integrations. ## FAQ What is the average credit card processing fee? In the UK, the average total fee is 0.5% to 1.5% for domestic consumer cards, depending on whether the transaction is debit or credit and in-person or online. In the US, average fees are higher -- typically 2.0% to 3.5% -- because interchange is not regulated. The global average across all card types and regions is roughly 2.0% to 2.5%. Who pays credit card processing fees -- the merchant or the customer? The merchant pays the processing fee. It's deducted from the transaction amount before settlement. Some merchants add a surcharge to pass the cost to the customer, but this is restricted or banned in several jurisdictions (including the UK for consumer debit and credit cards, following the Payment Services Regulations 2017). Are credit card processing fees tax deductible? Yes. Credit card processing fees are a legitimate business expense and can be deducted from taxable income. They appear as "merchant service charges" or "card processing costs" in most accounting systems. Speak to your accountant for specifics. Can I pass credit card processing fees on to my customers? It depends on your jurisdiction and card network rules. In the UK, surcharging on consumer debit and credit cards is banned. In the US, surcharging is allowed in most states but must be disclosed and cannot exceed the actual cost. Visa and Mastercard both have specific rules governing surcharging. An alternative is to offer a cash discount rather than a card surcharge. Why are American Express fees higher? Amex operates as both the card network and the card issuer (a "closed loop" model). It sets its own interchange and assessment fees without the competitive dynamics between separate issuers and networks. Historically, Amex has charged merchants higher fees in exchange for access to higher-spending cardholders. Rates have become more competitive in recent years, especially in the UK/EU, but Amex still typically costs 0.3% to 1.0% more than Visa or Mastercard. ## Related Reading - Card Processing Fees and Rates for UK Merchants -- provider-by-provider rate comparison for UK businesses - What Is a Payment Gateway? -- how gateways fit into the processing chain - How Platforms Monetise Payments -- turning payment processing into a platform revenue stream - Payment Layer Explained: Gateway vs Orchestrator vs PayFac -- understanding where processing fees fit in the infrastructure stack Processing payments across your platform? Shuttle gives platforms a single integration to 40+ payment providers -- so your merchants get PSP choice and competitive processing rates, and you maintain one integration instead of many. No lock-in. Limited PCI scope. Talk to Us | Compare Payment Providers ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Card Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Builders who accept cards for payment are better off ### 7 ways merchants can save money on payment provider fees ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### Accept Card Payments: A Complete Guide for Businesses ## Links - [payment gateway](/blog/what-is-a-payment-gateway/) - [payment provider](/payment-providers/) - [card processing fees and rates for UK merchants](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [voice payments](/guides/voice-payments/) - [payment provider options](/payment-providers/) - [payment layer approach](/guides/payment-layer-explained/) - [Card Processing Fees and Rates for UK Merchants](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [What Is a Payment Gateway?](/blog/what-is-a-payment-gateway/) - [Payment Layer Explained: Gateway vs Orchestrator vs PayFac](/guides/payment-layer-explained/) - [Talk to Us](/discovery/) - [Compare Payment Providers](/payment-providers/) - [Book a Call](/discovery/) - [BlogCard Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026)→](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogBuilders who accept cards for payment are better off→](/blog/building-success-how-accepting-card-payments-can-boost-your-business/) - [Blog7 ways merchants can save money on payment provider fees→](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogAccept Card Payments: A Complete Guide for Businesses→](/blog/the-top-5-reasons-why-your-business-needs-to-accept-card-payments/) --- URL: https://www.shuttleglobal.com/guides/cresta-payments/ --- # Cresta and Payments: PCI-Compliant Card Capture for Cresta-Powered Contact Centres | Shuttle > If your contact centre uses Cresta, for an insurance sales operation, a financial services collections team, a SaaS retention organisation, or an... # Cresta and Payments: PCI-Compliant Card Capture for Cresta-Powered Contact Centres By Shuttle Team, April 21, 2026 If your contact centre uses Cresta, for an insurance sales operation, a financial services collections team, a SaaS retention organisation, or an outsourced sales BPO, you've probably already met the payment gap. Cresta makes your agents better. It surfaces real-time coaching, suggests next-best responses, and detects intent and sentiment as the conversation unfolds. But when a customer says "I'd like to pay," Cresta's AI doesn't capture cards, and the underlying CCaaS that Cresta sits on top of usually doesn't either. Cresta works alongside Talkdesk, Genesys, Five9, Webex Contact Centre, and other major CCaaS platforms. The AI runs in real time across both human-agent calls and automated voice flows. What Cresta doesn't handle, and isn't built to handle, is the secure card-capture moment. That's a separate problem, and it's where most Cresta customers end up either reading numbers into recordings, redirecting to external IVRs, or running single-PSP add-ons that lock them to one acquirer. This guide is for merchants running Cresta on top of a CCaaS platform, and for solution providers and Cresta partners deploying Cresta for clients. It covers how Shuttle adds PCI-compliant payment capture to Cresta-powered operations, what that involves today, and why card data stays out of Cresta's transcripts. ## The Payment Gap Around Cresta Cresta is purpose-built for real-time conversation intelligence and agent coaching. It is not a payment platform, and here are the gaps for businesses taking payments on Cresta-powered calls: - Cresta sits on the AI layer, not the telephony layer. Cresta surfaces coaching cues and intent detection in real time, but it doesn't route calls or capture DTMF. Card capture has to happen elsewhere. - The CCaaS underneath usually doesn't capture cards either. Talkdesk, Genesys, Five9, and Webex CC all face the same payment gap, see the contact centre payments guide for platform-specific detail. - Single-PSP add-ons miss the multi-tenant case. Cresta is heavily used by enterprise sales teams, BPOs, and outsourced contact centres where each business unit may have its own acquirer. Single-gateway integrations don't fit. - Cresta AI cannot execute a card transaction. Cresta's value is in the coaching and analysis layer. The agent still needs a secure mechanism to capture and settle the card. Cresta can detect that a payment is about to happen; it cannot make the payment safe. - Recording and transcription pose PCI risk. Cresta processes call transcripts in real time. If card numbers are spoken aloud, they end up in transcripts and recordings, dragging Cresta-adjacent infrastructure into PCI scope. ## How Shuttle Adds Payments to Cresta Shuttle adds PCI-compliant card capture to your Cresta payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Cresta recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Cresta specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Cresta call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Cresta have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach Cresta's transcripts, coaching outputs, or the CCaaS recordings, because the card data never enters that pipeline. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Cresta-triggered payment cues Cresta's real-time intent detection can flag the moment the customer is ready to pay. The agent sees the cue in the Cresta UI, then triggers a Shuttle payment action from the agent interface you've built against Shuttle's APIs. Cresta detects intent, the agent confirms, Shuttle handles the secure capture via Twilio Pay. ### Payment Links This is the most turnkey path. For outbound sales follow-ups, agreed payment plans, or customers who can't enter card details on the phone, Shuttle generates payment links with the agreed amount and sends them via SMS or email, including mid-call. Status posts back to the agent's screen. Links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Cresta, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Cresta have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on your CCaaS as normal. Cresta continues coaching and analysing the surrounding conversation. - Payment is triggered from your agent interface when the customer is ready to pay, often cued by Cresta's intent detection. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay, the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment, never reaching Cresta. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways, then tokenises before any return to your systems. - Result returned to your interface and your systems via webhook. - No card data in Cresta. Cresta transcripts, coaching outputs, and analytics never contain card numbers. ## Multi-PSP Support Shuttle is gateway-agnostic. We connect to 40+ PSPs, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Authorize.Net, GlobalPayments, FreedomPay, FIS, Elavon, Fiserv, and most regional acquirers. You can route transactions based on currency, region, business unit, or tenant, useful for enterprise Cresta deployments running BPO models or multi-brand operations. Switching processors later is straightforward, gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, cardholder data stays out of the Cresta pipeline entirely: - Card digits are captured directly into Shuttle's certified environment, then tokenised before any return to your systems. They are never recorded, never transcribed, never reach Cresta's transcript stream. - Cresta transcripts, coaching outputs, and analytics never contain card numbers. Your PCI scope, and Cresta's, stays narrow on the lighter SAQ-A path. - Audit trails, settlement reports, and reconciliation are available via Shuttle's reporting layer. For Cresta customers in regulated verticals, financial services, insurance, healthcare, sales BPOs handling regulated products, Shuttle is built to keep certified scope tight without disrupting the AI coaching layer. Full compliance documentation is in the security docs. ## For Solution Providers and Cresta Implementation Partners If you're a Cresta partner or SI deploying Cresta on top of Talkdesk, Genesys, Five9, Webex CC, or other CCaaS for clients, Shuttle is the payment layer you can add via a Twilio-based setup. We support white-label deployment, multi-PSP routing across your client portfolio (each client keeps their preferred acquirer), and partner-friendly commercials. Shuttle is a Pay Connector provider on the Twilio Marketplace. A native Cresta integration can be built as a paid project. For partnership conversations, book a discovery call. ## Use Cases ### Insurance Sales and Renewal Insurance teams using Cresta for sales coaching can settle premium payments and renewals during the call itself. Cresta surfaces the moment to ask for the card, Shuttle handles the secure capture. ### Sales BPOs and Outsourced Sales Teams Sales BPOs deploying Cresta on top of Talkdesk or Five9 for client work can take payments inside the call, with multi-PSP routing per client account. ### Collections and Recovery Collections teams using Cresta for tone-aware coaching during recovery calls can take agreed payment plans during the call, with payment links as fallback. ### SaaS Retention and Upsell SaaS retention teams using Cresta for in-call coaching can take credit card details for plan upgrades or payment-method updates without breaking the call flow. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Cresta plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Cresta specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Cresta call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Cresta have already done it. - A native Cresta integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Cresta integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Cresta or its underlying CCaaS. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Cresta have already done. We can build a native Cresta integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Does Shuttle affect Cresta's transcripts or coaching? No. Cresta continues transcribing and coaching throughout the conversation. Because the card is captured in the separate Twilio Pay call, transcripts and coaching outputs never contain cardholder data, while the conversational context around the payment moment is preserved. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### What does Shuttle cost? $0.20 per successful transaction for voice, with no per-seat fees, so cost scales with payment volume not headcount. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the platform-by-platform merchant + SI guide - Talkdesk Payments, common CCaaS underneath Cresta - Genesys Payments, common CCaaS underneath Cresta - Five9 Payments, common CCaaS underneath Cresta - AI Voice Agent PCI Payments, for AI-led contact centres - Twilio Pay Connectors, Shuttle's multi-gateway Pay Connector - Voice Payments, comprehensive voice payment capture guide ## Get Started Shuttle adds enterprise-grade, PCI-compliant payment capture to a Cresta-powered operation via Twilio, without changes to Cresta's coaching layer, your CCaaS configuration, or your agent training, and across multiple PSPs. If you take payments in a contact centre, see how Shuttle works for merchants, or book a discovery call to walk through your specific Cresta + CCaaS deployment. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [contact centre payments guide](/guides/contact-centre-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [a Pay Connector provider on the Twilio Marketplace](/guides/twilio-pay-connectors/) - [book a discovery call](/contact/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Talkdesk Payments](/guides/talkdesk-payments/) - [Genesys Payments](/guides/genesys-payments/) - [Five9 Payments](/guides/five9-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [Shuttle works for merchants](/merchants/payment-services/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/cybersource-twilio-integration/ --- # How to Connect Cybersource to Twilio for Voice & IVR Payments | Shuttle > Cybersource doesn't natively connect to Twilio for voice payments. If you want to process Cybersource transactions during a phone call (via IVR,... # How to Connect Cybersource to Twilio for Voice & IVR Payments By Shuttle Team, June 23, 2026 Cybersource doesn't natively connect to Twilio for voice payments. If you want to process Cybersource transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Cybersource (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Cybersource + Twilio Don't Connect Directly Cybersource is Visa's enterprise payment gateway. It's built for large organisations that process at scale: airlines, telcos, utilities, insurers, and global retailers. Its platform handles payment processing, fraud management, and tokenisation across acquirer connections worldwide, which is why so many enterprises standardise on it. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Cybersource isn't one of Twilio's built-in connectors. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Cybersource's API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Cybersource. The connector creates a Cybersource payment request, processes the transaction through your Cybersource merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the Cybersource transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Cybersource account with REST API credentials (merchant ID, API key ID, and shared secret key, created in the Cybersource Business Center) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Cybersource Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Cybersource - Merchant ID: Your Cybersource merchant ID - Key ID: The API key ID generated in the Business Center - Shared secret: The shared secret key paired with that key ID - Currency: Set your default (GBP, USD, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Cybersource account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in the Cybersource Business Center if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Cybersource's sandbox is completely separate from production and needs its own credentials, so create a test key pair in the sandbox Business Center first. Then run the flow end-to-end with Cybersource's sandbox test cards: (Visa), (Mastercard). Use any future expiry date. ## What You Can Do With Cybersource + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Cybersource processes, done. This is the typical pattern for bill payments in utility, telco, and insurance contact centres. ### Authorise Now, Capture Later Place a hold on the card during the call and capture the payment later through Cybersource. Useful for bookings, deposits, and variable-amount transactions, a common pattern for airlines and travel operators taking reservations over the phone. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Cybersource's Token Management Service (TMS) and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems, which matters for insurers and utilities collecting recurring or instalment payments from the same customer. ### Keep Your Acquirer Relationships Cybersource is a gateway with acquirer connections around the world, and many enterprises route through negotiated acquiring agreements behind it. Voice payments taken through Shuttle flow into the same Cybersource merchant account as your web and in-app transactions, so reporting, reconciliation, and fraud screening stay in one place. ## Multi-PSP: Beyond Cybersource One of the key advantages of using Shuttle rather than a Cybersource-only connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: put the merchants in one region on Cybersource and another region on a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Cybersource account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Cybersource + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Cybersource (PCI DSS Level 1) Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to Cybersource. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Cybersource to Twilio without Shuttle? Cybersource isn't one of Twilio's built-in connectors. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Does this work with Cybersource's Token Management Service? Yes. Shuttle can tokenise cards captured over the phone via Cybersource TMS, so a card taken during a call can be reused for later web, mobile, or recurring payments. What about Cybersource's test environment? Fully supported. Cybersource's sandbox is separate from production with its own credentials. Create a sandbox key pair, add it to a test payment profile in Shuttle, and run the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Cybersource's standard fees apply on top (your negotiated gateway and acquiring rates). No Shuttle setup fees or monthly minimums. Can I switch from Cybersource to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Enterprise PSP Mandates: When Your Customer Chooses the Gateway: handling gateway requirements from enterprise buyers - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Twilio Pay: Connect Any Payment Gateway to Twilio covering all supported gateways, pricing, and setup *Connect Cybersource to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for Cybersource: Send Branded Checkout Links Without Writing Code ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [Cybersource](/payment-providers/cybersource/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Enterprise PSP Mandates: When Your Customer Chooses the Gateway](/guides/enterprise-psp-mandates/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for Cybersource: Send Branded Checkout Links Without Writing Code→](/blog/payment-links-for-cybersource/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/decagon-payments/ --- # How to Take Payments on Decagon AI Agents: PCI-Compliant Payments | Shuttle > Decagon is an enterprise omnichannel AI customer-service platform. Its agents handle voice, chat and email for contact centres and CX operations across... # How to Take Payments on Decagon AI Agents: PCI-Compliant Payments By Shuttle Team, May 29, 2026 Decagon is an enterprise omnichannel AI customer-service platform. Its agents handle voice, chat and email for contact centres and CX operations across retail, travel, healthcare and fintech, resolving customer issues end to end rather than just routing tickets. When those conversations involve money (a bill to settle, a deposit to take, an order to complete) the question becomes how payments actually work inside a Decagon deployment. Decagon's marketing references processing payments by securely collecting card details through PCI-compliant voice interactions, and notes that it connects to payment processors and accounting systems. However, Decagon does not publish a PCI DSS certification level or the underlying payment architecture, so whether it captures and processes card data itself or integrates with an external layer is not publicly documented. This guide is for teams evaluating how to add verified, certified, multi-PSP payment capture to their Decagon agents. It explains why taking cards in an AI voice call requires an isolated, certified payment layer, and how Shuttle provides exactly that: a PCI DSS Level 1 certified Service Provider with secure in-call capture, SMS payment links and routing to 30+ gateways. There is no native Decagon integration: instead, your application invokes Shuttle's Twilio-based secure capture, which does require you to be a Twilio customer today. ## The Payment Challenge for Decagon Taking a card payment during an AI-driven conversation introduces a hard constraint: raw card data cannot flow through the AI pipeline. The moment a primary account number, CVV or expiry passes through your speech-to-text, transcription, logging, model context or analytics, every one of those systems is pulled into PCI DSS scope. For an enterprise running voice, chat and email at volume, that scope is unmanageable. The answer is a certified, isolated payment layer that captures card data outside the AI path entirely. The customer enters their card, that data is handled only by a certified processor, and the AI agent never sees, hears or stores it. This keeps the conversation flowing while keeping cardholder data out of your environment. See PCI scope for what this means in practice. Building that layer yourself is expensive. Achieving and maintaining PCI DSS Level 1 typically costs $500k+ upfront and $200k+ per year in audits, infrastructure and dedicated security staff. Shuttle removes that burden by providing the certified layer as a service. ## How Shuttle Works with Decagon Today There is no native Decagon integration. The handoff is API-driven and built on Shuttle's Twilio-based capture: you must be a Twilio customer, and your application code triggers the handoff at the point of payment. Shuttle handles the payment moment in isolation: - The Decagon agent runs the conversation as normal, resolving the customer's request across voice, chat or email. - When payment is due, your application triggers Shuttle via a simple API call with the amount and reference. - At the point of payment, the card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay, with Shuttle as the certified connector) on voice, or via a secure link on chat and email, so card data never enters the Decagon pipeline. - Shuttle processes the payment and routes it to your chosen gateway from 30+ supported providers. - The result is returned to your application, which confirms the outcome to the customer. One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Decagon agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native Decagon integration is possible only as a paid project. ## How It Works: Step by Step - The Decagon agent identifies payment intent during the conversation. - The amount and reference are confirmed with the customer. - A secure Shuttle payment session is created via API by your application. - On a voice call, a secure PCI DSS Level 1 capture takes over the card collection at the point of payment, isolated from the agent and transcription. - The customer enters their card number using the phone keypad. - The keypad digits are captured by Shuttle inside its certified environment, never reaching Decagon. - Shuttle processes the transaction through the routed gateway. - A webhook returns the success or failure result to your application. - The agent confirms the outcome. Returning the caller to the same Decagon agent and call after payment works today: your Twilio flow routes the call back and passes a conversation ID, so the agent resumes with context. Shuttle provides the secure capture and the result webhook; the return leg is wiring your team owns. ## Multi-PSP Support Shuttle routes to 30+ payment gateways, so you keep your existing processor relationships and pricing: - Checkout.com You can route by client, region, currency or merchant account, which matters for enterprises and agencies running payments across multiple entities. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest assurance level. Card data is captured, processed and stored only within Shuttle's certified environment. Your Decagon agents, transcripts, logs and analytics never touch it. This changes the compliance posture. Because cardholder data is isolated inside Shuttle, your environment can typically qualify for the far simpler SAQ-A self-assessment rather than the extensive SAQ-D you would face if card data passed through your own systems. Fewer controls, fewer audits, less risk. ## Beyond Voice: Payment Links Payment links are the turnkey path. Shuttle issues hosted payment links over SMS, email or chat, including mid-call. Your application can send a link mid-conversation, let the customer pay on a secure hosted page, and receive confirmation back. This suits higher-value transactions, follow-ups, or customers who prefer to pay on their own device, all without adding card data to your scope. Links work even with gateways that do not support voice capture. ## Use Cases ### Bill-Pay and Collections Decagon agents handling outstanding balances can take payment in the moment, or set up a payment plan and collect the first instalment, with cards captured securely on every call. ### Customer Support Payments When a support conversation turns into a purchase, an upgrade or a fee, the agent collects payment without handing the customer off to another channel. ### Bookings and Deposits Travel and hospitality agents can confirm a reservation and take a deposit in the same conversation, then send a payment link for the balance later. ### Order Taking Retail and ordering agents can complete a sale end to end, capturing the card by DTMF or sending a link for the customer to pay. ## FAQ Does Shuttle have a native Decagon integration? No. There is no native Decagon integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native Decagon integration is possible only as a paid project. Does this require Twilio? Yes, today. The secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Does Decagon process payments natively? Decagon references collecting card details through PCI-compliant voice interactions and connecting to payment processors, but it does not publish a PCI DSS certification level or its payment architecture. Whether it processes cards itself or integrates with an external layer is not publicly documented. Shuttle adds a verified, PCI DSS Level 1 certified capture layer with clear architecture and multi-PSP routing. How do I take PCI-compliant payments with Decagon? Your application triggers Shuttle at the payment moment. Shuttle captures the card in a secure PCI DSS Level 1 capture (today, via Twilio Pay) or via a secure link, processes it through your gateway, and returns the result to your application. Card data never enters the Decagon pipeline, keeping it out of your PCI scope. Which payment gateways does Shuttle support? Shuttle routes to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square and Mollie. You keep your existing processor and pricing. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture. Should we build PCI Level 1 ourselves instead? You can, but it typically costs $500k+ upfront and $200k+ per year to maintain. Shuttle provides the certified layer as a service at $0.20 per successful transaction for voice, with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). Does this work for outbound calls? Yes. Outbound collections and sales agents can capture payment or set up a payment plan in the same conversation, with the same secure, certified capture. ## Related Reading - AI Voice Agent PCI Payments: the technical pattern for capturing cards in AI voice calls. - Voice Payments: how secure payment capture works over voice channels. - The Payment Layer for AI Agents: why AI agents need a dedicated, certified payment layer. - Sierra Payments: adding certified payment capture to Sierra AI agents. - Contact Centre Payments: the full picture on PCI-compliant payments across contact centre channels. ## Add Payments to Your Decagon Agents Add verified, PCI DSS Level 1 certified payment capture to your Decagon deployment with Shuttle's Twilio-based secure capture, SMS payment links and routing to 30+ gateways, at $0.20 per successful transaction for voice (links currently free) with no setup or monthly fees. Shuttle provides a Pay Connector on the Twilio Marketplace. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS](/glossary/pci-dss/) - [30+ payment gateways](/payment-providers/) - [payment links](/platforms/voice-checkout/) - [DTMF](/guides/dtmf-payments/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Sierra Payments](/guides/sierra-payments/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/dialpad-payments/ --- # How to Take Payments on Dialpad: PCI-Compliant Voice Payments | Shuttle > Dialpad has built one of the most AI-forward contact centre platforms on the market. # How to Take Payments on Dialpad: PCI-Compliant Voice Payments By Shuttle Team, April 1, 2026 Dialpad has built one of the most AI-forward contact centre platforms on the market. Dialpad Ai powers real-time transcription, sentiment analysis, agent coaching, and automated summaries across every call. But when a customer on a Dialpad call needs to pay, the AI can't help. Dialpad does not have native PCI-compliant payment capture. There is no built-in mechanism to securely collect card details during a voice call while maintaining PCI compliance. Third-party marketplace DTMF integrations exist but are typically single-gateway and don't cover a full payment infrastructure. This guide covers how a Dialpad-based operation can add comprehensive, PCI-compliant payment capture using Shuttle, enabling both human agents and AI agents to collect payments during calls without handling card data. ## The Payment Gap in Dialpad Dialpad Ai Contact Center is a strong platform for conversation intelligence. But payment capture requires different infrastructure: - No native payment processing. Dialpad does not have a built-in payment engine. There is no way to trigger a card transaction from within a Dialpad call flow or Ai agent interaction without external integration. - No secure card capture built in. Dialpad offers recording pause via API or Chrome extension to avoid capturing card data, but this is a manual workaround. Pausing recordings doesn't prevent the agent from hearing card numbers. - Limited marketplace options. Available DTMF marketplace integrations are typically single-gateway and designed for basic card capture, not multi-PSP routing or per-transaction pricing. - No AI-to-payment handoff. Dialpad Ai can detect payment intent and transcribe conversations, but it cannot initiate a secure payment flow. The AI generates coaching suggestions and summaries; it cannot execute a transaction. - No multi-PSP routing. Enterprise customers and BPOs need to route payments to different gateways for different merchants or regions. Native and marketplace options on Dialpad don't support this. ## How Shuttle Adds Payments to Dialpad Shuttle adds PCI-compliant card capture to your Dialpad calls, for both live agents and Dialpad Ai. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Dialpad recordings, your Ai transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Dialpad specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Dialpad call flow (live agent or Dialpad Ai) over Twilio, and add your own agent screen if your workflow needs one. Customers running Dialpad have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Dialpad recordings, your Ai transcription, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Triggering from Dialpad Ai or a live agent You can trigger the secure capture via Shuttle's APIs from a live agent's interface or from a Dialpad Ai flow when payment intent is detected. The payment result is returned so the conversation can continue, confirming the payment and providing a reference number. The connecting logic between Dialpad and Shuttle is the small integration you build, because Dialpad does not have a pre-built Shuttle app today. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Dialpad, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent or Ai flow if your workflow needs one. Customers running Dialpad have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on Dialpad as normal, with a live agent or Dialpad Ai. - Payment is triggered from your agent interface, or via API from a Dialpad Ai flow. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay; the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. - Result returned to your interface or AI flow via webhook, so an agent can confirm the outcome or Dialpad Ai can continue the conversation. - No card data in Dialpad. The card digits never touch your Dialpad recordings, your transcriptions, or your agent workstations. ## Multi-PSP Support Shuttle supports 30+ payment gateways with configurable routing: - By merchant: each client routes to its own gateway - By region: UK payments to one PSP, US to another - By switching: automatic backup if the primary gateway is unavailable - By card type: route specific card brands to preferred processors For BPOs running multiple clients on Dialpad, multi-PSP routing is essential, and it's not available through native or single-gateway marketplace options. Switching processors later is straightforward; gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, card data never enters your Dialpad environment. Recordings, transcriptions, Ai analytics, and agent workstations stay out of PCI scope, keeping you on the lighter SAQ-A path. Full compliance documentation is in the security docs. This is critical for Dialpad deployments. Dialpad Ai transcribes every call in real time. Because the card is captured in the separate Twilio Pay call, card data never reaches the audio stream that Dialpad's AI pipeline processes. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Insurance Insurance brokers and contact centres on Dialpad handle premium collections and renewal payments daily. Shuttle enables secure payment capture during the renewal conversation, with no transfer and no callback. ### Professional Services Accountancy firms, legal practices, and consultancies using Dialpad can collect invoice payments during client calls. The client enters card details on a secure Twilio Pay call, and payment confirms before the call ends. ### Collections Collections teams need to capture payment when the debtor agrees to pay. Any delay reduces conversion, though a mid-call payment link keeps the customer on the line. Shuttle captures payment immediately, in-call. ### Utilities High-volume bill payment calls handled by Dialpad Ai can hand off the payment leg to Shuttle's secure Twilio Pay capture, then confirm the result. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Dialpad plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Dialpad specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Dialpad call flow (live agent or Dialpad Ai) over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Dialpad have already done it. - A native Dialpad integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire Dialpad conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Dialpad integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Dialpad. What you build is small: pass the payment amount to Shuttle via its API (the minimum data we need), connect the secure capture into your Dialpad call flow over Twilio, and add your own agent or Ai-side screen if your workflow needs one. Customers running Dialpad have already done this. We can build a native Dialpad integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Does Shuttle work with Dialpad Ai features? Yes. Because the card is captured in a separate, secure Twilio Pay call, no card data reaches Dialpad's audio stream, so Ai transcription, sentiment analysis, and coaching continue to work normally; they just never see card data. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### What does Shuttle cost? $0.20 per successful transaction for voice, no setup fees and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres: the complete guide to contact centre payment processing - Talkdesk Payments: PCI-compliant payment capture for Talkdesk and Autopilot - RingCentral Payments: secure voice payments for RingCX and RingEX - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents - Five9 Payments: PCI-compliant payment processing for Five9 - Voice Payments: comprehensive guide to voice payment capture ## Get Started Shuttle adds PCI-compliant payment capture to a Dialpad operation via Twilio, for both human agents and Ai, without expanding your PCI scope or locking you into a single gateway. We'll walk you through what's live today and the path for your setup. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Talkdesk Payments](/guides/talkdesk-payments/) - [RingCentral Payments](/guides/ringcentral-payments/) - [Retell AI Payments](/guides/retell-ai-payments/) - [Five9 Payments](/guides/five9-payments/) - [Voice Payments](/guides/voice-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/dso-benchmarks-uk/ --- # DSO Benchmarks by Industry UK (2026) | Shuttle > Why DSO Benchmarks Matter If you don't know what "good" looks like for your industry, you can't tell whether your debtor days are a problem or just... # DSO Benchmarks by Industry UK (2026) By Shuttle Team, March 4, 2026 ## Why DSO Benchmarks Matter If you don't know what "good" looks like for your industry, you can't tell whether your debtor days are a problem or just normal. A 45-day DSO might be excellent in construction (where 60-90 days is common) but concerning in retail (where 15-25 days is the norm). Benchmarking tells you where you stand relative to your peers -- and how much cash you're leaving on the table. This guide compiles UK-specific DSO data from Companies House filings, BACS payment surveys, Experian's Late Payment Index, and the Chartered Institute of Credit Management (CICM) to give you benchmarks you can actually use. ## UK DSO Benchmarks by Industry (2026) Average DSO Excellent DSO Typical Terms Construction 65-80 days 50-60 days Under 45 days 30-60 days Professional Services 50-65 days 35-45 days Under 30 days 14-30 days Recruitment & Staffing 45-60 days 30-40 days Under 25 days IT Services & Software 45-55 days Marketing & Creative Manufacturing 55-70 days 40-50 days Under 35 days Wholesale & Distribution 40-55 days Healthcare & Social Care 60-75 days Under 40 days Transport & Logistics Property & Facilities Management 35-50 days Retail (B2B supply) 25-35 days Under 20 days Hospitality (B2B supply) 30-45 days Sources: BACS Late Payment Survey 2025, Experian Late Payment Index Q4 2025, CICM Credit Management Survey 2025, Atradius Payment Practices Barometer UK 2025, Companies House average debtor days from FTSE 350 / AIM filings. ### What the Data Shows - Construction is the worst-performing sector -- 65-80 day average DSO, driven by long supply chains, subcontractor nesting, and the widespread abuse of payment terms by main contractors. The Construction Act and Prompt Payment Code have improved things slightly, but the sector remains an outlier. - Professional services and marketing/creative are consistently above 50 days -- despite typically setting 30-day terms. The gap between terms and actual payment is 20-35 days in these sectors. - Recruitment and IT services are improving -- both sectors are adopting online payment tools faster than others, and DSO is trending downward. - Public sector clients push DSO up across every sector -- NHS trusts, local authorities, and government departments often take 60-90 days regardless of agreed terms. If a large portion of your revenue comes from public sector clients, your DSO will be above industry average. ## How to Calculate Your DSO ### Basic DSO Formula DSO = (Trade Receivables / Annual Revenue) x 365 Example: £150,000 in receivables, £900,000 annual revenue. (150,000 / 900,000) x 365 = 61 days ### Monthly DSO (More Accurate) The annual formula can be misleading if your revenue is seasonal. Monthly DSO gives a more current picture: Monthly DSO = (Trade Receivables / Monthly Revenue) x 30 Example: £150,000 in receivables, £80,000 monthly revenue. (150,000 / 80,000) x 30 = 56 days ### Weighted Average DSO For businesses with varying invoice sizes, weight the DSO by invoice value: Weighted DSO = Sum of (Invoice Value x Days to Pay) / Total Invoice Value This prevents a few large invoices from skewing your average. ## What Your DSO Is Costing You Every extra day of DSO has a real financial cost. Here's how to quantify it: ### Working Capital Impact Cash tied up = (Annual Revenue / 365) x Excess DSO Days If your annual revenue is £1 million and your DSO is 55 days instead of a target of 30: (1,000,000 / 365) x 25 = £68,493 in working capital locked up in receivables. ### Cost of Financing If you're using an overdraft or invoice finance to bridge the gap, multiply the locked-up capital by your borrowing rate: £68,493 x 8% = £5,479 per year in financing costs -- just because invoices are paid 25 days late. ### Opportunity Cost Money tied up in receivables can't be used for growth, hiring, inventory, or marketing. For a small business, £68,000 freed up could fund a new hire, a marketing campaign, or several months of runway. ## UK Late Payment Statistics These numbers put the problem in context: - £23.4 billion in late payments owed to UK SMEs at any time (FSB) - 50,000 businesses close each year in the UK due to late payments (FSB) - 87% of UK businesses have been paid late in the past year (BACS) - 62% of invoices to UK SMEs are paid after the due date (Xero Small Business Insights) - £9,000 -- the average amount owed to a UK small business in late payments at any time - 8.4 hours per week -- average time UK business owners spend chasing payments (Tide survey) - The UK government's Prompt Payment Code targets 30-day payment -- but the average across signatories is still 36 days ## How to Improve Your DSO If your DSO is above the "Good" benchmark for your industry, these are the highest-impact actions in order of effort: ### Quick Wins (This Week) - Add [payment links](/blog/pay-now-button-invoices/) to every invoice -- 30-50% DSO reduction is typical. Works with Xero, QuickBooks, Sage, or plain email. - Offer [multiple payment methods](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) -- cards, bank transfer, Apple Pay, Open Banking. More choice = faster payment. - Invoice on the day you deliver -- every day between delivery and invoicing is a day added to your DSO. ### Short-Term (This Month) - Set up automated [payment reminders](/blog/payment-reminder-email-templates/) -- pre-due, on-due, Day 7, Day 14, Day 30. - Chase across [multiple channels](/guides/multi-channel-payment-collection/) -- email first, then SMS, then WhatsApp. Same payment link, different channel. - Review your payment terms -- if you're on 30-day terms and your DSO is 55, try 14-day terms for new customers. ### Medium-Term (This Quarter) - Run credit checks on new customers -- prevent bad debts from entering your book. - Formalise your [escalation process](/blog/overdue-invoice-email-templates-uk/) -- define what happens at 7, 14, 30, 45, 60+ days overdue. - Consider early payment discounts -- 2% off for payment within 7 days (2/7 net 30). - Segment your debtors -- identify chronic late payers and apply stricter terms or upfront payment requirements. For the full breakdown, see our guide on how to reduce debtor days: 10 strategies that work. ## DSO by Company Size DSO behaviour varies significantly by company size: Company Size Sole traders / micro (<£500K) Often don't have formal collection processes Small (£500K-£5M) Typically 1 person doing credit control + other roles Medium (£5M-£50M) Dedicated credit controller, but often overwhelmed Large (£50M+) Larger, slower-paying customers; longer approval chains Enterprise (£500M+) Dedicated AR teams, formal processes, but supplier power imbalance Counterintuitively, larger companies often have higher DSO -- not because they're worse at collection, but because their customers are larger organisations with longer approval processes and payment runs. ## DSO Trends: What's Changing ### Improving - Open Banking adoption is accelerating in the UK. Bank-to-bank payments settle same-day, cutting 2-3 days off DSO compared to card payments. - Payment links are becoming standard practice. The percentage of B2B invoices with an online payment option has doubled since 2023. - Automated reminders via SMS and WhatsApp are normalising. Customers expect (and respond to) multi-channel collection. ### Getting Worse - Public sector payment times are not improving despite government commitments. - Invoice complexity is increasing -- more line items, more VAT codes, more approval chains. Complex invoices take longer to process. - Economic uncertainty leads to customers strategically delaying payment to manage their own cash flow. ## Common Questions ### Is DSO the same as debtor days? Yes. DSO (Days Sales Outstanding) and debtor days are the same metric -- how long on average it takes customers to pay. DSO is the more common term in finance; debtor days is more common in UK accounting. ### How often should I calculate DSO? Monthly. Annual DSO smooths over seasonal variations and won't show you trends quickly enough. Monthly DSO lets you spot problems within 30-60 days. ### What if my DSO is below the industry average? That's excellent -- you're collecting faster than your peers. Focus on maintaining it rather than pushing it lower. Below a certain point, aggressively chasing payment can damage customer relationships. ### Does DSO include disputed invoices? Yes -- disputed invoices are still receivables. This is why clear, accurate invoicing matters. Every disputed invoice inflates your DSO until it's resolved. If disputes are a significant portion of your receivables, fix the invoicing process first. ### How does DSO relate to cash flow? Directly. Higher DSO = more cash locked in receivables = less cash available for operations. Reducing DSO is the fastest way to improve cash flow without increasing revenue or borrowing. See our guide on how payment links improve cash flow. ## Get Started The fastest route from "above average DSO" to "below average" is adding a payment link to every invoice. It's the one change that works across every industry, every company size, and every invoicing system. Shuttle Payment Links work with 40+ gateways, support white-label branding, and deliver via email, SMS, WhatsApp, and QR code. See how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Links - [Xero](/blog/xero-payment-links/) - [QuickBooks](/blog/quickbooks-payment-collection/) - [Sage](/blog/sage-invoice-payments/) - [how to reduce debtor days: 10 strategies that work](/guides/reduce-debtor-days/) - [how payment links improve cash flow](/blog/how-to-use-payment-links-to-improve-cash-flow/) - [40+ gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [Book a Call](/discovery/) --- URL: https://www.shuttleglobal.com/guides/dtmf-payments/ --- # DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking | Shuttle > DTMF payments are transactions where the customer enters their card details on a phone keypad during a call -- and the digits are captured securely so they... # DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking By Shuttle Team, April 26, 2026 DTMF payments are transactions where the customer enters their card details on a phone keypad during a call -- and the digits are captured securely so they never reach the agent, the call recording, or the business systems. When you enter a card number on a phone, each key press generates a tone. That's DTMF (Dual-Tone Multi-Frequency). For decades those tones travelled openly through the call, exposing card data to anyone listening, recording, or transcribing. The job of a secure DTMF payment flow is to make sure the customer's real digits are captured inside a certified payment environment and never reach the business, while the audio the agent and recordings hear carries no decodable card data. The category uses three terms, DTMF clamping, DTMF masking, and DTMF suppression, that get used interchangeably in marketing copy but are technically distinct, with different PCI implications. This guide covers what each one actually does, when you'd pick one over another, and what to look for in a DTMF payment processing solution. ## What Is DTMF? DTMF stands for Dual-Tone Multi-Frequency. Every key on a telephone keypad emits two simultaneous frequencies -- one from a row, one from a column. The combination uniquely identifies the digit. These tones were designed in the 1960s for telephone signalling and have been the universal language of phone systems ever since. DTMF is what lets you "press 1 for sales" on an IVR. It's also how a customer types in their card number when an automated system asks for it. The tones are audible by design -- anyone on the call hears them, and anyone with a basic decoder can read the digits back out of a call recording. For how a complete automated payment flow is built on those tones, see IVR Payments. That's the problem DTMF payment systems exist to solve. ## The DTMF Payment Problem If you ask a customer to read their card number aloud to an agent, three things happen. The agent hears it. The call recording captures it. And the business is now in scope for some of the most onerous PCI DSS requirements -- your contact centre is processing card data, your call recordings store card data, and your agents have access to card data. DTMF was meant to solve part of this. The customer types instead of speaking, the agent doesn't hear the digits -- but the tones still travel through the same audio path. They're still in the call recording. They can still be decoded by anyone with the audio. PCI DSS treats DTMF tones the same as spoken card numbers: cardholder data, in scope, full requirement set applies. The fix is to intercept the DTMF before it reaches the agent or the recording, and that's where the three approaches diverge. ## DTMF Clamping vs Masking vs Suppression The terminology has drifted in the market, but here's what each technically means. ### DTMF Clamping Clamping is the most aggressive intervention. The system replaces the customer's actual DTMF tones with flat, neutral tones (typically a single low-frequency hum) before they reach the agent's audio path or the recording. The customer's real digits are forwarded to the payment gateway via a separate, secured channel; everyone else hears a string of identical, undecodeable beeps. Best for: PCI DSS Level 1 contact centres where audit defensibility is critical. Clamping leaves zero residue of the real tones in the recording, which is the cleanest scope-reduction outcome. Trade-off: Requires session-level audio control. Usually deployed at the SIP carrier or session border controller (SBC) -- not something you bolt on to a typical CCaaS platform without help. ### DTMF Masking Masking replaces the real tones with substitute tones -- often a fixed digit like "0" or a different tone entirely -- but unlike clamping, the agent and the recording typically still hear something in the same temporal pattern. The substitution preserves call cadence (so the agent can tell the customer is typing) without exposing the real digits. Best for: Agent-assisted flows where the agent needs to confirm the customer is making progress, but shouldn't see or hear the actual numbers. Trade-off: Some implementations leave timing-based side channels. A determined attacker analysing the recording's tone-spacing could in theory infer card length or segment boundaries. Strong masking implementations randomise spacing to defeat this. ### DTMF Suppression Suppression removes DTMF tones from the agent and recording paths entirely -- no substitute, just silence. The audio gap is the only signal that the customer typed something. Some providers use the term interchangeably with clamping; others distinguish suppression (silent drop) from clamping (neutral substitute). Best for: Fully automated IVR or AI voice flows where there's no agent to keep informed and the recording doesn't need conversational continuity. Trade-off: Less natural in agent-assisted calls. Long silences during card entry can confuse agents and customers; some agents may drop the call thinking the line is dead. ### Quick comparison What the recording hears PCI scope outcome Flat substitute tones Live-agent contact centres needing maximum audit defence Card data fully out of scope Substituted digits / patterned tones Agent-assisted flows with conversational continuity Card data out of scope (caveat: implementation quality) Suppression Pure IVR / AI voice / automated flows Card data out of scope In practice, most production systems blend approaches -- clamping for the digit capture, suppression for downstream metadata, masking applied at the recording layer as belt-and-braces. ## PCI Compliance for DTMF Payments PCI DSS does not name DTMF specifically, but treats it as cardholder data the moment it enters your environment. The decisive question for compliance is whether the DTMF tones ever traverse a system you operate, store, or could decode. If a customer enters their card via DTMF and the tones pass through your CCaaS platform, your call recording system, or your agents' headsets -- even briefly -- the entire path is in PCI scope. That means PCI DSS controls apply to your network, your storage, your access management, your audit logs, and the call recordings themselves. If the card is captured *before* it enters your environment, by a PCI Level 1 service provider handling the secure capture at the point of payment, and the decodable digits never reach your systems, you can claim significant scope reduction. Your contact centre is no longer processing card data. The card is handled in the service provider's certified environment and forwarded to the gateway over a protected channel. The common SAQ for merchants using a fully descoped DTMF service is SAQ A -- the lightest of the self-assessment questionnaires, applicable when all card data handling is outsourced. Some implementations qualify for SAQ A-EP if there are integration touchpoints. The full SAQ D (the heaviest) is what you're trying to avoid. For documentation: ask any DTMF payment vendor for their Attestation of Compliance (AOC) as a Level 1 Service Provider. If they can't produce one, they cannot give you scope reduction -- and you remain in full PCI scope regardless of what their marketing claims. ## How DTMF Payment Processing Actually Works In a typical PCI-compliant DTMF payment flow: - The customer is on a call, with a live agent, an IVR, or an AI voice agent. - The payment step is triggered, handing the card capture to the payment provider's secure, PCI-certified session at the point of payment. - The customer enters their card number on their keypad. - The provider captures the card inside its certified environment, so the digits are captured securely and the call's main audio path carries no decodable card data. The provider forwards the card to the payment gateway over a protected channel. - The gateway processes the transaction, runs the authorisation, and returns a token plus result. - The agent or system sees only the result, approved or declined, with a tokenised reference. No card number ever appears on screen, in logs, or in the recording. - The call continues, with the result confirmed back to the customer. The secure capture adds a short window to the call versus reading a card number aloud, without the business ever touching the card data. ## What to Look For in a DTMF Payment Provider The market has consolidated around half a dozen serious providers and several dozen white-label resellers. Picking among them comes down to five questions. 1. PCI DSS Level 1 Service Provider designation? Non-negotiable. Anything less means scope-reduction claims won't hold up at audit. Ask for the AOC, not just a marketing claim. 2. How and where is the card captured? The strongest model captures the card inside the provider's own PCI-certified environment at the point of payment, so the decodable digits never enter your stack. Be wary of approaches that lean on stripping or post-processing card data inside your own systems, which tends to reintroduce scope. Ask the provider to be specific about what their environment captures and what, if anything, touches yours. 3. Which carrier or platform does it actually run on today? Secure voice capture usually depends on a specific telephony provider rather than plugging natively into any CCaaS platform. Shuttle's voice capture, for example, runs on Twilio Pay today, so using it for voice means being a Twilio customer; shuttle works with Twilio today, and any carrier coming soon. For other platforms (Genesys, Five9, Talkdesk, Avaya, Cisco, NICE CXone, Amazon Connect, Twilio Flex), integrating a given platform may require technical work and, for a packaged build, a paid project. Don't assume a native, finished integration exists for your platform; confirm it. 4. Which payment gateways does it route to? Some DTMF providers are tied to a single gateway (their own or a parent company's). Others are gateway-agnostic. If you have an existing PSP relationship -- or want PSP optionality -- gateway-agnostic is materially safer. 5. Does it support AI voice agents? A DTMF system designed for live-agent calls may not fit cleanly into an AI voice agent flow where there's no human in the loop. Newer providers explicitly support automated voice channels; legacy ones often don't. ## DTMF and the Move to AI Voice Agents The DTMF problem changes shape when the agent isn't human. AI voice agents -- built on platforms like PolyAI, Retell AI, Cresta, or custom LLM stacks -- don't need DTMF for the same reasons live agents do. There's no agent listening; the issue is the recording, the transcript, and the AI's own ability to hear and process card data it shouldn't have. Two patterns dominate: Pattern A -- DTMF in the AI flow. The AI agent invokes a "secure payment" tool that hands control to a DTMF capture provider. The customer types digits as normal. The AI receives only the result (success/fail/token) and continues the conversation. Pattern B -- Voice transcription suppression. The AI agent stays in control but the speech-to-text layer is configured to strip card-shaped sequences before they reach the LLM, with payment capture handled out of band via a side-channel (SMS link mid-call, IVR transfer, agent escalation). Pattern A maps cleanly onto existing DTMF infrastructure. Pattern B is newer and trickier -- it requires confidence that no card data residue survives in transcripts, embeddings, or training data. For most AI voice payment deployments today, Pattern A is the safer architectural choice. ## Shuttle's Approach to DTMF Payments Shuttle is a PCI DSS Level 1 Service Provider. When it's time to pay, the secure card capture takes over at the point of payment, the customer enters their card on the keypad inside Shuttle's certified environment, and the card is forwarded to the merchant's chosen payment gateway over a protected channel. The card never reaches the merchant's platform, recordings, or agents. How it runs today (be clear on this). Shuttle's voice card capture runs on Twilio Pay today. Using Shuttle for voice therefore means being a Twilio customer. The secure capture is scoped to the point of payment; Shuttle riding the full live call is not yet turnkey. Returning the caller to the same agent afterwards works today: you program the return route in your Twilio flow and pass a conversation ID. Shuttle works with Twilio today, and any carrier coming soon. For gateways or platforms where voice capture isn't available, payment links (sent by SMS or email, including mid-call) are the turnkey path. Two further design choices matter for buyers comparing options: No card storage. Shuttle does not operate a card vault. Tokenisation is handled by the underlying gateway. Shuttle hands the gateway's token back to the merchant but never holds the card data itself. This keeps the blast radius small and avoids putting the merchant in the position of trusting Shuttle as a card storage vendor as well as a transaction router. Gateway-agnostic. Shuttle integrates with 40+ PSPs, so the capture isn't tied to a specific processor. Merchants can switch gateways without re-implementing the payment layer, and platforms can offer payments to merchants on different PSPs without forcing a switch. One caveat: a few gateways (such as Braintree) won't allow raw card data over voice, so they work for payment links but not for keypad capture. The full architectural detail is at docs.shuttleglobal.com/docs/twilio-intro. ## DTMF Payments FAQ How do you send DTMF digits mid-call on a Twilio media stream? A common developer question: once a call is running TwiML's `` (the architecture behind most AI voice agents), calling `calls(callSid).update()` with `` replaces the TwiML document, which kills the stream. Because a bidirectional media stream gives you the raw audio channel, the working approach is to send the DTMF as in-band audio: generate the dual-tone frames (8kHz mulaw) and push them as media events over the WebSocket. If you only need to listen to the call, use the asynchronous `` instead, which survives TwiML updates, so `` works without dropping it. And if the digits you need to send or capture are card numbers, stop: card digits must never pass through your application or the LLM pipeline. Use Twilio `` with a PCI-certified connector so capture happens inside a certified environment. What is DTMF masking? DTMF masking replaces the real keypad tones a customer enters with substitute tones in the call audio path, so the agent and the call recording can't decode the original digits. The real digits are forwarded separately to the payment gateway. Is DTMF payment processing PCI compliant? DTMF payment processing is PCI compliant when the card is captured inside a certified environment, typically a PCI DSS Level 1 Service Provider handling the secure capture at the point of payment, and the merchant's systems never receive the decodable card data. Implementation matters more than the label. What's the difference between DTMF clamping and masking? Clamping replaces the customer's tones with flat, neutral audio (no digit pattern preserved). Masking replaces them with substitute tones that preserve some call cadence. Clamping is more aggressive and typically gives stronger PCI scope reduction. Can AI voice agents take DTMF payments? Yes -- modern DTMF capture providers integrate with AI voice agent platforms by exposing a "secure payment" tool the AI invokes mid-conversation. The AI receives only the result; the card data never enters the LLM pipeline. Do I still need PCI compliance if I use a DTMF service? Yes, but the scope drops dramatically. With a Level 1 service provider handling card capture and your systems never touching the tones, you typically qualify for SAQ A (the lightest self-assessment questionnaire) instead of full SAQ D. Can DTMF payments work over softphones and VoIP? Yes, with caveats. The interception still has to happen before the tones reach the call recording or agent -- which is harder over softphones than over traditional SIP trunks. Confirm with your DTMF provider that they certify your specific softphone/VoIP stack. ## Related Reading - PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - the head-term guide to compliant phone payment patterns - Voice Payments: The Complete Guide - PCI Compliance Service Provider: How to Choose One - AI Voice Agents and PCI Payments - Twilio PCI Compliance for Voice Payments - Contact Centre Payments Hub ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### DTMF vs Payment Links: Which is More Secure for Phone Payments? ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [IVR Payments](/guides/ivr-payments/) - [PCI Level 1 service provider](/guides/pci-compliance-service-provider/) - [Genesys](/guides/genesys-payments/) - [Five9](/guides/five9-payments/) - [Talkdesk](/guides/talkdesk-payments/) - [Avaya](/guides/avaya-payments/) - [Cisco](/guides/cisco-webex-payments/) - [NICE CXone](/guides/nice-cxone-payments/) - [AI voice agent flow](/guides/ai-voice-agent-pci-payments/) - [PolyAI](/guides/polyai-payments/) - [Retell AI](/guides/retell-ai-payments/) - [Cresta](/guides/cresta-payments/) - [PCI DSS Level 1 Service Provider](/guides/pci-compliance-service-provider/) - [docs.shuttleglobal.com/docs/twilio-intro](https://docs.shuttleglobal.com/docs/twilio-intro) - [PCI-certified connector](/guides/twilio-pay-connectors/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [PCI Compliance Service Provider: How to Choose One](/guides/pci-compliance-service-provider/) - [AI Voice Agents and PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Twilio PCI Compliance for Voice Payments](/guides/twilio-pci-compliance/) - [Contact Centre Payments Hub](/guides/contact-centre-payments/) - [Book a Call](/discovery/) - [BlogDTMF vs Payment Links: Which is More Secure for Phone Payments?→](/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/ecommpay-twilio-integration/ --- # How to Connect Ecommpay to Twilio for Voice & IVR Payments | Shuttle > Ecommpay doesn't natively connect to Twilio for voice payments. If you want to process Ecommpay transactions during a phone call (via IVR, agent-assisted,... # How to Connect Ecommpay to Twilio for Voice & IVR Payments By Shuttle Team, June 18, 2026 Ecommpay doesn't natively connect to Twilio for voice payments. If you want to process Ecommpay transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Ecommpay (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Ecommpay + Twilio Don't Connect Directly Ecommpay is a UK-headquartered payment service provider and direct card acquirer, authorised by the Financial Conduct Authority, with additional European licensing. It combines its own acquiring, 100+ alternative payment methods, and payouts in a single platform, and it's a popular choice for UK and EU merchants in specialised verticals like travel and ticketing where many mainstream providers are more restrictive. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Ecommpay isn't one of Twilio's built-in connectors, so there's no native path between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Ecommpay's API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Ecommpay. The connector creates an Ecommpay payment request, processes the transaction through your Ecommpay project, and handles the response. - Result returned to your call flow. Your webhook receives the Ecommpay payment reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An Ecommpay account with API credentials (project ID + secret key) - A Shuttle account (free to create: you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Ecommpay Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Ecommpay - Project ID: Your Ecommpay project identifier - Secret key: Your Ecommpay project secret key (used to sign API requests) - Currency: Set your default (GBP, EUR, USD, etc.) - Environment: Live or Test Ecommpay sets up separate test and production projects during onboarding, each with its own project ID. Use the test project first, then switch the profile to your production credentials when you're ready to go live. Save the profile. Shuttle now has a live connection to your Ecommpay account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in Ecommpay if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Use your Ecommpay test project credentials in Shuttle and Twilio's test setup to verify the flow end-to-end before going live. Because Ecommpay's test and production environments use identical request formats, promoting to live is a credentials change, not a rebuild. ## What You Can Do With Ecommpay + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Ecommpay processes, done. ### Authorise Now, Capture Later Place a hold on the card during the call and capture the payment later. Useful for travel bookings, ticketing holds, deposits, or variable-amount transactions where the final figure is confirmed after the call. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Take Deposits and Balances in Travel and Ticketing Call Centres Travel and ticketing are phone-heavy verticals: itinerary changes, group bookings, box office sales, and rebookings all land in the call centre. With Ecommpay handling the acquiring and Twilio handling the call, agents can take a deposit on the booking call and collect the balance later against the stored token, all without ever hearing a card number. ## Multi-PSP: Beyond Ecommpay One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your UK and EU merchants with Ecommpay, and other regions with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Split by amount or transaction type: send high-value bookings to one acquirer and low-value top-ups to another You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly useful for BPOs and outsourced call centres that serve multiple merchants. Each merchant can use their own Ecommpay project (or any other gateway) through the same Twilio integration. ## PCI Compliance The Ecommpay + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Ecommpay (PCI DSS Level 1) Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to Ecommpay. Your application only receives redacted data (last 4 digits, card brand, payment reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Ecommpay to Twilio without Shuttle? Twilio doesn't have a built-in Ecommpay Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports . Configure it with as the connector and the payment step runs within your Studio flow. Does this suit specialised verticals like travel and ticketing? Yes. Ecommpay's own acquiring and appetite for specialised verticals is one of the main reasons merchants choose it. The Twilio integration doesn't change your underwriting: transactions process through your existing Ecommpay project under your existing agreement. What about Ecommpay's test environment? Fully supported. Use your Ecommpay test project ID and secret key in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Ecommpay's standard fees apply on top (your negotiated acquiring rate). No Shuttle setup fees or monthly minimums. Can I switch from Ecommpay to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Paysafe to Twilio for Voice Payments: another gateway with strong specialised-verticals coverage - Enterprise PSP Mandates: When Customers Choose Your Gateway: routing to mandated gateways without re-integrating - Payment Collection for BPOs: multi-merchant voice payments for outsourced call centres - Ecommpay: Ecommpay coverage, currencies, and supported channels via Shuttle - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Ecommpay to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Paysafe to Twilio for Voice Payments](/guides/paysafe-twilio-integration/) - [Enterprise PSP Mandates: When Customers Choose Your Gateway](/guides/enterprise-psp-mandates/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Ecommpay](/payment-providers/ecommpay/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/elevenlabs-payments/ --- # How to Take Payments on ElevenLabs Agents: Native Stripe vs Multi-PSP | Shuttle > Unlike most AI voice platforms, ElevenLabs Agents already has a native payment story. # How to Take Payments on ElevenLabs Agents: Native Stripe vs Multi-PSP By Shuttle Team, May 30, 2026 Unlike most AI voice platforms, ElevenLabs Agents already has a native payment story. Its Stripe integration lets conversational AI agents take payments through saved one-click methods and secure payment links, with the actual card processing handled inside Stripe's PCI DSS Level 1 infrastructure. ElevenLabs explicitly steers agents away from collecting card numbers by voice and toward secure links instead. That is a genuinely good starting point. So this guide is not "ElevenLabs can't take payments." It can. This guide covers what the native Stripe integration does, where it stops, and when teams reach for Shuttle as the payment layer instead of, or alongside, the native option. The short version: if you only need Stripe, and you only need link or saved-method payments, the native ElevenLabs integration may be all you need. If you need more than one payment gateway, in-call card capture by keypad, or a single payment layer across ElevenLabs and your other channels, that is where Shuttle fits. ## What the Native ElevenLabs + Stripe Integration Covers The native integration is built specifically on Stripe. From the documentation, it provides: - Secure payment links for card data collection, sent during or after the conversation - One-click payments using a customer's saved Stripe payment method - Conversational checkout including cart management, order confirmation, and receipts - PCI DSS Level 1 processing via Stripe's infrastructure, so card data is handled by Stripe rather than stored on your systems Notably, ElevenLabs guidance is explicit that agents should never request card numbers through voice and should direct customers to secure payment links. So the native model is link-first and saved-method-first, by design. For a business that runs entirely on Stripe and is happy with link or saved-method payments, that covers a lot. ## Where the Native Integration Stops Three limits matter for many teams. It is Stripe-only. The native integration connects to Stripe and nothing else. If your business uses Adyen, Worldpay, Checkout.com, or any other gateway, or an enterprise client mandates a specific PSP, the native path does not reach them. Agencies running ElevenLabs agents for multiple clients cannot route each client to its own gateway. There is no in-call card capture by keypad. Because the native model deliberately avoids voice card entry, there is no way for a caller to key their card in on the phone mid-call and have it captured securely in the same flow. The customer is sent to a link. For some journeys that is fine; for others, especially older or less digital callers, the link adds friction and drop-off where a keypad payment would have closed there and then. It is one channel. The native integration lives inside ElevenLabs. If you also take payments through a contact centre, an IVR, or human agents on another platform, you end up with separate payment setups and separate reporting per channel. ## How Shuttle Fits Shuttle is a PCI DSS Level 1 certified Service Provider that acts as a payment layer across your channels, including ElevenLabs agents. You can use it instead of the native integration when its limits bite, or alongside it. There is no native ElevenLabs integration for Shuttle. The handoff is API-driven and built on Shuttle's Twilio-based capture, so you must be a Twilio customer, and your application code triggers the handoff at the point of payment. Multi-PSP routing. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. Set which provider handles each payment type, with amount and currency filters. For agencies and enterprises, each client or market can use its own gateway through a single integration. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed. Secure in-call keypad capture. When you do want the customer to pay by keypad during the call, your application invokes Shuttle's secure capture at the point of payment. The card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay) inside Shuttle's certified environment, so the digits never reach the ElevenLabs platform or your recordings. The agent's voice pauses during entry and resumes on the result. Payment links too. Shuttle also generates hosted payment links by SMS or email, including mid-call, so you keep the link option where it suits, across any of your supported gateways rather than Stripe alone. Payment links are the turnkey path and work even with gateways that do not support voice capture. One layer across channels. If you run ElevenLabs with other voice or contact-centre channels, Shuttle is the single payment layer and single source of payment reporting across all of them. ## How It Works with Shuttle - Your ElevenLabs agent runs the conversation and reaches the payment step. - A tool call from your application triggers Shuttle to create a payment session with the amount, currency, and gateway configuration. - The customer pays either by keypad, where a secure PCI DSS Level 1 capture takes the card at the point of payment (today, via Twilio Pay), or by a secure link Shuttle sends. - Shuttle processes the payment through your configured gateway inside its certified environment. - The result returns to your application as a webhook with the outcome, a transaction reference, and a masked card number, and the agent confirms. Card data never enters the ElevenLabs platform, your transcripts, or your recordings, so your application stays at SAQ-A. One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same ElevenLabs agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native ElevenLabs integration is possible only as a paid project. ## When to Use Which - Native ElevenLabs + Stripe: you are Stripe-only, link and saved-method payments are enough, and ElevenLabs is your only payment channel. - Shuttle: you need more than one gateway, an enterprise client or market mandates a specific PSP, you want in-call keypad payments, or you want one payment layer across ElevenLabs and your other channels. Many teams start native and move to Shuttle when a second PSP, an enterprise mandate, or a multi-client requirement appears. ## FAQ Can ElevenLabs agents take payments natively? Yes. ElevenLabs has a native Stripe integration with secure payment links and one-click saved-method payments, processed under Stripe's PCI DSS Level 1 infrastructure. Does Shuttle have a native ElevenLabs integration? No. There is no native ElevenLabs integration for Shuttle today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native ElevenLabs integration is possible only as a paid project. Does this require Twilio? Yes, today. Shuttle's secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Does the native integration support gateways other than Stripe? No. It is Stripe-only. For Adyen, Worldpay, Checkout.com, or per-client routing, you need a multi-PSP payment layer such as Shuttle, which connects to 30+ gateways. Switching gateway is configuration, not re-integration. Can a customer pay by keypad during an ElevenLabs call? Not with the native integration, which directs customers to payment links rather than voice or keypad card entry. With Shuttle, your application can invoke a secure PCI DSS Level 1 capture at the point of payment (today, via Twilio Pay) so the customer keys their card in without it reaching ElevenLabs. Is card data kept out of scope? With Stripe-native links, card data is handled by Stripe. With Shuttle, card data is captured and processed in Shuttle's PCI DSS Level 1 environment and never reaches the ElevenLabs platform or your recordings. Either way your application can stay at SAQ-A. What does Shuttle cost? $0.20 per successful transaction for voice, with no setup fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents - Vapi Payments: secure payment capture for Vapi voice agents - Bland AI Payments: secure payment capture for Bland AI phone agents - Synthflow Payments: native Stripe vs multi-PSP for Synthflow voice agents - How AI Voice Agents Take PCI-Compliant Payments: the technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared ## Add Multi-PSP Payments to Your ElevenLabs Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If your ElevenLabs agents have outgrown Stripe-only payments, or you need in-call card capture and routing across multiple gateways: See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [Retell AI Payments](/guides/retell-ai-payments/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [Synthflow Payments](/guides/synthflow-payments/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/embedded-payments-for-ccaas/ --- # Embedded Payments for CCaaS: The Platform Operator's Guide | Shuttle > Your platform handles the hardest thing in customer communications -- live voice, real-time intent, emotional conversations, AI routing. # Embedded Payments for CCaaS: The Platform Operator's Guide By Shuttle Team, February 17, 2026 Your platform handles the hardest thing in customer communications -- live voice, real-time intent, emotional conversations, AI routing. You've invested heavily in getting that right. But there's a moment in thousands of calls every day where everything falls apart: the customer says they want to pay. What happens next on your platform? If you're like most CCaaS operators, it's one of three things -- and none of them are good. ## The CCaaS Payment Problem Option one: The agent reads out a payment link URL. The customer writes it down, hangs up, navigates to a browser, and completes payment 20 minutes later. Or doesn't. Your call centre just became a lead generation tool for cart abandonment. Option two: The call transfers to a legacy IVR for card entry. A significant share of customers drop at the transfer. Those who stay through an archaic IVR experience blame your customer for the frustration, not the underlying system. And the IVR is almost certainly running on infrastructure your enterprise customer owns and maintains separately -- which is why they came to you in the first place. Option three: The agent takes the card number verbally. You already know this is wrong. It puts card data into your call recording, your transcription pipeline, your storage layer. You're now in scope for full PCI DSS Level 1 compliance, with everything that entails. If you're running AI transcription and summarisation -- and most of you are -- that card data is flowing through models you don't control. Now layer in AI voice agents, and it gets worse. Your AI agent can handle intent, triage, scheduling, account queries, even escalation logic. But the moment a customer says "I'd like to pay my bill," the AI hits a wall. It can't securely capture a 16-digit card number. It can't do DTMF isolation. It can route to a human -- but that's a step backward from the autonomous flow you've built, and it defeats the cost efficiency argument you're selling to enterprise buyers. This is not an edge case. For CCaaS platforms serving utilities, insurance, debt collection, telecoms, or any business that collects recurring or transactional payments through the contact centre, payments are core to the call flow. Not an afterthought. ## Why Bolting On a Gateway Doesn't Work The obvious response is: "We'll add a Stripe integration." It's the wrong answer, and here's exactly why. PCI scope is the first problem. The moment card data touches your platform -- your telephony infrastructure, your recording layer, your data pipeline -- you inherit PCI scope. That's not a checkbox exercise; for most CCaaS platforms it means a full QSA audit, significant infrastructure changes, and ongoing compliance overhead. Your enterprise customers will ask about this in procurement. If you can't answer it cleanly, you lose deals to competitors who can. Secure card capture requires purpose-built infrastructure. Secure card entry over voice relies on the customer entering their card on the keypad. But those keypresses can be captured in call recordings as audible tones. A compliant solution captures the card inside a PCI-certified payment environment at the point of payment, so the digits never reach your recordings or your platform. That's not a Stripe feature, and it's not something you build in a sprint. AI agent handoff is a hard technical problem, and the honest current state matters. When a customer needs to pay mid-call, the agent has to hand off to a secure payment flow and get the result back so the conversation can continue. The secure card capture at the point of payment is available now (on Twilio Pay today). Returning the caller to the same AI agent afterwards works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes the conversation with context. What is not yet turnkey is the payment layer being present for the entire call. Today the secure capture is scoped to the point of payment. Shuttle works with Twilio today, and any carrier coming soon. Treat any vendor promising zero-wiring, carrier-agnostic mid-call resume with scepticism. Your enterprise customers have their own PSPs. A utility company with 50,000 customers processed through your platform has an existing relationship with Worldpay, or Adyen, or Braintree. They're not switching gateways because you've added Stripe. Any payment solution you embed needs to support the customer's existing gateway. Locking your customers into a single PSP is a deal-breaker at enterprise level, and you'll discover that fact during procurement conversations when it's too late. Adding a gateway solves none of these problems. You need a payment layer built for CCaaS infrastructure. ## What Embedded Payment Infrastructure Looks Like for CCaaS The right architecture keeps card data off your platform entirely. Here's how it works in practice. During a call, whether handled by a human agent or an AI voice agent, when a payment moment is reached, your platform triggers the secure capture. At the point of payment, the payment layer takes over the PCI-sensitive portion: the customer enters their card on the keypad inside the payment layer's certified environment, the transaction is processed through the customer's existing PSP, and a confirmation returns to your platform. The card digits never reach your platform or your recordings. Your platform never sees card data. Your recording layer never sees card data. Your AI pipeline never sees card data. Your PCI scope stays minimal, a significant advantage when you're selling to regulated industries or enterprises with procurement security requirements. The same payment layer supports: - Voice -- secure keypad capture at the point of payment, captured inside the certified environment (on Twilio Pay today, any carrier coming soon) - Payment links -- payment links sent by SMS or email, including mid-call, generated from your agent-side interface. This is the turnkey path and works even with gateways that don't support voice. - APIs for AI and human agent flows -- you build your own agent-side interface against the capture and APIs. Note that the secure capture is scoped to the point of payment today; to return the caller to the same AI agent afterwards, you program the return route in your Twilio flow and pass a conversation ID. One integration, multiple channels, limited PCI scope on your platform. The architecture also supports white-labelling -- the payment experience is branded as your platform, not as a third-party vendor. Your enterprise customers see your brand throughout. Their customers see their brand. Nobody's wondering who "Shuttle" is in the middle of a call. ## The Gap Enterprise Buyers Notice Let's be direct about what's at stake. Your platform is processing calls that involve payments every day. You handle the hardest part, the real-time conversation and the integration complexity, and then the payment drops out of your product and into someone else's. Enterprise buyers increasingly ask how payments are handled before they sign. A platform that can answer inside its own product, on the buyer's existing PSP, is in a different procurement conversation from one that hands the payment off. The integration scales with your customers. When your customer processes more calls, they process more payments, on the same single integration. One integration covers every client, whichever PSP each of them uses. Payments go from being a gap in your platform, a thing enterprise buyers notice you're missing, to part of the product. And there's a churn dynamic here worth naming: CCaaS platforms that offer embedded payments create switching costs that platforms without payments don't have. When payment data, reconciliation workflows, and merchant configuration are all inside your platform, your customers don't leave. ## The Five Things to Get Right If you're evaluating embedded payment options for your CCaaS platform, these are the five criteria that matter. Anything that can't satisfy all five is either a compliance risk or a commercial compromise. 1. PCI scope isolation. The payment layer carries PCI compliance, not your platform. Card data should never touch your infrastructure, your recording layer, or your AI pipeline. Ask specifically whether the card is captured inside the provider's own certified environment (so the digits never reach your recordings), rather than relying on stripping or post-processing inside your stack. Ask which PCI tier the provider is certified at. 2. Channel coverage. You want a single integration that covers voice capture, payment links, and your AI and human agent flows. Be precise about what's turnkey today: payment links work with any supported gateway, while voice capture runs on Twilio Pay today, and returning the caller to the same AI agent is wiring you build in your Twilio flow (route the call back and pass a conversation ID). If you're adding channel-specific point solutions, you're building technical debt and inconsistency across your platform. For the connector that routes Twilio card capture to any of 16+ gateways, see Twilio Pay by Shuttle. 3. PSP flexibility. Your enterprise customers have existing gateway relationships. Your payment layer must support multi-PSP routing and allow each customer to use their own gateway. Any solution that requires a single PSP will fail enterprise procurement at companies with established payment relationships. 4. White-label. The payment experience should be branded as your platform. Your checkout, your merchant portal, your payment links -- all carrying your brand. A third-party logo appearing mid-call flow is a trust problem and a positioning problem. 5. Effort and honesty about timelines. Integrating a payment layer is far faster than building payment infrastructure yourself (full PCI DSS certification typically takes 6-12 months from scratch), because the compliance work is already done. But be wary of fixed go-live promises: you build your own agent-side interface against the provider's capture and APIs, and integrating a given platform may require technical work and, for a packaged build, a paid project. Ask for a scoped estimate for your stack rather than a headline number. ## How Shuttle Works for CCaaS Platforms Shuttle is a payments infrastructure provider built specifically for platforms -- CCaaS operators, AI voice providers, SaaS businesses -- that need to embed payments without becoming payment businesses. You integrate your platform against Shuttle's payment layer. From there: For voice calls: When a payment moment is reached, the secure card capture takes over at the point of payment. The customer enters their card on the keypad inside Shuttle's PCI-certified environment, the card is processed through the customer's PSP, and a confirmation returns to your platform. The card digits never reach your platform or recordings. This runs on Twilio Pay today, so using Shuttle for voice means being a Twilio customer; shuttle works with Twilio today, and any carrier coming soon. For AI and human agent flows: Shuttle provides the secure capture, IVR, and APIs. You build your own agent-side interface to trigger the payment flow and read the result. Be clear on the current state: the secure capture at the point of payment is live now, and you return the caller to the same AI agent by programming the return route in your Twilio flow and passing a conversation ID. The payment layer being present for the entire call is not yet turnkey. That fuller call control is on the roadmap with the carrier-agnostic version. For payment links: Generate and send payment links by SMS or email from your agent-side interface, including mid-call. Links are the turnkey path, work even with gateways that don't support voice, are a separate app, and payment status updates back to your system. Links can be white-labelled and expire on a schedule you control. PSP coverage: Shuttle supports 40+ PSPs. Your customers use their existing gateway, so you don't force them to switch or lose enterprise deals over PSP lock-in. (A few gateways, such as Braintree, work for payment links but won't allow raw card data over voice.) White-label merchant experience: Your brand on the checkout, the payment confirmation, and the merchant portal. Shuttle is the infrastructure layer; your platform is what the customer sees. Revenue share: See /pricing/ for the current model. Timeline: Far faster than building payment infrastructure yourself, since Shuttle carries the PCI compliance and your scope stays minimal. The exact effort depends on your platform and the agent-side interface you build, so ask for a scoped estimate rather than assuming a fixed timeline. PolyAI, a leading AI voice agent provider, uses Shuttle to handle PCI-compliant payment capture within their agent conversations, keeping card data out of their platform. ## What Your Competitors Are Doing The CCaaS market is moving toward embedded payments as a platform capability, not an optional add-on. Enterprise buyers evaluating CCaaS platforms are starting to ask the payments question in procurement: "How do payments work within the call flow?" Platforms that can answer that question clearly -- with a compliant, white-labelled, multi-PSP capable payment layer -- are winning deals that platforms without payments are losing. For the implementation-partner view -- how SIs deliver payments alongside the rest of the CCaaS rollout -- see Payments for CCaaS Implementation Partners. This isn't speculative. The contact centre use case for embedded payments is being driven by the same forces driving AI agent adoption: cost efficiency, customer experience consistency, and operational consolidation. A platform buyer who is consolidating their contact centre onto your platform doesn't want to maintain a separate payment IVR. They want payments to work within the same flow. The platforms that integrate payments now build a structural advantage: sticky customers and a cleaner answer to the enterprise procurement question that's coming more frequently. Waiting to prioritise this means entering more procurement processes at a disadvantage, and doing the integration work later under more pressure. ### A Note on BPOs and Contact Centre Outsourcers This guide is aimed at CCaaS platform operators -- the companies building and selling the contact centre software. But many of your customers are BPOs and outsourced contact centres that handle payments on behalf of their own clients. Their payment problem is different: multiple clients, multiple PSPs, different branding per client. If you're building for BPO customers, or if you're a BPO evaluating payment options, see our dedicated guides on payment collection for BPOs and PCI-compliant payments for contact centres. ## Related Reading - Voice AI Is Booming -- But Can It Take a Payment? -- the market analysis behind the opportunity - AI Payment Security: How AI Agents Handle Card Data -- the PCI architecture explained - How AI Voice Agents Take PCI-Compliant Payments -- the technical deep dive - The CCaaS Payments Revenue Opportunity -- the math on monetising payment volume through your platform - How Platforms Monetise Payments -- the revenue model for platform operators - Agentic Payments in 2026: The Infrastructure Guide -- the broader infrastructure landscape for AI agent payments - Chat Agent Payments -- the chat channel equivalent of voice payment capture - What Is Embedded Payments? -- the fundamentals if you're new to embedded payments - PCI-Compliant Payments for Contact Centres -- the complete guide for contact centre operators (not just platform vendors) - Payment Collection for BPOs -- multi-client, multi-PSP payment collection for outsourcers ## Talk to Us About Adding Payments to Your CCaaS Platform If you're building or operating a CCaaS platform and payments is on your roadmap -- or should be -- we're worth 30 minutes of your time. We've worked with CCaaS operators and AI voice providers on exactly this problem. We know what the integration looks like, what the enterprise procurement questions are, and what the integration involves. Book a Discovery Call -- See How It Works for Platforms ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [DTMF](/guides/dtmf-payments/) - [payment links](/guides/take-payments-online/payment-links/) - [Twilio Pay by Shuttle](/integrations/twilio-pay/) - [Payments for CCaaS Implementation Partners](/guides/payments-for-ccaas-implementation-partners/) - [payment collection for BPOs](/guides/payment-collection-for-bpos/) - [PCI-compliant payments for contact centres](/guides/contact-centre-payments/) - [Voice AI Is Booming -- But Can It Take a Payment?](/blog/voice-ai-payment-infrastructure-gap/) - [AI Payment Security: How AI Agents Handle Card Data](/guides/ai-payment-security/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [Agentic Payments in 2026: The Infrastructure Guide](/blog/agentic-payments-infrastructure-2026/) - [Chat Agent Payments](/guides/chat-agent-payments/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Book a Discovery Call](/discovery/) - [See How It Works for Platforms](/platforms/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/embedded-payments-without-payfac/ --- # Embedded Payments Without Becoming a PayFac | Shuttle > The Pattern It starts the same way for every platform. A customer asks: "Can we pay through your software?" Then an enterprise prospect says: "We need... # Embedded Payments Without Becoming a PayFac By Shuttle Team, December 26, 2025 ## The Pattern It starts the same way for every platform. A customer asks: "Can we pay through your software?" Then an enterprise prospect says: "We need embedded payments -- and we need Worldpay, not Stripe." Then your product team is fielding payment questions in sprint planning. Then your CTO is estimating a 12-month roadmap for payment infrastructure. Payments have gone from a nice-to-have to a requirement. And the first answer most platforms hear is: "Become a PayFac." ## What Is a PayFac (and Why Platforms Consider It) A Payment Facilitator (PayFac) is a business that processes payments on behalf of sub-merchants under its own merchant ID. Think Stripe, Square, or PayPal -- they're PayFacs. Your merchants don't have individual merchant accounts; they process through the PayFac's account. The appeal for platforms is clear: - One integration across every transaction your merchants process - Control over the payment experience - Stickiness -- merchants using your payments don't churn easily It sounds like the right move. Here's why it usually isn't. ## Why Becoming a PayFac Is Harder Than It Looks ### Regulatory Burden PayFacs are regulated entities. You're responsible for: - KYC/AML compliance for every merchant you onboard - Transaction monitoring across your entire merchant base - Fraud liability -- chargebacks and disputes are your problem - State and federal licensing in every jurisdiction you operate - Ongoing reporting to your acquiring bank and card networks This isn't a checkbox exercise. It's an operational function that requires dedicated compliance staff, legal counsel, and ongoing investment. ### PCI Compliance Processing payments means handling card data. That puts you in PCI DSS scope -- potentially at Level 1, the highest certification level. Achieving and maintaining PCI DSS Level 1 typically costs upwards of $2M, including annual audits, infrastructure, and operational controls. ### Capital Requirements Your acquiring bank will require a reserve -- capital you hold against potential fraud, chargebacks, and processing losses. The amount depends on volume and risk profile, but it's real money sitting in a trust account. ### Time to Market Building PayFac infrastructure takes 12-18 months minimum. That includes acquiring bank relationships, compliance frameworks, technology integrations, underwriting processes, and certification. Your enterprise customers are asking for payments now, not in 18 months. ### Ongoing Maintenance PSP APIs change. Compliance requirements evolve. Card network rules update. Fraud patterns shift. Each of these requires engineering time, compliance review, and operational adjustment -- time that comes directly off your product roadmap. ### The Real Cost Platforms that pursue PayFac status typically spend: - $2M+ on PCI compliance alone - 12+ months before processing a single transaction - $360K/year in ongoing infrastructure and operational costs - 20-30% of engineering capacity diverted from core product These aren't hypothetical numbers. They're the reality of running payment infrastructure. ## What Platforms Actually Need Most platforms don't need to be a PayFac. They need four things: ### 1. Embedded Payments That Feel Native A checkout, payment form, or payment flow that lives inside your platform -- branded as yours. The merchant's customer never leaves your interface. They never see a third-party brand. White-label means your brand, your colours, your domain. The payment infrastructure is invisible. ### 2. Merchant Onboarding That Doesn't Require a Compliance Team Getting merchants live should take minutes, not weeks. KYC, compliance checks, and PSP provisioning handled in a single flow -- without your team doing the underwriting. ### 3. PSP Flexibility This is where most solutions fall short. If you embed Stripe, your merchants use Stripe. If you embed Adyen, your merchants use Adyen. This works until an enterprise customer says: "We have a Worldpay relationship and we're not switching." PSP-neutral infrastructure lets your merchants bring their own PSP -- or you choose the best PSP for each market, use case, or merchant segment. One integration, any gateway. ### 4. Multi-Channel Coverage Payments don't just happen at checkout anymore. Your platform may need: - Embedded checkout in your web or mobile app - Payment links sent via email, SMS, or chat - Voice payments for phone-based workflows - AI agent payments for automated sales or service channels A PayFac model locks you into a single channel (online checkout). A payment layer supports all of them. ## The Alternative: A Payment Layer Instead of becoming a PayFac, use a payment layer that sits between your platform and PSPs. Here's what that looks like: You integrate once. A single API connects your platform to 40+ payment gateways. Adding a new gateway doesn't require new integration work. Your merchants choose their PSP. Or you choose for them. Or different merchants use different gateways based on geography, volume, or preference. The payment layer handles routing. PCI compliance is included. The payment layer is PCI DSS Level 1 certified. Card data never touches your infrastructure. Your PCI scope is effectively zero. You go live in weeks. Pre-built merchant onboarding, checkout components, and a management portal -- white-labelled to your brand. No 12-month build project. You offer payments to your merchants. They keep their own PSP contracts and rates, and you avoid the regulatory and operational burden of being a PayFac. You expand to new channels. Voice, links, chat, AI agents -- all through the same integration. Add a new payment channel without re-engineering your payment stack. ## PayFac vs. Payment Layer: A Direct Comparison Becoming a PayFac Using a Payment Layer Time to market 12-18 months PCI compliance You carry it ($2M+) Provider carries it PSP flexibility You are the PSP Any PSP, merchant's choice Merchant onboarding You build it Pre-built, white-label Regulatory burden Full (KYC, AML, licensing) Capital requirements Reserve account required Engineering investment 20-30% of roadmap ongoing Single integration Channel coverage Checkout only Checkout, voice, links, chat, AI Revenue opportunity Higher margin per transaction One integration, without the burden High (white-label, configurable) The honest trade-off: PayFac gives you more margin per transaction and more control. But it costs more, takes longer, and consumes engineering resources that could be building your core product. For most platforms, the math doesn't work. The payment layer delivers 80% of the revenue upside at 10% of the cost and complexity. ## When a PayFac Model Does Make Sense To be fair, there are cases where becoming a PayFac is the right move: - Payments are your core product. If you're building a payments company, not a platform that needs payments, then owning the stack makes strategic sense. - You have the scale to justify the investment. Processing billions in annual volume with the margins to support a dedicated compliance and engineering team. - You need pricing control at the merchant level. Setting your own interchange-plus rates, controlling underwriting criteria, managing risk directly. - You already have the compliance infrastructure. Financial services companies, banks, and regulated entities that are already PCI certified and licensed. If none of these apply, a payment layer is the faster, cheaper, and more flexible path. ## The Enterprise PSP Problem This deserves its own section because it's the pain point that pushes most platforms toward a payment layer. Enterprise customers mandate their PSP. It happens in every industry: - Insurance platforms: carriers require specific payment processors - Travel and hospitality platforms: airlines, hotel chains, and operators have existing PSP relationships - ERP platforms: enterprise clients won't switch PSP for a software vendor For a deeper look at the ERP-platform pattern specifically, see Embedded Payments for ERP Platforms. - Contact centres: clients bring their own gateway and expect the platform to support it If you've built your payments on Stripe, and an enterprise customer requires Worldpay, you have three options: - Turn down the deal. This is what usually happens. - Build a Worldpay integration. And then another one for the next customer's PSP. And another. Each one takes months and expands your PCI scope. - Use a PSP-neutral payment layer. One integration supports whatever gateway the customer brings. Enterprise PSP mandates are the #1 reason platforms move from single-PSP to multi-PSP infrastructure. A payment layer makes this a configuration change, not an engineering project. ## FAQ What's the difference between a PayFac and a payment aggregator? A PayFac processes transactions under its own merchant ID, with sub-merchants beneath it. An aggregator pools transactions from multiple merchants through a single account. In practice, the terms are often used interchangeably, but PayFac implies more control and more regulatory responsibility. Can I still monetise payments without being a PayFac? Yes. A payment layer lets you offer payments to your merchants without carrying the regulatory, compliance, or operational burden of being a PayFac. What about PayFac-as-a-Service (PFaaS)? Providers like Payrix and Finix offer "PayFac in a box" -- you get PayFac-like capabilities without building everything from scratch. This reduces the build time but still carries compliance obligations, and typically locks you into a single PSP. It's a middle ground that works for some platforms but doesn't solve the multi-PSP problem. How long does it take to embed payments using a payment layer? Weeks, not months. Pre-built components for checkout, merchant onboarding, and management portals are white-labelled and deployed as part of the integration. A demo environment can typically be running within hours. What if I've already started down the PayFac path? It's not too late to change course. Many platforms that began building PayFac infrastructure have switched to a payment layer approach after realising the ongoing cost and complexity. The sunk cost is real, but the ongoing savings usually justify the switch. ## Related Reading - PayFac Alternatives for Platforms -- the full landscape of PayFac alternatives - Shuttle vs PayFac-as-a-Service (Payrix, Finix) -- how PFaaS compares to a payment layer - How to Get Payments Off Your Product Roadmap -- the hidden cost of building and maintaining payment infrastructure - How Platforms Monetise Payments Without PSP Lock-In -- embedded payments without PayFac obligations - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways -- the enterprise pain point that drives multi-PSP adoption - Shuttle vs Building In-House -- the full build-vs-buy analysis - Gateway vs Orchestrator vs PayFac vs Payment Layer -- how a payment layer differs from gateways, orchestrators, and PayFac models - Payment Links for Hotels & Holiday Accommodation -- how travel platforms embed payment links without PayFac overhead - Car Dealership Payment Solutions -- payment infrastructure for automotive platforms - Payment Infrastructure for Food Ordering Platforms -- food platforms embedding payments without becoming a PayFac - Payments Are Eating 5-9% of Your Revenue -- why the PayFac build cost surprises most platforms Shuttle replaces the PayFac build with a single integration -- 40+ PSPs, white-label checkout, merchant onboarding, voice payments, and PCI DSS Level 1 compliance included. Your platform embeds payments in weeks, not months. Book a Demo | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Is reselling payments and becoming a PayFac right for my SaaS? ### How Creators, Small Business Owners, and Solo Entrepreneurs Can Accept Payments Without a Shopping Cart ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### PayFac Alternatives for Platforms ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [becoming a PayFac](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [payment gateways](/blog/what-is-a-payment-gateway/) - [hotel chains](/guides/payment-links-for-hotels/) - [Embedded Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [#1 reason platforms move from single-PSP to multi-PSP infrastructure](/guides/enterprise-psp-mandates/) - [aggregator](/blog/what-is-payment-gateway-aggregation/) - [middle ground that works for some platforms](/vs/payrix-finix/) - [PayFac Alternatives for Platforms](/alternatives/payfac/) - [Shuttle vs PayFac-as-a-Service (Payrix, Finix)](/vs/payrix-finix/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Car Dealership Payment Solutions](/guides/car-dealership-payment-solutions/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [Payments Are Eating 5-9% of Your Revenue](/blog/payments-cost-saas-platforms/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [Book a Call](/discovery/) - [BlogIs reselling payments and becoming a PayFac right for my SaaS?→](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [BlogHow Creators, Small Business Owners, and Solo Entrepreneurs Can Accept Payments Without a Shopping Cart→](/blog/how-creators-small-business-owners-and-solo-entrepreneurs-can-accept-payments-without-a-shopping-cart/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [AlternativePayFac Alternatives for Platforms→](/alternatives/payfac/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) --- URL: https://www.shuttleglobal.com/guides/enterprise-psp-mandates/ --- # Enterprise PSP Mandates: Why Platforms Need Multiple Gateways | Shuttle > The Deal You Can't Close The conversation follows a predictable script. Your platform is in late-stage negotiations with an enterprise customer. # Enterprise PSP Mandates: Why Platforms Need Multiple Gateways By Shuttle Team, December 28, 2025 ## The Deal You Can't Close The conversation follows a predictable script. Your platform is in late-stage negotiations with an enterprise customer. The product fits. The pricing works. The technical requirements are met. Then the procurement team asks: "Which payment processor do you use?" "We use Worldpay. We have negotiated rates, existing compliance certifications, and a three-year contract. We're not switching." The deal stalls. Your engineering team scopes a Worldpay integration -- three months minimum, plus PCI scope expansion. The enterprise customer isn't willing to wait. The deal dies, or gets delayed until the prospect finds a platform that supports their gateway. This isn't an edge case. For platforms selling to mid-market and enterprise customers, PSP mandates are one of the most common reasons deals fail to close. ## Why Enterprise Customers Mandate Their PSP It's easy to dismiss PSP mandates as stubbornness. They're not. Enterprise customers have legitimate reasons for requiring specific payment processors: ### Negotiated Rates Large enterprises process millions (or billions) in annual transaction volume. They've negotiated interchange-plus rates, volume discounts, and custom fee structures with their PSP that are significantly better than standard pricing. Switching PSPs means losing these rates and renegotiating from scratch. ### Compliance and Certification In regulated industries -- insurance, financial services, healthcare -- the payment processor is part of the compliance framework. The PSP has been vetted, approved, and certified as part of the enterprise's compliance posture. Switching introduces audit risk, re-certification requirements, and regulatory review. ### Treasury Integration Enterprise payment flows connect to treasury management systems, ERP platforms, and accounting infrastructure. Settlement files, reconciliation formats, and banking relationships are configured for a specific PSP. Changing the PSP disrupts downstream financial operations. ### Contractual Obligations Multi-year contracts with PSPs often include volume commitments, exclusivity clauses, or minimum transaction thresholds. Breaking these contracts carries financial penalties. ### Institutional Knowledge The enterprise's finance team, engineering team, and operations team know their PSP. They understand its reporting, its dispute processes, its API quirks. Switching means retraining staff and rebuilding institutional knowledge. ### Risk Mitigation Large enterprises are conservative about payment infrastructure changes. Payments are mission-critical -- any disruption affects revenue. The perceived risk of switching PSPs often outweighs the perceived benefit of a new software platform. ## Where PSP Mandates Show Up ### Insurance Platforms Insurance carriers processing premium payments, renewals, and claims disbursements typically have long-standing PSP relationships. The carrier's compliance team has approved the processor. Regulatory filings reference the payment infrastructure. A platform offering policy management or claims automation can't require the carrier to switch PSPs. ### Travel Platforms Airlines, hotel chains, and tour operators have negotiated payment terms based on their transaction profiles -- high average transaction values, multi-currency requirements, specific chargeback handling. A booking platform or travel management system that mandates a single PSP loses deals with operators whose payment infrastructure doesn't align. For a detailed look at how travel platforms solve the multi-PSP problem, including airline IATA settlement and OTA multi-currency routing, see our dedicated guide. Hotels face a specific version of this problem with deposit and no-show collection, where the PSP needs to support payment links across multiple properties. ### Contact Centres and BPOs Business process outsourcers handle payments on behalf of their clients. Each client may have a different PSP relationship. A contact centre platform that only supports one gateway can serve one client's payment needs -- but not the next client's. This is arguably the sharpest example of the PSP mandate problem: a single BPO may serve dozens of clients, each mandating their own gateway. For a detailed look at how this plays out operationally, see Payment Collection for BPOs. ### ERP and Finance Platforms Enterprise finance teams integrate payment processing with accounts receivable, cash management, and financial reporting systems. The PSP is a component of a larger financial infrastructure. An invoicing or ERP platform can't ask an enterprise client to rebuild their payment stack. ### Shopping Carts and Commerce Engines Enterprise retailers have existing payment processing agreements, often with regional acquirers for domestic transactions and global PSPs for cross-border. A commerce platform that locks merchants into a single gateway loses retailers who've optimised their payment costs across multiple providers. ## The Platform's Dilemma When an enterprise customer mandates a PSP your platform doesn't support, you have three options: ### Option 1: Turn Down the Deal This is the most common outcome. The platform can't support the customer's required PSP, so the deal doesn't close. The revenue is lost. The customer finds a competitor or builds a workaround. The cost: Lost revenue, plus the signal it sends to your sales team. Once they've lost a few deals to PSP mandates, they start qualifying out enterprise prospects early -- shrinking your addressable market. ### Option 2: Build the Integration Your engineering team scopes and builds an integration with the mandated PSP. This takes 2-6 months depending on the gateway's API complexity, your existing architecture, and PCI considerations. The cost: Engineering time (2-3 engineers for 2-6 months), expanded PCI scope if the new gateway handles card data differently, ongoing maintenance for a gateway that may serve a single customer, and the same problem recurring with the next enterprise customer who mandates a different PSP. ### Option 3: Use PSP-Neutral Infrastructure Your platform connects to a payment layer that already supports the mandated gateway. The enterprise customer's PSP is configured during onboarding. No engineering project required. The cost: Transaction fees to the payment layer provider. No build time. No PCI scope expansion. And the next enterprise customer's PSP mandate is handled the same way -- configuration, not engineering. ## The Compounding Effect PSP mandates don't happen once. They compound. Enterprise deal 1: Customer requires Worldpay. You build the integration. Three months, two engineers. Enterprise deal 2: Customer requires Adyen. Another integration. Three months, two engineers. Enterprise deal 3: Customer requires Checkout.com. Another integration. Meanwhile, Worldpay has updated their API and your first integration needs maintenance. Enterprise deal 4: Customer requires a regional acquirer you've never heard of. Each integration adds: - 2-6 months of engineering work - Expanded PCI scope - Ongoing maintenance burden - A new set of webhooks, error handling, and edge cases - A new PSP relationship to manage By the time you've built four gateway integrations, you have a permanent team maintaining payment infrastructure. Your platform has become a payments company -- which was never the plan. ## How PSP-Neutral Infrastructure Solves This A PSP-neutral payment layer pre-integrates with 40+ gateways. When an enterprise customer mandates their PSP, the platform configures that gateway for the customer -- no engineering work, no PCI scope change, no new integration to maintain. - Enterprise customer says: "We use Worldpay." - Platform configures Worldpay in the payment layer for that customer. - Customer's existing Worldpay credentials are connected during onboarding. - Payments from that customer's end-users route through Worldpay. - Other merchants on the platform continue using their assigned gateways. - All transactions -- regardless of gateway -- appear in the same dashboard. What changes: A configuration setting. What doesn't change: The platform's code, PCI scope, merchant experience, or reporting. The same infrastructure handles the next enterprise customer's PSP mandate, and the one after that. Each is a configuration change, not a project. ## The Revenue Implication Enterprise deals are typically 5-50x the value of SMB customers. A platform that can close enterprise deals by supporting PSP mandates unlocks a fundamentally different revenue tier. The math is straightforward: - Cost of losing enterprise deals to PSP mandates: $100K-$1M+ per deal in annual contract value - Cost of building each PSP integration: $150K-$300K in engineering resources, plus ongoing maintenance - Cost of PSP-neutral infrastructure: Transaction fees on a per-transaction basis For most platforms, the revenue from a single enterprise deal that would have been lost covers the entire cost of PSP-neutral infrastructure for a year. ## FAQ How common are enterprise PSP mandates? Very. In our experience, the majority of enterprise platform deals involve a PSP preference or mandate. The percentage increases with deal size -- the larger the enterprise, the more entrenched their payment infrastructure. Can't I just ask enterprise customers to use Stripe? You can ask. Most will say no. Enterprise procurement teams evaluate software platforms on whether the platform fits their infrastructure -- not the other way around. Asking an enterprise to change their PSP is like asking them to change their bank. What about Stripe Connect for enterprise? Stripe Connect is excellent -- if all your merchants are willing to process through Stripe. Enterprise customers with existing PSP relationships are the specific case where Connect doesn't work. It's not a Stripe limitation in the traditional sense -- it's a business model constraint. Stripe wants to be the PSP; PSP-neutral infrastructure lets the merchant choose. Do PSP mandates apply to small businesses too? Rarely. SMBs typically don't have established PSP relationships and are happy to use whatever gateway the platform provides. PSP mandates are primarily an enterprise phenomenon -- which is why they become critical as your platform moves upmarket. What if the mandated PSP isn't supported? A payment layer with 40+ integrations covers the vast majority of enterprise PSP mandates. For genuinely unusual gateways, the payment layer provider can typically add new integrations based on demand. The important thing is that adding a gateway is the provider's problem, not yours. ## Related Reading - PSP-Neutral vs Single-PSP: Which Approach Is Right? -- the architectural decision framework - Embedded Payments Without Becoming a PayFac -- embed payments without the compliance burden - When Your SaaS Outgrows Stripe Connect -- when single-PSP hits its limits - How Platforms Monetise Payments Without PSP Lock-In -- why PSP flexibility drives more revenue - How to Get Payments Off Your Product Roadmap -- stop building payment infrastructure - Shuttle vs Building In-House -- the full build-vs-buy analysis - What PSP Consolidation Means for Your Platform -- how acquirer mergers accelerate enterprise PSP mandate pressure - PCI-Compliant Payments for Contact Centres -- the complete guide for contact centres navigating PCI compliance - AI Voice Payments for Hotels & Travel -- enterprise hotel chains and OTAs with PSP mandate challenges - Payment Solutions for Travel Platforms -- multi-PSP, multi-currency payment infrastructure for airlines, OTAs, and tour operators - Payment Links for Hotels & Holiday Accommodation -- how hotels collect deposits, no-shows, and upsells via payment links - Car Dealership Payment Solutions -- payment links and multi-PSP infrastructure for automotive Stop losing enterprise deals to PSP mandates. Shuttle connects your platform to 40+ payment gateways through a single integration. When your enterprise customer says "we use Worldpay" -- you say "no problem." Book a Demo | See Platforms ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### What PSP Consolidation Means for Your Platform ### Why You Should Have a Backup Payment Service Provider (PSP) ### Where PSP Distribution Actually Lives ### Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### What Stripe's Unbundling Tells Us About the Future of Payments ## Links - [travel platforms solve the multi-PSP problem](/guides/travel-platform-payments/) - [deposit and no-show collection](/guides/payment-links-for-hotels/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [never the plan](/guides/get-payments-off-your-roadmap/) - [Stripe Connect](/vs/stripe-connect/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [What PSP Consolidation Means for Your Platform](/blog/psp-consolidation-platform-risk/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [Payment Solutions for Travel Platforms](/guides/travel-platform-payments/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Car Dealership Payment Solutions](/guides/car-dealership-payment-solutions/) - [payment gateways](/blog/what-is-a-payment-gateway/) - [Book a Demo](/discovery/) - [See Platforms](/platforms/) - [Book a Call](/discovery/) - [BlogWhat PSP Consolidation Means for Your Platform→](/blog/psp-consolidation-platform-risk/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogWhere PSP Distribution Actually Lives→](/blog/where-psp-distribution-actually-lives/) - [BlogMulti-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know→](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) --- URL: https://www.shuttleglobal.com/guides/fat-zebra-twilio-integration/ --- # How to Connect Fat Zebra to Twilio for Voice & IVR Payments | Shuttle > Fat Zebra doesn't natively connect to Twilio for voice payments. If you want to process Fat Zebra transactions during a phone call (via IVR,... # How to Connect Fat Zebra to Twilio for Voice & IVR Payments By Shuttle Team, June 14, 2026 Fat Zebra doesn't natively connect to Twilio for voice payments. If you want to process Fat Zebra transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Fat Zebra (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. For Australian businesses the fit is particularly strong. Twilio's is available in the Australia (AU1) Twilio region, and Shuttle is one of the connectors Twilio's docs list for AU1. That means an Australian utility, insurer, or collections team can capture card details over the phone with Australian data residency on the Twilio side, and process them in AUD through a local gateway on the Fat Zebra side. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Fat Zebra + Twilio Don't Connect Directly Fat Zebra is an Australian payment gateway built for online commerce. Its REST API handles card processing, tokenisation, card-on-file payments, and digital wallets, and it serves over 100,000 Australian merchants. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Fat Zebra isn't one of Twilio's built-in connectors, so there's no native path between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Fat Zebra's API for processing. One integration connects the two platforms, and because Shuttle's connector is listed for Twilio's AU1 region, the whole flow can run in Australia. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Fat Zebra. The connector creates a Fat Zebra purchase request, processes the transaction through your Fat Zebra merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the Fat Zebra transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability (the AU1 region if you need Australian data residency) - A Fat Zebra account with API credentials (username + API token) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Fat Zebra Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Fat Zebra - Username: Your Fat Zebra API username - Token: Your Fat Zebra API token - Currency: AUD (or another supported currency) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Fat Zebra account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code (AUD for Australian processing) - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in Fat Zebra if needed. Update your account records, confirm to the caller, and continue the flow. ### Step 5: Test Fat Zebra provides a test environment with test card numbers, so you can verify the flow end-to-end before going live. Use your Fat Zebra test credentials in the Shuttle payment profile, run a call through your Twilio flow, and confirm the transaction appears in the Fat Zebra dashboard. ## What You Can Do With Fat Zebra + Twilio ### Charge Immediately Standard purchase flow. The caller pays, Fat Zebra processes in AUD, done. This is the pattern most Australian contact centres need: utilities taking bill payments, insurers collecting premiums, and collections teams settling arrears on the call. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Fat Zebra's card-on-file capability and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Payment Plans and Recurring Collections Tokenise on the first call, then charge the stored card on a schedule. For BPOs and collections teams, this turns a single agent-assisted call into an ongoing payment arrangement without ever re-capturing card details. ### AI Voice Agents The same connector works when an AI voice agent, rather than a human, handles the call. The agent hands off to at the payment step, the caller keys in their card, and Fat Zebra processes the transaction. ## Multi-PSP: Beyond Fat Zebra One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Australian merchants with Fat Zebra and your overseas merchants with a local acquirer in each market - Serve enterprise customers who mandate a specific PSP (Stripe, Adyen, Worldpay, etc.) - Want a backup gateway: if one gateway is down, you can move the affected payment types to another connected gateway - Expand beyond Australia where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This matters for platforms and BPOs that serve multiple merchants. Each merchant can use their own Fat Zebra account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Fat Zebra + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data, SAQ-A Card data flows from Twilio → Shuttle → Fat Zebra. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Fat Zebra to Twilio without Shuttle? Twilio doesn't have a built-in Fat Zebra Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work in Twilio's Australia (AU1) region? Yes. Twilio's is available in the AU1 region, and Shuttle is one of the connectors Twilio lists for AU1. Combined with Fat Zebra's Australian processing, the full payment path suits businesses with Australian data residency requirements. What credentials do I need from Fat Zebra? Your Fat Zebra API username and API token. Enter them in your Shuttle payment profile and the connection is live. No development work on the Fat Zebra side. Does Fat Zebra's test environment work with this? Yes. Use your Fat Zebra test credentials in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Fat Zebra's standard processing fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from Fat Zebra to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect NAB to Twilio for Voice Payments: the other Australian gateway option for Twilio voice payments - Payment Collection for BPOs: multi-client payment collection for outsourced contact centres - Fat Zebra: everything Shuttle supports on Fat Zebra - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Fat Zebra to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Payment Links for Fat Zebra: Send Branded Checkout Links for Australian Merchants ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [BPOs and collections teams](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect NAB to Twilio for Voice Payments](/guides/nab-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Fat Zebra](/payment-providers/fat-zebra/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogPayment Links for Fat Zebra: Send Branded Checkout Links for Australian Merchants→](/blog/payment-links-for-fat-zebra/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/field-agent-payment-collection/ --- # Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals | Shuttle > The Card Terminal Problem at Scale When you have five field agents, card terminals feel manageable. # Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals By Shuttle Team, March 8, 2026 ## The Card Terminal Problem at Scale When you have five field agents, card terminals feel manageable. You buy five devices, hand them out, and everyone collects payments on-site. Simple enough. When you have 20, 50, or 100 agents, the whole thing falls apart. Start with the monthly cost. A card terminal with mobile connectivity runs £20 to £30 per month per device. At 50 agents, that's £1,000 to £1,500 a month just for the hardware rental. That's £12,000 to £18,000 a year before anyone has processed a single transaction. Now add the operational headaches. Devices break. Agents drop them, leave them in vans overnight in winter, spill coffee on them. A replacement takes days to arrive. During that time, your agent either can't collect payment on-site or has to tell the customer "we'll send an invoice." That invoice might take 30 days to get paid instead of getting the money on the spot. Devices go missing. They end up in glove compartments, under seats, in toolboxes. When an agent leaves the company, getting the terminal back becomes a treasure hunt. You're still paying the monthly fee while it sits in someone's spare room. Every terminal needs charging. That means every agent has to remember to charge their device overnight, keep a cable in their van, and actually do it. On a Monday morning after a busy weekend, you'll have agents turning up to jobs with dead terminals. Then there's the signal problem. Card terminals rely on mobile data or Bluetooth paired with a phone. Try taking a payment in a basement, a lift shaft, a server room, or a rural farmhouse. The signal drops and the payment fails. Your agent is standing there with an apologetic face and a customer with a card in hand. Finally, reconciliation. Every terminal generates its own transaction log. With 50 terminals across 50 agents, matching payments to jobs means pulling data from multiple sources and cross-referencing manually. Your accounts team spends hours on this every week. Card terminals were built for shops with a fixed counter and a power socket. Strapping that model onto a mobile workforce of 50+ people is fighting against the design of the product. ## How Payment Links Replace Card Terminals for Field Teams The alternative is simpler than most operations managers expect. Your field agent finishes a job. They open their phone, tap a button in your job management system (or a simple web app), and send the customer a payment link via SMS. The customer taps the link, sees a branded checkout page with the job details and amount, and pays with their card or Apple Pay/Google Pay. Payment confirmed. Matched to the job. Done. No hardware. No charging cables. No mobile signal dependency for the payment itself, because the customer completes the payment on their own phone using their own data or wifi connection. Your agent just needs enough signal to send a text message. For on-site payments where the customer wants to pay right now, the agent can show a QR code on their phone screen instead. Customer scans it, same branded checkout page appears, same result. This works even if the agent has no signal at all, since QR codes are generated in advance and the customer's phone handles the connection. The payment is processed through your existing payment gateway. Shuttle works with 40+ PSPs, so you bring your own provider and keep your existing merchant account, rates, and relationship. Nothing changes on the processing side. You just change how the payment gets collected. At $49 per month for Shuttle's Links Checkout, the cost difference at scale is significant. But the real savings come from eliminating the operational overhead: no device management, no replacements, no charging logistics, and no manual reconciliation. ## SMS Links vs QR Codes vs Both You don't have to pick one. Different situations call for different approaches, and most field teams end up using both. SMS payment links work best when: - The agent wants to send the payment request before arriving, so the customer can pay while the agent is still en route. Useful for call-out fees and deposits. - The job is done and the agent needs to move to the next appointment. Send the link and leave. The customer pays in their own time. - The customer isn't present. Think: landlords who aren't on-site for property maintenance, or office managers who've left for the day by the time an evening job finishes. - You want a paper trail. The SMS with the payment link serves as a record of the amount requested. QR codes work best when: - The customer is standing right there and wants to pay immediately. - You want the fastest possible on-site experience. Scan, pay, walk away. - The agent doesn't have the customer's mobile number. - Signal is poor or non-existent for the agent's phone. The QR code displays offline. The customer's phone handles the rest. The practical approach is to set up both. Your agents will naturally gravitate toward whichever method suits the job. An HVAC technician finishing a boiler repair will probably show the QR code to the homeowner standing in the kitchen. A pest control team doing a commercial treatment after hours will send an SMS link to the facilities manager. Either way, the customer sees the same branded checkout page with the same job details and amount. The back-end process is identical. ## CRM and Job Management Integration Payment collection gets dramatically better when it's wired into the system your agents already use to manage their jobs. Here's what the workflow looks like when your field service management (FSM) or CRM system is connected: - Agent marks the job as complete in the app - System automatically generates a payment link for the quoted amount - Link is sent to the customer via SMS (automatically or with one tap from the agent) - Customer pays - Payment status updates in the job record - Accounts team sees paid/unpaid status across all jobs in real time No manual data entry. No copying amounts between systems. No end-of-week reconciliation sessions. Shuttle's API integrates with any system that supports webhooks or API calls. That covers the major field service platforms: - ServiceM8 and Jobber for trade businesses - Housecall Pro and ServiceTitan for home services - Method CRM and Salesforce for custom field service setups - Fergus for trade contractors in the UK and ANZ markets If your FSM software supports Zapier or Make (formerly Integromat), you can connect it to Shuttle without writing any code. A typical Zapier workflow takes about 20 minutes to set up: when job status changes to "complete," create a payment link via Shuttle's API and send it to the customer's phone number from the job record. For larger operations with in-house dev teams, Shuttle's REST API lets you build payment collection directly into your own workflows, dispatch systems, or custom field service apps. As a Payment Layer that sits between your software and your PSP, Shuttle handles the payment processing, PCI compliance, and multi-gateway routing while your system handles the business logic. ## Cost Comparison: Card Terminals vs Payment Links Card Terminals Payment Links (Shuttle) Hardware cost £0-100 per device upfront (depends on provider) None. Agents use their existing phone Monthly fee per agent £20-30/month per terminal $49/month for Links Checkout Replacement cost £50-100 per broken/lost device + downtime Charging/maintenance Daily charging, cable management, firmware updates Signal dependency Agent's terminal needs mobile data signal to process Customer's own phone/wifi handles the connection Reconciliation Manual. Pull data from each terminal separately Automatic. Payments matched to jobs via API CRM/FSM integration Limited. Most terminals don't talk to your job system Full. API, webhooks, Zapier/Make support Scalability Linear cost increase. 50 agents = 50 terminals + logistics Add users in minutes. No hardware to ship Terminal shows your PSP's branding White-label checkout page with your brand At 10 agents, the monthly hardware cost is roughly comparable. At 50 agents, you're saving £500 to £1,000+ per month on terminal fees alone before factoring in the operational cost of managing devices. The less obvious saving is admin time. Finance teams at field service companies regularly report spending 10 to 15 hours per week reconciling terminal payments to jobs. When payments auto-match to job records, that time drops to near zero. ## What About Customers Who Want to Tap Their Card? This is the most common objection, and it's worth addressing directly. Some customers will ask "can I just tap my card?" when the agent is standing in front of them. It's a fair question. Contactless payments are familiar and fast. Here's the reality: the vast majority of customers are perfectly happy tapping a payment link on their phone. They do it every day when they buy things online, pay parking, or split a restaurant bill. A branded checkout page with the job details, amount, and Apple Pay/Google Pay as a payment option is just as fast as tapping a card. For the small percentage of customers who genuinely prefer card-tap over everything else, you don't need to equip every agent with a terminal. One or two backup terminals kept by team leads or in supervisor vehicles will cover the edge cases. The question to ask is: does a 5% preference justify 100% of your team carrying hardware? Most operations managers, once they see the numbers, decide it doesn't. ## Security and Compliance Sending payment requests via SMS or QR code is actually more secure than handing a card terminal to a field agent. With card terminals, the agent physically handles the customer's card. Even with chip-and-pin or contactless, the card leaves the customer's hand momentarily. That's a trust issue, particularly in a customer's home. With payment links, the customer's card details never go anywhere near the agent's phone. The customer enters their payment information directly on a PCI DSS Level 1 compliant checkout page hosted by Shuttle. Card data is processed by your chosen PSP through Shuttle's secure infrastructure. No card numbers are stored on the agent's device. No card numbers are stored in your CRM. No card numbers exist anywhere in your environment. The agent sees "paid" or "not paid" and nothing else. Shuttle maintains PCI DSS Level 1 compliance, which is the highest level of payment security certification. This is the same standard required of the largest payment processors in the world. For your business, this means you meet card scheme data security requirements without having to manage PCI compliance across dozens of mobile devices in the field. ## Frequently Asked Questions What if the customer doesn't have a smartphone? The payment link works in any web browser, including basic feature phones with internet access. For the rare customer without any internet-capable phone, your agent can take a phone payment through your office team, or you can send the payment link via email instead. In practice, smartphone penetration in the UK is above 95% for adults, so this situation is uncommon. Can agents add tips to the payment? Yes. You can configure payment links to include an optional tip/gratuity field on the checkout page. The customer chooses whether and how much to add. This is popular with home service businesses where customers want to thank a technician for good work. Can agents see if the customer has paid? Yes. Payment status updates are available in real time through the Shuttle dashboard and via API callbacks to your CRM or job management system. Agents can check the status of any payment link they've sent. Managers get a dashboard view across the whole team. What about deposits or part-payments? Payment links can be configured for any amount. You can send a deposit link before the job starts and a balance link after completion. Both link back to the same job record. Some field service businesses use a three-stage approach: deposit on booking, progress payment at midpoint, final balance on completion. Can I use my existing payment gateway? Yes. Shuttle works with 40+ PSPs including Stripe, Worldpay, Adyen, Braintree, and most major UK and European payment providers. You keep your existing merchant account and processing rates. Shuttle sits between your software and your PSP, handling the payment link generation, checkout hosting, and PCI compliance. How quickly can we get started? Most field service businesses are live within a week. The setup involves connecting your payment gateway to Shuttle, configuring your branded checkout page, and setting up the integration with your CRM or FSM software. If you're using Zapier or Make, the integration piece takes less than an hour. ## Related Reading - How to Take Payments Without a Card Machine - Multi-Channel Payment Collection - Best Payment Link Providers - How B2B Service Companies Collect Payments Faster - White-Label Payment Links Ready to replace card terminals across your field team? Talk to Shuttle about Links Checkout for your business. ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ### What Is Local Acquiring? How It Cuts International Payment Costs ### Can You Take Card Payments on a Retell AI Voice Agent? ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [How to Take Payments Without a Card Machine](/guides/take-payments-online/without-card-machine/) - [Multi-Channel Payment Collection](/guides/multi-channel-payment-collection/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [Talk to Shuttle about Links Checkout for your business](/merchants/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) --- URL: https://www.shuttleglobal.com/guides/five9-payments/ --- # How to Take Payments on Five9: PCI-Compliant Contact Centre Payments | Shuttle > Five9 is one of the leading cloud contact centre platforms, serving thousands of organisations across financial services, healthcare, retail, and... # How to Take Payments on Five9: PCI-Compliant Contact Centre Payments By Shuttle Team, March 8, 2026 Five9 is one of the leading cloud contact centre platforms, serving thousands of organisations across financial services, healthcare, retail, and telecommunications. It handles intelligent routing, workforce optimisation, and AI-powered virtual agents. It processes millions of customer conversations daily. What Five9 does not do natively is capture card payments in a PCI-compliant way. Five9 has partnerships with payment providers, but these integrations are typically limited to a single gateway and lack the multi-PSP routing that enterprise customers require. If your contact centre serves multiple clients, operates across regions, or needs to route transactions to different processors based on merchant or currency, the native options fall short. This guide covers how to add secure, multi-gateway payment capture to Five9 using Shuttle, maintaining PCI compliance while keeping your existing telephony and call flows intact. ## The Payment Gap in Five9 Five9 excels at what it was built for: intelligent call routing, agent productivity, and customer experience analytics. But payment capture is not part of that architecture, and the gaps are significant for organisations that need to collect payments during calls. - Limited PSP flexibility. Five9's existing payment partnerships typically lock you into a specific gateway. If your merchants use Worldpay, your payment partner supports Stripe, and there is no easy bridge. Enterprise customers with established gateway relationships cannot simply switch processors. - No multi-PSP routing. BPOs running Five9 on behalf of multiple end clients need to route each client's payments to that client's own gateway. Five9 has no mechanism for this. Each client would need a separate payment integration, or compromise on a shared gateway that many clients will reject. - DTMF exposure in recordings. Without purpose-built DTMF suppression, keypad tones from card entry are captured in call recordings and audible to agents. This puts your telephony, recording infrastructure, and agent workstations into full PCI scope. - AI agent limitations. Five9's Intelligent Virtual Agent (IVA) can handle conversational flows, but when a customer needs to pay, the AI hits a wall. There is no native secure payment handoff that maintains the conversation context and returns a result to the AI flow. - Full PCI scope. Without an external payment layer that isolates card data, any payment flow built on Five9 inherits SAQ-D compliance requirements, the most demanding level, covering hundreds of controls across your entire infrastructure. The practical result: organisations either transfer customers out of Five9 to a separate payment IVR (breaking the experience), send payment links after the call (reducing conversion), or have agents take card details verbally (creating compliance risk). ## How Shuttle Adds Payments to Five9 Shuttle adds PCI-compliant card capture to your Five9 payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Five9 recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Five9 specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Five9 call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Five9 have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When a payment is initiated during a Five9 call, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Five9 recordings, agents, or analytics. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links via SMS or email This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer completes payment on a secure hosted checkout page, and confirmation is returned in real time. This is particularly useful for customers calling from landlines or VoIP clients without keypads, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Five9, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Five9 have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - Customer is on a call managed by Five9, connected to a human agent or an IVA. - Payment is triggered from your agent interface with the amount and currency, or a Five9 IVA flow triggers it via API. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card number, expiry, and CVV on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the merchant's configured payment gateway, any of the 40+ supported PSPs, and authorises in real time. - Result returned to your interface or the IVA flow. The agent confirms the result to the customer, or the IVA continues the conversation autonomously. - No card data in Five9. The card digits never touch your Five9 recordings, CRM, or agent workstations. ## Multi-PSP Support Enterprise contact centres on Five9 rarely operate with a single payment gateway. A BPO serving utility companies, insurance firms, and retail businesses needs to route each client's payments to that client's own processor. A multinational enterprise may need different gateways for different regions. Shuttle supports 30+ payment gateways and routes transactions based on configurable rules: - By merchant: each end client or business unit gets its own gateway configuration. A BPO processing calls for Client A routes to Worldpay; Client B routes to Adyen; Client C routes to Stripe. All through the same Five9 instance and the same Shuttle setup. - By region or currency: GBP payments go to one gateway, USD to another, EUR to a third. This is common for multinational deployments where gateway rates and settlement terms vary by market. - By switching: if the primary gateway is down, you can point the affected payment types at another connected gateway. There is no automatic failover. - By card type: route specific card brands to gateways with preferential rates for those brands. Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This multi-PSP capability is a key differentiator for Five9 deployments in BPO and multi-tenant environments where the native payment options are too restrictive. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. This is the highest level of payment security certification, validated by an annual audit from a Qualified Security Assessor. Because the card is captured in the secure Twilio Pay call, card data never enters your Five9 environment. It is captured, encrypted, and processed entirely within Shuttle's infrastructure. Your Five9 telephony, call recordings, agent workstations, CRM integrations, and network infrastructure stay out of PCI scope, keeping you on the lighter SAQ-A path. Full compliance documentation, including the AOC scope, is in the security docs. For regulated industries like financial services and insurance, this scope reduction is not just a cost saving, it is often a procurement requirement. Enterprise buyers need to see that card data is handled by a certified third party, not by the contact centre platform or the BPO. ## Use Cases ### Financial Services Banks and financial institutions use Five9 for collections, account servicing, and customer support. Payment capture during these calls is routine, settling outstanding balances, processing one-off payments, or setting up payment plans. Shuttle enables agents to collect payments without transferring the customer or breaking compliance. ### Retail and E-Commerce Retail contact centres handle order payments, refunds, and exchanges. Five9 manages the customer interaction; Shuttle handles the payment. For high-value orders where customers prefer to pay by phone, in-call payment capture improves conversion compared to sending a payment link after the call. ### Healthcare Revenue Cycle Healthcare organisations use Five9 for patient billing, insurance verification, and appointment management. Collecting patient payments during billing calls, co-pays, outstanding balances, payment plans, requires PCI-compliant capture. Shuttle provides this without exposing patient payment data to the contact centre environment. ### BPO and Outsourced Contact Centres BPOs running Five9 on behalf of multiple clients face the most complex payment requirements. Each client has its own gateway, its own merchant account, its own settlement process. Shuttle's multi-PSP coverage handles this natively, one integration to Shuttle, with per-client gateway configuration. No need for separate payment integrations per client. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Five9 plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Five9 specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Five9 call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Five9 have already done it. - A native Five9 integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Five9 integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Five9. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Five9 have already done. We can build a native Five9 integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Does Shuttle work with Five9's Intelligent Virtual Agent? Yes. The Twilio Pay capture can be triggered via API from Five9's IVA flows, enabling automated payment capture without agent involvement. The payment result is returned to the IVA so the conversation can continue. You build this handoff against Shuttle's APIs. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can I use my existing payment gateway with Shuttle? Yes. Shuttle supports 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and many more. You keep your existing gateway, rates, and settlement arrangements. ### What does Shuttle cost? $0.20 per successful transaction for voice, with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the complete guide to secure contact centre payments - Twilio Pay Connectors, Shuttle's integration with Twilio payment infrastructure - Voice Payments, how to take payments over voice channels - AI Voice Agent PCI Payments, payment capture for AI voice agents - Embedded Payments for CCaaS, adding payments to CCaaS platforms ## Get Started Shuttle adds PCI-compliant, multi-gateway payment capture to Five9 without expanding your PCI scope or limiting your merchants to a single processor. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [DTMF suppression](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [40+ supported PSPs](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/food-ordering-platform-payments/ --- # Payment Infrastructure for Food Ordering Platforms | Shuttle > The Payment Problem Every Food Ordering Platform Hits Whether you're building a voice AI ordering system, a chatbot that takes orders via WhatsApp, a... # Payment Infrastructure for Food Ordering Platforms By Shuttle Team, February 27, 2026 ## The Payment Problem Every Food Ordering Platform Hits Whether you're building a voice AI ordering system, a chatbot that takes orders via WhatsApp, a delivery marketplace, or a ghost kitchen management platform -- you hit the same wall once you have more than a handful of restaurant clients: Every restaurant uses a different payment processor. Restaurant A is on Toast. Restaurant B uses Square. Restaurant C has a Worldpay merchant account. Restaurant D processes through Stripe. Restaurant E is on Clover with Fiserv. If your platform processes all orders through your own Stripe account, you're adding fees on top of what restaurants already pay their existing processor. The restaurant pays twice -- once for your platform's Stripe fees, and again when reconciling against their POS settlement. If you try to integrate with each restaurant's processor directly, you're building and maintaining 5, 10, 15 separate PSP integrations -- each with different APIs, different webhook formats, different error codes, and different settlement timelines. Neither approach scales. The first creates merchant friction. The second creates engineering debt that never stops growing. ## Who This Affects ### Voice AI Ordering Platforms Companies like SoundHound, ConverseNow, Kea, Loman, VOICEplug, Checkmate, and Tarro are automating phone orders for restaurants. They handle the order. They struggle with the payment. Most fall back to SMS payment links (breaking the voice experience) or route orders to the POS for pay-at-pickup (losing the prepayment guarantee). The payment capture problem is covered in detail in How Voice AI Ordering Platforms Handle Payments. ### Chatbot and Messaging Ordering Platforms that let customers order via WhatsApp, Instagram DMs, Facebook Messenger, or SMS. The order happens in the chat. Payment needs to happen there too -- typically via a payment link sent in the conversation. The link needs to process through the restaurant's PSP, not the chatbot platform's Stripe account. And the link needs to be branded appropriately -- the customer should see the restaurant's name, not a generic checkout. ### Delivery and Marketplace Platforms Online ordering platforms (beyond the major aggregators like Uber Eats and DoorDash) that serve independent restaurants, regional chains, or specific cuisines. These platforms collect payment from the diner and settle with the restaurant -- but each restaurant's settlement requirements differ. Some want funds in their Toast account. Some want bank deposits via their Worldpay settlement. Some want separate settlement for delivery vs pickup orders. ### Ghost Kitchen and Virtual Brand Operators A ghost kitchen runs 5 virtual brands from one physical location. Each brand may have its own: - Merchant account (different legal entities or tax structures) - PSP (different processors per brand or per delivery partner) - Settlement requirements (different bank accounts, different settlement frequencies) Processing all brands through one account creates accounting complexity, tax issues, and reconciliation headaches. Multi-brand operators need sub-merchant routing -- each brand treated as a separate merchant within the platform. ### Restaurant Management Platforms Software that manages operations across multiple restaurants -- POS systems, kitchen display systems, reservation platforms, inventory management. When these platforms add payment capabilities (payment links for phone orders, online ordering, or invoice payments), they need the payment to work with whatever processor each restaurant already uses. ## What Food Ordering Platforms Need From Payment Infrastructure ### Multi-PSP Coverage The platform integrates once. Each restaurant is configured with its existing payment processor. When a customer pays -- whether by voice, chat, payment link, or embedded checkout -- the transaction routes to that restaurant's PSP. Adding a new PSP (because a new restaurant client uses a processor you haven't supported before) is a configuration change, not an engineering project. See PSP-neutral vs single-PSP architecture for the detailed trade-off. ### Payment Capture Across Channels Food orders come through multiple channels: - Phone -- still the dominant channel for independent restaurants. Needs PCI-compliant voice payment capture or a payment link sent mid-call. - Web and app -- embedded checkout on the platform's ordering page or the restaurant's own website. - Messaging -- WhatsApp, SMS, Instagram DMs, Facebook Messenger. Needs payment links that work in-chat. - AI agents -- voice bots and chat agents that handle orders autonomously need to trigger payment capture mid-conversation. All channels should route through the same PSP configuration. A card captured over the phone should reconcile in the same system as an online order. The restaurant shouldn't need to check two dashboards. ### Merchant Onboarding at Scale Onboarding 50 restaurants per month means 50 merchant setups -- each potentially with a different PSP, different settlement account, different branding requirements. Manual onboarding doesn't scale. White-label onboarding flows -- branded as your platform, not as a third-party payment provider -- let restaurants connect their existing PSP credentials, configure their settlement preferences, and go live in minutes rather than days. ### Sub-Merchant and Multi-Brand Support Ghost kitchens, franchise groups, and multi-location operators need payments routed at the brand or location level -- not aggregated into one account. A ghost kitchen with 5 brands needs each brand's payments settled separately. A franchise with 200 locations needs per-location PSP configuration. The platform needs group-level reporting across all brands and locations, while each entity maintains its own payment identity. ### Platform Revenue Model Payment infrastructure shouldn't just be a cost. Platforms that route payments through a payment layer keep one integration across every transaction, instead of building and maintaining one per provider. For a platform processing 100,000 orders per month at an average of £15, even a small per-transaction margin adds up. See how platforms monetise payments for the full commercial model. ## The Build vs Buy Decision ### What building looks like A food ordering platform that builds payment infrastructure in-house faces: Multiple PSP integrations. Toast, Square, Stripe, Worldpay, Adyen -- each is a separate API integration with different data models, webhook formats, and authentication mechanisms. Supporting 5 PSPs means 5 codebases to build and maintain. PCI compliance. Any platform that handles card data -- whether through a web checkout form, a voice channel, or a payment link -- has PCI DSS obligations. The scope depends on architecture, but for platforms handling voice card capture, PCI compliance is a major infrastructure and audit commitment. Merchant onboarding. Building a white-label onboarding flow that connects restaurants to their existing PSP, validates credentials, and configures settlement is product work that doesn't generate revenue directly. Ongoing maintenance. PSP APIs change. PCI standards evolve (4.0.1 is now enforced). Payment methods expand (Apple Pay, Google Pay, Pay by Bank). Each update requires engineering attention. The typical timeline: 6-12 months to build a basic multi-PSP integration, with 2-4 engineers permanently allocated to maintenance. That's engineering capacity not spent on ordering AI, menu management, or restaurant experience -- the things that differentiate your platform. For more on this trade-off, see how to get payments off your product roadmap. ### What buying looks like A payment layer provides multi-PSP routing, payment capture across channels (web, links, chat, and voice), merchant onboarding, and PCI compliance through a single API integration. The platform integrates once. The payment layer handles PSP connectivity, PCI scope, and settlement routing. Each restaurant uses its existing processor. The platform keeps one integration across every merchant. Payment links are the turnkey path: they go out via SMS, email or in-chat, work mid-call, and work even with gateways that don't support voice capture. For voice, Shuttle's secure card capture runs on Twilio Pay today, so voice requires being a Twilio customer; there is no native integration with a voice or AI platform, so the platform builds its own agent interface against Shuttle's APIs, and a packaged integration is available as a paid project. Ongoing maintenance for PSP connectivity, PCI compliance and payment methods is handled by the payment layer. ## Payment Methods for Food Ordering Beyond standard card payments, food ordering platforms increasingly need: Apple Pay and Google Pay. Mobile wallet payments have the highest conversion rates on mobile -- and most food orders happen on phones. Wallet payments should be available on payment links, embedded checkout, and in-app flows. Pay by Bank (Open Banking). For higher-value orders (catering, large group orders, B2B food ordering), Pay by Bank offers lower fees than card processing and instant settlement. Particularly relevant for business catering platforms and wholesale food ordering. Cash on delivery tracking. In some markets and for some restaurant types, cash remains common. The payment platform needs to track cash orders alongside digital payments for accurate reporting and reconciliation -- even though it doesn't process the cash transaction. Split payments. Group orders where multiple people pay their share. The platform needs to generate multiple payment requests for a single order, each processed independently. ## FAQ Do we need to be PCI compliant if we use a payment layer? If the payment layer handles all card capture (web checkout, voice, payment links), your platform never touches card data. Your PCI scope stays at the minimum level -- typically SAQ A or equivalent. The payment layer carries PCI DSS Level 1 certification for all channels. What about tips and service charges? Tips can be added to the payment amount before processing (customer adds tip on the payment page) or processed as a separate transaction. Service charges and delivery fees are included in the order total. The payment layer processes the full amount and the platform handles the split in its settlement logic. Can we still use Stripe for restaurants that don't have their own PSP? Yes. A PSP-neutral architecture doesn't mean you stop using Stripe. It means Stripe becomes one of several available processors. Restaurants with existing PSP relationships use theirs. Restaurants without one can default to Stripe (or whichever processor the platform prefers). The platform configures the default -- it's not a choice the restaurant needs to make. How does this work with existing POS integrations? The payment layer handles payment processing -- it doesn't replace the POS integration. The voice AI or ordering platform still pushes orders to the POS (Toast, Square, Clover) for kitchen display and fulfilment. Payment is handled separately, through the restaurant's configured PSP. The POS shows the order; the payment layer handles the money. What about marketplace-model platforms where the platform is the merchant? Some food platforms operate as the merchant of record -- collecting payment from the customer and settling with restaurants. In this model, the platform processes through its own PSP account. A payment layer supports both models: marketplace (platform is merchant) and agency (restaurant is merchant), often within the same platform for different restaurant segments. ## Related Reading - How Voice AI Ordering Platforms Handle Payments -- the specific payment challenges for voice AI in food ordering - Voice Payments: The Complete Guide -- PCI-compliant payment capture over voice channels - Chat Agent Payments -- payment capture in messaging and chat channels - PSP-Neutral vs Single-PSP -- why food platforms need multi-PSP flexibility - How Platforms Monetise Payments -- the revenue model for embedding payments - Embedded Payments Without Becoming a PayFac -- adding payments without the regulatory burden - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the four categories of payment infrastructure - How to Get Payments Off Your Product Roadmap -- reclaim engineering capacity for your core product Building a food ordering, voice AI, or restaurant platform? Shuttle gives food platforms multi-PSP coverage, payment links, embedded checkout, and secure voice capture (on Twilio Pay today) through a single integration. Payment links are self-serve; for voice you build your own agent interface against Shuttle's APIs. Each restaurant uses their existing processor. Your platform keeps one integration to maintain. PCI DSS Level 1 compliance included. Talk to Us | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Savour the Convenience: How Payment Links are Revolutionizing Food and Beverage Ordering ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### The Future of Platform Payments: From Gateways to Agentic Commerce ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ## Links - [How Voice AI Ordering Platforms Handle Payments](/guides/voice-ai-ordering-payments/) - [PSP-neutral vs single-PSP architecture](/guides/psp-neutral-vs-single-psp/) - [PCI-compliant voice payment capture](/guides/voice-payments/) - [chat agents](/guides/chat-agent-payments/) - [payment layer](/glossary/payment-layer/) - [how to get payments off your product roadmap](/guides/get-payments-off-your-roadmap/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS](/glossary/pci-dss/) - [PSP-neutral architecture](/guides/psp-neutral-vs-single-psp/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [Chat Agent Payments](/guides/chat-agent-payments/) - [PSP-Neutral vs Single-PSP](/guides/psp-neutral-vs-single-psp/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Talk to Us](/discovery/) - [See How It Works](/platforms/) - [Book a Call](/discovery/) - [BlogSavour the Convenience: How Payment Links are Revolutionizing Food and Beverage Ordering→](/blog/savour-the-convenience-how-payment-links-are-revolutionizing-food-and-beverage-ordering/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogThe Future of Platform Payments: From Gateways to Agentic Commerce→](/blog/the-future-of-payments/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) --- URL: https://www.shuttleglobal.com/guides/fortis-twilio-integration/ --- # How to Connect Fortis to Twilio for Voice & IVR Payments | Shuttle > Fortis doesn't natively connect to Twilio for voice payments. If you want to process Fortis transactions during a phone call (via IVR, agent-assisted, or... # How to Connect Fortis to Twilio for Voice & IVR Payments By Shuttle Team, June 12, 2026 Fortis doesn't natively connect to Twilio for voice payments. If you want to process Fortis transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Fortis (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Fortis + Twilio Don't Connect Directly Fortis is an embedded payments platform built for ISVs and B2B software. Its APIs and plugins put payment processing inside the software businesses already run: ERP and accounting platforms like Sage, NetSuite and Acumatica, healthcare practice management systems, and other vertical B2B tools. Tokenisation, recurring billing, and click-to-pay invoicing are core to the platform. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Fortis isn't one of Twilio's built-in connectors, so there is no native path between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Fortis for processing. One integration connects the two platforms. For an ISV or B2B platform that already embeds Fortis, this adds a phone channel without touching the existing payment stack: accounts receivable teams can take a card on a follow-up call, field service businesses can collect deposits by phone, and healthcare providers can settle patient balances during a billing call. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Fortis. The connector creates a Fortis transaction, processes it through your Fortis merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the Fortis transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Fortis account with API credentials - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Fortis Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Fortis - Credentials: Your Fortis API credentials - Currency: Set your default (USD, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Fortis account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in Fortis if needed. Update your invoice or order record, confirm to the caller, and continue the flow. ### Step 5: Test Use Fortis's test environment and Twilio's test credentials to verify the flow end-to-end before going live. Run a full test transaction and confirm the result lands in both your webhook and your Fortis reporting. ## What You Can Do With Fortis + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Fortis processes, done. For AR teams chasing overdue invoices by phone, this turns a promise-to-pay into a settled payment on the same call. ### Authorise Now, Capture Later Place a hold on the card during the call and capture later. Useful for deposits, work orders with a variable final amount, or bookings that need confirmation before billing. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. This suits recurring B2B billing and healthcare payment plans, and the card data is never stored in your systems. ### Add Voice to an Embedded Payments Stack If you're an ISV that embeds Fortis in your ERP, accounting, or healthcare software, the phone channel plugs into the same merchant relationship. Your users take payments in-app through Fortis and over the phone through Twilio, and both land in the same place. See payments for ERP platforms for how platforms structure this. ## Multi-PSP: Beyond Fortis One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your US merchants with Fortis and your international merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Fortis account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Fortis + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to Fortis. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For healthcare software, this matters twice over: card data stays out of the same systems that hold patient records. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Fortis to Twilio without Shuttle? Twilio doesn't have a built-in Fortis Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. I'm an ISV that embeds Fortis. Does this work for my merchants? Yes. Each merchant's payment profile in Shuttle points to their own Fortis account, so voice payments settle alongside their existing in-app transactions. One Twilio integration serves all of them. Does tokenisation work over the phone? Yes. Cards captured via Twilio's verb can be tokenised through Shuttle for reuse across web, mobile, voice, and payment links, which supports recurring billing without your systems ever holding card data. What about Fortis's test environment? Fully supported. Use your Fortis test credentials in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Fortis's processing fees apply on top per your agreement. No Shuttle setup fees or monthly minimums. Can I switch from Fortis to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Payments for ERP Platforms: embedding payment collection inside ERP and accounting software - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Fortis to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [Fortis](/payment-providers/fortis/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [payments for ERP platforms](/guides/payments-for-erp-platforms/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogPayment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations→](/blog/payment-links-for-fortis/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/freedompay-twilio-integration/ --- # How to Connect FreedomPay to Twilio for Voice & IVR Payments | Shuttle > FreedomPay doesn't natively connect to Twilio for voice payments. If you want to process FreedomPay transactions during a phone call (via IVR,... # How to Connect FreedomPay to Twilio for Voice & IVR Payments By Shuttle Team, July 1, 2026 FreedomPay doesn't natively connect to Twilio for voice payments. If you want to process FreedomPay transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects FreedomPay (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This matters most for the businesses FreedomPay serves best: enterprise hospitality, food service, retail, and stadium groups that have already standardised on the FreedomPay Commerce Platform for in-store payments. Reservations desks, central booking lines, and guest services teams take payments over the phone every day. Connecting FreedomPay to Twilio extends the same platform, the same acquiring relationships, and the same reporting to those calls, without adding a separate phone-payments vendor. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why FreedomPay + Twilio Don't Connect Directly FreedomPay is an enterprise commerce platform with a heritage in PCI-validated point-to-point encryption (P2PE). It is strongest where large, multi-location merchants need one payment layer across in-store terminals, kiosks, online checkout, and mobile: hotels, restaurant groups, retailers, stadiums, and venues. Its platform connects those merchants to their chosen acquirers and tokenises cards for reuse across channels. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. FreedomPay isn't one of Twilio's built-in connectors, so there is no native path between the two platforms. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to FreedomPay for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via FreedomPay. The connector submits the transaction to the FreedomPay Commerce Platform, which processes it through your existing merchant configuration and acquiring relationships, then returns the response. - Result returned to your call flow. Your webhook receives the transaction reference, last four digits, card brand, and status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A FreedomPay account with API credentials (Store ID, Terminal ID, and an Enhanced Security Key from FreedomPay's Enterprise Portal) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add FreedomPay Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: FreedomPay - Store ID: Supplied by FreedomPay's boarding team - Terminal ID: Supplied by FreedomPay's boarding team - Enhanced Security Key: Generated in FreedomPay's Enterprise Portal - Currency: Set your default (USD, GBP, EUR, etc.) - Environment: Live or Test (UAT) Save the profile. Shuttle now has a live connection to your FreedomPay account. Keep UAT and production credentials separate: a test Store ID or Terminal ID will not work in live mode, and vice versa. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in FreedomPay's reporting if needed. Update your booking or order, confirm to the caller, and continue the flow. ### Step 5: Test Use FreedomPay's UAT environment with your test Store ID, Terminal ID, and Enhanced Security Key to verify the flow end-to-end before going live. FreedomPay provides test card details for the UAT environment through its developer resources. ## What You Can Do With FreedomPay + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, FreedomPay processes, done. Ideal for guest services teams settling a balance or taking a walk-in booking payment. ### Authorise Now, Capture Later Place a hold on the card during the call and capture later. This fits hospitality workflows naturally: authorise a deposit when the reservation is made over the phone, capture at check-in or after the stay. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token, so you can charge the same guest again across any channel: web, mobile, voice, or payment links. For hotel and restaurant groups already using FreedomPay's tokenisation in-store, this closes the loop: the phone channel joins the same card-on-file strategy, and the card data is never stored in your systems. ### One Platform Across Every Location Large groups run many properties, sites, or venues on FreedomPay. Shuttle payment profiles can map voice payments to the right store and terminal configuration, so central booking lines and individual properties both settle into the correct merchant setup. ## Multi-PSP: Beyond FreedomPay One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: put the merchants in one region on FreedomPay and another region on a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly useful for BPOs and outsourced contact centres serving hospitality and retail clients. One client may be on FreedomPay, another on a different gateway, and both run through the same Twilio integration. ## PCI Compliance The FreedomPay + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing FreedomPay (PCI-validated platform) Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to FreedomPay. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. This mirrors the scope-reduction logic FreedomPay merchants already apply in-store with P2PE: keep sensitive data out of your systems entirely. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect FreedomPay to Twilio without Shuttle? Twilio doesn't have a built-in FreedomPay Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. We run multiple properties on FreedomPay. Can voice payments route to the right one? Yes. Create a Shuttle payment profile per store and terminal configuration, and route each call flow (or each client, for BPOs) to the correct profile. What about FreedomPay's test environment? Fully supported. Use your UAT Store ID, Terminal ID, and Enhanced Security Key in a Shuttle test profile and verify the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. FreedomPay's platform and processing fees apply on top per your agreement. No Shuttle setup fees or monthly minimums. Can I switch from FreedomPay to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - AI Voice Payments for Hotels & Travel: voice payments across reservations, guest services, and OTAs - FreedomPay: FreedomPay on Shuttle, supported features and setup - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect FreedomPay to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs and outsourced contact centres](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [FreedomPay](/payment-providers/freedompay/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments→](/blog/payment-links-for-freedompay/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) --- URL: https://www.shuttleglobal.com/guides/freshdesk-payments/ --- # How to Take Payments in Freshdesk Contact Center: PCI-Compliant Payments | Shuttle > Freshdesk Contact Center (formerly Freshcaller) gives your team cloud voice and a PBX you can provision in-platform, while Freshchat handles messaging and... # How to Take Payments in Freshdesk Contact Center: PCI-Compliant Payments By Shuttle Team, May 16, 2026 Freshdesk Contact Center (formerly Freshcaller) gives your team cloud voice and a PBX you can provision in-platform, while Freshchat handles messaging and Freshdesk handles ticketing. Bundled as Freshdesk Omni, the Freshworks suite runs the conversations, but it does not process card payments natively. When a customer wants to pay during a call or a chat, you need a separate layer to capture and process that payment securely. The common route today is a specialist PCI payments app from the Freshworks Marketplace, which uses DTMF masking with a speech fallback so card data is never seen or heard by the agent. That is a solid, well-established option. This guide covers an alternative for merchants who want broader gateway choice: PCI-compliant payment capture for a Freshworks-based operation, with 30+ gateways, bring-your-own-gateway support, and per-client routing, and it explains exactly what that involves with Shuttle today. It is written for two readers: merchants taking payments inside their Freshworks contact centre, and System Integrators implementing Freshworks deployments who need to add payment capture for their clients. ## The Payment Challenge in Freshdesk Contact Center The moment a customer reads a card number aloud on a Freshcaller call, that data enters your voice path and, if you record calls, your recordings. Both fall inside PCI DSS scope. The same applies to card details typed into a Freshchat thread. Once cardholder data touches your systems, the controls, audits, and evidence required to stay compliant expand sharply. Freshworks does not capture or process card payments natively, so the contact centre alone cannot handle a transaction end to end. You can keep recordings clean with a tool like the Voicebase PCI redaction app, but redaction after the fact is not the same as taking a payment securely in the first place. Building a Level 1 compliant payment capability yourself is expensive. Achieving PCI DSS Level 1 certification typically runs into hundreds of thousands of pounds in initial build, often quoted above $500k, with $200k or more in ongoing annual assessment, tooling, and audit costs. For most merchants and SIs, integrating a certified payment layer is the faster and cheaper path. See our explainer on PCI DSS and PCI scope for the underlying detail. ## How Shuttle Adds Payments to Freshdesk Shuttle adds PCI-compliant card capture to your Freshdesk payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Freshdesk environment or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Freshdesk specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Freshdesk workflow over Twilio, and add your own agent screen if your workflow needs one. Customers running Freshdesk have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent workflow The agent stays on the Freshcaller call or in the Freshchat conversation throughout. When it is time to pay, the agent triggers the payment, confirms the amount with the customer, and prompts them to pay. On voice, the customer keys their card via the keypad in the secure Twilio Pay call; the agent never receives the digits. In Freshchat, the agent sends a secure payment link. The agent watches for the approved result and confirms it to the customer. No card data is ever read aloud, typed by the agent, or written to a ticket. ### Customer experience On voice, the customer enters their card number, expiry, and security code on their phone keypad in the secure call, guided by the agent. In Freshchat, they complete payment through a secure hosted link. They get an immediate confirmation, the same interaction they expect from any modern contact centre. ## Multi-PSP Support Shuttle is gateway-neutral, which matters most when you process across multiple merchant accounts or clients. - 30+ payment gateways supported, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. See the full list on the payment providers page. - Bring your own gateway. Keep your existing processor and pricing; Shuttle adds the capture layer on top. Switching processors later is configuration, not re-integration. - Per-client routing. Route each client, brand, or merchant account to its own gateway from a single integration, which is essential for BPOs and agencies running many accounts. - One layer across channels. The same payment layer covers Freshcaller voice and Freshchat links, so you are not stitching together separate tools per channel. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification. Because the card is captured in the secure Twilio Pay call and never enters your Freshworks environment, your contact centre stays out of scope. In practice this can move your compliance burden from SAQ-D, the most demanding self-assessment questionnaire that applies when you store, process, or transmit card data, toward SAQ-A, the lightest version for merchants who fully outsource cardholder data handling. The exact SAQ that applies depends on your setup, but descoping the contact centre is the single biggest lever. See PCI scope for how this works, and the security docs for the AOC scope. ## Beyond Voice: Payment Links Not every payment happens live on a call, and payment links are the most turnkey path. Shuttle generates hosted payment links your agents can send by SMS, email, or inside a Freshchat thread, including mid-call. The customer pays on a secure hosted page, the result flows back to your records, and no card data touches your systems. Links work even with gateways that do not support voice capture. This covers follow-up balances, deposits, and any case where the customer prefers to pay in their own time. See the Payment Links docs. ## For Solution Providers and Freshworks Implementation Partners Freshworks has one of the strongest partner ecosystems for adding capability to a deployment. The Freshworks Marketplace (freshworks.com/apps) lists apps that extend Freshdesk, Freshcaller, and Freshchat, and the Freshworks Technology Partner Program lets developers and SIs build apps with Freshworks developer tools and list them on the Marketplace for free. For SIs, Shuttle is the certified payment capture you add to Freshworks deployments via Twilio. You integrate compliant capture into your client's Freshdesk Contact Center and Freshchat workflows, route each client to their own gateway, and deliver PCI-compliant payments without taking on Level 1 build yourself. You build the agent-side interface against Shuttle's APIs once and reuse it across clients, and a native packaged app on the Marketplace is available as a paid project. See our guide for CCaaS implementation partners for the full SI playbook. ## Use Cases ### Bill-Pay and Collections Customers settle invoices, overdue balances, or payment-plan instalments live on a Freshcaller call, with the secure Twilio Pay capture keeping the agent and recordings out of scope. ### Order Taking and Support Payments Support agents take payment for an order, upgrade, or add-on without transferring the customer or breaking the conversation. ### Account Payments Account-management teams collect top-ups, renewals, or subscription payments inside the same Freshworks workflow they already use. ### Bookings and Deposits Take a deposit or full booking payment during the call or chat, then send a payment link for any balance due later. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Freshdesk plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Freshdesk specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Freshdesk workflow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Freshdesk have already done it. - A native Freshdesk integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Shuttle have a native Freshdesk integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Freshdesk or Freshcaller. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your workflow over Twilio), which customers running Freshdesk have already done. We can build a native Freshworks integration, including a Marketplace app, as a paid project, and a carrier-agnostic version is on our roadmap. Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Does Freshdesk process payments natively? No. Freshworks does not capture or process card payments natively. The common route is a specialist PCI payments app from the Freshworks Marketplace, which uses DTMF masking. Shuttle is an alternative if you want 30+ gateways and per-client routing. How do I take PCI-compliant payments in Freshdesk? Add a certified payment layer like Shuttle via Twilio. During a Freshcaller call the customer enters card details on their keypad in a secure Twilio Pay call, or pays through a secure link in Freshchat. Card data flows to Shuttle's PCI DSS Level 1 environment, never into Freshworks, keeping your contact centre out of scope. Which payment gateways does Shuttle support? 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You can bring your own gateway and route each client to a different one. Switching gateways later is configuration, not re-integration. See the payment providers page. Should I build PCI Level 1 capture myself instead? For almost all merchants and SIs, no. A Level 1 build typically exceeds $500k upfront plus $200k or more annually. Integrating a certified layer is faster and far cheaper. Can I take outbound payments too? Yes. The same secure voice capture works on outbound Freshcaller calls for collections and proactive bill-pay, and you can send payment links for customers to pay after the call. ## Related Reading - Contact centre payments: the hub guide covering PCI-compliant payments across every major contact centre platform. - Embedded payments for CCaaS: how the payment layer model works across cloud contact centre platforms. - AI voice agent PCI payments: taking compliant payments through automated and AI-assisted voice. - Payment collection for BPOs: multi-client routing and collections workflows for outsourcers. - Payments for CCaaS implementation partners: the SI playbook for adding payments to contact centre deployments. ## Take Payments in Your Freshdesk Contact Center Add PCI-compliant payment capture to a Freshdesk Contact Center and Freshchat operation via Twilio, with 30+ gateways, bring-your-own-gateway support, and per-client routing. Pricing is $0.20 per successful transaction with no setup or per-seat fees, and Links Checkout is a separate app. See the pricing page for detail. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF masking](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [book a call](/contact/) - [payment providers page](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [guide for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI voice agent PCI payments](/guides/ai-voice-agent-pci-payments/) - [Payment collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [pricing page](/pricing/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/genesys-payments/ --- # How to Take Payments on Genesys Cloud: PCI-Compliant Voice & IVR Payments | Shuttle > Genesys Cloud CX is one of the largest contact centre platforms in the world, powering millions of customer interactions daily across voice, chat, and... # How to Take Payments on Genesys Cloud: PCI-Compliant Voice & IVR Payments By Shuttle Team, March 10, 2026 Genesys Cloud CX is one of the largest contact centre platforms in the world, powering millions of customer interactions daily across voice, chat, and digital channels. It handles routing, workforce management, analytics, and AI-powered experiences at enterprise scale. What it doesn't do is capture payments securely. Genesys Cloud has IVR capabilities and can build sophisticated call flows with Architect. But when a customer on a call says "I'd like to pay my bill," there is no native PCI-compliant mechanism to capture card details without exposing your environment to cardholder data. The moment an agent hears a card number or DTMF tones appear in a call recording, your entire Genesys environment falls into PCI scope. This guide covers how to add secure, PCI-compliant payment capture to Genesys Cloud using Shuttle, without rebuilding your telephony stack or locking your merchants into a single payment gateway. ## The Payment Gap in Genesys Cloud Genesys Cloud CX is built for customer experience orchestration. It routes calls intelligently, supports AI-powered virtual agents, and integrates with CRM platforms. But payments sit outside its architecture for a reason: handling card data requires PCI DSS certification, DTMF isolation, and gateway-agnostic processing, none of which are core to a communications platform. Here is what Genesys Cloud does not provide out of the box: - No DTMF tone suppression. If a customer enters card digits via their keypad during a call, those tones are audible to the agent and captured in call recordings. This puts your telephony, recording, and storage systems into PCI scope. - No native payment gateway integration. Genesys Architect can trigger API calls and route calls, but there is no built-in payment processing engine. You cannot route a card transaction to Stripe, Worldpay, or Adyen from within a call flow without custom middleware. - No multi-PSP routing. Enterprise customers, particularly in insurance, utilities, and collections, typically have existing relationships with specific payment gateways. They need those gateways, not yours. Genesys has no mechanism for routing transactions to different processors based on merchant, region, or currency. - No PCI scope isolation. Without a purpose-built payment layer, any payment flow you build on Genesys inherits full PCI scope. That means SAQ-D compliance across your telephony infrastructure, call recording, agent workstations, and network. The cost and complexity of maintaining this are significant. The result: most organisations running Genesys Cloud either avoid phone payments entirely (sending customers to a website after the call), use pause-and-resume recording (which doesn't actually de-scope the environment), or transfer calls to a separate legacy IVR for payment, breaking the customer experience. ## How Shuttle Adds Payments to Genesys Cloud Shuttle adds PCI-compliant card capture to your Genesys Cloud payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Genesys Cloud recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Genesys Cloud specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Genesys Cloud call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Genesys Cloud have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When a payment is triggered, by an agent action, an Architect flow reaching a payment node, or an AI agent detecting payment intent, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card number, expiry, and CVV on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your Genesys recordings, agents, or analytics. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links during calls This is the most turnkey path. For scenarios where keypad capture is not suitable, for example calls from VoIP clients without keypad access, or where the customer prefers to enter details on their phone screen, Shuttle generates a payment link and sends it via SMS or email, including mid-call while the agent is on the line. The customer completes payment on a secure hosted page, and confirmation is returned in real time. Links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Genesys Cloud, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Genesys Cloud have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - Customer is on a call handled by Genesys Cloud, routed to a human agent or an AI virtual agent via Architect. - Payment is triggered from your agent interface with the amount, currency, and merchant details, or the Architect flow reaches a payment node. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card number, expiry, and CVV on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the merchant's configured payment gateway, Stripe, Adyen, Worldpay, Checkout.com, or any of the 40+ supported PSPs, and authorises in real time. - Result returned to your interface or the Architect flow. The agent confirms the outcome, or the flow continues autonomously if handled by an AI agent. - No card data in Genesys. The card digits never touch your Genesys recordings, CRM, or agent workstations. ## Multi-PSP Support Enterprise organisations running Genesys Cloud rarely use a single payment gateway. A large insurance company might process UK payments through Worldpay, European payments through Adyen, and US payments through Stripe. A BPO operating on behalf of multiple clients needs to route each client's transactions to that client's own gateway. Shuttle handles this by configuration. Provider selection can be set by: - Merchant: each of your clients or business units can have its own gateway configuration - Currency: settle GBP transactions with one gateway, EUR with another, USD with a third - Failover: if a gateway is down, you can move the affected payment types to another connected gateway. There is no automatic failover - Card type: Shuttle does not route by card scheme; provider selection is per payment type Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This flexibility is particularly important for Genesys Cloud deployments in multi-tenant BPO environments, where a single contact centre instance serves dozens of end clients, each with their own payment infrastructure. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification in the payment card industry. Because the card is captured in the secure Twilio Pay call, card data never enters your Genesys Cloud environment. It is captured, encrypted, and processed entirely within Shuttle's certified infrastructure. Your Genesys Cloud deployment, call recordings, agent workstations, CRM systems, and network stay out of PCI scope, keeping you on the lighter SAQ-A path. Full compliance documentation, including the AOC scope, is in the security docs. Your call recordings are clean, they contain no card data. Your transcription and analytics pipelines can process payment calls without risk. Your AI models never see cardholder data. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Insurance Premium Collection Insurance contact centres handle high volumes of premium payments, renewals, and policy adjustments. Genesys Cloud is widely deployed in insurance. With Shuttle, agents can collect payments during policy servicing calls without transferring to a separate IVR, reducing call handling time and improving first-call resolution. ### Debt Collection and Recovery Collections agencies running Genesys Cloud need to capture payments at the moment of agreement, when a customer commits to a payment plan or settlement. Transferring to a website or sending a link after the call dramatically reduces conversion. Shuttle enables in-call payment capture, and multi-PSP coverage lets BPOs process payments through each client's own gateway. ### Travel and Hospitality Travel companies use Genesys Cloud for booking modifications, cancellations, and upsells, all of which may involve payment. Shuttle captures payments during these calls, supporting the complex multi-currency, multi-gateway requirements common in travel. ### Utilities and Telecoms Utility companies process millions of bill payments through contact centres. Genesys Cloud handles the customer interaction; Shuttle handles the payment capture. The combination supports high-volume, low-value transactions at scale, with each client configured against their own gateway. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Genesys Cloud plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Genesys Cloud specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Genesys Cloud call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Genesys Cloud have already done it. - A native Genesys Cloud integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Genesys Cloud integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Genesys. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Genesys Cloud have already done. We can build a native Genesys integration as a paid project, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can I use Shuttle with Genesys Cloud Architect flows? Yes. The Twilio Pay capture can be triggered from within Architect flows, enabling automated payment capture in IVR and virtual agent scenarios without agent involvement. You build this handoff against Shuttle's APIs. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### What does it cost? $0.20 per successful transaction for voice, with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ### Can I keep my existing payment gateway? Yes. Shuttle supports 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and more. You keep your existing gateway relationship, rates, and settlement process. Note that a few gateways (such as Braintree) work for payment links but not for voice capture. ## Related Reading - PCI-Compliant Payments for Contact Centres, comprehensive guide to secure contact centre payment processing - Twilio Pay Connectors, how Shuttle works with Twilio's payment infrastructure - Voice Payments, the complete guide to taking payments over voice channels - AI Voice Agent PCI Payments, adding payment capture to AI voice agents - Embedded Payments for CCaaS, the platform operator's perspective ## Get Started Shuttle adds PCI-compliant payment capture to Genesys Cloud CX without changing your telephony, locking you into a gateway, or expanding your PCI scope. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF tones](/guides/dtmf-payments/) - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment link](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [40+ supported PSPs](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [30+ payment gateways](/payment-providers/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/get-payments-off-your-roadmap/ --- # How to Get Payments Off Your Product Roadmap | Shuttle > "Just One More Sprint on Payments" You know this meeting. It happens every planning cycle. Product wants to ship a new feature. # How to Get Payments Off Your Product Roadmap By Shuttle Team, February 24, 2026 ## "Just One More Sprint on Payments" You know this meeting. It happens every planning cycle. Product wants to ship a new feature. Engineering says they can -- but they need two weeks to fix a PSP webhook issue first. Or update the PCI scanning. Or handle a new dispute flow. Or integrate the PSP that the latest enterprise prospect requires. Payments never occupy one sprint. They occupy a permanent, expanding slice of your engineering capacity -- and they never give it back. This isn't because your team built payments badly. It's because payment infrastructure has an irreducible maintenance cost that grows with every PSP, every channel, every compliance update, and every enterprise customer with specific requirements. The question isn't "how do we build payments better?" It's "should we be building payments at all?" ## How Payments Hijack a Product Roadmap ### Phase 1: The Reasonable Request "We need to accept payments. Let's integrate Stripe." Two engineers, two months. Basic checkout, webhook handling, some reporting. It ships. Everyone moves on. ### Phase 2: The First Complication An enterprise prospect requires Worldpay. Their compliance team mandates it. The deal is worth £500K ARR. ERP vendors face the same decision under different constraints -- see Embedded Payments for ERP Platforms. So your team builds a second PSP integration. Different API, different webhook format, different error codes, different settlement process. Three months of engineering time. The feature roadmap slides. ### Phase 3: The Compliance Burden Your security team runs a PCI scan. Turns out your architecture puts several systems in PCI scope. The remediation project takes two engineers off the roadmap for a quarter. Annual PCI audits become a recurring line item -- not just in cost, but in engineering attention. ### Phase 4: The Channel Expansion Sales wants payment links for outbound campaigns. The contact centre wants phone payments. The AI team wants their voice agent to take payments. Each new channel needs its own payment integration, its own PCI considerations, and its own ongoing maintenance. Your payments codebase is now larger than some of your core product features. ### Phase 5: The Permanent Tax You now have 3-4 engineers who spend most of their time on payment infrastructure. They maintain PSP integrations, handle PCI compliance, debug settlement discrepancies, manage dispute workflows, and respond to PSP API changes. These engineers aren't building your product. They're building someone else's. ## The Real Cost: Engineering Capacity, Not Just Money The £2M PCI cost and £360K annual maintenance figures get attention. But the harder cost to quantify -- and the one that matters most -- is what doesn't get built. For a 20-person engineering team dedicating 4 engineers to payments: Without Payment Burden With Payment Burden 20 engineers on product 16 on product, 4 on payments Annual capacity 80 engineer-quarters on product 64 engineer-quarters on product That's 16 engineer-quarters -- a full year of a 4-person team -- spent on infrastructure that isn't your competitive advantage. Over three years, it compounds. Your competitors (who aren't building payment infrastructure) ship 48 more engineer-quarters of product features. That gap is visible to prospects, to the market, and to your board. ## What "Getting Payments Off the Roadmap" Actually Means It doesn't mean removing payments from your platform. Embedded payments are often essential to your product and your revenue. It means moving payment infrastructure from "things we build and maintain" to "things we use." The same way you don't build your own database engine (you use PostgreSQL), your own hosting stack (you use AWS), or your own email infrastructure (you use SendGrid) -- you don't need to build your own payment infrastructure. ### What You Stop Doing - Building and maintaining individual PSP integrations - Managing PCI DSS compliance and annual audits - Debugging PSP webhook handling and settlement discrepancies - Building payment UIs (checkout forms, payment pages, receipts) - Hiring and retaining payment-specialist engineers - Responding to PSP API changes and deprecations - Building each new payment channel from scratch ### What You Keep Doing - Deciding which payment features your platform offers - Setting pricing and revenue share models - Customising the merchant experience (white-label) - Integrating payment events into your product workflows - Controlling which PSPs your merchants can use - Building differentiated product features on top of payment capabilities ### What Changes - Integration effort: From months per PSP to one integration, once - PCI scope: From your problem to the payment layer's problem - New PSPs: From engineering projects to configuration changes - New channels: From build projects to API calls - Ongoing maintenance: From 3-4 FTEs to zero dedicated payment engineers - Roadmap space recovered: 20-30% of engineering capacity back on your core product ## The Objections (and Honest Answers) ### "We'll lose control of the payment experience" White-label payment infrastructure means you control the brand, the merchant experience, and the business logic. The merchant never sees the payment layer -- they see your platform. You don't lose control; you lose maintenance burden. ### "Adding a dependency is risky" You already depend on external infrastructure for hosting, databases, email, monitoring, authentication. Payment infrastructure is the same category -- mission-critical infrastructure that's better handled by a specialist than built in-house. The risk isn't adding a dependency. It's maintaining a critical system with a team that should be working on something else. ### "Our payment integration is a competitive advantage" Is it? Or is it a cost of entry that every competitor also has? Unless payments are literally your product (you are a payments company), your competitive advantage is your core product -- the workflow, the domain expertise, the user experience that makes customers choose you over alternatives. Payment infrastructure supports that advantage. It rarely is that advantage. ### "We've already invested too much to switch" Sunk cost. The question is forward-looking: what will maintaining this infrastructure cost over the next three years, and what will your team build instead if you don't have to maintain it? If the next three years of maintenance cost (£850K-£1.75M annually) plus the opportunity cost of 4 engineers exceeds the cost of switching to a payment layer, the decision is clear. ### "Our CFO wants us to own the full payment margin" Full margin on a system that costs £1M+ to build and £850K+ per year to maintain is not full margin. It's gross margin minus a very large infrastructure cost. A revenue share model with a payment layer typically yields higher net margin -- lower total cost, faster time to market, and engineering capacity redirected to revenue-generating product features. ## How to Make the Case Internally ### For the CTO "We're spending 20% of our engineering capacity on payment infrastructure. That's X] engineer-quarters per year not spent on specific product feature]. A payment layer eliminates the maintenance burden and gives us multi-PSP, multi-channel coverage through a single integration." ### For the CFO "Our payment infrastructure costs £X] per year in direct costs (engineering salaries, PCI compliance, PSP maintenance) plus £Y] in opportunity cost (features not built). A payment layer replaces this with transaction-based pricing -- typically £Z] per year. Net saving: £A], plus we ship faster." ### For the CEO "We're a your product category] company building payment infrastructure. Every sprint spent on payments is a sprint not spent on core product]. Our competitors aren't building payments -- they're using a layer. We should too." ### For the VP Engineering "I want my team building core product features], not debugging Worldpay webhooks. A payment layer gives us better coverage (40+ PSPs, voice, links, AI) with zero ongoing engineering maintenance." ## FAQ How long does the transition take? Most platforms integrate a payment layer in 2-4 weeks. Existing merchants can be migrated gradually -- no big-bang cutover required. Your team's maintenance burden drops immediately; full migration happens over months as merchant contracts renew. What happens to our existing PSP relationships? They continue. Your existing PSP (Stripe, Adyen, Worldpay, etc.) becomes one of the PSPs available through the payment layer. Merchants currently on that PSP stay on it -- transactions just route through the payment layer. No merchant disruption. Will we still need any payment engineers? You'll need product engineers who understand payment flows (integration, business logic, UX decisions). You won't need infrastructure engineers maintaining PSP integrations, PCI compliance, and settlement reconciliation. The shift is from "build and maintain" to "configure and use." What if we need custom payment logic? Payment layers provide APIs for custom logic -- split payments, escrow, delayed capture, conditional refunds. The difference is you're building custom business logic on top of infrastructure someone else maintains, rather than building both the logic and the infrastructure. ## Related Reading - Shuttle vs Building In-House -- the detailed cost comparison: build vs payment layer - When Your SaaS Outgrows Stripe Connect -- if your team is maintaining a Stripe integration that's grown beyond its original scope - How Platforms Monetise Payments Without PSP Lock-In -- redirect engineering capacity toward revenue-generating payment features - AI Payment Security: How AI Agents Handle Card Data -- why adding AI agent payments to an in-house build is even harder - Agentic Payments in 2026: The Infrastructure Guide -- the next channel your roadmap will need to support - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the full comparison of payment infrastructure categories - Payment Infrastructure for Food Ordering Platforms -- how food platforms reclaim engineering capacity by outsourcing multi-PSP payments - Payments Are Eating 5-9% of Your Revenue -- the real cost of payment infrastructure for SaaS platforms - What is PCI DSS? | What is PCI Scope? | What is a Payment Layer? Ready to get payments off your roadmap? Shuttle replaces your payment infrastructure build with a single integration -- 40+ PSPs, voice payments, payment links, AI agent channels, and PCI DSS Level 1 compliance included. Your team ships product. We handle payments. See How It Works | Calculate Your Savings ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Understand Online Payments - Transform your business ### Improve your cash flow. Stop waiting to get your invoices paid ### Builders who accept cards for payment are better off ### Accept Card Payments: A Complete Guide for Businesses ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [Embedded Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [payment links](/glossary/payment-links/) - [phone payments](/guides/take-payments-online/phone-payments/) - [voice agent to take payments](/blog/agentic-payments-infrastructure-2026/) - [£2M PCI cost and £360K annual maintenance](/vs/build-in-house/) - [Shuttle vs Building In-House](/vs/build-in-house/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [AI Payment Security: How AI Agents Handle Card Data](/guides/ai-payment-security/) - [Agentic Payments in 2026: The Infrastructure Guide](/blog/agentic-payments-infrastructure-2026/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [Payments Are Eating 5-9% of Your Revenue](/blog/payments-cost-saas-platforms/) - [PCI DSS](/glossary/pci-dss/) - [PCI Scope](/glossary/pci-scope/) - [Payment Layer](/glossary/payment-layer/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [See How It Works](/platforms/) - [Calculate Your Savings](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogUnderstand Online Payments - Transform your business→](/blog/understand-online-payments-transform-your-business/) - [BlogImprove your cash flow. Stop waiting to get your invoices paid→](/blog/improve-your-cash-flow-stop-waiting-to-get-your-invoices-paid/) - [BlogBuilders who accept cards for payment are better off→](/blog/building-success-how-accepting-card-payments-can-boost-your-business/) - [BlogAccept Card Payments: A Complete Guide for Businesses→](/blog/the-top-5-reasons-why-your-business-needs-to-accept-card-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/gladly-payments/ --- # Gladly Payments: One Multi-PSP Layer Across Voice and Chat | Shuttle > Gladly is an all-in-one, people-centred customer service platform built around the customer rather than the ticket. # Gladly Payments: One Multi-PSP Layer Across Voice and Chat By Shuttle Team, May 18, 2026 Gladly is an all-in-one, people-centred customer service platform built around the customer rather than the ticket. It unifies voice and IVR, chat, SMS, email, and social into a single agent workspace, and it is a strong fit for retail and direct-to-consumer brands. Teams at consumer names like Crate & Barrel and Ulta use it to give shoppers one continuous conversation across every channel. If you run customer experience for a retail or DTC brand on Gladly, or you implement Gladly for clients as a system integrator, you may already be taking payments inside it. Gladly has native chat payments: agents can accept a credit card inside a messaging conversation, card data appears briefly to a single agent with a configurable display time, nothing is stored in Gladly, and a number typed into chat is masked automatically. For voice, Gladly relies on a third-party agent-assist integration that uses DTMF masking. Gladly states it is PCI DSS Level 2 compliant. This guide is for merchants and SIs who want to understand when a single multi-PSP payment layer across both voice and chat fits better than a native chat tool plus a separate voice path. Shuttle is that layer, and this guide explains exactly what that involves today. ## Gladly's Payments Today: What You Get Out of the box, Gladly gives you native chat payment capture. An agent can request and process a card-not-present payment directly inside a messaging thread. The card details surface to one agent for a short, configurable window, are not retained in Gladly, and Gladly masks card numbers that a customer types into the chat. That covers a real DTC use case well: a shopper messaging in to complete or change an order. For voice, Gladly does not capture cards natively. The supported route is a third-party agent-assist integration that masks DTMF tones during a call. This is a capable approach to descoping voice, and it is the right answer for many Gladly customers. It does require a separate vendor agreement and a Gladly Professional Services implementation. So the honest picture is: Gladly has solid native chat payments, a third-party voice option, and PCI DSS Level 2 compliance. The question is whether you want chat and voice handled by one consistent payment layer, and how much PSP flexibility you need underneath. ## When a Single Multi-PSP Layer Helps A single layer across both channels is worth considering when: - You take payments over both voice and chat and want one workflow, one reconciliation view, and one compliance posture across both, rather than native chat in one place and a separate voice integration in another. - You need secure in-call capture for voice, where the customer keys the card on their phone in a certified call and the digits never reach the agent or your call recording. - You want PSP breadth. Shuttle connects 30+ payment gateways, so you can bring your own gateway and keep the processor and rates you already negotiated. - You run multiple brands or clients and need per-brand or per-client routing, so each retail brand settles to its own processor and merchant account. - You want the highest compliance tier. Shuttle is a PCI DSS Level 1 certified Service Provider. ## How Shuttle Adds Payments to Gladly Shuttle adds PCI-compliant card capture to your Gladly payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Gladly recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Gladly specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Gladly call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Gladly have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent workflow The agent works inside Gladly as normal. On a voice call, they start a secure payment and ask the customer to key in their card; the capture happens in a certified Twilio Pay call, and the screen shows progress and a masked confirmation, never the full number. In chat, the agent sends a secure payment link instead of asking for card details in the thread. The agent sees a clear paid or declined result and continues the conversation. ### Customer experience On voice, the customer keys their card into their own phone keypad in the secure call, so nothing is exposed to the agent or the recording. In chat, the customer taps a secure hosted link to pay. Either way the interaction stays within the same Gladly conversation, so there is no clunky handoff. ## Multi-PSP Support - Connect 30+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. - Bring your own gateway and keep your negotiated rates and existing merchant accounts. - Route per brand for multi-brand retailers, so each label settles to its own processor. - Route per client for agencies and BPOs running Gladly on behalf of several brands. - Switch or add processors later without re-integrating; gateway choice is configuration. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest tier. Because the card is captured in the secure Twilio Pay call and never touches your agents, your Gladly environment, or your call recordings, Shuttle keeps cardholder data out of your PCI scope. For many brands this means qualifying for the lighter SAQ-A rather than the far heavier SAQ-D, which cuts audit cost and effort. Full compliance documentation is in the security docs. ## Beyond Voice: Payment Links Not every payment needs an agent on the line, and payment links are the most turnkey path. With Shuttle you can send a hosted payment link over SMS, email, or chat from inside the Gladly conversation, including mid-call. The customer pays on a secure page, the result flows back to your records, and the same gateways and provider selection apply. Links work even with gateways that do not support voice capture. This is useful for higher-value orders, deposits, or follow-ups after a call ends. See the Payment Links docs. ## For Solution Providers and Gladly Implementation Partners If you implement Gladly for retail and DTC clients, Shuttle is the certified payment capture you add to those rollouts via Twilio, especially the voice path. Gladly has an integration and partner ecosystem, and voice capture is typically delivered through Gladly Professional Services, so payments are a natural part of an implementation scope. Shuttle gives you a repeatable way to add PCI-compliant capture across voice and chat. You build the agent-side interface against Shuttle's APIs once and reuse it across clients, connect each client's preferred gateway from 40+ options, configure per-client routing, and keep card data out of scope by default. For agencies and SIs running Gladly across several brands, one payment layer with per-client routing is far simpler to support than stitching a separate processor integration into each engagement. A native Gladly integration is available as a paid project. Pricing is $0.20 per successful transaction with no setup or per-seat fees, which makes the commercial model easy to pass through to clients. ## Use Cases ### Retail and DTC Order Taking Complete or amend an order during a voice or chat conversation, with the card captured securely and routed to the right brand's processor. ### Bill-Pay and Account Payments Let customers settle balances or recurring charges over voice or a chat link without exposing card data to agents. ### Bookings and Deposits Take a deposit or booking payment in the conversation, then send a payment link for the balance later. ### Customer Support Payments Handle warranty fees, replacement charges, or upgrades inline, keeping the whole interaction in one Gladly thread. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Gladly plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Gladly specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Gladly call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Gladly have already done it. - A native Gladly integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Shuttle have a native Gladly integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Gladly. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Gladly have already done. We can build a native Gladly integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Does Gladly take payments? Yes. Gladly has native chat payments, where an agent can accept a card inside a messaging conversation with card data masked and not stored. For voice, Gladly offers payments through a third-party agent-assist integration that masks DTMF, set up via Gladly Professional Services. Gladly states it is PCI DSS Level 2 compliant. What does Shuttle add? One payment layer across both voice and chat, with secure in-call capture via Twilio, 30+ gateways and bring-your-own-gateway, per-brand and per-client routing, and PCI DSS Level 1 compliance. Which payment gateways does Shuttle support? 40+, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You can keep your current processor and negotiated rates, and switching gateways later is configuration, not re-integration. Can Shuttle handle outbound payments too? Yes. The same secure capture and payment links work on outbound calls and follow-ups, such as collections, renewals, or completing a deferred order. How much does it cost? $0.20 per successful transaction for voice, with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). You bring your own gateway and keep your processing rates. ## Related Reading - Contact centre payments: the hub guide on taking secure payments across any contact centre platform. - Embedded payments for CCaaS: how payment capture fits into modern CCaaS stacks. - AI voice agent PCI payments: keeping payments compliant when AI agents handle calls. - Zendesk payments: the same multi-PSP approach applied to Zendesk. - Payments for CCaaS implementation partners: how SIs add a payment layer to contact centre rollouts. ## Take Payments Across Voice and Chat in Gladly Gladly gives you native chat payments and a third-party voice path. If you want one multi-PSP layer that handles both voice and chat via Twilio, with 30+ gateways and PCI DSS Level 1 compliance, Shuttle fits in cleanly. We'll walk you through what's live today and the path for your setup. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF masking](/guides/dtmf-payments/) - [30+ payment gateways](/payment-providers/) - [Level 1](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [PCI scope](/glossary/pci-scope/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [payment link](/merchants/payment-services/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [$0.20 per successful transaction](/pricing/) - [30+ gateways](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI voice agent PCI payments](/guides/ai-voice-agent-pci-payments/) - [Zendesk payments](/guides/zendesk-payments/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/global-payments-twilio-integration/ --- # How to Connect Global Payments to Twilio for Voice & IVR Payments | Shuttle > Global Payments doesn't natively connect to Twilio for voice payments. If you want to process Global Payments transactions during a phone call -- via IVR,... # How to Connect Global Payments to Twilio for Voice & IVR Payments By Shuttle Team, March 23, 2026 Global Payments doesn't natively connect to Twilio for voice payments. If you want to process Global Payments transactions during a phone call -- via IVR, agent-assisted, or AI voice agent -- you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Global Payments (and 30+ other gateways) to Twilio's `` verb, so you can accept PCI-compliant card payments during any voice interaction. Going live needs a Twilio account and some technical resource on your side -- but Global Payments is a supported voice gateway, so there's no custom connector to build. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Global Payments + Twilio Don't Connect Directly Global Payments is a major worldwide payment technology company, processing billions of transactions across merchant acquiring, issuing, and integrated payments. Its APIs handle payment processing, tokenisation, and reporting for businesses of all sizes. Twilio is built for voice and messaging. Its `` verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's `` needs a Pay Connector to route captured card data to a payment gateway. Global Payments isn't one of Twilio's built-in connectors. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's `` verb and routes it to Global Payments for processing. One integration connects the two platforms. ## How It Works ``` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Global Payments (processing) → Result ``` - Caller reaches payment step. Your Twilio call flow -- IVR, Studio, or custom TwiML -- triggers the `` verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Global Payments. The connector creates a Global Payments transaction, processes the payment through your merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Global Payments merchant account with API credentials - A Shuttle account (free to create -- you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Global Payments Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Global Payments - Merchant ID: Your Global Payments merchant ID - Account / API credentials: Your Global Payments shared secret or API key - Currency: Set your default (GBP, USD, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Global Payments account. ### Step 3: Configure Your Twilio Call Flow Add the `` verb to your TwiML or Twilio Studio flow: ```xml Please enter your card number followed by the hash key. ``` ### Step 4: Handle the Payment Result Twilio sends a POST to your `action` URL with the payment result: ```json "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-7890", "PaymentCardType": "visa", "PaymentConfirmationCode": "GP-TXN-REF-123...", "ProfileId": "your-shuttle-profile-id" ``` ### Step 5: Test Use Global Payments' test environment and Twilio's test credentials to verify the flow end-to-end before going live. ## What You Can Do With Global Payments + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Global Payments processes, done. Ideal for utility payments, insurance premiums, council tax, and account top-ups. ### Authorise Now, Capture Later Place a hold on the card during the call. Capture the payment later -- useful for bookings, service deposits, or variable-amount transactions. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Global Payments and returns a reusable token. Use it for future payments across any channel -- web, mobile, voice, or payment links. ### Enterprise & Government Global Payments is widely used across enterprise, healthcare, and government sectors. If your contact centre or BPO serves clients in these sectors, Shuttle connects their Global Payments merchant accounts to Twilio without those clients needing to change their payment infrastructure. ## Multi-PSP: Beyond Global Payments Your Twilio integration stays the same even if you: - Add a second gateway -- route transactions to Global Payments for some clients and Stripe or Adyen for others - Serve enterprise customers who mandate a specific PSP - Want a backup gateway -- if Global Payments is down, you can move the affected payment types to another connected gateway - Expand internationally where a different acquirer gives better rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. ## PCI Compliance The Global Payments + Twilio integration via Shuttle limits your PCI scope: Layer | PCI handled by DTMF capture & suppression | Twilio Card data processing | Shuttle (PCI DSS Level 1) Payment processing | Global Payments (PCI DSS Level 1) Your systems | No card data -- SAQ-A Card data flows from Twilio → Shuttle → Global Payments. Your application only receives redacted data. You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Global Payments to Twilio without Shuttle? Twilio doesn't have a built-in Global Payments Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework -- handling PCI compliance yourself. Shuttle provides a pre-built, PCI-certified connector. Does this work with Twilio Studio? Yes. Twilio Studio supports the `` widget. Configure it with `shuttle-pay-connector` as the connector and the payment flow works within your Studio flow. Which Global Payments APIs does Shuttle support? Shuttle integrates with Global Payments' ecommerce APIs. The exact configuration depends on your merchant account setup -- the Shuttle dashboard walks you through the credentials needed. What does it cost? Shuttle charges $0.20 per successful transaction for voice. Global Payments' standard processing fees apply on top (your negotiated rate). No Shuttle setup fees or monthly minimums. Can I use Global Payments for both voice and online payments? Yes. Your Global Payments merchant account works the same across channels. Voice payment tokens created via Shuttle can be used for future online or recurring payments. Can I switch from Global Payments to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same -- no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments -- step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice Payments -- step-by-step Adyen + Twilio setup - How to Connect Worldpay to Twilio for Voice Payments -- step-by-step Worldpay + Twilio setup - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup Connect Global Payments to Twilio with Shuttle's Pay Connector -- PCI DSS Level 1, $0.20 per successful transaction, no setup fees. [Install on Twilio](/integrations/twilio-pay/) or [book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### Global Payments: International Solutions for Business ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### Shuttle and Rezkit Partner to Offer Seamless Payment Solutions for Travel and Tourism Businesses ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [contact centre](/guides/contact-centre-payments/) - [BPO](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [How to Connect Worldpay to Twilio for Voice Payments](/guides/worldpay-twilio-integration/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [BlogGlobal Payments: International Solutions for Business→](/blog/global-payments-for-online-and-offline-businesses/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogShuttle and Rezkit Partner to Offer Seamless Payment Solutions for Travel and Tourism Businesses→](/blog/shuttle-and-brightpearl-partner-to-enable-invoice-and-pos-payments-for-global-retailers/) --- URL: https://www.shuttleglobal.com/guides/global-psp-vs-local-acquirers/ --- # Single Global PSP vs Multiple Local Acquirers: How to Decide | Shuttle > Quick answer: one global PSP is simpler to run and usually right until international volume becomes material in a specific market. # Single Global PSP vs Multiple Local Acquirers: How to Decide By Shuttle Team, July 30, 2026 Quick answer: one global PSP is simpler to run and usually right until international volume becomes material in a specific market. Multiple local acquirers can improve the economics and the customer experience in each market, but the cost lands on your team rather than your rate card: more contracts, more reconciliation, more routing logic to maintain, and more places for something to break. The decision is not really about acquiring. It is about who absorbs the operational complexity of running more than one provider. If you want the market coverage without your engineers owning a separate integration per provider, that is a third option, and this guide covers it last. This guide covers what each model looks like day to day, the four tradeoffs the decision always comes down to, how to test an acquirer's performance claims before you sign, and how to sequence a move if you decide to make one. If you want the underlying mechanism first, why a domestic transaction is treated differently to a cross-border one, read what local acquiring is and how it works. This guide assumes you already understand that and picks up at the decision. ## The two models, in operational terms The brochure version of this decision is about fees. The real version is about what your team does every week. Single global PSP. You hold one contract, one integration, one dashboard, one settlement file and one support relationship. Your provider handles cross-border processing to whatever markets you sell into. Some global PSPs hold local acquiring licences in a set of countries and can route domestically inside their own network, which gives you part of the local benefit without you contracting separately. Your engineering surface stays at one API. Your finance team reconciles one source. Multiple local acquirers. You hold a contract per market, or per region. Each one has its own onboarding, its own underwriting, its own API and its own settlement cycle. You decide which transaction goes where, which means you own routing logic. You reconcile several settlement files into one view of revenue. When a provider changes an API or a scheme changes a rule, you absorb that per provider rather than once. Nobody chooses the second model because they enjoy it. They choose it because the first one stopped serving a market well enough, and the difference became big enough to justify the work. ## The four tradeoffs Almost every version of this question reduces to these four. Take them in order of how much they actually bite. Single global PSP Multiple local acquirers One rate card, simple to forecast. Cross-border pricing applies when the acquirer's country differs from the card issuer's country. Domestic pricing in each market where you hold a local relationship. Better unit economics, offset by the internal cost of running the model. One dashboard, one data model, one definition of every metric. Several dashboards with different schemas, different timezones and different definitions of the same word. Someone has to normalise this. Reconciliation One settlement file, one currency treatment, one payout cadence. Several files, several cadences, several currency treatments. This is the tradeoff finance teams underestimate most. Single point of failure. If the provider degrades, you have no alternative path unless you built one. Genuine redundancy, but only if you built the routing to fail over. Holding two contracts and no failover logic gives you the cost of both models and the resilience of neither. Two of these deserve more than a table row. Reconciliation is the one that hurts. Adding a second provider does not just add finance work, it compounds it, because you inherit the job of making two different data models agree. Settlement timing differs. Refund and chargeback handling differ. Fee structures are itemised differently. Currency conversion may happen at different points in the flow. Until someone normalises all of that into one ledger, your month end gets slower and your revenue reporting gets softer. Redundancy only exists if you built the failover. This is worth being blunt about because it is the most commonly claimed benefit of a multi-provider setup and the least commonly realised one. Holding contracts with two providers gives you a commercial fallback, not a technical one. Unless traffic can move between them without a deploy, a provider incident is still an outage. Ask yourself whether you could shift traffic in minutes today. If the honest answer is that it would take an engineering ticket and a release, you do not currently have redundancy. ## How to evaluate an acquirer's authorisation performance without relying on sales claims Providers usually quote a headline authorisation rate. It is rarely comparable, and the ways it becomes incomparable are consistent enough to test for. Aggregate approval rate is close to meaningless on its own. Approval rate is a function of the traffic mix, not just the provider. A provider whose book skews towards domestic consumer debit will show a better headline number than one processing cross-border commercial credit, with no difference in capability. Comparing two headline rates compares two customer bases. Ask for the denominator in writing. Before you compare anything, get the definition. Does an attempt include retries, or does a retried transaction count once? Are 3DS challenge abandonments counted as declines, excluded, or never counted as attempts? Are pre-auths and captures counted separately? Providers make defensible but different choices here, and the choice can move the headline number more than genuine performance does. Insist on segmentation. A useful comparison is split by issuing country, card type (consumer or commercial, debit or credit), channel (ecommerce, telephone or recurring), and ideally BIN cohort. A provider that is genuinely stronger in a market will be stronger inside a segment. A provider that only looks stronger in aggregate is showing you a mix effect. Separate soft declines from hard declines. Hard declines (closed account, reported stolen) are not recoverable and say nothing about the provider. Soft declines (issuer temporary failures, generic do-not-honour) are where routing and retry strategy earn their keep. Ask for the decline-code breakdown. If a provider will not share it, that is itself informative. Ask what retry logic is applied and whether it is counted. Aggressive automated retries can lift a headline approval rate while also increasing scheme fees and, past a point, triggering the card schemes' excessive-reattempt fees. Both Visa and Mastercard operate programmes that charge for reattempts beyond a threshold. You want to know what is being done on your behalf and how it appears in the reporting. The only honest test is matched traffic. Run both providers concurrently over the same period on comparable traffic, split by a neutral rule such as BIN range or round robin, and compare inside segments. Sequential tests are unreliable because seasonality, fraud pressure and your own product changes move the numbers underneath you. Be aware that pilot traffic tends to be your easiest traffic, so a pilot flatters everyone. Ask who decides the routing, and whether you can see it. This is the question people skip. If your provider also owns the acquiring, it has a commercial reason to keep transactions inside its own network, which may or may not be the best path for a given transaction. That is not necessarily wrong, but you should know it is happening, be able to see the decision, and be able to override it. Shuttle is not an acquirer and does not issue merchant accounts, so it has no processing of its own to steer volume into. ## What running multiple providers actually costs you The rate card comparison is the easy part. These are the line items that usually get left out of the business case: - Integration per provider. Each acquirer or PSP is its own API, its own error taxonomy, its own tokenisation model and its own edge cases. This is not a one-off cost, because it recurs every time one of them changes. - Routing logic you own and maintain. Deciding which transaction goes where, handling failover, and keeping the rules current as you add markets. - Reconciliation and reporting normalisation. Covered above. This is usually the largest hidden cost and it falls on finance, not engineering, so it often escapes the original estimate. - Compliance validation. Each acquirer sets its own compliance validation and reporting requirements, so the paperwork and the SCA and 3DS implementation work repeat per relationship. Your PCI scope itself is set by how you handle card data, not by how many providers you hold. - Ongoing maintenance. Provider APIs change, scheme rules update, local regulation evolves. Every additional relationship adds a stream of small mandatory work. None of these are reasons not to run multiple providers. They are reasons to be honest about where the saving goes. A material rate improvement that gets consumed by ongoing engineering and finance maintenance is not a saving, it is a transfer. ## The third option: keep the relationships, drop the integration burden The framing of "one PSP or several" assumes you have to choose between simplicity and coverage. You do not, because the two costs are separable. The commercial relationships and the integration work are different problems. Shuttle is a payment execution layer that sits above PSPs and gateways. You connect to it once, and it connects to the providers you hold relationships with. You keep your own contracts and your own rates, because Shuttle is not an acquirer, not a PSP and not a merchant of record. What changes is where the work sits. Adding a provider becomes configuration and onboarding rather than a new integration build. You choose which connected provider handles a given payment type from the portal rather than in code. Payment methods can be filtered separately by minimum amount, maximum amount and currency. Transaction activity across your connected providers is visible in one place. Be precise about what that does and does not cover, because this is where vendors in this category tend to overpromise. Processor selection is per payment type, and the amount and currency rules filter payment methods. There is no routing by issuing country or BIN. Currency is also not the same thing as market: one currency can span several acquiring markets, so a currency rule will not separate a French acquirer from a German one. Changing which provider handles traffic is a configuration change you make, not automatic failover. And because Shuttle tokenises with the gateway rather than holding card data itself, stored credentials stay with the provider that tokenised them, so continuity for saved cards and subscriptions depends on network tokenisation and on what your providers support. That matters most in three situations: - You are entering a market where your current provider is weak and you want a local relationship without a second integration to build and maintain. - A large customer or a market mandates a provider you do not currently use. If Shuttle already connects to that provider, it becomes a provider you add rather than a build. - You want to be able to move new transaction traffic between providers by changing configuration rather than shipping a release. Shuttle supports a wide range of gateways and providers across a large number of markets. The current supported list is on the payment providers directory. If you want the technical detail on how connections and payment configuration work, the documentation is public, and PCI documentation including the AoC is at docs.shuttleglobal.com/docs/org-security. ## A decision framework Stay on one global PSP if: international volume is not yet material in any single market, your authorisation rates in your main markets are acceptable, no customer or regulator is mandating a provider you cannot support, and you can tolerate a provider incident. This covers a lot of businesses for a long time. Add local acquiring in a specific market if: that one market is now material on its own, and you can point to a concrete problem there such as costs that have become a visible margin item, decline patterns concentrated on domestic issuers, settlement timing that is hurting working capital, or customers expecting local payment behaviour you cannot offer. Add it for that market, on evidence, rather than adopting a multi-acquirer posture everywhere at once. Solve the integration layer first if: you can see more than one of these coming. If you are going to end up with several providers, the order matters. Adding the layer before the second provider means you integrate once. Adding it after means you integrate twice and then migrate. Treat redundancy as its own reason. If concentration risk is the actual concern, say so explicitly, because it changes the design. Redundancy needs failover routing, not just a second contract. ## If you decide to move Do not migrate everything at once. The sequence that tends to work is: agree the metric definitions before you start so you can tell whether it worked, run the new provider in parallel on a slice of traffic, compare inside segments rather than in aggregate, then shift traffic progressively while keeping the ability to roll back. Card data portability is the part that catches people out, particularly with saved cards and subscriptions. That is a solvable problem with a defined process, but it is not automatic and it needs planning before you sign anything. We cover it in detail in how to switch payment providers without losing customers. ## Global PSP vs local acquirers FAQ ### Is a single global PSP always more expensive for international payments? No. It depends on where your volume actually is. A global PSP holding local acquiring licences can route domestically inside its own network in those countries, which captures much of the benefit without you contracting separately. The gap tends to open up in markets where your provider has no domestic presence and your volume there has grown. The honest answer is that it is worth checking per market rather than assuming. ### Do I need separate contracts with each acquirer? In a direct model, yes. Each relationship has its own commercial agreement, underwriting and onboarding. If you use a payment layer above your providers, you still hold the contracts, because the layer is not the acquirer. What changes is the integration and routing work, not the commercial relationship. ### What is the difference between using multiple PSPs and payment orchestration? Using multiple PSPs describes the commercial arrangement. Orchestration describes software that routes between them. The distinction that matters commercially is whether the software also sells you processing, because that creates an incentive in the routing. Worth being clear about where we sit, since this guide describes configuring providers. Shuttle is a payment layer rather than an orchestrator: you configure which connected provider handles a payment type, and Shuttle does not make routing decisions about individual transactions on your behalf. It also has no processing of its own to route to. See payment orchestration vs payment layer for the fuller comparison. ### How do I know if a provider's authorisation claims are real? Get the definition of the metric in writing, insist on segmentation by issuing country and card type, ask for the decline-code breakdown split into soft and hard declines, and ask what retry logic is applied. Then test with matched concurrent traffic rather than sequentially. A provider that is genuinely stronger will be stronger inside a segment, not only in aggregate. ### Does holding two providers give me redundancy? Not on its own. Two contracts with no way to move traffic gives you the cost of a multi-provider setup and the resilience of a single one. Ask how quickly you could actually shift traffic today, and whether that needs a code change. Note also that stored credentials are tokenised with the provider that captured them, so saved cards and subscriptions do not move as freely as new transactions do. ### Should I add local acquiring before or after fixing my integration layer? If you expect to end up with more than one provider, do the layer first. Adding a second provider directly means building an integration you will later migrate. The sequencing is the difference between integrating once and integrating twice. ## Where to go next If you run payments across more than one market and this decision is live for you, the useful next step is a conversation about your specific markets and providers rather than a generic recommendation. - Platforms embedding payments for their customers: platform payment infrastructure - Businesses taking payments in several markets: payment services for merchants - Either way, book a call and we will go through your markets, your current providers and what moving would actually involve. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### What PSP Consolidation Means for Your Platform ### Why You Should Have a Backup Payment Service Provider (PSP) ### Where PSP Distribution Actually Lives ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### Shuttle and vFairs work together to revolutionise global event management ### Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know ## Links - [what local acquiring is and how it works](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [payment providers directory](/payment-providers/) - [documentation](https://docs.shuttleglobal.com/docs/) - [docs.shuttleglobal.com/docs/org-security](https://docs.shuttleglobal.com/docs/org-security) - [how to switch payment providers without losing customers](/guides/payment-provider-migration/) - [payment orchestration vs payment layer](/guides/payment-orchestration-vs-payment-layer/) - [platform payment infrastructure](/platforms/) - [payment services for merchants](/merchants/payment-services/) - [book a call](/contact/) - [Book a Call](/discovery/) - [BlogWhat PSP Consolidation Means for Your Platform→](/blog/psp-consolidation-platform-risk/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogWhere PSP Distribution Actually Lives→](/blog/where-psp-distribution-actually-lives/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [BlogShuttle and vFairs work together to revolutionise global event management→](/blog/shuttle-and-vfairs-work-together-to-revolutionise-global-event-management/) - [BlogMulti-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know→](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) --- URL: https://www.shuttleglobal.com/guides/goto-payments/ --- # How to Take Payments in GoTo: PCI-Compliant Contact Centre Payments | Shuttle > GoTo Connect is a cloud-based UCaaS platform built for SMB and mid-market businesses, combining business phone, video, and messaging in one place. # How to Take Payments in GoTo: PCI-Compliant Contact Centre Payments By Shuttle Team, May 27, 2026 GoTo Connect is a cloud-based UCaaS platform built for SMB and mid-market businesses, combining business phone, video, and messaging in one place. The GoTo Contact Center add-on extends that into an omnichannel contact centre with voice, SMS, web chat, email, and social channels including Messenger, Instagram, and WhatsApp. It is used by thousands of businesses to manage customer calls, support queues, and agent workflows from a single interface. What GoTo Connect and GoTo Contact Center do not include is native card capture for the contact-centre or voice channel. GoTo has no PCI DSS payment product for agents taking card payments on calls. The only payment integrations in the GoTo ecosystem relate to the separate GoTo Webinar and GoTo Training products, which handle event ticketing. These have nothing to do with contact-centre payments. If a customer calls to pay a bill, top up an account, or place an order, there is no built-in mechanism inside GoTo to capture that card securely. The card capture has to come from somewhere else. This guide is written for two audiences. The first is merchants who run their contact centre on GoTo and want to take PCI-compliant payments over voice or via payment links without rebuilding their infrastructure. The second is system integrators (SIs) who implement GoTo for clients and want to close the payment gap as part of a GoTo deployment. Shuttle is the payment layer that fills that gap, capturing card data in its own certified environment so it never reaches the platform your agents already use. ## The Payment Challenge in GoTo When a customer reads their card number aloud on a GoTo call, or types it into the GoTo chat interface, the card data travels through GoTo's voice stream, potentially into call recordings, and across agent screens. Every system that touches card data is pulled into PCI scope. That includes your telephony platform, your recording solution, your CRM, and your contact centre software. Under PCI DSS, you must demonstrate that each of those systems is secured, audited, and compliant. The cost of building and maintaining that compliance in-house is significant. Initial certification for a Level 1 PCI programme typically runs above $500,000. Ongoing compliance, including annual assessments, penetration testing, vulnerability scanning, and internal resource costs, adds another $200,000 or more per year. That is before accounting for the time your engineering team spends managing scope, responding to audit requests, and keeping controls current as your infrastructure changes. GoTo itself carries strong security credentials: SOC 2 Type II, SOC 3, BSI C5, and HIPAA-ready configurations. However, PCI DSS is not part of its certification set, and it has made no public commitment to providing a PCI-compliant payment capture product for contact centres. The IVR functionality within GoTo Contact Center handles routing and self-service navigation via DTMF tone input, but it does not include a secure payment capture environment. Merchants who need to take card payments in GoTo need a dedicated solution that removes card data from GoTo's environment entirely. ## How Shuttle Adds Payments to GoTo Shuttle adds PCI-compliant card capture to your GoTo payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your GoTo recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for GoTo specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your GoTo call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running GoTo have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent workflow The agent keeps the customer on the GoTo call. When payment is required, the agent triggers a Shuttle session. On a voice call, the customer is prompted to enter their card number, expiry, and CVV using their phone keypad, and the digits are captured inside Shuttle's certified environment via Twilio Pay, so neither the agent's ear nor the recording system picks them up. The agent sees a masked status in real time: a confirmation that capture is in progress and a success or decline notification when the transaction is processed. The agent never sees the card number at any point. ### Customer experience On voice, the customer stays connected to the same agent and is guided through the keypad entry in a few seconds. For digital or follow-up payments, they receive a hosted payment link from Shuttle, tap to open it on their device, and return to the conversation once payment is confirmed. There is no requirement to call back or visit a separate website. The experience is fast and straightforward from the customer's perspective, which matters for first-call resolution rates. ## Multi-PSP Support Shuttle connects to 30+ supported gateways. If you already use Stripe, Adyen, Worldpay, Checkout.com, Braintree, or Square, you do not need to change your acquiring arrangement. Shuttle routes transactions to the gateway you already have in place, and switching later is configuration, not a re-integration. For businesses that operate multiple brands, multiple client accounts, or have inherited mixed payment stacks through growth or acquisition, Shuttle supports per-client routing. Each call or transaction can be directed to a different gateway based on business logic you define. This is particularly useful for BPOs and managed service providers who run contact centre operations for more than one client and need to keep payment flows separated. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, which is the highest level of certification available. Card data is captured inside Shuttle's environment and does not enter GoTo at any point. This means the card capture process is out of scope for your GoTo platform, your call recordings, and your agents' workstations. Because Shuttle removes card data from your environment, businesses that previously faced a SAQ-D assessment (the most extensive self-assessment questionnaire, covering systems that store, process, or transmit cardholder data) can work toward SAQ-A compliance instead. SAQ-A applies when card data handling is fully outsourced to a PCI-compliant provider. Reducing your assessment scope cuts the compliance burden significantly for your internal team and your external assessors. ## Beyond Voice: Payment Links Payment links are the most turnkey path, and they do not require Twilio. Shuttle generates a hosted payment link and sends it via SMS or email, including mid-call to a customer who is still on the line. The link opens a Shuttle-hosted checkout page where the customer completes payment securely, and the payment status is returned to the agent as soon as the transaction is processed. Shuttle provides the link interfaces out of the box. This is useful for follow-up billing after a call, payment requests sent over SMS for field service or delivery scenarios, and collections workflows where a link is sent after an initial conversation. Links also work with gateways that do not support voice capture, all routing through the same 40+ gateway network. ## For Solution Providers and GoTo Implementation Partners SIs who implement GoTo Contact Center for clients frequently encounter the payment gap during discovery. Clients running call centres for billing, collections, order taking, or account management need a compliant way to take card payments, and GoTo does not provide one out of the box. This is a solvable problem that can be scoped into a GoTo delivery and presented as part of a complete contact centre solution. Shuttle's voice capture runs on Twilio Pay, so the client needs to be a Twilio customer, and the agent-side interface is built against Shuttle's APIs as part of your delivery. There is no pre-built GoTo widget today, though we can build a native GoTo integration as a paid project for a specific deployment. Clients retain their existing acquirer or choose from 30+ gateways. Voice payments are $0.20 per successful transaction with no setup fees and no per-seat charges, which is easy to include in a project cost model and simple to explain to clients. Links Checkout is a separate app; see [pricing](/pricing/). You can build a proof of concept against Shuttle's sandbox gateway and demo app before deploying for a client. ## Use Cases ### Bill-Pay and Collections Utilities, telecoms, financial services, and debt collection businesses that use GoTo to handle inbound and outbound payment calls. Shuttle enables agents to take card or direct debit payments on the call without putting the contact centre into PCI scope. ### Order Taking and E-commerce Support Retail and e-commerce businesses that take orders by phone or chat and need to process card payments at the point of conversation. Shuttle captures the card during the GoTo interaction and routes to the merchant's existing gateway. ### Account Payments SaaS, insurance, and subscription businesses that handle account top-ups, premium renewals, and invoice payments through their GoTo contact centre. Agents can accept payment mid-call without transferring the customer or asking them to pay online separately. ### Bookings and Deposits Service businesses that take deposits or full payments at the point of booking, including hospitality, healthcare, and professional services. Shuttle handles the card capture while the agent manages the booking inside GoTo. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged GoTo plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for GoTo specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your GoTo call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running GoTo have already done it. - A native GoTo integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does GoTo process payments natively? GoTo Connect and GoTo Contact Center do not include a native contact-centre payment product. The only GoTo payment integrations in the marketplace relate to GoTo Webinar and GoTo Training for event ticketing, which are separate products. There is no built-in card capture for agents handling payment calls. Does Shuttle have a native GoTo integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in GoTo. For voice you'll need to be a Twilio customer and to build the agent-side trigger for your workflow against Shuttle's APIs. Payment links require no Twilio relationship. We can build a native GoTo integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? For voice capture, yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. How do I take PCI-compliant payments in GoTo? Agents trigger a Shuttle session from within their GoTo workflow. On voice, Shuttle captures the card in a secure Twilio Pay call; for digital or follow-up payments, it sends a hosted link via SMS or email. Card data is captured inside a PCI Level 1 environment that is fully separate from GoTo's infrastructure. Which gateways does Shuttle support? Shuttle supports 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You can keep your existing acquirer and use per-client routing to direct transactions to different gateways based on business rules. Switching is configuration, not a re-integration. Can't I just build payment capture into GoTo myself? Building and maintaining your own PCI-compliant payment capture environment typically costs more than $500,000 to set up and over $200,000 per year to sustain. You also bear the ongoing risk of audit failures, data breach liability, and the engineering overhead of keeping controls current. Using Shuttle removes card data from your environment and from your compliance scope. Can Shuttle handle outbound payment collection in GoTo? Yes. For outbound collections, agents can trigger a secure Twilio Pay capture during the outbound call or send a hosted payment link via SMS or email. Shuttle supports both inbound and outbound contact-centre payment scenarios. ## Related Reading - Contact centre payments: an overview of PCI-compliant payment capture across contact centre channels - Embedded payments for CCaaS: how the embedded payment layer model works for contact centre software - AI voice agent PCI payments: PCI compliance for automated voice agents handling payment capture - Payment collection for BPOs: multi-client payment collection for outsourced contact centre operations - Payments for CCaaS implementation partners: how SIs can close the payment gap in CCaaS deployments ## Take Payments in Your GoTo Contact Centre Shuttle adds PCI-compliant card capture to a GoTo-based operation, via Twilio for voice and via payment links over SMS or email, without bringing your contact centre into PCI scope. We'll walk you through what's live today and the path for your setup. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI scope](/glossary/pci-scope/) - [PCI DSS](/glossary/pci-dss/) - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [30+ supported gateways](/payment-providers/) - [40+ gateway](/payment-providers/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [30+ payment gateways](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI voice agent PCI payments](/guides/ai-voice-agent-pci-payments/) - [Payment collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/gupshup-payments/ --- # Gupshup Payments: UPI and WhatsApp Pay vs Multi-PSP Card Capture | Shuttle > Gupshup is one of the world's leading conversational messaging platforms. It powers WhatsApp-first commerce and customer engagement across India and... # Gupshup Payments: UPI and WhatsApp Pay vs Multi-PSP Card Capture By Shuttle Team, June 1, 2026 Gupshup is one of the world's leading conversational messaging platforms. It powers WhatsApp-first commerce and customer engagement across India and emerging markets, serving brands in BFSI, retail, healthcare, and utilities. As a Meta Business Solution Provider (BSP), Gupshup gives businesses a direct route to WhatsApp Business API, as well as reach across SMS, Instagram, RCS, and voice channels. Its ISV Partner Program extends that reach through solution providers and system integrators building on top of the platform. What sets Gupshup apart from most conversational platforms is that it has a genuine native payment capability. It is not a messaging tool that simply redirects users to a payment page. Gupshup has built UPI-native bill pay, WhatsApp Pay integration via Meta-approved processors, and in-chat conversational commerce directly into its messaging stack. For India-first deployments, that is a significant head start. This guide covers what Gupshup's native payments give you and, importantly, when you need to extend beyond them. Specifically: when you are handling international card payments, managing multiple clients each with their own acquirer, running voice-channel collections alongside messaging, or operating in markets where UPI does not reach. If you are building or operating a platform that combines Gupshup's conversational reach with card payments, multi-currency support, or voice capture, this guide explains where the two approaches complement each other. ## Gupshup's Native Payments: What You Get Gupshup's native payment capabilities are real and well-integrated into its messaging channels. They are purpose-built for India's payment infrastructure: - 1-Click Bill Pay: UPI payment links sent directly inside WhatsApp, SMS, Instagram, and RCS messages. Customers tap once and pay via UPI without leaving the conversation. Designed for bill-pay, renewals, and collections workflows in India. - WhatsApp Pay via Razorpay and PayU: In-chat WhatsApp Pay flows powered by Razorpay and PayU, which are the only Meta-approved processors for India. Card payments can also be handled through these processors within the WhatsApp interface. - GSPay: UPI-based payments for feature phone users via USSD and SMS flows, extending reach to customers without smartphones or reliable data connectivity. - Conversational commerce: In-chat product catalogues, cart flows, and payment collection for retail and D2C brands operating on WhatsApp. For India-first messaging commerce, this is a genuinely strong native stack. If your business is collecting payments from Indian consumers via WhatsApp or SMS, Gupshup's native payments may cover the majority of your volume. ## When You Need a Multi-PSP Card Layer Gupshup's native payments are optimised for UPI and WhatsApp Pay in India. There are specific scenarios where a dedicated multi-PSP layer alongside Gupshup is the practical answer: - International card payments and multi-currency: UPI is India-specific. If you are collecting from customers in Europe, the US, Southeast Asia, or the Middle East, you need international card rails with multi-currency support. Gupshup's native stack does not provide this. - Bring-your-own-gateway and negotiated acquirer rates: Larger platforms and enterprises often have existing acquirer relationships and negotiated interchange rates. A multi-PSP layer lets you route to those preferred gateways rather than being tied to a fixed processor. - Per-client and per-tenant gateway routing: Agencies and platforms managing payments on behalf of multiple clients need to route each transaction to the correct merchant account. UPI flows do not support this kind of multi-tenant configuration. - Voice-channel card capture: Some collections and customer-service workflows require card capture over a phone call, with PCI scope handled by the payment layer rather than your contact centre. Gupshup's native payments do not cover voice card capture. - One integration across markets and channels: Platforms operating in India and internationally benefit from a single payment integration that handles both, rather than separate stacks per region. ## How Shuttle Works with Gupshup Today Shuttle has no native integration with Gupshup. Because Gupshup is messaging-led, payment links are the most relevant path: Shuttle generates hosted, PCI-compliant payment links that the Gupshup flow can deliver over SMS, email, or any messaging channel, including mid-conversation. For voice card capture, you invoke Shuttle's Twilio-based setup, and you must be a Twilio customer for that path. - The agent or messaging flow runs inside Gupshup: conversation, fulfilment, intent capture. - At the payment moment, your application triggers Shuttle via API or generates a hosted payment link. - Shuttle captures card details in isolation, via a hosted checkout page (links) or, on voice channels, via a secure PCI DSS Level 1 capture handed off via Twilio Pay. Card data does not enter Gupshup's environment or yours. - Shuttle routes the transaction to whichever of your 30+ gateways applies, based on currency, region, or client configuration. - The result returns to your system for fulfilment, confirmation, or CRM update. The Gupshup-side conversational experience is unchanged. You build the orchestration and agent-side wiring yourself; Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app. Honest caveat: for voice, secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same flow after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. A native Gupshup integration is possible only as a paid project. ## Multi-PSP Support Shuttle connects to 30+ payment gateways through a single integration. That list includes Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie, among others. Key capabilities: - Per-tenant gateway configuration: Each client or merchant on your platform can be mapped to their own acquirer relationship. - Routing by currency and region: Transactions are routed to the gateway best suited to the currency, card scheme, or geography of the payment. - Redundancy: If a gateway is unavailable, you can move the affected payment types to another connected gateway. - Switching is configuration, not re-integration. A few gateways (for example, Braintree) do not work for voice capture but do work for payment links. This is what makes international and multi-client operations practical beyond UPI. You are not limited to the processors Gupshup has partnerships with, and you are not rebuilding integrations per market. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, the highest tier of PCI certification. For card payments, cardholder data flows through Shuttle's certified environment, keeping your compliance scope on a lighter SAQ-A footing rather than SAQ-D. UPI payments do not carry card PANs. A UPI transaction is an account-to-account transfer initiated by a VPA (Virtual Payment Address), so PCI DSS does not apply to that flow. If Gupshup's native UPI payments are your primary collection method for Indian customers, PCI scope is not a concern for those transactions. Where PCI scope does matter is card payments and voice capture. If your platform handles international credit or debit cards, or captures card details over a phone call, you need a certified environment for that data. That is Shuttle's role in the stack. ## Beyond Messaging: Payment Links and Voice Gupshup's native UPI flows are channel-specific: they work inside WhatsApp, SMS, Instagram, and RCS. Shuttle adds two additional capture channels that Gupshup's native payments do not cover. Hosted card payment links: Payment links are the turnkey path, and they work even with gateways that do not support voice capture. Shuttle generates hosted payment pages that can be sent via any channel, over SMS or email, including mid-conversation. The link opens a PCI-compliant checkout outside your environment. This is useful for email, SMS, or messaging flows where the recipient is outside India or using an international card. Links Checkout is a separate app; see [pricing](/pricing/). Secure voice card capture: For contact centres and IVR deployments, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay (you must be a Twilio customer for this path). The caller enters card digits on the keypad, and they never reach the agent, the recording, or your systems. This is the standard approach for PCI-compliant card capture over voice. Both channels work alongside Gupshup's conversational flows rather than replacing them. ## Use Cases ### Cross-Border and International Card Payments A utility or BFSI brand using Gupshup for India-based collections wants to extend payment collection to international customers or diaspora payers. UPI does not reach them. Shuttle provides international card rails across 30+ gateways with multi-currency support, using the same API and reporting layer as the India stack. ### Multi-Client Platforms and Agencies A CPaaS reseller or messaging integrator manages Gupshup deployments for multiple enterprise clients, each with their own acquirer. Shuttle's per-tenant gateway routing maps each client to their own merchant account, so collections stay correctly attributed without a separate payment integration per client. ### Bill-Pay Beyond UPI A collections or utilities platform handles UPI bill pay via Gupshup's 1-Click Bill Pay for Indian consumers. For customers paying by card, or customers in markets without UPI, Shuttle generates a hosted payment link that captures card details in a PCI-certified environment and routes to the appropriate gateway. ### Voice and Card-Not-Present A financial services or debt collections operation runs Gupshup-powered outbound messaging for payment reminders, then handles inbound calls for customers who want to pay by card. Shuttle's secure Twilio Pay capture handles the call-centre leg, keeping card digits out of the agent environment, while Gupshup continues to own the messaging channel. ## FAQ Does Gupshup process payments natively? Yes. Gupshup has native payment capabilities including 1-Click Bill Pay (UPI payment links across WhatsApp, SMS, Instagram, and RCS), WhatsApp Pay via Razorpay and PayU (Meta's approved India processors), GSPay for feature phones, and in-chat conversational commerce. These are well-integrated into its messaging stack and cover Indian UPI-based payment flows. Does Shuttle have a native Gupshup integration? No. Shuttle has no native Gupshup integration. Payment links are the most relevant path for a messaging-led platform, and your application generates them or triggers Shuttle via API. For voice capture you invoke Shuttle's Twilio-based setup. A native Gupshup integration is possible only as a paid project. Does this require Twilio? For payment links, no. For the voice card capture path, yes: the secure capture runs via Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Why use Shuttle if Gupshup has native payments? Gupshup's native payments are optimised for India and UPI. If you need international card payments, multi-currency support, per-client gateway routing, payment links across markets, or voice card capture, those are not part of Gupshup's native stack. Shuttle extends the stack to cover those channels without replacing the UPI flows Gupshup handles well. Which gateways does Shuttle support? Shuttle connects to 30+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie. Transactions can be routed per currency, region, or client configuration. See the full list on the payment providers page. A few gateways (for example, Braintree) do not work for voice but do work for payment links. Does Shuttle support international card payments and multi-currency? Yes. Shuttle routes card transactions to whichever gateway is configured for the relevant currency and region. You can run a single integration that handles Indian UPI flows via Gupshup's native stack and international card payments via Shuttle, without separate payment systems per market. ## Related Reading - The Payment Layer for AI Agents: how a dedicated payment layer sits between conversational AI and card capture. - Voice Payments: guide to PCI-compliant card capture across voice channels. - AI Voice Agent PCI Payments: secure capture, PCI scope reduction, and voice agent architecture. - Payment Orchestration: how multi-PSP routing, failover, and per-tenant configuration work in practice. - Yellow.ai Payments: a similar native-vs-multi-PSP comparison for another conversational AI platform strong in emerging markets. ## Add Multi-PSP Payments Alongside Gupshup Shuttle is a PCI DSS Level 1 Service Provider offering card capture across 30+ gateways, via payment links and a secure Twilio Pay handoff for voice. Pricing is $0.20 per successful transaction with no setup or per-seat fees (see pricing). Read the Twilio setup docs, the payment links docs, and the security overview. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [PCI DSS](/glossary/pci-dss/) - [payment providers page](/payment-providers/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Payment Orchestration](/guides/what-is-payment-orchestration/) - [Yellow.ai Payments](/guides/yellow-ai-payments/) - [see pricing](/pricing/) - [Twilio setup docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links docs](https://docs.shuttleglobal.com/docs/links-intro) - [security overview](https://docs.shuttleglobal.com/docs/org-security) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/how-ccaas-platforms-add-payments/ --- # How CCaaS Platforms Add Payment Capabilities Without Building In-House | Shuttle > The CCaaS Payment Opportunity Contact centre platforms handle billions of customer interactions each year. # How CCaaS Platforms Add Payment Capabilities Without Building In-House By Shuttle Team, December 30, 2025 ## The CCaaS Payment Opportunity Contact centre platforms handle billions of customer interactions each year. A significant share of those interactions involve money changing hands: bill payments, insurance premiums, debt collections, subscription renewals, order payments, travel bookings. Yet most CCaaS platforms don't have native payment capabilities. Their enterprise customers are asking for it. A utility company running collections through a CCaaS platform wants agents to capture payments on the call. An insurance carrier wants IVR self-service renewals. A retailer wants AI agents that close sales and take payment in one conversation. These aren't edge cases. They are recurring, high-volume use cases that happen across every vertical a CCaaS platform serves. The platform that adds payment capture creates two things: a new revenue stream (payments become a billable feature) and massive customer stickiness (platforms that handle payments are hard to leave). The platform that doesn't add payments watches its enterprise customers solve the problem with bolt-on vendors, fragmented workflows, and eventual migration to a competitor that got there first. The opportunity is not theoretical. Twilio identified it early. Five9, Talkdesk, and Genesys all have enterprise customers requesting it. The question for every CCaaS platform is not whether to add payments but how to add them without derailing the core product roadmap. ## Why CCaaS Platforms Struggle with Payments Payments are not a CCaaS platform's core competency. Building payment infrastructure from scratch is a fundamentally different engineering discipline, and it comes with compliance obligations that most CX-focused teams are not equipped to manage. ### PCI DSS Compliance Is Complex for Voice Channels PCI DSS (Payment Card Industry Data Security Standard) applies to every system that stores, processes, or transmits cardholder data. In a voice environment, that means the telephony stack, call recording, agent workstations, and the network carrying the audio. If a customer reads a card number to an agent, the entire call path is in PCI scope. Achieving PCI DSS Level 1 certification for a voice environment costs upwards of $2M and takes 12+ months. Maintaining it is an ongoing operational burden that competes directly with product development resources. ### Enterprise Customers Bring Their Own PSPs This is the problem that breaks most in-house payment builds. Enterprise contact centres don't use one payment service provider. A US-based insurer might mandate Worldpay. A European retailer requires Adyen. A debt collection agency uses a regional acquirer. If the CCaaS platform builds a Stripe integration, it works for customers that use Stripe. The moment an enterprise deal requires a different PSP, the platform faces a choice: build another integration (weeks to months per PSP) or lose the deal. Multi-PSP support through a single integration is a prerequisite for enterprise CCaaS payments. Most platforms don't realise this until they've already shipped a single-PSP solution and hit the wall. ### The Build Diverts From Core CX Even if a CCaaS platform has the engineering resources, building DTMF capture, tone suppression, card tokenisation, multi-PSP routing, agent payment UI, and transaction reporting is a 12-month project at minimum. That is a year of engineering time not spent on the platform's core CX capabilities -- call routing, workforce management, analytics, AI features. Payment infrastructure is a deep rabbit hole. Once you start, it doesn't stop. There are gateway-specific quirks, 3D Secure flows, refund handling, settlement reconciliation, regional compliance variations, and ongoing PCI re-certification. Payments become a permanent roadmap tax. ## What Enterprise Customers Actually Need When enterprise contact centres evaluate a CCaaS platform's payment capabilities, they have a specific set of non-negotiable requirements. PCI-compliant voice payment capture. DTMF-based card entry with tone suppression, so the agent stays on the call but never hears, sees, or accesses card data. This is the baseline. Pause-and-resume (where the agent manually stops recording) doesn't pass enterprise security reviews. Support for their mandated PSP. Enterprise customers have existing PSP relationships. They are not switching to Stripe because the CCaaS platform only supports Stripe. The platform needs to route transactions to whichever PSP the customer uses -- Worldpay, Adyen, Checkout.com, Braintree, or a regional acquirer. Agent-assisted payment UI. Agents need to see real-time payment status during a call: whether the customer is entering digits, whether validation passed, whether the transaction was approved or declined. This needs to sit within the agent desktop, not in a separate window or system. Payment links for post-call collection. Not every payment completes on the call. The customer may not have their card, the call may drop, or the agent may need to follow up. Sending a branded payment link via SMS or email -- while the conversation is still warm -- recovers revenue that would otherwise be lost. Real-time transaction reporting. Enterprise customers need a dashboard showing transaction volume, success rates, refund activity, and settlement status. For CCaaS platforms serving multiple enterprise clients, this needs to be segmented per customer. Compliance documentation for their own audits. Enterprise customers undergo their own PCI, SOC 2, and ISO audits. They need the CCaaS platform to provide certificates and attestation documents proving that payment capture is handled within a certified environment. If the platform can't provide these, the deal stalls in procurement. ## The Twilio Model: How It Already Works Twilio is the infrastructure layer underneath many CCaaS platforms. Talkdesk, Five9 Flex, and dozens of purpose-built contact centre solutions run on Twilio's programmable voice APIs. Shuttle provides the payment capture layer within Twilio-powered voice flows. It's available on the Twilio Marketplace and already in production with enterprise customers across insurance, AI voice, and collections. Here is how the model works: - Twilio handles voice. The call is running on Twilio's infrastructure -- routing, recording, agent connection, IVR logic. - Shuttle handles payment capture. When a payment is triggered (by an agent, an IVR flow, or an AI voice agent), Shuttle creates a secure payment session within the active call. - DTMF tones are intercepted. The customer enters their card number via keypad. Shuttle captures the tones within its PCI DSS Level 1 environment. The tones are stripped from the audio stream -- the agent hears masking tones, not digits. - Card data is tokenised. Shuttle tokenises the card data. No card numbers touch the CCaaS platform, the telephony stack, or the call recording. - Transaction is routed to the enterprise customer's PSP. Shuttle routes the payment to whichever PSP the end customer uses -- Worldpay, Adyen, Stripe, or any of 40+ supported providers. The CCaaS platform doesn't need to integrate with each one. - Result is returned. The transaction result (approved, declined, 3DS required) is returned to the CCaaS platform via webhook and displayed to the agent in real time. The CCaaS platform's role is simply to enable it. No card data enters their stack. Limited PCI scope. No PSP integrations to build or maintain. This is not hypothetical. PolyAI -- an AI voice platform -- uses this exact model in production. Their AI agents handle high-value transactions across regulated industries, routing payments through their enterprise customers' mandated PSPs, with limited PCI scope on PolyAI's side. ## Three Ways to Add Payments to a CCaaS Platform ### Option 1: Build Proprietary Payment Infrastructure Build DTMF capture, tone suppression, tokenisation, PSP integrations, agent UI, and reporting from scratch. Timeline: 12-18 months to first production transaction. Ongoing maintenance indefinitely. Cost: $2M+ for PCI DSS Level 1 certification alone. Plus engineering headcount, ongoing re-certification, and per-PSP integration maintenance. Upside: Full control over the payment experience. Downside: Massive resource diversion from core CX product. PCI compliance becomes a permanent operational burden. Every new PSP requires a new integration build. Every compliance change requires engineering response. Best for: Platforms with dedicated payments teams and a strategic decision to make payments a core product pillar. Very few CCaaS platforms fit this profile. ### Option 2: Partner with a Single PSP Integrate directly with Stripe, Adyen, or another PSP. Offer payments through that one provider. Timeline: 3-6 months to production. Cost: Lower than building from scratch, but PCI scope still exists for voice channels unless the PSP handles DTMF suppression (most don't). Upside: Faster than building from zero. Known brand name. Downside: Lock-in. Enterprise customers that use a different PSP cannot use the payment feature. The CCaaS platform becomes a distribution channel for that one PSP -- not a flexible payments platform. Best for: Platforms with a homogeneous customer base that all use the same PSP. This is rare at enterprise scale. ### Option 3: Embed a Payment Layer Integrate a PSP-neutral payment layer that handles PCI compliance, DTMF capture, tokenisation, and multi-PSP routing. The CCaaS platform enables payments through a single integration. Enterprise customers connect their own PSP. Timeline: Weeks, not months. Pre-built connectors for Twilio and SIP-based telephony. Cost: Usage-based. No PCI certification to fund. No per-PSP integration cost. Upside: Full PSP flexibility. Multi-channel (voice, IVR, SMS payment links, AI agents). Limited PCI scope. White-label -- the enterprise customer sees the CCaaS platform's brand, not the payment layer underneath. Downside: Dependency on a third-party payment partner. Mitigated by the PSP-neutral architecture -- the platform isn't locked to any single provider. Best for: CCaaS platforms that need enterprise-grade payment capabilities without diverting core engineering resources. ## The Revenue Opportunity Adding payment capabilities isn't just a feature checkbox. It's a revenue driver with multiple layers. Payments as a billable feature. Payment capture becomes a paid add-on -- charged per transaction, per seat, or as a premium tier. Platforms that embed payments through a revenue-share model generate recurring income on transaction volume without managing any payment infrastructure. Higher contract values. Enterprise deals that include payment capabilities command higher annual contract values. A CCaaS platform that solves voice payments alongside call routing and agent management captures more budget from the same buyer. Reduced churn. Payments create deep integration. When an enterprise customer's agents, IVR flows, and AI bots all capture payments through the CCaaS platform, switching costs increase significantly. Payment data, merchant configurations, and PSP connections don't migrate easily. Competitive differentiation. In RFPs against Five9, Talkdesk, Genesys, or niche CCaaS platforms, native payment capabilities are a differentiator. Most CCaaS platforms punt on payments. The one that solves it wins the deal -- especially in verticals like insurance, utilities, collections, and financial services where phone payments are high-volume. Expansion revenue. Once voice payments are live, the same payment layer enables SMS payment links, chat payments, and AI agent payment capture. Each new channel is expansion revenue without a new integration. ## Technical Architecture: How Payment Capture Works The architecture is straightforward. No card data touches the CCaaS platform at any point. ### Voice Payment Flow (Agent-Assisted or IVR) - Payment triggered. An agent clicks "take payment" in their desktop, or an IVR flow reaches a payment node. - Secure session created. The CCaaS platform calls Shuttle's API to initiate a payment session for the active call. Parameters include amount, currency, and the merchant's PSP configuration. - Audio routed through PCI environment. The call's media stream is routed through Shuttle's PCI DSS Level 1 environment. The agent remains connected. The customer hears a prompt to enter card details via keypad. - DTMF captured and suppressed. Keypad tones are intercepted by Shuttle. The agent hears masking tones -- silence, flat tones, or hold music. No card data enters the CCaaS audio path. - Card data tokenised. Shuttle validates the card number (Luhn check, BIN lookup), tokenises it, and prepares the transaction. - Transaction routed to PSP. Shuttle sends the transaction to the enterprise customer's configured PSP -- Worldpay, Stripe, Adyen, or any supported provider. 3D Secure is handled if required. - Result returned via webhook. Approved, declined, or requires further authentication. The CCaaS platform displays the result to the agent. A transaction ID is logged for reconciliation. ### What Never Touches the CCaaS Platform - Raw card numbers - DTMF tones containing card data - Any data that would put the platform in PCI scope The CCaaS platform receives only: transaction status, last four digits (masked), transaction ID, and a token. This keeps the platform at PCI SAQ-A -- the lightest compliance level. ### SMS Payment Link Fallback If DTMF capture fails (customer on a VoIP phone without a keypad, or in a noisy environment), the agent triggers an SMS payment link. The customer receives a branded checkout page on their device, completes payment (card, Apple Pay, Google Pay, or bank transfer), and the agent sees confirmation in real time. Same architecture -- no card data in your systems. ## Conclusion CCaaS platforms sit on top of the interactions where payments happen. Collections calls, insurance renewals, order confirmations, subscription payments -- these are live conversations that should end with a completed transaction. The platforms that add payment capabilities capture more revenue per customer, win more enterprise deals, and build switching costs that reduce churn. The platforms that don't add payments leave that value for bolt-on vendors and competitors to capture. Building payment infrastructure in-house is a 12+ month, multi-million-dollar commitment that diverts engineering from core CX product development. Partnering with a single PSP creates lock-in that breaks at enterprise scale. Embedding a PSP-neutral payment layer -- one that handles PCI compliance, DTMF capture, multi-PSP routing, and white-label branding -- gets payments live in weeks without touching the product roadmap. Shuttle is the payment layer underneath Twilio-powered voice flows and CCaaS platforms. 40+ PSP integrations. PCI DSS Level 1. Voice, IVR, SMS payment links, and AI agent support. White-label. Live in weeks. If your CCaaS platform is evaluating payment capabilities, talk to us. We'll show you how platforms like PolyAI and others in the Twilio ecosystem are already capturing payments in production -- without building a single PSP integration. [Book a Call] | [See How It Works] ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Adyen for Platforms Alternatives ### Can You Take Card Payments on a Retell AI Voice Agent? ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [DTMF capture](/guides/dtmf-payments/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) --- URL: https://www.shuttleglobal.com/guides/how-psps-get-distribution-into-software/ --- # How PSPs Get Distribution Into Enterprise Software | Shuttle > PSPs Don't Lose to Other PSPs. They Lose to Software. The traditional PSP competitive landscape looks like this: Stripe vs Adyen vs Worldpay vs... # How PSPs Get Distribution Into Enterprise Software By Shuttle Team, February 20, 2026 ## PSPs Don't Lose to Other PSPs. They Lose to Software. The traditional PSP competitive landscape looks like this: Stripe vs Adyen vs Worldpay vs Checkout.com. Product features, pricing, geographic coverage, developer experience. But that's not where PSPs are actually losing deals. PSPs lose deals when a software platform -- an ERP, a contact centre, a booking engine, an insurance platform -- embeds a competitor's gateway as the default. The merchant never evaluates PSPs directly. They use whatever their software provides. The shift: Payment decisions are moving from merchants to software platforms. The platform picks the PSP. The merchant follows. This isn't a future trend. It's happening now: - Shopify routes the majority of its merchants through Shopify Payments (powered by Stripe) - Toast processes restaurant payments through its own stack - ServiceTitan embeds payments into field service workflows - INSTANDA embeds payments into insurance platform workflows In every case, the PSP that's embedded in the software wins the volume. The PSPs that aren't embedded don't even get evaluated. ## The Distribution Problem Every major PSP recognises this shift. Their strategy decks include "platform partnerships" and "ISV distribution" as growth priorities. But execution is hard: ### 1. Custom Integrations Don't Scale A PSP that wants to be embedded in 50 software platforms needs 50 custom integrations. Each platform has its own API design, onboarding flow, compliance requirements, and settlement process. Building and maintaining these integrations is expensive and slow. Most PSPs can resource 3-5 direct platform integrations per year. The platforms that don't make the cut get a generic API and a "figure it out yourself" developer portal. ### 2. Platforms Want PSP Choice, Not PSP Lock-In Enterprise software platforms increasingly resist single-PSP lock-in. Their customers demand specific PSPs based on geography, existing contracts, and compliance requirements. A platform that embeds only Worldpay loses deals where the merchant requires Adyen. A platform that embeds only Stripe can't serve enterprise customers with mandated regional acquirers. The platforms that win enterprise deals offer PSP flexibility. That means supporting multiple PSPs -- which is the opposite of what any individual PSP wants. ### 3. New Payment Channels Need New Infrastructure Platforms are expanding beyond online checkout into voice payments, payment links, AI agent payments, and pay-by-bank. Each channel needs payment infrastructure. Most PSPs cover checkout and mobile well. Few cover voice. Fewer cover AI agent payments. None cover all channels through a single integration. For PSPs, this creates a gap: even if you're embedded in a platform's checkout flow, you might not be embedded in their voice, links, or AI agent channels. ## The Distribution Layer Model Instead of building custom integrations with every platform, PSPs can get distribution through a payment layer that's already embedded in those platforms. How it works for the PSP: - The payment layer integrates with software platforms. One integration per platform, maintained by the payment layer provider. - The PSP integrates with the payment layer. One integration that gives the PSP access to every platform connected to the layer. - When a merchant on any platform chooses (or is configured for) that PSP, transactions route automatically. No additional integration work for the PSP or the platform. - New channels (voice, links, AI) are handled by the payment layer. The PSP receives transactions through those channels without building channel-specific infrastructure. The maths: Instead of building 50 platform integrations, the PSP builds 1 integration with the payment layer and reaches 50 platforms. Each new platform the payment layer onboards is additional distribution for every connected PSP. ## What PSPs Gain Through a Distribution Layer ### 1. Access to Platform-Embedded Volume Every platform connected to the payment layer is a potential distribution channel. When a merchant on that platform selects your gateway -- either by choice, by mandate, or because your rates are best for their region -- transactions flow to you automatically. This is volume you'd never see through direct merchant acquisition, because the merchant's payment decision was made at the platform level. ### 2. Enterprise PSP Mandate Capture Enterprise merchants frequently mandate their PSP. "We use Worldpay. Whatever software we adopt needs to process through Worldpay." Through a distribution layer, these mandates become automatic routing. The platform configures the merchant's required PSP, and transactions route there. For PSPs with strong enterprise relationships, this turns mandates into embedded volume. ### 3. Multi-Channel Reach The payment layer handles voice, links, chat, and AI agent channels. Transactions from these channels route to the configured PSP -- giving the PSP volume from payment surfaces they don't support directly. A PSP that doesn't have voice payment infrastructure still receives voice-originated transactions through the payment layer. The same applies to AI agent payments, payment links, and any new channel the payment layer supports. ### 4. Reduced Integration Burden Every platform integration a PSP builds directly requires ongoing maintenance -- API updates, compliance changes, testing, support. Through a distribution layer, the PSP maintains one integration. The payment layer handles the platform-facing complexity. ## The Strategic Question for PSPs PSPs that embed directly in platforms gain deeper control and typically higher margins. PSPs that distribute through a payment layer gain broader reach with lower integration cost. The optimal strategy depends on scale: Direct Integration Distribution Layer Top 5 global (Stripe, Adyen, Worldpay, Checkout.com, PayPal) Can resource direct integrations with top 20-30 platforms Still can't resource the long tail of 1,000+ niche platforms Mid-tier (Mollie, GoCardless, Square, regional acquirers) Can resource 5-10 direct integrations per year Distribution layer extends reach to platforms they can't resource directly Regional / niche (local acquirers, specialist processors) Struggle to get any platform integrations Distribution layer is the only viable path to platform-embedded volume For most PSPs, the answer is both: direct integrations with the highest-value platforms, plus distribution layer coverage for everything else. ## Why This Matters Now ### 1. Platform Payments Volume Is Growing Exponentially Embedded finance is projected to reach $7.2 trillion by 2030. An increasing share of total payment volume flows through software platforms rather than direct merchant relationships. PSPs that aren't embedded in platforms will see their addressable market shrink -- not because they're losing merchants, but because merchants are making fewer direct PSP decisions. ### 2. AI Agents Are Creating New Payment Surfaces AI voice agents and chat agents are processing payments in production. These are entirely new payment channels -- they didn't exist two years ago. PSPs that don't have infrastructure for AI agent payments can still capture this volume through a payment layer that does. ### 3. Geographic Expansion Requires Local Rails Platforms expanding internationally need PSPs with local acquiring in each market. No single PSP covers every geography competitively. The platforms that support merchant-chosen PSPs (via a payment layer) give regional acquirers access to volume they'd never see through direct sales. ## FAQ Does using a distribution layer mean the PSP loses its merchant relationship? No. The PSP still has a direct contractual and financial relationship with the merchant. The payment layer handles transaction routing and multi-channel support, but the PSP relationship (rates, settlement, support) remains direct. What about PSPs that want to own the full stack? Some PSPs (notably Stripe and Adyen) are building vertically -- owning the platform solution end-to-end. This works for merchants happy to standardise on that PSP. It doesn't work for enterprise merchants who mandate a different PSP or platforms that need PSP flexibility. Both models will coexist. How does pricing work for the PSP? The PSP charges its standard processing fees. The payment layer charges separately (to the platform). The PSP doesn't subsidise the payment layer -- it gains distribution that would otherwise require direct platform integration. Can a PSP be on both sides -- embedded directly AND in the distribution layer? Yes. Most large PSPs will have direct integrations with their top platform partners and use distribution layers for broader reach. These aren't mutually exclusive. ## Related Reading - How Platforms Monetise Payments Without PSP Lock-In -- the platform-side view of embedded payment revenue - When Your SaaS Outgrows Stripe Connect -- why platforms are moving to multi-PSP architecture - Agentic Payments in 2026: The Infrastructure Guide -- AI agents are creating new payment surfaces PSPs need to reach - Shuttle vs Adyen for Platforms -- why even Adyen can't serve all merchants across all geographies - What is a PSP? | What is PSP-Neutral? | What are Embedded Payments? PSP looking for platform distribution? Shuttle connects PSPs to enterprise software platforms across checkout, voice, links, and AI agent channels. One integration. Access to every platform in the network. Partner With Us | See the Network ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Buying Moved Into the Conversation. The Checkout Didn't Follow. ### Where PSP Distribution Actually Lives ### Uncovering the Limitations of Spreedly for Software Platforms ### The Power of Payment Links: Enhancing Financial Management in Practice Management Software ### PCI DSS v4 Implications for Service Provider (software vendors) ### Invoicing Software for SMEs: 6 Best Tools in 2026 ## Links - [single-PSP lock-in](/guides/when-saas-outgrows-stripe-connect/) - [AI voice agents and chat agents are processing payments in production](/blog/agentic-payments-infrastructure-2026/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Agentic Payments in 2026: The Infrastructure Guide](/blog/agentic-payments-infrastructure-2026/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [PSP](/glossary/psp/) - [PSP-Neutral](/glossary/psp-neutral/) - [Embedded Payments](/glossary/embedded-payments/) - [Partner With Us](/discovery/) - [See the Network](/payment-providers/) - [Book a Call](/discovery/) - [BlogBuying Moved Into the Conversation. The Checkout Didn't Follow.→](/blog/buying-moved-into-the-conversation/) - [BlogWhere PSP Distribution Actually Lives→](/blog/where-psp-distribution-actually-lives/) - [BlogUncovering the Limitations of Spreedly for Software Platforms→](/blog/uncovering-the-limitations-of-spreedly-for-software-platforms-2/) - [BlogThe Power of Payment Links: Enhancing Financial Management in Practice Management Software→](/blog/the-power-of-payment-links-enhancing-financial-management-in-practice-management-software/) - [BlogPCI DSS v4 Implications for Service Provider (software vendors)→](/blog/pci-dss-v4-implications-for-service-provider-software-vendors/) - [BlogInvoicing Software for SMEs: 6 Best Tools in 2026→](/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/) --- URL: https://www.shuttleglobal.com/guides/how-to-choose-payment-platform/ --- # How to Choose a Payment Platform: The Evaluation Checklist for Platform Operators | Shuttle > Choosing a payment platform is one of the highest-stakes infrastructure decisions a platform operator will make. # How to Choose a Payment Platform: The Evaluation Checklist for Platform Operators By Shuttle Team, February 23, 2026 Choosing a payment platform is one of the highest-stakes infrastructure decisions a platform operator will make. Not because payments are complicated -- though they are -- but because the decision is effectively irreversible for three to five years. Your merchants onboard, tokenise their card data, and build workflows around whatever you deploy. Switching means re-integration work, re-tokenisation (which requires active merchant cooperation), potential downtime, and the political cost of explaining to customers why their payment setup is changing. Get it right and payments becomes a competitive moat -- a revenue line, a retention driver, a capability that larger competitors can't easily replicate. Get it wrong and you spend the next two years managing technical debt, fielding merchant complaints, and watching your engineering team fight fires instead of shipping product. This guide is a working evaluation framework. Use it in vendor RFPs, in internal scoring sessions, and as a checklist when a vendor's sales deck is designed to obscure the things you most need to know. ## Why This Decision Matters More Than Most Infrastructure Choices Most infrastructure decisions are reversible. You can swap your database, re-platform your CMS, or change your cloud provider with effort and cost but without fundamental business disruption. Payments is different for three reasons. Tokenisation lock-in. Card data is stored as tokens held by your payment provider. Moving tokens between providers requires a formal token migration -- a process that takes months, requires cooperation from both the old and new provider, and carries real risk of declined transactions during the transition. Many platforms discover this only after they've decided to switch. Merchant migration. If you have hundreds or thousands of merchants connected to your platform, every one of them needs to reconnect their bank account, re-verify their identity, and potentially update their integration when you switch providers. Attrition during migration is material. Compliance re-certification. Your PCI scope, your compliance documentation, and your security audit findings are all tied to the specific provider you use. Switching means starting those processes again. The platforms that navigate this well are the ones that spend 60 to 90 days on vendor evaluation -- before writing a single line of integration code. That time investment at the front is worth 12 to 18 months of avoidable engineering work later. ## The 12 Criteria That Matter ### 1. PSP Flexibility What you need to know: Are you locked into a single processor, or can different merchants use different payment gateways? This matters immediately for enterprise sales. Large customers -- hotel chains, insurance carriers, established retailers -- often have existing PSP relationships with negotiated rates they've spent years optimising. If your platform mandates a single processor, you lose those deals or spend months building one-off integrations. Multi-PSP architecture solves this at the infrastructure level. Questions to ask: - "Can a merchant bring their own PSP and still use our platform?" - "What happens when an enterprise customer mandates Worldpay or Adyen?" - "Can we add a new PSP without re-integrating our core platform?" - "Is PSP routing logic something we control, or something your platform controls?" Red flag: Any answer that starts with "we have a preferred PSP relationship" without explaining the opt-out path. ### 2. White-Label Depth What you need to know: How completely does your platform brand replace the provider's brand in the merchant experience? True white-labelling means your merchants never encounter the payment provider's brand -- not in the checkout flow, not in the merchant dashboard, not in onboarding emails, not in support interactions. Partial white-labelling (branded checkout but provider-branded merchant portal, for example) creates confusion and undermines the perception that payments is your platform's capability. - "Will my merchants ever see your brand name or logo anywhere in their experience?" - "Is the merchant dashboard served from our domain?" - "Are onboarding and KYC emails sent from our brand?" - "What does a support ticket look like from a merchant's perspective?" Red flag: "We can co-brand the portal" -- this is not white-labelling. ### 3. Merchant Onboarding What you need to know: How long does it take a new merchant to go from signup to processing live transactions, and how much of that is your problem to build? KYC/KYB (Know Your Customer / Know Your Business) is the regulatory requirement that identifies and verifies merchants before they can process payments. Some platforms give you pre-built onboarding flows. Others give you an API and leave you to build the UX, the document collection, and the status management yourself. The difference is three months of engineering work. - "What does the merchant onboarding flow look like out of the box?" - "Who handles KYC/KYB verification -- your team, a third party, or us?" - "What's the typical time from merchant application to first live transaction?" - "What happens when a merchant is flagged during KYC -- who handles remediation?" Red flag: "Our API makes it easy to build your own onboarding" -- this is not a pre-built solution. ### 4. Channel Coverage What you need to know: Does the payment integration support every channel you might need, including channels you haven't built yet? Most platforms start with online checkout. But the most interesting growth vectors right now are voice channels (IVR, AI agents), payment links for invoice-based workflows, and chat-embedded payments. If your payment provider only supports card-present and card-not-present via web checkout, you're re-integrating when you add a voice product or a payment link feature. - "If we add a voice channel or AI agent in 18 months, does our payment integration support that?" - "Do you support payment links -- standalone hosted checkout pages?" - "Can payments be initiated from a chat interface or messaging platform?" - "What channels have your existing platform customers added over time?" Red flag: "We're focused on online payments for now" -- this is a roadmap commitment you're making on behalf of your platform. ### 5. Compliance and Certifications What you need to know: What is your PCI scope with this provider, and who is responsible for maintaining it? PCI DSS Level 1 is the highest certification level -- required for providers processing over six million card transactions annually. ISO 27001 and SOC 2 Type II are the information security certifications that enterprise buyers and their procurement teams will ask for. The key question for your platform is not just whether the provider is certified, but what that certification means for your own compliance obligations. - "What PCI DSS level are you certified at, and can you provide your current AOC (Attestation of Compliance)?" - "What is our PCI scope as a platform operator using your solution?" - "Are you ISO 27001 certified? SOC 2 Type II?" - "What documentation do you provide to help us pass enterprise security reviews?" Red flag: Vague answers about "shared responsibility" without specifics on where your scope ends. ### 6. Commercial Model What you need to know: How does your payment integration generate revenue for your platform, and what are the unit economics per transaction? Embedded payments should not just be a feature -- it should be a revenue line. The mechanisms are: a share of interchange or processing margin on every transaction, platform fees charged to merchants for payment access, or a combination. Understanding this upfront determines whether payments becomes a profit centre or a cost centre. - "What is our revenue share per transaction, and how does it scale with volume?" - "Can we set our own pricing to merchants, or are rates fixed?" - "How is revenue share reported and settled to us?" - "What's the realistic annual payment revenue for a platform at our scale?" Red flag: A provider that can't give you a clear per-transaction economics model isn't ready for platform customers. ### 7. Enterprise Readiness What you need to know: Does the platform scale to enterprise customers with complex requirements -- their own PSPs, negotiated rates, multiple entities, multiple currencies? Winning a mid-market platform customer is good. Winning enterprise is transformative. But enterprise customers have requirements that break most embedded payment solutions: PSP mandates, complex settlement structures, multi-currency operations, multi-entity corporate hierarchies. Your payment infrastructure needs to support these without custom engineering. - "What's the largest or most complex customer currently using your platform product?" - "What happens when we land a customer with 10,000 sub-merchants or multiple legal entities?" - "Can merchants operate in multiple currencies and settlement accounts?" - "How do you handle a customer who needs their own dedicated payment infrastructure?" Red flag: Reference customers that are all small or mid-market only. ### 8. Integration Complexity What you need to know: What does integration actually require, and what is the realistic path from zero to production? Every payment provider will tell you their API is well-documented and easy to integrate. The real questions are: what are the pre-built components (hosted payment pages, UI kits, SDKs) that reduce engineering work, and what does production-ready look like versus a basic proof of concept? - "What pre-built UI components do you offer?" - "What's the realistic time from contract to first live merchant transaction?" - "What does your implementation support look like -- a dedicated solutions engineer, or documentation only?" - "Can you share integration timelines from comparable platform customers?" Red flag: An implementation timeline quoted in weeks when comparable platforms measure theirs in months -- this suggests the salesperson hasn't been realistic with you. ### 9. Reporting and Reconciliation What you need to know: Can your merchants self-serve on transaction data, and can your platform team reconcile payments at scale? Merchant support tickets about transactions are one of the highest-cost support categories for platforms. If your payment provider gives merchants access to clear, real-time transaction data and self-serve dispute management, those tickets don't reach your team. Equally, your finance team needs platform-level reporting and settlement data in a format they can actually use. - "What does the merchant-facing transaction dashboard look like?" - "Can merchants download transaction exports or access data via API?" - "How is settlement data provided to our platform -- CSV, API, or both?" - "How are chargebacks and disputes managed in the merchant portal?" Red flag: "Reporting is on our roadmap" -- this will cost you in support overhead. ### 10. Geographic Coverage What you need to know: Which countries can your merchants process in, and what does cross-border expansion look like? Many embedded payment solutions are strong in their home market and brittle elsewhere. If your platform operates or plans to operate internationally, you need to understand local acquiring, local payment methods, currency support, and the regulatory requirements the provider manages on your behalf. - "Which countries do you currently support for merchant processing?" - "Do you offer local acquiring, or only cross-border processing?" - "What local payment methods (SEPA, iDEAL, BACS, etc.) are supported in key markets?" - "What's the process for launching in a new country -- what do we need to do versus what do you handle?" Red flag: Strong presence in one geography with vague commitments about international expansion. ### 11. Scalability and Reliability What you need to know: What is the provider's actual uptime track record, and what happens to your platform during payment infrastructure incidents? Payments downtime is not like application downtime. When payment processing fails, merchants lose revenue in real time -- and they hold your platform responsible. Uptime SLAs in contracts matter less than the actual reliability track record and the incident response process. - "What has your uptime been over the last 12 months? Can you share a status page or incident history?" - "What is your SLA for payment processing availability, and what are the remedies for breaches?" - "How are incidents communicated to platform operators and their merchants?" - "What is your peak transaction throughput, and what happens to performance during high-volume events?" Red flag: No public status page or incident history to review. ### 12. Vendor Stability What you need to know: Who owns the business, what is their financial position, and what happens to your integration if the company is acquired or runs out of capital? Payment infrastructure companies are acquisition targets. A provider that is venture-backed, growing fast, and operating in a consolidating market may look like a great partner today and a strategic asset of a direct competitor in 18 months. Understand the ownership structure, the funding runway, and the contractual protections you have if ownership changes. - "Who are your investors, and what is your current funding position?" - "Have there been any recent ownership changes or acquisition discussions?" - "What change-of-control protections exist in the contract?" - "What is your plan for long-term independent operation?" Red flag: Evasiveness about ownership or funding -- particularly from a company that has raised significant venture capital in a market with active M&A. ## The Four Models Compared There are four fundamental approaches to embedded payments for platform operators. Understanding the tradeoffs before you start vendor conversations will sharpen every question you ask. PayFac (DIY) PayFac-as-a-Service (Payrix, Finix) PSP Platform Product (Stripe Connect, Adyen for Platforms) PSP-Neutral Layer (Shuttle) PSP Flexibility Single processor Single PSP (theirs) 40+ PSPs, merchant-selectable White-Label Depth Full (you own it) Merchant Onboarding Build yourself Channel Coverage Online-focused Online, voice, links, agents Compliance Burden High (you own it) Provider-managed Commercial Model Full margin Revenue share Merchants keep their own PSP contracts and rates Enterprise PSP Mandates Not supported Native support Integration Complexity Time to Market 12-18 months 3-6 months 2-4 months Becoming a PayFac (registering directly with card networks and managing your own risk and compliance) gives you the most control and the best economics, but it requires substantial capital, legal infrastructure, and ongoing compliance investment. It's the right choice for platforms processing over $1bn annually with a dedicated payments team. For most platforms, it's a distraction. PayFac-as-a-Service providers like Payrix (now Worldpay for Platforms) and Finix give you the PayFac economic model without building it yourself -- but they typically lock you into their processing network. Enterprise customers with existing PSP relationships become harder to serve. PSP Platform Products like Stripe Connect and Adyen for Platforms offer deep functionality within their ecosystem, with excellent developer experience and global reach. The tradeoff is single-PSP lock-in -- all your merchants process through Stripe or Adyen, which becomes a commercial and strategic constraint as you grow into enterprise. PSP-Neutral Payment Layers like Shuttle sit above the PSP layer, connecting to 40+ processors and routing transactions based on merchant preference, cost, or geography. This model gives platforms the white-label experience of a PayFac, the pre-built infrastructure of a platform product, and the PSP flexibility that enterprise customers require -- without the compliance burden of registering as a PayFac. The right model depends on your scale, your merchant base, and your enterprise ambitions. Most platforms that are serious about enterprise deals will eventually require PSP flexibility -- the question is whether to build that flexibility in from the start. ## Red Flags in Vendor Conversations After seeing dozens of platform payment evaluations, these are the warning signs that a vendor isn't a fit: "You can always add more PSPs later." The architecture either supports multi-PSP at the core or it doesn't. Adding PSP support as a later integration almost always means custom engineering work scoped to you. Ask to see a reference customer who has actually done it. "Our checkout converts better." Compared to what baseline, over what time period, in what vertical? Conversion claims without methodology are marketing. Ask for the A/B test methodology and the confidence interval. Vague pricing in the first three conversations. Commercial models and processing economics vary significantly. A vendor who won't give you indicative numbers until late in the sales cycle is either building in negotiating leverage or doesn't have a standard commercial model -- both are problems. No reference customers in your vertical. A payments provider who has never worked with a platform in your industry will learn on your dime. Ask specifically for two or three reference calls with similar platform operators, and take them. "We'll handle implementation together." This sounds collaborative; it sometimes means the implementation timeline is undefined. Ask for a project plan with milestones, timelines, and named resources -- before you sign. Change-of-control clauses that don't protect you. If the contract doesn't give you a clean exit right if the vendor is acquired, you have no protection if they're bought by a competitor or wound down. This is non-negotiable. ## The RFP Template Copy these into your vendor evaluation scorecard and rate each provider on a 1-5 scale. - Can merchants bring their own PSP? - Can we add new PSPs without re-integrating? - Is PSP routing logic configurable by us? White-Label - Is every merchant touchpoint under our brand? - Is the merchant dashboard served from our domain? - Is KYC/KYB fully managed by the provider? - What is the average time from application to first live transaction? - Does the platform support voice-initiated payments? - Does the platform support payment links? - Does the platform support chat and AI agent integrations? Compliance - What PCI DSS level is the provider certified at? - What is our PCI scope as an operator? - Are ISO 27001 and SOC 2 Type II in place? - What is the per-transaction revenue share? - Can we set our own pricing to merchants? Enterprise Readiness - Can enterprise customers use their own negotiated PSP rates? - Is multi-currency and multi-entity supported natively? Integration - What pre-built UI components and SDKs are available? - What is the realistic time to first live merchant transaction? - Do merchants have real-time self-serve transaction access? - Is settlement data available via API? - Which countries and currencies are supported today? - Is local acquiring available in our target markets? Reliability - What is the 12-month uptime track record? - Is a public status page available? Vendor Stability - Who owns the business? - What change-of-control protections exist in the contract? ## Taking the Next Step The most expensive payment infrastructure decision is the wrong one made quickly. The second most expensive is the right one made too slowly while a competitor closes enterprise deals you can't support. If you're at the stage of shortlisting vendors, the evaluation framework above should give you enough to run a structured RFP and score responses consistently. If you're earlier -- still deciding which model is right for your platform -- start with the foundational questions: do you need PSP flexibility for enterprise, do you need multi-channel coverage, and how important is speed to market? Related Reading: - What Is a Payment Gateway? -- how gateways work, costs, and top providers compared - Payment Providers Explained -- gateway aggregation and how to choose a payment provider - What Is Embedded Payments? -- the fundamentals of the embedded payments model - Embedded Payments Without Becoming a PayFac -- the PayFac decision in detail - PSP-Neutral vs Single-PSP Architecture -- the architectural choice and its long-term implications - How to Get Payments Off Your Product Roadmap -- the build vs buy decision for platform teams - Enterprise PSP Mandates -- why PSP flexibility is a precondition for enterprise sales - How Platforms Monetise Payments -- building payments into your revenue model - Payment Links for Hotels & Holiday Accommodation -- payment platform evaluation from the hospitality vertical perspective - Car Dealership Payment Solutions -- payment platform requirements for automotive and motor trade Shuttle Global is The Payment Layer -- connecting platforms to 40+ payment processors. White-label merchant onboarding, multi-channel support (online, voice, payment links, AI agents), and PCI DSS Level 1, ISO 27001, and SOC 2 Type II certified. Used by platforms that need PSP flexibility from day one. Book a discovery call to walk through your specific platform requirements, or see how platforms use Shuttle. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Do I Need a Full AR Platform or Just Smarter Payment Links? ### Payment Orchestration Alternatives for Platforms ### Insurance Billing vs Payment Execution: Why Your Platform Needs Both ### Payment Providers: How They Work & How to Choose (2026) ### Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It ### Why Platforms Don't Want to Be Payment Companies ## Links - [payment gateways](/blog/what-is-a-payment-gateway/) - [hotel chains](/guides/payment-links-for-hotels/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [What Is a Payment Gateway?](/blog/what-is-a-payment-gateway/) - [Payment Providers Explained](/blog/what-is-payment-gateway-aggregation/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Car Dealership Payment Solutions](/guides/car-dealership-payment-solutions/) - [Book a discovery call](/discovery/) - [see how platforms use Shuttle](/platforms/) - [Book a Call](/discovery/) - [BlogDo I Need a Full AR Platform or Just Smarter Payment Links?→](/blog/do-i-need-a-full-ar-platform-or-just-smarter-payment-links/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogInsurance Billing vs Payment Execution: Why Your Platform Needs Both→](/blog/insurance-billing-vs-payment-execution/) - [BlogPayment Providers: How They Work & How to Choose (2026)→](/blog/what-is-payment-gateway-aggregation/) - [BlogPayment Gateway Aggregation: What It Is and Why SaaS Platforms Need It→](/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/) - [BlogWhy Platforms Don't Want to Be Payment Companies→](/blog/why-platforms-dont-want-to-be-payment-companies/) --- URL: https://www.shuttleglobal.com/guides/how-to-send-payment-requests/ --- # How to Send Payment Requests: The Complete Guide to Digital Payment Collection | Shuttle > What Is a Payment Request? A payment request is a digital message -- SMS, email, WhatsApp, or QR code -- that contains a link to a branded checkout page. # How to Send Payment Requests: The Complete Guide to Digital Payment Collection By Shuttle Team, April 3, 2026 ## What Is a Payment Request? A payment request is a digital message -- SMS, email, WhatsApp, or QR code -- that contains a link to a branded checkout page. The recipient clicks, chooses their payment method, pays, and the sender gets instant confirmation. It replaces: - Invoices that sit unpaid for 30-90 days - Card details read over the phone (a PCI compliance risk) - Bank transfer requests that need manual reconciliation - "Please bring your card when you visit" -- friction that delays payment Payment requests work for any business that collects money from customers, clients, or patients -- from a £50 service invoice to a £30,000 vehicle deposit. ## How to Send a Payment Request: 5 Methods ### 1. SMS Payment Request The fastest delivery channel. The customer receives a text with a short message and a link to pay. Best for: Immediate requests during or after a conversation. Appointment deposits. Delivery charges. Balance reminders. Why it works: SMS open rates exceed 90%. Most people read a text within 3 minutes. The payment link opens in a mobile browser -- no app required. Example: "Hi Sarah -- your vehicle deposit of £2,000 is ready to pay. Tap here to complete: [link]. Payment options: card, Apple Pay, or bank transfer." ### 2. Email Payment Request Longer-form delivery with space for invoice details, itemisation, and branding. Best for: Invoice-attached requests. Monthly statements. Professional services. B2B payments where the recipient needs a paper trail. Why it works: Email supports rich formatting -- your logo, line items, payment terms, and a prominent "Pay Now" button. Forwards easily within organisations (e.g., tradesperson forwards to their accounts department). ### 3. WhatsApp Payment Request Delivered through the customer's preferred messaging app. Higher engagement than email for consumer audiences. Best for: Hospitality (hotel deposits, restaurant pre-payments). Retail follow-ups. Service businesses where WhatsApp is the primary communication channel. Why it works: WhatsApp messages have even higher open rates than SMS. The conversational context (previous messages, booking details) sits alongside the payment request. ### 4. QR Code Payment Request A scannable code displayed in-person -- on an invoice, receipt, counter display, or screen. Best for: Point-of-sale alternatives. Trade counters. Showroom displays. Event payments. Invoices that include a "scan to pay" option. Why it works: No need to collect contact details. The customer scans and pays from their own device. Useful in environments where terminals aren't practical or where you want to offer card-free options. ### 5. Phone Payment (Voice Checkout) The customer pays during a phone call by entering card details via keypad, without reading numbers aloud. Best for: Contact centres. Insurance renewals. Debt collection. Any business where customers call to pay and you want to capture payment during the conversation -- not send a link and hope they pay later. How it works: The staff member triggers a payment capture. The customer enters their 16-digit card number, expiry, and CVV via keypad (DTMF). The tones are masked -- the agent never hears them. Payment completes in seconds. The call continues. This is fundamentally different from "sending a payment request." It's capturing payment in real time during a conversation. For businesses that handle phone-based payments daily, voice checkout is faster and higher-converting than sending a link mid-call. ## Payment Methods Customers Can Use A good payment request supports multiple payment methods on a single checkout page. The customer chooses what works for them: Payment Method Card (Visa, Mastercard, Amex) Universal -- works for any amount Instant confirmation, 1-3 day settlement Open Banking / Pay by Bank High-value transactions (£1,000+) Fraction of card fees Near-instant confirmation and settlement Mobile-first customers Same as card Instant -- biometric authentication Google Pay Android users Customers who prefer PayPal Instant confirmation BNPL (Klarna, Affirm) Consumer purchases where instalments help conversion Provider-dependent Instant for merchant, instalments for customer ACH Direct Debit US bank payments Low fixed fee 2-3 business days BACS Direct Debit UK recurring payments Open banking deserves special attention. For businesses processing high-value transactions -- car dealerships, property, trade supplies, professional services -- the card fee savings from Pay by Bank are substantial. A £20,000 transaction at 2% card fees costs £400. Pay by Bank costs pennies. Offering both on the same payment link lets the customer choose while the business saves. ## Payment Request Software: What to Look For ### Branding The checkout page should look like your business -- logo, colours, domain. For high-value payments, trust matters. A generic third-party page creates doubt. ### Multi-channel delivery SMS + email + WhatsApp + QR at minimum. Different customers prefer different channels. The same payment link should work across all of them. ### Payment method coverage Cards, open banking, Apple Pay, Google Pay as a baseline. BNPL if you serve consumers. ACH/BACS if you handle recurring or US payments. ### Reminders and chase Automated follow-ups for unpaid requests. Configurable intervals (3 days, 7 days, on due date). Escalation from email to SMS for unresponsive recipients. ### Real-time tracking See which requests are sent, viewed, started, and completed. Know when a customer opens the link but doesn't pay -- that's a signal for a follow-up call. ### PCI compliance If the software handles card data, the provider must be PCI DSS certified. Level 1 is the highest standard. This keeps card data out of your environment entirely. ### API and integrations Can you trigger payment requests from your existing systems -- CRM, ERP, accounting software, booking system? API access, Zapier, and Make.com connectors eliminate manual link creation. ### Multi-PSP support Does the tool work with your existing payment gateway? Can you switch gateways without re-implementing? For platforms serving multiple merchants, can each merchant use their own PSP? ## Comparing Payment Request Tools Stripe Payment Links GoCardless SMS delivery No (link only) Email delivery Via chat integration Open banking Yes (14 countries) Yes (direct debit) Card payments Yes (40+ PSPs) Yes (merchant's gateway) Yes (Stripe only) No (PayPal only) Apple Pay / Google Pay Voice checkout Yes (DTMF) White-label Full branding Branded pages Stripe-branded PayPal-branded GoCardless-branded 40+ gateways Merchant's gateway Stripe only PayPal only GoCardless only Platform/multi-merchant From $49/month From €299/month Free (Stripe fees apply) Free (PayPal fees apply) Stripe Payment Links and PayPal.Me are free but lock you into a single PSP, offer no SMS delivery, and can't be white-labelled. They work for simple use cases but don't scale. Prommt is strong for high-value transactions with European open banking, but costs significantly more and doesn't offer voice checkout or multi-PSP support. See the full Shuttle vs Prommt comparison. GoCardless is excellent for recurring direct debit but doesn't support card payments or one-off payment links. ## FAQ How do I send a payment request to a customer? Choose a payment request tool (Shuttle, Prommt, or a PSP-native option like Stripe Links). Create a payment link with the amount and reference. Send it via SMS, email, or WhatsApp. The customer clicks, pays, and you get instant confirmation. What's the difference between a payment request and an invoice? An invoice is a document requesting payment. A payment request is a document with a built-in way to pay. The best approach is both together -- an invoice with a "Pay Now" link embedded in it. See Payment Links on Invoices. Which payment method has the lowest fees? Open banking (Pay by Bank) has the lowest fees -- typically pennies per transaction vs 1.5-2.5% for cards. But not all customers have compatible banks, so offering both cards and open banking on the same payment link maximises both conversion and savings. Can I send payment requests from QuickBooks or Xero? Yes. See QuickBooks Payment Links and Xero Payment Links for integration guides. Shuttle connects to both via API and workflow automation. What if the customer wants to pay over the phone? Use voice checkout to capture card details via keypad during the call. PCI-compliant, instant, and no card numbers read aloud. This is better than sending a link mid-call for customers who want to pay right now. Are payment requests secure? Yes. Payment links from PCI DSS Level 1 certified providers (like Shuttle) handle all card data within a certified environment. Open banking payments are authenticated through the customer's own banking app. Both are more secure than taking card details verbally. Can I automate payment requests from my CRM or billing system? Yes. Most payment request tools offer APIs and integrations with Zapier, Make.com, and native connectors. Common automations: send a link when an invoice is created, send a reminder when payment is overdue, send a receipt when payment is confirmed. ## Related Reading - Payment Links for Car Dealerships -- automotive payment collection with links, voice, and open banking - Builders Merchant Payment Collection -- payment links and voice checkout for trade suppliers - Shuttle vs Prommt -- comparing payment request platforms - Best Payment Link Providers (2026) -- ranked comparison of payment link services - Payment Links on Invoices -- embed payment links in your invoices - QuickBooks Payment Links -- payment links for QuickBooks users - What Are Voice Payments? -- the complete guide to voice payment channels - White-Label Payment Links for Platforms -- branded payment pages for multi-merchant businesses Send payment requests that actually get paid. Shuttle gives you branded payment links with cards, open banking, Apple Pay, and voice checkout -- from $49/month. Send via SMS, email, or WhatsApp. Get paid in seconds. See Payment Links | Book a Demo ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments ### Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Payment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants ## Links - [DTMF](/guides/dtmf-payments/) - [voice checkout](/platforms/voice-checkout/) - [full Shuttle vs Prommt comparison](/vs/prommt/) - [Payment Links on Invoices](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [QuickBooks Payment Links](/guides/quickbooks-payment-links/) - [Xero Payment Links](/blog/xero-payment-links/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payment Links for Car Dealerships](/guides/payment-links-for-car-dealerships/) - [Builders Merchant Payment Collection](/guides/builders-merchant-payment-collection/) - [Shuttle vs Prommt](/vs/prommt/) - [Best Payment Link Providers (2026)](/guides/best-payment-link-providers/) - [What Are Voice Payments?](/guides/voice-payments/) - [White-Label Payment Links for Platforms](/guides/white-label-payment-links/) - [See Payment Links](/merchants/links-checkout/) - [Book a Demo](/discovery/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [BlogPayment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments→](/blog/payment-links-for-freedompay/) - [BlogPayment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments→](/blog/payment-links-for-cardconnect/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [BlogPayment Links for BS Payone: Send Branded Checkout Links For DACH Region Merchants→](/blog/payment-links-for-bs-payone/) --- URL: https://www.shuttleglobal.com/guides/hubspot-commerce-hub-transaction-fees/ --- # HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) | Shuttle > HubSpot Payments charges a transaction fee on top of the underlying card processing rate -- and most teams discover this only after they've committed to... # HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026) By Shuttle Team, May 9, 2026 HubSpot Payments charges a transaction fee on top of the underlying card processing rate -- and most teams discover this only after they've committed to HubSpot Commerce Hub as their billing engine. The total cost of accepting a card payment through HubSpot is typically 2.9% + $0.30 (US) or 1.9% + £0.20 (UK) for cards, plus 0.5% (capped) for ACH -- but those numbers hide a lot of structure. The headline question searchers ask -- does HubSpot support payment links without transaction fees? -- has a longer answer than HubSpot's pricing page suggests. There are payment links inside Commerce Hub with HubSpot Payments processing them (the version that charges the transaction fee), and there are payment links inside Commerce Hub processed by a third-party integration (the version that doesn't). Most teams don't know the second option exists. This guide covers what HubSpot Payments actually charges, what's included in each Commerce Hub tier, the hidden cost structures most teams miss, and the integration patterns that let you keep HubSpot's CRM-attached payment links without paying HubSpot's transaction markup. ## Quick Answer - HubSpot Payments transaction fee (cards): 2.9% + $0.30 in the US, 1.9% + £0.20 in the UK, 1.9% + €0.25 in most of the EU. Layered on top of HubSpot's own processor agreement. - HubSpot Payments transaction fee (ACH): 0.5% capped at $5 per transaction (US only). - Commerce Hub tier required: Payment links and HubSpot Payments are available on Commerce Hub Starter and above. Free Commerce tools include limited invoicing but not full payment links. - Currencies supported: USD, GBP, EUR, CAD, AUD as of 2026. Other currencies require a third-party processor integration. - To avoid HubSpot transaction fees: use a third-party payment link provider (like Shuttle, Stripe, GoCardless) wired to HubSpot via API/CRM integration. You keep HubSpot's CRM and commerce workflow; the payment processes outside of HubSpot Payments at your processor's direct rate. ## What HubSpot Payments Actually Charges HubSpot Payments is HubSpot's own merchant-of-record payment processor, launched in 2021 and rolled into Commerce Hub when that product launched in 2024. When you use it, HubSpot underwrites your merchant account, processes the transaction, and deposits funds to your bank -- but they add a transaction fee on top of whatever the underlying card networks and processor charge them. The published rates (as of 2026): Card transactions ACH transactions United States 2.9% + $0.30 0.5%, capped at $5 United Kingdom 1.9% + £0.20 Not supported EU (most countries) 1.9% + €0.25 2.9% + CAD $0.30 2.9% + AUD $0.30 International cards (cards issued outside your business region) typically attract an additional 1.5% cross-border fee on top of the published rates. Currency conversion adds another 1-2% if HubSpot is handling FX. What's not included in those rates: - Refund processing fees -- HubSpot refunds the transaction fee on full refunds but not always on partial refunds. - Chargeback fees -- typically $15-25 per chargeback, separate from the transaction fee. - Disputed transaction handling -- your time, not HubSpot's, but it lives inside the HubSpot UI which adds friction. - Payout fees -- HubSpot's standard payouts are free, but expedited payouts (instant or 1-day) carry fees. The 2.9% headline is what marketing copy compares; the all-in effective rate, including failed transactions, refunds, chargebacks, and FX, typically runs 3.2-3.6% of gross volume for most US merchants. ## What's Included in Commerce Hub Tiers HubSpot Payments is gated to Commerce Hub paid tiers. The transaction fees above apply regardless of which tier you're on -- the tiers determine what features you can use around the payments. Free Commerce Tools (with HubSpot Free CRM): - Invoices (limited templates, no automation) - One-off payment links - Basic payment tracking in the CRM - No subscription billing, no quotes-to-payment workflow Commerce Hub Starter (~$20/seat/month, billed annually as of 2026): - Full invoicing with templates - Recurring payment links and subscriptions - Quotes with embedded payment links - Basic automation triggers (invoice sent, payment received) Commerce Hub Professional (~$1,200/month): - Subscription management with proration - Customer portal for self-service - Advanced automation (dunning, retry logic) - Custom payment link branding (subdomain, logo, colours) - Multi-currency on a single contract Commerce Hub Enterprise (~$3,200/month): - Custom approval workflows - Sandbox environment - Advanced reporting and revenue analytics - Single sign-on, audit logs Pricing exact figures shift; check HubSpot's pricing page for current numbers. The structural point: transaction fees are flat across tiers -- paying for Professional doesn't lower your processing rate. What you're buying with higher tiers is features around the transaction, not better economics on the transaction itself. ## The Hidden Cost Structure Most Teams Miss Three cost dynamics aren't visible from HubSpot's pricing page but show up on the monthly statement. 1. The "blended rate" problem on B2B invoicing. HubSpot Payments is optimised for B2C-style checkout. If your B2B invoices average £5,000 and you take them via HubSpot Payments cards, you're paying ~£100 per invoice in processing fees (~1.9% + £0.20). On 50 invoices a month, that's £5,000 in fees. Open banking (pay-by-bank) on the same volume would cost ~£150-£300 in fees. HubSpot Payments does not currently support open banking in any region. 2. Currency support gates entire markets. If you're billing customers in Brazilian Real, Singapore Dollars, INR, MXN, JPY, or any currency outside HubSpot's supported five, HubSpot Payments simply can't process the transaction. You either force the customer into a supported currency (and they pay FX on their side) or you bypass HubSpot Payments entirely. This is a hard wall, not a fee issue. 3. PSP optionality is zero. HubSpot Payments is a single-processor stack. If your business has volume tiers or special pricing with Stripe, Adyen, Worldpay, or another acquirer, you can't route HubSpot transactions through them. Every transaction takes HubSpot's standard rate, regardless of your existing PSP relationships. For most teams using HubSpot for CRM + lightweight invoicing, the convenience tax of HubSpot Payments is worth it. For teams with high-value B2B invoices, international currencies, or existing PSP economics, it adds up faster than the published rates suggest. ## How to Get HubSpot Payment Links Without HubSpot's Transaction Fees The integration pattern that most teams don't know about: HubSpot Commerce Hub can generate payment links that route to a third-party processor instead of HubSpot Payments. You keep the HubSpot UI, the CRM attachment, the workflow triggers -- but the transaction happens at your processor's rate, not HubSpot's marked-up rate. There are three implementation patterns. ### Pattern 1: Native HubSpot + Stripe / GoCardless integration HubSpot has native integrations with Stripe (and GoCardless in some regions) that let you connect your own processor account to HubSpot Commerce Hub. Payment links generated in HubSpot route to Stripe's checkout instead of HubSpot Payments. You pay Stripe's standard rates (2.9% + $0.30 in the US -- same headline rate as HubSpot Payments, but no HubSpot markup) and HubSpot doesn't get a cut of the transaction. Trade-offs: Limited to Stripe (and GoCardless ACH/SEPA where supported). You lose some HubSpot-specific features like the native customer portal. Currency support is still capped by what Stripe supports natively. Best for: Teams already on Stripe who want to keep that relationship while using HubSpot CRM. ### Pattern 2: Embed a third-party payment link in HubSpot workflows Instead of using HubSpot's native payment link, generate a payment link from a third-party provider via API and embed the URL in HubSpot's invoice, email, or workflow. - HubSpot workflow triggers (deal closed-won, invoice generated, custom trigger) - Workflow calls your payment provider's API to generate a unique link tied to the deal/invoice - Workflow inserts the link into the email or invoice template - Customer clicks, lands on the third-party hosted checkout, pays - Webhook fires back to HubSpot updating the deal/contact with payment status Trade-offs: Requires HubSpot Operations Hub (or Professional+) for custom workflow code or a connector. The customer-facing checkout is on the third-party's domain unless you use white-label payment links. Best for: Teams with non-standard currency needs, existing PSP relationships, or B2B invoice profiles where 1.9% + fees materially impacts margin. ### Pattern 3: Shuttle integration (multi-PSP coverage under HubSpot) For teams that want HubSpot's CRM workflow with maximum payment optionality, the Shuttle integration provides: - Payment links generated from HubSpot triggers -- same workflow as native HubSpot Payments - Routed across 40+ underlying processors -- your existing Stripe, Adyen, Worldpay, Braintree, GoCardless, or any combination - Multi-currency support beyond HubSpot's five -- Shuttle covers 210+ countries via its PSP coverage - White-label checkout on your domain, not HubSpot's or Shuttle's - Open banking / pay-by-bank for high-value B2B invoices, dropping effective rates to 0.5-1% on UK/EU transactions - HubSpot CRM attachment -- webhook back to HubSpot with payment status, fee data, processor used, full reconciliation Trade-offs: Adds a layer to the stack. Not the right answer for teams processing <$10k/month where HubSpot Payments' simplicity is worth the markup. Best for: Mid-to-high volume B2B merchants on HubSpot Commerce Hub who care about transaction economics, international support, or PSP optionality. ## HubSpot Payments vs Third-Party Integration: Side-by-Side HubSpot Payments Stripe/GoCardless via HubSpot Shuttle via HubSpot US card transaction fee 2.9% + $0.30 (Stripe direct) Your PSP rate, no markup UK card transaction fee Varies by PSP 0.5% capped at $5 0.8% + $0.05 (Stripe) Varies, often 0.2-0.5% Open banking / pay-by-bank ❌ Not supported Limited (GoCardless only) ✓ 0.2-0.5% on UK/EU Currency support 5 currencies ~135 (Stripe) 210+ countries PSP optionality Single (HubSpot) Single (Stripe or GC) 40+ PSPs, route per transaction White-label checkout ❌ HubSpot branding ❌ Stripe branding ✓ Your domain + branding HubSpot CRM attachment ✓ Via webhook Setup complexity None (built-in) Low (native integration) Medium (API + workflow setup) Low volume, US-centric, simple billing Single-PSP teams already on Stripe Mid-high volume, multi-currency, B2B, multi-PSP ## Frequently Asked Questions Does HubSpot charge transaction fees on payment links? Yes. HubSpot Payments (the default processor for HubSpot payment links) charges 2.9% + $0.30 in the US, 1.9% + £0.20 in the UK, and similar rates in supported EU currencies. ACH is 0.5% capped at $5 (US only). The transaction fee is the same regardless of which Commerce Hub tier you're on. Can I use HubSpot payment links without HubSpot Payments? Yes. HubSpot supports native integrations with Stripe and GoCardless that route payment links to your own processor account at their direct rates. For broader PSP optionality (Adyen, Worldpay, multi-PSP routing), you can integrate a third-party payment link provider via HubSpot's API and workflow triggers -- see the integration patterns above. Is HubSpot Commerce Hub required for payment links? You can generate one-off payment links on HubSpot Free Commerce Tools, but recurring payments, subscriptions, branded checkout, and most automation features require Commerce Hub Starter or above. What currencies does HubSpot Payments support? As of 2026: USD, GBP, EUR (in most countries), CAD, and AUD. Currencies outside these require a third-party integration if you're billing customers in their local currency. Are HubSpot Payments fees negotiable at higher volumes? HubSpot will negotiate Commerce Hub seat pricing at enterprise tier, but the transaction fee structure is not typically negotiated. Volume-based pricing on transaction fees is a key differentiator of direct PSP relationships over embedded payment platforms. How much does HubSpot Commerce Hub cost? Pricing (as of 2026): Starter ~$20/seat/month, Professional ~$1,200/month, Enterprise ~$3,200/month. Check HubSpot's pricing page for current figures -- the structural point is that transaction fees are flat across tiers. Does HubSpot Payments support open banking / pay-by-bank? No. HubSpot Payments processes cards and ACH (US) only. Open banking and pay-by-bank -- which materially reduce fees on high-value B2B invoices -- require a third-party integration. Open banking payment links typically cost 0.2-0.5% per transaction. ## Related Reading - HubSpot Payment Links: Complete 2026 Guide - Best Payment Link Providers 2026 - Invoice Payment Links: How to Get Paid Faster - Pay Now Button for Invoices: B2B Guide - White-Label Payment Links - Payment Workflow Automation: Zapier vs Make vs Direct API ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### HubSpot Payment Links: Setup, Integrations & Alternatives ### Phygital commerce and help of agentic solutions ### 7 ways merchants can save money on payment provider fees ### The Future of Voice Commerce: From IVR to Intelligent Payments ### Agentic Commerce: How AI Will Rewrite the Checkout ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ## Links - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [payment link from a third-party provider](/guides/best-payment-link-providers/) - [white-label payment links](/guides/white-label-payment-links/) - [direct PSP relationships](/guides/best-payment-link-providers/) - [Open banking payment links](/guides/best-payment-link-providers/) - [HubSpot Payment Links: Complete 2026 Guide](/guides/hubspot-payment-links/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [Invoice Payment Links: How to Get Paid Faster](/guides/invoice-payment-links/) - [Pay Now Button for Invoices: B2B Guide](/guides/pay-now-button-invoices/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [Payment Workflow Automation: Zapier vs Make vs Direct API](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) - [BlogHubSpot Payment Links: Setup, Integrations & Alternatives→](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [BlogPhygital commerce and help of agentic solutions→](/blog/phygital-commerce-and-help-of-agentic-solutions/) - [Blog7 ways merchants can save money on payment provider fees→](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [BlogThe Future of Voice Commerce: From IVR to Intelligent Payments→](/blog/the-future-of-voice-commerce/) - [BlogAgentic Commerce: How AI Will Rewrite the Checkout→](/blog/agentic-commerce-how-ai-will-rewrite-the-checkout/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) --- URL: https://www.shuttleglobal.com/guides/hubspot-international-payments/ --- # HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies | Shuttle > HubSpot Payments -- the default processor for HubSpot Commerce Hub payment links -- supports five currencies and five regions. USD, GBP, EUR, CAD, AUD. # HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies By Shuttle Team, May 10, 2026 HubSpot Payments -- the default processor for HubSpot Commerce Hub payment links -- supports five currencies and five regions. USD, GBP, EUR, CAD, AUD. If your customers pay in Brazilian Real, Singapore Dollars, Indian Rupees, Mexican Pesos, South African Rand, Japanese Yen, or any other currency, HubSpot Payments can't process the transaction at all. For most HubSpot Commerce Hub customers in North America and Western Europe, this isn't a problem. For anyone selling cross-border into Latin America, Asia-Pacific, the Middle East, or Africa -- or anyone whose customer base spans 20+ countries -- HubSpot Payments stops working at the currency boundary. The fix isn't to leave HubSpot. The fix is to route international payments through a third-party processor while keeping HubSpot's CRM, workflow, and invoicing layer intact. This guide covers exactly which countries HubSpot Payments serves, what currencies international customers can pay in, and the three integration patterns that let HubSpot process payments worldwide. ## Quick Answer - HubSpot Payments currencies (as of 2026): USD, GBP, EUR, CAD, AUD. - HubSpot Payments merchant countries: United States, United Kingdom, EU (most), Canada, Australia. Your business must be incorporated in one of these regions to onboard. - Can HubSpot Payments accept international cards? Yes -- cards from anywhere can pay you in your supported currency. A US merchant accepting USD can charge a card from Brazil. But the customer pays in USD with their bank's FX, plus typically a cross-border fee of ~1.5% added to your transaction. - Can HubSpot Payments charge in non-supported currencies (BRL, SGD, INR, etc.)? No. Not natively. You need a third-party integration. - Cross-border card fees on HubSpot Payments: Typically +1.5% on top of standard rates (2.9% + $0.30 in the US, so ~4.4% all-in on international cards). - Workarounds: Native HubSpot integrations with Stripe or GoCardless extend currency support to 135+ (Stripe) or limited SEPA/BACS (GoCardless). Multi-PSP integrations like Shuttle cover 210+ countries via 40+ underlying processors. ## What HubSpot Payments Actually Supports There are three different layers of "international support" -- they get conflated in HubSpot's marketing copy. ### Layer 1: Merchant region Where your business is incorporated and your bank account lives. HubSpot Payments will onboard merchants in: - United States - United Kingdom - Most EU countries (Ireland, Germany, France, Netherlands, Spain, etc.) If your business is incorporated in Brazil, India, Singapore, UAE, South Africa, or anywhere outside the above -- HubSpot Payments cannot onboard you at all. You'll need a third-party processor integration regardless of where your customers are. ### Layer 2: Settlement currencies The currencies HubSpot Payments will deposit into your bank account. Same five: USD, GBP, EUR, CAD, AUD. Multi-currency on a single contract requires Commerce Hub Professional or above. ### Layer 3: Customer payment currencies What customers can be charged in. HubSpot Payments only charges in your settlement currencies. A US merchant cannot present a checkout in Brazilian Real to a Brazilian customer through HubSpot Payments -- the checkout shows USD, and the customer's bank handles the FX on their side. That last layer is what most teams discover too late. The customer experience for international payments is poor: prices in unfamiliar currency, surprise FX on the bank statement, higher card decline rates, and abandoned checkouts. The conversion gap between local-currency checkout and forced-USD checkout is typically 15-40% depending on the market. ## What "International Cards" Actually Costs You When a non-domestic card pays a HubSpot Payments invoice, three fees stack: - The standard transaction fee -- 2.9% + $0.30 (US merchant accepting USD). - Cross-border / international card fee -- typically +1.5%. HubSpot doesn't always surface this clearly in pricing docs but applies it via the underlying processor schedule. - Currency conversion fee -- if HubSpot is converting between settlement and customer currency, typically +1-2%. On a $1,000 invoice paid by an international card: ~$29 standard + ~$15 cross-border + ~$10-20 FX = ~$54-64 in total fees, or 5.4-6.4% of the transaction. Compare that to ~2.9% domestic. For US merchants billing international B2B contracts at $5,000+, this is the largest line item in payment costs and rarely surfaces in finance reviews until quarterly statement reconciliation. For SMB merchants selling cross-border ecommerce, it compounds quickly across hundreds of transactions. ## The Three Integration Patterns There are three ways to accept international payments inside HubSpot -- each with different tradeoffs. ### Pattern 1: Stay on HubSpot Payments, accept the cross-border premium Cheapest setup, highest per-transaction cost. Works if: - You're invoicing in USD/GBP/EUR/CAD/AUD and your customer can pay in that currency - Your international transaction volume is low enough that 5-6% all-in doesn't matter - You don't need local-currency presentation for conversion For most HubSpot SMBs with occasional international transactions, this is the right answer. For anyone with serious cross-border volume, the next two patterns pay back fast. ### Pattern 2: HubSpot + Stripe (or GoCardless) native integration HubSpot has native integrations with Stripe and (in some regions) GoCardless that let you connect your own processor account. Payment links generated in HubSpot Commerce Hub route to Stripe instead of HubSpot Payments. What this unlocks: - 135+ currencies via Stripe's coverage (full list at stripe.com/global) - Local payment methods -- iDEAL (Netherlands), Bancontact (Belgium), Klarna (EU), Alipay/WeChat Pay (China), Sofort (Germany) - Stripe's standard pricing rather than HubSpot's marked-up rate - CRM attachment preserved -- HubSpot still tracks payment status against the contact/deal What this doesn't unlock: - Merchant onboarding outside Stripe's supported markets (Latin America beyond Brazil/Mexico, much of Africa, parts of Asia) - PSP optionality -- you're locked to Stripe - White-label checkout (Stripe-branded by default) Best for: Teams already on Stripe who want to keep that relationship while using HubSpot CRM, with customer bases concentrated in Stripe's supported countries. ### Pattern 3: Multi-PSP coverage via Shuttle (or an orchestrator) For teams whose customer base spans regions that no single PSP covers -- typically anything involving 20+ countries, or specific markets like Latin America, Southeast Asia, India, Africa -- a payment orchestrator routes each transaction through the best available processor. - 210+ countries via 40+ underlying processors (Stripe, Adyen, Checkout.com, Worldpay, plus regional specialists like dLocal, EBANX, Cybersource, Razorpay) - Local acquiring -- transactions routed to a processor with local acquiring in the customer's country, dropping decline rates and FX costs - Local payment methods at the orchestrator level -- Pix (Brazil), UPI (India), boleto (Brazil), OXXO (Mexico), PayU (India), etc. - Multi-currency settlement -- collect in 30+ currencies, settle to your bank in fewer - Open banking / pay-by-bank in markets that support it, dropping fees to 0.2-0.5% on high-value B2B Trade-offs: - Adds a layer to the integration stack - Requires Commerce Hub Professional+ for the workflow triggers - Setup is more complex than the native Stripe integration Best for: Cross-border B2B platforms, marketplaces, SaaS companies with global customer bases, or any HubSpot Commerce Hub merchant with material volume outside North America / Western Europe. ## Which Countries Does HubSpot Payments Actually Reach? A practical question that doesn't get a direct answer on HubSpot's site. HubSpot Payments reaches: Strong support (merchant + customer + local currency): United States, United Kingdom, Ireland, Germany, France, Netherlands, Spain, Italy, Belgium, Austria, Portugal, Finland, Estonia, Luxembourg, Canada, Australia. Card acceptance only (customer can pay you, but you can't onboard as a merchant): The rest of the world, if the card brand is Visa, Mastercard, or American Express, and the customer is willing to be charged in your supported currency, and their bank doesn't decline the cross-border transaction. Genuinely unreachable (where HubSpot Payments adds no value vs not having it): - Most of Latin America -- Brazil, Mexico, Argentina, Colombia, Chile, Peru. Local payment methods (Pix, OXXO, boleto, PSE) aren't supported. - South & Southeast Asia -- India, Indonesia, Vietnam, Philippines, Thailand. UPI, OVO, GCash, PayMaya, PromptPay all absent. - Africa -- South Africa, Nigeria, Kenya, Egypt. M-Pesa, instant EFT, USSD payments absent. - Middle East -- UAE, Saudi Arabia, Israel. Mada, Knet, regional wallets absent. - Eastern Europe outside EU -- Russia, Ukraine, Turkey. Regional methods absent. For merchants whose customers cluster in these regions, HubSpot Payments isn't a workable solution and the conversation should start with multi-PSP orchestration, not optimisation of HubSpot Payments itself. ## HubSpot International Payments: Decision Framework Your situation Recommended pattern US/UK/EU/CA/AU merchant, customers mostly in same region HubSpot Payments native ✓ US/UK/EU merchant, occasional international cards HubSpot Payments + accept the 5-6% cross-border ✓ Single-PSP team already on Stripe, customers in Stripe-supported countries HubSpot + Stripe native integration ✓ GoCardless user, SEPA/BACS focus HubSpot + GoCardless native ✓ Customers in Latin America, India, SEA, Africa, ME Multi-PSP layer (Shuttle) or orchestrator (Primer / Gr4vy) ✓ Cross-border B2B with high invoice values Multi-PSP with open banking on supported corridors ✓ Marketplace / platform with global merchants Multi-PSP, possibly Commerce Hub Enterprise + custom workflow ✓ Merchant incorporated outside US/UK/EU/CA/AU Can't use HubSpot Payments -- third-party only ✓ ## Implementation Notes for Non-Standard Currencies For HubSpot Commerce Hub teams adding non-standard currencies via Pattern 3, three workflow patterns: 1. Native HubSpot multi-currency on the deal record. Commerce Hub Professional+ supports multi-currency at the deal level. Configure the additional currencies, set FX rates (manual or auto), and HubSpot will store the deal value in the chosen currency. This is the display layer -- it doesn't change what currency the customer pays in. 2. Workflow-triggered payment link generation in the deal's currency. When a deal moves to a payment-required stage, a HubSpot workflow calls your payment orchestrator's API with the deal currency. The orchestrator generates a payment link denominated in that currency, routed to a processor with local acquiring. The link is inserted into the invoice or email automatically. 3. Multi-currency reconciliation back to HubSpot. Webhook from the orchestrator returns: payment status, transaction currency, settlement currency, FX rate applied, fees deducted, processor used. HubSpot's deal record is updated with all of these so finance can reconcile from inside HubSpot. The setup is typically 1-2 days of integration work for a team that already has HubSpot Operations Hub and basic workflow experience. ## Frequently Asked Questions Does HubSpot accept international credit cards? Yes for payment -- a card issued anywhere can pay a HubSpot Payments invoice as long as the card brand is Visa, Mastercard, or American Express and the customer is willing to be charged in your supported currency. Expect a +1.5% cross-border fee and higher decline rates on international cards. Can I charge customers in their local currency through HubSpot? Not natively through HubSpot Payments. HubSpot Payments only settles in USD, GBP, EUR, CAD, AUD. Local-currency presentation requires a third-party processor integration (Stripe for 135+ currencies, multi-PSP orchestration for 210+ countries with local acquiring). Which countries can use HubSpot Payments as a merchant? United States, United Kingdom, most EU countries, Canada, Australia. Merchants in Latin America, Asia (outside enterprise contracts), Africa, and the Middle East need a third-party processor. What's the cross-border fee on HubSpot Payments? Typically 1.5% on top of standard rates, levied when a non-domestic card pays your invoice. Combined with FX and standard fees, all-in cost on international cards is typically 5-6% in the US. Can I use HubSpot Commerce Hub with Stripe instead of HubSpot Payments? Yes. HubSpot has a native Stripe integration that routes Commerce Hub payment links to your Stripe account at Stripe's standard rates. You keep HubSpot CRM and workflow attachment; you avoid HubSpot Payments' fee markup. How do I accept Pix, UPI, M-Pesa, or other local payment methods in HubSpot? HubSpot Payments doesn't support these directly. You need a multi-PSP integration via a payment orchestrator. The orchestrator handles local payment method presentation, processing, and reconciliation back to HubSpot via webhook. Does HubSpot support multi-currency on a single deal? Yes, on Commerce Hub Professional+. The deal record displays in the chosen currency and HubSpot tracks FX. Whether the *payment* happens in that currency depends on your processor configuration -- see the implementation patterns above. ## Related Reading - HubSpot Payment Links: Complete 2026 Guide - HubSpot Commerce Hub Transaction Fees - Best Payment Link Providers 2026 - Payment Orchestration vs Payment Layer - White-Label Payment Links ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Global Payments: International Solutions for Business ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [HubSpot Payment Links: Complete 2026 Guide](/guides/hubspot-payment-links/) - [HubSpot Commerce Hub Transaction Fees](/guides/hubspot-commerce-hub-transaction-fees/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [Book a Call](/discovery/) - [BlogGlobal Payments: International Solutions for Business→](/blog/global-payments-for-online-and-offline-businesses/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/hubspot-payment-gateway/ --- # HubSpot Payment Gateway Integration: Every Option Compared (2026) | Shuttle > HubSpot Commerce Hub ships with HubSpot Payments as the default gateway -- but it's not the only option. # HubSpot Payment Gateway Integration: Every Option Compared (2026) By Shuttle Team, May 11, 2026 HubSpot Commerce Hub ships with HubSpot Payments as the default gateway -- but it's not the only option. Native integrations with Stripe and GoCardless cover the most common alternatives, the HubSpot App Marketplace has 30+ payment connectors, and multi-PSP orchestrators sit on top of all of them. The question "what payment gateway should I use with HubSpot" has different answers depending on what you're optimising for: lowest transaction fees, broadest payment method support, international currency coverage, existing PSP relationships, or simplest setup. This guide covers every workable HubSpot payment gateway option in 2026, what each unlocks, and how to pick. ## Quick Answer - Native HubSpot gateways: HubSpot Payments (default), Stripe, GoCardless (in supported regions). - HubSpot App Marketplace gateway connectors: PayPal, Square, Authorize.Net, Adyen, Worldpay, Braintree, Checkout.com, Mollie, plus 20+ regional / niche providers. - Multi-PSP orchestrators: Shuttle, Primer, Gr4vy, Spreedly -- sit above multiple gateways, route per transaction. - Cheapest setup: HubSpot Payments (built-in, no configuration). - Cheapest transaction cost at volume: Direct PSP relationship via a multi-PSP orchestrator (you keep negotiated rates). - Best for most US/UK SMBs: HubSpot Payments or HubSpot + Stripe native. - Best for cross-border B2B: Multi-PSP orchestrator with HubSpot integration. ## What HubSpot Calls a "Payment Gateway" HubSpot uses "payment gateway", "payment integration", and "payment processor" somewhat interchangeably -- but they're different layers of the stack. Payment gateway: The piece that captures card details (or other payment method) on the checkout page and securely transmits them to the processor for authorisation. Examples in HubSpot context: Stripe Checkout, HubSpot Payments hosted checkout, PayPal's checkout iframe. Payment processor / acquirer: The bank-adjacent entity that routes the authorisation to card networks and settles funds. Examples: Stripe (gateway + processor), Adyen (gateway + processor), Worldpay (processor), Chase Merchant Services (acquirer). Payment orchestrator: Sits above multiple gateways/processors and routes transactions across them. Examples: Shuttle, Spreedly, Primer, Gr4vy. HubSpot Commerce Hub's "payment integration" is really about the gateway layer -- what captures the payment on your behalf. The processor underneath is determined by which gateway you choose. This guide uses "gateway" loosely (matching HubSpot's terminology) but each section is explicit about which layers are involved. ## Tier 1: Native HubSpot Gateway Integrations Three gateways are integrated natively into HubSpot Commerce Hub -- meaning HubSpot built and maintains the integration, and the gateway shows up directly in Commerce Hub settings rather than as a third-party app. ### HubSpot Payments The default. HubSpot is the merchant of record, processing transactions through their underlying processor agreement. - Rates: 2.9% + $0.30 (US cards), 1.9% + £0.20 (UK), 0.5% capped at $5 (ACH, US only). See HubSpot Commerce Hub transaction fees for the full breakdown. - Currencies: USD, GBP, EUR, CAD, AUD only. - Setup: Zero config -- built into Commerce Hub. - Best for: SMBs in supported markets with simple invoicing needs and low international exposure. - Worst for: International merchants, high-volume B2B, anyone with an existing PSP relationship. ### Stripe (native HubSpot integration) HubSpot has a deep native Stripe integration that routes Commerce Hub payment links to your Stripe account instead of HubSpot Payments. - Rates: Your direct Stripe rates (2.9% + $0.30 US standard, often lower with volume). No HubSpot markup. - Currencies: 135+ via Stripe's coverage. - Local payment methods: Apple Pay, Google Pay, Klarna, Affirm, iDEAL, Bancontact, SEPA, BACS, and ~40 others depending on region. - Setup: Connect Stripe in Settings → Commerce → Connected accounts. 5-10 minutes. - Best for: Teams already on Stripe who want CRM-attached payment links without HubSpot Payments' markup. - Trade-offs: Single-PSP -- you can't route across multiple processors. Stripe-branded checkout by default. ### GoCardless (native HubSpot integration, supported regions) GoCardless handles bank-to-bank direct debit -- BACS (UK), SEPA (EU), ACH (US, in beta), PAD (Canada). - Rates: ~1% of transaction value, capped (varies by region and plan). - Best for: Recurring B2B billing, subscriptions where customers prefer direct debit over cards, high-value invoices where 1% beats 2.9%. - Trade-offs: Direct debit takes 3-5 working days to clear (cards are instant). Doesn't replace card acceptance -- sits alongside. ### Combined native setup Many HubSpot teams run all three: - HubSpot Payments for one-off invoices and SMB customers - Stripe for ecommerce-style checkout with local payment methods - GoCardless for recurring B2B subscriptions HubSpot Commerce Hub Pro+ supports multiple connected payment accounts simultaneously, with different gateways selected per workflow or deal type. ## Tier 2: HubSpot App Marketplace Gateway Connectors Beyond the natively integrated gateways, the HubSpot App Marketplace hosts 30+ payment connectors built by gateway providers or third-party developers. Quality varies -- read reviews and check the install count before committing. Strong marketplace connectors: - PayPal -- official PayPal app, handles PayPal Checkout, Venmo (US), PayPal Pay Later. - Square -- for HubSpot users with existing Square POS. - Authorize.Net -- common for US merchants on traditional acquirer relationships. - Adyen for HubSpot -- for enterprise merchants using Adyen as primary processor. - Worldpay -- UK merchant accounts via Worldpay (FIS). - Braintree -- owned by PayPal, often used for marketplace-style platforms. - Checkout.com -- strong for cross-border merchants in EMEA. - Mollie -- European focus, strong local payment method support. Regional / niche: - Razorpay (India), MercadoPago (LATAM), Paystack (Africa), iyzico (Turkey), PayMongo (Philippines), PayU (LATAM/India/Africa), and more. What marketplace connectors typically do: - Generate payment links from HubSpot triggers - Embed checkout iframes in HubSpot CMS pages - Send payment status back to HubSpot via webhook - Attach payment data to deals/contacts What they typically don't do: - Replace HubSpot Payments entirely on the native payment link feature - Route across multiple gateways (single-PSP only) - Provide white-label / your-domain checkout For most HubSpot teams, marketplace connectors are how you add support for a payment method or processor that isn't natively integrated. They sit alongside HubSpot Payments rather than replacing it. ## Tier 3: Multi-PSP Orchestrators (Beyond Single-Gateway) The third pattern: instead of picking one gateway, sit a payment orchestrator above multiple gateways and route each transaction to the best processor for that specific transaction's characteristics (currency, country, card BIN, transaction value). What an orchestrator does in a HubSpot stack: - Sits between HubSpot Commerce Hub and 40+ underlying gateways (Stripe, Adyen, Worldpay, Braintree, regional processors) - HubSpot workflow generates a payment link via the orchestrator's API - Orchestrator picks the best processor per transaction (lowest fees, best decline rates, local acquiring) - Customer pays on a white-label checkout (your domain, your branding) - Webhook returns to HubSpot with full transaction data Examples of orchestrators with HubSpot integration paths: - Shuttle -- 40+ underlying processors, 210+ countries, white-label, designed for platform-style use cases - Primer -- enterprise focus, strong workflow / no-code routing rules - Gr4vy -- cloud-native orchestration, modern API - Spreedly -- tokenisation-first orchestrator, common with subscription businesses When orchestrators make sense: - Cross-border B2B with customers in 20+ countries - High volume where 0.3-0.5% in fee savings exceeds the orchestrator's monthly fee - Multi-brand / multi-entity merchants needing different processor relationships per brand - Platforms reselling payments to their merchants When they don't: - SMB single-country merchants with under $100k/month processed - Teams without engineering capacity to maintain the integration - Cases where HubSpot Payments' simplicity is the actual value, not the rate ## Picking Your HubSpot Payment Gateway A decision tree that maps to the question "what payment gateway should I use with HubSpot?" Are you a HubSpot SMB customer in the US/UK/EU/CA/AU, with simple invoicing needs and customers in your home market? → HubSpot Payments. Don't overthink it. The convenience is worth the markup. Do you already have a Stripe account with negotiated rates? → HubSpot + Stripe native integration. You keep your Stripe rates and add HubSpot CRM attachment for free. Are you doing recurring B2B billing where direct debit is preferred over cards? → HubSpot + GoCardless (BACS/SEPA/PAD/ACH) for recurring; HubSpot Payments for one-offs. Do you have a specific gateway requirement (existing Adyen / Worldpay / Braintree / Checkout.com relationship)? → HubSpot App Marketplace connector for that gateway. Verify the connector quality before committing. Do you have customers in Latin America, Asia, Africa, or the Middle East? → HubSpot Payments will fail you on currency support. Multi-PSP orchestrator or regional marketplace connector (Razorpay, MercadoPago, Paystack, etc.). Are you processing >$500k/month? → Multi-PSP orchestrator. The savings on transaction fees from PSP routing typically pay back the integration in 2-4 months. Are you a platform or marketplace reselling payments to your own merchants? → Multi-PSP orchestrator with white-label support. HubSpot's branding controls won't go far enough; you need full white-label. ## Side-by-Side Comparison Headline Fee Currencies Setup Effort 2.9% + $0.30 (US) SMB, US/UK/EU/CA/AU None -- built in Stripe native Stripe rate, no markup Stripe users, ecommerce GoCardless native ~1% capped BACS/SEPA/ACH Recurring B2B PayPal (Marketplace) 2.9-3.5% + $0.30 PayPal-preferred customer base Adyen (Marketplace) Enterprise pricing Enterprise, cross-border Worldpay (Marketplace) Negotiated UK/EU, traditional acquirer fit Razorpay, MercadoPago, Paystack, etc. Local rates Local + global Regional markets Shuttle (payment layer) Your PSP rates, no markup 210+ countries Cross-border, platforms, mid-large volume Primer / Gr4vy / Spreedly Enterprise orchestration ## Common HubSpot Payment Gateway Questions What payment gateway does HubSpot use by default? HubSpot Payments -- HubSpot's own merchant-of-record processor. You can replace it with Stripe, GoCardless, or any of 30+ App Marketplace connectors. Can I use Stripe with HubSpot? Yes -- HubSpot has a native Stripe integration that routes Commerce Hub payment links to your Stripe account at Stripe's direct rates. No HubSpot fee markup. Setup is 5-10 minutes in Settings → Commerce → Connected accounts. Does HubSpot work with PayPal? Yes, via the HubSpot App Marketplace PayPal connector. PayPal Checkout becomes an option alongside or instead of HubSpot Payments. Not as deeply integrated as Stripe but sufficient for adding PayPal as a payment method. Can I use multiple payment gateways in HubSpot? Yes on Commerce Hub Pro+. You can connect HubSpot Payments + Stripe + GoCardless simultaneously and route different workflows/deals to different gateways. For routing across many more gateways or doing intelligent per-transaction routing, you need a multi-PSP orchestrator. What's the best payment gateway for HubSpot Sales Hub? For most SMBs the answer is HubSpot Payments or HubSpot + Stripe. Sales Hub customers who already use a specific PSP for their company-wide billing typically integrate that PSP via the App Marketplace or via a workflow-triggered API integration. Does HubSpot integrate with Adyen? Yes, via the HubSpot App Marketplace. Adyen's HubSpot connector is built for enterprise customers using Adyen as their primary acquirer. For multi-PSP routing (Adyen + others), use a payment orchestrator. Can I switch payment gateways without disrupting my HubSpot data? Yes -- HubSpot stores payment data on the deal/contact record independent of the gateway. Switching gateways changes how new transactions are processed but historical transaction data, invoices, and deals are unaffected. Test the new gateway on a small subset of workflows before cutting over fully. ## Related Reading - HubSpot Payment Links: Complete 2026 Guide - HubSpot Commerce Hub Transaction Fees - HubSpot International Payments - HubSpot Payment Link Branding - Payment Orchestration vs Payment Layer - Best Payment Link Providers 2026 ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It ### HubSpot Payment Links: Setup, Integrations & Alternatives ### Insuretech Innovation: Choosing the Right Payment Gateway for Your Business ### Event Payment Gateway: How to Choose the Right One ### What Is a Payment Gateway? How It Works, Costs & Top Providers ### Payment Gateway Integration: How to Add Payments to Your App or Platform ## Links - [HubSpot Commerce Hub transaction fees](/guides/hubspot-commerce-hub-transaction-fees/) - [multi-PSP orchestrator](/guides/payment-orchestration-vs-payment-layer/) - [HubSpot Payment Links: Complete 2026 Guide](/guides/hubspot-payment-links/) - [HubSpot Commerce Hub Transaction Fees](/guides/hubspot-commerce-hub-transaction-fees/) - [HubSpot International Payments](/guides/hubspot-international-payments/) - [HubSpot Payment Link Branding](/guides/hubspot-payment-link-branding/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [Book a Call](/discovery/) - [BlogPayment Gateway Aggregation: What It Is and Why SaaS Platforms Need It→](/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/) - [BlogHubSpot Payment Links: Setup, Integrations & Alternatives→](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [BlogInsuretech Innovation: Choosing the Right Payment Gateway for Your Business→](/blog/insuretech-innovation-choosing-the-right-payment-gateway-for-your-business/) - [BlogEvent Payment Gateway: How to Choose the Right One→](/blog/choosing-the-right-payment-gateway-for-your-event-software-a-comprehensive-guide/) - [BlogWhat Is a Payment Gateway? How It Works, Costs & Top Providers→](/blog/what-is-a-payment-gateway/) - [BlogPayment Gateway Integration: How to Add Payments to Your App or Platform→](/blog/the-ultimate-guide-to-integrating-a-payment-gateway-into-your-app/) --- URL: https://www.shuttleglobal.com/guides/hubspot-payment-link-branding/ --- # HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) | Shuttle > HubSpot Commerce Hub payment links carry HubSpot branding by default -- a generic checkout page on a HubSpot subdomain, with a "Powered by HubSpot... # HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide) By Shuttle Team, May 10, 2026 HubSpot Commerce Hub payment links carry HubSpot branding by default -- a generic checkout page on a HubSpot subdomain, with a "Powered by HubSpot Payments" footer. For B2B sellers, agencies, and high-value transactions, that default checkout works against the trust signal the rest of the buyer journey worked to build. The good news: HubSpot supports progressively deeper branding as you move up Commerce Hub tiers, and full white-label is achievable through a third-party integration. The bad news: most of the meaningful branding controls -- custom domain, full checkout customisation, branded receipts -- sit behind Commerce Hub Professional or above. This guide covers exactly what branding controls each Commerce Hub tier unlocks, how to configure them, and how to go beyond HubSpot's native limits when the in-platform branding isn't enough. ## Quick Answer - Logo + colours on payment links: Available on all Commerce Hub tiers including Starter (~$20/seat/month). - Custom subdomain (e.g. `pay.yourcompany.com`): Commerce Hub Professional+ (~$1,200/month). - Custom checkout fields and flow: Commerce Hub Professional+ with workflow customisation. - Fully white-labeled checkout on your own domain: Not available natively -- requires a third-party payment link provider with white-label support. - Branded receipts and emails: Yes natively, on Starter+. - What ranks in Google for "custom payment link branding HubSpot": Real configuration documentation is sparse -- most published content is HubSpot's own marketing. This guide covers what actually configurable and what isn't. ## What HubSpot Branding Controls Are Available by Tier ### Free Commerce Tools (with HubSpot Free CRM) - Your company name on the checkout page ✓ - Default HubSpot checkout layout (no custom layout) ✗ - HubSpot subdomain on the URL (e.g. ) ✗ - "Powered by HubSpot Payments" footer present ✗ Free tier is fine for testing but the checkout looks like a HubSpot test environment. Not for production B2B. ### Commerce Hub Starter (~$20/seat/month) - Your logo on the checkout ✓ - Brand colours (primary, accent) ✓ - Custom business name and contact details ✓ - Branded confirmation email and receipt ✓ - HubSpot subdomain still on the URL ✗ Adequate for most SMB invoicing. Customers see your logo and colour scheme but the URL gives away that it's a HubSpot-hosted checkout. ### Commerce Hub Professional (~$1,200/month) Everything in Starter, plus: - Custom subdomain -- or similar, pointed at HubSpot's checkout via DNS CNAME - Custom email sender domain for invoice and receipt emails - Workflow-driven payment link generation -- different branding per workflow / deal type / customer segment - Branded customer portal for self-service subscription management - "Powered by HubSpot Payments" footer can be removed (check current tier docs) - More customisable checkout page layout (limited templating, not full HTML control) Professional is where HubSpot's branding becomes acceptable for serious B2B. The custom subdomain in particular makes the checkout feel like part of your domain rather than a HubSpot product. ### Commerce Hub Enterprise (~$3,200/month) Everything in Professional, plus: - Single sign-on on the customer portal for repeat buyers - Custom field types on the checkout (beyond HubSpot's standard set) - Audit logs for branding changes (compliance use case) - Sandbox environment for testing branding changes before production Enterprise pricing rarely justifies itself for branding alone -- most teams pay for Enterprise for workflow approvals, audit, and SSO. Branding controls are a bonus. ## How to Configure HubSpot Payment Link Branding (Step by Step) For Commerce Hub Starter+ setups, the basic branding configuration: - Settings → Commerce → Payment configuration - Upload your logo (PNG/SVG, recommended 200×60px) - Set primary and accent colours (hex codes) - Add business name, support email, support phone - Enable / disable HubSpot Payments footer (Pro+) - Settings → Commerce → Invoices - Configure the default invoice template - Set sender name and email - Enable the "Pay Now" button visibility - Map the button colour to your primary brand colour - Settings → Marketing → Email → Templates - Customise the payment confirmation email - Customise the receipt email - Set the sender domain (requires DNS records on Pro+) - Settings → Account → Domains (Professional+ only) - Add your custom subdomain (e.g. ) - Configure the DNS CNAME record per HubSpot's instructions - Wait for SSL provisioning (typically 1-24 hours) - Verify the subdomain serves the payment checkout The whole setup takes 30-60 minutes if your DNS access is sorted and your brand assets are ready. ## What HubSpot Native Branding Doesn't Cover Five gaps regularly come up when teams reach the limit of HubSpot's in-platform branding. 1. The URL still says "checkout.hubspot.com" without Professional. Even with full Starter branding, the URL is on a HubSpot domain. B2B finance teams sometimes flag this as a phishing risk -- your beautifully branded payment page is on a third-party domain they don't recognise. Custom subdomain (Pro+) solves this if the customer notices the URL bar. 2. Layout customisation is template-bound. You can pick from a small set of HubSpot-provided templates and customise colours/logos within them. You can't materially restructure the checkout -- add custom fields above the card entry, embed a video, change the flow from one-page to multi-step, etc. 3. Receipt and invoice PDF branding is limited. The PDF templates HubSpot generates support logo and basic colour customisation but not full layout control. Agencies, accountants, and others who care about the precise look of the invoice PDF often supplement HubSpot with a separate invoicing tool. 4. "Powered by HubSpot Payments" persists at lower tiers. The footer message remains on Starter and Free tiers. Removing it requires Pro+. 5. White-label means "your logo on HubSpot's product" -- not your product. Even with all controls maxed out, the experience is HubSpot's product styled to look like yours. For platforms reselling payments to their own customers (the actual white-label use case), this isn't enough -- your customers shouldn't ever land on a HubSpot URL. ## Going Beyond HubSpot's Native Branding For teams that need full white-label -- payments on your own domain, your own checkout flow, your own receipt format -- the answer is a third-party payment link provider integrated with HubSpot via API and workflow triggers. Two patterns make this work. ### Pattern A: Embed external payment links in HubSpot The simpler version. Your payment link provider generates a unique URL per invoice/deal via API, and a HubSpot workflow inserts that URL into the email / invoice template instead of the native HubSpot payment link. What this unlocks: - Full control of the checkout -- your domain, your layout, your fields - Custom flows like deposit-then-balance, instalments, donations, multi-amount - Multi-PSP routing under the hood - Your branding on the receipt and follow-up emails What stays HubSpot: - The deal/contact record, CRM workflow, automation, reporting Setup complexity: Low-medium. Most modern payment link providers have direct HubSpot connectors (in the App Marketplace) or are 1-2 hours via the API. ### Pattern B: Iframe a custom checkout inside HubSpot pages For teams that want the payment experience embedded inside a HubSpot CMS page -- say, a custom landing page with form + payment in one flow -- the payment link provider's checkout iframe drops directly into the HubSpot page. Customer never leaves the HubSpot domain; the iframe loads from your payment provider but the surrounding chrome is yours. Trade-offs: PCI scope considerations -- depending on the integration mode, the iframe approach can keep the merchant in SAQ A (cleanest). Confirm with your provider that the integration is SAQ A eligible. See PCI compliance service provider guide for the scope-reduction implications. ### Pattern C: Full white-label with Shuttle For teams that need payments on their own domain (e.g. ) with full HubSpot CRM attachment: - Domain & branding: Checkout served from your domain via white-label DNS configuration - Receipt and email: Sent from your sender domain with your branding - Checkout customisation: Custom fields, custom flows, custom payment method ordering - HubSpot attachment: Webhook back to HubSpot with full transaction data - Multi-PSP under the hood: Route across 40+ processors based on currency, country, transaction value Setup is typically 1-2 days including DNS, SSL, and the HubSpot workflow integration. ## Side-by-Side: HubSpot Native vs Third-Party White-Label Branding control Free/Starter Pro/Enterprise Stripe via HubSpot Shuttle via HubSpot Your logo on checkout Your colours on checkout Custom subdomain ✗ (Stripe domain) Full custom domain (e.g. checkout.yourcompany.com) Layout customisation Custom checkout fields Custom receipt/email Limited (Stripe-branded) Remove "Powered by..." HubSpot CRM attachment ✓ (via webhook) ## When HubSpot Native Branding Is Enough Most teams overthink this. HubSpot's Pro-tier branding (logo, colours, custom subdomain) is sufficient for: - B2B invoicing where customers already know your business and trust the relationship - Agency client payments where the agency name is on the invoice - Recurring SaaS billing where the brand is already established - E-commerce where conversion data shows no impact from the subdomain Where it falls short: - Marketplaces reselling payments to merchants under the marketplace's brand - Platforms embedding payments as a product feature - High-trust transactions (escrow, large B2B, regulated industries) where any third-party domain triggers questions - Cross-currency or international flows that need bank-grade trust signals on the checkout ## Frequently Asked Questions Can I add my logo to HubSpot payment links? Yes -- on Commerce Hub Starter and above. Settings → Commerce → Payment configuration. Logo + colours apply across all HubSpot payment links generated from that account. How do I get a custom domain on my HubSpot payment links? Commerce Hub Professional or Enterprise is required. Configure under Settings → Account → Domains with a DNS CNAME pointing your subdomain (e.g. ) at HubSpot's checkout host. SSL provisioning takes 1-24 hours. Can I remove the "Powered by HubSpot Payments" footer? Yes, on Commerce Hub Professional+. On Starter and Free tiers the footer remains. What's the most customisable HubSpot checkout option? HubSpot's native customisation tops out at logo, colours, and custom subdomain. For checkout layout, custom fields, and full white-label flows, you need a third-party payment link provider integrated with HubSpot. Does HubSpot support white-label payment links for resellers? Not natively -- HubSpot Commerce Hub branding is for the merchant using HubSpot, not for resellers of HubSpot. For reseller / marketplace scenarios, use a white-label payment link provider integrated with HubSpot CRM. How much does HubSpot Commerce Hub Professional cost? Approximately $1,200/month as of 2026 (check HubSpot's pricing page for current figures). It unlocks custom subdomain, custom email sender, workflow-driven payment link generation, and branded customer portal. ## Related Reading - HubSpot Payment Links: Complete 2026 Guide - HubSpot Commerce Hub Transaction Fees - HubSpot International Payments - White-Label Payment Links - Best Payment Link Providers 2026 ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### HubSpot Payment Links: Setup, Integrations & Alternatives ### How to Launch a Payment Link Feature in Weeks, Not Months ### Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ## Links - [third-party payment link provider](/guides/best-payment-link-providers/) - [PCI compliance service provider guide](/guides/pci-compliance-service-provider/) - [white-label payment link provider](/guides/white-label-payment-links/) - [HubSpot Payment Links: Complete 2026 Guide](/guides/hubspot-payment-links/) - [HubSpot Commerce Hub Transaction Fees](/guides/hubspot-commerce-hub-transaction-fees/) - [HubSpot International Payments](/guides/hubspot-international-payments/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [Book a Call](/discovery/) - [BlogHubSpot Payment Links: Setup, Integrations & Alternatives→](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [BlogHow to Launch a Payment Link Feature in Weeks, Not Months→](/blog/how-to-launch-a-payment-link-feature-in-weeks-not-months/) - [BlogPayment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending→](/blog/payment-links-for-payu/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) --- URL: https://www.shuttleglobal.com/guides/hubspot-payment-links/ --- # HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) | Shuttle > HubSpot Payment Links -- What's Available, and What's Missing HubSpot has steadily added payment functionality over the last few years. # HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide) By Shuttle Team, April 27, 2026 ## HubSpot Payment Links -- What's Available, and What's Missing HubSpot has steadily added payment functionality over the last few years. Today there are three ways to take payments through HubSpot: native HubSpot Payments, HubSpot Commerce Hub payment links, and third-party integrations via HubSpot's marketplace, Zapier, or Make.com. Each has its own trade-offs around supported gateways, transaction fees, branding, and international support. This guide covers what each option does, when each is the right fit, and how to use any payment gateway you want with HubSpot -- including Stripe, Adyen, Worldpay, Checkout.com, Mollie, and 25+ others. ## Quick Answer: Does HubSpot Allow Creating Custom Payment Links? Yes -- but with limits depending on which HubSpot product you have. - HubSpot Payments (US-only) lets you create payment links that take card and ACH, but it only processes payments through HubSpot's own Stripe-powered system. No alternative gateway, no international card processing outside the US. - HubSpot Commerce Hub (a paid add-on on Sales Hub Professional+) lets you create custom payment links with your own logo and basic branding. It handles invoices, recurring billing, and quotes. Underneath, it still runs on Stripe (or HubSpot Payments in supported regions). - Third-party integration via Shuttle + Zapier/Make.com lets you use any of 30+ payment gateways, full custom branding, support international cards via local PSPs, and choose your own transaction fees. If you're a UK, EU, or non-US merchant, or you want to use a specific gateway (Adyen, Worldpay, Checkout.com, Mollie), the third-party route is usually the right call. ## Option 1: HubSpot Payments (US-Only) HubSpot Payments is HubSpot's own payment product, available to US-based merchants. You connect your bank account directly and HubSpot becomes the merchant of record. Card payments are powered by Stripe under the hood. ### What you get - Payment links sendable from quotes, invoices, deals, or directly from a contact record - ACH and card payment support - Automatic reconciliation against the contact and deal record - HubSpot-branded checkout (limited customisation) ### Transaction fees HubSpot Payments charges 2.9% + $0.30 per card transaction and 0.5% + $0.30 per ACH transaction (capped at $5). These are competitive for US merchants but typical of US-domestic gateways. ### Limitations - US-only at time of writing - No alternative payment gateway support - Limited checkout branding (HubSpot logo on the page) - No international card processing through local PSPs (Adyen, Worldpay, Mollie) - No support for non-card payment methods like SEPA Direct Debit, BACS, BLIK, iDEAL, Bancontact ### When it's the right fit US-based merchants with simple payment needs, where the convenience of native HubSpot integration outweighs the lack of gateway choice. ## Option 2: HubSpot Commerce Hub HubSpot Commerce Hub is a paid add-on (sits on Sales Hub Professional or Enterprise) and gives you a richer commerce toolset. It includes payment links, invoices, recurring billing, quotes-to-payment, and subscription management. - Custom payment links with your logo and basic colour customisation - Invoice and quote payment links bundled with the document - Recurring billing (subscriptions) with native dunning - Reporting on payment status, MRR, and revenue across the commerce funnel Commerce Hub uses HubSpot Payments or Stripe Connect underneath. The fees are the same as Option 1 (2.9% + $0.30 for card) plus the cost of Commerce Hub itself, which sits on top of Sales Hub Professional ($90/month/seat starting price). - Still tied to Stripe / HubSpot Payments - US-first (international support is improving but partial) - Branding is "your logo on a HubSpot-branded page", not a fully custom checkout - Limited support for region-specific payment methods US merchants on Sales Hub Professional+ who want subscriptions, recurring billing, and a unified commerce dashboard inside HubSpot. ## Option 3: Third-Party Integration via Shuttle + Zapier or Make.com This is the most flexible route and the only option if you need: - A payment gateway other than Stripe (Adyen, Worldpay, Checkout.com, Mollie, Braintree, Square, GoCardless, etc.) - International card processing through a local PSP - Region-specific payment methods (SEPA Direct Debit, BACS, iDEAL, Bancontact, BLIK, Apple Pay, Google Pay) - Fully custom checkout branding (your logo, colours, page design -- not a HubSpot-branded page) - Multi-PSP support for different markets or merchant accounts - Payment links that work outside HubSpot too (Slack, WhatsApp, SMS) using the same Shuttle account ### How it works Shuttle Links Checkout connects to HubSpot via Zapier or Make.com. The integration is no-code -- your ops team builds it in an afternoon. The basic flow: - Trigger -- a HubSpot deal moves to a particular stage, an invoice is sent, a quote is accepted, or a custom property changes - Generate -- Zapier or Make.com calls Shuttle to create a payment link with the deal's value, customer email, and any metadata you want to track - Deliver -- the link is delivered to the customer via HubSpot's email tool, SMS via Twilio, Slack, or any of Zapier/Make's connected channels - Sync back -- when the payment is captured, a webhook fires that updates the HubSpot record with the paid status, posts to Slack, and creates an invoice in your accounting tool ### Supported payment gateways The full Shuttle gateway list is available regardless of which workflow tool you use: - Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, GoCardless, PayPal, Paysafe, Global Payments, FreedomPay, Authorize.Net, USAePay, Trust Payments, and 15+ more You can switch PSP without rebuilding the HubSpot integration. The Shuttle side abstracts the gateway, so the same Zap or scenario runs against whichever PSP you have configured. Transaction fees are whatever your chosen PSP charges. For UK and European merchants, this typically means: - Worldpay: 0.4-1.5% depending on volume and card type - Adyen: ~0.5% + interchange (interchange++) - Checkout.com: blended pricing from ~1.4% - Stripe via Shuttle: standard Stripe rates - Mollie: 1.8% + €0.25 for European cards Shuttle doesn't add a markup on payment processing -- you pay your PSP directly. ### Branding Full custom branding. Your logo, your colours, your URL on a hosted checkout page that looks like part of your brand. Mobile-first, optimised for conversion. No HubSpot logo or HubSpot branding on the customer-facing checkout. - Non-US merchants - Merchants with an existing PSP relationship (Adyen, Worldpay, Checkout.com) - Merchants who want full control over checkout branding - Multi-region operations (different PSPs for different markets) - Anyone who wants payment links that work consistently across HubSpot, Slack, WhatsApp, and SMS ## Common HubSpot Payment Link Workflows These are the patterns we see most often when teams use Shuttle with HubSpot: ### Deal stage change → payment link When a deal moves to "Closed Won" (or any custom stage like "Awaiting Payment"), a Zapier or Make.com workflow generates a Shuttle payment link with the deal's value and customer email. The link is sent through HubSpot's email tool with merge fields, so it looks like a standard email from your sales rep. ### Quote accepted → deposit collected When a HubSpot quote is accepted by the prospect, generate a payment link for the agreed deposit (typically 25-50% of total). Cuts the gap between "yes" and "deposit paid" from days to minutes. ### Invoice sent → payment link attached When you send a HubSpot invoice, attach a Shuttle payment link as a CTA in the same email. Customer pays with one tap on their phone. The payment outcome syncs back to HubSpot, marking the invoice as paid automatically. ### Renewal date approaching → payment link sent A workflow runs 7 days before a contract renewal date. Generates a payment link for the renewal amount, sends it to the customer with a "your renewal is coming up" message. Conversion is far higher than waiting for the customer to action the renewal themselves. ### Custom property change → payment link Any HubSpot property change can trigger a payment link. "Outstanding balance" becomes greater than zero -- send a link. "Late fee applied" toggles to true -- send a link with the fee included. ## HubSpot Sales Hub vs HubSpot Commerce Hub: Which Do You Need? The question we get most often is: do you need Commerce Hub to take payments through HubSpot? The honest answer is no, not necessarily. ### You need Commerce Hub if: - You want HubSpot-native subscriptions, recurring billing, and dunning - You want a unified commerce dashboard inside HubSpot for revenue reporting - You're on Sales Hub Professional+ and have the budget for the add-on - US merchant where Stripe-via-HubSpot is the right gateway ### You don't need Commerce Hub if: - You want to use a non-Stripe gateway (Adyen, Worldpay, Checkout.com, Mollie) - You're a UK, EU, or non-US merchant - You want fully custom checkout branding - You'd rather build the workflow in Zapier or Make.com (cheaper, more flexible) - You only need transactional payment links (one-off, not subscriptions) For most non-US merchants, the Shuttle + Zapier/Make.com route is a better fit than Commerce Hub. You get more gateway choice, full branding control, and lower per-transaction cost -- at the price of building the workflow yourself (which takes about an afternoon). ## Frequently Asked Questions ### Does HubSpot accept international credit cards? HubSpot Payments (US-only) processes international cards through Stripe's standard cross-border flow -- they work, but rates are higher (typically +1.5% on top of the base rate). For a better international rate, you can connect a local PSP (Adyen, Worldpay, Checkout.com) via Shuttle and process through them instead. UK and EU cards on a UK PSP cost ~0.4-1.5%; the same cards on cross-border Stripe cost 2.9%+. ### How much do HubSpot payment links cost in transaction fees? HubSpot Payments and HubSpot Commerce Hub charge 2.9% + $0.30 per card transaction (US standard rates). If you connect a third-party gateway via Shuttle, fees are whatever your PSP charges -- typically 0.4-1.8% depending on the PSP, card type, and volume. Shuttle doesn't add a markup; you pay your gateway directly. ### Can I customise the HubSpot payment link checkout page? HubSpot Commerce Hub allows your logo and basic colour on the checkout page, but the page is HubSpot-branded underneath. For fully custom checkout branding (your URL, your colours, your design, no HubSpot logo), use Shuttle Links Checkout via Zapier or Make.com integration. ### Can I create custom payment links from HubSpot deals? Yes -- both via HubSpot's native tools and via the third-party route. HubSpot Commerce Hub lets you generate links from deals directly. Shuttle + Zapier/Make.com lets you trigger links from any HubSpot stage change, custom property change, or workflow event with full flexibility on amount, description, currency, and metadata. ### Does HubSpot integrate with Stripe directly? Yes, but with caveats. HubSpot Commerce Hub uses Stripe Connect internally, so any Commerce Hub merchant is on Stripe by default. For a more flexible Stripe integration where you keep your own Stripe account separate from HubSpot, use the Stripe + HubSpot integration via Zapier or Make.com -- or use Shuttle as the middle layer if you want to add other gateways alongside Stripe. ### Can I use PayPal with HubSpot payment links? PayPal is supported through Shuttle's Braintree integration (Braintree is the PayPal-owned PSP). Connect Braintree to your Shuttle account, build the HubSpot trigger via Zapier or Make.com, and customers can pay by PayPal Wallet, Pay Later, or card on the Shuttle hosted checkout. No direct PayPal integration is available natively in HubSpot Payments or Commerce Hub. ### What happens to the payment in HubSpot after the customer pays? If you use HubSpot Payments or Commerce Hub, the payment is automatically logged against the contact and deal record. If you use Shuttle via Zapier or Make.com, configure a "Payment Received" webhook that fires a Zap or scenario to update the HubSpot record (mark deal as paid, add a note, change a property). Both routes give you a clean record in HubSpot. ## Where to Start If you're a US merchant on Sales Hub Professional+ and want subscriptions, HubSpot Commerce Hub is the right starting point. The convenience of native integration outweighs the gateway lock-in for many US businesses. If you're a UK, EU, or non-US merchant -- or you have an existing PSP relationship you don't want to lose -- start with Shuttle + Zapier or Make.com. Build one workflow (CRM stage change → payment link) and see how much faster it converts than chasing invoices. Expand from there. Either way, start with one workflow, ship it in a day, and measure the time-to-payment uplift. The biggest mistake teams make is over-designing the payment system before it's connected to the CRM trigger that matters. ### Related guides - Payment workflow automation: Zapier vs Make.com vs Direct API - Shuttle + Zapier: how it works - Shuttle + Make.com: how it works - Best payment link providers (UK) - How to send payment requests ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### HubSpot Payment Links: Setup, Integrations & Alternatives ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ## Links - [Payment workflow automation: Zapier vs Make.com vs Direct API](/guides/payment-workflow-automation/) - [Shuttle + Zapier: how it works](/platforms/links-checkout/workflows/zapier/) - [Shuttle + Make.com: how it works](/platforms/links-checkout/workflows/make/) - [Best payment link providers (UK)](/guides/take-payments-online/best-payment-link-services-uk/) - [How to send payment requests](/guides/how-to-send-payment-requests/) - [Book a Call](/discovery/) - [BlogHubSpot Payment Links: Setup, Integrations & Alternatives→](/blog/boosting-conversions-how-to-use-payment-links-in-hubspot/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) --- URL: https://www.shuttleglobal.com/guides/ --- # Payment Guides for Platforms & SaaS | Shuttle > In-depth guides on payments infrastructure, voice payments, embedded payments, and platform payment strategy. Built for CTOs, product leaders, and payment teams. # Payment Guides In-depth guides on payments infrastructure, voice payments, embedded payments, and platform payment strategy. ## Taking Payments for Your Business Service Business Guides ### How to Take Payments Online The complete guide to collecting payments for service businesses -- compare every method. ### Send Payment Links Step-by-step guide to creating and sending payment links to customers. ### Phone Payments Take secure card payments over the phone -- PCI-compliantly. Quick answer: one global PSP is simpler to run and usually right until international volume becomes material in a... Quick answer: a virtual terminal is a browser-based payment form where a member of staff keys in a customer's card... Quick answer: taking card payments over the phone is fine under PCI DSS. What matters is how the card number travels.... Quick answer: agent-assisted payments keep a live agent on the call while the caller types their card number on their... Quick answer: IVR payments let callers pay through an automated keypad flow with no agent on the line. The caller keys... Quick answer: a medical billing company or RCM firm collects patient payments that belong to its client practices. That... Quick answer: if your business collects payments that belong to your clients, you need each payment to settle into that... Twilio Pay is Twilio's product for taking card payments over the phone. It is built into Twilio Voice as the ... There are two ways to charge a Stripe-connected card during a phone call (IVR, agent-assisted, or AI voice agent):... Twilio Pay Connectors are integrations that link Twilio's voice platform to a payment gateway, so you can capture card... If Twilio's verb just threw a 64xxx error at you, here's the thing to understand before you touch any code: these... The Twilio Stripe Pay Connector is Twilio's native integration between the verb and Stripe. It lets you capture... Quick answer: switching Twilio Pay Connectors is a one-attribute change. The connector is selected per-request by the... Quick answer: yes, you can take ACH payments over the phone. The caller keys their bank routing number and account... LiqPay doesn't natively connect to Twilio for voice payments. If you want to process LiqPay transactions during a phone... USAePay doesn't natively connect to Twilio for voice payments. If you want to process USAePay transactions during a... Twilio's Generic Pay Connector, generally available since 15 August 2023, lets you connect Twilio's verb to any... FreedomPay doesn't natively connect to Twilio for voice payments. If you want to process FreedomPay transactions during... PayU doesn't natively connect to Twilio for voice payments. If you want to process PayU transactions during a phone... Paysafe doesn't natively connect to Twilio for voice payments. If you want to process Paysafe transactions during a... CardConnect is one of the few gateways Twilio supports natively. Alongside Stripe, Braintree, Base Commerce, Chase... Opayo doesn't natively connect to Twilio for voice payments. If you want to process Opayo transactions during a phone... Moneris doesn't natively connect to Twilio for voice payments. If you want to process Moneris transactions during a... Braintree, PayPal's full-stack payment gateway, is one of the few PSPs that Twilio supports natively. Twilio launched a... NMI doesn't natively connect to Twilio for voice payments. If you want to process NMI transactions during a phone call... Cybersource doesn't natively connect to Twilio for voice payments. If you want to process Cybersource transactions... NAB doesn't natively connect to Twilio for voice payments. If you want to process NAB Transact transactions during a... Transbank doesn't natively connect to Twilio for voice payments. If you want to process Transbank transactions during a... Xendit doesn't natively connect to Twilio for voice payments. If you want to process Xendit card transactions during a... Ecommpay doesn't natively connect to Twilio for voice payments. If you want to process Ecommpay transactions during a... BS Payone (now branded PAYONE) doesn't natively connect to Twilio for voice payments. If you want to process PAYONE... Trust Payments doesn't natively connect to Twilio for voice payments. If you want to process Trust Payments... Fat Zebra doesn't natively connect to Twilio for voice payments. If you want to process Fat Zebra transactions during a... ACI Speedpay doesn't natively connect to Twilio for voice payments. If you want to process Speedpay transactions during... Fortis doesn't natively connect to Twilio for voice payments. If you want to process Fortis transactions during a phone... ACH is the cheapest way to get paid on a large invoice. Cards cost a percentage of every transaction, so a $10,000... Mollie doesn't natively connect to Twilio for voice payments. If you want to process Mollie transactions during a phone... If you run a software platform, you almost certainly built your own payment links. You are a tech company with... Shift4 doesn't natively connect to Twilio for voice payments. If you want to process Shift4 transactions during a phone... QuickBooks Payments doesn't natively connect to Twilio for voice payments. If you invoice from QuickBooks and want to... Lindy is a no-code AI agent builder that lets businesses create "AI employees": autonomous agents that handle email... Mitel is one of the most widely deployed enterprise telephony and unified communications platforms in the world. Its... Phonely is an AI phone answering platform for businesses. It answers inbound calls, books appointments, qualifies... Ada (ada.cx) is an enterprise AI customer service platform built around what the company calls Agentic Customer... Sierra (sierra.ai) is an enterprise conversational AI platform, an "AI Agent OS" that powers customer service agents... Gupshup is one of the world's leading conversational messaging platforms. It powers WhatsApp-first commerce and... Parloa is an AI Agent Management Platform for contact centres. Enterprise teams in financial services, utilities,... 3CX is an open-platform software PBX used by tens of thousands of businesses worldwide. It runs voice calls, live chat,... boost.ai is a Gartner-recognised leader in conversational AI for the enterprise, with a particularly strong footprint... Unlike most AI voice platforms, ElevenLabs Agents already has a native payment story. Its Stripe integration lets... Decagon is an enterprise omnichannel AI customer-service platform. Its agents handle voice, chat and email for contact... Content Guru is a UK enterprise CCaaS provider. Its storm platform powers mission-critical contact centre operations... Synthflow is a no-code platform for building AI voice agents, and unlike most of its peers it already has a native... Thoughtly is an AI voice, SMS, and email agent platform built for revenue and GTM teams. Businesses in insurance,... GoTo Connect is a cloud-based UCaaS platform built for SMB and mid-market businesses, combining business phone, video,... Kore.ai is an enterprise agentic and conversational AI platform used to build production AI agents across voice, chat,... Voiceflow is a no-code AI agent builder used by product teams, agencies, and enterprise developers to design and deploy... Bland AI is a platform for building AI phone agents that handle real conversations at scale, inbound and outbound, on... Yellow.ai is an enterprise agentic AI platform for customer and employee experience automation, used by large brands... Vapi is a developer platform for building voice AI agents. It combines speech recognition, an LLM, and text-to-speech... Regal.ai is a voice AI agent platform built for outbound contact: AI phone calls plus SMS and chat, with particular... UJET runs your contact centre. With its smartphone-first architecture, native cloud voice and IVR, web chat, SMS,... Gladly is an all-in-one, people-centred customer service platform built around the customer rather than the ticket. It... Policy administration systems are the operational heart of insurance carriers and MGAs. They underwrite, rate, bind,... Every ERP platform has billing. Almost none execute payments. The accounts receivable module records the invoice. It... Freshdesk Contact Center (formerly Freshcaller) gives your team cloud voice and a PBX you can provision in-platform,... Outsourced parking, enforcement and toll operators are payment-collection businesses dressed up as service businesses.... Salesforce Service Cloud runs your support operation, and Service Cloud Voice (SCV) brings telephony into the same... If you implement Genesys, Five9, Talkdesk, NICE, RingCentral, Zoom Contact Center or any of the major CCaaS platforms,... Nextiva is a unified communications and contact centre platform (UCaaS plus CCaaS) that positions itself around... HubSpot Commerce Hub ships with HubSpot Payments as the default gateway -- but it's not the only option. Native... HubSpot Commerce Hub payment links carry HubSpot branding by default -- a generic checkout page on a HubSpot subdomain,... LivePerson runs the Conversational Cloud, an enterprise conversational AI and digital-messaging platform. It is... HubSpot Payments -- the default processor for HubSpot Commerce Hub payment links -- supports five currencies and five... HubSpot Payments charges a transaction fee on top of the underlying card processing rate -- and most teams discover this... A PCI compliance service provider is a certified third party that handles card data on behalf of merchants -- typically... A Pay Now button on a B2B invoice does two things at once. It signals to your client that you're modern enough to take... An invoice payment link turns a static document into a one-click payment. The customer opens the invoice, taps the... HubSpot Payment Links -- What's Available, and What's Missing HubSpot has steadily added payment functionality over the... DTMF payments are transactions where the customer enters their card details on a phone keypad during a call -- and the... Why Payment Workflow Automation Matters Most teams collect payments through one of three patterns: a card machine in a... If your contact centre uses Verint, for a financial services compliance team, a major insurance carrier, a multi-state... If your contact centre uses Observe.AI, for a financial services collections operation, a healthcare revenue-cycle... If your contact centre uses Cresta, for an insurance sales operation, a financial services collections team, a SaaS... A merchant account is the bank account that lets your business accept card payments. The "provider" is whoever opens... If you're running a contact centre on Sprinklr Service, for a global retailer, a financial services brand, an airline,... If you're running an enterprise contact centre on RingCX, RingCentral's dedicated CCaaS product, for an insurance... If you're running a contact centre on Zoom Contact Center, for an insurance brokerage, a debt-recovery agency, a... What Is a Payment Request? A payment request is a digital message -- SMS, email, WhatsApp, or QR code -- that contains a... Dialpad has built one of the most AI-forward contact centre platforms on the market. Dialpad Ai powers real-time... The Builders Merchant Cash Flow Problem Builders merchants and trade suppliers operate on tight margins with long... Vonage Contact Centre (VCC), now part of Ericsson, is a well-established CCaaS platform with deep Salesforce... The Dealership Payment Problem Car dealerships handle some of the highest-value consumer transactions in retail. A... 8x8 Contact Center is a strong mid-market and enterprise CCaaS platform. 8x8 XCaaS combines UCaaS and CCaaS in a single... Aircall is a cloud phone system popular with sales and support teams, particularly in the SMB and mid-market segments.... Here's the important thing to know up front: PayPal/Braintree does not work for Shuttle voice card capture. Braintree... Global Payments doesn't natively connect to Twilio for voice payments. If you want to process Global Payments... Authorize.net doesn't natively connect to Twilio for voice payments. If you want to process Authorize.net transactions... Checkout.com doesn't natively connect to Twilio for voice payments. If you want to process Checkout.com transactions... How Do You Switch Payment Providers? Plan three to six months end to end, and follow six steps: audit your current... Stripe is the most popular modern payment platform -- used by millions of businesses from startups to enterprises. But... Adyen doesn't natively connect to Twilio for voice payments. If you want to process Adyen transactions during a phone... A payment gateway sits between your checkout and the banks. It encrypts card details, routes the transaction to the... Worldpay doesn't natively connect to Twilio for voice payments. If you want to process Worldpay transactions during a... If Stripe has frozen your account, you're probably reading this in a state of panic. Your payments are stuck. Your... Worldpay is one of the largest payment processors in the world -- processing billions of transactions per year across... You signed up with a payment provider because they were easy to integrate, competitively priced, and ticked the right... The Ops Problem Nobody Warns You About When your platform processes a few hundred transactions a day through a single... Cognigy is one of the leading enterprise conversational AI platforms. Its AI agents handle complex multi-turn... Braintree -- PayPal's full-stack payment gateway -- handles card processing, PayPal, Venmo, Apple Pay, and Google Pay... Twilio PCI compliance comes down to whether card data ever reaches your application, your agents or your call... Your customers want to pay with PayPal. You can see it in the emails -- "Do you accept PayPal?" -- and in the delayed... The Case for Building Every platform CTO who considers building payment infrastructure in-house has good reasons. You... PolyAI deploys AI voice agents that handle hundreds of millions of conversations a year across insurance, hospitality,... Payment processing fees are one of the largest variable costs for any business that accepts cards. At low volumes, the... The Number That Catches Platforms Off Guard Most platform CTOs know PCI DSS compliance isn't free. Few realise how... Replicant builds autonomous AI agents for contact centres. Their platform handles the Tier 1 support calls that make up... Genesys Cloud CX is one of the largest contact centre platforms in the world, powering millions of customer... Method CRM is built for businesses that live in QuickBooks. It syncs contacts, invoices, estimates, and work orders in... Every AI agent that tries to buy something on the open web hits the same wall. The checkout was built for a human with... The Promise vs the Reality Five years ago, the pitch was irresistible. Become a Payment Facilitator. Own the merchant... Retell AI lets developers build production-grade AI voice agents fast. Its API-first platform handles the hard parts of... Five9 is one of the leading cloud contact centre platforms, serving thousands of organisations across financial... The Card Terminal Problem at Scale When you have five field agents, card terminals feel manageable. You buy five... The Zendesk Payment Problem Zendesk is where your support team lives. Tickets, chat, email, phone, every customer... What Are Debtor Days and Why Do They Matter? Debtor days (also called Days Sales Outstanding or DSO) measure the... NICE CXone (formerly NICE inContact) is an enterprise-grade CCaaS platform used by some of the largest contact centre... Looking for the right payment link provider in 2026? We compare Stripe, Square, PayPal, GoCardless and Shuttle on fees,... Intercom Handles Conversations. It Doesn't Handle Payments. Intercom is built for customer messaging, live chat, in-app... Why DSO Benchmarks Matter If you don't know what "good" looks like for your industry, you can't tell whether your... The Professional Services Payment Problem A client owes you £47,000 for six months of advisory work. You send an... Talkdesk has positioned itself as the AI-first contact centre platform. Talkdesk Autopilot handles conversational AI,... The Scale of the Problem Late payments are the single biggest cash flow threat to UK businesses. The numbers speak for... Payment Collection in Property Management Is Still Manual Lettings agencies and property management firms handle... Amazon Connect Has No Built-In Payment Capture Amazon Connect is AWS's cloud contact centre platform. It handles... What Are Marketplace Payment Solutions? A marketplace payment solution is the infrastructure that handles money... It Happens More Often Than You Think Stripe processes payments for over 3 million businesses. PayPal, Square, Adyen,... The Trust Gap Nobody Talks About A customer owes you money. You send them a payment link by email or SMS. They tap the... Voice AI Can Take the Order. It Can't Take the Payment. Voice AI for restaurant ordering is one of the fastest-growing... Avaya Does Not Have Native PCI-Compliant Payment Capture Avaya has been the backbone of enterprise contact centres for... Every time a customer pays by card, the merchant pays a fee. That fee isn't a single charge -- it's a stack of costs... The B2B Payment Problem B2B service companies have a cash flow problem that nobody talks about openly. You send an... The Payment Problem Every Food Ordering Platform Hits Whether you're building a voice AI ordering system, a chatbot... If you're a software platform trying to add payments, you've probably encountered four different approaches -- and a lot... RingCentral Does Not Have Native Payment Capture RingCentral is one of the largest UCaaS and CCaaS providers in the... Why Hotels Still Chase Payments by Email Hotels and holiday accommodation providers deal with payment complexity that... One Link, Many Channels A payment link is just a URL. It opens a branded checkout page where your customer picks their... Authorize.net and Stripe are two of the most compared payment gateways. Here's the honest breakdown -- features, pricing, limitations, and when each one fits. The Problem With Car Dealership Payments Car dealerships process some of the highest-value consumer transactions... Three Scenarios, One Compliance Problem Debt collection agencies collect payments through three distinct scenarios -- ... Cisco Webex Contact Centre Has No Native Payment Capture Cisco Webex Contact Centre, formerly Cisco Contact Center... "Just One More Sprint on Payments" You know this meeting. It happens every planning cycle. Product wants to ship a new... Why Travel Payments Are Uniquely Complex Travel is one of the hardest verticals for payment infrastructure. Not because... PCI scope is the single biggest reason insurance core platforms don't execute payments. The moment card data enters the... What Is Payment Orchestration? Payment orchestration is a software layer that sits between a merchant and multiple... Adyen vs Worldpay: an honest 2026 comparison for platforms and enterprise merchants. We cover pricing, settlement... Choosing a payment platform is one of the highest-stakes infrastructure decisions a platform operator will make. Not... Embedded payments are one of the most significant shifts in how software companies generate revenue -- and most... Adyen vs Checkout.com compared: pricing, features, platform support, multi-PSP flexibility. Independent breakdown for platforms choosing between the two biggest enterprise PSPs. Your Platform's AI Agents Need to Take Payments Your platform runs conversations. Customer service calls. Sales chats.... The Multi-Client Payment Problem You run a BPO or outsourced contact centre. You handle calls, chat, email -- maybe AI... AI Agents Are Starting to Transact. The Infrastructure Isn't Ready. Something shifted in early 2026. AI agents stopped... Voice payments are transactions completed during a phone call -- through an IVR system, a live agent, or an AI voice... PSPs Don't Lose to Other PSPs. They Lose to Software. The traditional PSP competitive landscape looks like this: Stripe... You've sent the invoice. It's sitting in your customer's inbox. And now you wait -- 30 days, 45 days, sometimes longer -- ... The Stripe Connect Growth Trap Stripe Connect is the best way to start embedding payments in a SaaS platform. The docs... The Security Question Nobody's Asking Loudly Enough AI agents are processing real payments. Voice agents take card... Your AI voice agent is impressive. It handles intent recognition, sentiment analysis, conversational routing, customer... QuickBooks doesn't have a built-in payment links feature. You can send invoices, but there's no native way to generate... Your platform handles the hardest thing in customer communications -- live voice, real-time intent, emotional... Authorize.net is one of the most widely used payment gateways in the United States -- and a significant number of... AI agents are everywhere. They're booking meetings, resolving support tickets, qualifying leads, handling insurance... Call center payment processing is how contact centres take card payments on live calls without card numbers reaching... The Travel Payment Problem Travel payments are unlike anything else in digital commerce. A customer in Tokyo books a... The Invoicing Platform Payment Problem Invoicing and ERP platforms sit at the exact point where money is owed. They... Every insurance core platform has billing. Almost none execute payments. Billing modules handle invoices, installment... Two Solutions That Sound Similar But Solve Different Problems If you're a software platform evaluating how to add... The CCaaS Payment Opportunity Contact centre platforms handle billions of customer interactions each year. A... Payments Meet AI Agents AI agents are no longer just answering questions. They're closing sales, collecting debts,... The Deal You Can't Close The conversation follows a predictable script. Your platform is in late-stage negotiations... The Pattern It starts the same way for every platform. A customer asks: "Can we pay through your software?" Then an... The Checkout Redirect Is Killing Your Conversion A customer is mid-conversation with your AI chat agent. They've asked... Insurance Runs on Phone Calls. Phone Calls Don't Run on Payments. Insurance is one of the last industries where the... Hotels Are Replacing Call Centres. The Payment Moment Is the Gap. Over 70% of hotel executives are now prioritising AI... The Collections Problem: Agreements Without Payments Debt collection runs on a simple loop: contact the debtor,... AI Voice Agents Are Creating a New Payment Channel AI voice agents are no longer novelty. They're production... The Question Every Platform Faces At some point, every software platform that embeds payments hits the same fork in the... Payments Aren't Just Checkout Anymore For most of the internet's history, "payments" meant one thing: a checkout page.... ## Also Explore Related Content ### Comparisons See how Shuttle compares to Stripe Connect, Spreedly, and other platforms. 10 comparisons ### Alternatives Exploring alternatives to popular payment platforms and approaches. 8 alternatives ## Links - [How to Take Payments Online The complete guide to collecting payments for service businesses -- compare every method.](/guides/take-payments-online/) - [Send Payment Links Step-by-step guide to creating and sending payment links to customers.](/guides/take-payments-online/payment-links/) - [Phone Payments Take secure card payments over the phone -- PCI-compliantly.](/guides/take-payments-online/phone-payments/) - [Single Global PSP vs Multiple Local Acquirers: How to Decide](/guides/global-psp-vs-local-acquirers/) - [Read more](/guides/global-psp-vs-local-acquirers/) - [Virtual Terminal Payments: PCI Rules and Secure Alternatives](/guides/virtual-terminal-payments/) - [Read more](/guides/virtual-terminal-payments/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [Read more](/guides/pci-compliant-phone-payments/) - [Agent-Assisted Payments: Secure Card Capture on Live Calls](/guides/agent-assisted-payments/) - [Read more](/guides/agent-assisted-payments/) - [IVR Payments: PCI Compliant Self-Service Phone Payments](/guides/ivr-payments/) - [Read more](/guides/ivr-payments/) - [Payment Solutions for Medical Billing Companies and RCM Firms](/guides/medical-billing-payments/) - [Read more](/guides/medical-billing-payments/) - [Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem](/guides/take-payments-on-behalf-of-clients/) - [Read more](/guides/take-payments-on-behalf-of-clients/) - [What Is Twilio Pay? How It Works, Pricing, and Connectors (2026)](/guides/what-is-twilio-pay/) - [Read more](/guides/what-is-twilio-pay/) - [Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026)](/guides/stripe-twilio-integration/) - [Read more](/guides/stripe-twilio-integration/) - [Twilio Pay Connectors: How to Connect Any Payment Provider to Twilio](/guides/twilio-pay-connectors/) - [Read more](/guides/twilio-pay-connectors/) - [Twilio Pay Error Codes Explained: What Your Pay Connector Actually Supports](/guides/twilio-pay-error-codes/) - [Read more](/guides/twilio-pay-error-codes/) - [Twilio Stripe Pay Connector: What It Does, Its Limits, and the Multi-Gateway Alternative](/guides/twilio-stripe-pay-connector/) - [Read more](/guides/twilio-stripe-pay-connector/) - [How to Switch Twilio Pay Connectors Without Breaking Your Call Flow](/guides/switch-twilio-pay-connector/) - [Read more](/guides/switch-twilio-pay-connector/) - [ACH Payments Over the Phone: How to Take Bank Payments by IVR and Agent](/guides/ach-payments-over-the-phone/) - [Read more](/guides/ach-payments-over-the-phone/) - [How to Connect LiqPay to Twilio for Voice & IVR Payments](/guides/liqpay-twilio-integration/) - [Read more](/guides/liqpay-twilio-integration/) - [How to Connect USAePay to Twilio for Voice & IVR Payments](/guides/usaepay-twilio-integration/) - [Read more](/guides/usaepay-twilio-integration/) - [Twilio Generic Pay Connector: How It Works and What It Means for Your PCI Scope](/guides/twilio-generic-pay-connector/) - [Read more](/guides/twilio-generic-pay-connector/) - [How to Connect FreedomPay to Twilio for Voice & IVR Payments](/guides/freedompay-twilio-integration/) - [Read more](/guides/freedompay-twilio-integration/) - [How to Connect PayU to Twilio for Voice & IVR Payments](/guides/payu-twilio-integration/) - [Read more](/guides/payu-twilio-integration/) - [How to Connect Paysafe to Twilio for Voice & IVR Payments](/guides/paysafe-twilio-integration/) - [Read more](/guides/paysafe-twilio-integration/) - [How to Connect CardConnect to Twilio for Voice & IVR Payments](/guides/cardconnect-twilio-integration/) - [Read more](/guides/cardconnect-twilio-integration/) - [How to Connect Opayo to Twilio for Voice & IVR Payments](/guides/opayo-twilio-integration/) - [Read more](/guides/opayo-twilio-integration/) - [How to Connect Moneris to Twilio for Voice & IVR Payments](/guides/moneris-twilio-integration/) - [Read more](/guides/moneris-twilio-integration/) - [How to Connect Braintree to Twilio: Voice Payments & Payment Links](/guides/braintree-twilio-integration/) - [Read more](/guides/braintree-twilio-integration/) - [How to Connect NMI to Twilio for Voice & IVR Payments](/guides/nmi-twilio-integration/) - [Read more](/guides/nmi-twilio-integration/) - [How to Connect Cybersource to Twilio for Voice & IVR Payments](/guides/cybersource-twilio-integration/) - [Read more](/guides/cybersource-twilio-integration/) - [How to Connect NAB to Twilio for Voice & IVR Payments](/guides/nab-twilio-integration/) - [Read more](/guides/nab-twilio-integration/) - [How to Connect Transbank to Twilio for Voice & IVR Payments](/guides/transbank-twilio-integration/) - [Read more](/guides/transbank-twilio-integration/) - [How to Connect Xendit to Twilio for Voice & IVR Payments](/guides/xendit-twilio-integration/) - [Read more](/guides/xendit-twilio-integration/) - [How to Connect Ecommpay to Twilio for Voice & IVR Payments](/guides/ecommpay-twilio-integration/) - [Read more](/guides/ecommpay-twilio-integration/) - [How to Connect BS Payone to Twilio for Voice & IVR Payments](/guides/bs-payone-twilio-integration/) - [Read more](/guides/bs-payone-twilio-integration/) - [How to Connect Trust Payments to Twilio for Voice & IVR Payments](/guides/trust-payments-twilio-integration/) - [Read more](/guides/trust-payments-twilio-integration/) - [How to Connect Fat Zebra to Twilio for Voice & IVR Payments](/guides/fat-zebra-twilio-integration/) - [Read more](/guides/fat-zebra-twilio-integration/) - [How to Connect ACI Speedpay to Twilio for Voice & IVR Payments](/guides/aci-speedpay-twilio-integration/) - [Read more](/guides/aci-speedpay-twilio-integration/) - [How to Connect Fortis to Twilio for Voice & IVR Payments](/guides/fortis-twilio-integration/) - [Read more](/guides/fortis-twilio-integration/) - [How to Accept ACH Payments in QuickBooks (Without Intuit's Processor)](/guides/quickbooks-ach-payments/) - [Read more](/guides/quickbooks-ach-payments/) - [How to Connect Mollie to Twilio for Voice & IVR Payments](/guides/mollie-twilio-integration/) - [Read more](/guides/mollie-twilio-integration/) - [Build vs Buy: Should Your Platform Build Its Own Payment Links?](/guides/build-vs-buy-payment-links/) - [Read more](/guides/build-vs-buy-payment-links/) - [How to Connect Shift4 to Twilio for Voice & IVR Payments](/guides/shift4-twilio-integration/) - [Read more](/guides/shift4-twilio-integration/) - [How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments](/guides/quickbooks-payments-twilio-integration/) - [Read more](/guides/quickbooks-payments-twilio-integration/) - [How to Take Payments on Lindy: PCI-Compliant AI Agent Payments](/guides/lindy-payments/) - [Read more](/guides/lindy-payments/) - [How to Take Payments in Mitel: Multi-PSP PCI-Compliant Capture](/guides/mitel-payments/) - [Read more](/guides/mitel-payments/) - [How to Take Payments on Phonely AI Voice Agents: PCI-Compliant Payments](/guides/phonely-payments/) - [Read more](/guides/phonely-payments/) - [How to Take Payments on Ada: PCI-Compliant AI Agent Payments](/guides/ada-payments/) - [Read more](/guides/ada-payments/) - [Sierra AI Payments: Multi-PSP Payment Capture vs Native Payments](/guides/sierra-payments/) - [Read more](/guides/sierra-payments/) - [Gupshup Payments: UPI and WhatsApp Pay vs Multi-PSP Card Capture](/guides/gupshup-payments/) - [Read more](/guides/gupshup-payments/) - [Parloa Payments: Multi-PSP Payment Capture for AI Contact Centre Agents](/guides/parloa-payments/) - [Read more](/guides/parloa-payments/) - [How to Take Payments in 3CX: PCI-Compliant Phone Payments](/guides/3cx-payments/) - [Read more](/guides/3cx-payments/) - [How to Take Payments on boost.ai: PCI-Compliant Virtual Agent Payments](/guides/boost-ai-payments/) - [Read more](/guides/boost-ai-payments/) - [How to Take Payments on ElevenLabs Agents: Native Stripe vs Multi-PSP](/guides/elevenlabs-payments/) - [Read more](/guides/elevenlabs-payments/) - [How to Take Payments on Decagon AI Agents: PCI-Compliant Payments](/guides/decagon-payments/) - [Read more](/guides/decagon-payments/) - [Content Guru storm Payments: Native storm LOCK vs Multi-PSP Capture](/guides/content-guru-payments/) - [Read more](/guides/content-guru-payments/) - [How to Take Payments on Synthflow Voice Agents: Native Stripe vs Multi-PSP](/guides/synthflow-payments/) - [Read more](/guides/synthflow-payments/) - [How to Take Payments on Thoughtly: PCI-Compliant AI Voice Payments](/guides/thoughtly-payments/) - [Read more](/guides/thoughtly-payments/) - [How to Take Payments in GoTo: PCI-Compliant Contact Centre Payments](/guides/goto-payments/) - [Read more](/guides/goto-payments/) - [How to Take Payments on Kore.ai Voice Agents: PCI-Compliant Payments](/guides/kore-ai-payments/) - [Read more](/guides/kore-ai-payments/) - [How to Take Payments on Voiceflow: PCI-Compliant AI Agent Payments](/guides/voiceflow-payments/) - [Read more](/guides/voiceflow-payments/) - [How to Take Payments on Bland AI Phone Agents: PCI-Compliant Payments](/guides/bland-ai-payments/) - [Read more](/guides/bland-ai-payments/) - [Yellow.ai Payments: In-Call Capture vs Payment Links](/guides/yellow-ai-payments/) - [Read more](/guides/yellow-ai-payments/) - [How to Take Payments on Vapi AI Voice Agents: PCI-Compliant Payments](/guides/vapi-payments/) - [Read more](/guides/vapi-payments/) - [How to Take Payments on Regal.ai Voice Agents: In-Call PCI-Compliant Capture](/guides/regal-ai-payments/) - [Read more](/guides/regal-ai-payments/) - [How to Take Payments in UJET: PCI-Compliant Contact Centre Payments](/guides/ujet-payments/) - [Read more](/guides/ujet-payments/) - [Gladly Payments: One Multi-PSP Layer Across Voice and Chat](/guides/gladly-payments/) - [Read more](/guides/gladly-payments/) - [Payments for Insurance Carriers and MGA Platforms](/guides/payments-for-insurance-carriers-mga/) - [Read more](/guides/payments-for-insurance-carriers-mga/) - [Embedded Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [Read more](/guides/payments-for-erp-platforms/) - [How to Take Payments in Freshdesk Contact Center: PCI-Compliant Payments](/guides/freshdesk-payments/) - [Read more](/guides/freshdesk-payments/) - [Payment Collection for Parking, Enforcement and Toll Operators](/guides/parking-enforcement-toll-payments/) - [Read more](/guides/parking-enforcement-toll-payments/) - [How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments](/guides/salesforce-service-cloud-payments/) - [Read more](/guides/salesforce-service-cloud-payments/) - [Payments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments](/guides/payments-for-ccaas-implementation-partners/) - [Read more](/guides/payments-for-ccaas-implementation-partners/) - [Nextiva Payments: Multi-PSP Payment Capture Across Voice and Chat](/guides/nextiva-payments/) - [Read more](/guides/nextiva-payments/) - [HubSpot Payment Gateway Integration: Every Option Compared (2026)](/guides/hubspot-payment-gateway/) - [Read more](/guides/hubspot-payment-gateway/) - [HubSpot Payment Link Branding: Customizing the Checkout (2026 Guide)](/guides/hubspot-payment-link-branding/) - [Read more](/guides/hubspot-payment-link-branding/) - [LivePerson Payments: Multi-PSP Capture Across Messaging and Voice](/guides/liveperson-payments/) - [Read more](/guides/liveperson-payments/) - [HubSpot International Payments: Accepting Cards Outside the Big 5 Currencies](/guides/hubspot-international-payments/) - [Read more](/guides/hubspot-international-payments/) - [HubSpot Commerce Hub Transaction Fees: What You Actually Pay (2026)](/guides/hubspot-commerce-hub-transaction-fees/) - [Read more](/guides/hubspot-commerce-hub-transaction-fees/) - [PCI Compliance Service Provider: How to Choose One in 2026](/guides/pci-compliance-service-provider/) - [Read more](/guides/pci-compliance-service-provider/) - [Pay Now Button for Invoices: The B2B Guide](/guides/pay-now-button-invoices/) - [Read more](/guides/pay-now-button-invoices/) - [Invoice Payment Links: How to Get Paid Faster on Every Invoice](/guides/invoice-payment-links/) - [Read more](/guides/invoice-payment-links/) - [HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)](/guides/hubspot-payment-links/) - [Read more](/guides/hubspot-payment-links/) - [DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking](/guides/dtmf-payments/) - [Read more](/guides/dtmf-payments/) - [Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide)](/guides/payment-workflow-automation/) - [Read more](/guides/payment-workflow-automation/) - [How to Take Payments with Verint: PCI-Compliant Payment Integration for Verint-Powered Contact Centres](/guides/verint-payments/) - [Read more](/guides/verint-payments/) - [Observe.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres](/guides/observe-ai-payments/) - [Read more](/guides/observe-ai-payments/) - [Cresta and Payments: PCI-Compliant Card Capture for Cresta-Powered Contact Centres](/guides/cresta-payments/) - [Read more](/guides/cresta-payments/) - [Merchant Account Providers Compared: 12 Best Options for 2026](/guides/merchant-account-providers/) - [Read more](/guides/merchant-account-providers/) - [How to Take Payments on Sprinklr: PCI-Compliant CX Payment Integration](/guides/sprinklr-payments/) - [Read more](/guides/sprinklr-payments/) - [How to Take Payments on RingCX: Enterprise CCaaS Payment Integration](/guides/ringcx-payments/) - [Read more](/guides/ringcx-payments/) - [How to Take Payments on Zoom Contact Center: PCI-Compliant Voice Payments](/guides/zoom-contact-center-payments/) - [Read more](/guides/zoom-contact-center-payments/) - [How to Send Payment Requests: The Complete Guide to Digital Payment Collection](/guides/how-to-send-payment-requests/) - [Read more](/guides/how-to-send-payment-requests/) - [How to Take Payments on Dialpad: PCI-Compliant Voice Payments](/guides/dialpad-payments/) - [Read more](/guides/dialpad-payments/) - [Payment Collection for Builders Merchants: Links, Voice & Open Banking](/guides/builders-merchant-payment-collection/) - [Read more](/guides/builders-merchant-payment-collection/) - [How to Take Payments on Vonage Contact Centre: Secure Payment Processing](/guides/vonage-payments/) - [Read more](/guides/vonage-payments/) - [Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments](/guides/payment-links-for-car-dealerships/) - [Read more](/guides/payment-links-for-car-dealerships/) - [How to Take Payments on 8x8: PCI-Compliant Contact Centre Payments](/guides/8x8-payments/) - [Read more](/guides/8x8-payments/) - [How to Take Payments on Aircall: Secure Voice Payment Processing](/guides/aircall-payments/) - [Read more](/guides/aircall-payments/) - [How to Connect PayPal to Twilio for Voice & IVR Payments](/guides/paypal-twilio-integration/) - [Read more](/guides/paypal-twilio-integration/) - [How to Connect Global Payments to Twilio for Voice & IVR Payments](/guides/global-payments-twilio-integration/) - [Read more](/guides/global-payments-twilio-integration/) - [How to Connect Authorize.net to Twilio for Voice & IVR Payments](/guides/authorize-net-twilio-integration/) - [Read more](/guides/authorize-net-twilio-integration/) - [How to Connect Checkout.com to Twilio for Voice & IVR Payments](/guides/checkout-com-twilio-integration/) - [Read more](/guides/checkout-com-twilio-integration/) - [How to Switch Payment Providers Without Losing Customers](/guides/payment-provider-migration/) - [Read more](/guides/payment-provider-migration/) - [Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe](/guides/quickbooks-stripe-payments/) - [Read more](/guides/quickbooks-stripe-payments/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Read more](/guides/adyen-twilio-integration/) - [How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs](/guides/payment-gateway-cost/) - [Read more](/guides/payment-gateway-cost/) - [How to Connect Worldpay to Twilio for Voice & IVR Payments](/guides/worldpay-twilio-integration/) - [Read more](/guides/worldpay-twilio-integration/) - [Stripe Froze My Account: What to Do and How to Prevent It](/guides/stripe-account-frozen/) - [Read more](/guides/stripe-account-frozen/) - [Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay](/guides/quickbooks-worldpay-payments/) - [Read more](/guides/quickbooks-worldpay-payments/) - [How to Avoid Payment Provider Lock-In: A Platform Guide](/guides/payment-provider-lock-in/) - [Read more](/guides/payment-provider-lock-in/) - [Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions](/guides/payment-operations-at-scale/) - [Read more](/guides/payment-operations-at-scale/) - [How to Add Payments to Cognigy AI Agents: Voice & Chat Payment Integration](/guides/cognigy-payments/) - [Read more](/guides/cognigy-payments/) - [Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree](/guides/quickbooks-braintree-payments/) - [Read more](/guides/quickbooks-braintree-payments/) - [Twilio PCI Compliance: How to Take Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Read more](/guides/twilio-pci-compliance/) - [PayPal + QuickBooks Integration: Add PayPal to QuickBooks Invoices](/guides/quickbooks-paypal-payments/) - [Read more](/guides/quickbooks-paypal-payments/) - [Build vs Buy Payment Infrastructure: A Decision Framework for Platforms](/guides/build-vs-buy-payment-infrastructure/) - [Read more](/guides/build-vs-buy-payment-infrastructure/) - [How PolyAI Voice Agents Take Payments: PCI-Compliant AI Voice Payments](/guides/polyai-payments/) - [Read more](/guides/polyai-payments/) - [How to Reduce Payment Processing Fees Without Switching Providers](/guides/reduce-payment-processing-fees/) - [Read more](/guides/reduce-payment-processing-fees/) - [PCI Compliance Cost for Platforms: What It Really Costs in 2026](/guides/pci-compliance-cost-platforms/) - [Read more](/guides/pci-compliance-cost-platforms/) - [How to Add Payments to Replicant AI: Voice Agent Payment Integration](/guides/replicant-payments/) - [Read more](/guides/replicant-payments/) - [How to Take Payments on Genesys Cloud: PCI-Compliant Voice & IVR Payments](/guides/genesys-payments/) - [Read more](/guides/genesys-payments/) - [Payment Links for Method CRM: Collect Field Payments Without Card Terminals](/guides/payment-links-method-crm/) - [Read more](/guides/payment-links-method-crm/) - [Agent-Native Checkout: Why AI Commerce Needs New Payment APIs](/guides/agent-native-checkout/) - [Read more](/guides/agent-native-checkout/) - [PayFac Regret: Why Platforms Are Unwinding Their PayFac Status](/guides/payfac-regret/) - [Read more](/guides/payfac-regret/) - [How to Take Payments on Retell AI Voice Agents: PCI-Compliant Payments](/guides/retell-ai-payments/) - [Read more](/guides/retell-ai-payments/) - [How to Take Payments on Five9: PCI-Compliant Contact Centre Payments](/guides/five9-payments/) - [Read more](/guides/five9-payments/) - [Field Agent Payment Collection: Why Your Team Doesn't Need Card Terminals](/guides/field-agent-payment-collection/) - [Read more](/guides/field-agent-payment-collection/) - [How to Take Payments in Zendesk: Secure Payment Collection for Support Teams](/guides/zendesk-payments/) - [Read more](/guides/zendesk-payments/) - [How to Reduce Debtor Days: 10 Strategies That Actually Work](/guides/reduce-debtor-days/) - [Read more](/guides/reduce-debtor-days/) - [How to Take Payments on NICE CXone: Secure Payment Processing](/guides/nice-cxone-payments/) - [Read more](/guides/nice-cxone-payments/) - [Best Payment Link Providers 2026: Stripe vs Square vs PayPal vs Shuttle](/guides/best-payment-link-providers/) - [Read more](/guides/best-payment-link-providers/) - [How to Take Payments in Intercom: Payment Collection for Sales & Support](/guides/intercom-payments/) - [Read more](/guides/intercom-payments/) - [DSO Benchmarks by Industry UK (2026)](/guides/dso-benchmarks-uk/) - [Read more](/guides/dso-benchmarks-uk/) - [Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices](/guides/payment-collection-professional-services/) - [Read more](/guides/payment-collection-professional-services/) - [How to Take Payments on Talkdesk: PCI-Compliant Voice Payments](/guides/talkdesk-payments/) - [Read more](/guides/talkdesk-payments/) - [The UK Guide to Collecting Overdue Payments](/guides/uk-guide-collecting-overdue-payments/) - [Read more](/guides/uk-guide-collecting-overdue-payments/) - [Payment Links for Property Management & Lettings Agencies](/guides/payment-links-property-management/) - [Read more](/guides/payment-links-property-management/) - [How to Take Payments on Amazon Connect: PCI-Compliant Voice Payments](/guides/amazon-connect-payments/) - [Read more](/guides/amazon-connect-payments/) - [Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale](/guides/marketplace-payment-solutions/) - [Read more](/guides/marketplace-payment-solutions/) - [What Happens When Your Only Payment Processor Cuts You Off](/guides/single-psp-risk/) - [Read more](/guides/single-psp-risk/) - [White-Label Payment Links: Why Your Brand on the Checkout Matters](/guides/white-label-payment-links/) - [Read more](/guides/white-label-payment-links/) - [How Voice AI Ordering Platforms Handle Payments -- And Why It's Broken](/guides/voice-ai-ordering-payments/) - [Read more](/guides/voice-ai-ordering-payments/) - [How to Take Payments on Avaya: PCI-Compliant Contact Centre Payments](/guides/avaya-payments/) - [Read more](/guides/avaya-payments/) - [Credit Card Processing Fees Explained: What You Actually Pay](/guides/credit-card-processing-fees/) - [Read more](/guides/credit-card-processing-fees/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [Read more](/guides/b2b-payment-collection/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [Read more](/guides/food-ordering-platform-payments/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference?](/guides/payment-layer-explained/) - [Read more](/guides/payment-layer-explained/) - [How to Take Payments on RingCentral: Secure Payment Processing](/guides/ringcentral-payments/) - [Read more](/guides/ringcentral-payments/) - [Payment Links for Hotels & Holiday Accommodation: The Complete Guide](/guides/payment-links-for-hotels/) - [Read more](/guides/payment-links-for-hotels/) - [Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes](/guides/multi-channel-payment-collection/) - [Read more](/guides/multi-channel-payment-collection/) - [Authorize.net vs Stripe: Which Payment Gateway Should You Choose?](/guides/authorize-net-vs-stripe/) - [Read more](/guides/authorize-net-vs-stripe/) - [Payment Solutions for Car Dealerships & Auto Finance Platforms](/guides/car-dealership-payment-solutions/) - [Read more](/guides/car-dealership-payment-solutions/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [Read more](/guides/secure-payment-collection-debt-agencies/) - [How to Take Payments on Cisco Webex Contact Centre: Secure Voice Payments](/guides/cisco-webex-payments/) - [Read more](/guides/cisco-webex-payments/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Read more](/guides/get-payments-off-your-roadmap/) - [Payment Solutions for Travel Platforms: Multi-PSP, Multi-Currency, Multi-Channel](/guides/travel-platform-payments/) - [Read more](/guides/travel-platform-payments/) - [PCI-Compliant Payment Architecture for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [Read more](/guides/pci-payments-insurance-platforms/) - [What Is Payment Orchestration? The Complete Guide](/guides/what-is-payment-orchestration/) - [Read more](/guides/what-is-payment-orchestration/) - [Adyen vs Worldpay: Which PSP for Your Platform?](/guides/adyen-vs-worldpay/) - [Read more](/guides/adyen-vs-worldpay/) - [How to Choose a Payment Platform: The Evaluation Checklist for Platform Operators](/guides/how-to-choose-payment-platform/) - [Read more](/guides/how-to-choose-payment-platform/) - [What Is Embedded Payments? The Definitive Guide for Platforms](/guides/what-is-embedded-payments/) - [Read more](/guides/what-is-embedded-payments/) - [Adyen vs Checkout.com: Which PSP for Your Platform?](/guides/adyen-vs-checkout-com/) - [Read more](/guides/adyen-vs-checkout-com/) - [Agentic Payments: What Platforms Need to Know](/guides/agentic-payments-for-platforms/) - [Read more](/guides/agentic-payments-for-platforms/) - [Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope](/guides/payment-collection-for-bpos/) - [Read more](/guides/payment-collection-for-bpos/) - [Agentic Commerce: Payment Infrastructure for AI Agents](/guides/agentic-commerce/) - [Read more](/guides/agentic-commerce/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [Read more](/guides/voice-payments/) - [How PSPs Get Distribution Into Enterprise Software](/guides/how-psps-get-distribution-into-software/) - [Read more](/guides/how-psps-get-distribution-into-software/) - [How to Accept Payments on QuickBooks Invoices (Without Switching Provider)](/guides/quickbooks-invoice-payments/) - [Read more](/guides/quickbooks-invoice-payments/) - [When Your SaaS Outgrows Stripe Connect: A Migration Playbook](/guides/when-saas-outgrows-stripe-connect/) - [Read more](/guides/when-saas-outgrows-stripe-connect/) - [AI Payment Security: How AI Agents Handle Card Data Without Breaking PCI](/guides/ai-payment-security/) - [Read more](/guides/ai-payment-security/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [Read more](/guides/ai-voice-agent-pci-payments/) - [QuickBooks Payment Links: Add a Pay Now Button to Any Invoice](/guides/quickbooks-payment-links/) - [Read more](/guides/quickbooks-payment-links/) - [Embedded Payments for CCaaS: The Platform Operator's Guide](/guides/embedded-payments-for-ccaas/) - [Read more](/guides/embedded-payments-for-ccaas/) - [Authorize.net + QuickBooks Integration: Accept Invoice Payments Online](/guides/authorize-net-quickbooks/) - [Read more](/guides/authorize-net-quickbooks/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Read more](/guides/the-payment-layer-for-ai-agents/) - [Call Center Payment Processing: PCI Compliant Payments Guide (2026)](/guides/contact-centre-payments/) - [Read more](/guides/contact-centre-payments/) - [Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure](/guides/payments-for-travel-platforms/) - [Read more](/guides/payments-for-travel-platforms/) - [Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure](/guides/payments-for-invoicing-erp-platforms/) - [Read more](/guides/payments-for-invoicing-erp-platforms/) - [Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure](/guides/payments-for-insurance-platforms/) - [Read more](/guides/payments-for-insurance-platforms/) - [Payment Orchestration vs Payment Layer: Why They're Not the Same](/guides/payment-orchestration-vs-payment-layer/) - [Read more](/guides/payment-orchestration-vs-payment-layer/) - [How CCaaS Platforms Add Payment Capabilities Without Building In-House](/guides/how-ccaas-platforms-add-payments/) - [Read more](/guides/how-ccaas-platforms-add-payments/) - [How AI Agents Process Payments: The Infrastructure Guide](/guides/ai-agent-payments/) - [Read more](/guides/ai-agent-payments/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Read more](/guides/enterprise-psp-mandates/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Read more](/guides/embedded-payments-without-payfac/) - [Chat Agent Payments: How AI Closes Sales Without a Human Handoff](/guides/chat-agent-payments/) - [Read more](/guides/chat-agent-payments/) - [AI Voice Payments for Insurance: Automate Premium Collection Without Compliance Risk](/guides/ai-voice-payments-insurance/) - [Read more](/guides/ai-voice-payments-insurance/) - [AI Voice Payments for Hotels & Travel: Capture Revenue at the Moment of Guest Intent](/guides/ai-voice-payments-hotels-travel/) - [Read more](/guides/ai-voice-payments-hotels-travel/) - [AI Voice Payments for Debt Collection: Capture Payments at the Moment of Agreement](/guides/ai-voice-payments-debt-collection/) - [Read more](/guides/ai-voice-payments-debt-collection/) - [AI Voice Agents and Payments: How PolyAI Captures Payments in Conversation](/guides/ai-voice-agents-payments/) - [Read more](/guides/ai-voice-agents-payments/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform?](/guides/psp-neutral-vs-single-psp/) - [Read more](/guides/psp-neutral-vs-single-psp/) - [Multi-Channel Payment Capture: Voice, Links, Chat, and Embedded Checkout](/guides/multi-channel-payments/) - [Read more](/guides/multi-channel-payments/) - [Comparisons See how Shuttle compares to Stripe Connect, Spreedly, and other platforms. 10 comparisons](/vs/) - [Alternatives Exploring alternatives to popular payment platforms and approaches. 8 alternatives](/alternatives/) --- URL: https://www.shuttleglobal.com/guides/intercom-payments/ --- # How to Take Payments in Intercom: Payment Collection for Sales & Support | Shuttle > Intercom Handles Conversations. It Doesn't Handle Payments. Intercom is built for customer messaging, live chat, in-app messages, email, and increasingly,... # How to Take Payments in Intercom: Payment Collection for Sales & Support By Shuttle Team, March 5, 2026 ## Intercom Handles Conversations. It Doesn't Handle Payments. Intercom is built for customer messaging, live chat, in-app messages, email, and increasingly, phone. Sales teams qualify leads and close deals through it. Support teams resolve issues. Success teams manage renewals. But when any of those conversations reaches the point where money needs to change hands, Intercom has no native answer. There's no payment capture. No checkout flow. No way to collect a card number securely within a conversation. The result: agents copy-paste links from separate systems, tell customers to "go to your account settings and update your card," or, worse, ask customers to type card details into the chat. That last one is a PCI violation, and it happens more often than anyone admits. Shuttle closes this gap for Intercom-based teams. Agents send branded payment links directly within chat, and customers pay without leaving the conversation. For phone teams, Shuttle adds secure voice card capture via Twilio Pay. Card data never touches Intercom, your network, or your agents. ## How Shuttle Adds Payments to Intercom Shuttle adds PCI-compliant card capture to your Intercom payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Intercom environment or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Intercom specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Intercom workflow over Twilio, and add your own agent screen if your workflow needs one. Customers running Intercom have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## Why Intercom Teams Need Payment Capture Intercom sits at the intersection of sales, support, and success. Each function has payment moments that the platform currently can't handle. Failed payment recovery. A customer's card declines. Their subscription is at risk. The automated dunning email got ignored. But when a support agent reaches out in Intercom and can send a payment link right there in the chat, recovery rates jump. The friction between "I want to fix this" and "my card is updated" drops to a single click. Upgrade and expansion revenue. A sales conversation in Intercom leads to a plan upgrade. Today, the rep says "I'll send you an invoice" or "you can upgrade in your dashboard." Both add steps. Both lose deals. If the rep can send a payment link for the upgrade amount mid-conversation, the deal closes on the spot. Invoice collection. B2B customers with outstanding invoices are already in Intercom asking about their account. If the agent can send a payment link for the exact invoice amount during that conversation, collection happens immediately instead of entering a follow-up cycle. One-off charges. Professional services, implementation fees, overage charges, custom work. These don't fit neatly into subscription billing. Payment links handle them cleanly, the agent sends a link for the specific amount, the customer pays, done. Subscription changes. Pro-rata adjustments, add-on purchases, plan switches with price differences. The customer wants it handled now, in the conversation they're already having. ## How to Add Payments to Intercom ### Payment Links in Conversations This is the primary integration pattern for Intercom. It works across every Intercom channel, live chat, in-app messenger, email, and social. - During a conversation, the agent determines that a payment needs to be collected. They generate a payment link through Shuttle, either via a sidebar integration, a conversational shortcut, or an API call from your backend. - The agent sends the link in the conversation. It appears as a tappable, clickable URL, or as a rich card if you've built a custom Intercom app. - The customer taps the link. On mobile, it opens in their browser. On desktop, it opens in a new tab. They see a branded checkout page showing the amount, a description of what they're paying for, and standard card input fields. - The customer enters their card details and completes payment. Card data goes directly from their browser to Shuttle's PCI Level 1 certified infrastructure. It never passes through Intercom, your servers, or any agent-visible system. - The agent receives confirmation in real time. A webhook updates the conversation with payment status, transaction ID, and amount. The agent can confirm to the customer immediately. Why this fits Intercom's model: Intercom is conversational by design. Payment links extend that conversation to include the transaction itself, rather than breaking the flow with "please go to this other system." The customer stays in the same chat, on the same device, in the same context. For automated flows, Intercom's bots and workflows, payment links can be generated programmatically and sent without agent involvement. A Resolution Bot that identifies a failed payment can automatically send a recovery link. A product tour that ends with a purchase step can include a payment link as the final message. Payment links are available at /platforms/links-checkout/. ### Voice Payments via Twilio Pay For teams that handle payment-related phone calls, Shuttle's Voice Checkout captures the card in a secure Twilio Pay call. To use it you need to be a Twilio customer. How it works: - The agent triggers a payment session during a call. This starts a secure Twilio Pay capture on the voice channel. - The customer enters their card details using their phone's keypad. Each digit is captured inside Shuttle's PCI DSS Level 1 certified environment. - The digits never reach your call recordings, your Intercom instance, or your agents. The card data stays inside Shuttle's certified environment. - The payment is processed through the configured gateway. The result is returned to the agent in real time. This keeps your telephony out of PCI scope. Agents never hear card numbers, recordings are clean, and your environment needs far fewer compliance controls. See the Twilio IVR & Agent Assist payment docs for the technical flow. Voice Checkout details at /platforms/voice-checkout/. ## Payment Links in Intercom Conversations The payment link approach deserves deeper exploration because it's where most Intercom teams will start. Branded checkout pages. The payment page carries your brand, logo, colours, company name. It doesn't look like a third-party tool. Customers see a professional checkout experience that matches your product. Pre-populated amounts and references. Links are generated with the exact amount, currency, and description already set. The customer doesn't need to enter an amount or find an invoice number. This reduces errors and speeds up completion. Multi-currency support. If you operate internationally, payment links can be generated in the customer's local currency. Shuttle handles the gateway routing and currency configuration. Expiry and security. Links can be set to expire after a defined period, useful for time-sensitive offers or outstanding balances. Each link is single-use by default, preventing double-payment. Automation-friendly. Payment links can be generated via API, making them available to Intercom's Custom Bots, workflows, and third-party automations. A Zapier or Make integration can trigger payment link generation based on Intercom events, conversation tags, custom attributes, or specific bot paths. Mobile-first. Intercom's messenger is heavily used on mobile. Payment links open in the device's browser with a responsive checkout page. On iOS and Android, Apple Pay and Google Pay can be offered alongside card input, depending on your gateway configuration. ## Multi-PSP Support Your payment gateway choice shouldn't constrain how you take payments. Shuttle connects to 40+ payment service providers, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, PayPal, Mollie, and GoCardless. Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This matters in several scenarios: - You're migrating gateways. Moving from Stripe to Adyen? Your Intercom payment workflow doesn't change. Only the backend routing updates. - Different markets, different gateways. Your EU business runs through Adyen, your US business through Stripe. Each merchant is configured against their own gateway. - Client-specific gateways. If you're a platform serving multiple businesses (each with their own merchant account), Shuttle routes payments to the correct gateway for each transaction. Agents don't need to know which gateway is processing a given payment. They send a link, the customer pays, the money lands in the right account. ## PCI Compliance Every organisation that processes card payments must comply with PCI DSS. The question is how much of your environment falls within scope, and how expensive that compliance is to maintain. The risk with chat-based payments. If a customer types a card number into an Intercom chat, that data is now stored in Intercom's conversation history, potentially visible to multiple agents, and backed up across systems. This puts your Intercom environment, your network, and your data storage in PCI scope. You're looking at SAQ-D, 300+ compliance requirements and significant annual costs. How payment links eliminate scope. With Shuttle's payment links, card data never enters Intercom. The customer's browser communicates directly with Shuttle's PCI Level 1 certified infrastructure. Intercom sees only a URL (outbound) and a payment confirmation (inbound). Your PCI assessment drops to SAQ-A, the lightest self-assessment level. Voice payment compliance. If you take phone payments with Shuttle's Twilio Pay capture, the same de-scoping applies. Card data is captured inside Shuttle's certified environment in the secure Twilio Pay call and never reaches your telephony, recordings, or agents. Your telephony remains out of scope. Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification, validated annually by an independent Qualified Security Assessor. ## Use Cases ### SaaS Failed Payment Recovery A customer's card expires. Automated dunning emails go unread. The customer opens an Intercom chat about an unrelated issue. The agent sees the failed payment flag, sends a payment link for the outstanding amount, and the customer updates their card and pays, all within the same conversation. Recovery rate: significantly higher than email-only dunning. ### Professional Services Payment A customer agrees to a paid implementation package during an Intercom sales conversation. The rep generates a payment link for the implementation fee and sends it in the chat. The customer pays immediately. No invoice. No accounts payable cycle. No follow-up. ### E-commerce Order Issue Resolution A customer contacts support about a damaged item. Instead of a full refund, the agent offers a partial refund plus a replacement, with the customer paying the price difference. A payment link for the difference is sent in the chat. The customer pays, and the replacement is dispatched. ### Subscription Upgrade A trial user is chatting with sales in Intercom. They're ready to upgrade to a paid plan. The sales rep sends a payment link for the first month (or annual subscription). The customer pays within the chat. The account is upgraded automatically via webhook. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Intercom plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Intercom specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Intercom workflow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Intercom have already done it. - A native Intercom integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions Does Shuttle have a native Intercom integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Intercom. For voice you'll need to be a Twilio customer and to build the agent-side trigger for your workflow against Shuttle's APIs. Payment links require no Twilio relationship. We can build a native Intercom integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? For voice capture, yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Can payment links be sent by Intercom bots, or only by human agents? Both. Payment links are generated via API, so they can be triggered by Custom Bots, workflows, or any automation that can make an HTTP request. This enables fully automated payment recovery flows without agent involvement. Does the customer need to leave the Intercom chat to pay? The payment page opens in a new browser tab or the device's browser. The customer completes payment there and returns to the conversation. The agent receives confirmation in real time, so the conversation continues seamlessly. What payment methods are supported? Card payments (Visa, Mastercard, Amex) are supported across all gateways. Depending on your gateway configuration, Apple Pay, Google Pay, and other local payment methods can also be enabled on the checkout page. How much does it cost? Voice payments are $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). Can we track which Intercom conversations resulted in payments? Yes. Payment confirmations include metadata that can be mapped back to Intercom conversation IDs, allowing you to track conversion rates, recovery rates, and revenue generated through Intercom payment flows. ## Related Reading - PCI-Compliant Payments for Contact Centres, comprehensive guide to secure payment capture in contact centre environments - Voice Payments: The Complete Guide, everything about DTMF, IVR, and agent-assisted voice payment capture - Multi-Channel Payment Collection, collecting payments across chat, email, SMS, and voice - Twilio Pay Connectors, how Shuttle connects to Twilio's payment infrastructure - Voice Checkout, Shuttle's voice payment product for phone-based transactions ## Get Started Adding payment capture to Intercom takes days, not months. Shuttle handles the PCI infrastructure, gateway connections, and payment processing, your team just sends links or initiates voice payments within the conversations already happening. Talk to us about Intercom payment integration or explore Payment Links and Voice Checkout. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [/platforms/links-checkout/](/platforms/links-checkout/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [/platforms/voice-checkout/](/platforms/voice-checkout/) - [40+ payment service providers](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [DTMF](/guides/dtmf-payments/) - [Multi-Channel Payment Collection](/guides/multi-channel-payment-collection/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Checkout](/platforms/voice-checkout/) - [Talk to us about Intercom payment integration](/contact/) - [Payment Links](/platforms/links-checkout/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/invoice-payment-links/ --- # Invoice Payment Links: How to Get Paid Faster on Every Invoice | Shuttle > An invoice payment link turns a static document into a one-click payment. The customer opens the invoice, taps the link, lands on a hosted checkout page,... # Invoice Payment Links: How to Get Paid Faster on Every Invoice By Shuttle Team, April 30, 2026 An invoice payment link turns a static document into a one-click payment. The customer opens the invoice, taps the link, lands on a hosted checkout page, pays -- and the funds settle to your account within 1-3 business days, no follow-up required. The hardest part of getting paid isn't the work. It's the gap between sending the invoice and the customer actually paying it. UK B2B invoices average 30-45 days outstanding, and a third of small businesses report at least one customer paying 60+ days late in any given quarter. Most of that lag isn't unwilling payers -- it's friction. The customer needs to open the invoice, find the bank details, log into their banking app, type the reference correctly, hit transfer, and remember to do all of that during a busy week. A payment link removes every step of that friction. The customer pays in the moment they look at the invoice, on the device they're already holding, with the card or wallet they already have set up. Businesses that switch from "bank details on the PDF" to "payment link on the invoice" routinely cut DSO (days sales outstanding) by 30-50%. This guide covers what an invoice payment link actually is, the four channels you can deliver it through, how to add one to any invoice (whether you use accounting software or not), and what to look for in a payment link provider. ## What Is an Invoice Payment Link? An invoice payment link is a unique URL -- usually generated by a payment link provider -- that takes the customer to a pre-filled checkout page for a specific invoice. The amount, currency, invoice reference, and customer details are baked into the link, so the customer just enters their card and confirms. Behind the link sits a hosted checkout page, a payment gateway, and a settlement flow. From the customer's view it's three taps. From the business's view it's a tracked transaction with the invoice reference attached automatically. The category goes by several names -- "pay now button", "pay-by-link", "checkout link", "payment URL", "invoice link" -- but the underlying mechanic is the same. Where they differ is in branding control, supported payment methods, and how the link gets generated and tracked. ## How to Add a Payment Link to an Invoice There are four ways to add a payment link to an invoice. Which one you pick depends on whether you use accounting software, what your invoice volume looks like, and how much branding control you need. ### 1. Native integration in accounting software Most modern accounting platforms -- QuickBooks, Xero, FreshBooks, Wave, Zoho Books, Sage, and HubSpot -- let you generate a payment link inside the invoice itself. You toggle a "pay online" option, the link is auto-attached to the invoice PDF and email, and the customer sees a "Pay now" button when they receive it. For ERP platform vendors embedding pay-now flows into their AR modules natively, see Embedded Payments for ERP Platforms. Best for: Businesses already using one of these platforms with invoice volumes under ~500/month. Setup is usually 10 minutes and the link reconciliation happens automatically inside the same tool. Trade-off: You're locked to whatever payment processor the accounting platform supports natively -- usually Stripe, Square, or PayPal -- and you pay that processor's standard rate (typically 2.9% + 30p in the UK). If you want a different gateway or lower fees, the native option won't help you. ### 2. Manual link generation per invoice For invoices generated outside an accounting platform -- Word docs, Google Docs, PDFs, custom invoice templates -- you can generate a payment link manually for each invoice and paste it into the document. Best for: Service businesses with low invoice volume (under ~50/month) who use custom invoice formats and don't want to migrate their workflow. Trade-off: Manual creation, manual reconciliation. You'll need to track which link goes with which invoice and update your accounting system when each one is paid. Most payment link providers offer a dashboard to make this manageable, but it's still extra steps. ### 3. Bulk link generation via API or upload If you send hundreds or thousands of invoices a month, batch generation is the only sensible option. You upload a CSV (or push via API) with one row per invoice -- amount, reference, customer email -- and the payment link platform generates all the links and either sends them automatically or returns them to you to embed. Best for: Subscription businesses, B2B with high invoice volume, multi-tenant platforms generating invoices on behalf of customers, or any business where invoice generation is automated. Trade-off: Requires technical setup for the API path, or a recurring CSV process for the upload path. The reward is full control over the format, branding, channel, and timing of every payment link. ### 4. Embedded payment links in invoice templates The most polished option: a payment link that's templated into your invoice itself, rendered as a "Pay Now" button with your branding. Every invoice you generate automatically embeds a unique link tied to that invoice's amount and reference. This is the pay now button on invoices pattern. Best for: Businesses sending branded invoices regularly -- agencies, professional services, B2B sellers. Looks professional, removes friction, and reinforces your brand on every payment. Trade-off: Requires either an invoice template platform that supports it natively, or a payment link provider with a templating + dynamic link API. Usually means a higher tier of payment link provider, but the conversion uplift is worth it. ## Channels for Sending Invoice Payment Links Once you have the link, you can deliver it through any channel the customer uses. The four most effective: Email. The invoice email itself includes the link, either as a "Pay now" button at the top or as a clickable URL alongside the bank details. Email is still the dominant invoice delivery channel for B2B, and the open-and-click data is easy to track. Most accounting platforms do this natively. SMS. A short text reminder with the payment link converts faster than email for overdue invoices -- typically 3-5x the click-through rate within 24 hours. Best used for follow-up rather than initial delivery, and only if you have explicit consent to text the customer. QR code. Print the QR code on the paper invoice. The customer scans it with their phone camera, lands on the checkout, pays. Most useful for in-person businesses (trades, hospitality, retail) and for international customers who don't want to type long URLs. Embedded in PDF. Some PDF generators support clickable links inside the document itself. The customer opens the PDF, taps the "Pay" button, and the link launches in their browser. Works for both email-delivered and printed-and-handed-over invoices. In practice, businesses that take payments faster don't pick one channel -- they layer them. Email at invoice send. SMS reminder at day 14 if unpaid. QR on the printed copy. Embedded button in the PDF. ## What to Look For in a Payment Link Provider for Invoices Five criteria matter when picking a provider for invoice-led payments. 1. Per-invoice link generation, with custom references. You need to attach an invoice number / reference to every link so reconciliation is automatic. Some providers force you to create one-off links manually with no API; rule those out. 2. Branding control. A "Pay Now" button on a generic Stripe checkout page is fine. The same payment with your logo, your colours, and your business name in the URL is materially better -- especially for B2B. Look for white-label payment links if branding matters. 3. Payment method coverage. Cards are table stakes. The differentiators are bank-to-bank (open banking) for low fees on high-value B2B, Apple Pay / Google Pay for mobile conversion, BACS / SEPA for recurring B2B, and BNPL for retail. 4. Reconciliation back to the invoice. Either via webhook to your accounting platform, or via reference fields on the settlement report. Without this, every paid invoice is a manual lookup. 5. Multi-PSP routing. If you're processing high volumes, the difference between 1.5% and 2.9% on every invoice adds up fast. A provider that routes across multiple PSPs lets you optimise rates per invoice -- domestic cards via cheapest local processor, international via the best cross-border one. ## Common Use Cases Trade and service businesses -- electricians, plumbers, contractors -- typically send the invoice on the spot and need payment within a week. Payment links via SMS dramatically outperform "pay by bank transfer" notes. See taking payments online for trades. Professional services -- agencies, consultants, accountants -- send branded invoices monthly and care more about presentation than speed. Embedded pay-now buttons on PDF invoices are the right pattern. B2B SaaS and platforms -- generate invoices automatically every billing cycle. Bulk API generation with embedded links and per-invoice references is the only sustainable approach. Wholesale and freight -- large invoices, slow bank-transfer culture. Payment links with open banking support reduce the cost vs cards while still cutting DSO. Donations and nonprofits -- recurring or one-off payment links embedded in receipts and appeal letters. Low-fee providers and clear reference fields matter most. ## Frequently Asked Questions How do I add a payment link to an invoice? Use a payment link provider to generate a unique URL tied to the invoice amount and reference, then either embed the link as a "Pay Now" button on the invoice or paste it as a URL alongside your bank details. Most accounting platforms (QuickBooks, Xero, HubSpot) can do this automatically; for invoices outside those tools, generate the link manually or via API. What's the cheapest way to add payment links to invoices? For low volume, the cheapest path is your accounting platform's native integration (typically 2.9% + 30p per card transaction). For higher volumes, a multi-PSP payment link provider with bank-transfer / open banking support can drop effective costs to 0.5-1% on UK B2B invoices. Can I add a payment link to a paper invoice? Yes -- print a QR code on the invoice. The customer scans with their phone camera and lands on the checkout. Most payment link providers generate QR codes automatically alongside the URL. Do payment links work for B2B invoices? Yes, and they're particularly effective for B2B because the dollar amounts are higher and the manual bank-transfer process is more painful. Look for providers that support open banking / pay-by-bank to keep fees low on high-value invoices. How do I track which invoice a payment link payment is for? Use a payment link provider that supports custom reference fields per link. The reference (your invoice number) gets stamped on the transaction and shows up on the settlement report, so reconciliation is automatic. Can I send the same payment link to multiple customers? Don't -- generate a unique link per invoice. Shared links lead to reconciliation chaos and potential fraud (one customer pays the wrong amount, or a link gets shared publicly). Modern payment link platforms generate unique links instantly via API. ## Related Reading - Pay Now Button on Invoices: B2B Guide - Best Payment Link Providers 2026 - QuickBooks Payment Links Guide - HubSpot Payment Links Guide - White-Label Payment Links - Payment Workflow Automation ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ## Links - [payment link provider](/guides/best-payment-link-providers/) - [QuickBooks](/guides/quickbooks-payment-links/) - [HubSpot](/guides/hubspot-payment-links/) - [Embedded Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [pay now button on invoices pattern](/guides/pay-now-button-invoices/) - [white-label payment links](/guides/white-label-payment-links/) - [provider that routes across multiple PSPs](/guides/payment-orchestration-vs-payment-layer/) - [taking payments online for trades](/guides/take-payments-online/) - [Pay Now Button on Invoices: B2B Guide](/guides/pay-now-button-invoices/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [QuickBooks Payment Links Guide](/guides/quickbooks-payment-links/) - [HubSpot Payment Links Guide](/guides/hubspot-payment-links/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [Payment Workflow Automation](/guides/payment-workflow-automation/) - [Book a Call](/discovery/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) --- URL: https://www.shuttleglobal.com/guides/ivr-payments/ --- # IVR Payments: PCI Compliant Self-Service Phone Payments | Shuttle > Quick answer: IVR payments let callers pay through an automated keypad flow with no agent on the line. # IVR Payments: PCI Compliant Self-Service Phone Payments By Shuttle Team, July 13, 2026 Quick answer: IVR payments let callers pay through an automated keypad flow with no agent on the line. The caller keys in a reference and their card details, the digits route straight to the payment gateway, and a confirmation closes the call. Because the card number never enters your phone system, call recordings or agent screens, those systems stay out of PCI DSS scope, and when the IVR is hosted by a validated provider it typically supports the lightest self-assessment route. Confirm your exact position with your acquirer or assessor. IVR stands for interactive voice response: the automated menu system that answers a phone line, plays prompts, and reads the caller's keypad presses. An IVR payment system puts a payment flow inside that menu. "Press 1 to pay your balance" is the version most people have heard, and it exists because a large share of phone payments don't need a conversation at all. The caller knows what they owe, has their card in hand, and wants to pay and hang up. This guide covers how IVR payment processing works, the three flows most operations run, where IVR fits alongside agent-assisted capture, what it does to your PCI compliance, and the design choices that separate an IVR flow that completes payments from one that drives callers to zero. ## What IVR payments are and how the flows work An IVR payment is an unattended card transaction taken over the phone. No member of staff hears or sees anything. The caller interacts with prompts, enters digits on their keypad, and the payment goes to the gateway for authorization. In practice this shows up as three flows. ### Inbound self-pay The caller dials a payment number, usually the one printed on a statement, invoice or letter. The IVR asks for a reference (an account number, invoice number or statement reference), looks up or confirms the amount, then prompts for card number, expiration date and security code. The caller keys each one in, the IVR reads back the amount, the caller confirms, and the payment is authorized. A confirmation is played on the call and can be followed by an SMS or email receipt. This is the workhorse flow. It runs 24 hours a day, handles any volume the phone line can carry, and never puts a payment in front of a person. ### Mid-call transfer The caller starts with an agent. The conversation resolves whatever needed a human (a query, a dispute, a payment plan agreement), and when it's time to pay, the agent transfers the caller into the IVR payment flow. The caller pays through the same automated prompts, and the flow can hand the caller back to the agent afterward to confirm the payment landed and finish the call. This gives you the compliance profile of an unattended transaction with the service profile of an agented call. It's a common pattern for collections conversations and for teams that want agents to close calls personally. If the agent should stay on the line during payment instead, that's agent-assisted capture, covered below. ### After-hours coverage An IVR payment line doesn't keep office hours. Callers who ring after close, on weekends or across time zones hit the same self-pay flow and complete the same payments. For operations that print a payment number on statements or letters, this matters: people tend to deal with bills in the evening, after the office that sent the letter has gone home. An automated phone payment line collects the payment when the intent is there rather than asking the caller to try again tomorrow. ## Where IVR fits, and where it doesn't IVR is a volume tool. It absorbs the routine, high-frequency payments where the caller already knows what they're paying: bill payments, balance payments, renewals, installments on an agreed plan. Every one of those calls that completes in the IVR is a call an agent never handles, which means agents spend their time on the calls that actually need judgment: disputes, hardship conversations, complex accounts, callers who want to negotiate. It is the wrong tool for payments that need a conversation. If the amount has to be agreed, the account has to be untangled, or the caller has objections to work through, an automated menu will frustrate them and lose the payment. Those calls belong with an agent, and the compliant way to take the card there is agent-assisted DTMF capture: the agent stays on the line while the caller types their card number on the keypad and the digits route to the gateway, not the agent. Both patterns rest on the same mechanics. The caller's keypad presses are DTMF tones, and the payment system captures those tones directly while keeping them off the agent's line and out of recordings. How that capture, clamping and masking works is covered in our guide to DTMF payments. The practical difference is who's present: agent-assisted capture keeps a person on the call, IVR runs with nobody on it. Most phone-heavy operations end up running both: IVR for the routine volume, agent-assisted capture for the conversations, with payment links as the recovery path when a call drops or a caller struggles. ## IVR payment gateway: how the flow reaches your processor An IVR payment system does not process the payment itself. It captures the card and passes it to a payment gateway, which is the component that actually authorises the transaction against the card networks. Three layers do the work: the telephony platform answers the call and captures the keypad entry, the payment layer passes that capture to your gateway for tokenisation without it reaching your systems, and your gateway authorises and settles. That split matters commercially, because it means adding an IVR payment line does not mean replacing your payment setup. You keep your own gateway and your own acquiring agreement, on your existing rates. The IVR sits in front of the processor you use today rather than becoming a new one. The card is tokenised with that gateway, so the token stays with your provider. The one thing to check before you design the flow is whether your gateway is supported for voice capture. Shuttle does not support voice capture on Square or Braintree. On Braintree that comes down to a merchant-account configuration requirement on Braintree's side, and Twilio's own Braintree connector is the route if you need keypad capture there. If your processor is one of those, the phone-adjacent option with Shuttle is a payment link sent during or after the call. Shuttle connects voice and IVR flows to 30+ gateways, listed on the payment providers page. Two design details to settle before you build. Whether you can authorise now and capture later (useful when the goods ship after the call) depends on both your gateway and the capture layer supporting a split auth and capture, so check that path end to end rather than assuming it. And refunds against an IVR payment are issued in your gateway like any other transaction, not through the phone line. ## What IVR does to your PCI compliance An IVR payment is an unattended transaction, and that shapes the compliance picture. Card data bypasses your environment. The caller's card number travels as keypad input from their phone to the payment platform and on to the gateway. It doesn't pass through your agents' ears, their screens, your CRM or your own telephony estate. The systems that PCI DSS would otherwise drag into scope on a spoken-card-number call (the phone system, the recordings, the desktops, the people) never touch cardholder data in this flow. That has a direct effect on validation. Merchant PCI DSS self-assessment ranges from short questionnaires for merchants whose card data is fully handled by validated third parties, up to hundreds of controls when card data touches your own systems. When the IVR is hosted by a validated provider, the merchant typically qualifies for the lightest self-assessment route. The exact SAQ level depends on the details of your setup and your acquirer's requirements, so confirm it with your acquirer or assessor rather than assuming. Call recording gets simpler too. On an IVR payment there is nothing to pause: card data never enters the call recording path, so recordings can run for quality and dispute purposes without ever containing a card number, and your recording practices stop being tangled up with your payment compliance. For the wider picture across every phone payment pattern, see our guide to PCI compliant phone payments. ## Who uses IVR payments The businesses that get the most from IVR share a shape: high volumes of routine payments, often collected on behalf of someone else. - Statement printers and AR outsourcers. You already produce the statement or the letter. Printing an IVR payment number on it closes the loop: the recipient calls, keys the reference from the page, and pays. The payment completes without your client's office or yours ever picking up a phone. - Billing services. Medical and dental billing services and RCM firms field patient balance calls all day. An IVR line absorbs the routine balance payments so agents handle the queries and disputes, and it keeps agents away from patient card data entirely. - Collections servicers. Agencies running payment plans need a way for debtors to make each installment without an agent call. A self-pay line takes the scheduled payment at any hour, and mid-call transfer handles the payments agreed during a conversation. - Property managers. Rent is the definition of a routine, repeating payment. An IVR line gives tenants a way to pay by phone without the office handling a single card number. Most of these businesses collect money that belongs to their clients, which adds a routing requirement on top of the channel: each payment has to settle to the right client's own merchant account, not a pooled one. That's a solvable problem, covered in our guide to taking payments on behalf of your clients, and it applies to IVR payments the same as any other channel: each client's payments route to that client's own merchant account. ## Designing an IVR flow that completes payments An IVR payment flow lives or dies on completion rate, and the failures are predictable. The design notes that matter: - Keep the flow shallow. Every menu layer loses callers. A payment line should go from greeting to card prompt in as few steps as the lookup allows. - Accept the reference from the statement. The caller is holding the letter or statement that told them to call. Ask for the reference printed on it, in the format it's printed in, and confirm the account back to them. - Read back the amount before capture. Confirm what's being charged before asking for the card. It prevents disputes and gives the caller a clean point to bail out if something's wrong. - Offer a payment-link fallback by SMS. Some callers struggle with keypad entry: long card numbers, mobile handsets, mistyped digits. Offering to text a payment link lets them finish on their own screen instead of abandoning. - Keep a path to an agent. A caller who can't complete in the IVR should reach a person (or a callback queue) rather than a dead end. The agent can then take the payment with agent-assisted capture. None of this is exotic. It's the difference between an IVR that collects the routine volume and one that generates complaint calls. ## How to choose an IVR payment system Most IVR payment systems demonstrate well, because the demo is a caller keying in a card and a success message. The differences show up later, in what you had to change to get there and what happens when the flow does not fit. The questions worth asking: - Where does card data actually go? Ask for the data path in writing: which systems the digits pass through, what is retained, and what lands in your call recordings. If the card number touches your telephony platform at any point, that platform is in scope. - Which gateways does it work with? A system tied to a single processor means adding a phone channel forces a payments migration. Check that yours is supported before anything else, and check whether you can keep more than one if you collect for different entities. - Can callers move between the IVR and an agent? Mid-call transfer into the payment flow and back to the agent is the difference between an IVR that handles routine volume and one that dead-ends every caller with a question. - Does it cover your other phone patterns? Few operations run IVR alone. Agent-assisted capture for conversations, AI voice agents where those are deployed, and a link to fall back to when a card declines or a call drops all need to work off the same integration and reconcile in one place. - Can it route per client? If you collect on behalf of other businesses, each payment has to settle to that client's merchant account. Systems built for a single merchant make this a manual reconciliation problem later. - What do you have to build? Expect to build the agent-side screen for your own workflow. What you should not have to build is the capture, the compliance boundary or the gateway connections. - How is it priced? Per transaction and per agent seat behave very differently as you grow, particularly for seasonal or campaign-driven phone volume. Shuttle charges per transaction, with a monthly fee per live app, and never per agent seat. See pricing for current rates. ## How Shuttle handles IVR payments Shuttle provides IVR self-payment as part of one phone payments layer: - IVR payment flows run on Twilio voice infrastructure. Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Inbound self-pay, mid-call transfer and after-hours coverage all run on the same rails. - Card details are tokenized with the payment gateway itself. Shuttle holds no card vault of its own, so the IVR doesn't create a new place where card data accumulates. - Your gateway, not ours. Shuttle works with 30+ payment gateways, so IVR payments settle through the merchant account you already have. Voice capture works on many supported gateways; payment links cover the rest. - The fallbacks are built in. A payment link by SMS or email when keypad entry fails, agent-assisted capture when the call needs a human, and bank payment options where cards don't fit. - Multi-client routing. If you run an IVR line on behalf of many clients (statement printers, billing services, collections servicers, property managers), each client connects their own merchant account and every payment goes to the one you configured. ## IVR payments FAQ ### What is an IVR payment? An IVR payment is a card payment made through an automated phone menu, with no agent on the line. The caller enters a reference and their card details on their phone keypad, the digits route to the payment gateway for authorization, and the caller gets a confirmation. It's an unattended, card-not-present transaction. ### Are IVR payments PCI compliant? The pattern supports compliance well: card data goes from the caller's keypad to the payment gateway without entering your phone system, recordings or screens, so those systems stay out of PCI DSS scope. When the IVR is hosted by a validated provider, this typically supports the lightest self-assessment route for the merchant. Your exact SAQ level depends on your setup, so confirm it with your acquirer or assessor. ### Can callers pay after hours? Yes. An IVR payment line runs around the clock, so callers who ring in the evening, on weekends or from other time zones complete payments while your office is closed. For businesses that put a payment number on printed statements or letters, after-hours coverage is often where a large share of the volume arrives. ### What happens if the caller makes a mistake? Well-designed flows read back what was entered and let the caller correct it: re-enter the card number, fix the reference, or confirm the amount before anything is charged. If keypad entry keeps failing, the flow should offer a payment link by SMS so the caller finishes on their own screen, or route them to an agent. ### Can an agent transfer a caller to the IVR and get them back? Yes. Mid-call transfer hands the caller into the automated payment flow, and the flow can return the caller to the agent once the payment completes. The agent never hears or sees card details, the transaction stays unattended for compliance purposes, and the agent still closes the call personally. ### Does IVR work for payment plans? Yes. A payment plan needs each installment collected on schedule, and a self-pay line gives the payer a way to make each one without an agent call. Collections servicers commonly pair an agent conversation (where the plan is agreed) with IVR self-pay or scheduled payment links for the installments that follow. ### What does IVR payment mean? IVR stands for interactive voice response, the automated menu that answers a phone line and reads the caller's keypad presses. An IVR payment means paying through that menu rather than to a person: the caller keys in a reference and their card details, the system authorises the payment, and a confirmation closes the call. There is no agent on the line, and the card number goes straight to the gateway without entering your systems. ### What is an IVR payment gateway? The term usually means one of two things. Strictly, the gateway is the payment processor that authorises the transaction, and the IVR is the phone flow that captures the card and passes it on. Loosely, people use it for the combination of the two: the automated phone line plus the connection to their processor. If a supplier uses the phrase, ask which they mean, and specifically whether their system works with the gateway you already use. ### Is an IVR payment a MOTO transaction? Usually yes. A payment taken over the phone is card-not-present and is commonly processed as MOTO, short for mail order and telephone order. MOTO transactions are out of scope of strong customer authentication, under PSD2 in the EEA and under the UK's onshored SCA rules, which is why a MOTO-processed IVR payment does not carry a 3-D Secure challenge. That depends on how the transaction is submitted: if the flow finishes on a hosted payment page, or the payment is submitted as e-commerce, SCA applies. Confirm the classification and the associated rates with your gateway and acquirer. ### Can an IVR handle bill payments and account top-ups? That is the flow IVR suits best. Bill payments, statement balances, account top-ups and instalment payments all share the same shape: the caller knows the amount, holds a reference, and wants to pay without a conversation. Printing a payment number on the statement or letter that prompted the call closes the loop. ### How much do IVR payments cost? Pricing models vary more than the technology does. The two common shapes are a charge per transaction and a charge per agent seat, and which is cheaper depends on how your phone volume is distributed across the year. Shuttle charges per transaction, with a monthly fee per live app, and never per agent seat. See the pricing page for current rates. ## Related reading - PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - Agent-Assisted Payments: Secure Card Capture on Live Calls - DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking - Virtual Terminal Payments - Take Payments on Behalf of Your Clients - ACH and Bank Payments Over the Phone Want your routine phone payments handled without an agent on the line? Talk to us. If you'd rather explore the technical side first, docs.shuttleglobal.com covers the flows, with sandbox accounts available for testing. ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [agent-assisted capture](/guides/agent-assisted-payments/) - [agent-assisted DTMF capture](/guides/agent-assisted-payments/) - [DTMF payments](/guides/dtmf-payments/) - [payment link](/platforms/links-checkout/) - [payment providers](/payment-providers/) - [PCI compliant phone payments](/guides/pci-compliant-phone-payments/) - [taking payments on behalf of your clients](/guides/take-payments-on-behalf-of-clients/) - [pricing](/pricing/) - [30+ payment gateways](/payment-providers/) - [pricing page](/pricing/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [Agent-Assisted Payments: Secure Card Capture on Live Calls](/guides/agent-assisted-payments/) - [DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking](/guides/dtmf-payments/) - [Virtual Terminal Payments](/guides/virtual-terminal-payments/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [ACH and Bank Payments Over the Phone](/guides/ach-payments-over-the-phone/) - [Talk to us](/contact/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/kore-ai-payments/ --- # How to Take Payments on Kore.ai Voice Agents: PCI-Compliant Payments | Shuttle > Kore.ai is an enterprise agentic and conversational AI platform used to build production AI agents across voice, chat, SMS, web, and social channels. # How to Take Payments on Kore.ai Voice Agents: PCI-Compliant Payments By Shuttle Team, May 27, 2026 Kore.ai is an enterprise agentic and conversational AI platform used to build production AI agents across voice, chat, SMS, web, and social channels. It is especially strong in banking, financial services, healthcare, retail, and telecom, where large organisations use it to automate high-volume customer interactions at scale. Kore.ai is built to run the conversation and orchestrate the systems already in place. In banking deployments, that often means triggering an institution's existing bill-pay or payment rails through integrations. What Kore.ai does not do is capture or process a card in the call itself. There is no native merchant product, no native payment service provider, and no "take a card during the conversation" capability inside the AI pipeline. That distinction matters. Orchestrating an existing bill-pay rail is not the same as accepting a new card payment from a caller in a PCI-compliant way. For many use cases, from collections to outbound sales to ad-hoc support payments, you need to take the card there and then. This guide explains the payment gap, and how Shuttle adds the payment layer that handles PCI-compliant card capture, SMS or email payment links, and routing to 30+ gateways alongside a Kore.ai deployment. ## The Payment Challenge for Kore.ai The core problem is simple: card data cannot safely enter the AI pipeline. The moment a caller reads or keys a card number into a Kore.ai voice agent, those digits flow through transcription, logging, and model infrastructure that was never designed to be in scope for cardholder data. That is a serious PCI liability. Orchestrating an institution's bill-pay rails sidesteps this for known, stored payment methods, but it does not let you accept a new card from a caller in real time. Bill-pay orchestration and new-card capture are two different jobs. Building PCI Level 1 capture yourself is expensive and slow. Most teams find it costs $500k+ upfront and $200k+ per year to build and maintain compliant infrastructure, audits included. That is before you have processed a single payment. Bolting on a separate payment line or "press 1 to be transferred to pay" also breaks the experience. You lose the conversational flow Kore.ai was chosen to deliver, and you add drop-off at the exact moment you want a completed payment. ## How Shuttle Works with Kore.ai Today Shuttle has no native integration with Kore.ai. Instead, you invoke Shuttle's Twilio-based payment setup. The handoff is API-driven: your application code triggers the Shuttle payment handoff at the point of payment. To use the voice capture path, you must be a Twilio customer. - Your Kore.ai agent handles the conversation as it does today across voice, chat, or SMS. - When it is time to pay, your application code triggers the Shuttle payment handoff. - At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The card digits are captured inside Shuttle's certified environment and never reach Kore.ai, the LLM, or the agent. - Shuttle routes the transaction to your chosen gateway from 30+ supported providers. - The authorisation result is returned to your application, which confirms the outcome. You build the orchestration and agent-side wiring yourself. Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app before going live. Honest caveat: secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Kore.ai agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. A native Kore.ai integration is possible only as a paid project. ## How It Works: Step by Step - The caller reaches a point where payment is needed (a bill, a balance, an order). - The Kore.ai agent confirms the amount and reference. - Your application code triggers the Shuttle payment handoff. - At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. - The caller enters card details on the keypad. The digits are captured inside Shuttle's certified environment, so they never reach Kore.ai, the recording, or your systems. - Card data is tokenised inside Shuttle's PCI Level 1 environment. - Shuttle routes the payment to your configured gateway. - The authorisation result returns to your application. - Your application records the outcome and the agent confirms the result. ## Multi-PSP Support Shuttle is gateway-neutral and routes to 30+ payment gateways, including: - Checkout.com This matters for Kore.ai's enterprise and banking customers. Many have a mandated acquirer or gateway already in place, and Shuttle routes to it rather than forcing a switch. Switching or adding a gateway is configuration, not re-integration. For platforms and BPOs serving multiple clients, Shuttle supports multi-tenant routing, so each client's payments settle to their own gateway. A note on gateways: a few gateways (for example, Braintree) do not work for voice capture, because they will not allow raw card data to be passed, but they do work for payment links. Switching between gateways is configuration, not a new integration. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of compliance. When the call is handed to Shuttle's secure capture, cardholder data stays inside Shuttle's certified environment and never enters Kore.ai's voice, chat, or logging systems. This keeps your Kore.ai deployment out of PCI scope for card capture. In practical terms, it can keep you on a lighter SAQ-A posture (where you never see or store card data) rather than the far heavier SAQ-D obligations that apply when card data flows through your own systems. ## Beyond Voice: Payment Links Payment links are the turnkey path. Not every payment needs to happen mid-call, and links work even with gateways that do not support voice capture. Shuttle can send an SMS or email payment link directly from a Kore.ai interaction, including mid-call. The agent confirms the amount, Shuttle sends a hosted, PCI-compliant link, and the customer pays on their own device. This is ideal for chat and SMS channels, higher-value transactions, or any case where the customer prefers to enter card details themselves on a secure page. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Bill-Pay and Account Payments Let customers pay a bill or top up an account in a single Kore.ai conversation, capturing a new card when there is no stored method to orchestrate. ### Collections and Payment Plans Take a payment or set up a plan during outbound or inbound collections calls, with compliant capture and routing to the creditor's mandated gateway. ### Customer Support Payments Handle ad-hoc payments in support flows (a fee, a replacement, an upgrade) without transferring the caller to a separate line. ### Outbound Sales Close and capture payment in the same outbound Kore.ai call, turning a confirmed yes into a completed transaction before the caller hangs up. ## FAQ Does Kore.ai process card payments natively? No. Kore.ai runs the conversation and can orchestrate an institution's existing bill-pay or payment rails through integrations, but it does not capture or process new card payments in the call. Shuttle adds that capability via a secure Twilio Pay handoff. Does Shuttle have a native Kore.ai integration? No. Shuttle has no native Kore.ai integration. You invoke Shuttle's Twilio-based setup, and your application code triggers the payment handoff at the point of payment. A native Kore.ai integration is possible only as a paid project. Does this require Twilio? Yes, for the voice capture path today. The secure capture runs via Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Payment links do not require Twilio. How do I take PCI-compliant payments with Kore.ai? Invoke Shuttle's Twilio-based setup. At the point of payment, your application code triggers the handoff, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, the card digits are captured inside Shuttle's certified environment, and the result returns to your application. Which payment gateways does Shuttle support? Shuttle routes to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie, so you can keep your existing or mandated provider. A few gateways (for example, Braintree) do not work for voice but do work for payment links. Switching is configuration, not re-integration. Why not build PCI payment capture ourselves? You can, but PCI Level 1 infrastructure typically costs $500k+ upfront and $200k+ per year to build and maintain. Shuttle gives you the same capability at $0.20 per successful transaction with no setup or per-seat fees. Can I take payments on outbound Kore.ai calls? Yes. Shuttle supports both inbound and outbound flows, so your agents can capture payment during outbound collections or sales calls. ## Related Reading - AI Voice Agent PCI Payments: how PCI-compliant capture works behind any AI voice agent. - Voice Payments: taking secure payments over voice channels. - The Payment Layer for AI Agents: why payments sit as a layer beneath your agent platform. - Cognigy Payments: the same gap-fill approach for another enterprise conversational AI platform. - Contact Centre Payments: payment capture across contact centre and CCaaS deployments. ## Add Payments to Your Kore.ai Agents Shuttle is the payment layer that adds PCI-compliant capture via a secure Twilio Pay handoff, SMS and email payment links, and routing to 30+ gateways at $0.20 per successful transaction. Read the Twilio setup docs, the payment links docs, and the security overview. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ supported providers](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Cognigy Payments](/guides/cognigy-payments/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Twilio setup docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links docs](https://docs.shuttleglobal.com/docs/links-intro) - [security overview](https://docs.shuttleglobal.com/docs/org-security) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/lindy-payments/ --- # How to Take Payments on Lindy: PCI-Compliant AI Agent Payments | Shuttle > Lindy is a no-code AI agent builder that lets businesses create "AI employees": autonomous agents that handle email triage, meeting scheduling, CRM... # How to Take Payments on Lindy: PCI-Compliant AI Agent Payments By Shuttle Team, June 3, 2026 Lindy is a no-code AI agent builder that lets businesses create "AI employees": autonomous agents that handle email triage, meeting scheduling, CRM updates, and phone calls without human intervention. Its phone capability, Lindy Gaia, lets teams deploy inbound and outbound voice agents that can qualify leads, answer queries, book appointments, and follow up on outstanding tasks. Businesses use Lindy across sales, customer support, and operations to reduce the manual overhead of repetitive communications work. The payment wall is a predictable friction point for Gaia deployments. Lindy does connect to Stripe, but that integration is read-only workflow automation: it triggers on Stripe events (payments received, invoices created), retrieves invoice and refund data, and feeds that into downstream Lindy workflows. It is used primarily for internal operations and billing Lindy's own subscribers, not for capturing card details from a Lindy user's customers. Gaia itself has no DTMF suppression, no PCI-compliant capture path, and no ability to initiate a customer charge inside a call. When a Gaia agent reaches the payment moment, whether that is closing an inbound sale, collecting an overdue balance, or taking a deposit, it has no native way to handle it securely. This guide is for developers and operations teams building Lindy Gaia workflows that need to take payments from customers: inbound sales calls, outbound collections, appointment deposits, and subscription renewals. It explains how to connect Shuttle's PCI DSS Level 1 payment layer to Lindy so Gaia agents can complete transactions without card data ever touching Lindy's infrastructure. There is no native Lindy integration: instead, your application invokes Shuttle's Twilio-based secure capture, which does require you to be a Twilio customer today. ## The Payment Challenge for Lindy Agents Lindy's compliance posture covers what its core product handles. The platform holds SOC 2 Type II, GDPR, HIPAA, and PIPEDA certifications. PCI DSS is not on that list because Lindy is not a payment processor and does not handle cardholder data. That is not a criticism: it is a sensible scope decision for a workflow automation platform. The practical consequence is that any Gaia agent that needs to collect a card payment runs into a hard wall. You cannot instruct Gaia to ask for a card number and store it, because there is no compliant capture mechanism to do so. Asking a customer to read card digits aloud on a call that is not PCI-scoped creates a PCI scope problem for your organisation immediately. Teams working around this today typically end the call, send a payment link by email, and ask the customer to complete checkout separately. That break in the conversation costs conversions. Customers who are ready to pay during the call do not always come back. Shuttle closes this gap by acting as the compliant payment capture layer your application hands the payment to, without requiring Lindy to become a payments platform. ## How Shuttle Works with Lindy Today There is no native Lindy integration. The handoff is API-driven and built on Shuttle's Twilio-based capture: you must be a Twilio customer, and your application code triggers the handoff at the point of payment via webhook. For non-voice channels, Shuttle provides hosted payment links. The flow for a voice call is straightforward: - Gaia runs the call and handles the full conversation: qualification, product explanation, pricing, and any objections. When the customer confirms they want to pay, the workflow reaches the payment handoff point. - Your application triggers Shuttle via a webhook or API call, passing session context (amount, currency, customer reference, provider selection). - A secure PCI capture takes the card. At the point of payment, the card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay, with Shuttle as the certified connector). The customer keys their card number on their phone keypad, and the digits are captured directly inside Shuttle's certified environment. The card number is never spoken aloud and never reaches Lindy or Gaia. - Shuttle processes and routes the transaction to your chosen payment gateway, applies the per-tenant or per-merchant provider selection, and handles authorisation and confirmation. - Shuttle returns the result to your application. Gaia receives a success or failure signal and continues the conversation accordingly, confirming the payment, offering a receipt, or handling a retry. Card data never enters Lindy at any point in this flow. Lindy and Gaia remain entirely outside PCI scope, which simplifies your compliance obligations significantly. One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Gaia agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native Lindy integration is possible only as a paid project. ## Multi-PSP Support Shuttle connects to 30+ gateways through a single integration. You are not locked to one processor: Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie are all supported, alongside regional and specialist processors. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed. For teams building multi-client or multi-tenant Gaia deployments, Shuttle supports per-tenant payment routing. Each client or business unit can use its own gateway credentials, settlement account, and currency configuration, while sharing the same Lindy workflow template. You can also bring your existing gateway relationship rather than switching processors, and you can move the affected payment types to another connected gateway if a primary is unavailable. This is particularly useful for agencies building Lindy-powered voice agents across multiple customers, where each customer needs payments to settle into their own merchant account. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, the highest certification tier for payment processors. The practical implication for your Lindy deployment is scope reduction. Because Shuttle handles all cardholder data capture, storage, and transmission, your Lindy environment and your Gaia agents are not in scope for PCI DSS. You move from SAQ-D (the most demanding self-assessment questionnaire, covering full cardholder data environments) toward SAQ-A (the lightest category, applicable when all capture is outsourced to a certified provider). Your annual compliance effort shrinks substantially. Shuttle does not vault card data on your behalf. Card numbers are passed directly to your gateway for authorisation and are not stored in Shuttle's infrastructure after the transaction. This no-vault posture reduces the attack surface further and keeps Shuttle's own PCI scope tight. ## Beyond the Call: Payment Links Gaia is not the only channel where Lindy agents operate. Lindy runs across email, Slack, Teams, and thousands of other connected apps via Pipedream's 5,000+ integrations. For these non-voice channels, Shuttle provides hosted payment links. A Lindy email or Slack agent can generate a Shuttle payment link as part of an automated workflow, insert it into a message, and send it to the customer. The customer clicks through to a Shuttle-hosted checkout page, enters card details there, and the result is returned to your application for downstream processing. No card data passes through Lindy's environment at any point. Payment links are the turnkey path: they can be sent by SMS or email, including mid-call, and work even with gateways that do not support voice capture. This means a single Lindy workflow can handle both the conversation and the payment across channels: voice via Gaia with the secure capture, and email or messaging via hosted payment links. ## Use Cases ### Inbound Sales and Order Taking Gaia agents handling inbound sales calls frequently reach a point where the customer is ready to buy. Rather than ending the call and sending a follow-up email, your application can hand off to Shuttle's secure capture at the point of payment. The customer keys their card on the keypad, the transaction is authorised, and the result is confirmed. Capturing payment while intent is highest converts better than post-call payment requests. For flows where you would rather avoid the keypad capture entirely, a payment link sent mid-call by SMS is the turnkey alternative. ### Outbound Collections and Payment Plans Outbound Gaia agents used for debt collection or account recovery can present balance information, negotiate payment plans, and then collect the first payment in the same call. Shuttle supports instalment structures and recurring payment setups, so a collections agent can lock in a plan and take the initial payment without requiring the customer to visit a portal or wait for a link. ### Appointment Deposits Service businesses using Gaia to handle booking calls often require a deposit to confirm an appointment. Shuttle allows Gaia to collect the deposit at the end of the booking conversation, reducing no-shows and removing the friction of a separate payment step that customers frequently abandon. ### Subscription and Renewal Payments Lindy's workflow automation is well suited to subscription management: renewal reminders, failed payment retries, and plan upgrade conversations. Where those workflows involve Gaia calls, Shuttle handles the card capture for renewal or upgrade payments, with the result fed back into Lindy's CRM and billing workflows. ## FAQ Does Lindy process payments natively? No. Lindy does not have a customer-facing payment capture product. Its Stripe integration is read-only workflow automation: it triggers on Stripe events (payments received, invoices created) and retrieves invoice or refund data for use in Lindy workflows. It is not a mechanism for charging a Lindy user's customers and does not handle cardholder data. Does Shuttle have a native Lindy integration? No. There is no native Lindy integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native Lindy integration is possible only as a paid project. Does this require Twilio? Yes, today. The secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. How do I take PCI-compliant payments on Lindy Gaia? Connect Shuttle to your workflow via webhook or API. When the workflow reaches the payment moment in a call, your application triggers Shuttle, which handles the card in a secure PCI DSS Level 1 capture (today, via Twilio Pay). Card data never enters Lindy or Gaia. Shuttle processes the transaction against your chosen gateway and returns a success or failure signal to the workflow. Which gateways does Shuttle support? Shuttle connects to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. You can bring your existing gateway or use a new one. Switching gateway is configuration, not re-integration. Per-tenant routing is supported for multi-client deployments. A few gateways (Braintree, for example) work for payment links but not for voice capture. Does this work for outbound calls? Yes. Gaia outbound calls follow the same pattern as inbound. The Shuttle capture is triggered by your application when the workflow reaches the payment point, regardless of whether the call was initiated by the agent or the customer. Can Lindy's Stripe integration capture customer card payments? No. The Stripe connection in Lindy is an event-driven workflow automation tool. It listens for Stripe webhooks (a payment succeeded, an invoice was created, a refund was issued) and uses that data to trigger or inform other Lindy workflows. It does not provide a mechanism for a Gaia agent to initiate a charge against a customer's card, and it does not handle cardholder data in any form. For actual card capture, a dedicated PCI-compliant layer like Shuttle is required. ## Related Reading - The Payment Layer for AI Agents: how a compliant payment layer fits into AI agent infrastructure - AI Voice Agent PCI Payments: secure card capture and PCI scope reduction for voice agents - Voice Payments: end-to-end guide to PCI-compliant payment capture over phone and IVR - Vapi Payments: adding payment capture to Vapi AI voice agents - Bland AI Payments: payment integration for Bland AI phone agent deployments ## Add Payments to Your Lindy Agents Shuttle is a PCI DSS Level 1 Service Provider with connections to 30+ gateways. Voice pricing is $0.20 per successful transaction with no setup fees, monthly fees, or per-seat charges; Links Checkout is a separate app; see /pricing/, with a new model coming (see pricing). Your Lindy environment stays out of PCI scope, Gaia agents take payment at the point of capture, and card data never touches Lindy's infrastructure. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF suppression](/guides/dtmf-payments/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ gateways](/payment-providers/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [see pricing](/pricing/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/liqpay-twilio-integration/ --- # How to Connect LiqPay to Twilio for Voice & IVR Payments | Shuttle > LiqPay doesn't natively connect to Twilio for voice payments. If you want to process LiqPay transactions during a phone call (via IVR, agent-assisted, or... # How to Connect LiqPay to Twilio for Voice & IVR Payments By Shuttle Team, July 4, 2026 LiqPay doesn't natively connect to Twilio for voice payments. If you want to process LiqPay transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects LiqPay (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why LiqPay + Twilio Don't Connect Directly LiqPay is PrivatBank's payment service and one of the most widely used payment providers in Ukraine. It handles card payments (Visa and Mastercard), Privat24-based payment confirmation, and hryvnia (UAH) processing for Ukrainian businesses, from major marketplaces to utilities. Its APIs are built for online checkout: hosted payment pages, server-to-server requests, and callbacks. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. LiqPay isn't one of Twilio's built-in connectors, so there's no native path from a Twilio call flow to your LiqPay account. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to LiqPay's API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via LiqPay. The connector creates a LiqPay payment request, processes the transaction through your LiqPay merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the LiqPay transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A LiqPay merchant account with API credentials (public key + private key, found in your company settings under the API tab) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add LiqPay Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: LiqPay - Public key: Your LiqPay public key - Private key: Your LiqPay private key - Currency: Set your default (UAH, or another supported currency) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your LiqPay account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code (UAH for hryvnia) - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in your LiqPay account if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test LiqPay provides a dedicated test environment: your test public key and private key carry a prefix, and sandbox transactions return a "sandbox" status rather than "success". Add your test keys to a Shuttle payment profile set to Test, run the full Twilio call flow end-to-end, then swap in your live keys when you're ready. ## What You Can Do With LiqPay + Twilio ### Charge Immediately Standard charge. The caller pays, LiqPay processes the payment in UAH through PrivatBank rails, done. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Serve Ukrainian Customers From Any Contact Centre Your contact centre doesn't need to be in Ukraine to take UAH payments from Ukrainian cardholders. A BPO or offshore support team can collect payments over the phone through your LiqPay account, with card data kept out of the agent environment entirely. ### Automate With IVR and AI Voice Agents The same connector works for fully automated flows. An IVR or AI voice agent can quote an amount, trigger , and confirm the LiqPay transaction without a human agent on the line. ## Multi-PSP: Beyond LiqPay One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Ukrainian merchants with LiqPay and your EU or US merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway is unavailable, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle handles which gateway processes the transaction: by merchant, region, amount, or failover rules. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own LiqPay account (or any other gateway) through the same Twilio integration. ## PCI Compliance The LiqPay + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing LiqPay (PCI DSS certified) Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to LiqPay. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect LiqPay to Twilio without Shuttle? Twilio doesn't have a built-in LiqPay Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Can I take UAH payments over the phone? Yes. Set the parameter to UAH in your verb and the transaction processes in hryvnia through your LiqPay account. What about LiqPay's test environment? Fully supported. LiqPay issues test keys with a prefix. Add them to a Shuttle payment profile set to Test and run the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. LiqPay's standard processing fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from LiqPay to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice Payments: step-by-step Adyen + Twilio setup - LiqPay: LiqPay on Shuttle: supported features and channels - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect LiqPay to Twilio in minutes with Shuttle's Pay Connector. PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [BPO](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [LiqPay](/payment-providers/liqpay/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout→](/blog/payment-links-for-liqpay/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/liveperson-payments/ --- # LivePerson Payments: Multi-PSP Capture Across Messaging and Voice | Shuttle > LivePerson runs the Conversational Cloud, an enterprise conversational AI and digital-messaging platform. # LivePerson Payments: Multi-PSP Capture Across Messaging and Voice By Shuttle Team, May 10, 2026 LivePerson runs the Conversational Cloud, an enterprise conversational AI and digital-messaging platform. It is messaging-first: web and in-app messaging, SMS, WhatsApp, Apple Messages for Business, RCS and Facebook Messenger sit at the centre, with conversational bots and human agents handling customers across all of them. If you are a merchant running customer conversations on LivePerson, or a system integrator implementing it, payments are a natural extension of those conversations. LivePerson already orchestrates payments. Through Bring Your Own Payments (BYOP) in Conversation Builder, an Apple Pay integration, and a specialist partnership for PCI-descoped capture, customers can transact inside the conversation. LivePerson is messaging-first today, with its voice and agentic story growing (it is being acquired by SoundHound AI, announced April 2026, to add voice and agentic AI capabilities). This guide is for merchants and SIs weighing when a single multi-PSP payment layer that spans both messaging and voice fits alongside what LivePerson provides. The goal is not to replace LivePerson's orchestration. It is to show where one payment layer across channels, with gateway breadth and secure in-call capture, adds value, and exactly what that involves with Shuttle today. ## LivePerson's Payments Today: What You Get LivePerson does not process cards itself. It orchestrates payment flows so the customer transacts without leaving the conversation: - Bring Your Own Payments (BYOP) in Conversation Builder lets you connect your existing payment provider into the conversational flow. LivePerson orchestrates the steps; your provider processes the card. - Apple Pay integration supports a fast, native checkout for customers in supported channels. - PCI-descoping partnership (announced August 2024) adds secure, PCI-descoped payment capture inside Conversational Cloud, designed to remove agents from PCI DSS scope. - Enterprise compliance, including PCI-DSS, is part of LivePerson's platform posture. This is a capable starting point. If your business already routes through one payment provider and your conversations are messaging-only, BYOP plus LivePerson's PCI-descoping partner may cover what you need. The questions below help you decide when a broader layer is worth adding. ## When a Multi-PSP Layer Across Channels Helps A dedicated payment layer like Shuttle fits when you need more than a single provider wired into a single channel: - One layer across messaging and voice. LivePerson is messaging-first, with voice growing. A single payment layer covers messaging links and in-call voice capture so the experience is consistent as your voice channels expand. - 30+ payment gateways. Connect 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square, rather than wiring up one provider per flow. - Bring your own gateway. Keep your existing acquiring relationships and processing rates. Shuttle routes; it does not force a switch. - Per-client and per-tenant routing. Route different brands, regions or business units to different gateways from one integration. - PCI DSS Level 1 as a certified Service Provider, with secure in-call capture for voice conversations. ## How Shuttle Adds Payments to LivePerson Shuttle adds PCI-compliant card capture to your LivePerson payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your LivePerson recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for LivePerson specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your LivePerson call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running LivePerson have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent and bot workflow In a messaging conversation, a bot or human agent shares a Shuttle payment link at the right step. The agent never sees or handles card numbers. In a voice conversation, the agent initiates a secure capture session via Twilio Pay and stays on the line while the customer keys in card details; the digits are captured inside Shuttle's certified environment, so the agent and any call recording never receive them. Confirmation lands back in the agent workspace so the conversation can continue. ### Customer experience The customer pays where they already are. In messaging, they tap a link, see a branded checkout, and pay with card or Apple Pay without downloading an app or leaving the thread. On voice, they enter card details on their phone keypad in the secure call while the agent waits, with no need to read numbers aloud. The result is one consistent, secure flow across channels. ## Multi-PSP Support - Connect 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square. - Bring your own gateway and keep existing acquiring and pricing. - Route per client, per brand, per region or per business unit from a single integration. - Add or switch gateways without rebuilding your conversational flows; gateway choice is configuration, not re-integration. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. - Pricing is $0.20 per successful transaction for voice with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Card data is captured inside Shuttle's compliant environment via the secure Twilio Pay call and never reaches LivePerson, your agents or your infrastructure. That keeps card data out of your PCI scope: instead of the broader SAQ-D obligations that apply when sensitive data touches your systems, most merchants using Shuttle qualify for the lighter SAQ-A. The effect is similar in spirit to what LivePerson's descoping partner offers for messaging, extended across messaging and voice through one layer. Full compliance documentation is in the security docs. ## Beyond Messaging: Voice Capture LivePerson's voice and agentic story is growing. As you add voice channels, payments need to follow. Shuttle provides secure in-call capture via Twilio Pay: the customer types card details on the phone keypad during a live call, the digits are captured inside Shuttle's certified environment before they reach the agent or the recording, and the transaction is processed in the background. The agent stays in conversation throughout. One payment layer covers both your messaging conversations today and your voice conversations as they scale, with no second integration to maintain. ## For Solution Providers and LivePerson Implementation Partners If you implement LivePerson for clients, Shuttle is the certified payment capture you add through the LivePerson Developer Center (developers.liveperson.com) and Twilio. The same surface where BYOP, Apple Pay and custom integrations are built, using the platform's APIs and Functions, is where you wire Shuttle in: - Use Functions and API integrations to trigger Shuttle payment sessions from bot or agent workflows. - Deliver hosted payment links into messaging conversations, and secure capture sessions into voice flows. - Keep card data outside the LivePerson environment so your client's PCI scope stays minimal. - Offer per-client gateway routing so one implementation pattern serves multiple brands. You build the agent-side and bot-side interface against Shuttle's APIs once and reuse it across clients, and a native LivePerson integration is available as a paid project. This lets you deliver payment capture as a repeatable part of your LivePerson builds, across messaging and voice, without becoming a payments company yourself. ## Use Cases ### Conversational Commerce and Order Taking Let customers complete a purchase inside a messaging or voice conversation, with the gateway and methods you already use. ### Bill-Pay and Account Payments Collect outstanding balances and recurring bills in-conversation, with secure links or in-call capture and instant confirmation. ### Bookings and Deposits Take deposits and booking payments at the moment of intent, before the conversation ends, across any channel. ### Customer Support Payments Resolve payment-related support issues in the same thread or call, from upgrades to renewals, without handing customers off. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged LivePerson plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for LivePerson specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your LivePerson call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running LivePerson have already done it. - A native LivePerson integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Shuttle have a native LivePerson integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in LivePerson. You'll need to be a Twilio customer and to build the agent-side and bot-side interface for your workflow against Shuttle's APIs. We can build a native LivePerson integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Does LivePerson take payments? Yes, by orchestration. LivePerson does not process cards itself, but through BYOP in Conversation Builder, an Apple Pay integration and its PCI-descoping partnership, customers can pay inside the conversation while your provider processes the card. What does Shuttle add? One payment layer across messaging and voice, 30+ gateways with bring-your-own-gateway, per-client routing, PCI DSS Level 1 capture, and secure in-call capture for voice via Twilio. Which gateways does Shuttle support? 40+ including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square. You can keep your existing acquiring relationship and route per client or brand. Switching gateways later is configuration, not re-integration. Can it handle outbound conversations? Yes. Payment links and in-call capture work in outbound messaging and outbound voice, such as collections, renewals and proactive billing. How much does it cost? $0.20 per successful transaction for voice, with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - Contact centre payments: the hub for secure payment capture across contact centre channels. - Embedded payments for CCaaS: how payment capture embeds into conversational and contact centre platforms. - AI voice agent PCI payments: taking PCI-compliant payments on AI voice agents. - Zendesk payments: payment capture for another messaging-first support platform. - Payments for CCaaS implementation partners: how SIs add a payment layer to contact centre builds. ## Take Payments Across Messaging and Voice in LivePerson Add one PCI Level 1 payment layer to your LivePerson conversations via Twilio, with 30+ gateways, per-client routing and secure in-call capture across messaging and voice. We'll walk you through what's live today and the path for your setup. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [30+ payment gateways](/payment-providers/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [$0.20 per successful transaction](/pricing/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [30+ gateways](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI voice agent PCI payments](/guides/ai-voice-agent-pci-payments/) - [Zendesk payments](/guides/zendesk-payments/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/marketplace-payment-solutions/ --- # Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale | Shuttle > What Are Marketplace Payment Solutions? A marketplace payment solution is the infrastructure that handles money movement between buyers, sellers, and the... # Marketplace Payment Solutions: How to Handle Multi-Party Payments at Scale By Shuttle Team, March 1, 2026 ## What Are Marketplace Payment Solutions? A marketplace payment solution is the infrastructure that handles money movement between buyers, sellers, and the marketplace operator. Unlike standard ecommerce payments -- where one merchant collects from one customer -- marketplaces involve at least three parties in every transaction: the buyer, the seller (or service provider), and the platform itself. This creates problems that standard payment gateways weren't built to solve. Funds need to be split between multiple recipients. Sellers need onboarding and identity verification. The marketplace needs to take its commission before paying out. Refunds need to reverse through the same split logic. And regulators want to know who is holding money, for how long, and under what licence. Marketplace payment solutions exist to handle all of this -- split payments, seller onboarding, automated payouts, compliance, and reporting -- so the platform can focus on building its core product rather than becoming a payments company. ## Key Challenges of Marketplace Payments ### Split Payments and Multi-Party Settlement Every marketplace transaction involves splitting funds. A customer pays £100 for a service. The marketplace takes a 15% commission. The seller receives £85. Sounds simple -- until you add VAT handling, tip distribution, multi-vendor carts (where a single order goes to three different sellers), or delayed fulfilment where the marketplace holds funds in escrow until delivery is confirmed. The payment solution must support configurable split logic at the transaction level, not just at the account level. Different sellers may have different commission structures, different payout schedules, and different currencies. ### Seller Onboarding and KYC Every seller on your marketplace needs identity verification before they can receive funds. This is a regulatory requirement -- Know Your Customer (KYC) and Know Your Business (KYB) -- and it's the marketplace's responsibility to ensure it happens. Bad onboarding creates two problems: friction that stops sellers from joining, and compliance gaps that expose the marketplace to regulatory risk. The payment solution should handle KYC/KYB within the platform's branded flow, so sellers never leave the marketplace experience. ### Compliance and Money Transmission Depending on your jurisdiction, holding funds on behalf of sellers -- even briefly -- may require a money transmission licence or e-money licence. Marketplaces that collect payment from buyers and then pay out to sellers are in regulatory scope. The structure of your payment solution determines whether you carry this burden directly or whether a licensed provider handles it on your behalf. Getting this wrong is expensive. Getting it right means choosing infrastructure that limits the marketplace's PCI scope and keeps the marketplace off the hook for money transmission licensing. ### Payouts Across Geographies A UK marketplace with sellers in Germany, the US, and Australia needs to handle multi-currency payouts, local banking formats, and regional tax reporting. Each new geography adds compliance requirements and banking relationships. The payment solution either supports this natively or forces the marketplace to build country-by-country integrations. ### Fraud and Dispute Management Marketplace fraud is structurally different from merchant fraud. Fake sellers, inflated refund claims, buyer-seller collusion, and triangulation fraud all require marketplace-specific detection. Disputes in a marketplace context involve three parties -- the buyer, the seller, and the platform -- and the payment solution needs to support workflows for all three. ## Types of Marketplace Payment Models There are four models marketplaces typically adopt for payment infrastructure. Each involves different trade-offs around control, compliance burden, time to market, and flexibility. ### 1. Aggregator Model The marketplace processes all transactions under its own merchant account. Sellers are sub-merchants. The marketplace takes full responsibility for compliance, fraud, and seller payouts. Pros: Maximum control over the payment experience. Full revenue capture. Cons: Regulatory burden (money transmission licensing, PCI compliance, KYC obligations). Requires significant capital and compliance infrastructure. This is effectively becoming a PayFac -- with all the cost and complexity that entails. Best for: Very large marketplaces with dedicated compliance teams and processing volume to justify the investment. ### 2. PSP Platform Product (Stripe Connect, Adyen for Platforms) The marketplace uses a single PSP's purpose-built marketplace product. The PSP handles seller onboarding, split payments, compliance, and payouts. Pros: Fast time to market. Strong developer experience. Compliance handled by the PSP. Cons: All sellers must use the same PSP. Enterprise sellers with existing payment relationships can't bring their own provider. The marketplace is locked into one vendor's pricing, capabilities, and geographic coverage. Best for: Marketplaces in early or growth stage that need to ship fast and are comfortable with single-PSP dependency. ### 3. PayFac-as-a-Service Providers like Payrix (now Worldpay for Platforms) or Finix offer "PayFac in a box" -- marketplace-specific payment infrastructure without building it from scratch. Pros: PayFac-like economics without the full build. Faster than building your own. Cons: Still typically locks you into one processing network. Enterprise PSP flexibility is limited. Ongoing compliance obligations remain. Best for: Marketplaces that want PayFac economics but can't justify a full PayFac build. ### 4. PSP-Neutral Payment Layer A payment layer sits between the marketplace and multiple PSPs. Sellers connect through whichever gateway suits their geography, volume, or existing relationship. The marketplace integrates once and supports 40+ payment providers through a single API. Pros: Full PSP flexibility -- sellers bring their own provider or the marketplace selects the best option per market. White-label experience. Multi-channel support (checkout, payment links, voice, chat). PCI compliance included. Cons: Less granular control than building your own PayFac. Commercial model rather than full margin capture. Best for: Marketplaces selling to enterprise buyers or operating across multiple geographies where PSP flexibility is a commercial requirement. ## Essential Features to Look For When evaluating marketplace payment solutions, these capabilities separate infrastructure that scales from infrastructure you'll replace in 18 months. ### Split Payment Configuration Can you define splits at the transaction level? Can you handle multi-vendor carts where a single payment is distributed to three or four sellers plus the marketplace commission? Can splits accommodate tips, taxes, and platform fees as separate line items? ### Seller Onboarding Is KYC/KYB built into the platform, or do you need to build the flow yourself? Can sellers complete onboarding without leaving your marketplace's branded experience? What's the typical time from seller application to first payout? ### PSP Flexibility Can different sellers use different payment providers? Can the marketplace switch or add PSPs without re-integrating? This matters most when enterprise sellers mandate their own PSP -- a requirement that kills deals if your infrastructure doesn't support it. ### Payout Management Does the solution handle automated payouts to sellers? Can you configure payout schedules (daily, weekly, on fulfilment)? Does it support multi-currency payouts and local banking formats? ### Multi-Channel Payment Capture Payments don't only happen at checkout. Does the solution support payment links for invoice-based marketplaces? Voice payments for phone-based booking? Chat payments for conversational commerce? A marketplace that starts with checkout-only will likely need additional channels within 12 months. ### White-Label Depth Does your brand appear everywhere -- checkout, seller dashboard, onboarding emails, payout notifications? Partial branding (marketplace checkout but PSP-branded seller portal) undermines the perception that payments is your capability. ### Compliance Coverage What's your PCI scope? Who handles money transmission compliance? Is the provider PCI DSS Level 1 certified? Do they carry ISO 27001 and SOC 2? These questions determine whether your compliance team grows from zero to ten or stays at zero. ## Popular Marketplace Payment Solutions Compared ### Stripe Connect What it is: Stripe's platform and marketplace payment product. Supports Custom, Express, and Standard account types with varying levels of marketplace control. Strengths: Best-in-class developer experience. Strong documentation. Global coverage. Handles seller onboarding, split payments, and payouts. Well understood by engineering teams. Limitations: All sellers must process through Stripe. Enterprise sellers with existing Worldpay or Adyen relationships can't bring their provider. Pricing becomes a constraint at scale. Geographic gaps in some markets. The marketplace's commercial leverage diminishes as dependency deepens. Best for: Early-stage to mid-market marketplaces that prioritise speed to market and developer experience over PSP flexibility. ### Adyen for Platforms What it is: Adyen's marketplace and platform product, built on their acquiring infrastructure. Strengths: Strong enterprise capabilities. Own acquiring licences in major markets (reducing intermediary costs). Good multi-currency and multi-entity support. Split payment functionality through their platform product. Limitations: Adyen wants to be the acquirer -- sellers process through Adyen. Not PSP-neutral. Pricing and onboarding better suited to high-volume enterprise than early-stage. Integration is more involved than Stripe. Best for: Enterprise marketplaces with high volume and a preference for working with a single full-stack acquirer. ### PayPal for Marketplaces What it is: PayPal's commerce platform product, including PayPal Complete Payments and Braintree marketplace capabilities. Strengths: Brand recognition reduces buyer friction. PayPal balance and BNPL options. Wide consumer adoption. Decent split payment and payout capabilities. Limitations: Seller experience is PayPal-branded, not white-label. Limited PSP flexibility. Enterprise sellers often have separate PSP relationships they won't abandon. Fee structure can be opaque at scale. Best for: Consumer-facing marketplaces where PayPal brand recognition drives buyer conversion. ### Shuttle What it is: A PSP-neutral payment layer that connects marketplaces to 40+ payment providers through a single integration. The marketplace integrates once; sellers connect through whichever PSP suits them. Strengths: Full PSP flexibility -- sellers bring their own provider, or the marketplace selects the best option per geography. White-label checkout, seller onboarding, and management portal. Multi-channel support: embedded checkout, payment links, voice payments, chat, and AI agent payments. PCI DSS Level 1, ISO 27001, and SOC 2 certified. Go live in weeks. Limitations: Commercial model rather than full PayFac margin capture. Less granular control over acquiring economics than building your own PayFac. Best for: Marketplaces that sell to enterprise buyers with PSP mandates, operate across multiple geographies, or need multi-channel payment capture beyond standard checkout. ### Comparison Summary Capability Stripe only Adyen only PayPal/Braintree White-Label Split Payments Multi-Channel Online + links Online, voice, links, chat, AI PCI Compliance Provider-managed Provider-managed (Level 1) Enterprise PSP Mandates Not supported Native support Time to Market ## How to Choose the Right Solution for Your Marketplace The right marketplace payment solution depends on where you are today and where you're heading. ### Start with Your Seller Base If your sellers are small businesses and sole traders who don't have existing PSP relationships, a single-PSP solution like Stripe Connect gets you live fastest. If your sellers include enterprise businesses with mandated payment providers, you need PSP flexibility from day one -- retrofitting it later is painful. ### Consider Your Geographic Footprint A UK-only marketplace can get by with a single acquirer. A marketplace operating across Europe, the US, and APAC needs local acquiring, local payment methods, and multi-currency payouts. Check whether your provider supports local acquiring in every market you need, or if they're routing everything cross-border (which costs more and converts worse). ### Map Your Channel Requirements Most marketplaces start with online checkout. But service marketplaces may need payment links for invoicing. Phone-based booking marketplaces need voice payments. Conversational commerce platforms need chat-embedded payments. If your roadmap includes any channel beyond web checkout, evaluate whether your payment solution supports it -- or whether you'll be re-integrating in 12 months. ### Calculate the Lock-In Cost Single-PSP solutions create dependency. Your sellers' card tokens, onboarding data, and payout configurations are all held by the PSP. Switching means re-onboarding every seller and re-tokenising every card. At 500+ sellers, this is a 6-12 month migration project. Ask yourself: if this PSP raises prices by 20% next year, can you move? If an enterprise seller demands a different provider, can you support them? If the PSP discontinues their marketplace product, what's your migration path? ### Evaluate Revenue Potential Marketplace payments should be a revenue line, not just a cost. Understand the revenue share model, the per-transaction economics, and how revenue scales with volume. The best payment solution is one where your revenue grows as your marketplace grows -- across all sellers, not just the ones on a specific PSP. ## FAQ What's the difference between marketplace payments and standard ecommerce payments? Standard ecommerce payments involve two parties: a buyer and a seller. The merchant collects payment directly. Marketplace payments involve at least three parties: buyer, seller, and platform. The platform must handle fund splitting, seller payouts, multi-party compliance, and commission collection -- none of which standard payment processing supports natively. Do I need a money transmission licence to run a marketplace? It depends on your structure. If you collect funds from buyers and hold them before paying sellers, you may need a money transmission or e-money licence in your jurisdiction. Most marketplace payment solutions are structured so a licensed provider holds and distributes funds on your behalf, keeping the marketplace out of regulatory scope. Confirm this with your payment provider and legal counsel. Can enterprise sellers use their own PSP on my marketplace? With single-PSP solutions (Stripe Connect, Adyen for Platforms), no -- all sellers must process through the same provider. With a PSP-neutral payment layer, yes -- enterprise sellers connect their mandated PSP while processing through your marketplace's unified experience. How long does it take to integrate marketplace payment infrastructure? Single-PSP solutions like Stripe Connect can be integrated in 2-4 weeks for basic functionality, longer for complex split logic and custom onboarding flows. PSP-neutral payment layers typically take a similar timeframe with pre-built components for checkout, onboarding, and seller management. Building your own PayFac infrastructure takes 12-18 months minimum. What about buy-now-pay-later (BNPL) for marketplaces? BNPL is a payment method, not a payment infrastructure choice. Most marketplace payment solutions support BNPL providers (Klarna, Afterpay, etc.) as a payment method within their checkout. With a PSP-neutral approach, you can offer BNPL through whichever provider covers your markets best -- without being limited to a single PSP's BNPL partnerships. ## Related Reading - When Your SaaS Outgrows Stripe Connect -- what happens when single-PSP lock-in limits your marketplace's enterprise reach - How Platforms Monetise Payments Without PSP Lock-In -- turning marketplace transactions into a revenue line - Embedded Payments Without Becoming a PayFac -- the full PayFac vs payment layer comparison - Shuttle vs Stripe Connect -- PSP-neutral vs single-PSP for platforms and marketplaces - Adyen for Platforms -- Alternatives -- evaluating Adyen's platform product against PSP-neutral options - Payment Providers Compared -- 40+ payment providers and how they work with marketplace infrastructure Shuttle connects marketplaces to 40+ payment providers through a single integration. White-label checkout, seller onboarding, split payments, multi-channel support, and PCI DSS Level 1 compliance included. Your marketplace ships payments in weeks -- without PSP lock-in. Book a Discovery Call | See How Platforms Use Shuttle ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Shuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers ### Maximizing Revenue and Customer Satisfaction with Payment Solutions for Marketplaces ### Travel Payment Solutions: How Agencies Collect Payments Faster ### Law Firm Payment Solutions: A Complete Guide for 2026 ### Payment Orchestration Alternatives for Platforms ## Links - [payment gateways](/blog/what-is-a-payment-gateway/) - [effectively becoming a PayFac](/guides/embedded-payments-without-payfac/) - [payment links](/guides/take-payments-online/payment-links/) - [PCI compliance included](/guides/pci-compliance-cost-platforms/) - [mandate their own PSP](/guides/enterprise-psp-mandates/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Pricing becomes a constraint at scale](/guides/when-saas-outgrows-stripe-connect/) - [Not PSP-neutral](/alternatives/adyen-for-platforms/) - [retrofitting it later is painful](/guides/psp-neutral-vs-single-psp/) - [enterprise sellers connect their mandated PSP](/guides/enterprise-psp-mandates/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [Adyen for Platforms -- Alternatives](/alternatives/adyen-for-platforms/) - [Payment Providers Compared](/payment-providers/) - [Book a Discovery Call](/discovery/) - [See How Platforms Use Shuttle](/platforms/) - [Book a Call](/discovery/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [BlogShuttle and Eventsforce work together to Deliver Seamless Payment Solutions for Event Organisers→](/blog/shuttle-and-eventsforce-work-together-to-deliver-seamless-payment-solutions-for-event-organisers/) - [BlogMaximizing Revenue and Customer Satisfaction with Payment Solutions for Marketplaces→](/blog/marketplace-payments/) - [BlogTravel Payment Solutions: How Agencies Collect Payments Faster→](/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/) - [BlogLaw Firm Payment Solutions: A Complete Guide for 2026→](/blog/modernising-legal-payments-how-law-firms-use-shuttle-payment-links-to-improve-collections/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) --- URL: https://www.shuttleglobal.com/guides/medical-billing-payments/ --- # Payment Solutions for Medical Billing Companies and RCM Firms | Shuttle > Quick answer: a medical billing company or RCM firm collects patient payments that belong to its client practices. # Payment Solutions for Medical Billing Companies and RCM Firms By Shuttle Team, July 13, 2026 Quick answer: a medical billing company or RCM firm collects patient payments that belong to its client practices. That means two hard requirements: every payment must settle to the right practice's own merchant account, and your agents must be able to take payments by phone without handling card numbers. The way to meet both is one payment system that holds a separate merchant account connection per practice, sends each payment to the merchant account you configured, and captures card details on the phone keypad instead of in your agents' headsets. Shuttle does this across agent calls, IVR, payment links and bank payments. A billing company serving 40 practices is running 40 businesses' receivables. The statements go out under each practice's name. The patient thinks they're paying their doctor or dentist, because they are. The practice expects its money in its bank account, reconciled against its ledger. Most payment tools assume you're collecting your own money. The moment you collect for client practices, you inherit two problems those tools can't solve: where the money settles, and what happens to your PCI position when your agents spend all day taking cards over the phone. This guide covers both, plus the collection workflows (statements, plans, IVR self-pay) that billing operations actually run. ## The money has to land in each practice's account A merchant account is tied to one legal entity. Payments processed on it settle to that entity, and the card statement shows that entity's name. Run every practice's patient payments through your own single merchant account and the problems stack up fast: - Settlement goes to you, not the practice. Now you're disbursing client funds from your own account, with the trust-accounting burden and timing risk that brings. - The patient's card statement shows your name. Patients don't recognise the billing company they've never heard of. Unrecognised descriptors get disputed, and those chargebacks land on your account. - Your acquirer sees unregistered aggregation. Processing other entities' payments through your own merchant account breaches most merchant agreements. We cover this fully in our guide to taking payments on behalf of your clients. The clean model: each practice keeps (or gets) its own merchant account, and your system routes every payment to the right one. The practice keeps its own gateway relationship and settlement. You keep one operation, one workflow and one screen for your agents. Shuttle is built around exactly this: each practice connects its own merchant account or gateway credentials once, and routing happens per payment automatically, across 40+ supported payment gateways. One practice on Stripe and another on the acquirer their bank set up years ago both work; nobody has to switch. ## Taking patient payments by phone without touching card data Patient balances are collected on the phone. Statement queries turn into payments, outbound balance calls end in payments, and the patient on the line wants to settle now. The default way billing teams handle this is the risky way: the agent asks for the card number and keys it into a virtual terminal. Once your agents hear or see card numbers, your operation is inside PCI DSS scope: the phone system, the call recordings, the agents' screens, the desktop environment, the training and vetting behind them. For a billing company, that's dozens of practices' patients' card data concentrated in one contact centre. Two patterns keep card data out of your environment while keeping the phone channel: - Agent-assisted secure capture. The agent stays on the call. The patient types their card number on the phone keypad; the digits go to the payment gateway, and the agent sees only masked progress on screen. The conversation continues, and the card number never enters your phone system or recordings. This is how DTMF payment capture works. - IVR self-payment. The patient calls the number on their statement, keys in a reference and pays through an automated flow with no agent at all. This absorbs the routine statement payments so your agents handle the exceptions and the conversations that need a human. Real calls fail in predictable ways, so the fallbacks matter as much as the happy path. Patient's card is in another room: send a payment link by SMS or email and they finish on their own phone. Call drops mid-payment: same recovery. Patient prefers not to use a card: take a bank payment on the same call. Every one of these is a payment that would otherwise become another statement cycle. A note on recordings: billing operations already manage call recordings carefully because calls contain patient information. Keypad capture takes the card numbers out of those recordings entirely, so your payment flow stops adding card data to an already sensitive asset. PCI DSS governs the card data; your obligations for patient health information are a separate matter and stay with your existing compliance programme. ## Statements, plans and the rest of the collection workflow Phone is the pressure point, but billing operations collect across a wider surface, and per-practice routing has to hold everywhere: - Pay-now on statements. A payment link on the e-statement or patient portal message, and an IVR number on the printed statement, both settling to the issuing practice's account. - Payment plans. Patient balances are frequently paid in instalments. Agreeing a plan on the phone and automating the collections beats chasing a new payment every month. - Reconciliation per practice. Every payment carries its practice and patient references, so posting back to your billing platform or the practice's ledger is a data exercise, not a matching exercise. Shuttle exposes this through payment APIs and webhooks rather than assuming any particular practice management system. The same applies to dental billing companies, veterinary billing services and specialty RCM firms: the operational shape (many client practices, each with its own merchant account, phone-heavy patient contact) is identical even where the terminology differs. ## Why billing companies can go live quickly An RCM firm doesn't wait for anyone to adopt anything. The patient call volume is already in your contact centre, the practices' merchant accounts already exist, and every payment your agents take today is a payment you could route properly tomorrow. The practical path: talk to us about your practice mix and call volume. If your team wants to explore the technical side first, docs.shuttleglobal.com covers the flows, and sandbox accounts are available for testing before any practice account is connected. Adding each practice after the first is configuration, not a new project. ## Medical billing payments FAQ ### How do medical billing companies take patient payments by phone without PCI problems? Use keypad capture instead of verbal card numbers. Either the agent stays on the line while the patient types their card number (the digits route to the payment gateway, not the agent), or the patient pays through an IVR flow with no agent involved. In both patterns card data stays out of your phone system, recordings and agent screens, which keeps those systems out of PCI DSS scope. ### Can we collect for multiple practices through one system? Yes, if the system supports per-client merchant account routing. Each practice connects its own merchant account or gateway credentials, and every payment goes to the one you configured. Your agents work one queue; each practice's money settles to that practice. ### Does the money come to us or to the practice? To the practice, directly. In the routing model you never hold patient funds: each payment settles from the practice's own merchant account to the practice's bank. That keeps you a billing service rather than a money handler, and keeps the patient's card statement showing the practice they recognise. ### What if our practices use different payment gateways? That's normal and it's fine. One practice on Stripe, another on Worldpay, a third on whatever their bank installed: each connects the account they have, provided it's among the 40+ gateways Shuttle supports. You don't have to standardise your clients onto one provider. Phone keypad capture works on many supported gateways; payment links cover the rest. ### Can we set up payment plans for patient balances? Yes. Agree the plan on the call, and the instalments collect automatically against the practice's merchant account, with the same per-practice routing and reconciliation references as one-off payments. ### How quickly can a billing company get started? Quickly, because nothing waits on downstream adoption. Sandbox accounts let your team trial the agent-assisted and IVR flows before connecting any real practice accounts, and going live is then per-practice configuration, driven by your own rollout pace rather than a vendor project plan. ## Related reading - Take Payments on Behalf of Your Clients - the multi-merchant-account problem across every servicer vertical - DTMF Payments - how keypad capture keeps agents out of PCI scope - ACH and Bank Payments Over the Phone - for patients who won't pay by card - Contact Centre Payments - the complete guide for phone-led payment operations - Payment Infrastructure for Healthcare - Shuttle's healthcare overview Ready to route every patient payment to the right practice? Talk to us. If your team wants to dig into the technical detail first, docs.shuttleglobal.com covers the flows, with sandbox accounts available for testing. ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [taking payments on behalf of your clients](/guides/take-payments-on-behalf-of-clients/) - [40+ supported payment gateways](/payment-providers/) - [DTMF payment capture](/guides/dtmf-payments/) - [take a bank payment on the same call](/guides/ach-payments-over-the-phone/) - [payment APIs and webhooks](https://docs.shuttleglobal.com) - [talk to us](/contact/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [40+ gateways Shuttle supports](/payment-providers/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [DTMF Payments](/guides/dtmf-payments/) - [ACH and Bank Payments Over the Phone](/guides/ach-payments-over-the-phone/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Payment Infrastructure for Healthcare](/industries/healthcare/) - [Talk to us](/contact/) - [See Links Checkout](/merchants/links-checkout/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/merchant-account-providers/ --- # Merchant Account Providers Compared: 12 Best Options for 2026 | Shuttle > A merchant account is the bank account that lets your business accept card payments. # Merchant Account Providers Compared: 12 Best Options for 2026 By Shuttle Team, April 21, 2026 A merchant account is the bank account that lets your business accept card payments. The "provider" is whoever opens and maintains that account on your behalf -- and the choice has more impact on your economics than most businesses realise. The category has fragmented in the last decade. What used to be a straightforward bank relationship now spans five distinct provider types, each with different pricing, contract terms, settlement speeds, and integration models. Picking the wrong one can cost you 30+ basis points on every transaction, weeks of approval delays, or months of technical rework when you need to change. This guide covers what a merchant account provider actually does, the five types you'll encounter, how to compare them, the leading providers in each category -- and the scenario nobody else writes down: when you don't need a merchant account at all. ## What Is a Merchant Account Provider? A merchant account provider is the institution that holds your merchant account and processes card transactions on your behalf. They sit between your business and the card networks (Visa, Mastercard, American Express), handling authorisation, settlement, chargebacks, and the compliance requirements that come with accepting card payments. Functionally, every merchant account provider does four things: - Underwrites your business -- assesses risk, approves or rejects your application, and sets your processing limits - Processes transactions -- authorises card payments in real-time and routes them through the card networks - Settles funds -- deposits payment proceeds into your bank account on a defined schedule - Manages disputes -- handles chargebacks, fraud alerts, and compliance with card scheme rules What varies between providers is *how* they do this -- and who they do it for. A traditional bank takes weeks to underwrite a complex business. A PayFac like Stripe approves a new merchant in minutes. A payment orchestrator doesn't hold a merchant account at all -- it routes your transactions across multiple providers. Same problem, radically different solutions. ## The Five Types of Merchant Account Providers The term "merchant account provider" gets used loosely. In practice, there are five distinct provider types -- and the right one for your business depends on your size, your industry, your risk profile, and your technical setup. ### 1. Acquiring Banks Acquiring banks are the original merchant account providers. They hold your account directly, underwrite you as a customer, and have direct membership of the card networks. Examples include Chase Merchant Services, Wells Fargo Merchant Services, Barclaycard, and Lloyds Cardnet. Best for: Established businesses with predictable volumes, sophisticated compliance needs, or existing banking relationships. Trade-offs: Slow underwriting (often weeks), rigid contracts, less modern technology, and pricing that rewards scale but penalises smaller merchants. ### 2. Independent Sales Organisations (ISOs) ISOs are resellers. They don't hold acquiring licences themselves -- they sell merchant accounts on behalf of an acquiring bank and take a margin. Many of the brands you'll see advertising "merchant services" are ISOs: Elavon, TSYS, WorldPay ISO partners, and hundreds of smaller regional players. Best for: Small-to-medium merchants who want a relationship-driven sales process and a single point of contact for account support. Trade-offs: Layered pricing (you pay the bank margin plus the ISO margin), variable contract terms, and sometimes opaque fee structures. Watch for long lock-in contracts and early termination fees. ### 3. Payment Service Providers (PSPs) / Aggregators Aggregator PSPs -- Stripe, Square, PayPal, Adyen for Platforms, Checkout.com -- don't give you your own merchant account. You operate under their master merchant account and they handle the underwriting, compliance, and settlement for you. Best for: Startups, SaaS businesses, and merchants who want to start accepting payments the same day they sign up. Also the default for ecommerce platforms. Trade-offs: Higher per-transaction fees (typically 1.5-3.0%+), risk of account freezes if your business profile changes, and limited negotiation leverage until you hit serious volume. ### 4. Payment Facilitators (PayFacs) PayFacs are a specific regulatory model -- a registered entity that sponsors sub-merchants under its master merchant account. Stripe and Square are PayFacs. So are many SaaS platforms that embed payments (Shopify, Toast, Mindbody). If you're a platform considering becoming a PayFac, the trade-offs are significant: you take on liability, compliance, and capital requirements in exchange for owning the payment economics. Best for: Platforms with enough volume and risk tolerance to run payments as a product in their own right. Trade-offs: 18-24 months to build, substantial compliance overhead, and a locked-in single-PSP dependency. ### 5. Payment Orchestrators (The Payment Layer) Payment orchestrators sit above merchant account providers. Rather than replacing your merchant account, they route transactions to whichever provider gives you the best outcome -- based on geography, card type, price, or success rate. Shuttle operates here, as do platforms like Primer and Spreedly. Best for: Platforms and merchants with multi-region operations, multiple PSPs, or complex routing needs. Also the right answer for most platforms that want embedded payments without the PayFac lift. Trade-offs: You still need at least one underlying merchant account or PSP relationship. Orchestration is layered on top -- it doesn't eliminate the merchant account question, it reframes it. ## How to Compare Merchant Account Providers The mistake most businesses make is shopping on headline rates. A "1.4% + 20p" quote means nothing without the rest of the fee stack. Here's what actually matters: ### Pricing Models There are three common pricing models: - Blended / flat-rate -- one rate for every transaction (e.g. Stripe's 1.5% + 20p). Simple, but you overpay on low-cost transactions (e.g. debit cards) and underpay on high-cost ones (e.g. corporate credit). - Interchange+ (IC+) -- you pay the true interchange fee (set by Visa/Mastercard) plus a fixed markup. Fairer for merchants with stable profiles. Harder to compare on headline rates but usually better in total cost. - Interchange++ (IC++) -- interchange + scheme fees + acquirer markup, all unbundled. Most transparent. Standard for enterprise merchants. If a provider only offers blended pricing and you process £100K+ per month, you are almost certainly overpaying. See our guide to credit card processing fees for a full breakdown. ### Settlement Speed Standard settlement is T+2 or T+3 (funds arrive 2-3 business days after the transaction). Faster settlement costs more -- some PSPs charge 1% for instant or next-day settlement. If cash flow matters, model the real cost: a 1% fee for 2 days of acceleration is a 183% APR on working capital. ### Global Reach If you take payments in multiple countries, local acquiring matters. Routing a Brazilian transaction through a UK acquirer drops authorisation rates by 10-20% compared to a Brazilian acquirer. Providers like Adyen vs Worldpay hold direct acquiring licences in 30+ and 40+ countries respectively. Most ISOs don't -- they're single-country operators. ### Contract Terms ISO contracts frequently include 3-year lock-ins and early termination fees. Modern PSPs and orchestrators run on month-to-month terms. Read the fine print on any contract longer than 12 months. ### Integration and API Quality How your merchant account provider integrates with your checkout, your ERP, and your fraud tools determines your engineering cost over the next five years. Providers with legacy APIs (Worldpay's original API, some bank acquirer APIs) are painful to work with. Modern PSPs and orchestrators offer well-documented REST APIs, SDKs, and prebuilt checkout components. ### Chargebacks and Reserves Ask explicitly about chargeback handling, representment support, and reserve requirements. Some providers hold 5-15% of your processing in reserve for 6+ months -- a material working capital impact for smaller merchants. ## Top Merchant Account Providers in 2026 A shortlist, broken down by category and provider type. This isn't a ranking -- the right choice depends entirely on your business profile. PSP / PayFac Startups, SaaS, platforms 40+ countries Acquirer + PSP Enterprise, platforms, marketplaces 30+ direct Enterprise, travel, retail 146 countries Checkout.com Digital-first merchants 50+ countries Braintree (PayPal) SaaS platforms, subscription Blended/IC+ 45+ countries SMB, retail, services US, UK, CA, AU, JP Chase Merchant Services US enterprise IC+ / IC++ US-focused Barclaycard UK enterprise UK-focused Acquirer / ISO UK/US multi-segment IC+ / blended US, UK, EU GoCardless Direct debit / bank Subscription, recurring 30+ countries Orchestrator Platforms routing across PSPs Flat platform fee Works with 40+ PSPs For deeper provider comparisons, see our guides on Adyen vs Worldpay, Adyen vs Checkout.com, and Authorize.Net vs Stripe. ## Merchant Account Providers Reviewed The comparison table above summarises the main options. Here is a closer look at where each widely used provider fits, and who it suits best. ### Stripe Stripe is a PSP and payment facilitator with best-in-class APIs, fast onboarding, and broad international coverage. Blended pricing (typically 1.5 percent + 20p for UK cards) makes it ideal for startups, SaaS, and developers. The trade-offs are aggregator risk (accounts can be frozen for sudden volume or risk changes) and a premium on high volume versus interchange-plus. Best for technical teams and platforms that value integration speed. ### Square Square bundles hardware, software, and payments behind one flat rate with no monthly fee, which makes it the simplest option for small and in-person merchants. Onboarding is instant and there is no contract. It is less suited to high-volume or high-risk businesses, where the blended rate becomes expensive and underwriting is conservative. Best for small retail, hospitality, and service businesses that want one easy package. ### PayPal PayPal offers near-universal consumer recognition and instant onboarding, which can lift checkout conversion. Pricing is blended and on the higher side, and account holds are a known frustration for growing merchants. Best as an additional checkout option rather than a sole merchant account, particularly for consumer-facing ecommerce. ### Adyen Adyen is a direct acquirer and processor built for enterprise and platforms, with interchange-plus pricing, local acquiring in many markets, and strong approval rates. It rewards scale: pricing and support are excellent at high volume but it is less suited to very small merchants. Best for enterprise, marketplaces, and global platforms. ### Worldpay Worldpay is one of the largest acquirers globally, with deep card-present and card-not-present coverage and direct acquiring across many regions. Contracts and pricing can be complex and are worth negotiating. Best for established mid-market and enterprise merchants that need broad acquiring reach. Checkout.com is an API-first direct acquirer aimed at scaling digital businesses, with granular data, local acquiring, and interchange-plus pricing. Like Adyen, it suits higher volumes rather than micro-merchants. Best for digital-first companies expanding internationally. ### Helcim and Stax Helcim and Stax use interchange-plus and subscription/membership pricing respectively, passing near-cost interchange to the merchant in exchange for transparent margins or a monthly fee. Both reward steady, mid-to-high volume where the savings outweigh any fixed cost. Best for established businesses focused on lowering the effective rate. ### Shuttle Shuttle is a payment layer rather than a single acquirer. Instead of tying you to one merchant account, it connects to 30+ payment gateways and routes each transaction to the right one by region, currency, card type, or failover. That removes single-processor risk, supports per-tenant routing for platforms, and makes switching or adding an acquirer a configuration change rather than a re-integration. Best for platforms, multi-region merchants, and any business that has outgrown a single provider. ## Best Merchant Account Provider by Business Type There is no single best merchant account provider. The right choice depends on how you sell, your monthly volume, your risk profile, and where your customers are. Here is how the leading options break down by business type. ### Best for ecommerce Online retailers need a strong payment gateway, built-in fraud screening, and support for the cards and wallets their customers actually use. Stripe, Adyen, and Checkout.com lead here because they pair acquiring with developer-friendly APIs, tokenised checkout, and tools like 3-D Secure and network tokenisation. For stores selling across borders, multi-currency pricing and local payment methods matter more than the headline rate. The risk with a single ecommerce processor is lock-in, which is why higher-volume merchants often place a payment orchestration layer in front of two or more acquirers. ### Best for small business and low volume If you process less than roughly £10,000 a month, a flat-rate aggregator is almost always the right starting point. Square, PayPal, and Stripe charge a single blended rate (around 1.5 to 2.9 percent), have no monthly fee, and approve you in minutes rather than days. You trade a slightly higher per-transaction cost for zero setup friction and no contract. As volume grows the blended premium adds up, and interchange-plus pricing from a dedicated provider becomes cheaper. If most of your sales happen over invoices or links rather than a storefront, compare the best payment link providers instead. ### Best for high-risk businesses Industries such as gaming, adult, CBD, travel, subscriptions, and debt collection are classed as high risk and are routinely declined or frozen by aggregators like Stripe and PayPal. These businesses need a specialist high-risk acquirer or an ISO that underwrites the vertical directly, usually with a rolling reserve and higher rates in exchange for stability. The priority is a provider that knows your industry and will not suspend the account at the first chargeback spike. A true merchant account, not an aggregator sub-account, is essential here. ### Best for SaaS and platforms Software platforms that want to embed payments for their own customers face a build-versus-buy decision. Becoming a payment facilitator (PayFac) gives the most control but carries heavy compliance and underwriting obligations. A payment orchestration layer is the lighter route: you embed payments, route each merchant to the right acquirer, and avoid taking on PayFac liability. Per-tenant gateway configuration matters most here, so each of your customers can keep their own processor. Compare the connected options on the payment providers page. ### Best for international and multi-currency Selling into multiple regions means caring about local acquiring, settlement currency, and local payment methods, not just card rates. Adyen, Worldpay, and Checkout.com offer direct acquiring in many markets, which lifts approval rates and lowers cross-border fees versus routing everything through one country. The most resilient setup connects more than one acquirer, so you can move volume if one processor starts declining. Shuttle connects to 30+ payment gateways for exactly this reason. ### Best for enterprise Large merchants negotiate interchange-plus (IC++) pricing directly with acquirers and expect dedicated support, custom settlement terms, and high approval rates. At this scale, single-processor risk becomes a board-level concern: an outage or a sudden policy change can stop revenue. Enterprises increasingly run two or more acquirers behind a payment orchestration layer for redundancy, cost arbitrage, and negotiating leverage, rather than depending on one provider. ## Merchant Account Pricing Models Explained How a provider prices processing matters as much as the headline rate. Four models dominate the market, and the cheapest one depends entirely on your volume and average transaction size. ### Interchange-plus (IC++) You pay the card scheme's interchange fee plus a fixed, transparent markup (for example, interchange + 0.3 percent + 10p). It is the most transparent model and almost always the cheapest at scale, because you can see exactly what the provider keeps. It is favoured by mid-market and enterprise merchants on dedicated accounts. ### Flat-rate (blended) A single rate applies to every transaction (for example, 1.75 percent) regardless of the underlying card type. It is simple and predictable, with no monthly fee, which is why aggregators like Square, Stripe, and PayPal use it. You overpay slightly on cheap debit cards and underpay on premium cards, so it suits lower volumes where simplicity wins. ### Tiered pricing Transactions are sorted into qualified, mid-qualified, and non-qualified tiers, each with a different rate. It looks competitive on the headline qualified rate but is the least transparent model, because the provider decides which transactions land in the expensive tiers. It is generally worth avoiding unless the effective rate is genuinely lower. ### Subscription / membership You pay a fixed monthly membership fee and then near-cost interchange with a small per-transaction charge. Providers like Helcim and Stax use this model. It can be the cheapest option for high-volume merchants whose membership fee is outweighed by the interchange savings, but the monthly fee makes it poor value at low volume. ### Which pricing model is cheapest? As a rough rule, flat-rate wins below roughly £10,000 a month because there is no fixed cost to absorb. Above that, interchange-plus or subscription pricing usually wins, because the per-transaction saving outgrows any monthly fee. Always compare the effective rate (total fees divided by total volume), not the advertised headline rate. ## How to Switch Merchant Account Providers Switching is more common than most merchants expect, usually triggered by rising fees, a frozen account, poor approval rates, or expansion into a new market. The migration itself is manageable if you plan for three things. First, card data: if your old provider stores tokenised cards, arrange a secure token migration so you do not force every customer to re-enter their details. Second, settlement overlap: run both providers in parallel for a short window so in-flight transactions and refunds settle cleanly before you switch off the old account. Third, downtime: update your gateway or orchestration configuration during a low-traffic period. Merchants on a payment orchestration layer avoid most of this, because adding or swapping an acquirer is a configuration change rather than a full re-integration. ## When You Don't Need a Merchant Account Provider Most guides stop at the comparison table. The more interesting question is whether you need a traditional merchant account provider at all. If you're a platform or SaaS company, the answer is often no -- at least not in the traditional sense. Embedded payments via a PayFac-in-a-box (Stripe Connect, Adyen for Platforms) or a payment layer gives you the economics and control of owning payments without the 18-month build or the single-PSP dependency. See our guide on embedded payments without becoming a PayFac for the full breakdown. If you're a merchant processing in multiple countries, a single merchant account provider is often the wrong frame. Multi-PSP routing via an orchestrator typically gives better authorisation rates, better currency handling, and better negotiating leverage than any single provider. If you're a merchant with simple, single-country needs, a modern PSP (Stripe, Square, Adyen) is usually the fastest path to revenue. You'll overpay on headline rates versus a bank acquirer, but you'll be live in a day instead of a month. ## When You Do Need a Traditional Merchant Account You need a direct acquirer relationship when: - You process high volume (£10M+ annually) and can negotiate IC++ pricing that beats PSP blended rates - Your industry is high-risk (adult, gambling, high-ticket B2B, CBD, certain subscription models) and aggregator PSPs won't underwrite you - You need functionality that PSPs don't support (surcharging, interchange optimisation, specific settlement currencies, direct card-scheme relationships) - You operate in industries with sector-specific processing requirements (insurance, lending, real estate) For UK merchants in particular, see our guide to merchant payment collection for the full set of options beyond card processing -- including open banking, pay-by-link, and voice payments. ## Merchant Account Providers FAQ ### What's the difference between a merchant account and a payment gateway? A merchant account is the bank account that holds your card processing proceeds. A payment gateway is the software that passes card data from your checkout to your merchant account provider. You need both -- but they can come from the same vendor (e.g. Stripe) or from different vendors (e.g. a bank acquirer plus a separate gateway like Authorize.Net). ### Do I need a merchant account for my online business? Not necessarily. PSPs like Stripe, Square, and PayPal let you accept card payments without holding your own merchant account -- you operate under their master account. This is the default for most startups and small online businesses. You only need a dedicated merchant account once your volume or risk profile makes aggregator pricing uncompetitive or unsustainable. ### How much does a merchant account cost? Typical costs: 1.5-3.0% per transaction for PSPs / aggregators, 0.5-2.0% + monthly fees for direct acquirer relationships with IC++ pricing. There may also be gateway fees, PCI fees, chargeback fees, monthly minimums, and early termination fees. Always ask for the full fee stack, not just the headline rate. ### How long does merchant account approval take? PSPs like Stripe approve in minutes to hours. ISOs typically take 3-7 business days. Direct acquiring banks take 2-6 weeks depending on industry and risk profile. High-risk industries (CBD, gambling, adult) can take 6-12 weeks and require multiple underwriting rounds. ### Can I have multiple merchant accounts? Yes, and many larger merchants do. Multi-merchant-account setups are standard for multi-region operations, high-risk mitigation, and redundancy. If you're running multiple merchant accounts, a payment orchestrator will save you significant engineering time and improve your routing economics. ### What's the best merchant account for a small business? For most UK small businesses, Stripe or Square is the fastest path to accepting payments. If you process £50K+ per month and want to negotiate, Barclaycard, Elavon, or Worldpay offer better unit economics. If you're UK-specific and cash flow matters, consider open banking via GoCardless or Truelayer. ### What's the difference between a merchant account provider and a payment processor? A merchant account provider supplies the underwritten account that lets you accept card payments and receive settled funds, while a payment processor moves the transaction between the card networks, the issuing bank, and that account. Many modern providers do both, which is why the terms are often used interchangeably. Aggregators like Stripe and Square bundle the account, the processing, and the gateway into one signup, whereas a traditional setup separates the acquiring bank, the processor, and the gateway. ### Do high-risk businesses need a special merchant account provider? Yes. High-risk industries (gaming, adult, CBD, travel, subscriptions, debt collection) are routinely declined or frozen by mainstream aggregators, so they need a specialist high-risk acquirer or an ISO that underwrites the vertical directly. Expect higher rates and often a rolling reserve in exchange for an account that will not be suspended at the first chargeback spike. A true underwritten merchant account, rather than an aggregator sub-account, is the safer foundation for a high-risk business. ## Choosing Your Merchant Account Provider The right merchant account provider depends on three things: your business profile, your volume, and your technical sophistication. A startup doing £10K/month should not be in conversation with a bank acquirer. A £50M/year platform should not be on Stripe's blended rate. If you're a platform considering how to take payments for your customers, start with our guide to embedded payments without becoming a PayFac or explore Shuttle's payment layer -- most platforms save 18+ months of build time by orchestrating across existing providers rather than becoming a merchant account provider themselves. If you're a merchant looking to collect payments more effectively, explore Shuttle's merchant tools -- including payment links, voice checkout, and open banking -- which work alongside your existing merchant account provider rather than replacing it. To compare the leading payment link options side by side, see Best Payment Link Providers. And if you collect payments on behalf of clients, as billing services, agencies and property managers do, see our guide to taking payments on behalf of your clients. If your account came with a virtual terminal your team keys card numbers into, see virtual terminal payments for what that costs you in PCI scope and whether you can replace it without leaving your provider. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### What is a merchant account? ### PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope ### Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared ### Braintree vs Checkout.com - which is the right choice for an enterprise merchant? ### Best UK Payment Providers - The definitive guide ### Account Updater Service: How It Works for Card Payments ## Links - [payment orchestrator](/guides/what-is-payment-orchestration/) - [Checkout.com](/alternatives/checkout-com/) - [becoming a PayFac](/guides/embedded-payments-without-payfac/) - [credit card processing fees](/guides/credit-card-processing-fees/) - [Adyen vs Worldpay](/guides/adyen-vs-worldpay/) - [Adyen vs Checkout.com](/guides/adyen-vs-checkout-com/) - [Authorize.Net vs Stripe](/guides/authorize-net-vs-stripe/) - [30+ payment gateways](/payment-providers/) - [payment orchestration](/guides/payment-layer-explained/) - [best payment link providers](/guides/best-payment-link-providers/) - [payment providers](/payment-providers/) - [payment layer](/guides/payment-layer-explained/) - [embedded payments without becoming a PayFac](/guides/embedded-payments-without-payfac/) - [merchant payment collection](/guides/take-payments-online/) - [payment gateway](/blog/what-is-a-payment-gateway/) - [Shuttle's payment layer](/platforms/) - [Shuttle's merchant tools](/merchants/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [taking payments on behalf of your clients](/guides/take-payments-on-behalf-of-clients/) - [virtual terminal payments](/guides/virtual-terminal-payments/) - [Book a Call](/discovery/) - [BlogWhat is a merchant account?→](/blog/what-is-a-merchant-account/) - [BlogPCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope→](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [BlogFastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared→](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [BlogBraintree vs Checkout.com - which is the right choice for an enterprise merchant?→](/blog/braintree-vs-checkout-com-which-is-the-right-choice-for-an-enterprise-merchant/) - [BlogBest UK Payment Providers - The definitive guide→](/blog/best-uk-payment-providers-the-definitive-guide/) - [BlogAccount Updater Service: How It Works for Card Payments→](/blog/should-i-use-account-updater-services-for-card-payments/) --- URL: https://www.shuttleglobal.com/guides/mitel-payments/ --- # How to Take Payments in Mitel: Multi-PSP PCI-Compliant Capture | Shuttle > Mitel is one of the most widely deployed enterprise telephony and unified communications platforms in the world. # How to Take Payments in Mitel: Multi-PSP PCI-Compliant Capture By Shuttle Team, June 2, 2026 Mitel is one of the most widely deployed enterprise telephony and unified communications platforms in the world. Its portfolio spans MiVoice Business for mid-market and enterprise PBX, MiContact Center Business and MiContact Center Enterprise for contact centre operations, and Mitel CX for cloud-first deployments. The installed base runs deep in hospitality, public sector, and healthcare, where multi-site telephony and structured contact centre workflows are common requirements. Like most UC and contact centre platforms, Mitel does not ship a native payment product. For organisations that need to collect card payments over voice, Mitel's own platform offers exclude-recording or manual pause as workarounds, but neither constitutes true DTMF suppression or a PCI DSS-compliant capture environment. Mitel addresses this through its Apps and Integrations Gallery, where several specialist PCI payment partners are listed, covering DTMF suppression, agent-assisted capture and secure IVR. Each is a capable, established solution within its own approach. This guide covers how payments work on Mitel today, what each gallery partner delivers, and when a gateway-neutral multi-PSP layer like Shuttle is the better fit for organisations that need more than a single-capture vendor can offer. It is written for two audiences: enterprises running Mitel who want PSP flexibility and cleaner PCI scope without lock-in to one capture provider, and solution providers or SIs deploying Mitel who need a payment layer they can configure differently for each client. ## How Payments Work on Mitel Today Mitel gives organisations a clear path to PCI-compliant voice payments through its gallery partner ecosystem: - Mitel's own platform offers no native DTMF suppression. The available platform-level options are exclude-recording (omitting the call segment from recordings) or manual pause, neither of which removes card data from the live call path in the way a certified capture solution does. - The gallery's primary PCI payment integration suppresses DTMF tones during live agent-assisted calls and holds PCI DSS Level 1 certification. - At least one other listed option is certified at PCI Level 1 and carries both Mitel Technology Network (MTN) and MSA certifications. - DTMF-silencing and secure IVR tools round out the gallery options. - Each partner is a point solution: it solves PCI voice capture within its own platform and PSP integrations. ## When You Need a Gateway-Neutral Payment Layer The gallery partners cover the core use case well. Where organisations run into constraints is when the payment requirement is more complex than a single-vendor solution is designed to handle: - Multi-PSP routing across many gateways with BYO acquirer: each gallery partner integrates with a defined set of payment processors. Organisations that have existing gateway contracts, or want to retain the ability to switch acquirers, benefit from a layer that routes across 30+ gateways without a renegotiation. - Per-client or per-tenant PSP routing: SIs managing Mitel deployments across multiple clients often need different gateways configured per client, whether due to commercial arrangements, currency requirements, or client-mandated processors. Point solutions are typically configured per deployment rather than per client within a deployment. - Enterprise PSP mandates: large organisations operating under a mandated processor (a corporate treasury or procurement requirement to settle through a specific acquirer) need the capture layer to route to that processor by default, with override logic for specific use cases. - Cross-channel payment capture beyond DTMF voice: Mitel deployments increasingly include email, live chat, and SMS alongside voice. Hosted payment links delivered across those channels need the same PCI infrastructure and reconciliation as voice capture. - Platform-agnostic integration: organisations or SIs who want a payment layer that stays consistent if they migrate from MiVoice to Mitel CX, or from Mitel to another platform entirely, avoid rework when the capture layer is not tied to one platform's gallery. ## How Shuttle Adds Payments to Mitel Shuttle adds PCI-compliant card capture to your Mitel payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Mitel recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Mitel specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Mitel call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Mitel have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## Multi-PSP Support Shuttle connects to over 40 payment gateways from a single integration, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square, alongside regional and specialist processors. Each gateway is configured per tenant or per client. Provider selection and currency preferences are set at the client level, not the platform level. This means an SI managing ten Mitel clients can have ten different gateway configurations within one Shuttle integration, with no per-client re-integration work. Switching gateways later is configuration, not a re-integration. For organisations under an enterprise PSP mandate, Shuttle routes to the mandated processor by default and supports override rules for specific transaction types, cost centres, or geographies. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 Service Provider, the highest certification tier. Card data enters and is processed within Shuttle's certified environment. It does not pass through Mitel's platform, infrastructure, or call recordings. This approach reduces the Mitel environment's PCI scope substantially. Organisations that previously required SAQ-D assessments covering their telephony infrastructure can move toward SAQ-A for the card capture component, with the assessment burden sitting with Shuttle rather than the contact centre operator. ## Beyond Voice: Payment Links Mitel deployments often include more than voice. MiContact Center Business and Mitel CX support email, live chat, and SMS alongside phone queues. Shuttle's hosted payment links work across all of these channels: an agent can send a secure payment link via the digital channel of the customer's choice, and the customer completes payment in a Shuttle-hosted environment. The same PCI Level 1 infrastructure applies regardless of channel, and all transactions reconcile in the same Shuttle reporting view regardless of whether they originated from a voice DTMF session or a digital payment link. ## For Solution Providers and Mitel Partners SIs and resellers deploying Mitel can reference two relevant programmes: the Mitel Technology Network (MTN) for ISV-level integrations, and the Mitel Global Partner Program for resellers and implementation partners. Several of the existing gallery partners have certifications within the MTN framework. Shuttle operates as the gateway-neutral payment layer an SI can position across a Mitel practice without tying each client to one capture vendor. Per-client PSP routing means the payment configuration reflects each client's commercial and compliance requirements. There are no setup fees and no per-seat charges: voice is priced at $0.20 per successful transaction, and Links Checkout is a separate app (a new pricing model is coming), making it straightforward to present to clients next to the Mitel licence. For practices managing Mitel alongside other platforms, Shuttle's integration is consistent across platforms, which reduces the training and support overhead of managing multiple capture vendors across a portfolio. ## Use Cases ### Multi-Brand and Multi-Client Operations Hospitality groups, managed service providers, and outsourced contact centres often run Mitel across several brands or client accounts from a shared infrastructure. Shuttle's per-tenant gateway configuration supports different payment providers per brand or client within a single integration, without separate deployments or renegotiated gateway contracts. ### Enterprise PSP Mandates Large organisations in financial services, public sector, and healthcare frequently operate under treasury or procurement mandates that require card settlement through a specific acquirer. Shuttle handles mandate routing natively, directing transactions to the mandated processor while allowing override rules for specific use cases. ### Hospitality and Bookings Mitel has a strong hospitality installed base, covering hotels, travel operators, and venue management. Voice-assisted booking payments, deposit collection, and modification fees are natural use cases for secure voice capture via Twilio Pay, with payment links covering email confirmation and follow-up payment collection across the same booking journey. ### Public Sector and Healthcare Collections Public sector and healthcare organisations using Mitel for inbound contact centre operations frequently collect payments over the phone: council tax, service fees, co-pay collections, and outstanding balance recovery. Shuttle's PCI Level 1 environment and gateway-neutral routing supports these use cases, including direct debit and alternative payment methods alongside card capture. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Mitel plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Mitel specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Mitel call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Mitel have already done it. - A native Mitel integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Mitel process payments natively? Mitel does not have a native payment product. Its platform offers exclude-recording and manual pause as workarounds for card handling, but PCI-compliant card capture is delivered through specialist gallery partners covering DTMF suppression, agent-assisted capture and secure IVR. Does Shuttle have a native Mitel integration? Not today. Shuttle is not a Mitel gallery partner and there is no Shuttle app inside Mitel. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Mitel have already done. We can build a native Mitel integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. Does this require Twilio? Yes, today, for voice card capture. The secure capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links for digital channels don't require a Twilio voice call. The carrier-agnostic version that removes the voice Twilio requirement is on our roadmap. How is Shuttle different from those PCI payment partners? The gallery partners are established, certified solutions that sit inside the Mitel call path with their own PSP integrations. Shuttle takes a different route: voice capture runs via Twilio Pay rather than inside Mitel, and the differentiator is gateway neutrality, one integration across 30+ gateways, BYO acquirer support, per-client PSP routing, and cross-channel payment links. Organisations or SIs that need more than a single-PSP capture vendor, and that have the technical resource to build the agent-side interface, will find Shuttle's model more flexible. Which gateways does Shuttle support? Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and a broad range of regional and specialist processors. A small number (for example Braintree) work for payment links but not for voice capture, because they won't accept raw card data. Can Shuttle route different clients to different PSPs? Yes. Shuttle supports per-tenant gateway configuration, so SIs or contact centre operators managing multiple clients can configure separate gateway rules per client within a single Shuttle integration. Does this keep our contact centre out of PCI scope? Shuttle is a PCI DSS Level 1 Service Provider. For voice, the card is captured in the secure Twilio Pay call and never passes through Mitel's platform or recordings. This significantly reduces the PCI scope of the Mitel deployment, keeping you on the lighter SAQ-A path and moving the assessment burden to Shuttle rather than the contact centre operator. ## Related Reading - Contact centre payments: how PCI-compliant payment capture works across modern contact centre platforms - Embedded payments for CCaaS: embedding a payment layer inside CCaaS and UC platforms without owning the infrastructure - Payment orchestration: how multi-PSP routing and gateway orchestration works in practice - Payment collection for BPOs: multi-client payment collection across outsourced contact centre operations - Payments for CCaaS implementation partners: how SIs and resellers add a gateway-neutral payment layer across their CCaaS practice ## Add Gateway-Neutral Payments to Mitel Shuttle adds multi-PSP PCI Level 1 capture alongside Mitel: secure voice payments via Twilio Pay and hosted payment links across 30+ gateways, at $0.20 per successful transaction for voice (Links Checkout is a separate app; see /pricing/) with no setup or per-seat fees. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF suppression](/guides/dtmf-payments/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ gateways](/payment-providers/) - [book a call](/contact/) - [40 payment gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [30+ payment gateways](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [Payment orchestration](/guides/what-is-payment-orchestration/) - [Payment collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/mollie-twilio-integration/ --- # How to Connect Mollie to Twilio for Voice & IVR Payments | Shuttle > Mollie doesn't natively connect to Twilio for voice payments. If you want to process Mollie transactions during a phone call (via IVR, agent-assisted, or... # How to Connect Mollie to Twilio for Voice & IVR Payments By Shuttle Team, June 11, 2026 Mollie doesn't natively connect to Twilio for voice payments. If you want to process Mollie transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Mollie (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Mollie + Twilio Don't Connect Directly Mollie is an Amsterdam-based payment service provider built for European commerce. It's especially strong in the Netherlands, Belgium, and Germany, where it gives merchants a single integration for cards plus local payment methods like iDEAL, Bancontact, and SEPA. Its API and dashboard are designed to be simple enough for SMEs while scaling to larger platforms. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Mollie isn't one of Twilio's built-in connectors, so there's no native path between the two platforms. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Mollie's API for processing. One integration connects the two platforms. One point worth noting up front: DTMF keypad capture is for card payments, while local methods like iDEAL and Bancontact work over the phone via a Shuttle payment link sent to the caller by SMS or email during the call, not keypad entry. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Mollie. The connector creates a Mollie payment request, processes the transaction through your Mollie account, and handles the response. - Result returned to your call flow. Your webhook receives the Mollie payment reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Mollie account with an API key (Mollie issues keys in pairs: a key for test mode and a key for production, found under Developers in your Mollie Dashboard) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Mollie Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Mollie - API key: Your Mollie API key (or key for testing) - Currency: Set your default (EUR for most Mollie merchants) Save the profile. Shuttle now has a live connection to your Mollie account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in your Mollie Dashboard if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Swap in your Mollie API key in your Shuttle payment profile and run the flow end-to-end in Mollie's test mode before going live. Once verified, switch the profile to your key. ## What You Can Do With Mollie + Twilio ### Charge Immediately Standard card payment. The caller pays on the keypad, Mollie processes in EUR (or another supported currency), done. This suits Dutch, Belgian, and German contact centres taking bookings, invoice payments, or deposits by phone. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token, so you can charge repeat payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Card by Keypad, Local Methods by Link DTMF capture handles card payments. For callers who prefer iDEAL or Bancontact, your agent can send a Shuttle payment link by SMS or email while still on the call, and the caller completes the payment through Mollie's local method rails on their own device. ### Serve Multiple Merchants BPOs and outsourced collection teams can run separate Shuttle payment profiles per client, each pointing at that client's own Mollie account, through a single Twilio integration. ## Multi-PSP: Beyond Mollie One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Dutch and Belgian merchants with Mollie and your UK or US merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Adyen, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, per merchant, with amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. ## PCI Compliance The Mollie + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1 Service Provider) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to Mollie. Your application only receives redacted data (last 4 digits, card brand, payment reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Mollie to Twilio without Shuttle? Twilio doesn't have a built-in Mollie Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Can callers pay with iDEAL or Bancontact over the phone? Not via the keypad. DTMF capture is for card payments. For iDEAL, Bancontact, and other local methods, send the caller a Shuttle payment link by SMS or email during the call and they complete it on their own device. What about Mollie's test mode? Fully supported. Use your Mollie API key in your Shuttle payment profile and verify the full flow with Twilio before switching to your key. What does it cost? Shuttle charges $0.20 per successful transaction. Mollie's standard transaction fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from Mollie to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Mollie: Mollie coverage, methods, and Shuttle support - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Mollie to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Mollie: Branded Checkout Links for Mollie Merchants ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment link](/merchants/links-checkout/) - [payment links](/merchants/links-checkout/) - [outsourced collection teams](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Mollie](/payment-providers/mollie/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Mollie: Branded Checkout Links for Mollie Merchants→](/blog/payment-links-for-mollie/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/moneris-twilio-integration/ --- # How to Connect Moneris to Twilio for Voice & IVR Payments | Shuttle > Moneris doesn't natively connect to Twilio for voice payments. If you want to process Moneris transactions during a phone call (via IVR, agent-assisted,... # How to Connect Moneris to Twilio for Voice & IVR Payments By Shuttle Team, June 26, 2026 Moneris doesn't natively connect to Twilio for voice payments. If you want to process Moneris transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Moneris (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. For Canadian businesses this matters. Moneris is Canada's largest payment processor, a joint venture of RBC and BMO, and the default acquirer for hundreds of thousands of Canadian merchants. If your business already settles through Moneris, this guide shows you how to take CAD payments over the phone without changing processors. ## Why Moneris + Twilio Don't Connect Directly Moneris is built for Canadian commerce: in-store terminals, ecommerce via the Moneris Gateway, and card-present processing with CAD settlement into Canadian bank accounts. Its APIs handle purchases, pre-authorisations, and tokenisation through the Moneris Vault. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Moneris isn't one of Twilio's built-in connectors, so there's no direct path from a Twilio call to your Moneris account. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Moneris for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Moneris. The connector creates a Moneris payment request, processes the transaction through your Moneris account, and handles the response. - Result returned to your call flow. Your webhook receives the Moneris reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Moneris account with gateway credentials (store ID + API token, found in the Merchant Resource Center under Admin > Store Settings) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Moneris Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Moneris - Store ID: Your Moneris store ID - API token: Your Moneris API token - Currency: CAD (USD is also supported if your Moneris account processes it) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Moneris account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code (CAD for Canadian merchants) - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in the Merchant Resource Center if needed. Update your account records, confirm to the caller, and continue the flow. ### Step 5: Test Use Moneris's test environment credentials in your Shuttle payment profile and verify the flow end-to-end before going live. Moneris's test environment simulates issuer responses, approving or declining transactions based on the amount you send, so you can rehearse both success and failure paths in your call flow. ## What You Can Do With Moneris + Twilio ### Charge Immediately Standard purchase. The caller pays, Moneris processes, funds settle to your Canadian bank account on your normal Moneris schedule. ### Authorise Now, Capture Later Place a pre-authorisation on the card during the call. Capture the payment later through Moneris, useful for bookings, deposits, or amounts that are finalised after the call. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via the Moneris Vault, which returns a permanent token (a data key) for that stored card. Use it for future payments across any channel: web, mobile, voice, or payment links. This is the pattern for recurring billing, instalment plans, and card-on-file collections. The card data is never stored in your systems. Note that the Vault option must be enabled on your Moneris account; your Moneris representative can switch it on. ### Serve Canadian Phone-Payment Use Cases Moneris + Twilio via Shuttle fits anywhere Canadian customers pay by phone: utilities taking bill payments through IVR, insurers collecting premiums on renewal calls, collections teams processing settlements and payment plans, and healthcare providers taking patient billing over the phone. The caller pays in CAD, your agents stay out of PCI scope, and settlement lands with your existing acquirer. ## Multi-PSP: Beyond Moneris One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Canadian merchants with Moneris and your US or international merchants with another acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand beyond Canada, where a local acquirer may give better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured for that merchant and payment type. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Moneris account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Moneris + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio → Shuttle → Moneris. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Moneris to Twilio without Shuttle? Twilio doesn't have a built-in Moneris Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Can I take CAD payments over the phone with this? Yes. That's the primary use case. Transactions process in CAD through your Moneris account and settle to your Canadian bank account as normal. What about Moneris's test environment? Fully supported. Use your Moneris test credentials in Shuttle and test the full flow with Twilio before going live. Moneris's test environment simulates issuer approvals and declines based on the transaction amount. What does it cost? Shuttle charges $0.20 per successful transaction. Moneris's standard processing fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from Moneris to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Payment Collection for BPOs: multi-client phone payments for outsourcers - Moneris: Moneris on Shuttle: supported features and channels - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Moneris to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Moneris](/payment-providers/moneris/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/multi-channel-payment-collection/ --- # Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes | Shuttle > One Link, Many Channels A payment link is just a URL. It opens a branded checkout page where your customer picks their payment method, enters their... # Multi-Channel Payment Collection: SMS, Email, WhatsApp & QR Codes By Shuttle Team, February 26, 2026 ## One Link, Many Channels A payment link is just a URL. It opens a branded checkout page where your customer picks their payment method, enters their details, and pays. The whole interaction takes under 60 seconds. The link itself doesn't change. What changes is how you deliver it. Send the same link by email, text it to a mobile number, share it on WhatsApp, print it as a QR code on an invoice, or read it out over the phone. The customer lands on the same checkout page regardless of how they got there. This is the real advantage. Different customers respond to different channels. A B2B client checking email at their desk behaves differently from a homeowner who just had their boiler fixed. A guest checking out of a hotel is not the same as a debtor receiving a collections notice. The businesses that collect fastest are the ones matching the payment channel to the customer, not forcing every customer through the same funnel. For a sector-specific application across letters, SMS, voice and AI agents, see Payment Collection for Parking, Enforcement and Toll Operators. ## Email: The Default Starting Point Email is where most businesses start with payment links, and for good reason. It's familiar, it's free to send, and it works well for anything invoice-related. The typical flow: you generate an invoice, include a "Pay Now" button or link in the email, and the client clicks through to a branded checkout page. No PDF downloads. No manual bank transfers. No reference numbers to copy. - B2B clients and professional services - Recurring billing and subscription renewals - Invoice follow-ups where you already have an email thread - Larger transactions where the customer expects documentation Strengths: No character limits, so you can include full context around the payment. Works across every device. Easy to automate from your invoicing or CRM system. Provides a natural paper trail. Weaknesses: Emails get buried. Your payment link is competing with 80 other unread messages in your client's inbox. Average email open rates sit around 20-25% for transactional messages. If your client's accounts payable person is on holiday, that email sits untouched until they get back. Email works. But it's slow. If speed matters, you need a second channel. ## SMS: Highest Open Rates, Fastest Response SMS open rates sit around 98%. Most text messages are read within 3 minutes of delivery. Compare that to email's 20-25% open rate and you can see why SMS payment links convert significantly faster. The format is simple: a short message with context and a link. "Hi Sarah, your invoice #1042 for £450 is ready. Pay here: [link]." The customer taps the link, lands on the checkout page, and pays. - Payment reminders and overdue invoices - Time-sensitive collections (field service, deliveries, appointments) - Younger demographics who live on their phones - Customers you don't have an email relationship with Strengths: Near-instant delivery. Near-universal open rates. Works on every mobile phone, including older handsets without WhatsApp. Short and direct, which suits payment prompts. Weaknesses: Character limits mean you can't include much context. SMS costs money per message (typically 3-5p per send in the UK). Some customers are wary of links in text messages due to smishing scams, so branding and trust signals on the checkout page matter. You also need the customer's mobile number, which isn't always available for B2B contacts. Tip: Use a URL shortener or branded short domain so the link looks trustworthy. A link from "pay.yourbrand.com" converts better than a generic shortened URL. ## WhatsApp: Rich Messaging With Global Reach WhatsApp has over 2 billion active users worldwide. In markets like India, Brazil, and large parts of Europe, it's the default messaging app. Even in the UK, WhatsApp is the most-used messaging platform after standard SMS. Sending a payment link via WhatsApp gives you more than just delivery. You get read receipts, rich formatting, the ability to include images or branding, and a conversational thread the customer can reply to with questions before they pay. - International customers (especially in markets where WhatsApp dominates) - Hospitality and personal services (salons, private healthcare, event management) - Ongoing client relationships where you already chat on WhatsApp - Situations where the customer might have questions before paying Strengths: Higher engagement than SMS in many markets. Rich message formatting. Two-way conversation. Read receipts so you know the message was seen. Free to send for most business use cases through WhatsApp Business API. Weaknesses: Requires the customer to have WhatsApp installed. You need their phone number and opt-in consent (WhatsApp Business API rules require this). Setting up the WhatsApp Business API takes more effort than sending an SMS. Not ideal for formal B2B communications where email is expected. WhatsApp works especially well as a follow-up channel. Send the invoice by email. If it's not paid in a week, send a WhatsApp message with the same link. The conversational format makes it feel like a friendly nudge rather than a formal demand. ## QR Codes: Bridging Physical and Digital A QR code is just a payment link encoded as an image. The customer scans it with their phone camera and lands on the checkout page. Same link, different delivery method. What makes QR codes powerful is that they work in physical contexts where you can't send a digital message. Print one on a paper invoice. Display one at a reception desk. Put one on a door hanger after a property viewing. Include one in product packaging. - Paper invoices and statements (accounting firms, utilities, property management) - Events, conferences, and ticketing - Retail and hospitality (countertop payments, table payments) - Field service (leave a QR code after a job for the customer to pay at their convenience) - Property viewings and letting agents Strengths: Works in physical spaces where digital channels can't reach. No need for the customer's contact details. The customer initiates the payment at their own pace. Easy to generate and cheap to print. Weaknesses: Requires the customer to have a smartphone with a camera. Older demographics may not be comfortable scanning QR codes (though adoption has increased significantly since COVID). You can't track delivery the way you can with SMS or email, so you don't know if the customer has seen the code. Tip: Always include the payment amount and a brief description next to the QR code. "Scan to pay £320 for your March service visit" gives the customer confidence before they scan. ## Voice: Phone-Based Payment Capture Not every customer is sitting at a screen. Some are on the phone with your team right now, ready to pay, and the fastest path is to take the payment during the call. Voice payments work through DTMF (where the customer types their card number on the phone keypad) or through AI voice agents that guide the customer through payment verbally. Either way, the call stays PCI-compliant because the payment data never touches your systems. - Contact centres and customer service teams - Debt collection and payment plans - Insurance renewals and claims - Older demographics who prefer phone over digital - High-value transactions where the customer wants to speak to someone Strengths: Captures payment at the moment of intent. No waiting for an email to be opened or a link to be clicked. Personal interaction builds trust, especially for larger amounts. Works for customers who don't use smartphones or aren't comfortable with digital payments. Weaknesses: Requires a phone interaction, so it's not scalable the same way automated channels are. PCI compliance for voice is more complex than for payment links. Costs more per transaction than self-service channels. The automated exception is the self-service payment line: see IVR Payments. Shuttle's Voice Checkout handles this through the Twilio Marketplace (see [pricing](/pricing/)). It works with existing phone systems, supports AI voice agents, and keeps card data out of your contact centre, which limits its PCI scope. ## Choosing the Right Channel for Your Customer The best channel depends on who your customer is, what they owe, and how urgently you need to collect. Customer Type Primary Channel Secondary Channel When to Use B2B clients on account Phone (voice) Invoice payments, recurring billing Consumer service customers Post-service payments, reminders International customers Cross-border collections Walk-in or in-person customers SMS (if you have their number) Retail, hospitality, events Overdue accounts Collections, payment plan setup Older demographics Insurance, utilities, property Field service customers SMS or QR code After job completion The key insight: you don't have to pick one channel. The businesses with the highest collection rates use multiple channels for the same payment, starting with the most convenient and escalating to the most direct. ## Multi-Channel Sequences: The Escalation Pattern The most effective approach to payment collection isn't picking the right channel. It's using the right sequence of channels. Here's a pattern that works across industries: Day 0: Send the invoice by email with a payment link. This is the standard starting point. Many customers will pay within 48 hours. Day 7: If unpaid, send an SMS reminder with the same payment link. "Your invoice #1042 for £450 is still outstanding. Pay here: [link]." Short, direct, and arrives on their phone screen. Day 14: If still unpaid, follow up on WhatsApp. The conversational format works well here because you can ask if there's an issue. "Hi, just checking you received the invoice for your March service. Here's the payment link if you need it: [link]. Let me know if you have any questions." Day 21: Try a different time of day or combine channels. Resend the email with an updated subject line. Send another SMS. Sometimes the issue is simply timing. Day 30+: Move to voice. A phone call with the option to pay during the call. This is where Voice Checkout becomes valuable. The customer is on the phone, the agent can address any concerns, and the payment can be captured right there. No "I'll pay it when I get to my computer" and another two weeks of waiting. This sequence works because each channel is progressively more personal and harder to ignore. Email is passive. SMS is direct. WhatsApp is conversational. Voice is personal. The same payment link works across all of these channels. You generate it once and deliver it however makes sense. Shuttle's Payment Layer handles the link generation, PSP routing, and checkout page. You focus on choosing the right channel and timing. ## FAQ Do I need separate providers for each channel? No. A payment link is a URL that works everywhere. You generate one link and send it via whatever channel suits your customer. Shuttle creates branded payment links that work across email, SMS, WhatsApp, QR codes, and web embeds through a single integration. Voice payments use a separate product (Voice Checkout), but it's the same platform underneath. What about GDPR and consent? You need a lawful basis for contacting someone on each channel. For email, legitimate interest or contractual necessity usually covers payment collection communications. For SMS and WhatsApp, you should have explicit consent to message the customer on that channel, and they must be able to opt out. WhatsApp Business API has its own opt-in requirements. For voice, standard telephone regulations apply. None of this is unique to payment links. The same rules apply to any business communication on these channels. Can I track which channel converts best? Yes. Use UTM parameters or unique link identifiers per channel. If you send the same payment via email and SMS, use a slightly different URL parameter for each so you can see which one the customer used. Over time, this data tells you which channels work best for which customer segments. Most businesses find SMS converts fastest, email converts the most total volume, and voice captures the highest average transaction value. How much does each channel cost? The payment link itself is the same price regardless of channel. With Shuttle, Links Checkout is $49 per month. On top of that, each delivery channel has its own cost: email is effectively free if you have an email provider, SMS costs 3-5p per message in the UK, WhatsApp Business API messages are priced per conversation (varies by country), QR codes cost nothing beyond printing, and Voice Checkout is $0.20 per transaction through the Twilio Marketplace. Can I automate multi-channel sequences? Yes. Most CRM and invoicing platforms support automated email reminders. SMS can be triggered through APIs when an invoice hits a certain age. The escalation pattern described above can be fully automated with the right integrations. Shuttle's API lets you generate payment links programmatically, so you can plug them into whatever automation workflow you already use. ## Related Reading - Best Payment Link Providers - Payment Collection for Professional Services - How B2B Service Companies Collect Payments Faster - PCI-Compliant Payments for Contact Centres - Voice Payments Guide - Payment Collection for Field Service Teams - Payment Reminder Email Templates (With Pay Now Links) - Dunning Letter Templates: From Friendly Reminder to Final Notice Ready to collect payments across every channel from a single platform? See how Shuttle works for merchants. ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending ### What Is Local Acquiring? How It Cuts International Payment Costs ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Payment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout ## Links - [Payment Collection for Parking, Enforcement and Toll Operators](/guides/parking-enforcement-toll-payments/) - [DTMF](/guides/dtmf-payments/) - [IVR Payments](/guides/ivr-payments/) - [Voice Checkout](/platforms/voice-checkout/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [Payment Collection for Professional Services](/guides/payment-collection-professional-services/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Voice Payments Guide](/guides/voice-payments/) - [Payment Collection for Field Service Teams](/guides/field-agent-payment-collection/) - [Payment Reminder Email Templates (With Pay Now Links)](/blog/payment-reminder-email-templates/) - [Dunning Letter Templates: From Friendly Reminder to Final Notice](/blog/dunning-letter-templates/) - [See how Shuttle works for merchants](/merchants/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogPayment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending→](/blog/payment-links-for-payu/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [BlogPayment Links for LiqPay: Send Branded Checkout Links With Multi-Currency Branded Checkout→](/blog/payment-links-for-liqpay/) --- URL: https://www.shuttleglobal.com/guides/multi-channel-payments/ --- # Multi-Channel Payment Capture: Voice, Links, Chat, and Embedded Checkout | Shuttle > Payments Aren't Just Checkout Anymore For most of the internet's history, "payments" meant one thing: a checkout page. # Multi-Channel Payment Capture: Voice, Links, Chat, and Embedded Checkout By Shuttle Team, December 15, 2025 ## Payments Aren't Just Checkout Anymore For most of the internet's history, "payments" meant one thing: a checkout page. A customer fills in a form, clicks pay, and the transaction processes. That model still works. But it's no longer the only model -- and for many businesses, it's not even the primary one. Today, payments happen: - During phone calls -- a customer pays while talking to an agent or AI - Via SMS -- a payment link arrives mid-conversation and the customer pays on their device - In chat -- a support agent or AI bot captures payment within a messaging thread - Inside software -- embedded checkout within a platform's interface, white-labelled and seamless - Through AI agents -- autonomous systems that sell, service, and collect payments without human involvement Each of these is a payment channel. Each has different technical requirements, different user experiences, and different compliance implications. The businesses winning right now aren't the ones with the best checkout page. They're the ones that can capture a payment wherever a conversation happens. ## The Five Payment Channels ### 1. Embedded Checkout The traditional model, evolved. A payment form lives inside your platform -- your branding, your domain, no redirect to a third-party page. The customer pays within the flow they're already in. When it's used: E-commerce, SaaS subscriptions, marketplace transactions, in-app purchases Technical requirements: API integration, hosted payment fields or SDKs, PCI tokenisation Key consideration: This is the channel most platforms start with. It handles the majority of online transactions. ### 2. Voice Payments Payments captured during a phone call -- via IVR, agent-assisted DTMF, or AI voice agent. Card data is entered by keypad or spoken aloud within a PCI-compliant environment. When it's used: Contact centres, insurance renewals, collections, phone sales, AI voice agent conversations Technical requirements: Telephony integration, DTMF capture and suppression, PCI-certified audio processing Key consideration: Voice is the forgotten channel. Most payment infrastructure ignores it. But for businesses where the phone is a primary customer interaction -- insurance, travel, utilities, collections -- voice payments are essential. See What Are Voice Payments? The Complete Guide. ### 3. Payment Links A URL that opens a branded checkout page. Sent via SMS, email, WhatsApp, or any messaging channel. The customer clicks, pays, and the transaction is confirmed -- no app download, no account creation. When it's used: Invoicing, post-call payment, field service, appointment deposits, collections follow-up Technical requirements: Link generation API, hosted checkout page, delivery via SMS/email API Key consideration: Payment links bridge the gap between conversations and transactions. An agent discusses an amount on the phone, sends a link via SMS, and the customer pays on their device -- all within the same interaction. ### 4. Chat Payments Payments captured within a messaging interface -- website live chat, WhatsApp, Facebook Messenger, or in-app messaging. An agent or AI bot presents a payment option inline, and the customer completes the transaction without leaving the chat. When it's used: Customer support, AI chat agents, conversational commerce, subscription management Technical requirements: Secure payment form rendered within chat, or payment link sent inline Key consideration: Chat is the fastest-growing payment channel for AI-driven businesses. AI chat agents can qualify, recommend, and close a sale -- including payment -- in a single conversation thread. See Chat Agent Payments: How AI Closes Sales Without a Human Handoff. ### 5. AI Agent Payments Autonomous payment capture by AI agents operating across voice and chat. The AI handles the conversation; a payment layer handles the transaction. When it's used: Automated sales, AI customer service, AI collections, AI-driven renewals Technical requirements: API-triggered payment flows, PCI-compliant capture environment, real-time result handling Key consideration: AI agents aren't a channel themselves -- they operate across channels (voice and chat). The payment infrastructure needs to support whatever channel the AI is using. See How AI Agents Process Payments: The Infrastructure Guide. ## Why Managing Channels Separately Breaks Most businesses build each payment channel as a separate integration: - Stripe for online checkout - A custom SMS gateway for payment links - A different provider for chat payments This creates four problems: ### 1. Fragmented Data Each channel has its own dashboard, its own transaction records, its own reporting. Reconciling across channels is manual. Getting a single view of a customer's payment history requires stitching data from multiple systems. ### 2. Inconsistent Merchant Experience If you're a platform serving merchants, each channel may support different PSPs, different payment methods, and different settlement flows. Merchant A can accept cards online but not over the phone. Merchant B can send payment links but can't take voice payments. The experience is fractured. ### 3. Multiple PCI Integrations Each payment channel that handles card data is a separate PCI surface. More integrations mean more compliance scope, more audit surface, and more risk. Every new channel expands the attack surface. ### 4. Engineering Overhead Four channel integrations means four sets of APIs to maintain, four providers to manage, four sets of webhooks to handle, and four potential points of failure. When a PSP changes their API, you update it in four places. ## The Unified Payment Layer Approach A single payment layer that supports all channels solves these problems by design. One integration. Your platform connects to the payment layer once. Voice, links, chat, embedded checkout -- all route through the same API. One dashboard. Transaction data from every channel appears in one place. Refunds, disputes, and reporting are unified. You see the full picture. One PCI surface. The payment layer handles card data for all channels within a single PCI-certified environment. Your compliance scope doesn't expand as you add channels. One set of PSPs. The gateways configured for your platform work across all channels. Add Worldpay for your UK merchants and it's available for voice, links, checkout, and chat -- without separate integrations per channel. Channel expansion without re-integration. Starting with embedded checkout? Adding voice payments later doesn't require re-engineering your payment stack. It's a configuration change. ## What Multi-Channel Looks Like in Practice ### Platform Serving Enterprise Merchants A vertical SaaS platform offers embedded checkout within its software. When an enterprise client requests phone payments for their customers, the platform enables voice checkout through the same payment layer -- same PSP configuration, same merchant setup, same reporting dashboard. The enterprise client's Worldpay integration works across both channels without additional development. ### Contact Centre With AI Agents A BPO handles customer service calls for an insurance company. Human agents take payments via DTMF during live calls. The company deploys AI voice agents for routine payment calls (renewals, top-ups). Both channels use the same payment infrastructure. When DTMF isn't practical, agents -- human or AI -- send a payment link via SMS. Three channels, one integration. ### AI-First Sales Operation An AI chat agent qualifies leads on a website and collects payment to close the sale. For customers who prefer phone interaction, an AI voice agent handles the same flow. Both agents trigger the same payment layer. Transaction data, tokenised cards, and merchant configuration are shared across channels. ## What to Look For ### Channel Coverage Today and Tomorrow Does the solution support the channels you need now? What about the channels you'll need in 12 months? Adding AI agent payments or voice checkout shouldn't require switching providers. ### Unified Reporting Can you see all transactions -- across all channels -- in one dashboard? Can merchants? ### PSP Consistency Do the same gateways work across all channels? If you add a PSP for checkout, does it automatically work for voice and links? ### Single PCI Surface Does adding a channel expand your PCI scope? It shouldn't. All channels should route through the same PCI-certified environment. ### Tokenisation Across Channels Can you tokenise a card during a voice call and reuse that token for an online transaction later? Cross-channel tokenisation is what makes the unified model powerful -- a customer provides card details once, and they're available everywhere. ## FAQ Do I need all five channels? No. Most businesses start with one or two and expand. The point of a unified payment layer is that expansion doesn't require re-integration. Start with embedded checkout, add voice later, add AI agent payments when you're ready. Is multi-channel more expensive than single-channel? Not with a unified layer. You pay per transaction regardless of channel. The cost of adding a channel is integration effort, not incremental payment infrastructure cost. How does PCI compliance work across channels? All channels route through the same PCI-certified environment. Card data is captured and tokenised within that environment regardless of whether it entered via DTMF (voice), a hosted form (checkout/chat), or a payment link. Your PCI scope doesn't change as you add channels. Can different merchants use different channels? Yes. Channel availability can be configured per merchant. Merchant A might use checkout and payment links. Merchant B might use checkout, voice, and AI agent payments. The platform controls which channels are available to which merchants. What about settlement and reconciliation? Transactions from all channels settle through the same PSP relationships and appear in the same reporting. There's no need to reconcile across separate systems. Ready to capture payments across every channel? Shuttle gives platforms a single integration for embedded checkout, voice payments, payment links, and AI agent payments -- with 40+ PSPs and PCI DSS Level 1 compliance. [Book a Demo] | [See Platforms] ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments) - [Chat Agent Payments: How AI Closes Sales Without a Human Handoff](/guides/chat-agent-payments) - [How AI Agents Process Payments: The Infrastructure Guide](/guides/ai-agent-payments) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/nab-twilio-integration/ --- # How to Connect NAB to Twilio for Voice & IVR Payments | Shuttle > NAB doesn't natively connect to Twilio for voice payments. If you want to process NAB Transact transactions during a phone call (via IVR, agent-assisted,... # How to Connect NAB to Twilio for Voice & IVR Payments By Shuttle Team, June 22, 2026 NAB doesn't natively connect to Twilio for voice payments. If you want to process NAB Transact transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects NAB (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction, with settlement going straight to your NAB merchant facility. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why NAB + Twilio Don't Connect Directly NAB is one of Australia's big four banks, and NAB Transact is its merchant payment gateway: the online and virtual-terminal system Australian businesses use to process card payments against their NAB merchant facility. It handles AUD processing with bank-grade settlement directly into your NAB business account. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. And is available in Twilio's Australia (AU1) region, which matters if your organisation needs voice data processed in-country. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. NAB isn't one of Twilio's built-in connectors, so there is no direct path from a Twilio call to your NAB Transact account. This is where Shuttle comes in. As one of the connectors listed for the AU1 region), Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to NAB Transact for processing. One integration connects the two platforms. For Australian enterprises and contact centres that bank with NAB (utilities, insurers, councils, collections teams), this combination means voice payments with Australian data residency and settlement to your own bank, not a third-party acquirer. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via NAB Transact. The connector creates a payment request, processes the transaction through your NAB merchant facility, and handles the response. - Result returned to your call flow. Your webhook receives the NAB transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A NAB merchant facility with NAB Transact credentials (your NAB client ID and transaction password, supplied by NAB) - A Shuttle account (free to create: you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add NAB Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: NAB (NAB Transact) - Merchant / client ID: Your NAB Transact client ID - Transaction password: Your NAB Transact API password (this is separate from your NAB login password; contact NAB if you don't have it) - Currency: AUD - Environment: Live or Test Save the profile. Shuttle now has a live connection to your NAB merchant facility. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code (AUD for NAB Transact) - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in NAB Transact if needed. Update your account records, confirm to the caller, and continue the flow. ### Step 5: Test Use NAB Transact's test environment and Twilio's test credentials to verify the flow end-to-end before going live. Run a test transaction, confirm the webhook fires, and check the transaction appears in your NAB Transact reporting. ## What You Can Do With NAB + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, NAB Transact processes, and funds settle to your NAB merchant facility. ### Authorise Now, Capture Later Place a hold on the card during the call and capture the payment later: useful for bookings, deposits, or variable-amount transactions. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Australian Data Residency Because Twilio's verb is available in the Australia (AU1) region and Shuttle is one of the connectors available there, Australian organisations can run voice payments with in-country voice processing and settlement through an Australian bank. For councils, utilities, and insurers with data-residency requirements, this is often the deciding factor. ## Multi-PSP: Beyond NAB One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Australian merchants with NAB and your international merchants with a global acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Adyen, Worldpay, etc.) - Want a backup gateway: if one gateway is unavailable, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, with minimum amount, maximum amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own NAB merchant facility (or any other gateway) through the same Twilio integration. ## PCI Compliance The NAB + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to NAB Transact. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect NAB to Twilio without Shuttle? Twilio doesn't have a built-in NAB Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work in Twilio's Australia (AU1) region? Yes. Twilio's verb is available in the AU1 region, and Shuttle is one of the connectors Twilio lists for it. That means Australian organisations can keep voice payment processing in-region. Do I need a NAB merchant facility first? Yes. Shuttle connects to your existing NAB Transact account; it doesn't replace your merchant relationship with NAB. Settlement continues to flow into your NAB business account on NAB's standard terms. What about NAB Transact's test environment? Fully supported. Use your NAB Transact test credentials in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. NAB's standard merchant fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from NAB to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same: no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Fat Zebra to Twilio for Voice Payments: the other Australian gateway, step-by-step setup - NAB on Shuttle: gateway details and supported features - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect NAB to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ### Payment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Fat Zebra to Twilio for Voice Payments](/guides/fat-zebra-twilio-integration/) - [NAB on Shuttle](/payment-providers/nab/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) - [BlogPayment Links for Fortis: Send Branded Checkout Links Without Building Custom Integrations→](/blog/payment-links-for-fortis/) --- URL: https://www.shuttleglobal.com/guides/nextiva-payments/ --- # Nextiva Payments: Multi-PSP Payment Capture Across Voice and Chat | Shuttle > Nextiva is a unified communications and contact centre platform (UCaaS plus CCaaS) that positions itself around "Unified Customer Experience Management."... # Nextiva Payments: Multi-PSP Payment Capture Across Voice and Chat By Shuttle Team, May 12, 2026 Nextiva is a unified communications and contact centre platform (UCaaS plus CCaaS) that positions itself around "Unified Customer Experience Management." It pulls voice, chat, SMS and contact centre workflows into one stack and is widely used across SMB and mid-market teams. The telephony is Nextiva-native, so if your agents handle inbound and outbound calls, Nextiva is often already the system of record for those conversations. On payments, the posture is precise and worth getting right. Nextiva is explicitly not a credit card processor: its own documentation states "We are not a credit card processor, you still use your bank's credit card processing service." What Nextiva does provide is a native Secure Payment Agent Assist (SPAA) capability, a PCI-descope capture tool that routes a caller through a secure IVR so card data never reaches the agent. That is a real, useful native feature, and this guide treats it as such. If you are a merchant using Nextiva, or a System Integrator or reseller implementing it for clients, this guide covers what SPAA gives you and when a multi-PSP payment layer across voice and payment links fits better, particularly for agencies, BPOs and multi-brand operators who need to route to many gateways rather than one. It also sets out, plainly, how Shuttle works with a Nextiva operation today. ## Nextiva's Secure Payment Agent Assist: What You Get SPAA (also surfaced as Advanced IVR Credit Card Payment) is a genuine PCI-descope tool. When a caller is ready to pay, the agent clicks "CC Pay" and the caller is routed to a secure IVR. The caller enters their card number, expiry and CVV using their phone keypad (DTMF touch-tone). The agent cannot see or hear those digits. The encrypted card data is transmitted to the merchant's existing payment gateway, a confirmation returns, and the caller reconnects to the agent to finish the conversation. Nextiva states that SPAA / Advanced IVR Credit Card Payment is PCI DSS Level 1 compliant. Because the agent never touches the card data, it keeps spoken card numbers out of call recordings and reduces the cardholder data environment the agent workstation sits in. For a single-merchant, voice-only payment flow that points at one gateway, SPAA does the core job well. The two things to note are scope, not quality: SPAA is voice and IVR only, and it routes to one merchant gateway. That is the right design for most single-brand operators. It becomes a constraint when you need multiple gateways or payment on channels beyond the phone. ## When a Multi-PSP Layer Helps A multi-PSP payment layer like Shuttle is the better fit when one of these is true: - You run an agency, BPO or multi-brand operation and need per-client or per-tenant routing. SPAA points at one gateway. If you collect on behalf of many clients, each with their own acquirer or merchant account, you need to configure each client against their own gateway. - You take payments on more than voice. Customers pay over SMS, email and hosted payment links, not just on the phone. A single layer that covers voice card capture and links keeps one reconciliation flow instead of separate tools per channel. - You want gateway choice. Shuttle connects to 30+ payment gateways with bring-your-own-gateway support, so you keep your existing acquirer and pricing rather than being tied to a single processor relationship. ## How Shuttle Works With Nextiva Today Before the architecture, be clear about the model, because it determines whether Shuttle is a fit: - There is no native Nextiva integration today. Shuttle's voice payment capture runs on Twilio Pay. You invoke that Twilio-based setup; you do not install a Shuttle app inside Nextiva. - You need to be a Twilio customer to use voice capture with Shuttle. - You need technical resource to implement it. Shuttle provides ready-made interfaces for payment links and the PCI-compliant capture, IVR and APIs for voice, but you build the agent-side interface for your own Nextiva workflow, because every contact centre setup is different. There is no pre-built Shuttle widget for Nextiva. - A native Nextiva integration is possible as a paid project. If you want a deeper, platform-specific build, Shuttle can deliver one at a project cost. - Carrier-agnostic is on the roadmap. Shuttle works with Twilio today, and any carrier coming soon. If you have the technical resource and are (or can be) a Twilio customer, here is how the pieces fit together. - You keep Nextiva as your communications and contact centre platform. Nothing changes about how agents handle calls and chats. - Shuttle connects to your existing payment gateway (or several), so funds settle to your own merchant account with no change to your acquirer. - When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The caller keys their card in on their phone keypad, and the digits are captured inside Shuttle's certified environment, never reaching your Nextiva agents, recordings or CRM. - For SMS, email or follow-up, Shuttle generates a hosted payment link the customer completes themselves on a PCI-compliant page, including mid-call to a customer still on the line. - Confirmation returns in real time and the transaction reconciles back to the right client or brand, with per-tenant routing for agencies. ## How It Works ### Agent workflow When the customer is ready to pay, the agent triggers a secure payment session from the interface you build against Shuttle's APIs. For voice, the card is captured in a PCI DSS Level 1 call via Twilio Pay while the caller keys in their digits; those digits are captured inside Shuttle's certified environment, away from the agent and the recording. For SMS or email follow-up, the agent sends a payment link in one click. The agent sees only a success or failure status, never the card data. ### Customer experience On a call, the caller is taken into the secure Twilio Pay capture, keys their card in privately, and the agent confirms the result once payment clears. By link, they tap and pay on a branded, secure page. One honest caveat: the secure capture at the point of payment is what's live now via Twilio Pay. Shuttle being present for the entire Nextiva conversation is not yet turnkey. Returning the caller to the same agent and call after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes with context. Shuttle works with Twilio today, and any carrier coming soon. ## Multi-PSP Support - 30+ payment gateways supported, including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square. See the full list at /payment-providers/. - Bring your own gateway: keep your existing acquirer, merchant account and negotiated rates. Switching gateways later is configuration, not a re-integration. - Per-client and per-tenant routing: send each transaction to the correct gateway automatically, essential for agencies, BPOs and multi-brand operators. - One layer across voice and payment links, so reconciliation stays in a single place. One voice caveat: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of PCI assurance. Because card data is captured directly by Shuttle and never enters your Nextiva agents' workstations, call recordings or chat transcripts, the PCI scope of your contact centre is reduced. In practice this can move qualifying merchants from the heavier SAQ-D obligations toward the much lighter SAQ-A, since the sensitive cardholder data environment is descoped to Shuttle's certified infrastructure. Your QSA confirms the exact SAQ that applies to your setup, but the direction of travel is fewer controls to evidence on your side. ## Beyond Voice: Payment Links Not every payment happens on a live call. A customer may want to pay after the conversation, confirm an order later, or settle a balance from an SMS. Shuttle generates hosted payment links your Nextiva agents can send by SMS or email, including mid-call. The customer pays on a secure, branded page, and the result reconciles back into the same flow as your voice payments. Links are the most turnkey part of Shuttle and work even with gateways that don't support voice capture. This is the part SPAA does not cover, and it is often the reason multi-channel operators add Shuttle to a Nextiva operation. ## For Solution Providers and Nextiva Partners If you implement Nextiva for clients, payments are a recurring requirement you can own. Nextiva runs a Nextiva Partner Program for channel partners, agents, resellers and MSPs, with a partner portal, plus a Nextiva App Marketplace and integrations catalogue. It is more reseller and channel-oriented than an open developer app store, so payment capability is added through integrations and partner-led delivery rather than self-serve developer apps. Shuttle is the multi-PSP payment layer you add to Nextiva deployments. For each client you can connect their existing gateway, route per tenant when you serve multiple brands, and deliver voice plus link payment in one integration, on Twilio today. Voice pricing is $0.20 per successful transaction with no setup or per-seat fees, and Links Checkout is a separate app, which makes it straightforward to attach to a client engagement and resell without a fixed cost base to recover. ## Use Cases ### Bill-Pay and Collections Inbound and outbound calls where customers settle invoices or arrears. Agents take card payments securely on the call, or send a link for the customer to pay later, with full descope. ### Order Taking Sales and service teams capturing card-not-present orders over the phone, or by link sent to the customer, without spoken card numbers landing in recordings. ### Account Payments Subscription, membership and account top-up payments handled mid-conversation, with the customer keying their card privately and returning to the agent. ### Multi-Client / Agency Collection Agencies and BPOs collecting on behalf of many clients, with each transaction routed to the correct client gateway automatically and reconciled per brand. ## FAQ Does Nextiva process payments? No, Nextiva is not a credit card processor and says so directly: you still use your bank's processing service. It does provide a native Secure Payment Agent Assist (SPAA) descope tool that routes card capture through a secure IVR to your existing gateway. What does Shuttle add over SPAA? SPAA is voice and IVR only and routes to one merchant gateway. Shuttle adds multi-PSP and per-client routing across 30+ gateways, plus hosted payment links, all in one layer. It suits agencies, BPOs and multi-channel operators rather than single-brand voice-only flows. Does Shuttle have a native Nextiva integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Nextiva. You need to be a Twilio customer and to build the agent-side interface for your workflow. Shuttle can build a native Nextiva integration as a paid project. Shuttle works with Twilio today, and any carrier coming soon. Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so voice capture needs you to be a Twilio customer. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Which gateways does Shuttle support? 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square, with bring-your-own-gateway support. Switching gateways is configuration, not a re-integration. A few gateways (for example Braintree) don't work for voice capture but do work for links. See /payment-providers/. Does Shuttle work for outbound payments and collections? Yes. Agents can take card payments on outbound calls via the secure Twilio Pay capture, or send a payment link by SMS or email for the customer to pay in their own time. Will this reduce our PCI scope? Yes. Card data is captured in the secure Twilio Pay call by Shuttle's PCI DSS Level 1 certified infrastructure and never reaches your agents or recordings, which can move qualifying merchants from SAQ-D toward SAQ-A. Confirm your exact SAQ with your QSA. ## Related Reading - Contact Centre Payments: the hub guide covering secure payment capture across CCaaS platforms. - Embedded Payments for CCaaS: how payment capture embeds into contact centre workflows. - AI Voice Agent PCI Payments: taking PCI-compliant payments through automated and AI-assisted voice. - Payment Collection for BPOs: multi-tenant collection and per-client gateway routing for outsourcers. - Payments for CCaaS Implementation Partners: adding a payment layer to CCaaS deployments as an SI or reseller. ## Take Payments Across Channels in Nextiva Nextiva's SPAA covers voice descope to a single gateway. If you need multi-PSP routing, per-client collection or payment across voice and links, Shuttle is the layer that fits alongside it, on Twilio today. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [/payment-providers/](/payment-providers/) - [PCI DSS Level 1](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [$0.20 per successful transaction](/pricing/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Payments for CCaaS Implementation Partners](/guides/payments-for-ccaas-implementation-partners/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/nice-cxone-payments/ --- # How to Take Payments on NICE CXone: Secure Payment Processing | Shuttle > NICE CXone (formerly NICE inContact) is an enterprise-grade CCaaS platform used by some of the largest contact centre operations in the world. # How to Take Payments on NICE CXone: Secure Payment Processing By Shuttle Team, March 6, 2026 NICE CXone (formerly NICE inContact) is an enterprise-grade CCaaS platform used by some of the largest contact centre operations in the world. It handles omnichannel routing, workforce management, analytics, and AI-powered automation at scale. For organisations processing thousands of customer interactions daily, CXone is a proven platform. But when it comes to capturing card payments during calls, CXone has a gap, and the existing options to fill it are more limited than most buyers realise. NICE has partnerships with third-party providers for payment capture. These integrations work, but they typically limit you to specific payment gateways. If your merchants use Worldpay and the payment partner only supports Stripe, you have a problem. If you are a BPO routing payments to dozens of different client gateways, the limitation is a deal-breaker. This guide covers how a CXone-based operation can add enterprise-grade, PCI-compliant payment capture with full multi-PSP flexibility using Shuttle, and exactly what that involves today. Some of the world's biggest brands use Shuttle for voice payments. ## The Payment Gap in NICE CXone CXone's payment partnerships address the basic requirement, secure card capture during calls. But the implementation details matter, and for many enterprise deployments, the current options fall short. - Gateway lock-in. The existing payment partnerships typically support a limited set of payment gateways. Enterprise customers with established relationships with specific processors (Worldpay, Adyen, Checkout.com, Braintree) may find that their gateway is not supported, or that switching is required. This is rarely acceptable at enterprise scale. - Limited multi-PSP routing. BPOs and multi-tenant contact centres need to route different clients' payments to different gateways. A single-gateway integration does not scale to environments where Client A uses Adyen, Client B uses Worldpay, and Client C uses Stripe. Each requires separate configuration, or separate payment vendor relationships. - Cost structure. Some existing payment partners charge per-seat licensing, setup fees, or minimum commitments in addition to per-transaction costs. For contact centres with large agent populations, this can add significant overhead. - Integration complexity. Switching from one payment partner to another, or adding multi-PSP capability to an existing CXone deployment, can involve significant re-integration work across Studio scripts, agent interfaces, and reporting. The result is that many CXone deployments either accept gateway lock-in (limiting their merchants), pay premium pricing for limited flexibility, or avoid in-call payments entirely. ## How Shuttle Adds Payments to NICE CXone Shuttle adds PCI-compliant card capture to your NICE CXone payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your NICE CXone recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for NICE CXone specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your NICE CXone call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running NICE CXone have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your CXone recordings, your connected CRM, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for NICE CXone, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running NICE CXone have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on CXone as normal, connected to a live agent or a virtual agent powered by CXone SmartAssist. - Payment is triggered from your agent interface when the customer is ready to pay, or via API from an automated flow. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay; the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways, and the transaction is authorised in real time. - Result returned to your interface and your systems via webhook. - No card data in CXone. The card digits never touch your CXone recordings, your CRM, or your agent workstations. ## Multi-PSP Support This is where Shuttle differs most from the existing CXone payment partnerships. Where those integrations typically limit you to one or two gateways, Shuttle supports 30+ payment gateways with configurable provider selection. For enterprise CXone deployments, multi-PSP capability is not a nice-to-have, it is a requirement: - BPO operations serve multiple end clients, each with their own merchant account and gateway. Client A processes through Worldpay, Client B through Adyen, Client C through Checkout.com. Shuttle routes each transaction to the correct gateway based on the client configuration. - Multinational enterprises need different gateways for different regions. UK payments route to one processor, European payments to another, North American payments to a third. Shuttle handles region-based routing. - Redundancy: if a primary gateway goes down, you can move the affected payment types to another connected gateway. For high-volume contact centres processing thousands of payments daily, gateway outages cannot mean payment outages. - Card-type routing sends specific card brands to gateways with preferential rates, optimising transaction costs at scale. Switching processors later is straightforward; gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest certification level, validated annually by a Qualified Security Assessor. Because the card is captured in the secure Twilio Pay call, card data never enters your CXone environment. Your telephony systems, call recordings, agent desktops, CRM integrations, and network infrastructure stay out of PCI scope, keeping you on the lighter SAQ-A path. Full compliance documentation, including the AOC scope, is in the security docs. For CXone deployments in regulated industries (insurance, financial services, healthcare, utilities), this scope reduction is often a procurement requirement. Buyers want documented evidence that card data is handled exclusively by a PCI-certified third party, not by the contact centre infrastructure. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Insurance Insurance contact centres on CXone handle premium collections, policy renewals, claims payments, and payment plan adjustments. These are high-frequency payment interactions that benefit from in-call capture. Shuttle enables agents to collect payments without breaking the conversation, and multi-PSP routing supports insurers with complex gateway arrangements across different business lines. ### Debt Collection and BPO Collections agencies and BPOs are among the largest CXone users. They need to capture payments at the moment of commitment, when a debtor agrees to a settlement or payment plan. Any delay (transferring to a website, sending a link) reduces conversion, though a mid-call link keeps the customer on the line. Shuttle captures the payment in-call, and per-client gateway routing means BPOs do not need to force their clients onto a single processor. ### Utilities and Telecoms Utility companies process millions of bill payments through contact centres. CXone handles the customer interaction at scale; Shuttle handles the payment capture. High-volume, low-value transactions benefit from Shuttle's $0.20 flat per-transaction pricing with no seat-based licensing. ### Government and Public Sector Government agencies using CXone for citizen services (tax payments, licence fees, fines) require strict PCI compliance and often have specific gateway requirements. Shuttle's PCI Level 1 certification and gateway flexibility meet public sector procurement standards. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged NICE CXone plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for NICE CXone specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your NICE CXone call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running NICE CXone have already done it. - A native NICE CXone integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native NICE CXone integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in CXone. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running NICE CXone have already done. We can build a native CXone integration as a paid project, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### Can we try it before committing? Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready. ### How many payment gateways does Shuttle support? Shuttle supports 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, GoCardless, and many more. You can configure multiple gateways simultaneously with per-merchant configuration. Switching gateways is configuration, not a re-integration. ### What does Shuttle cost? $0.20 per successful transaction for voice, no setup fees and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, comprehensive guide to secure contact centre payments - Twilio Pay Connectors, Shuttle's Twilio payment infrastructure integration - Voice Payments, taking payments over voice channels - AI Voice Agent PCI Payments, payment capture for AI voice agents - Embedded Payments for CCaaS, the CCaaS platform operator's guide ## Get Started Shuttle adds multi-gateway, PCI-compliant payments to a NICE CXone operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/nmi-twilio-integration/ --- # How to Connect NMI to Twilio for Voice & IVR Payments | Shuttle > NMI doesn't natively connect to Twilio for voice payments. If you want to process NMI transactions during a phone call (via IVR, agent-assisted, or AI... # How to Connect NMI to Twilio for Voice & IVR Payments By Shuttle Team, June 24, 2026 NMI doesn't natively connect to Twilio for voice payments. If you want to process NMI transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects NMI (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and why it's a particularly good fit for the software platforms, ISVs, and multi-merchant operations that NMI serves. ## Why NMI + Twilio Don't Connect Directly NMI is the gateway behind the gateway. It's a white-label payment platform used by ISVs, ISOs, SaaS companies, and banks to embed payments under their own brand, with hundreds of processor and acquirer integrations underneath. If you're a software platform that resells payments, there's a good chance NMI is somewhere in your stack. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. NMI isn't one of Twilio's built-in connectors, so there's no native path between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to NMI's Payment API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via NMI. The connector submits the transaction to NMI, authenticated with your security key, and handles the response. - Result returned to your call flow. Your webhook receives the NMI transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An NMI gateway account with a security key (created in the Merchant Portal under Settings, then Security Keys) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add NMI Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: NMI - Security key: Your NMI API security key (the private, server-side key, not a Collect.js tokenisation key) - Currency: Set your default (USD, GBP, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your NMI gateway account. If you're a platform managing multiple merchants, create one payment profile per merchant, each with that merchant's own NMI security key. More on this below. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in your NMI Merchant Portal if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test NMI supports test mode on your gateway account (Settings, then Test Mode in the Merchant Portal). While test mode is enabled, valid test cards are approved but no charges are processed. Use NMI's standard Visa test card to verify the flow end-to-end before going live. ## What You Can Do With NMI + Twilio ### Charge Immediately Standard sale transaction. The caller pays, NMI processes through your configured processor, done. ### Authorise Now, Capture Later Place a hold on the card during the call and capture later. Useful for bookings, deposits, or variable-amount transactions where the final figure isn't known at call time. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via NMI's Customer Vault, NMI's secure storage for payment data used in recurring and repeat billing. The token is reusable across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Multi-Merchant Voice Payments for Platforms This is where NMI + Twilio really fits. NMI's core market is software platforms and ISVs that embed payments for many merchants at once. Shuttle mirrors that model: each sub-merchant's NMI credentials become a separate Shuttle payment profile, and Shuttle routes each call's transaction to the right merchant's gateway account. One Twilio integration, any number of merchants, each settling through their own NMI account. The same pattern works for BPOs and outsourced contact centres taking payments on behalf of multiple clients. ## Multi-PSP: Beyond NMI One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: route some merchants through NMI and others through Stripe, Adyen, or a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, per merchant, with amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. For NMI-centric platforms this is a genuine safety valve. You keep NMI as your primary rail while staying free to onboard a merchant who arrives with a different gateway mandate. ## PCI Compliance The NMI + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to NMI. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect NMI to Twilio without Shuttle? Twilio doesn't have a built-in NMI Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. I'm an ISV with many merchants on NMI. Can each merchant use their own account? Yes. Create a Shuttle payment profile per merchant, each holding that merchant's NMI security key. Shuttle routes each transaction to the correct merchant's gateway account through the same Twilio integration. Does this work with NMI's Customer Vault? Yes. Cards captured over the phone can be tokenised into the Customer Vault for recurring or repeat billing, and reused across web, mobile, voice, and payment links. What about testing? Fully supported. Enable test mode on your NMI account, use the standard test card (), and run the full Twilio flow before going live. What does it cost? Shuttle charges $0.20 per successful transaction. NMI's gateway and processing fees apply on top, per your NMI agreement. No Shuttle setup fees or monthly minimums. Can I switch from NMI to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Payment Collection for BPOs: multi-client payment collection in outsourced contact centres - NMI on Shuttle: supported features and channels - Twilio Pay, Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect NMI to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for NMI: Send Branded Checkout Links for ISOs, Resellers, and Merchants ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [NMI](/payment-providers/nmi/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [BPOs and outsourced contact centres](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [NMI on Shuttle](/payment-providers/nmi/) - [Twilio Pay, Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for NMI: Send Branded Checkout Links for ISOs, Resellers, and Merchants→](/blog/payment-links-for-nmi/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/observe-ai-payments/ --- # Observe.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres | Shuttle > If your contact centre uses Observe.AI, for a financial services collections operation, a healthcare revenue-cycle team, an insurance servicing... # Observe.AI and Payments: PCI-Compliant Card Capture for Observe.AI-Powered Contact Centres By Shuttle Team, April 23, 2026 If your contact centre uses Observe.AI, for a financial services collections operation, a healthcare revenue-cycle team, an insurance servicing organisation, or an outsourced support BPO, you've probably already met the payment gap. Observe.AI's voice agents and agent assist tools transcribe, analyse, score, and coach in real time across every call. But when a customer says "I'd like to pay," neither Observe.AI nor the CCaaS underneath it has a native, PCI-compliant way to capture their card. Observe.AI sits across the conversation layer, voice AI agents handling automated flows, agent assist coaching live agents in real time, post-call quality monitoring, and conversation intelligence for compliance and coaching. The platform integrates with Genesys, Five9, NICE CXone, Avaya, Talkdesk, Twilio, Cisco, and other major CCaaS environments. What Observe.AI doesn't do, and isn't built to do, is the secure card-capture moment. This guide is for merchants running Observe.AI on top of a CCaaS platform, and for solution providers and Observe.AI partners deploying Observe.AI for clients. It covers how Shuttle adds PCI-compliant payment capture to Observe.AI-powered operations, what that involves today, and why card data stays out of Observe.AI's analysis pipeline. ## The Payment Gap Around Observe.AI Observe.AI is a voice AI and conversation intelligence platform. Card capture is a separate problem, and here are the gaps for businesses taking payments on Observe.AI-powered calls: - Observe.AI sits on the AI/analytics layer, not telephony. The platform analyses conversations, surfaces insights, and runs voice AI agents, but card capture has to happen elsewhere. - The CCaaS underneath usually doesn't capture cards either. Genesys, Five9, NICE CXone, Talkdesk, Avaya all face the same payment gap, see the contact centre payments guide for platform-specific detail. - Voice AI cannot execute card transactions safely. Observe.AI voice agents handle conversational flows, intent recognition, routing, scheduling, FAQ. Capturing a card during a fully autonomous voice AI call requires a PCI-compliant payment layer the AI can hand off to. - Recording and transcription pose PCI risk. Observe.AI processes recordings and transcripts in real time and post-call. If card numbers are spoken aloud, they end up in transcripts and analytics, dragging Observe.AI-adjacent infrastructure into PCI scope. - Single-PSP add-ons miss the multi-tenant case. BPOs and outsourcers running Observe.AI across multiple end-clients each have different acquirer relationships. Single-gateway integrations don't fit. ## How Shuttle Adds Payments to Observe.AI Shuttle adds PCI-compliant card capture to your Observe.AI payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Observe.AI recordings, transcription, or your agents. AI-based operations today. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Observe.AI specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Observe.AI call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Observe.AI have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach Observe.AI's transcripts, voice agent flows, quality scoring, or coaching outputs, because the card data never enters that pipeline. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Voice AI payment handoff For autonomous Observe.AI voice agent calls, the payment moment is a handoff: the AI agent confirms intent and amount, then hands off to Shuttle's secure Twilio Pay capture. The AI never touches cardholder data. This is the handoff pattern via Shuttle's APIs, which you wire into your own voice AI flow rather than relying on a pre-built connector. ### Payment Links This is the most turnkey path. For outbound recovery, agreed payment plans, or customers who can't enter card details on the phone, Shuttle generates payment links with the agreed amount and sends them via SMS or email, including mid-call. Status posts back into the case for the agent's reference. Links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Observe.AI, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Observe.AI have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on your CCaaS as normal. Observe.AI continues transcribing, scoring, and coaching the surrounding conversation. - Payment is triggered from your agent interface, or via handoff from an autonomous voice AI flow, when the customer is ready to pay. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay, the customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment, never reaching Observe.AI. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways, then tokenises before any return to your systems. - Result returned to your interface and your systems via webhook. - No card data in Observe.AI. Observe.AI transcripts, voice agent flows, quality scoring, and coaching outputs never contain card numbers. ## Multi-PSP Support Shuttle is gateway-agnostic. We connect to 40+ PSPs, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Authorize.Net, GlobalPayments, FreedomPay, FIS, Elavon, Fiserv, and most regional acquirers. You can route transactions based on currency, region, business unit, or BPO client, useful for enterprise Observe.AI deployments where each tenant or brand has its own acquirer. Switching processors later is straightforward, gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, cardholder data stays out of the Observe.AI pipeline entirely: - Card digits are captured directly into Shuttle's certified environment, then tokenised before any return to your systems. They are never recorded, never transcribed, never reach Observe.AI's transcript stream. - Observe.AI transcripts, voice agent flows, quality scoring, and coaching outputs never contain card numbers. Your PCI scope, and Observe.AI's, stays narrow on the lighter SAQ-A path. - Audit trails, settlement reports, and reconciliation are available via Shuttle's reporting layer. For Observe.AI customers in regulated verticals, financial services, insurance, healthcare, BPOs handling regulated products, Shuttle is built to keep certified scope tight without disrupting the voice AI and analytics layer. Full compliance documentation is in the security docs. ## For Solution Providers and Observe.AI Implementation Partners If you're an Observe.AI partner or SI deploying Observe.AI on top of Genesys, Five9, NICE CXone, Talkdesk, Avaya, or other CCaaS for clients, Shuttle is the payment layer you can add via a Twilio-based setup. We support white-label deployment, multi-PSP routing across your client portfolio (each client keeps their preferred acquirer), and partner-friendly commercials. Shuttle is a Pay Connector provider on the Twilio Marketplace. A native Observe.AI integration can be built as a paid project. For partnership conversations, book a discovery call. ## Use Cases ### Financial Services Collections Collections teams using Observe.AI for tone-aware coaching during recovery calls can settle agreed payment plans during the call. Multi-PSP routing handles different agency-of-record arrangements. ### Healthcare Revenue Cycle Healthcare revenue-cycle teams using Observe.AI for compliance-aware quality monitoring can take patient payments during billing calls without exposing PHI or cardholder data to the analytics pipeline. ### Insurance Premium and Renewal Insurance servicing teams using Observe.AI can take premium payments and renewals during inbound enquiries or outbound nudges. Voice AI agents can handle the conversational flow; Shuttle handles the secure capture. ### BPO and Outsourced Contact Centres BPOs running Observe.AI across multiple end-clients can route payment transactions to each client's preferred acquirer, with per-tenant configuration and clean settlement separation. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Observe.AI plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Observe.AI specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Observe.AI call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Observe.AI have already done it. - A native Observe.AI integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Observe.AI integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Observe.AI or its underlying CCaaS. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Observe.AI have already done. We can build a native Observe.AI integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Will Shuttle work with Observe.AI's voice AI agents? For autonomous voice AI flows, the payment moment is a handoff, the AI confirms amount and intent, Shuttle handles the secure capture via Twilio Pay, then control returns to the AI. The AI never touches cardholder data. You wire this handoff into your flow using Shuttle's APIs. ### Does Shuttle affect Observe.AI's transcripts or quality scoring? No. Observe.AI continues transcribing, scoring, and analysing the surrounding conversation. Because the card is captured in the separate Twilio Pay call, transcripts and quality outputs never contain cardholder data. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### What does Shuttle cost? $0.20 per successful transaction for voice, with no per-seat fees, so cost scales with payment volume not headcount. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the platform-by-platform merchant + SI guide - Genesys Payments, common CCaaS underneath Observe.AI - Five9 Payments, common CCaaS underneath Observe.AI - NICE CXone Payments, common CCaaS underneath Observe.AI - AI Voice Agent PCI Payments, for AI-led contact centres - Twilio Pay Connectors, Shuttle's multi-gateway Pay Connector - Voice Payments, comprehensive voice payment capture guide ## Get Started Shuttle adds enterprise-grade, PCI-compliant payment capture to an Observe.AI-powered operation via Twilio, without changes to Observe.AI's analytics layer, your CCaaS configuration, or your agent training, and across multiple PSPs. If you take payments in a contact centre, see how Shuttle works for merchants, or book a discovery call to walk through your specific Observe.AI + CCaaS deployment. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [contact centre payments guide](/guides/contact-centre-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [a Pay Connector provider on the Twilio Marketplace](/guides/twilio-pay-connectors/) - [book a discovery call](/contact/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Genesys Payments](/guides/genesys-payments/) - [Five9 Payments](/guides/five9-payments/) - [NICE CXone Payments](/guides/nice-cxone-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [Shuttle works for merchants](/merchants/payment-services/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/opayo-twilio-integration/ --- # How to Connect Opayo to Twilio for Voice & IVR Payments | Shuttle > Opayo doesn't natively connect to Twilio for voice payments. If you want to process Opayo transactions during a phone call (via IVR, agent-assisted, or AI... # How to Connect Opayo to Twilio for Voice & IVR Payments By Shuttle Team, June 27, 2026 Opayo doesn't natively connect to Twilio for voice payments. If you want to process Opayo transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Opayo (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This matters more for Opayo merchants than most. Opayo, formerly Sage Pay and now part of Elavon (a U.S. Bank company), is one of the UK's longest-established gateways, and a large share of its merchant base has always taken payments by phone: MOTO orders, invoice settlement, deposits, bookings. If your agents currently key card numbers into a virtual terminal while the customer reads them out, every agent, headset, and call recording sits inside PCI scope. Connecting Opayo to Twilio replaces that with automated DTMF capture, so card data never reaches your people or systems. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Opayo + Twilio Don't Connect Directly Opayo is built for card-not-present commerce: online checkout, invoice payments, and telephone (MOTO) orders. It has served UK and Irish merchants for over two decades, first as Sage Pay, and since Elavon's acquisition, as Opayo. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Opayo isn't one of Twilio's built-in connectors, so there's no native way to send transactions to your Opayo account. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Opayo's API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Opayo. The connector creates an Opayo transaction, processes it through your Opayo vendor account, and handles the response. - Result returned to your call flow. Your webhook receives the Opayo transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. For merchants used to reading card numbers back for confirmation, it's a step change: faster, quieter, and with the card data out of your systems. ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - An Opayo account with API credentials (vendor name, integration key, and integration password) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Opayo Credentials to Shuttle Generate API credentials in the MyOpayo portal if you haven't already (note: Opayo issues a single set of API credentials per account, and the integration password is shown only once, so store it securely). Then log into the Shuttle dashboard, navigate to Payment Profiles, and create a new profile: - Gateway: Opayo - Vendor name: Your Opayo vendor name - Integration key: From MyOpayo - Integration password: From MyOpayo - Currency: Set your default (GBP, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Opayo account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in MyOpayo if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Opayo's test environment is a copy of the live system without the banks attached, so you can run the full flow end-to-end with no money moving. Point your Shuttle payment profile at the test environment, use the test card numbers from Elavon's Opayo developer documentation, and verify the complete call flow before switching to live credentials. ## What You Can Do With Opayo + Twilio ### Charge Immediately Standard payment transaction. The caller pays, Opayo processes, done. This is the direct replacement for agents keying MOTO transactions into a virtual terminal. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card with Opayo and returns a reusable token, which you can use for future payments across any channel: web, mobile, voice, or payment links. For merchants taking recurring or repeat telephone orders, this means the customer reads out (or keys in) their card exactly once. The card data is never stored in your systems. ### Send a Payment Link Instead Not every caller wants to key digits. From the same Shuttle account, an agent can send a payment link by SMS or email mid-call, backed by the same Opayo profile. One gateway connection, multiple collection channels. ## Multi-PSP: Beyond Opayo One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your UK merchants with Opayo, and other regions with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway is unavailable, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for BPOs and outsourced contact centres that serve multiple merchants. One client might be on Opayo, another on Stripe; each merchant's transactions go through their own gateway account via the same Twilio integration. ## PCI Compliance The Opayo + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Opayo / Elavon Your systems No card data (SAQ-A) Card data flows from Twilio to Shuttle to Opayo. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. Contrast that with the traditional MOTO setup, where the agent hears the card number and types it into a terminal: the agent, their workstation, the call recording platform, and often the whole contact centre are in scope. For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Opayo to Twilio without Shuttle? Twilio doesn't have a built-in Opayo Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. I still know it as Sage Pay. Is this the same thing? Yes. Sage Pay was acquired by Elavon (a subsidiary of U.S. Bank) in 2019 and rebranded as Opayo. Your vendor account, credentials, and integrations carry the Opayo name, but it's the same UK gateway. Everything in this guide applies whether you signed up as Sage Pay or Opayo. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Where do I find my Opayo API credentials? In the MyOpayo portal, under the Administrator settings. You need three values: vendor name, integration key, and integration password. Opayo issues one set of API credentials per account, and the password is displayed only once at creation, so if you already integrate with Opayo elsewhere, reuse your existing keys. What about Opayo's test environment? Fully supported. Opayo's test server mirrors the live system without banks attached. Use your test credentials in Shuttle and run the full Twilio flow before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Opayo's standard fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from Opayo to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Opayo on Shuttle: supported channels and setup - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Opayo to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Opayo: Send Branded Checkout Links for UK Merchants ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF capture](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs and outsourced contact centres](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Opayo on Shuttle](/payment-providers/opayo/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Opayo: Send Branded Checkout Links for UK Merchants→](/blog/payment-links-for-opayo/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/parking-enforcement-toll-payments/ --- # Payment Collection for Parking, Enforcement and Toll Operators | Shuttle > Outsourced parking, enforcement and toll operators are payment-collection businesses dressed up as service businesses. # Payment Collection for Parking, Enforcement and Toll Operators By Shuttle Team, May 15, 2026 Outsourced parking, enforcement and toll operators are payment-collection businesses dressed up as service businesses. The patrol officers, the cameras, the call centres, the back-office adjudication teams -- all of it exists to convert an event (an overstayed bay, a missed toll, a contravention) into a paid penalty. For the largest operators -- Marston Holdings, Verra Mobility, APCOA, and the long tail of regional enforcement firms -- the collection volume is enormous. UK councils alone issued over eight million Penalty Charge Notices in the last published year. Toll concessionaires manage tens of millions of journeys, with non-payment recovery layered behind every camera capture. Add in private parking, low-emission zones, congestion charges, bus lane enforcement, moving traffic offences and clamp release fees, and the operator is running a high-volume, multi-channel payment business with a public-sector compliance overlay. This guide is for the operators behind that infrastructure -- and how Shuttle's Payment Layer consolidates the payment side of the operation across letters, SMS, web portals, IVR, agent-assisted voice and AI voice channels. ## The Enforcement Payment Stack Today Most outsourced enforcement operators run something close to this collection mix. Letter and statutory notice. The PCN, NoR, charge certificate or final demand goes out by post. Each contains a pay-by URL, a reference, and a phone number. A meaningful share of the recipient base pays via the URL on the letter. SMS reminder. Where the operator has a mobile number -- from a registration lookup, an online enquiry, or a previous payment -- an SMS reminder is sent before escalation. The SMS typically contains a payment URL or a return-call number. Web portal. The pay-by URL routes to a hosted payment portal -- usually a third-party gateway-skinned page, sometimes a custom build. It handles card payments, sometimes direct debit set-up for payment plans, and increasingly digital wallet (Apple Pay, Google Pay) capture. IVR. Inbound callers who don't want to use the web are routed to an IVR system that reads back the balance and captures card data via DTMF. The IVR is often a legacy on-prem system or a hosted DTMF capture vendor with a separate contract. Call centre agent-assisted. Customers who escalate beyond the IVR -- disputes, payment plans, hardship cases, foreign callers -- talk to an agent. The agent processes the payment manually, with the operator's call centre platform recording the call. Bailiff / enforcement officer in-field. Where escalation goes physical, the officer takes payment in person -- card-present terminal, sometimes a Chip+PIN reader, sometimes a mobile payment link sent to the debtor's phone. Each of those channels has its own payment infrastructure, often with a different vendor. The result is fragmentation: multiple PSPs, multiple PCI compliance surfaces, multiple reconciliation flows, multiple per-channel reporting layers. The operator's finance team spends a disproportionate amount of time reconciling settled receipts to debt records across systems. ## Where the Friction Actually Lives Every operator we've spoken to has the same recurring pain points. PCI scope across multiple touch points. Every channel that touches card data -- the IVR, the web portal, the agent screen, the bailiff terminal -- is in PCI scope. The IVR alone is usually the largest scope item, especially if it's a legacy system with mixed-purpose ports. Reducing PCI scope is a perennial transformation project that never quite finishes. Call centre payment friction. Agents on a call have to navigate a separate payment screen, capture card data into a back-office system, and risk pause-and-resume failures that drop the call. Pause-and-resume is brittle, especially with modern hosted contact centres that don't expose the recording stack directly. The result is a meaningful share of agent-assisted payments fail at the capture point and have to be retried later through a different channel -- sometimes the customer just drops off. Customer drop-off between channels. A customer reads a letter, navigates to the web portal, can't find their reference, calls in, sits in the IVR, escalates to an agent, and finally pays. Every hop is an opportunity to drop. The data shows that payments completed in the same channel as first contact recover materially better than payments that hop channels. Payment plans and instalments. A non-trivial share of penalties end up on a payment plan rather than a one-off payment. Operators need to capture a mandate (direct debit, recurring card-on-file), set up the schedule, dunning rules and adjustment flows for missed instalments. Most legacy IVR and portal stacks weren't built for this. Multi-entity, multi-client reconciliation. Operators settle to dozens or hundreds of underlying authorities -- a county council, a city, a hospital trust, a private landowner. Each client wants its receipts segregated, reconciled and reported separately. The operator's settlement engine has to slice across all of that without bottlenecking the customer-facing payment flow. Foreign drivers and toll cross-border. Toll concessionaires and low-emission zone operators collect from non-domestic drivers -- typically a substantial share of penalty volume in border regions and on high-traffic toll corridors. Different currencies, different cards, different acquiring relationships, different recovery cycles. The operator who consolidates these into a single payment infrastructure -- one PCI surface, one reconciliation engine, one set of channel-agnostic payment objects -- runs a structurally lower-cost collection operation. ## Where Shuttle Fits Shuttle is The Payment Layer for outsourced enforcement, parking and toll operators -- a single integration that powers payments across every channel, with PCI scope held outside the operator's stack. Hosted payment links carry every letter, SMS, email and outbound notification. Operators issue a Shuttle-hosted link for every notice; the link is branded for the client authority (Council X, Toll Operator Y, Private Operator Z); the page handles card, wallet and account-to-account payment in one flow. Reconciliation flows back to the operator's debt management system via webhook. [Voice Checkout](/voice-checkout/) replaces legacy IVR card capture and the brittle pause-and-resume patterns inside the call centre. Shuttle's voice capture runs on Twilio Pay today (voice requires being a Twilio customer). When it is time to pay, the card is captured in a secure PCI DSS Level 1 flow that never enters the agent's audio path or the contact centre's recording layer, so card data stays out of the operator's environment. There is no native integration with a CCaaS or AI voice platform: Shuttle ships the link interfaces plus PCI-compliant capture, IVR and APIs, and the operator builds the agent-side interface for its own setup. One honest caveat: full-call presence is not yet turnkey; returning the caller to the same agent works today when the operator builds the return route in Twilio and passes a conversation ID. Shuttle works with Twilio today, and any carrier coming soon. AI voice agent collection. For operators running an AI voice agent on routine enquiries -- "what's my balance?", "I want to pay my PCN", "set me up on a payment plan" -- payment can be captured securely at the point of payment rather than handing off to a human. The operator builds its own agent interface against Shuttle's APIs; a packaged platform integration is available as a paid project. See PCI-compliant payments for AI voice agents for the architecture. Recurring mandates support payment plans and instalments out of the box, with direct debit (Bacs, SEPA) and card-on-file across the same control plane. Schedule logic, dunning, retry policy and adjustment for partial payments live in the operator's debt system; Shuttle executes. Multi-PSP routing lets operators keep existing acquirer relationships per client. UK acquirer for domestic; multi-currency acquirer for foreign drivers; a different provider for specific authority contracts. One integration, many gateways -- see 40+ supported PSPs. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. Branded for each client authority. A hosted payment page can be reskinned per authority, so the resident sees the council's branding (or the toll operator's, or the landowner's), not Shuttle's. Operators run a single technical stack while presenting dozens of customer-facing brands. ## Why This Reduces Operating Cost Three lines of cost compress when payment infrastructure consolidates. PCI compliance overhead. With card data flowing through Shuttle's PCI DSS Level 1 environment and never landing in the operator's telephony, recording, IVR or web infrastructure, the scope of the operator's annual audit shrinks dramatically. Less audit prep, fewer remediation findings, lower QSA hours. For operators running multiple legacy IVR systems, the saving compounds. Vendor sprawl. A typical operator runs a payment gateway for the web portal, a DTMF capture vendor for the IVR, a different gateway for the call centre, a separate mandate vendor for direct debit, and a card-present provider for officers in-field. Consolidating onto one payment layer eliminates the contract overhead and the integration drift between systems. Reconciliation engineering. When every channel writes to the same payment objects, reconciliation to the underlying debt records becomes one flow instead of five. Finance teams stop maintaining spreadsheets and bespoke ETL between vendor reports. The recovery rate lift is the other side of the same coin. Customers who can complete payment in the same channel they first engaged in -- letter to portal, SMS to link, call to voice agent -- pay more often than customers forced to hop channels. ## Sector-Specific Notes Civil parking enforcement. Local authority and outsourced council enforcement work. Public-sector compliance overlay (data protection, accessibility, dispute and appeal handling). Mandatory acceptance channels (cash equivalents, accessibility for disabled users). Plan support for "discount window" payment within 14 days. Private parking and landowner enforcement. Trade-body codes of practice (BPA, IPC, etc.), distinct procedural rules, higher dispute volumes, more variable customer profiles. Branded payment pages per landowner. Toll concessions. Higher daily transaction volumes, multi-currency, cross-border reciprocity arrangements, transponder-vs-camera-vs-licence-plate billing models. Real-time top-up flows for prepaid accounts. Low-emission and clean-air zone enforcement. Camera-led, high-volume, often centralised at a city or regional scale. Daily charge collection plus penalty escalation for non-payment. Bus lane and moving-traffic offence enforcement. Similar profile to parking civil enforcement but with different statutory frameworks. Often delivered alongside parking enforcement on the same operator contract. The same payment layer supports all of them -- one integration, branding and provider selection per client. ## What Implementation Looks Like A representative deployment for an outsourced enforcement operator looks like this. Phase 1 -- Web and letter consolidation. All hosted payment URLs across letters, emails and SMS reminders route to Shuttle-hosted, per-client branded payment pages. The existing payment gateway sits behind Shuttle as one of the routing destinations. The web portal drops out of PCI scope: the card is entered on the hosted payment page. Phase 2 -- Call centre and IVR. Inbound payment calls move to secure capture via Twilio Pay (the operator becomes a Twilio customer for voice), so card data stays off the call audio and out of the recording layer. The contact centre platform stays the same; the operator builds the agent-side trigger against Shuttle's APIs, and a packaged integration is available as a paid project. Phase 3 -- AI voice agent. Routine balance queries and payment-plan set-ups can route to an AI voice agent, with payment captured securely at the point of payment. The operator builds its own agent interface; escalation rules send dispute, hardship and complex cases to human agents. Phase 4 -- Multi-PSP and cross-border. Foreign-driver acquiring is routed via a multi-currency PSP. Client-authority-specific acquirers are added where the underlying contract demands it. Officers in-field collect via mobile payment links sent from the operator's CMS. Each phase delivers cost reduction and recovery uplift independently. Operators don't have to wait for a multi-year transformation to see returns -- phase 1 alone typically removes the largest PCI scope item from the audit. ## Related Reading - Voice Payments: The Complete Guide -- covering DTMF, masking, AI voice and agent-assisted collection - PCI-Compliant Payments for Contact Centres -- the full hub covering 20+ CCaaS platforms - PCI-Compliant Payments for AI Voice Agents -- the architecture pattern for AI agent payments - Secure Payment Collection for Debt and Enforcement Agencies -- the closest-adjacent guide on the collection side - Payment Collection for BPOs -- for operators running enforcement collection as an outsourced service - Multi-Channel Payment Collection -- the framework for consolidating payments across letter, SMS, voice and portal Shuttle is The Payment Layer for parking, civil enforcement and toll operators. One integration powering hosted payment pages, voice payments, AI voice agents and direct debit mandates -- branded per client authority, routed to any PSP. PCI DSS Level 1, ISO 27001, and SOC 2 certified. [See how it works for platforms](/platforms/) or [book a discovery call](/discovery/). ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI-compliant payments for AI voice agents](/guides/ai-voice-agent-pci-payments/) - [40+ supported PSPs](/payment-providers/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [PCI-Compliant Payments for AI Voice Agents](/guides/ai-voice-agent-pci-payments/) - [Secure Payment Collection for Debt and Enforcement Agencies](/guides/secure-payment-collection-debt-agencies/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Multi-Channel Payment Collection](/guides/multi-channel-payment-collection/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/parloa-payments/ --- # Parloa Payments: Multi-PSP Payment Capture for AI Contact Centre Agents | Shuttle > Parloa is an AI Agent Management Platform for contact centres. Enterprise teams in financial services, utilities, retail, and healthcare use it to... # Parloa Payments: Multi-PSP Payment Capture for AI Contact Centre Agents By Shuttle Team, May 31, 2026 Parloa is an AI Agent Management Platform for contact centres. Enterprise teams in financial services, utilities, retail, and healthcare use it to automate voice and chat conversations end to end, with AI agents that resolve queries, qualify callers, and complete transactions without an agent in the loop. When a conversation needs a payment, Parloa has a native Payment Skill. Mid-call, the AI agent hands off to Parloa's own PCI-DSS-compliant payment subsystem, a deterministic system that sits separate from the language model. The caller enters their card on the keypad via DTMF, the transaction is processed, and the AI resumes the conversation. Parloa says it integrates with existing payment systems so businesses can route transactions through their preferred providers. So this is not a question of whether Parloa can take payments. It can. The question is when a dedicated, multi-PSP payment layer earns its place alongside it, and how the two compare. This guide covers what Parloa's Payment Skill gives you, when teams reach for a dedicated payment layer like Shuttle, and how Shuttle adds explicit multi-gateway breadth and PCI DSS Level 1 assurance across any voice or chat stack. ## Parloa's Payment Skill: What You Get Parloa's native payment capability is genuinely useful, and for many deployments it is enough: - DTMF card capture mid-conversation. The AI agent pauses, hands the caller to a deterministic payment flow, and the caller keys in their card details on the phone keypad rather than speaking them aloud. - A subsystem separate from the LLM. Card handling runs in a dedicated payment system, not through the conversational model, which is the right architecture for keeping sensitive data out of AI prompts and logs. - PCI-DSS-compliant processing. Parloa advertises a PCI-DSS-compliant payment system, so card data is handled in a controlled environment rather than passing through the open conversation. - Routing to your preferred providers. Parloa integrates with existing payment systems, so transactions can flow through the processor you already use rather than a single mandated PSP. If you run one contact centre, one payment provider, and one channel, the native Payment Skill may cover everything you need. The rest of this guide is about the cases where a dedicated payment layer adds something the native skill is not designed to. ## When You Need a Dedicated Payment Layer A separate payment layer like Shuttle becomes worthwhile when payment is a first-class concern in its own right, not just a step inside one platform. Common triggers: - Explicit gateway breadth. You want a documented list of 30+ supported gateways and the freedom to bring your own, rather than relying on whatever integrations are wired up case by case. - Per-client or per-tenant routing. Agencies, BPOs, and platforms that serve many merchants need each client's transactions to settle into that client's own processor and account, with routing decided per tenant. - Enterprise PSP mandates. Larger organisations are often required to process through a specific acquirer or gateway. A payment layer that supports that provider out of the box removes friction. - Stated PCI DSS Level 1 assurance. Procurement and security teams frequently ask for a named certification level. Shuttle is a PCI DSS Level 1 certified Service Provider, which is the highest level and the one large buyers tend to require. - One layer across every stack and channel. If you also run other voice agents, chat agents, IVR, or live agents, a payment layer that works across all of them gives you one integration and one reconciliation flow instead of separate setups per tool. ## How Shuttle Adds Multi-PSP Payment Capture Shuttle is a dedicated payment layer. There is no native Parloa integration: the handoff is API-driven and built on Shuttle's Twilio-based capture, so you must be a Twilio customer, and your application code triggers the handoff at the point of payment. Here is the flow: - Trigger. Your application reaches the payment step in the conversation and invokes Shuttle's secure capture. - Secure capture. At the point of payment, the card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay, with Shuttle as the certified connector). The caller enters their card on the keypad. Digits are captured in Shuttle's certified environment, never spoken aloud and never exposed to the AI model or your application. - Route to your gateway. Shuttle routes the transaction to your chosen processor from 30+ supported gateways, selected globally or per client, per tenant, or per merchant. - Confirm. The result returns to your application, which confirms the outcome to the caller. - Reconcile. Funds settle into your own merchant accounts, and the same layer powers payments across other channels you run. A few honest caveats to set expectations. The secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Parloa agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes with context. Parloa's own native Payment Skill, which keeps the caller inside Parloa with no return-leg wiring, remains the lower-effort fit when zero orchestration matters most. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native Parloa integration is possible only as a paid project. ## Multi-PSP Support Shuttle connects to 30+ payment gateways, so you process through the provider you already use rather than switching to a single mandated one: - Checkout.com Bring your own gateway, keep your existing rates and acquirer relationships, and route different clients or business units to different providers from one integration. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest assurance level under the standard. Card data is captured and processed inside Shuttle's PCI-scoped environment. It never touches your Parloa agent, your application servers, your conversation logs, or your CRM. That separation keeps sensitive cardholder data out of your systems entirely. The practical benefit is PCI scope reduction. Because raw card data never enters your environment, many businesses can qualify for the lighter SAQ-A self-assessment rather than the far heavier SAQ-D that applies when cardholder data flows through your own systems. That difference can mean weeks of audit work saved and a materially smaller compliance surface. ## Beyond Voice: Payment Links Payment links are the turnkey path. Where a caller would rather pay later, or a chat conversation needs a checkout, Shuttle can send a hosted payment link by SMS or email, including mid-call. The customer pays on a secure page in their own time, and the result reconciles back through the same layer. Links work even with gateways that do not support voice capture. This means one integration covers both the secure in-call capture and asynchronous link-based payments, across voice and chat, with no second system to maintain. ## Use Cases ### Bill-Pay and Collections Utilities, financial services, and healthcare callers settle balances and arrears directly in the conversation. Outstanding amounts can be looked up, payment plans confirmed, and cards captured by DTMF, with transactions routed to the right acquirer per business unit. ### Outbound Sales Outbound AI agents that close renewals, upsells, or one-off purchases can take payment at the moment of agreement instead of handing off, which protects conversion on the call where intent is highest. ### Order Taking Retail and hospitality agents handle ordering and reservations and collect payment or deposits in the same flow, with card data kept out of order-management systems. ### Customer Support Payments Support conversations that surface a chargeable action, an upgrade, an excess, or a service fee, can collect payment inline without transferring the caller to a separate line or a human agent. ## FAQ Does Parloa take payments natively? Yes. Parloa has a native Payment Skill: the AI hands off mid-conversation to a PCI-DSS-compliant subsystem that captures the card via DTMF, then resumes the call. It integrates with existing payment systems so you can route to your preferred providers. Does Shuttle have a native Parloa integration? No. There is no native Parloa integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native Parloa integration is possible only as a paid project. Parloa's own Payment Skill keeps the caller inside Parloa with no return-leg wiring; with Shuttle, you return the caller to the same agent by programming the return route in Twilio and passing a conversation ID. Does this require Twilio? Yes, today. Shuttle's secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Then why add Shuttle? For explicit, documented breadth and assurance. Shuttle gives you 30+ named gateways with bring-your-own-gateway support, per-client and per-tenant routing for agencies and BPOs, a stated PCI DSS Level 1 certification, and one payment layer that works across channels. Which payment gateways does Shuttle support? 30+, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. You can see the full list and bring your own. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture. Could we just build multi-PSP routing ourselves? You could, but maintaining PCI-scoped capture, multiple gateway integrations, per-tenant routing, and Level 1 certification is a significant ongoing engineering and audit cost. Shuttle is $0.20 per successful transaction for voice, with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). Does Shuttle handle outbound payments? Yes. Outbound Parloa agents can capture payment in-call via the secure handoff, or send a hosted payment link by SMS for the customer to pay later, all through the same layer. ## Related Reading - Contact Centre Payments: how payment capture works across contact-centre platforms. - AI Voice Agent PCI Payments: the compliance model for taking cards through AI voice agents. - The Payment Layer for AI Agents: why a dedicated layer sits beneath any agent stack. - Sierra Payments: adding multi-PSP capture to Sierra AI agents. - Cognigy Payments: payment capture for Cognigy voice and chat agents. ## Add Payments to Your Parloa Agents Keep Parloa's native Payment Skill where it fits, and add a dedicated layer where you need gateway breadth, per-client routing, and Level 1 assurance across every channel. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [PCI DSS Level 1](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [payment link](/platforms/voice-checkout/) - [see the full list](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Sierra Payments](/guides/sierra-payments/) - [Cognigy Payments](/guides/cognigy-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/pay-now-button-invoices/ --- # Pay Now Button for Invoices: The B2B Guide | Shuttle > A Pay Now button on a B2B invoice does two things at once. It signals to your client that you're modern enough to take card or bank payments -- and it... # Pay Now Button for Invoices: The B2B Guide By Shuttle Team, May 1, 2026 A Pay Now button on a B2B invoice does two things at once. It signals to your client that you're modern enough to take card or bank payments -- and it removes every excuse for a 45-day payment cycle. For most B2B businesses, the bottleneck on getting paid isn't whether the client can pay. It's whether they remember to schedule a transfer in the gap between receiving the invoice and the work moving onto something else. A Pay Now button collapses that gap. The decision to pay and the act of paying happen in the same moment, on the same screen. This guide covers how to add a Pay Now button to a B2B branded invoice -- what the technical options are, how to keep your branding intact, which payment methods to support, and how to set it up without breaking your accounting workflow. ## What Is a Pay Now Button on an Invoice? A Pay Now button is a clickable element on an invoice -- usually rendered as a contrasting CTA in the invoice email, the PDF, or the hosted invoice page -- that takes the recipient directly to a checkout page pre-filled with the invoice amount and reference. One tap, one card or bank transfer, payment confirmed. The category is closely related to invoice payment links -- the underlying mechanic is the same -- but the framing matters. A "payment link" is an SMS-friendly URL. A "Pay Now button" is a styled CTA inside a branded document. For B2B, where invoice presentation reinforces your professionalism, the button framing is what most clients respond to. ## Why It Matters for B2B Specifically B2B invoices have three things in common that make Pay Now buttons disproportionately effective: 1. The invoice values are higher. A 30-day delay on a £20,000 invoice represents real working capital. Even small reductions in DSO compound across a year of invoicing. 2. The decision-maker isn't always the payer. The person who approves the invoice often hands it to finance to actually pay. A Pay Now button on the approval email lets them just pay it themselves -- which they often will, especially for sub-£10,000 amounts. 3. The buying experience reflects on your business. If you're a £200/day consultant invoicing a £5,000 retainer, the difference between "bank transfer to sort code 12-34-56" and a clean Pay Now button changes how the client perceives the relationship. The button isn't just a payment mechanism -- it's a credibility signal. Studies on B2B invoice conversion consistently show 2-3x faster payment and 40-60% reduction in late payments when invoices include a Pay Now button vs. bank-transfer-only invoices. ## How to Add a Pay Now Button to a B2B Invoice There are three workable patterns, ordered from simplest to most polished. ### Pattern 1: Native Pay Now in your accounting software Most accounting platforms now ship a Pay Now button as a feature of their hosted invoice templates. The customer receives an email with the invoice attached; the email itself contains a "Pay Now" button that takes them to the platform's hosted checkout. - QuickBooks -- see the QuickBooks payment links guide - Xero -- Pay Now via Stripe, GoCardless, or PayPal - HubSpot -- see the HubSpot payment links guide - FreshBooks -- Pay Now via FreshBooks Payments - Sage Business Cloud -- Pay Now via Stripe, GoCardless This is the right starting point if your invoice volume is moderate and you don't need brand control beyond your logo and colours. ### Pattern 2: Custom branded Pay Now with a payment link API For agencies, consultancies, and B2B sellers who care about presentation, the next step up is generating Pay Now buttons via a payment link provider's API and embedding them in your own branded invoice templates. - Your invoice generation tool calls the payment link API with amount, reference, customer email - The API returns a unique link tied to that invoice - Your invoice template renders a "Pay Now" button styled to your brand, pointing at that link - Recipient clicks → branded checkout page → pays → webhook fires back to your accounting tool This pattern lets you control every pixel of the invoice and the checkout -- your logo on the invoice, your logo on the checkout, your domain on the URL -- without giving up automated reconciliation. ### Pattern 3: Hosted invoice + Pay Now button The most polished option: instead of attaching a PDF, you send the client a link to a hosted invoice page (on your domain or your provider's), with the Pay Now button rendered directly on the page. The client lands on a fully branded invoice experience, sees the line items, sees a clear CTA, taps to pay. Hosted invoices typically convert faster than PDF invoices because there's no extra step (open PDF, find link, tap link). They also work better on mobile -- the most common device for B2B email reading. This pattern is offered by a small number of payment link providers and most modern invoicing platforms (Stripe Invoicing, Square Invoices, GoCardless via partners). ## Branding the Pay Now Button (Without Breaking the Trust Signal) For B2B invoices, branding control on both ends -- the invoice and the checkout -- affects whether clients pay quickly or stop to investigate. The minimum brand requirements: On the invoice: Your logo, your colour scheme, your business name. The Pay Now button should look like part of your invoice, not a third-party widget bolted on. On the checkout page: Your logo, your business name (not "[Provider] hosted by [Provider]"), and ideally your domain in the URL bar. Clients who see "stripe.com" or "square.com" sometimes hesitate; clients who see your own subdomain ("pay.yourbusiness.com") rarely do. On the receipt: The same branding carried through. The auto-generated receipt is the last thing the client sees, and it's the one most likely to surface in their finance team's records months later. White-label payment links are how you achieve all three. Without white-label support, you're stuck with the provider's branding showing through somewhere in the flow. ## Payment Methods to Support on B2B Invoices Cards are the floor, not the ceiling. For B2B Pay Now buttons, the payment method mix matters more than for retail. Card payments. Universally accepted, fast settlement, but the highest fees (typically 2.5-2.9% in the UK on B2B card transactions). Best for invoices under £5,000 where convenience trumps fees. Open banking / pay-by-bank. Direct bank-to-bank transfer from inside the Pay Now flow. Costs 0.2-0.5% in the UK. Materially better economics for invoices over £2,000 -- and increasingly familiar to B2B buyers. BACS / SEPA Direct Debit. For recurring B2B retainers or instalment plans. Lowest cost (~£0.20-0.50 per transaction), but takes 3 working days to clear. Best added as an option alongside cards. Apple Pay / Google Pay. Surprisingly underused on B2B invoices. Most B2B clients pay from a mobile device when they pay personally; wallet pay collapses the friction further. Easy to enable on most providers. The right answer for most B2B businesses is to surface 2-3 methods on the Pay Now flow -- card by default, open banking promoted for high-value invoices, BACS as a low-friction option for retainers. A multi-method Pay Now button typically lifts payment rate by another 15-25% over card-only. ## Reconciliation: Don't Break the Accounting Workflow The fastest way to lose the benefits of a Pay Now button is to create more reconciliation work than you save. The default reconciliation patterns: - Webhook to accounting platform -- payment fires a webhook, the invoice is auto-marked as paid, the journal entry is created. Zero manual work. This is the bar. - Reference field on the transaction -- invoice number is stamped on the payment, settlement report can be matched against your invoice list. Manual but predictable. - Manual lookup -- payment arrives, someone in finance figures out which invoice it relates to. Avoid. If your provider doesn't support webhook reconciliation back to your accounting tool of choice, the Pay Now button isn't worth it. The provider should integrate with QuickBooks, Xero, Sage, NetSuite, HubSpot, or whatever you're using -- directly or via Zapier / Make. For the platform-vendor side of this pattern -- where the ERP itself ships embedded payments -- see Embedded Payments for ERP Platforms. ## What to Avoid Three patterns that look helpful but create more friction than they remove: Generic "Pay" buttons that link to a non-branded checkout. Defeats the trust signal. If the checkout looks like a phishing attempt, B2B finance teams will ignore it. Single-payment-method buttons (card-only). Forces high-fee cards on high-value B2B invoices. Costs you margin and conversion. Manual link generation per invoice. Fine at 5 invoices a month, unscalable at 50. Pick a provider with API generation from day one even if you start manual. ## Frequently Asked Questions How do I add a Pay Now button to my invoices? The simplest path is to enable Pay Now in your accounting platform (QuickBooks, Xero, HubSpot all support it natively). For more control over branding and payment methods, generate payment links via API from a payment link provider and embed them in your invoice template. What's the best Pay Now button for B2B invoices? For B2B specifically, you want white-label branding, multiple payment methods (card + open banking + BACS), and webhook reconciliation back to your accounting tool. Multi-PSP providers tend to win on these criteria over single-processor solutions. Does Stripe have a Pay Now button for invoices? Yes -- Stripe Invoicing includes a Pay Now button by default on its hosted invoice pages. It's a clean experience but tied to Stripe's pricing and Stripe's branding on the checkout page. How much does a Pay Now button cost? The button itself is usually free; you pay per transaction at whatever rate your payment provider charges. UK card rates typically run 2.5-2.9%; open banking 0.2-0.5%; BACS 0.2% or fixed. Can I add a Pay Now button to a PDF invoice? Yes -- most PDF generators support clickable links. The button is rendered as a styled image with a hyperlink to your payment URL. Quality varies; hosted invoices generally convert better than PDFs but PDFs work for clients who require document-based delivery. ## Related Reading - Invoice Payment Links: Complete Guide - Best Payment Link Providers 2026 - White-Label Payment Links - QuickBooks Payment Links Guide - HubSpot Payment Links Guide ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Give Customers More Ways to Pay Your Invoices ### Dropping some knowledge on Buy Now Pay Later ### Invoice Payment Links: How to Get Paid Faster on Every Invoice ### QuickBooks ACH Payments: Setup, Fees & Tips ### Improve your cash flow. Stop waiting to get your invoices paid ### The best orders were always conversations. Now AI can have them, and take the payment. ## Links - [invoice payment links](/guides/invoice-payment-links/) - [QuickBooks payment links guide](/guides/quickbooks-payment-links/) - [HubSpot payment links guide](/guides/hubspot-payment-links/) - [payment link provider's](/guides/best-payment-link-providers/) - [White-label payment links](/guides/white-label-payment-links/) - [Embedded Payments for ERP Platforms](/guides/payments-for-erp-platforms/) - [payment link provider](/guides/best-payment-link-providers/) - [Invoice Payment Links: Complete Guide](/guides/invoice-payment-links/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [White-Label Payment Links](/guides/white-label-payment-links/) - [QuickBooks Payment Links Guide](/guides/quickbooks-payment-links/) - [HubSpot Payment Links Guide](/guides/hubspot-payment-links/) - [Book a Call](/discovery/) - [BlogHow to Give Customers More Ways to Pay Your Invoices→](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [BlogDropping some knowledge on Buy Now Pay Later→](/blog/dropping-some-knowledge-on-buy-now-pay-later/) - [BlogInvoice Payment Links: How to Get Paid Faster on Every Invoice→](/blog/payment-links-on-invoices-the-game-changing-strategy-your-business-needs/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogImprove your cash flow. Stop waiting to get your invoices paid→](/blog/improve-your-cash-flow-stop-waiting-to-get-your-invoices-paid/) - [BlogThe best orders were always conversations. Now AI can have them, and take the payment.→](/blog/best-orders-were-always-conversations/) --- URL: https://www.shuttleglobal.com/guides/payfac-regret/ --- # PayFac Regret: Why Platforms Are Unwinding Their PayFac Status | Shuttle > The Promise vs the Reality Five years ago, the pitch was irresistible. Become a Payment Facilitator. Own the merchant experience. Control the economics. # PayFac Regret: Why Platforms Are Unwinding Their PayFac Status By Shuttle Team, March 9, 2026 ## The Promise vs the Reality Five years ago, the pitch was irresistible. Become a Payment Facilitator. Own the merchant experience. Control the economics. Capture revenue share. Build a payments moat around your platform. Software platforms across every vertical bought in. The logic was sound: if your platform already controlled the merchant's workflow, why not control their payments too? The revenue was attractive -- 10-30 basis points on every transaction, compounding as your merchants grew. What the pitch left out was the operational reality. As The Financial Revolutionist put it: "The PayFac era is ending for software platforms." And Nuvei's analysis was blunter: "Everyone embraced the PayFac concept. Then the bubble burst." The platforms that became PayFacs are now discovering what payment companies have known for decades: processing payments on behalf of other businesses is a regulated, capital-intensive, operationally complex undertaking that never stops demanding attention. Many platforms now find themselves maintaining a complex operating model to achieve outcomes that no longer require it. ## What Becoming a PayFac Actually Means The PayFac model sounds simple in a pitch deck. In practice, it means your platform becomes the merchant of record -- legally responsible for every payment processed by every merchant on your platform. That responsibility comes with obligations: ### Merchant Underwriting Every merchant on your platform must be underwritten before they can process payments. You need to assess their business type, financial health, risk profile, and regulatory standing. This isn't a one-time check -- ongoing monitoring is required. High-risk merchants need enhanced due diligence. Suspicious activity triggers investigation obligations. Building an underwriting function requires compliance expertise, risk scoring models, and ongoing monitoring systems. Most platforms underestimate this: it's not a feature you build once. It's an operation you run permanently. ### KYC/AML Compliance Know Your Customer and Anti-Money Laundering regulations require identity verification, beneficial ownership identification, sanctions screening, and ongoing transaction monitoring. The regulatory landscape varies by country and changes frequently. Non-compliance carries serious consequences: fines, enforcement actions, and potential loss of payment processing capability. Platforms that become PayFacs are directly responsible for KYC/AML compliance across their entire merchant base. ### Fraud Monitoring As the merchant of record, you're liable for fraud losses. Not just your platform's fraud -- your merchants' fraud. If a merchant on your platform is running a scam, you bear the financial liability for chargebacks and the reputational consequences with card networks. This requires real-time transaction monitoring, fraud scoring, velocity checks, and a fraud operations team that can investigate and act on alerts. It's a 24/7 operation. ### Chargeback Liability When a cardholder disputes a transaction processed through your platform, you're in the middle. As the PayFac, you manage the dispute process, provide evidence, and absorb losses when disputes are lost. Excessive chargeback rates (above 1% for Visa, 1.5% for Mastercard) trigger monitoring programmes with escalating consequences. ### Regulatory Reporting PayFacs must comply with reporting requirements to card networks, acquiring banks, and financial regulators. Transaction reporting, suspicious activity reporting, and compliance attestation are ongoing obligations that require dedicated staff and systems. ### Capital Reserves Card networks and acquiring banks require PayFacs to maintain reserve funds -- capital set aside to cover potential losses from merchant fraud, chargebacks, and operational failures. These reserves tie up cash that could otherwise fund growth. ## The Real Cost The total cost of becoming a PayFac breaks down across three phases: ### Phase 1: Setup (6-12 months) Cost Range PCI DSS Level 1 certification £50,000-£500,000 Merchant management systems £200,000-£500,000 Underwriting and onboarding platform £100,000-£250,000 Legal and regulatory setup £50,000-£150,000 Acquiring bank sponsorship £50,000-£200,000 Total setup £450,000-£1,600,000 ### Phase 2: Go-Live (ongoing) Annual Cost Compliance team (3-5 people minimum) £250,000-£500,000 PCI DSS maintenance £100,000-£200,000 Fraud monitoring and operations Technology maintenance Regulatory and legal £50,000-£100,000 Annual operating cost £600,000-£1,250,000 ### Phase 3: The Hidden Costs These are the costs that don't appear in any budget: Opportunity cost. Every engineer working on payment compliance, merchant underwriting, or chargeback management is an engineer NOT working on your core product. For platforms where payments are infrastructure rather than product, this is the most expensive cost of all. Regulatory risk. Financial regulation changes. PCI standards evolve. Card network rules get updated. Each change potentially requires engineering work, process changes, and compliance re-validation. These changes arrive on the regulator's timeline, not yours. Board-level distraction. When your platform is a PayFac, payment compliance becomes a board-level concern. Audit committee reviews, regulatory correspondence, and compliance attestations consume executive attention that should be focused on growth. ## Why Platforms Did It The PayFac model gained momentum for legitimate reasons: Revenue capture. Processing payments generates 10-30 basis points on every transaction. At scale, that's meaningful revenue. Merchant experience. Platforms wanted to control the full merchant journey -- onboarding, checkout, settlement -- rather than handing merchants off to a third-party PSP. Competitive differentiation. In 2018-2022, offering embedded payments was a differentiator. Platforms without payments lost deals to platforms with payments. Stripe Connect's influence. Stripe Connect made it possible for platforms to embed payments with relatively low initial investment, creating the impression that PayFac-like capabilities were accessible. Many platforms started with Connect and then pursued full PayFac status for better economics or more control. ## Why the Calculus Changed Three shifts have undermined the PayFac value proposition: ### 1. Processors Modernised Distribution PSPs have dramatically improved their platform and marketplace offerings. The capabilities that once required PayFac status -- white-label checkout, merchant onboarding, split payments, custom settlement -- are now available through managed models that don't require the platform to become a regulated entity. The technology gap that justified becoming a PayFac in 2019 has largely closed. ### 2. Managed Models Match the Economics The revenue premium for being a PayFac has narrowed. Managed PayFac services, PayFac-as-a-Service providers, and PSP-neutral payment layers offer revenue share models that approach full PayFac economics -- without the compliance burden, operational overhead, or capital requirements. When the revenue difference between "own it" and "use a managed model" narrows to a few basis points, the operational cost of owning it no longer pencils out. ### 3. Compliance Costs Increased PCI DSS 4.0 raised the compliance bar. KYC/AML requirements have tightened across jurisdictions. Card network rules have become more stringent. The cost of maintaining PayFac status has increased materially since 2020, while the revenue premium has decreased. ## Signs of PayFac Regret These patterns signal that a platform's PayFac status has become a liability rather than an asset: Your compliance team is growing faster than your product team. When headcount in compliance, risk, and payment operations outpaces hiring in product and engineering, your organisational priorities have shifted away from your core business. Regulatory changes require board-level attention. If PCI DSS updates, card network rule changes, or KYC regulation shifts are consuming executive and board bandwidth, you're operating a financial services function -- not a software platform. Merchant onboarding is your biggest bottleneck. If the time to onboard a new merchant is measured in weeks (due to underwriting, compliance checks, and risk review) rather than minutes, your PayFac infrastructure is slowing your growth rather than enabling it. Engineering is spending more time on payment compliance than product features. Track the ratio. If payment-related work -- compliance updates, audit preparation, fraud system maintenance -- exceeds 20% of engineering capacity, the opportunity cost is severe. You're carrying risk you didn't sign up for. A merchant fraud event, a compliance breach, or a card network fine can cost hundreds of thousands of pounds and months of management attention. If these risks keep you up at night, you're in the wrong business. ## The Alternatives Platforms unwinding PayFac status -- or choosing not to pursue it in the first place -- have three primary alternatives: ### Managed PayFac A sponsor bank or payment processor handles the regulated functions (underwriting, compliance, settlement) while the platform maintains a white-label experience. The platform offers payments without bearing regulatory burden. Pros: Reduced compliance burden, faster merchant onboarding. Cons: Less economic control, dependency on the managed PayFac provider. ### PayFac-as-a-Service Third-party platforms provide the infrastructure for PayFac-like capabilities without requiring the platform to obtain its own registration. The service provider handles the regulated layer; the platform handles the merchant experience. Pros: PayFac economics without PayFac regulation. Cons: Still typically limited to a single payment provider. ### PSP-Neutral Payment Layer A payment layer sits between the platform and multiple PSPs, providing white-label checkout, merchant management, and multi-PSP routing without requiring the platform to handle card data or maintain PayFac registration. Pros: Multi-PSP flexibility, limited PCI scope, a lighter compliance load. Cons: Platform doesn't own the payment flow at the infrastructure level. Shuttle provides the third option. Platforms integrate once and access 40+ PSPs through a single layer. Merchant onboarding is white-label. PCI compliance is handled at the layer. The platform monetises payments -- without underwriting merchants, managing chargebacks, maintaining PCI certification, or hiring a compliance team. The result is the outcome platforms originally wanted from PayFac -- payment revenue, merchant control, embedded experience -- without the operating model they didn't. ## The Trend Is Clear The PayFac model made sense when it was the only path to embedded payment economics. It isn't anymore. Platforms that became PayFacs in 2019-2022 are reassessing the cost-benefit as compliance costs rise and managed alternatives improve. New platforms are increasingly choosing not to pursue PayFac status at all, opting for managed models that deliver comparable economics with a fraction of the operational burden. The question for platform leaders isn't "should we become a PayFac?" It's "do we want to be a payment company?" For platforms whose core product is software -- not payments -- the answer is almost always no. And for those that already made the PayFac decision and are feeling the weight of it: unwinding is possible. The alternatives exist. The economics work. And your engineering team will thank you. ## Further Reading - Embedded Payments Without Becoming a PayFac - PayFac Alternatives - Payment Layer Explained - What Is Embedded Payments? ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### PayFac Alternatives for Platforms ### Is reselling payments and becoming a PayFac right for my SaaS? ### Shuttle vs PayFac-as-a-Service (Payrix, Finix) ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Links - [becoming a PayFac](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [payments are infrastructure rather than product](/guides/get-payments-off-your-roadmap/) - [white-label checkout, merchant management, and multi-PSP routing](/guides/embedded-payments-without-payfac/) - [PCI compliance is handled at the layer](/guides/pci-compliance-cost-platforms/) - [alternatives](/alternatives/payfac/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [PayFac Alternatives](/alternatives/payfac/) - [Payment Layer Explained](/guides/payment-layer-explained/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [Book a Call](/discovery/) - [AlternativePayFac Alternatives for Platforms→](/alternatives/payfac/) - [BlogIs reselling payments and becoming a PayFac right for my SaaS?→](/blog/is-reselling-payments-and-becoming-a-payfac-right-for-my-saas/) - [ComparisonShuttle vs PayFac-as-a-Service (Payrix, Finix)→](/vs/payrix-finix/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) --- URL: https://www.shuttleglobal.com/guides/payment-collection-for-bpos/ --- # Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope | Shuttle > The Multi-Client Payment Problem You run a BPO or outsourced contact centre. You handle calls, chat, email -- maybe AI agents -- for a portfolio of clients. # Payment Collection for BPOs: Multiple Clients, Multiple PSPs, Limited PCI Scope By Shuttle Team, February 22, 2026 ## The Multi-Client Payment Problem You run a BPO or outsourced contact centre. You handle calls, chat, email -- maybe AI agents -- for a portfolio of clients. Some of those clients need you to collect payments on their behalf. Here's where it gets complicated. Client A processes through Worldpay. Client B uses Stripe. Client C has a Braintree account they negotiated rates on three years ago and aren't switching. Client D is a debt collection agency that's contractually required to use a specific processor mandated by their creditors. Each client expects their branding on the payment experience. Each client has different compliance requirements. Each client's payments need to settle into their own merchant account. And your agents -- whether human or AI -- need to handle all of this from a single interface, without seeing card data, without expanding your PCI scope, and without logging into four different payment dashboards. This is the multi-client payment problem. It's unique to BPOs and outsourcers, and almost no payment solution is designed for it. ## Why Standard Solutions Don't Work ### Single-Gateway DTMF Solutions The incumbent single-gateway DTMF providers in the contact centre space solve the PCI compliance piece well. They mask DTMF tones so agents can't hear card data. Recordings are clean. The call centre is de-scoped. But they're built for single-merchant environments. An insurance company with one PSP and one brand. A utility company with a direct Worldpay integration. When a BPO tries to use these solutions across a multi-client portfolio, the problems multiply: - PSP configuration per client. Most DTMF solutions support a limited set of gateways. Each client's PSP needs separate configuration, often requiring professional services involvement. - No multi-tenant architecture. The solution isn't designed to route Client A's payments through Worldpay and Client B's through Stripe from the same agent session. You end up with separate configurations, separate dashboards, separate reporting. - Per-seat pricing is common. Many single-gateway DTMF providers charge per agent seat. For a BPO running 200 agents across 15 clients, a seat-based fee is borne entirely by the BPO -- and it doesn't scale down when volume drops. A quiet month costs the same as a peak month. - No white-label. The payment experience carries the DTMF provider's branding, not your client's. For BPOs that position payment collection as a premium capability, that undermines the value proposition. ### Logging Into Client Portals Smaller call answering services often handle payments by logging into each client's Stripe dashboard or payment terminal. An agent takes a call for Client A, alt-tabs to Client A's Stripe account, processes the payment, switches back. This is operationally fragile at any scale: - Agents need credentials for multiple payment systems - No audit trail linking the call to the transaction - Card data is visible to the agent (full PCI scope) - Training complexity multiplies with every new client - A single mis-keyed transaction goes to the wrong merchant account ### Building In-House Some enterprise BPOs consider building their own payment infrastructure. The scope is sobering: multi-PSP integration (each gateway is 2-4 weeks of engineering plus ongoing maintenance), PCI DSS Level 1 certification ($500K+ in year one), tokenisation vault, multi-tenant merchant management, and a compliance function to maintain it all. The build path makes sense for a payments company. BPOs are not payments companies. ## What BPOs Actually Need Strip it back to requirements: - Multi-PSP routing. Each client's payments route through their own PSP -- Worldpay, Stripe, Adyen, Checkout.com, or any of the 40+ gateways their merchants might use. One integration from the BPO's side. - Multi-tenant by design. The system knows which client the agent is handling. When a payment is triggered, it automatically routes to the correct PSP with the correct merchant credentials. No agent decision-making. No manual switching. Outsourced parking and enforcement operators face an analogous multi-client routing problem -- see Payment Collection for Parking, Enforcement and Toll Operators. - Limited PCI scope for the BPO. Card data never enters the BPO's environment. The card is captured within a PCI DSS Level 1 certified boundary (for voice today, that runs on Twilio Pay, so voice requires being a Twilio customer). Recordings stay clean. The BPO's telephony and recording stack stays out of scope. - White-label. The payment experience -- whether it's a DTMF prompt during a call or an SMS payment link sent mid-conversation -- carries the client's branding. The BPO can position this as their own capability. The end customer sees the brand they trust. - Per-transaction pricing. Cost scales with payment volume, not headcount. Quiet months cost less. Peak months scale without renegotiating seat licences. This aligns the payment infrastructure cost with the revenue it generates. - Multi-channel. Voice (DTMF) for live calls. Payment links via SMS or email for post-call follow-up or when the caller can't use a keypad. Chat payments for digital channels. The same integration covers all of them. - Unified reporting. One dashboard showing payment activity across all clients, with client-level filtering, reconciliation, and refund management. No logging into separate portals. ## The Revenue Opportunity Most BPOs treat payment collection as a cost centre -- a compliance headache they tolerate because clients demand it. That framing is wrong. Payment collection is a premium service. Clients will pay more for a BPO that can securely capture payments during calls, because the alternative is: - Post-call payment links with 30-50% drop-off - Customers calling back to a separate payment line - Failed collections that never convert When your BPO can capture a payment while the customer is live on the call -- with their card in hand, intent confirmed, agent guiding them through -- collection rates jump. That's directly measurable value for your clients. ### The Numbers The UK contact centre outsourcing market is worth $5.7 billion, growing to $7.8 billion by 2030. Payment-related calls represent 15-20% of contact centre volume across sectors like utilities, insurance, debt collection, telecoms, and financial services. For a mid-size BPO handling 50,000 payment calls per month at a $0.20 per-transaction cost: - Monthly infrastructure cost: $10,000 - Client charge (passed through + margin): $15,000-$25,000 - Net revenue from payment capability: $5,000-$15,000/month That's $60K-$180K in annual revenue from a capability that also improves client retention, wins new business, and differentiates you from BPOs that can't take payments. For larger operations, the numbers scale proportionally. A BPO processing 200,000 payment calls monthly is looking at $240K-$720K in annual margin from payment collection alone. ### Payments as a Competitive Moat Once a client's payment flows run through your infrastructure -- their PSP configured, their branding applied, their reconciliation integrated -- switching BPOs means rebuilding that entire payment setup elsewhere. Payment collection creates operational switching costs that message-taking and appointment-booking services don't. ## How It Works in Practice ### Agent-Assisted Payments (Human Agents) - Agent is on a call with a customer who needs to pay - Agent triggers "Take Payment" from the interface you build against Shuttle's APIs -- your routing identifies which client this call belongs to - The card is captured securely via Twilio Pay, routed to the client's configured PSP (voice requires being a Twilio customer) - The customer enters their card details on the keypad; the digits are captured inside Shuttle's certified environment and never reach the agent or the recording - The payment layer processes the transaction through the client's PSP - Agent sees confirmation: "Payment of £150.00 approved -- last four digits 4242" Shuttle ships the PCI-compliant capture, IVR and APIs plus ready-made link interfaces; the agent-side screen for your workflow is something you build, because every contact-centre setup is different. A packaged platform integration is available as a paid project. One honest caveat: full-call presence is not yet turnkey; returning the caller to the same agent works today when your team builds the return route in Twilio and passes a conversation ID. Shuttle works with Twilio today, and any carrier coming soon. The automated self-pay flow is covered in IVR Payments. If the customer can't use their keypad, the agent sends an SMS payment link with one click. Payment links are the turnkey path: they work mid-call, and they work even with gateways that don't support voice. The link is branded to the client, and the customer completes payment on their device. ### AI Agent Payments The same model works for AI voice agents. When the AI identifies payment intent, your agent triggers the payment layer via API. The card is captured securely at the point of payment, and the AI receives a webhook confirming success or failure. You build the agent interface against Shuttle's APIs; a packaged integration is a paid project. This is particularly relevant for BPOs scaling AI agents for debt collection, appointment payments, and renewal processing -- high-volume, repeatable payment scenarios. See PCI-compliant payments for AI voice agents for the architecture. ### Post-Call Payment Links For calls where payment wasn't completed live -- customer needed to check their account, wanted to discuss with a partner, or the call was informational -- the agent (human or AI) triggers an SMS or email payment link. The link carries the client's branding, supports cards, digital wallets, and bank transfers, and reports back when payment is received. ## PCI DSS v4.0.1: What Changed for BPOs PCI DSS v4.0.1 (effective March 2025) tightened requirements for outsourced payment collection: - Shared responsibility is now explicit. Merchants (your clients) can't fully transfer PCI liability to you by outsourcing. But they can dramatically reduce their scope by ensuring you use a PCI-certified payment layer that keeps card data out of your environment. - Enhanced monitoring of third-party providers. Your clients are now required to monitor and assess the compliance of their service providers more rigorously. A BPO using pause-and-resume or manual card entry is a compliance liability your clients must actively manage and report on. - Targeted risk analysis required. Every payment handling procedure needs documented risk analysis. A secure payment layer with DTMF isolation and multi-PSP routing is a cleaner compliance story than a patchwork of pause-and-resume policies and manual workarounds. For BPOs, the v4.0.1 changes mean that clients will increasingly require evidence of PCI-compliant payment infrastructure -- not just a policy document saying "we pause the recording." The BPOs that invest in compliant payment infrastructure now will win the clients whose compliance teams are asking these questions. ## Comparing Approaches Pause & Resume | DTMF Overlay (Single-Gateway) | Multi-PSP Payment Layer (Shuttle) PCI scope | Full SAQ-D | SAQ-A | SAQ-A Multi-PSP | N/A | Limited (1-3 gateways) | 40+ PSPs Multi-tenant | No | Limited | Built for it White-label | N/A | Limited | Full Pricing | N/A | Per-seat ($15-40/agent/mo) | Per-transaction ($0.20) Channels | Voice only | Voice only | Voice (Twilio Pay) + links + chat AI agent support | No | Limited | Yes (you build the agent interface) Implementation | Minimal | Weeks-months | Links self-serve; voice needs your build Best for | Small, single-client centres | Enterprise single-merchant | BPOs, multi-client outsourcers ## FAQ How does the system know which client's PSP to use? When your agent handles a call, your CRM or CTI identifies the client. When payment is triggered, the client's PSP configuration is passed to the payment layer. This is typically automated via your workforce management or routing system -- no manual selection required. What if a client changes their PSP? Configuration change. The client's PSP settings are updated in the payment layer. No re-integration. No downtime. Payments route through the new gateway from that point. Can we use this for outbound collections? Yes. Outbound calls work the same way -- when a customer agrees to pay, the agent triggers payment capture via DTMF or sends a payment link. For AI-driven outbound collections, see our guide on secure payment collection for debt agencies. What about refunds? Refunds are processed through the same payment layer, routed back through the original PSP. Agents can initiate refunds from the same interface they use for payment capture. Full audit trail included. How does this affect our existing CCaaS platform? There is no native integration with CCaaS or AI voice platforms today. Shuttle's voice capture runs on Twilio Pay, so voice requires being a Twilio customer; you keep your contact-centre platform and build the agent-side trigger against Shuttle's APIs. A packaged platform integration for your deployment is available as a paid project. For Twilio users, Pay Connectors cover the Twilio path. For CCaaS operators embedding this for their BPO customers, see Embedded Payments for CCaaS. What's the implementation timeline? Payment links are self-serve and can go out the same day; they work mid-call and with gateways that don't support voice. Voice capture requires being a Twilio customer and building your own agent-side interface against Shuttle's APIs -- a packaged integration is available as a paid project. Shuttle works with Twilio today, and any carrier coming soon. ## Related Reading - Take Payments on Behalf of Your Clients - solving the multi-merchant-account problem for servicers - PCI-Compliant Payments for Contact Centres -- the complete guide to contact centre payment approaches - Secure Payment Collection for Debt Agencies -- PCI-compliant payments for the collections vertical - Why Most Call Answering Services Can't Take Payments -- the payment gap in the call answering market - Enterprise PSP Mandates -- why enterprise clients demand their own PSP - PSP-Neutral vs Single-PSP -- the architectural decision for multi-PSP support - How Platforms Monetise Payments -- the revenue model for payment infrastructure - Prommt Alternatives for Platforms -- comparing payment link providers for multi-merchant collection - Twilio Pay Connectors -- connecting Twilio Flex to any PSP for BPO payment collection - Twilio PCI Compliance -- PCI scope and compliance for Twilio-based contact centres Collect payments for every client, through every PSP, without touching card data. Shuttle gives BPOs and outsourced contact centres a single integration for multi-client, multi-PSP payment collection -- with white-label branding, per-transaction pricing, and PCI DSS Level 1 compliance included. Voice (on Twilio Pay today), links, and chat. Payment links are self-serve; voice runs on Twilio and you build the agent interface, with a packaged integration available as a paid project. Book a Demo | See Voice Checkout ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### How BPOs Are Turning Every Call into a Payment Opportunity ### What Is Local Acquiring? How It Cuts International Payment Costs ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ## Links - [DTMF tones](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payment Collection for Parking, Enforcement and Toll Operators](/guides/parking-enforcement-toll-payments/) - [Payment links](/guides/take-payments-online/payment-links/) - [IVR Payments](/guides/ivr-payments/) - [PCI-compliant payments for AI voice agents](/guides/ai-voice-agent-pci-payments/) - [secure payment collection for debt agencies](/guides/secure-payment-collection-debt-agencies/) - [Pay Connectors](/guides/twilio-pay-connectors/) - [Embedded Payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [Why Most Call Answering Services Can't Take Payments](/blog/call-answering-service-payments/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [PSP-Neutral vs Single-PSP](/guides/psp-neutral-vs-single-psp/) - [Prommt Alternatives for Platforms](/alternatives/prommt/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Twilio PCI Compliance](/guides/twilio-pci-compliance/) - [Book a Demo](/discovery/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogHow BPOs Are Turning Every Call into a Payment Opportunity→](/blog/how-bpos-are-turning-every-call-into-a-payment-opportunity/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) --- URL: https://www.shuttleglobal.com/guides/payment-collection-professional-services/ --- # Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices | Shuttle > The Professional Services Payment Problem A client owes you £47,000 for six months of advisory work. You send an invoice as a PDF. They print it. # Payment Collection for Professional Services: Law Firms, Consultancies & Accounting Practices By Shuttle Team, March 4, 2026 ## The Professional Services Payment Problem A client owes you £47,000 for six months of advisory work. You send an invoice as a PDF. They print it. It sits on someone's desk. Two weeks later, a finance administrator emails asking for bank details. You reply. They process it in the next payment run. Maybe. That's six weeks from billing to cash for a single engagement. Multiply it across a portfolio of clients and the picture gets worse. Professional services firms bill differently from retail businesses. Transactions are large, often between £5,000 and £500,000. Payment terms are longer. Clients expect a level of formality and trust in every interaction, including the payment experience. And there are sector-specific compliance requirements that consumer payment tools simply don't address. Yet most law firms, accounting practices, consultancies, and engineering firms still rely on bank transfers initiated by the client after receiving a PDF invoice. The process is slow, manual, and disconnected from the systems that track billable work. This isn't a technology gap. Card payments and digital payment methods have existed for decades. The gap is that most payment solutions are designed for e-commerce checkout or retail point-of-sale. They don't fit the way professional services firms operate. ## What Professional Services Firms Need From a Payment Solution Before evaluating specific providers, it helps to define what actually matters for firms billing five- and six-figure amounts to corporate clients. ### Your Brand on the Checkout Page When a client clicks a payment link for £85,000, they need to know it's from you. A generic Stripe checkout page with your firm's name in small text doesn't cut it. The payment page needs your logo, your colours, and your domain. Anything less looks like a phishing attempt at these transaction values. White-label branding isn't a nice-to-have. For professional services firms handling large payments, it's a requirement. Your clients' finance teams will flag unbranded payment pages to their IT security departments before they'll enter a card number. ### Matter and Reference Tracking Every payment needs to tie back to a matter number, engagement code, or invoice reference. This is non-negotiable for law firms (where client money regulations require precise tracking) and equally important for consultancies and accounting practices that bill across dozens of active engagements. A payment solution that can't attach structured reference data to each transaction creates reconciliation work that wipes out any efficiency gains. ### Multi-Channel Delivery Some clients prefer email. Others respond faster to SMS. Property and construction professionals are often on-site and respond better to a WhatsApp message with a payment link than an email buried in their inbox. The ability to send payment requests through the channel your client actually uses is the difference between getting paid in 24 hours and waiting three weeks. ### Team Access and Permissions In a 40-person law firm, partners, associates, and accounts staff all need different levels of access to payment tools. A partner might need to create a payment link for a new matter. An accounts administrator needs to see transaction history and reconcile. A junior associate shouldn't have access to either. Role-based permissions aren't optional once a firm has more than a handful of people involved in billing. ### PCI Compliance Without the Overhead Professional services firms don't have payment engineering teams. They shouldn't need one. PCI DSS Level 1 compliance should be handled entirely by the payment provider, keeping card data out of the firm's environment. ## Law Firms: Trust Accounts, SRA Compliance, and Client Expectations Law firms have the most demanding payment collection requirements of any professional services sector. ### The SRA Client Money Problem In England and Wales, the Solicitors Regulation Authority (SRA) requires strict separation of client money from office money. Funds received on behalf of a client must go into a client account. Fees owed to the firm go to the office account. Getting this wrong isn't just an accounting error; it's a regulatory breach. This means a payment solution for law firms needs to support routing payments to the correct account based on the nature of the transaction. A retainer payment on account of costs goes to the client account. A settled invoice for disbursements goes elsewhere. Most generic payment tools have no concept of this distinction. They route all payments to a single merchant account. ### Client Expectations at High Values A private client paying £150,000 for conveyancing completion expects a professional experience. The payment page should look like it belongs to the firm. The reference should match their matter number. The confirmation should be instant and clear. Law firms that have adopted branded payment links report faster collection on completions and settlements specifically because the client trusts the process. There's no phone call to reception asking "is this link real?" before paying. ### Practical Implementation The firms getting this right use payment links tied to their practice management system. A fee earner raises an invoice in their case management software. The accounts team generates a branded payment link with the matter reference pre-attached. The link goes to the client via email or SMS. The client pays on a page that carries the firm's branding, with the matter reference visible. The payment lands in the correct account and is automatically matched to the invoice. No PDF. No BACS details. No three-week wait. ## Accounting Practices and Consultancies: Retainers, Milestones, and Recurring Fees Accounting firms and consultancies face different collection challenges. Transactions are often recurring or milestone-based rather than one-off. The billing relationship extends over months or years. ### Retainer Collection Monthly retainers are the backbone of accounting practice revenue. A firm managing 200 clients on monthly retainer packages of £500 to £5,000 each needs to collect those payments reliably without manual chasing. Payment links work here because they can be sent as recurring requests. Each month, the client receives a link for their specific amount with the period reference attached. No standing order setup required. No direct debit mandate paperwork. For firms that prefer automated collection, the same infrastructure supports recurring card payments and direct debit through the client's chosen payment service provider. ### Milestone Billing for Consultancies Management consultancies and engineering firms often bill against project milestones. A £200,000 strategy engagement might be structured as four payments of £50,000 at agreed project stages. Each milestone payment needs its own link, its own reference, and its own confirmation. The client's finance team needs to match each payment to the corresponding deliverable and purchase order. Generic invoicing tools handle the invoice side but leave the collection to bank transfer. Adding a branded payment link to each milestone invoice converts it from a "please arrange payment" request to a "click here to pay now" action. ### Team Billing Across Partners In multi-partner accounting practices, each partner manages their own client portfolio. They need to create and track payment requests independently while the practice's finance function maintains a consolidated view. This is where team features matter. Each partner can generate payment links for their clients. The accounts team sees all transactions across the practice. Reports can be filtered by partner, client, or period. ## How Payment Links Solve the Collection Problem The payment link model works for professional services because it separates the payment infrastructure from the billing system. ### The Process - Create a payment link. Set the amount, attach a matter or invoice reference, and choose the client's preferred payment method (card, bank transfer, or both). - Brand it. The payment page carries your firm's logo, colours, and domain. The client sees your brand, not a third-party gateway. - Send it. Email, SMS, or WhatsApp. Pick the channel the client responds to. - Client pays. They click the link, land on your branded checkout page, and complete payment. Card, Apple Pay, Google Pay, or bank transfer. - Auto-reconcile. The payment arrives with the reference data attached. Your accounts team matches it to the invoice without manual lookups. ### Why This Beats Traditional Invoicing PDF invoices with bank transfer details have been the professional services standard for decades. They work. They're just slow. The average time from PDF invoice to bank transfer receipt across UK professional services is 34 days (source: Xero Small Business Insights). Payment links reduce that to 1 to 3 days for firms that have adopted them. The difference is friction. A bank transfer requires the client to log into their banking portal, enter your sort code and account number, type in a reference, set the amount, and authorise. A payment link requires one click and a card number. For large transactions, the time savings compound. A law firm collecting 20 completions per month at an average of £80,000 each, moving from 30-day to 3-day collection, frees up significant working capital. ## Choosing a Payment Link Provider for Professional Services Not all payment link solutions are built for professional services. Here's what separates the options. ### Stripe Payment Links Stripe offers built-in payment links. They're fast to set up, support card payments and bank transfers, and work well for straightforward transactions. Limitations for professional services: - Branding is limited to logo and colour. The checkout page is clearly Stripe-hosted, which creates trust issues at high transaction values. - You're locked to Stripe as your payment processor. If your firm already has negotiated rates with Worldpay or another provider, you can't use them. - No multi-user team features designed for professional services workflows. - Reference tracking requires workaround configuration rather than being built into the link creation flow. ### GoCardless GoCardless specialises in direct debit collection. For recurring retainer payments, it's effective. - Direct debit only. No card payments, which limits flexibility for one-off large payments where clients prefer to pay by card. - The mandate setup process adds friction to the first payment. - No white-label option. The payment experience carries GoCardless branding. - Not suited to variable milestone billing or ad-hoc invoice collection. ### Shuttle Links Checkout Shuttle takes a different approach. Rather than being a payment processor, Shuttle sits as The Payment Layer between your firm and whichever PSP you use (or want to use). It connects to 40+ payment service providers, so you keep your existing gateway and rates. What this means for professional services firms: - Full white-label. Your brand on every payment page. Your domain. Your colours. No third-party branding visible to the client. - Bring your own PSP. If your firm already processes through Worldpay, Barclays, or any other provider, you connect that account. No switching. No renegotiating rates. - Matter and reference tracking built in. Every link carries structured reference data that flows through to your reconciliation. - Multi-channel delivery. Send links via email, SMS, or WhatsApp from the same dashboard. - Team features. Role-based access across partners, fee earners, and accounts staff. Shuttle charges a flat monthly fee per app, with transactions beyond the monthly allowance billed at a banded rate that falls with volume. See our pricing page for current rates. - PCI DSS Level 1. Card data never touches your systems. Shuttle handles the compliance burden. The key difference is flexibility. Stripe requires you to process through Stripe. GoCardless requires direct debit. Shuttle lets you use whatever payment methods and processors your firm and clients prefer, behind your own brand. ## Getting Started Professional services firms typically roll out payment links in stages: Week 1-2: Connect your existing PSP, configure branding (logo, colours, domain), and set up team accounts with appropriate permissions. Week 3-4: Start with new invoices. Attach a payment link to every invoice that goes out. Track conversion rates and time-to-payment against your baseline. Month 2: Extend to outstanding receivables. Send payment links for aged invoices. Most firms see a significant reduction in overdue balances within the first 30 days. Month 3+: Integrate with your practice management or accounting software. Automate link generation when invoices are raised. Set up recurring links for retainer clients. The firms that see the fastest results start with their largest outstanding invoices. A single £100,000 payment collected three weeks earlier than usual makes the ROI case immediately. Talk to our team about payment collection for your firm ## FAQ ### Can law firms accept credit card payments for legal fees? Yes. The SRA permits law firms to accept card payments for both office and client account transactions, provided the firm maintains proper records and the payment is allocated to the correct account. Many firms already accept card payments for smaller matters and are expanding to larger transactions as client expectations shift. ### What transaction fees apply to large professional services payments? Card processing fees are typically 1.4% to 2.5% for UK business cards, depending on your PSP and negotiated rates. For a £50,000 payment, that's £700 to £1,250 in fees. Some firms absorb this cost as a collection efficiency gain. Others pass it through to the client as a card payment surcharge (permitted under UK law for commercial transactions). Bank transfer options through payment links carry lower or zero transaction fees. ### How does reference tracking work with payment links? When creating a payment link, you attach a reference field (matter number, invoice number, engagement code, or any other identifier). This reference appears on the client's payment page and flows through to the transaction record. Your accounts team can then match the payment to the correct invoice without manual reconciliation. ### Is it secure for clients to pay large amounts via a payment link? Payment links from a PCI DSS Level 1 certified provider are more secure than reading card details over the phone or emailing bank transfer information. Card data is captured within the provider's certified environment and never enters the firm's systems. The link itself is single-use or amount-locked, preventing tampering. ### Can we use payment links alongside our existing invoicing process? Yes. Most firms add a payment link to their existing invoice (whether PDF or emailed) rather than replacing the invoice itself. The link provides a faster payment option while the invoice remains the formal billing record. Over time, many firms find the link becomes the primary payment channel and the invoice becomes purely a record-keeping document. ### What if our clients prefer bank transfers? Payment links can offer multiple payment methods on the same checkout page. A client who prefers bank transfer can select that option and complete an Open Banking payment (instant bank-to-bank transfer) directly from the link, with the reference data automatically attached. This is faster and more reliable than manual BACS transfers. ## Related Reading - Best Payment Link Providers - How B2B Service Companies Collect Payments Faster - Payment Links for Property Management - PCI-Compliant Payments for Contact Centres - Invoicing Software for SMEs - Payment Collection for Field Service Teams - Overdue Invoice Email Templates UK - The UK Guide to Collecting Overdue Payments - DSO Benchmarks by Industry UK (2026) ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Get Paid Faster: How IT Services Firms Use Shuttle Payment Links to Improve Cash Flow ### What Is Local Acquiring? How It Cuts International Payment Costs ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ### Payment Links for PayPal: Send Professional Payment Links Through PayPal ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Talk to our team about payment collection for your firm](/merchants/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [Payment Links for Property Management](/guides/payment-links-property-management/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Invoicing Software for SMEs](/guides/payment-collection-professional-services/) - [Payment Collection for Field Service Teams](/guides/field-agent-payment-collection/) - [Overdue Invoice Email Templates UK](/blog/overdue-invoice-email-templates-uk/) - [The UK Guide to Collecting Overdue Payments](/guides/uk-guide-collecting-overdue-payments/) - [DSO Benchmarks by Industry UK (2026)](/guides/dso-benchmarks-uk/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogGet Paid Faster: How IT Services Firms Use Shuttle Payment Links to Improve Cash Flow→](/blog/get-paid-faster-how-it-services-firms-use-shuttle-payment-links-to-improve-cash-flow/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) - [BlogPayment Links for PayPal: Send Professional Payment Links Through PayPal→](/blog/payment-links-for-paypal/) --- URL: https://www.shuttleglobal.com/guides/payment-gateway-cost/ --- # How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs | Shuttle > A payment gateway sits between your checkout and the banks. It encrypts card details, routes the transaction to the right acquirer, and returns an... # How Much Does a Payment Gateway Cost? Fees, Pricing & Hidden Costs By Shuttle Team, March 20, 2026 A payment gateway sits between your checkout and the banks. It encrypts card details, routes the transaction to the right acquirer, and returns an approval or decline. Every gateway charges for this service, but the cost structure varies enormously between providers -- and the sticker price rarely tells the full story. This guide breaks down exactly what a payment gateway costs, the different pricing models, what the major providers charge, and the hidden costs that catch businesses out. ## What Does a Payment Gateway Cost? For most businesses, a payment gateway costs between 1.5% and 3.5% per transaction, plus a fixed fee of 10p to 30p per transaction. On top of that, you may pay monthly fees, setup fees, PCI compliance fees, and chargeback fees. The total cost depends on your volume, average transaction value, card mix, and the provider you choose. A business processing £50,000 per month through Stripe at 2.9% + 30p would pay roughly £1,600 in gateway fees. The same volume through an interchange-plus provider might cost £900-£1,200. The key distinction: some providers bundle everything into a single flat rate, while others break out interchange separately. Flat-rate is simpler. Interchange-plus is usually cheaper at scale. ## Types of Payment Gateway Fees ### Transaction Fees The per-transaction charge is the largest cost for most businesses. It has two components: - Percentage fee -- a percentage of the transaction value (typically 1.4% to 3.5%) - Fixed fee -- a flat amount per transaction (typically 10p to 30p) The percentage covers interchange, scheme fees, and the gateway's margin. The fixed fee covers processing costs that don't scale with transaction size. For low-value transactions (under £5), the fixed fee becomes disproportionately expensive. A 20p fixed fee on a £2 transaction is 10% -- far more than the percentage alone. ### Monthly / Subscription Fees Some gateways charge a monthly fee for account access, reporting dashboards, or advanced features. This ranges from £0 (Stripe, Square) to £25-£50/month (Authorize.net, some Worldpay plans). Monthly fees are less significant at scale but can hurt small businesses processing fewer than 100 transactions per month. ### Setup Fees Most modern gateways have eliminated setup fees. Stripe, Square, and Adyen charge nothing to get started. Some legacy providers and enterprise acquirers still charge £50-£500 for account setup, integration support, or custom configuration. If a provider charges a setup fee in 2026, question what you are getting for it. The market has moved past this. ### PCI Compliance Fees Any business that handles card data must comply with PCI DSS. Gateways handle this differently: - Hosted payment pages / tokenisation -- the gateway handles PCI scope for you, usually included in the transaction fee - Non-compliance fees -- some acquirers charge £5-£15/month if you haven't completed your PCI SAQ (Self-Assessment Questionnaire) - Enterprise PCI -- if you handle raw card data yourself, PCI compliance costs run into tens of thousands annually for audits, penetration testing, and infrastructure For most businesses, using a gateway with a redirect-based or fully hosted checkout cuts PCI compliance costs sharply. ### Chargeback Fees When a customer disputes a transaction, the gateway or acquirer charges a chargeback fee -- typically £15-£25 per dispute, regardless of outcome. High chargeback rates (above 1%) can trigger monitoring programmes with additional penalties. Some providers include chargeback protection or insurance as a paid add-on (0.4%-0.6% per transaction). ### Cross-Border and Multi-Currency Fees Processing international payments adds cost: - Cross-border fee -- charged when the card-issuing bank is in a different country to the merchant's acquirer. Typically 0.5% to 1.5% on top of domestic rates. - Currency conversion fee -- if you settle in a different currency to the transaction currency. Usually 1% to 2.5%. - Scheme cross-border fees -- Visa and Mastercard charge additional scheme fees on cross-border transactions. For businesses with international customers, these fees can add 2-3% on top of the base transaction rate. Local acquiring -- processing through an acquirer in the customer's country -- is one way to reduce this. ## Payment Gateway Pricing Models ### Flat-Rate Pricing A single blended rate for all transactions, regardless of card type or issuing bank. Example: Stripe charges 2.9% + 30p for all domestic card transactions. Pros: Simple, predictable. Easy to calculate margins. Cons: You pay the same rate for a debit card (which has low interchange) as for a corporate Amex (which has high interchange). At scale, you overpay on cheap transactions. Best for: businesses processing under £50,000/month or those that prioritise simplicity over cost optimisation. ### Interchange-Plus (Interchange++) Pricing The gateway passes through the actual interchange rate and scheme fees, then adds a fixed markup. Example: Adyen charges interchange + scheme fees + 0.10-0.12 EUR per transaction. Pros: Transparent. You see exactly what interchange costs and what the gateway charges. Cheaper at scale because you benefit from low interchange on debit cards and regulated EU cards. Cons: More complex invoicing. Harder to predict exact costs month to month. Best for: businesses processing over £50,000/month, those with a high proportion of debit cards, or any business operating in the EU (where interchange is capped at 0.2-0.3%). ### Tiered Pricing Transactions are grouped into tiers -- qualified, mid-qualified, and non-qualified -- each with a different rate. The gateway decides which tier a transaction falls into. Pros: None, frankly. Cons: Opaque. The gateway controls tier assignment, and "non-qualified" rates (often 3%+) apply to a surprising proportion of transactions. This model is designed to make the headline rate look cheap while the effective rate is higher. Best for: nobody. Avoid tiered pricing. It is the most expensive model for merchants and the least transparent. ## Payment Gateway Cost Comparison (2026) Transaction Fee (Domestic) Monthly Fee Pricing Model 2.9% + 30p Custom rates available at volume Interchange++ + €0.11 Interchange-plus Minimum processing requirements Custom (typically 1.5-2.75%) Negotiated UK's largest acquirer; rates depend on volume Checkout.com Interchange++ + variable Strong in enterprise / cross-border Higher cross-border fees; buyer trust advantage 2.6% + 10p Primarily POS / omnichannel 2.59% + 49p Owned by PayPal; strong mobile SDKs Authorize.net Legacy provider; declining market share Important: These are published list prices. At volume (typically above £100,000/month), every provider on this list will negotiate. Stripe offers custom pricing from around 2.2% + 20p. Adyen and Checkout.com can get close to interchange + 5-8p per transaction for large merchants. ## Hidden Costs Most Businesses Miss ### 1. Integration and Development Time The gateway's API documentation may be free, but building, testing, and maintaining the integration is not. Budget 2-8 weeks of developer time for a basic integration, more for complex checkout flows or subscription billing. This is a real cost. At £500-£800/day for a payments engineer, a four-week integration project costs £10,000-£16,000 before you process a single transaction. ### 2. Gateway Lock-In Once you have built against a gateway's API, switching is expensive. You need to re-integrate, migrate stored card tokens (which some providers make deliberately difficult), update your reconciliation, and retest everything. This lock-in gives the gateway leverage in pricing negotiations. If switching costs £30,000 in development time, a provider only needs to undercut your current rate enough to make the ROI work -- and they know the switching cost. The antidote is a PSP-neutral architecture that abstracts the gateway layer, so you can add or swap providers without rebuilding your checkout. ### 3. PCI Compliance at Scale If you are a platform or marketplace handling payments on behalf of sub-merchants, your PCI scope expands significantly. Level 1 PCI compliance (for businesses processing over 6 million transactions per year) requires: - Annual on-site audit by a Qualified Security Assessor (QSA) - Quarterly network scans - Penetration testing - Dedicated security infrastructure Total cost: £50,000-£200,000+ per year. This is why most platforms use tokenisation and hosted payment fields to keep card data out of their environment entirely. ### 4. Multi-Currency and Settlement Costs If you accept payments in multiple currencies, the published transaction rate is only part of the picture. Look at: - FX spread -- the markup on the exchange rate when converting to your settlement currency (typically 1-2.5%) - Settlement timing -- some providers hold funds for longer on international transactions - Multi-currency settlement -- settling in the transaction currency avoids FX conversion but adds treasury complexity ### 5. Chargeback and Fraud Costs Beyond the per-chargeback fee (£15-£25), high dispute rates trigger: - Card scheme monitoring programmes (Visa VDMP, Mastercard ECM) with fines of £5,000-£25,000/month - Increased processing rates - Account termination in severe cases Budget for fraud prevention tooling (3D Secure, risk scoring, manual review) as part of your total gateway cost. ## How Platforms Pay Differently If you are a software platform embedding payments for your users -- rather than a single merchant accepting payments -- the cost equation changes fundamentally. ### The Platform Cost Stack A platform typically pays: - Gateway/PSP fees -- the underlying transaction processing cost - PayFac or orchestration fees -- the cost of onboarding sub-merchants, managing KYC, and splitting payouts - Compliance overhead -- PCI DSS, anti-money-laundering, and regulatory obligations - Integration and maintenance -- engineering time to build and maintain the payments infrastructure The gateway transaction fee is often the smallest part of the total cost. The real expense is in the infrastructure around it -- the payment layer that connects your platform to one or more PSPs. ### Multi-PSP Changes the Economics Platforms locked into a single gateway pay whatever that provider charges. Platforms that can route transactions across multiple PSPs gain: - Competitive leverage -- negotiate rates with multiple providers and shift volume to the cheapest - Lower interchange -- route transactions to local acquirers in each market, avoiding cross-border fees - Resilience -- if one provider goes down, traffic routes to another. Downtime is its own cost The upfront cost of multi-PSP architecture is higher, but the long-term savings on a business processing £10M+ annually typically pay for the infrastructure many times over. Read more in our enterprise PSP mandate guide. ## How to Reduce Payment Gateway Costs ### 1. Negotiate Based on Volume Published rates are starting points. If you process over £50,000/month, request custom pricing. If you process over £500,000/month, you should be on interchange-plus with a markup of 0.1% or less. ### 2. Optimise for Interchange Interchange is the largest component of your processing cost. Reduce it by: - Sending Level 2/3 transaction data for B2B payments (can reduce interchange by 0.5-1%) - Using 3D Secure authentication (triggers lower interchange categories) - Encouraging debit card payments over credit cards ### 3. Use Local Acquiring For international transactions, process through an acquirer in the customer's country to avoid cross-border fees. This alone can save 1-2% per transaction on international volume. Payment orchestration makes this operationally practical. ### 4. Review Your Effective Rate Monthly Your effective rate = total fees paid / total volume processed. Compare this to your contracted rate. If they differ significantly, dig into the transaction-level data to find where the overcharges are -- cross-border fees, downgrades, and scheme fee increases are common culprits. ### 5. Avoid Gateway Lock-In Build with portability in mind. Use tokenisation standards, abstract your gateway integration behind an internal API, or work with a PSP-neutral payment layer that lets you add and swap providers without re-engineering your checkout. ## Frequently Asked Questions ### How much does a payment gateway cost per transaction? Most payment gateways charge between 1.5% and 3.5% of the transaction value, plus a fixed fee of 10p to 30p per transaction. Flat-rate providers like Stripe charge 2.9% + 30p. Interchange-plus providers like Adyen pass through the actual interchange rate (as low as 0.2% for EU debit cards) and add a small fixed markup. ### Are there free payment gateways? No payment gateway is free -- they all charge per-transaction fees. However, many (Stripe, Square, Adyen) have eliminated monthly fees and setup fees, so you only pay when you process transactions. The per-transaction fee is the gateway's revenue. ### What is the cheapest payment gateway in the UK? For small businesses, Square (2.6% + 10p for online payments) is often the cheapest flat-rate option. For businesses processing over £50,000/month, interchange-plus providers like Adyen or Checkout.com are typically cheaper because EU interchange is capped at 0.2-0.3% for consumer cards. Your effective rate on interchange-plus can be as low as 0.5-0.8% for debit-heavy merchants. ### How much does PCI compliance cost? For most businesses using hosted payment fields or a redirect-based checkout, PCI compliance is effectively free -- the gateway handles it. For businesses handling raw card data, PCI SAQ-D self-assessment costs a few hundred pounds annually. For large enterprises requiring Level 1 PCI compliance with on-site audits, costs range from £50,000 to £200,000+ per year. ### Can I negotiate payment gateway fees? Yes. Every major gateway offers custom pricing at volume. Start negotiations when you hit £50,000/month in processing volume. At £500,000+/month, you should expect interchange-plus with a markup below 0.1%. Always get competing quotes -- this gives you leverage. ### What are cross-border payment gateway fees? Cross-border fees apply when the customer's card-issuing bank is in a different country to your acquiring bank. They typically add 0.5% to 1.5% on top of domestic rates, plus currency conversion fees of 1-2.5%. Using local acquiring (processing through an acquirer in the customer's country) eliminates these fees. ## Related Reading - What Is a Payment Gateway? -- how gateways work, key features, and how to choose one - Credit Card Processing Fees Explained -- detailed breakdown of interchange, scheme fees, and processor markups - Gateway vs Orchestrator vs PayFac vs Payment Layer -- understanding the infrastructure options beyond a single gateway - What Is Payment Orchestration? -- how multi-PSP routing reduces costs and increases approval rates - PSP-Neutral vs Single PSP -- the case for gateway portability and avoiding lock-in - Enterprise PSP Mandates -- why large enterprises require multi-PSP and what it means for costs ## Stop Overpaying for Payment Infrastructure If you are a platform or SaaS company embedding payments, the gateway transaction fee is just one piece of the puzzle. The real cost is in the infrastructure that connects your platform to the payment ecosystem -- and the lock-in that accumulates over time. Shuttle Global is the payment layer for software platforms. We connect you to 40+ PSPs through a single integration, so you can put each market on the provider that suits it, negotiate from a position of strength, and swap providers without re-engineering your checkout. Talk to us about your payment infrastructure or explore our Voice Checkout and Payment Links products. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### What Is a Payment Gateway? How It Works, Costs & Top Providers ### Payment Gateway Aggregation: What It Is and Why SaaS Platforms Need It ### Insuretech Innovation: Choosing the Right Payment Gateway for Your Business ### Event Payment Gateway: How to Choose the Right One ### Payment Gateway Integration: How to Add Payments to Your App or Platform ### Payment Providers: How They Work & How to Choose (2026) ## Links - [Local acquiring](/guides/what-is-payment-orchestration/) - [PSP-neutral architecture](/guides/psp-neutral-vs-single-psp/) - [the payment layer](/guides/payment-layer-explained/) - [enterprise PSP mandate guide](/guides/enterprise-psp-mandates/) - [Payment orchestration](/guides/what-is-payment-orchestration/) - [PSP-neutral payment layer](/guides/psp-neutral-vs-single-psp/) - [What Is a Payment Gateway?](/blog/what-is-a-payment-gateway/) - [Credit Card Processing Fees Explained](/guides/credit-card-processing-fees/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [What Is Payment Orchestration?](/guides/what-is-payment-orchestration/) - [PSP-Neutral vs Single PSP](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [Talk to us about your payment infrastructure](/platforms/) - [Voice Checkout](/merchants/) - [Payment Links](/merchants/links-checkout/) - [Book a Call](/discovery/) - [BlogWhat Is a Payment Gateway? How It Works, Costs & Top Providers→](/blog/what-is-a-payment-gateway/) - [BlogPayment Gateway Aggregation: What It Is and Why SaaS Platforms Need It→](/blog/unlocking-the-power-of-payment-gateway-aggregation-benefits-for-your-saas/) - [BlogInsuretech Innovation: Choosing the Right Payment Gateway for Your Business→](/blog/insuretech-innovation-choosing-the-right-payment-gateway-for-your-business/) - [BlogEvent Payment Gateway: How to Choose the Right One→](/blog/choosing-the-right-payment-gateway-for-your-event-software-a-comprehensive-guide/) - [BlogPayment Gateway Integration: How to Add Payments to Your App or Platform→](/blog/the-ultimate-guide-to-integrating-a-payment-gateway-into-your-app/) - [BlogPayment Providers: How They Work & How to Choose (2026)→](/blog/what-is-payment-gateway-aggregation/) --- URL: https://www.shuttleglobal.com/guides/payment-layer-explained/ --- # Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? | Shuttle > If you're a software platform trying to add payments, you've probably encountered four different approaches -- and a lot of confusion about which one... # Gateway vs Orchestrator vs PayFac vs Payment Layer: What's the Difference? By Shuttle Team, February 27, 2026 If you're a software platform trying to add payments, you've probably encountered four different approaches -- and a lot of confusion about which one applies to you. This guide breaks down each option: what it does, who it's designed for, and where it falls short for platforms. It also introduces a newer category -- The Payment Layer -- that was built specifically for the problem platforms actually face. ## Quick Comparison Gateway | Orchestrator | PayFac | Payment Layer What it does | Processes transactions | Routes between PSPs | Makes you the PSP | Embeds payments inside software PSP relationship | Is the PSP | Sits above PSPs | Replaces the PSP | Distributes PSPs Who it serves | Merchants | Merchants | Platforms wanting to be PayFacs | Platforms wanting to NOT be PayFacs Channels | Checkout page | Checkout page | Checkout page | Voice, links, chat, embedded, workflows Multi-tenant | No | Limited | Yes (heavy) | Yes (thin) Time to live | Weeks | Months | 6-12 months | Days to weeks PCI scope | Merchant owns it | Merchant owns it | Platform owns it | Layer owns it Examples | Stripe, Adyen, Worldpay | Primer, Spreedly | Stripe Connect, Adyen for Platforms | Shuttle ## What Is a Payment Gateway? A payment gateway is the core infrastructure that authorises and processes card transactions. When a customer enters their card number on a checkout page, the gateway communicates with the acquiring bank, the card network, and the issuing bank to approve or decline the transaction. Gateways are the foundation of online payments. Every digital transaction flows through one. The most recognised gateways -- Stripe, Adyen, Worldpay, Checkout.com -- also function as acquirers and payment service providers (PSPs). ### What gateways do well - Process transactions reliably at scale - Handle card-present and card-not-present payments - Provide fraud screening and tokenisation - Offer well-documented APIs for direct integration ### Where gateways fall short for platforms Gateways are designed to serve merchants, not platforms. When a platform integrates a gateway directly: - Each merchant on the platform needs a separate merchant account or sub-account - The platform is locked into that single PSP -- if a customer already uses a different provider, the platform can't accommodate them - Expanding to new payment channels (voice, links, chat) requires separate integrations - PCI compliance falls on the platform or merchant A gateway answers the question "how do I process a payment?" It doesn't answer "how do I embed payments inside my software for hundreds of merchants across multiple PSPs?" ## What Is a Payment Orchestrator? A payment orchestrator sits above multiple gateways and routes transactions between them. The premise: instead of integrating with one PSP, integrate with an orchestration layer that connects to many. Orchestrators like Primer and Spreedly offer a single API that abstracts multiple gateway connections. They handle retry logic, failover routing, and transaction optimisation -- sending each payment to whichever gateway is most likely to approve it at the lowest cost. ### What orchestrators do well - Abstract multiple PSP connections behind a single API - Optimise routing for approval rates and cost - Reduce gateway lock-in for merchants with multiple processors - Provide a unified reporting layer across PSPs ### Where orchestrators fall short for platforms Orchestrators solve merchant-side routing complexity. They're designed for a single business that uses three or four gateways and wants to optimise which gateway handles which transaction. For platforms, the problem is different: - Platforms don't need to route their own transactions across PSPs -- they need each customer to use their own PSP - Orchestrators are still checkout-page-centric -- they don't natively support voice payments, payment links, or AI agent conversations - Multi-tenancy is bolted on, not built in -- onboarding hundreds of merchants through an orchestrator requires significant custom work - PCI compliance still falls on the platform An orchestrator answers "how do I optimise routing across my PSPs?" It doesn't answer "how do I let each of my customers bring their own PSP?" For a deeper comparison, see our guide on payment orchestration vs The Payment Layer. ## What Is a PayFac? A Payment Facilitator (PayFac) is a model where a platform becomes a registered payment processor. Instead of each merchant on the platform having their own merchant account with a bank, the PayFac holds a master merchant account and onboards sub-merchants underneath it. Stripe Connect and Adyen for Platforms are the best-known PayFac-as-a-service models. They let platforms process payments on behalf of their merchants without obtaining a full PayFac licence independently -- though the platform still takes on significant compliance and operational overhead. ### What PayFac models do well - Give platforms control over the merchant experience - Enable revenue sharing on payment processing - Provide merchant onboarding and KYC workflows - Handle fund flows and settlement splits ### Where PayFac models fall short for platforms The PayFac model requires the platform to become a payment company: - Compliance overhead is substantial -- even with managed PayFac services, the platform takes on PCI scope, AML/KYC responsibilities, and ongoing regulatory obligations - Time to market is 6-18 months depending on the approach - The platform is locked into the PayFac provider -- if a customer already has a relationship with a different PSP, the PayFac model can't accommodate that - Revenue comes from payments margin, which requires volume to justify the investment - Engineering focus shifts from core product to payment infrastructure A PayFac model answers "how do I own the payment relationship?" But most platforms don't want to own the payment relationship. They want payments to work inside their product -- without the overhead of becoming a processor. For alternatives to the PayFac path, see our guide on embedded payments without becoming a PayFac. ## What Is The Payment Layer? The Payment Layer is a different category of infrastructure -- designed specifically for software platforms that need to embed payments without becoming a payment company. Instead of processing transactions (gateway), routing between PSPs (orchestrator), or making you the processor (PayFac), The Payment Layer sits between platforms and PSPs as thin, portable infrastructure. The platform integrates once. The layer handles everything else. ### How it works - The platform integrates once -- a single API connection to The Payment Layer - Each customer brings their own PSP -- or the platform connects them to any of 40+ supported providers - The layer handles compliance -- PCI DSS Level 1 is owned by the layer, not the platform - Payments work across channels -- voice, links, chat, embedded checkout, workflows -- all through the same integration - Merchant onboarding is white-labelled -- the platform's brand, not the layer's ### What The Payment Layer does differently PSP-neutral by design. The platform doesn't choose a PSP for its customers. Each customer uses their existing PSP -- or picks from the full range. This is critical for enterprise deals where customers mandate specific processors. Multi-channel from day one. Voice payments, payment links, embedded checkout, and chat payments all work through the same integration. Platforms don't need separate projects for each channel. See how this works for voice payments and payment links. Thin, not heavy. The Payment Layer doesn't replace the PSP. It doesn't replace the platform's product. It connects the two -- with the minimum infrastructure needed to handle compliance, onboarding, and payment capture. Platform-native multi-tenancy. Every concept in The Payment Layer is multi-tenant by default. Merchants, PSP connections, payment channels, and reporting all scope to the platform's customer base -- not to a single merchant account. ## Decision Framework: Which Do You Need? ### You need a gateway if... - You're a single merchant processing your own transactions - You need direct control over payment processing - You're building a checkout experience for your own customers ### You need an orchestrator if... - You're a large merchant using multiple PSPs - You want to optimise routing for approval rates and cost - You process enough volume that gateway arbitrage matters ### You need a PayFac if... - Payment revenue is core to your business model - You want full control over the merchant relationship - You're willing to invest 12+ months and significant capital in compliance infrastructure - Your customers don't have existing PSP relationships they need to keep ### You need The Payment Layer if... - You're a software platform and your customers need payments inside your product - Your customers have their own PSPs (or need flexibility to choose) - You need payments across multiple channels -- not just checkout pages - You don't want to become a payment company - You need to ship payments in weeks, not quarters - PCI compliance should not be your platform's responsibility Most platforms that evaluate PayFac models or direct PSP integrations discover that what they actually need is The Payment Layer. The requirement isn't "own the payment relationship." The requirement is "make payments work inside our product -- fast, flexibly, and without the overhead." ## How The Payment Layer Compares to Specific Solutions ### vs Stripe Connect Stripe Connect is a PayFac model -- it makes your platform the processor, locks you into Stripe, and limits you to Stripe's channels. The Payment Layer supports Stripe as one of 40+ PSPs without making the platform dependent on any single provider. ### vs Adyen for Platforms Adyen for Platforms is Adyen's equivalent -- powerful but Adyen-exclusive. The Payment Layer lets platforms support Adyen alongside other PSPs, rather than choosing one and building around it. ### vs Spreedly / Primer These are orchestrators optimised for merchant-side routing. The Payment Layer serves platforms, not merchants -- and adds multi-channel capabilities (voice, links, chat) that orchestrators don't offer. ### vs Building It Yourself Building multi-PSP support, PCI compliance, voice payments, and merchant onboarding internally takes 12-18 months and pulls engineering away from core product development. Getting payments off your roadmap is the primary value of The Payment Layer. ## FAQ Is The Payment Layer a gateway? No. Gateways process transactions. The Payment Layer connects platforms to gateways -- any gateway -- without the platform building each connection. Is The Payment Layer an orchestrator? No. Orchestrators optimise routing for merchants with multiple PSPs. The Payment Layer enables platforms to support whichever PSP each of their customers uses -- a fundamentally different problem. Do I still need a PSP? Yes. The Payment Layer doesn't process transactions. It connects your platform to PSPs. Your customers either bring their existing PSP or choose one from the 40+ providers the layer supports. What about PCI compliance? The Payment Layer handles PCI DSS Level 1 compliance. Card data passes through the layer's PCI-certified infrastructure -- your platform never touches it, even during voice payment calls. How long does integration take? Most platforms go live in days to weeks, depending on the channels they need. Compare this to 6-12 months for a PayFac setup or months of work for multi-PSP direct integrations. Can I start with one channel and add more later? Yes. Many platforms start with payment links or embedded checkout and later add voice payments or chat payments -- without new integration projects. Shuttle is The Payment Layer for software platforms. One integration. 40+ PSPs. Voice, links, chat, and embedded checkout. [See how it works](/platforms/) or [book a discovery call](/discovery/). ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Why We Built The Payment Layer ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ## Links - [Stripe Connect](/alternatives/stripe-connect/) - [payment gateway](/blog/what-is-a-payment-gateway/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [Checkout.com](/payment-providers/checkout-com/) - [payment orchestrator](/guides/what-is-payment-orchestration/) - [payment orchestration vs The Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [Stripe Connect](/vs/stripe-connect/) - [Adyen for Platforms](/vs/adyen/) - [embedded payments without becoming a PayFac](/guides/embedded-payments-without-payfac/) - [40+ supported providers](/payment-providers/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [customers mandate specific processors](/guides/enterprise-psp-mandates/) - [voice payments](/platforms/voice-checkout/) - [payment links](/merchants/links-checkout/) - [Getting payments off your roadmap](/guides/get-payments-off-your-roadmap/) - [40+ providers](/payment-providers/) - [voice payment calls](/platforms/voice-checkout/) - [Book a Call](/discovery/) - [BlogWhy We Built The Payment Layer→](/blog/why-we-built-the-payment-layer/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) --- URL: https://www.shuttleglobal.com/guides/payment-links-for-car-dealerships/ --- # Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments | Shuttle > The Dealership Payment Problem Car dealerships handle some of the highest-value consumer transactions in retail. A deposit on a new vehicle. # Payment Links for Car Dealerships: Collect Deposits, Balances & F&I Payments By Shuttle Team, March 29, 2026 ## The Dealership Payment Problem Car dealerships handle some of the highest-value consumer transactions in retail. A deposit on a new vehicle. The balance payment on collection day. F&I product add-ons. Service and parts invoices. And yet most dealerships still collect these payments through: - Card terminals at the desk -- requiring the customer to be physically present - Phone calls where the customer reads out card numbers -- a PCI compliance risk and a poor customer experience - Bank transfers -- slow, manual reconciliation, no confirmation until the money lands - Cheques -- still common for high-value transactions, with all the clearing delays that implies The result: delayed payments, manual follow-up, reconciliation headaches, and lost deposits when customers don't complete the process. ## How Payment Links Solve This A payment link is a branded checkout page delivered via SMS, email, or WhatsApp. The customer clicks, pays, done. No terminal needed. No card details read over the phone. No waiting for bank transfers to clear. For a car dealership, this means: ### Deposits -- secure immediately after agreement The sales team agrees a vehicle purchase with the customer -- whether in the showroom, on a call, or via email. Instead of asking the customer to come in or read out card details, the salesperson sends a payment link. The customer pays from their phone in seconds. The deposit is secured before the customer leaves the conversation. ### Balance payments -- collect before collection day Send a payment link for the outstanding balance a few days before the vehicle handover. The customer pays at their convenience. When they arrive to collect the car, the balance is already cleared. No delays on the day. ### F&I products -- upsell after the sale Finance and insurance products (GAP insurance, extended warranties, service plans) are often discussed after the main sale. Payment links let the dealership send a follow-up request for these add-ons without requiring another visit or phone payment. ### Service and parts -- invoice and collect digitally Send a payment link when servicing is complete or parts are ready for collection. Customers pay before arriving, reducing time at the counter and improving cash flow. ## Why Open Banking Matters for Automotive Car transactions are high-value. A deposit might be £1,000-£5,000. A balance payment might be £15,000-£40,000. At standard card processing rates (1.5-2.5%), the fees on a £30,000 balance payment are £450-£750. That's real margin erosion on every vehicle sale. Pay by Bank (open banking) eliminates card processing fees on these transactions. The customer pays directly from their bank account -- instant confirmation, no chargebacks, no card fees. For a dealership selling 100 vehicles a month with an average balance of £20,000: - Card fees at 2%: £40,000/month - Pay by Bank fees: A fraction of card processing -- typically pence per transaction That's potentially £35,000-£40,000 in annual savings for a single dealership. Shuttle supports Pay by Bank alongside card payments on the same payment link. The customer chooses their preferred method at checkout -- card, open banking, Apple Pay, or Google Pay. ## Voice Checkout -- For Customers Who Call Not every customer will click a link. Some customers -- particularly for high-value purchases -- want to speak to someone and pay during the call. Shuttle's voice checkout lets the customer enter card details via keypad (DTMF) while the agent stays on the line. The tones are masked -- the agent never hears the card number. Payment completes in seconds without leaving the conversation. This matters for: - Older customers who prefer phone transactions over digital - Fleet buyers making multiple vehicle payments on a call - Finance settlements where the customer calls to make a final payment - Out-of-hours enquiries via IVR -- automated payment capture without staff The alternative -- asking a customer to read their card number to a salesperson -- is a PCI compliance breach waiting to happen. And sending a link to someone who called specifically to pay right now adds unnecessary friction. ## What to Look for in a Dealership Payment Solution ### Payment method coverage High-value transactions demand options. At minimum: cards, open banking, Apple Pay, Google Pay. BNPL may be relevant for service and parts. ### Branding The payment page should carry your dealership's logo, colours, and domain. Customers completing a £30,000 payment need to trust the page. A generic third-party checkout creates doubt. ### Multiple delivery channels SMS is the fastest for in-person conversations. Email works for follow-ups. WhatsApp for customers who prefer messaging. QR codes for showroom displays. ### Real-time confirmation Both the customer and the sales team should know instantly when payment completes. No checking email. No refreshing dashboards. Real-time status so the deal progresses immediately. ### PCI compliance If you handle card data in any form -- including over the phone -- you need PCI-compliant infrastructure. A payment link provider should be PCI DSS Level 1 certified as a Service Provider, so your dealership's PCI scope stays minimal. ### DMS integration Ideally, payment activity feeds into your dealer management system -- CDK, Reynolds, Pinewood, Keyloop -- for automatic reconciliation. API access and workflow connectors (Zapier, Make.com) make this achievable without custom development. ## Prommt vs Shuttle for Car Dealerships Prommt is the incumbent in automotive payment requests. They've built DMS integrations and positioned heavily around Pay by Bank for high-value vehicle transactions. Here's how the two compare for dealership use: Payment links Yes -- SMS, email, chat Yes -- SMS, email, WhatsApp, QR Pay by Bank Yes -- 14 countries Voice payments No -- sends a link during the call Yes -- DTMF capture during the call Apple Pay / Google Pay Yes (via supported PSPs) Chase reminders Automated with payment method fallback Configurable reminders DMS integrations Oracle OPERA, some automotive DMS API + Zapier/Make.com connectors From €299/month From $49/month PCI certification Level 1 + ISO 27001 + SOC 2 For dealerships where phone payments are common (finance settlements, fleet, older customers), Shuttle's voice checkout is a capability Prommt doesn't have. For dealerships focused purely on digital payment requests with European Pay by Bank, Prommt's chase paths and DMS integrations may be more mature. ## FAQ Can customers pay with Apple Pay or Google Pay for a car deposit? Yes. Shuttle's payment links support Apple Pay and Google Pay alongside cards and open banking. For customers with cards saved in their wallet, this makes deposit payment almost instant -- tap to pay from the SMS notification. Is it safe to collect £30,000+ through a payment link? Yes. Payment links are PCI DSS Level 1 compliant, meaning card data is handled within a certified environment. Open banking payments are authenticated through the customer's own banking app with biometric or password verification. Both are more secure than taking card details over the phone. What if a customer wants to pay over the phone? Use voice checkout. The customer enters card details via keypad during the call. The agent stays on the line but never hears the card number. This is PCI-compliant and eliminates the risk of agents handling card data. Can I send payment links from our DMS? Shuttle provides API access and integrations with Zapier and Make.com, which connect to most DMS platforms. A triggered workflow (deal status → send payment link) can be set up without custom development. How quickly does the money arrive? Settlement depends on the payment method and PSP. Card payments typically settle in 1-3 business days. Open banking payments can be near-instant depending on the bank and payment scheme. Can I use this for used car sales too? Absolutely. The same workflow applies -- deposit link, balance link, F&I upsell link. Used car dealerships often benefit more because margins are tighter and saving card fees on high-value transactions has an outsized impact. ## Related Reading - Shuttle vs Prommt -- full comparison of payment link and voice checkout capabilities - Prommt Alternatives for Platforms -- the landscape of payment request providers - How to Send Payment Requests -- the complete guide to digital payment collection - Best Payment Link Providers (2026) -- ranked comparison of payment link services - What Are Voice Payments? -- how voice checkout works for phone-based payment collection - White-Label Payment Links for Platforms -- branded payment pages for multi-location businesses Collect deposits, balances, and F&I payments -- digitally. Shuttle gives car dealerships payment links with open banking, Apple Pay, and voice checkout. From $49/month. No card details over the phone. No card fees on high-value transactions. See Payment Links | Book a Demo ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments ### Payment Links for Trust Payments: Send Branded Checkout Links for European Card Processing ### Payment Links for GoCardless: Add Card Payment Links to Your GoCardless Setup ### Secure Payment Links: Card Authorization Made Simple ### Xero Payment Links: Collect Invoice Payments Faster ## Links - [voice checkout](/platforms/voice-checkout/) - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Prommt](/vs/prommt/) - [Shuttle vs Prommt](/vs/prommt/) - [Prommt Alternatives for Platforms](/alternatives/prommt/) - [How to Send Payment Requests](/guides/how-to-send-payment-requests/) - [Best Payment Link Providers (2026)](/guides/best-payment-link-providers/) - [What Are Voice Payments?](/guides/voice-payments/) - [White-Label Payment Links for Platforms](/guides/white-label-payment-links/) - [See Payment Links](/merchants/links-checkout/) - [Book a Demo](/discovery/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for CardConnect: Send Branded Checkout Links For Remote Card Payments→](/blog/payment-links-for-cardconnect/) - [BlogPayment Links for Trust Payments: Send Branded Checkout Links for European Card Processing→](/blog/payment-links-for-trust-payments/) - [BlogPayment Links for GoCardless: Add Card Payment Links to Your GoCardless Setup→](/blog/payment-links-for-gocardless/) - [BlogSecure Payment Links: Card Authorization Made Simple→](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) --- URL: https://www.shuttleglobal.com/guides/payment-links-for-hotels/ --- # Payment Links for Hotels & Holiday Accommodation: The Complete Guide | Shuttle > Why Hotels Still Chase Payments by Email Hotels and holiday accommodation providers deal with payment complexity that most e-commerce businesses never... # Payment Links for Hotels & Holiday Accommodation: The Complete Guide By Shuttle Team, February 26, 2026 ## Why Hotels Still Chase Payments by Email Hotels and holiday accommodation providers deal with payment complexity that most e-commerce businesses never face. A guest books online -- card captured. But then they want to extend their stay. Or upgrade their room. Or they no-show and you need to charge a cancellation fee against a card you captured six months ago. Or the card on file declines, and now your front desk is calling the guest to collect over the phone. Holiday lets and vacation rentals have it worse. Many operate on manual bank transfers -- the guest receives an email with account details and a polite request. Some pay promptly. Others don't. Chasing late payments eats hours every week. The pattern is the same across the accommodation sector: the initial booking payment works, but everything after that is manual, slow, and expensive to collect. Payment links solve this by giving hotels and accommodation providers a way to collect any payment, at any point in the guest journey, without needing the guest to visit a checkout page or call in card details. ## What Are Payment Links for Hotels? A payment link is a unique URL that takes a guest directly to a branded payment page. The guest clicks, enters their card details (or pays via Apple Pay, Google Pay, or bank transfer), and the payment is done. No app download. No login. No phone call. The link works on any device, in any browser. For hotels and holiday accommodation, payment links cover use cases that traditional checkout doesn't reach: - Pre-arrival deposits -- Send a link when a booking is confirmed. The guest pays immediately rather than on arrival. - No-show and cancellation charges -- If a card on file is expired or declined, send a link to collect the fee. - Room upgrades and upsells -- Guest wants to upgrade? Send a link for the difference. No need to take card details over the phone. - Damage deposits and security bonds -- Holiday lets can collect refundable deposits via link before check-in. - Extended stays -- Guest extends their booking mid-stay. Send a link for the additional nights. - Spa, restaurant, and ancillary charges -- Collect payment for add-on services without routing through the PMS. - Group bookings and events -- Send individual payment links to each guest in a group, rather than collecting one lump sum. - Outstanding balances -- Post-checkout charges (minibar, late check-out fees) collected via link instead of chasing by email. The key advantage: payment links work asynchronously. The guest pays when it suits them. Your team doesn't need to be on the phone or at the front desk to collect. ## How Payment Links Work in a Hotel Context ### The Flow - Your team creates a payment link -- through a dashboard, API, or directly from your PMS. The link includes the amount, a description (e.g. "Room upgrade -- Suite 204"), and optionally the guest's name. - The link is sent to the guest -- via email, SMS, WhatsApp, or embedded in a chat message. Whatever channel the guest prefers. - The guest clicks and pays -- they see a branded payment page (your hotel's logo and colours, not a third-party brand). They enter card details or use a wallet/bank transfer. - Payment is confirmed -- both the guest and your team receive confirmation. The payment reconciles against the booking in your PMS or accounting system. ### PMS Integration For hotels running a Property Management System (OPERA, Mews, Cloudbeds, APALEO, or similar), the ideal setup is a payment link that posts the transaction directly to the guest folio. This eliminates manual reconciliation -- the payment appears in the PMS as if it were collected at the front desk. Some payment link providers offer direct PMS integrations. Others provide API-level connectivity that your platform or technology partner configures. ### Multi-Currency International hotels and holiday accommodation providers need payment links that handle multiple currencies. A villa in the Algarve renting to UK guests should be able to send a link in GBP, not EUR. A London hotel collecting a deposit from a Japanese guest should offer JPY. Multi-currency payment links reduce friction and foreign exchange surprises for guests -- both of which improve conversion rates. ## Payment Links vs Traditional Hotel Payment Methods When it works Where it breaks Card on file (from booking) Standard charges at checkout Card expires, guest disputes, need to collect new amount Phone payments (MOTO) Guest is available and willing to call PCI compliance burden, staff time, guest inconvenience Bank transfer Guest is willing to send money manually Slow, error-prone, no confirmation, hard to reconcile Invoice + chase Corporate bookings with agreed terms Slow payment, admin overhead, bad debt risk Payment links Any payment, any time, any channel Requires guest to have a phone or email (nearly universal) Payment links don't replace card-on-file for standard charges. They cover everything card-on-file can't -- which, for most hotels and holiday accommodation providers, is a significant portion of revenue collection. ## Holiday Lets and Vacation Rentals: A Specific Use Case Holiday accommodation -- cottages, villas, apartments, Airbnb-style rentals -- operates differently from hotels. Bookings are often higher value (a week vs a night), payments are typically split (deposit + balance), and many operators still rely on bank transfers. Payment links are particularly valuable here: Deposit collection. When a guest books (via your website, Booking.com, or direct enquiry), send a payment link for the deposit immediately. No waiting for a bank transfer. No chasing. Balance collection. 4-6 weeks before arrival, send a link for the remaining balance. Set a due date. If unpaid, send a reminder link automatically. Security/damage deposits. Send a separate link for a refundable deposit. Refund via the same system after check-out inspection. Late cancellation fees. If a guest cancels inside the cancellation window and you can't charge the original card, a payment link collects the fee without confrontation. Cleaning and additional charges. Pet fees, extra cleaning, lost key charges -- send a link with a clear description rather than an awkward phone call. For operators managing multiple properties, payment links with reporting give a single view of all outstanding and completed payments across the portfolio. ## What to Look For in a Hotel Payment Link Solution ### Branding The payment page should carry your hotel or accommodation brand -- logo, colours, property photos. A generic or third-party branded page undermines guest confidence, especially for high-value payments. ### Channel Flexibility You need to send links via the channel the guest uses: email, SMS, WhatsApp, web chat. A solution that only supports email misses guests who respond better to text messages. ### PSP Flexibility This matters more than most accommodation providers realise. If you're a hotel group with properties in multiple countries, each property may have a different acquiring bank or payment processor. A payment link solution that locks you into a single PSP means some properties pay higher cross-border fees than necessary. For platforms serving multiple accommodation providers -- property management platforms, booking engines, holiday rental marketplaces -- PSP flexibility is essential. Each property or operator may have their own preferred payment processor. ### Payment Methods Cards (Visa, Mastercard, Amex) are the baseline. But increasingly, guests expect: - Apple Pay / Google Pay -- especially for mobile link clicks - Pay by Bank (Open Banking) -- lower fees for high-value payments like holiday rental balances - Local payment methods -- iDEAL in the Netherlands, Bancontact in Belgium, Klarna in Scandinavia ### Reconciliation Payment link transactions need to appear in your accounting or PMS alongside other payments. Look for solutions that provide structured data exports, API-level transaction data, or direct PMS integration -- not just receipt emails. ### PCI Compliance Any payment collection involves PCI DSS obligations. With payment links, the card data is captured on the payment page hosted by the link provider -- meaning your hotel or accommodation business never touches card data. This keeps your PCI scope minimal, which is a significant compliance and security advantage over phone-based card collection. ## Payment Links for Hotel Groups and Accommodation Platforms Individual hotels and holiday let operators benefit from payment links. But the bigger opportunity is at the platform level. Hotel groups with 10, 50, or 200+ properties need consistent payment collection across all sites -- with reporting that rolls up to a group level. Each property might need its own PSP, its own branding, its own settlement account. A payment link solution built for platforms handles this out of the box. Property management platforms (software that manages bookings, guest communication, and operations for multiple properties) can embed payment links as a feature of their platform. Instead of each property figuring out payment collection independently, the platform provides it -- branded as the platform, powered by a payment layer behind the scenes. Holiday rental marketplaces act as intermediary between guest and property owner. Payment links let the marketplace collect payments on behalf of the owner, with funds routed to the correct settlement account -- potentially through the owner's own PSP. This is where the distinction between a merchant payment link tool and a platform payment layer matters. A merchant tool (like Prommt or standalone Stripe Payment Links) serves one business at a time. A payment layer lets a platform offer payment links to hundreds or thousands of accommodation providers through a single integration. ## Voice Payments: The Other Hotel Payment Channel Payment links handle asynchronous collection -- the guest pays in their own time. But hotels also need real-time payment collection over the phone. A guest calls to book. A front desk agent processes a cancellation charge. A concierge takes payment for a restaurant reservation. These phone-based payments have traditionally required agents to ask for card details verbally -- which creates PCI compliance obligations and security risk. Voice payment solutions solve this by moving the card capture to a secure channel (IVR, DTMF tones, or a payment link sent mid-call) while the agent stays on the line. The card data never passes through the hotel's systems. For a complete hotel payment collection strategy, payment links and voice payments work together: links for asynchronous collection, voice for real-time phone-based collection. Both should route through the same PSP and reconcile in the same system. For more on voice payments in hospitality, see AI Voice Payments for Hotels & Travel. ## FAQ How much do payment links cost? Pricing varies by provider. Most charge a percentage per transaction (typically 1-3%) plus a small fixed fee. For high-value payments (holiday rental balances, group bookings), percentage-based pricing adds up -- so look for providers that offer tiered rates or flat fees at volume. Pay by Bank (Open Banking) typically costs less than card-based links. Can payment links handle recurring payments? Payment links are primarily for one-off collections. For recurring charges (monthly rent on long-term lets, subscription-based hotel services), you'd typically capture a card via a payment link and then set up recurring charges via the underlying PSP. Some platforms support this in a single flow. Are payment links secure? Yes -- payment links hosted by a PCI DSS Level 1 compliant provider are as secure as any other online card payment. The guest enters their details on a secure hosted page. Card data is tokenised and never stored on your systems. This is significantly more secure than taking card details over the phone. Can I customise the payment page? Most providers support white-label branding -- your logo, colours, and property name on the payment page. Some allow custom fields (booking reference, guest name, room number) that appear on the page and in the transaction record. What happens if the guest doesn't pay? Payment links can be configured with expiry dates and automated reminders. If a link expires unpaid, your system can trigger a follow-up -- a new link, a phone call from your team, or an escalation in your booking workflow. ## Related Reading - AI Voice Payments for Hotels & Travel -- real-time phone-based payment collection for hospitality - What Are Payment Links? -- the basics of payment link infrastructure - PSP-Neutral vs Single-PSP -- why hotel groups and platforms need multi-PSP flexibility - How Platforms Monetise Payments -- for property management platforms and booking engines embedding payments - Gateway vs Orchestrator vs PayFac vs Payment Layer -- understanding the infrastructure categories - Contact Centre Payments -- PCI-compliant phone payments for hotel call centres - Payment Solutions for Travel Platforms -- multi-PSP payment infrastructure for airlines, OTAs, and tour operators - Enterprise PSP Mandates -- when hotel chains require specific payment processors - Payment Links for Property Management Need payment links for your hotel, holiday accommodation, or property platform? Shuttle gives platforms and accommodation providers branded payment links across 40+ PSPs -- with voice payments, multi-currency support, and PCI DSS Level 1 compliance included. Each property uses their preferred payment processor. One integration covers everything. Talk to Us | See How It Works ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments ## Links - [PSP flexibility is essential](/guides/psp-neutral-vs-single-psp/) - [PCI scope](/glossary/pci-scope/) - [payment layer](/glossary/payment-layer/) - [payment layer](/guides/payment-layer-explained/) - [Voice payment solutions](/guides/voice-payments/) - [DTMF tones](/guides/dtmf-payments/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [What Are Payment Links?](/glossary/payment-links/) - [PSP-Neutral vs Single-PSP](/guides/psp-neutral-vs-single-psp/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Payment Solutions for Travel Platforms](/guides/travel-platform-payments/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [Payment Links for Property Management](/guides/payment-links-property-management/) - [Talk to Us](/discovery/) - [See How It Works](/platforms/) - [See Links Checkout](/merchants/links-checkout/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [BlogPayment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments→](/blog/payment-links-for-freedompay/) --- URL: https://www.shuttleglobal.com/guides/payment-links-method-crm/ --- # Payment Links for Method CRM: Collect Field Payments Without Card Terminals | Shuttle > Method CRM is built for businesses that live in QuickBooks. It syncs contacts, invoices, estimates, and work orders in real time. # Payment Links for Method CRM: Collect Field Payments Without Card Terminals By Shuttle Team, March 10, 2026 Method CRM is built for businesses that live in QuickBooks. It syncs contacts, invoices, estimates, and work orders in real time. For HVAC companies, plumbers, electricians, pest control operators, and other field service businesses, it is one of the better CRM options available. But when a field agent finishes a job and needs to collect payment on the spot, Method CRM has a gap. Card terminals don't integrate with Method. MethodPay covers online invoice payments but doesn't extend to SMS links, QR codes, or on-site mobile collection. And buying card machines for every van in your fleet gets expensive fast. Payment links solve this. An agent sends a link by text or shows a QR code, the customer pays on their own phone, and the payment syncs back to QuickBooks. No hardware required. ## The Method CRM Payment Gap Method CRM connects to QuickBooks better than almost any other CRM. Two-way sync means changes in either system stay in step. For quoting, scheduling, and job management, it works well. The payment side is more limited. MethodPay lets you accept payments on online forms and invoices, but it was built for customers paying remotely after receiving a bill. It wasn't designed for a technician standing in someone's kitchen after fixing a boiler. Field service businesses need to collect payment at the point of service. The usual answer is a card terminal, but card terminals create their own problems with Method CRM: - No direct integration. Terminal payments don't sync to Method or QuickBooks automatically. Someone has to reconcile them manually. - Hardware costs. A terminal for each agent means buying, maintaining, and replacing devices. At $300-$500 per terminal plus monthly fees, it adds up. - Connectivity issues. Terminals need a mobile data connection or Bluetooth pairing. In basements, rural areas, or older buildings, signal is unreliable. - Lost or damaged devices. Terminals in work vans get dropped, left behind, or damaged. Every lost unit is a cost and a gap in your collection workflow. Payment links bypass all of these problems. ## How Payment Links Work with Method CRM There are two ways to connect Shuttle payment links to your Method CRM workflow: manual and automated. Most businesses start with manual and move to automated as they scale. ### Manual: Agent Creates and Sends a Link - Agent completes the job and opens the Shuttle dashboard on their phone - Creates a payment link for the invoice amount - Sends it to the customer via SMS, WhatsApp, or email - Customer taps the link and pays on a branded checkout page - Payment is processed through your existing payment gateway - Payment records sync to QuickBooks via Shuttle's QuickBooks integration This takes about 30 seconds and works immediately. ### Automated: Method CRM Triggers the Link For businesses with higher volume, you can automate the entire flow using Zapier or Make (formerly Integromat): - Agent marks a job as complete in the Method CRM mobile app - A Zapier/Make automation detects the status change - Shuttle generates a branded payment link for the invoice amount - The link is sent to the customer via SMS automatically - Customer pays on their phone - A webhook confirms the payment back to Method CRM and QuickBooks The agent doesn't touch the payment at all. They finish the job, mark it done, and move to the next appointment. The customer gets a payment link within seconds. ## The Field Agent Workflow: Step by Step Here is what this looks like for a typical field service call: 1. Agent arrives and completes the work. Nothing changes about how your team operates in the field. They do the job as normal. 2. Agent marks the job complete in Method CRM. Using the Method mobile app, the agent updates the job status. If you're using the automated workflow, this is the only step the agent needs to take. 3. Customer receives an SMS with a branded payment link. The message comes from your business name (not "Shuttle" or some unknown number). The link opens a checkout page with your branding, the job description, and the amount due. 4. Customer pays on their own phone. They tap the link, enter their card details or use Apple Pay / Google Pay, and confirm. The checkout page works on any phone with a browser. No app download needed. 5. Payment is confirmed. The agent sees the payment status update in Method CRM. The transaction is recorded in QuickBooks automatically. The customer receives a receipt by email. No card terminal. No cash. No "I'll send you an invoice later" delays that turn into 30, 60, or 90-day collection cycles. ## Why This Beats Card Terminals for Method CRM Users ### Cost A card terminal costs $300-$500 upfront per device, plus $15-$30/month in service fees. For a team of 10 field agents, that's $3,000-$5,000 in hardware before anyone takes a payment. Shuttle Links Checkout costs $49/month. No hardware to buy, ship, track, or replace. Adding a new agent to your team costs nothing extra in equipment. ### Integration Card terminal payments don't sync to Method CRM or QuickBooks without manual entry. Someone in your office has to match terminal receipts to invoices at the end of each day. Payment links sync automatically. Payment goes through your gateway, hits QuickBooks, and updates Method CRM. No reconciliation needed. ### Scale Adding new agents with card terminals means ordering hardware, setting up accounts, shipping devices, and training staff. It takes days. Adding new agents with payment links means giving them login credentials. It takes minutes. ### Reliability Card terminals depend on the device having battery, a data connection, and working hardware. Payment links depend on the customer having a phone. Since every customer already has one, the failure rate is close to zero. ## SMS, QR Codes, and Email: Choosing the Right Channel Payment links are just URLs. They can be delivered through any channel. The right choice depends on when and where you are collecting. ### On-Site Collection: QR Code When the agent is standing in front of the customer, a QR code is the fastest option. The agent pulls up the QR code on their phone screen, the customer scans it with their camera, and the checkout page opens immediately. No typing a phone number. No waiting for a text to arrive. The customer pays while the agent is still there. ### Post-Visit Collection: SMS If the customer isn't available when the job finishes (common with commercial properties, rental units, or scheduled maintenance), an SMS link sent after the visit is the best option. Text messages have a 98% open rate and most are read within 3 minutes. ### Invoiced Work: Email For larger jobs that go through a formal invoicing process, embed the payment link in the email with the invoice. The customer reviews the invoice and clicks to pay without needing to log into a portal or send a bank transfer. ### All Channels, One Checkout Page Regardless of how the link is delivered, the customer lands on the same branded checkout page. Your logo, your colours, your business name. The experience is consistent whether they got the link by text, scanned a QR code, or clicked through from an email. ## What About MethodPay? MethodPay is Method CRM's built-in payment feature. It works for accepting payments on web forms and attaching payment options to invoices sent from Method. For office-based collection, MethodPay does the job. If your customers are paying invoices from their computer after receiving an emailed bill, MethodPay handles that. Where MethodPay falls short is field collection. It doesn't support: - SMS payment links sent from the job site - QR codes displayed on an agent's phone - Multi-PSP flexibility (MethodPay uses a fixed payment processor) - White-label checkout with full branding control - WhatsApp or chat delivery for payment requests Shuttle doesn't replace MethodPay. It fills the gap that MethodPay doesn't cover. Use MethodPay for your invoiced, online collection. Use Shuttle for on-site, field-based, and multi-channel collection. If you're already using a specific payment processor for your business, Shuttle works with it. Shuttle connects to 40+ PSPs, so you keep your existing rates and settlement. MethodPay locks you into their processor. With Shuttle, you choose. ## Getting Started Pricing: $49/month for Links Checkout. No setup fees. No hardware costs. No long-term contract. Setup time: Connect your payment gateway and QuickBooks account. Your first payment link can go out the same day. What you need: A Method CRM account, a QuickBooks Online or Desktop account, and an existing payment gateway (or Shuttle can help you set one up). Talk to the Shuttle team about field payment collection → ## FAQ ### Does this work with QuickBooks Desktop or just QuickBooks Online? Both. Shuttle integrates with QuickBooks Online directly. For QuickBooks Desktop, the sync runs through Method CRM's existing two-way connection to Desktop, so payment records flow through to either version. ### Can I use my existing payment processor? Yes. Shuttle connects to 40+ PSPs including Stripe, Worldpay, Authorize.net, Braintree, Adyen, and many others. Your processing rates and settlement schedule stay exactly the same. You're adding a payment link layer on top of your current setup, not switching providers. ### What does the customer see? A branded checkout page with your business name, logo, and colours. The customer sees the amount due, a description of the service, and fields to enter their card details (or Apple Pay / Google Pay buttons). It looks like your business, not a third-party payment page. ### How fast do funds settle? Settlement follows your existing payment processor's schedule. Shuttle doesn't hold funds or change your settlement terms. If your gateway settles in T+1 (next business day), that's what you get. ### Can agents generate links from their phone? Yes. The Shuttle dashboard is mobile-friendly. Agents can create a payment link, copy it, and send it via SMS or pull up a QR code, all from their phone. No laptop or office access needed. ### Do I need to replace MethodPay? No. MethodPay handles invoice payments sent from Method CRM. Shuttle handles field collection, SMS links, QR codes, and multi-channel payment requests. They work alongside each other. ## Related Reading - Field Agent Payment Collection -- workflows and tools for collecting payments in the field - Best Payment Link Providers -- comparison of payment link platforms - How to Take Payments Without a Card Machine -- alternatives to card terminals for in-person collection - Multi-Channel Payment Collection -- SMS, email, WhatsApp, and QR code payment strategies - QuickBooks Payment Links -- adding payment links to QuickBooks invoices ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ### Payment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments ## Links - [Talk to the Shuttle team about field payment collection →](/merchants/) - [Field Agent Payment Collection](/guides/field-agent-payment-collection/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [How to Take Payments Without a Card Machine](/guides/take-payments-online/without-card-machine/) - [Multi-Channel Payment Collection](/guides/multi-channel-payment-collection/) - [QuickBooks Payment Links](/guides/quickbooks-payment-links/) - [Book a Call](/discovery/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) - [BlogPayment Links for FreedomPay: Send Branded Checkout Links For Remote and Off-Premise Payments→](/blog/payment-links-for-freedompay/) --- URL: https://www.shuttleglobal.com/guides/payment-links-property-management/ --- # Payment Links for Property Management & Lettings Agencies | Shuttle > Payment Collection in Property Management Is Still Manual Lettings agencies and property management firms handle hundreds of transactions every month. # Payment Links for Property Management & Lettings Agencies By Shuttle Team, March 2, 2026 ## Payment Collection in Property Management Is Still Manual Lettings agencies and property management firms handle hundreds of transactions every month. Rent, deposits, maintenance charges, service charges, inventory fees. Each one tied to a specific tenant, a specific property, and often a specific landlord account. And yet most of the industry still relies on bank transfers, standing orders, and cheques. The problems are predictable. Tenants use the wrong reference when paying by BACS, so the payment arrives but nobody can match it to the right property. Standing orders don't update when rent changes or a tenant moves out. Cheques get lost in the post. And when a tenant misses a payment, someone on your team spends their morning chasing it by phone and email. The result: hours of manual reconciliation every week, late payments that drag on for days, and arrears that could have been prevented with a better collection method. Payment links fix this by giving property managers a direct, trackable way to request and collect money from tenants, without relying on the tenant to remember the right bank details or update a standing order. ## What Property Managers Actually Need From Payment Collection Generic payment tools miss the mark for property management. The industry has specific requirements that most payment providers don't account for. ### Reference-Based Reconciliation Every payment needs to tie back to a property, a tenant, and often a landlord. When a tenant pays rent for Flat 4, 22 Marsh Lane, that payment needs to land against the right account in your property management software. If your payment tool doesn't support custom references, you're back to manual matching. ### Branded Checkout Pages Tenants should see your agency's name and branding when they pay. A generic Stripe or PayPal checkout page creates confusion. Tenants don't recognise the company name, they worry it's a scam, and your support team fields calls asking "who is this charge from?" A branded payment page with your agency logo builds trust and reduces failed payments. ### Multi-Channel Delivery Your tenant base is mixed. Some are young professionals who respond to WhatsApp. Some are older tenants who check email. Some only respond to text messages. You need to send payment requests through whatever channel the tenant actually uses. A payment system that only supports email links misses a large part of your portfolio. ### Team Access for Multiple Agents Property management firms have multiple agents, each managing their own portfolio. The payment system needs to support team logins so agents can create and track payment links for their properties without seeing everyone else's transactions. Admin users need oversight across the whole agency. ### Compliance and Deposit Protection Holding deposits and tenancy deposits have specific legal requirements under the Tenant Fees Act and deposit protection schemes. Your payment collection method needs a clear audit trail showing when money was received, what it was for, and which tenancy it relates to. Payment links create this trail automatically because each link has a defined purpose and reference from the moment it's created. ## How Payment Links Work for Property Management The process is straightforward. ### Step 1: Create the Link An agent creates a payment link through a dashboard. They set the amount, add a description ("March 2026 Rent - Flat 4, 22 Marsh Lane"), and attach a reference that maps to the property and tenant in your management system. Some providers let you create links via API, which means your property management software can generate payment links automatically when rent is due or a charge is raised. ### Step 2: Send It to the Tenant The link goes out to the tenant via their preferred channel. SMS, email, or WhatsApp. The message includes the amount, what the payment is for, and the link itself. For recurring charges like rent, you can set up scheduled links that go out on the same date each month. The tenant gets a fresh link every time, with the correct amount and reference already attached. ### Step 3: The Tenant Pays The tenant clicks the link on their phone or computer. They see a branded payment page with your agency's name and logo. They enter their card details or pay via bank transfer, Apple Pay, or Google Pay. No app to download. No account to create. No sorting through bank details to find the right account number. ### Step 4: Payment Matches Automatically Because the link was created with a specific reference, the payment reconciles against the right property and tenant as soon as it clears. Your finance team doesn't need to open the bank statement and manually match fifty BACS transfers with wrong or missing references. The agent and the tenant both get confirmation. There's a full audit trail showing when the link was sent, when it was opened, and when payment was made. ## Use Cases Across Property Management Payment links cover far more than just rent. Here are the charges that property managers and lettings agents typically collect. ### Rent Collection The core use case. Send a payment link at the start of each rent period instead of relying on standing orders or BACS transfers. The link includes the exact amount and a reference that ties back to the tenancy. No more chasing payments with the wrong reference. ### Holding Deposits When a prospective tenant wants to reserve a property, send a payment link for the holding deposit. The link creates an instant record of when the deposit was paid and what it was for, which matters when the Tenant Fees Act requires you to return or account for it within specific timescales. ### Tenancy Deposits Collect security deposits via payment link before move-in. The audit trail shows the exact amount and date, making it easier to register the deposit with a protection scheme and resolve disputes at the end of the tenancy. ### Maintenance and Repair Charges When a tenant is liable for a repair (damage beyond fair wear and tear, lost keys, emergency callout), send a payment link for the exact amount. The description on the link makes clear what the charge is for, reducing disputes. ### Service Charges and Ground Rent For managed properties with service charge obligations, payment links let you collect each charge individually with a clear breakdown. Leaseholders see exactly what they're paying for before they click. ### Move-In and Move-Out Fees Inventory check fees, professional cleaning charges, key cutting costs. Send individual links for each charge rather than bundling them into a confusing invoice that tenants query. ### Arrears Collection When a tenant falls behind, a payment link is more effective than a letter asking them to transfer money. It removes friction. The tenant can pay immediately from their phone rather than having to log into their bank, find the right sort code and account number, and type in a reference. For persistent arrears, you can resend the same link or create a new one with an updated amount that includes late fees where the tenancy agreement allows. Every send and every open is tracked, which gives you a documented record of attempts to collect if the case escalates to a deposit dispute or court claim. ### Renewal and Administration Fees When a tenancy renews or a lease extension is agreed, there are often administration charges to collect. A payment link sent alongside the renewal paperwork makes collection immediate. The tenant signs the new agreement and pays the fee in the same sitting, rather than the charge sitting unpaid for weeks while your accounts team chases it. ## Why Generic Payment Tools Don't Work for Property Management Property managers have tried the obvious options. Stripe payment links. PayPal.me links. GoCardless for direct debits. Each has problems specific to the property sector. ### No Reference Tracking Most generic payment link tools let you set an amount and a description, but they don't support structured references that map to your property management system. You're back to manual reconciliation. ### No Branding A Stripe checkout page says "Stripe" at the bottom. A PayPal link takes tenants to PayPal's site. Neither carries your agency's branding. For an industry built on trust between agent and tenant, this matters. Tenants need to recognise who they're paying. ### PSP Lock-In If you use Stripe's payment links, you're locked into Stripe for processing. If your fees go up or Stripe changes its terms, you have to rebuild your entire payment collection workflow. The same applies to PayPal, Square, or any other provider that ties the link to their own processing. ### No Team Features Most payment link tools are built for solo operators or e-commerce businesses. They don't support multiple agents with separate portfolios, different permission levels, or agency-wide reporting. A lettings agency with ten negotiators and three property managers needs a system where each person can manage their own payment links while the finance team has visibility across everything. ### No Recurring or Scheduled Sending Generic tools treat each payment link as a one-off event. Property management needs scheduled sends (rent day each month), recurring amounts, and the ability to adjust amounts when rent reviews take effect. Without this, someone on your team is manually creating and sending links every month. ### What to Look For Instead The right payment link provider for property management should offer: - Custom references on every link that map to your property and tenant records - White-label branding so tenants see your agency, not a third-party payment company - Multi-channel sending (SMS, email, WhatsApp) to reach tenants on their preferred channel - Team accounts with agent-level access and admin oversight - PSP flexibility so you can connect your existing payment gateway rather than being locked into one provider - PCI DSS Level 1 compliance to protect tenant card data - Reporting and export for reconciliation with your property management software Shuttle's Links Checkout was built for exactly this type of use case. It works as a Payment Layer that sits between your property management operation and whichever payment gateway you already use. Connect any of 40+ PSPs, apply your own branding, and give your team the tools to create, send, and track payment links across your whole portfolio. Shuttle charges a flat monthly fee per app plus a banded per-transaction rate that falls with volume, separate from your existing processing fees. See our pricing page for current rates. ## Frequently Asked Questions ### Can tenants pay by bank transfer through a payment link? Yes. Most modern payment link providers support open banking payments alongside card payments. The tenant clicks the link, selects bank transfer, and authorises the payment through their banking app. The payment still reconciles against the reference on the link, so you get the same automatic matching as a card payment. ### What about tenants who prefer standing orders? Standing orders still work for tenants who want them. Payment links don't replace standing orders. They give you a backup for when standing orders fail (wrong amount, cancelled by the bank, tenant moved and forgot to update) and a primary method for one-off charges like deposits, maintenance, and fees that standing orders can't cover. ### How does this work with deposit protection schemes? Payment links create a clear audit trail of when a deposit was collected, the exact amount, and which tenancy it relates to. This makes registration with deposit protection schemes (DPS, MyDeposits, TDS) straightforward. The payment confirmation serves as proof of receipt with a timestamp, which is useful if there's ever a dispute about when or how much was paid. ### What are the fees? This depends on the provider. With Shuttle, you pay a flat monthly fee for the Links Checkout app. Your payment processing fees are whatever you've negotiated with your existing PSP. Each app includes a monthly transaction allowance; beyond it, Shuttle bills a banded per-transaction rate that falls with volume, separate from your gateway's processing fees. Current allowances and rates are on our pricing page. This is different from providers like Stripe or PayPal, where the link tool is free but you pay their processing rates on every transaction. ### Can I send bulk payment links for rent day? Yes. Providers with API access let you generate links in bulk from your property management software. On rent day, your system creates a link for each tenancy and sends it automatically. No manual work required. ### Is this PCI compliant? With the right provider, yes. Shuttle is PCI DSS Level 1 certified, which is the highest level of payment security compliance. Tenant card data is handled in Shuttle's secure environment, not on your agency's systems. This means you don't need to worry about PCI compliance obligations beyond choosing a compliant provider. ## Related Reading - Take Payments on Behalf of Your Clients - How servicers route payments to each client's own merchant account - Best Payment Link Providers - Compare payment link platforms for business use - Payment Collection for Professional Services - How service businesses collect payments faster - How B2B Service Companies Collect Payments Faster - Payment collection strategies for B2B firms - How to Take Payments Online - Getting started with online payment collection - Payment Links for Hotels - Similar use case in hospitality and accommodation ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### The Power of Payment Links: Enhancing Financial Management in Practice Management Software ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Global Payments: Send Branded Checkout Links Without Developer Resources ## Links - [Links Checkout](/merchants/links-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [Best Payment Link Providers](/guides/best-payment-link-providers/) - [Payment Collection for Professional Services](/guides/payment-collection-professional-services/) - [How B2B Service Companies Collect Payments Faster](/guides/b2b-payment-collection/) - [How to Take Payments Online](/guides/take-payments-online/) - [Payment Links for Hotels](/guides/payment-links-for-hotels/) - [Book a Call](/discovery/) - [BlogThe Power of Payment Links: Enhancing Financial Management in Practice Management Software→](/blog/the-power-of-payment-links-enhancing-financial-management-in-practice-management-software/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Global Payments: Send Branded Checkout Links Without Developer Resources→](/blog/payment-links-for-global-payments/) --- URL: https://www.shuttleglobal.com/guides/payment-operations-at-scale/ --- # Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions | Shuttle > The Ops Problem Nobody Warns You About When your platform processes a few hundred transactions a day through a single PSP, payment operations feel... # Payment Operations at Scale: Why Reconciliation Breaks at 10,000 Transactions By Shuttle Team, March 16, 2026 ## The Ops Problem Nobody Warns You About When your platform processes a few hundred transactions a day through a single PSP, payment operations feel invisible. Settlement lands on time. Disputes get handled. Refunds get tracked. Everything works. Then you add a second PSP. Then a third. Your transaction volume crosses 10,000 per day. And suddenly the back office is on fire. This is the payment ops inflection point -- the moment where processes that worked at startup scale become actively dangerous at mid-market scale. The numbers tell the story. According to Modern Treasury's 2025 State of Payment Operations report, 88% of companies face payment operations problems. Nearly half -- 47% -- describe their payment operations as "manual". Among fintechs and platforms processing significant volume, 40% lose eight or more hours per week on payment operations tasks alone. These aren't small inconveniences. They're operational liabilities. ## What Breaks at Scale ### Reconciliation Across Multiple PSPs Every PSP reports differently. Settlement files arrive in different formats, at different times, covering different date ranges. Some report in UTC, others in local time zones. Some group transactions by merchant, others by batch. Some include fees inline, others report fees separately. At one PSP, this is manageable. Your finance team learns the format, builds a spreadsheet, and matches transactions to bank deposits. At three PSPs, the spreadsheet becomes a monster. At five, it's fiction. Transaction records don't match because one PSP settled Tuesday's transactions on Wednesday while another batched them into Thursday. Currency conversion timing differs. Fee deductions happen at different points in the chain. The result: reconciliation drift. Your books say one thing. Your bank accounts say another. The gap might be small -- until it isn't. A 2024 study by Gartner found that 90% of CFOs face reconciliation challenges, with the problem increasing proportionally with the number of payment providers in their stack. Manual reconciliation doesn't just slow down -- it produces errors. Research from the Association of Financial Professionals shows that 42% of organisations experience reporting errors directly attributable to manual reconciliation processes. ### Settlement Reporting Each PSP produces its own settlement report. Different column headers. Different transaction identifiers. Different approaches to grouping, netting, and fee presentation. Your finance team needs to answer a simple question: "How much revenue did we collect yesterday?" With a single PSP, it takes five minutes. With four PSPs across three currencies, it takes half a day -- and the answer still might be wrong. Settlement timing compounds the problem. PSP A settles T+1 to one bank account. PSP B settles T+2 to another. PSP C settles weekly. Your treasury team is reconciling across different time horizons, different bank accounts, and different reporting formats simultaneously. ### Chargeback Management Chargebacks are time-sensitive. You typically have 7-14 days to respond, and each PSP has its own dispute portal, its own evidence format requirements, its own notification system. When disputes are distributed across five PSPs, the risk of missing a deadline increases dramatically. A missed chargeback response is an automatic loss -- and at enterprise volumes, those losses add up fast. Worse, you lose pattern visibility. Fraud patterns that span multiple PSPs become invisible when each provider's data sits in a separate silo. A coordinated fraud attack might hit your Worldpay flow first and your Adyen flow two days later. Without a unified view, you don't see the pattern until the damage is done. ### Refund Tracking Refunds seem simple. They're not -- especially across multiple PSPs. Each PSP handles refund timing differently. Some process refunds immediately. Others batch them. Some net refunds against future settlements. Others debit your bank account directly. The accounting treatment varies, the cash flow impact varies, and the reconciliation complexity multiplies with each provider. Now add partial refunds, multi-currency refunds, and refunds that span settlement periods. Your team is tracking refund status across multiple dashboards, matching them to original transactions in different formats, and ensuring each one is correctly reflected in your accounting system. ## Signs Your Payment Ops Are Breaking These are the early warning signals that your payment operations have outgrown your processes: Manual spreadsheets are the single source of truth. If your reconciliation process involves downloading CSV files from multiple PSP dashboards and combining them in Excel, you've already lost. Spreadsheets don't scale, they don't audit, and they hide errors until month-end. Month-end close keeps getting longer. What used to take two days now takes a week. Your finance team is spending the last five working days of every month manually reconciling payment data instead of producing management accounts. You're missing chargebacks. Even one missed chargeback deadline is a sign that your dispute management process can't keep up. If it's happening regularly, you're haemorrhaging money. Reconciliation drift exceeds 1%. If the gap between what your system says you collected and what actually landed in your bank accounts is growing, your reconciliation process isn't keeping pace with your transaction volume. Your ops team is growing faster than your transaction volume. Hiring more people to handle payment operations is a temporary fix that doesn't scale. If you need one more ops person for every 5,000 additional daily transactions, your unit economics are heading in the wrong direction. You can't answer "how much did we collect yesterday?" in under five minutes. This is the litmus test. If the answer requires pulling data from multiple sources and running calculations, your reporting infrastructure isn't fit for purpose. ## Why This Gets Worse Before It Gets Better The natural trajectory of a growing platform is more PSPs, not fewer. Enterprise customers mandate their preferred gateway. Geographic expansion requires region-specific providers. Pricing optimisation demands routing flexibility. Being locked to a single PSP becomes a competitive disadvantage. Each additional PSP multiplies the operational burden. If reconciliation with one PSP takes 30 minutes per day, the instinct is to assume two PSPs take an hour. In practice, it takes two hours -- because the cross-referencing, format translation, and exception handling don't scale linearly. This is the payment operations trap: the same business decisions that drive revenue growth (more PSPs, more channels, more geographies) also compound operational complexity. And most platforms don't invest in ops infrastructure until the problem is already painful. ## How to Fix It ### Unified Settlement View The first step is eliminating the need to log into multiple PSP dashboards. Every transaction, every settlement, every fee -- regardless of which PSP processed it -- should appear in a single normalised view. This isn't just about convenience. It's about accuracy. When your finance team works from a single data source that's already reconciled cross-PSP data, the error rate drops dramatically. Month-end close goes from a week to a day. ### Automated Cross-PSP Reconciliation Manual reconciliation doesn't scale. The answer is automated matching: transactions in your system matched to settlement records from each PSP, with exceptions flagged automatically. The key word is "exceptions." Automated reconciliation doesn't mean zero human involvement. It means humans only get involved when something is genuinely wrong -- a missing settlement, a fee discrepancy, an unmatched transaction -- rather than spending hours confirming that everything matches. ### Centralised Chargeback Management Every dispute, from every PSP, should flow into a single queue with unified deadlines, evidence templates, and response tracking. Pattern detection works across PSPs, not within silos. This alone can recover significant revenue. Platforms that move from distributed dispute management to centralised systems typically see chargeback response rates increase from 60-70% to 95%+, simply because deadlines stop getting missed. ### Standardised Refund Workflow Refunds should follow the same process regardless of which PSP processed the original transaction. One initiation point, one tracking system, one reconciliation flow. The underlying PSP mechanics are abstracted away from your ops team. ## The Architecture That Solves This The operational problems described above all share a root cause: multiple direct PSP integrations, each with its own data format, timeline, and process. The fix isn't better spreadsheets or more ops staff. It's an abstraction layer -- a single integration surface that normalises data across all your PSPs. This is what a payment layer provides. Instead of integrating directly with each PSP and managing the operational sprawl that follows, you integrate once. The payment layer handles the PSP-specific translation, normalises settlement data, and presents a unified operational view. With Shuttle, platforms connect to 40+ PSPs through a single integration. Settlement data, chargeback notifications, and refund status are normalised into one format, one dashboard, one reconciliation surface. Your finance team works from a single source of truth regardless of how many PSPs are processing transactions underneath. The operational benefit is immediate: reconciliation that took days becomes automated. Chargeback deadlines stop getting missed. Month-end close shrinks from a week to hours. And critically, adding a new PSP -- whether because an enterprise customer demands it or because you're expanding into a new market -- doesn't add operational burden. It's configuration, not a new ops workstream. ## What Good Looks Like A platform processing 50,000 transactions per day across five PSPs should be able to: - Report total collections for any date range within seconds - Automatically reconcile 99%+ of transactions without human intervention - Respond to 100% of chargebacks within SLA - Process refunds through a single workflow regardless of PSP - Add a sixth PSP without hiring additional ops staff This isn't aspirational. It's table stakes for platforms operating at scale. The question is whether you build this operational infrastructure yourself -- adding months to your roadmap and expanding your team -- or whether you use a payment layer that includes it. For most platforms, payments are infrastructure that supports the core product. The same is true for payment operations. The goal isn't to build a world-class payment ops function. It's to make payment ops invisible -- so your team can focus on the product your customers actually pay for. ## Further Reading - PSP-Neutral vs Single PSP: The Strategic Case for Payment Flexibility - What Is Payment Orchestration? - Payment Layer Explained: Gateway vs Orchestrator vs PayFac vs Payment Layer - How to Migrate Payment Providers Without Downtime ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ### Consent-Based AI Payments: How Agent Transactions Handle User Consent ## Links - [Enterprise customers mandate their preferred gateway](/guides/enterprise-psp-mandates/) - [Being locked to a single PSP](/guides/psp-neutral-vs-single-psp/) - [a payment layer](/guides/payment-layer-explained/) - [enterprise customer demands it](/guides/enterprise-psp-mandates/) - [expanding into a new market](/guides/payment-provider-migration/) - [PSP-Neutral vs Single PSP: The Strategic Case for Payment Flexibility](/guides/psp-neutral-vs-single-psp/) - [What Is Payment Orchestration?](/guides/what-is-payment-orchestration/) - [Payment Layer Explained: Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [How to Migrate Payment Providers Without Downtime](/guides/payment-provider-migration/) - [Book a Call](/discovery/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) - [BlogConsent-Based AI Payments: How Agent Transactions Handle User Consent→](/blog/ai-agent-payment-consent/) --- URL: https://www.shuttleglobal.com/guides/payment-orchestration-vs-payment-layer/ --- # Payment Orchestration vs Payment Layer: Why They're Not the Same | Shuttle > Two Solutions That Sound Similar But Solve Different Problems If you're a software platform evaluating how to add multi-PSP payment support, you'll... # Payment Orchestration vs Payment Layer: Why They're Not the Same By Shuttle Team, January 24, 2026 ## Two Solutions That Sound Similar But Solve Different Problems If you're a software platform evaluating how to add multi-PSP payment support, you'll encounter two categories: payment orchestration and payment layers. If the question is how many providers to hold rather than which category of software to buy, start with single global PSP vs multiple local acquirers. They share surface-level similarities -- both connect to multiple PSPs, both promise to simplify payment infrastructure. But they solve fundamentally different problems, serve different audiences, and require different integration approaches. Choosing the wrong one wastes months and creates technical debt that's expensive to reverse. ## What Payment Orchestration Does Payment orchestration platforms route transactions across multiple PSPs based on rules. They sit between a merchant (or platform) and a set of payment gateways, making decisions about where to send each transaction. Core capabilities: - Smart routing -- Send transactions to the PSP most likely to approve them, based on card type, geography, amount, or historical performance - Failover -- If PSP A declines or is down, automatically retry with PSP B - Tokenisation -- Store card tokens in a vault that works across multiple gateways - Analytics -- Compare PSP performance (authorisation rates, fees, speed) in one dashboard Who it's designed for: Merchants processing high volumes who want to optimise authorisation rates and reduce costs by routing intelligently across their existing PSP relationships. The value proposition: "You already have multiple PSPs. We'll help you route between them better." Key players: Primer, Spreedly, and a growing list of platforms positioning as orchestration solutions. ## What a Payment Layer Does A payment layer embeds multi-PSP payment infrastructure into a software platform -- so the platform's merchants can accept payments through whatever PSP they need, across whatever channel the platform supports. - PSP-neutral payment processing -- Connect to 40+ gateways through a single integration. Merchants choose their PSP or the platform assigns one. - White-label merchant onboarding -- Pre-built onboarding flows branded as the platform's own. Merchants are live in minutes, not weeks. - Multi-channel coverage -- Embedded checkout, voice payments, payment links, chat payments, AI agent payments -- all through the same integration. - Management portal -- Branded dashboard for merchants to view transactions, process refunds, and manage payment settings. - PCI compliance included -- The payment layer carries PCI DSS Level 1 certification. The platform's PCI scope is effectively zero. Who it's designed for: Software platforms that need to embed payment capabilities for their merchants -- where different merchants may require different PSPs, and payments may happen across multiple channels. The value proposition: "Your platform needs to offer payments. We make every PSP and every channel available through one integration -- branded as yours." ## The Core Distinction Here's the simplest way to think about it: Orchestration optimises how an existing merchant routes transactions across PSPs they already have. A payment layer enables a platform to offer multi-PSP payments to merchants who don't have payment infrastructure yet -- or who need their existing PSP to work within the platform's workflows. Payment Orchestration | Payment Layer Primary user | Merchant (or merchant's engineering team) | Platform (embedding payments for many merchants) Core function | Route and optimise transactions across PSPs | Embed multi-PSP payment capabilities into software Merchant onboarding | Not included -- merchant manages PSP relationships directly | White-label onboarding included -- merchants go live in minutes Channel coverage | Online checkout (web/mobile) | Checkout, voice, payment links, chat, AI agents PSP relationships | Merchant brings their own | Merchant brings their own OR platform provides PCI compliance | Reduces scope for tokenisation; card capture still requires PCI setup | Full PCI coverage -- card data never touches the platform Management portal | Analytics dashboard for the merchant | White-label portal for merchants, branded as the platform Time to value | Weeks-months (PSP relationships must exist) | Weeks (PSP configuration included) Commercial model for platform | Not applicable -- orchestration serves the merchant | Merchants keep their own PSP contracts and rates ## Why This Matters for Platforms If you're a software platform -- a SaaS company, a marketplace, a CCaaS provider, an ERP -- and you need to embed payments, here's why the distinction is critical: ### Orchestration doesn't solve the platform problem Orchestration assumes the merchant already has PSP relationships and wants to optimise routing between them. But most platform merchants don't have this setup. They need the platform to provide payment capabilities -- onboarding, checkout, compliance, and all. An orchestration layer gives you multi-PSP routing. It doesn't give you: - A way to onboard merchants onto those PSPs - A branded checkout experience for your merchants' customers - A merchant portal for self-service refunds and reporting - Voice or link-based payment channels - PCI compliance that covers card capture (not just token storage) ### The enterprise PSP mandate problem Here's the scenario that reveals the gap most clearly: Your platform has embedded checkout using Stripe. An enterprise customer says: "We have a Worldpay contract and we're not switching." With an orchestration layer, you'd need Worldpay already configured as a connection. Your enterprise customer would need their own Worldpay account provisioned and connected. And you'd still need to handle onboarding, checkout rendering, and PCI compliance for the Worldpay flow. With a payment layer, you configure Worldpay as an available gateway. The enterprise customer's existing Worldpay credentials are connected during onboarding. Their payments route through Worldpay using the same checkout, the same portal, and the same compliance envelope that every other merchant on your platform uses. It's a configuration change, not an engineering project. ### Multi-channel is the multiplier Orchestration focuses on online checkout -- routing a web transaction to the optimal PSP. But payments increasingly happen beyond checkout: - A contact centre agent takes payment over the phone - An AI voice agent processes a renewal - A payment link is sent via SMS after a service call - A chat agent captures payment mid-conversation Orchestration doesn't cover these channels. A payment layer does -- through the same integration, the same PSP configuration, and the same compliance environment. ## When Orchestration Is the Right Choice To be clear: payment orchestration solves a real problem. It's the right choice when: - You're a merchant (not a platform) processing high volumes across multiple PSPs and want to optimise authorisation rates through intelligent routing - You already have PSP relationships and need a technical layer to manage routing, failover, and retry logic - Your primary goal is transaction optimisation -- improving approval rates, reducing processing costs, A/B testing PSP performance - You don't need to embed payments for others -- your payments are for your own business, not for merchants on your platform If you're processing $100M+ annually and losing revenue to failed authorisations, orchestration can pay for itself through routing optimisation alone. ## When a Payment Layer Is the Right Choice A payment layer is the right choice when: - You're a platform that needs to offer payment capabilities to merchants or customers - Your merchants need PSP flexibility -- different merchants require different gateways - You need white-label payments -- branded onboarding, checkout, and merchant portals - You need multi-channel coverage -- payments happen via checkout, voice, links, chat, or AI agents - You want one integration across every PSP -- earning revenue share on merchant transactions - You don't want PCI compliance burden -- card data stays inside the payment layer's certified environment - You need to go live fast -- weeks, not a multi-quarter engineering project ## The Convergence Question "Won't orchestration platforms add embedding features? Won't payment layers add routing?" Some convergence is inevitable. But the architectures are fundamentally different: Orchestration is built merchant-out -- it starts with transaction routing and adds features around it. The merchant is the primary user. A payment layer is built platform-out -- it starts with embeddability and adds PSP connectivity behind it. The platform is the primary user, and merchants are the platform's customers. Adding white-label onboarding, multi-channel capture, and platform-level merchant management to an orchestration architecture is a ground-up rebuild. Adding smarter routing to a payment layer is a feature. The direction of travel matters. ## FAQ Is a payment layer just orchestration with extra features? No. The architecture is different. Orchestration optimises routing for a merchant's transactions. A payment layer provides payment infrastructure that a platform embeds for its merchants. They share multi-PSP connectivity but differ in who they serve, how they're integrated, and what they include. Can I use both? Technically yes -- a platform could use a payment layer for embedding and an orchestration layer for routing optimisation. In practice, this adds unnecessary complexity. A good payment layer includes routing capabilities, and the added value of standalone orchestration diminishes when the platform layer is handling PSP connectivity. Which has better PSP coverage? Depends on the provider. Orchestration platforms typically connect to 50-100+ gateways. Payment layers may connect to fewer (40+) but include white-label onboarding and multi-channel support for each. Coverage numbers alone don't tell the story -- what matters is whether the PSPs your merchants need are supported, and whether the channels you need are covered. What about Stripe/Adyen -- are they orchestration or payment layers? Neither. Stripe and Adyen are PSPs -- payment gateways that offer platform tools (Stripe Connect, Adyen for Platforms). They're excellent PSPs, but they lock you into their processing network. You can't "orchestrate" to Worldpay through Stripe Connect, and you can't embed Worldpay through Adyen for Platforms. They want to be your only PSP -- which works until an enterprise customer demands otherwise. [CTA section] Need a payment layer, not an orchestration platform? Shuttle gives platforms a single integration for 40+ PSPs across embedded checkout, voice, payment links, and AI agent payments -- with white-label merchant onboarding and PCI DSS Level 1 compliance included. [Book a Demo] | [See Platforms] ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Payment Orchestration Alternatives for Platforms ### Why We Built The Payment Layer ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ## Links - [single global PSP vs multiple local acquirers](/guides/global-psp-vs-local-acquirers/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [payment gateways](/blog/what-is-a-payment-gateway/) - [Book a Call](/discovery/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogWhy We Built The Payment Layer→](/blog/why-we-built-the-payment-layer/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) --- URL: https://www.shuttleglobal.com/guides/payment-provider-lock-in/ --- # How to Avoid Payment Provider Lock-In: A Platform Guide | Shuttle > You signed up with a payment provider because they were easy to integrate, competitively priced, and ticked the right boxes. # How to Avoid Payment Provider Lock-In: A Platform Guide By Shuttle Team, March 17, 2026 You signed up with a payment provider because they were easy to integrate, competitively priced, and ticked the right boxes. Two years later, they've raised fees twice, their support has deteriorated, and you're stuck -- because migrating means losing stored payment tokens, rewriting your integration, and asking every customer to re-enter their card details. This is payment provider lock-in, and it's one of the most common -- and costly -- mistakes platforms make when building their payment infrastructure. ## What Creates Lock-In Lock-in doesn't happen on day one. It builds gradually, through a combination of technical dependencies, commercial terms, and data ownership structures that make leaving progressively more painful. ### Proprietary Payment Tokens When a customer saves their card with your platform, your payment provider stores the actual card number and gives you a token -- a reference ID you can use for future charges. The problem: these tokens only work with the provider that issued them. Stripe tokens don't work with Adyen. Adyen tokens don't work with Worldpay. If you switch providers, every stored card becomes useless. Your customers must re-enter their payment details, which means: - Subscription businesses lose subscribers -- failed rebills from expired tokens create involuntary churn - Marketplaces lose repeat buyers -- friction at checkout drives customers to competitors - Platforms lose merchant trust -- asking merchants to re-onboard their payment setup damages the relationship For a platform with 10,000 stored cards, even a 5% customer loss during migration represents hundreds of lost relationships. ### API Dependencies Every payment provider has a different API. The deeper your integration, the harder it is to leave: - Webhooks and event handling -- your entire order management, fulfilment, and accounting pipeline is wired to provider-specific event formats - Payout logic -- split payments, marketplace disbursements, and platform fees are built around your provider's payout APIs - Fraud rules and risk scoring -- custom fraud rules configured in your provider's dashboard don't transfer - Reporting and reconciliation -- your finance team's workflows depend on provider-specific reporting formats A platform that spent six months integrating Stripe Connect's split payment logic faces another six months rebuilding that logic on a different provider. That's engineering time that could be spent on product features. ### Contract Terms and Exit Fees Some providers lock you in commercially as well as technically: - Volume commitments -- minimum processing volumes with penalties for falling short - Multi-year contracts -- especially common with traditional acquirers and enterprise payment platforms - Exit fees -- charges for early termination or data export - Data portability fees -- some providers charge to export your transaction history and customer data Even providers without explicit contracts create effective lock-in through the sheer cost and complexity of migration. ### Institutional Knowledge Dependency Over time, your engineering team builds deep expertise in your provider's API, quirks, and workarounds. That institutional knowledge has real value -- and it's lost when you switch. The new provider has different edge cases, different error codes, different behaviour under load. ## The Real Cost of Lock-In ### You Can't Negotiate The most immediate cost: you lose leverage. When your provider knows you can't easily leave, they have no incentive to compete on price, support quality, or feature delivery. A platform processing GBP 5M annually that's locked into 2.9% + 20p can't credibly threaten to move to a provider offering 2.4% + 15p. The switching cost -- token migration, engineering time, customer disruption -- exceeds years of savings from the lower rate. Your provider knows this. Their commercial team knows this. Your rate increases will reflect it. ### Forced to Accept Fee Increases Payment providers regularly adjust their pricing. Sometimes it's driven by card network fee changes (interchange increases, scheme fee adjustments). Sometimes it's driven by the provider's own margin targets. When you're locked in, you absorb these increases because the alternative -- migration -- costs more than the price hike. Over time, small increases compound. A platform that started at 2.4% and accepted three annual 0.1% increases is now paying 2.7% -- an effective 12.5% increase in payment costs. ### Token Migration Means Customer Churn If you do decide to switch, token migration is the hardest part. Options include: - Network tokenisation -- Visa and Mastercard offer account updater services that can map old tokens to new ones, but coverage is imperfect and the process takes months - Customer re-entry -- asking customers to re-enter their card details, which always results in some percentage abandoning the process - Parallel processing -- running both old and new providers simultaneously during a transition period, doubling your compliance and operational overhead None of these are clean. All of them carry real risk of lost customers and revenue. ### Innovation Stalls Lock-in doesn't just affect your costs -- it limits your options. Want to add local payment methods in a new market? Your provider might not support them. Want to optimise routing for lower decline rates? You're limited to your provider's acquiring relationships. Want to offer merchants a choice of processors? Your architecture doesn't allow it. Every feature decision is constrained by what your single provider can do. ## How to Avoid Lock-In ### Build PSP-Neutral From the Start The most effective prevention is architectural. Instead of integrating directly with a single payment provider, build (or adopt) an abstraction layer that sits between your platform and the providers. A PSP-neutral architecture means: - One integration to a payment layer, which connects to multiple providers behind the scenes - Provider-agnostic tokens that work across any gateway - Routing flexibility -- send transactions to different providers based on cost, geography, success rates, or merchant preference - Swap providers without code changes -- adding or removing a PSP is a configuration change, not an engineering project This is the approach that enterprise platforms use by default. They've learned -- often the hard way -- that single-provider dependency is an unacceptable business risk. ### Insist on Portable Tokens If you're evaluating payment providers, ask explicitly: - "Can I export my stored payment tokens if I leave?" - "Do my tokens work with other processors?" - "Do you support network tokenisation?" If the answer is no, you're building lock-in from day one. Portable tokens -- where the token is managed independently of any single provider -- are the single most important technical feature for avoiding lock-in. ### Negotiate Data Portability Upfront Before signing with any provider, negotiate data portability terms into your agreement: - Transaction history export -- full history in a standard format (CSV, API access) - Customer payment data -- the ability to migrate stored payment methods - No exit fees -- explicit terms that you can leave without penalty - Reasonable notice periods -- 30 days, not 6 months These terms are much easier to negotiate before you sign than after you've been processing for two years. ### Maintain Multi-PSP Capability Even if you primarily use one provider, maintain the ability to route through others: - Keep at least one backup PSP configured and tested - Run a small percentage of transactions through the backup to keep the integration live - Monitor both providers' performance so you have data to support switching decisions This isn't over-engineering -- it's the payment equivalent of having a disaster recovery plan. ## How to Escape Existing Lock-In If you're already locked in, migration is possible -- it just requires planning. ### Phase 1: Assess Your Exposure Map out exactly what's locked: - How many stored payment tokens do you have? - What percentage of revenue comes from returning customers using stored cards? - How deeply integrated are your systems with provider-specific APIs? - What contractual terms apply to leaving? ### Phase 2: Run Parallel Providers Don't attempt a hard cutover. Run your new provider alongside your existing one: - Route new customers to the new provider - Continue serving existing customers through the old provider - Gradually migrate stored cards using network tokenisation or customer re-entry during natural touchpoints (subscription renewals, account updates) ### Phase 3: Migrate Deliberately Set a timeline -- typically 6-12 months -- to complete migration. Track: - Percentage of transactions on new vs old provider - Token migration success rate - Customer churn attributable to the migration - Cost savings realised ## How Shuttle Eliminates Lock-In Shuttle's payment infrastructure is built specifically to prevent the lock-in problem: - 40+ PSPs connected through a single integration -- add or remove providers without changing your code - Provider-agnostic tokens -- your stored payment data works across any gateway in Shuttle's network, so you never lose customer cards when changing providers - No contracts -- month-to-month, usage-based pricing with no volume commitments or exit fees - Swap providers instantly -- routing changes are configuration, not code. Move from Stripe to Adyen to Worldpay without touching your integration - PCI DSS Level 1 -- Shuttle handles the compliance burden regardless of which providers you use The result: you get the best rates, the best features, and the best support from every provider -- because every provider knows you can leave at any time. That's not just a technical advantage. It's negotiating leverage. ## Key Takeaways Lock-in is a design choice, not an inevitability. Platforms that build PSP-neutral architecture from the start avoid the cost, risk, and frustration of single-provider dependency. Those already locked in can escape with careful planning and parallel migration. The fundamental question is simple: does your payment architecture give you options, or does it give your provider power over you? Related reading: - PSP-Neutral vs Single-PSP: Which Approach Is Right? - Enterprise PSP Mandates: Why Big Customers Force Multi-PSP - When SaaS Outgrows Stripe Connect - Gateway vs Orchestrator vs PayFac vs Payment Layer ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Why You Should Have a Backup Payment Service Provider (PSP) ### Payment Providers: How They Work & How to Choose (2026) ### 7 ways merchants can save money on payment provider fees ### Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared ### Best UK Payment Providers - The definitive guide ### What Is a Payment Gateway? How It Works, Costs & Top Providers ## Links - [PSP-neutral architecture](/guides/psp-neutral-vs-single-psp/) - [enterprise platforms use by default](/guides/enterprise-psp-mandates/) - [Shuttle's payment infrastructure](/platforms/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates: Why Big Customers Force Multi-PSP](/guides/enterprise-psp-mandates/) - [When SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Book a Call](/discovery/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogPayment Providers: How They Work & How to Choose (2026)→](/blog/what-is-payment-gateway-aggregation/) - [Blog7 ways merchants can save money on payment provider fees→](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [BlogFastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared→](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [BlogBest UK Payment Providers - The definitive guide→](/blog/best-uk-payment-providers-the-definitive-guide/) - [BlogWhat Is a Payment Gateway? How It Works, Costs & Top Providers→](/blog/what-is-a-payment-gateway/) --- URL: https://www.shuttleglobal.com/guides/payment-provider-migration/ --- # How to Switch Payment Providers Without Losing Customers | Shuttle > How Do You Switch Payment Providers? Plan three to six months end to end, and follow six steps: audit your current integration, decide whether to move to... # How to Switch Payment Providers Without Losing Customers By Shuttle Team, March 21, 2026 ## How Do You Switch Payment Providers? Plan three to six months end to end, and follow six steps: audit your current integration, decide whether to move to another single PSP or to a PSP-neutral layer, request a PCI-compliant vault-to-vault transfer of your stored cards, run both providers in parallel for at least one full billing cycle, cut over, then monitor for 30 days. A silent card transfer is often available and easy to miss. Major processors can export your stored card data directly to another PCI DSS Level 1 provider. Ask whether yours will, before you plan any customer re-entry campaign. Two things cause most of the damage. Stored cards that cannot be moved, and webhooks that silently stop firing. Plan for both before you write any migration code. The safest migrations never have a cutover date at all. You run old and new side by side and let the old provider drain naturally. ## Why Platforms Switch Payment Providers Nobody switches payment provider for fun. It is one of the highest-risk infrastructure changes a platform can make. The fact that you are reading this means something has already gone wrong with your current setup. The triggers are well documented. They tend to follow a pattern: Account issues. Your PSP freezes funds, applies rolling reserves without warning, or terminates merchants with little explanation. For platforms processing on behalf of sub-merchants, a single compliance flag can cascade across your entire portfolio. Fee pressure. What started as a single headline rate now includes platform fees, payout fees, dispute fees, and monthly minimums. At scale, the blended rate is materially higher than what competitors quote, and your margin is being squeezed from underneath. Lock-in. Your payment tokens are proprietary. Your merchant data sits behind an API you do not control. Switching means re-collecting card details from every customer, which means friction, drop-off, and lost revenue. Missing features. You need voice payments, pay-by-bank, multi-currency settlement, or white-label merchant portals. Your current provider does not offer them, or offers them only through their own branded experience. International expansion. Your platform is growing into markets where your current PSP either has no licence, poor acquiring rates, or limited local payment method coverage. A single-PSP architecture cannot solve this without bolting on separate integrations per region. If you are still deciding how many providers to run rather than which one to move to, see single global PSP vs multiple local acquirers. Any one of these is manageable. Two or three together, and the cost of staying exceeds the cost of switching. ## The Migration Challenge Switching payment providers is not the same as switching any other SaaS tool. Payments touch revenue directly. A botched migration does not cause inconvenience. It causes lost sales, failed renewals, and customer churn. Here is what makes it difficult: ### Token Portability Most PSPs issue proprietary tokens when a customer saves a card. Those tokens only work with the PSP that issued them. If you switch from Stripe to Adyen, every Stripe token becomes useless. Your customers must re-enter their card details. For a platform with 10,000 stored cards, that means 10,000 potential points of failure. A meaningful share of customers never complete re-entry, and every card that does not come across is a subscription that quietly stops billing. Treat this as a revenue event, not a migration task. Some PSPs support network tokens, issued by Visa or Mastercard rather than the gateway. These can survive a provider change, but only when the Token Requestor ID they sit under belongs to you rather than to your PSP. Most PSPs register that ID themselves, which quietly keeps the tokens on their side. Adoption is also inconsistent, and not all card types or regions support them yet. ### API Differences No two PSPs have the same API. Field names differ. Webhook structures differ. Error codes differ. Settlement reporting differs. A migration is not a find-and-replace. It is a re-integration. If your platform has built business logic around your current PSP's API quirks (and it has), that logic needs auditing and rewriting. ### Customer Impact The worst migrations are the ones customers notice. Failed subscription renewals, broken checkout flows, payment confirmation emails that stop arriving. Each of these erodes trust that took years to build. ### Downtime Risk Payment systems do not have maintenance windows. Your merchants expect to process transactions 24/7. Any gap, even minutes, means lost revenue and support tickets. ## Step-by-Step Migration Plan ### Step 1: Audit Your Current Setup Before writing a single line of migration code, document what you actually use today: - Transaction types: one-off payments, subscriptions, pre-authorisations, refunds, partial captures - Stored credentials: how many customers have saved cards, and what token format they use - Webhooks: every webhook you consume and what business logic it triggers - Settlement: how funds flow, what reporting you depend on, and how reconciliation works - Compliance: your PCI scope, who handles cardholder data, and what SAQ level you hold - Multi-currency: which currencies you process, settlement currencies, and FX handling - Disputes: your chargeback workflow, evidence submission process, and win rates This audit reveals your actual integration surface. Teams routinely find it is far larger than expected, because payment logic spreads well beyond the checkout code into billing, reporting, and support tooling. ### Step 2: Choose a PSP-Neutral Architecture This is the single most important decision in your migration. You have two options: Option A: Migrate from one PSP to another PSP. You solve today's problem but create the same lock-in with a different provider. Sooner or later your new PSP raises prices or your merchants demand a different gateway, and you will be back here reading this guide again. Option B: Migrate to a PSP-neutral architecture. You integrate once with an abstraction layer that connects to multiple PSPs. Adding or removing a gateway becomes a configuration change, not a re-integration. Option B costs more upfront but turns the next provider change from a project into a configuration change. The more volume you process, and the more gateways your merchants ask for, the faster that upfront cost pays back. A PSP-neutral approach means your platform can: - Route transactions to different PSPs based on region, cost, or merchant preference - Honour enterprise PSP mandates without custom integrations - Move to a backup PSP if your primary goes down - Negotiate rates with multiple providers simultaneously ### Step 3: Run Parallel Processing Never do a hard cutover. Instead, run your old and new payment paths simultaneously: - New transactions go through the new provider (or abstraction layer) - Existing subscriptions continue on the old provider temporarily - Refunds and disputes for old transactions still route through the old provider Plan for 30 to 90 days of dual running, driven by your subscription billing cycles. The goal is to drain the old provider of active obligations naturally rather than forcing a switchover. During parallel processing, monitor: - Authorisation rates (compare old vs new, since a drop signals configuration issues) - Settlement timing (ensure funds arrive on schedule) - Webhook reliability (confirm all events fire and are processed) - Error rates by card type, region, and currency ### Step 4: Migrate Tokens and Stored Cards This is the hardest part, and it is easy to start in the wrong place. Work through these options in order: PCI-compliant vault-to-vault migration. This is the standard route, and the one teams most often overlook. Major processors can export your stored card data directly to another PCI DSS Level 1 provider, encrypted, with no customer involvement at all. Stripe documents both importing from and exporting to another processor. Adyen documents an equivalent export process, which requires the receiving provider to supply an attestation of compliance and a publicly listed PGP key. Expect to sign a data transfer agreement, evidence your new provider's PCI DSS Level 1 status, and exchange encryption keys. The gating factor is usually whether your current provider will co-operate and how quickly, so ask at the start of the project rather than the end. Network tokenisation. Where a card is provisioned as a Visa or Mastercard network token, that token can survive a provider change, but only if the Token Requestor ID it sits under belongs to you rather than to your PSP. Most PSPs register the TRID themselves, which leaves the tokens inside that provider's umbrella. Find out who owns yours before assuming portability. Gradual re-collection. For cards that cannot be migrated programmatically, trigger re-entry at the next natural interaction point: a subscription renewal, a checkout session, or a payment settings update. Frame it as a security upgrade, not a system change. Bulk re-entry campaigns. As a last resort, email customers asking them to update their payment method. Completion rates on these campaigns are low. Follow up with SMS or in-app prompts for non-responders, and expect to carry a tail of customers who never update at all. The key principle: exhaust the silent options first, because bulk re-entry campaigns cost you customers. Be precise about what a card export actually covers. It moves stored card credentials. It does not move PayPal billing agreements, wallet or device tokens from Apple Pay and Google Pay, SEPA or Bacs direct debit mandates, or network token provisioning. If your subscriptions sit on those rails, each one needs its own migration path, so inventory them during the audit rather than discovering them at cutover. One clarification, because this trips teams up. Account updater services (Visa Account Updater, Mastercard Automatic Billing Updater) are not a migration tool. They refresh credentials a provider already holds when a card is reissued or expires, so the new provider must already have the card on file for them to return anything. Enable them on the new provider once migration is complete, as ongoing credential hygiene. ### Step 5: Cut Over Once parallel processing has run for a full billing cycle and your monitoring confirms parity: - Stop sending new transactions to the old provider - Process final settlements and reconcile - Migrate any remaining active subscriptions - Update webhook endpoints - Decommission the old integration (but keep it available for at least 120 days, since chargebacks routinely arrive that late, and considerably longer if you sell future-dated goods or services) ### Step 6: Monitor Post-Migration The first 30 days after cutover are critical. Watch for: - Authorisation rate changes: even a 1% drop at scale means significant lost revenue - Failed recurring payments: subscriptions that silently stopped processing - Reconciliation gaps: transactions that processed but did not settle correctly - Customer complaints: support ticket volume related to payment failures Set up automated alerts for any of these metrics moving outside normal ranges. ## How to Do It Without Customer Impact The ideal migration is one your customers never notice. Here is how to achieve that: Use a dual-run period. As described above, run old and new providers in parallel. Customers continue transacting normally while you migrate the infrastructure underneath. Make token portability a concrete requirement. If you are choosing a new provider or abstraction layer, do not accept "we support network tokens" as an answer. Ask who the Token Requestor ID is registered to, and get it in writing. Tokens registered under your provider's TRID are migration debt dressed up as portability. Never force card re-entry during checkout. If a customer arrives at checkout and their stored card does not work because of your migration, you have failed. Migrate tokens before they are needed, not when they are needed. Maintain webhook continuity. Your post-payment workflows, including confirmation emails, fulfilment triggers, and accounting updates, must continue firing without interruption. Test this in staging with production-like data before going live. Communicate proactively with merchants, not end customers. Your merchants (if you are a platform) need to know the migration is happening. Their customers should not. ## Why PSP-Neutral Architecture Prevents Future Migrations The reason most platforms end up in a painful migration is architectural: they integrated directly with a single PSP, and now they are coupled to it. A PSP-neutral approach breaks that coupling. Your platform integrates with an abstraction layer with a single API, a single webhook format, and a single settlement report, and that layer handles the PSP-specific translation underneath. When you need to add Adyen for European merchants, you configure it. When an enterprise customer mandates Worldpay, you enable it. When Stripe raises prices, you route volume elsewhere. None of these is a migration in the sense this guide describes. You are configuring and testing a new provider rather than re-integrating your platform. Shuttle connects to a wide range of gateways and payment services through a single integration, listed in the payment providers directory. It tokenises with the gateway rather than holding card data itself, so card portability still depends on network tokenisation and on what your providers support. Shuttle does not make a first migration free. What it changes is the cost of every migration after that. Adding or removing a gateway becomes a configuration change in Shuttle instead of a re-integration in your codebase. There is still work involved: credentials, onboarding, testing, and checking payment method coverage in each market. But it is configuration and testing rather than a rebuild. If your platform is about to outgrow Stripe Connect or any other single-PSP setup, the question is not "which PSP should we migrate to?" It is "how do we make sure the next one is a configuration change?" ## Migration Checklist Use this as a reference when planning your migration: - [ ] Complete integration audit (transaction types, tokens, webhooks, settlement, compliance) - [ ] Decide: migrate to a new single PSP or adopt PSP-neutral architecture - [ ] Set up parallel processing environment - [ ] Establish monitoring dashboards (auth rates, settlement, errors) - [ ] Request a PCI-compliant vault-to-vault card transfer from your current provider (start early, it gates everything else) - [ ] Establish who your Token Requestor ID is registered to, then migrate any portable network tokens - [ ] Map the credentials a card export will not cover (wallet tokens, device tokens, direct debit mandates) - [ ] Execute dual-run period (minimum one full billing cycle) - [ ] Migrate active subscriptions - [ ] Cut over new transactions to new provider - [ ] Run gradual re-collection for unmigrated cards - [ ] Enable account updater on the new provider (credential hygiene after migration, not a migration step) - [ ] Monitor post-migration for 30 days - [ ] Decommission old integration only after the dispute window closes (120 days minimum, longer for future-dated goods) ## Switching Payment Providers FAQ ### How do I switch card payment provider without losing my existing setup? Run both providers in parallel rather than cutting over. Send new transactions to the new provider while existing subscriptions, refunds, and disputes continue on the old one. Your existing setup stays intact throughout. Stop sending it new traffic once the new path has run clean for a full billing cycle, then keep it available until the dispute window closes before you decommission anything. ### How do I switch payment provider without disrupting customers? Migrate stored cards before they are needed, never at the moment of checkout. Ask your current processor for a PCI-compliant vault-to-vault export, which moves saved cards to the new provider without customers touching anything, then collect any remainder at natural touchpoints such as a renewal or a settings update. Customers should never see a re-entry prompt caused by your migration. ### What is a safe migration plan to avoid downtime and protect saved cards and subscriptions? The safe plan has no cutover moment. Audit your integration surface first, stand up the new provider alongside the old, and let subscriptions drain naturally across their billing cycles rather than forcing them across. Monitor authorisation rates, settlement timing, and webhook delivery on both paths in parallel, and only decommission the old integration once the dispute window has closed. Chargebacks commonly arrive up to 120 days after a transaction, and considerably later on future-dated goods and services. ### Will I lose my saved cards when I switch payment providers? Often not, though it depends on your current provider. Stripe and Adyen both document a PCI-compliant vault-to-vault transfer that exports saved cards directly to a new provider with no customer involvement, and many other processors have an equivalent process, though it is not universal. Whether yours will co-operate, and how quickly, is the thing to establish first. Network tokens can also survive a move, but only where the Token Requestor ID belongs to you rather than to your PSP. Confirm both routes with your current provider before you commit to a migration date. ### Can I run two payment providers at the same time? Yes, and for a migration you should. Plan a dual-run period of 30 to 90 days, because that overlap is what removes downtime risk. Running two providers permanently is also viable, and is how platforms honour enterprise gateway mandates or split volume between providers. ### How long does it take to switch payment providers? Plan three to six months end to end. The parallel-running window is 30 to 90 days, driven by your longest subscription billing cycle rather than by engineering time, and the integration work itself is usually shorter than that drain period. Add time at the front for the audit and for negotiating a card export with your current provider, and keep the old integration available for at least 120 days after cutover to handle late refunds and chargebacks. ### How do I switch payment providers without disrupting client billing? Let each client's billing cycle complete on the old provider before moving them. Migrate in cohorts rather than all at once, so a configuration problem affects a handful of clients instead of your whole book. Tell your clients the migration is happening. Their own customers should not need to know. ### What is a realistic plan for replacing in-store terminals across many sites? Stage it by location, not by date. Install and certify the new terminals at one site, run both old and new for a full trading week, then roll out in waves once the reconciliation matches. Terminal estates add hardware logistics and staff retraining on top of the software migration, so treat those as their own workstream. ### How do I switch merchant account providers? The mechanics mirror a gateway migration, with two additions. Underwriting on the new merchant account takes time, so start the application before you plan any technical work. Watch settlement carefully in the first month, because payout timing and reserve terms often differ from your previous agreement even when the processing rate looks similar. ### How do I avoid going through this again? Integrate with a PSP-neutral layer rather than directly with one provider. When your platform talks to a single API that handles the provider-specific translation underneath, changing gateway becomes a matter of configuration and testing rather than a re-integration. That does not remove the first migration, and there is still real work in credentials, onboarding and verifying payment method coverage. But the next change is configuration rather than a rebuild. ## Further Reading - Payment Provider Lock-In: How It Happens and How to Avoid It - PSP-Neutral vs Single-PSP: Which Approach Is Right? - When Your SaaS Outgrows Stripe Connect - Enterprise PSP Mandates: What Platforms Need to Know - Shuttle vs Stripe Connect ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Why You Should Have a Backup Payment Service Provider (PSP) ### Payment Providers: How They Work & How to Choose (2026) ### 7 ways merchants can save money on payment provider fees ### Fastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared ### Best UK Payment Providers - The definitive guide ### What Is a Payment Gateway? How It Works, Costs & Top Providers ## Links - [voice payments](/guides/voice-payments/) - [single-PSP architecture](/guides/psp-neutral-vs-single-psp/) - [single global PSP vs multiple local acquirers](/guides/global-psp-vs-local-acquirers/) - [PCI scope](/glossary/pci-dss/) - [lock-in](/guides/payment-provider-lock-in/) - [enterprise PSP mandates](/guides/enterprise-psp-mandates/) - [PSP-neutral approach](/guides/psp-neutral-vs-single-psp/) - [mandates Worldpay](/guides/enterprise-psp-mandates/) - [payment providers directory](/payment-providers/) - [outgrow Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Payment Provider Lock-In: How It Happens and How to Avoid It](/guides/payment-provider-lock-in/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Enterprise PSP Mandates: What Platforms Need to Know](/guides/enterprise-psp-mandates/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [Book a Call](/discovery/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogPayment Providers: How They Work & How to Choose (2026)→](/blog/what-is-payment-gateway-aggregation/) - [Blog7 ways merchants can save money on payment provider fees→](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [BlogFastest Settlement Payment Providers 2026: Same-Day & Next-Day Payouts Compared→](/blog/speedy-settlement-the-ultimate-guide-to-payment-providers-with-rapid-payouts/) - [BlogBest UK Payment Providers - The definitive guide→](/blog/best-uk-payment-providers-the-definitive-guide/) - [BlogWhat Is a Payment Gateway? How It Works, Costs & Top Providers→](/blog/what-is-a-payment-gateway/) --- URL: https://www.shuttleglobal.com/guides/payment-workflow-automation/ --- # Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) | Shuttle > Why Payment Workflow Automation Matters Most teams collect payments through one of three patterns: a card machine in a shop, a hosted checkout on a... # Payment Workflow Automation: Zapier vs Make.com vs Direct API (2026 Guide) By Shuttle Team, April 26, 2026 ## Why Payment Workflow Automation Matters Most teams collect payments through one of three patterns: a card machine in a shop, a hosted checkout on a website, or an invoice sent by email. None of these scale well to the moments where payment matters most -- the moment a deal is signed, the moment a booking is confirmed, the moment an installation is complete, the moment a renewal is approved. Payment workflow automation closes the gap between the moment of commitment and the moment of payment. When the trigger fires (a deal moves to "Won", a contract is signed, a booking is made), an automated workflow generates a payment link, delivers it to the customer in their preferred channel, and routes the payment outcome back into your CRM, your accounting tool, and your team chat. Done right, this collapses a multi-day chase into a sub-minute conversion. Done at scale, it removes the entire "follow up on the invoice" function from your back office. This guide covers the four real options for building payment workflow automation today: Zapier, Make.com, n8n, and a direct API integration. We'll cover what each is good for, the supported payment gateway list, and concrete workflow templates you can copy. ## The Four Tools That Matter ### Zapier Zapier is the most widely-adopted no-code automation tool, with native connections to 6,000+ apps. Its strength is breadth -- almost any SaaS tool you use is a one-click trigger or action. Workflows ("Zaps") are linear: trigger, action, action, action. Best for: broad app coverage, simple linear flows, ops teams who aren't deeply technical, fast prototyping. Trade-offs: pricing scales with task volume (each step is a billable task), branching scenarios are awkward, error handling is limited. ### Make.com Make.com (formerly Integromat) is a visual scenario builder with deeper branching, error handling, and routing. It connects to 1,800+ apps -- fewer than Zapier, but covering all the payment-relevant ones (CRMs, sheets, chat, document signing, scheduling, messaging). Best for: branching workflows ("if amount > X, route to approval"), high-volume workflows where Zapier's per-task pricing would dominate, scenarios that involve many internal steps. Trade-offs: smaller app catalogue than Zapier, learning curve for the visual builder, naming convention ("operations") is less familiar. ### n8n n8n is the open-source, self-hostable workflow tool. It runs on your own infrastructure (or n8n Cloud), so there's no per-task pricing -- just compute and storage. It supports 400+ native integrations plus generic HTTP and database nodes that cover the long tail. Best for: teams that already run their own infrastructure, workflows with sensitive data that shouldn't leave your systems, very high volume (millions of executions per month). Trade-offs: requires hosting and operations effort, smaller integration catalogue, less polished onboarding than the SaaS alternatives. ### Direct API A direct integration with the Shuttle API (or any payment provider's API) is the most powerful option. You write code that calls the API directly, embed it in your product or back office, and own the workflow end-to-end. Best for: product-embedded payments (your customers pay through your product), very high volume, custom logic that's hard to express in a workflow tool, sub-second latency requirements. Trade-offs: requires engineering time, less flexible to change without redeployment, you own the infrastructure. ## Side-by-Side: When to Use Which Sales-led B2B, ops team owns the workflow Zapier or Make.com Branching scenario ("if X then Y, else Z") Very high volume (>10,000 links/month) n8n or Direct API Self-hosted / data must stay in-house Product-embedded payments Quick prototype with niche SaaS app Zapier (largest app catalogue) Cost-sensitive at moderate volume Make.com (operations are cheaper than tasks) For most teams, the answer is a hybrid: Zapier or Make.com for ops-team workflows (CRM, sales, support), Direct API for product-embedded payments. Many of our customers run all three side by side against the same Shuttle account. ## Supported Payment Gateways for Workflow Automation Shuttle Links Checkout works as a payment-layer abstraction. Whichever workflow tool you use, the same set of payment gateways is available underneath. You can change PSP without rebuilding the workflow. The most commonly automated gateways: - Stripe -- global card processing, the default for SaaS and digital businesses - Adyen -- enterprise-grade, multi-region settlement - Worldpay -- UK and European merchants, strong on traditional retail - Checkout.com -- global, popular with high-growth platforms - Braintree (PayPal) -- bundled with PayPal Wallet - Mollie -- European-first PSP with strong local payment methods - Square -- small business and US-led merchants - GoCardless -- direct debit and recurring collection - PayPal -- direct PayPal account integration - Paysafe, Global Payments, FreedomPay, Authorize.Net, USAePay, Trust Payments -- and more See the full list at our payment providers directory. The same Shuttle Zapier app, Make.com app, or API gives you access to all of them. ## Common Payment Workflow Templates These templates work across Zapier, Make.com, n8n, and direct API -- only the implementation differs. ### Template 1: CRM stage change → payment link Trigger: A deal moves to "Closed Won" (or any custom stage) in HubSpot, Pipedrive, Salesforce, or Close. - Trigger fires when the deal stage changes - Pull the deal value, customer email, and any reference fields - Generate a Shuttle payment link with those details - Send the link to the customer by email or SMS - Optional: post a Slack message to the team channel Best for: B2B SaaS, agencies, consulting, anyone with a sales-led pipeline. ### Template 2: Proposal accepted → deposit collected Trigger: A proposal in PandaDoc, Docusign, Proposify, or Better Proposals is marked as accepted. - Trigger fires on signature event - Pull the proposal value and customer details - Generate a Shuttle payment link for the agreed deposit (often 25-50% of total) - Email the link to the customer with a "thanks for signing -- here's the deposit" message - If unpaid after 48 hours, send a follow-up - If unpaid after 7 days, cancel the link and flag the deal Best for: agencies, consultancies, professional services, installer businesses (where deposits matter). ### Template 3: Slack command → payment link Trigger: A team member types in a Slack channel. - Slack slash command fires the workflow - Parse the message for amount and description - Generate a Shuttle payment link - Reply in the same Slack channel with the link - Optional: post a "link sent" message in a payments-tracking channel Best for: sales, support, and ops teams that want to take payment from any conversation without leaving Slack. ### Template 4: Form submission → calculated payment link Trigger: A customer submits a Typeform, Jotform, Tally, or Google Form. - Form submission fires the workflow - Calculate the total based on the form responses (quantities, options selected, region) - Generate a Shuttle payment link with the calculated amount - Redirect the customer to the link, or email it to them - On payment, fire downstream actions (delivery ticket, CRM update, mail list add) Best for: custom orders, event registration, lead-to-payment funnels, marketplaces. ### Template 5: Booking made → upfront payment Trigger: A customer books a paid consultation or service in Calendly, Acuity, or SavvyCal. - Booking webhook fires - Check the meeting type or service - Generate a Shuttle payment link for the agreed amount - Email the link with a "pay before the call" message - If unpaid 1 hour before the meeting, cancel the booking Best for: consultants, coaches, therapists, professional services with paid time slots. ### Template 6: Inbound chat / WhatsApp → payment link reply Trigger: A customer messages your business on WhatsApp Business, Intercom, Front, or a website chat. - Inbound message webhook fires - (Optional) AI agent or human agrees the amount with the customer - Reply in the same conversation with the link - On payment, post a "paid" confirmation back to the chat Best for: retail, hospitality, conversational commerce, agentic-commerce flows. ### Template 7: Multi-step "payment received" fan-out Trigger: A Shuttle "Payment Received" event fires. - Post the payment to a Slack channel - Update the CRM record with the paid status - Create an invoice in QuickBooks, Xero, or Sage - Add the customer to a Mailchimp audience (for upsell or onboarding) - Generate a delivery ticket in your warehouse system - Send the customer a thank-you email Best for: any team that wants payment to fire a downstream sequence rather than just landing in a bank account. ## Implementation by Tool ### Zapier setup - Search for "Shuttle Links Checkout" in Zapier's app library - Authenticate with your Shuttle API key - Build the Zap: trigger → Shuttle "Generate Payment Link" → delivery action - (Optional) Build a second Zap with the Shuttle "Payment Received" trigger for the downstream fan-out - Test, switch on Full guide to Shuttle + Zapier setup → ### Make.com setup - Search for "Shuttle Links Checkout" in Make.com's app catalogue - Build the scenario: trigger module → Shuttle "Generate Payment Link" module → routing/filtering → delivery module - Use Make's visual builder for branching logic - (Optional) Build a second scenario for "Payment Received" downstream actions Full guide to Shuttle + Make.com setup → ### n8n setup - Use n8n's HTTP Request node to call the Shuttle API directly (POST /links) - Build the workflow with native n8n nodes for triggers and downstream actions - Use n8n's expression language for any conditional logic - Self-host or use n8n Cloud ### Direct API setup - Get your API key from the Shuttle dashboard - POST to /links with amount, currency, description, customer email, and metadata - Subscribe to webhooks for payment events - Embed in your product or back-office system ## Frequently Asked Questions ### What payment gateways does Shuttle support for workflow automation? Shuttle supports 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, GoCardless, PayPal, Paysafe, Global Payments, FreedomPay, Authorize.Net, USAePay, and Trust Payments. The same Zapier app, Make.com app, or API gives you access to all of them -- change PSP without rebuilding the workflow. ### Is Make.com or Zapier cheaper for payment automation? Make.com is typically cheaper at scale because it bills per "operation" and operations cost less than Zapier's "tasks". For workflows with multiple internal steps (filtering, routing, formatting), Make.com pulls ahead on price quickly. Zapier is competitive at low volume and for very simple linear flows. ### Can I switch from Zapier to Make.com without rebuilding? You'll need to rebuild the workflow in the new tool -- the workflow logic doesn't transfer between platforms. But the Shuttle side stays identical: the same API, the same payment gateways, the same payment links. Only the orchestration tool changes. ### Do I need a developer to build payment workflows? No. Both Zapier and Make.com are no-code. Most teams have a non-technical ops person own the payment workflows. You only need a developer if you're going down the direct API route. ### Can I use multiple workflow tools in parallel? Yes. Many of our customers run Zapier for one set of workflows and Make.com (or direct API) for others. They all hit the same Shuttle account, so you get one settlement stream and one set of payment data regardless of how the link was created. ## Where to Start Pick the workflow with the highest pain right now. For most teams, that's one of: - The deposit you keep chasing on accepted proposals -- automate via PandaDoc/Docusign trigger - The CRM deal that gets stuck in "Closed Won -- awaiting payment" -- automate via the CRM stage change - The Slack channel where someone keeps asking for payment links -- automate via slash command Pick one, ship it in an hour, see the conversion lift, then expand from there. The biggest mistake teams make is trying to design a comprehensive payment workflow up front. Start with one trigger, one delivery channel, and one downstream action -- the rest builds on top. For a deeper walkthrough of the Zapier or Make.com integration specifically, see: - Shuttle + Zapier: how it works - Shuttle + Make.com: how it works - HubSpot payment links via workflow automation - Best payment link providers (UK) ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### 5 Payment Workflows That Work Better With Payment Links ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Xero Payment Links: Collect Invoice Payments Faster ### Payment Reminder Email Templates (With Pay Now Links) ## Links - [payment providers directory](/payment-providers/) - [Full guide to Shuttle + Zapier setup →](/platforms/links-checkout/workflows/zapier/) - [Full guide to Shuttle + Make.com setup →](/platforms/links-checkout/workflows/make/) - [Shuttle + Zapier: how it works](/platforms/links-checkout/workflows/zapier/) - [Shuttle + Make.com: how it works](/platforms/links-checkout/workflows/make/) - [HubSpot payment links via workflow automation](/guides/hubspot-payment-links/) - [Best payment link providers (UK)](/guides/take-payments-online/best-payment-link-services-uk/) - [Book a Call](/discovery/) - [Blog5 Payment Workflows That Work Better With Payment Links→](/blog/5-real-merchant-workflows-that-work-better-with-payment-links/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogPayment Reminder Email Templates (With Pay Now Links)→](/blog/payment-reminder-email-templates/) --- URL: https://www.shuttleglobal.com/guides/payments-for-ccaas-implementation-partners/ --- # Payments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments | Shuttle > If you implement Genesys, Five9, Talkdesk, NICE, RingCentral, Zoom Contact Center or any of the major CCaaS platforms, you already know what happens... # Payments for CCaaS Implementation Partners: How SIs Deliver PCI-Compliant Voice Payments By Shuttle Team, May 13, 2026 If you implement Genesys, Five9, Talkdesk, NICE, RingCentral, Zoom Contact Center or any of the major CCaaS platforms, you already know what happens partway through every serious enterprise rollout. The customer asks how the contact centre is going to take payments. You can route the call. You can transcribe it. You can hand it to an AI voice agent. You can pop the CRM record. But the moment someone reads a 16-digit card number into a recorded, transcribed, AI-summarised voice channel, the project hits a wall -- PCI scope, compliance review, security architecture rework, procurement delays. System integrators absorb the cost of that wall. Either the payments piece falls out of scope and the customer is unhappy, or the SI is forced to integrate a third-party voice payment vendor mid-deployment -- a separate contract, a separate engagement, a separate timeline. This guide is for CCaaS implementation partners -- the AppFoundry, AppConnect, App Gallery, DevConnect and AppHub partners who deliver enterprise-grade CCaaS deployments -- and how to deliver payments as part of every rollout without becoming a payments company. ## The Implementation Partner's Payment Problem Your value proposition to the customer is straightforward: you take the platform out of the box and turn it into a working contact centre that fits their business. Routing rules, IVR design, CRM integration, AI agent training, reporting, change management. You sell the outcome, not the licence. But every enterprise CCaaS deployment has the same buried requirement. The customer takes inbound payments -- utilities collecting bills, insurance carriers collecting premiums, councils collecting penalty charges, retailers collecting deposits, healthcare practices collecting copays, debt agencies collecting plans. The contact centre is where those payments get made. And the customer expects you, the integrator, to make that work. So far, partners have had three options. Refer to a third-party voice payments vendor. Specialist voice-payment vendors integrate at the CCaaS layer. They work, but they're a separate sales cycle, a separate procurement, a separate set of contracts, and pricing that surprises customers when they see it as a line item. The SI is sourcing a piece of the deployment they can't control or co-sell. Tell the customer to handle it post-launch. Carve payments out of the scope of work. The CCaaS platform goes live, the customer collects payments via a separate website portal or a legacy IVR, and the deployment delivers on the proposal -- but the customer never reaches the unified contact centre vision you sold them. Build a custom integration. Stand up a Twilio Pay flow or write a custom card capture into a third-party telephony bridge. Now the integrator owns PCI scope, indirectly. The custom code becomes a maintenance liability. The deployment goes live, and the SI inherits the operational risk every quarter. None of those options scale across deployments. None of them let the partner monetise the payment piece. And none of them give the customer the single-vendor experience they signed up for. ## Why CCaaS Vendors Don't Ship Payments Natively Every CCaaS vendor knows about this gap. None of them solve it natively. Genesys, Five9, NICE, RingCentral, Talkdesk -- the contact centre vendors build routing, AI, workforce optimisation, analytics. They don't build payment processing because payments are a different discipline with different certifications, different vendors, different operational risks, and different liability profiles. The PCI DSS certification alone takes 12 to 18 months to achieve and costs hundreds of thousands of pounds annually to maintain. It's also a non-strategic move for them. Owning the payment relationship would commit them to a single PSP and lock out the customers who already have processor relationships with Adyen, Worldpay, Chase, Elavon or one of thirty other gateways. Enterprise CCaaS customers will not switch their payment processor to satisfy a contact centre roadmap. The result: the platform exposes telephony, IVR and screen-pop hooks, and leaves the payment integration to the partner ecosystem. That's the gap implementation partners can either close -- or get blocked by. ## What "Payment-Ready" CCaaS Deployments Actually Need When a customer asks for payment functionality in a contact centre rollout, they usually mean four things, even if they don't articulate them that way. 1. Live agent voice collection with limited PCI scope. A customer on the phone reads their card number to the agent. The card data must not enter the CCaaS recording, transcription, or storage layers. The agent stays on the call, the customer never leaves, and the platform's PCI scope stays limited. This is the DTMF clamping / pause-and-resume / agent-assist pattern -- and it's the bedrock of every voice payments deployment. 2. AI voice agent payment capture. Customers calling in are increasingly hitting an AI voice agent first. The agent triages, schedules, answers account queries -- but when the customer says "I'd like to pay my bill," the AI shouldn't drop them back to a human queue. It should capture the payment securely inside the same conversation. That requires the AI to invoke a payment flow without ever seeing the card data. See PCI-compliant payments for AI voice agents for the architecture pattern. 3. SMS / link-out fallback for self-service. Some customers prefer to pay themselves. The agent (or the AI) sends a hosted payment link via SMS or email mid-call. The customer completes payment on their own device. The agent sees confirmation in the same workflow. No card data on the call. 4. CRM and ticket reconciliation. The payment outcome must land back in the customer's CRM, billing system or service ticket -- automatically. If the integrator has wired Salesforce, HubSpot, ServiceNow, Zendesk or a custom CRM into the deployment, payment events should populate those records the same way a call disposition does. A "payment-ready" deployment delivers all four. Anything less leaves the customer with a half-finished contact centre. ## The Implementation Partner Model Shuttle is built so that implementation partners can include payments in every deployment as a co-sold component -- not a referral. Pre-built CCaaS integrations. Genesys AppFoundry, Five9 App Marketplace, NICE CXexchange, Talkdesk AppConnect, Amazon Connect (via NeuraFlash partners and direct), Zoom App Marketplace, RingCentral App Gallery, Avaya DevConnect, Cisco Webex App Hub, 8x8 Marketplace, Dialpad Integrations, Sprinklr Marketplace, Vonage App Center. Implementation partners deploy the integration in days rather than building it from scratch. PSP-neutral execution. Customers keep their existing PSP -- Stripe, Adyen, Worldpay, Chase, Elavon, Braintree, Checkout.com, GoCardless, and 40+ others. Shuttle routes the transaction to the customer's processor. The integrator doesn't need to negotiate processor switches as part of the deployment scope. Voice, links and embedded checkout from one integration. A single integration powers live agent voice payments, AI voice agent payments, SMS payment links, embedded checkout, and pay-now buttons. Partners don't need to pick a category -- every deployment ships with the full set. PCI DSS Level 1 hosted by Shuttle. Card data never enters the CCaaS platform or the customer's infrastructure. PCI scope is minimised by architecture, not configuration. The customer's compliance review accelerates, not stalls. Partner economics. Integrators participate in the deal commercially. Shuttle pays partners on transaction volume routed through their deployments -- turning the payment piece from a scope cost into a recurring revenue line. The deeper your CCaaS book, the more material the partner economics become. ## A Typical Implementation Flow Here's what a payment-ready CCaaS rollout looks like when payments are part of the integrator's standard delivery, not an add-on. Discovery. During the standard contact centre discovery, the integrator asks the usual call flow questions -- and one additional question: where in the call flow do customers currently pay? The answer surfaces the payment volume, the channels (voice, link, IVR), and the PSPs already in use. Solution design. The payment flow is documented as part of the same call flow diagram the integrator produces for routing, IVR, AI agent, and CRM. Pay points are marked. The agent script is written once. The AI agent prompt includes the payment handover. The SMS template is drafted alongside the post-call SMS templates the integrator is already building. Integration. The CCaaS platform is provisioned with the Shuttle integration -- typically from the partner marketplace. Shuttle is connected to the customer's PSP (or PSPs) via configuration. The CRM webhook lands payment events back into the customer's record system. Pilot. The integrator pilots payment flows alongside the rest of the deployment. Agents test pause-and-resume on a few transactions. The AI agent test scripts include payment intents. The SMS link template is reviewed by the customer's marketing team. Go-live. Payments go live the same day the rest of the contact centre does. The customer doesn't have a separate "phase 2" for payments. The integrator delivered the full vision. Operate. Shuttle handles PCI scope, processor relationships, and reconciliation infrastructure. The integrator owns the customer relationship, the deployment health, and the change requests -- the same as every other part of the contact centre. ## Why This Matters for the SI Practice For a CCaaS practice -- Salesforce + Amazon Connect, Genesys, Five9, NICE, RingCentral or any combination -- embedding payments into the standard delivery changes the practice economics. Deal size grows. A contact centre deployment that includes payments is a larger engagement than one that excludes them. Discovery time goes up, but so does the SOW value. Customers buy more from a single partner. Procurement closes faster. Customers stop sequencing the deployment around a separate voice payments vendor. The legal review for a third-party PCI vendor disappears. The compliance team reviews one integration, not three. Renewals stick. Customers who consolidate payments into the CCaaS deployment renew the engagement at higher rates because the integrator owns more of the day-to-day. Switching costs increase. The partner relationship deepens. Recurring revenue. Transaction-volume revenue share creates an annuity that scales with the customer's call volume -- not with the SI's billable hours. The integrators that embed payments earliest get a structural advantage in their CCaaS practice. The ones that don't keep referring out -- and watch a slice of every deal go to a third party who isn't a CCaaS specialist. ## What's Different About This vs Twilio Pay or Specialist Payment Vendors Some integrators have built custom payment flows on Twilio Pay or referred out to specialist voice-payment vendors. Both are reasonable historical answers. Neither was designed for the modern CCaaS partner. Twilio Pay is a developer toolkit, not a partner-ready product. You build the flow yourself, you maintain the PCI scope of the integration, and it's limited to Twilio-based telephony. If the customer's CCaaS sits on a different stack -- Genesys, NICE, Five9, RingCentral -- Twilio Pay isn't a fit. See Twilio Pay alternatives and the partner model for the full breakdown. Specialist voice-payment vendors solve secure voice capture well. They work, but they're standalone vendors with their own commercial model and limited partner economics for the integrator. They typically centre on voice capture rather than payment links, AI agent flows, or embedded checkout. The integrator carries the relationship without participating in it. Shuttle is built to slot into a partner-led delivery model. The integrator owns the customer, embeds Shuttle into the deployment, and ships a unified payment experience across voice, links, AI and embedded checkout -- without taking card data into their own systems or holding the PSP relationships. ## Related Reading - Embedded Payments for CCaaS Platforms -- the platform-side view of the same problem - PCI-Compliant Payments for AI Voice Agents -- the architecture pattern for AI agent payments - PCI-Compliant Payments for Contact Centres -- the full hub covering 20+ CCaaS platforms - Agentic Payments for Platforms -- the ICP positioning piece for AI-led CX vendors - Voice Payments: The Complete Guide -- covering DTMF, masking, AI voice, and platform integration - CCaaS Payments Revenue Opportunity -- the business case for adding payments to a contact centre engagement - Enterprise PSP Mandates: Why Customers Need Multiple Gateways -- the constraint that drives PSP-neutral architecture Shuttle is The Payment Layer for CCaaS deployments. Pre-built integrations into every major contact centre platform. One integration, any customer PSP. Voice, AI, links and embedded checkout. PCI DSS Level 1, ISO 27001, and SOC 2 certified. [See the partner programme](/partners/) or [book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF clamping](/guides/dtmf-payments/) - [PCI-compliant payments for AI voice agents](/guides/ai-voice-agent-pci-payments/) - [40+ others](/payment-providers/) - [Twilio Pay alternatives and the partner model](/guides/twilio-pay-connectors/) - [Embedded Payments for CCaaS Platforms](/guides/embedded-payments-for-ccaas/) - [PCI-Compliant Payments for AI Voice Agents](/guides/ai-voice-agent-pci-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Agentic Payments for Platforms](/guides/agentic-payments-for-platforms/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [Enterprise PSP Mandates: Why Customers Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/payments-for-erp-platforms/ --- # Embedded Payments for ERP Platforms | Shuttle > Every ERP platform has billing. Almost none execute payments. The accounts receivable module records the invoice. It tracks the due date. # Embedded Payments for ERP Platforms By Shuttle Team, May 17, 2026 Every ERP platform has billing. Almost none execute payments. The accounts receivable module records the invoice. It tracks the due date. It logs the customer. It drives the ageing report. When the customer eventually pays -- by BACS transfer, by card on a separate portal, by a posted cheque, by a finance team manually keying a payment -- the ERP records the receipt and reconciles. It does not, in most platforms, initiate or capture the payment itself. This guide is for ERP platforms -- from horizontal mid-market suites to vertical-specific ERPs in commerce, manufacturing, distribution and field service -- and how to close that gap by adding embedded payment execution without becoming a payments company. ## Why ERP Platforms Don't Execute Payments The reasons are structural, the same ones that keep most B2B platforms out of payment execution. PCI compliance. The moment an ERP touches card data, PCI DSS applies. For a platform that handles general ledger entries, inventory, manufacturing routings, project accounting and customer master data, taking on PCI scope means new audit cycles, new security controls, and a security posture that the rest of the product roadmap doesn't justify. Customers won't switch their PSP. A mid-market manufacturer using Adyen for B2B card collection won't switch to your gateway because your ERP only supports it. A distributor using Worldpay won't migrate either. ERP customers expect the platform to fit into their existing finance stack -- including the processor relationships their treasury team has already negotiated. Payments aren't the engineering priority. ERP roadmaps are bottomless. Inventory enhancements, multi-entity consolidation, manufacturing planning, project costing, statutory tax reporting in fifteen jurisdictions -- the backlog is structural. Building a multi-PSP, multi-channel payment infrastructure inside the ERP would consume engineering capacity that's already over-allocated. Liability. Carrying funds -- even briefly -- is a regulated activity. ERPs that briefly held customer money would need money-transmission or e-money licences in the jurisdictions they operate. Most ERP vendors don't want that liability profile. The result: the ERP records the obligation. The customer pays through a separate channel. The platform sits at the centre of the finance operation but doesn't touch the moment of payment. ## What "Embedded Payments" Looks Like Inside an ERP There's a difference between an ERP that has a "Pay" button and an ERP that has embedded payments. A "Pay" button routes the customer to a third-party portal. The user leaves the ERP. The transaction completes in someone else's branded checkout. The ERP gets a webhook back (sometimes) and reconciles. The customer's perception is that the ERP is a billing front-end and a separate site handles payment. Embedded payments mean the payment execution happens inside the ERP workflow. The customer never leaves. The invoice email contains a pay-now flow that completes in the same UI. The AR clerk processing an invoice can take the payment in the ERP. The customer portal exposes the same payment surface inside the ERP brand. Reconciliation isn't a webhook-and-pray flow; it's a native field on the invoice record. For ERP platforms with a self-service customer portal (most modern mid-market and SMB ERPs), embedded payments transform the portal from a billing-statement viewer into a billing-and-payment workspace. That's where the customer experience competitive advantage lives. ## The Four AR Workflows That Embed Cleanly When ERP vendors add embedded payments, four workflows tend to absorb most of the volume. 1. Invoice email pay-now. The standard outbound invoice email -- generated by the ERP -- carries a hosted payment link that opens to a Shuttle-hosted payment page branded for the ERP customer (the merchant, not the ERP itself). The customer pays card or account-to-account. The payment lands back on the invoice record in real-time. See invoice payment links and the B2B pay-now invoice pattern for the deeper mechanics. 2. Customer portal one-click pay. The customer-facing portal shows outstanding invoices. A pay-now control on each invoice -- or a "pay all" control on the AR ledger -- initiates payment inside the portal. Card-on-file, BACS direct debit and SEPA mandate options are surfaced based on what the customer's account has authorised. 3. AR clerk-assisted payment. The clerk taking a customer call (or processing a manual payment instruction) initiates the payment from inside the ERP invoice screen. For card payments, the customer is sent a payment link or completes through Voice Checkout if the call centre is integrated. No card data ever lands in the ERP -- but the clerk's workflow is single-screen. 4. Recurring AR and direct debit mandates. For subscription and recurring B2B billing -- common in SaaS, telecoms, utilities and managed services on top of ERP -- the ERP captures the mandate once and Shuttle executes on the schedule. Failed payments retry automatically; dunning surfaces back into the ERP's AR module. These four cover most of what a customer means when they ask the ERP vendor to "support payments natively." Across these flows, the ERP platform is the system of record. Shuttle is the payment execution layer. ## Multi-PSP Without the Integration Burden The structural reason ERP platforms have stayed away from embedded payments is the multi-PSP requirement. Every ERP customer has its own processor relationship. The platform can't dictate which. Shuttle solves the multi-PSP problem at the architecture layer. Customers connect their existing PSP -- Stripe, Adyen, Worldpay, Chase, Elavon, Braintree, GoCardless, Checkout.com, and 40+ others -- and Each merchant is configured against their own processor. The ERP integrates once. Each customer's transactions flow through their own processor relationship with their own merchant pricing, their own settlement schedule, and their own statement. That changes the economics for the ERP vendor. Instead of building thirty processor integrations (and maintaining them through every API version bump for the next decade), the vendor integrates Shuttle once and the multi-PSP coverage is inherent. For the deeper architecture discussion, see PSP-neutral vs single-PSP architecture and enterprise PSP mandates. ## The Revenue Model Payment execution isn't just a feature -- it's a revenue line for the ERP vendor. For an ERP processing materially-sized B2B payment volume across its customer base, the embedded payment revenue can rival or exceed module subscription revenue within a few years. For vertical ERPs in commerce, distribution and field service -- where transaction volume per customer is high -- the impact is meaningful from quarter one. ## Vertical ERP Patterns Commerce ERPs (JTL, Actindo, distribution suites). High invoice volume, mix of B2B and B2C payment patterns, multi-currency, marketplace and channel-driven order flow. Embedded payments slot into customer portals and inbound order acknowledgements. Manufacturing and project ERPs. Project-based invoicing, milestone payments, retention and stage payments. Embedded payments handle scheduled invoicing and mid-project disbursements. Recurring services billed alongside one-off project work in the same payment flow. Field service ERPs. Service-call-driven invoicing, often with mobile-engineer card-present capture at the customer site, plus follow-up payment links for outstanding balances. See field service payment collection for the field-side pattern. Open-source / extensible ERPs (Frappe / ERPNext, Odoo-style). Multi-tenant deployments by implementation partners, with payment configuration per tenant. Implementation partners earn on transaction volume the same way CCaaS implementation partners do -- embedded payments become a recurring revenue stream for the partner ecosystem, not just the ERP vendor. Vertical-specific finance ERPs (Rillet and similar). Accounting-led ERPs where the invoice and the GL entry are the primary objects. Embedded payments turn the platform from an accounting record into an end-to-end AR workflow. ## Build vs Integrate The build-vs-integrate decision for ERP platform payments comes down to the same two questions every B2B platform faces. 1. Can you justify the engineering investment? Building multi-PSP payment execution -- with PCI compliance, multi-currency, card and account-to-account methods, mandate management for recurring billing, and per-customer routing -- requires 12 to 18 months of dedicated development and significant ongoing compliance investment. That's engineering capacity diverted from the modules your customers are actually buying. 2. Can you justify the ongoing operational overhead? Every PSP integration requires version management, certification renewals, monitoring and incident response. Multiply by the number of acquirer relationships your customer base demands. Add PCI audit cycles and statutory compliance reporting in each jurisdiction. The operational cost compounds annually. The alternative: integrate once with The Payment Layer. 40+ PSPs supported. Embedded checkout, payment links, voice and recurring direct debit. PCI handled. New customer PSPs onboard in days, not engineering cycles. The ERP ships embedded payments without building payment infrastructure. For the broader build-vs-integrate framework, see Build vs Buy: Payment Infrastructure for Platforms. ## Related Reading - Embedded Payments Without Becoming a PayFac -- why most platforms shouldn't own the payment relationship - Invoice Payment Links -- the canonical pattern for invoice-led payment flows - Pay-Now Buttons on B2B Invoices -- the buyer-side experience - Get Payments Off Your Roadmap -- the engineering-leadership argument - PSP-Neutral vs Single-PSP Architecture -- when PSP flexibility matters - Enterprise PSP Mandates: Why Customers Need Multiple Gateways -- the constraint that drives PSP-neutral architecture - Payment Layer Explained: Gateway vs Orchestrator vs PayFac vs Payment Layer -- the category framework Shuttle is The Payment Layer for ERP platforms. One integration. Any customer's PSP. Embedded checkout, invoice links, AR portals, recurring direct debit and voice -- branded for each customer. PCI DSS Level 1, ISO 27001, and SOC 2 certified. [See how it works for platforms](/platforms/) or [book a discovery call](/discovery/). ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Adyen for Platforms Alternatives ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ## Links - [invoice payment links](/guides/invoice-payment-links/) - [the B2B pay-now invoice pattern](/guides/pay-now-button-invoices/) - [40+ others](/payment-providers/) - [PSP-neutral vs single-PSP architecture](/guides/psp-neutral-vs-single-psp/) - [enterprise PSP mandates](/guides/enterprise-psp-mandates/) - [field service payment collection](/guides/take-payments-online/field-service/) - [CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [40+ PSPs](/payment-providers/) - [building payment infrastructure](/guides/get-payments-off-your-roadmap/) - [Build vs Buy: Payment Infrastructure for Platforms](/guides/build-vs-buy-payment-infrastructure/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Invoice Payment Links](/guides/invoice-payment-links/) - [Pay-Now Buttons on B2B Invoices](/guides/pay-now-button-invoices/) - [Get Payments Off Your Roadmap](/guides/get-payments-off-your-roadmap/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates: Why Customers Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Payment Layer Explained: Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Book a Call](/discovery/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) --- URL: https://www.shuttleglobal.com/guides/payments-for-insurance-carriers-mga/ --- # Payments for Insurance Carriers and MGA Platforms | Shuttle > Policy administration systems are the operational heart of insurance carriers and MGAs. # Payments for Insurance Carriers and MGA Platforms By Shuttle Team, May 18, 2026 Policy administration systems are the operational heart of insurance carriers and MGAs. They underwrite, rate, bind, endorse, renew, cancel, and adjudicate claims. They issue the invoices for premium and they record the disbursements on claims. What they generally do not do is execute the underlying money movement. Premium collection happens through a separate billing portal, a separate IVR, a separate cards-on-file system or a separate direct debit bureau. Claims disbursement happens through the carrier's treasury workflow, a separate ACH/Bacs file, sometimes a third-party prepaid card vendor. The PAS sits at the centre of the policy lifecycle but cedes the moment of money movement to a perimeter of point solutions. That perimeter is increasingly the bottleneck. New product launches stall on payment configuration. Cross-border programmes hit acquirer constraints. MGA delegated authority programmes need flexible per-MGA routing that the carrier's central infrastructure was never designed to support. And the customer-experience expectation -- driven by personal lines disruption and embedded insurance -- is for premium and claims flows that feel native, not bolted on. This guide is for PAS vendors, MGA platforms, carrier platform teams and the technology partners that serve them -- and how Shuttle's Payment Layer slots into the PAS workflow as a single embedded payment execution layer. ## Why PAS Platforms Don't Execute Payments PAS vendors built deep expertise in policy administration. Payment execution is a separate discipline with separate certifications. PCI scope. Card data inside a PAS environment triggers PCI DSS scope across the policy, claims and customer master systems. That's a multi-year compliance project layered on a platform that was certified for other things. Acquirer relationships are carrier-specific. A regional carrier has Worldpay. A national carrier has Adyen. A specialty MGA has Chase. A direct-to-consumer brand uses Stripe. The PAS serves all of them. Forcing a single processor through the platform is commercially impossible -- the carriers already have their merchant pricing negotiated. Multi-jurisdictional payment methods. Premium collection in the UK leans on direct debit (Bacs). The US uses ACH for recurring and card for one-off. Continental Europe needs SEPA. Latin America wants local debit and instalments. Each method has different mandate, dispute and reconciliation rules. The PAS team isn't staffed to maintain that breadth. Claims disbursement is regulated. Paying a claim is a regulated activity in most jurisdictions -- anti-money-laundering checks, beneficiary verification, sometimes tax withholding. PAS vendors aren't licensed money-services businesses and don't want to be. The result: the PAS handles every part of the policy except the moment money changes hands. ## What "Carrier-Side" Payments Look Like Carrier and MGA payment flows differ structurally from broker-side or distribution-side payments. A useful distinction. Premium collection. Recurring, mandate-driven, often multi-instalment, often net of premium financing. Payment frequency tied to policy cadence (monthly, annual, mid-term endorsements). Direct debit dominant in some markets, card dominant in others. First-payment-on-bind is often card while ongoing collection switches to direct debit. Mid-term adjustments. Endorsement-driven pro-rata charges and refunds. Often the friction point -- refunds in particular are slow and manual in most legacy stacks. Modern PAS deployments expect these to be near-instant from the customer's perspective. Renewal collection. Annual or semi-annual cycle, often the moment of churn. Friction at renewal -- declined cards, expired mandates, payment-method changes -- is a leading cause of involuntary lapse. Smart retry and proactive mandate maintenance materially reduce lapse rate. Claims disbursement. Outbound payments to policyholders, repair networks, healthcare providers, replacement vendors. Faster Payments / RTP / instant payouts increasingly expected in personal lines. Bulk-file ACH/Bacs still the default in commercial and specialty. Premium financing reconciliation. Where the policy is financed (especially commercial lines and high-premium personal), the PAS reconciles between the financing provider and the underwriter. Payment infrastructure has to settle correctly to two counterparties. MGA delegated authority programmes. The carrier's PAS may host multiple MGAs with delegated underwriting authority, each with its own brand, its own premium collection, its own bank account, sometimes its own acquirer relationship. The platform needs per-MGA routing without per-MGA engineering. A payment layer that supports all of these -- card, direct debit, ACH/Bacs, SEPA, instant payouts, multi-acquirer routing, multi-MGA segregation -- is the unlock. Most PAS vendors haven't built one because it's a different platform underneath. ## Where Shuttle Fits Inside a PAS Shuttle integrates with the PAS as the payment execution layer behind the policy and claims modules. Inbound premium collection. At bind, at endorsement, at renewal, the PAS calls Shuttle to capture or charge. Hosted payment pages, mandate capture, card-on-file collection -- all branded for the carrier or MGA, all routed to that entity's chosen PSP. Webhooks reconcile to the policy record in real-time. Direct debit / ACH / SEPA mandates. Mandate capture, schedule execution, retry rules, dunning and adjustment flows. The PAS owns the policy schedule; Shuttle executes it. Failed payments surface back as exceptions on the policy record. Claims disbursement. Outbound payments via Faster Payments / RTP, ACH and SEPA bank transfer, or push-to-card where supported. Beneficiary verification and basic AML screening sit at the payment layer; underwriting and adjustment sit at the PAS. Voice channel premium collection. Call centres handling renewal calls, hardship cases and mid-term endorsements often capture payment on the call. Shuttle's Voice Checkout runs on Twilio Pay today (voice requires being a Twilio customer), capturing the card in a secure PCI DSS Level 1 flow so card data never enters the carrier's contact centre. There is no native CCaaS integration: the carrier builds the agent-side trigger against Shuttle's APIs, and a packaged integration is available as a paid project. One honest caveat: full-call presence is not yet turnkey; returning the caller to the same agent after payment works today when the carrier builds the return route in Twilio and passes a conversation ID. Shuttle works with Twilio today, and any carrier coming soon. Multi-MGA routing. Each MGA configured on the PAS has its own brand, its own acquirer, its own settlement account. Each MGA is configured against their own gateway and settles per the MGA's commercial agreement. The PAS doesn't carry MGA-specific integration code. AI voice agent collection. Carriers running AI voice agents in their contact centres can capture payment securely at the point of payment rather than escalating to a human. The carrier builds its own agent interface against Shuttle's APIs; a packaged platform integration is available as a paid project. See PCI-compliant payments for AI voice agents for the architecture pattern. ## How This Differs From The Insurance Core Platform Guide This guide deliberately separates carrier and MGA platform patterns from the broader insurance core platform pattern and the broker / distribution-platform pattern. The audiences and the workflows are different. A broker platform is distributing policies sold by underwriters. The payment flow on a broker platform is typically a first-money collection at the point of sale and a hand-off to the underwriter's collection cycle thereafter. A carrier / MGA platform -- what most PAS vendors serve -- is the underwriter. Premium collection is the full lifecycle, claims disbursement is core, regulatory and treasury obligations attach to the carrier rather than the distributor. Payment infrastructure has to support the full set, not just the point-of-sale moment. OneShield, Genasys, and the other PAS vendors building modern carrier and MGA infrastructure are the platforms this guide is written for. ## Why Carriers Want Their PAS to Handle Payments Carrier teams have a particular set of incentives that drive demand for native PAS payment execution. Renewal retention. Mandates that survive renewal cycles, smart retry on declined first-bind payments, instant repair of expired cards. Carriers can quantify the basis-point impact of involuntary lapse reduction on retained premium. Cycle time on launching new products. A carrier launching a new product line -- a new commercial line, a new personal lines proposition, a new MGA programme -- moves faster when payment configuration is a setting, not an engineering project. PAS vendors who can ship payment-ready new programmes win deals. Customer experience parity with personal lines disruptors. Embedded insurance and digital-native personal lines brands have set a customer-experience bar around instant claims payout, frictionless renewal and seamless mid-term changes. Traditional carrier stacks that cede payment execution to legacy systems can't match that bar without modernising the payment layer. Premium financing flexibility. Commercial lines and high-premium personal lines depend on premium financing arrangements. Payment infrastructure that reconciles cleanly to financing partners removes friction from the most material part of the commercial book. Multi-MGA scaling. Carriers running multiple MGA programmes on a single PAS need payment routing flexibility. PAS vendors who can offer that out of the box win the MGA-platform deals. PAS vendors who embed Shuttle hit all of these without becoming a payments company. ## Build vs Integrate The build-vs-integrate question for PAS platforms is sharper than for most B2B software, because the regulatory overlay is real. Building multi-PSP, multi-method, multi-jurisdiction payment infrastructure inside a PAS would require: - PCI DSS Level 1 certification - Money-services regulatory registration in each operating jurisdiction (where holding funds is contemplated) - ACH, Bacs, SEPA and Faster Payments / RTP scheme participation or sponsor arrangements - AML and KYC infrastructure for outbound claims payment - Per-PSP integration and maintenance across the global PSP landscape - Mandate management infrastructure for recurring direct debit across jurisdictions That's not a feature -- that's a separate company. The alternative: integrate once with The Payment Layer. 40+ PSPs supported. Inbound and outbound flows in one integration. PCI scope held outside the PAS. Per-carrier and per-MGA routing without per-deployment engineering. For the broader build-vs-integrate framework, see Build vs Buy: Payment Infrastructure for Platforms. ## Related Reading - Payments for Insurance Core Platforms -- the broader insurance platform guide covering broker and distribution patterns - PCI-Compliant Payment Architecture for Insurance Platforms -- the technical deep dive on limited-scope architecture - AI Voice Payments for Insurance -- the AI voice agent collection pattern for insurance - Embedded Payments Without Becoming a PayFac -- why most platforms shouldn't own the payment relationship - Enterprise PSP Mandates: Why Customers Need Multiple Gateways -- the constraint that drives PSP-neutral architecture - Insurance Payment Solutions: Alternatives Compared -- the buying-side comparison of insurance payment vendors Shuttle is The Payment Layer for insurance carriers, MGAs and PAS vendors. One integration powers inbound premium collection, recurring mandates, claims disbursement, voice and AI agent capture -- routed to any acquirer, branded per carrier or MGA. PCI DSS Level 1, ISO 27001, and SOC 2 certified. [See how it works for platforms](/platforms/) or [book a discovery call](/discovery/). ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Why Insurance Call Centres Still Can't Take a Secure Payment ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ## Links - [Voice Checkout](/platforms/voice-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI-compliant payments for AI voice agents](/guides/ai-voice-agent-pci-payments/) - [insurance core platform pattern](/guides/payments-for-insurance-platforms/) - [40+ PSPs](/payment-providers/) - [Build vs Buy: Payment Infrastructure for Platforms](/guides/build-vs-buy-payment-infrastructure/) - [Payments for Insurance Core Platforms](/guides/payments-for-insurance-platforms/) - [PCI-Compliant Payment Architecture for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [AI Voice Payments for Insurance](/guides/ai-voice-payments-insurance/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Enterprise PSP Mandates: Why Customers Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [Insurance Payment Solutions: Alternatives Compared](/alternatives/insurance-payment-solutions/) - [Book a Call](/discovery/) - [BlogWhy Insurance Call Centres Still Can't Take a Secure Payment→](/blog/insurance-call-centre-payments/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) --- URL: https://www.shuttleglobal.com/guides/payments-for-insurance-platforms/ --- # Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure | Shuttle > Every insurance core platform has billing. Almost none execute payments. Billing modules handle invoices, installment schedules, delinquency tracking, and... # Payments for Insurance Platforms: Embed Multi-PSP Payment Infrastructure By Shuttle Team, January 25, 2026 Every insurance core platform has billing. Almost none execute payments. Billing modules handle invoices, installment schedules, delinquency tracking, and reconciliation. They manage the record of what's owed. But when it's time to actually collect the money -- capture a card, route to a processor, confirm the transaction -- the platform hands off. The carrier figures it out. A third-party system takes over. The customer leaves the platform workflow. This is the gap between billing and payment execution. And it's the single biggest missed opportunity for insurance core platforms today. ## Why Insurance Core Platforms Don't Execute Payments The reasons are structural, not accidental. PCI compliance is the first wall. The moment card data enters a platform's infrastructure, PCI DSS applies. For a core platform that manages policy data, claims, and billing across dozens of carriers, adding PCI scope introduces a compliance burden that most product teams rightly avoid. Every carrier uses a different PSP. Allianz has its processor. AXA has another. A regional mutual uses a third. An insurance core platform serves all of them -- but can't force them onto a single payment gateway. This multi-PSP requirement makes direct gateway integrations impractical. Building one integration per carrier per PSP doesn't scale. Payments aren't the core competency. Insurance platforms are built by teams that understand policy administration, actuarial models, and claims workflows. Payment infrastructure is a different discipline with different certification requirements, different vendors, and different operational risks. The result: billing is table stakes. Payment execution is the missing layer. ## The Three Ways Carriers Solve Payments Today When the platform doesn't execute payments, carriers default to one of three workarounds: 1. Separate payment portal. The carrier sets up a standalone payment page -- disconnected from the core platform. Policyholders navigate away from the platform workflow to pay. Reconciliation between the payment portal and the billing module is manual or semi-automated. Data lives in two places. 2. Manual phone collection. Agents read card numbers over the phone, type them into a terminal, or transfer the caller to an IVR system. This works but creates PCI scope for the contact centre, compliance risk for the carrier, and a poor experience for the customer. 3. Paper and batch processing. Checks, direct debit mandates, and bank transfers processed outside the platform. Reconciliation is slow. Delinquency detection lags. Cash flow forecasting is unreliable. All three approaches share the same problem: the payment happens outside the platform. The platform knows what's owed but can't collect it. The carrier owns the payment relationship, and the platform has no visibility, no revenue participation, and no ability to improve the experience. ## What Native Payment Execution Looks Like When payment execution is embedded inside the insurance core platform, the entire dynamic changes. Premium collection during a voice call. A policyholder calls about a renewal. The agent -- human or AI -- confirms the premium amount, triggers a secure payment capture within the conversation, and the payment is processed through the carrier's PSP before the call ends. No transfer to IVR. No "please go online." Card data never touches the platform. Payment links for overdue premiums. The billing module identifies an overdue installment. The platform sends a branded payment link via SMS or email. The policyholder pays in two taps. The payment settles through the carrier's existing processor. Reconciliation is automatic. Embedded checkout in the policy portal. A new policyholder purchases a policy through the carrier's digital channel. The checkout component is embedded in the platform's UI -- white-labelled, carrier-branded. The card is tokenised, stored securely, and used for recurring premium collection without the policyholder re-entering details. AI agent payment capture. An AI voice agent handles a collections call for an overdue premium. The agent confirms the amount, the policyholder enters card details via DTMF, and the payment processes -- all within the automated conversation. No human intervention. PCI compliance handled by The Payment Layer. In each case, payment execution is native to the platform workflow. The carrier doesn't need a separate payment system. The platform captures the transaction. ## The Multi-Tenant PSP Problem This is the structural challenge that makes insurance platform payments different from merchant payments. A single insurance core platform might serve 20 carriers. Each carrier has its own processing agreement -- with Stripe, Adyen, Worldpay, or a regional acquirer. Enterprise carriers mandate their PSP. It's in their procurement contracts. It's not negotiable. A platform that integrates with one PSP serves one carrier. A platform that needs to serve all carriers needs to either: - Build and maintain 20 separate PSP integrations (years of engineering, ongoing maintenance) - Force all carriers onto one PSP (impossible -- they'll refuse) - Use a PSP-neutral payment layer that supports any PSP through a single integration The third option is what The Payment Layer provides. One integration from the platform. Any PSP per carrier. No re-engineering when a new carrier onboards with a different processor. Allianz runs call centre payments through Shuttle across 3 countries -- each routing to Allianz's contracted processors. Adding a new country or a new PSP is configuration, not development. ## PCI Compliance Architecture For insurance platforms, PCI scope is the make-or-break constraint. ### Limited Scope for the Platform The architecture that works: card data never enters the platform's environment. Payment capture -- whether via DTMF on a voice call, a hosted payment page, or a payment link -- happens within The Payment Layer's PCI DSS Level 1 certified infrastructure. The platform receives only redacted data: last four digits, transaction status, settlement confirmation. This means: - The platform stays at SAQ-A -- the lightest PCI self-assessment - Not SAQ-D -- the full assessment (300+ requirements, annual QSA audit, $200K+ per year) - The carrier's scope stays limited for platform-initiated payments - Call recordings contain no card data -- DTMF tones are stripped before they reach the recording system ### What This Saves PCI DSS Level 1 certification costs upwards of $2M to achieve and maintain. For an insurance core platform that isn't in the business of processing payments, carrying that burden makes no strategic sense. The Payment Layer carries it instead -- PCI DSS Level 1, ISO 27001, and SOC 2 certified. For the full technical architecture, see our guide on how AI voice agents take PCI-compliant payments. ## Voice Payments for Insurance Insurance is a voice-heavy industry. Phone renewals, collections calls, claim payments, policy inception -- millions of these conversations happen daily, and a significant percentage involve a payment moment. Phone renewals. A policyholder calls to renew. The agent confirms the premium, triggers DTMF capture, and the payment processes within the call. Or an AI voice agent handles the entire renewal autonomously. Collections calls. An overdue premium triggers an outbound call -- automated or agent-assisted. The payment is captured mid-conversation through secure DTMF entry. No "please call back during business hours." No "we'll send you a letter." Claim payments. A settled claim payment is issued via payment link or direct transfer, triggered from the claims module and routed through the carrier's PSP. PolyAI -- whose AI agents handle conversations across regulated industries including insurance -- processes voice payments with a 75% completion rate and zero human handoffs: "Shuttle let us treat legacy payment providers as a modern SaaS service. It enabled us to support the gateways our customers required and fully automate high-value transactions across regulated industries." ## Payment Links for Insurance Payment links are the fastest path to collecting overdue premiums and reducing delinquency. The billing module identifies an overdue installment. The platform sends a branded link via SMS or email. The policyholder opens it, sees the amount and policy reference, enters payment details, and pays. Settlement routes through the carrier's PSP. The billing module updates automatically. Why this matters for insurance: - Reduces delinquency -- policyholders pay immediately instead of waiting for a letter or logging into a portal - Works across carriers -- each link routes to the correct PSP for that carrier - Limited PCI scope -- the payment page is hosted by The Payment Layer, not the platform - Branded -- the policyholder sees the carrier's name and branding, not a third party ## The Revenue Model Payment execution isn't just a feature. It's a revenue line. For insurance core platforms, the math is compelling. Policy premiums are high-value, recurring transactions. A platform processing premium collections for even a fraction of its carrier base generates material revenue from day one. ## Build vs Integrate The build-vs-buy decision for insurance platform payments comes down to two questions: 1. Can you justify the engineering investment? Building multi-PSP payment execution -- with PCI compliance, voice payment support, payment links, and per-carrier routing -- requires 12+ months of dedicated development and $2M+ in compliance investment. That's engineering capacity diverted from policy administration, claims, billing, and every other feature your carriers are actually paying for. 2. Can you justify the ongoing maintenance? Each PSP integration requires monitoring, version updates, certification renewals, and incident response. Multiply by the number of carriers. Add PCI audit cycles. The operational cost compounds. The alternative: integrate once with The Payment Layer. 40+ PSPs supported. Voice, links, embedded checkout. PCI handled. New carriers onboard in days. The platform ships payment execution without building payment infrastructure. For a detailed comparison, see Gateway vs Orchestrator vs PayFac vs Payment Layer. ## Related Reading - Embedded Payments Without Becoming a PayFac -- why most platforms shouldn't own the payment relationship - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways -- the enterprise constraint that drives multi-PSP adoption - PSP-Neutral vs Single-PSP Architecture -- when PSP flexibility matters - PCI-Compliant Payments for Contact Centres -- the full guide to human and AI agent payment flows - Payment Orchestration vs Payment Layer -- why orchestration doesn't solve the platform problem - PCI-Compliant Payment Architecture for Insurance Platforms -- the technical deep dive on limited-scope architecture Shuttle is The Payment Layer for insurance core platforms. One integration. Any carrier's PSP. Voice, links, and embedded checkout. PCI DSS Level 1, ISO 27001, and SOC 2 certified. [See how it works for platforms](/platforms/) or [book a discovery call](/discovery/). ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Why Insurance Call Centres Still Can't Take a Secure Payment ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Adyen for Platforms Alternatives ## Links - [PCI scope](/glossary/pci-scope/) - [payment link](/merchants/links-checkout/) - [DTMF](/guides/dtmf-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [Enterprise carriers mandate their PSP](/guides/enterprise-psp-mandates/) - [PSP-neutral payment layer](/guides/psp-neutral-vs-single-psp/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [how AI voice agents take PCI-compliant payments](/guides/ai-voice-agent-pci-payments/) - [40+ PSPs](/payment-providers/) - [building payment infrastructure](/guides/get-payments-off-your-roadmap/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [PCI-Compliant Payment Architecture for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [Book a Call](/discovery/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogWhy Insurance Call Centres Still Can't Take a Secure Payment→](/blog/insurance-call-centre-payments/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) --- URL: https://www.shuttleglobal.com/guides/payments-for-invoicing-erp-platforms/ --- # Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure | Shuttle > The Invoicing Platform Payment Problem Invoicing and ERP platforms sit at the exact point where money is owed. They generate invoices. # Payments for Invoicing & ERP Platforms: Embed Multi-PSP Payment Infrastructure By Shuttle Team, January 26, 2026 ## The Invoicing Platform Payment Problem Invoicing and ERP platforms sit at the exact point where money is owed. They generate invoices. They track receivables. They manage billing cycles, credit terms, and payment schedules. They know who owes what, when it's due, and how overdue it is. But the actual payment? That happens somewhere else. The customer gets a PDF. They log into their bank. They type in a reference number and an amount. Maybe they enter card details into a completely separate system. Maybe they send a bank transfer and misspell the reference, and the finance team spends an hour matching it up. This is the gap. Invoicing platforms control the entire lifecycle of a transaction -- except the one step that generates revenue. The platforms that close this loop -- invoice generated, payment captured, reconciliation automatic -- win. They reduce DSO. They reduce support tickets about "has this been paid?" They reduce the manual reconciliation grind that finance teams deal with daily. The ones that don't close it remain document generators. Sophisticated, feature-rich document generators. But document generators nonetheless. Every invoicing platform knows this. The question isn't whether to add payments. It's how to do it without turning your ERP product into a payments project. ## Why Invoicing and ERP Is Different Invoicing platforms don't operate like ecommerce checkout. The payment dynamics are fundamentally different, and getting this wrong is why generic payment integrations fail in the invoicing space. ### Transaction Amounts Vary by Orders of Magnitude A small business invoice might be £50. An enterprise B2B invoice might be £500,000. The risk profile, the payment method, and the processing requirements are completely different at each end. A one-size-fits-all checkout that works for £50 often doesn't support the controls, authentication, and settlement requirements of a six-figure B2B payment. ### Enterprise Customers Mandate Their PSP This is the one that catches invoicing platforms off guard. You integrate Stripe. It works. Then a large enterprise customer says: "We process all payments through Worldpay. It's in our treasury policy. Non-negotiable." You either support their PSP or you lose them. And the next enterprise customer will have a different mandate. ### Reconciliation Matters More Than Checkout UX In ecommerce, checkout conversion rate is everything. In invoicing, reconciliation is. Can the platform automatically match a payment to an invoice? Can it mark it as paid, update the ledger, trigger the next invoice in the sequence? Can it handle partial payments against an invoice without manual adjustment? The payment experience matters. But the back-office automation behind it is where invoicing platforms live or die. ### Payment Links, Not Checkout Pages The primary payment channel isn't a storefront. It's an email. An invoice goes out with a "Pay Now" link. The customer clicks, sees the amount, chooses their payment method, pays, and the invoice is automatically marked as settled. This means payment links are the killer feature -- not embedded checkout on a website. The link has to be brandable, support multiple payment methods, and feed data back to the invoicing system in real time. ### Multi-Currency Is Standard, Not Optional International invoicing means multi-currency support from day one. A platform serving UK and EU clients needs to issue invoices in GBP and EUR, process payments in both currencies, and handle FX considerations. A payment solution that only supports a single currency is immediately disqualifying. ### Accounting System Integration Invoicing platforms integrate with QuickBooks, Xero, Sage, and dozens of other accounting tools. Payment data needs to flow into these systems cleanly -- matched to invoices, with the right references, in the right currency, with fees accounted for. A disconnected payment flow that requires manual journal entries defeats the purpose. ## How Invoice Stack Embedded Multi-PSP Payments Invoice Stack is an invoicing platform. Their customers -- merchants -- use Invoice Stack to generate and manage invoices. When it came time to add payment capabilities, they hit the same wall that every invoicing platform hits. ### The Problem Invoice Stack's customers didn't share a single PSP. Some used Stripe. Some used Worldpay. Some used regional processors with specific acquiring relationships. Building and maintaining individual integrations to each of these PSPs was not feasible -- not without hiring a dedicated payments engineering team and taking on PCI compliance obligations. The options were: - Pick one PSP and standardise. This meant telling enterprise customers "you have to use our PSP" -- which meant losing enterprise customers. - Build integrations one by one. Possible in theory. In practice, each PSP integration takes months, requires PCI-compliant infrastructure, and needs ongoing maintenance. Three PSPs means three sets of documentation, three sets of API changes, three sets of edge cases. - Find a payment layer that handles multi-PSP through a single integration. One integration. Every PSP their customers need. PCI compliance handled. They chose option 3. They chose Shuttle. ### The Result Invoice Stack integrated once with Shuttle's payment layer. Through that single integration, their merchants could connect their own PSPs -- whichever gateway their business already used or their policies mandated. > "Shuttle let us add payments without having to own or manage payments ourselves. Our customers can bring their own gateways, and we were able to improve the payment experience and scale without hiring a payments or finance team." -- Harry Bevan, Invoice Stack The key outcomes: - No payments team required. Invoice Stack didn't hire payment engineers or a compliance team. Shuttle handles the payment infrastructure, PCI compliance, and PSP connectivity. - Merchant PSP choice preserved. Each merchant on Invoice Stack can connect their preferred PSP. No forced migration. No "you have to use Stripe." - Payment links embedded in invoices. Every invoice generated through Invoice Stack can include a branded "Pay Now" link. Customers click, pay, and the invoice is automatically reconciled. - Limited PCI scope. Invoice Stack doesn't store, process, or transmit card data. Shuttle carries PCI DSS Level 1 compliance as a service provider. Invoice Stack's PCI obligation drops to nothing. - Scale without hiring. As Invoice Stack's customer base grew, the payment infrastructure scaled with it. No additional headcount. No infrastructure scaling issues. ## What Invoicing Platforms Actually Need If you're building or running an invoicing platform and evaluating how to add payments, here's the capability checklist that matters. These aren't nice-to-haves. They're the requirements that separate "we added payments" from "payments actually work for our customers." ### Payment Links This is the primary channel. Every invoice should have the option of a "Pay Now" link -- delivered via email alongside the invoice, or embedded in a customer portal. The link should: - Be branded as the platform (white-label), not as a third-party payment provider - Support card, bank transfer, and digital wallets (Apple Pay, Google Pay) - Pre-populate the amount, reference, and merchant details - Return payment status via webhook so the invoicing system can auto-reconcile ### Multi-PSP Support Enterprise customers bring their own PSPs. A payments layer should support 40+ PSPs through a single integration, so that onboarding a new merchant with a different gateway is a configuration step -- not a development project. ### White-Label The payment experience should carry the platform's brand. The merchant's customer should see the platform's name and logo on the checkout page, not a third-party provider. This matters for trust, for brand consistency, and for the platform's positioning as a complete invoicing solution. ### Recurring and Subscription Payments Invoicing platforms that handle subscription billing need to capture card details once and charge on a schedule. Tokenisation, stored payment methods, and automated retry logic are required. ### Partial Payments B2B invoicing often involves partial payments -- deposits, milestone payments, staged settlements. The payment system needs to accept a partial amount against an invoice and update the outstanding balance accordingly. ### Multi-Currency Sterling, Euro, Dollar, and beyond. The platform needs to process payments in the currency of the invoice, with clear settlement and reporting. ### Automatic Reconciliation When a payment completes, a webhook fires. The invoicing platform matches the payment to the invoice, updates the status, adjusts the ledger, and triggers any downstream actions (next invoice in sequence, receipt generation, accounting system sync). Zero manual matching. ### PCI Compliance The platform should not handle card data. A PCI DSS Level 1 certified payment layer means card data never enters the invoicing platform, which keeps its PCI scope limited. No cardholder data environment to secure, no penetration testing on one, and far less compliance overhead. ## Payment Links: The AR Automation Engine Accounts receivable teams spend an enormous amount of time on one question: has this invoice been paid? They send invoices. They wait. They follow up. They check bank statements. They match payments to invoices manually -- especially when the payment reference doesn't match, the amount is slightly off, or the payment arrived from an unexpected account. Payment links eliminate most of this work. ### From PDF to Instant Payment The traditional flow: - Generate invoice - Send PDF via email - Customer receives PDF - Customer logs into bank, enters details, transfers funds - Finance team checks bank feed, matches payment to invoice - Invoice marked as paid (maybe days later) The payment link flow: - Send invoice with "Pay Now" link - Customer clicks link, pays immediately via card, bank transfer, or wallet - Webhook fires, invoice auto-marked as paid - Accounting system synced in real time ### Reducing DSO Days Sales Outstanding (DSO) is the metric that finance teams obsess over. It measures how long it takes to collect payment after an invoice is issued. Average B2B DSO across industries hovers around 40-55 days. Late payments cost UK businesses an estimated £22 billion annually. Payment links compress DSO by removing friction. The customer doesn't need to remember to pay. They don't need to log in anywhere. They click a link in the same email as the invoice. The easier you make it to pay, the faster money arrives. ### Automated Reminders Combine payment links with automated reminders and the AR function becomes largely self-running. Invoice sent on day 1 with a payment link. Reminder on day 14 -- same link. Escalation on day 30 -- same link, different tone. Each reminder includes the exact same one-click path to payment. ### Payment Status Visibility Platform operators and their merchants see payment status in real time. Not "we sent the invoice and we're waiting" but "link opened, payment initiated, payment completed" or "link sent, not opened after 7 days -- trigger escalation." This visibility transforms AR from a reactive function into a proactive one. ## Three Approaches to Adding Payments Every invoicing platform evaluating payment capabilities will weigh three paths. ### Approach 1: Build In-House Integrate directly with one or more PSPs. Build your own checkout experience. Handle PCI compliance. Maintain the integrations as PSP APIs evolve. Timeline: 6-12 months for a single PSP integration with proper PCI compliance. Longer for multi-PSP. Cost: $2M+ for PCI DSS Level 1 certification alone. Ongoing engineering resource for maintenance, updates, and support. Advantages: Full control. No third-party dependency. Disadvantages: Massive distraction from your core invoicing/ERP product. Every month spent on payment infrastructure is a month not spent on the features your customers actually chose you for. And you still only support the PSPs you've built integrations for -- until an enterprise customer demands one you haven't. Verdict: This is the #1 competitor to any payment infrastructure provider. Not because it's the best option, but because engineering teams default to "we'll build it." The reality: 12 months later, you have one PSP integration, a PCI compliance burden, and a product roadmap that's been hijacked by payments. ### Approach 2: Single PSP Integration Integrate with Stripe, Adyen, or another major PSP. Use their hosted checkout or payment links. Fast to implement, well-documented, and solves the immediate problem. Timeline: Days to weeks. Cost: Low upfront. Transaction fees per payment. Advantages: Fast. Simple. Proven. Disadvantages: PSP lock-in. Your platform is now married to that PSP's capabilities, pricing, and limitations. The first time an enterprise customer says "we use Worldpay, not Stripe" -- and they will -- you have no answer. You either lose the customer or start building a second integration, which puts you back on Approach 1. Verdict: Works for early-stage platforms with SMB customers who don't have PSP mandates. Falls apart the moment enterprise enters the picture. ### Approach 3: Payment Layer (Multi-PSP) Integrate once with a payment layer that connects to 40+ PSPs. Each merchant on your platform configures their own PSP. Payment links, checkout, reconciliation, and compliance are handled by the layer. Timeline: Weeks. One integration. Merchants self-configure. Cost: Usage-based. No PCI certification to fund. No payment engineering hires. Advantages: PSP-neutral. Enterprise customers bring their own gateway. New PSPs are a configuration step, not a dev project. PCI compliance handled. Payment links built in. Scales without hiring. Disadvantages: Third-party dependency. You're relying on the payment layer's uptime, PSP coverage, and roadmap. Verdict: The approach that Invoice Stack and other invoicing platforms use. One integration. Any PSP. Payment links from day one. A far lighter compliance load. ## Implementation: What It Looks Like For invoicing platforms evaluating the payment layer approach, here's how implementation typically works. ### API-Generated Payment Links When an invoice is created in your platform, your backend calls the payment layer's API to generate a payment link. The API accepts the amount, currency, reference, and merchant ID. It returns a branded URL. You embed that URL in the invoice email as a "Pay Now" button and display it in your customer portal. ### PSP Configured Per Merchant Each merchant on your platform connects their PSP through a white-label onboarding flow. They enter their gateway credentials (or complete an OAuth flow), and the payment layer handles connectivity. Merchant A uses Stripe. Merchant B uses Worldpay. Merchant C uses Adyen. Your platform doesn't care -- it's one API regardless. ### Webhooks for Reconciliation When a payment is completed, the payment layer sends a webhook to your platform. The webhook contains the invoice reference, amount paid, currency, payment method, and transaction ID. Your platform matches this to the invoice, marks it as paid (or partially paid), updates the ledger, and syncs with the merchant's accounting system. ### White-Label Checkout The payment page the customer sees carries the merchant's branding -- or your platform's branding, depending on your model. Logo, colours, domain. The customer sees the invoicing platform's experience, not a third-party payment page. ### Merchant Self-Service Merchants access a white-label portal to view transaction history, process refunds, download settlement reports, and manage their PSP configuration. This reduces your support burden and gives merchants the visibility they expect. ## FAQ Can invoicing platforms offer payments without becoming a PayFac? Yes. A payment layer like Shuttle handles the regulatory and compliance requirements. The invoicing platform never processes, stores, or transmits card data. There's no need to register as a Payment Facilitator. You embed payment capabilities without taking on payment obligations. What PSPs can merchants connect? Through a multi-PSP payment layer, merchants can connect 40+ PSPs including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and regional processors. New PSPs are added to the layer -- your platform's integration doesn't change. How do payment links work with existing invoicing workflows? Payment links are generated via API when an invoice is created. The link is embedded in the invoice email or customer portal. When clicked, the customer sees a branded checkout pre-populated with the invoice amount, reference, and merchant details. On payment, a webhook updates the invoice status automatically. What about partial payments? The payment layer supports partial payments. If a customer pays less than the full invoice amount, the payment is recorded and the outstanding balance is updated. This is common in B2B invoicing for milestone-based billing or staged payments. How long does integration take? Typical integration takes weeks, not months. The core work is API calls to generate payment links and webhook handlers for reconciliation. There's no PCI compliance infrastructure to build, no gateway-specific code, and no payment-specific hiring required. Is multi-currency supported? Yes. Payment links can be generated in any currency supported by the merchant's PSP. The invoicing platform issues invoices in the appropriate currency, and the payment link matches. ## Close the Payment Loop Invoicing platforms that generate the invoice but don't capture the payment are leaving value on the table -- for themselves and for their customers. The gap between "invoice sent" and "payment received" is where revenue leaks, AR teams burn hours, and customer experience degrades. Closing that gap with embedded payment links, multi-PSP support, and automatic reconciliation turns an invoicing platform into a revenue engine. Invoice Stack did it without a payments team, without building PCI compliance infrastructure, and without locking their merchants into a single gateway. If your invoicing or ERP platform is ready to close the payment loop -- embed a "Pay Now" button in every invoice, support your customers' PSP preferences, and automate reconciliation -- the infrastructure exists today. [Book a Call] | [See How It Works] ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Adyen for Platforms Alternatives ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Call](/discovery/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) --- URL: https://www.shuttleglobal.com/guides/payments-for-travel-platforms/ --- # Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure | Shuttle > The Travel Payment Problem Travel payments are unlike anything else in digital commerce. # Payments for Travel Platforms: Multi-PSP, Multi-Currency Infrastructure By Shuttle Team, January 27, 2026 ## The Travel Payment Problem Travel payments are unlike anything else in digital commerce. A customer in Tokyo books a hotel in Barcelona, pays in British pounds, and the hotel's acquirer settles in euros. The platform takes a commission in US dollars. One transaction. Four currencies. Three parties. Multiple regulatory regimes. Now multiply that across airlines, hotels, car rentals, transfers, and experiences -- each with their own PSP requirements, settlement terms, and compliance mandates. Add pre-authorisation holds, partial captures, multi-leg itineraries, and a refund rate that makes other industries look simple. This is the payment reality for every travel platform operating at scale. Online travel agencies, tour operators, booking engines, and travel management companies all face the same fundamental challenge: travel payment flows are multi-party, multi-currency, multi-PSP, and multi-channel -- by default. Most travel platforms handle this in one of three ways: - Build everything custom. Multiple PSP integrations, in-house currency handling, bespoke settlement logic. Works eventually. Takes 18+ months and a dedicated payments team. - Standardise on a single PSP. Use Stripe or Adyen for everything. Works for simple OTAs with limited geography. Breaks the moment an airline mandates a specific acquirer or a hotel chain requires a regional processor. - Use a payment layer. A single integration point, with each region on the PSP you configured for it, that handles multi-currency, supports pre-authorisation flows, and covers voice and link channels alongside embedded checkout. Option 1 is expensive and slow. Option 2 works until it doesn't. Option 3 is how scaled travel platforms are solving this without turning payments into a multi-year infrastructure project. ## Why Travel Is Different from Standard E-Commerce Standard e-commerce is a cart, a checkout, and a single payment. Travel is not that. ### Pre-Authorisation and Delayed Capture Hotels take deposits at booking and capture the full amount at check-in -- or later. Car rental companies pre-authorise a hold that exceeds the booking value (for damage deposits) and capture a different amount at return. Airlines may pre-authorise at the point of booking and only capture once the ticket is issued. These aren't edge cases. They're the default flow. Any travel payment infrastructure that doesn't support pre-auth, incremental auth, partial capture, and delayed settlement is fundamentally incomplete. ### Multi-Party Settlement A single travel booking can involve multiple suppliers. An OTA sells a package: flight from one airline, hotel from a chain, airport transfer from a local operator, and travel insurance from an underwriter. Each party needs to be settled separately, in different currencies, on different timelines. The platform takes its commission. The airline settles through BSP (Billing and Settlement Plan). The hotel settles net of commission. The transfer operator settles weekly. One booking. Four settlement streams. Payment infrastructure that only handles simple one-to-one merchant settlement can't support this. ### Currency Complexity Travel is inherently cross-border. A French customer booking through a UK-based OTA for a Thai hotel involves at least three currencies. The customer expects to pay in euros. The platform reports in pounds. The hotel settles in baht. Currency conversion happens at multiple points -- and each conversion point is either a cost centre or a margin opportunity. Competitive FX rates aren't a nice-to-have. They directly impact margin on every cross-border booking. ### Chargebacks and Disputes Travel has some of the highest chargeback rates in e-commerce. Bookings made months in advance. Services that don't match expectations. Cancellations. Schedule changes. Force majeure events that trigger mass refund requests. Airlines face friendly fraud at scale -- customers claiming flights weren't taken when they were. Hotels deal with no-show disputes. OTAs sit in the middle, managing disputes between customers and suppliers they don't control. Payment infrastructure needs to handle dispute management, evidence submission, and chargeback representment across multiple PSPs -- not just one. ### Regulatory and Industry Mandates Airlines operating through IATA-accredited agents must settle through BSP (Billing and Settlement Plan) or ARC (Airlines Reporting Corporation). This isn't optional. It's an industry requirement that dictates which acquirers and settlement mechanisms can be used for ticket sales. Hotel chains with corporate PSP agreements mandate that bookings are processed through their designated acquirer -- regardless of what the platform prefers. Regional regulations add another layer: PSD2/SCA in Europe, specific payment method requirements in APAC, local acquiring mandates in Latin America. A single PSP can't satisfy all of these requirements. The math doesn't work. ## The Multi-PSP Requirement This is where travel payment processing diverges most sharply from standard e-commerce. ### Airlines Mandate Specific Acquirers Major airlines have contractual relationships with specific payment processors for ticket sales. When a travel platform sells airline tickets, the payment often must be processed through the airline's designated acquirer -- not the platform's preferred PSP. A platform selling tickets for ten airlines across three continents may need to support six different acquirers. Building and maintaining six PSP integrations is not a checkout feature. It's an infrastructure project. ### Hotel Chains Have Corporate PSP Agreements Large hotel groups negotiate enterprise-level PSP agreements with preferential rates. They require that bookings -- even those made through third-party platforms -- are processed through their designated processor. The platform doesn't get to choose. The hotel's PSP agreement takes precedence. ### Regional Payment Methods Are Non-Negotiable Travel is a global business. Chinese travellers expect Alipay and WeChat Pay. Dutch customers default to iDEAL. Brazilians use PIX and Boleto. Japanese travellers use Konbini payments. Indian customers expect UPI. A travel platform targeting international customers that only supports cards and PayPal is leaving conversion on the table. Regional payment methods aren't a nice-to-have -- they're the dominant payment method in their respective markets. ### The Integration Burden Each PSP integration means: - A separate technical integration (API, webhooks, error handling) - Separate merchant onboarding and KYC - Separate reconciliation and reporting - Separate dispute management workflows - Separate compliance and certification maintenance For a travel platform managing five to ten PSP relationships, this consumes a payments team of three to five engineers -- permanently. That's engineering capacity not spent on core product: search, booking, pricing, supplier management. The question becomes: should a travel platform be a payments company? For most, the answer is no. ## Phone-Based Travel Payments Despite the shift to online booking, a significant portion of travel transactions still happen by phone. Group travel bookings. Corporate travel arrangements. Complex multi-leg itineraries. Booking modifications and additions. Customers who started online but need human help to complete. Travel call centres handle high-value transactions daily. A corporate group booking for 40 people. A multi-city business trip with specific airline and hotel requirements. A family booking a month-long holiday with multiple components. These aren't transactions that happen in a shopping cart. They happen in a conversation. ### The PCI Problem on Voice Channels Every time an agent takes a card number over the phone, the contact centre's PCI scope expands. The telephony system, call recordings, agent workstations, and network infrastructure all enter PCI scope. For a travel call centre processing thousands of bookings weekly, maintaining PCI DSS compliance across the entire voice environment costs hundreds of thousands annually -- before factoring in audit, remediation, and the operational overhead of PCI controls. ### Secure Voice Payment Capture DTMF-based payment capture solves this. The customer enters card details via keypad during the call. Tones are captured within a PCI-certified environment and suppressed from the audio stream. The agent stays on the line, guiding the customer through the booking, but never hears or sees card data. The contact centre's PCI scope drops from SAQ-D to SAQ-A. The compliance burden shifts to the payment provider. For travel platforms with call centres -- which is most of them at any meaningful scale -- voice payment capability isn't an add-on. It's core infrastructure. ### Payment Links as Fallback When DTMF capture isn't practical (customer on a landline without keypad, international call quality issues, customer preference), SMS or email payment links provide a secure alternative. The agent sends a branded payment link during the call. The customer completes payment on their device -- supporting cards, digital wallets, and local payment methods -- while the conversation continues. This covers the full range of phone-based travel payment scenarios without any card data entering the platform's environment. ## Three Approaches to Travel Payment Infrastructure ### 1. Build Custom What it involves: Integrate each required PSP directly. Build currency conversion logic. Develop pre-authorisation and delayed capture flows. Create reconciliation systems for multi-party settlement. Build PCI-compliant infrastructure for voice channels. Maintain everything. Timeline: 18-24 months to reach production parity with what a payment layer provides out of the box. Then ongoing maintenance, version upgrades, and new PSP integrations as requirements change. Cost: $2M+ for PCI DSS Level 1 compliance alone. Three to five full-time payments engineers. Ongoing maintenance running $360K+ annually. When it makes sense: Almost never -- unless payments are your core business. Travel platforms exist to sell travel, not to build payment infrastructure. ### 2. Single PSP with Add-Ons What it involves: Standardise on Stripe, Adyen, or Checkout.com. Use their multi-currency support. Rely on their acquiring network. Add third-party tools for voice payments if needed. Where it works: Simple OTAs with limited geography, selling primarily their own inventory, targeting customers in one or two regions. Where it breaks: The first time an airline mandates a different acquirer. The first time a hotel chain requires processing through their corporate PSP. The first time you need Alipay for the Chinese market and your PSP's coverage is weak in APAC. The first time an enterprise client demands a gateway you don't support. Single-PSP works until your business outgrows it. For travel platforms with enterprise ambitions, that happens fast. ### 3. Payment Layer What it involves: A single integration point that sits between the platform and multiple PSPs. The platform integrates once. The payment layer handles PSP routing, currency conversion, pre-authorisation flows, multi-channel support (embedded checkout, voice, payment links), and PCI compliance. How it works: Configure which PSP handles which region, product type, or supplier requirement. Add new PSPs through configuration, not code. Route payments based on currency, geography, airline mandate, or hotel chain requirement. Handle voice payments and payment links through the same integration. Timeline: Weeks, not months. Single API integration. PSP configuration handled at the platform level. Trade-off: You're adding a dependency. But you're replacing five to ten PSP dependencies (each requiring separate integration, maintenance, and compliance) with one. ## What Travel Platforms Need from Payment Infrastructure Not every travel platform needs every capability. But at scale, the requirements converge: Multi-PSP with regional routing. Configure each airline or hotel-chain merchant against the PSP their mandate requires, per payment method. Add new PSPs without re-integration. Multi-currency with competitive FX. Handle tourist-pays-in-home-currency, platform-settles-in-reporting-currency, supplier-receives-in-local-currency. FX rates that don't eat your margin. Pre-authorisation and delayed capture. Support hotel deposits, car rental holds, and booking-to-ticketing flows where authorisation and capture happen at different times. Split payment support. Route funds to multiple parties from a single booking -- supplier, platform commission, insurance provider, transfer operator. Voice payments for call centres. PCI-compliant DTMF capture with tone suppression. Agents stay on the call. Card data never enters your environment. Payment links for booking confirmations. Branded payment links sent via SMS, email, or chat. Supports cards, digital wallets, and local payment methods. Useful for deposits, balance payments, and post-booking additions. PCI DSS Level 1 compliance. Non-negotiable. Travel platforms handling card data across multiple channels need Level 1 -- the highest certification tier. Building this yourself costs $2M+. A payment layer includes it. White-label checkout. Customers see the travel platform's brand throughout the payment experience. No redirects to third-party checkout pages. Consistent with the booking flow. ## Implementation: What It Actually Looks Like For platforms evaluating a payment layer approach, the integration is simpler than the problem it solves. Single API integration. One set of endpoints for payment creation, capture, refund, and status. The platform's booking system calls the payment API. The payment layer handles PSP routing, currency conversion, and compliance. PSP configuration per region and product. Define routing rules: European hotel bookings go through Acquirer A, airline tickets through the airline's mandated processor, APAC bookings through a regional PSP with local payment method coverage. Configuration, not code. Currency handling. Specify the customer's preferred currency, the settlement currency, and the reporting currency. The payment layer handles conversion at each point. Transparent FX rates visible in the merchant portal. Pre-authorisation flows. Create a pre-auth at booking. Capture (full or partial) at the appropriate trigger -- check-in, ticket issuance, service delivery. Release unused holds automatically based on configurable timeouts. Webhook notifications. Real-time notifications for payment events -- authorisation, capture, refund, chargeback -- pushed to the booking system. The platform's workflow engine reacts to payment events without polling. Merchant portal. White-label dashboard for transaction monitoring, refund processing, dispute management, and reconciliation. Configurable per merchant or per supplier. The integration typically takes a single developer one to two weeks. PSP configuration and testing add another week. Compare that to 18+ months of custom build. ## The Cost of Getting This Wrong Travel platforms that underestimate payment complexity pay for it in predictable ways. Lost bookings. Customers abandon checkout when their preferred payment method isn't available. In markets where local payment methods dominate (China, Netherlands, Brazil, India), card-only checkout is a conversion killer. Failed airline partnerships. Airlines that mandate specific acquirers won't work with platforms that can't support them. No PSP flexibility, no airline inventory. Engineering drag. Every new PSP integration consumes engineering capacity. Every PSP API change requires maintenance. Every compliance upgrade requires remediation. Payments become a permanent tax on the product roadmap. Compliance exposure. Operating voice payment channels without proper PCI controls creates liability that scales with transaction volume. One breach can cost more than years of infrastructure investment. Margin erosion. Poor FX rates on multi-currency transactions compound across millions of bookings. A 50-basis-point difference on currency conversion across $100M in annual bookings is $500K in lost margin. ## Conclusion Travel payment infrastructure is not a checkout problem. It's an infrastructure problem -- multi-PSP, multi-currency, multi-party, multi-channel -- that compounds as the platform scales. Building it from scratch is expensive and slow. Relying on a single PSP works until it doesn't. And the gap between "works for now" and "works at scale" is where travel platforms lose bookings, airline partnerships, and engineering momentum. A payment layer approach gives travel platforms multi-PSP routing, multi-currency handling, voice and link payment channels, and PCI compliance through a single integration -- without turning the platform into a payments company. If your travel platform is wrestling with multi-PSP mandates, multi-currency complexity, or the cost of maintaining payment infrastructure across channels, that's the problem Shuttle was built to solve. [Book a Call] | [See How It Works] ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Navigating the Future of Travel Booking and Payments ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Travel Payment Solutions: How Agencies Collect Payments Faster ### Adyen for Platforms Alternatives ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Book a Call](/discovery/) - [BlogNavigating the Future of Travel Booking and Payments→](/blog/navigating-the-future-of-travel-booking-and-payments/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [BlogTravel Payment Solutions: How Agencies Collect Payments Faster→](/blog/payment-links-the-secret-weapon-for-travel-agents-to-boost-sales/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) --- URL: https://www.shuttleglobal.com/guides/paypal-twilio-integration/ --- # How to Connect PayPal to Twilio for Voice & IVR Payments | Shuttle > Here's the important thing to know up front: PayPal/Braintree does not work for Shuttle voice card capture. # How to Connect PayPal to Twilio for Voice & IVR Payments By Shuttle Team, March 24, 2026 Here's the important thing to know up front: PayPal/Braintree does not work for Shuttle voice card capture. Braintree won't allow raw card data to be passed to it, which is exactly what keypad (DTMF) capture during a voice call requires. So there is no PayPal/Braintree "voice" path through Twilio's `` verb. What does work -- and works well -- is payment links. If you take calls on Twilio and your processor is PayPal/Braintree, Shuttle can send the customer a secure payment link by SMS or email, including mid-call while they're still on the line. The customer pays on a hosted page, and PayPal/Braintree processes it as normal. This guide explains why voice capture isn't possible with PayPal/Braintree, how the payment-links path works instead, and which gateways do support voice if that's a hard requirement for you. ## Why You Can't Capture PayPal/Braintree Cards Over Voice PayPal is the world's largest digital payments platform, and through its Braintree subsidiary handles card processing for millions of businesses. Its APIs are designed for web and mobile checkout -- buttons, hosted fields, and drop-in UIs. Twilio is built for voice and messaging. Its `` verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. To work, `` hands the raw card number to a payment connector, which passes it to the gateway. That's the blocker: Braintree (and therefore PayPal-via-Braintree) does not permit raw card data to be passed to it. Voice/keypad capture depends on passing the raw PAN to the processor, so PayPal/Braintree can't be the gateway behind a Twilio `` voice flow. This isn't a Shuttle limitation -- it's how Braintree's integration works. The good news: the same restriction doesn't apply to payment links, because the customer enters their card on Braintree's own hosted, tokenised checkout rather than passing raw digits through a voice channel. So if you're on PayPal/Braintree, links are your path. ## How It Works (Payment Links) ``` Caller on Twilio → agent/IVR sends Shuttle link by SMS → customer pays on hosted page → PayPal/Braintree (processing) → result returned ``` - Caller reaches the payment step. They're on a Twilio call -- IVR, agent-assisted, or an AI voice agent. - A Shuttle payment link is sent by SMS (or email), mid-call. The customer doesn't need to hang up. - The customer pays on a secure hosted page. They enter their card (or a digital wallet) on Shuttle's hosted checkout -- never reading digits aloud, never typing them into the call. - PayPal/Braintree processes the payment through your merchant account, using its own tokenised, PCI-compliant flow. - Result returned in real time. Confirmation comes back to the agent/flow; the call can continue or wrap up. No raw card data ever passes through the voice channel or your systems. ## Setting It Up ### Prerequisites - A PayPal Business or Braintree account with API credentials - A Shuttle account (free to create) - A way to send the link mid-call -- Twilio SMS works well, but any SMS/email channel is fine ### Step 1: Add PayPal/Braintree Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: PayPal / Braintree - Merchant ID: Your PayPal/Braintree merchant ID - API credentials: Your public key and private key (Braintree) or API credentials (PayPal) - Currency: Set your default (USD, GBP, EUR, etc.) - Environment: Live or Sandbox Save the profile. Shuttle now has a live connection to your PayPal/Braintree account. ### Step 2: Generate and Send the Link Mid-Call Create a payment link in Shuttle (via the dashboard or API) for the amount due, and send it to the customer by SMS or email while they're on the line. See the Payment Links docs for the API. ### Step 3: Handle the Result Shuttle returns the outcome -- transaction reference, last four digits, card brand, and status -- to your webhook so the agent or flow knows the payment cleared. ### Step 4: Test Use Braintree's sandbox environment to verify the flow end-to-end. Braintree sandbox test card: `4111 1111 1111 1111` (Visa). ## What You Can Do With PayPal/Braintree Links ### Charge Immediately Standard auth-and-capture. The customer pays on the hosted page, Braintree processes, done. ### Tokenise for Future Use When the customer pays via the link, Braintree tokenises the card in its own Vault. Use that token for future payments across any channel -- web, mobile, or further payment links. The card data is never stored in your systems. ### Marketplace Payments If you use Braintree Marketplace (sub-merchants), Shuttle can route link payments to the correct sub-merchant. Each merchant's transactions are processed through their own account. ## If Voice Capture Is a Hard Requirement If you specifically need keypad (DTMF) capture during the call -- not links -- you'll need a gateway that permits raw card data to be passed to it. Shuttle's voice card capture runs on Twilio Pay today and works with 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, and Global Payments. PayPal/Braintree is the notable exception that does not. A common pattern: run voice capture on a voice-compatible gateway for live keypad payments, and keep PayPal/Braintree on the links path. Routing is configured in Shuttle's dashboard. ## PCI Compliance Collecting PayPal/Braintree payments via Shuttle payment links limits your PCI scope: Layer | PCI handled by Hosted checkout page | Shuttle (PCI DSS Level 1) Card data processing | PayPal/Braintree (PCI DSS Level 1) Your systems | No card data -- SAQ-A The customer enters their card on a hosted page; your application only receives redacted data. You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I take PayPal/Braintree payments over voice with Twilio's `` verb? No. Braintree doesn't allow raw card data to be passed to it, and voice/keypad capture requires passing the raw card number to the gateway. So PayPal/Braintree can't sit behind a Twilio `` voice flow. Use payment links instead -- they work because the customer enters their card on Braintree's own hosted, tokenised checkout. Which gateways do work for voice capture, then? Most do -- Shuttle's voice capture (on Twilio Pay) works with 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, and Global Payments. PayPal/Braintree is one of the few that don't. Is this PayPal or Braintree? Both. PayPal owns Braintree, and Shuttle integrates with the Braintree/PayPal payment processing APIs for the links path. If you have a Braintree merchant account or a PayPal Business account with card processing enabled, Shuttle can use it for payment links. What does it cost? Links Checkout is a separate app; see [pricing](/pricing/). Voice capture, where the gateway supports it, is $0.20 per successful transaction. PayPal/Braintree's standard processing fees apply on top (2.59% + 49¢ or your negotiated rate). Can I accept PayPal wallet payments over the phone? PayPal wallet (balance/bank) payments require the PayPal checkout flow, which is web-based. A payment link is the right way to offer that mid-call -- the customer completes it on the hosted page. Can I switch from PayPal/Braintree to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Moving to a voice-compatible gateway would also unlock keypad capture. ## Related Reading - Payment Links: Take Payments Without Handling Card Data -- the turnkey path for PayPal/Braintree - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments -- a gateway that does support voice capture - How to Connect Adyen to Twilio for Voice Payments -- another voice-compatible gateway - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup PayPal/Braintree doesn't support voice card capture -- use Shuttle payment links instead, sent by SMS mid-call. PCI DSS Level 1, links currently free. [Book a discovery call](/discovery/). ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for PayPal: Send Professional Payment Links Through PayPal ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [DTMF](/guides/dtmf-payments/) - [payment link](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [payment links](/merchants/links-checkout/) - [30+ gateways](/payment-providers/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Payment Links: Take Payments Without Handling Card Data](/guides/take-payments-online/payment-links/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for PayPal: Send Professional Payment Links Through PayPal→](/blog/payment-links-for-paypal/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/paysafe-twilio-integration/ --- # How to Connect Paysafe to Twilio for Voice & IVR Payments | Shuttle > Paysafe doesn't natively connect to Twilio for voice payments. If you want to process Paysafe transactions during a phone call (via IVR, agent-assisted,... # How to Connect Paysafe to Twilio for Voice & IVR Payments By Shuttle Team, June 29, 2026 Paysafe doesn't natively connect to Twilio for voice payments. If you want to process Paysafe transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Paysafe (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Paysafe + Twilio Don't Connect Directly Paysafe is a global payments platform with deep roots in North America and Europe. It grew up serving specialised and higher-risk verticals (iGaming, forex, and other regulated industries) and now offers card processing, digital wallets, and alternative payment methods through a single REST API. Merchants who process through Paysafe often chose it precisely because mainstream gateways couldn't support their vertical. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Paysafe isn't one of Twilio's built-in connectors, so there's no native way to send a capture to your Paysafe merchant account. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Paysafe's API for processing. One integration connects the two platforms. That matters most for the businesses Paysafe typically serves: North American contact centres, collections operations, and merchants in specialised verticals whose Paysafe account took real underwriting effort to obtain. You keep the account. You add the voice channel. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Paysafe. The connector creates a Paysafe payment request, processes the transaction through your Paysafe merchant account, and handles the response. - Result returned to your call flow. Your webhook receives the Paysafe transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Paysafe account with server-to-server API credentials (API key username and password, plus your account number) - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Paysafe Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Paysafe - API key username and password: Your server-to-server API key from the Paysafe Back Office (Settings > API Key) - Account number: The Paysafe account ID for the card account you want to process through - Currency: Set your default (USD, CAD, GBP, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Paysafe account. If you hold multiple Paysafe account numbers (for example, separate accounts per currency or per business line), create a profile for each and route accordingly. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in the Paysafe Back Office if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Paysafe provides a dedicated Test environment where transactions run through a simulator rather than the banking network. Use your Paysafe test API key in Shuttle, run the flow end-to-end with Paysafe's published test card numbers, and verify your webhook handling before switching the profile to Live. Never use real card numbers in the Paysafe test environment. ## What You Can Do With Paysafe + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Paysafe processes, done. ### Authorise Now, Settle Later Place a hold on the card during the call and settle later through Paysafe. Useful for deposits, bookings, or transactions where the final amount isn't fixed at call time. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Paysafe (which supports converting a payment into a reusable stored credential) and returns a token you can reuse across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. For collections teams, this is the foundation of payment plans: capture the card on the first call, then charge agreed instalments without asking the customer to re-enter anything. ### Agent-Assisted and IVR Collections Collections is a natural fit for Paysafe + Twilio. Agents trigger `` mid-call for a promise-to-pay, or an outbound IVR lets debtors self-serve a payment at any hour. Tones are suppressed, so recordings stay compliant. See payment collection for BPOs for the multi-client version of this setup. ## Multi-PSP: Beyond Paysafe One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: route your specialised-vertical volume to Paysafe and lower-risk volume to another acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway declines or is unavailable, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, per merchant, with amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for BPOs and platforms that serve multiple merchants. Each merchant can use their own Paysafe account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Paysafe + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Paysafe (PCI DSS Level 1) Your systems No card data, SAQ-A Card data flows from Twilio to Shuttle to Paysafe. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. That's a meaningful saving for contact centres, where taking card numbers verbally would otherwise drag the entire agent floor, telephony stack, and recording system into scope. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Paysafe to Twilio without Shuttle? Twilio doesn't have a built-in Paysafe Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. I'm in a higher-risk vertical. Does that change anything? No. Your underwriting relationship stays with Paysafe, exactly as it is today. Shuttle is the technical connector between Twilio and your existing Paysafe merchant account; it doesn't sit in the money flow or re-underwrite you. What about Paysafe's test environment? Fully supported. Use your Paysafe test API credentials in Shuttle and test the full flow with Twilio before going live. Paysafe's test environment runs transactions through a simulator, so nothing hits the banking network. What does it cost? Shuttle charges $0.20 per successful transaction. Paysafe's standard processing fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from Paysafe to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice Payments: step-by-step Adyen + Twilio setup - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Paysafe on Shuttle: supported features, currencies, and channels - Twilio Pay, Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Paysafe to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Paysafe: Send Branded Checkout Links via Paysafe ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [payment collection for BPOs](/guides/payment-collection-for-bpos/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Paysafe on Shuttle](/payment-providers/paysafe/) - [Twilio Pay, Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Paysafe: Send Branded Checkout Links via Paysafe→](/blog/payment-links-for-paysafe/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/payu-twilio-integration/ --- # How to Connect PayU to Twilio for Voice & IVR Payments | Shuttle > PayU doesn't natively connect to Twilio for voice payments. If you want to process PayU transactions during a phone call (via IVR, agent-assisted, or AI... # How to Connect PayU to Twilio for Voice & IVR Payments By Shuttle Team, June 30, 2026 PayU doesn't natively connect to Twilio for voice payments. If you want to process PayU transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects PayU (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. This matters most in PayU's home markets. PayU is the dominant payment provider across many emerging markets: India, Latin America, Central and Eastern Europe, and Africa. If your customers pay through PayU because it gives you local acquiring and local payment methods in those regions, you shouldn't have to switch gateways just to take a payment over the phone. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why PayU + Twilio Don't Connect Directly PayU is built for online commerce in growth markets. It operates across more than 50 countries and supports a deep bench of local payment methods alongside cards: net banking and UPI in India, cash voucher and bank transfer methods in Latin America, and local card acquiring across Central and Eastern Europe. Its APIs handle hosted checkout, server-to-server payments, and card tokenisation. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. PayU isn't one of Twilio's built-in connectors, so there is no native path between the two. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to PayU for processing through your existing PayU merchant account. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via PayU. The connector creates a PayU payment request, processes the transaction through your PayU merchant account with your local acquiring rates, and handles the response. - Result returned to your call flow. Your webhook receives the PayU transaction reference, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A PayU account with API credentials for your region - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add PayU Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile with your PayU credentials. The exact fields depend on your PayU region: - PayU India: merchant key + salt, generated from the PayU Dashboard (test and production sets are issued separately) - PayU Europe / GPO: POS ID plus OAuth client credentials (client ID and client secret), found in the point-of-sale section of your management panel - Currency: set your default (INR, PLN, EUR, etc.) - Environment: live or test Save the profile. Shuttle now has a live connection to your PayU account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in your PayU dashboard if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test PayU provides test environments in every region: PayU India issues dedicated test merchant keys and salts through its dashboard, and PayU Europe runs a full sandbox environment for integration testing. Use your PayU test credentials in Shuttle and verify the flow end-to-end with Twilio before going live. ## What You Can Do With PayU + Twilio ### Charge Immediately Standard authorisation and capture. The caller pays, PayU processes through your local acquirer, done. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token (PayU supports both single-use and multi-use card tokens). Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Serve Callers in PayU's Markets With Local Acquiring This is the real reason to pair PayU with Twilio. A contact centre taking payments from customers in India, Poland, or Colombia gets domestic processing rates and higher authorisation rates through PayU's local acquiring, instead of routing everything through a foreign cross-border acquirer. ### Collect Across Channels From One Profile The same Shuttle payment profile that powers your Twilio voice flow can also generate payment links for SMS and WhatsApp follow-ups. If a caller would rather not key in card details, send a link mid-call and keep the PayU processing relationship identical. ## Multi-PSP: Beyond PayU One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: serve your Indian merchants with PayU and your UK merchants with a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Adyen, Worldpay, etc.) - Want a backup gateway: if PayU has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for BPOs and platforms serving clients across PayU's regions. A BPO with clients in India, Central Europe, and Latin America can give each client their own PayU merchant account (or any other gateway) through the same Twilio integration. For PayU's full gateway profile on Shuttle, see PayU on Shuttle. ## PCI Compliance The PayU + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing PayU (PCI DSS certified) Your systems No card data, SAQ-A Card data flows from Twilio → Shuttle → PayU. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect PayU to Twilio without Shuttle? Twilio doesn't have a built-in PayU Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Which PayU regions are supported? Shuttle connects to PayU merchant accounts using the credential set for your region: merchant key and salt for PayU India, POS ID and OAuth client credentials for PayU Europe. If you operate PayU accounts in multiple regions, create a Shuttle payment profile for each and route by caller or client. What about PayU's test environment? Fully supported. PayU India issues test merchant keys and salts from its dashboard, and PayU Europe provides a sandbox environment. Add your test credentials to a Shuttle test profile and run the full Twilio flow before going live. What does it cost? Shuttle charges $0.20 per successful transaction. PayU's standard fees for your region apply on top. No Shuttle setup fees or monthly minimums. Can I switch from PayU to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - Payment Collection for BPOs: multi-client payment routing for outsourced contact centres - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect PayU to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Payment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PayU on Shuttle](/payment-providers/payu/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogPayment Links for PayU: Send Branded Checkout Links with Full Branding and Multi-Channel Sending→](/blog/payment-links-for-payu/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/pci-compliance-cost-platforms/ --- # PCI Compliance Cost for Platforms: What It Really Costs in 2026 | Shuttle > The Number That Catches Platforms Off Guard Most platform CTOs know PCI DSS compliance isn't free. # PCI Compliance Cost for Platforms: What It Really Costs in 2026 By Shuttle Team, March 11, 2026 ## The Number That Catches Platforms Off Guard Most platform CTOs know PCI DSS compliance isn't free. Few realise how expensive it actually is -- or that the thresholds for platforms are dramatically lower than they expect. Here's the figure that stops conversations: PCI DSS Level 1 compliance costs up to £1.1 million to achieve initially, plus approximately £135,000 per year to maintain. For a platform that processes payments on behalf of its customers, this isn't a theoretical number. It's the cost of doing business if card data touches your environment. But that headline figure only tells part of the story. The real cost of PCI compliance for platforms includes direct audit expenses, infrastructure changes, ongoing monitoring, staff time, and the opportunity cost of engineering resources diverted from your core product. ## The Threshold Trap This is where most platforms get caught. PCI DSS defines two categories of entities: merchants and service providers. Merchants accept payments for their own goods and services. Service providers process, store, or transmit cardholder data on behalf of other businesses. Platforms that embed payments for their customers are classified as service providers. And the thresholds for service providers are six times more stringent than those for merchants. Merchant Threshold Service Provider Threshold 6,000,000+ transactions/year 300,000+ transactions/year 1,000,000-6,000,000 Under 300,000 A platform processing 500,000 transactions per year would be Level 2 as a merchant but is Level 1 as a service provider. Level 1 is the most expensive and rigorous tier -- requiring a full onsite audit by a Qualified Security Assessor (QSA), not just a Self-Assessment Questionnaire. At 300,000 transactions per year -- roughly 820 per day -- you hit the Level 1 threshold. For a growing platform, that number arrives faster than expected. ## Cost Breakdown by Level ### Level 1 Service Provider (300,000+ transactions/year) This is the tier most growing platforms will reach. The costs: Annual Cost QSA audit (onsite assessment) £80,000-£120,000 Remediation (fixing gaps found in audit) £150,000-£250,000 Penetration testing (external + internal) £40,000-£75,000 Vulnerability scanning (quarterly ASV scans) £5,000-£15,000 Security automation and monitoring tools £30,000-£50,000 Staff training and awareness £10,000-£20,000 Documentation and policy maintenance £15,000-£25,000 Typical annual total £330,000-£555,000 First-year costs are substantially higher because of initial infrastructure changes. Network segmentation, encryption implementation, key management systems, access control overhauls, and logging infrastructure can add £500,000-£800,000 in Year 1. Representative Year 1 total: £830,000-£1,100,000+ ### Level 2 Service Provider (Under 300,000 transactions/year) Level 2 service providers complete a Self-Assessment Questionnaire (SAQ-D) rather than a full onsite audit. The costs are lower but still substantial: SAQ-D completion and validation £15,000-£30,000 Penetration testing Vulnerability scanning £5,000-£10,000 Security tooling Remediation £20,000-£50,000 £70,000-£150,000 The jump from Level 2 to Level 1 is steep. Platforms approaching the 300,000 transaction threshold should plan for the cost increase 12-18 months in advance. ## What PCI DSS 4.0 Changed PCI DSS 4.0 came into full enforcement in March 2025, replacing version 3.2.1. The changes increased both the technical requirements and the cost of compliance. Key changes that affect platforms: Stronger encryption requirements. All cardholder data must be encrypted with current, strong cryptographic algorithms. Deprecated algorithms must be phased out -- this often requires infrastructure changes. Mandatory multi-factor authentication (MFA). MFA is now required for all access to the cardholder data environment, not just remote access. This extends to internal access by administrators, developers, and operations staff. Continuous monitoring. Version 4.0 shifts the model from point-in-time assessment to continuous validation. Automated log monitoring, real-time alerting on security events, and regular security control testing are now baseline requirements. Targeted risk analysis. Organisations must perform formal risk analysis for any requirement where they use a "customised approach" rather than the defined method. This adds documentation and justification overhead. Client-side security. New requirements for monitoring and controlling JavaScript loaded on payment pages -- addressing Magecart-style attacks. Platforms with web-based checkout flows need content security policies, script inventories, and integrity monitoring. The net effect: compliance is more expensive, more technically demanding, and requires more ongoing attention than under version 3.2.1. ## How Channels Expand PCI Scope Every channel that touches card data adds to your PCI scope. This is where platforms underestimate the cumulative cost. Web checkout. The most common channel. If your platform renders a checkout page where cardholders enter details, that page and its infrastructure are in scope. Even with iframes or hosted fields, the hosting page needs to meet PCI DSS 4.0's client-side security requirements. Voice payments. If your platform takes card details over the phone -- whether through an IVR system, agent-assisted calls, or AI voice agents -- the voice infrastructure is in PCI scope. Call recording systems must pause during card capture. DTMF tones must be suppressed. Agent screens must be masked. The telephony infrastructure itself needs segmentation and monitoring. Chat payments. If customers type card details into a chat interface -- whether live chat, messaging, or an AI chat agent -- that channel is in scope. Chat logs containing card data must be encrypted, access-controlled, and purged according to retention policies. Email and SMS. Payment links sent via email or SMS can be designed to keep card data out of your environment (the cardholder enters details on a hosted page). But if card details are ever communicated back through these channels, they're in scope. Each channel you add doesn't just add its own cost -- it expands the boundary of your cardholder data environment, which increases the scope of every audit, every penetration test, and every monitoring requirement. ## The Descoping Strategy There is a way to reduce PCI compliance cost to near zero: ensure card data never enters your environment. If cardholder data is captured, processed, and stored entirely by a PCI DSS Level 1 certified third party -- and never passes through or is accessible to your systems -- your platform typically qualifies for SAQ-A. This is the lightest self-assessment level, covering approximately 20 requirements instead of the 300+ in SAQ-D. Ongoing Effort Self-certified (card data in your environment) Level 1 SP Level 2 SP Descoped via certified provider (SAQ-A) The cost difference is dramatic. A platform processing 500,000 transactions per year saves £315,000-£540,000 annually by descoping -- before accounting for the engineering time freed up. ### How Descoping Works in Practice The principle is simple: card data flows directly between the cardholder and the certified payment provider. Your platform initiates the payment flow and receives the result, but the sensitive data takes a path that bypasses your infrastructure entirely. For web payments, this means hosted checkout pages or payment fields rendered in iframes from the payment provider. For voice payments, this means DTMF masking -- the cardholder enters their card number on their phone keypad, and the tones are captured directly by the payment provider rather than passing through your telephony system. For chat and messaging, this means payment links that redirect the cardholder to a hosted page. Shuttle is PCI DSS Level 1 certified, ISO 27001 certified, and SOC 2 certified. Platforms integrating through Shuttle keep card data entirely outside their environment across all channels -- web, voice, chat, payment links. The platform stays at SAQ-A regardless of how many PSPs are processing transactions underneath, because the card data boundary sits with Shuttle, not with the platform. This is the difference between building payment infrastructure in-house -- where PCI scope expands with every feature -- and using a payment layer where compliance is included and scope stays minimal. ## Non-Compliance Risk Platforms sometimes weigh PCI compliance costs against the risk of non-compliance. The maths on that calculation is not favourable. Fines. Card networks can impose fines of £5,000-£100,000 per month on acquiring banks for non-compliant merchants and service providers. Those fines flow downstream. Breach liability. If a data breach occurs and the organisation is non-compliant, liability exposure increases substantially. Forensic investigation costs alone typically run £100,000-£500,000. Add notification costs, legal fees, regulatory penalties, and brand damage. Loss of processing capability. In severe cases, card networks can revoke a service provider's ability to process card payments. For a platform whose customers depend on payment processing, this is existential. The cost of PCI compliance is significant. The cost of non-compliance is worse. ## The Bottom Line PCI DSS compliance is not optional for platforms that handle card data. The question is how much it costs -- and that's largely determined by whether card data enters your environment. Platforms that process card data directly face costs of £330,000-£555,000 per year at Level 1, with first-year costs exceeding £1 million. Platforms that descope by using a PCI Level 1 certified payment layer reduce that cost to under £15,000 per year. For most platforms, the decision is clear. Card data handling is not a competitive advantage. It's a liability -- an expensive, resource-consuming liability that can be eliminated entirely by choosing the right architecture. ## Further Reading - Twilio PCI Compliance: How to Take Secure Payments Over Voice - AI Voice Agent PCI Payments - Contact Centre Payments - PCI Compliance for Service Providers - Voice Payments ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Adyen for Platforms Alternatives ### Why Platforms Don't Want to Be Payment Companies ### Uncovering the Limitations of Spreedly for Software Platforms ### PCI DSS v4 Implications for Service Provider (software vendors) ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [voice infrastructure is in PCI scope](/guides/twilio-pci-compliance/) - [DTMF tones](/guides/dtmf-payments/) - [AI chat agent](/guides/ai-voice-agent-pci-payments/) - [voice payments](/guides/voice-payments/) - [building payment infrastructure in-house](/guides/build-vs-buy-payment-infrastructure/) - [Twilio PCI Compliance: How to Take Secure Payments Over Voice](/guides/twilio-pci-compliance/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [PCI Compliance for Service Providers](/guides/pci-compliance-cost-platforms/) - [Voice Payments](/guides/voice-payments/) - [Book a Call](/discovery/) - [BlogPCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope→](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) - [BlogWhy Platforms Don't Want to Be Payment Companies→](/blog/why-platforms-dont-want-to-be-payment-companies/) - [BlogUncovering the Limitations of Spreedly for Software Platforms→](/blog/uncovering-the-limitations-of-spreedly-for-software-platforms-2/) - [BlogPCI DSS v4 Implications for Service Provider (software vendors)→](/blog/pci-dss-v4-implications-for-service-provider-software-vendors/) --- URL: https://www.shuttleglobal.com/guides/pci-compliance-service-provider/ --- # PCI Compliance Service Provider: How to Choose One in 2026 | Shuttle > A PCI compliance service provider is a certified third party that handles card data on behalf of merchants -- typically the parts of the payment flow that... # PCI Compliance Service Provider: How to Choose One in 2026 By Shuttle Team, May 4, 2026 A PCI compliance service provider is a certified third party that handles card data on behalf of merchants -- typically the parts of the payment flow that touch cardholder data directly -- so that the merchant's own systems stay out of PCI DSS scope. The economics matter. PCI DSS compliance for a merchant who handles card data themselves means full SAQ D (the most extensive self-assessment questionnaire), annual penetration testing, network segmentation, encryption key management, and ongoing audit overhead. For a mid-sized merchant, that's typically £50,000-£250,000 a year in compliance cost, before counting the operational burden on engineering and security teams. Using a PCI Level 1 Service Provider for the part of the flow that touches card data -- checkout, voice capture, vault, gateway routing -- drops merchant scope dramatically. SAQ A (a one-page questionnaire) becomes possible. Penetration testing requirements relax. Engineering teams stop worrying about HSM key rotation and tokenisation algorithms. The service provider's annual audit by a Qualified Security Assessor (QSA) does the heavy lifting on behalf of every merchant using their environment. This guide covers what a PCI compliance service provider actually is, the four service provider levels, how PCI service provider compliance differs from merchant compliance, what Level 1 specifically requires, and how to evaluate a provider for your use case. ## What Is a PCI Compliance Service Provider? PCI DSS recognises two primary categories of entity: merchants (businesses that accept card payments for their own goods and services) and service providers (companies that store, process, or transmit cardholder data on behalf of merchants -- or that could affect the security of cardholder data). A PCI compliance service provider sits in the second category. Examples include: - Payment gateways -- Stripe, Adyen, Checkout.com, Worldpay, Authorize.Net - Payment processors -- the entities that route transactions to card networks - Acquirers -- banks that hold the merchant account and have direct card scheme membership - Tokenisation / vault providers -- companies that store card credentials and return tokens - Voice payment providers -- companies handling DTMF capture and voice payments - Hosted checkout providers -- platforms that run the card entry form on your behalf - PCI scope reduction providers -- services that intercept card data before it reaches your environment Every one of these categories includes Level 1 service providers. Each subset of the payment flow can -- in principle -- be outsourced to one. The merchant's PCI obligation shrinks to the parts of the flow they still touch directly. ## The Four PCI Service Provider Levels Service provider levels are determined by transaction volume processed annually. The card schemes (Visa and Mastercard, primarily) define the thresholds; PCI DSS itself doesn't, but in practice the requirements scale with the level. ### Level 1: Service Providers processing 300,000+ card transactions per year The highest tier. Required for any third-party service provider handling card data at meaningful scale. Compliance demands: - Annual on-site audit by a Qualified Security Assessor (QSA) -- not a self-assessment. The QSA produces a Report on Compliance (ROC). - Quarterly network scans by an Approved Scanning Vendor (ASV) -- external vulnerability scans of the cardholder data environment. - Annual penetration testing -- both network-layer and application-layer. - Attestation of Compliance (AOC) on file -- published or made available on request to merchants and partners. Level 1 is the bar for any service provider you're trusting to give you scope reduction at audit. Merchants integrating with non-Level-1 service providers cannot claim the same scope-reduction benefits -- and in some cases, regulators will treat the merchant as if they handled the card data themselves. ### Level 2: Service Providers processing fewer than 300,000 transactions per year May complete a Self-Assessment Questionnaire (SAQ) of the appropriate type -- typically SAQ D for Service Providers -- instead of a full QSA audit. Same control requirements as Level 1, but the merchant attests rather than an independent assessor. In practice, most enterprise merchants and platforms require Level 1 from their service providers regardless of the provider's transaction volume. Level 2 is rare for serious payment infrastructure vendors. ### Level 3 and Level 4 These levels exist for very small service providers, often individual independent sales organisations (ISOs) or small regional players. Most modern payment infrastructure providers operate at Level 1. ## Merchant PCI Compliance vs Service Provider PCI Compliance The two compliance regimes look similar but have different scopes, audit requirements, and consequences. Merchant Compliance Service Provider Compliance Who needs it Any business accepting card payments Any third party handling card data on behalf of merchants 4 levels (Level 1 = 6M+ transactions/year) 2 main levels (Level 1 = 300K+ transactions/year) Validation SAQ (self-assessment) for most levels; ROC for Level 1 ROC for Level 1; SAQ-D-SP for Level 2 Annual QSA audit only at Level 1 Annual QSA audit at Level 1 (mandatory) Pen testing Annual at Level 1; situational at lower levels Annual + after major changes Generated for merchants Required to be available to merchant customers The thresholds are different (300K transactions for service providers vs. 6M for merchants) because the blast radius of a service provider breach is different -- a single breach can compromise thousands of merchants. The bar is correspondingly higher. ## What PCI DSS Level 1 Service Provider Status Actually Means When a service provider claims to be "PCI DSS Level 1", these are the concrete things it should mean: - They have a current AOC -- an Attestation of Compliance signed by a QSA within the last 12 months. Ask to see it. - They have a current ROC -- the Report on Compliance produced by their QSA. Usually held by the QSA and not shared in full, but the AOC is the proof of the ROC's existence. - They run quarterly ASV scans -- external vulnerability scans of their cardholder data environment by an Approved Scanning Vendor. - They run annual pen tests -- by a qualified pen testing firm, on both network and application layers. - Their cardholder data environment is segmented -- physically and logically separated from non-cardholder systems, with controlled boundary devices. - They run a continuous monitoring programme -- file integrity monitoring, intrusion detection, log review, on the cardholder data environment. A claim of "PCI Level 1" without a current AOC isn't a claim, it's marketing language. The AOC is the only document that proves the audit happened and passed. It's also the document that lets your QSA confirm the service provider's compliance during your own audit. ## How a PCI Service Provider Reduces Merchant Scope Scope reduction is the entire reason merchants use PCI service providers. Done right, it transforms the merchant's compliance burden from "build and maintain a fully-segmented cardholder data environment" to "configure your integration with a certified provider and document the boundary." The mechanism: the parts of the payment flow that touch cardholder data -- entry, transmission, storage -- happen inside the service provider's certified environment, not the merchant's. The merchant's systems receive only tokens, references, or non-sensitive metadata. Concretely: Hosted checkout / payment page hosted by the service provider → merchant typically qualifies for SAQ A (the lightest SAQ). All card data entry happens on the service provider's domain via redirect or iframe. Hosted fields / iframe inside merchant's checkout → merchant typically qualifies for SAQ A-EP. The card fields are loaded from the service provider, but the merchant's site contains the rest of the checkout. Some integration controls apply (subresource integrity, CSP, etc). Server-side card capture by the merchant, with tokenisation by the service provider → merchant typically qualifies for SAQ D-MERCHANT. Card data passes through the merchant's servers (briefly) before being exchanged for a token. Most demanding scope. DTMF interception by the service provider for voice payments → merchant typically qualifies for SAQ A for the voice channel. Tones never enter the merchant's contact centre environment. White-label payment links on the merchant's domain → merchant typically qualifies for SAQ A because the actual card capture page is the service provider's, even though the URL is on the merchant's domain. The pattern: every step you outsource to a Level 1 service provider's certified environment is a step you don't have to certify yourself. Pick service providers that take responsibility for the highest-scope parts of the flow. ## Types of PCI Compliance Service Providers The market segments into several distinct provider types, each owning a different part of the flow. ### Payment Gateways The original PCI service providers. Handle authorisation, transmission to the acquirer, settlement reconciliation. Examples: Stripe, Adyen, Checkout.com, Worldpay, Braintree, Authorize.Net. All operate at Level 1. ### Payment Processors and Acquirers Banks and bank-adjacent entities that hold the merchant account and route transactions to card networks. Examples: Chase Merchant Services, FIS / Worldpay (acquiring side), Wells Fargo Merchant Services, Barclaycard. All Level 1. ### Tokenisation / Vault Providers Specialised in storing card credentials and returning tokens for repeat use. Examples: Spreedly, Basis Theory, VGS (Very Good Security), TokenEx. Used when merchants want to maintain PSP optionality without holding card data themselves. ### Hosted Checkout / Payment Page Providers Run the actual card-entry page on their domain so merchants can claim SAQ A. Examples: Stripe Checkout, PayPal Checkout, Adyen Hosted Checkout, Braintree Drop-in. ### Voice Payment / DTMF Service Providers Specialised in voice payments and DTMF capture for contact centres. Examples include specialist voice-payment vendors and Shuttle Voice Checkout. Credible providers in this category operate at Level 1 to provide scope-reduction value. ### Payment Links / Pay-by-Link Providers Provide hosted checkout pages accessed via URL -- ideal for invoice payments, SMS-led flows, social commerce. Examples: Stripe Payment Links, Shuttle Payment Links, Square Payment Links, GoCardless Pay-Now. ### Payment Orchestrators / Multi-PSP Routers Sit between the merchant and multiple gateways, handling smart routing and scope reduction. Examples: Gr4vy, Spreedly, Primer, Shuttle. Most operate at Level 1; verify before assuming. ### Industry-specific PCI Service Providers Some service providers specialise by vertical -- healthcare (HIPAA + PCI), legal trust accounts, government, hospitality. The vertical specialisation is usually layered on top of standard Level 1 PCI compliance. ## How to Evaluate a PCI Compliance Service Provider Six questions cut through the marketing noise. 1. Show me the current AOC. Not the marketing page that says "PCI Level 1 certified". The AOC, dated within the last 12 months, signed by a QSA. If they can't or won't share it under NDA, walk away. 2. Which version of PCI DSS are you certified under? PCI DSS 4.0 is the current standard (replacing 3.2.1 fully by 31 March 2025). A current AOC will be against 4.0. Older AOCs against 3.2.1 are obsolete. 3. What's your cardholder data environment, and what stays out of it? A serious service provider has clear answers about CDE boundaries and what's logically segmented. If the answer is hand-wavy, they don't know -- which means their next audit might surprise them. 4. What scope reduction do you actually give my merchants? Different integration patterns = different SAQ outcomes. Ask: "If I use your hosted checkout, what SAQ do I qualify for?" The answer should be SAQ A (or A-EP if there's iframe / partial integration). If they're vague, the scope reduction may not actually exist. 5. How do you handle cardholder data -- and do you store it? Some providers vault. Some don't. Both are valid models, but you need to know which you're getting. If they vault, ask about the encryption model, key management (HSM-backed?), and breach response. If they don't vault -- like Shuttle -- clarify what they tokenise and where the actual card credential lives (typically the gateway). 6. What happens at *your* audit, and what's the breach process for *my* customers? The AOC is annual. Between audits, things change. Ask about continuous monitoring, change-control process, and the exact breach notification path that affects you as a customer (not just the regulator-facing path). ## What "PCI Compliance as a Service" Means "PCI Compliance as a Service" (sometimes "PCIaaS") is a framing rather than a defined product category. It usually describes one of three things: 1. Outsourced compliance management. Consultancies that manage your QSA relationship, run your scans, advise on remediation. You're still the entity being audited. 2. Bundled service provider offerings. A vendor that provides multiple Level 1 service provider services (gateway + vault + checkout + voice) under one AOC, simplifying the integration and audit story. 3. Turn-key compliance reduction platforms. Pre-integrated stacks designed to drop a merchant straight to SAQ A -- typically a hosted checkout + tokenisation + reporting bundle. All three are legitimate. None of them remove your PCI obligation entirely; they just shift the heaviest parts to specialists. Treat any vendor claiming "we make you PCI compliant" with appropriate scepticism -- your obligation as a merchant doesn't disappear, it just gets smaller. ## Industry-Specific Considerations Some industries layer additional requirements on top of standard PCI Level 1. - Healthcare -- HIPAA on top of PCI; service providers handling both must hold both certifications. Examples: dedicated healthcare payment processors and platforms. - Government -- FedRAMP for US federal, IL4/5 for some agencies. Layered on top of Level 1. - Legal / trust accounts -- bar-association rules, often state-specific, alongside PCI. - Hospitality -- restaurant / hotel-specific scope considerations around tipping, gratuity, room charges. See restaurant PCI compliance. - Voice / contact centre -- DTMF-specific controls and recording obligations. Layered on top of Level 1; see DTMF payments. - Insurance and financial services -- typically layered with FCA / PRA requirements in the UK, state insurance regulator requirements in the US. See PCI payments for insurance platforms. ## Shuttle as a PCI Compliance Service Provider Shuttle is a PCI DSS Level 1 Service Provider. The certification is renewed annually by an external QSA, with quarterly ASV scans and annual penetration testing. The Attestation of Compliance is available to customers and partners. Three architectural choices distinguish Shuttle's PCI posture from the typical service provider model. No card vault. Shuttle does not store card data. Tokenisation is handled by the underlying payment gateway -- Shuttle hands the gateway's token back to the merchant for repeat use, but never holds the card credential itself. This keeps Shuttle's blast radius small and keeps merchants from having to trust Shuttle as a card storage vendor in addition to a transaction router. Gateway-agnostic. Shuttle integrates with 40+ payment gateways and processors. The PCI scope reduction doesn't depend on a specific PSP -- merchants and platforms can route via any supported processor while keeping the same SAQ A outcome. Multi-channel coverage under one AOC. Voice (DTMF capture), payment links, embedded checkout, and orchestration all sit inside the same Level 1 environment. Merchants integrating across channels deal with one service provider, one AOC, one scope-reduction story. Shuttle also holds SOC 2 Type II and ISO 27001 certifications, with all data stored in Europe and full GDPR coverage. ICO registration: ZB059255. Full architectural documentation at docs.shuttleglobal.com. ## Frequently Asked Questions What is a PCI compliance service provider? A PCI compliance service provider is a third party certified to handle cardholder data on behalf of merchants. They take on the most demanding parts of PCI compliance -- card capture, transmission, storage -- so the merchant's own systems can stay out of PCI scope. What does PCI DSS Level 1 mean? PCI DSS Level 1 is the highest tier of compliance. For service providers, it requires processing 300,000+ card transactions per year, an annual on-site audit by a Qualified Security Assessor, quarterly external vulnerability scans, annual penetration testing, and an Attestation of Compliance signed by the QSA. What's the difference between a Level 1 merchant and a Level 1 service provider? The thresholds are different (6M+ annual transactions for Level 1 merchant; 300K+ for Level 1 service provider) and the audit obligations differ. Service providers are audited because a single breach affects all their merchants; the bar is correspondingly higher. Can a service provider make my business PCI compliant? A service provider can dramatically reduce your PCI scope, but they cannot remove your obligation entirely. As a merchant, you still need to complete an SAQ (typically SAQ A if you've outsourced everything sensitive) and meet the controls that apply to your remaining environment. How do I verify a PCI service provider's compliance? Ask for their current Attestation of Compliance (AOC), dated within the last 12 months and signed by a QSA. The AOC is the only document that proves the audit happened. Marketing claims of "PCI Level 1" without an AOC are not verifiable. What is "PCI compliance as a service"? "PCI compliance as a service" usually means either (1) outsourced compliance management by a consultancy, (2) bundled service provider offerings under one AOC, or (3) a turn-key platform that drops merchants straight to SAQ A. All three exist; none of them eliminate the merchant's PCI obligation -- they just minimise it. Do payment links require PCI compliance? Yes. Any system handling cardholder data -- including payment link hosted checkout pages -- needs PCI DSS coverage. Using a Level 1 service provider for the payment link's checkout drops the merchant to SAQ A. ## Related Reading - PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - agent-assisted, IVR and pause-resume patterns compared - DTMF Payments: Clamping, Masking & PCI Compliance - Voice Payments: The Complete Guide - AI Voice Agents and PCI Payments - Twilio PCI Compliance for Voice Payments - PCI Compliance Cost for Platforms - PCI Payments for Insurance Platforms - Best Payment Link Providers 2026 ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope ### PCI DSS v4 Implications for Service Provider (software vendors) ### Why You Should Have a Backup Payment Service Provider (PSP) ### Why Most Call Answering Services Can't Take Payments ### Shuttle vs PayFac-as-a-Service (Payrix, Finix) ### Payment Providers: How They Work & How to Choose (2026) ## Links - [DTMF capture](/guides/dtmf-payments/) - [voice payments](/guides/voice-payments/) - [DTMF interception](/guides/dtmf-payments/) - [White-label payment links](/guides/white-label-payment-links/) - [Shuttle Payment Links](/guides/best-payment-link-providers/) - [Gr4vy](/vs/gr4vy/) - [Shuttle](/platforms/voice-checkout/) - [restaurant PCI compliance](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [DTMF payments](/guides/dtmf-payments/) - [PCI payments for insurance platforms](/guides/pci-payments-insurance-platforms/) - [payment links](/guides/best-payment-link-providers/) - [embedded checkout](/guides/what-is-embedded-payments/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [payment link](/guides/best-payment-link-providers/) - [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/) - [DTMF Payments: Clamping, Masking & PCI Compliance](/guides/dtmf-payments/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [AI Voice Agents and PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Twilio PCI Compliance for Voice Payments](/guides/twilio-pci-compliance/) - [PCI Compliance Cost for Platforms](/guides/pci-compliance-cost-platforms/) - [PCI Payments for Insurance Platforms](/guides/pci-payments-insurance-platforms/) - [Best Payment Link Providers 2026](/guides/best-payment-link-providers/) - [Book a Call](/discovery/) - [BlogPCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope→](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) - [BlogPCI DSS v4 Implications for Service Provider (software vendors)→](/blog/pci-dss-v4-implications-for-service-provider-software-vendors/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogWhy Most Call Answering Services Can't Take Payments→](/blog/call-answering-service-payments/) - [ComparisonShuttle vs PayFac-as-a-Service (Payrix, Finix)→](/vs/payrix-finix/) - [BlogPayment Providers: How They Work & How to Choose (2026)→](/blog/what-is-payment-gateway-aggregation/) --- URL: https://www.shuttleglobal.com/guides/pci-compliant-phone-payments/ --- # PCI Compliant Phone Payments: How to Take Card Payments Over the Phone | Shuttle > Quick answer: taking card payments over the phone is fine under PCI DSS. What matters is how the card number travels. # PCI Compliant Phone Payments: How to Take Card Payments Over the Phone By Shuttle Team, July 15, 2026 Quick answer: taking card payments over the phone is fine under PCI DSS. What matters is how the card number travels. If your agents hear it, type it, or your call recordings capture it, your phone system, recordings, agent desktops and staff all fall inside PCI DSS scope. The compliant patterns keep the card number out of your environment entirely: the caller types it on their phone keypad and the digits route straight to the payment gateway (agent-assisted DTMF capture), or the caller pays through an automated IVR flow with no agent on the line. Implemented correctly, both patterns take those systems out of scope and cut your compliance validation down to a fraction of the alternative. Phone payments are a card-not-present channel the card brands call MOTO (mail order / telephone order). Every business that takes them has the same tension: the phone is where payments actually complete, and it's also the channel where card data most easily leaks into systems that were never meant to hold it. This guide covers what PCI DSS actually requires for phone payments, the patterns that keep you compliant, what US call recording laws add on top, and how to choose between the approaches. ## Why phone payments create a PCI problem PCI DSS applies to every system that stores, processes or transmits cardholder data, plus everything connected to those systems. The PCI Security Standards Council's guidance on telephone payments is explicit: when card numbers are spoken on a call, the "telephony environment" is in scope. That means: - Your phone system. VoIP platforms, SIP trunks and call routing all carry the spoken card number. - Your call recordings. A recording that captures a card number is stored cardholder data. Storing the security code (CVV) after authorization is prohibited outright, in any form, recording included. - Your agents' desktops. If the agent types the number into a virtual terminal, the workstation, its network and everything connected to it are in scope. - Your people. Staff who hear or see card numbers become part of the compliance surface: vetting, training and monitoring all follow. For a business taking a handful of phone payments a month, that scope might be manageable. For a call center taking hundreds a day, it means the whole operation lives inside the card data environment, with the assessments, controls and audit burden that brings. ## The compliant patterns, compared There are three established ways to take a card payment on a phone call while keeping card data away from your people and systems, plus two fallbacks worth having. ### Agent-assisted DTMF capture The agent stays on the call. When it's time to pay, the caller types their card number on their phone keypad. The keypad tones (DTMF) route directly to the payment gateway; the agent's line carries flat tones or silence, and their screen shows only masked progress, so the conversation continues while the card number never enters your phone system, recordings or screens. This is the pattern to reach for when payments happen inside a conversation: the agent can resolve the query, agree the amount, and take payment without transferring the caller anywhere. It's how DTMF payment capture works in detail. ### IVR self-payment The caller pays through an automated keypad flow with no agent involved: they call in (or are transferred), enter a reference and their card details, and get a confirmation. Because no member of staff is on the line, it's an unattended transaction, and when the IVR is hosted by a validated provider it typically qualifies the merchant for the lightest self-assessment route. IVR absorbs high-volume, low-exception payments: bill payments, balances, renewals. Agents handle the calls that need a human. ### Pause-and-resume recording The agent pauses the call recording while the caller reads out their card number, then resumes it after. This pattern is widely deployed and can be operated compliantly. Its weakness is operational: the card number still enters your phone system and your agent's ears, so those stay in scope, and the protection depends on the pause actually happening on every call. A missed pause means a recording with a card number in it. Automated triggers reduce that risk; they don't remove the underlying scope. ### The fallbacks that save real calls Phone payments fail in predictable ways, and the compliant answer isn't "read me the number after all": - Payment links. Caller's card is in another room, or the call drops mid-payment: send a link by SMS or email and they finish on their own device. - Bank payment on the call. Caller prefers not to use a card: take a bank transfer without leaving the conversation. See ACH and bank payments over the phone. ## What US call recording laws add PCI DSS is not the only constraint on a US phone-payment operation. Call recording consent is governed by federal and state law, and a number of states, California among them, require the consent of all parties to record a call. Most call centers already handle this with a recording notice, but it interacts with payments in one useful way: patterns that keep card data out of recordings entirely (DTMF capture, IVR) mean your recording practices and your payment compliance stop being tangled together. The recording can run for quality and dispute purposes without ever containing a card number. ## What this does to your PCI validation Merchant PCI DSS validation runs from SAQ A (a short self-assessment for merchants whose card data is fully handled by compliant third parties) up to SAQ D and full on-site assessments (hundreds of controls when card data touches your own systems). Where a given phone operation lands depends on the details and is worth confirming with your acquirer or assessor, but the direction is consistent: keypad capture and IVR patterns that keep card data out of your environment typically support the lighter end of that spectrum, and letting agents hear or key in card numbers pushes you toward the heavy end. The provider you use matters too: under PCI DSS, service providers that handle card data on your behalf must themselves be validated, and Level 1 is the strictest tier. Our guide to choosing a PCI compliant service provider covers what to check. ## How Shuttle handles PCI compliant phone payments Shuttle provides both compliant phone patterns through one layer: - Agent-assisted capture and IVR self-payment run on Twilio's voice infrastructure. Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. - Card details are tokenized with the payment gateway itself. Shuttle holds no card vault of its own, so there is no new place where card data accumulates. - Your gateway, not ours. Shuttle works with 40+ payment gateways, so phone payments settle through the merchant account you already have. Voice capture works on many supported gateways; payment links cover the rest. - The fallbacks are built in. Payment links by SMS or email and bank payments on the call, so a failed card moment doesn't become a lost payment. - Multi-client routing. If you take payments on behalf of many clients, each with their own merchant account (billing services, answering services, collections servicers), payments route to the right client's account automatically. See taking payments on behalf of your clients. ## Choosing between the approaches Agent-assisted DTMF Pause-and-resume Payment link Agent on the call Card data enters your systems Yes (spoken) Recording can run throughout No (must pause) Payments inside conversations High-volume routine payments Legacy operations Fallback and async Most phone-heavy operations end up running two of these side by side: IVR for the routine volume, agent-assisted capture for the conversations, with links as the recovery path. ## PCI compliant phone payments FAQ ### Is it legal to take card payments over the phone? Yes. Phone payments are a standard card-not-present channel (MOTO). The card brands and PCI DSS permit them; the requirements govern how the card data is handled, not whether the channel is allowed. ### Can my staff write down card numbers during a call? They shouldn't. A written card number is stored cardholder data on paper, in scope and hard to control, and writing down the security code is prohibited after authorization in any form. Keypad capture removes the need entirely. ### Do call recordings break PCI compliance? They can. A recording that contains a card number is stored cardholder data, and storing the security code post-authorization is prohibited in any form. Either pause recording during card capture, or use DTMF or IVR capture so recordings never contain card data in the first place. ### What's the difference between agent-assisted capture and IVR payments? Agent-assisted capture keeps a person on the call while the caller types their card number on the keypad; it suits payments that happen inside a conversation. IVR is fully automated with no agent involved; it suits routine, high-volume payments. Both keep card data out of your environment. ### Does using a compliant phone payment provider make my business PCI compliant? It takes the phone channel's heavy lifting off you, but your business still validates its own compliance. The gain is scope: with card data kept out of your systems, your validation typically shrinks to the lighter self-assessment routes. Confirm your exact SAQ level with your acquirer or assessor. ### Can I take phone payments for multiple clients through one system? Yes, if the system supports per-client merchant account routing. Each client connects their own merchant account, and every payment routes to the right one, which matters for billing services, answering services and other businesses collecting on behalf of clients. ## Related reading - Virtual Terminal Payments: PCI Rules and Secure Alternatives - IVR Payments: PCI Compliant Self-Service Phone Payments - Agent-Assisted Payments: Secure Card Capture on Live Calls - DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking - PCI Compliance Service Providers: Levels, Scope and What to Check - Voice Payments: The Complete Guide - AI Voice Agents and PCI Compliant Payments - Contact Centre Payments: The Complete Guide - Take Payments on Behalf of Your Clients Want phone payments out of your PCI scope? Talk to us. If you'd rather explore the technical side first, docs.shuttleglobal.com covers the flows, with sandbox accounts available for testing. ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### DTMF vs Payment Links: Which is More Secure for Phone Payments? ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [DTMF payment capture](/guides/dtmf-payments/) - [ACH and bank payments over the phone](/guides/ach-payments-over-the-phone/) - [choosing a PCI compliant service provider](/guides/pci-compliance-service-provider/) - [40+ payment gateways](/payment-providers/) - [taking payments on behalf of your clients](/guides/take-payments-on-behalf-of-clients/) - [Virtual Terminal Payments: PCI Rules and Secure Alternatives](/guides/virtual-terminal-payments/) - [IVR Payments: PCI Compliant Self-Service Phone Payments](/guides/ivr-payments/) - [Agent-Assisted Payments: Secure Card Capture on Live Calls](/guides/agent-assisted-payments/) - [DTMF Payment Processing: PCI Compliant Capture, Clamping & Masking](/guides/dtmf-payments/) - [PCI Compliance Service Providers: Levels, Scope and What to Check](/guides/pci-compliance-service-provider/) - [Voice Payments: The Complete Guide](/guides/voice-payments/) - [AI Voice Agents and PCI Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [Contact Centre Payments: The Complete Guide](/guides/contact-centre-payments/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [Talk to us](/contact/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [Book a Call](/discovery/) - [BlogDTMF vs Payment Links: Which is More Secure for Phone Payments?→](/blog/dtmf-vs-link-checkout-which-is-more-secure-for-customer-payments/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/pci-payments-insurance-platforms/ --- # PCI-Compliant Payment Architecture for Insurance Platforms | Shuttle > PCI scope is the single biggest reason insurance core platforms don't execute payments. # PCI-Compliant Payment Architecture for Insurance Platforms By Shuttle Team, February 23, 2026 PCI scope is the single biggest reason insurance core platforms don't execute payments. The moment card data enters the platform's environment -- in memory, in storage, in transit, in a call recording -- the platform is subject to PCI DSS. For a platform that manages policy data, claims, and billing across dozens of carriers, that's a compliance burden that dwarfs the value of adding a payment feature. For carrier-side and MGA-platform-specific payment architecture, see Payments for Insurance Carriers and MGA Platforms. This guide explains the architecture that eliminates that trade-off. Insurance platforms can execute payments -- across voice, links, and embedded checkout -- without card data ever touching their infrastructure. ## Why PCI Scope Is the Real Blocker Insurance core platforms handle sensitive data already: policyholder information, health data, financial records. Adding payment card data on top of that creates a new compliance surface that intersects with existing ones. The problem isn't just the PCI audit. It's what PCI DSS requires operationally: - Network segmentation between cardholder data environments and everything else - Encryption at rest and in transit for all card data - Access controls, logging, and monitoring for every system that touches card data - Annual penetration testing of the cardholder data environment - Quarterly vulnerability scans by an Approved Scanning Vendor - Incident response procedures specific to card data breaches - Staff training for everyone with access to payment systems For a platform that serves 20+ carriers, each with different security requirements and audit cycles, layering PCI on top of existing compliance obligations is a non-starter. ## The Architecture: Separating Card Capture from the Core Platform The solution is architectural, not procedural. Card data never enters the platform's environment. Period. ### How It Works - The platform initiates a payment request. The billing module identifies a premium due, or an agent reaches the payment moment in a call. The platform sends a payment request to The Payment Layer -- amount, currency, carrier ID, reference number. No card data. - The Payment Layer captures card data. Depending on the channel: - Voice: DTMF tones captured within The Payment Layer's PCI-certified telephony environment - Payment links: Hosted payment page served by The Payment Layer's infrastructure - Embedded checkout: iFrame or SDK component rendered from The Payment Layer's domain - The Payment Layer routes to the carrier's PSP. Each carrier has a pre-configured PSP connection. The layer routes the transaction to Stripe, Adyen, Worldpay, or whichever processor the carrier uses. - The platform receives a result. Transaction approved/declined, last four digits, reference ID. No card numbers, no CVVs, no expiry dates. The billing module updates. The conversation continues. At no point does the platform's infrastructure handle, process, or store card data. ## DTMF Capture for Voice Payments Insurance is a voice-heavy industry. Phone renewals, collections calls, and claim payment queries all create payment moments during conversations. ### The DTMF Architecture When a policyholder is ready to pay during a call: - The agent (human or AI) triggers the payment flow. The call enters a secure segment. - The policyholder enters card digits via keypad (DTMF tones). - DTMF tones are captured by The Payment Layer's PCI-certified environment -- not the platform's telephony stack. - Tones are stripped from the audio stream before reaching the agent, the call recording system, or any monitoring feed. - The payment processes through the carrier's PSP. - The agent receives confirmation -- "payment approved" -- and the conversation resumes. ### What Gets Stripped - Agent audio: DTMF tones are suppressed in real time. The digits never reach the agent during card entry. - Call recordings: No card data in any recording. Full compliance with PCI DSS Requirement 3 (protect stored cardholder data). - Screen pop / agent dashboard: Only last four digits displayed. No full card numbers visible to agents. - Quality monitoring: Supervisors and QA teams never have access to card data in reviewed calls. This is the same architecture used by Allianz, which runs call centre payments through Shuttle across 3 countries. Each country routes to Allianz's contracted processors. The contact centre agents never hear or see card data. ## Payment Links: Collecting Premiums Without Touching Card Data Payment links are the simplest path to limited-scope premium collection. ### How It Works for Insurance - The billing module identifies an overdue premium or upcoming renewal. - The platform generates a payment link via The Payment Layer API -- passing amount, currency, carrier PSP, and policy reference. - The link is sent to the policyholder via SMS or email. - The policyholder opens the link, sees a branded payment page (carrier branding, policy details), and enters card details. - The payment page is hosted entirely within The Payment Layer's PCI-certified infrastructure. - The transaction routes to the carrier's PSP. - The platform receives a webhook: payment confirmed, reference ID, last four digits. ### Why This Matters for PCI The payment page is on The Payment Layer's domain, rendered from The Payment Layer's servers, processed within The Payment Layer's PCI boundary. The platform's infrastructure is not involved in card capture at all. This is the cleanest possible PCI scope reduction. For the platform: SAQ-A. 22 self-assessment questions. No QSA audit required. No network segmentation. No cardholder data environment to maintain. ## Multi-Tenant PCI: Each Carrier's PSP, One Compliance Boundary The multi-tenant PSP problem is unique to platforms. A platform serves many carriers. Each carrier has its own PSP. The platform needs to route payments to the correct processor per carrier -- without building a separate PCI-compliant integration for each one. ### How The Payment Layer Handles This - One PCI boundary covers all carriers. The Payment Layer's PCI DSS Level 1 certification applies regardless of which PSP processes the transaction. - Per-carrier PSP routing is configuration, not code. When a new carrier onboards, their PSP connection is configured within the layer. No platform development required. - Tokenisation spans PSPs. Cards tokenised through The Payment Layer can be used for recurring payments regardless of which PSP processes them -- useful for premium installment plans that may need to fail over between processors. This means the platform achieves multi-PSP payment execution with a single compliance posture. Whether a carrier uses Stripe, Adyen, Worldpay, or a regional acquirer, the platform's PCI scope doesn't change. ## SAQ-A vs SAQ-D: The Cost Difference This is where the business case becomes concrete. ### SAQ-D (Full PCI Scope) If the platform handles card data -- even transiently: - 300+ requirements in the self-assessment questionnaire - Annual QSA audit by a Qualified Security Assessor -- typically $150K-$300K per year - Network segmentation between cardholder data environment and everything else - Dedicated security personnel for PCI operations - Quarterly ASV scans and annual penetration testing - Incident response plan specific to card data breaches - Total annual cost: $500K-$2M+ depending on complexity ### SAQ-A (Limited Scope) If the platform delegates all card handling to a PCI-certified provider: - requirements -- mostly confirming you don't handle card data - No QSA audit required -- self-assessment only - No network segmentation for payment data - No dedicated PCI security team - Total annual cost: Negligible -- part of normal security operations The difference is not marginal. It's the difference between a platform that can add payment execution in weeks and a platform that needs a year of compliance preparation before writing a line of payment code. ## What "Limited PCI Scope for the Platform" Actually Means Limited scope doesn't mean no responsibility. It means the platform's responsibility is limited to: - Not handling card data. No card numbers, CVVs, or expiry dates in the platform's systems, logs, or communications. - Using a PCI-certified provider. Verifying that The Payment Layer maintains current PCI DSS Level 1 certification. - Securing the integration. API keys, webhooks, and authentication between the platform and The Payment Layer must follow standard security practices. - Not circumventing the architecture. If a developer adds a text field that captures a card number, PCI scope returns instantly. What limited scope does NOT require: - Annual QSA audits - Cardholder data environment segmentation - Card data encryption infrastructure - PCI-specific incident response - Quarterly vulnerability scans of payment systems For insurance platforms already managing compliance obligations across multiple regulatory frameworks, minimising PCI scope is a material simplification. ## Related Reading - Payments for Insurance Core Platforms: The Complete Guide -- the full picture of embedded payment execution for insurance - How AI Voice Agents Take PCI-Compliant Payments -- the technical architecture for AI agent payment flows - PCI-Compliant Payments for Contact Centres -- agent-assisted and automated payment capture - What Are Voice Payments? -- the complete guide to IVR, agent-assisted, and AI voice payments - What is PCI DSS? | What is PCI Scope? | What is a Payment Layer? *Shuttle is PCI DSS Level 1, ISO 27001, and SOC 2 certified. Insurance platforms integrate once and execute payments across voice, links, and embedded checkout -- without card data entering their environment. See how it works or book a discovery call.* ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Agent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Why Insurance Call Centres Still Can't Take a Secure Payment ### Agentic Payments in 2026: The Infrastructure Guide for Platforms ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Adyen for Platforms Alternatives ## Links - [Payments for Insurance Carriers and MGA Platforms](/guides/payments-for-insurance-carriers-mga/) - [DTMF tones](/guides/dtmf-payments/) - [Stripe](/payment-providers/stripe/) - [Adyen](/payment-providers/adyen/) - [Worldpay](/payment-providers/worldpay-access/) - [Payment links](/merchants/links-checkout/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Payments for Insurance Core Platforms: The Complete Guide](/guides/payments-for-insurance-platforms/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [What Are Voice Payments?](/guides/voice-payments/) - [PCI DSS](/glossary/pci-dss/) - [PCI Scope](/glossary/pci-scope/) - [Payment Layer](/glossary/payment-layer/) - [See how it works](/platforms/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogAgent-Ready Commerce: How SaaS Platforms Prepare for AI-Driven Payments→](/blog/agent-ready-commerce-how-saas-platforms-prepare-for-ai-driven-payments/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogWhy Insurance Call Centres Still Can't Take a Secure Payment→](/blog/insurance-call-centre-payments/) - [BlogAgentic Payments in 2026: The Infrastructure Guide for Platforms→](/blog/agentic-payments-infrastructure-2026/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativeAdyen for Platforms Alternatives→](/alternatives/adyen-for-platforms/) --- URL: https://www.shuttleglobal.com/guides/phonely-payments/ --- # How to Take Payments on Phonely AI Voice Agents: PCI-Compliant Payments | Shuttle > Phonely is an AI phone answering platform for businesses. It answers inbound calls, books appointments, qualifies leads, and runs custom call flows, so... # How to Take Payments on Phonely AI Voice Agents: PCI-Compliant Payments By Shuttle Team, June 2, 2026 Phonely is an AI phone answering platform for businesses. It answers inbound calls, books appointments, qualifies leads, and runs custom call flows, so service businesses can handle every call without staffing a front desk. You configure the conversation, routing logic, booking steps, and payment workflows around how your business actually works. But when a Phonely agent needs to take a payment, card data cannot be allowed to enter the AI pipeline. This guide covers how to take PCI-compliant payments on Phonely AI voice agents using Shuttle, so your agents can collect card payments mid-call without putting your business or the call flow in PCI scope. Phonely advertises PCI-compliant infrastructure and lets you build a payment step into a call flow. But a payment workflow step is not the same as processing the payment. Phonely does not capture the card in an isolated environment, does not connect to a payment gateway, and does not charge the card. You still need a payment layer that captures the card away from the agent flow, keeps it out of your call logs, and actually processes it. If card digits enter the audio stream unprotected, your whole stack falls into PCI scope. Shuttle provides the payment layer that closes that gap. There is no native Phonely integration: instead, your application invokes Shuttle's Twilio-based secure capture, the card is captured in an isolated PCI-certified environment, and the result comes back to your application. This does require you to be a Twilio customer today. ## The Payment Challenge for Phonely Phonely is built for businesses, not developers, which means the goal is a working call flow rather than a custom payment stack. That goal still runs into the same compliance wall every voice AI platform hits. Card data cannot enter the AI pipeline. If a customer reads or keys in card digits during a Phonely call, that is cardholder data under PCI DSS. If it flows through the audio path, your transcription, call recordings, and any connected systems are all in PCI scope. A configured payment step is not payment processing. Phonely lets you add a payment workflow to a call flow, and it runs on PCI-compliant infrastructure. But that step still needs something to capture the card in isolation and route it to a gateway. The platform handling the conversation is not the same as the layer that charges the card. Building card capture yourself is not realistic. PCI DSS Level 1 certification costs $500,000+ upfront and $200,000+ per year, plus a Qualified Security Assessor, quarterly scans, and annual penetration testing. For a business that just wants its AI receptionist to take a deposit, that is a non-starter. Bolting on a separate payment line breaks the experience. Telling the caller to hang up and dial a payment number, or transferring them to a separate IVR, undoes the seamless agent experience and loses payments at exactly the wrong moment. The answer is a secure payment handoff that captures the card in an isolated environment and returns a clean result to your application. ## How Shuttle Works with Phonely Today There is no native Phonely integration. The handoff is API-driven and built on Shuttle's Twilio-based capture: you must be a Twilio customer, and your application code triggers the handoff at the point of payment. Shuttle handles every piece of card data inside its PCI DSS Level 1 certified environment, while Phonely runs the conversation. - Your Phonely agent runs the conversation: greeting, qualification, booking, and amount confirmation are handled by your Phonely call flow. - The payment is triggered: when payment is due, a webhook or tool step from your application calls Shuttle to create a payment session with the amount, currency, and gateway configuration. - A secure PCI capture takes the card: at the point of payment, the card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay, with Shuttle as the certified connector). The card digits are captured inside Shuttle's certified environment, so they never reach Phonely or the AI model. - Payment is processed: Shuttle tokenises the card and routes it to your configured gateway. Authorisation happens entirely inside Shuttle's certified environment. - Result returned to your application: Shuttle sends a webhook with the outcome, a transaction reference, and a masked card number. Your Phonely agent confirms the payment in the conversation. One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Phonely agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native Phonely integration is possible only as a paid project. ## How It Works: Step by Step Step 1: Payment intent recognised. Your Phonely agent reaches the point in the call flow where a payment or deposit is due. Step 2: Amount confirmed. The agent says the total and tells the customer they'll enter their card on the keypad. Step 3: Payment session created. A webhook from your application calls Shuttle's API with the amount, currency, and gateway config. Shuttle returns a session token. Step 4: Secure capture takes over. At the point of payment, a secure PCI DSS Level 1 capture takes over the card collection (today, via Twilio Pay, with Shuttle as the certified connector). This is the key step: the card is captured inside that secure PCI capture, so it never touches Phonely or the AI model. Step 5: Card details entered. Shuttle plays a secure prompt and the customer enters card number, expiry, and CVV via the keypad. Step 6: Card captured in isolation. Shuttle captures the digits in its certified environment. The card never reaches Phonely, so recordings never contain card data. Step 7: Payment processed. Shuttle tokenises the card and routes it to your gateway for authorisation. Step 8: Webhook received. Shuttle sends the result back: outcome, transaction reference, masked card number. Step 9: Agent confirms. Your Phonely agent confirms the payment and continues the conversation. The customer stays on the line throughout the capture, with no transfer to a separate line. Returning the caller to the same Phonely agent and call after payment works today: your Twilio flow routes the call back and passes a conversation ID, so the agent resumes with context. Shuttle provides the secure capture and the result webhook; the return leg is wiring your team owns. ## Multi-PSP Support Whether you process on Stripe today, your enterprise client mandates Adyen, or you run multiple locations that each bring their own gateway, Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed. - Per-client gateway configuration: each business or location can use its own PSP - Single integration: integrate with Shuttle once; gateway routing is configuration, not code - Multi-PSP routing: route by currency, region, card type, or custom rules - Failover: automatic fallback to a secondary gateway if the primary is unavailable For agencies and operators running Phonely agents across multiple businesses, this means offering payment capability to everyone without maintaining a separate gateway integration per client. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of payment security certification. What stays in your business / Phonely: conversation logic, booking, amount calculation, and handling of non-sensitive webhook results. None of this is cardholder data, so your business and the Phonely call flow stay out of PCI scope. What stays in Shuttle: secure card capture after the handoff, card tokenisation, gateway communication, and secure prompt playback, all inside the certified environment. Call recordings: because the card is entered during the secure PCI capture, the digits are never part of the audio Phonely processes or records, so there is no cardholder data in your recordings, logs, or systems. With Shuttle handling all card data, your business typically qualifies for SAQ-A, the simplest PCI compliance tier, rather than the SAQ-D obligations that taking card data yourself would trigger. ## Beyond Voice: Payment Links Payment links are the turnkey path. Mid-call, your application can send a secure link by SMS or email; the customer opens a hosted checkout page, pays, and the result returns to your application in real time. Links work even with gateways that do not support voice capture. Payment links suit higher-value transactions, mobile-first callers, customers who find keypad entry difficult, and post-call payments. Both methods use the same Shuttle infrastructure, and your application chooses which to use. ## Use Cases ### AI Receptionists and Appointment Booking Phonely agents for clinics, salons, dental practices, and service businesses can take a deposit or full payment to secure a booking before the call ends, cutting no-shows. ### Home and Field Services Plumbers, electricians, HVAC, and other trades using Phonely to answer calls can collect a call-out deposit or balance during the booking conversation rather than chasing payment afterwards. ### Inbound Bill-Pay and Account Payments Businesses fielding account and billing calls can take a payment in the same conversation rather than directing the caller to a website or a separate line. ### Lead Qualification to Purchase Agents that qualify inbound interest can close and collect payment in one call, capturing the card at the moment the customer commits. ## Integration Webhook-driven. Trigger a Shuttle payment session from your application and resume the conversation when the result webhook arrives. You build the agent-side orchestration; Shuttle provides the capture, payment links, and APIs. Built on Twilio Pay today. The secure capture currently runs over Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Sandbox available. Build your proof of concept against Shuttle's sandbox gateway and demo app, then run the full payment flow with test card numbers before going live. [$0.20 per successful transaction](/pricing/) for voice. No setup fees, no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## FAQ Does Shuttle have a native Phonely integration? No. There is no native Phonely integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native Phonely integration is possible only as a paid project. Does this require Twilio? Yes, today. The secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Does Phonely process payments on its own? Phonely runs PCI-compliant infrastructure and lets you add a payment step to a call flow, but it does not capture the card in isolation, connect to a payment gateway, or charge the card. Shuttle provides that secure capture and gateway connection. Can I build PCI-compliant payment capture myself on Phonely? Technically, but PCI DSS Level 1 certification runs $500,000+ upfront and $200,000+/year. Shuttle provides the same capability at $0.20 per successful transaction. What payment gateways does Shuttle support? 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You configure your gateway in Shuttle and it handles routing. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture. Can I use this for outbound calls? Yes. The same secure handoff works for outbound agents that need to collect payment during a call. Does the customer hear the agent during card entry? During the secure capture, Shuttle plays secure prompts and the agent's voice is paused. Once entry is complete, the agent resumes the conversation. To return the caller to the same agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## Related Reading - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents - Vapi Payments: secure payment capture for Vapi voice agents - Bland AI Payments: secure payment capture for Bland AI phone agents - How AI Voice Agents Take PCI-Compliant Payments: the technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared - The Payment Layer for AI Agents: why AI agents need a dedicated payment layer ## Add Payments to Your Phonely AI Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're using Phonely for AI call answering and need PCI-compliant payment capture: See Voice Checkout | Book a discovery call ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI scope](/glossary/pci-scope/) - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [30+ gateways](/payment-providers/) - [Retell AI Payments](/guides/retell-ai-payments/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/polyai-payments/ --- # How PolyAI Voice Agents Take Payments: PCI-Compliant AI Voice Payments | Shuttle > PolyAI deploys AI voice agents that handle hundreds of millions of conversations a year across insurance, hospitality, telecoms, and financial services. # How PolyAI Voice Agents Take Payments: PCI-Compliant AI Voice Payments By Shuttle Team, March 14, 2026 PolyAI deploys AI voice agents that handle hundreds of millions of conversations a year across insurance, hospitality, telecoms, and financial services. These agents handle everything from booking confirmations to policy renewals to account queries -- autonomously, at scale, without human agents. But every one of those conversations hits the same wall: "I'd like to pay now." AI voice agents -- no matter how sophisticated -- cannot natively process card payments. The AI model must never see, hear, or process cardholder data. That's not a product limitation. It's a compliance requirement under PCI DSS. A voice agent built on PolyAI needs a payment layer that can take the card securely and return the result, without the AI agent ever touching sensitive data. Shuttle is that payment layer. Shuttle has no native integration with PolyAI. Instead, your application code invokes Shuttle's Twilio-based payment setup. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, so the card digits are captured inside Shuttle's certified environment and never reach PolyAI, the LLM, or the agent. To use this path, you must be a Twilio customer, and your team builds the orchestration that triggers the handoff. ## The Payment Challenge for PolyAI PolyAI's voice agents are built on large language models fine-tuned for conversational AI. They understand context, handle complex multi-turn dialogues, and integrate with backend systems via APIs. But payments create a problem that no amount of model sophistication can solve. The moment a customer reads out a card number or enters it via their keypad, that data is cardholder data under PCI DSS. If it enters PolyAI's audio pipeline -- even as raw audio that gets transcribed -- PolyAI's entire voice infrastructure is in PCI scope. That includes the ASR pipeline, the LLM inference layer, call recordings, transcription storage, and every network segment those systems touch. PCI DSS Level 1 certification for that footprint would cost upwards of $500,000 in the first year, with $200,000+ in ongoing annual costs. It would also impose constraints on model training, data retention, and infrastructure architecture that would fundamentally slow down PolyAI's product development. The correct answer is to keep cardholder data out of PolyAI's platform entirely. That's what Shuttle does. ## How Shuttle Works with PolyAI Today Shuttle has no native integration with PolyAI. The handoff is API-driven: your application code triggers the Shuttle payment handoff, and the card is captured by Shuttle inside its PCI DSS Level 1 certified environment, never by PolyAI. To use the secure voice capture, you must be a Twilio customer, because today the capture runs over Twilio Pay. Shuttle provides ready-made interfaces for payment links plus the capture/IVR and the APIs. Your team builds the agent-side orchestration that triggers the handoff. You can build and validate the flow against Shuttle's sandbox gateway and demo app before going live. A deeper, native PolyAI integration is possible only as a paid project. Here's the architecture: - PolyAI manages the conversation -- The AI agent handles intent recognition, customer authentication, amount confirmation, and all conversational logic. It knows the customer wants to pay and how much they owe. - The call is handed to Shuttle's secure capture -- When payment is triggered, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. It operates within Shuttle's certified environment, completely isolated from PolyAI's infrastructure. - Card capture in isolation -- The customer enters their card on the keypad during the secure capture. The digits are captured by Shuttle inside its certified environment, so they never reach PolyAI, the LLM, or any recording. - Gateway routing -- Shuttle tokenises the card data and routes it to the appropriate payment gateway. The gateway is determined by the merchant's configuration -- different PolyAI customers can use different PSPs. - Result returned -- Shuttle fires a webhook with the transaction result: success or failure, a transaction ID, and a masked card reference. No card data. Your application records the result, and PolyAI's agent confirms the payment in natural language. One honest caveat to set expectations on up front: the secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same PolyAI agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. ## How It Works: Step by Step Here's what happens during a live PolyAI call when a customer is ready to pay: Step 1: Payment intent recognised. The PolyAI agent detects that the customer wants to make a payment. This might be explicit ("I'd like to pay my bill") or contextual (the agent has just confirmed an outstanding balance and the customer agrees to settle it). Step 2: Amount confirmed. The agent confirms the payment amount: "That's £247.50 for your policy renewal. I'll take your card details now -- you'll be prompted to enter them using your keypad." Step 3: Secure session initiated. PolyAI's platform makes an API call to Shuttle to create a payment session. The request includes the amount, currency, and the merchant's gateway configuration. Shuttle returns a session token. Step 4: Call handed to secure capture. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, with Shuttle as the certified connector. The card capture happens inside that secure environment, not inside PolyAI. Step 5: Card details entered. Shuttle plays a secure prompt: "Please enter your 16-digit card number followed by the hash key." The customer enters their card number, expiry date, and CVV via their phone keypad. Step 6: Digits captured in isolation. The card is captured by Shuttle inside its PCI DSS Level 1 certified environment. No card data enters PolyAI's infrastructure at any point. Step 7: Payment processed. Shuttle tokenises the card data and sends it to the merchant's configured payment gateway for authorisation. This happens within Shuttle's certified environment. Step 8: Result returned. The gateway returns an authorisation result. Shuttle sends a webhook: `payment_completed` with the outcome, a transaction reference, and a masked card number (e.g., `**4242`). Step 9: Conversation continues. Your application records the result, and the PolyAI agent confirms: "Your payment of £247.50 has been processed successfully. Your reference number is TXN-8834. Is there anything else I can help with?" The customer stays on the line for the secure capture, which keeps the experience close to the IVR keypad entry callers already know. To return the caller to the same PolyAI agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## Multi-PSP Support PolyAI serves enterprise customers across multiple industries and geographies. Those customers don't all use the same payment gateway. An insurance company in the UK might process through Worldpay. A hotel chain in the US might use Stripe. A telecoms provider in Europe might route through Adyen. PolyAI can't dictate which PSP its customers use -- and it shouldn't have to. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and others. Each customer's payment flow is routed to their configured gateway automatically, and switching gateways is configuration, not re-integration. Shuttle handles the gateway abstraction so you don't need separate integrations for each PSP. This also enables more sophisticated routing: - Geographic routing -- Route UK transactions through Worldpay, US transactions through Stripe - Failover -- if the primary gateway is down, you can move the affected payment types to another connected gateway - Merchant-level configuration -- Each customer can have their own gateway setup One gateway caveat worth knowing: a few gateways (Braintree, for example) do not work for voice capture, because they will not allow raw card data to be passed, but they do work for payment links. This means payment capability scales with your customer base without multiplying integration complexity. ## PCI Compliance The entire point of the Shuttle integration is to keep PolyAI out of PCI scope for card data. Here's what that means in practice: What PolyAI handles: - Conversation management, intent recognition, customer authentication - Payment amount confirmation and session initiation - Receiving transaction results (success/failure, reference numbers, masked card details) - None of this is cardholder data. None of it puts PolyAI in PCI scope. What Shuttle handles: - Card capture during the secure Twilio Pay handoff - Card data tokenisation - Gateway communication and authorisation - All of this happens within Shuttle's PCI DSS Level 1 certified environment. Call recordings: because the card is entered during the secure PCI capture, the card details are never part of the audio PolyAI processes or records. There is no cardholder data in any recording, transcript, or log that PolyAI stores. PCI scope for PolyAI customers: Because card data never enters PolyAI's infrastructure, end merchants can self-assess under SAQ-A -- the simplest PCI compliance tier. No penetration testing, no ASV scans on their end, no on-site QSA audits for payment processing. Shuttle is a PCI DSS Level 1 certified Service Provider. That certification covers the full card capture, tokenisation, and gateway routing pipeline. ## Beyond Voice: Payment Links The secure in-call capture is one method, but Shuttle also supports payment links, and they are the turnkey path. During a PolyAI conversation, the AI agent can send a payment link via SMS or email. Here's how it works: the PolyAI agent confirms the payment amount, then tells the customer "I've just sent a secure payment link to your mobile." Shuttle generates a hosted checkout page and delivers it. The customer taps the link, enters their card details on a secure page, and completes the payment. The result is returned to your application, and the agent confirms it in the conversation. Payment links are useful when: - The customer is on a mobile and can easily switch to a browser - The transaction involves a higher amount where customers prefer visual confirmation - The caller is uncomfortable entering card details via keypad - The gateway does not support voice capture, for example Braintree Both methods -- secure in-call capture and payment links -- are processed through the same Shuttle infrastructure, the same PCI-compliant environment, and the same gateway routing. Your application chooses the appropriate method based on context. ## What's Live Today Being straight about the current state matters more than a polished promise. Available now: the secure card capture at the point of payment, via Twilio Pay. When it is time to pay, the call is handed to the secure capture, the customer pays, and your application receives the result. The card never passes through PolyAI. Payment links are available now too, and they are the turnkey path. Not yet turnkey: Shuttle being present for the entire call. Today the secure capture is scoped to the point of payment, not the whole conversation. Returning the caller to the same PolyAI agent and call after payment works today when you program the return route in your Twilio flow and pass a conversation ID. On the roadmap: Shuttle works with Twilio today, and any carrier coming soon. If your flow needs the agent to pick the conversation back up seamlessly after payment, talk to us about where this work is, and we will give you the honest current state rather than overpromise. ## FAQ Does Shuttle have a native PolyAI integration? No. Shuttle has no native integration with PolyAI. The handoff is API-driven: your application code triggers Shuttle's Twilio-based payment setup, and at the point of payment the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. A native PolyAI integration is possible only as a paid project. Does this require Twilio? Yes, for the secure in-call capture. The capture runs over Twilio Pay today, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Can PolyAI agents take payments without Shuttle? Not compliantly. If the AI model processes card data -- even as audio -- PolyAI's entire infrastructure enters PCI scope. Shuttle provides the PCI-compliant bridge that keeps card data isolated from PolyAI's systems. What payment gateways does this work with? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and others. Switching gateways is configuration, not re-integration. A few gateways (Braintree, for example) do not work for voice capture but do work for payment links. Does the call return to my PolyAI agent automatically after payment? The secure card capture is available now via Twilio Pay. Returning the caller to the same PolyAI agent and call after payment works today: you program the return route in your Twilio flow and pass a conversation ID. The secure capture is scoped to the point of payment, and fuller call control is on the roadmap with the carrier-agnostic version. We will give you the honest current state for your flow rather than overpromise. What does it cost? Shuttle charges $0.20 per successful transaction for voice, with no setup fees, and no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). For technical detail, see the Shuttle docs: Twilio setup, payment links, and security and PCI. ## Related Reading - How AI Voice Agents Take PCI-Compliant Payments -- The technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide -- IVR, agent-assisted, and AI voice payment models compared - Twilio Pay Connectors -- How Shuttle connects to Twilio's payment infrastructure - The Payment Layer for AI Agents -- Why AI agents need a dedicated payment layer - Contact Centre Payments -- PCI-compliant payment capture for contact centres ## Add Payments to Your AI Voice Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're deploying AI voice agents and need PCI-compliant payment capture, talk to us about Voice Checkout or see how it works for platforms. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Shuttle and PolyAI - conversational payments ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI scope](/glossary/pci-scope/) - [30+ payment gateways](/payment-providers/) - [30+ gateways](/payment-providers/) - [Twilio setup](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](https://docs.shuttleglobal.com/docs/links-intro) - [security and PCI](https://docs.shuttleglobal.com/docs/org-security) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [talk to us about Voice Checkout](/platforms/voice-checkout/) - [see how it works for platforms](/platforms/) - [Book a Call](/discovery/) - [BlogShuttle and PolyAI - conversational payments→](/blog/shuttle-and-polyai/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/psp-neutral-vs-single-psp/ --- # PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform? | Shuttle > The Question Every Platform Faces At some point, every software platform that embeds payments hits the same fork in the road: Option A: Standardise on a... # PSP-Neutral vs Single-PSP: Which Approach Is Right for Your Platform? By Shuttle Team, December 16, 2025 ## The Question Every Platform Faces At some point, every software platform that embeds payments hits the same fork in the road: Option A: Standardise on a single PSP. Every merchant on your platform processes through Stripe, Adyen, or whichever gateway you've chosen. Option B: Support multiple PSPs. Merchants choose their preferred gateway, or you assign gateways based on region, volume, or use case. Option A is simpler. Option B is more flexible. The right answer depends on your merchants, your market, and how far you're planning to scale. Here's the honest analysis. ## The Single-PSP Approach ### How It Works Your platform integrates directly with one PSP -- typically Stripe (via Connect) or Adyen (via Adyen for Platforms). All merchants on your platform process through that single gateway. ### The Advantages Simplicity. One API. One set of webhooks. One dashboard. One contract. One relationship to manage. Engineering complexity is minimal. Speed to market. A single Stripe Connect integration can be live in days to weeks. No routing logic, no gateway abstraction, no multi-PSP configuration. Proven at scale. Stripe and Adyen have built excellent platform tools. Connect and Adyen for Platforms are mature products used by major marketplaces and SaaS companies. Support and documentation. Stripe's developer experience is industry-leading. You'll find answers to almost any integration question. ### The Limitations PSP lock-in. Your merchants must use your chosen PSP. If they have an existing relationship with a different gateway, they either switch or don't use your platform for payments. Enterprise deal friction. Enterprise customers -- insurance carriers, large retailers, travel operators -- often mandate their PSP. They have negotiated rates, existing contracts, and compliance requirements tied to a specific gateway. "Switch to Stripe" is not an acceptable answer. Geographic constraints. No single PSP offers optimal coverage and pricing in every market. Stripe's rates in Southeast Asia differ from Adyen's. A UK acquirer may be better for domestic transactions than a global PSP. No leverage. With a single PSP, you have no negotiating power. If rates increase or terms change, your only options are to accept or rebuild on a different gateway -- a project that takes months. Channel limitations. Most single-PSP integrations cover online checkout only. Voice payments, payment links via SMS, and AI agent payment capture typically require separate infrastructure. ## The PSP-Neutral Approach Your platform connects to a payment layer that supports multiple PSPs. Merchants are assigned a gateway based on their preference, geography, or your platform's configuration. Adding a new PSP is a configuration change, not an integration project. Enterprise deal enablement. When an enterprise customer says "we use Worldpay," you say "no problem." The deal doesn't stall on payment infrastructure. Merchant choice. Merchants bring their existing PSP relationships -- negotiated rates, established contracts, compliance setups. They don't have to start over. Geographic optimisation. Use the best acquirer for each region. Route UK transactions through a domestic acquirer. Route US transactions through a US processor. Optimise for authorisation rates and cost. Negotiating leverage. With multiple PSPs available, you're not locked into any single provider's terms. If Stripe raises rates, you route more volume to an alternative. This leverage is structural, not theoretical. Future-proofing. As payment methods evolve and new gateways emerge, adding support is configuration -- not engineering. More complex initial setup. A multi-PSP architecture has more moving parts than a single integration. Routing rules, gateway configuration, and merchant assignment all need design. Potentially slower to start. If you use a payment layer, integration is still fast (weeks). But it's not as instant as dropping in a Stripe checkout widget. ## What Forces the Decision In theory, you could stay on a single PSP forever. In practice, three forces push platforms toward multi-PSP: ### 1. Enterprise Customer Mandates This is the most common trigger. An enterprise customer in your pipeline says: "We use Worldpay. We're not switching." It happens in every vertical: - Insurance: Carriers require specific payment processors aligned with their compliance frameworks - Travel and hospitality: Airlines, hotel chains, and operators have existing PSP relationships with negotiated rates for their transaction volumes -- travel platforms face this across airlines, OTAs, and tour operators, and hotel payment collection is a common example where multi-PSP flexibility is essential - ERP/Finance: Enterprise clients won't change their treasury and payment infrastructure for a software vendor - Contact centres: BPO clients bring their own gateway and expect the platform to support it -- see Payment Collection for BPOs for the full multi-client PSP challenge You have three options: turn down the deal, build a custom integration for that PSP (months of work), or use PSP-neutral infrastructure that supports the gateway already. The first enterprise PSP mandate is the moment most platforms realise single-PSP won't scale. ### 2. Geographic Expansion Your platform launches in a new market. The PSP you've standardised on either doesn't support that region well, charges higher fees for cross-border transactions, or doesn't support local payment methods that are dominant in that market. A single PSP forces a trade-off: higher costs or limited functionality in new markets. Multi-PSP lets you use the optimal provider for each region. ### 3. Risk and Redundancy If your single PSP has an outage, your entire platform's payment processing stops. This isn't theoretical -- every major PSP has experienced outages. Multi-PSP provides failover: if one gateway is down, transactions route to another. ## The Transition Pattern Most platforms follow the same path: Stage 1: Single PSP. Platform integrates Stripe or Adyen. Works well for the first 50-200 merchants. Fast, simple, proven. Stage 2: Friction. Enterprise prospects require different PSPs. Geographic expansion hits coverage gaps. The platform starts scoping a second gateway integration. Stage 3: Decision point. Build a second PSP integration in-house (months of work, expanded PCI scope, ongoing maintenance) or adopt a PSP-neutral payment layer (weeks, single integration covers all gateways). Stage 4: Multi-PSP. The platform either builds and maintains multiple PSP integrations (expensive, slow) or uses a payment layer (fast, scalable). The payment layer path is more common because it solves the problem without consuming engineering resources. The platforms that recognise Stage 2 early and adopt a payment layer skip months of custom integration work. The ones that build integration-by-integration accumulate technical debt until the maintenance burden forces the switch anyway. ## Making the Decision ### Stay with a single PSP if: - All your merchants are comfortable with your chosen gateway - You don't serve enterprise customers with PSP mandates - You operate in a single geography with strong PSP coverage - Payment revenue optimisation is not a priority - You have no near-term need for voice, link, or AI agent payment channels ### Go PSP-neutral if: - Enterprise customers require specific gateways (or you anticipate they will) - You operate across multiple geographies (or plan to) - You want negotiating leverage with your PSP - You need multi-channel payment coverage (voice, links, chat) - You want to future-proof against PSP changes ### The hybrid approach Some platforms maintain a "default" PSP (Stripe for most merchants) while supporting alternative gateways for enterprise customers that require them. A PSP-neutral payment layer makes this straightforward -- most merchants route through the default, enterprise merchants route through their mandated gateway, all through the same integration and the same merchant experience. ## FAQ How many PSPs do I actually need? Most platforms use 2-4 actively. A primary gateway for the majority of transactions, one or two alternatives for enterprise mandates or geographic coverage, and optionally a backup for failover. The point of PSP-neutral infrastructure isn't to use all 40+ available gateways -- it's to support whichever ones your merchants require without rebuilding. Won't multiple PSPs complicate reconciliation? Not with a unified payment layer. Transactions from all gateways appear in one dashboard. Settlement data, refund tracking, and dispute management are consistent regardless of which PSP processed the transaction. The complexity is abstracted away. What about tokenisation across PSPs? This is a key technical consideration. If you tokenise a card with Stripe, that token only works with Stripe. A PSP-neutral payment layer provides its own tokenisation -- tokens work across any gateway. A card captured during a voice call can be charged later via a different PSP for an online transaction. Can I switch from single-PSP to multi-PSP without disrupting existing merchants? Yes. A payment layer can connect to your existing PSP. Current merchants continue processing through the same gateway. New merchants (or enterprise customers with mandates) use whichever gateway they require. The transition is additive, not disruptive. ## Related Reading - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways -- the #1 driver of multi-PSP adoption - When Your SaaS Outgrows Stripe Connect -- a migration playbook for platforms hitting single-PSP limits - Payment Orchestration vs Payment Layer -- the category distinction - Shuttle vs Stripe Connect -- how the single-PSP problem plays out with Stripe - Shuttle vs Adyen for Platforms -- how the single-PSP problem plays out with Adyen - What PSP Consolidation Means for Your Platform -- why acquirer M&A makes PSP-neutral architecture essential - PCI-Compliant Payments for Contact Centres -- why multi-PSP matters in the contact centre vertical - Payment Solutions for Travel Platforms -- multi-PSP, multi-currency payments for airlines, OTAs, and tour operators - Car Dealership Payment Solutions -- multi-PSP payment infrastructure for automotive platforms and dealer groups - Payment Infrastructure for Food Ordering Platforms -- why every restaurant using a different PSP is the core food platform payment problem - What Happens When Your Only Payment Processor Cuts You Off -- the business risk of single-PSP dependency Ready for PSP flexibility? Shuttle connects your platform to 40+ payment gateways through a single integration. Your merchants choose their PSP -- or you choose for them. White-label checkout, onboarding, and PCI compliance included. Book a Demo | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### What PSP Consolidation Means for Your Platform ### Why You Should Have a Backup Payment Service Provider (PSP) ### Where PSP Distribution Actually Lives ### Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know ### What Stripe's Unbundling Tells Us About the Future of Payments ## Links - [Stripe (via Connect)](/vs/stripe-connect/) - [Adyen (via Adyen for Platforms)](/vs/adyen/) - [mandate their PSP](/guides/enterprise-psp-mandates/) - [travel platforms](/guides/travel-platform-payments/) - [hotel payment collection](/guides/payment-links-for-hotels/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [maintenance burden forces the switch anyway](/guides/when-saas-outgrows-stripe-connect/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Payment Orchestration vs Payment Layer](/guides/payment-orchestration-vs-payment-layer/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [Shuttle vs Adyen for Platforms](/vs/adyen/) - [What PSP Consolidation Means for Your Platform](/blog/psp-consolidation-platform-risk/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Payment Solutions for Travel Platforms](/guides/travel-platform-payments/) - [Car Dealership Payment Solutions](/guides/car-dealership-payment-solutions/) - [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/) - [What Happens When Your Only Payment Processor Cuts You Off](/guides/single-psp-risk/) - [Book a Demo](/discovery/) - [See How It Works](/platforms/) - [Book a Call](/discovery/) - [BlogWhat PSP Consolidation Means for Your Platform→](/blog/psp-consolidation-platform-risk/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogWhere PSP Distribution Actually Lives→](/blog/where-psp-distribution-actually-lives/) - [BlogMulti-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know→](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-ach-payments/ --- # How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) | Shuttle > ACH is the cheapest way to get paid on a large invoice. Cards cost a percentage of every transaction, so a $10,000 invoice can cost you $250 or more in... # How to Accept ACH Payments in QuickBooks (Without Intuit's Processor) By Shuttle Team, June 12, 2026 ACH is the cheapest way to get paid on a large invoice. Cards cost a percentage of every transaction, so a $10,000 invoice can cost you $250 or more in fees. ACH (bank-to-bank transfer) usually costs a flat fee or a small capped percentage, which is why B2B sellers, agencies, and anyone invoicing four and five-figure amounts prefer it. The problem: QuickBooks makes you choose between Intuit's own processor and manual bank-transfer chasing. This guide shows a third option, collecting ACH on your QuickBooks invoices through a gateway you choose, with every payment recorded back against the invoice automatically. ## Does QuickBooks Charge for ACH Payments? Yes. If you use QuickBooks Payments (Intuit's native processor), ACH costs 1% per transaction, capped at $10. So a $500 invoice paid by ACH costs $5, and any invoice above $1,000 costs the flat $10 cap. Card payments through the same processor cost 2.99%. That capped rate is competitive, but it comes with three catches: - US only. QuickBooks Payments ACH is not available outside the United States. - Intuit lock-in. You process through Intuit or not at all. If you already use Stripe, Authorize.net, or another gateway elsewhere in your business, you now run two payment stacks. - No bank payments over other channels. The native button only works inside the invoice. There is no way to take an ACH payment over the phone or via a link you send by text. If those limits do not bother you, Intuit's native ACH is a reasonable option for invoice-only collection. For everything else, you can collect ACH through your own gateway instead. ## Option 1: QuickBooks Payments (Intuit Native ACH) Intuit's processor adds a "Pay Now" button to invoices that supports both card and ACH. - Native, no extra setup beyond enabling - Auto-reconciliation built in - ACH capped at $10 per transaction Limitations: - You cannot use your existing gateway - ACH only works inside the QuickBooks invoice, not over the phone or via standalone links - One processor, one set of rates, no routing flexibility ## Option 2: Collect ACH Through Your Own Gateway with Shuttle Shuttle adds ACH collection to QuickBooks invoices through any gateway that supports ACH, such as Stripe or Authorize.net. You keep your existing processor, your existing rates, and your existing banking relationship. Shuttle is the layer that connects that gateway to QuickBooks and reconciles the payment. Here is how it works: - Install the Shuttle QuickBooks Online Invoice Payments app - Connect the payment gateway you already use for ACH - Add a payment option to your QuickBooks invoices - Customers pay by bank transfer from the invoice - The payment is recorded against that invoice in QuickBooks automatically No manual matching, no second payment stack, no switching processor. If your gateway supports ACH, Shuttle can collect it on your QuickBooks invoices. ### Why route ACH through your own gateway - Keep your rates. If you have negotiated ACH pricing with your provider, you keep it. - One processor across the business. The same gateway handles your card, ACH, and other payments, so reconciliation and reporting stay in one place. - Not US-locked at the platform level. Your coverage follows your gateway, not Intuit's US-only ACH rule. - PCI DSS Level 1. Bank and card details are handled in a compliant environment. ## ACH Over the Phone: Voice Payments Most ACH-on-invoice tools stop at the invoice. Shuttle also collects ACH over voice, through Voice Checkout. A customer on a call can pay an invoice by bank transfer without reading card numbers aloud and without leaving the call to find a link. This matters for businesses that still close and collect by phone: B2B sales, accounts-receivable teams chasing overdue invoices, field service, and contact centres. The agent confirms the invoice, the customer authorises the bank payment on the call, and the payment posts back to QuickBooks like any other. Card-only voice solutions cannot do this. ## ACH vs Card on QuickBooks Invoices: Which to Use Both have a place. The right choice depends on invoice size and customer. ACH (bank transfer) Cost on large invoices Low (flat or capped) High (percentage of total) Settlement speed 1 to 4 business days Often same or next day B2B, large invoices, recurring billing Smaller invoices, consumer, instant need Customer friction Bank details once, low after Card details each time unless saved Chargeback profile A common pattern: offer ACH as the default on large B2B invoices to protect margin, and card for smaller or one-off payments where speed matters more than fees. ## Recurring ACH on QuickBooks Invoices For retainers, subscriptions, and payment plans, ACH is well suited to recurring billing because the per-transaction cost stays low even as volume grows. With a gateway that supports recurring ACH, Shuttle can collect scheduled bank payments and record each one against the relevant QuickBooks invoice. This removes the manual step of re-requesting payment every cycle and keeps the books matched without a reconciliation backlog. ## How ACH Payments Reconcile Back into QuickBooks The reconciliation problem is the reason most businesses avoid mixing gateways and QuickBooks: payments arrive in one system and invoices live in another, so someone has to match them by hand. Shuttle closes that gap. When a customer pays an invoice by ACH, the QuickBooks Online Invoice Payments app marks that specific invoice as paid and records the payment against it. Whether the payment came from the invoice, a link, or a voice call, it lands in the same place. Finance sees a matched, paid invoice rather than an unallocated deposit. ## QuickBooks ACH Payments FAQ Does QuickBooks charge for ACH payments? Through QuickBooks Payments (Intuit's processor), ACH costs 1% per transaction capped at $10. If you collect ACH through your own gateway with Shuttle, you pay your gateway's ACH rate instead. How long do ACH payments take to settle? ACH typically settles in 1 to 4 business days, slower than card but cheaper, which is why it suits larger and recurring invoices. Can I take recurring ACH payments in QuickBooks? Yes, with a gateway that supports recurring ACH. Shuttle collects scheduled bank payments and records each against the matching QuickBooks invoice. Is ACH on QuickBooks invoices secure? Yes. Payments run through your gateway in a PCI DSS Level 1 compliant environment, and bank details are never handled manually. Can I collect ACH over the phone? Yes. Shuttle's Voice Checkout takes ACH bank payments on a live call and posts them back to QuickBooks, which card-only phone payment tools cannot do. ## Get Started If your gateway supports ACH, you can collect it on your QuickBooks invoices without switching processor and without manual reconciliation. - See QuickBooks payment options and connect your gateway - Add payment links to invoices: QuickBooks Payment Links - Full setup walkthrough: How to Accept Payments on QuickBooks Invoices - Collect bank payments over the phone: Voice Checkout - Questions about your gateway or pricing? Talk to us or see pricing ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### QuickBooks ACH Payments: Setup, Fees & Tips ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### How to Accept Payments in QuickBooks: Full Guide ## Links - [Shuttle QuickBooks Online Invoice Payments app](/quickbooks-online) - [Voice Checkout](/platforms/voice-checkout/) - [QuickBooks Online Invoice Payments app](/quickbooks-online) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [QuickBooks payment options](/quickbooks-online/) - [QuickBooks Payment Links](/guides/quickbooks-payment-links/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [Talk to us](/contact/) - [pricing](/pricing/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogHow to Accept Payments in QuickBooks: Full Guide→](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-braintree-payments/ --- # Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree | Shuttle > Braintree -- PayPal's full-stack payment gateway -- handles card processing, PayPal, Venmo, Apple Pay, and Google Pay through a single integration. # Braintree + QuickBooks Integration: Accept Invoice Payments via Braintree By Shuttle Team, March 16, 2026 Braintree -- PayPal's full-stack payment gateway -- handles card processing, PayPal, Venmo, Apple Pay, and Google Pay through a single integration. It's the gateway of choice for businesses that want the flexibility of card processing with the reach of PayPal, all under one roof. But Braintree doesn't connect to QuickBooks invoices natively. If you want online payment on your invoices, Intuit pushes you toward QuickBooks Payments -- their own processor -- which means splitting your payment stack and losing the Braintree features you chose specifically. This guide walks through how to connect Braintree to QuickBooks Online using Shuttle, so invoice payments process through your Braintree account and reconcile automatically. ## Why Braintree Users Hit a Wall with QuickBooks Braintree is popular with businesses that need more than basic card processing. The typical Braintree merchant chose it because: - PayPal + cards in one gateway. No need for separate integrations. One account, one dashboard, one settlement. - Venmo support. For US merchants, Venmo is a significant payment method -- especially for younger demographics and consumer-facing businesses. - Apple Pay and Google Pay. Mobile wallet support built into the gateway. - PayPal's fraud protection. Braintree transactions benefit from PayPal's network-level fraud data -- one of the largest transaction datasets in the world. - Transparent pricing. Braintree's standard rate (2.59% + 49c for cards, 3.49% + 49c for PayPal/Venmo) is straightforward and competitive. None of these advantages carry over to QuickBooks Payments. If you switch to Intuit's processor for invoice payments, you lose PayPal acceptance, Venmo, and your existing Braintree rates. You also split your reporting between two platforms. The usual workaround -- including bank details on invoices and waiting for manual transfers -- defeats the purpose of having a modern payment gateway. ## How Shuttle Connects Braintree to QuickBooks Shuttle's QuickBooks Online Invoice Payments app bridges Braintree and QuickBooks Online. It adds a payment link to your invoices that processes through your Braintree account. - Customer receives your QuickBooks invoice - They click the payment link - A secure checkout page opens with card, PayPal, Apple Pay, and Google Pay options - Payment is processed through your Braintree account - Funds settle to your Braintree-connected bank account - The payment is automatically recorded in QuickBooks -- invoice marked as "Paid" Your Braintree account, PayPal acceptance, and processing rates stay exactly as they are. ## Setup Guide: Braintree + QuickBooks via Shuttle ### Prerequisites - A QuickBooks Online account (any plan) - An active Braintree merchant account - Your Braintree API credentials (Merchant ID, Public Key, Private Key) ### Step 1: Install the Shuttle App Go to shuttleglobal.com/quickbooks-online and click "Get App." Authorise QuickBooks access through the standard OAuth flow. ### Step 2: Connect Braintree In the Shuttle dashboard, select Braintree as your payment gateway. Enter your Braintree credentials: - Merchant ID -- found in the Braintree Control Panel under Settings → Business - Public Key -- under Settings → API → Keys - Private Key -- generated from the same location Shuttle validates the credentials immediately. Green confirmation means you're connected. ### Step 3: Configure Payment Settings Enable the features that matter for your invoicing: - Saved cards -- returning customers save card details for faster future payments. Tokenised securely via Braintree's Vault. - Partial payments -- accept deposits or staged payments against invoices. The balance updates in QuickBooks automatically. - Email notifications -- instant alerts when payment is received. - Custom branding (Basic plan, $16/month) -- your logo on the checkout page and a custom payment URL. ### Step 4: Add the Payment Link to Invoices Copy your unique payment link from the Shuttle dashboard. In QuickBooks Online: - Go to Settings → Custom Form Styles - Edit your invoice template - In the message/notes section, add: "Pay online: [your payment link]" Every invoice now includes a clickable link to pay through Braintree. ## The Braintree Advantage: PayPal on Your Invoices Here's what makes the Braintree + QuickBooks connection particularly valuable: PayPal acceptance on invoices. QuickBooks Payments doesn't support PayPal. Stripe doesn't offer native PayPal. But Braintree -- as PayPal's own gateway -- provides seamless PayPal checkout alongside card payments. Why this matters: - PayPal has 430+ million active accounts worldwide. Many of your customers already have PayPal and prefer to use it. - PayPal payments have higher completion rates. Customers don't need to enter card details -- they log in and confirm. Less friction, faster payment. - B2B PayPal usage is growing. Business accounts with PayPal balances are increasingly common. Offering PayPal on invoices taps into money that's ready to be spent. - Buyer protection builds trust. Customers paying a new supplier may feel more comfortable with PayPal's purchase protection layer. Through the Shuttle checkout page, your QuickBooks invoice customers see both card payment and PayPal as options. They choose what suits them, and payment reconciles to QuickBooks either way. ## Braintree Features That Work Through Shuttle Braintree Feature Supported via Shuttle Card payments (Visa, Mastercard, Amex) Google Pay Braintree Vault (saved cards) Yes -- your Braintree rules apply Fraud protection (PayPal network data) Multi-currency Yes -- based on your Braintree account Venmo (US) Depends on configuration Recurring billing (Braintree subscriptions) Not directly -- use Shuttle's partial payments Your Braintree fraud settings, 3D Secure configuration, and risk rules remain active on all transactions -- including those from invoice payment links. ## QuickBooks Payments vs. Braintree via Shuttle QuickBooks Payments Braintree via Shuttle Processing rates 2.99% + 25c (cards), 1% ACH Your Braintree rates (2.59% + 49c standard) PayPal acceptance Yes -- native Braintree PayPal Yes (where configured) Apple Pay / Google Pay Availability Global (Braintree operates in 40+ countries) Auto-reconciliation Saved cards Yes (Braintree Vault) Partial payments Custom branding QuickBooks branding Your brand (Basic plan) Fraud protection PayPal network-level data Monthly cost Included with QuickBooks Free plan available, Basic $16/month The differentiator is clear: if you want PayPal, Apple Pay, and Google Pay on your invoices -- processed through a single gateway -- Braintree via Shuttle is the only path that doesn't require multiple integrations. ## When Braintree + QuickBooks Makes Sense You already use Braintree for your website or app. Routing invoice payments through the same account consolidates your reporting and simplifies reconciliation. One gateway for everything. Your customers want PayPal. If you're in a B2C or B2SMB market where customers have PayPal accounts, offering it on invoices increases the likelihood of fast payment. This is especially true for creative agencies, consultancies, and service businesses invoicing consumers or small business clients. You need international coverage. Braintree operates in 40+ countries and supports multi-currency processing. QuickBooks Payments is US-only. You want one provider for cards + PayPal. The alternative is Stripe for cards and a separate PayPal integration -- two dashboards, two settlements, two reconciliation flows. Braintree combines them. You value fraud protection. Braintree's fraud tools leverage PayPal's transaction network, which is one of the largest in the world. That protection extends to invoice payments processed through Shuttle. ## Pricing Shuttle Free plan: - Auto-record payments in QuickBooks - Saved cards (via Braintree Vault) - Email notifications - PCI DSS Level 1 compliant - No Shuttle transaction fee (your Braintree rates apply) Shuttle Basic plan ($16/month): - Everything in Free - Your logo on the checkout page - Custom payment URL - No advertising on checkout - Email support - 25% discount if paid annually Braintree fees are unchanged. Shuttle doesn't add to your Braintree processing rates. Standard Braintree fees apply to every transaction. ## Common Questions ### Can customers choose between card and PayPal on the same checkout? Yes. The Shuttle checkout page presents all payment methods enabled on your Braintree account. Customers see card fields, PayPal button, Apple Pay, and Google Pay -- and choose their preference. The payment reconciles to QuickBooks regardless of which method they use. ### Does Braintree Vault (saved cards) work? Yes. Returning customers can save their card details during checkout. Next time they pay an invoice, their saved card is available for one-click payment. Tokens are stored securely in Braintree's Vault -- PCI compliant, no card data on your side. ### I use Braintree for my ecommerce site -- any conflict? None. Shuttle uses your Braintree account for invoice payment links only. Your website checkout, mobile app integration, and any other Braintree connections continue independently. ### Is 3D Secure supported? Yes. 3D Secure authentication is triggered based on your Braintree configuration and the relevant regulations (PSD2/SCA for EU/UK). This protects you from chargebacks on authenticated transactions. ### What about Braintree sandbox for testing? You can connect a Braintree sandbox account to test the full flow -- process test transactions, verify auto-reconciliation in QuickBooks, and confirm everything works before going live with production credentials. ### We also process Venmo -- does that work on invoices? Venmo support through Shuttle depends on your Braintree configuration and is subject to Braintree's Venmo availability (currently US only). Contact us to confirm Venmo support for your setup. ## Related Guides - How to Accept Payments on QuickBooks Invoices - QuickBooks Payment Links: Add Pay Now to Any Invoice - Authorize.net + QuickBooks: Complete Integration Guide - QuickBooks Stripe Payments - QuickBooks Worldpay Payments - QuickBooks PayPal Payments - Braintree PSP Overview ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### QuickBooks ACH Payments: Setup, Fees & Tips ### How to Accept Payments in QuickBooks: Full Guide ## Links - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [QuickBooks Stripe Payments](/guides/quickbooks-stripe-payments/) - [QuickBooks Worldpay Payments](/guides/quickbooks-worldpay-payments/) - [QuickBooks PayPal Payments](/guides/quickbooks-paypal-payments/) - [Braintree PSP Overview](/payment-providers/braintree/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogHow to Accept Payments in QuickBooks: Full Guide→](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-invoice-payments/ --- # How to Accept Payments on QuickBooks Invoices (Without Switching Provider) | Shuttle > You've sent the invoice. It's sitting in your customer's inbox. And now you wait -- 30 days, 45 days, sometimes longer -- for a cheque, a bank transfer, or... # How to Accept Payments on QuickBooks Invoices (Without Switching Provider) By Shuttle Team, February 20, 2026 You've sent the invoice. It's sitting in your customer's inbox. And now you wait -- 30 days, 45 days, sometimes longer -- for a cheque, a bank transfer, or a phone call asking for your bank details. QuickBooks makes invoicing easy. Collecting is the problem. This guide walks through how to add online payment capability to your QuickBooks invoices so customers can pay by card, PayPal, Apple Pay, or Google Pay -- directly from the invoice. And critically, how to do it without switching away from your existing payment gateway. To collect bank payments specifically, see How to Accept ACH Payments in QuickBooks. ## The QuickBooks Payment Collection Problem QuickBooks Online is used by millions of small and mid-sized businesses globally. The invoicing feature is mature -- recurring invoices, customisation, automated reminders. But when it comes to actually getting paid, businesses hit a wall: - QuickBooks Payments (Intuit's own processor) works natively but locks you into their rates and is only available in the US - Third-party gateways you already use (Authorize.net, Stripe, Worldpay, Braintree) don't plug into QuickBooks invoices natively - Manual reconciliation is the default -- payments come in via one system, invoices live in another, and someone has to match them The result: invoices go out fast, payments come back slow, and finance teams spend hours reconciling. ## Option 1: QuickBooks Payments (Intuit Native) Intuit's own payment processor integrates directly with QuickBooks Online. Customers see a "Pay Now" button on invoices. - Native integration -- no setup required beyond enabling - Auto-reconciliation built in - ACH and card payments supported Limitations: - Intuit sets the processing rates (2.99% card, 1% ACH with $10 max) - You can't use your existing gateway -- it's Intuit or nothing - No multi-PSP support -- if you process through Stripe, Worldpay, or Authorize.net elsewhere, you now have two payment stacks to manage - Limited payment methods compared to specialist gateways For US-only businesses with simple payment needs and no existing gateway relationship, QuickBooks Payments works. For everyone else, there's a gap. ## Option 2: Add Payment Links to QuickBooks Invoices The alternative: connect your existing payment gateway to QuickBooks and add a payment link to every invoice. Customers click, pay, and the payment is recorded back into QuickBooks automatically. This is what Shuttle's QuickBooks Online Invoice Payments app does: - Connect your gateway -- Authorize.net, Braintree, PayPal, Stripe, Worldpay, and more - Get a payment link -- a unique URL tied to your QuickBooks account - Paste into invoices -- add the link to your invoice template or individual invoices - Customer pays -- they click, enter card details (or use Apple Pay / Google Pay), and pay - Auto-recorded -- the payment is automatically recorded back into QuickBooks, matched to the invoice No migration. No switching processors. Your existing gateway rates, settlement, and merchant account stay exactly as they are. ### Why This Matters for Your Business Keep your negotiated rates. If you've spent years building a relationship with your payment provider and negotiating processing rates, you shouldn't have to abandon that just to add a pay button to invoices. One payment stack. Instead of running QuickBooks Payments alongside your existing gateway, everything processes through the same provider. One set of reports, one settlement, one relationship. Works internationally. QuickBooks Payments is US-only. If you invoice customers in the UK, EU, Australia, or anywhere else, you need a gateway that supports those regions. Shuttle connects your international-capable gateway to QuickBooks. More payment methods. Depending on your gateway, customers can pay by card, PayPal, Apple Pay, Google Pay, and local payment methods -- more options than QuickBooks Payments offers natively. ## How to Set It Up (5 Minutes) Setting up online invoice payments in QuickBooks via Shuttle takes about 5 minutes: ### Step 1: Install the App Go to the QuickBooks Online Invoice Payments app and click "Get App." Connect your QuickBooks Online account via OAuth -- standard QuickBooks app authorisation. ### Step 2: Connect Your Payment Gateway Choose from the supported gateways: - Authorize.net -- the most popular gateway among QuickBooks users (full integration guide) - Stripe -- if you already process cards through Stripe - Braintree -- PayPal's gateway for card processing - PayPal -- direct PayPal payments - Worldpay -- for UK and international merchants - USAePay -- US-focused gateway Enter your gateway credentials or connect via OAuth. Your existing merchant account and rates remain unchanged. ### Step 3: Configure Settings Choose which features to enable: - Saved cards -- customers can save card details for faster future payments - Partial payments -- accept deposits or instalments against invoices - Email notifications -- get alerted the moment a payment is made - Custom branding (Basic plan) -- your logo and custom payment URL ### Step 4: Add the Link to Invoices Copy your unique payment link and paste it into your QuickBooks invoice template. Every invoice you send will now include a "Pay Online" option. Alternatively, add the link to specific invoices only -- useful if some customers prefer bank transfer. ## What Your Customer Sees When a customer receives your invoice with the payment link: - They click the link - A branded checkout page opens (your logo on the Basic plan) - They enter card details or choose Apple Pay / Google Pay - Payment is processed through your gateway - They see a confirmation - The payment is auto-recorded in QuickBooks against the correct invoice No account creation. No app download. No friction. Just click and pay. ## Auto-Reconciliation: The Real Time Saver The biggest operational win isn't the faster payment -- it's the automatic reconciliation. Every payment processed through the link is recorded back into QuickBooks against the correct invoice. The invoice status updates to "Paid" (or "Partial" for deposits). Your books stay accurate without anyone manually matching bank statements to invoices. For businesses sending 50+ invoices per month, this eliminates hours of manual reconciliation work. ## Pricing Free plan: Auto-record payments, saved cards, partial payments, email notifications, PCI DSS Level 1 compliance. No transaction fee from Shuttle (your normal gateway fees apply). Basic plan ($16/month): Everything in Free, plus your own logo on the checkout page, a custom payment URL, no advertising, and email support. 25% discount if paid annually. See full pricing → ## When to Use QuickBooks Payments vs. a Payment Link Solution QuickBooks Payments Payment Link (Shuttle) US-only, no existing gateway Works, but unnecessary Existing gateway relationship Forces you to switch or run two stacks Keep your gateway International invoicing Not supported Works with any international gateway Multiple payment methods Cards + ACH Cards, PayPal, Apple Pay, Google Pay, local methods Custom branding Full branding on Basic plan Multi-PSP environment Single provider only Connects to 40+ gateways Auto-reconciliation ## Frequently Asked Questions ### Can I use this with QuickBooks Desktop? The Shuttle app is designed for QuickBooks Online. If you're on QuickBooks Desktop, you can still use Shuttle Payment Links to send payment links to customers -- the reconciliation back to QuickBooks Desktop would be manual. ### Does this replace my payment gateway? No. Shuttle connects to your existing gateway. Your processing rates, merchant account, and settlement don't change. Shuttle adds the invoice payment link on top. ### Is it PCI compliant? Yes. Shuttle is a PCI DSS Level 1 service provider. Card data is handled securely and never touches your systems or QuickBooks. ### Can customers save their card for next time? Yes. The saved card feature works with all supported gateways. Customers can opt in to save their details for faster payments on future invoices. ### What about partial payments or deposits? Supported. You can accept partial payments against an invoice. The remaining balance updates automatically in QuickBooks. ### How fast do I get paid? Settlement depends on your gateway -- typically 1-2 business days for card payments. The key improvement is reducing DSO (days sales outstanding): instead of waiting 30-45 days for a manual payment, customers pay within days of receiving the invoice. ## Related Guides - QuickBooks Payment Links: Add Pay Now to Any Invoice - Authorize.net + QuickBooks: Complete Integration Guide - What Is Embedded Payments? - Payment Links for Stripe - How to Choose a Payment Platform - Stripe + QuickBooks Integration -- accept invoice payments via Stripe - Worldpay + QuickBooks Integration -- pay invoices through Worldpay - Braintree + QuickBooks Integration -- accept payments via Braintree (PayPal + cards) - PayPal + QuickBooks Integration -- add PayPal to QuickBooks invoices ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. ## Related Reading Explore More ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### Sage Invoice Payments: How to Let Customers Pay Online ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ## Links - [How to Accept ACH Payments in QuickBooks](/guides/quickbooks-ach-payments/) - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [QuickBooks Online Invoice Payments app](/quickbooks-online) - [full integration guide](/guides/authorize-net-quickbooks/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [See full pricing →](/quickbooks-online) - [Shuttle Payment Links](/merchants/links-checkout) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [What Is Embedded Payments?](/guides/what-is-embedded-payments/) - [Payment Links for Stripe](/blog/payment-links-for-stripe/) - [How to Choose a Payment Platform](/guides/how-to-choose-payment-platform/) - [Stripe + QuickBooks Integration](/guides/quickbooks-stripe-payments/) - [Worldpay + QuickBooks Integration](/guides/quickbooks-worldpay-payments/) - [Braintree + QuickBooks Integration](/guides/quickbooks-braintree-payments/) - [PayPal + QuickBooks Integration](/guides/quickbooks-paypal-payments/) - [Book a Call](/discovery/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-payment-links/ --- # QuickBooks Payment Links: Add a Pay Now Button to Any Invoice | Shuttle > QuickBooks doesn't have a built-in payment links feature. You can send invoices, but there's no native way to generate a shareable payment link that works... # QuickBooks Payment Links: Add a Pay Now Button to Any Invoice By Shuttle Team, February 18, 2026 QuickBooks doesn't have a built-in payment links feature. You can send invoices, but there's no native way to generate a shareable payment link that works across SMS, email, WhatsApp, or chat -- processed through your own gateway. This guide shows how to add payment links to QuickBooks invoices and standalone payment collection, so your customers can click and pay from anywhere. ## What Is a QuickBooks Payment Link? A payment link is a URL that opens a checkout page. The customer clicks it, enters their card details (or uses Apple Pay / Google Pay), and pays. The payment is processed through your gateway and auto-recorded in QuickBooks. Unlike QuickBooks Payments (Intuit's native processor), a payment link through Shuttle works with your existing gateway -- Authorize.net, Stripe, Braintree, PayPal, Worldpay, or others. You're not locked into Intuit's rates or US-only coverage. The same applies to bank payments: see How to Accept ACH Payments in QuickBooks. Payment links can be: - Embedded in invoices -- paste into your QuickBooks invoice template - Sent via SMS -- text a pay link to a customer's phone - Sent via email -- standalone payment request outside of QuickBooks - Shared via chat -- WhatsApp, live chat, or any messaging channel - Posted on your website -- a "Pay Invoice" button on your site One link, multiple channels. ## How to Create Payment Links for QuickBooks ### Method 1: QuickBooks Invoice Integration The simplest approach -- add a payment link directly into your QuickBooks invoices. - Install the Shuttle QuickBooks Online Invoice Payments app - Connect your payment gateway - Copy your unique payment link - Paste it into your QuickBooks invoice template (in the notes or custom field) - Every invoice now has a clickable payment link When a customer pays via the link, the payment is automatically recorded in QuickBooks against that invoice. No manual matching. Full setup walkthrough: How to Accept Payments on QuickBooks Invoices ### Method 2: Standalone Payment Links (Links Checkout) For payment collection beyond invoices -- ad-hoc payments, deposits, recurring billing, or payment requests sent outside QuickBooks -- use Shuttle Links Checkout. Use cases: - Send a deposit request before starting work - Collect payment over the phone by texting a link during the call - Add a "Pay Now" button to your website - Send payment reminders via WhatsApp or SMS - Collect recurring payments without manual invoice creation Links Checkout generates branded checkout pages tied to your payment gateway. You can pre-fill amounts, add descriptions, and track payment status in real time. Key features: - Branded checkout pages (your logo, your colours) - Pre-fill customer details and amounts - Multiple payment methods (cards, PayPal, Apple Pay, Google Pay) - Payment tracking dashboard - Email/SMS delivery - Partial payments and deposits - PCI DSS Level 1 compliant ## Payment Link vs. QuickBooks "Pay Now" Button QuickBooks Payments (Intuit's native option) adds a "Pay Now" button to invoices. How does it compare to a Shuttle payment link? QuickBooks Payments Shuttle Payment Link Works with your gateway No -- Intuit only Yes -- Authorize.net, Stripe, Worldpay, etc. Send via SMS/WhatsApp/chat International support Custom branding QuickBooks branding Your brand Auto-reconciliation Multiple payment methods Cards + ACH Cards, PayPal, Apple Pay, Google Pay, local methods Standalone links (no invoice) Saved cards Partial payments If you're US-only and happy with Intuit's rates, their native button works for invoice-only collection. For everything else -- international, multi-channel, BYO gateway -- payment links through Shuttle cover more ground. ## Practical Scenarios ### Credit Controllers Chasing Overdue Invoices Instead of calling a customer to ask for payment, send a link. Via SMS, they see it immediately. One tap, card details, paid. Average DSO reduction: 5-12 days. ### Service Businesses Collecting Deposits Before starting a job, send a payment link for the deposit. The customer pays before you arrive. No awkward "Do you have your card?" conversations on site. ### Agencies and Consultancies Send a project milestone payment link at the end of each phase. Cleaner than chasing invoice payments, faster than waiting for bank transfers. ### Logistics and Transport Driver delivers goods, sends a payment link from the cab. Customer pays immediately. No 30-day invoice cycle for delivery charges. ### Auto Sales and Dealerships Collect deposits, service payments, or parts orders via link. Customer pays from their phone without visiting the dealership. ## Setting Up Payment Links: Step by Step ### For Invoice Payments (QuickBooks Integration) Time required: ~5 minutes - Go to shuttleglobal.com/quickbooks-online - Click "Get App" and authorise QuickBooks access - Connect your payment gateway (API keys or OAuth) - Enable features: saved cards, partial payments, email notifications - Copy the payment link - Open your QuickBooks invoice template → paste the link in the notes/message field - Send an invoice -- the customer now sees a clickable payment link Free plan includes auto-reconciliation, saved cards, partial payments, and email alerts. Basic plan ($16/month) adds your logo, custom URL, and removes advertising. ### For Standalone Payment Links - Go to shuttleglobal.com/merchants/links-checkout - Sign up and connect your payment gateway - Create a payment link from the dashboard - Set the amount, description, and customer details (or leave blank for flexible-amount links) - Send via email, SMS, or chat - Track payment status in the dashboard ## Security and Compliance All payment links are PCI DSS Level 1 compliant. Card data is captured on Shuttle's secure checkout page and tokenised -- it never touches your systems, your QuickBooks account, or your email. Shuttle also holds ISO 27001 and SOC 2 certifications. For businesses in regulated industries, this matters: your payment collection is handled by infrastructure-grade security, not a lightweight add-on. ## Frequently Asked Questions ### Can I customise the checkout page? On the Basic plan, yes -- add your logo and use a custom payment URL. The checkout page is clean, mobile-optimised, and branded to your business. ### What gateways are supported? Authorize.net, Braintree, PayPal, Stripe, USAePay, Worldpay, and more. If you already have a gateway, you can likely connect it. ### Do customers need to create an account? No. They click the link, enter card details, and pay. Optional card saving for repeat customers. ### Can I send links to multiple customers at once? With Links Checkout, yes -- generate individual links per customer or use the API for bulk generation. For QuickBooks invoice links, the link is embedded in each invoice automatically. ### What about refunds? Refunds are processed through your payment gateway as normal. The refund status syncs based on your gateway's standard process. ## Related Guides - How to Accept Payments on QuickBooks Invoices - Authorize.net + QuickBooks: Complete Integration Guide - Links Checkout for Merchants - Payment Links for Authorize.net - Payment Links for Stripe - Payment Links for Hotels & Holiday Accommodation -- payment links for hotel deposits, no-shows, and upsells - Car Dealership Payment Solutions -- payment links for car deposits and service invoices - Prommt Alternatives for Platforms -- comparing payment link providers - Stripe + QuickBooks Integration -- accept invoice payments via Stripe - Worldpay + QuickBooks Integration -- pay invoices through Worldpay - Braintree + QuickBooks Integration -- accept payments via Braintree (PayPal + cards) - PayPal + QuickBooks Integration -- add PayPal to QuickBooks invoices ## Related Reading - QuickBooks Payment Collection: Add Pay Now Links to Every Invoice - How to Reduce Debtor Days: 10 Strategies That Actually Work Ready to add Pay Now links to every QuickBooks invoice? Shuttle Links & Checkout connects to your existing payment provider, gives you a branded checkout page, and works with any QuickBooks invoice template. Cards, Apple Pay, Google Pay, ACH, and more -- paid faster than waiting for a cheque. See how it works. ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Xero Payment Links: Collect Invoice Payments Faster ### Using Payment Links to increase TikTok sales ### Moneris Payment Links: Features, Setup & Alternatives (2026) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ## Links - [How to Accept ACH Payments in QuickBooks](/guides/quickbooks-ach-payments/) - [Shuttle QuickBooks Online Invoice Payments app](/quickbooks-online) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [Shuttle Links Checkout](/merchants/links-checkout/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [shuttleglobal.com/merchants/links-checkout](/merchants/links-checkout/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [Links Checkout for Merchants](/merchants/links-checkout/) - [Payment Links for Authorize.net](/blog/payment-links-for-authorize-net/) - [Payment Links for Stripe](/blog/payment-links-for-stripe/) - [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/) - [Car Dealership Payment Solutions](/guides/car-dealership-payment-solutions/) - [Prommt Alternatives for Platforms](/alternatives/prommt/) - [Stripe + QuickBooks Integration](/guides/quickbooks-stripe-payments/) - [Worldpay + QuickBooks Integration](/guides/quickbooks-worldpay-payments/) - [Braintree + QuickBooks Integration](/guides/quickbooks-braintree-payments/) - [PayPal + QuickBooks Integration](/guides/quickbooks-paypal-payments/) - [QuickBooks Payment Collection: Add Pay Now Links to Every Invoice](/blog/quickbooks-payment-collection/) - [How to Reduce Debtor Days: 10 Strategies That Actually Work](/guides/reduce-debtor-days/) - [Shuttle Links & Checkout](/merchants/links-checkout/) - [See how it works](/merchants/links-checkout/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogXero Payment Links: Collect Invoice Payments Faster→](/blog/xero-payment-links/) - [BlogUsing Payment Links to increase TikTok sales→](/blog/payment-links-for-tiktok-sales/) - [BlogMoneris Payment Links: Features, Setup & Alternatives (2026)→](/blog/payment-links-for-moneris/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-payments-twilio-integration/ --- # How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments | Shuttle > QuickBooks Payments doesn't natively connect to Twilio for voice payments. If you invoice from QuickBooks and want to take a card payment during a phone... # How to Connect QuickBooks Payments to Twilio for Voice & IVR Payments By Shuttle Team, June 8, 2026 QuickBooks Payments doesn't natively connect to Twilio for voice payments. If you invoice from QuickBooks and want to take a card payment during a phone call (a deposit, an overdue invoice, a phone order) you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects QuickBooks Payments (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction, with the transaction settling through your QuickBooks Payments merchant account so your books stay in QuickBooks. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why QuickBooks Payments + Twilio Don't Connect Directly QuickBooks Payments is Intuit's payment processing service, built around QuickBooks Online. It's invoicing-led: a customer receives a QuickBooks invoice, pays it online, and the payment is matched to the invoice with the deposit and fees recorded in your books. That tight reconciliation loop is why it's so popular with US small businesses and service firms. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. QuickBooks Payments isn't one of Twilio's built-in connectors, so there's no out-of-the-box way to charge a card over the phone and have it land in your QuickBooks Payments account. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to QuickBooks Payments for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the verb. Typical trigger: a customer calls to pay a deposit or settle an overdue QuickBooks invoice. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via QuickBooks Payments. The connector processes the transaction through your QuickBooks Payments merchant account and handles the response. - Result returned to your call flow. Your webhook receives the transaction reference, last four digits, card brand, and status. The call continues, and you can record the payment against the customer's invoice in QuickBooks Online. The entire flow happens in seconds. The caller stays on the line. No redirects, no "we'll email you a link and hope you click it." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A QuickBooks Payments account. API access runs through Intuit's developer platform: apps authenticate with OAuth 2.0 credentials from an Intuit developer app, using the QuickBooks Payments scope - A Shuttle account (free to create, you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Connect QuickBooks Payments to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: QuickBooks Payments - Credentials: authorise Shuttle against your QuickBooks Payments account via Intuit's OAuth flow - Currency: USD (QuickBooks Payments serves US merchants) - Environment: Live or Sandbox Save the profile. Shuttle now has a live connection to your QuickBooks Payments account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to record the payment against the invoice in QuickBooks Online. Because the charge runs through your QuickBooks Payments account, the deposit and processing fees flow into QuickBooks the same way as your online invoice payments, so reconciliation stays in one place. ### Step 5: Test Intuit provides a sandbox environment for QuickBooks Payments through its developer platform. Use sandbox credentials in your Shuttle payment profile and verify the flow end-to-end with Twilio before going live. ## What You Can Do With QuickBooks Payments + Twilio ### Collect Overdue Invoices by Phone The most common use case. A customer with an unpaid QuickBooks invoice calls in (or your team calls out), the amount is confirmed, and the card is captured securely via DTMF while the caller is still on the line. No chasing, no "the cheque is in the post." ### Take Deposits and Phone Orders Service firms that quote by phone (contractors, repair shops, professional services) can take a deposit at the moment of commitment instead of sending an invoice and waiting. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems. ### Keep Reconciliation in QuickBooks Because voice payments settle through your QuickBooks Payments merchant account rather than a separate phone-payments provider, you avoid running a second merchant account that needs its own reconciliation workflow. ## Multi-PSP: Beyond QuickBooks Payments One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: keep QuickBooks Payments for invoice-linked payments and route other transactions to a different acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand beyond the US, where QuickBooks Payments doesn't process, by routing those regions to a local gateway You choose which connected provider handles each payment type in Shuttle's dashboard, with minimum amount, maximum amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly important for BPOs and firms that serve multiple clients. Each client can use their own QuickBooks Payments account (or any other gateway) through the same Twilio integration. ## PCI Compliance The QuickBooks Payments + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1 Service Provider) Payment processing QuickBooks Payments (Intuit) Your systems No card data: SAQ-A Card data flows from Twilio → Shuttle → QuickBooks Payments. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect QuickBooks Payments to Twilio without Shuttle? Twilio doesn't have a built-in QuickBooks Payments Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Do phone payments show up in QuickBooks? Payments processed this way settle through your QuickBooks Payments merchant account, so deposits and fees flow into QuickBooks like your other QuickBooks Payments transactions. Use the transaction reference from the webhook to record the payment against the right invoice. Does this work for IVR self-service payments? Yes. The verb works in fully automated IVR flows as well as agent-assisted calls. A caller can pay an invoice at 9pm with no agent involved. Is there a test environment? Yes. Intuit provides a sandbox for QuickBooks Payments via its developer platform. Use sandbox credentials in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. QuickBooks Payments' standard processing fees apply on top. No Shuttle setup fees or monthly minimums. Can I switch from QuickBooks Payments to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup - QuickBooks Invoice Payments: How to Get Paid Faster: speeding up invoice collection in QuickBooks - QuickBooks Payment Links: Send a Pay-Now Link From Your Books: payment links for QuickBooks users - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect QuickBooks Payments to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### 5 Reasons you shouldn't build payments integrations in-house ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [QuickBooks Payments](/payment-providers/quickbooks-payments/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect Adyen to Twilio for Voice & IVR Payments](/guides/adyen-twilio-integration/) - [QuickBooks Invoice Payments: How to Get Paid Faster](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Send a Pay-Now Link From Your Books](/guides/quickbooks-payment-links/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [Blog5 Reasons you shouldn't build payments integrations in-house→](/blog/5-reasons-you-shouldnt-build-payments-integrations-in-house/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-paypal-payments/ --- # PayPal + QuickBooks Integration: Add PayPal to QuickBooks Invoices | Shuttle > Your customers want to pay with PayPal. You can see it in the emails -- "Do you accept PayPal?" -- and in the delayed payments from customers who don't want... # PayPal + QuickBooks Integration: Add PayPal to QuickBooks Invoices By Shuttle Team, March 14, 2026 Your customers want to pay with PayPal. You can see it in the emails -- "Do you accept PayPal?" -- and in the delayed payments from customers who don't want to type their card number into yet another form. PayPal has over 430 million active accounts. It's the most recognised online payment brand in the world. And QuickBooks invoices don't support it. QuickBooks Payments -- Intuit's native processor -- handles cards and ACH. That's it. No PayPal, no digital wallets, no alternative payment methods. If you want PayPal on your invoices, Intuit doesn't have an answer. This guide shows how to add PayPal as a payment option on your QuickBooks invoices using Shuttle -- so customers can pay with their PayPal balance or linked card, and the payment is automatically recorded in QuickBooks. ## Why PayPal on Invoices Matters PayPal isn't just another payment method. For many customers, it's the preferred payment method -- and offering it can be the difference between a 3-day payment and a 30-day one. Trust and familiarity. Customers paying a new supplier for the first time often prefer PayPal. The buyer protection, the familiar login flow, and the fact that they don't need to share card details with an unknown checkout page -- it all reduces friction. Speed. PayPal payments are two clicks: log in, confirm. No typing a 16-digit card number, expiry date, and CVV. For mobile users especially, this dramatically reduces abandonment. Global reach. PayPal operates in 200+ markets and supports 100+ currencies. If you invoice internationally, PayPal gives your customers a payment method they already use, regardless of their local banking setup. Business PayPal balances. Many small businesses maintain PayPal balances from their own sales. When they receive your invoice with a PayPal option, they can pay from that balance instantly -- no bank transfer delay. Higher conversion on invoices. Internal data from payment link providers consistently shows that offering PayPal alongside cards increases payment completion rates by 10-20%. When people see a payment method they trust, they pay faster. ## The Gap: QuickBooks + PayPal Here's the problem. QuickBooks Online is excellent invoicing software. PayPal is the world's most popular online payment method. But connecting them is surprisingly difficult: - QuickBooks Payments doesn't support PayPal. Cards and ACH only. - PayPal's own invoicing tool is separate. PayPal has its own invoice feature, but it doesn't sync with QuickBooks. You'd be maintaining two invoicing systems. - Manual PayPal payments create reconciliation chaos. If a customer pays you via PayPal independently (sending money to your PayPal email), you have to manually match that payment to the QuickBooks invoice. At scale, this is unsustainable. - PayPal.Me links don't reconcile. You could paste a PayPal.Me link on your invoice, but there's no connection back to QuickBooks -- the payment won't match to the invoice automatically. Businesses end up in one of two camps: either they don't offer PayPal (losing customers who prefer it) or they accept PayPal payments separately and spend hours reconciling manually. ## How Shuttle Adds PayPal to QuickBooks Invoices Shuttle's QuickBooks Online Invoice Payments app connects your PayPal account to QuickBooks Online. It generates a payment link for your invoices that offers both PayPal and card payment -- with automatic reconciliation back to QuickBooks. - Customer receives your QuickBooks invoice via email - They click the payment link - A secure checkout page opens with PayPal and card payment options - Customer chooses PayPal -- they log in and confirm, or pay with their PayPal balance - Payment is processed through your PayPal account - The payment is automatically recorded in QuickBooks -- invoice marked as "Paid" No manual matching. No separate invoicing system. No reconciliation headaches. ## Setup Guide: PayPal + QuickBooks via Shuttle ### Prerequisites - A QuickBooks Online account (any plan) - A PayPal Business account - Access to your PayPal account settings ### Step 1: Install the Shuttle App Go to shuttleglobal.com/quickbooks-online and click "Get App." Authorise QuickBooks access via the standard OAuth flow. ### Step 2: Connect PayPal In the Shuttle dashboard, select PayPal as your payment provider. You'll connect via PayPal's OAuth -- click the button, log in to your PayPal Business account, and grant access. The connection is validated instantly. No API keys to hunt down -- just log in and authorise. ### Step 3: Configure Payment Settings Set up the features you need: - Saved cards -- if customers pay by card (rather than PayPal balance), they can save details for next time. - Partial payments -- accept deposits or instalment payments. The balance updates in QuickBooks automatically. - Email notifications -- get alerted the moment a payment is received. - Custom branding (Basic plan, $16/month) -- your logo on the checkout page and a custom payment URL. ### Step 4: Add the Payment Link to Invoices Copy your unique payment link. In QuickBooks Online: - Go to Settings → Custom Form Styles - Edit your invoice template - In the message/notes section, add: "Pay online: [your payment link]" Every invoice you send now includes a payment link with PayPal as an option. ## What Your Customer Sees When a customer opens your invoice and clicks the payment link: - A branded checkout page opens - They see two options: Pay with PayPal and Pay with Card - If they choose PayPal: - They're redirected to PayPal's login - They confirm the payment amount - They can pay from their PayPal balance, linked bank account, or linked card - They're returned to a confirmation page - If they choose Card: - They enter card details on the secure checkout page - Apple Pay and Google Pay are available on supported devices - Either way, the payment is recorded in QuickBooks against the correct invoice The customer doesn't need to know that Shuttle is involved. They see your invoice, they see PayPal, they pay. Simple. ## QuickBooks Payments vs. PayPal via Shuttle QuickBooks Payments PayPal via Shuttle PayPal acceptance Card payments Apple Pay / Google Pay Availability 200+ markets Processing rates 2.99% + 25c (cards) PayPal's rates (varies by region and volume) Auto-reconciliation Saved cards Partial payments Custom branding QuickBooks branding Your brand (Basic plan) Buyer protection PayPal Buyer Protection Customer recognition New checkout Familiar PayPal flow Monthly cost Included with QuickBooks Free plan available, Basic $16/month The key differentiator: QuickBooks Payments doesn't offer PayPal at all. If your customers want PayPal -- and many do -- the only way to offer it on QuickBooks invoices with auto-reconciliation is through a connector like Shuttle. ## When PayPal + QuickBooks Makes Sense Your customers ask for PayPal. If you're regularly hearing "Can I pay by PayPal?" or seeing invoices go unpaid because customers don't want to enter card details, adding PayPal removes that barrier. You invoice consumers or small businesses. B2C and B2SMB invoicing benefits most from PayPal. Consumer PayPal adoption is high, and many small businesses maintain PayPal balances. Enterprise B2B is less PayPal-centric, though it's growing. You operate internationally. PayPal works in 200+ markets. For businesses invoicing across borders, PayPal gives customers a payment method they already have -- no international card worries, no unfamiliar checkout pages. You want faster payment. The two-click PayPal flow (log in, confirm) is faster than card entry. Faster checkout means faster payment, which means better cash flow. For businesses where DSO (days sales outstanding) is a problem, adding PayPal can measurably reduce it. You already have a PayPal Business account. If you're already receiving PayPal payments in other contexts (online store, marketplace sales), connecting that same account to QuickBooks invoices consolidates your PayPal activity. ## PayPal Fees: What to Expect PayPal's fee structure varies by region and account type. Typical rates for online payments: - US: 3.49% + 49c (standard), lower for qualified merchants - UK: 2.9% + 30p (standard) - EU: 2.9% + fixed fee (varies by currency) - Cross-border: Additional fee applies (typically 1-1.5%) PayPal occasionally offers volume-based discounts for businesses processing above certain thresholds. Your existing PayPal rates carry over -- Shuttle doesn't modify or add to PayPal's fees. For businesses where the PayPal fee is higher than their card processing rate, consider offering both options through the checkout page. Customers who prefer cards pay at your card rate; customers who prefer PayPal pay via PayPal. You capture both audiences. ## Pricing Shuttle Free plan: - Auto-record payments in QuickBooks - PayPal + card acceptance - Email notifications - PCI DSS Level 1 compliant - No Shuttle transaction fee (PayPal rates apply) Shuttle Basic plan ($16/month): - Everything in Free - Your logo on the checkout page - Custom payment URL - No advertising on checkout - Email support - 25% discount if paid annually ## Common Questions ### Can customers pay with their PayPal balance? Yes. When a customer clicks "Pay with PayPal," they log in and can choose to pay from their PayPal balance, linked bank account, or linked debit/credit card. Whatever method they select within PayPal, the payment reconciles to QuickBooks the same way. ### What if my customer doesn't have PayPal? No problem. The checkout page shows both PayPal and card payment options. Customers without PayPal accounts can pay by card. You're not forcing anyone to use PayPal -- you're offering it as an additional option. ### Does PayPal Buyer Protection apply? Yes. Payments made through PayPal carry PayPal's standard buyer and seller protection policies. This can actually work in your favour -- customers who are hesitant to pay a new supplier feel safer knowing PayPal's protection is in place. ### Can I use PayPal for invoice payments and Braintree for my website? Yes. In fact, Braintree (PayPal's card processing gateway) and direct PayPal are complementary. If you have both, you could connect Braintree to Shuttle for the full range of payment methods. See our Braintree + QuickBooks guide. ### Do refunds work? Refunds are processed through PayPal as normal. Issue the refund from your PayPal account, and the refund follows PayPal's standard process and timeline. ### I send invoices in multiple currencies -- does PayPal handle that? Yes. PayPal supports 100+ currencies. If you invoice a customer in EUR and they pay via PayPal, the currency conversion is handled by PayPal at their exchange rate. Your QuickBooks invoice is marked as paid in the invoiced currency. ### Is this the same as PayPal's own invoicing feature? No. PayPal has its own invoice tool, but it's completely separate from QuickBooks. You'd be maintaining two invoicing systems with no sync. Shuttle connects your existing QuickBooks invoicing workflow to PayPal for payment -- one system, one workflow, automatic reconciliation. ## Related Guides - How to Accept Payments on QuickBooks Invoices - QuickBooks Payment Links: Add Pay Now to Any Invoice - Authorize.net + QuickBooks: Complete Integration Guide - QuickBooks Stripe Payments - QuickBooks Worldpay Payments - QuickBooks Braintree Payments - PayPal PSP Overview ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### QuickBooks ACH Payments: Setup, Fees & Tips ### How to Accept Payments in QuickBooks: Full Guide ## Links - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Braintree + QuickBooks guide](/guides/quickbooks-braintree-payments/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [QuickBooks Stripe Payments](/guides/quickbooks-stripe-payments/) - [QuickBooks Worldpay Payments](/guides/quickbooks-worldpay-payments/) - [QuickBooks Braintree Payments](/guides/quickbooks-braintree-payments/) - [PayPal PSP Overview](/payment-providers/paypal-commerce/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogHow to Accept Payments in QuickBooks: Full Guide→](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-stripe-payments/ --- # Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe | Shuttle > Stripe is the most popular modern payment platform -- used by millions of businesses from startups to enterprises. # Stripe + QuickBooks Integration: Accept Invoice Payments via Stripe By Shuttle Team, March 20, 2026 Stripe is the most popular modern payment platform -- used by millions of businesses from startups to enterprises. But if you also use QuickBooks Online for invoicing, you've probably noticed the gap: there's no native way to process QuickBooks invoice payments through Stripe. Intuit wants you to use QuickBooks Payments -- their own processor. That means maintaining two payment relationships, two fee structures, and two reconciliation workflows. For businesses already running everything through Stripe, that's a step backwards. This guide shows how to connect your Stripe account to QuickBooks invoices using Shuttle -- so customers pay through Stripe, and payments are automatically recorded in QuickBooks. ## Why Stripe Users Need This Stripe has become the default payment infrastructure for modern businesses. If you're already on Stripe, you likely have: - Optimised processing rates -- negotiated or earned through volume - A complete transaction history -- months or years of data in one place - Connected services -- Stripe Radar for fraud, Stripe Billing for subscriptions, Stripe Connect for marketplaces - Developer integrations -- your website, app, and internal tools all connected to Stripe Switching to QuickBooks Payments for invoice collection means abandoning all of that for a subset of your transactions. You'd be splitting your payment data across two platforms, paying two sets of fees, and losing the reporting consistency that makes Stripe valuable. The real question isn't "should I use QuickBooks Payments?" -- it's "how do I route invoice payments through the Stripe account I already have?" ## How Shuttle Connects Stripe to QuickBooks Shuttle's QuickBooks Online Invoice Payments app connects your Stripe account to QuickBooks Online. It adds a payment link to your invoices that processes through Stripe and auto-reconciles back to QuickBooks. - Customer receives your QuickBooks invoice via email - They click the payment link - A secure checkout page opens with card, Apple Pay, and Google Pay options - Payment is processed through your Stripe account - Funds settle to your Stripe-connected bank account at your usual rates - The payment is automatically recorded in QuickBooks -- invoice marked as "Paid" No code. No API work. No changes to your Stripe configuration. ## Setup Guide: Stripe + QuickBooks via Shuttle ### Prerequisites - A QuickBooks Online account (any plan) - An active Stripe account - Access to your Stripe Dashboard ### Step 1: Install the Shuttle App Go to shuttleglobal.com/quickbooks-online and click "Get App." Authorise QuickBooks access via the standard OAuth flow. ### Step 2: Connect Stripe In the Shuttle dashboard, select Stripe as your payment gateway. You'll connect via Stripe's OAuth -- click the button, log in to Stripe, and grant access. No manual API key entry required (though API keys are also supported if you prefer). Shuttle validates the connection immediately. Once confirmed, your Stripe account is linked. ### Step 3: Configure Payment Settings Enable the features you need: - Saved cards -- returning customers can save card details for one-click future payments. Tokenised securely via Stripe. - Partial payments -- accept deposits or instalment payments against invoices. The outstanding balance updates in QuickBooks automatically. - Email notifications -- receive alerts the moment a payment lands. - Custom branding (Basic plan, $16/month) -- your logo on the checkout page and a custom payment URL. ### Step 4: Add the Payment Link to Invoices Copy your unique payment link from the Shuttle dashboard. In QuickBooks Online: - Go to Settings → Custom Form Styles - Edit your invoice template - In the message/notes section, add: "Pay online: [your payment link]" Every invoice you send now includes a clickable link to pay via Stripe. ## Stripe Features That Work Through Shuttle Stripe Feature Supported via Shuttle Card payments (Visa, Mastercard, Amex) Google Pay Stripe Radar (fraud detection) Yes -- your Radar rules apply 3D Secure / SCA Yes -- triggered by your Stripe rules Saved cards (tokenisation) ACH payments Depends on configuration SEPA Direct Debit Stripe fees and settlement Unchanged -- your rates apply Multi-currency Yes -- based on your Stripe account settings Your Stripe Radar rules, 3D Secure policies, and dispute handling remain active. Shuttle processes through your Stripe account -- all your existing settings govern the transaction. ## QuickBooks Payments vs. Stripe via Shuttle QuickBooks Payments Stripe via Shuttle Processing rates 2.99% + 25c (cards), 1% ACH Your Stripe rates (typically 2.9% + 30c US, 1.4% + 20p UK/EU) Availability 47 countries Payment methods Cards, ACH Cards, Apple Pay, Google Pay, ACH, SEPA, local methods Fraud protection Stripe Radar (ML-powered) Auto-reconciliation Saved cards Yes (Stripe tokenisation) Partial payments Custom branding QuickBooks branding Your brand (Basic plan) 135+ currencies Existing Stripe data Separate system Same Stripe account Monthly cost Included with QuickBooks Free plan available, Basic $16/month For businesses already on Stripe -- especially those outside the US or needing Apple Pay, Google Pay, and multi-currency support -- routing through Stripe via Shuttle is the stronger option. ## When Stripe + QuickBooks Makes Sense You already use Stripe for your website or app. Consolidating invoice payments into the same Stripe account gives you one dashboard, one set of reports, and one settlement flow. No split reconciliation. You invoice internationally. Stripe operates in 47 countries and supports 135+ currencies. QuickBooks Payments is US-only. If you have customers in the UK, EU, Australia, or anywhere else, Stripe via Shuttle covers them. You want Apple Pay and Google Pay on invoices. Mobile wallet payments are faster and have lower abandonment. Stripe supports both natively, and they work through Shuttle's checkout page. You've built around Stripe's ecosystem. If you use Stripe Radar, Stripe Billing, or Stripe Connect, keeping invoice payments in the same account maintains your data integrity and operational workflows. You have negotiated Stripe rates. High-volume businesses often negotiate custom pricing with Stripe. QuickBooks Payments doesn't honour those rates -- you'd pay Intuit's standard pricing on invoice transactions. ## Common Questions ### Does Shuttle add fees on top of Stripe? No. Shuttle's Free plan has no transaction fees. Your standard Stripe processing rates apply. The Basic plan ($16/month) adds branding features but still no per-transaction markup. ### Can I still use Stripe for my website checkout? Absolutely. Shuttle uses your Stripe account for invoice payments only. Your website, app, subscriptions, and any other Stripe integrations continue working independently. Same account, no conflicts. ### Does Stripe Radar work on invoice payments? Yes. Transactions processed through Shuttle go through your Stripe account, which means your Radar rules, block lists, and risk settings all apply. If you've configured Radar for enhanced fraud detection, that protection extends to invoice payments. ### What about Stripe Connect -- can I use this with connected accounts? Shuttle connects to your primary Stripe account. If you operate a Stripe Connect platform, the invoice payment integration works with your platform account. Speak to us about specific Connect configurations. ### Can my customer pay in a different currency? Multi-currency support depends on your Stripe account configuration. If your Stripe account accepts GBP, EUR, AUD, etc., those currencies are available through the Shuttle checkout page. Currency conversion is handled by Stripe at their standard exchange rates. ### I'm already using QuickBooks Payments -- can I switch? Yes. Disable QuickBooks Payments in your QuickBooks settings and add the Shuttle payment link to your invoice template instead. Future invoices will process through Stripe. Past invoices already paid through QuickBooks Payments are unaffected. ## Related Guides - How to Accept Payments on QuickBooks Invoices - QuickBooks Payment Links: Add Pay Now to Any Invoice - Authorize.net + QuickBooks: Complete Integration Guide - QuickBooks Worldpay Payments - QuickBooks Braintree Payments - QuickBooks PayPal Payments - Stripe PSP Overview - Payment Links for Stripe ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### Authorize.net QuickBooks Integration: Full Guide ### What Stripe's Unbundling Tells Us About the Future of Payments ### QuickBooks ACH Payments: Setup, Fees & Tips ## Links - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [QuickBooks Worldpay Payments](/guides/quickbooks-worldpay-payments/) - [QuickBooks Braintree Payments](/guides/quickbooks-braintree-payments/) - [QuickBooks PayPal Payments](/guides/quickbooks-paypal-payments/) - [Stripe PSP Overview](/payment-providers/stripe/) - [Payment Links for Stripe](/blog/payment-links-for-stripe/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) --- URL: https://www.shuttleglobal.com/guides/quickbooks-worldpay-payments/ --- # Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay | Shuttle > Worldpay is one of the largest payment processors in the world -- processing billions of transactions per year across 146 countries. # Worldpay + QuickBooks Integration: Pay Invoices Through Worldpay By Shuttle Team, March 18, 2026 Worldpay is one of the largest payment processors in the world -- processing billions of transactions per year across 146 countries. In the UK and Europe especially, Worldpay is the default for many established businesses. Terminal in the shop, Worldpay. Card-not-present transactions, Worldpay. Negotiated rates built over a decade of processing history -- all through Worldpay. Then you try to collect payments on a QuickBooks invoice, and Worldpay is nowhere to be found. QuickBooks Payments -- Intuit's own processor -- is the only gateway with native invoice integration. It's US-only, it ignores your existing Worldpay relationship, and it charges its own rates. For UK and European businesses running QuickBooks Online with Worldpay, there has been no good answer. Until now. This guide shows how to connect Worldpay to QuickBooks Online through Shuttle -- keeping your Worldpay rates, settlement, and merchant account while adding online payment collection to every invoice. ## The Problem for Worldpay + QuickBooks Users If you're a UK or European business using both Worldpay and QuickBooks Online, you've likely hit this wall: - QuickBooks Payments isn't available outside the US. Even if you wanted to use it, you can't. - Worldpay doesn't integrate with QuickBooks invoices. There's no plugin, no API connection, no "Pay Now" button powered by Worldpay. - Manual bank transfers are your only option. You send an invoice, include your bank details, and hope the customer pays within terms. No card payments, no instant confirmation, no auto-reconciliation. - Reconciliation is manual. When payments do arrive, someone has to match bank statements to QuickBooks invoices line by line. This is the reality for thousands of UK businesses: excellent invoicing software, excellent payment processing, and no bridge between them. ## How Shuttle Bridges Worldpay and QuickBooks Shuttle's QuickBooks Online Invoice Payments app connects your Worldpay merchant account to QuickBooks Online. It generates a payment link that you add to invoices -- customers click, pay by card, and the payment is recorded in QuickBooks automatically. How it works: - Install the Shuttle app and connect to QuickBooks Online - Enter your Worldpay gateway credentials - Configure features (saved cards, partial payments, notifications) - Add the payment link to your QuickBooks invoice template - Customers receive the invoice, click the link, and pay by card - Payment is processed through your Worldpay account - Payment is auto-recorded in QuickBooks -- invoice marked as "Paid" Your Worldpay rates, settlement schedule, and merchant account stay exactly as they are. Shuttle handles the link between the invoice and the payment. ## Setup Guide: Worldpay + QuickBooks via Shuttle ### Prerequisites - A QuickBooks Online account (any plan -- works with international QBO) - An active Worldpay merchant account with gateway access - Your Worldpay gateway credentials (Installation ID, Merchant Code) ### Step 1: Install the Shuttle App Go to shuttleglobal.com/quickbooks-online and click "Get App." Authorise QuickBooks access via the standard OAuth flow. ### Step 2: Connect Worldpay In the Shuttle dashboard, select Worldpay as your payment gateway. Enter your Worldpay gateway credentials: - Installation ID -- found in your Worldpay Business Gateway administration panel - Merchant Code -- your Worldpay merchant identifier Shuttle validates the connection immediately. If credentials are correct, you'll see confirmation. ### Step 3: Configure Payment Settings Choose the features that suit your business: - Saved cards -- repeat customers can store card details securely for faster payment next time. Tokens stored via Worldpay's tokenisation service. - Partial payments -- accept deposits, staged payments, or part-payments against an invoice. The outstanding balance updates in QuickBooks. - Email notifications -- instant alerts when a payment is received. - Custom branding (Basic plan, $16/month) -- your logo on the checkout page and a custom payment URL. ### Step 4: Add the Payment Link to Invoices Copy your unique payment link from the Shuttle dashboard. In QuickBooks Online: - Go to Settings → Custom Form Styles - Edit your invoice template - In the message/notes section, add: "Pay online: [your payment link]" Every invoice now includes a clickable link. Customers on desktop or mobile can tap and pay by card. ## Why UK Businesses Choose Worldpay Over QuickBooks Payments QuickBooks Payments doesn't operate in the UK. But even in markets where both are available, Worldpay offers advantages that matter to established businesses: Negotiated rates. Businesses that have processed with Worldpay for years often have rates significantly below standard pricing. These are built on volume history and relationship -- you can't replicate them by signing up to a new processor. Terminal + online consistency. Many Worldpay merchants use Worldpay for in-store terminals and online transactions. Adding invoice payments through the same provider keeps all transaction data in one place. Enterprise support. Worldpay provides dedicated account management for mid-market and enterprise clients. QuickBooks Payments is self-service. Global acquiring. Worldpay processes in 146 countries and 120+ currencies. For businesses invoicing internationally, this reach matters. Regulatory familiarity. UK and EU businesses operate under FCA regulation and PSD2/SCA requirements. Worldpay's compliance infrastructure is built for this environment. ## QuickBooks Payments vs. Worldpay via Shuttle QuickBooks Payments Worldpay via Shuttle Availability 146 countries Processing rates Intuit's standard rates Your negotiated Worldpay rates Settlement Intuit's schedule Your Worldpay settlement terms Payment methods Cards, ACH Cards, Apple Pay, Google Pay 3D Secure / SCA US-focused Full SCA compliance (EU/UK) Auto-reconciliation Saved cards Yes (Worldpay tokenisation) Partial payments Custom branding QuickBooks branding Your brand (Basic plan) Account management Self-service Worldpay dedicated support Monthly cost Included with QuickBooks Free plan available, Basic $16/month For UK and European businesses, there's no comparison -- QuickBooks Payments isn't an option, and Worldpay via Shuttle gives you everything you need. ## What Happens When a Customer Pays - Customer opens your QuickBooks invoice (email or customer portal) - They click the payment link - A secure checkout page opens (Shuttle-hosted, PCI DSS Level 1) - They enter card details -- 3D Secure is triggered where required by your Worldpay configuration and SCA rules - Transaction is processed through your Worldpay merchant account - Funds settle to your bank account on your usual Worldpay schedule - Payment is automatically recorded in QuickBooks -- invoice status updates to "Paid" The entire process is automatic. No manual reconciliation, no chasing, no matching bank statements. ## Pricing Shuttle Free plan: - Auto-record payments in QuickBooks - Email notifications - PCI DSS Level 1 compliant - No Shuttle transaction fee (your Worldpay rates apply) Shuttle Basic plan ($16/month): - Everything in Free - Your logo on the checkout page - Custom payment URL - No advertising on checkout - Email support - 25% discount if paid annually Worldpay fees are yours. Shuttle doesn't change or add to your Worldpay processing rates. Your negotiated per-transaction fees apply as normal. ## Common Questions ### Will this change anything about my Worldpay account? No. Shuttle processes transactions through your existing Worldpay gateway using the standard API. Your rates, settlement, fraud settings, and reporting remain unchanged. Invoice payment transactions appear in your Worldpay reporting alongside all other transactions. ### Does 3D Secure / Strong Customer Authentication (SCA) work? Yes. SCA and 3D Secure are handled according to your Worldpay configuration and the relevant regulations. For UK/EU transactions, authentication is triggered automatically where required by PSD2 rules. ### I use Worldpay terminals in-store -- any conflict? None. The Shuttle integration uses your Worldpay account for invoice payment links only. Your in-store terminals, ecommerce gateway, and any other Worldpay integrations continue independently. ### Can I accept payments in multiple currencies? Yes, subject to your Worldpay account configuration. If your merchant account supports GBP, EUR, USD, or other currencies, those are available on the checkout page. Currency handling follows your Worldpay multi-currency setup. ### We've been with Worldpay for 10+ years -- will our rates carry over? Absolutely. That's the entire point. Your Worldpay rates -- however they've been negotiated -- apply to every transaction processed through Shuttle. You're not signing up to a new processor; you're connecting the one you already have. ### Is this just for the UK? No. Worldpay operates globally. If you have a Worldpay merchant account in any supported country, the integration works. It's particularly popular with UK businesses because QuickBooks Payments isn't available there, but the solution works anywhere Worldpay does. ## Related Guides - How to Accept Payments on QuickBooks Invoices - QuickBooks Payment Links: Add Pay Now to Any Invoice - Authorize.net + QuickBooks: Complete Integration Guide - QuickBooks Stripe Payments - QuickBooks Braintree Payments - QuickBooks PayPal Payments - Worldpay PSP Overview ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. ## Related Reading Explore More ### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices ### Maximize Efficiency: Accepting Card Payments in QuickBooks Online ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### QuickBooks ACH Payments: Setup, Fees & Tips ### How to Accept Payments in QuickBooks: Full Guide ## Links - [Shuttle's QuickBooks Online Invoice Payments app](/quickbooks-online) - [shuttleglobal.com/quickbooks-online](/quickbooks-online) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [How to Accept Payments on QuickBooks Invoices](/guides/quickbooks-invoice-payments/) - [QuickBooks Payment Links: Add Pay Now to Any Invoice](/guides/quickbooks-payment-links/) - [Authorize.net + QuickBooks: Complete Integration Guide](/guides/authorize-net-quickbooks/) - [QuickBooks Stripe Payments](/guides/quickbooks-stripe-payments/) - [QuickBooks Braintree Payments](/guides/quickbooks-braintree-payments/) - [QuickBooks PayPal Payments](/guides/quickbooks-paypal-payments/) - [Worldpay PSP Overview](/payment-providers/worldpay-access/) - [See Links Checkout](/merchants/links-checkout/) - [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/) - [BlogMaximize Efficiency: Accepting Card Payments in QuickBooks Online→](/blog/maximize-efficiency-accepting-card-payments-in-quickbooks-online/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogQuickBooks ACH Payments: Setup, Fees & Tips→](/blog/the-benefits-of-accepting-ach-for-quickbooks-invoices-using-shuttle-quickbooks-app/) - [BlogHow to Accept Payments in QuickBooks: Full Guide→](/blog/quickbooks-101-a-step-by-step-guide-to-accepting-online-payment/) --- URL: https://www.shuttleglobal.com/guides/reduce-debtor-days/ --- # How to Reduce Debtor Days: 10 Strategies That Actually Work | Shuttle > What Are Debtor Days and Why Do They Matter? Debtor days (also called Days Sales Outstanding or DSO) measure the average number of days it takes your... # How to Reduce Debtor Days: 10 Strategies That Actually Work By Shuttle Team, March 6, 2026 ## What Are Debtor Days and Why Do They Matter? Debtor days (also called Days Sales Outstanding or DSO) measure the average number of days it takes your customers to pay their invoices. The lower the number, the faster your cash comes in. The formula is simple: Debtor Days = (Trade Receivables / Annual Revenue) x 365 For example, if your business has £200,000 in outstanding receivables and £1.2 million in annual revenue: (200,000 / 1,200,000) x 365 = 61 debtor days. That means on average, you wait two months to get paid for work you've already done. In the UK, the average debtor days across all industries sits between 50 and 65 days -- well above the standard 30-day payment terms most businesses set. For some sectors like construction and professional services, it's even worse. Every day your debtor days stay high, you're effectively giving your customers an interest-free loan. Reducing debtor days from 60 to 30 on £1 million in annual revenue frees up roughly £82,000 in working capital. That's money you can reinvest, use to cover costs, or simply keep in the bank instead of borrowing. ## The 10 Strategies ### 1. Add Pay Now Links to Every Invoice Impact: High | Effort: Low | Time to result: Immediate This is the single highest-impact change you can make. A pay now button on your invoice removes every friction point between "I should pay this" and "I've paid this." Instead of asking customers to find bank details, open their banking app, type a sort code and reference -- they click a link and pay in 60 seconds. Card, bank transfer, Apple Pay, whatever they prefer. Businesses that add payment links to invoices report 30-50% reductions in DSO. The reason is simple: most late payments aren't disputes or cash flow problems. They're procrastination. Make it easy, and people pay immediately. This works with any invoicing system -- Xero, QuickBooks, Sage, or plain email. ### 2. Offer Multiple Payment Methods Impact: High | Effort: Low | Time to result: 1-2 weeks If your only payment option is bank transfer, you're excluding customers who'd prefer to pay by card, Apple Pay, Google Pay, or Open Banking. Every missing payment method is a segment of customers who'll pay slower -- because they have to do it the hard way. A single payment link that offers multiple methods on one checkout page removes this barrier. Card payments settle in 1-3 days. Bank transfers can take 3-5. Open Banking payments settle same-day. The method your customer chooses affects how fast you get paid. ### 3. Shorten Your Payment Terms Impact: Medium-High | Effort: Low | Time to result: 1-3 months If your terms are 30 days and your customers routinely pay at 50, try setting 14-day terms. Some customers will still pay late -- but "late" on 14-day terms is better than "late" on 30-day terms. Before shortening terms, make sure you've done Strategy #1. There's no point demanding faster payment if you haven't made it easy to pay. Short terms without a pay-now link is a recipe for frustrated customers and no improvement in cash flow. For new customers, set the shorter terms from day one. For existing customers, give 60-90 days notice before changing terms. ### 4. Send Automated Payment Reminders Impact: High | Effort: Medium | Time to result: 2-4 weeks A structured payment reminder sequence catches invoices before they become seriously overdue: - Day -5: Pre-due date reminder (courtesy) - Day 0: Due today notification - Day 7: Friendly first chase - Day 14: Firm follow-up (switch to SMS) - Day 30: Formal notice with statutory interest reference Each reminder should include the payment link. The reminder itself costs nothing to send -- and the payment link means the customer can pay the moment they read it. Most accounting software supports basic email reminders. For multi-channel automation (email, then SMS, then WhatsApp), you'll need a payment link provider that supports all channels. ### 5. Chase Across Multiple Channels Impact: High | Effort: Medium | Time to result: Immediate If your collection process is email-only, you're missing 80% of your audience. Email open rates for payment reminders average around 20%. SMS open rates are 98%. The most effective approach is escalating channels: - Email for the initial invoice and first reminder - SMS for the second chase (Day 14) - WhatsApp for the third chase (Day 21) - Posted letter with QR code for formal escalation (Day 30+) The same payment link works across all channels. See our multi-channel payment collection guide for the full playbook. ### 6. Run Credit Checks Before Extending Terms Impact: Medium | Effort: Medium | Time to result: 1-3 months Prevention is better than cure. Before extending credit to a new customer, check their payment history: - Companies House -- free basic financial data (accounts, filing history, CCJs) - Credit reference agencies -- Creditsafe, Experian Business, Dun & Bradstreet provide detailed credit reports (£5-50 per check) - Trade references -- ask the customer for two or three references from other suppliers For customers with poor credit history, consider requiring payment upfront or on shorter terms. For large customers with good credit, standard 30-day terms are appropriate. This won't help with existing debtors, but it prevents future bad debts from entering your book. ### 7. Invoice Immediately -- Don't Delay Impact: Medium | Effort: Low | Time to result: Immediate Every day between completing work and sending the invoice is a day added to your debtor days. If you finish a project on the 1st and invoice on the 15th, you've already lost two weeks before the payment clock starts. Invoice the same day the work is delivered or the service is completed. If your invoicing process involves approvals, draft the invoice before delivery so it can go out immediately. For recurring services (retainers, subscriptions), invoice at the start of the period, not the end. This is standard practice and most clients expect it. ### 8. Make Your Invoices Clear and Correct Disputed invoices don't get paid until the dispute is resolved. The most common causes of invoice disputes are: - Wrong amount -- mismatched PO number, incorrect hourly rate, VAT errors - Missing purchase order -- many large companies won't process an invoice without a PO number - Unclear description -- "Professional services -- March" doesn't tell accounts payable what they're paying for - Wrong recipient -- sent to the project manager instead of the accounts payable department Fix these and you eliminate the "we can't pay this because..." delay. Check that every invoice has: the correct PO number, a clear description of work, the right VAT treatment, and the correct billing contact. ### 9. Offer Early Payment Discounts Impact: Medium | Effort: Low | Time to result: 1-2 months A 2% discount for payment within 7 days (written as "2/7 net 30") can motivate customers to pay early. On a £10,000 invoice, that's £200 -- a cost to you, but less than the cost of waiting 60 days and the associated cash flow impact. Early payment discounts work best with: - Large invoices where 2% is a meaningful saving for the customer - Customers who have the cash but not the urgency - Recurring relationships where the discount becomes a habit Combine this with a payment link and you remove the last barrier -- the customer gets a discount AND can pay in one click. ### 10. Escalate Formally When Needed Impact: Variable | Effort: High | Time to result: 30-90 days For invoices that remain unpaid beyond 30 days despite reminders, escalate formally: - Day 30: Send a formal notice referencing the Late Payment of Commercial Debts Act and apply statutory interest - Day 45: Send a dunning letter by recorded delivery -- a Letter Before Action - Day 75+: File a County Court claim via Money Claim Online (for debts under £10,000) The key is having a consistent, documented process. Many businesses never escalate because they don't have a defined procedure. Create one, follow it, and your debtor days will fall -- partly because you're collecting faster, and partly because customers learn that you follow through. ## How to Measure Progress Track these metrics monthly: ### Days Sales Outstanding (DSO) Formula: (Trade Receivables / Revenue) x Days in Period This is the headline number. Track it monthly and set a target -- if you're at 55 days, aim for 40 within 6 months. ### Collection Effectiveness Index (CEI) Formula: (Beginning Receivables + Monthly Credit Sales - Ending Total Receivables) / (Beginning Receivables + Monthly Credit Sales - Ending Current Receivables) x 100 CEI measures how effective you are at collecting what's owed within your credit terms. A score above 80% is good; above 90% is excellent. ### Aged Debt Breakdown Split your receivables by age bracket: - Current (not yet due) - 1-30 days overdue - 31-60 days overdue - 61-90 days overdue - 90+ days overdue The goal is to keep the 60+ brackets as close to zero as possible. If more than 10% of your receivables are 60+ days overdue, your collection process needs attention. ### First-Reminder Resolution Rate What percentage of invoices get paid after the first reminder? If this is below 40%, your reminders aren't effective enough -- check that you're including payment links and sending at the right time. ## Quick Wins vs Long-Term Strategies Add payment links (#1) Multiple payment methods (#2) Automated reminders (#4) Multi-channel chasing (#5) Invoice immediately (#7) Clear invoices (#8) Shorten terms (#3) Medium-High 1-3 months Credit checks (#6) Early payment discounts (#9) 1-2 months Formal escalation (#10) 30-90 days Start with strategies 1, 2, and 4 -- they're low effort, high impact, and you'll see results within weeks. ## Common Questions ### What's a good DSO target? It depends on your industry and payment terms. If your standard terms are 30 days, a DSO of 35-40 is realistic and healthy. Below 30 is excellent. Above 50 means your collection process needs work. See DSO benchmarks by industry for UK-specific data. ### Will shortening payment terms upset customers? Some, yes. Give existing customers 60-90 days notice and explain why. Frame it positively: "We're making it easier to pay with new online payment options, and moving to 14-day terms." The pay-now link softens the blow -- shorter terms are less annoying when paying is effortless. ### Should I outsource collections? For invoices 90+ days overdue, a debt recovery agency may be more effective than internal chasing. Agencies typically charge 5-15% of recovered amounts. For invoices under 90 days, internal collection with the right tools (payment links, multi-channel reminders) is usually more cost-effective. ### How do payment links actually reduce debtor days? They eliminate friction. The #1 reason invoices are paid late isn't disputes or cash flow -- it's inconvenience. Copying bank details, remembering references, logging into banking apps. A payment link reduces "pay this invoice" to one click. That converts "I'll do it later" into "I'll do it now." ## Get Started Payment links are the quickest way to cut your debtor days. No IT project, no software migration, no change to your accounting workflow. Just a link on every invoice. Shuttle Payment Links work with 40+ gateways, support white-label branding, and can be sent via email, SMS, WhatsApp, or QR code. See how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### PCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope ## Links - [pay now button on your invoice](/guides/pay-now-button-invoices/) - [Xero](/blog/xero-payment-links/) - [QuickBooks](/blog/quickbooks-payment-collection/) - [Sage](/blog/sage-invoice-payments/) - [Open Banking](/blog/what-is-open-banking-and-pisp/) - [multiple methods on one checkout page](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [payment reminder sequence](/blog/payment-reminder-email-templates/) - [statutory interest reference](/blog/overdue-invoice-email-templates-uk/) - [accounting software](/blog/invoicing-made-easy-the-top-10-software-solutions-for-smes/) - [multi-channel automation](/guides/multi-channel-payment-collection/) - [multi-channel payment collection guide](/guides/multi-channel-payment-collection/) - [Late Payment of Commercial Debts Act](/blog/overdue-invoice-email-templates-uk/) - [dunning letter](/blog/dunning-letter-templates/) - [Money Claim Online](https://www.gov.uk/make-court-claim-for-money) - [DSO benchmarks by industry](/guides/dso-benchmarks-uk/) - [40+ gateways](/payment-providers/) - [white-label branding](/guides/white-label-payment-links/) - [See how it works](/merchants/links-checkout/) - [Book a Call](/discovery/) - [BlogPCI Compliance for Service Providers: Requirements, Levels & How to Reduce Scope→](/blog/pci-compliance-an-introduction-for-merchants-and-service-providers/) --- URL: https://www.shuttleglobal.com/guides/reduce-payment-processing-fees/ --- # How to Reduce Payment Processing Fees Without Switching Providers | Shuttle > Payment processing fees are one of the largest variable costs for any business that accepts cards. # How to Reduce Payment Processing Fees Without Switching Providers By Shuttle Team, March 13, 2026 Payment processing fees are one of the largest variable costs for any business that accepts cards. At low volumes, the standard 2.9% + 20p doesn't feel like much. At GBP 1M in annual card revenue, you're paying GBP 29,000+ in processing fees alone. At GBP 10M, it's GBP 290,000. At GBP 50M, you're spending more on payment processing than most businesses spend on their entire engineering team. The good news: most businesses are overpaying, and there are concrete steps to reduce costs without the disruption of a full provider switch. ## Why Fees Escalate at Scale ### The Flat-Rate Trap Most businesses start with a flat-rate provider like Stripe (2.9% + 20p) or Square (2.6% + 10p). Flat-rate pricing is simple and predictable. It's also designed to be profitable for the provider across a wide range of transaction types -- which means you're overpaying on low-risk, low-cost transactions to subsidise the provider's risk on high-cost ones. A UK debit card transaction has an interchange cost of around 0.2%. On a GBP 100 transaction, that's 20p. But Stripe charges you 2.9% + 20p -- GBP 3.10. The provider's markup is GBP 2.70 on a transaction that costs them roughly 40p to process (interchange + scheme fees + acquiring costs). That markup is acceptable when you're processing GBP 10,000 a month and the simplicity of flat-rate pricing saves you time. It's not acceptable when you're processing GBP 1M a month and the overpayment is tens of thousands of pounds annually. ### Cross-Border Markups Processing a card issued in another country typically costs 0.5% to 1.5% more than a domestic transaction. For businesses with international customers, cross-border fees can represent a significant chunk of total processing costs -- often without the business realising how much they're paying. Stripe, for example, charges an additional 1.5% for cross-border transactions and 2% for currency conversion. On a GBP 100 transaction from a US-issued card, the total fee is 4.4% + 20p -- GBP 4.60 per transaction. ### Hidden Charges Beyond the headline rate, watch for: - Chargeback fees -- GBP 15-25 per dispute, regardless of outcome - Refund fee retention -- most providers keep the processing fee when you issue a refund - PCI non-compliance fees -- monthly charges if you don't complete PCI self-assessment questionnaires - Monthly minimums -- fees if your processing volume falls below a threshold - Statement fees, batch fees, and gateway fees -- smaller charges that add up at scale - Currency conversion margins -- the spread between the real exchange rate and the rate your provider applies ## 7 Strategies to Reduce Your Payment Processing Fees ### 1. Negotiate on Volume Potential saving: 0.2% to 0.8% per transaction If you're processing more than GBP 50,000 per month, you have negotiating leverage. Payment providers have significant margin in their pricing, and they'd rather reduce your rate than lose your volume to a competitor. How to negotiate effectively: - Get competing quotes -- approach 2-3 other providers for formal pricing proposals before negotiating with your current provider - Know your numbers -- present your average transaction value, monthly volume, chargeback rate, and transaction mix (debit vs credit, domestic vs international) - Ask for interchange-plus -- providers are more likely to offer competitive rates on an interchange-plus model than to deeply discount flat-rate pricing - Negotiate annually -- don't set and forget. Review pricing every 12 months as your volume grows Even Stripe offers custom pricing for businesses processing significant volume. You won't get it by asking through the standard support channel -- you need to reach their sales team. ### 2. Switch to Interchange-Plus Pricing Potential saving: 0.3% to 1.0% per transaction Interchange-plus (also called cost-plus) pricing separates the non-negotiable costs (interchange and scheme fees) from the provider's markup. Instead of paying a blended rate of 2.9%, you pay the actual interchange rate (which varies by card type) plus a fixed markup. Volume (Monthly) Flat Rate (2.9% + 20p) Interchange-Plus (IC + 0.4% + 8p) GBP 50,000 GBP 510 (33%) GBP 200,000 GBP 2,200 (37%) GBP 500,000 GBP 14,700 GBP 5,700 (39%) GBP 1,000,000 GBP 29,200 GBP 17,500 GBP 11,700 (40%) Estimates based on a typical UK transaction mix (60% debit, 40% credit, 90% domestic). Actual savings vary. The savings increase with volume because flat-rate pricing over-charges on low-cost transactions (debit cards, domestic transactions) -- and those make up the majority of most businesses' transaction mix. Not all providers offer interchange-plus to smaller merchants. But if you're processing more than GBP 100,000 monthly, it should be available. ### 3. Use Local Acquiring to Reduce Cross-Border Fees Potential saving: 1.0% to 2.0% on international transactions When a UK customer pays with a UK-issued card and the transaction is processed through a UK acquirer, it's a domestic transaction with domestic interchange rates. When the same customer's transaction is processed through a US-based acquirer, it becomes cross-border -- with significantly higher fees. If you have customers in multiple countries, using local acquirers in each major market eliminates cross-border surcharges: - EU transactions processed through an EU acquirer avoid cross-border fees - US transactions processed through a US acquirer avoid international surcharges - APAC transactions processed through regional acquirers reduce costs and improve authorisation rates This requires either maintaining relationships with acquirers in each market (complex and operationally heavy) or using a payment platform that routes transactions to local acquirers automatically. ### 4. Route Transactions by Cost Potential saving: 0.3% to 0.5% per transaction Different payment providers charge different rates for different transaction types. Provider A might offer the best rate for UK debit cards but charge a premium for international credit cards. Provider B might be cheapest for recurring payments but expensive for one-off transactions. Intelligent routing sends each transaction to the lowest-cost provider for that specific card type, geography, and transaction type. This isn't manual switching -- it's automated, real-time routing based on pre-configured rules. For this to work, you need a multi-PSP architecture that connects to several providers simultaneously. Most businesses can't do this with a direct single-provider integration, but payment infrastructure platforms make it possible without additional engineering work. ### 5. Reduce Chargebacks Potential saving: GBP 15-25 per avoided dispute + indirect fee reduction Every chargeback costs you the transaction amount, the processing fee, and a chargeback fee (typically GBP 15-25). But the indirect cost is higher: elevated chargeback rates push you into monitoring programmes, trigger higher processing rates, and can ultimately lead to account termination. Practical steps to reduce chargebacks: - Use clear billing descriptors -- the name on the customer's bank statement should be recognisable. "SHUTTLEYOURCOMPANY" is better than "SP38291X" - Send transaction receipts immediately -- customers who recognise a charge don't file disputes - Implement 3D Secure selectively -- strong authentication on higher-risk transactions shifts liability and reduces fraud - Offer easy refunds -- a customer who can self-serve a refund won't file a chargeback instead - Use Visa CE 3.0 and Mastercard Ethoca alerts -- these services notify you of disputes before they become formal chargebacks, giving you the opportunity to refund proactively Keeping your chargeback rate below 0.5% not only avoids monitoring programme fees but also gives you leverage in rate negotiations. ### 6. Optimise for Scheme Fees Potential saving: 0.05% to 0.2% per transaction Card schemes (Visa, Mastercard) charge fees on top of interchange, and these fees vary based on how you process transactions. Optimisations include: - Send Level 2/Level 3 data for B2B transactions -- including purchase order numbers, item details, and tax amounts qualifies transactions for lower interchange categories - Use network tokens instead of PAN storage -- Visa and Mastercard offer lower interchange rates for transactions using their network tokens - Optimise authorisation-to-capture timing -- capturing transactions promptly (within 24 hours for e-commerce) avoids downgrade fees - Batch settle daily -- delayed settlement can trigger higher fees with some acquirers These are smaller individual savings, but they compound. A business processing GBP 10M annually can save GBP 5,000-20,000 through scheme fee optimisation alone. ### 7. Add Alternative Payment Methods Potential saving: 0.5% to 2.0% per transaction diverted from cards Cards are the most expensive payment method for merchants. Alternative methods are often significantly cheaper: - Open Banking (Pay by Bank) -- flat fee of 20p-50p per transaction, regardless of amount. On a GBP 500 transaction, that's 0.04-0.10% vs 2.9% for cards - Direct Debit (GoCardless, BACS) -- 1-2% or flat fees, ideal for recurring payments - Digital wallets -- Apple Pay and Google Pay can route via debit rails, reducing costs compared to credit card transactions - Bank transfers -- zero processing fee for higher-value B2B transactions The key is offering these methods at checkout without forcing customers away from cards. A "Pay by Bank" option alongside card payment captures cost-conscious customers and price-insensitive ones alike. ## How Multi-PSP Coverage Reduces Fees Automatically Strategies 3 and 4 -- local acquiring and cost-based routing -- require connecting to multiple payment providers simultaneously. For most businesses with a single direct integration, that means rebuilding their payment infrastructure. A PSP-neutral payment layer solves this by connecting to multiple providers through a single integration. You choose which connected provider handles each payment type. The factors worth weighing: - Card type -- debit vs credit, consumer vs commercial - Issuing country -- route to local acquirers to avoid cross-border fees - Transaction value -- fixed-fee providers are cheaper for high-value transactions, percentage-based providers are cheaper for low-value ones - Provider-specific rates -- leverage your negotiated rates across multiple providers Shuttle connects to 40+ PSPs through one integration. Adding a new provider is a configuration change, not an engineering project. You set which provider handles each payment type, so you can put volume where your rates are best without negotiating individual deals with every provider. Combined with portable tokens that work across any gateway, you maintain full negotiating leverage: if a provider raises their rates, move your merchants elsewhere. No migration, no customer impact, no re-integration. ## Building a Fee Reduction Plan Not every strategy applies to every business. Here's how to prioritise: Processing under GBP 50,000/month: Focus on strategies 5 (reduce chargebacks) and 7 (alternative payment methods). The volume-dependent strategies won't deliver meaningful savings yet. Processing GBP 50,000-500,000/month: Negotiate with your current provider (strategy 1) and push for interchange-plus pricing (strategy 2). These two changes alone can save 0.5-1.0% -- thousands of pounds annually. Processing over GBP 500,000/month: All seven strategies are relevant. The biggest wins come from multi-PSP routing (strategies 3 and 4), which requires the right infrastructure but delivers the largest per-transaction savings at scale. ## Key Takeaways Payment processing fees are not fixed costs. They're negotiable, optimisable, and reducible -- often significantly -- without switching your primary provider. The businesses that pay the least per transaction aren't the ones who found the cheapest provider. They're the ones who built the infrastructure to keep every provider competing for their volume. Related reading: - How Much Does a Payment Gateway Cost? - Credit Card Processing Fees Explained - What Is a Payment Gateway? - PSP-Neutral vs Single-PSP: Which Approach Is Right? ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### 7 ways merchants can save money on payment provider fees ### Card Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026) ### Payment Links for Trust Payments: Send Branded Checkout Links for European Card Processing ### Best Payment Gateways UK 2026: Fees, Features & Integration Compared ### Insurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac ### Payment Orchestration Alternatives for Platforms ## Links - [PSP-neutral payment layer](/guides/psp-neutral-vs-single-psp/) - [Shuttle connects to 40+ PSPs](/platforms/) - [portable tokens](/guides/payment-provider-lock-in/) - [How Much Does a Payment Gateway Cost?](/guides/payment-gateway-cost/) - [Credit Card Processing Fees Explained](/guides/credit-card-processing-fees/) - [What Is a Payment Gateway?](/blog/what-is-a-payment-gateway/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [Book a Call](/discovery/) - [Blog7 ways merchants can save money on payment provider fees→](/blog/7-ways-merchants-can-save-money-on-payment-gateway-fees/) - [BlogCard Processing Fees UK: Complete Guide to Rates, Costs & How to Save (2026)→](/blog/card-processing-fees-and-rates-for-uk-merchants/) - [BlogPayment Links for Trust Payments: Send Branded Checkout Links for European Card Processing→](/blog/payment-links-for-trust-payments/) - [BlogBest Payment Gateways UK 2026: Fees, Features & Integration Compared→](/blog/best-payment-gateways-for-uk-businesses-comparison/) - [AlternativeInsurance Payment Solutions Compared: Payment Layer vs Gateway vs PayFac→](/alternatives/insurance-payment-solutions/) - [AlternativePayment Orchestration Alternatives for Platforms→](/alternatives/payment-orchestration/) --- URL: https://www.shuttleglobal.com/guides/regal-ai-payments/ --- # How to Take Payments on Regal.ai Voice Agents: In-Call PCI-Compliant Capture | Shuttle > Regal.ai is a voice AI agent platform built for outbound contact: AI phone calls plus SMS and chat, with particular strength in collections, financial... # How to Take Payments on Regal.ai Voice Agents: In-Call PCI-Compliant Capture By Shuttle Team, May 21, 2026 Regal.ai is a voice AI agent platform built for outbound contact: AI phone calls plus SMS and chat, with particular strength in collections, financial services, insurance, healthcare, and BPO operations. Its agents place outbound calls at scale, hold natural conversations, and move accounts toward resolution. When it comes to money, Regal.ai today arranges the payment and directs the caller to a payment portal. Its collections agents confirm intent to pay, offer repayment options, schedule payment dates, and send a portal link so the borrower can complete the transaction. The actual card entry happens after the call, on a separate page the borrower has to visit. This guide covers how to close that last step inside the call itself: how Regal.ai handles payments now, why capturing at the moment of agreement matters for collections, and how Shuttle adds secure in-call PCI-compliant payment capture across 30+ gateways via a Twilio Pay handoff. ## How Regal.ai Handles Payments Today Regal.ai is designed to drive conversations to an outcome. In a collections context, the agent works the account: it confirms the right party, discusses the balance, offers repayment options, agrees a plan or a payment date, and provides a payment-portal link so the customer can pay. This is a clean, respectful model. Regal advertises PCI Compliant infrastructure and SOC 2 Type II, consistent with routing the customer to a portal rather than handling raw card data in the conversation. The agent secures the commitment, and the portal handles the card. The trade-off is the handoff. Once the call ends, completion depends on the borrower actually opening the link and finishing the payment. The agreement was reached live, but the money lands later, if it lands at all. ## Why In-Call Capture Matters for Collections In collections, the hardest part is reaching the right party. Right-party contact is expensive: dialler time, retries, compliance windows, and the cost of the conversation itself. When an agent finally has the borrower on the line and they agree to pay, that is the moment of maximum intent. Relying on a later portal visit lets that intent cool. People agree on the call and never open the link. Promise-to-pay rates always beat actual-payment rates, and every gap between agreement and payment is leakage. Capturing in the call closes the gap. The agent takes the first instalment while the borrower is still committed, and tokenises the payment method so future instalments in the plan run automatically on the scheduled dates. You collect at the moment of agreement instead of hoping the borrower returns to a portal. ## How Shuttle Works with Regal.ai Today Shuttle has no native integration with Regal.ai. Instead, you invoke Shuttle's Twilio-based payment setup. The handoff is API-driven: your application code triggers the Shuttle payment handoff at the point of payment. To use the in-call capture path, you must be a Twilio customer. - The Regal.ai agent agrees the amount or repayment plan with the borrower and confirms intent to pay. - At the point of payment, your application code triggers the Shuttle payment handoff. - The call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The borrower enters their card details on the keypad, and the digits are captured inside Shuttle's certified environment, so the raw card number never reaches the agent's hearing, the call recording, Regal.ai, or your systems. - Shuttle processes the payment and routes it to the creditor's chosen gateway, tokenising the method for any scheduled future instalments. - The result returns to your application in real time, so the conversation can continue with a confirmed payment instead of a pending link. You build the orchestration and agent-side wiring yourself. Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app. Honest caveat: secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Regal.ai agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. A native Regal.ai integration is possible only as a paid project. ## Multi-PSP Support Collections operations rarely run on a single gateway. Shuttle connects to 30+ payment gateways with per-client routing: - Route each creditor or client to their own gateway and merchant account. - Supported gateways include Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie. See the full list at /payment-providers/. - BPOs and collections agencies handling multiple creditors can keep funds, settlement, and reporting cleanly separated per client. - Add or switch gateways as configuration, not a new integration. A few gateways (for example, Braintree) do not work for voice capture but do work for payment links. This makes Shuttle a fit for agencies that collect on behalf of many creditors, each with their own banking and PSP requirements. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of card data security validation. Handing the call to Shuttle's secure capture keeps raw card data out of your environment entirely. The borrower enters their card on the keypad, the digits are captured inside Shuttle's certified environment, and they never reach the agent, the recording, Regal.ai, or your call infrastructure. That keeps card data out of your PCI scope. The practical effect is the difference between a heavyweight SAQ-D obligation, which applies when card data flows through your systems, and the much lighter SAQ-A posture, which applies when a certified Service Provider handles capture for you. ## Beyond Voice: Payment Links Payment links are the turnkey path, and they work even with gateways that do not support voice capture. In-call capture does not mean abandoning the portal model. Shuttle also generates hosted payment links you can send by SMS or email, including mid-call, so you keep the link option inside the same payment layer. If a borrower prefers to pay later, or the call drops before completion, the agent (or an automated follow-up) sends a Shuttle payment link by text. Whether the customer pays in the call or via a link, it runs through the same gateways, the same tokenisation, and the same reporting. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Debt Collection and Repayment Plans Take the first instalment in the call and tokenise the card so the agreed plan runs automatically on each scheduled date. No reliance on the borrower returning to a portal. ### Bill-Pay and Past-Due Balances Settle overdue invoices, subscriptions, and account balances live during the outbound call, with confirmation back to your application before the conversation ends. ### Outbound Sales Convert an outbound AI sales call into a completed purchase in the same conversation, capturing the card at the point of yes rather than emailing a checkout link. ### Insurance and Loan Servicing Collect premiums, reinstatement payments, and loan instalments on outbound servicing calls, with per-client gateway routing for carriers and servicers managing multiple books. ## FAQ Does Regal.ai capture card payments in the call? Public evidence shows Regal.ai arranging the payment and directing the caller to a payment portal link rather than completing card capture in the conversation. Its agents confirm intent, schedule dates, and hand off to the portal for the actual transaction. Shuttle adds the in-call capture step on top of that workflow via a secure Twilio Pay handoff. Does Shuttle have a native Regal.ai integration? No. Shuttle has no native Regal.ai integration. You invoke Shuttle's Twilio-based setup, and your application code triggers the payment handoff at the point of payment. A native Regal.ai integration is possible only as a paid project. Does this require Twilio? Yes, for the in-call capture path today. The secure capture runs via Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Payment links do not require Twilio. How do I take payment during a Regal.ai call? Your application code triggers the Shuttle payment handoff at the point of payment. The call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, the borrower enters their card on the keypad, Shuttle captures it in its certified environment, processes it through the creditor's gateway, and returns confirmation to your application. Can an AI agent split a balance into a payment plan? Yes. Shuttle tokenises the payment method when the first instalment is taken, so the remaining instalments run automatically on the dates the agent agreed during the call. Which payment gateways does Shuttle support? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie, with per-client routing. See /payment-providers/. A few gateways (for example, Braintree) do not work for voice but do work for payment links. Switching is configuration, not re-integration. Does this work for outbound calls? Yes. Shuttle supports the outbound, collections-led calling that Regal.ai specialises in, capturing payment at the moment of agreement on outbound calls. ## Related Reading - AI Voice Payments for Debt Collection: taking payments and running repayment plans on AI collections calls. - Secure Payment Collection for Debt Agencies: secure, multi-creditor payment collection for debt agencies. - AI Voice Agent PCI Payments: how PCI-compliant payment capture works inside an AI voice agent. - Voice Payments: the full picture on taking payments over voice channels. - The Payment Layer for AI Agents: why AI agents need a dedicated payment layer. ## Add Payments to Your Regal.ai Agents Capture payments at the moment of agreement on Regal.ai calls via a secure Twilio Pay handoff. 30+ gateways, per-client routing, PCI DSS Level 1, and $0.20 per successful transaction with no setup or per-seat fees. Read the Twilio setup docs, the payment links docs, and the security overview. See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [/payment-providers/](/payment-providers/) - [PCI DSS](/glossary/pci-dss/) - [PCI scope](/glossary/pci-scope/) - [AI Voice Payments for Debt Collection](/guides/ai-voice-payments-debt-collection/) - [Secure Payment Collection for Debt Agencies](/guides/secure-payment-collection-debt-agencies/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [$0.20 per successful transaction](/pricing/) - [Twilio setup docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links docs](https://docs.shuttleglobal.com/docs/links-intro) - [security overview](https://docs.shuttleglobal.com/docs/org-security) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/replicant-payments/ --- # How to Add Payments to Replicant AI: Voice Agent Payment Integration | Shuttle > Replicant builds autonomous AI agents for contact centres. Their platform handles the Tier 1 support calls that make up the bulk of inbound volume -- ... # How to Add Payments to Replicant AI: Voice Agent Payment Integration By Shuttle Team, March 11, 2026 Replicant builds autonomous AI agents for contact centres. Their platform handles the Tier 1 support calls that make up the bulk of inbound volume -- account lookups, status checks, appointment scheduling, FAQ resolution -- without a human agent. For contact centres processing thousands of calls a day, Replicant eliminates the staffing bottleneck for routine interactions. But routine interactions often end with a payment. A customer confirms their outstanding balance and wants to settle it. A caller verifies their account details and asks to update their payment. A service request is completed and payment is due. Replicant's AI agents can handle everything up to and after the payment. The payment itself, capturing a card number, processing it through a gateway, returning a result, requires infrastructure that sits outside the conversational AI stack entirely. The AI model must never see, hear, or process cardholder data. That's a PCI DSS requirement, not a product limitation. Shuttle provides the PCI-compliant payment layer that lets Replicant agents capture payments during a call without any cardholder data entering Replicant's platform. There is no native Replicant integration: instead, your application invokes Shuttle's Twilio-based secure capture, and the card is captured inside Shuttle's certified environment, not Replicant's. This does require you to be a Twilio customer today. ## The Payment Challenge for Replicant Replicant's value proposition is automation. Every call their AI handles is a call that doesn't need a human agent. But if a call requires a payment and the AI can't process it, the call gets transferred -- and the automation benefit is lost. The challenge is structural: Card data is toxic to AI infrastructure. The moment a customer enters card digits via their keypad, those DTMF tones carry cardholder data. If they enter Replicant's audio pipeline, Replicant's entire infrastructure is in PCI scope: the speech recognition engine, the AI model, call recordings, transcription logs, data storage, and every network path those systems use. PCI certification is expensive and slow. Level 1 PCI DSS certification for a complex AI voice infrastructure costs $500,000+ initially and $200,000+ annually. It requires quarterly vulnerability scans, annual penetration testing, a Qualified Security Assessor, and ongoing compliance management. For a company whose core product is conversational AI, that's a massive diversion of engineering and security resources. Human handoffs defeat the purpose. If the AI agent has to transfer the caller to a human agent or a separate IVR system every time there's a payment, the automation promise breaks down. The customer waits on hold. The human agent handles a simple card capture. The cost savings evaporate. The solution is a secure payment handoff that captures card data in a completely isolated PCI-compliant environment and returns the result to your application, so card data never reaches Replicant. ## How Shuttle Works with Replicant Today There is no native Replicant integration. Instead, the handoff is API-driven and built on Shuttle's Twilio-based capture, with a clean boundary where cardholder data exists only on Shuttle's side. You must be a Twilio customer, and your application code triggers the handoff at the point of payment. Here's the architecture: - Replicant manages the conversation -- The AI agent handles the call: intent recognition, customer verification, amount confirmation, and conversational flow. All of this is standard Replicant functionality. - A secure PCI capture is triggered for payment -- When payment is needed, your application invokes Shuttle's secure capture. Today this runs over Twilio Pay, with Shuttle as the certified capture and gateway connector, operating within its own PCI DSS Level 1 certified environment. - Shuttle captures the card -- The customer enters their card on their keypad during that secure PCI capture. The digits are captured by Shuttle in its certified environment, so they never reach Replicant or the AI model. - Payment is processed -- Shuttle tokenises the card data and routes it to the merchant's payment gateway. The authorisation happens entirely within Shuttle's certified perimeter. - Result flows back -- Shuttle returns the transaction outcome to your application via webhook: success or failure, a transaction reference, and a masked card number. The AI agent uses this to confirm the payment conversationally. One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Replicant agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring. A native Replicant integration is possible only as a paid project. ## How It Works: Step by Step Here's the flow during a live Replicant call: Step 1: Payment intent detected. The Replicant agent identifies that the customer wants to pay. This could be triggered by the customer's request, a workflow condition, or a backend lookup showing an outstanding balance. Step 2: Amount confirmed. The agent confirms: "Your outstanding balance is $156.00. Would you like to pay that now?" The customer says yes. Step 3: Payment explained. The agent sets expectations: "I'll just need your card details. You'll be prompted to enter them using your phone keypad." Step 4: Shuttle session created. Your application calls Shuttle's API with the payment amount, currency, and the merchant's gateway configuration. Shuttle returns a session token and signals readiness. Step 5: Secure capture begins. At the point of payment, a secure PCI DSS Level 1 capture takes over the card collection (today, via Twilio Pay). Shuttle plays secure prompts: "Please enter your 16-digit card number followed by the hash key." The customer enters digits via their keypad. Step 6: Card captured in isolation. Shuttle captures the keypad digits inside its certified environment. The card never reaches Replicant or the AI model, so call recordings never contain card data. Step 7: Card processed. Shuttle tokenises the card and sends the authorisation request to the merchant's gateway. The response comes back within seconds. Step 8: Result returned. Shuttle sends the outcome to your application. The AI agent confirms: "Your payment of $156.00 has been processed. Your confirmation number is TXN-5518. Is there anything else I can help with?" The customer stays on the line throughout the capture, with no transfer to a human agent. Returning the caller to the same Replicant agent and call after payment works today: your Twilio flow routes the call back and passes a conversation ID, so the agent resumes with context. Shuttle provides the secure capture and the result webhook; the return leg is wiring your team owns. ## Multi-PSP Support Replicant serves contact centres across industries: healthcare, financial services, insurance, utilities, telecoms. Each of those industries has established payment gateway relationships. A healthcare billing centre might process through Stripe. An insurance company might use Worldpay. A utility provider might route through Adyen. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and others. Switching gateway is configuration, not re-integration. Each Replicant deployment can be configured with the appropriate gateway for that merchant. A few gateways (Braintree, for example) do not work for voice capture because they will not allow raw card data to be passed, but they do work for payment links. Routing capabilities include: - Per-merchant configuration -- Each contact centre using Replicant can connect to their own PSP - Multi-PSP routing -- Route transactions based on currency, region, or card type - Failover -- Automatic routing to a backup gateway if the primary is unavailable - No integration multiplication -- One Shuttle integration covers all gateways, regardless of how many different PSPs Replicant's customers use This is particularly important for Replicant's enterprise customers, who often have multi-PSP strategies for redundancy and cost optimisation. ## PCI Compliance The integration architecture keeps cardholder data out of Replicant's and its customers' environments, which is what limits their PCI scope. What Replicant handles: - Conversation flow, intent detection, customer authentication - Payment amount confirmation and session initiation via API - Transaction result handling (success/failure, reference, masked card number) This is all non-sensitive data. It doesn't expand PCI scope. What Shuttle handles: - Secure card capture after the handoff - Card data tokenisation - Gateway communication and authorisation - Secure prompt playback during card entry All of this happens within Shuttle's PCI DSS Level 1 certified environment. Call recordings are clean. Because the card is entered during the secure PCI capture, the digits are never part of the audio Replicant processes or records. No cardholder data is stored in Replicant's infrastructure, or in the contact centre's infrastructure. SAQ-A eligibility. Because card data never enters Replicant's systems, the contact centres using Replicant can self-assess under SAQ-A for payment processing. This is the simplest PCI compliance tier -- no penetration testing, no quarterly ASV scans, no on-site QSA audits. Shuttle is a PCI DSS Level 1 certified Service Provider. The certification covers the complete card capture, tokenisation, and routing pipeline. ## Beyond Voice: Payment Links Payment links are the turnkey path. During a Replicant call, your application can send a payment link via SMS or email, including mid-call, as an alternative to keypad entry. The flow: the agent confirms the payment amount, then tells the customer "I've sent a secure payment link to your mobile number." Shuttle generates a hosted checkout page and delivers it via SMS. The customer opens the link, enters their card details on a secure page, and completes the payment. The result is returned to your application in real time. Links work even with gateways that do not support voice capture. Payment links are useful when: - The customer prefers visual confirmation of the amount and merchant - Higher-value transactions where customers want to see what they're paying - The caller has difficulty with keypad entry (accessibility, unfamiliarity) - The contact centre wants to offer the customer a choice of payment method Both the secure capture and payment links use the same Shuttle infrastructure, the same PCI-compliant environment, and the same gateway routing. Your application can offer either option based on the conversation context. ## FAQ Does Shuttle have a native Replicant integration? No. There is no native Replicant integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment. A native Replicant integration is possible only as a paid project. Does this require Twilio? Yes, today. The secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Can Replicant agents take payments without a secure handoff? Not compliantly. If card data enters Replicant's audio pipeline, the entire platform is in PCI scope. Shuttle's secure capture keeps card data isolated so Replicant's infrastructure stays clean. Does this work with Replicant's existing call flows? Yes. The Shuttle handoff is triggered at the point in the conversation where payment is needed. It's an additional step in the workflow, wired up by your application code. You build the agent-side orchestration; Shuttle provides the capture, payment links, and APIs. What if the customer's card is declined? Shuttle returns the decline reason to your application. The AI agent can offer to retry with a different card, send a payment link as an alternative, or handle the situation according to the contact centre's configured workflow. How many payment gateways does Shuttle support? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and others. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture. What does Shuttle charge? $0.20 per successful transaction for voice. No setup fees, no per-seat licensing. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - How AI Voice Agents Take PCI-Compliant Payments -- The technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide -- IVR, agent-assisted, and AI voice payment models compared - Twilio Pay Connectors -- How Shuttle connects to Twilio's payment infrastructure - The Payment Layer for AI Agents -- Why AI agents need a dedicated payment layer - Contact Centre Payments -- PCI-compliant payment capture for contact centres ## Add Payments to Your Replicant Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're deploying Replicant AI agents and need PCI-compliant payment capture, talk to us about Voice Checkout or see how it works for platforms. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS](/glossary/pci-dss/) - [DTMF tones](/guides/dtmf-payments/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [30+ gateways](/payment-providers/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [talk to us about Voice Checkout](/platforms/voice-checkout/) - [see how it works for platforms](/platforms/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/retell-ai-payments/ --- # How to Take Payments on Retell AI Voice Agents: PCI-Compliant Payments | Shuttle > Retell AI lets developers build production-grade AI voice agents fast. Its API-first platform handles the hard parts of voice AI, so teams can focus on... # How to Take Payments on Retell AI Voice Agents: PCI-Compliant Payments By Shuttle Team, March 9, 2026 Retell AI lets developers build production-grade AI voice agents fast. Its API-first platform handles the hard parts of voice AI, so teams can focus on the conversation rather than the telephony stack. But when one of those agents needs to take a payment, the card details have to be handled somewhere other than the AI pipeline. This guide covers how to take PCI-compliant payments on Retell AI voice agents using Shuttle, so your agents can collect card payments during a call without putting your application or Retell's platform in PCI scope. It is written as "payments done right on Retell, with Shuttle": Retell runs the conversation, Shuttle runs the secure payment. Developers are building appointment booking agents, outbound sales callers, customer service bots, and lead qualification systems on Retell. Many of those use cases end with a payment. A customer confirms a booking and needs to pay. A caller agrees to settle an outstanding bill. A lead converts and wants to purchase. Retell deliberately focuses on the conversation, not card handling, and that is the right design. The AI model must never see, hear, or process cardholder data. That is a PCI DSS requirement. The secure pattern, which Retell itself recommends, is to hand the call off to a dedicated payment layer before any card details are entered, so the card number never reaches Retell or the LLM. Shuttle is that payment layer. When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call at the point of capture (today, via Twilio Pay), and the result comes back to your application. The card digits never touch your application or Retell's platform. ## The Payment Challenge for Retell AI Retell AI is a developer platform. That means the teams building on it are making their own architectural decisions, and when they hit the payment question, they face the same compliance reality that every voice AI platform faces. Card data cannot enter the AI pipeline. If a customer presses their card digits during a Retell call, those DTMF tones are cardholder data under PCI DSS. Retell is not PCI DSS Level 1 certified, and its PII redaction runs *after* the language model has already processed the input, so capturing card details inside the Retell call would still pull your stack into PCI scope. That includes Retell's speech infrastructure, your LLM, your call recordings, your database, and every network path connecting them. The card entry has to happen off Retell entirely. Building your own payment capture is not viable. PCI DSS Level 1 certification costs $500,000+ initially and $200,000+ per year. It requires a Qualified Security Assessor, quarterly vulnerability scans, annual penetration testing, and strict controls on every system that handles card data. For a startup or small team building on Retell, that is not a realistic investment. Redirecting to a separate system breaks the experience. If your Retell agent has to tell the customer "Please hang up and call our payment line," the seamless AI experience breaks down. The customer waits, gets confused, or drops off entirely. The goal is to keep the customer on the line and hand the call to a secure payment environment, rather than send them away. The solution is a payment layer the agent can hand the call to, that captures card data in an isolated PCI-compliant environment and returns the result, without the card ever passing through Retell. ## How Shuttle Integrates with Retell AI Shuttle provides the payment infrastructure that Retell AI agents need. The integration is API-driven, which fits Retell's developer-first model: your application code orchestrates the payment flow, and the card itself is captured by Shuttle in its PCI DSS Level 1 certified environment, never by Retell. Shuttle ships the secure PCI capture, payment links, and the payment APIs; what you build is the small glue on your side: pass the payment amount to Shuttle through its API (the minimum data we need), trigger the handoff from your agent, and handle the result. There is no out-of-the-box screen or input UX wired for your specific app, and teams building on Retell have already wired this up. Here's the architecture: - Your Retell agent manages the conversation: Intent recognition, customer interaction, amount confirmation, all handled by your agent's LLM and Retell's voice infrastructure. - A secure PCI capture is triggered for payment: When payment is needed, the card capture runs as a secure, PCI DSS Level 1 call at the point of capture. Today this runs over Twilio Pay, with Shuttle as the certified capture and gateway connector. - Shuttle captures the card: The customer enters their card details on their keypad during that secure PCI call. The digits are captured by Shuttle in its certified environment, so they never reach Retell or the LLM. - Payment is processed: Shuttle tokenises the card and routes it to your configured payment gateway. The authorisation happens entirely within Shuttle's certified environment. - Result returned to your application: Shuttle sends a webhook with the transaction outcome (success or failure, a transaction reference, and a masked card number), which your application uses to confirm the payment. Retell handles the voice. Shuttle handles the card. Your application ties them together. One honest caveat worth setting expectations on up front: the secure PCI capture at the point of payment is available now, and returning the caller to the same Retell agent afterwards is wiring your application owns: you program the return route in your Twilio flow and pass a conversation ID. See Call control: what's live today. ## How It Works: Step by Step Here's what happens during a live call with a Retell AI agent integrated with Shuttle: Step 1: Payment intent recognised. Your Retell agent detects that the customer wants to pay. This could be explicit ("I'd like to pay for my appointment") or triggered by your application logic (a booking is confirmed and payment is due). Step 2: Amount confirmed. The agent says: "The total for your appointment is $85.00. I'll connect you to our secure payment line to take your card details." Step 3: Secure capture triggered. At the point of payment, a secure PCI DSS Level 1 call takes over the card capture (today, via Twilio Pay, with Shuttle as the certified connector). This is the key step: the card is captured inside that secure PCI call, so it never touches Retell or the LLM. Step 4: Card details entered securely. During the secure PCI call, the customer is prompted to enter their card number, expiry, and CVV on their phone keypad. Shuttle captures the digits inside its certified environment. Step 5: Payment processed. Shuttle tokenises the card data and sends it to your payment gateway for authorisation. This takes a few seconds. Step 6: Result returned. Shuttle sends the outcome to your application via webhook: success or failure, a transaction reference, and a masked card number. Your application records the result and confirms the payment to the customer. The customer stays on the line throughout. There is no "hang up and call another number." The card is captured by Shuttle, not Retell, which is what keeps your stack out of PCI scope. ## Call control: what's live today This is the part most guides gloss over, so we'll be straight about it. Available now (Twilio Pay product): the card capture runs as a secure, PCI DSS Level 1 call at the point of capture. When it is time to pay, the secure capture takes the card, the customer pays, and your application receives the result. The card never passes through Retell. Not yet available on the Twilio-only product: Shuttle being present for the entire call, or being dialed in at exactly the right moment. Today, the secure capture is scoped to the point of capture, not the whole conversation. Shuttle works with Twilio today, and any carrier coming soon. The practical consequence: returning the caller to the same Retell agent and call after payment works today, but it is wiring your application owns: you program the return route in your Twilio flow and pass a conversation ID so the agent resumes with context. Shuttle is not yet riding the full call, and the return-leg orchestration is not shipped out of the box. If your flow needs the agent to pick the conversation back up seamlessly after payment, talk to us about where this work is, and we will give you the honest current state rather than overpromise. ## Multi-PSP Support If you're building on Retell AI, you might be a startup using Stripe. Or you might be building for an enterprise customer that requires Adyen. Or you might be building a multi-tenant application where each of your customers uses a different gateway. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, and others. Your Shuttle configuration determines which gateway processes each transaction. For developers building multi-tenant applications on Retell, this is particularly valuable: - Per-tenant gateway configuration: Each of your customers can use their own PSP - Single integration: You integrate with Shuttle once. Gateway routing is configuration, not code. - Multi-PSP routing: Route by currency, region, card type, or custom rules - Failover: Automatic fallback to a secondary gateway if the primary is unavailable This means you can offer payment capability to all your customers without building and maintaining separate gateway integrations for each one. ## PCI Compliance For developers building on Retell AI, PCI compliance is the single biggest reason to use a payment layer rather than building card capture yourself. What stays in your application / Retell: - Conversation management and agent logic - Payment amount calculation and confirmation - Initiating the handoff to Shuttle - Transaction result handling (webhook with non-sensitive data) None of this is cardholder data. Your application and Retell's platform stay out of PCI scope. What stays in Shuttle: - Secure card capture after the handoff - Card data tokenisation - Gateway communication and authorisation - Secure prompt playback All within Shuttle's PCI DSS Level 1 certified environment. Call recordings: because the card is entered during the secure PCI capture, the card details are never part of the audio Retell processes or records. Any call recordings you store on Retell do not contain cardholder data. There are no card digits in your recordings, your logs, or your database. Your PCI scope: with Shuttle handling all card data, your application typically qualifies for SAQ-A, the simplest PCI compliance tier. You are not storing, processing, or transmitting cardholder data. Your PCI obligation is limited to the API calls between your server and Shuttle, which contain no card data. Shuttle is a PCI DSS Level 1 certified Service Provider. That covers the full pipeline: capture, tokenisation, gateway routing, and authorisation. ## Beyond Voice: Payment Links The secure PCI capture at the point of payment is the primary method during voice calls, but Shuttle also supports payment links, and for some Retell use cases, they are the better option. During a Retell call, your agent can tell the customer: "I've just sent a secure payment link to your mobile." Shuttle generates a hosted checkout page and delivers it via SMS. The customer taps the link, enters their card details on the secure page, and completes the payment. The result is returned to your application. Payment links are useful for: - Higher-value transactions: Customers may prefer to see the amount and merchant details on screen before entering their card - Mobile-first customers: If the caller is on a mobile phone, switching to a browser is seamless - Accessibility: Customers who find keypad entry difficult can use the visual checkout instead - Post-call payments: Your agent can send a payment link at the end of a call for the customer to complete later Both methods use the same Shuttle infrastructure and PCI-compliant environment. Your application logic decides which method to use based on context. ## Use Cases Retell agents tend to cluster around a few high-value workflows, and most of them end in a payment. Here is where Shuttle fits. ### Appointment Booking (Clinics, Salons, Services) Booking agents for clinics, dental practices, salons, and service businesses confirm an appointment and then need a deposit or full payment to secure it. The Retell agent confirms the slot, states the amount, and triggers the secure card capture, all before the customer hangs up. Taking payment at the point of booking is a common way to reduce no-shows. ### Outbound Sales and Collections Outbound Retell agents that close sales or chase outstanding balances need to capture payment at the moment of agreement. The agent triggers the secure card capture the instant the customer commits, so there is no callback and no link that goes unclicked. ### Lead Qualification to Purchase When an inbound agent qualifies a lead and the conversation turns into a sale, the payment has to happen in the same call or momentum is lost. Shuttle lets the agent move straight from "you're a fit" to taking payment, by handing the call to the secure payment line, rather than routing to a human. ### Customer Service Bill-Pay Support agents handling account queries frequently get asked "can I just pay my bill now?" With Shuttle, the Retell agent hands the call to the secure payment environment in the same conversation, rather than transferring the customer to a separate payment line. ## Developer Integration Retell AI is a developer platform, so the Shuttle integration is designed to fit into a typical development workflow: API-driven. Initiate the payment handoff, configure gateways, and receive webhooks via REST API. No SDKs required (though they're available). Built on Twilio Pay today. The secure card capture currently runs over Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle works with Twilio today, and any carrier coming soon. Webhook-based results. Transaction outcomes are delivered via webhook to your application server. Parse the payload, update your database, and confirm the payment to the customer. Test mode available. Test the full payment flow with test card numbers before going live. Same API, same flow, no real charges. $0.20 per successful transaction. No setup fees, no per-seat licensing. You pay for successful transactions, not infrastructure. ## FAQ Can I capture card payments directly inside a Retell call? No. Retell is not PCI DSS Level 1 certified, and its PII redaction runs after the language model has already processed the input, so capturing card digits inside the Retell call would keep your stack in PCI scope. The secure pattern, which Retell itself recommends, is to hand the call off to a dedicated payment layer before any card details are entered. Shuttle is that handoff. Is Retell PCI compliant? Retell is not a PCI DSS Level 1 certified payment processor, and it is not designed to be one. It runs the conversation. Payments are handled off-platform by Shuttle, which is PCI DSS Level 1 certified, so Retell and your application stay out of scope. After payment, does the call return to my Retell agent automatically? The secure PCI card capture is available now on the Twilio Pay product. Returning the caller to the same Retell agent and call after payment works today when you program the return route in your Twilio flow and pass a conversation ID; Shuttle does not ship that orchestration out of the box, and Shuttle does not yet ride the full call. Shuttle being present for the entire call (or dialed in at the right moment) is on the roadmap with the carrier-agnostic version. We will give you the honest current state for your flow rather than overpromise. What payment gateways does Shuttle support? 30+ gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and others. You configure your gateway in Shuttle and it handles the routing. Can I build PCI-compliant payment capture myself on Retell? Technically, but the cost is prohibitive. PCI DSS Level 1 certification requires $500,000+ upfront and $200,000+/year in ongoing compliance costs. Shuttle provides the same capability at $0.20 per successful transaction. Can I use this for outbound calls? Yes. If your Retell agent makes outbound calls and needs to collect payment during the call, the same secure Shuttle capture works. The capture is triggered identically to inbound calls. ## Related Reading - How AI Voice Agents Take PCI-Compliant Payments: The technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared - Vapi Payments: PCI-compliant payment capture for voice agents built on Vapi - Bland AI Payments: secure payment capture for Bland AI phone agents - Dialpad Payments: Secure voice payments for Dialpad Ai Contact Center - RingCentral Payments: PCI-compliant payment capture for RingCX and RingEX - The Payment Layer for AI Agents: Why AI agents need a dedicated payment layer - Contact Centre Payments: PCI-compliant payment capture for contact centres - Phonely Payments: PCI-compliant payment capture for Phonely AI phone agents ## Add Payments to Your Retell AI Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If you're building voice agents on Retell AI and need PCI-compliant payment capture: See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [DTMF tones](/guides/dtmf-payments/) - [PCI scope](/glossary/pci-scope/) - [30+ payment gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [30+ gateways](/payment-providers/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [Dialpad Payments](/guides/dialpad-payments/) - [RingCentral Payments](/guides/ringcentral-payments/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [Contact Centre Payments](/guides/contact-centre-payments/) - [Phonely Payments](/guides/phonely-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/ringcentral-payments/ --- # How to Take Payments on RingCentral: Secure Payment Processing | Shuttle > RingCentral Does Not Have Native Payment Capture RingCentral is one of the largest UCaaS and CCaaS providers in the market. # How to Take Payments on RingCentral: Secure Payment Processing By Shuttle Team, February 26, 2026 ## RingCentral Does Not Have Native Payment Capture RingCentral is one of the largest UCaaS and CCaaS providers in the market. RingEX handles unified communications. RingCX is their contact centre product: AI-powered, omnichannel, with workforce engagement and analytics built in. What RingCentral does not have is PCI-compliant payment capture. When a customer on a RingCentral call says "I'd like to pay," there is no native mechanism to securely collect their card details. The agent either takes the number verbally, putting card data into recordings, transcriptions, and PCI scope, or directs the customer to pay through another channel. Both approaches are poor outcomes. This is a significant gap for businesses running RingCentral in industries where phone payments are a daily operation: insurance, utilities, debt collection, travel, and professional services. ## The Payment Gap in RingCentral RingCentral has invested heavily in AI: RingSense for conversation intelligence, AI-powered agent assist, automated summarisation. RingCX is a capable CCaaS platform. But payment capture was not part of the product roadmap. No DTMF isolation. RingCentral can handle DTMF input for IVR navigation, but there is no mechanism to capture DTMF card entry while suppressing tones from the agent audio and call recording. If a customer enters card digits via keypad during a RingCentral call, the agent hears the tones and the recording captures them. AI features create additional exposure. RingSense transcribes and analyses calls. If a customer reads a card number aloud, that data is transcribed, stored, and potentially surfaced in analytics dashboards. The AI features that make RingCentral attractive also amplify the PCI risk of handling card data on the platform. No payment API in the platform. RingCentral's API is extensive for call management, messaging, and video, but there is no payment-specific API. Building a custom payment integration requires developing outside the platform and managing the PCI implications yourself. UCaaS-first architecture. RingCentral's heritage is unified communications. RingCX is newer and still building out its contact centre feature set. Payment capture, a niche but critical requirement for specific industries, is not a priority for a platform focused on competing with Microsoft Teams and Zoom on the UCaaS side. The result: businesses running RingCentral that need to take phone payments are left to find their own solution. Most default to sending payment links after the call, which works but increases drop-off and slows cash collection. ## How Shuttle Adds Payments to RingCentral Shuttle adds PCI-compliant card capture to your RingCentral calls. When the customer is ready to pay, they enter their card on their phone keypad, the digits are captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your RingCentral recordings, RingSense transcription and analytics, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for RingCentral specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your RingCentral call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running RingCentral have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. They never reach your RingCentral recordings, RingSense transcription and analytics, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for RingCentral, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running RingCentral have already built this. There is more in the "What to Expect" section below. ## How a voice payment works - The call proceeds on RingCentral as normal. Standard call handling, queries, account management, issue resolution. - Payment is triggered from your agent interface when the customer is ready to pay. - Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits are captured inside Shuttle's certified environment. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. Provider selection can be configured by merchant and payment type. - Result returned to your interface and your systems via webhook. A tokenised reference is available for CRM logging. - No card data in RingCentral. The card digits never touch your RingCentral recordings, RingSense analytics, or your agent workstations. ## Multi-PSP Support Businesses running RingCentral often operate across multiple regions or business units, each with their own PSP relationships. Shuttle supports 40+ PSPs and allows flexible routing: - By merchant: different clients or business units route to different gateways - By region: UK transactions to one PSP, US transactions to another - By switching: if the primary gateway is unavailable, you can move the affected payment types to another connected gateway - By card type: route specific card schemes through preferred processors Switching processors later is straightforward; gateway choice is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This flexibility is particularly relevant for BPO and outsourced contact centre operations running RingCentral, where different end clients have different PSP requirements. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of payment security certification. Because the card is captured in the secure Twilio Pay call, card data never enters your RingCentral environment, keeping you on the lighter SAQ-A path: - Card data never enters your RingCentral environment - Call recordings contain no cardholder data - RingSense transcription and analytics process no card information - Agents never hear, see, or handle card numbers - Your network infrastructure is out of PCI scope Full compliance documentation, including the AOC scope, is in the security docs. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Use Cases ### Insurance Brokers and Underwriters Insurance businesses running RingCentral handle premium payments, policy renewals, and mid-term adjustments over the phone. Shuttle allows agents to collect payment during the renewal conversation, critical for retention, without creating PCI exposure or breaking the call flow. ### Professional Services Accountancy firms, legal practices, and consultancies using RingCentral for client communications can collect invoice payments during calls. The client confirms the amount, enters their card via keypad, and payment is confirmed before the call ends. ### Debt Collection Agencies Collections teams running RingCentral need to capture payment when the debtor is engaged and willing to pay. Transferring to a separate system or sending a link risks losing the commitment. Shuttle enables immediate, secure payment capture mid-call. ### Travel and Events Travel agencies and event companies processing bookings over the phone can capture payment at the point of commitment. The customer confirms their booking, enters card details via keypad, and receives confirmation, all on the same call. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged RingCentral plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for RingCentral specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your RingCentral call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running RingCentral have already done it. - A native RingCentral integration is available as a paid project. If you would rather not build the bridge yourself, or you want a Shuttle app in the RingCentral App Gallery or a deeper RingCX build, we can scope that with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire call, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native RingCentral integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in RingCX or RingEX. You'll need to be a Twilio customer and to build a small bridge connecting your workflow to Twilio, which customers running RingCentral have already done. We can build a native RingCentral integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### Will Shuttle work with both RingCX and RingEX? Yes. The Twilio-based capture works wherever your voice calls are handled, so it applies to both RingCentral's contact centre (RingCX) and unified communications (RingEX) products. You build a small bridge to fit whichever you run. ### Does Shuttle affect RingSense analytics? No, and this is a key benefit. Because the card is captured in the secure Twilio Pay call, no card data enters RingCentral, so RingSense continues to transcribe and analyse calls normally. The only difference is that card data is absent from transcriptions and recordings, which is exactly what PCI compliance requires. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### What is the pricing model? $0.20 per successful transaction for voice. No setup fees, no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres: the complete guide to secure contact centre payments - Twilio Pay Connectors: how Shuttle integrates with Twilio's payment infrastructure - Voice Payments: the definitive guide to taking payments over voice channels - AI Voice Agent PCI Payments: adding payment capture to AI-powered voice agents - Voice Checkout: Shuttle's voice payment product - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents ## Get Started Shuttle adds PCI-compliant payments to a RingCentral-based operation via Twilio, with multi-PSP routing and no gateway lock-in, and works with your existing PSP relationships. We'll walk you through what's live today and the path for your setup. Talk to our team about adding secure payment capture to RingCentral, or explore Voice Checkout to see how it works. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [40+ PSPs](/payment-providers/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Checkout](/platforms/voice-checkout/) - [Retell AI Payments](/guides/retell-ai-payments/) - [Talk to our team](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/ringcx-payments/ --- # How to Take Payments on RingCX: Enterprise CCaaS Payment Integration | Shuttle > If you're running an enterprise contact centre on RingCX, RingCentral's dedicated CCaaS product, for an insurance carrier, a debt-recovery operation, a... # How to Take Payments on RingCX: Enterprise CCaaS Payment Integration By Shuttle Team, April 17, 2026 If you're running an enterprise contact centre on RingCX, RingCentral's dedicated CCaaS product, for an insurance carrier, a debt-recovery operation, a multi-state utility, a travel and events business, or a multi-tenant BPO, you've already met the payment gap. Customers want to pay on the call. RingCX doesn't have a native, PCI-compliant way to capture their card. RingCX sits separately from RingEX, RingCentral's UCaaS product. RingCX targets enterprise contact centre operations, outbound campaigns, predictive dialling, AI-driven agent assist, workforce engagement, omnichannel routing. RingSense AI handles transcription and analytics across the platform. But the moment a 16-digit card number needs to be captured, the existing options are limited: agents reading numbers into recordings, redirecting to separate IVRs, or single-PSP partnerships that lock you to one acquirer. This guide is for merchants taking payments through RingCX, and for solution providers and RingCentral App Gallery partners deploying RingCX for clients. It covers how Shuttle adds PCI-compliant payment capture to RingCX, multi-PSP, RingSense-compatible, and built so payment moments fit into outbound and inbound flows alike. For the broader RingCentral platform (RingEX + RingCX combined), see the RingCentral Payments guide. ## The Payment Gap in RingCX RingCX is built for enterprise contact centre operations. Payment capture is a separate problem, and the gaps for businesses taking payments on the platform: - No native payment processing. RingCX has no built-in mechanism to trigger a card transaction inside an agent script, outbound campaign, or inbound flow. Card capture has to come from an external integration. - No DTMF isolation built in. RingCX supports recording controls, but pause-and-resume is a manual workaround, not secure DTMF masking. The agent still hears the card number, and any drift drags recordings into PCI scope. - Single-gateway add-ons. Available payment integrations are typically tied to one acquirer, fine for businesses on a single PSP, painful for enterprise contact centres that operate across multiple geographies, brands, or BPO clients. - No AI-to-payment handoff. RingSense AI transcribes and analyses calls in real time. It surfaces sentiment and coaching cues. It cannot execute a card transaction. - Per-seat licensing layered on top. RingCX pricing is seat-based. Payment add-ons that price per seat compound the cost across an enterprise deployment. A per-transaction model fits the underlying economics far better. ## How Shuttle Adds Payments to RingCX Shuttle adds PCI-compliant card capture to your RingCX payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your RingCX recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for RingCX specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your RingCX call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running RingCX have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When the agent (or an outbound campaign) is ready to take payment, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment. Neither the agent nor RingCX recordings receive cardholder data, and RingSense transcription continues around the payment moment. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links via SMS or email This is the most turnkey path. Shuttle generates a payment link with the agreed amount, currency, and reference. The agent drops the link into an SMS or email, including mid-call while the customer is still on the line. The customer pays on a hosted, PCI-compliant page, and status posts back to the agent's screen. Useful for outbound recovery campaigns where the caller agrees to pay later, or where a follow-up payment plan is agreed, and links work even with gateways that don't support voice capture. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for RingCX, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running RingCX have already built this. There is more in the "What to Expect" section below. ## How a voice payment works Shuttle connects to RingCX via the Twilio Pay capture, an agent-side UI you build, and webhooks for status reporting back into your CRM, case management, or campaign tools. ### Agent workflow From the RingCX agent desktop, the agent stays on the live call. When the caller is ready to pay, whether on an inbound enquiry or an outbound recovery call, the agent triggers the capture from your interface and confirms the amount. They never see, type, or hear the card number. The card is captured in the secure Twilio Pay call, so nothing reaches the agent's audio or the RingCX recording. The agent sees status updates (entered card, validated, processed, approved or declined) without ever entering PCI scope. If the call drops mid-payment, the agent can send a payment link to finish the transaction asynchronously. ### Customer experience When prompted, the customer enters their card details on their phone keypad during the secure Twilio Pay call, and the digits are captured inside Shuttle's certified environment. They hear confirmation in real time. RingSense AI assist remains active around the payment flow. ## Multi-PSP Support Shuttle is gateway-agnostic. We connect to 40+ PSPs, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Authorize.Net, GlobalPayments, FreedomPay, FIS, Elavon, Fiserv, and most regional acquirers. You can route transactions based on currency, region, card type, merchant entity, brand, or campaign, useful for enterprise RingCX deployments that span multiple business units, geographies, or BPO client portfolios. Switching processors later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This matters for RingCX customers who already have established acquirer relationships, who run multi-tenant BPO models, or who serve international markets where one PSP doesn't cover every country. Pricing is transparent and volume-based, see Shuttle pricing for the per-transaction model and what you pay across multiple PSPs. ## PCI Compliance Shuttle is PCI DSS Level 1 certified. Because the card is captured in the secure Twilio Pay call, the model keeps cardholder data out of your RingCX environment entirely: - Card data never reaches the agent's audio, RingCX recordings, or RingSense transcripts. - Card data is captured directly into Shuttle's certified environment, then tokenised before any return to your systems. - RingCX recordings, RingSense transcripts, and quality monitoring outputs never contain card numbers, keeping you on the lighter SAQ-A path. - Audit trails, settlement reports, and reconciliation are available via Shuttle's reporting layer and feed into RingCX-adjacent reporting tools. For RingCX customers in regulated verticals, financial services, insurance, healthcare, public sector, telco, Shuttle is designed to keep certified scope tight without compromising the AI-driven agent experience. Full compliance documentation, including the AOC scope, is in the security docs. Voice payments cost $0.20 per successful transaction with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## For Solution Providers and RingCentral App Gallery Partners If you're a RingCentral App Gallery partner or SI deploying RingCX for clients, Shuttle is the payment layer you can build into your deployment. We support white-label deployment, multi-PSP routing across your client portfolio (each client keeps their preferred acquirer), and partner-friendly commercials. Shuttle is a Pay Connector provider on the Twilio Marketplace, and the Twilio Pay capture works on both inbound and outbound RingCX flows without disrupting RingSense AI assist. A native RingCX or App Gallery integration can be scoped as a paid project. For partnership conversations, book a discovery call. ## Use Cases ### Outbound Collections and Recovery RingCX is widely used for outbound debt-recovery campaigns. Shuttle lets agents take payment plans during the recovery call itself, far higher conversion than asking the customer to action a link separately. Multi-PSP routing handles different agency-of-record arrangements across portfolios. ### Insurance Premium and Renewal Collection Insurance carriers using RingCX for premium collection, both inbound enquiries and outbound renewal nudges, can settle the payment moment inside the call. Useful for monthly premium chases and lapsed-policy reactivation. ### Multi-Tenant BPO Operations BPOs running RingCX across multiple end-clients can route payment transactions to each client's preferred acquirer, keeping settlement cleanly separated. Shuttle supports per-tenant configuration without per-seat licensing penalties. ### Utility and Telco Billing Utilities and telcos using RingCX for billing enquiries can complete card payments inside the call rather than transferring customers to web portals, faster handle time, higher conversion, narrower PCI scope. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged RingCX plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for RingCX specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your RingCX call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running RingCX have already done it. - A native RingCX integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native RingCX integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in RingCX. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running RingCX have already done. We can build a native RingCX or App Gallery integration as a paid project, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. The carrier-agnostic version that removes this requirement is on our roadmap. ### How is taking payments on RingCX different from RingCentral overall? RingCX is RingCentral's dedicated enterprise CCaaS, separate from RingEX (UCaaS). The Twilio Pay approach works on both, but RingCX deployments typically need outbound campaign support, multi-tenant routing, and tighter coexistence with RingSense AI than RingEX setups. For RingEX-only deployments, see the RingCentral Payments guide. ### Does Shuttle affect RingSense analytics? No. RingSense AI continues transcribing and analysing throughout the call. Because the card is captured in the secure Twilio Pay call, RingSense transcripts and analytics never contain card numbers, but the conversation context around the payment moment is preserved. ### Will Shuttle work with outbound predictive dialling campaigns? Yes. The Twilio Pay capture and payment links both work on inbound and outbound flows. For outbound recovery campaigns, agents can take payment during the call, with payment links as a fallback for customers who can't enter card details on the phone. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture. ### What is the pricing model? $0.20 per successful transaction for voice, with no setup fees and no per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the platform-by-platform merchant + SI guide - RingCentral Payments, broader RingEX + RingCX coverage - Twilio Pay Connectors, Shuttle's multi-gateway Pay Connector - Voice Payments, comprehensive voice payment capture guide - AI Voice Agent PCI Payments, for AI-led contact centres - Five9 Payments, enterprise CCaaS comparison - Genesys Payments, enterprise CCaaS comparison ## Get Started Shuttle adds enterprise-grade, PCI-compliant payments to a RingCX-based operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. If you take payments in a contact centre, see how Shuttle works for merchants, or book a discovery call to walk through your specific deployment. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [RingCentral Payments guide](/guides/ringcentral-payments/) - [DTMF masking](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment link](/guides/take-payments-online/payment-links/) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [40+ PSPs](/payment-providers/) - [Shuttle pricing](/pricing/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [$0.20 per successful transaction](/pricing/) - [a Pay Connector provider on the Twilio Marketplace](/guides/twilio-pay-connectors/) - [book a discovery call](/contact/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [RingCentral Payments](/guides/ringcentral-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Five9 Payments](/guides/five9-payments/) - [Genesys Payments](/guides/genesys-payments/) - [Shuttle works for merchants](/merchants/payment-services/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/salesforce-service-cloud-payments/ --- # How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments | Shuttle > Salesforce Service Cloud runs your support operation, and Service Cloud Voice (SCV) brings telephony into the same agent console, whether through Amazon... # How to Take Payments in Salesforce Service Cloud: PCI-Compliant Contact Centre Payments By Shuttle Team, May 14, 2026 Salesforce Service Cloud runs your support operation, and Service Cloud Voice (SCV) brings telephony into the same agent console, whether through Amazon Connect or Service Cloud Voice for Partner Telephony with providers like Five9, Genesys, Cisco, Avaya, Vonage, RingCentral RingCX, or Talkdesk. Your agents handle calls, chat, messaging, and email from one screen, with full case context from the CRM. What they cannot do natively is take a card payment inside that conversation. This trips up a lot of teams, because Salesforce does sell a product called Salesforce Payments. The important detail: Salesforce Payments is built for Commerce Cloud and Order Management web checkout, not for agent-assisted payments on a phone or chat session in Service Cloud Voice. It is commerce checkout, not contact centre payments. This guide is written for two audiences: merchants running Service Cloud or SCV who need to collect card payments during agent conversations, and the System Integrators and Salesforce Consulting Partners implementing those contact centres. If you are trying to close the in-call payment gap, this is for you. ## Salesforce Payments vs Contact Centre Payments It is worth being precise here, because the naming overlap causes real confusion during scoping. Salesforce Payments is a genuine product. It powers checkout for B2B and B2C Commerce storefronts and ties into Order Management, so a customer buying through your commerce site can pay with a saved card, digital wallet, or similar. That is a web-commerce flow. A Service Cloud Voice conversation is a different surface entirely. When a customer calls your support line, or messages your team, and wants to pay a bill, settle an overdue balance, or place an order over the phone, there is no native Salesforce capability to capture and process that card securely inside the call. Salesforce Payments does not extend into the agent console for this. The platform is PCI DSS certified as a service provider under a shared-responsibility model, but it provides no compliant in-call card-capture mechanism. To collect payments in the contact centre, merchants add a third-party AppExchange app or a PCI descope vendor. ## The Payment Challenge in Service Cloud Voice The core problem is that card data cannot be allowed to enter your voice stack, your call recordings, or your CRM. The moment a customer reads a card number aloud and an agent hears it, types it, or it lands in a recording, that telephony platform, the SCV layer, and Salesforce itself fall into PCI DSS scope. For an enterprise on Service Cloud, that scope can be enormous. Doing this yourself is not realistic for most teams. Building and maintaining a PCI DSS Level 1 environment with the right network segmentation, tokenisation, and audited controls typically runs $500k+ to stand up and $200k+ a year to maintain. And Salesforce gives you no native in-call capture to build on, so you would be assembling the entire payment path from scratch. The goal is to keep card data out of the conversation altogether while still letting the agent stay on the line and guide the customer through payment. ## How Shuttle Adds Payments to Salesforce Service Cloud Shuttle adds PCI-compliant card capture to your Salesforce Service Cloud payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Salesforce Service Cloud recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Salesforce Service Cloud specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Salesforce Service Cloud call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Salesforce Service Cloud have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ## How It Works ### Agent workflow The agent stays on the call the entire time. When it is time to pay, they trigger the secure Twilio Pay capture from your workflow. The customer keys in their card, and the agent sees only masked progress indicators and the final outcome. There is no transfer to a separate payment line, and the agent confirms the result and logs it against the case. ### Customer experience The customer never has to repeat card details aloud or worry about who is listening. They simply type their card number, expiry, and security code on their phone keypad while still talking to the agent. They get an immediate confirmation. ## Multi-PSP Support Shuttle is gateway-neutral, so you keep your existing acquiring relationships and processing economics. - Connect to 30+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. - Route per client, per business unit, or per region, which matters for enterprises running multiple brands or subsidiaries through one Service Cloud instance. - Keep your current pricing and settlement arrangements with each acquirer. - Switch gateways without re-engineering the payment flow; it is configuration, not a re-integration. One caveat for voice specifically: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider, the highest assurance level. Because card data is captured and processed entirely inside Shuttle's environment and never enters your Salesforce, telephony, or recording systems, those systems stay out of scope. This is a shared-responsibility model done properly. Instead of carrying the burden of a full SAQ-D assessment across your contact centre, descoping the conversation can reduce your obligation toward SAQ-A. Your auditors will still confirm the boundaries, but the surface they have to assess shrinks dramatically. ## Beyond Voice: Payment Links Not every payment happens on a live call. For chat, messaging, and email cases inside Service Cloud, agents can send a hosted payment link the customer opens and pays through securely. The same gateway routing and PCI posture apply, so whether the conversation is voice or digital, the card data stays off your stack and the case stays current in Salesforce. ## For Solution Providers and Salesforce Implementation Partners If you implement Service Cloud and SCV for clients, the in-call payment gap is a recurring requirement you can solve cleanly. Shuttle's voice capture runs on Twilio Pay, so the client needs to be a Twilio customer, and the agent-side interface is built against Shuttle's APIs as part of your delivery. There is no pre-built Service Cloud widget today, though we can build a native Service Cloud integration as a paid project for a specific deployment. For Consulting Partners delivering implementations, Shuttle is the payment layer you add to the SCV build: you handle the contact-centre design and CRM configuration, and Shuttle handles compliant card capture and gateway routing. That keeps PCI scope out of the environment you are delivering, which is an easier story to take to enterprise procurement and security review. ## Use Cases ### Bill-Pay and Account Payments Customers calling about an invoice or account balance can settle on the spot, with the payment logged against the case in Service Cloud. ### Collections and Payment Plans Collections agents can take a one-off payment or set up a payment plan mid-call, without card data touching the recording or the CRM. ### Order Taking Phone and chat orders convert immediately, with the agent confirming the transaction before the customer hangs up. ### Subscriptions and Renewals Capture a card for a renewal or recurring plan during a service conversation, routed to your preferred gateway. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Salesforce Service Cloud plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Salesforce Service Cloud specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Salesforce Service Cloud call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Salesforce Service Cloud have already done it. - A native Salesforce Service Cloud integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## FAQ Does Salesforce Service Cloud take payments? Not natively in the contact-centre conversation. Service Cloud and Service Cloud Voice have no built-in way to capture and process a card during a call or chat. Merchants add a PCI descope provider like Shuttle. Does Shuttle have a native Service Cloud integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Salesforce. For voice you'll need to be a Twilio customer and to build the agent-side trigger for your workflow against Shuttle's APIs. Payment links require no Twilio relationship. We can build a native Service Cloud integration as a paid project, and a carrier-agnostic version is on our roadmap. Does this require Twilio? For voice capture, yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Isn't Salesforce Payments enough? No. Salesforce Payments is scoped to Commerce Cloud and Order Management web checkout. It does not provide agent-assisted, in-call card capture in Service Cloud Voice. It is commerce checkout, not contact centre payments. Which payment gateways does Shuttle support? Shuttle connects to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square, with per-client and per-business-unit routing. Switching is configuration, not a re-integration. Can we just build PCI-compliant capture ourselves? You can, but standing up a PCI DSS Level 1 environment typically costs $500k+ upfront and $200k+ a year to maintain, and Salesforce gives you no native in-call capture to build on. Most teams use a certified provider instead. ## Related Reading - Contact centre payments: the hub guide covering PCI-compliant payments across every contact-centre platform. - Embedded payments for CCaaS: how payment capture embeds into cloud contact-centre stacks. - Genesys payments: taking payments when Genesys is your SCV partner telephony. - Amazon Connect payments: in-call capture when Service Cloud Voice runs on Amazon Connect. - Payments for CCaaS implementation partners: how SIs add the payment layer to contact-centre builds. ## Take Payments in Your Service Cloud Contact Centre Shuttle adds PCI-compliant payment capture to Salesforce Service Cloud Voice across 30+ gateways, at $0.20 per transaction with no setup or per-seat fees. Keep card data off your Salesforce, telephony, and recording stack while your agents stay on the call. See Payment Services | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### Why Most Call Answering Services Can't Take Payments ### Account Updater Service: How It Works for Card Payments ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ## Links - [PCI DSS](/glossary/pci-dss/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [30+ payment gateways](/payment-providers/) - [Level 1](/glossary/pci-dss/) - [scope](/glossary/pci-scope/) - [payment link](/merchants/payment-services/) - [30+ gateways](/payment-providers/) - [Contact centre payments](/guides/contact-centre-payments/) - [Embedded payments for CCaaS](/guides/embedded-payments-for-ccaas/) - [Genesys payments](/guides/genesys-payments/) - [Amazon Connect payments](/guides/amazon-connect-payments/) - [Payments for CCaaS implementation partners](/guides/payments-for-ccaas-implementation-partners/) - [$0.20 per transaction](/pricing/) - [See Payment Services](/merchants/payment-services/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogWhy Most Call Answering Services Can't Take Payments→](/blog/call-answering-service-payments/) - [BlogAccount Updater Service: How It Works for Card Payments→](/blog/should-i-use-account-updater-services-for-card-payments/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) --- URL: https://www.shuttleglobal.com/guides/secure-payment-collection-debt-agencies/ --- # Secure Payment Collection for Debt Agencies | Shuttle > Three Scenarios, One Compliance Problem Debt collection agencies collect payments through three distinct scenarios -- and each one creates a PCI challenge. # Secure Payment Collection for Debt Agencies By Shuttle Team, February 25, 2026 ## Three Scenarios, One Compliance Problem Debt collection agencies collect payments through three distinct scenarios -- and each one creates a PCI challenge. Scenario 1: Inbound debtor calls. A debtor calls to settle an account. The agent verifies the balance, negotiates a payment (full or partial), and needs to capture card details immediately -- while the debtor is motivated and ready to pay. Any friction -- "we'll send you a link" or "call back on our payment line" -- risks losing the payment entirely. Scenario 2: Outbound agent calls. An agent calls a debtor as part of a collections campaign. After navigating the conversation -- often sensitive, sometimes confrontational -- the debtor agrees to pay. The agent needs to capture payment in that moment. Transferring to an IVR or ending the call to send a link breaks the momentum and drastically reduces conversion. Where the payer would rather not speak to an agent at all, an automated self-pay line collects the same payment: see IVR Payments. Scenario 3: Automated payment plans. A debtor agrees to a structured payment plan -- £200/month for 12 months. The first payment is captured live. Subsequent payments need to be collected automatically, on schedule, without the debtor calling back each month. In all three scenarios, the traditional approach -- agent verbally collects card details -- puts the agency in full PCI scope. Call recordings contain card data. Agent workstations are in scope. The entire telephony environment needs to meet PCI DSS requirements. For an industry already operating on thin margins with high staff turnover and intense regulatory scrutiny, that compliance burden is unsustainable. ## Why Debt Collection Is Different Debt collection has requirements that generic contact centre payment solutions don't address: ### Multi-PSP Is Mandatory Agencies collect on behalf of creditors. Creditor A mandates Worldpay. Creditor B uses Stripe. Creditor C has a Barclays merchant account. Creditor D's contract specifies the exact processor their payments must route through. Outsourced parking, civil enforcement and toll operators face the same multi-client PSP-mandate problem -- see Payment Collection for Parking, Enforcement and Toll Operators. This isn't optional. Creditors dictate the PSP. The agency must comply. A payment solution that only connects to one or two gateways can serve one client -- but not a portfolio. This is the same multi-PSP mandate problem that platforms face, but amplified: a single debt collection agency may serve dozens of creditors, each with different payment processing requirements. ### Compliance Is Under a Microscope Debt collection is one of the most heavily regulated sectors. FCA oversight in the UK, CFPB in the US, and sector-specific codes of practice all impose strict requirements on how debtor data is handled. PCI DSS v4.0.1 added further pressure: - Shared responsibility -- creditors can't fully transfer PCI liability by outsourcing collections. They must monitor and verify their agencies' compliance posture. - Enhanced third-party monitoring -- agencies must demonstrate PCI compliance to every creditor they serve. - Targeted risk analysis -- every payment handling procedure requires documented risk assessment. An agency using pause-and-resume or verbal card capture faces increasing pushback from creditors whose own compliance teams are asking pointed questions. ### Staff Turnover Amplifies Risk Debt collection agencies have some of the highest staff turnover rates in the contact centre industry. High-pressure work, emotional conversations, and shift-based schedules drive churn. Every agent who hears a card number is a potential fraud vector. An agent who leaves after three months may have processed hundreds of payments. If they've heard card details on every one, the agency's exposure to insider fraud is significant. The secure approach: agents never hear card data. Period. ### Payment Plans Require Tokenisation A one-off payment capture is straightforward. But debt collection lives on payment plans -- recurring payments over weeks, months, or years. This requires: - Tokenisation of the card at first capture - Secure storage of the token linked to the debtor's account - Scheduled execution of subsequent payments via the creditor's PSP - Automatic retry logic for failed payments - Notification to the agency (and debtor) of payment status A DTMF solution that captures a one-off payment but can't tokenise and schedule recurring payments only solves half the problem. ## The Architecture That Works ### For Inbound and Outbound Calls When a debtor agrees to pay during a live call: - The agent triggers payment capture from their interface -- the system identifies the creditor and their configured PSP - A DTMF capture session initiates within a PCI DSS Level 1 certified payment layer - The debtor enters their card details via keypad -- tones are masked from the agent and stripped from the call recording - The payment layer processes the transaction through the creditor's PSP - The agent sees: "Payment of £350.00 approved -- Ref TXN-8294 -- Card ending 5531" - The call continues -- the agent confirms the payment verbally and discusses next steps No card data enters the agency's environment. The recording is clean. The agent never heard the card number. If the debtor can't use their keypad -- older handset, VoIP call, or simply prefers not to -- the agent sends an SMS payment link with one click. The debtor completes payment on their device while the conversation continues. The link carries the creditor's branding and supports cards, digital wallets, and bank transfers. ### For Payment Plans When a debtor agrees to a payment plan: - First payment is captured live via DTMF or payment link (as above) - The card is tokenised within the payment layer -- no card data stored by the agency - Subsequent payments are scheduled against the token, routed through the creditor's PSP - Each payment executes automatically on the agreed date - Failed payments trigger retry logic and notification to the agency - The debtor receives payment confirmation for each instalment The agency manages the plan -- adjusting amounts, pausing, or cancelling -- through a dashboard. Card data never reaches the agency: it is captured inside the payment layer's certified environment and tokenised with the agency's own gateway. The agency's systems hold only tokens, references, and payment status. ### For AI-Driven Collections AI voice agents are entering debt collection -- handling outbound calls at scale, navigating sensitive conversations, and identifying payment opportunities. When a debtor agrees to pay during an AI-managed call, the same architecture applies: - AI agent identifies payment intent - API call triggers DTMF capture session - Debtor enters card details via keypad - Payment confirmation returns to the AI agent via webhook - AI agent confirms payment and continues the conversation No human agent involved. Fully automated. The same multi-PSP routing, tokenisation, and payment plan capabilities apply. For the full AI agent architecture, see How AI Voice Agents Take PCI-Compliant Payments. ## Cost Comparison PCI scope | Full SAQ-D | SAQ-A | SAQ-A Annual PCI cost | $200K-$500K+ | Included in vendor fee | Included Multi-PSP | Manual (log into each portal) | 1-3 gateways | 40+ gateways Payment plans | Manual recurring | Limited | Automated with tokenisation Per 100-seat agency | PCI cost + fraud risk | ~$2,500-$4,000/mo (per-seat) | ~$1,000-$3,000/mo (per-transaction) Channels | Voice only (non-compliant) | Voice only | Voice + links + chat AI agent support | No | Limited | Yes White-label | N/A | Limited | Full ## What Creditors Are Asking Creditors are tightening their oversight of agency payment practices. Expect these questions in your next creditor review: - "Are your agents exposed to cardholder data during collections calls?" - "What PCI SAQ level does your payment process qualify for?" - "Can you produce an Attestation of Compliance (AOC) for your payment handling?" - "How do you ensure our payments route through our mandated PSP?" - "What fraud controls exist around agent access to payment data?" Agencies using a PCI-certified payment layer with DTMF isolation can answer all five cleanly. Agencies using pause-and-resume or verbal capture will struggle -- and increasingly, creditors are making compliant payment handling a condition of their agency agreements. ## FAQ Can we process payments for multiple creditors through one system? Yes. A multi-PSP payment layer lets you configure each creditor's PSP and merchant account. When an agent (or AI agent) triggers a payment, the system routes it through the correct creditor's processor automatically. How do payment plans work with different creditor PSPs? The first payment is captured and tokenised. Subsequent payments execute against the token through the creditor's configured PSP. Each creditor's payment plans route through their own gateway -- the agency manages plans through a unified dashboard regardless of the underlying PSP. What about partial payments and settlements? The system handles arbitrary amounts. If a debtor negotiates a partial payment or a settlement figure, the agent enters the agreed amount and processes it. Payment plan amounts can be adjusted mid-plan. Does this work with our existing dialler/CRM? The payment layer integrates via API with your existing infrastructure -- Avaya, Genesys, Five9, Twilio, or any SIP-based telephony. CRM integration is typically via webhooks that update debtor records with payment status. What about Continuous Payment Authority (CPA)? CPA (recurring card payments where the agency initiates the charge) requires tokenisation and explicit debtor consent. The payment layer handles tokenisation at first capture and stores consent alongside the token. Subsequent CPA charges are initiated by the agency through the API, processed through the creditor's PSP. How does this compare to the existing AI voice debt collection guide? Our guide on AI voice agent PCI payments focuses on the AI agent and CCaaS platform angle -- how AI voice providers build payment capture into their agents. This guide focuses on the agency operator: you're running a collections business, human or AI agents, and need compliant multi-creditor payment infrastructure. ## Related Reading - Take Payments on Behalf of Your Clients - the multi-merchant-account problem across every servicer vertical - PCI-Compliant Payments for Contact Centres -- the complete guide to secure contact centre payment approaches - Payment Collection for BPOs -- the multi-client, multi-PSP problem for outsourcers - Why Most Call Answering Services Can't Take Payments -- the payment gap in the call answering market - How AI Voice Agents Take PCI-Compliant Payments -- the technical AI agent payment architecture - Enterprise PSP Mandates -- why creditors mandate their own PSP Collect every payment. Comply with every creditor. Limited PCI scope. Shuttle gives debt collection agencies multi-PSP payment collection through a single integration. DTMF voice capture, SMS payment links, automated payment plans -- with white-label branding and PCI DSS Level 1 compliance included. Book a Demo | See Voice Checkout ## Start collecting payments faster Send branded payment links by email or SMS, track them in real time, and connect the payment providers you already work with. Explore More ### QuickBooks Payment Collection: Add Pay Now Links to Every Invoice ### Secure Payment Links: Card Authorization Made Simple ### What Is Local Acquiring? How It Cuts International Payment Costs ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Payment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections ### Payment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections ## Links - [IVR Payments](/guides/ivr-payments/) - [Payment Collection for Parking, Enforcement and Toll Operators](/guides/parking-enforcement-toll-payments/) - [multi-PSP mandate problem](/guides/enterprise-psp-mandates/) - [DTMF](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [payment link](/guides/take-payments-online/payment-links/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [AI voice agent PCI payments](/guides/ai-voice-agent-pci-payments/) - [Take Payments on Behalf of Your Clients](/guides/take-payments-on-behalf-of-clients/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Payment Collection for BPOs](/guides/payment-collection-for-bpos/) - [Why Most Call Answering Services Can't Take Payments](/blog/call-answering-service-payments/) - [Enterprise PSP Mandates](/guides/enterprise-psp-mandates/) - [Book a Demo](/discovery/) - [See Voice Checkout](/platforms/voice-checkout/) - [See Links Checkout](/merchants/links-checkout/) - [BlogQuickBooks Payment Collection: Add Pay Now Links to Every Invoice→](/blog/quickbooks-payment-collection/) - [BlogSecure Payment Links: Card Authorization Made Simple→](/blog/secure-and-streamlined-the-benefits-of-using-payment-links-for-card-authorization/) - [BlogWhat Is Local Acquiring? How It Cuts International Payment Costs→](/blog/local-acquiring-the-secret-to-streamlining-international-payment-collection/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogPayment Links for VEEM: Send Branded Checkout Links For Faster B2B Card Collections→](/blog/payment-links-for-veem/) - [BlogPayment Links for Ecommpay: Send Branded Checkout Links For European Merchant Collections→](/blog/payment-links-for-ecommpay/) --- URL: https://www.shuttleglobal.com/guides/shift4-twilio-integration/ --- # How to Connect Shift4 to Twilio for Voice & IVR Payments | Shuttle > Shift4 doesn't natively connect to Twilio for voice payments. If you want to process Shift4 transactions during a phone call (via IVR, agent-assisted, or... # How to Connect Shift4 to Twilio for Voice & IVR Payments By Shuttle Team, June 9, 2026 Shift4 doesn't natively connect to Twilio for voice payments. If you want to process Shift4 transactions during a phone call (via IVR, agent-assisted, or AI voice agent) you need a Twilio Pay Connector that bridges the two platforms. Shuttle's Pay Connector does exactly this. It connects Shift4 (and 30+ other gateways) to Twilio's verb, so you can accept PCI-compliant card payments during any voice interaction. For hospitality groups, hotel chains, and restaurant brands already running Shift4 at the point of sale, this closes an obvious gap: the phone. Reservation deposits, central booking lines, group bookings, and pre-authorisations can all run through the same Shift4 account that powers your in-person payments. This guide walks through how the integration works, how to set it up, and what to watch for. ## Why Shift4 + Twilio Don't Connect Directly Shift4 is a US payments company built for end-to-end processing in the experience economy. Its technology powers a large share of table-service restaurants and hotels in the United States, along with stadiums, casinos, and entertainment venues. The stack runs from POS software through to acquiring, with card data tokenised inside Shift4's environment. Twilio is built for voice and messaging. Its verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them. The problem: Twilio's needs a Pay Connector to route captured card data to a payment gateway. Shift4 isn't one of Twilio's built-in connectors, so there's no native path between the two platforms. This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's verb and routes it to Shift4's API for processing. One integration connects the two platforms. ## How It Works - Caller reaches payment step. Your Twilio call flow (IVR, Studio, or custom TwiML) triggers the verb. For a hotel booking line, that might be the moment a reservation deposit is due. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Shift4. The connector creates a payment request against your Shift4 account, processes the transaction, and handles the response. - Result returned to your call flow. Your webhook receives the transaction reference, last four digits, card brand, and status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Shift4 account with API credentials (Shift4 issues a secret API key, with separate test-mode and live-mode key pairs) - A Shuttle account (free to create: you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Shift4 Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Shift4 - API key: Your Shift4 secret key - Currency: Set your default (USD, GBP, EUR, etc.) - Environment: Live or Test Save the profile. Shuttle now has a live connection to your Shift4 account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - : the amount to charge - : ISO currency code - : your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the transaction in Shift4 if needed. Update your booking or order, confirm to the caller, and continue the flow. ### Step 5: Test Use Shift4's test mode (with your test-mode API key in Shuttle) and Twilio's test credentials to verify the flow end-to-end before going live. Run at least one full call: capture, charge, webhook, confirmation. ## What You Can Do With Shift4 + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Shift4 processes, done. Ideal for taking a balance payment on a booking line or settling an invoice by phone. ### Authorise Now, Capture Later Place a hold on the card during the call and capture later. This suits hotels and venues especially well: take a pre-authorisation for a reservation or event deposit on the call, then capture at check-in or after the event. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Shift4 and returns a reusable token. Use it for future payments across any channel: web, mobile, voice, or payment links. A guest who books by phone can settle incidentals or repeat bookings later without reading their card out again, and the card data is never stored in your systems. ### Central Reservations Across Properties Hotel groups and restaurant brands often run a central booking line that takes payments on behalf of multiple properties. Shuttle's payment profiles let you route each transaction to the right Shift4 configuration, so the central team works one call flow while funds settle correctly per site. ## Multi-PSP: Beyond Shift4 One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway: keep your US merchants on Shift4 and put European properties on a local acquirer - Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.) - Want a backup gateway: if one gateway has an outage, you can move the affected payment types to another connected gateway - Expand to new markets where a different acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard, with minimum amount, maximum amount and currency filters. Your Twilio call flow doesn't change. The verb always points to , and Shuttle sends the payment to the provider you configured. This is particularly useful for platforms and BPOs that serve multiple merchants. Each merchant can use their own Shift4 account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Shift4 + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1 Service Provider) Payment processing Your systems No card data: SAQ-A Card data flows from Twilio to Shuttle to Shift4. Your application only receives redacted data (last four digits, card brand, transaction reference). You typically qualify for SAQ-A, the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Shift4 to Twilio without Shuttle? Twilio doesn't have a built-in Shift4 Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built, PCI-certified connector that handles this. Does this work alongside my Shift4 POS? Yes. The connector processes voice payments through your Shift4 account via its API. Your in-person POS setup is unaffected, and phone transactions appear in Shift4 reporting alongside the rest of your volume. Does this work with Twilio Studio? Yes. Configure the payment step with as the connector and the flow works within Studio. What about Shift4's test mode? Fully supported. Shift4 provides separate test-mode API keys. Add your test key to a Shuttle payment profile and run the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Shift4's processing fees apply on top per your agreement. No Shuttle setup fees or monthly minimums. Can I switch from Shift4 to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup - How to Connect FreedomPay to Twilio for Voice Payments: step-by-step FreedomPay + Twilio setup - AI Voice Payments for Hotels & Travel: automating booking and deposit payments with AI voice agents - Shift4 Payment Integration: everything Shuttle supports on Shift4 - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Connect Shift4 to Twilio in minutes with Shuttle's Pay Connector: PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### Payment Links for Shift4: Send Branded Checkout Links for Hospitality and Restaurant Payments ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Authorize.net QuickBooks Integration: Full Guide ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ## Links - [Twilio Pay Connector](/guides/twilio-pay-connectors/) - [30+ other gateways](/payment-providers/) - [DTMF](/guides/dtmf-payments/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Stripe to Twilio for Voice Payments](/guides/stripe-twilio-integration/) - [How to Connect FreedomPay to Twilio for Voice Payments](/guides/freedompay-twilio-integration/) - [AI Voice Payments for Hotels & Travel](/guides/ai-voice-payments-hotels-travel/) - [Shift4 Payment Integration](/payment-providers/shift4/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogPayment Links for Shift4: Send Branded Checkout Links for Hospitality and Restaurant Payments→](/blog/payment-links-for-shift4/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [BlogAuthorize.net QuickBooks Integration: Full Guide→](/blog/maximize-invoice-payments-in-quickbooks-with-authorize-net-integration/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) --- URL: https://www.shuttleglobal.com/guides/sierra-payments/ --- # Sierra AI Payments: Multi-PSP Payment Capture vs Native Payments | Shuttle > Sierra (sierra.ai) is an enterprise conversational AI platform, an "AI Agent OS" that powers customer service agents across both chat and voice. # Sierra AI Payments: Multi-PSP Payment Capture vs Native Payments By Shuttle Team, June 1, 2026 Sierra (sierra.ai) is an enterprise conversational AI platform, an "AI Agent OS" that powers customer service agents across both chat and voice. It is used by large enterprises like Rocket Mortgage, SoFi, and Gap to handle high-volume customer interactions with autonomous AI. Sierra is also one of the few conversational AI platforms with a genuine native payment capability. Sierra says it is the first Level 1 PCI-compliant conversational AI platform, and is listed on the Visa Global Service Provider Registry. Its agents can securely capture card data and route it to your existing payment processor, keeping the AI agent out of PCI scope. So unlike many AI voice and chat platforms, Sierra can take payments. This guide covers what Sierra's native payments give you, and when a dedicated multi-PSP payment layer like Shuttle is the better fit, whether alongside Sierra or in place of its native flow. If you run multiple gateways, operate under enterprise PSP mandates, or need one payment integration that works the same across every voice and chat agent you deploy, this is for you. ## Sierra's Native Payments: What You Get Sierra's payment capability is strong and worth taking seriously. The core pieces: - Level 1 PCI compliance. Sierra is the first conversational AI platform certified at PCI DSS Level 1 and listed on the Visa Global Service Provider Registry. That is the highest tier of PCI DSS validation. - PSP-neutral capture. Sierra securely captures card data and routes it to the merchant's existing payment processor or gateway. It does not lock you to a single PSP and does not force you onto a particular provider. - Voice and chat. Keypad (DTMF) capture handles payments over voice, and secure embedded forms handle payments in chat sessions. - Agent kept out of scope. The card data never enters the conversational model, which keeps the AI agent itself outside your cardholder data environment. - Flexible payment types. Sierra's flow supports one-off charges, payment plans, bill-pay, and ACH. For an enterprise standardised on Sierra for customer service, native payments inside the same platform is a clean, well-engineered option. The question is not whether Sierra can take payments. It is whether a single-platform payment flow fits how your payments actually need to work. ## When You Need a Dedicated Payment Layer Native payments are ideal when your stack is consolidated on one vendor. A dedicated payment layer like Shuttle earns its place when payments span more variables than a single platform is built to manage: - Multi-PSP breadth. You process across several gateways and want a single integration that reaches all of them, not a flow tied to one connected processor. - Bring your own gateway. You have negotiated rates or a specific acquirer relationship and want to keep it, with explicit BYO-gateway support. - Per-client and per-tenant routing. Agencies, BPOs, and contact centres run payments on behalf of many end clients, each with their own PSP. You need to route each tenant's transactions to that tenant's gateway. - Enterprise PSP mandates. Large organisations are often required to settle through a mandated processor (Worldpay, Adyen, a regional acquirer). A neutral layer routes to whatever the mandate requires. - Cross-platform consistency. You run Sierra plus other voice or chat agents, or you expect to change agent platforms over time. A dedicated layer keeps one payment integration that works the same regardless of the agent stack on top. If any of those describe you, a multi-PSP payment layer either complements Sierra or replaces its native flow, depending on how you want to own the payment relationship. ## How Shuttle Works With Sierra Today Be clear about the model first, because it determines whether Shuttle is a fit: - There is no native Sierra integration today. Shuttle's voice payment capture runs on Twilio Pay. You invoke that Twilio-based setup; you do not install a Shuttle app inside Sierra. - You need to be a Twilio customer to use voice capture with Shuttle. - You need technical resource to implement it. Shuttle ships ready-made interfaces for payment links and the PCI-compliant capture, IVR and APIs for voice, but you build the agent-side interface for your own Sierra workflow, because every agent stack is different. There is no pre-built Shuttle widget for Sierra. - A native Sierra integration is possible as a paid project. If you want a deeper, platform-specific build, Shuttle can deliver one at a project cost. - Carrier-agnostic is on the roadmap. Shuttle works with Twilio today, and any carrier coming soon. If you have the technical resource and are (or can be) a Twilio customer, the flow works like this: - The agent runs the conversation. Your Sierra agent handles the customer interaction exactly as it does today. - The agent triggers Shuttle at the payment moment. When it is time to collect payment, the agent hands off to Shuttle from the interface you build against Shuttle's APIs. - Shuttle captures the card in isolation. Over voice, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay: the customer keys their card in on the keypad and the digits are captured inside Shuttle's certified environment, so neither the agent nor any recording is exposed to raw card data. - Shuttle processes and routes to your gateway. Shuttle tokenises the card and routes the transaction to whichever of your connected gateways applies for that customer, currency, or client. - The result returns to the agent. Shuttle passes a clean success or failure result back so the agent can confirm the outcome. The agent never touches card data, and the payment logic lives in one place across every channel. One honest caveat: the secure capture at the point of payment is what's live now via Twilio Pay. Shuttle being present for the entire Sierra conversation is not yet turnkey. Returning the caller to the same agent and call after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes with context. Shuttle works with Twilio today, and any carrier coming soon. ## Multi-PSP Support Shuttle connects to 30+ payment gateways through one integration, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. That breadth is what makes per-client and mandate-driven payments practical: - Per-tenant gateway configuration. Map each client, brand, or business unit to its own gateway and credentials. - One integration, many processors. Add or switch gateways without re-integrating your agents. Switching gateways is configuration, not a re-integration. - Routing rules. Route transactions by currency, region, or card type to the right processor. - Failover. Fall back to a secondary gateway if a primary processor is unavailable. One voice caveat: a few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. ## PCI Compliance Shuttle is a PCI DSS Level 1 certified Service Provider. When Shuttle captures the card, the cardholder data flows through Shuttle's certified environment, not yours and not the agent's. That shrinks your PCI scope. Because raw card data never lands in your systems, most integrations qualify for the lighter SAQ-A assessment rather than the far heavier SAQ-D you would face if card data passed through your own infrastructure. Your agent platform, your CRM, and your call recordings stay outside the cardholder data environment. ## Beyond Voice: Payment Links Not every payment needs to complete in the live conversation. From the same Shuttle integration, an agent can send an SMS or email payment link that opens a hosted, PCI-compliant checkout page, including mid-call to a caller still on the line. The customer pays on their own device, and the result still routes to your chosen gateway and reports back. Links are the most turnkey part of Shuttle and work even with gateways that don't support voice capture. This is useful when a caller prefers to pay later, needs to switch cards, or wants a written record of the transaction. ## Use Cases ### Outbound Sales An outbound Sierra agent closes a sale and collects payment in the same call, routing to the gateway tied to that product line or region. ### Bill-Pay and Collections Agents take bill payments and set up payment plans for overdue balances, with secure card capture and ACH support, ideal for BPOs collecting on behalf of multiple creditors. ### Bookings and Deposits Capture deposits to confirm appointments, reservations, or bookings, with the balance collected later via an SMS payment link. ### Customer Support Payments Support agents resolve an issue and take payment for an upgrade, renewal, or add-on without transferring the customer to a separate line. ## FAQ Does Sierra process payments natively? Yes. Sierra describes itself as the first Level 1 PCI-compliant conversational AI platform, and is listed on the Visa Global Service Provider Registry. It securely captures card data and routes it to your existing payment processor, keeping the agent out of PCI scope. Why use Shuttle if Sierra has native payments? Sierra's native flow is excellent for a consolidated single-vendor setup. Shuttle fits when you need breadth across 30+ gateways, explicit BYO-gateway support, per-client or per-tenant routing, or one payment integration that works the same across Sierra and any other agent platform you run. Does Shuttle have a native Sierra integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Sierra. You need to be a Twilio customer and to build the agent-side interface for your workflow. Shuttle can build a native Sierra integration as a paid project. Shuttle works with Twilio today, and any carrier coming soon. Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so voice capture needs you to be a Twilio customer. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon. Which payment gateways does Shuttle support? Shuttle connects to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie, through a single integration. Switching gateways is configuration, not a re-integration. A few gateways (for example Braintree) don't work for voice capture but do work for links. Can I build payment capture into my Sierra agents myself? You can, but building and maintaining a PCI Level 1 capture flow and multi-gateway routing is significant work. Shuttle gives you that as one integration so your team focuses on the agent experience, not payment compliance. Does this work for outbound calls? Yes. Shuttle captures payments on both inbound and outbound calls via the secure Twilio Pay capture, and can send SMS or email payment links when a caller prefers to pay on their own device. ## Related Reading - The Payment Layer for AI Agents: how a dedicated payment layer sits beneath any agent stack. - AI Voice Agent PCI Payments: keeping AI voice agents out of PCI scope. - Voice Payments: how secure payment capture works over voice channels. - Parloa Payments: adding payment capture to Parloa's AI agents. - ElevenLabs Payments: native Stripe payments versus a multi-PSP layer. ## Add Payments to Your Sierra Agents Shuttle gives a Sierra operation PCI Level 1 payment capture across 30+ gateways, on Twilio today, for $0.20 per successful transaction on voice with no setup or per-seat fees. Links Checkout is a separate app; see [pricing](/pricing/). See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [PCI DSS](/glossary/pci-dss/) - [DTMF](/guides/dtmf-payments/) - [PSP](/payment-providers/) - [30+ payment gateways](/payment-providers/) - [PCI scope](/glossary/pci-scope/) - [30+ gateways](/payment-providers/) - [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Voice Payments](/guides/voice-payments/) - [Parloa Payments](/guides/parloa-payments/) - [ElevenLabs Payments](/guides/elevenlabs-payments/) - [$0.20 per successful transaction](/pricing/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/single-psp-risk/ --- # What Happens When Your Only Payment Processor Cuts You Off | Shuttle > It Happens More Often Than You Think Stripe processes payments for over 3 million businesses. # What Happens When Your Only Payment Processor Cuts You Off By Shuttle Team, March 1, 2026 ## It Happens More Often Than You Think Stripe processes payments for over 3 million businesses. PayPal, Square, Adyen, Worldpay -- each serves hundreds of thousands more. Every one of them reserves the right to freeze or terminate your account at any time, for any reason, with minimal notice. And they do. The pattern is documented across hundreds of incidents on Hacker News, Reddit, and industry forums: - A platform using Stripe Connect since 2016 had 35% of its connected merchant accounts deactivated overnight -- no warning, no explanation, despite Stripe staff having previously approved the business model by phone. - A merchant had $400,000+ frozen during Cyber Monday after a volume spike triggered automated fraud detection. Resolution took months and only happened after the story went viral on Hacker News. - An AI platform was suspended after a single chargeback from users who accidentally purchased annual instead of monthly subscriptions. - A European SaaS platform had accounts suspended due to SEPA Direct Debit disputes that Stripe later admitted were being miscategorised by its own system. These aren't edge cases from questionable businesses. They're legitimate platforms, SaaS companies, and marketplaces that built their entire payment flow on a single provider -- and discovered what happens when that provider decides to pull the plug. ## The Mechanics of Account Termination ### How It Happens Payment processors -- especially aggregators like Stripe, Square, and PayPal -- follow a pattern that creates maximum vulnerability at the worst possible moment: They onboard first, underwrite later. Stripe's frictionless signup means you can start processing within hours. But the real risk assessment happens after you're live -- once transaction patterns, chargeback rates, and business model details become visible. As one payment industry veteran put it: "They approve you first, then scrutinise you when you start scaling." This means the risk of termination is highest when your business is growing fastest -- exactly when you can least afford it. ### Common Triggers Chargeback rate breaches. The most common technical trigger. Visa's Dispute Monitoring Programme activates at 0.9% or 100 chargebacks per month. Mastercard's threshold is 1.5%. But Stripe's internal limit is lower -- approximately 0.75%. At low transaction volumes, a handful of disputes can breach these percentages instantly. A SaaS with 50 monthly transactions needs only 1 dispute to hit 2%. Volume spikes. A sudden increase in processing volume -- seasonal surge, product launch, viral moment -- triggers automated fraud systems. The account freeze happens before any human reviews it. Your best sales month becomes the trigger for losing payment access. Industry reclassification. Stripe updates its prohibited and restricted business lists. A business approved under one policy version can find itself in a prohibited category when the policy changes, with no grandfather clause. CBD products, supplements, financial services, and AI companies have all experienced this. Business model changes. If your product evolves -- new features, new markets, new merchant types -- without notifying your processor, the new activity can look fraudulent relative to your original onboarding profile. Platform cascade. For Stripe Connect platforms, the risk multiplies. If your platform account is flagged, it doesn't just affect you -- it immediately affects every merchant processing through your platform. One risk flag propagates to your entire customer base. ## What Happens Next ### Immediate Impact All payment processing stops. Not gradually -- instantly. No ability to accept cards, process subscriptions, or complete transactions. For a SaaS company with monthly recurring revenue, every subscription renewal that hits during the outage fails. ### Fund Holds: 90-180 Days Stripe holds all processed funds in the account for a minimum of 90 days, typically 180 days, to cover potential chargebacks. Some merchants report holds extended beyond 180 days. For the platform that had $400,000 frozen, those funds were inaccessible for months -- during their highest-revenue period. ### The MATCH List: A Five-Year Problem If the account is terminated for reasons coded as fraud, excessive chargebacks, or compliance violations, the business principals can be added to the MATCH list (Member Alert to Control High-Risk Merchants), maintained by Mastercard. MATCH listing lasts five years. Banks and processors consult it before approving new merchant accounts. Being listed effectively blocks the business from mainstream payment processing for half a decade. The consequences extend beyond payments -- third-party vendors, billing platforms, and marketplaces often refuse to work with MATCH-listed businesses. Removal before five years is possible only in very narrow circumstances. ### Migration Difficulty Even if you find a new processor within days, the migration is painful: - Tokenised card data doesn't transfer. PSPs don't share tokens. Every customer has to re-enter their payment details -- causing immediate churn and failed subscriptions. - Integration takes weeks. Finding, applying for, and integrating a new PSP takes 2-8 weeks minimum. During the gap, you can't process payments. - Subscription continuity breaks. Failed renewals during the migration window mean lost customers who may never come back. Research from FreedomPay estimates that payment outages cost US businesses $44.4 billion annually in lost sales. Between minutes 8 and 13 of an outage, businesses lose approximately $1.2 billion per minute. But an account termination isn't a 13-minute outage -- it's days, weeks, or months. ## Who Is Most at Risk ### SaaS and Subscription Businesses Digital goods, recurring billing, and trial-to-paid conversion models generate higher chargeback rates than physical goods. A customer who forgets they signed up for a trial and disputes the charge is enough to move the needle. SaaS as a category is classified as elevated risk by most processors. ### Marketplace and Connect Platforms Aggregated risk from sub-merchants means the platform is responsible for the behaviour of every merchant on its system. One bad actor among hundreds can trigger a review of the entire platform account. ### High-Growth Companies The paradox: the faster you grow, the more likely you are to trigger automated risk systems. Volume spikes, geographic expansion, and new product launches all create patterns that fraud systems flag. Growth is the trigger. ### Adjacent-Category Businesses Companies selling products near a prohibited category boundary -- legal CBD cosmetics, financial education, health supplements -- operate in a grey zone where policy changes can reclassify them overnight. ## The Multi-PSP Insurance Policy The solution isn't to find a "better" processor. Every PSP carries the same structural risk -- they all reserve the right to terminate, they all use automated risk systems, and they all hold funds during disputes. The solution is to never depend on a single one. ### How Multi-PSP Architecture Works A PSP-neutral payment layer connects your platform to multiple payment processors through a single integration. Each merchant -- or each transaction -- can route through a different PSP. In normal operations, this provides: - PSP flexibility -- each merchant uses their preferred processor - Geographic optimisation -- each market on the provider you chose for it - Cost optimisation -- compare processing fees across providers - Better approval rates -- retry failed transactions on an alternative PSP In a crisis, it provides something more fundamental: survival. ### The Failover Scenario With two or more PSPs already approved and integrated: - PSP A flags your account → you move volume to PSP B - Transactions continue processing within minutes, not weeks - No customer-facing disruption -- subscriptions renew, checkouts work - You resolve the PSP A issue from a position of strength, not desperation Without multi-PSP: your business stops until you find, apply for, get approved by, and integrate a new processor. That's weeks at best. Months at worst. ### What This Looks Like in Practice You don't need to actively use five PSPs. Most platforms maintain: - A primary PSP handling the majority of transactions - One or two secondary PSPs approved and configured as backups - The ability to add new PSPs as configuration changes, not engineering projects The secondary PSPs don't cost anything when idle. They're insurance -- and the premium is the initial configuration time, not an ongoing fee. ## Beyond Failover: Why Multi-PSP Is Becoming Standard Account termination risk is the most dramatic reason for multi-PSP architecture, but it's not the only one. Enterprise customers mandate their PSP. The #1 reason platforms adopt multi-PSP is that enterprise clients won't switch processors for a software vendor. If you only support Stripe and a prospect requires Worldpay, you lose the deal. PSP consolidation creates new risks. When Worldpay acquires another processor or Stripe changes its fee structure, platforms locked into a single provider have no leverage. PSP consolidation is accelerating -- and single-PSP platforms are the most exposed. Regulators are watching. The debanking controversy of 2024-2025 brought regulatory attention to processor termination practices. The OCC confirmed that "all reviewed institutions had engaged in debanking activity." Multi-PSP architecture protects against regulatory shifts at any single provider. ## FAQ How quickly can I add a second PSP? With a payment layer, adding a new PSP is a configuration change -- typically hours to days. Without one, it's an engineering project -- weeks to months per PSP. Does multi-PSP mean higher costs? Not necessarily. A payment layer charges per transaction, but the comparison should include the engineering cost of building and maintaining PSP integrations, plus the risk cost of single-provider dependency. Most platforms find the total cost is lower. See the full build vs buy analysis. What about tokenised cards -- can I move them between PSPs? PSP-specific tokens only work with that PSP. A payment layer provides its own tokenisation -- tokens work across any connected gateway. A card captured via one PSP can be charged later via a different one. Is this only relevant for high-risk businesses? No. The examples above include a legitimate SaaS platform, an AI tool, and a long-standing Connect marketplace. Any business processing through a single PSP carries concentration risk -- regardless of industry classification. Should I keep my Stripe account if I add other PSPs? Yes. Multi-PSP doesn't mean abandoning Stripe. It means Stripe becomes one of several available processors. If Stripe works well for most of your volume, keep routing through it. The difference is that if something goes wrong, you have immediate alternatives. ## Related Reading - PSP-Neutral vs Single-PSP Architecture -- the full comparison of single-PSP lock-in vs multi-PSP flexibility - Enterprise PSP Mandates: Why Platforms Need Multiple Gateways -- when your customers require PSP flexibility - What PSP Consolidation Means for Your Platform -- why acquirer M&A makes multi-PSP essential - When Your SaaS Outgrows Stripe Connect -- the migration path when single-PSP hits limits - Gateway vs Orchestrator vs PayFac vs Payment Layer -- the four categories of payment infrastructure - How to Get Payments Off Your Product Roadmap -- reclaim engineering capacity for your core product - Embedded Payments Without Becoming a PayFac -- adding multi-PSP payments without the regulatory burden Running your platform on a single PSP? Shuttle connects your platform to 40+ payment processors through a single integration. If one PSP has a problem, your payments keep running. No engineering overhead. No vendor lock-in. PCI DSS Level 1 compliance included. Talk to Us | See How It Works ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### What PSP Consolidation Means for Your Platform ### Why You Should Have a Backup Payment Service Provider (PSP) ### Where PSP Distribution Actually Lives ### Multi-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know ### What Stripe's Unbundling Tells Us About the Future of Payments ## Links - [PSP-neutral payment layer](/guides/psp-neutral-vs-single-psp/) - [#1 reason platforms adopt multi-PSP](/guides/enterprise-psp-mandates/) - [PSP consolidation is accelerating](/blog/psp-consolidation-platform-risk/) - [payment layer](/guides/payment-layer-explained/) - [build vs buy analysis](/guides/get-payments-off-your-roadmap/) - [PSP-Neutral vs Single-PSP Architecture](/guides/psp-neutral-vs-single-psp/) - [Enterprise PSP Mandates: Why Platforms Need Multiple Gateways](/guides/enterprise-psp-mandates/) - [What PSP Consolidation Means for Your Platform](/blog/psp-consolidation-platform-risk/) - [When Your SaaS Outgrows Stripe Connect](/guides/when-saas-outgrows-stripe-connect/) - [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/) - [How to Get Payments Off Your Product Roadmap](/guides/get-payments-off-your-roadmap/) - [Embedded Payments Without Becoming a PayFac](/guides/embedded-payments-without-payfac/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Talk to Us](/discovery/) - [See How It Works](/platforms/) - [Book a Call](/discovery/) - [BlogWhat PSP Consolidation Means for Your Platform→](/blog/psp-consolidation-platform-risk/) - [BlogWhy You Should Have a Backup Payment Service Provider (PSP)→](/blog/why-you-should-have-a-backup-payment-service-provider-psp/) - [BlogWhere PSP Distribution Actually Lives→](/blog/where-psp-distribution-actually-lives/) - [BlogMulti-Gateway Connectors vs Native PSP Integrations: What SaaS Platforms Need to Know→](/blog/multi-gateway-connectors-vs-native-psp-integrations-what-saas-platforms-need-to-know/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) --- URL: https://www.shuttleglobal.com/guides/sprinklr-payments/ --- # How to Take Payments on Sprinklr: PCI-Compliant CX Payment Integration | Shuttle > If you're running a contact centre on Sprinklr Service, for a global retailer, a financial services brand, an airline, a public-sector services team, or... # How to Take Payments on Sprinklr: PCI-Compliant CX Payment Integration By Shuttle Team, April 19, 2026 If you're running a contact centre on Sprinklr Service, for a global retailer, a financial services brand, an airline, a public-sector services team, or an enterprise BPO, you've already met the payment gap. Customers want to pay during the call, in the chat, or inside the ticket. Sprinklr doesn't have a native, PCI-compliant way to capture their card. Sprinklr's unified-CXM platform handles voice, digital messaging, social, and email in a single agent workspace. Sprinklr AI++ powers agent assist, intent detection, and automated routing. The platform is built for enterprise scale, global brands, multi-language deployments, multi-channel volumes that no single-channel CCaaS can match. But card capture remains a separate problem, and the existing options leave gaps. This guide is for merchants taking payments through Sprinklr Service, and for solution providers and Sprinklr Partner Program members deploying Sprinklr for clients. It covers how Shuttle adds PCI-compliant payment capture to a Sprinklr operation today, and exactly what that involves. ## The Payment Gap in Sprinklr Sprinklr Service is built for unified customer experience management. Payment processing isn't part of the platform, and the gaps for businesses taking payments through Sprinklr: - No native payment processing. Sprinklr has no built-in mechanism to trigger a card transaction from inside a voice call, digital conversation, or case workflow. Card capture has to come from an external integration. - No secure voice card capture built in. Voice cases handled through Sprinklr's omnichannel routing don't have built-in secure card capture. Pause-and-resume on recording is a manual workaround that drags recordings into PCI scope on every drift. - Limited App Exchange options. App Exchange integrations exist but are typically narrow, single-gateway card capture, no multi-PSP routing, no cross-channel coverage. Enterprise deployments need more. - No AI-to-payment handoff. Sprinklr AI++ can deflect routine queries, surface coaching, and automate ticket routing. It cannot execute a card transaction securely. - Cross-channel friction. A customer might raise a billing issue on social, escalate to chat, and end on a voice call. Sprinklr unifies that case, but payment capture across all three channels needs a single payment layer that works in each. Most add-ons handle one channel, not all. ## How Shuttle Adds Payments to Sprinklr Shuttle adds PCI-compliant card capture to your Sprinklr payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay, and the card data never reaches your Sprinklr recordings, transcription, or your agents. The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Sprinklr specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Sprinklr call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running Sprinklr have already built exactly this. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down. ### Secure card capture (voice) When it is time to pay on a voice case, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits are captured inside Shuttle's certified environment, they never reach your Sprinklr recordings, your case data, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow. ### Payment Links across channels This is the most turnkey path, and it covers the digital channels Sprinklr unifies. Shuttle generates a payment link the agent can drop into the case conversation, chat, messaging, email, or social DM, or send by SMS mid-call. The customer pays on a hosted, PCI-compliant page, and status posts back to the case so the agent sees "paid" or "failed" inline. Links work even with gateways that don't support voice capture, and they suit cases that span multiple channels, payment can happen on whichever channel the customer prefers. See the Payment Links docs. ### Agent experience For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Sprinklr, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. Customers running Sprinklr have already built this. There is more in the "What to Expect" section below. ## How It Works - The case proceeds on Sprinklr: voice, chat, social, or email, as normal. - Payment is triggered from the interface you've built when the customer is ready to pay; the agent confirms the amount and never sees, types, or hears the card number. - Card captured securely. For voice, the card is captured in a PCI DSS Level 1 call via Twilio Pay, with the digits captured inside Shuttle's certified environment. For digital cases, the customer pays via a hosted payment link without the agent seeing any cardholder data. - Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. - Result returned. Status posts back into the Sprinklr case in real time via webhook, so the agent sees outcomes inline without entering PCI scope. - No card data in Sprinklr. The card digits never touch your Sprinklr cases, recordings, transcripts, or agent workstations. Sprinklr AI++ remains active throughout, helping deflect or summarise the surrounding conversation without ever capturing cardholder data, because the card digits are handled outside the Sprinklr environment. ## Multi-PSP Support Shuttle is gateway-agnostic. We connect to 40+ PSPs, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Authorize.Net, GlobalPayments, FreedomPay, FIS, Elavon, Fiserv, and most regional acquirers. You can route transactions based on currency, region, brand, business unit, or BPO client, useful for global Sprinklr deployments where different markets and brands use different acquirers. This matters for enterprise Sprinklr customers managing multiple brands, geographies, or BPO arrangements where one PSP doesn't cover everything. Switching gateways later is configuration, not a re-integration. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. Pricing is per successful transaction, see Shuttle pricing for the model and what you pay across multiple PSPs. ## PCI Compliance Shuttle is PCI DSS Level 1 certified. The integration is designed to keep cardholder data out of your Sprinklr environment entirely: - For voice, card digits are captured in the secure Twilio Pay call, never recorded, never transcribed, never reaching the agent's audio. - Card data captured on digital channels happens on Shuttle's hosted, PCI-compliant page, Sprinklr only receives status updates and tokens. - Sprinklr cases, transcripts, and AI++ outputs never contain card numbers. PCI scope stays narrow on the lighter SAQ-A path. - Audit trails, settlement reports, and reconciliation are available via Shuttle's reporting layer. For Sprinklr customers in regulated verticals, financial services, insurance, healthcare, telco, government, Shuttle is built to keep certified scope tight while supporting enterprise-scale CX operations. Full compliance documentation is in the security docs. ## For Solution Providers and Sprinklr Partner Program Members If you're a Sprinklr Partner Program member or SI deploying Sprinklr Service for clients, Shuttle is the payment layer you can build alongside your delivery. We support multi-PSP routing across your client portfolio (each client keeps their preferred acquirer) and partner-friendly commercials. Shuttle's voice capture runs via Twilio Pay, and payment links cover Sprinklr's digital channels; you build the agent-side interface against Shuttle's APIs. For partnership conversations, book a discovery call. ## Use Cases ### Global Retail and E-commerce Retailers running Sprinklr for unified service across social, chat, email, and voice can take payments on whichever channel the customer is on, order issue resolution, refund-and-rebill, abandoned-cart recovery. Multi-PSP routing supports multi-region acquirer setups. ### Financial Services and Insurance Banks and insurers using Sprinklr for omnichannel servicing can settle premium payments, loan repayments, and fee transactions inside the case. PCI scope stays narrow regardless of which channel the customer uses. ### Travel and Hospitality Airlines, OTAs, and hotel groups on Sprinklr can take ancillary payments, change fees, and deposits across voice and digital channels. The same payment layer handles a social complaint that escalates to chat and ends on a voice call. ### Multi-Tenant BPO Operations BPOs running Sprinklr across multiple end-clients can route payment transactions to each client's preferred acquirer with per-tenant configuration. No per-seat licensing penalties. ## What to Expect Shuttle is a payment layer you connect to your stack, not a pre-packaged Sprinklr plugin. Here is the honest detail so there are no surprises on the call: - It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. - You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Sprinklr specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Sprinklr call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running Sprinklr have already done it. - A native Sprinklr integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you. - Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version. Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later. ## Frequently Asked Questions ### Does Shuttle have a native Sprinklr integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Sprinklr. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio), which customers running Sprinklr have already done. We can build a native Sprinklr integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap. ### Does this require Twilio? Yes, today, for voice card capture. The secure capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Payment links for digital channels do not require the customer to be on a Twilio voice call. The carrier-agnostic version that removes the voice Twilio requirement is on our roadmap. ### Does Shuttle work across voice and digital channels? Yes. Voice card capture runs via Twilio Pay, and digital channels (chat, email, social, SMS) are covered by hosted payment links. Status posts back to the same Sprinklr case regardless of which channel the payment happened on. ### Does Shuttle affect Sprinklr AI++ analytics? No. AI++ continues transcribing, summarising, and analysing throughout the payment flow. Because card data is captured outside the Sprinklr environment, AI++ outputs never contain cardholder data. ### Can we just use payment links instead of voice capture? Yes. Many teams use links only, sent via SMS, email, or in the digital channel the customer is already on. Links are the most turnkey part of Shuttle and work even with gateways that don't support voice capture. ### What does Shuttle cost? $0.20 per successful transaction for voice, with no per-seat fees, no setup fees, and so cost scales with payment volume not headcount or channel. Links Checkout is a separate app; see [pricing](/pricing/). ## Related Reading - PCI-Compliant Payments for Contact Centres, the platform-by-platform merchant + SI guide - Twilio Pay Connectors, Shuttle's multi-gateway Pay Connector - Voice Payments, comprehensive voice payment capture guide - AI Voice Agent PCI Payments, for AI-led contact centres - Genesys Payments, enterprise CCaaS comparison - NICE CXone Payments, enterprise CCaaS comparison - Zendesk Payments, multi-channel support payment integration ## Get Started Shuttle adds enterprise-grade, PCI-compliant payment capture to a Sprinklr Service operation via Twilio for voice and payment links for digital channels, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup. If you take payments in a contact centre, see how Shuttle works for merchants, or book a discovery call to walk through your specific deployment. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [book a call](/contact/) - [Twilio IVR & Agent Assist payment docs](https://docs.shuttleglobal.com/docs/twilio-intro) - [Payment Links docs](https://docs.shuttleglobal.com/docs/links-intro) - [30+ supported gateways](/payment-providers/) - [40+ PSPs](/payment-providers/) - [Shuttle pricing](/pricing/) - [security docs](https://docs.shuttleglobal.com/docs/org-security) - [book a discovery call](/contact/) - [$0.20 per successful transaction](/pricing/) - [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/) - [Twilio Pay Connectors](/guides/twilio-pay-connectors/) - [Voice Payments](/guides/voice-payments/) - [AI Voice Agent PCI Payments](/guides/ai-voice-agent-pci-payments/) - [Genesys Payments](/guides/genesys-payments/) - [NICE CXone Payments](/guides/nice-cxone-payments/) - [Zendesk Payments](/guides/zendesk-payments/) - [Shuttle works for merchants](/merchants/payment-services/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/stripe-account-frozen/ --- # Stripe Froze My Account: What to Do and How to Prevent It | Shuttle > If Stripe has frozen your account, you're probably reading this in a state of panic. Your payments are stuck. Your customers can't check out. # Stripe Froze My Account: What to Do and How to Prevent It By Shuttle Team, March 19, 2026 If Stripe has frozen your account, you're probably reading this in a state of panic. Your payments are stuck. Your customers can't check out. Your cash flow has stopped. And Stripe's support team is sending templated responses that don't actually explain what happened. You're not alone. This happens to thousands of businesses every year -- legitimate ones, not just high-risk operations. Stripe processes payments for over 3 million businesses, and their automated risk systems flag accounts at a scale that means genuine businesses get caught up constantly. This guide covers exactly what to do right now, why it happened, and how to make sure it never happens again. ## Why Stripe Freezes Accounts Stripe isn't a bank. It's a payment facilitator (PayFac), which means your business operates under Stripe's master merchant account. That gives Stripe enormous discretion over who can process and when. Understanding why accounts get frozen helps you respond correctly and prevent recurrence. ### High Dispute Rates The most common trigger. Visa's Dispute Monitoring Programme activates at 0.9% of transactions or 100 disputes per month. Mastercard's threshold is 1.5%. But Stripe's internal threshold is lower -- roughly 0.75%. At low volumes, the maths is brutal. If you process 50 transactions a month, a single dispute puts you at 2%. Two disputes and you're at 4%. Stripe's automated systems don't distinguish between a business with 2 chargebacks out of 50 transactions and one with 200 out of 5,000. ### Sudden Volume Spikes Stripe's risk models build a profile of your "normal" transaction patterns. A sudden spike -- a successful marketing campaign, a seasonal rush, a viral product launch -- can trigger automated holds. The system interprets unexpected volume as potential fraud. This is particularly painful because it hits businesses at the exact moment they're growing fastest. ### Prohibited or Restricted Business Types Stripe maintains a restricted businesses list that covers dozens of categories. Some are obvious (gambling, adult content). Others catch people off guard: nutraceuticals, travel agencies, telehealth, subscription boxes with high return rates, and certain SaaS models. The catch: Stripe often approves these businesses initially (their onboarding is deliberately frictionless), then flags them weeks or months later once transaction data reveals the business type. ### Algorithmic False Positives Stripe's machine learning models analyse transaction patterns, customer behaviour, and metadata. These models are tuned to minimise Stripe's risk, not your false positive rate. Legitimate patterns -- like a B2B SaaS with large, infrequent transactions -- can look indistinguishable from fraud to an algorithm. ### Refund Patterns High refund rates, even without chargebacks, signal risk. If customers frequently request refunds, Stripe's systems may conclude your product or service has quality issues that will eventually lead to disputes. ### Regulatory or Compliance Triggers Changes in regulations, card network rules, or Stripe's own policies can retroactively make your business non-compliant. Stripe doesn't always notify merchants before acting. ## What to Do Immediately ### 1. Don't Panic -- But Act Fast Stripe typically gives you a window to respond, but it varies. Some freezes are temporary holds pending review. Others are full terminations with a 14-day wind-down. Check your email carefully for the specific terms. ### 2. Document Everything Before you do anything else, export and save: - Transaction history -- download your full transaction log from the Stripe Dashboard - Customer data -- export your customer list, subscriptions, and payment methods (you'll need this if you have to migrate) - Dispute evidence -- gather any documentation related to disputes: delivery confirmations, customer correspondence, terms of service agreements - Communication logs -- screenshot every email and notification from Stripe This documentation serves two purposes: it supports your appeal, and it prepares you for migration if the appeal fails. ### 3. Review Stripe's Communication Stripe's notification will usually reference a specific policy or risk category. Read it carefully. Common language includes: - "Elevated dispute rate" -- your chargebacks exceeded their threshold - "Business model concerns" -- they've flagged your business type - "Unusual activity" -- volume spike or pattern change - "Additional information required" -- they want documentation, not necessarily terminating you The distinction matters. An information request is recoverable. A termination notice is much harder to reverse. ### 4. Respond Promptly and Professionally If Stripe has requested information or you're filing an appeal: - Respond within 24-48 hours - Provide specific data, not general assurances - Include evidence: customer contracts, delivery confirmations, business licences, financial statements - Explain any volume changes with context (marketing campaigns, seasonal patterns, new product launches) - If disputes caused the freeze, show what you've done to reduce them (updated terms, improved customer service, clearer billing descriptors) ### 5. Contact Stripe Support Directly If you have a Stripe account manager or are on a premium support plan, contact them directly. For standard accounts, use the Dashboard support chat -- it's typically faster than email. Be aware that front-line support often can't override risk decisions. You may need to escalate to the risk or compliance team. ## If Your Appeal Fails ### Understand the Timeline When Stripe terminates an account, they typically hold remaining funds for 90-120 days to cover potential chargebacks. This is standard industry practice, not unique to Stripe, but it can be devastating for cash flow. ### Legal Options If you believe the freeze is unjustified and the amounts are significant: - Review your Stripe agreement -- check the specific terms around termination, fund holds, and dispute resolution - Send a formal complaint -- a letter from a solicitor can sometimes accelerate the review process - Financial ombudsman -- in the UK, the Financial Ombudsman Service may be able to help if Stripe is regulated for the specific activity - Small claims or litigation -- for significant amounts, legal action is an option, though the cost-benefit analysis matters ### The MATCH List Risk If Stripe terminates your account for excessive chargebacks or fraud, they may add your business to the MATCH list (Member Alert to Control High-risk Merchants). This is a Mastercard-maintained database that other processors check during underwriting. Being on the MATCH list makes it significantly harder to get approved by another provider. Not all terminations result in MATCH listing. Account closures due to business type restrictions or Stripe's risk appetite changes typically don't. But chargeback or fraud-related terminations often do. ## How to Prevent This From Happening Again ### Diversify Your Payment Processors This is the single most important step. If you process through only one provider, that provider has absolute power over your business. When Stripe freezes your account, everything stops. With a multi-PSP architecture, a single provider freeze doesn't shut you down. Traffic routes to your other processors while you resolve the issue. Your customers never notice. This isn't theoretical risk mitigation -- it's the same approach that every enterprise uses. No serious business processes $10M+ through a single gateway. The question is whether you wait until after a freeze to learn this lesson, or act before it happens. ### Monitor Your Dispute Rate Proactively Don't wait for Stripe to tell you there's a problem. Track your dispute rate weekly: - Set alerts at 0.5% -- well below Stripe's threshold, giving you time to act - Investigate every dispute -- understand why customers are filing chargebacks, not just how to win them - Improve billing descriptors -- unclear charges on bank statements are a leading cause of "friendly fraud" chargebacks - Respond to disputes within 24 hours -- faster responses have higher win rates ### Communicate Volume Changes in Advance If you're about to run a major campaign, enter a seasonal peak, or launch a new product, notify Stripe proactively. This won't guarantee protection, but it creates a record that the volume change was planned and legitimate. ### Keep Reserves Don't run your business on a razor-thin cash flow that depends on next-day Stripe payouts. Maintain enough reserve to cover 2-3 months of operations independently of any single payment provider. This gives you breathing room if funds are held. ### Understand Your Risk Profile Be honest about your business's risk characteristics: - Subscription businesses -- higher chargeback risk due to recurring billing disputes - High-ticket items -- individual chargebacks have outsized impact on dispute ratios - Digital goods -- harder to prove delivery, making disputes harder to win - International transactions -- higher fraud rates and cross-border complexity If your business falls into a higher-risk category, a single-provider approach is especially dangerous. ## Why Platforms Should Never Rely on a Single PSP If you're a platform processing payments on behalf of merchants -- using Stripe Connect, Adyen for Platforms, or similar -- the single PSP risk is amplified. Your merchants' behaviour directly affects your platform's standing with the processor. One bad merchant with high chargebacks can trigger scrutiny on your entire platform. And if your platform account is frozen, every merchant on your platform goes dark simultaneously. This is why growing platforms adopt PSP-neutral infrastructure: - Route merchants to different processors based on risk profile, geography, or volume - Isolate risk so one merchant's problems don't cascade to others - Maintain continuity if one processor changes their risk appetite or terms - Avoid the lock-in trap where switching costs become prohibitive after years of building on a single provider's API ## A Better Architecture The businesses that handle payment processor issues well share a common trait: they're not dependent on any single provider. Shuttle's payment infrastructure connects to 40+ PSPs through a single integration. If one processor freezes your account, transactions route to another -- automatically. No downtime, no customer impact, no panic. Key features that prevent the Stripe freeze scenario: - Multi-PSP routing -- traffic shifts to healthy processors instantly - Portable tokens -- your customer payment data isn't locked inside Stripe's vault - No contracts -- you're never trapped with a provider that's holding your funds - PCI DSS Level 1 -- enterprise-grade security without the compliance burden The goal isn't to avoid Stripe specifically. Stripe is an excellent payment processor for many use cases. The goal is to avoid the architectural mistake of making any single provider a single point of failure for your business. ## Next Steps If your account is currently frozen, focus on the immediate response steps above. Document everything, file your appeal, and start evaluating backup processors today. If you're reading this before it happens to you -- and it may never happen -- the prevention steps are straightforward: diversify your processors, monitor your dispute rate, and build an architecture that doesn't give any single company the power to shut down your business overnight. Related reading: - PSP-Neutral vs Single-PSP: Which Approach Is Right? - What Happens When Your Only Payment Processor Cuts You Off - Shuttle vs Stripe Connect - Stripe Connect Alternatives for Platforms ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Payment Links for Stripe: Add Branded Checkout Links to Your Stripe Account ### 5 Stripe Connect Limitations That Force Platforms to Switch ### What Stripe's Unbundling Tells Us About the Future of Payments ### Revolutionize Your Payment Process with Stripe Payment Links ## Links - [restricted businesses list](https://stripe.com/legal/restricted-businesses) - [multi-PSP architecture](/guides/psp-neutral-vs-single-psp/) - [single PSP risk](/guides/single-psp-risk/) - [Shuttle's payment infrastructure](/platforms/) - [PSP-Neutral vs Single-PSP: Which Approach Is Right?](/guides/psp-neutral-vs-single-psp/) - [What Happens When Your Only Payment Processor Cuts You Off](/guides/single-psp-risk/) - [Shuttle vs Stripe Connect](/vs/stripe-connect/) - [Stripe Connect Alternatives for Platforms](/alternatives/stripe-connect/) - [Book a Call](/discovery/) - [BlogPayment Links for Stripe: Add Branded Checkout Links to Your Stripe Account→](/blog/payment-links-for-stripe/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [AlternativeStripe Connect Alternatives for Platforms→](/alternatives/stripe-connect/) - [Blog5 Stripe Connect Limitations That Force Platforms to Switch→](/blog/stripe-connect-limitations/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) - [BlogRevolutionize Your Payment Process with Stripe Payment Links→](/blog/revolutionize-your-payment-process-with-stripe-payment-links/) --- URL: https://www.shuttleglobal.com/guides/stripe-twilio-integration/ --- # Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) | Shuttle > There are two ways to charge a Stripe-connected card during a phone call (IVR, agent-assisted, or AI voice agent): Twilio's own Stripe Pay Connector, or... # Stripe Twilio Integration: Voice, IVR & AI Agent Payments (2026) By Shuttle Team, July 6, 2026 There are two ways to charge a Stripe-connected card during a phone call (IVR, agent-assisted, or AI voice agent): Twilio's own Stripe Pay Connector, or Shuttle's Pay Connector with Stripe configured as your gateway. Both use Twilio's `` verb for PCI-compliant card capture. The difference is what sits between Twilio and Stripe. The native connector links `` to a single Stripe account and covers simple in-call charge and tokenisation. Shuttle connects Stripe (and 30+ other gateways) through one connector, adding multi-gateway routing, cross-channel token reuse, and multi-merchant management. This guide walks through how the Stripe + Twilio integration works via Shuttle, how to set it up, and when the native Stripe connector is the better fit. ## Two Ways to Connect Stripe to Twilio Twilio ships a first-party Stripe Pay Connector: you authorise it against your Stripe account via Stripe Connect OAuth, and `` can then charge or tokenise cards straight into Stripe. Since January 2024 Twilio bills $0.15 per successful transaction for it. If you have one Stripe account and only ever need a simple in-call charge, it is the simplest path, and we say so plainly in our full comparison of the Twilio Stripe Pay Connector. The native connector's ceiling shows up quickly for platforms and contact centres: it is Stripe-only, there is no multi-gateway routing or failover, no multi-merchant management, refunds and post-payment operations happen outside the call flow in Stripe directly, and Twilio's docs do not list it for the Ireland (IE1) or Australia (AU1) regions. Shuttle provides the multi-gateway alternative: a Pay Connector that accepts card data from Twilio's verb and routes it to Stripe's API for processing. Your Stripe account and Stripe fees stay exactly as they are. What changes is everything around the transaction: routing, token reuse across channels, and merchant management. ## How It Works - Caller reaches payment step. Your Twilio call flow -- IVR, Studio, or custom TwiML -- triggers the verb. - Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings. - Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers. - Shuttle charges the card via Stripe. The connector creates a Stripe PaymentIntent (or charge), processes the transaction, and handles the response. - Result returned to your call flow. Your webhook receives the Stripe charge ID, last four digits, card brand, and transaction status. The call continues. The entire flow happens in seconds. The caller stays on the line. No redirects, no "please visit our website." ## Step-by-Step Setup ### Prerequisites - A Twilio account with voice capability - A Stripe account with API keys - A Shuttle account (free to create -- you pay per transaction) ### Step 1: Install Shuttle's Pay Connector Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration. ### Step 2: Add Stripe Credentials to Shuttle Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile: - Gateway: Stripe - API key: Your Stripe secret key () - Currency: Set your default (GBP, USD, EUR, etc.) - Mode: Live or Test (use for testing) Save the profile. Shuttle now has a live connection to your Stripe account. ### Step 3: Configure Your Twilio Call Flow Add the verb to your TwiML or Twilio Studio flow: Key parameters: - -- the amount to charge - -- ISO currency code - -- your webhook endpoint for the payment result ### Step 4: Handle the Payment Result Twilio sends a POST to your URL with the payment result: Use the to look up the charge in Stripe if needed. Update your order, confirm to the caller, and continue the flow. ### Step 5: Test Use Stripe's test mode () and Twilio's test credentials to verify the flow end-to-end before going live. Test card numbers: (Visa), (Mastercard). ## What You Can Do With Stripe + Twilio ### Charge Immediately Standard auth-and-capture. The caller pays, Stripe processes, done. ### Authorise Now, Capture Later Place a hold on the card during the call. Capture the payment later -- useful for hotel reservations, car hire deposits, or any scenario where the final amount might change. ### Tokenise for Future Use Capture card details once over the phone. Shuttle tokenises the card via Stripe and returns a reusable token. Use it for future payments across any channel -- web, mobile, voice, or payment links. The card data is never stored in your systems. ### Recurring Payments Combine tokenisation with Stripe's subscription or recurring payment features. Capture the card securely over a phone call, then use the token for ongoing charges without the customer needing to call again. ## Multi-PSP: Beyond Stripe One of the key advantages of using Shuttle rather than a Stripe-only connector is flexibility. Your Twilio integration stays the same even if you: - Add a second gateway -- serve your UK merchants with Worldpay and your US merchants with Stripe - Serve enterprise customers who mandate a specific PSP (Adyen, Checkout.com, Global Payments, etc.) - Want a backup gateway -- if Stripe is down, you can move the affected payment types to another connected gateway - Expand to new markets where a local acquirer gives better authorisation rates You choose which connected provider handles each payment type in Shuttle's dashboard. Your Twilio call flow doesn't change. The verb always points to -- Shuttle sends the payment to the provider you configured. This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Stripe account (or any other gateway) through the same Twilio integration. ## PCI Compliance The Stripe + Twilio integration via Shuttle limits your PCI scope: PCI handled by DTMF capture & suppression Card data processing Shuttle (PCI DSS Level 1) Payment processing Stripe (PCI DSS Level 1) Your systems No card data -- SAQ-A Card data flows from Twilio → Shuttle → Stripe. Your application only receives redacted data (last 4 digits, card brand, charge ID). You typically qualify for SAQ-A -- the lightest PCI self-assessment. For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data. ## FAQ Can I connect Stripe to Twilio without Shuttle? Yes. Twilio has a built-in Stripe Pay Connector that links to a single Stripe account for in-call charges and tokenisation. It suits simple, single-account setups. Choose Shuttle when you need multiple gateways or merchants, routing and failover, cross-channel token reuse, or availability in Twilio's IE1 and AU1 regions. Does this work with Twilio Studio? Yes. Twilio Studio supports the widget. Configure it with as the connector and the payment flow works within your Studio flow. Can I use Stripe Connect with this? Not at the platform level. Shuttle doesn't connect to a Stripe Connect parent/platform account and route payments to connected accounts dynamically -- there's no way to point Twilio at a Connect platform key and have Shuttle distribute charges across sub-accounts. What you can do: add each Stripe account as its own Shuttle payment profile using that account's own API key. That includes individual Stripe Connect connected accounts -- if you have direct API key access to the connected (sub) account, add it as a standalone profile in Shuttle and route Twilio calls to that profile. Each sub-account = one Shuttle profile. What about Stripe's test mode? Fully supported. Use your Stripe test API key () in Shuttle and test the full flow with Twilio before going live. What does it cost? Shuttle charges $0.20 per successful transaction. Stripe's standard fees apply on top (2.9% + 30¢ or your negotiated rate). No Shuttle setup fees or monthly minimums. Can I switch from Stripe to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same -- no code changes needed. ## Related Reading - Twilio Stripe Pay Connector: Features, Limits and the Multi-Gateway Alternative -- the full native-vs-Shuttle comparison - Twilio Pay Connectors: How to Connect Any Payment Gateway -- the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio PCI Compliance: Payments Without Handling Card Data -- how to keep your PCI scope at SAQ-A - How to Connect Adyen to Twilio for Voice Payments -- step-by-step Adyen + Twilio setup - How to Connect Worldpay to Twilio for Voice Payments -- step-by-step Worldpay + Twilio setup - How to Connect Checkout.com to Twilio for Voice Payments -- step-by-step Checkout.com + Twilio setup - Stripe Alternatives for Platforms -- why platforms choose PSP-neutral infrastructure over Stripe-only - Shuttle vs Stripe for Platforms -- comparing embedded payment approaches - Twilio Pay -- Connect Any Payment Gateway to Twilio -- all supported gateways, pricing, and setup *Connect Stripe to Twilio in minutes with Shuttle's Pay Connector -- PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### QuickBooks Stripe Integration: Full Setup Guide (2026) ### Shuttle vs Stripe Connect ### Stripe Connect Alternatives for Platforms ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### 5 Stripe Connect Limitations That Force Platforms to Switch ### What Stripe's Unbundling Tells Us About the Future of Payments ## Links - [Stripe Pay Connector](/guides/twilio-stripe-pay-connector/) - [30+ other gateways](/payment-providers/) - [full comparison of the Twilio Stripe Pay Connector](/guides/twilio-stripe-pay-connector/) - [payment links](/merchants/links-checkout/) - [a specific PSP](/guides/enterprise-psp-mandates/) - [BPOs](/guides/payment-collection-for-bpos/) - [PCI scope](/glossary/pci-scope/) - [DTMF capture](/guides/dtmf-payments/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Stripe Pay Connector: Features, Limits and the Multi-Gateway Alternative](/guides/twilio-stripe-pay-connector/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [How to Connect Adyen to Twilio for Voice Payments](/guides/adyen-twilio-integration/) - [How to Connect Worldpay to Twilio for Voice Payments](/guides/worldpay-twilio-integration/) - [How to Connect Checkout.com to Twilio for Voice Payments](/guides/checkout-com-twilio-integration/) - [Stripe Alternatives for Platforms](/vs/stripe-connect/) - [Shuttle vs Stripe for Platforms](/vs/stripe-connect/) - [Twilio Pay -- Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogQuickBooks Stripe Integration: Full Setup Guide (2026)→](/blog/maximize-invoice-payments-in-quickbooks-with-stripe-integration/) - [ComparisonShuttle vs Stripe Connect→](/vs/stripe-connect/) - [AlternativeStripe Connect Alternatives for Platforms→](/alternatives/stripe-connect/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [Blog5 Stripe Connect Limitations That Force Platforms to Switch→](/blog/stripe-connect-limitations/) - [BlogWhat Stripe's Unbundling Tells Us About the Future of Payments→](/blog/stripe-unbundling-multi-psp/) --- URL: https://www.shuttleglobal.com/guides/switch-twilio-pay-connector/ --- # How to Switch Twilio Pay Connectors Without Breaking Your Call Flow | Shuttle > Quick answer: switching Twilio Pay Connectors is a one-attribute change. The connector is selected per-request by the paymentConnector attribute on the... # How to Switch Twilio Pay Connectors Without Breaking Your Call Flow By Shuttle Team, July 5, 2026 Quick answer: switching Twilio Pay Connectors is a one-attribute change. The connector is selected per-request by the attribute on the verb (or the connector name in the Agent Assist Payments API call), so pointing your call flow at a new connector takes seconds. The real work is the checklist around it: saved card tokens do not port between connectors, custom support differs, and webhook result fields vary slightly. Because Twilio lets you install multiple connectors side by side, you can run old and new in parallel and cut over with zero downtime. This guide covers what actually changes, the full migration checklist, and the two most common starting points: the Stripe connector and a self-built Generic connector. ## What Actually Changes (and What Does Not) Twilio designed so that the connector is a routing decision, not an architecture decision. That is good news for anyone who has hit a capability wall on their current connector. What stays the same: - Your `` TwiML structure. , , , , prompts, and input handling are all connector-agnostic. None of it changes. - Your call flow. IVR logic, Studio flows, agent scripting, and DTMF capture behave identically. Twilio handles capture and tone suppression regardless of which connector processes the payment. - Your Twilio account and phone numbers. Nothing at the account level moves. What changes per connector, and needs planning: - Saved card tokens. Tokens are not portable. A Stripe Token or PaymentMethod id lives in Stripe's vault and was created through the Stripe connector; tokens created via a different connector live in that connector or gateway's vault. If you charge repeat customers against stored tokens, this is the biggest item on your checklist. - Custom `` support. The Stripe connector supports an undocumented `metadata_` prefix and a `CustomerPhone` parameter on reusable tokens, per its Marketplace listing. Shuttle's connector documents its parameters: `account_` for routing to a specific payment profile, `metadata_action=AUTHfrequency` for recurring setup. - Webhook result fields. The core result payload is consistent, but some fields differ slightly per connector. , for example, means different things depending on the connector, per Twilio's documentation. Your result handler needs a quick review. - Twilio's per-transaction fee. Twilio bills the Stripe connector at $0.15 per successful transaction, Shuttle at $0.20, and CardConnect moved to usage-based billing in October 2025. Factor the delta into your business case alongside what you gain. One attribute to change, four things to plan. Here is the sequence. ## The Migration Checklist - Install the new connector alongside the old one. The Twilio Console catalogue supports multiple installed connectors, and Twilio's docs describe creating multiple instances of a connector. Install Shuttle's Pay Connector from the Twilio Marketplace without touching your existing one. Nothing changes in production yet. - Recreate your configuration on the new connector. For Shuttle, that means adding your gateway credentials as payment profiles in the Shuttle dashboard. Your existing gateway account stays exactly as it is: if you process through Stripe today, Shuttle routes to that same Stripe account, and your gateway fees are unchanged. You are swapping the bridge, not the bank. - Map your custom parameters. Audit every `` in your TwiML. Stripe's undocumented `metadata_` workaround maps cleanly to Shuttle's documented `metadata_` parameters, so your pass-through data survives. While you are in there, consider adding `account_action=AUTH` if you want authorise-now-capture-later. - Plan for saved tokens. Stored cards do not transfer, so pick a strategy per customer segment: - Run both connectors in parallel. Keep charging existing tokens through the old connector while all new payments (and new tokenisations) go through the new one. Retire the old connector once the token base has rolled over. - Re-capture on the next call. The next time a repeat customer calls, take card details fresh through the new connector and store the new token. - Send a payment link to re-vault. Push customers a hosted payment link so they can re-enter card details on their own time, no call needed. - Update your webhook handling. Review your and handlers against the new connector's result fields. Most fields carry over, but check anything you parse from or connector-specific confirmation codes, and update your transaction lookup logic to point at the new connector's references. - Test end to end in sandbox. Shuttle supports test mode via sandbox gateway credentials, so you can run the full flow with test cards: capture, charge, webhook, and any post-payment operations like refunds, captures, and voids via the Shuttle API. - Cut over. Change the attribute in your TwiML, or the connector name in your Studio flow's Pay widget or Agent Assist API call. Because the attribute is evaluated per request, the change takes effect on the very next call. Calls already in progress on the old connector complete normally. Zero downtime. - Monitor, then uninstall. Watch success rates and webhook results for a week or two. Once you are confident (and any parallel-run token strategy has completed), uninstall the old connector from the Console. ## Switching From the Stripe Connector The most important thing to understand: your Stripe account survives the switch. Shuttle connects to Stripe as one of its 30+ supported gateways, so you add your Stripe credentials as a Shuttle payment profile and transactions keep settling into the same Stripe account at the same Stripe fees. Only the connector layer changes. What you gain is the capability set the Stripe connector does not offer: documented custom parameters, authorise-and-capture-later, multi-gateway routing, and post-payment operations (refunds, captures, voids) through the Shuttle API. The full comparison is in Twilio Stripe Pay Connector: Capabilities and Limits. The one real migration cost is tokens. Stripe PaymentMethod ids created through the Stripe connector stay usable in Stripe itself, but they were vaulted via that connector's flow, so plan your repeat-customer strategy per step 4 above. ## Switching Off a Self-Built Generic Connector If you built your own connector on Twilio's Generic Pay Connector framework, you are carrying two burdens a pre-built connector removes: the endpoint and the compliance scope. The Generic connector's gateway URL is immutable in LIVE mode, and going live required submitting an Attestation of Compliance to Twilio Support. That endpoint receives cardholder data, which means it sits inside your PCI cardholder data environment, with everything that implies for your assessments. Switching to Shuttle means decommissioning that self-hosted endpoint entirely. Card data flows from Twilio to Shuttle (a PCI DSS Level 1 Service Provider) and on to your gateway, never touching your infrastructure. Your cardholder data environment shrinks, which is a concrete win at your next assessment: you typically qualify for SAQ-A, the lightest self-assessment. The full background is in Twilio Generic Pay Connector: Build vs Buy. ## Rollback Plan Keep the old connector installed until you are confident. Because the connector is selected per request, rolling back is the same one-attribute change in reverse: point back at the old connector name and the next call uses it. No reinstallation, no reconfiguration, no waiting. This is also why the parallel-run strategy is low risk. Both connectors sit installed side by side, both fully configured, and your TwiML decides which one handles each payment. You control the pace of the cutover completely. ## Switching Pay Connectors FAQ Can I run two Twilio Pay Connectors at once? Yes. The Twilio Console supports multiple installed connectors, and each request selects its connector via the attribute. Running old and new in parallel during migration is the standard zero-downtime approach. Do saved cards transfer between Pay Connectors? No. Tokens live in the vault of the gateway or connector that created them, so they do not port. Plan for repeat customers by running the old connector in parallel until tokens roll over, re-capturing card details on the next call, or sending a payment link to re-vault. Do I need to change my Twilio call flow? Only the attribute (or the connector name in your Studio Pay widget or Agent Assist API call). The rest of the structure, including , , , and , is connector-agnostic. Will my Stripe account still work after switching? Yes. If you switch to Shuttle, you add your existing Stripe account as a payment profile and Shuttle routes transactions to it. Settlement, reporting, and your Stripe fees are unchanged. Only the connector between Twilio and Stripe changes. How long does switching take? Installing and configuring the new connector typically takes under an hour, and the cutover itself is instant because the attribute is evaluated per call. The overall timeline is set by your token strategy: if you have no stored cards, you can switch same-day; if you charge repeat customers, plan for a parallel-run period. ## Related Reading - Twilio Pay Connectors: How to Connect Any Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing - Twilio Stripe Pay Connector: Capabilities and Limits: what the Stripe connector does and where it stops - Twilio Generic Pay Connector: Build vs Buy: what building your own connector really involves - Twilio Pay Error Codes Explained: diagnosing failed payments during and after migration - Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope at SAQ-A - Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup *Switch to Shuttle's Pay Connector with zero downtime: 30+ gateways, PCI DSS Level 1, $0.20 per successful transaction. Install on Twilio or book a discovery call.* ## Take payments over the phone PCI-compliant payment capture for contact centres, IVR flows, and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Twilio chooses Shuttle to provide payment connectivity ### How to Give Customers More Ways to Pay Your Invoices ### Dropping some knowledge on Buy Now Pay Later ### FreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle ### Shuttle vs Worldpay for Platforms ## Links - [DTMF capture](/guides/dtmf-payments/) - [Twilio Stripe Pay Connector: Capabilities and Limits](/guides/twilio-stripe-pay-connector/) - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [Twilio Generic Pay Connector: Build vs Buy](/guides/twilio-generic-pay-connector/) - [Twilio Pay Connectors: How to Connect Any Payment Gateway](/guides/twilio-pay-connectors/) - [Twilio Pay Error Codes Explained](/guides/twilio-pay-error-codes/) - [Twilio PCI Compliance: Payments Without Handling Card Data](/guides/twilio-pci-compliance/) - [Twilio Pay: Connect Any Payment Gateway to Twilio](/integrations/twilio-pay/) - [Install on Twilio](/integrations/twilio-pay/) - [book a discovery call](/discovery/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogTwilio chooses Shuttle to provide payment connectivity→](/blog/twilio-chooses-shuttle-to-provide-payment-connectivity/) - [BlogHow to Give Customers More Ways to Pay Your Invoices→](/blog/from-chase-to-choice-give-customers-easier-ways-to-pay-your-invoices/) - [BlogDropping some knowledge on Buy Now Pay Later→](/blog/dropping-some-knowledge-on-buy-now-pay-later/) - [BlogFreedomPay Integration -- Simplified: Connect with Zapier, Twilio, QuickBooks & More via Shuttle→](/blog/freedompay/) - [ComparisonShuttle vs Worldpay for Platforms→](/vs/worldpay/) --- URL: https://www.shuttleglobal.com/guides/synthflow-payments/ --- # How to Take Payments on Synthflow Voice Agents: Native Stripe vs Multi-PSP | Shuttle > Synthflow is a no-code platform for building AI voice agents, and unlike most of its peers it already has a native payment story. # How to Take Payments on Synthflow Voice Agents: Native Stripe vs Multi-PSP By Shuttle Team, May 28, 2026 Synthflow is a no-code platform for building AI voice agents, and unlike most of its peers it already has a native payment story. Its Stripe integration lets agents charge callers during conversations, reconcile transactions automatically, and keep billing in sync, all without writing code. Synthflow also markets PCI-compliant handling with credit-card redaction across its SOC 2, HIPAA, PCI DSS, and GDPR certified infrastructure. So this guide is not "Synthflow can't take payments." It can, through Stripe. This guide covers what the native Stripe integration does, where it stops, and when teams reach for Shuttle as the payment layer instead of, or alongside, the native option. The short version: if you run on Stripe and that is all you need, the native Synthflow integration may be enough. If you need more than one payment gateway, per-client routing for an agency, or true PCI scope reduction via a secure handoff that keeps card data out of the agent, that is where Shuttle fits. ## What the Native Synthflow + Stripe Integration Covers The native integration is built on Stripe. From the documentation, it lets you: - Charge callers during conversations inside automated agent workflows, white-labelled to your brand - Reconcile transactions automatically and keep billing data synced across your organisation - Run agency and subaccount billing by connecting a Stripe account to create custom plans, included minutes, and usage-based overage Synthflow also pairs with native telephony providers including Twilio, Telnyx, RingCentral, and Vonage, and applies selective redaction to sensitive data such as card numbers within its certified infrastructure. For a business that runs entirely on Stripe, that covers the common cases, including the debt-collection and outbound use cases Synthflow promotes. ## Where the Native Integration Stops Two limits matter most, and they hit agencies hardest. It is Stripe-only. The native integration connects to Stripe. If you use Adyen, Worldpay, Checkout.com, or any other gateway, or an end client mandates a specific PSP, the native path does not reach it. This is the sharpest constraint for Synthflow's agency and subaccount model: an agency running agents for many clients cannot route each client to that client's own gateway on a Stripe-only integration. Redaction is not the same as keeping card data out of scope. Marketing PCI-compliant infrastructure with credit-card redaction is real, but redaction means card data has already entered the pipeline and is being scrubbed. A payment layer that hands the call to a secure, isolated capture, so the digits never enter the agent flow or your recordings at all, is a stronger PCI posture. The documentation does not detail a secure capture path that keeps card data out of the agent entirely. ## How Shuttle Fits Shuttle is a PCI DSS Level 1 certified Service Provider that acts as a payment layer across your channels, including Synthflow agents. Shuttle has no native integration with Synthflow. Instead, your application code invokes Shuttle's Twilio-based payment setup, and at the point of payment the call is handed to a secure capture via Twilio Pay. You can use it instead of the native integration when its limits bite, or alongside it. To use the secure voice capture, you must be a Twilio customer. Multi-PSP routing. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. Set which provider handles each payment type, with amount and currency filters, all through one integration, where switching gateways is configuration, not re-integration. For Synthflow agencies, each client can use its own gateway. A few gateways (Braintree, for example) do not work for voice capture but do work for payment links. Secure in-call card capture. At the point of payment, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The customer enters their card on the keypad, and Shuttle captures the digits in its certified environment, so they never reach Synthflow or your recordings. The agent's voice pauses during entry, so card data stays out of the pipeline rather than being redacted after the fact. Payment links too. Payment links are the turnkey path. Shuttle sends hosted payment links by SMS or email across any supported gateway, including mid-call, so you keep the link option without being tied to Stripe. One honest caveat: the secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Synthflow agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Your team builds the agent-side orchestration that triggers the handoff, and you can validate it against Shuttle's sandbox gateway and demo app first. A native Synthflow integration is possible only as a paid project. Shuttle works with Twilio today, and any carrier coming soon. ## How It Works with Shuttle - Your Synthflow agent runs the conversation and reaches the payment step. - A workflow action triggers Shuttle to create a payment session with the amount, currency, and gateway configuration. - The customer pays either by keypad during the secure Twilio Pay capture (Shuttle captures the digits in its certified environment) or by a secure link Shuttle sends. - Shuttle processes the payment through your configured gateway inside its certified environment. - The result returns to your workflow, and the agent confirms the payment. Card data never enters Synthflow or your recordings, so your business stays at SAQ-A. To return the caller to the same Synthflow agent afterwards, program the return route in your Twilio flow and pass a conversation ID so the conversation resumes with context. ## When to Use Which - Native Synthflow + Stripe: you are Stripe-only, charging callers through Stripe is enough, and you do not need per-client gateway routing. - Shuttle: you need more than one gateway, you run an agency that routes clients to different PSPs, a client mandates a specific gateway, or you want a secure in-call keypad capture that keeps card data fully out of scope. The secure voice capture requires you to be a Twilio customer. ## FAQ Can Synthflow agents take payments natively? Yes. Synthflow has a native Stripe integration that lets agents charge callers during conversations, with automatic reconciliation and agency-friendly billing. Does the native integration support gateways other than Stripe? No. It is Stripe-only. For Adyen, Worldpay, Checkout.com, or per-client routing, you need a multi-PSP payment layer such as Shuttle, which connects to 30+ gateways. Switching gateways is configuration, not re-integration. Does Shuttle have a native Synthflow integration? No. Shuttle has no native integration with Synthflow. The handoff is API-driven: your application code triggers Shuttle's Twilio-based payment setup, and at the point of payment the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. A native Synthflow integration is possible only as a paid project. Does this require Twilio? Yes, for the secure in-call capture. The capture runs over Twilio Pay today, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Can an agency route each client to its own gateway? Not on the Stripe-only native integration. Shuttle supports per-client gateway configuration through a single integration. What does Shuttle cost? $0.20 per successful transaction for voice, with no setup fees. Links Checkout is a separate app; see [pricing](/pricing/). For technical detail, see the Shuttle docs: Twilio setup, payment links, and security and PCI. ## Related Reading - Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents - Vapi Payments: secure payment capture for Vapi voice agents - Bland AI Payments: secure payment capture for Bland AI phone agents - ElevenLabs Payments: native Stripe vs multi-PSP for ElevenLabs agents - How AI Voice Agents Take PCI-Compliant Payments: the technical architecture for secure payment capture during AI voice calls - What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared ## Add Multi-PSP Payments to Your Synthflow Agents Shuttle is a PCI DSS Level 1 certified Service Provider. If your Synthflow agents have outgrown Stripe-only payments, or you run an agency that needs per-client gateway routing: See Voice Checkout | Book a discovery call ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. Explore More ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Can You Take Card Payments on a Retell AI Voice Agent? ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ### Voice Payments Are an Architecture Decision, Not a Feature Request ## Links - [PCI DSS Level 1](/guides/pci-compliance-service-provider/) - [30+ payment gateways](/payment-providers/) - [30+ gateways](/payment-providers/) - [$0.20 per successful transaction](/pricing/) - [Twilio setup](https://docs.shuttleglobal.com/docs/twilio-intro) - [payment links](https://docs.shuttleglobal.com/docs/links-intro) - [security and PCI](https://docs.shuttleglobal.com/docs/org-security) - [Retell AI Payments](/guides/retell-ai-payments/) - [Vapi Payments](/guides/vapi-payments/) - [Bland AI Payments](/guides/bland-ai-payments/) - [ElevenLabs Payments](/guides/elevenlabs-payments/) - [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/) - [What Are Voice Payments? The Complete Guide](/guides/voice-payments/) - [See Voice Checkout](/platforms/voice-checkout/) - [Book a discovery call](/contact/) - [Book a Call](/discovery/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) - [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/) --- URL: https://www.shuttleglobal.com/guides/take-payments-on-behalf-of-clients/ --- # Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem | Shuttle > Quick answer: if your business collects payments that belong to your clients, you need each payment to settle into that client's own merchant account, not... # Take Payments on Behalf of Your Clients: Solving the Multi-Merchant-Account Problem By Shuttle Team, July 12, 2026 Quick answer: if your business collects payments that belong to your clients, you need each payment to settle into that client's own merchant account, not yours. A single gateway account can't do that. The clean solution is one payment system that holds a separate merchant account (MID) connection per client and routes every transaction to the right one. Shuttle does this across phone, payment links and API, with your clients keeping their own gateway relationships. There's a class of business that operates like a software platform without ever using the word. Medical and dental billing services. Revenue cycle management (RCM) firms. Collections servicers. Statement printers and AR outsourcers. Call answering services that take payments for the practices and firms they answer for. Property managers collecting rent for dozens of landlords. The pattern is the same in every case: you collect money that belongs to someone else. Fifty clients means fifty businesses whose money passes through your operation, and each of them expects their money to land in their bank account, under their name, reconciled against their ledger. Most payment tools are built for a business collecting its own money. The moment you collect for clients, those tools stop fitting. This guide explains why, what the two workable models are, and how to run payments for every client through one system without becoming a money handler yourself. ## Why one merchant account doesn't work A merchant account (and its MID, the merchant identifier the card networks use) is tied to one legal entity. Payments processed on it settle to that entity's bank account, and the card statement descriptor shows that entity's name. Run all your clients' payments through your own single account and three problems arrive quickly: - The money lands in the wrong place. Everything settles to you. Now you're disbursing client funds from your own account, which creates trust-accounting obligations, timing risk and a reconciliation burden that grows with every client. - You look like the merchant. Cardholders see your name, not the dental practice or the landlord they think they paid. Confused cardholders dispute charges, and the chargebacks are yours. - Your acquirer notices. Processing other businesses' payments through your own merchant account is, from the acquirer's point of view, unregistered aggregation. It breaches most merchant agreements and can get the account shut down. So the volume has to run on each client's own merchant account. The question is how you do that operationally when you have one team, one phone system and fifty MIDs. ## Two ways to route money to clients There are two workable models, and the difference matters more than any feature comparison. Route to each client's own merchant account Become the merchant of record Where funds settle Directly to each client's bank, from their own MID To you (or your provider), then disbursed to clients Whose PSP relationship The client keeps their own gateway and acquirer Yours; clients depend on your processing setup Statement descriptor The client's name Yours or your provider's Your regulatory position Service provider Money handler, with the obligations that follow Chargebacks and liability Sit with the client's account Concentrate on you Merchant-of-record aggregation is a legitimate model, but it turns you into a payments business: funds flow, disbursement schedules, KYC on every client, and liability concentrated in your entity. Most billing services, servicers and agencies don't want any of that. They want to be paid for the service they already provide, with the money going straight to the client. Routing to each client's own merchant account keeps the roles clean. The client keeps their gateway relationship and their settlement. You keep one operation and one system. Nobody's money sits in your accounts. That's the model Shuttle is built around: each client connects their own merchant account or gateway credentials once, and every payment your team takes is attributed to the right client. One integration on your side, however many MIDs on theirs. Shuttle works with 40+ payment gateways, so it fits the accounts your clients already have rather than forcing anyone to switch. Voice capture works on many of those gateways; payment links cover the rest. ## The phone is the compliance trap For most of these businesses the highest-volume channel is the phone. A patient calls the billing line. A debtor answers an outbound call. A tenant rings about rent. And a common way teams handle it today is also the riskiest: the agent asks for the card number and types it into a virtual terminal. The moment your staff hear or see card numbers, your whole operation is inside PCI DSS scope. Your phone system, your call recordings, your agents' screens, your training and vetting processes all become part of the compliance surface. For a servicer handling payments for fifty clients, that's fifty clients' worth of card data risk concentrated in one room. There are two ways to keep card data out of your environment while keeping the phone channel: - IVR self-payment ("press 1 to pay"). The caller pays through an automated flow, entering card details on the keypad. No agent involved, no card data in your environment. This suits high-volume, low-exception collections like patient balances and rent. - Agent-assisted secure capture. The agent stays on the line while the caller enters their card number on the keypad. The digits go to the payment gateway, not to the agent, whose screen shows only masked progress. The conversation continues; the card number never enters your phone system or recordings. And because real calls fail in predictable ways, the failure modes need answers too. Call drops mid-payment: send a payment link by SMS or email so the caller finishes on their phone. Caller has no card to hand: take a bank payment on the same call instead. Caller wants to pay later: schedule the link. Each of these is a recovery path for a payment that would otherwise be lost. Shuttle's Voice Checkout covers both phone patterns, with payment links as the fallback channel, and the same per-client routing applies everywhere: the IVR payment, the agent-assisted payment and the link payment all settle to the right client's merchant account. Card details are tokenised with the gateway itself; Shuttle holds no card vault of its own. For teams on Twilio, note that Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. ## Who this fits ### Medical and dental billing services (and RCM firms) You collect patient balances on behalf of practices. Each practice has its own merchant account, and payments must reconcile against the practice management or RCM system per client. Phone volume is high and PCI exposure is the operational headache: agents on patient calls all day, taking cards. Per-client routing plus agent-assisted capture fits this shape directly, and IVR self-pay absorbs the routine balance payments so agents handle exceptions. See the full guide to payment solutions for medical billing companies and RCM firms. ### Collections servicers and debt agencies Agencies collect on behalf of creditors, and creditors mandate where their money goes. One creditor requires their Worldpay account, another uses Stripe, a third names their acquiring bank in the contract. Per-client MID routing is not a nice-to-have here; it's a contractual requirement. See the full guide to secure payment collection for debt agencies. ### Call answering and virtual reception services You answer for hundreds of small firms, and callers increasingly expect to pay in the same call: the booking deposit, the outstanding invoice, the consultation fee. Taking a card verbally on behalf of a client is the same PCI trap plus the same settlement problem. Routing by client, with the receptionist using agent-assisted capture, turns payment-taking into a service line you can charge for. More in our piece on payments for call answering services. ### Statement printers and AR outsourcers You already produce the invoice, the statement or the dunning letter. Adding "pay now" (a link on the e-statement, an IVR number on the printed letter) closes the loop, but only if each payment settles to the issuing client's account. Per-client routing lets one print-and-post operation carry payment collection for every client on the file. ### Property managers and lettings agencies Rent belongs to the landlord. Client-money rules in most markets require it to be handled accordingly. Routing each tenant payment to the right landlord's account, rather than pooling and disbursing, keeps the agency out of the money chain. See payment links for property management. ## Why these businesses can go live fast A software platform that embeds payments has to wait for its downstream merchants to adopt. You don't. The call volume is already in your building, the client MIDs already exist, and every payment your team takes today is a payment you could route properly tomorrow. That's why these businesses can go live fast: the volume is theirs to move. The practical path: talk to us about your client mix and channels. If you want to explore the technical side first, docs.shuttleglobal.com covers the APIs, IVR and agent-assisted flows, and sandbox accounts are available for testing before any real client MID is connected. When it works, connect the first client's account and move their volume; then it's repetition, not integration. ## Take payments on behalf of clients: FAQ ### Can I take payments for multiple clients through one system? Yes. The requirement is per-client merchant account routing: each client connects their own merchant account or gateway credentials, and the system routes every payment to the right one. Your team works in one place; the money settles to each client directly. ### Do my clients need their own merchant accounts? In the routing model, yes, and that's the point: their money settles under their name, and they keep their own gateway relationship. Clients that don't yet have an account can set one up with one of the gateways Shuttle supports. The alternative (processing everything on your account) makes you an aggregator, which most merchant agreements prohibit. ### How do billing services take patient payments by phone without breaking PCI? Two patterns: IVR self-payment, where the patient pays through an automated keypad flow with no agent involved, or agent-assisted capture, where the agent stays on the line while the patient keys in the card number and the digits go straight to the gateway. In both, card data never enters your phone system, recordings or screens, which keeps those systems out of PCI DSS scope and cuts your own validation burden to a minimum. For how to design that automated flow, see IVR Payments. ### What's the difference between routing to client merchant accounts and being a merchant of record? Merchant of record means the funds flow through you: you settle, you disburse, you carry the chargebacks and the compliance obligations of a money handler. Routing means each payment settles directly to the client's own merchant account and you never touch the funds. For servicers, routing keeps your business a service business. ### Can each client use a different payment gateway? Yes. One client on Stripe, another on Worldpay, a third on their bank's acquiring service, provided it's one of the 40+ gateways Shuttle supports. Each connects the account they have. Shuttle supports 40+ gateways, so per-client routing doesn't require standardising your clients onto one provider. ### How fast can we go live? There's no downstream adoption to wait for: the phone volume is already yours. Test the IVR and agent-assisted flows against a sandbox account first, then connect the first client's merchant account. From there, adding clients is configuration, not a new project. ## Related reading - Payment collection for BPOs: multiple clients, multiple PSPs - Secure payment collection for debt agencies - Contact centre payments: the complete guide - DTMF payments: how keypad capture keeps agents out of PCI scope - ACH and bank payments over the phone - Merchant account providers compared Ready to route every payment to the right client's account? Talk to us. If you'd rather explore the technical side first, docs.shuttleglobal.com covers the APIs and flows, with sandbox accounts available for testing. ## Talk to us See how Shuttle can power payments for your platform: multi-PSP, multi-channel, white-label. ## Related Reading Explore More ### Can You Take Card Payments on a Retell AI Voice Agent? ### Why Most Call Answering Services Can't Take Payments ### How to Add Secure Payments to Your Twilio IVR (2026 Guide) ### Sage Invoice Payments: How to Let Customers Pay Online ### Agentic Payments Isn't Solved Yet ### Payments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It) ## Links - [40+ payment gateways](/payment-providers/) - [Voice Checkout](/platforms/voice-checkout/) - [payment links](/platforms/links-checkout/) - [payment solutions for medical billing companies and RCM firms](/guides/medical-billing-payments/) - [secure payment collection for debt agencies](/guides/secure-payment-collection-debt-agencies/) - [payments for call answering services](/blog/call-answering-service-payments/) - [payment links for property management](/guides/payment-links-property-management/) - [talk to us](/contact/) - [docs.shuttleglobal.com](https://docs.shuttleglobal.com) - [gateways Shuttle supports](/payment-providers/) - [IVR Payments](/guides/ivr-payments/) - [40+ gateways Shuttle supports](/payment-providers/) - [Payment collection for BPOs: multiple clients, multiple PSPs](/guides/payment-collection-for-bpos/) - [Secure payment collection for debt agencies](/guides/secure-payment-collection-debt-agencies/) - [Contact centre payments: the complete guide](/guides/contact-centre-payments/) - [DTMF payments: how keypad capture keeps agents out of PCI scope](/guides/dtmf-payments/) - [ACH and bank payments over the phone](/guides/ach-payments-over-the-phone/) - [Merchant account providers compared](/guides/merchant-account-providers/) - [Talk to us](/contact/) - [Book a Call](/discovery/) - [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/) - [BlogWhy Most Call Answering Services Can't Take Payments→](/blog/call-answering-service-payments/) - [BlogHow to Add Secure Payments to Your Twilio IVR (2026 Guide)→](/blog/how-to-add-secure-payments-to-your-twilio-ivr-in-minutes/) - [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/) - [BlogAgentic Payments Isn't Solved Yet→](/blog/agentic-payments-not-solved/) - [BlogPayments Are Eating 5-9% of Your Revenue (And You Might Not Even Be Tracking It)→](/blog/payments-cost-saas-platforms/) --- URL: https://www.shuttleglobal.com/guides/take-payments-online/best-payment-link-services-uk/ --- # Best Payment Link Services for UK Businesses | Shuttle > Compare the best payment link services for UK businesses in 2026. Side-by-side comparison of Stripe, PayPal, Square, SumUp, GoCardless, Shuttle, and more. # Best Payment Link Services for UK Businesses A side-by-side comparison of payment link providers for UK service businesses Last updated: February 2026 ## What Are Payment Links? Payment links are URLs that you send to a customer to collect a specific payment. You create a link for an amount -- say £350 for a plumbing repair -- and send it by text, email, or WhatsApp. The customer taps the link, sees a checkout page with the amount and a description, enters their card details, and pays. You receive confirmation instantly. No card machine, no website, no app download required on either side. Payment links have become one of the fastest-growing payment methods for UK service businesses because they solve a simple problem: how do you accept card payments from customers when you are not standing next to them with a terminal? For businesses with teams -- where multiple people need to collect payments in the field, by phone, or from the office -- payment links are increasingly replacing card machines as the primary payment collection method. There are now dozens of providers offering payment link services in the UK. This guide compares the major options, covering fees, features, and who each provider is best suited to. ## What to Look For in a Payment Link Service Before comparing individual providers, it helps to understand the criteria that matter most for UK service businesses. Transaction fees. The percentage and fixed fee charged per payment. UK card fees are regulated, so most providers cluster around 1.4-1.75% + 20p for domestic consumer cards. The differences emerge on European cards, corporate cards, and American Express. Monthly costs. Some providers charge nothing per month and make their money on transaction fees alone. Others charge a monthly subscription that includes team features, branding, or lower transaction rates. The right model depends on your volume: high-volume businesses often save money on a subscription plan with lower transaction fees. Branding and customisation. When your customer opens a payment link, they see a checkout page. Can you add your logo? Your brand colours? Your business name? A generic checkout page can reduce trust and create confusion. Branded checkout pages convert better and present a more professional image. Team access. If you have 5, 10, or 20 staff who need to send payment links, you need multi-user support with role-based permissions. Not every provider offers this -- many are designed for sole traders or very small businesses with a single account holder. Payout speed. How quickly the funds arrive in your bank account after a customer pays. Ranges from same-day to 7+ business days depending on the provider and your account history. For cash-flow-dependent businesses, this matters enormously. Delivery channels. Can the provider send links by SMS natively, or do you have to copy and paste a URL into your own messaging app? SMS and WhatsApp delivery are significantly more effective than email for consumer-facing service businesses. Phone payment support. If your office takes payments over the phone, does the provider offer a compliant phone payment method (like Voice Checkout), or would you need a separate solution for phone-based payments? ## The Best Payment Link Services for UK Businesses ### Stripe Payment Links Stripe is the most developer-friendly payment platform in the world, and their Payment Links product brings some of that power to non-technical users. You can create a payment link from the Stripe Dashboard without writing any code, set a fixed amount or let the customer enter their own, and share the link however you like. Transaction fees: 1.4% + 20p for UK cards, 2.5% + 20p for non-UK cards. No monthly fee for the core product. Strengths: Stripe's infrastructure is arguably the most reliable in the industry. Uptime is excellent, payouts are fast (typically 2-3 business days, with options for next-day or instant payouts at an additional fee), and the reporting is comprehensive. If you have a developer on your team -- or plan to integrate payments into your own software -- Stripe's API is the gold standard. Stripe also supports recurring payment links and subscription-style billing. Weaknesses: Stripe Payment Links are relatively basic as a standalone product. Customisation is limited -- you can add your logo and brand colour, but the checkout page is clearly a Stripe page. There are no built-in team features: every user needs access to the same Stripe Dashboard, and there is no role-based access control for payment link creation (though the broader Stripe Dashboard does have team permissions). Stripe does not send links by SMS natively -- you copy the URL and send it yourself. For non-technical business owners, the Stripe Dashboard can be overwhelming. Best for: Tech-savvy businesses, SaaS companies, and businesses with a developer who can use Stripe's API for custom workflows. Also good for sole traders who want a low-cost, no-monthly-fee option and are comfortable with a slightly technical interface. ### PayPal.Me PayPal.Me gives you a permanent personal link (paypal.me/yourbusiness/50 for a £50 payment) that you can share with anyone. The customer clicks the link, logs into PayPal or pays with a card as a guest, and the money goes into your PayPal account. Transaction fees: 1.99% + 20p for standard commercial payments in the UK. Higher for international payments. Strengths: PayPal is the most recognised online payment brand in the UK. Many customers already have PayPal accounts and are comfortable paying through the platform. The trust factor is significant -- especially for consumer-facing businesses where the customer might be wary of entering card details on an unfamiliar checkout page. PayPal also offers buyer protection, which can increase a customer's willingness to pay upfront for work not yet completed. Weaknesses: PayPal.Me links are not true "payment links" in the professional sense. The customer can change the payment amount, which creates reconciliation headaches. There is no description field on the payment page, so the customer does not see what they are paying for. PayPal's holds and limitations are well-documented -- new accounts or accounts with sudden volume increases can have funds frozen for 21 days. The fees are higher than most dedicated payment link providers. There are no team features, no branded checkout, and no SMS delivery. PayPal also has a habit of redirecting customers to sign up for a PayPal account, which adds friction for customers who just want to pay by card. Best for: Businesses that need a quick, recognisable payment method with no setup -- particularly for consumer-facing transactions where PayPal's brand trust outweighs its limitations. Not suitable as a primary payment system for a business with a team. ### Square Invoices Square's invoicing product includes payment links as part of the invoice. You create an invoice in the Square Dashboard or app, add line items and a total, and send it to the customer. The invoice email includes a "Pay Now" link that takes the customer to a Square-hosted checkout page. Square also allows you to create standalone payment links without a full invoice. Transaction fees: 1.4% + 20p for online payments (payment links and invoices). No monthly fee for the basic plan. Square Plus (with team management) is £29/month. Strengths: Square is excellent if your workflow is invoice-first. The invoice-to-payment-link flow is seamless: create an invoice, send it, and the customer can pay directly from the invoice with a single click. Square's ecosystem is broad -- if you also have a physical location, you can use Square POS alongside Square Invoices for a unified view of all payments. The interface is clean and non-technical. Square also supports recurring invoices and automatic payment reminders. Weaknesses: Square's standalone payment links are less developed than their invoicing product. If you want to send a quick payment link by text -- without creating a full invoice -- the process is more cumbersome than with a dedicated payment link provider. Team features require the £29/month Plus plan. Square does not send links by SMS natively (invoices are sent by email). Branding on the checkout page is limited. Square's customer support has mixed reviews from UK businesses. Best for: Businesses whose payment workflow centres on invoicing -- accountants, consultants, agencies, and professional services firms. Good for businesses that want a combined in-person POS and online payment solution. Less ideal for field-based teams that need to send quick payment links by text. ### SumUp Payment Links SumUp is best known for its card readers, but the company also offers payment links as part of its ecosystem. You create a link in the SumUp app, set the amount and description, and share it with the customer. Transaction fees: 1.69% flat (no fixed per-transaction fee). No monthly fee. Strengths: SumUp's flat-rate pricing is simple to understand -- 1.69% on every transaction regardless of card type. For businesses that process a lot of small payments (under £30), the absence of a fixed per-transaction fee makes SumUp genuinely cheaper than providers charging 1.4% + 20p. The app is straightforward and designed for non-technical users. No monthly fees, no contracts, and fast setup. Weaknesses: SumUp's payment link product is basic. There is limited branding, limited reporting, and no multi-user or team features. For larger payments, SumUp's 1.69% rate is more expensive than Stripe or Square's 1.4% + 20p (the crossover point is around £65). SumUp does not offer native SMS delivery of links. Payout speed is 1-3 business days, which is standard but not best-in-class. The product feels like an add-on to SumUp's card reader business rather than a standalone payment link platform. Best for: Sole traders and very small businesses that want a simple, no-monthly-fee payment link option -- especially those already using a SumUp card reader. Not suitable for businesses with teams that need multi-user access or advanced features. ### GoCardless GoCardless is the UK's leading Direct Debit provider, and it is often mentioned alongside payment link services. However, GoCardless serves a fundamentally different use case. Instead of one-off card payments, GoCardless collects payments directly from the customer's bank account via the Direct Debit system. Transaction fees: 1% + 20p per transaction (capped at £4). Success+ (intelligent retries) available on higher plans. Strengths: GoCardless is excellent for recurring payments. Once a customer sets up a Direct Debit mandate, you can collect regular payments automatically without any action from the customer. Transaction fees are lower than card-based payment links. Failed payments can be automatically retried. GoCardless integrates with most accounting software (Xero, QuickBooks, FreeAgent). For businesses with monthly contracts -- cleaning companies, maintenance providers, subscription services -- GoCardless can dramatically reduce payment admin. Weaknesses: GoCardless is not a payment link service in the traditional sense. It does not accept card payments. Direct Debits take 3-5 business days to process -- there is no instant confirmation. The customer must complete a mandate setup form before the first payment. GoCardless is not suitable for one-off, variable-amount payments that service businesses typically collect after completing a job. It is a complementary payment method, not a replacement for payment links or card machines. Best for: Businesses with recurring revenue -- monthly maintenance contracts, memberships, subscription services, regular retainers. Use GoCardless alongside a payment link provider, not instead of one. ### Shuttle Links Checkout Shuttle is a payments infrastructure company that has built its payment link product specifically for businesses with teams. Unlike providers that started with card machines or developer APIs and added payment links as an afterthought, Shuttle designed Links Checkout from the ground up for multi-user, field-based, and office-based payment collection. Transaction fees: Competitive per-transaction rates. Per-user pricing model rather than a flat monthly fee. Strengths: Shuttle's standout features are team access and multi-channel delivery. Every team member gets their own login and can create and send payment links from their phone or desktop. Links can be sent by SMS, email, or WhatsApp -- natively, without copying and pasting URLs. The checkout page is fully branded with your business name, logo, and colours, so customers see your brand rather than a third-party payment page. Shuttle also offers Voice Checkout as an add-on: PCI-compliant phone payments where the customer enters card details via their phone keypad. For businesses that collect payments both in the field (via payment links) and over the phone (via their office), this means one provider covers both channels. The dashboard gives a real-time view of all payments across the business -- office managers can see which team members have collected what, which payments are outstanding, and which customers are overdue. Weaknesses: Shuttle is newer and less well-known than Stripe, PayPal, or Square. Businesses that want a global, consumer-recognised brand on their checkout page may prefer PayPal. Developers looking for extensive API documentation and ecosystem integrations may prefer Stripe. Shuttle's per-user pricing means that very small businesses (1-2 people) may find a flat-rate provider cheaper. Best for: Service businesses with teams of 5-20+ people who need multiple staff members sending payment links, branded checkout pages, SMS/WhatsApp delivery, and optional phone payment capability. This is the provider built for plumbing companies, electrical contractors, cleaning businesses, property maintenance firms, and similar team-based service operations. ### Worldpay Payment Links Worldpay (now part of FIS) is one of the largest payment processors in the world. They offer payment links as part of their broader merchant services package, alongside card machines, online payment gateways, and in-store POS systems. Transaction fees: Variable -- typically negotiated based on volume. Often 1.5-2.5% + 20p for online payments. Monthly fees apply and vary by plan. Strengths: Worldpay is an enterprise-grade payment processor with global reach. If your business processes very high volumes (£100,000+ per month) or needs multi-currency support, Worldpay's negotiated rates can be competitive. They offer dedicated account management, chargeback support, and integration with a wide range of business systems. For large businesses that want a single payment provider handling everything from card machines to online payments to payment links, Worldpay offers a consolidated solution. Weaknesses: Worldpay is not designed for small or medium-sized service businesses. Onboarding is slow (typically 2-4 weeks versus the same-day setup offered by Stripe or SumUp). Contracts are often 12-36 months with early termination fees. Pricing is opaque -- you typically need to speak to a sales rep to get a quote, and the fee structures are complex (interchange-plus, blended rates, monthly minimums). Their payment link product is less developed than their core card processing -- it feels like an add-on rather than a focus area. Customer support is geared toward larger clients, and smaller businesses often report difficulty getting issues resolved. Best for: Large businesses (50+ employees, £100k+ monthly processing) that need an enterprise payment processor and want payment links as one capability within a broader merchant services agreement. Not suitable for SMEs or team-based service businesses. ## Comparison Table Fees shown are for UK-issued consumer cards. European and international card fees are higher across all providers. GoCardless fees are for Direct Debit, not card payments. ## Which Service Is Right for Your Business? The right payment link provider depends on three factors: your team size, your monthly payment volume, and how you interact with customers. If you are a sole trader or freelancer processing under £5,000 per month, cost is likely your primary concern. SumUp and Stripe both offer no-monthly-fee plans with competitive transaction rates. SumUp is simpler to use; Stripe offers more flexibility and better reporting. PayPal.Me works as a quick backup option if you need something instantly, but should not be your primary payment method for professional services. If you are a small business with 2-5 staff and your payment workflow centres on invoicing, Square Invoices offers the best invoice-to-payment experience. If you send more standalone payment links than invoices (for example, field-based trades), Stripe or Shuttle start to make more sense depending on whether you prioritise API flexibility or team features. If you are a service business with 5-20+ staff -- multiple engineers, technicians, cleaners, or operatives in the field who all need to collect payments -- this is where Shuttle Links Checkout is purpose-built. Multi-user access, branded checkout, SMS and WhatsApp delivery, a central dashboard showing all payments across the business, and Voice Checkout for the office. The per-user pricing model means you pay for what you use, and the team features eliminate the workarounds (shared logins, copied URLs, manual SMS sending) that other providers force you into at this team size. If you have recurring revenue alongside one-off payments -- say you do monthly maintenance contracts as well as ad-hoc repair work -- consider using GoCardless for the recurring element and a payment link provider (Stripe, Square, or Shuttle) for one-off payments. This gives you the lowest transaction fees on predictable revenue and the flexibility of payment links for everything else. If you are a larger business processing over £100,000 per month and need a single enterprise payment provider, Worldpay's negotiated rates and consolidated services may justify the complexity. But even at this scale, many businesses find that a combination of a modern payment link provider and GoCardless for Direct Debits gives them better technology, faster onboarding, and more flexibility than a traditional merchant services agreement. The payment link market in the UK is maturing rapidly. Five years ago, the choice was essentially PayPal or bank transfer. Today, there are strong options at every price point and business size. The key is matching the provider to your specific needs -- particularly around team access, delivery channels, and the balance between simplicity and features. How Payment Link Services Work Choose a Provider Compare features, fees, and payout speed. Create Links Generate payment links from a dashboard or app. Send to Customers Share by SMS, email, WhatsApp, or embed on your site. Customers pay by card. Money settles to your bank. ## Frequently Asked Questions **What is the cheapest payment link service in the UK?** For transaction fees alone, Stripe and Square are among the cheapest at 1.4% + 20p for UK consumer cards. SumUp charges a flat 1.69% with no fixed per-transaction fee, which can be cheaper for very small payments. However, total cost depends on more than transaction fees -- monthly subscription charges, team user fees, and settlement speed all affect the real cost. A provider charging 1.5% with no monthly fee may be cheaper overall than one charging 1.2% plus £30 per month, depending on your transaction volume. **Which payment link provider is best for small businesses?** It depends on the type of small business. For sole traders who need a simple, no-monthly-fee option, SumUp or Stripe Payment Links work well. For small businesses with a team (5-20 staff) who need multiple people sending payment links, Shuttle Links Checkout is designed specifically for this -- with multi-user access, branded checkout pages, and SMS/WhatsApp delivery. For businesses that primarily send invoices and want payment links attached, Square Invoices is a strong choice. There is no single best option -- it depends on your team size, volume, and how you interact with customers. **Can I use payment links with my existing bank?** Payment links work alongside your existing bank account, not instead of it. When a customer pays via a payment link, the funds are processed by the payment provider and then settled into your existing business bank account -- typically within 1-3 business days. You do not need to open a new bank account or switch banks. The payment provider acts as the intermediary, handling the card processing and depositing the cleared funds into whatever bank account you specify during setup. **What transaction fees do payment link services charge?** UK payment link services typically charge between 1.4% and 2.9% per transaction, plus a fixed fee of 0-30p per transaction. For UK-issued consumer debit and credit cards, most providers charge around 1.4-1.75% + 20p. European cards are slightly higher, and non-European or corporate cards can be 2.5-2.9% + 20p. Some providers charge a flat rate regardless of card type (SumUp at 1.69%), which simplifies pricing but may be more expensive for domestic card payments. Always check the blended rate for your typical card mix, not just the headline rate. **Do I need a merchant account to use payment links?** No. Modern payment link providers like Stripe, Square, SumUp, PayPal, and Shuttle act as payment facilitators, which means they process payments under their own merchant account. You sign up, verify your identity and business details, and start accepting payments -- usually within 24-48 hours. You do not need a separate merchant account from a bank. Traditional providers like Worldpay do require a merchant account, which involves a longer application process (1-4 weeks) and typically a contract commitment. ## Related Guides Keep Reading ### Payment Links Guide How to send payment links to customers. ### Without a Website Accept payments without a website. ### Without a Card Machine Ditch the card machine for payment links. ## Start collecting payments today Send payment links by SMS, email, or WhatsApp. Your customers pay online -- you get paid the same day. ## Links - [Payment Links Guide How to send payment links to customers.](/guides/take-payments-online/payment-links/) - [Without a Website Accept payments without a website.](/guides/take-payments-online/without-a-website/) - [Without a Card Machine Ditch the card machine for payment links.](/guides/take-payments-online/without-card-machine/) - [Try Shuttle Links](/use-cases/payment-links/?utm_source=guide&utm_medium=cta&utm_campaign=take-payments-online) --- URL: https://www.shuttleglobal.com/guides/take-payments-online/cleaning/ --- # How to Take Payments for Your Cleaning Business | Shuttle > Payment collection guide for cleaning businesses. Compare payment links, Direct Debit, card machines, and invoicing for cleaning companies with teams of cleaners. # How to Take Payments for Your Cleaning Business Your cleaners clean -- your payment system should handle the rest Last updated: February 2026 ## The Payment Problem That Grows With Every Cleaner You Hire When you started your cleaning business, payment was simple. You cleaned a house, the client left cash on the kitchen table or transferred the money that evening. You knew every client by name, and if someone forgot to pay, you mentioned it at the next visit. No system needed -- it just worked. Then you hired your second cleaner. Then your fifth. Now you have a team of twelve cleaners, each doing three to four cleans a day. That is somewhere between thirty-six and forty-eight individual payments every single day. Two hundred or more per week. Over a thousand per month. And the system that worked when it was just you no longer works at all. Here is what typically happens. Your cleaners finish their jobs and your office sends invoices -- either by email or, in too many businesses, still on paper. Some clients pay straight away. Some pay within a week. Some need a reminder. Some need two reminders. Some need a phone call. A few need a stern letter before they pay. And through all of this, your office team -- who should be scheduling jobs, managing clients, and growing the business -- is spending hours every week chasing money for work that was completed days or weeks ago. The maths is punishing. If just 15% of your clients pay late (and for most cleaning businesses, the figure is higher), and your team spends an average of ten minutes per chase across reminder emails, texts, and calls, a business with two hundred weekly clients is losing over five hours of admin time every week to payment chasing alone. That is a part-time salary spent on asking people to pay for services they have already received. The recurring nature of cleaning makes this particularly painful. A plumber who does a one-off job and does not get paid has lost one payment. A cleaning business that has a client who pays two weeks late every time has a permanent cash flow drag -- and multiply that across twenty or thirty slow-paying clients, and you are consistently carrying thousands of pounds in completed but unpaid work. Cash payments -- still common in residential cleaning -- create their own problems. Cash gets lost, amounts get disputed, and there is no automatic record for your accounts. Your cleaners become responsible for handling money, which is a distraction from the job and a source of potential conflict. And cash makes it nearly impossible to grow beyond a certain size, because you cannot track, reconcile, or forecast cash income at scale. ## Your Options for Collecting Cleaning Payments The right payment method for your cleaning business depends on your client mix (residential vs. commercial), the size of your team, and whether your revenue is primarily recurring or one-off. Here is an honest comparison of every realistic option. ### Payment Links A payment link is a URL that opens a secure checkout page where your customer pays by card. Your cleaner finishes a job, a link is sent by text message, and the customer pays on their phone. No hardware, no cash, no invoice to chase. For cleaning businesses, payment links solve the core problem: collecting payment at the point of service, even when the customer is not present. This is critical for cleaning because a large proportion of residential cleans happen while the homeowner is at work. Your cleaner cannot collect a card tap or cash from someone who is not there. But a text message reaches them wherever they are, and the payment link converts the completed clean into collected revenue within minutes rather than weeks. Payment links work across every type of cleaning work. Regular weekly residential cleans, fortnightly deep cleans, one-off end-of-tenancy jobs, commercial office cleaning -- the same system handles all of them. The amount and description change per link, but the workflow is identical: clean complete, link sent, payment received. For a cleaning business with fifteen cleaners doing an average of three and a half jobs each per day, payment links eliminate the need to send, track, and chase approximately fifty invoices daily. Over a month, that is over a thousand invoices your office never needs to produce, monitor, or follow up on. Best for: per-clean billing, teams of cleaners, clients who are not present during the clean, variable amounts, one-off jobs. Weakness: requires the customer to actively tap and pay (though immediate sending after cleaning produces high completion rates). ### Direct Debit For cleaning businesses with a significant base of recurring clients paying the same amount on the same schedule -- weekly residential cleans at £50, monthly office cleaning at £400 -- Direct Debit is the lowest-effort collection method. The customer authorises the payment once, and it collects automatically. No invoice, no reminder, no link, no interaction at all. GoCardless is the most common Direct Debit provider for cleaning businesses. Per-transaction fees are typically lower than card payment fees (around 1-2%), and the automatic collection means your office does not touch these payments at all. For a cleaning business with eighty regular weekly clients on Direct Debit, that is eighty payments collected automatically every week -- a transformative reduction in admin workload. The downsides are setup friction and inflexibility. Each customer needs to complete a Direct Debit mandate (an online form authorising the payment), which takes more effort than simply paying a link. Some residential customers are uncomfortable authorising ongoing access to their bank account. And if the amount changes -- an extra room cleaned, a different schedule for a holiday week, a product charge -- you need to adjust the mandate or collect the difference separately. Direct Debit payments also take two to three working days to reach your account, and customers have a right to request a refund through their bank for a period after the payment. This is rarely a problem in practice, but it means Direct Debit payments are not as immediately "final" as card payments. Best for: fixed recurring amounts, high-volume regular clients, reducing admin overhead. Weakness: inflexible for variable amounts, setup friction, slower to clear, not suitable for one-off jobs. ### Card Machines Portable card terminals from SumUp, Zettle, Square, and others let customers tap their card for instant payment. They are straightforward, familiar, and the payment confirms immediately. For cleaning businesses, card machines are almost entirely impractical. The fundamental issue is that your cleaners are cleaning -- they are inside a customer's home or office, doing physical work, often with wet hands, moving between rooms, using chemical products. Expecting them to also carry, maintain, and operate a card terminal is unrealistic. Card machines need charging, they need mobile signal or WiFi, and they add a step to the end of every job that your cleaners should not be responsible for. More importantly, a large proportion of cleaning clients are not present during the clean. A card machine is useless if there is no card to tap. For office cleaning that happens in the evening after staff have left, for residential cleans during working hours, for Airbnb turnovers between guests -- the customer simply is not there. If you are a sole cleaner doing a small number of jobs per day where the client is always home, a single card machine can work. But for any cleaning business with a team, card machines are not a viable primary payment method. Best for: sole operators with clients who are always present. Weakness: impractical for teams, useless when the client is absent, requires hardware per cleaner, ongoing costs. ### Bank Transfers Bank transfer is what most cleaning businesses start with and what many continue to use long after they have outgrown it. You send an invoice (or just a text message) with your sort code and account number, and the customer transfers the money when they choose to. For cleaning, the chase rate on bank transfers is particularly high. The perceived value of a regular clean is lower than, say, a plumbing repair or an electrician visit. A customer who has just had a blocked drain fixed will pay promptly because the relief is immediate and tangible. A customer whose house was cleaned while they were at work comes home to a tidy house and -- because tidiness is the default expectation -- the urgency to pay is lower. The result is that cleaning invoices requesting bank transfers consistently have some of the longest average payment times of any trade. At scale, bank transfer reconciliation is also a significant problem. When you have fifty clients all paying by transfer with varying reference formats (some use their name, some use their address, some use nothing), matching payments to clients becomes a manual, error-prone process. Your bookkeeper or accountant spends hours every month reconciling bank statements against your client list. Best for: businesses with a handful of trusted, long-term clients. Weakness: high chase rate, no urgency mechanism, painful reconciliation at scale, no automation. ### Invoicing Software with Payment Links Accounting tools like Xero, QuickBooks, and FreshBooks -- as well as cleaning-specific software like ZenMaid, Jobber, and Launch27 -- can send invoices with embedded payment buttons. The customer opens the invoice email, clicks "Pay Now," and pays by card. This is a meaningful step up from manual invoicing, and if you already use accounting software, enabling the payment feature is straightforward. The payment is automatically reconciled against the invoice, saving your bookkeeper significant time. The limitation is delivery. Invoicing software typically sends payment requests by email. For cleaning clients -- who are often residential customers checking email sporadically -- this is slower than SMS. A text message is read within three minutes on average. An invoice email might sit in an inbox for days, especially if it lands in a promotions or spam folder. The payment rate is better than a plain invoice, but worse than a payment link sent by text immediately after the clean. The best approach for many cleaning businesses is to use both: invoicing software for accounting, record-keeping, and commercial clients who require formal invoices, and standalone payment links by SMS for the actual collection from residential clients. Best for: businesses already using accounting software, commercial clients requiring invoices. Weakness: email delivery is slower than SMS, less effective for residential clients. ## How Payment Links Work for Cleaning Businesses The practical workflow for a cleaning business using payment links depends on whether you are billing per clean, per week, or per month. Here is how it works for each scenario your business handles. Scenario 1: Per-clean billing (residential). Sarah, one of your team of fifteen cleaners, finishes a two-hour regular clean at a residential property. The homeowner is at work. Sarah locks up with the spare key, and the system sends a payment link to the customer by text message: "Hi Mrs Chen, your clean at 14 Birch Close is complete. Pay £60 here: [link]." Mrs Chen sees the text on her phone at work, taps the link, enters her card details, and the payment is done. Total time from clean completion to payment: typically under ten minutes. No invoice generated, no chase required, no office involvement. Scenario 2: End-of-tenancy deep clean. A letting agent books an end-of-tenancy clean for a three-bedroom flat. Your quote is £320. You send a payment link for a £100 deposit when the booking is confirmed -- this secures the slot in your schedule and reduces the risk of cancellation. On the day, your team completes the clean, and a second payment link for the remaining £220 is sent to the letting agent. For letting agents who book regularly, you build a trusted relationship where payment becomes automatic and fast. Scenario 3: Commercial office cleaning. You clean an accountancy firm's offices three evenings per week. The monthly total is £1,200. At the end of each month, you send a payment link for £1,200 with a clear description. The office manager pays by card. If the firm requires a formal invoice for their records, you send the invoice from your accounting software and the payment link separately -- or use accounting software that includes a payment button in the invoice email. Scenario 4: Airbnb turnover cleaning. You handle turnover cleans for a property management company with twelve Airbnb listings. The volume and timing varies -- some weeks you do fifteen turnovers, some weeks you do six. After each clean, a payment link is sent for the agreed amount. The property management company pays per clean, and both parties have a complete record of every job and every payment without any monthly invoicing or reconciliation. The common pattern across all scenarios is that payment collection happens automatically at the point of service completion. Your office does not send invoices. Your cleaners do not handle money. The system sends the request, the customer pays, and your dashboard updates. For a cleaning business processing forty to sixty payments per day, this is the difference between having a full-time person dedicated to billing and having no billing function at all. The conversion data is compelling. Payment links sent by text within five minutes of a clean being completed typically achieve a same-day payment rate of 85-95%. Invoices sent by email at the end of the week achieve a same-week payment rate of 50-65%. For a cleaning business doing a thousand cleans per month, that difference represents a cash flow improvement of tens of thousands of pounds. ## What to Look For in a Payment System for Cleaning Businesses Cleaning businesses have unique characteristics -- high payment volumes, recurring relationships, absent customers, and teams of staff -- that mean generic payment advice does not always apply. Here is what specifically matters when choosing a payment system for a cleaning operation. Volume handling. A cleaning business with fifteen cleaners can generate fifty or more payments per day. Your payment system needs to handle this volume without bottlenecks. Check that there are no daily transaction limits, that the dashboard remains usable at high volumes, and that reporting can handle hundreds of transactions per week without slowing down. SMS as the primary delivery channel. Email works for commercial clients who sit at desks. For residential cleaning clients -- the majority of most cleaning businesses' revenue -- text message is the only reliable delivery channel. Make sure your payment provider offers SMS delivery as a first-class feature, not an afterthought. Check the SMS delivery rate, the speed, and whether messages are sent from a branded sender name rather than a random number. No hardware requirement. Your cleaners should not carry, charge, or operate payment hardware. They should clean. Any payment system that requires your cleaners to do anything beyond their normal routine is a system that will not be used consistently. The ideal setup is entirely invisible to your cleaning team -- the payment request is triggered automatically when the job is marked complete, with no action required from the cleaner. Recurring payment support. Most cleaning revenue is recurring. Your payment system must handle this -- either through automated payment link scheduling (send a link every Tuesday after Mrs Jones's clean) or Direct Debit integration for fixed-amount regular clients. Managing recurring billing manually at scale is unsustainable. Per-transaction pricing. Cleaning businesses have variable revenue -- seasonal dips (fewer cleans in December and January when clients cancel for holidays), lost clients, new clients. A payment system with fixed monthly fees penalises you during slow periods. Per-transaction pricing means your payment costs scale exactly with your revenue. Check for hidden fees: some providers charge per SMS, per user, per payout, or have minimum monthly charges buried in the terms. Team management and visibility. You need to know which cleaners' jobs are paid and which are outstanding. A payment system with team features -- individual accounts for each cleaner or crew, with a centralised office dashboard -- gives you real-time visibility without requiring your cleaners to report back on payments. Look for the ability to filter by cleaner, by date, by status (paid, pending, overdue), and by client. Client communication. The payment link message is a touchpoint with your customer. A well-branded, clear payment request ("Your clean at [address] is complete -- pay here") reinforces professionalism. A generic, unbranded payment page creates hesitation. Check that you can customise the message text, the payment page branding, and the confirmation message the customer receives after paying. Payout speed. Cleaning businesses typically have tight margins and regular payroll commitments (your cleaners need paying every week or fortnight regardless of whether clients have paid you). Next-day or same-day payouts to your bank account smooth out cash flow and reduce the risk of shortfalls on payroll day. Providers that hold funds for three to five days create unnecessary cash flow pressure. Reporting that supports business decisions. Good payment data tells you more than just who has paid. It tells you which clients consistently pay late (so you can move them to Direct Debit or drop them), which days generate the most revenue (so you can optimise scheduling), and what your average payment speed is (so you can forecast cash flow accurately). Look for exportable reports and, ideally, integration with your accounting software. How Your Cleaning Team Gets Paid Job Completed Your cleaning team finishes the scheduled clean. Auto-Send Link Payment link sent automatically or by the team lead. Customer Pays Customer pays by card via the secure link. Payment Tracked Office sees the payment instantly. No invoicing delays. ## Frequently Asked Questions **What is the best way for cleaning companies to collect recurring payments?** For fixed recurring amounts (same client, same clean, same price every week), Direct Debit is the most efficient -- the payment collects automatically and neither you nor the customer needs to do anything. For clients where the amount varies per visit (additional deep cleaning, extra rooms, product charges), payment links sent after each clean give you the flexibility to bill the correct amount without constant Direct Debit adjustments. **Can my cleaners collect payment after each clean?** Yes. With payment links, your cleaners can send a payment request via text message as they finish each job. The customer receives a link, taps it, pays by card, and both parties get instant confirmation. No cash, no card machine, no paper invoice. This works whether the customer is present or not -- which matters for cleaning, since many clients are at work when your team cleans their home. **How do I reduce payment chasing for my cleaning business?** The most effective approach is collecting payment at the point of service rather than invoicing after the fact. Payment links sent immediately after each clean -- while the value of the service is fresh in the customer's mind -- convert at much higher rates than invoices sent days later. For recurring clients, Direct Debit eliminates chasing entirely by collecting automatically. Combining both methods (Direct Debit for regular weekly clients, payment links for variable or one-off work) can reduce your outstanding payments by 80% or more. **What payment system works for both residential and commercial cleaning?** Payment links cover both. For residential clients, send a link by text after each clean. For commercial clients, send a link after each visit or at agreed billing points (weekly, monthly). Commercial clients who require formal invoices can receive an invoice with an embedded payment link, combining the documentation they need with the convenience of instant card payment. Direct Debit works well for both segments when the amount is fixed and recurring. **How do end-of-tenancy cleaning companies collect payment?** End-of-tenancy cleaning is typically a one-off, higher-value job (£200-500+). The best approach is collecting a deposit via payment link when the booking is confirmed (to reduce no-shows) and the balance via payment link on completion. Some companies collect the full amount upfront. Payment links work well here because the letting agent or tenant can pay remotely -- they do not need to be present when the cleaning is done. ## Related Guides Keep Reading ### Landscaping Businesses Similar recurring payment challenges. ### Without a Card Machine Your cleaners don't need card machines. How to send payment links to customers. ## Start collecting payments today Send payment links by SMS, email, or WhatsApp. Your customers pay online -- you get paid the same day. ## Links - [Landscaping Businesses Similar recurring payment challenges.](/guides/take-payments-online/landscaping/) - [Without a Card Machine Your cleaners don't need card machines.](/guides/take-payments-online/without-card-machine/) - [Payment Links How to send payment links to customers.](/guides/take-payments-online/payment-links/) - [Get Started](/use-cases/payment-links/?utm_source=guide&utm_medium=cta&utm_campaign=take-payments-online) --- URL: https://www.shuttleglobal.com/guides/take-payments-online/construction/ --- # Payment Systems for Contractors & Construction Businesses (2026 Guide) | Shuttle > The 2026 payment system guide for contractors and construction businesses. Handle stage payments, deposits, retention, and final invoicing without the chase. # Payment Systems for Contractors & Construction Businesses (2026 Guide) Stage payments, deposits, and final invoicing -- without the admin headache Last updated: February 2026 ## Quick Answer: What's the Best Payment System for Contractors? For most contractors and construction businesses in 2026, the best payment system combines payment links for stage payments and deposits with bank transfer as a fallback for very large transactions and a Voice Checkout option for phone-based deposit collection. This is what works in practice across general contractors, specialist subcontractors, and tradespeople running renovation, extension, or build projects. The shortlist: - Payment links -- for deposits, stage payments, variations, and final balances. Sent by text, paid by card on a branded checkout page, instant confirmation, full audit trail per project. - Bank transfer -- for very large stage payments above the client's card limit (typically £25,000+). Free but slow and harder to reconcile. - Voice Checkout -- for collecting deposits during the booking call without taking card details verbally. PCI-compliant, no card data ever touches your office. - Card machines -- generally a poor fit for construction. Site conditions damage devices, signal is unreliable, and transaction limits get in the way of typical stage payment values. - Invoice factoring -- useful only if you're stuck on 60-90 day client payment terms. Fixing your collection method first is usually cheaper. The rest of this guide explains why this combination works, with concrete examples from real construction workflows. ## The Problem: Construction Payment Is Broken Construction has the worst late payment record of any industry in the UK. The average construction invoice takes 45 days to be paid, and for smaller contractors and subcontractors, that figure is often worse. A 2023 survey by the Federation of Master Builders found that 27% of construction SMEs had experienced payment delays of 60 days or more in the previous 12 months. If you run a construction business -- whether you are a general contractor, specialist subcontractor, or sole trader doing extensions and renovations -- you already know the pain. You finish a stage of work, send an invoice by email or post, and then wait. And wait. The client says they did not receive it. Or they want to query something. Or they are waiting for their own payment before they can pay you. Meanwhile, your material suppliers want paying on 30-day terms, your team needs wages on Friday, and your cash flow is stretched to breaking point. The fundamental problem is that construction payment processes have not changed in decades. Stage payments are tracked on spreadsheets or scribbled on paper. Invoices go out as PDFs attached to emails. Payment is by bank transfer, which means the client has to manually set up a payee, type in your account details, and choose to make the payment. Every step introduces delay and friction. When you multiply this across multiple projects running simultaneously -- each with their own stage payment schedules, retention clauses, and variation orders -- managing payment becomes a full-time job. There is a better way. Modern payment methods designed for service businesses can dramatically reduce the time between completing work and getting paid, while creating the clear audit trail that construction projects demand. ## Your Options for Collecting Construction Payments ### Bank Transfer (BACS / Faster Payments) Bank transfer is the default payment method in UK construction. It is free to send and receive, handles large amounts without issue, and every business has a bank account. For these reasons, it will likely remain part of how construction companies get paid for the foreseeable future. However, bank transfer puts the effort entirely on the client. They need your sort code and account number, they need to log into their banking app, they need to set you up as a payee (which can take 24 hours for the first payment), and they need to reference the payment correctly so you can match it to the right project and stage. For a busy property developer running six projects simultaneously, paying a dozen contractors each on different stage schedules, this is a real burden -- and it is your invoices that drop to the bottom of the pile. The other issue with bank transfers is the lack of a shared record. You know you sent an invoice. You think the client received it. But you cannot prove when they opened it, whether they saw the correct amount, or when they initiated payment. This ambiguity is what fuels disputes. ### Payment Links Payment links are the modern alternative that works particularly well for construction stage payments. When a stage is complete and signed off, you send the client a link by text message, email, or WhatsApp. They tap the link, see a branded checkout page showing the stage description and amount, and pay by card. The payment is confirmed instantly and both parties receive a receipt. For construction, this has several specific advantages. First, you can send the link the moment a stage is complete -- while the client is still on site, or immediately after they have seen the work. Catching the client at the point of satisfaction dramatically improves payment speed. Second, payment links create a timestamped audit trail: you can see when the link was sent, when it was opened, and when payment was made. This is invaluable for dispute resolution. Third, your office team can send links on behalf of site managers, meaning the person doing the work does not have to handle the payment admin. The main limitation for construction is transaction size. Card payments are subject to the client's card limit, which for debit cards is typically £5,000-£25,000 per day. For a £3,000 stage payment on a kitchen installation, this is no problem. For a £40,000 stage payment on a new build, the client may need to use a credit card or make the payment in parts. Some payment link providers offer higher limits or alternative payment methods alongside card payments to handle this. ### Card Machines Card machines are common in retail and hospitality, but they are a poor fit for construction. The transaction values in construction regularly exceed contactless limits and even standard card limits. A card machine rental costs £15-30 per month per device, and on a construction site -- with dust, rain, and the general chaos of a building project -- terminals get damaged or lost. Battery life is another problem: a card machine left in a van all day in winter may not hold charge. And connectivity is unreliable in basements, scaffolded buildings, and rural sites. Some smaller trade businesses (handymen, locksmiths, plumbers doing one-off callouts) do use card machines for jobs under £1,000 with some success. But for construction businesses managing projects with multiple stage payments, a card machine solves the wrong problem. ### Invoice Factoring Invoice factoring is common in construction precisely because late payment is so endemic. A factoring company advances you 80-90% of your invoice value immediately, then collects the full amount from your client and pays you the balance minus their fee (typically 1-5% of the invoice value plus an annual facility charge). Factoring solves the cash flow problem but at a significant cost. On a £100,000 contract, factoring fees can easily reach £3,000-£5,000. It also means a third party is contacting your clients about payment, which can affect the relationship. Factoring makes sense for large subcontractors dealing with main contractors who have 60-90 day payment terms, but for businesses dealing directly with homeowners or commercial clients, improving your payment collection method is a cheaper and simpler first step. ### Cheques Still surprisingly common in construction, especially with older clients and on larger projects. Cheques are slow (3-5 working days to clear), can bounce, and require a trip to the bank. They are declining year on year and most payment providers now recommend moving clients away from cheques entirely. If you are still accepting cheques as a significant proportion of your payments, any digital method will be an improvement. ## How Payment Links Work for Construction Businesses Payment links are particularly well-suited to the way construction businesses operate because they mirror the stage payment model that the industry already uses. Here is how a typical construction payment flow works with payment links. You agree a payment schedule with the client before work begins -- for example, 10% deposit, 25% at foundations, 25% at first fix, 25% at second fix, and 15% at completion (with a 5% retention). Each stage has a clear description and agreed value. When you complete the foundations and the client (or their architect, or the building control officer) signs the stage off, your office sends a payment link for 25% of the contract value. The link includes a description like "Stage 2 -- Foundations complete -- 14 Acacia Avenue" so the client knows exactly what they are paying for. The client receives the link by text or email, taps it, and pays by card on a branded checkout page. You receive confirmation within seconds and your records update automatically. For your office, this means no more chasing. No more "I didn't get the invoice." No more calling the client three weeks later to ask if they plan to pay. The link either gets paid or it does not, and you have a clear record either way. For businesses managing multiple projects simultaneously, this is transformative. Instead of a spreadsheet tracking which invoices have been sent, which have been acknowledged, and which have been paid, you have a dashboard showing real-time payment status across all your projects. Your quantity surveyor or office manager can see at a glance which stages are paid, which are outstanding, and which are overdue. Payment links also handle variation orders cleanly. When the client agrees to an additional cost -- say, upgrading the kitchen worktops or adding an extra socket -- you create a new payment link for the variation amount with a clear description. This keeps variations separate from the main stage payments, reducing disputes at the end of the project. ## Taking Payments Over the Phone Phone payments are relevant for construction businesses in specific scenarios. When a homeowner calls your office to pay a deposit for a small job -- a new bathroom, a driveway, a loft conversion -- taking the payment there and then, while they are motivated, significantly reduces the chance of them going with a competitor. Traditionally, taking card payments over the phone means asking the customer to read out their card number, expiry date, and CVC while your office staff types it into a terminal. This is a PCI compliance risk: if you write down or store card details, you are liable for any data breach. Most construction companies that take phone payments are technically non-compliant without realising it. Voice Checkout technology solves this by letting the customer enter their card details using their phone keypad during the call. Your staff never hear or see the card details, which means full PCI compliance without any additional security infrastructure. For a construction office that handles 10-20 deposit calls per week, this removes a genuine compliance risk while making the payment process faster and more professional. That said, for larger stage payments on active projects, payment links sent by text are usually more appropriate. The client can pay when they are ready, review the amount and description, and there is a clear paper trail of the request and payment. ## What to Look For in a Payment Solution for Construction Construction businesses have specific requirements that not every payment provider meets. Here is what to evaluate. High transaction limits. Construction payments are often larger than those in other service industries. Check whether your provider limits individual transactions or daily totals. A provider that caps transactions at £1,000 is useless for a business that routinely collects £5,000-£20,000 stage payments. Look for providers that support transactions of at least £10,000 or that offer flexible limits based on your business profile. Clear payment descriptions. Every payment link you send should include a description that identifies the project, the stage, and the work covered. This is not just good practice -- it is your first line of defence in a dispute. If a client claims they paid for work that was not completed, a payment link that says "Stage 3 -- First Fix Electrics and Plumbing -- 14 Acacia Avenue" is far stronger evidence than a bank transfer reference reading "PAYMENT". Team access. In a construction business with 5-20+ staff, multiple people may need to send payment requests. Site managers need to trigger payment collection when a stage is complete. The office team needs to see the status of all payments across all projects. The owner needs a financial overview. Look for a provider that supports multiple users with appropriate permissions rather than one that is tied to a single login. Speed of payout. Cash flow is everything in construction. If your payment provider holds funds for 7-14 days before paying out to your bank account, you have not really improved on the bank transfer model. Look for next-day or same-day settlement. The difference between receiving funds in 1 day versus 7 days can be the difference between making payroll and not. Audit trail and reporting. Construction projects are audited -- sometimes by clients, sometimes by quantity surveyors, sometimes by HMRC. Having a digital record of every payment request sent, every payment received, and every outstanding balance makes compliance and dispute resolution vastly simpler. Look for providers that offer downloadable reports and per-project payment histories. Dispute handling. The construction industry is inherently disputatious. Snagging lists, defective work claims, and arguments over variations are part of life. Your payment provider should have a clear process for handling chargebacks and disputes, and the evidence from your payment links (timestamps, descriptions, delivery confirmation) should support your position when disputes arise. Payment links offer construction businesses a genuine step change in how they collect stage payments, deposits, and final invoices. They do not eliminate every payment challenge the industry faces -- very large payments may still need bank transfers, and clients on 60-day contractual terms may still be slow -- but for the majority of payment interactions between construction companies and their clients, they are faster, cheaper, and more reliable than the status quo. How Construction Payment Collection Works Contract Signed Agree payment schedule -- deposit, stage payments, retention. Collect Deposit Send a payment link for the deposit before work begins. Stage Payments Send links at each milestone -- foundations, first fix, completion. Final Balance Collect the balance on handover. Full payment trail recorded. ## Frequently Asked Questions **How do construction companies collect stage payments?** Most construction companies collect stage payments by issuing invoices at agreed project milestones -- such as after foundations, first fix, or completion. Traditionally this means sending a PDF invoice and waiting for a bank transfer. Payment links offer a faster alternative: send a secure link by text or email the moment a stage is signed off, and the client pays immediately by card. This removes the typical 30-60 day wait and creates a timestamped record of every payment. **What is the best way to collect deposits for building work?** The best method depends on the deposit amount. For deposits under £5,000, payment links or card payments work well -- the client clicks a link, pays by card, and both parties have an instant receipt. For larger deposits above £10,000, bank transfers remain common because card limits can restrict single transactions. However, some payment link providers support higher transaction limits specifically for construction and trade businesses, making it possible to collect even large deposits digitally. **Can I take large payments by card for construction projects?** Yes, but there are limits to be aware of. Most consumer debit cards have daily spending limits between £5,000 and £25,000, while credit cards vary by provider and creditworthiness. Card machines often impose their own per-transaction limits on top of this. Payment links can support higher individual transaction values because the payment is processed online rather than through a terminal, though you should check your provider's maximum transaction limit. For very large payments (£50,000+), bank transfer may still be necessary. **How do I handle retention payments in construction?** Retention payments -- typically 2.5% to 5% of the contract value held back until a defects liability period ends -- are one of the trickiest parts of construction payment. The key is having a clear record of the original contract value, each stage payment made, and the retention amount calculated. Payment links help because every transaction is logged digitally. When the retention period ends (usually 6-12 months after practical completion), you can send a final payment link for the exact retention amount with a clear description, creating an auditable record. **What payment method reduces late payment in construction?** Payment links have the strongest track record for reducing late payment because they remove friction. The client receives a link on their phone, taps it, and pays in under a minute. There is no 'I didn't receive the invoice' excuse, no waiting for a cheque to clear, and no ambiguity about bank details. Studies show that digital payment requests are settled significantly faster than traditional invoices. For construction specifically, sending a payment link immediately when a stage is signed off -- while the client is still on site or has just seen the completed work -- dramatically improves collection speed. ## Related Guides Keep Reading ### Collecting Deposits How to collect deposits before starting projects. ### Installation Businesses Deposits on the closing call, balance by link -- for installers. Send stage payment requests to clients. ## Start collecting payments today Send payment links by SMS, email, or WhatsApp. Your customers pay online -- you get paid the same day. ## Links - [Collecting Deposits How to collect deposits before starting projects.](/guides/take-payments-online/deposits/) - [Installation Businesses Deposits on the closing call, balance by link -- for installers.](/guides/take-payments-online/installations/) - [Payment Links Send stage payment requests to clients.](/guides/take-payments-online/payment-links/) - [Get Started](/use-cases/payment-links/?utm_source=guide&utm_medium=cta&utm_campaign=take-payments-online) --- URL: https://www.shuttleglobal.com/guides/take-payments-online/deposits/ --- # How to Collect Deposits Before Starting Work | Shuttle > Protect your business by collecting deposits before starting work. Learn how to send deposit requests via payment links, take deposits over the phone, and set the right deposit amount. # How to Collect Deposits Before Starting Work Protect your cash flow and reduce no-shows by collecting deposits upfront Last updated: February 2026 ## The Problem: Starting Work Without a Deposit Is a Gamble Every service business owner has a story about the job that went wrong. Your team of joiners drives an hour to a kitchen installation only to find the customer isn't home. Your electricians buy £600 of materials for a rewiring job, and the customer cancels the morning of. Your cleaning team blocks out an entire day for a deep clean, the client no-shows, and those hours can't be filled. Without a deposit, your business absorbs all the risk. You've committed time, resources, and materials based on nothing more than a verbal agreement or a text message saying "yes, let's go ahead." The customer has zero financial commitment to the booking. If something better comes along, or they simply change their mind, there's nothing holding them to the appointment. The numbers tell a painful story. Trade businesses report no-show rates of 5% to 15% depending on the industry. For a business with 20 bookings a week, that's 1 to 3 wasted trips, plus the lost revenue from jobs you could have scheduled in those slots. Over a year, the cost of no-shows can run into thousands of pounds -- money that a simple deposit would have protected. Beyond no-shows, deposits solve the cash flow problem that plagues project-based businesses. If your team of builders is starting a £15,000 bathroom renovation, you'll spend thousands on materials before the customer pays a penny. A deposit ensures you're not funding the customer's project out of your own pocket. The good news: collecting deposits has never been easier. Modern payment tools mean you can request and receive a deposit in minutes -- not days. The challenge isn't the technology; it's knowing the right approach for your business. ## Your Options for Collecting Deposits There are several ways to collect a deposit before work begins. Each has trade-offs in speed, convenience, and reliability. Here's a straightforward comparison. ### Payment Links (Send by SMS, Email, or WhatsApp) The fastest and most reliable method. You create a payment link for the deposit amount through your payment provider, add a description ("Deposit -- bathroom renovation, 24 Maple Drive"), and send it to the customer by text message, email, or WhatsApp. The customer taps the link, enters their card details, and pays. Payment links are ideal for deposits because of the timing. The best moment to collect a deposit is immediately after confirming the booking -- while the customer is engaged and expecting to pay. With a payment link, you can send the request within seconds of confirming the appointment. The customer pays in under a minute. The deposit is secured before the conversation has even finished. For businesses with teams, this approach scales naturally. Your team of roofers has four estimators out doing quotes. Each one can send a deposit link directly from their phone the moment a customer agrees to go ahead. Your office gets a real-time notification when each deposit lands. No chasing, no waiting, no awkward "did they pay?" conversations. The best payment link providers let you brand the checkout page with your business name and logo, which is important for deposits. A customer is more likely to pay a deposit to a professional-looking page that clearly shows your company name than to a generic third-party payment form. ### Phone Payments (Voice Checkout) Many customers call to book. The conversation goes: "Can you come next Tuesday?" -- "Yes, that'll be £1,200 and we take a 25% deposit" -- "Great, how do I pay?" If the answer is "I'll send an invoice" or "We'll take payment on the day," you've missed the moment. The customer hangs up, life happens, and the deposit never materialises. Voice checkout solves this by letting the customer pay their deposit during the booking call itself. Your office staff initiates the payment, the customer enters their card details via their phone keypad, and the deposit is processed before they hang up. It takes 30 to 60 seconds and the booking is secured with payment confirmed. This is particularly effective for customers who prefer the personal touch of a phone call over clicking a link. Older customers, customers booking urgent work, and customers with specific questions about the job often fall into this category. Having the option to take the deposit right there on the call means you never have to let a committed customer leave without paying. ### Bank Transfer The traditional approach: give the customer your bank details and ask them to transfer the deposit amount. No fees, no provider, simple. In theory. In practice, bank transfers for deposits are problematic. You give the customer your sort code and account number. They say they'll do it tonight. Three days later, nothing has appeared. You send a reminder. They apologise and say they'll do it now. Another day passes. Meanwhile, you're holding a slot in your diary for a job that might not happen, turning away other customers for dates that might end up free. Bank transfers put the entire burden on the customer. They have to log into their banking app, find the right section, type in your details correctly, enter the amount, add a reference, and confirm. Each step is a chance for them to get distracted, make an error, or decide to do it later. There's no urgency built into the process. For regular clients who always pay promptly, bank transfers can work. For new customers booking for the first time, they're the least reliable method for securing a deposit. ### Card Machine (Face-to-Face) If your team collects deposits during an in-person visit -- for example, a surveyor takes a deposit at the end of a site visit -- a card machine works. The customer taps their card and the deposit is secured on the spot. The limitation is obvious: it only works when you're face-to-face. If a customer calls to book, you can't use a card machine. If a customer confirms by text, you can't use a card machine. Since most deposits are collected at the point of booking -- often before your team ever visits the site -- the face-to-face requirement makes card machines unsuitable as a primary deposit collection method. Card machines also mean that every team member who might collect a deposit needs a device. For a business with a team of five estimators, that's five card machines to buy, charge, and manage. ### Invoice with Payment Link Some businesses send a formal deposit invoice with a "Pay Now" link embedded. This combines the professionalism of an invoice with the convenience of instant payment. This works well for larger jobs where formal documentation is expected -- a building contractor quoting £30,000 for a house extension will typically send a formal quote and deposit invoice. The customer reviews the document, clicks the payment link, and pays the deposit. For smaller jobs and routine bookings, a full invoice is overkill. A simple payment link with a clear description achieves the same result in a fraction of the time. ## How to Use Payment Links for Deposits -- A Practical Workflow Payment links are the most effective deposit collection method for the majority of service businesses. Here's how to build deposit collection into your standard booking process so it becomes automatic rather than an afterthought. Consider a team of landscape gardeners that books 15 to 20 jobs per week, ranging from £200 garden maintenance visits to £5,000 landscaping projects. Before using payment links, they collected deposits via bank transfer about half the time. The other half of customers either "forgot" or "couldn't find their banking app." No-shows ran at around 10%. Here's the workflow they implemented: - Step 1: Confirm the booking. When a customer confirms they want to go ahead -- whether by phone, text, email, or in person -- the booking is logged in the team's