Przejdź do treści
Biblioteka skilli
Programowanie · Integracja z narzędziem

merchant-setup

/merchant-setup

Prowadzi przez założenie konta sprzedawcy Xsolla, uzyskanie kluczy API, różnice między kluczami konta i projektu oraz tryb sandbox do testów Pay Station.

Repozytorium
xsolla-ai-kit ↗
Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
11
Przestarzałość

Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Prowadzi przez założenie konta sprzedawcy Xsolla, uzyskanie kluczy API, różnice między kluczami konta i projektu oraz tryb sandbox do testów Pay Station.

Oryginalny opis (EN)

Guide for setting up a new Xsolla merchant account and obtaining API credentials. Use this skill whenever a user needs to create an Xsolla Publisher Account, get API keys, understand the difference between merchant-level and project-level API keys, set up sandbox mode for testing, or asks how to start integrating with Xsolla Pay Station. Also trigger when a user says they want to accept payments via Xsolla, start an Xsolla integration, or test Xsolla payments. Claude Code cannot create the account on behalf of the user — this skill provides the exact steps the user must complete manually befor

Jak działa

  1. Step 0: Check for Existing Credentials
  2. Step 1: Create a Publisher Account
  3. Step 2: Extract IDs from a Publisher Account URL
  4. Step 3: Generate a Project-Level API Key
  5. Step 4: Sandbox Mode — No Contract Needed
  6. Quick Reference
  7. Step 5: Write Credentials to .env
  8. Checklist
Sekcje z nagłówków SKILL.md, w oryginale · 179 linii, 945 słów
Podgląd SKILL.md
---
name: merchant-setup
description: Guide for setting up a new Xsolla merchant account and obtaining API credentials. Use this skill whenever a user needs to create an Xsolla Publisher Account, get API keys, understand the difference between merchant-level and project-level API keys, set up sandbox mode for testing, or asks how to start integrating with Xsolla Pay Station. Also trigger when a user says they want to accept payments via Xsolla, start an Xsolla integration, or test Xsolla payments. Claude Code cannot create the account on behalf of the user — this skill provides the exact steps the user must complete manually before integration can begin.
metadata:
  owner: y-klochikhin
  domain: orchestrator
---

# Merchant Setup

AI Agent **cannot** create an Xsolla account automatically. The user must complete the registration steps manually.

## Step 0: Check for Existing Credentials

**Before anything else**, check for a `.env` file in the project root:

```bash
# Check if .env exists and contains Xsolla variables
cat .env 2>/dev/null | grep -E "XSOLLA_MERCHANT_ID|XSOLLA_PROJECT_ID|XSOLLA_PROJECT_API_KEY"
```

**If all three variables are present and non-empty** — credentials are already configured. Report them to the user (show names and values, except mask the API key as `****`) and proceed directly with the integration. Skip all steps below.

```
✅ Found in .env:
   XSOLLA_MERCHANT_ID=887981
   XSOLLA_PROJECT_ID=308077
   XSOLLA_PROJECT_API_KEY=****  (set)
```

