Mail2Wa: WhatsApp users, QR, credit, and sending

When to use Mail2Wa

Mail2Wa is a reseller-based WhatsApp integration built around QR-linked user sessions and provider credit. It is separate from Meta WhatsApp Business Platform, which uses an official business account and approved templates, and from ISP WA, whose managed bidirectional flow can create and update tickets.

Select the provider according to governance, channel ownership, inbound workflow, template requirements, cost, and support model. Settings and credentials cannot be copied between providers.

API key and first connection

Enter the reseller API key supplied by Mail2Wa and save it as a secret. Never include it in screenshots, URLs, tickets, or client-side code. Use a dedicated credential where the provider allows it and define who may rotate it.

After saving, refresh reseller profile, account state, available users, and credit. A stored key is not proof of a working connection; distinguish authentication failure, disabled reseller, network error, and an account that simply has no users.

Create and link a user

Create a user with a stable name that identifies its business purpose, department, or sending number. Open that user’s current QR code and scan it only from the intended WhatsApp device and account.

The QR behaves like a temporary authentication credential. Do not forward or archive it. Wait for the provider to report the authenticated state, then confirm the displayed number and profile before enabling any automated communication.

States and lifecycle commands

Each user exposes remote state and commands such as Restart, Disconnect, QR Code, Block, Unblock, and Delete. Restart attempts to restore the session; Disconnect removes the active link; QR Code starts or resumes pairing; Block and Unblock control provider use; Delete removes the remote user.

These actions are not interchangeable. Confirm the target user, warn operators about interruption, execute one action, and reread the provider state before continuing. Do not repeatedly retry an uncertain command because the first request may already have succeeded remotely.

Reseller credit and user credit

Reseller balance and individual user credit are different scopes. Before adding credit, identify the target user, currency, amount, opening balance, commercial justification, and returned balance. Keep the provider reference when available.

A provider credit movement is not automatically a customer collection or an ISP Billing payment. Reconcile it with the supporting invoice, payment, and Cashbook process, and investigate timeouts before repeating the recharge.

Send a message

Select an authenticated, enabled, and funded user. Normalize the recipient to the international format required by the provider, verify the customer’s consent and communication purpose, and review text, links, timing, and any personal data.

After sending, record the provider outcome and refresh state. API acceptance means that Mail2Wa accepted the request; it does not prove delivery to the handset or reading by the recipient.

Differences from Meta and ISP WA

Meta uses the official WhatsApp Business Platform, approved templates outside the service window, webhooks, business-account assets, and its own conversation rules. ISP WA provides the managed ISP Billing channel with inbound conversations and ticket integration. Mail2Wa uses QR-authenticated user sessions and reseller/user credit.

Choose one deliberate operational path for each use case. A Meta template cannot be sent through a Mail2Wa session, and a Mail2Wa user does not automatically provide ISP WA’s inbound ticket behavior.

Diagnosis and checklist

For a failed send, check provider selection, reseller key, reseller state, target user, QR authentication, block state, credit, recipient format, consent, content, and provider response in that order. Correct the cause before retrying and assess duplicate risk after a timeout.

• Choose Mail2Wa for the intended operating model
• Protect and rotate the reseller API key
• Verify reseller profile and balance
• Create a clearly named user
• Protect and scan the correct QR
• Confirm number and authenticated state
• Use lifecycle commands deliberately
• Separate reseller and user credit
• Reconcile every credit movement
• Validate number, consent, and content
• Distinguish acceptance, delivery, and reading
• Do not mix Meta, ISP WA, and Mail2Wa procedures