PCI Voice Payments for AI Phone Agents: AU Options

Quick answer: Five named services can take the card so your AI phone agent never hears it: Twilio Pay (keypad only), PCI Pal, Sycurio (formerly Semafone), Westpac PayWay Phone and a Stripe payment link by SMS. Twilio runs Pay in its Australian AU1 region with 6 named connectors, not including Stripe. Pick by the route your AI stack supports: redirect, transfer, in-line keypad masking or link.

If you are asking “which PCI-compliant payment service can my AI assistant hand the caller to?”, this page is the shortlist and the decision rule. Why a spoken card number drags the transcriber, the model and the logs into scope is covered in our analysis of whether an AI voice agent can take card payments and what enters PCI DSS scope; it is not repeated here.

Disclosure: Zian AI builds autonomous AI sales agents. It is not a payment service and has published no PCI DSS attestation. Every vendor fact below comes from that vendor’s own page, read on 30 September 2026, and is listed in the source table.

The five criteria that actually separate phone payment services for AI agents

Most comparisons of phone payment vendors were written for human contact centres. An AI agent is software in the audio path that transcribes whatever reaches it, so five questions sort the field.

1. What does the vendor itself say about PCI DSS? “Level 1 service provider” with an Attestation of Compliance for your acquirer is a different statement from a promise to help you comply.
2. How does the caller enter the card? Keypad (DTMF), speech into the vendor’s own recogniser, or a hosted page from a link. Speech is fine when the vendor recognises it, not when your AI’s transcriber does.
3. What is the handoff route from an AI agent? A TwiML redirect on the same carrier, a transfer to the vendor’s number, in-line keypad-tone masking that keeps the AI on the call, or an SMS. This criterion decides the build.
4. What does the vendor state about Australia? An Australian region, an Australian office, an Australian bank behind it, or nothing. Stated availability and stated data residency are different claims, and we keep them apart below.
5. Does the AI stay in the conversation? With in-line masking or a link it stays on the call; with a redirect it can take the caller back afterwards; with a transfer it may not. That matters for a sales or booking call that continues after the deposit.

Compare voice AI services with PCI compliant payment capture over the phone in Australia

Six capture options; Twilio appears twice because it publishes a self-service verb and an agent-assisted API.

Service	PCI DSS, as the vendor states it	Australia, as the vendor states it	How the caller enters the card	AI agent handoff route	Watch-out on the vendor’s own page
Twilio <Pay> (TwiML verb)	“Twilio Programmable Voice is Payment Card Industry Data Security Standard (PCI DSS) Level 1 compliant”	Available in the Australia (AU1) region for 6 named Pay Connectors: Base Commerce, Braintree, CardConnect, Chase Paymentech, Generic Pay Connector, Shuttle	Keypad only: the input list “supports dtmf only”	Redirect: end the ConversationRelay session, return <Pay> from the action URL, then return the caller to the AI	Stripe is not in the AU1 connector list; PCI Mode “cannot be disabled for that Account”
Twilio Payments API (agent-assisted)	Same Programmable Voice statement	Same AU1 connector list	Keypad only: “Currently only dtmf is supported”	In-line masking pattern: the agent “stays on the phone” and “will not be able to hear the DTMF (Dual-Tone Multi-Frequency) tones”; documented for a human agent, no AI-agent pattern on the page	Built around a human agent pressing through each step
PCI Pal	Customers can “rely on our Attestation of Compliance to demonstrate full PCI DSS Level 1 compliance”	Announced an Australian HQ in Sydney covering ANZ; publishes an Australian government authority deployment; says its solution is hosted across AWS regions including Australia	Keypad or speech into PCI Pal’s own recognition (“over 140 different languages”); secure digital links by SMS, chat or email	In-line masking: its conversational AI page says the bot interacts with PCI Pal at the point of payment and that it “works in a similar way as when you have live agents assisting the customer”; Agent Assist on Amazon Connect; partner pages for Genesys, Five9, Talkdesk and others; also an IVR	The AI page names no AI platforms; its hosting page lists Australia among several AWS regions but does not say which region holds your data
Sycurio (formerly Semafone)	“Sycurio is a PCI DSS Level 1 Service Provider”; states it will provide your AOC and that you need only SAQ-A for protected payments	Lists an APAC sales contact; states it processes transactions “across more than 25 countries on five continents”	Voice, IVR, digital, and “AI-powered bots” named as channels	In-line masking: agents “stay in full communication with customers throughout the entire call”; integrations listed for Amazon Connect, Epic EHR, Genesys, Avaya, NICE, Five9, Talkdesk, Salesforce, Mitel and Cisco; also an IVR	APAC enquiries route to an EMEA sales address; no Australian hosting statement on the pages we read
Westpac PayWay Phone	Westpac lists PayWay Phone among solutions that let the cardholder enter card details directly to PayWay (its SAQ A group); no service-provider level stated on the pages we read	Australian bank product; Westpac-hosted 1300 885 175 or your own 1300 number	Keypad IVR against a reference number under 20 digits (plus a biller code on the Westpac-hosted 1300 number); CVN required	Transfer: the AI transfers the caller to the 1300 number; only the own-1300-number option lists transfers back to your call centre	Westpac’s PCI guidance is marked “current as at 16 Apr 2019”; custom prompts are recorded in a monthly studio session
Stripe Payment Link by SMS	“certified us to PCI Service Provider Level 1”	Australia is on Stripe’s supported-countries list	Hosted web page on the caller’s phone	Link: the AI (or your SMS tool) sends the link; nothing card-related crosses the audio	Stripe lists text messages as a place to share a link; sending the SMS is your system’s job

