PayNow

https://guides.paynow.gg
Admin
PayNow is a platform designed to help game server owners monetize their servers by providing tools...
Tokens:66,103
Snippets:127
Trust Score:8
Update:1 year ago
Show doc for...
Tokens:
Raw
### PayNow GG Payout Setup Details

Source: https://guides.paynow.gg/getting-started/creating-a-store

Details the information required for setting up payouts, including personal contact information, payment methods, and tax documentation.

```English
Address: Enter your contact information, including your email, phone number, and address.
Payment Method: Select how you want to receive your payouts (e.g., PayPal or bank transfer).
Tax Forms: Provide any necessary tax documentation based on your location. For U.S. companies, a 1099-K form will be issued at the end of the year for tax reporting purposes.
Review and Confirm: Verify your details and save your settings.
```

--------------------------------

### PayNow GG Store Creation Steps

Source: https://guides.paynow.gg/getting-started/creating-a-store

Outlines the sequential steps required to launch a store on PayNow GG, including product creation, server integration, payout setup, and verification.

```English
1. Create a Product
2. Link a Game Server
3. Setup Payouts
4. Verify Your Identity
5. Wait for Store Review
6. Enable Live Mode
```

--------------------------------

### Affiliate Link Setup Parameters

Source: https://guides.paynow.gg/marketing/affiliate-links

Details the parameters required for setting up an affiliate link, including general details, lifetime/renewal options, commission structure, discount options, and tracking settings.

```APIDOC
Affiliate Link Setup:
  General Details:
    Affiliate Code: Unique code for checkout or referral URL.
    Wallet ID: PayNow Wallet ID for commission payments.
  Lifetime & Renewal:
    Enabled: Boolean to activate the affiliate link.
    Credit for Subscription Renewals: Boolean to apply commissions to recurring payments.
  Commission Details:
    Commission Type: 'percentage'
    Commission Amount: Percentage value for affiliate earnings per sale.
  Discount Options:
    Discount Type: Optional discount type for customer using affiliate code.
  Tracking Settings:
    Referrer Type: 'first' or 'last' referrer gets credit.
    Tracking Length: Duration for tracking cookie validity (e.g., '7 days').
```

--------------------------------

### Creating and Managing Sales

Source: https://guides.paynow.gg/marketing

This guide explains how to create and manage sales on the PayNow.gg platform. It covers setting up different types of sales, applying discounts, and tracking their performance.

```APIDOC
Sales Management:
  - Creating a Sale:
    - Navigate to the 'Sales Page' on your PayNow.gg dashboard.
    - Define sale details including name, duration, and discount type.
  - Sale Details:
    - Configure specific discount percentages or fixed amounts.
    - Set conditions for sale application (e.g., specific products, customer groups).
  - Sale Lifetime:
    - Define the start and end dates/times for the sale.
  - Discount Details:
    - Specify the type of discount (e.g., percentage off, fixed amount off).
  - Sale Application:
    - Determine which products or services the sale applies to.
  - Redeem Requirements:
    - Set criteria for customers to be eligible for the sale (e.g., minimum purchase amount).
  - Orders using this sale:
    - View a list of orders that have utilized a specific sale.
```

--------------------------------

### Connect Game Server

Source: https://guides.paynow.gg/integration

Steps to connect a game server with PayNow for syncing the store and executing commands. This involves adding the server on the dashboard, associating products, downloading and installing a plugin, and running a command in the server console.

```APIDOC
1. Visit the Game Servers page on your dashboard.
2. Click 'Add Game Server.'
3. Enter your server's name and select the option for executing commands.
4. Associate products from your created list with this server.
5. Download the plugin for your specific game.
6. Install the plugin on your server and run the prompted command in the server's console.
7. Verify the server is added on the Game Servers page. Details, token reset, or command re-run are available by clicking on the server.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/appearance/navlinks

This section provides documentation for the PayNow API, covering various endpoints for managing stores, products, customers, and more. It includes details on authentication, request/response formats, and usage examples.

```APIDOC
API Keys:
  - Endpoint: /api/keys
  - Method: GET
  - Description: Retrieves a list of API keys associated with the account.
  - Authentication: Requires a valid API key in the Authorization header.
  - Response:
    - status: "success" or "error"
    - data: Array of API key objects, each containing 'key_id', 'name', 'created_at'.

