> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/ai/ai-features/payments.md). # Payment AI Payment AI lets the ASC AI assistant take payments on the call, 24/7, with a secure payment link by text and confirmation before the call ends. Payment AI lets the ASC AI assistant collect payments from your callers around the clock, with no live agent on the line. A caller places an order or settles a balance, pays from their own phone, and hears the confirmation before the call ends. ### On a typical call {% stepper %} {% step %} ### The caller is ready to pay The assistant takes the order, or confirms the amount due, and asks how the caller would like to pay. {% endstep %} {% step %} ### A secure payment link is sent by text The assistant confirms the caller's mobile number and texts them a secure payment link. The caller opens it on their phone and enters their card details on the payment page. {% endstep %} {% step %} ### The assistant waits on the line While the caller pays, the assistant stays on the call and checks whether the payment has gone through. If it has not, the assistant lets the caller know and keeps waiting. {% endstep %} {% step %} ### The payment is confirmed Once the payment clears, the assistant confirms it with the caller and wraps up the call. {% endstep %} {% step %} ### You get the details The order and payment details arrive through your usual delivery methods and appear in your portal alongside your other messages. {% endstep %} {% endstepper %} ### What callers experience * They can order or pay at any hour, with no hold time. * They pay on their own phone, on a secure payment page, in a few taps. * They hear the payment confirmed before the call ends, so there is no guessing whether it went through. ### Security * **Card details are never spoken.** Callers enter payment information on the payment page from their own device, so card numbers never appear in call recordings or messages. * **Handled by your processor.** Payments are processed by the payment processor connected to your account. ASC does not store your customers' card details. * **Paid straight to you.** Funds settle directly to your own account. ### Human backstop As with every AI call, the assistant escalates to a live agent 24/7 when a caller needs a person, for example to sort out a payment problem. See [Hybrid: AI plus live](/docs/ai/how-ai-answering-works/hybrid-answering.md) for how escalation rules work. ### Try it Three demo lines take a test payment by phone: * **Pie Society Pizza**, (866) 651-1340: order a pizza for pickup, then ask for a link to pay. * **Pinecrest Air Duct Cleaning**, (844) 788-1200: ask to pay your duct cleaning invoice. * **Bright Steps Foundation**, (888) 305-1070: make a $50 donation. Pay with test card 4242 4242 4242 4242 (Pie Society, Pinecrest) or 4111 1111 1111 1111 (Bright Steps), expiry 12/30, CVV 123, ZIP 33068. Test cards are never charged. ### Get started Payment AI is available on AI and hybrid plans and is set up per account with your implementation specialist, who connects your payment processor and configures what the assistant can take payment for. Ask your account manager to enable it, or contact . ### Related * [How AI answers your calls](/docs/ai/how-ai-answering-works/how-ai-answers.md) * [Multilingual answering](/docs/ai/ai-features/multilingual.md) * [Get started with AI](/docs/ai/ai-answering-overview/get-started.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://answeringservicecare.com/docs/ai/ai-features/payments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.