Payment instance setup guide

Last update: October 11, 2026

This guide shows how to set up your payment instance without waiting for support: where to get each token and credential, what goes into each field, and how to test before you start selling. Everything happens under My account → your license → Instance tab → Configuration. In the dashboard, every field has a Where to get it link (opens the provider's official dashboard) and a Step by step link (opens the matching part of this guide).

Tokens, keys, secrets, passwords, and the instance URL are the sole responsibility of the customer. MMMods Store is not responsible for any leak, exposure, or misuse of these credentials, or for the resulting damages, to the maximum extent permitted by law.

See section 5 of the Terms of UseOpen My account

1. Overview

The payment instance receives purchases made inside your DayZ server (MM_ModPack mod) and talks to your payment provider. The money goes straight to your Mercado Pago or Stripe account: MMMods Store does not intermediate or hold the funds.

What you need

  • An active license for the payment-instance product.
  • For PIX: a Mercado Pago account with a registered Pix key and activated production credentials.
  • For cards and international checkout: a Stripe account enabled to accept payments.
  • For the in-game CFTools panel (optional): a server registered on CFCloud with a Basic or higher subscription.

Process summary

  1. Open My account → your license → Instance tab → Configuration.
  2. Tick the methods you will use: PIX, Stripe, and/or CFTools. Each method's fields appear once ticked.
  3. Fill in the fields following the sections below.
  4. Click Save Configuration.
  5. Copy the Endpoint URL and paste it into the payments field of the mod's admin panel.
  6. Make a low-value test purchase and check the result in the Dashboard tab.

2. Security and responsibility for credentials

Tokens, keys, secrets, passwords, and the instance URL itself give access to your accounts and your money. Treat all of them like passwords.

  • Get credentials only from the providers' official dashboards (the links in this guide go straight to them).
  • The MMMods team never asks for tokens, passwords, secrets, or the instance URL. For support, share only the Instance ID.
  • Do not send credentials, or screenshots showing them, in tickets, Discord, AI support chat, videos, or streams.
  • Turn on two-factor authentication at Mercado Pago, Stripe, CFTools, and Discord.
  • Once saved, secret fields show as [configurado]. To replace one, clear it and type the new value; to keep it, leave the field alone.
  • Suspect a leak? Regenerate the credential in the provider's dashboard, update it here, and if the instance URL leaked, use Generate new URL.

Under section 5 of the Terms of Use, credentials belong to the customer and are the customer's responsibility. MMMods Store is not responsible for any leak, exposure, or misuse of tokens, keys, passwords, URLs, or other credentials, or for any resulting charges, refunds, account blocks, or other damages, to the maximum extent permitted by law.

3. Instance URL (goes into the mod)

At the top of the Instance tab you will find the Endpoint URL. It already contains your instance's integration key and is the only thing the mod needs:

  1. Click Copy.
  2. In game, open the MM_ModPack admin panel and paste it into the payments URL field (MM_URLPaymentsAPI).
  3. Save in the mod and restart the server so it loads the enabled methods.

The same URL serves the store (PIX/Stripe) and the CFTools panel. It does not change when you save the configuration.

Generate new URL creates a new key and invalidates the previous one immediately: the mod's store and CFTools panel stop working until you paste the new URL. Use it only if the URL leaked.

If the dashboard says the instance has no key yet, save the configuration once to generate the URL.

4. General fields

Application Name

Optional. Your store or server name. It appears on the Stripe payment page next to the number of coins (e.g. My Server DayZ Coins 100).

Discord Webhook URL

Optional. Posts to a channel on your Discord a log of admin actions taken through the in-game CFTools panel (kick, ban, priority queue, whitelist, RCon, Architect, and others).

  1. In Discord, open Server Settings → Integrations → Webhooks → New Webhook.
  2. Pick a private staff channel and click Copy Webhook URL.
  3. Paste it into the field. The URL starts with https://discord.com/api/webhooks/.

Do not confuse it with the PIX webhook: the Discord webhook does not receive payment notifications. Anyone with this URL can post to the channel, so keep it secret. Official Discord help

5. PIX (Mercado Pago)

To sell with PIX you use your own Mercado Pago account. Before you start:

  • have a registered Pix key on the Mercado Pago account that will receive the money;
  • create an application under Your integrations and activate the production credentials.

With PIX ticked, MercadoPago Token and PIX Webhook Secret are required: without the webhook secret (at least 32 characters) the dashboard will not save.

MercadoPago Token (Access Token)

  1. Go to Your integrations with the account that will receive payments.
  2. Open your application (or create one with Create application).
  3. In the side menu, open Production → Production credentials. If they are not active yet, enter your industry and website and click Activate production credentials.
  4. Copy the Access Token (starts with APP_USR-) and paste it into the MercadoPago Token field.

Use the production Access Token. The Public Key, Client ID, and Client Secret are not used here. Official documentation

PIX Webhook Secret and PIX Webhook URL

The webhook tells your instance as soon as a PIX is paid, and the secret signature proves the notice really came from Mercado Pago.

  1. Under Your integrations, open the same application as the Access Token.
  2. In the side menu, click Webhooks → Configure notifications.
  3. Under Production mode, enter your instance's webhook URL: https://mmmods.store/payments-api/INSTANCE_ID/pix/webhook. Replace INSTANCE_ID with the Instance ID shown in the dashboard. The dashboard shows this URL ready to copy.
  4. Under events, tick Payments (payment).
  5. Click Save. Mercado Pago generates the secret signature: reveal it and copy it.
  6. Paste the signature into the PIX Webhook Secret field.
  7. In the PIX Webhook URL field, click Use this URL (the same as step 3) or leave it empty, since it is already registered at Mercado Pago.

If you reset the signature at Mercado Pago, paste the new one here; otherwise payment notices will be rejected. Official documentation

MX validation

Checks that the domain of the e-mail a player registers in game exists and accepts mail, avoiding charges with invalid e-mails. Keep it on Validate email domain (MX).

6. Stripe (cards and other methods)

Stripe opens a payment page (Stripe Checkout) for the player. With Stripe ticked, Stripe Secret Key and Stripe Webhook Secret are required.

Currency: with PIX also enabled, the mod charges in BRL on Stripe; with only Stripe enabled, in USD. Make sure your Stripe account accepts that currency.

Stripe Secret Key

  1. Open API keys in the Stripe Dashboard with test mode turned off.
  2. On the Secret key row, reveal and copy the key (starts with sk_live_).
  3. Paste it into the Stripe Secret Key field.

The publishable key (pk_live_) is not used here. To test before selling, use the sk_test_ key with a webhook created in test mode, then replace both with the live ones.

Stripe Webhook Secret

  1. Open Webhooks in the Stripe Workbench and click Create an event destination (or Add endpoint).
  2. Select Your account.
  3. For the payload format, choose Snapshot (do not use Thin).
  4. Select these events:
    • checkout.session.completed
    • checkout.session.expired
    • checkout.session.async_payment_succeeded
    • checkout.session.async_payment_failed
  5. Choose Webhook endpoint and enter the URL: https://mmmods.store/payments-api/INSTANCE_ID/stripe/webhook. The instance dashboard shows this URL ready to copy.
  6. On the new endpoint's page, reveal the Signing secret (starts with whsec_) and paste it into Stripe Webhook Secret.

Test-mode and live-mode secrets are different: use the one from the same mode as your secret key. Official documentation

Stripe Success URL and Stripe Cancel URL

Optional. Where the player goes after paying or cancelling at checkout. If empty, they see a simple page saying they can close the tab. If you fill them in, use full https:// addresses (e.g. your server's website or Discord).

7. CFTools (in-game panel)

Turns on the in-game CFTools panel: online players, bans, priority queue, whitelist, leaderboard, GameLabs, and, optionally, Architect. It uses the same instance URL.

Requirement: the server must be on CFCloud with a Basic or higher subscription. On the Free plan, CFTools blocks the server API (the test reports Free plan), and no setting here can change that.

CFTools Application ID and Application Secret

  1. Go to developer.cftools.cloud/applications with your CFTools account.
  2. Create an application (or open an existing one).
  3. Copy the Application ID and Secret into the CFTools Application ID and CFTools Application Secret fields.

Both fields are required to turn CFTools on. Data API documentation

Grant access to the server and ban list

The application only sees what you authorize.

  1. Once the Application ID is filled in, the dashboard shows the Grant access on CFTools link (format https://app.cftools.cloud/authorize/YOUR_APPLICATION_ID).
  2. Open the link while logged into CFCloud, select the server and the ban list, and confirm.
  3. Back in the dashboard, save and click Test CFTools connection. Grants may take a few minutes to show up.

This link is not a key: do not paste it into any field.

Server API ID

It can stay empty when the application has a grant for a single server: it is discovered automatically. To fill it in:

  • Easiest: after the test, click Use this server in the grants list and save.
  • Manual: on CFCloud, open the server → Settings → API Key and copy the Server ID (UUID format, with hyphens).

Do not use the code in the browser's address bar or the "API Key" on that screen: that key belongs to the game plugin and is not used here.

Ban list ID

It can stay empty when there is a grant for a single ban list. To fill it in, click Use this ban list after the test or copy the ban list ID from the Ban manager.

Enterprise token and GDS API key

Leave them empty unless CFTools issued them for your account. The Enterprise token is only for Enterprise accounts. The GDS API key is the Gameserver Data Service key and adds statistics to the server overview. The grant link (app.cftools.cloud/authorize/...) is not a GDS key.

Blocked actions

Optional. A comma-separated list of actions the in-game panel can not run, not even for admins. Accepts an exact action or a group ending in .*.

Examples: server.rcon,bans.add · arch.* (turns off all of Architect) · gl.action,vip.sync.

Groups: server.* (server, messages, RCon, leaderboard), players.* and player.* (players), bans.* (bans), qp.* (priority queue), wl.* (whitelist), gl.* (GameLabs), vip.* (VIP sync), and arch.* (Architect).

Test the connection

  1. Save the configuration: the test uses the saved data.
  2. Click Test CFTools connection.
  3. Check the capabilities (Data API, Ban list, GameLabs, Architect, GDS) and the grants list. If something fails, the message says why; see Troubleshooting.

Show latest calls shows what the in-game panel has run.

8. Architect (optional)

Lets the in-game panel start, stop, restart, back up, and read the console of the server through the CFTools Architect agent installed on the server machine. If you do not use Architect, leave every field empty. Once the URL is filled in, username, password, and Server ID become required.

Agent URL

Public address of the agent in the format https://host:port (the agent's default port is 8090), with nothing after the port. E.g. https://myserver.com:8090. The address must be reachable from the internet: local network IPs (192.168.x.x, 10.x.x.x), localhost, and similar are rejected. Open the port in the machine's firewall.

Agent username and password

Create a user just for the site in the Architect Manager (Add new User); the initial password is shown when it is created. See the Architect users documentation.

A dedicated user can be removed at any time without affecting other access. The agent has broad access to the server machine: treat this user as administrator access, use a strong unique password, and block anything you do not need under Blocked actions.

Server ID on the agent

The identifier you gave the server when you created it in the Architect Manager (e.g. Server-1). It is not the CFTools Server API ID.

TLS fingerprint (optional)

  • Agent behind a domain with a valid certificate (e.g. Let's Encrypt): leave it empty.
  • Agent with a self-signed certificate (the install default): save without the fingerprint and run the test. The error message shows the certificate's SHA-256. Confirm it is your agent's, paste it here (accepts AA:BB:... or plain hex), save, and test again.

If the agent's certificate changes, update this field.

9. Turn it on and test

  1. Save the configuration. If something required is missing, the dashboard says what and does not save.
  2. Make sure the Endpoint URL is pasted into the mod.
  3. Restart the server so the mod loads the enabled methods.
  4. In game, register an e-mail and make a low-value test purchase.
  5. Follow the transaction in the instance's Dashboard tab and check the payment in the Mercado Pago or Stripe dashboard.
  6. For CFTools, open the in-game panel: the header should say Connected.

10. Troubleshooting

Message or symptom What to do
On save: "PIX_WEBHOOK_SECRET deve ter pelo menos 32 caracteres" Paste the Mercado Pago webhook secret signature into PIX Webhook Secret (step by step).
On save: "STRIPE_WEBHOOK_SECRET deve ter pelo menos 32 caracteres" Paste the whsec_ secret of the Stripe webhook endpoint (step by step).
On save: "Preencha Application ID e Secret da CFTools" Fill in both fields or untick CFTools.
On save: "GDS API key inválida: isso é um link" You pasted the grant link into the GDS field. Clear the field and open the link in your browser.
On save: Architect agent URL error Use https://host:port, with no path, ?, or username/password in the URL.
In-game purchases stopped after Generate new URL Paste the new URL into the mod and restart the server.
"MERCADO_PAGO_ACCESS_TOKEN nao configurado" Fill in the MercadoPago Token and save.
PIX paid, but confirmation is slow The mod checks the status by itself every few seconds. Make sure the webhook is registered at Mercado Pago and the secret signature is the current one.
A player cannot register their e-mail The e-mail domain does not accept mail. Ask for another e-mail.
Stripe shows webhook deliveries failing with 400 Wrong secret or from the other mode (test × live), or Thin format. Use the whsec_ of the right endpoint and the Snapshot format.
CFTools test: credentials rejected Check the Application ID and Secret and wait 1 minute before testing again.
CFTools test: no grant Open the Grant access on CFTools link and grant the server and ban list.
CFTools test: Free plan Subscribe the server to Basic or higher on CFCloud.
CFTools test: Server API ID missing or ambiguous More than one server is granted: click Use this server and save.
Architect: address not allowed The URL points to a local network. Use a public address.
Architect: unreachable or certificate error Closed port, agent down, or self-signed certificate without a fingerprint (step by step).
"Instance not yet provisioned" Wait a few minutes after purchase. If it persists, open a ticket.

Need help? Open a ticket through the official channels with only the Instance ID and the error message. Never send tokens, passwords, secrets, or the instance URL.

← Back to store