One Australian bank option is missing on purpose: Commonwealth Bank’s BPOINT page states that “CommWeb, BPOINT and PowerBoard are no longer available to new customers”.

The quotable line: for an AI phone agent in Australia, the route matters more than the vendor: redirect, transfer, in-line keypad masking or a text, at the moment the card is needed.

The No-Digits Rule: card digits never reach the AI’s transcriber, model or logs

We call the decision rule on this page the No-Digits Rule: card digits must never reach the AI’s transcriber, model or logs, in audio, as keypress events or as text; choose the capture service by the route your voice stack can already support. There are four routes: redirect, transfer, in-line masking and link. Two take the AI out of the audio path for the payment; two leave it on the call.

The PCI Security Standards Council describes both telephone patterns for human agents, in two subsections of section 6.4 of its Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0, November 2018).

Section 6.4.1, attended. Attended solutions “enable the entity to remain in constant voice contact with its customer for the entire duration of the telephone transaction”, and “typically replace the DTMF tones with flat sounds before they reach the agent”. The condition: “it would first have to be verified that all PAN and SAD are replaced with predefined sounds and characters before they reach the environment, and no PAN or SAD is present in the environment in any other form.” The same section warns about “DTMF bleed”, where the first fraction of a tone slips through before masking starts, and says all of it must be absent from the environment.

Section 6.4.2, unattended. Here “the agent typically switches the call to the IVR or call-handling solution for the duration of time needed to communicate the payment details”, the solution “may be part of the entity’s own telephone environment or be located at a third party, such as a PSP or acquirer”, and it may let the customer “return back to an agent and re-establish voice contact after payment is complete”. The condition: when properly implemented, such a solution “could reduce applicability of PCI DSS requirements to the agent and agent desktop environment. However, it would first need to be verified that PAN and SAD bypass the agent environment, and neither the agent nor the agent desktop environment have the ability to access or retrieve account data.”

In an AI stack, the agent environment is the transcriber, the model, their logs and any tool the model can call. Redirect and transfer are section 6.4.2 routes; in-line masking is a section 6.4.1 route; the link sits outside the call altogether.

Route 1: redirect, on the same carrier