Webhooks:
  - Endpoint: /api/webhooks
  - Method: POST
  - Description: Registers a new webhook to receive real-time event notifications.
  - Authentication: Requires a valid API key.
  - Request Body:
    - url: The URL to send webhook events to (string, required).
    - events: An array of event types to subscribe to (e.g., ['order.created', 'payment.succeeded']) (array of strings, required).
  - Response:
    - status: "success" or "error"
    - data: Object containing the newly created webhook details, including 'webhook_id', 'url', 'events', 'created_at'.

Discord Placeholders:
  - Description: Information on available placeholders for use in Discord messages via webhooks.
  - Placeholders:
    - {order_id}: The ID of the order.
    - {customer_name}: The name of the customer.
    - {product_name}: The name of the product purchased.
    - {total_amount}: The total amount of the order.

Steam Templates:
  - Description: Details on using Steam-specific templates for product delivery or notifications.

Minecraft Templates:
  - Description: Details on using Minecraft-specific templates for product delivery or notifications.
```

--------------------------------

### Connect Game Server

Source: https://guides.paynow.gg/integration/game-servers

Steps to connect a game server with PayNow for syncing the store and executing commands. This involves adding the server on the dashboard, associating products, downloading and installing a plugin, and running a command in the server console.

```APIDOC
1. Visit the Game Servers page on your dashboard.
2. Click 'Add Game Server.'
3. Enter your server's name and select the option for executing commands.
4. Associate products from your created list with this server.
5. Download the plugin for your specific game.
6. Install the plugin on your server and run the prompted command in the server's console.
7. Verify the server is added on the Game Servers page. Details, token reset, or command re-run are available by clicking on the server.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/content/subscriptions

This section provides comprehensive API documentation for PayNow, covering various endpoints and functionalities for integrating with the PayNow platform. It includes details on authentication, available resources, request/response formats, and usage examples.

```APIDOC
API Keys:
  Description: Manages API keys for accessing PayNow services.
  Endpoints:
    GET /api/keys: Retrieve a list of all API keys.
    POST /api/keys: Create a new API key.
      Request Body:
        name: string (Name for the API key)
    DELETE /api/keys/{key_id}: Delete an existing API key.

Webhooks:
  Description: Manages webhook subscriptions for real-time event notifications.
  Endpoints:
    GET /webhooks: List all active webhooks.
    POST /webhooks: Create a new webhook subscription.
      Request Body:
        url: string (The URL to send webhook events to)
        events: array of strings (List of events to subscribe to, e.g., 'order.created', 'subscription.updated')
    DELETE /webhooks/{webhook_id}: Delete a webhook subscription.

Discord Placeholders:
  Description: Information on placeholders available for Discord notifications.
  Placeholders:
    {user.name}: The username of the user.
    {product.name}: The name of the product purchased.
    {order.total}: The total amount of the order.

Steam Templates:
  Description: Templates for integrating with Steam for product delivery or notifications.

Minecraft Templates:
  Description: Templates for integrating with Minecraft for product delivery or notifications.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/faq/packages-faq/resending-commands

This section details the PayNow API, including endpoints, methods, parameters, and return values for integrating with PayNow services.

```APIDOC
API Keys:
  - Description: Manage API keys for secure access to PayNow services.
  - Endpoints:
    - GET /api/keys: Retrieve a list of your API keys.
    - POST /api/keys: Create a new API key.
      - Request Body:
        - name: string (required) - A descriptive name for the API key.
        - permissions: array of strings (optional) - Specific permissions to grant to the key.
      - Response:
        - id: string - The unique identifier for the API key.
        - key: string - The generated API key.
        - name: string - The name of the API key.
        - created_at: string - Timestamp of key creation.
    - DELETE /api/keys/{key_id}: Delete an existing API key.
      - Parameters:
        - key_id: string (path) - The ID of the API key to delete.
      - Response:
        - message: string - Confirmation message.

Webhooks:
  - Description: Configure and manage webhooks to receive real-time notifications from PayNow.
  - Endpoints:
    - GET /webhooks: Get a list of configured webhooks.
    - POST /webhooks: Create a new webhook.
      - Request Body:
        - url: string (required) - The URL to send webhook events to.
        - events: array of strings (required) - The events to subscribe to (e.g., 'order.created', 'payment.succeeded').
      - Response:
        - id: string - The unique identifier for the webhook.
        - url: string - The configured webhook URL.
        - events: array of strings - The subscribed events.
        - created_at: string - Timestamp of webhook creation.
    - DELETE /webhooks/{webhook_id}: Delete a webhook.
      - Parameters:
        - webhook_id: string (path) - The ID of the webhook to delete.
      - Response:
        - message: string - Confirmation message.

