Text-To-Pay Links

Text-To-Pay Links let you request and collect payments instantly via SMS directly from a conversation. No website required!

What are Text-To-Pay Links?

Text-To-Pay Links are secure payment requests you send by SMS from within a conversation. They generate a checkout link so customers can pay in a few taps. This reduces friction, speeds up collection, and keeps payment activity tied to the contact thread for easy follow-up and tracking.

Key Benefits of Text-To-Pay Links

• Fast Collection: Send a pay-ready link from any SMS thread for fewer steps and quicker conversion.
• On-Brand: Customize the invoices to match your brand style.
• Due Dates: Set a link due date to encourage timely payment and manage expectations.

Prerequisites

Verifying prerequisites prevents common setup issues and ensures links send and process correctly.

• An active Adaptive AI Payments (Stripe) connection in the sub-account.
• An active phone number in the sub-account.
• At least one active product.

Sending a Text-To-Pay Link from Conversations

1. 1Go to and open the conversation with the contact you would like to send the text-to-pay link to.
2. 2In the channel picker at the message box, choose.
3. 3Click ($ icon) below the text editor.
4. 4Click Send to send the text-to-pay link. The customer will see the following screen when opening the link! Tip: You can customize this page! Click here to learn how.

Before you begin

“Text-To-Pay Links” is part of the Payments → Payment Links area in Adaptive AI. Create direct checkout links for products, services, or amounts. Payment settings can create real charges, invoices, subscriptions, tax records, and customer notifications. Use a controlled test and verify the complete financial record before relying on the setup. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the correct payment provider is connected to the correct business and determine whether you are working in test or live mode.
• Verify currency, price, billing frequency, tax behavior, product or variant details, and customer-facing description.
• Use a clearly labeled internal test customer and avoid using a real customer record while validating a new configuration.
• Review the email, receipt, invoice, estimate, fulfillment, or subscription notifications that the transaction can trigger.
• Confirm your user role permits the intended change and that accounting or fulfillment owners know how the result should be handled.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Preview the customer-facing amount, schedule, terms, product details, and payment method before submitting a controlled test.
2. 2Complete the test and confirm the order, transaction, invoice, estimate, or subscription appears with the expected status.
3. 3Verify the customer record, payment timeline, receipt, internal notification, and connected workflow all contain matching information.
4. 4Check the payment provider or connected accounting system to confirm the same amount, currency, identifier, and status were recorded.
5. 5Validate the next billing date, cancellation behavior, inventory effect, or fulfillment action when the configuration is recurring or product-based.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm test and live credentials are not mixed and that the selected product or price belongs to the connected provider account.
• Check required customer fields, currency support, payment-method availability, and any provider decline or validation message.
• Compare Adaptive AI and provider timestamps or identifiers when a payment exists in one system but not the other.
• Review connected workflows and notifications separately from the transaction when payment succeeded but follow-up did not run.
• Do not repeatedly submit a live charge while diagnosing; use logs and a controlled test to avoid duplicate billing.

Best practices

• Use consistent product, price, invoice, and subscription names that make reports and customer statements easy to understand.
• Document refund, cancellation, fulfillment, tax, and failed-payment responsibilities before accepting live transactions.
• Restrict payment-setting access to appropriate staff and review provider connections whenever administrators change.
• Test every new checkout or recurring schedule with the smallest safe test scenario before sharing it publicly.
• Reconcile platform and provider records regularly rather than relying on a single dashboard as the financial source of truth.