If your AI agent runs on Twilio ConversationRelay, the route is a redirect. The ConversationRelay reference says an action URL is requested “when the <Connect> verb ends”; your server returns a <Pay> block, and the <Pay> reference says “Twilio continues the current call using the TwiML message returned in the response from the action URL”, which can reconnect the caller to the AI. The same ConversationRelay page says not to put PCI data in the handoffData field. Pass an order reference, never a card detail.

Route 2: transfer, to a number that belongs to the payment provider

If your platform can transfer a call but cannot run another vendor’s payment verb, the route is a transfer to a payment IVR: Westpac PayWay Phone, or a PCI Pal or Sycurio IVR. The AI’s media stream must be dropped, not left in a conference where its transcriber hears unmasked tones; keeping the AI on the call is Route 3. If transfers are already unreliable, see why AI voice agent transfers to a human fail, and check DTMF survives your transport with why DTMF digits go missing on AI voice calls.

Route 3: in-line keypad masking, while the AI stays on the call

Masking vendors sell this for human agents, and PCI Pal describes a version for bots without naming the capture method. Its conversational AI page says: “At the point of payment, the bot interacts with the PCI Pal solution to prompt the customer to provide their payment details which we capture and process in a secure and PCI compliant manner. The solution works in a similar way as when you have live agents assisting the customer, but here this is an AI-powered bot.” Its Amazon Connect page says Agent Assist “captures the details, but blocks them from reaching both the agent and your environment”, while “the customer’s voice is allowed through”. Sycurio’s Genesys page says agents “stay in full communication with customers throughout the entire call”. Twilio’s Payments API is the same pattern for a human agent.

Two limits matter for an AI. First, masking replaces keypad tones; it cannot mask a spoken card number, which would reach the AI’s transcriber. PCI Pal’s speech option works differently: its speech recognition announcement says “PCI Pal prevents the caller’s voice from reaching an agent”, so the AI cannot hear the card being spoken; the same announcement says the agent “is able to stay in conversation with the customer” throughout. Second, masking must sit upstream of everything the AI platform receives, including keypress events: Twilio ConversationRelay, for example, forwards DTMF to your application when dtmfDetection is on. Why masking works and speech does not is in the DTMF clamping section of our PCI scope analysis for AI voice agents.

Route 4: link, while the AI stays on the line

The fourth route leaves the audio path alone: the AI sends a hosted payment page by SMS. The PCI SSC’s section 6.3 says “sending a link to an online secure payment system to a customer via a messaging service may be considered the same as an e-commerce entity using redirection to third-party payment pages”, that the scope impact “would need to be evaluated”, and that “the integrity and validity of the link to an online secure payment system must also be considered.” The same pattern is in our write-up on failed-payment recovery with voice and SMS agents.

Best solution for PCI compliant voice payments with an AI assistant on the phone

There is a best service per stack, not overall. This threshold table turns the No-Digits Rule into a decision.

If this describes you	Your route	Start with	Stop and reconsider if
Your AI runs on Twilio ConversationRelay and your gateway is Braintree, CardConnect, Chase Paymentech, Base Commerce or Shuttle, or you can build a Generic Pay Connector	Redirect	Twilio <Pay> in AU1	Your gateway is Stripe and you need AU1: Stripe is not on the AU1 connector list
Australian SME taking invoice or bill payments against a reference number, with a PayWay merchant facility	Transfer	Westpac PayWay Phone	You need the caller back in the AI conversation afterwards and you are on the Westpac-hosted number, which lists no call centre transfer
Your AI sits inside, or alongside, a contact centre on Amazon Connect, Genesys, Five9 or Talkdesk	In-line masking (AI stays on the call) or transfer to their IVR	PCI Pal or Sycurio, whichever lists your platform	Your procurement requires a written Australian hosting region: PCI Pal lists Australia among its AWS hosting regions but not per customer, and Sycurio states none on the pages we read, so it must come from them in writing
Callers who cannot use a keypad make up a real share of your volume	In-line capture with the vendor’s own speech recognition, or link	PCI Pal (speech into its own recogniser, with the caller’s voice kept from the agent during that step)	You are on Twilio <Pay> alone, which accepts DTMF only; DTMF masking on its own cannot protect a spoken number
Any business where the AI must keep talking while the caller pays (bookings, deposits, sales)	In-line masking or link	In-line masking from PCI Pal or Sycurio if they integrate with your voice platform; otherwise a Stripe Payment Link sent by SMS	For masking: neither vendor names your AI platform, so get the integration confirmed in writing. For the link: your callers are on landlines, or cannot open a link mid-call