Discord Placeholders:
  - Description: Available placeholders for use in Discord notifications via webhooks.
  - Placeholders:
    - {{customer.name}}: The name of the customer.
    - {{order.id}}: The ID of the order.
    - {{product.name}}: The name of the product purchased.
    - {{amount}}: The total amount of the order.

Steam Templates:
  - Description: Templates for formatting messages related to Steam.

Minecraft Templates:
  - Description: Templates for formatting messages related to Minecraft.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/store/global-commands

Documentation for the PayNow API, covering endpoints, methods, and parameters for integrating with the PayNow platform.

```APIDOC
API Keys:
  - Used for authenticating API requests.
  - Generate and manage API keys in the 'Integration' section.

Webhooks:
  - Configure webhooks to receive real-time notifications about events.
  - Supported events include order creation, subscription changes, etc.
  - Discord Placeholders:
    - {user.name}: Displays the user's name.
    - {product.name}: Displays the product's name.
  - Steam Templates:
    - Used for formatting messages sent to Steam users.
  - Minecraft Templates:
    - Used for formatting messages sent to Minecraft servers.

Global Commands:
  - Commands that execute automatically across all products.
  - Configuration Options:
    - Stage:
      - On Purchase: Triggered immediately after purchase.
      - On Expire: Triggered when a subscription expires.
      - On Renew: Triggered on subscription renewal.
      - On Refund: Triggered when an order is refunded.
      - On Chargeback: Triggered if a chargeback occurs.
    - Command: The command to execute.
    - Game Servers to Execute On: Specifies the game servers where the command should run.
  - Creating a Global Command:
    1. Navigate to the 'Global Commands' tab.
    2. Click 'New global command'.
    3. Configure Stage, Command, and Game Servers.
```

--------------------------------

### API Documentation

Source: https://guides.paynow.gg/content/products/duplicate-a-product

Provides access to PayNow's API for integration and management. Includes details on API keys, webhooks, and related functionalities.

```APIDOC
API Keys:
  - Manages API keys for secure access to PayNow services.

Webhooks:
  - Configure and manage webhooks for real-time event notifications.
  - Discord Placeholders: Information on using Discord placeholders in webhook messages.
  - Steam Templates: Templates for integrating Steam data via webhooks.
  - Minecraft Templates: Templates for integrating Minecraft data via webhooks.
```

--------------------------------

### Assigning Multiple Deliverable Actions

Source: https://guides.paynow.gg/getting-started/faq/packages-faq

Explains how to assign multiple deliverable actions to a package by using the 'Add Action' button in the Deliverable Actions section. It lists examples of actions like assigning roles, executing commands, granting gift cards, and providing access to downloadable files. It also notes that webhooks need separate setup.

```text
When creating or editing a package, scroll to the **Deliverable Actions** section and click **"Add Action"**. You can stack multiple actions, such as:
  * **Assigning a Discord Role**
  * **Executing a game server command**
  * **Granting a Gift Card**
  * **Giving access to Downloadable Files**

**Webhooks must be set up separately** through the Webhooks page.
For more help about webhooks, visit the [Webhooks Guide](https://guides.paynow.gg/integration/webhooks) We also provide **default webhook templates** for [Minecraft](https://guides.paynow.gg/integration/webhooks/minecraft-templates) and [Steam](https://guides.paynow.gg/integration/webhooks/minecraft-templates)-based games.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/faq/packages-faq/discord-linking

This section outlines the PayNow API, including endpoints for managing various aspects of your store, such as products, orders, customers, and integrations. It details authentication, request methods, and response formats.

```APIDOC
API Keys:
  - Endpoint: /api/v1/keys
  - Method: POST
  - Description: Generate a new API key for accessing the PayNow API.
  - Request Body:
    - name: string (required) - A descriptive name for the API key.
    - permissions: array of strings (optional) - Specific permissions to grant to the key.
  - Response:
    - key: string - The generated API key.
    - name: string - The name of the API key.
    - permissions: array of strings - The permissions associated with the key.

