Webhooks

TTConnect receives webhooks from payment providers (e.g. Stripe) to keep payment and subscription state in sync. You don’t call these endpoints yourself—they’re used by the provider.

If you host the API

• The webhook endpoint expects a signature header from the provider. The raw body must be used for verification; don’t parse or modify the body before checking the signature.
• Respond with a success status (e.g. 200) after processing so the provider doesn’t retry unnecessarily. Implement handling in an idempotent way so duplicate events are safe.

Outgoing webhooks (if supported)

If your deployment supports sending webhooks to your server (e.g. payment completed, membership updated), your team will provide the event types and payload format. Configure your endpoint URL and optional secret in the platform or via configuration.

For provider-specific behavior (e.g. Stripe), refer to the provider’s webhook documentation and any TTConnect-specific notes from your team.