Skip to Content
FluxStore is currently invite-only. Some sections of this documentation are still being written and expanded.
OrdersRefunds & Chargebacks

Refunds & Chargebacks

This page covers refunds — money you give back voluntarily. For chargebacks (when a customer disputes with their bank instead), see Chargebacks for the deeper guide on what they are, how to reduce them, and how to fight them.

Issuing a refund

Open the order in Dashboard > Orders and click Refund. FluxStore sends the refund through the original payment gateway (Stripe or PayPal), updates the order status, and runs your package’s Refund commands if you’ve configured any.

Issuing refunds requires the Issue Refunds permission and the Orders permission. Team members without both can see orders but can’t initiate refunds. See Team Management.

Partial vs full refunds

Refunds are full-amount by default. If you need to refund a partial amount (e.g. one item in a multi-item order), do it from your payment gateway’s dashboard (Stripe or PayPal) — FluxStore will pick up the partial refund via webhook and mark the order accordingly.

What happens to entitlements

Refunding revokes the customer’s entitlement, but commands that already ran don’t undo themselves. If you gave someone 64 diamonds on purchase, those diamonds don’t come back when you refund — unless you’ve configured a Refund command on the package to take them back.

Configure refund commands on each package under its command editor. They support the same variables ({player}, {uuid}, {transaction_id}) and per-server targeting as your initial commands. Common patterns:

lp user {player} parent remove vip
clear {player} diamond 64

Without refund commands, the player keeps what they were given. For permission-based perks (LuckPerms ranks, etc.) this matters a lot — they’ll still have VIP after you refund unless your refund command removes it.

Chargebacks (quick reference)

A chargeback is when a customer disputes a payment with their bank instead of asking you for a refund. The bank pulls the money back; you lose the sale and typically pay a dispute fee on top.

FluxStore handles chargebacks automatically when your payment gateway sends a dispute notification:

  1. The order’s status flips to chargebacked.
  2. Chargeback commands on the affected packages run automatically (separate from refund commands so you can be harsher — e.g. ban the player as well as revoke the rank).
  3. If Auto-Ban on Chargeback is enabled in your store’s checkout settings, FluxStore creates a permanent ban for the player matching their username, UUID, and IP.
  4. A dispute.opened webhook fires (if you have outgoing webhooks configured).

For the full story — what chargebacks are, why they happen, how to reduce them, and Stripe Chargeback Protection — see Chargebacks.

Next Steps

  • Managing Orders — viewing, filtering, and exporting orders
  • Chargebacks — deep guide on dispute handling and prevention
  • Bans — manage bans, including auto-bans from chargebacks
  • Fraud Protection — block repeat chargeback offenders before they buy
Global CommandsCustomer Profiles