Webhooks:
  - Endpoint: /api/v1/webhooks
  - Method: POST
  - Description: Register a webhook to receive real-time notifications about events.
  - Request Body:
    - url: string (required) - The URL to send webhook events to.
    - events: array of strings (required) - A list of events to subscribe to (e.g., 'order.created', 'payment.succeeded').
  - Response:
    - id: string - The unique identifier for the webhook subscription.
    - url: string - The registered webhook URL.
    - events: array of strings - The subscribed events.

Discord Linking:
  - Functionality: Integrate your Discord server with PayNow for automated role management.
  - Setup:
    1. Create a Discord Server Integration in PayNow.
    2. Connect the PayNow Bot to your Discord Server.
    3. Assign Discord Roles in Deliverable Actions.
    4. Manage Discord-Based Purchases through PayNow.
  - Placeholders:
    - Discord Placeholders: Used in webhook templates for dynamic content.
    - Steam Templates: For integrating Steam-related data.
    - Minecraft Templates: For integrating Minecraft-related data.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started

This section provides API documentation for PayNow, detailing endpoints, methods, and parameters for integrating with the PayNow platform. It covers various functionalities like managing orders, subscriptions, customers, and products.

```APIDOC
API Keys:
  - Description: Manage API keys for secure access to the PayNow API.
  - Endpoints:
    - GET /api-keys: Retrieve a list of your API keys.
    - POST /api-keys: Create a new API key.
    - DELETE /api-keys/{key_id}: Delete an existing API key.

Webhooks:
  - Description: Configure webhooks to receive real-time notifications for events.
  - Endpoints:
    - GET /webhooks: List configured webhooks.
    - POST /webhooks: Create a new webhook.
    - PUT /webhooks/{webhook_id}: Update an existing webhook.
    - DELETE /webhooks/{webhook_id}: Delete a webhook.
  - Event Types:
    - order.created
    - subscription.updated
    - payment.failed
  - Placeholders:
    - Discord Placeholders: Special variables for Discord notifications.
    - Steam Templates: Templates for Steam-related notifications.
    - Minecraft Templates: Templates for Minecraft-related notifications.

Orders:
  - Description: Manage customer orders.
  - Endpoints:
    - GET /orders: List all orders.
    - GET /orders/{order_id}: Retrieve details of a specific order.

Subscriptions:
  - Description: Manage customer subscriptions.
  - Endpoints:
    - GET /subscriptions: List all subscriptions.
    - GET /subscriptions/{subscription_id}: Retrieve details of a specific subscription.
    - POST /subscriptions/{subscription_id}/cancel: Cancel a subscription.

Customers:
  - Description: Manage customer information.
  - Endpoints:
    - GET /customers: List all customers.
    - GET /customers/{customer_id}: Retrieve details of a specific customer.
    - PUT /customers/{customer_id}: Update customer information.

Products:
  - Description: Manage products offered in your store.
  - Endpoints:
    - GET /products: List all products.
    - POST /products: Create a new product.
    - GET /products/{product_id}: Retrieve details of a specific product.
    - PUT /products/{product_id}: Update product information.
    - POST /products/{product_id}/duplicate: Duplicate an existing product.

Analytics:
  - Description: Access sales and performance analytics.
  - Endpoints:
    - GET /analytics/sales: Retrieve sales data.
    - GET /analytics/performance: Retrieve performance metrics.

Marketing:
  - Description: Tools for marketing campaigns.
  - Endpoints:
    - GET /coupons: List available coupons.
    - POST /coupons: Create a new coupon.
    - GET /gift-cards: List gift cards.
    - POST /gift-cards: Create a new gift card.
    - GET /affiliate-links: Manage affiliate links.
    - GET /abandoned-checkouts: View abandoned checkouts.
    - POST /purchase-follow-ups: Configure purchase follow-up emails.

Access Control:
  - Description: Manage user access and roles.
  - Endpoints:
    - GET /team-members: List team members.
    - POST /team-members: Add a new team member.
    - GET /roles: List available roles.
    - POST /roles: Create a new role.
    - GET /roles/{role_id}/permissions: View permissions for a role.
    - POST /bans: Manage bans.

Billing:
  - Description: Manage payouts and billing information.
  - Endpoints:
    - GET /payouts: View payout history.
    - GET /billing: Access billing information.

Store Settings:
  - Description: Configure your store's settings.
  - Endpoints:
    - GET /store/settings: Retrieve store settings.
    - PUT /store/settings: Update store settings.
    - GET /store/global-commands: Manage global commands.
    - GET /store/custom-variables: Manage custom variables.
```

