PayNow integration

Your PayNow orders and subscriptions, on every player

PayNow is the least work to connect: you paste one API key and Analyse creates the webhooks in your store for you. Orders, refunds and subscriptions then land on the player who bought.

What PayNow does for you

Webhooks set up for you

Analyse creates one webhook per event in your PayNow store. Disconnect and it deletes them again. If someone removes one, Recreate webhooks puts it back.

Subscriptions and renewals

Activations, renewals and cancellations are recorded, and each renewal's payment counts as revenue, marked apart from first payments and one-time purchases.

Refunds and chargebacks

Refunds mark the refunded lines or the whole order. A chargeback marks the order, and a chargeback closed in your favour sets it back to completed.

Creator codes and coupons

The affiliate link code becomes the creator code and the coupon is recorded too, when the optional permissions are on the key's role.

Java, Bedrock and gifts

Orders match on the Minecraft UUID. Bedrock buyers with an Xbox account match their Floodgate UUID, and gifts count for the recipient, not the buyer.

Past orders included

Choose Import past payments in the setup dialog to bring in your order history, with refunded and chargeback orders marked as such.

How you'd use it

Which source brings subscribers who stay

The situation

You sell a monthly VIP subscription on PayNow and advertise on two server lists with their own hostnames.

With Analyse

Renewals and cancellations land on each subscriber, so you can compare players from each list on whether they keep renewing, not just whether they bought once.

A creator's affiliate link at checkout

The situation

A streamer shares a PayNow affiliate link during a live event and players buy crate keys through it.

With Analyse

Those purchases carry the affiliate code and count for the campaign that owns it, even for viewers who joined your server through a different address.

A gifted rank on a crossplay server

The situation

A Java player gifts a rank to a Bedrock friend who joins through Geyser and Floodgate.

With Analyse

The purchase counts for the Bedrock recipient's profile, matched through their Floodgate UUID, so the rank sits on the player who actually uses it.

Set it up

  1. 1

    Make a role for Analyse

    In PayNow, open Access, then Roles, and create a role named Analyse with read access to your store, orders and payments, plus permission to manage webhooks.

  2. 2

    Create an API key with that role

    Open Integrations, then API Keys, create a key with the Analyse role and copy its token.

  3. 3

    Paste it and connect webhooks

    In your game's Settings, Integration, pick PayNow and paste the token. Analyse checks every permission, then Connect webhooks creates them in your store.

  4. 4

    Import past payments

    Choose Import past payments so your earlier orders come in and revenue charts start full.

Questions

What permissions does the PayNow API key need?

View Store, View Orders, View Payments, View Webhooks, Create Webhooks and Delete Webhooks. View Subscriptions, Affiliate Links, Coupons and Products are optional and add more detail.

Do I need to add webhooks in PayNow myself?

No. Analyse creates one webhook per event in your store and keeps each webhook's signing secret encrypted. When you disconnect, it deletes the webhooks it created.

Does it track PayNow subscriptions?

Yes. Subscription activations, renewals and cancellations are recorded, and each renewal is also counted as a payment.

Can I import my PayNow order history?

Yes, from the setup dialog with Import past payments. Importing history is part of the paid plans, from Starter up.

What if my API key can see more than one store?

Analyse asks you to pick the store that sells for this game. To share one store across several games, connect it to the studio and map packages to games.

Connect one game and see it for yourself.

Free to start, 14 days of Pro, and about four minutes of setup.