Tyxter and Meta
Where Tyxter sits between your business and Meta, and what that means for the account, the bill, and your data.
That distinction decides the three things a vendor review asks about this integration: who owns the WhatsApp Business Account, who sends you the WhatsApp bill, and what Tyxter holds on your behalf.
Your WhatsApp Business Account is yours
WhatsApp Embedded Signup either creates a new WhatsApp Business Account (WABA) under your own Meta Business or connects one you already have there. Either way the account sits under your Meta Business and stays there. Tyxter’s Meta app is subscribed to it, and that subscription is what lets Tyxter send on your behalf and receive your delivery and inbound webhooks.
Signup launches two ways. The dashboard Connections page runs it for a signed-in owner or admin. From the API, GET /v1/provider-connections/meta/onboarding returns the non-secret launch payload your own front end needs (never the app secret, never a raw OAuth URL), and your server then posts the authorization code the browser hands back to POST /v1/provider-connections/meta/oauth. POST /v1/meta-signup-sessions is the hosted variant of that: Tyxter serves the browser page and completes the exchange itself.
What reaches your backend differs by exactly one thing. Tyxter always exchanges the code with Meta server-to-server, so the resulting access token, and Tyxter’s own Meta app secret, never transit your backend. The short-lived authorization code does pass through your server when you run the flow from your own front end, and does not when you use the hosted variant.
Leaving Tyxter
Leaving Tyxter does not delete or transfer your WABA. Disconnect the Tyxter provider connection, then use Meta Business, WhatsApp Manager, or your next provider to connect the customer-owned account elsewhere.
A WABA and a phone number are separate assets. The WABA always stays in your Meta Business, but who controls the underlying phone number depends on how the number entered Tyxter:
| Number class | Who controls it | Exit path |
|---|---|---|
| Bring your own (BYON) | You control the carrier number and the Meta registration; Tyxter stores only the environment-scoped sender row and connection metadata. | Release the BYON row to stop using it through Tyxter. The release is immediate and makes no carrier or Salvy call; reconnect the number through Meta or another provider. |
| Salvy-provisioned | Tyxter rents the number through its platform Salvy account and assigns that rental to your environment. | Release the row to request cancellation of the Tyxter-managed rental; the number becomes released after Salvy confirms. This is service closure, not a port-out. Tyxter publishes no self-serve or contractual port-out guarantee today, so treat the number as non-portable unless support confirms a case-specific path before release. |
Before changing providers, export any contact-scoped message history you need while it is still inside your retention window. Keep data_export_enabled on and use POST /v1/contacts/{contact_id}/export; the Data retention & privacy page owns the exact retention, export, and erasure rules.
Who bills what
Meta bills you for WhatsApp messaging, on the Meta account that owns your WABA, at a rate that depends on which of its categories the message falls into.
Tyxter bills you for Tyxter: one flat transport fee per outbound WhatsApp message, discounted by your plan, alongside the other Tyxter meters you use. Both sides read from one response. GET /v1/rate-cards/current carries everything Tyxter actually debits as kind: "billed" and reproduces the Meta category rates for reference as kind: "meta_reference". The rates themselves, and what a plan changes, are on the Billing page.
You fund your own account
Because the account is yours, so is its payment method. A brand-new WABA has none on it, and Meta will not register a phone number on an account it cannot bill. Tyxter surfaces that refusal as meta_payment_method_required, pointing at Billing & payments in WhatsApp Manager. Add the payment method there and then finish the connection: the remaining provider steps re-run from the credentials Tyxter already holds, so there is no second signup.
What Tyxter holds
To send on your behalf, Tyxter stores one access token scoped to your WhatsApp Business Account. It is encrypted at rest with AES-256-GCM, is never returned in an API response, and is never written to a log. Being subscribed to your account also means Tyxter receives your WhatsApp webhooks, message status updates and inbound messages alike, because that is how they reach you.
Sandbox touches none of it: sandbox messaging runs against Tyxter’s own simulator, and Meta signup completion and phone registration are production-only. What Tyxter keeps of your message content, for how long, and the retention window you set yourself are on the Data retention & privacy page.