Hytale Payment Plugin Guide

Under the hood, every Hytale payment plugin does roughly the same five things:

1. Register in-game commands or UI. The plugin exposes commands (or a clickable store interface) that players use to browse tiers, check their subscription status, and manage their perks. Commands like /store, /subscribe, /cancel, and /whoami are standard.

2. Listen for payment webhooks. When a player completes a purchase, the payment processor (Stripe, Tebex's own processor, Adyen, PayPal, etc.) sends a webhook to the plugin's HTTPS endpoint. The plugin verifies the webhook signature, looks up which player triggered the purchase, and schedules the perk grant.

3. Grant and revoke perks. On successful payment, the plugin assigns the in-game role, grants cosmetic access, unlocks the private channel, or whatever other perk the tier promises. On cancellation or failed payment, it reverses those grants. Well-designed plugins do this idempotently so retries do not create duplicate roles.

4. Handle subscription lifecycle events. Recurring payment plugins process renewal, refund, chargeback, upgrade, downgrade, and cancellation events. Most “donation store” plugins only handle one-time purchases and skip this layer entirely. If you want recurring supporter tiers (which is the highest-margin monetization model for most Hytale servers), you need a plugin that implements the full subscription lifecycle, not just a one-time checkout.

5. Surface admin controls. The plugin needs a way for the server operator to see what is happening: who subscribed, who churned, what the current MRR is, which payments failed. The best plugins push this to a web dashboard. The worst ones dump it into a log file.

Notably absent from that list: handling card data. No legitimate Hytale payment plugin should touch raw card numbers. All card entry happens in the payment processor's PCI-compliant checkout environment (Stripe Checkout, Tebex's hosted web store, etc.). The plugin only sees the result.

Every Hytale payment plugin installs roughly the same way. The specific file names and commands differ, but the shape is:

The whole setup typically takes 10-30 minutes depending on how familiar you are with the payment platform. Most of the time is spent on payment processor verification, not on the plugin itself.

The big architectural split among Hytale payment plugins is whether they treat your server as a satellite of an external web store or as the primary commerce surface. Everything else follows from this choice.

The two models have real trade-offs. External web stores are easier to customize visually and support more one-off product types (merch, gift cards, affiliated services). In-game stores win on subscription conversion, retention, and operational simplicity for community operators who are not running a full e-commerce catalog.

A second split: merchant-of-record (MoR) responsibility. Hytale's EULA, Section 7.7, states that the server operator “is the merchant of record and is solely responsible for pricing, fulfillment, customer service, refunds where required by applicable law, and compliance with consumer protection, advertising, tax, and payment laws.” With Arcalotl's Stripe Connect model, payouts go directly to your Stripe account and you literally are the merchant of record. With Tebex, Tebex acts as the MoR and handles chargebacks and tax compliance on your behalf (which can be convenient). Either model can comply with the EULA. The difference matters mainly for payout timing, fee transparency, and who absorbs fraud loss.

When evaluating a Hytale payment plugin, this is the short list of features that actually matter for revenue. The first four are table stakes; the last five are where the tools differentiate.

• Recurring subscription support. Not just one-time purchases. Monthly and annual billing, upgrade/downgrade flows, prorated billing changes.
• In-game perk automation. Role grants, cosmetic unlocks, private channel access, all handled automatically on payment events. No manual operator intervention.
• Webhook signature verification. The plugin validates that webhook events are actually coming from the payment processor, not a spoofed request. Non-negotiable for security.
• Compliance disclosure metadata. Gameplay-affecting tags, paid random item disclosure fields, refund policy surfacing. Hytale's Server Operator Policies require this for teen and mature servers.
• Automated dunning. Failed-payment recovery through DMs, in-game messages, or email sequences. Recovers 30-50% of involuntary churn on most communities. See the dunning glossary for the full breakdown.
• Cancel save flows. When a player cancels, the plugin presents a dynamic offer (discount, pause, downgrade) before the cancellation finalizes. Recovers 30-40% of attempted cancellations.
• Term optimization. Engaged monthly subscribers get an auto-prompt to upgrade to annual at a discount. Annual subscribers churn dramatically less than monthly ones.
• Analytics dashboard. MRR, churn rate, recovery rate, cancel save rate, average tier value. Not just “you made $500 last month” as a single number.
• Cross-platform subscriber management. If your community spans Hytale + Discord + other platforms, the plugin should manage subscriptions from one dashboard.

Of the Hytale payment plugins shipping in 2026, only Arcalotl covers all nine. Tebex covers the first four. PayNow, Tip4serv, and Buytale cover the first three with gaps. See the Tebex alternatives breakdown and the direct Tebex vs Arcalotl comparison for the specifics.

No payment plugin absolves you of compliance responsibility. Hytale's EULA, Section 7.7, states explicitly that the server operator is “the merchant of record and is solely responsible for pricing, fulfillment, customer service, refunds where required by applicable law, and compliance with consumer protection, advertising, tax, and payment laws.” A plugin can help you get compliant, but it cannot take the legal responsibility off you.

Whatever plugin you pick, you are still on the hook for:

• Truthful pricing and disclosures. Total price, renewal terms, material limitations, refund policy, all visible before checkout.
• Tagging gameplay-affecting purchases. Section 4.3 of the Policies requires teen/mature servers to disclose every gameplay-affecting purchase. Configure your tiers accordingly.
• Loot box disclosure (if applicable). Section 5 of the Policies requires numerical odds, expected spend, and a 12-month audit trail for any paid random items. For most community servers, this compliance load is higher than the revenue and not worth shipping.
• Prohibited categories. Section 4.1 bans NFTs, speculative crypto tokens, play-to-earn schemes, and real-money gambling on every server. Section 6 bans “double random” gacha chaining.
• Tax handling. Sales tax, VAT, GST where applicable. Most payment processors (Stripe Tax, Tebex's tax layer) can help with this, but you are responsible for filing.
• Age-gating. Section 7.9(c) of the EULA prohibits selling paid random items to identified minors. Arcalotl enforces this at the config level; other plugins require you to implement it yourself.

Read the full Hytale monetization pillar guide for the complete Policy breakdown with verbatim quotes. If you are running monetization without having read the Server Operator Policies end-to-end, stop and go read them first.