WhatsApp Payments in the US: Availability and Payment-Link Options

This guide separates personal transfers, business payments and external links. Names behind the Pay button vary by market and provider. Infobip uses WhatsApp Pay for peer-to-peer (P2P) payments and Payments on WhatsApp for business payments on the WhatsApp Business Platform.

Many articles use both names loosely, and Wati's guide calls the native feature WhatsApp Pay throughout. Check which product a vendor means before you compare setup steps, payment methods or country lists.

A third pattern sits beside them: the WhatsApp payment link. Your gateway hosts the checkout, and the chat only carries the URL. WASenderPlus fits this pattern, because it sends messages and leaves the transaction to your gateway.

Wise's guide lists the India-only setup steps. Open WhatsApp on an eligible device, go to More options, then Settings, then Payments. Tap Add new account and accept the terms and conditions.

Next, tap your bank from the list of supported banks. Choose Verify via SMS and allow the check, then select the bank account you want to use. Menu labels can change, so install the latest app version first.

If your bank is missing from the list, you cannot finish this flow in the app. Contact your bank or read the WhatsApp Help Center for the current list.

To send money, open the chat and tap attach. Choose the payment option, enter the amount and confirm with your UPI PIN. These steps follow the India flow, so labels may differ elsewhere.

Receiving uses the same linked account. Money moves between bank accounts on the Unified Payments Interface (UPI). Zoko notes that the National Payments Corporation of India (NPCI) developed it.

Request money options and instant transfer timing can vary by bank and market. Treat your own bank's confirmation as the proof of payment, not a screenshot that a contact sends you.

Availability differs between personal transfers and business payment features, so one country count can mislead. Picky Assist's 2026 guide names India through UPI, Brazil through Meta Pay and Singapore through Stripe. Confirm these vendor claims before relying on them.

For the United States, Wise's guide says you can't send money through WhatsApp Pay, but that is a secondary source. Check current WhatsApp documentation, and remember that a checkout link sent in chat is a separate route.

Country-specific availability also differs by product. Confirm current support in the WhatsApp Help Center and with your Business Solution Provider (BSP). Do this before you promise a customer an in-chat Pay button.

Picky Assist describes WhatsApp money transfer as domestic-only. Each country's version sits on separate rails under separate central bank rules. Its guide says a Mumbai sender cannot pay a WhatsApp Pay user in Brazil.

Some older articles still imply otherwise, but assume no cross-border P2P transfers until WhatsApp documents a change. If you need to pay someone abroad, use a licensed remittance service. Wise's guide offers its own service as one alternative.

For business collections, your gateway decides which currencies and countries it accepts. Check that list before you send a payment link abroad. Vendor talk of partner-led pilots does not indicate general availability.

Chat Reach Magnet lists UPI, debit cards, credit cards and net banking for in-chat collection in India. WhatChimp adds wallets to its link product. Each list describes that vendor's offer in supported contexts.

Underneath, YCloud describes real-time payment rails such as UPI, while Watsspace mentions card networks and local banking partners in Brazil. Your payment processor and market determine which of these a customer actually gets.

On the gateway link route, your gateway's checkout settings decide the options. For a US invoice in USD, confirm which card or bank methods it supports, then state them in your message.

Infobip describes a complete path inside one thread, from product discovery to checkout and confirmation. In supported markets, a customer can browse a catalog, build a cart and answer a payment request in chat.

Clickatell outlines a link version in plain steps. The business sends a request, the customer opens a secure checkout page, submits details, then receives an order confirmation and receipt.

After payment, the next steps in the same conversation can include shipping details and delivery notifications. Plan who sends each of these, because a paid customer's next question usually concerns delivery.

Choose by fit rather than by feature list. Compare what your country allows, how customers will pay and what each route requires of your team. Do this before you commit to any route.

WASenderPlus serves only the last row, using a team shared number and a Sheet or billing export. That is our workflow, not a link requirement. For a native Pay button, ask a BSP about market coverage.

If native payment is not offered in your market, you can still collect payments through WhatsApp by sending a link. The transaction happens on your gateway's page, and the chat handles the request and follow-up.

Describe that honestly in your message. Write 'Pay through [gateway name]', not 'Pay with WhatsApp Pay'. Identify your business and, where available, the statement descriptor configured with your processor.

The trade-off is real. Jelou argues that a link takes customers out of the chat at the moment of payment. Weigh that against reach, then measure your own paid rate per campaign.

Start with columns named first_name, phone, invoice_id, amount, description, due_date, payment_link, consent_source and paid. Each row is one invoice, so a customer with several invoices gets several clearly labeled rows.

Generate links in your gateway, with a matching expiry date if it supports one, and paste them in. Write: 'Hi [first_name], invoice [invoice_id] for [amount] is due [due_date]. Pay here: [payment_link]. Reply STOP to opt out.'

