Audit ChestShop taxes with one low-value transaction
A seller receiving less than the displayed price may be paying a configured transaction tax. Measure the debit and credit around one trade before treating the difference as missing money.
Before you start
ChestShop connects a sign, stock container and economy account. Test the buyer and seller separately: permission to create a shop does not prove stock access or payment works. Read the installed release documentation before changing signs on public shops.
Work through the check
- Read the active ChestShop tax settings and any exemption permissions for the installed release; record the previous configuration.
- Choose a test seller and buyer with known balances, using the same economy backend and world as the affected market.
- Make a single purchase and compare buyer debit, seller credit and any documented tax-account movement.
- Repeat with an account that lacks exemptions, then compare a staff role only if your policy intentionally treats it differently.
What to compare
Include the shop owner, customer and any configured tax recipient in the balance record. A missing amount may be an intentional tax destination rather than a lost transfer between the two visible participants.
Confirm the result
The observed difference should match the configured tax calculation and destination. No unexplained second charge should appear when a menu or another plugin wraps the transaction.
If the result differs
Rounding, bundle size and permission exemptions can change the result. Avoid evaluating tax from a leaderboard or cached display; use the provider’s direct balances and transaction timestamp.
Recover safely
Restore the original tax rule if the trial does not match your policy. Correct only the verified test differences and review public pricing before applying a server-wide tax change.
Documentation and related help
Check the ChestShop maintainer documentation and ChestShop maintainer reference against your installed release before applying changes.