Send a payment request by text and let customers complete an eligible invoice from their mobile phone.
Text to Pay powered by Authvia adds conversational payments to the NMI Merchant Portal. An authorized merchant user starts a text conversation, enters the customer and payment details, previews the message and sends it to an SMS-capable phone number.
VCCP can help confirm availability, pricing, processor compatibility and activation. The service is intended for merchant-initiated payment requests—not unsolicited marketing messages or an unrestricted public donation link.
How Authvia TXT2PAY Works
- The merchant opens Authvia TXT2PAY in the NMI Virtual Terminal and starts a conversation.
- The merchant enters the SMS-capable phone number, amount, customer name, expiration, topic and instructions.
- The customer receives a branded text with the payment amount and a secure payment link.
- A new Authvia customer enters a card through the hosted experience; a returning customer may be able to use the Authvia-issued code tied to the mobile number.
- After a successful payment, the customer receives confirmation and a receipt link while the merchant can review the conversation status and reporting.
Useful Merchant Features
- No custom checkout build: Start conversations from the enabled NMI Merchant Portal.
- Clear payment context: Include a topic and instructions such as an invoice, service or pickup notice.
- Conversation tracking: Review in-progress, completed and expired requests and download available reports.
- Processor selection: Merchants with multiple configured processors may select the appropriate path when supported.
- Receipt delivery: Customers receive a text confirmation with a printable or downloadable receipt link.
Important Operating Details
- The customer number must receive SMS messages; landlines will not work.
- NMI currently describes the service for eligible U.S. and Canadian accounts.
- The amount cannot be changed after the conversation is sent. Cancel the incorrect request and create a new one.
- Virtual Terminal conversations can be assigned an expiration of one to seven days; expired requests require a new conversation.
- Closing a conversation prevents payment through that request but does not send a separate cancellation text to the customer.
Security and Customer Trust
- Verify the customer’s phone number before sending a payment request.
- Use a recognizable business name, accurate amount and clear instructions so customers can distinguish the request from phishing.
- Send payment texts only where the merchant has a legitimate transaction and the customer has provided the number for that purpose.
- Limit portal access, use unique users and two-factor authentication, and review conversation history.
- Follow applicable consent, privacy, recordkeeping and text-messaging requirements.
Good Fits for Text to Pay
- Service businesses collecting after work is completed
- Invoices that need a convenient mobile follow-up
- Pickup-ready orders with a known customer and fixed balance
- Nonprofits following up with a known supporter on an agreed payment
- Businesses that want another remote-payment channel without building an app
Important Limitations
- Activation, geography, message delivery and processor support vary.
- A sent message does not guarantee that the customer will receive it, trust it or complete payment.
- Text to Pay does not replace fraud screening, customer verification, refund handling or reconciliation.
- Merchants remain responsible for text-message consent, accurate payment details and account security.
Related NMI Tools
- Electronic Invoicing for email-based invoice workflows
- Customer Vault for eligible stored payment records
- Fraud Prevention for gateway screening rules
- Card Testing Detection for suspicious activity alerts and restrictions
Authvia Text to Pay Frequently Asked Questions
What is Text to Pay powered by Authvia?
It is a conversational-payment service available through eligible NMI accounts. An authorized merchant sends a payment request by SMS, and the customer follows a secure link to complete the eligible payment.
Does the customer need to install an app?
No separate merchant app is normally required for the customer. The text directs the customer to Authvia’s hosted mobile payment experience, subject to the supported device and current service design.
Can Text to Pay send requests to a landline?
No. The customer number must be able to receive SMS messages. Merchants should verify the number and the customer’s intended use before sending a request.
Can the amount be changed after the payment text is sent?
No. If the amount is incorrect, the merchant should close or cancel the conversation and create a new request with the correct details.
How long does an Authvia payment request remain active?
Virtual Terminal conversations may be configured with an expiration of one to seven days. An expired request requires a new conversation.
Can Authvia Text to Pay be used for donations?
It may be useful for a known supporter and an agreed payment request, but it is not an unrestricted public donation form. Public donation pages still need appropriate checkout, consent, security and bot-protection controls.
Is Text to Pay the same as SMS marketing?
No. It is intended for legitimate merchant-initiated payment conversations. Merchants remain responsible for customer consent, privacy, message accuracy, recordkeeping and applicable text-messaging rules.
Add a Mobile Payment Conversation
Tell VCCP how you invoice customers, which processor is connected and whether you need one-time remote payments. We can help confirm whether Authvia TXT2PAY fits the workflow.
Availability, pricing, processor compatibility, messaging, expiration and customer experience depend on the NMI account, Authvia service and current platform rules. VCCP does not guarantee message delivery or payment authorization.