Before queuing, filter out paid rows and blank consent cells. Open a sample of links and compare each personalized customer name and amount with the gateway record. Then schedule the broadcast for local business hours.

WASenderPlus defaults to a gap of 4–40 seconds and allows up to 250 sends a day on a fresh number. These are WASenderPlus operational settings, not WhatsApp-published limits or guarantees.

For 250 sends, allow roughly 17 minutes at four-second intervals and about 2 hours 47 minutes at 40-second intervals. Those estimates exclude processing time and pauses, and they are not a guarantee.

Follow the rules and limits that apply to your sending method. The 2-week warm-up and 6,000 daily setting are WASenderPlus references. Pacing or account age does not establish permission or prevent restrictions.

Log block rates and spam reports per campaign. If they rise, pause the queue, review your consent evidence and check your wording before you resume.

If you send through the WhatsApp Business Platform, Meta's documentation sorts message templates into categories such as utility and marketing. Check current definitions before you classify a payment request, reminder or receipt.

A plain invoice notice tends to read as account information. Add a discount or upsell, and it starts to read as promotion. Keep those messages apart, whichever sending route your team uses.

Meta also describes a customer service window that opens after a customer messages you. Replies inside it and template sends outside it can follow different rules, so read Meta's current documentation for terms.

An opt-out in a payment campaign creates a real conflict. The customer said stop, but the invoice remains unpaid. Respect the opt-out on WhatsApp, then move the conversation to another agreed channel.

Separate transactional messages from marketing with different sheets and different wording. Store each customer's permission per message type, because someone who accepts receipts may not want discounts or upgrades.

Test the opt-out keywords your customers actually use, especially across mixed-language lists. Add the opted-out status to your billing records too, and take legal advice on debt-collection rules in your market.

Set the cadence before the first send. One workable structure is a notice before the due date, one on the date and one after it. Give each stage its own Sheet tab.

Set a frequency cap per customer and keep sends inside quiet hours for their time zone. Add a time zone column, then split the list so each group sends during its local business day.

Write overdue payment escalation rules in advance. After your final WhatsApp reminder, pass the account to a named agent or to finance. Do not keep broadcasting to a customer who has stopped replying.

Automatic stop after payment is something vendors advertise through gateway integrations in their own products. With WASenderPlus, you handle this step in your list before each send, using your gateway's records as the source.

Export paid invoices from your gateway as a CSV export. Match them to your Sheet by invoice ID and set the paid column. Filter to unpaid rows and use that view for the next reminder.

Run the export as close to send time as you can. A customer who pays mid-queue may still get a message, so add a line such as: ignore this if you have paid.

A shared number gives every customer one place to ask about an invoice. Payment replies land in the team inbox, where any agent on shift can read the thread rather than a colleague's phone.

Agree handoff rules for payment questions. Frontline agents answer link and due-date questions. Finance handles refunds, disputed amounts and partial payments. Note each owner in a Sheet column so the next shift knows.

Vendors such as SleekFlow show payment details and chat history side by side. If your gateway sits in a separate tab, agents search by invoice ID, so every message should carry that ID.

Role-based permissions for money belong in your gateway. Limit who can create a payment link, change an amount or issue a refund. Use named logins so its transaction logs identify each person.

Treat the send list as a financial document too. Restrict editing on the Sheet. Use its version history as an audit trail for amounts and links changed before a broadcast.

Add a reviewer before large sends. One person builds the list, and another samples rows against the gateway. The reviewer looks for mismatched amounts or links, then approves the queue.

End-to-end encryption protects message content between chat participants. It does not describe the hosted page a link opens, which your payment gateway secures, or the transfer your bank authorizes.

Chat encryption does not prevent authorized business users or connected tools from accessing messages at their endpoints. Review the access and storage practices of your inbox, extension and add-on before you send payment messages.

For a gateway link, ask separate questions. Who sees the message? Who hosts the secure checkout page? Who stores the card? Your gateway's security documentation answers the last two, not a chat encryption notice.

On the UPI route, guides from Zoko and Picky Assist describe a UPI PIN and two-factor authentication. They also list biometric authentication, SMS OTP and device binding. Exact checks can vary by bank and phone.

On card routes, ask your gateway about PCI DSS, tokenization and 3D Secure. Jelou, for example, describes PCI DSS-certified processing and tokenized capture for its own product. Those claims belong to that vendor only.

Data handling depends on the payment feature and provider, so consult the relevant payment privacy notice. Keep card numbers and UPI PINs out of your chat, inbox and Sheet. Route KYC for high-risk payments through your gateway.

Payment links attract impersonators, so make your messages easy to check. Name your business, the invoice ID and the amount in every request. Send from the same shared number customers already know.

