Staff Guide

Payments

The Payments feature lets you create Robux payment links that customers can pay in-game through Developer Products. Each link is a shareable URL that guides the customer through the purchase flow.

Required capability

payments.manage to create and view payment links.

How payments work#

The payment flow is:

  • You (the seller) create a Payment Link with one or more items and a total Robux amount.
  • You share the link URL with the customer (e.g., via Discord or in-game chat).
  • The customer visits the link at /pay/[token] — this page is public, no login required.
  • In-game, the RoPerms Payments SDK detects the customer joining and prompts them with the matching Developer Product.
  • After successful purchase, the link is automatically marked PAID.
  • The link page shows a confirmation; you are notified via the dashboard.

Payment categories & items#

Your org admin configures Payment Categories and Payment Itemsin Settings. Categories group related items (e.g., "Gamepasses", "Services"). Items have a name and a Robux price.

As a staff member with payments.manage, you select items from this catalogue when creating a link. You cannot add items outside the defined catalogue.

Click Payments in the sidebar, then New Link. Fill in:

  • Customer — the Roblox username of the buyer.
  • Items — select one or more items from the catalogue. The total Robux amount is calculated automatically.
  • Note — optional private note (not shown to the customer).

After creation, the link URL is shown. Copy and send it to the customer.

  • PENDING — created, waiting for the customer to pay.
  • PAID — the Developer Product purchase was confirmed by the SDK.
  • CANCELLED — you or an admin manually cancelled the link.
  • EXPIRED — the link was not paid within the expiry window (set by admin in Settings).

Tracking payments#

The Payments list page shows all links you have created, their status, and the total Robux value. Filters let you view only PENDING, PAID, or CANCELLED links.

Click any link to see its full detail, including the items purchased, the customer's Roblox username, the receipt ID from the Developer Product purchase, and timestamps.

Orders#

If your org uses the Orders feature (a separate system from payment links), theOrders badge in the sidebar shows how many orders are pending fulfilment. Orders are submitted by in-game scripts and represent product or service requests that need to be manually fulfilled.

In-game setup

For the payment flow to work, your org admin must have installed RoPermsPayments.lua and configured Developer Product IDs for each Robux amount. Ask them if customers are not being prompted in-game.