--------------------------------

### Example Usage of Custom Variables in Commands

Source: https://guides.paynow.gg/store/custom-variables

Demonstrates how to reference custom variables like {kit}, {name}, and {slots} within store commands. It shows the executed commands based on customer input for a VIP package sale.

```text
oxide.usergroup add {customer.steam.id} {kit}
say "{customer.name} just purchased the {kit} package!"
o.grant user {customer.steam.id} backpacks.size.{slots}
```

```text
oxide.usergroup add 7656119XXXXXXXXXXX gold
say "Lord just purchased the gold package!"
o.grant user 7656119XXXXXXXXXXX backpacks.size.6
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/creating-a-store

This section provides API documentation for PayNow, covering various endpoints and functionalities for integrating with the PayNow platform. It includes details on API keys, webhooks, and specific data structures.

```APIDOC
API Keys:
  - Purpose: Used for authenticating API requests.
  - Management: Accessible via the 'API Keys' section in the integration settings.
  - Security: Treat API keys like passwords; do not share them publicly.

Webhooks:
  - Purpose: To receive real-time notifications about events occurring in PayNow (e.g., new orders, payment confirmations).
  - Configuration: Set up webhook URLs in the 'Webhooks' section.
  - Events: Subscribe to specific events to receive relevant data.
  - Placeholders: Supports Discord and Steam/Minecraft templates for customizing webhook messages.
    - Discord Placeholders: Used for dynamic content in Discord notifications.
    - Steam Templates: For formatting data related to Steam.
    - Minecraft Templates: For formatting data related to Minecraft.

Integration:
  - Game Servers: Connect and manage game servers within PayNow.
  - Discord Servers: Link and manage Discord servers for notifications and integration.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/faq/packages-faq

This section provides API documentation for PayNow, covering various endpoints for managing stores, products, customers, orders, and more. It includes details on authentication, request/response formats, and available parameters.

```APIDOC
API Keys:
  - Endpoint: /api/v1/keys
  - Method: GET
  - Description: Retrieves a list of API keys associated with the account.
  - Authentication: Requires a valid API key in the Authorization header.
  - Response:
    - status: "success" or "error"
    - data: Array of API key objects, each containing id, key, name, and created_at.

Webhooks:
  - Endpoint: /api/v1/webhooks
  - Method: POST
  - Description: Registers a new webhook to receive event notifications.
  - Authentication: Requires a valid API key.
  - Request Body:
    - url: The URL to send webhook events to (string, required).
    - events: An array of event types to subscribe to (array of strings, optional).
  - Response:
    - status: "success" or "error"
    - data: Object containing the newly created webhook's id and url.

Discord Placeholders:
  - Description: Provides a list of placeholders that can be used in Discord messages sent via webhooks.
  - Placeholders:
    - {{customer.name}}: The name of the customer.
    - {{product.name}}: The name of the product purchased.
    - {{order.id}}: The ID of the order.

Steam Templates:
  - Description: Templates for formatting messages related to Steam game keys or items.

Minecraft Templates:
  - Description: Templates for formatting messages related to Minecraft server access or items.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/content/products/creating-a-product

This section details the PayNow API, covering endpoints for managing various aspects of the platform such as products, orders, customers, and integration settings. It includes information on authentication, request/response formats, and available parameters.

```APIDOC
API Keys:
  - Manages API key generation and management for secure access to the PayNow API.
  - Provides endpoints for creating, retrieving, and revoking API keys.

Webhooks:
  - Configures and manages webhook endpoints for real-time event notifications.
  - Supports custom payloads and event filtering.
  - Includes placeholders for Discord, Steam, and Minecraft templates.

Products:
  - Endpoints for creating, retrieving, updating, and deleting products.
  - Supports product details, pricing, stock management, and deliverable actions.
  - Includes options for product images, custom variables, and lifetime/stock settings.

Orders:
  - Manages the lifecycle of customer orders.
  - Includes endpoints for retrieving order details, status updates, and associated customer information.

Customers:
  - Manages customer data, including contact information and purchase history.
  - Provides functionality for retrieving and managing customer profiles.