**If the file is missing or any variable is absent** — walk the user through the steps below, then write the credentials to `.env` at the end ([Step 5](#step-5-write-credentials-to-env)).

---

## Step 1: Create a Publisher Account

Direct the user to: **https://publisher.xsolla.com/signup**

### Individual vs. Company account

| | Individual | Company |
|---|---|---|
| **When to use** | Just testing, evaluating Xsolla, quick sandbox setup | Committed to going live, need a contract |
| **Registration** | Simple — email, Google, or social login | Requires company details for the licensing agreement |
| **Contract** | Still needed for live payments, but can skip for sandbox | Submit from the Agreements tab once ready |

For pure exploration and sandbox testing, an individual account is the fastest path. The user can always add company details later when submitting the licensing agreement.

> Publisher Account uses two-factor authentication. Confirmation code is sent to the registered email.

---

## Step 2: Extract IDs from a Publisher Account URL

The user doesn't need to hunt for IDs — they're embedded in every Publisher Account URL. Parse them directly if the user shares a link.

URL pattern:
```
https://publisher.xsolla.com/{merchant_id}/projects/{project_id}/...
```

Examples:
- `https://publisher.xsolla.com/887981/settings/api_key` → **merchant_id = 887981**
- `https://publisher.xsolla.com/887981/projects/308077/edit/api_key` → **merchant_id = 887981**, **project_id = 308077**

If the user doesn't share a URL, tell them:
- **Merchant ID**: visible in the URL on any Publisher Account page, or under `Company settings → Company`
- **Project ID**: visible in the sidebar next to the project name, or in the URL when inside a project

---

## Step 3: Generate a Project-Level API Key

> ⚠️ **Critical**: The API key is shown **only once** at creation time. It is never sent by email. The user must copy and save it immediately — it cannot be recovered.

For standard integration, the **project-level key** is sufficient.

- Location: `Project settings → API key`
- Direct URL: `https://publisher.xsolla.com/{merchant_id}/projects/{project_id}/edit/api_key`
- Scope: this project only
- Auth format: `Authorization: Basic Base64({project_id}:{api_key})`

To generate:
1. Open the URL above (with the real IDs)
2. Click **Create**
3. Copy and store the value immediately

### Merchant-level API key (optional)

Only needed for Xsolla CLI or API calls where the endpoint URL has **no `project_id`** path parameter.

- Location: `Company settings → API keys` → `https://publisher.xsolla.com/{merchant_id}/settings/api_key`
- Auth format: `Authorization: Basic Base64({merchant_id}:{api_key})`

**Rule of thumb**: if the API endpoint URL contains `{project_id}`, use the project-level key. If it doesn't, use the merchant-level key.

---

## Step 4: Sandbox Mode — No Contract Needed

> ℹ️ Development can start **immediately** after account creation — no signed contract required.

A project-level API key is all that's needed to run a full sandbox integration: create tokens, test the payment UI, configure the catalog.

When going live, the only change needed is switching the mode from `sandbox` to production in the integration. Everything else stays the same.

What requires a **signed licensing agreement** (submit from the **Agreements** tab in Publisher Account):
- Accepting real payments from end users
- Completing the Tax Interview (W-8 for non-US / W-9 for US)

Contract review typically takes a few business days — submit it well before the planned launch date.
Full go-live checklist (utils probe, flip sandbox flags, deploy, live payment tests): **`production`**.

---

## Quick Reference

| Resource | URL |
|----------|-----|
| Sign up | https://publisher.xsolla.com/signup |
| Publisher Account | https://publisher.xsolla.com |
| API Reference | https://developers.xsolla.com/api |
| Getting started guide | https://developers.xsolla.com/get-started/work-in-pa/create-first-project/ |
| FAQ — API keys | https://developers.xsolla.com/dev-resources/faq/general/#faq_project_settings |

---

## Step 5: Write Credentials to .env

Once all credentials are confirmed, write them to `.env` in the project root. Use the `XSOLLA_*` variable names — other skills depend on these exact names.

**If `.env` already exists**, append or update only the Xsolla variables without touching existing content:

```bash
# Remove only this skill's own three keys. Deleting every ^XSOLLA_ line also erases
# keys other skills record there, such as XSOLLA_BUILD_PATH from shop-plan.
sed -i.bak -E '/^XSOLLA_(MERCHANT_ID|PROJECT_ID|PROJECT_API_KEY)=/d' .env && rm .env.bak
cat >> .env << EOF

# Xsolla credentials
XSOLLA_MERCHANT_ID={merchant_id}
XSOLLA_PROJECT_ID={project_id}
XSOLLA_PROJECT_API_KEY={api_key}
EOF
```

**If `.env` does not exist**, create it:

```bash
cat > .env << EOF
# Xsolla credentials
XSOLLA_MERCHANT_ID={merchant_id}
XSOLLA_PROJECT_ID={project_id}
XSOLLA_PROJECT_API_KEY={api_key}
EOF
```

After writing, confirm to the user:
```
✅ Written to .env:
   XSOLLA_MERCHANT_ID={merchant_id}
   XSOLLA_PROJECT_ID={project_id}
   XSOLLA_PROJECT_API_KEY=****
```

> ⚠️ Remind the user to add `.env` to `.gitignore` if it isn't there already — the API key must not be committed to version control.

```bash
grep -q "^\.env" .gitignore 2>/dev/null || echo ".env" >> .gitignore
```

---

## Checklist

- [ ] `.env` checked for existing credentials (Step 0)
- [ ] Publisher Account created (individual or company)
- [ ] Merchant ID known
- [ ] Project ID known
- [ ] Project-level API key generated and saved securely
- [ ] Credentials written to `.env`
- [ ] `.env` added to `.gitignore`
- [ ] *(Optional)* Merchant-level API key saved — only needed for CLI or cross-project API calls

Once credentials are in `.env`, proceed with the integration.

Wersje

W bazie nie ma innych skilli o nazwie merchant-setup.

Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.

Migawka bazy z 13.11.2026 · wersja paczki 4d95ebd5b07e (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100headless-checkout-integration
    Integruje Xsolla Headless Checkout, w pełni konfigurowalny interfejs płatności sterowany przez klienta z @xsolla/pay-station-sdk i danymi karty w izolowanych iframe, w tym wybór metody płatności i płatności w sandboxie.
  • 100shop-setup
    Pomaga zbudować i wdrożyć sklep w kodzie lub osadzić Xsolla w istniejącym sklepie.
  • 100jpm-merchant-integrations
    Implementuje w projekcie sprzedawcy integracje API J.P. Morgan Payments po uwierzytelnieniu OAuth: Checkout, Online Payments, Tokenization, 3-D Secure, Account Updater i Reporting.
  • 100react-native-pay
    Dodaje Apple Pay i Google Pay do aplikacji React Native przez Nitro Modules, z konfiguracją merchant ID i obsługą tokenów płatniczych po stronie serwera.
  • 100dodo-best-practices
    Wprowadza w integrację Dodo Payments: podstawy Merchant of Record, instalacja SDK i klienta, środowiska testowe i produkcyjne, klucze API oraz kanoniczny przepływ od checkoutu do webhooka.
  • 100click-integration
    Prowadzi integrację płatności Click z uzbeckim Click SuperApp: API SHOP i Merchant, prepare i complete, fiskalizacja, przycisk i faktura Click, tokeny kart, checkout.js, SDK mobilne oraz kody błędów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.