Emberstore logo

Emberstore

An in-game store for Paper servers. Players browse /store, pay in a checkout dialog through the gateway you choose, and get their reward once the payment is confirmed, even if they logged off in the meantime.

Read the docsGet it
  • Paper 1.21.7 and newer
  • Java 21 or newer
  • 11 payment gateways
  • SQLite, H2, MySQL or MariaDB

Features

What is in the box

Every card goes to the page that documents it, config keys and all.

Store menus
Categories and items live in YAML files. Add a file, reload, and a new category appears in /store.
Read more
Checkout dialogs
A real Minecraft dialog with the price, a code field, gifts and quantity. Older clients get a chest menu.
Read more
Eleven gateways
Stripe, PayPal, Razorpay, Creem, Dodo Payments and six crypto gateways. Turn on the ones you use.
Read more
Prices and currencies
Write prices once in your own currency. Gateways that bill in another one get a converted price.
Read more
Sales, codes and referrals
Timed sales, promo codes with use limits, and referral codes that reward the player who shared them.
Read more
Timed items
Ranks for 30 days, renewal reminders, and real subscriptions on the gateways that support them.
Read more
Refunds and take-backs
A refund or chargeback takes the reward back by itself, once, even if the player is offline.
Read more
Web dashboard
Revenue, orders, stock and gateway health in your browser. Read-only, with one-time login links.
Read more

Why this one

Built so a payment is never granted twice or lost

01

One path for every payment

A signed webhook, a status lookup when the webhook never came, and a test simulation all go through the same handler. A repeated message from a gateway is ignored, so nobody gets their rank twice.

A payment that is short, in the wrong currency, or late is never granted on its own. It is marked for review and staff are told.

How payments are confirmed
Signed webhooks, reconciliation lookups and test simulations all feed one status handler, which completes, reviews, reverses or ends the order.
02

Works for every player who joins

Java players on 1.21.6 or newer get the checkout dialog. Bedrock players and older clients get a chest menu instead, and both end at the same payment link in chat.

Dialogs and the menu fallback
A player on a 1.21.6 or newer Java client gets the checkout dialog. Bedrock players, older clients through ViaVersion, or servers with dialogs turned off get a chest menu, and both end at the same payment link.
03

Ready for networks

Put every server on one MySQL or MariaDB database. One server takes the payments, and the reward is delivered on whichever server the player is playing on.

Set up a network
Several servers share one MySQL or MariaDB database. Only the server with webhook.enabled true receives payments, and each server delivers rewards to the players online on it.

Inside the docs

Drawn, not just described

The pages carry diagrams of the parts that are easier to see than to read.

Six steps of a purchase: menu click, checkout dialog, order created, payment page, payment confirmed, reward delivered.
From click to reward
Every step a purchase goes through, from the menu click to the reward command.
Open the page
The checkout picker dialog with each part labelled with the dialogs/checkout.yml key that controls it.
Anatomy of the checkout dialog
Which line of the dialog files draws which part of the dialog.
Open the page

Quick start

Taking payments in four steps

  1. 1

    Drop in the jar

    Put the jar in your plugins folder on a Paper server and start it once.

  2. 2

    Turn on a gateway

    Fill in one gateway section of config.yml with its keys and set enabled to true.

  3. 3

    Point webhooks at you

    Set webhook.public-base-url to an HTTPS address that reaches the listener.

  4. 4

    Fill your store

    Edit the category files, run /store admin reload, and open /store.

Full installation guide

Try it all first with test mode, no real money needed.

Everything is documented

Every config key, every command and every permission has a page. If something is still unclear, ask in the Discord.

Read the docsDownloadGet support

Emberstore is by zArrowTan. The Discord is the only support channel, there is no public issue tracker.