WooCommerce can sell the membership, but the access system still needs a trusted backend handoff into Telegram. KickThemBot is designed to make that handoff auditable.
A WordPress site can handle product pages, order history, customer email, and bundles while KickThemBot handles Telegram access after payment is confirmed.
Order completion event
Product-to-plan mapping
Customer identity fields
Create access from trusted backend code
The website should call the membership API from server-side plugin or backend code. API keys should never appear in browser JavaScript or public templates.
Server-side API key
Access-code creation
Secure customer handoff
Keep renewals and support aligned
Renewal orders should update existing membership state where possible, so support can see the website payment source, Telegram identity, plan, and expiry date together.
Membership lookup
Expiry extension
Support-ready audit trail
Access lifecycle
How KickThemBot turns WooCommerce Telegram membership into an operating workflow.
Every paid membership in KickThemBot follows the same path: a payment, the member's Telegram account, a visible status and removal when access ends.
01 / Payment source
Start from a real payment
A Stripe checkout on your own account, or an access code you send after a crypto, invoice or partner sale, starts the membership.
02 / Telegram identity
Know who has access
The membership belongs to the Telegram account that paid or redeemed the code, and each invite link holds one member at a time.
03 / Access status
See every member
In the Mini App, admins search members, see each plan, status, end date and source, and extend or remove access.
04 / Expiry outcome
End access cleanly
Reminders go out before the end date, subscriptions get a short renewal grace, and the bot removes members when access ends.
Project access routeReady
Payment or codeMember recordedInvite link sentExpiry tracked