Use your gateway's own domain rather than a link shortener, so customers can read where the link goes. State in writing that your team will never ask for a UPI PIN, card number or OTP.

Give customers another way to confirm. Point them to an invoice in their account, or invite them to ask an agent. Offer a separate payment channel, such as your billing portal, for anyone unsure.

Reconciliation starts with one identifier. Put the invoice ID in the message, the link description and the Sheet. Gateway records, chat threads and accounting entries then all share the same key.

Add columns for partial payments, failed-payment retries and refunds. Confirm any remaining balance in the gateway, then update the request or create a new link if required. Failed attempts may need a fresh link if the old one closed.

Match settlement last. Gateway settlement to your bank account can group many payments in one deposit, less payment gateway fees. Use the gateway's settlement report, not the broadcast list, for your books.

Track a funnel per campaign where your tools support it: sent, delivered, read, link click and paid. Delivery and read data depend on your sending method. Click and paid data come from your gateway or link tracking.

Add time to payment by comparing send time with the gateway timestamp. Report recovered revenue only for invoices overdue at send time, and keep the campaign name in a Sheet column for joining.

Published conversion figures for in-chat payment are usually vendor data from their own customers. Treat them as claims, and compare your own attributed sales by campaign or agent before you change routes.

Transaction fees depend on the route, the country and your contract. Native routes follow local terms, payment gateway fees follow your gateway's current rate card, and bank fees, messaging-provider or currency-conversion charges may also apply.

Older articles quote a Brazilian business fee per received transaction. That figure is historical, so this page leaves it out. Check the WhatsApp Help Center and your provider's pricing page for what applies today.

WASenderPlus charges a subscription, with the Entry plan at $6/mo and the Team plan at $19/mo. Those prices cover the messaging tool. Your gateway bills its own charges separately. Check the pricing page for current billing terms.

Transfer limits and daily limits can depend on local rules and your bank. Published numbers go stale, so check your bank's app and the WhatsApp Help Center rather than a blog table.

If a transfer fails, check the app version, linked account, balance and UPI PIN. Confirm with your bank whether money left your account before you retry, so you do not pay twice.

On gateway links, a failed payment appears in the gateway with its decline reason. Send the customer a fresh link if the old one has expired, and log the retry against the invoice ID.

Recurring payments require an appropriate payment authorization and a provider-supported recurring mechanism. Jelou describes automatic charges at a set frequency for subscriptions and memberships. On a link route, the charge runs in your gateway, and WhatsApp carries the notice.

Card-on-file flows, described by Bird, let returning customers pay for upgrades, reorders, add-ons and prepayments in chat. Compare them with link broadcasts on fit: who stores the card, and who approves each charge.

For installments, keep one row per installment with its own link, due date and status. That layout lets a reminder name the right installment and leaves paid ones out of the next send.

Abandoned cart recovery suits customers who opted in to cart messages. Export unfinished carts from Shopify or your store, add the checkout link to a row, and send with a clear opt-out line.

Retail and restaurant teams can use links for deposits and one-time payments. Travel teams can collect balances before departure. Infobip also names insurance payments and bill payments, which need a clear policy or account reference.

Discounts, upselling and cross-selling belong in a separate marketing send. Keep them out of an invoice reminder, so a customer who consented only to billing messages hears only about billing.

Vendors stress no redirects, no app download and no account creation. Check which of those applies to your route. A hosted link can skip the download, yet it still opens a separate page.

Many guides present conversational commerce as a conversion gain, and some publish their own customer data. This page makes no such claim. Test your own payment confirmation flow and compare results with your current checkout.

Some work stays the same on every route. You still need consent records, clear wording, a refund process and someone to answer questions. Plan those before you choose chat buttons or a flow builder.

The WhatsApp Business app, WhatsApp Cloud API and a Business Solution Provider are not always separate choices. A provider can offer access to or services around the Business Platform, so compare number ownership, list location and volume.

Platforms such as Wati and SleekFlow advertise webhooks, flow builders, automated order updates and Shopify order sync. That fits teams with store events to automate. Check each vendor's current documentation for coverage in your market.

A Sheets-led setup fits billing data already in a spreadsheet. You paste in Stripe payment links or similar, with no payment gateway integration to build. Your sending method still determines which platform rules apply, so confirm it in WASenderPlus's documentation.

Local rules shape every route. UPI sits within the NPCI framework in India, while other regulators and card schemes apply elsewhere. Treat any vendor's compliance line as a starting point for your own check.

In the US, check applicable state privacy obligations. Customer data in your send list can also fall under laws such as GDPR in Europe and LGPD in Brazil. Keep only the columns you need, restrict Sheet access and delete old lists on schedule.

US teams should separate routine first-party invoice reminders, marketing messages and debt-collection activity, because federal and state rules may differ. Ask counsel about wording and contact hours. Keep timestamps and consent records so you can answer a complaint.