Subscriptions:
  - Handles subscription management, including creation, renewal, and cancellation.
  - Allows retrieval of subscription details and customer subscription status.

Game Servers & Discord Servers:
  - Integration points for connecting PayNow with game servers and Discord servers.
  - Facilitates automated delivery and management of digital goods.

Appearance Settings:
  - Customization options for the webstore appearance, including tags, navlinks, and branding.

Marketing Tools:
  - Features for managing sales, coupons, gift cards, affiliate links, abandoned checkouts, and purchase follow-ups.

Access Control:
  - Manages team members, roles, and permissions for granular access control.
  - Includes functionality for managing bans.

Billing & Payouts:
  - Handles billing information and payout management.
  - Provides access to billing history and payout details.
```

--------------------------------

### Discord Server Integration Guide

Source: https://guides.paynow.gg/integration/discord-servers

This guide explains how to integrate your Discord server with PayNow, covering the steps for creating the integration, connecting the PayNow bot, and managing existing connections.

```APIDOC
Step 1: Creating a Discord Server Integration
  - Navigate to your PayNow store settings.
  - Go to the 'Integrations' section.
  - Select 'Discord Server' and click 'Create Integration'.
  - Follow the on-screen prompts to authorize PayNow with your Discord account.

Step 2: Connecting the PayNow Bot to Your Discord Server
  - After creating the integration, you will be prompted to invite the PayNow bot to your server.
  - Click the 'Invite Bot' button.
  - Select the Discord server you wish to add the bot to.
  - Grant the necessary permissions for the bot.

Re-linking or Deleting a Discord Server Connection:
  - To re-link or delete a connection, go to the 'Integrations' section in your PayNow store settings.
  - Find your Discord Server integration and choose 'Re-link' or 'Delete'.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/marketing

This section outlines the API endpoints and functionalities available for integrating with PayNow.gg. It covers key areas such as managing API keys, setting up webhooks, and understanding data structures for game servers and Discord servers.

```APIDOC
API Keys:
  - Purpose: Generate and manage API keys for secure access to PayNow services.
  - Usage: Obtain keys from the 'Integration' section of your PayNow dashboard.

Webhooks:
  - Purpose: Receive real-time notifications about events occurring within PayNow.
  - Configuration: Set up webhook URLs in the 'Integration' section.
  - Event Types: Supports events related to orders, subscriptions, and customer actions.
  - Placeholders: Includes Discord and Steam/Minecraft template placeholders for dynamic message content.

Integration with Game Servers and Discord Servers:
  - Game Servers: Information on integrating PayNow with game server platforms.
  - Discord Servers: Details on linking PayNow functionalities with Discord servers, including placeholder usage for messages.
```

--------------------------------

### Resending Commands Guide

Source: https://guides.paynow.gg/getting-started/faq/packages-faq/resending-commands

Instructions on how to manually resend commands for purchased packages, useful for failed or undelivered purchases.

```Markdown
# Resending Commands
Learn how to manually resend commands for purchased packages in case of failed executions or delivery issues.

**When Should You Resend Commands?**
You may need to resend commands if:
  * A **server restart** caused the original command to fail.
  * The **customer did not receive their purchase** due to a temporary issue.
  * The command execution status shows as **failed** or **pending**.

**How to Resend Commands**
[Detailed steps on how to resend commands would typically be found here, possibly with screenshots or command examples.]

**Frequently Asked Questions**
[This section would address common questions related to resending commands.]
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/wallet-account

This section outlines the available API endpoints and functionalities for integrating with PayNow. It covers authentication, data retrieval, and management of various PayNow resources.

```APIDOC
API Keys:
  - Purpose: Used for authenticating API requests.
  - Management: Generate, view, and revoke API keys through the PayNow dashboard.

Webhooks:
  - Purpose: Receive real-time notifications about events within PayNow (e.g., new orders, subscription changes).
  - Configuration: Set up webhook endpoints to receive POST requests from PayNow.
  - Event Types: Orders, Subscriptions, Payments, etc.
  - Data Format: JSON payload containing event details.
  - Security: Use signature verification to ensure payload integrity.

Discord Placeholders:
  - Purpose: Utilize placeholders in Discord messages triggered by PayNow events.
  - Examples: {userName}, {orderId}, {productName}.

Steam Templates:
  - Purpose: Customize messages for Steam-related integrations.

