Tebex store integration

#Connecting the webhook

The dashboard gives your network its own webhook address and its own secret. Paste both into your Tebex panel. Every delivery is checked against that secret before we read a single field, and a delivery that fails the check is refused.

The address contains your network id, so it belongs to your network and to no other.

https://analytics.mcanalytics.net/api/v1/tebex/webhook/<your-network-id>

#How a purchase is matched

We read the transaction id, the amount, the currency, the package names, and the premium UUID of the buyer.

The UUID is the only thing we match on. Usernames are never used, because a username can be reused and a purchase credited to the wrong player is worse than a purchase credited to nobody.

Once the buyer is matched, the amount is credited to the source that player first joined through, however long ago that was.

#Unmatched purchases

A purchase we cannot match to a player on your network stays in an explicit unmatched group. It is counted in your totals and it is never quietly attached to the nearest guess.

The usual cause is a buyer who has not joined the network yet, or a Bedrock buyer whose store account carries no premium UUID.