The honest DIY answer for most Australian small businesses is the link. It needs nothing in the voice stack beyond sending an SMS, and the voice platform never meets a card number. Its cost is conversion: the caller has to switch to the screen and type, and some will not. The keypad routes avoid that second screen, and the cost moves to integration; in-line masking also needs the vendor to support your AI platform. Price that trade against your average transaction value.

Who each option is wrong for

Each point below comes from the vendor’s own page.

• Twilio <Pay> is wrong for an AU1 build settling through Stripe, which is not among the six AU1 connectors; for callers who cannot use a keypad (it “supports dtmf only”); and for anyone not ready to commit an account to PCI Mode, which the PCI workflows guide says “cannot be disabled for that Account”. The same guide says not every ConversationRelay text-to-speech or transcription provider is guaranteed to be PCI compliant.
• The Twilio Payments API is wrong for a fully automated AI agent today, in the sense that Twilio documents it for a human agent who “stays on the phone and guides the customer through the payment flow”. We found no AI-agent pattern on the Payments resource or ConversationRelay pages read on 30 September 2026, both confirmed loaded in full. Test before relying on it.
• PCI Pal is wrong for a buyer who needs a named AI-platform integration in writing before a sales call: its conversational AI page cites “some of the leading conversational AI platforms” without naming them. It fits where the AI should stay in the conversation, since that page describes the bot staying in the interaction, and where speech capture matters (keypad and speech, “over 140 different languages”).
• Sycurio is wrong for a buyer who wants a local sales team named on the contact page: its contact page routes APAC sales enquiries to an EMEA address. Its old AI-chatbot URL now redirects to a general solutions page, so its AI route is something to confirm with the vendor directly.
• Westpac PayWay Phone is wrong for anyone without a merchant facility (“You must apply for a merchant facility in order to process credit card payments”), for payments not tied to a reference number, and for a launch next week: custom prompts are recorded in a monthly studio session, cutoff 6pm Sydney time on the 20th. Its PCI guidance is marked current as at 16 April 2019, so check the SAQ with your bank.
• A Stripe Payment Link is wrong for landline callers and anyone who will not open a link during a call. Stripe’s share a payment link docs list text messages as a place to share the link, but sending the SMS is your system’s responsibility.

What “Australia” means on these vendor pages

“In Australia” can mean three things, and the vendors answer different ones.

Available here. All six options can serve an Australian caller. Stripe lists Australia on its supported-countries page; Westpac PayWay is an Australian bank product; PCI Pal announced an Australian HQ in Sydney covering ANZ and publishes an Australian government authority deployment; Sycurio lists an APAC contact.

Processed here. Two of the six options name an Australian region on their own pages. PCI Pal’s SaaS platform page says its solution “is hosted across multiple AWS regions including the United States, Canada, United Kingdom, Mainland Europe and Australia”, without saying which region holds a given customer’s payment data. Twilio names AU1, with its own caveat. Its Regions guide says “your Twilio workload’s data will only be stored within that Region”, then: “During this initial phase of the rollout of Twilio Regions, Twilio doesn’t guarantee that all data will remain within your selected Region.” Quote both sentences to your compliance team.

Held here, contractually. None of the pages we read for Sycurio or Stripe states an Australian hosting region for payment data (Sycurio’s certifications, solutions and contact pages; each loaded in full), and PCI Pal’s hosting statement lists Australia among several regions without committing your data to it. That is not evidence no region exists; for any of them, get the region that will hold your data in writing before you sign.