Minecraft Templates:
  - Purpose: Customize messages for Minecraft-related integrations.
```

--------------------------------

### Store Platform Configuration

Source: https://guides.paynow.gg/store

Configure the platform for your PayNow store. Selecting the correct platform ensures optimized features for your store's specific needs.

```text
Platform:
  * **Platform** : Choose your platform from the dropdown menu. Selecting the appropriate platform (e.g., Rust) ensures the features are optimized for your store’s needs.
```

--------------------------------

### Creating Navlinks

Source: https://guides.paynow.gg/appearance/navlinks

This guide explains how to create custom navigation links (Navlinks) in your PayNow store. Navlinks improve user experience by providing quick access to product categories, which are defined by Tags.

```APIDOC
Navlinks:
  - Purpose: Create custom buttons in the store's navigation bar.
  - Prerequisites: Requires at least one Tag to be created.
  - Steps:
    1. Create Tags: Group your products using the Tags feature.
    2. Navigate to Navlinks Page: Go to https://dashboard.paynow.gg/navlinks.
    3. Add Navlinks: Select the desired tags to display as navigation buttons.
```

--------------------------------

### Subscription Statuses

Source: https://guides.paynow.gg/content/customers/managing-customers

Defines the possible statuses for customer subscriptions.

```APIDOC
Subscription Status:
  - Active: The subscription is currently active.
  - Canceled: The subscription has been canceled.
  - Created: The subscription has been created but may not be active yet.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/integration/discord-servers

This section details the PayNow API, including endpoints, methods, parameters, and return values for various functionalities such as managing products, orders, customers, and integrations.

```APIDOC
API Keys:
  - Endpoint: /api/v1/keys
  - Methods:
    - GET /api/v1/keys: Retrieve a list of all API keys.
      - Returns: Array of API key objects.
    - POST /api/v1/keys: Create a new API key.
      - Request Body:
        - name: string (required) - Name for the API key.
        - permissions: array of strings (optional) - Permissions to grant.
      - Returns: Newly created API key object.
    - DELETE /api/v1/keys/{key_id}: Delete an API key.
      - Parameters:
        - key_id: string (path parameter) - The ID of the API key to delete.
      - Returns: Success message.

Webhooks:
  - Endpoint: /api/v1/webhooks
  - Methods:
    - GET /api/v1/webhooks: Retrieve a list of configured webhooks.
      - Returns: Array of webhook objects.
    - POST /api/v1/webhooks: Create a new webhook.
      - Request Body:
        - url: string (required) - The URL to send webhook events to.
        - events: array of strings (required) - Events to subscribe to (e.g., 'order.created', 'payment.succeeded').
        - secret: string (optional) - A secret to use for signing webhook events.
      - Returns: Newly created webhook object.
    - PUT /api/v1/webhooks/{webhook_id}: Update an existing webhook.
      - Parameters:
        - webhook_id: string (path parameter) - The ID of the webhook to update.
      - Request Body: (Same as POST)
      - Returns: Updated webhook object.
    - DELETE /api/v1/webhooks/{webhook_id}: Delete a webhook.
      - Parameters:
        - webhook_id: string (path parameter) - The ID of the webhook to delete.
      - Returns: Success message.

Discord Placeholders:
  - Description: Information on available placeholders for Discord messages via webhooks.
  - Placeholders:
    - {customer.name}: Name of the customer.
    - {order.id}: ID of the order.
    - {product.name}: Name of the product.
    - {payment.amount}: Amount of the payment.

Steam Templates:
  - Description: Templates for formatting messages related to Steam.

Minecraft Templates:
  - Description: Templates for formatting messages related to Minecraft.
```

--------------------------------

### Order Statuses

Source: https://guides.paynow.gg/content/customers/managing-customers

Defines the possible statuses for customer orders.

```APIDOC
Order Status:
  - Created: Order generated but not completed.
  - Completed: Order successfully processed.
  - Chargeback: Order has been chargebacked.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/appearance/tags

This section provides API documentation for PayNow, covering various functionalities for integrating with the platform. It includes details on API keys, webhooks, and specific integration points like game servers and Discord servers.

```APIDOC
API Keys:
  - Purpose: Used to authenticate and authorize requests to the PayNow API.
  - Management: Accessible via the 'API Keys' section in the integration settings.
  - Security: Treat API keys like passwords; do not share them publicly.

