Capture PCI-compliant payment card details during a Twilio Voice call using the <Pay> verb.
domain: twilio.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Twilio Verify for teams leaving Authy — the full failure-mode walkthrough related to twilio.com, checked against official docs, with linked verified routes.
Steps
Install a Pay Connector (e.g. Stripe) from the Console Add-ons/Marketplace and note its Unique Name.
Return TwiML with <Pay> nested in <Gather> or standalone, setting paymentConnector to the connector's Unique Name.
Set tokenType to one-time, reusable, or (Stripe only) payment-method depending on how you'll reuse the card.
Set chargeAmount to a value greater than 0 to charge immediately, or omit/leave at 0 to only tokenize.
Point statusCallback (and/or action) at a webhook to receive the resulting token/charge result.
Handle capture-step errors like invalid-security-code and invalid-postal-code in your call flow.
Known gotchas
Default paymentConnector name is literally 'Default' — must exactly match the installed connector's Unique Name or the call errors.
Current docs show no Sync Map step in the flow — the result arrives via the statusCallback/action webhook only.
Using <Pay> keeps you out of PCI scope only if you follow the connector's documented flow; you still authorize Twilio to call the processor on your behalf.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?