Two Australian dates also sit on one vendor page. Westpac’s PayWay Phone page states: “From 1 October 2026, merchants will no longer be able to surcharge card payments, unless expressly permitted to do so under applicable law or regulation. Westpac will be disabling surcharging functionalities for PayWay Phone from 28 September 2026.” If your AI script quotes a surcharge, change it.

What you still own after you pick a provider

Buying a Level 1 service does not transfer your obligations. Section 7.1 of the PCI SSC supplement says “the use of a third-party service provider does not relieve the entity of ultimate responsibility for its own PCI DSS compliance”. Section 2.6 says to confirm validation requirements with “their acquirer or the payment brands”. Vendor SAQ claims are their reading; your acquirer’s is the one that counts.

Three build items stay with you whichever vendor you choose:

1. Prove the digits never reached the AI. Place a test call, enter a test card, then search your AI platform’s transcript, logs and traces for those digits, and confirm no tool or API the AI can call is able to retrieve them. On the in-line masking route, also check for DTMF bleed and for keypress events reaching your application. That is the verification sections 6.4.1 and 6.4.2 both require.
2. Pass references, not data, across the handoff. Only an order ID, amount and caller reference should cross the boundary in either direction. The capture service should report back success or failure and, at most, the last four digits.
3. Script the return. Decide what the AI says when payment fails or the caller hangs up mid-payment. On the in-line masking route, script the silence while the caller keys.

The scope reasoning behind these items is in our PCI scope analysis for AI voice agents.

Frequently asked questions

Which PCI compliant payment services work with an AI voice agent in Australia?

Five named options, read on their own pages on 30 September 2026: Twilio’s Pay verb and Payments API (AU1 region, DTMF only), PCI Pal, Sycurio (formerly Semafone), Westpac PayWay Phone (a keypad IVR on a 1300 number), and a Stripe payment link sent by SMS. Pick by the route your AI platform can support: redirect, transfer, in-line keypad masking or link.

Can Twilio Pay use Stripe in the Australian AU1 region?

Not according to Twilio’s own list. The Twilio Pay reference says Pay and the Payment resource are available in the Australia (AU1) region for six connectors: Base Commerce, Braintree, CardConnect, Chase Paymentech, Generic Pay Connector and Shuttle. Stripe is not on that list, so a Stripe merchant who needs AU1 should ask Twilio or look at a Generic Pay Connector.

Can my AI assistant stay on the call while the customer pays?

Yes, on two routes. With in-line keypad masking from a vendor such as PCI Pal or Sycurio, the AI stays on the call and should receive only flat tones; the PCI SSC’s section 6.4.1 says it must first be verified that all card data is replaced before it reaches the environment. With a payment link sent by SMS, the card is typed on a web page and never crosses the audio. Masking cannot protect a spoken card number, so on that route the caller uses the keypad. PCI Pal also offers in-line speech capture into its own recogniser, which stops a spoken card number reaching the agent.

Is a payment link by SMS PCI compliant?

It can reduce scope, but it is not automatically compliant. The PCI SSC telephone payments supplement, section 6.3, says a link to a secure payment page sent by messaging may be considered the same as e-commerce redirection, that its scope impact would need to be evaluated, and that the integrity and validity of the link must also be considered.

Does a Level 1 payment provider make my AI phone line PCI compliant?

No. Section 7.1 of the PCI SSC supplement says using a third-party service provider does not relieve you of ultimate responsibility for your own PCI DSS compliance, and section 2.6 says to confirm validation requirements with your acquirer or the payment brands. The provider’s attestation covers their system; your AI platform’s transcripts and logs are still yours to prove clean.

Does Zian AI take card payments?

No. Zian AI builds autonomous AI sales agents and has published no PCI DSS attestation or payment capture capability. Where a card is needed, the design on this page applies: card capture goes to a PCI-validated provider by one of the four routes on this page: redirect, transfer, in-line masking or link.

Where every figure on this page comes from

