Copy page
View as Markdown View this page as plain textOpen in Claude Ask questions about this page
Recipe

WhatsApp agent with payment links

Recommended integration shape for apps that use Tyxter WhatsApp transport with Tyxter payment requests.

Tyxter payment requests create provider work asynchronously. Send a payment link only after Tyxter returns a non-null payment_link_url.

Recommended shape

  1. Use Tyxter for WhatsApp transport: inbound webhooks, outbound messages, delivery status, templates, contacts, phone numbers, and sandbox testing.
  2. Keep business orchestration in the application when the workflow depends on private scheduling, product catalog, pricing, or policy.
  3. Create Tyxter payment requests with your API key, then subscribe to payment.link_generated (or the compatible payment.approval_available name) and payment.paid. Poll or listen only when you have no registered endpoint.
  4. Send the returned link through Tyxter messages only after the request leaves link_pending.
  5. Confirm paid bookings only from Tyxter payment state or an explicit operator approval.

Tyxter endpoints

POST/v1/messages
POST/v1/webhook-endpoints
POST/v1/payments
POST/v1/sandbox/inbound-messages

LLM routing

Tyxter LLM routing is available for BYOK inbound automation, but it is optional for this architecture. Prefer app-owned LLM orchestration when the agent must call tools Tyxter does not own.