> For the complete documentation index, see [llms.txt](https://docs.tebex.io/creators/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tebex.io/creators/tebex-checkout/checkout-seller-actions.md).

# Checkout Seller Actions

Manage users, transactions, and payments confidently with this guide to **Tebex Checkout seller actions**. Learn how to change usernames or Discord IDs, resend commands, ban problematic users, and access customer insights.

> ⚠️ **Important**: Some features outlined below require the **Plus Plan**. Upgrade your plan [here](https://creator.tebex.io/billing/plans).

***

### Table of Contents

1. Changing a Username or User ID
2. Changing a Discord ID
3. Resending Commands
   * Resend All Commands
   * Resend a Specific Command
4. Customer Lookup
5. Checkout Bans

***

### 1. Changing a Username or User ID

Only update a username or ID if it was entered **incorrectly during checkout**. Misuse may result in buyers receiving **duplicate items**.

#### Steps:

1. Go to your **Payments** page.
2. Use the **Transaction ID** filter to find the payment.
3. In the transaction details, click **Change** next to the username.
4. Enter the **correct Username or ID**, then click **Update**.
5. Click **Resend** to reissue commands associated with the updated username.

> **Tip**: Use the **Notes** section to record this change for future reference.

***

### 2. Changing a Discord ID

Only change the Discord ID if:

* The user entered the wrong ID.
* They logged in using the wrong account.

Always verify using **server logs and role data** to prevent abuse.

#### Steps:

1. Locate the payment using the **Transaction ID**.
2. Under the **Packages** section, click **Details**.
3. Click **Change** next to the Discord ID field.
4. Enter the correct **Discord ID** (not the username).
   * Help the user find their [Discord ID here](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID).
5. Click **Update**, then **Resend** the Discord command.

***

### 3. Resending Commands

> ⚠️ Use caution when resending commands to prevent **duplicate deliveries**.

#### Resend All Commands

1. Locate the transaction in **Payments**.
2. Scroll to the **Commands** section.
3. Review the details, then click **Resend**.

#### Resend a Specific Command

1. Scroll to the **Processed Commands** area.
2. Identify the specific command.
3. Click **Resend** next to that command only.

***

### 4. Customer Lookup

⭐ **Plus Plan Required**

This feature allows you to review player activity and detect potential fraud.

#### Available Data:

* Username & ID (with first seen/cache expiration info)
* Total spend
* Chargeback rate
* Store bans
* Payment history

#### 🔍 How to Use:

1. Navigate to **Customers > Lookup**.
2. Enter a **username**, **email**, **IP**, or **ID**.

Useful for:

* Customer support follow-up
* Ban evaluations
* Fraud detection

***

### 5. Checkout Bans

⭐ **Plus Plan Required**

Prevent users from making future purchases.

#### How to Ban a User:

1. Go to **Customers > Bans**.
2. Click **Create Ban**.
3. Choose the identifier (Username, UUID, IP Address).
4. (Optional) Add a **reason**.
5. Click **Ban**.

#### Managing Bans:

* Review bans in the **Bans** section.
* Click **View Reason** or **Unban** to reverse the restriction.

> ⚠️ **Reminder**: Only authorized users should manage bans.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tebex.io/creators/tebex-checkout/checkout-seller-actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.