Figure	Who published it	Link	Date read
Pay and Payment resource in AU1 for 6 named connectors; Pay supports dtmf only; call continues with TwiML from the action URL	Twilio	twilio.com/docs/voice/twiml/pay	30 Sep 2026
Agent-assisted payments: agent stays on the phone and cannot hear the DTMF tones; “only dtmf is supported”; same AU1 connector list	Twilio	twilio.com/docs/voice/api/payment-resource	30 Sep 2026
Programmable Voice PCI DSS Level 1 statement	Twilio	twilio.com/en-us/pci-compliance	30 Sep 2026
PCI Mode cannot be disabled; not all ConversationRelay TTS/STT providers PCI compliant	Twilio	twilio.com/docs/voice/pci-workflows	30 Sep 2026
Action URL requested when Connect ends; no PCI data in handoffData; dtmfDetection sends keypresses over the WebSocket	Twilio	twilio.com/docs/voice/twiml/connect/conversationrelay	30 Sep 2026
AU1 data stored in region; no guarantee all data remains in region during rollout	Twilio	twilio.com/docs/global-infrastructure/understanding-twilio-regions	30 Sep 2026
Attestation of Compliance, PCI DSS Level 1	PCI Pal	pcipal.com trust-pci-dss-compliance	30 Sep 2026
Bot interacts with PCI Pal at the point of payment, works like live-agent assist; platforms not named	PCI Pal	pcipal.com conversational-ai	30 Sep 2026
Keypad or speech; over 140 languages	PCI Pal	pcipal.com ivr-payment-solutions	30 Sep 2026
Secure links by chat, SMS or email	PCI Pal	pcipal.com secure-digital-links	30 Sep 2026
Speech capture: caller’s voice prevented from reaching the agent	PCI Pal	pcipal.com speech recognition announcement	30 Sep 2026
Australian HQ in Sydney covering ANZ	PCI Pal	pcipal.com Australian launch announcement	30 Sep 2026
Australian government authority deployment	PCI Pal	pcipal.com public sector success story	30 Sep 2026
Solution hosted across AWS regions including Australia	PCI Pal	pcipal.com saas-payment-processing	30 Sep 2026
Agent Assist on Amazon Connect blocks card details from agent and environment; customer’s voice allowed through; Web Services API	PCI Pal	pcipal.com secure-payments-for-amazon-connect	30 Sep 2026
PCI DSS Level 1 Service Provider; more than 25 countries on five continents	Sycurio	sycurio.com/about/security-certifications	30 Sep 2026
SAQ-A and AOC statement; channels incl. AI-powered bots	Sycurio	sycurio.com/solutions/pci-compliance-solutions	30 Sep 2026
Integrations list (10 platforms)	Sycurio	sycurio.com/integrations	30 Sep 2026
Masking lets agents stay in full communication with customers	Sycurio	sycurio.com/integrations/genesys	30 Sep 2026
APAC sales contact address	Sycurio	sycurio.com/contact-us	30 Sep 2026
Semafone rebranded as Sycurio (14 April 2022)	Sycurio	sycurio.com rebrand press release	30 Sep 2026
1300 885 175; reference under 20 digits; CVN required; monthly studio session, 20th cutoff; surcharging dates	Westpac	payway.com.au/docs/phone.html	30 Sep 2026
PayWay Phone in the SAQ A group; guidelines current as at 16 Apr 2019	Westpac	payway.com.au/docs/pci-dss.html	30 Sep 2026
BPOINT no longer available to new customers	Commonwealth Bank	commbank.com.au BPOINT page	30 Sep 2026
PCI Service Provider Level 1	Stripe	docs.stripe.com/security	30 Sep 2026
Payment links shareable by text message	Stripe	docs.stripe.com/payment-links/share	30 Sep 2026
Australia on supported-countries list	Stripe	stripe.com/au/global	30 Sep 2026
Sections 2.6, 6.3, 6.4.1, 6.4.2, 7.1 quotations	PCI Security Standards Council	Protecting Telephone-Based Payment Card Data v3.0	30 Sep 2026
The No-Digits Rule and the four routes	Zian AI (this page)	Framing is ours; the facts are the sources above	30 Sep 2026