Ringup adds payment to your Twilio ConversationRelay call by transfer: when the order is confirmed, your agent creates a Checkout Session and hands the live call to a Ringup payment line, like a hosted web checkout. Returning callers are recognized by number, first-timers are texted a secure link, and charges settle on the merchant’s own payment processor.
Your Twilio ConversationRelay agent can take an order. Collecting payment is the hard part. Reading a card number aloud is clumsy and drags you into PCI scope, and telling the caller to "pay online later" loses the sale.
Ringup adds payment to the call itself, like a checkout that remembers the customer. A returning caller is recognized by phone number and pays with their saved card; a first-time caller is texted a secure link and is remembered next time. Charges settle on the merchant's own payment processor, and no card number is ever spoken.
When the order is confirmed, your agent creates a Checkout Session and transfers the live call to a Ringup payment line, exactly as a hosted web checkout redirects the browser. Your Twilio server redirects the call to the Ringup SIP URI, carrying the Checkout Session id. Ringup recognizes the caller, charges the saved card on the merchant's own processor, texts a receipt, and can transfer the caller back to your agent to finish in your own voice. It is one integration you can reuse across every platform, and the same Checkout Session and webhook underneath.
Ready to build? The developer docs have the exact Twilio ConversationRelay setup, the step-by-step, and the API reference.
Read the developer docs →payment_required as required, optional, or none, resolved per purchase from the merchant's own rule. A merchant who has not connected a processor yet simply gets a payment-free call (the none state).return_to and Ringup transfers the caller back with the outcome in SIP headers, so your agent closes in its own voice. Or let Ringup read a short confirmation and end. Either way the caller gets an SMS receipt.checkout.completed webhook with the payment id and confirmation, so you mark the order paid. See the developer docs for the webhook shape.identify at the greeting yourself; it needs only the caller's phone number. For a returning caller it returns their name and saved card, so your agent greets them by name and skips re-asking for what it already knows, like the name for the order. Recognition happens at the greeting, separate from and earlier than taking payment.Create a Checkout Session, transfer the call. Your returning callers never touch their card again.
Request demo