Webhooks:
  - Purpose: To receive real-time notifications from PayNow about events such as new orders, payments, or customer updates.
  - Configuration: Set up webhook URLs in the 'Webhooks' section.
  - Event Types: Supports various event types, including order creation, payment confirmation, etc.
  - Placeholders: Supports Discord and Steam placeholders for dynamic message content.
    - Discord Placeholders: Used for customizing messages sent to Discord.
    - Steam Templates: For formatting messages related to Steam.
    - Minecraft Templates: For formatting messages related to Minecraft.

Integration:
  - Game Servers: Information on integrating PayNow with game servers.
  - Discord Servers: Information on integrating PayNow with Discord servers.
```

--------------------------------

### PayNow API Documentation

Source: https://guides.paynow.gg/getting-started/faq

This section provides API documentation for PayNow, detailing endpoints, methods, and parameters for integrating with the PayNow platform. It covers various functionalities like managing orders, subscriptions, customers, and products.

```APIDOC
API Keys:
  - Description: Manage API keys for secure access to the PayNow API.
  - Endpoints:
    - GET /api-keys: Retrieve a list of your API keys.
    - POST /api-keys: Create a new API key.
    - DELETE /api-keys/{key_id}: Delete an existing API key.

Webhooks:
  - Description: Configure webhooks to receive real-time notifications for events.
  - Endpoints:
    - GET /webhooks: List configured webhooks.
    - POST /webhooks: Create a new webhook.
    - PUT /webhooks/{webhook_id}: Update an existing webhook.
    - DELETE /webhooks/{webhook_id}: Delete a webhook.
  - Event Types:
    - order.created
    - subscription.updated
    - payment.failed
  - Placeholders:
    - Discord Placeholders: Special variables for Discord notifications.
    - Steam Templates: Templates for Steam-related notifications.
    - Minecraft Templates: Templates for Minecraft-related notifications.

Orders:
  - Description: Manage customer orders.
  - Endpoints:
    - GET /orders: List all orders.
    - GET /orders/{order_id}: Retrieve details of a specific order.

Subscriptions:
  - Description: Manage customer subscriptions.
  - Endpoints:
    - GET /subscriptions: List all subscriptions.
    - GET /subscriptions/{subscription_id}: Retrieve details of a specific subscription.
    - POST /subscriptions/{subscription_id}/cancel: Cancel a subscription.

Customers:
  - Description: Manage customer information.
  - Endpoints:
    - GET /customers: List all customers.
    - GET /customers/{customer_id}: Retrieve details of a specific customer.
    - PUT /customers/{customer_id}: Update customer information.

Products:
  - Description: Manage products offered in your store.
  - Endpoints:
    - GET /products: List all products.
    - POST /products: Create a new product.
    - GET /products/{product_id}: Retrieve details of a specific product.
    - PUT /products/{product_id}: Update product information.
    - POST /products/{product_id}/duplicate: Duplicate an existing product.

Analytics:
  - Description: Access sales and performance analytics.
  - Endpoints:
    - GET /analytics/sales: Retrieve sales data.
    - GET /analytics/performance: Retrieve performance metrics.

Marketing:
  - Description: Tools for marketing campaigns.
  - Endpoints:
    - GET /coupons: List available coupons.
    - POST /coupons: Create a new coupon.
    - GET /gift-cards: List gift cards.
    - POST /gift-cards: Create a new gift card.
    - GET /affiliate-links: Manage affiliate links.
    - GET /abandoned-checkouts: View abandoned checkouts.
    - POST /purchase-follow-ups: Configure purchase follow-up emails.

Access Control:
  - Description: Manage user access and roles.
  - Endpoints:
    - GET /team-members: List team members.
    - POST /team-members: Add a new team member.
    - GET /roles: List available roles.
    - POST /roles: Create a new role.
    - GET /roles/{role_id}/permissions: View permissions for a role.
    - POST /bans: Manage bans.

Billing:
  - Description: Manage payouts and billing information.
  - Endpoints:
    - GET /payouts: View payout history.
    - GET /billing: Access billing information.

Store Settings:
  - Description: Configure your store's settings.
  - Endpoints:
    - GET /store/settings: Retrieve store settings.
    - PUT /store/settings: Update store settings.
    - GET /store/global-commands: Manage global commands.
    - GET /store/custom-variables: Manage custom variables.
```
Tokens:
Raw