production
Skill9 starsChanged 5 months agoMITView on GitHub
Takes Xsolla payments from sandbox to real money. Headless Checkout and Pay Station follow the same steps: licensing agreement, tax interview, switching off sandbox, a public HTTPS webhook, and a live payment checklist. Use for "go live", "leave sandbox", "switch my shop to production", "Merchant contract not signed", or error 0002-0004.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- miisodev/skillstheir own version, first seen Oct 15, 2026
- lavine888/Accounting-Red-Flag-Detectortheir own version, first seen Sep 23, 2026
- Mothilal-M/agentflow-skillstheir own version, first seen Apr 25, 2026
- vstorm-co/production-stack-skillstheir own version, first seen Apr 16, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- vstorm-co/production-stack-skills★ 25same name
- lavine888/Accounting-Red-Flag-Detector★ 0same name
- miisodev/skills★ 0same name
- Mothilal-M/agentflow-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/xsolla-ai-kit.mdcCursor rule
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- productionSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shopbuilder-translateSkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
- catalog-designSkill
- description-to-shopSkill
- game-web-portalSkill
- headless-checkout-integrationSkill
- login-setupSkill
- login-stylingSkill
- merchant-setupSkill
- nocode-shop-setupSkill
- quest-setupSkill
- shop-builder-assemblySkill
- shopbuilder-translateSkill
- shop-setupSkill
- webhooks-implSkill
- xla-pagesSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
If the licensing agreement is missing, expect an error like:
- Distinctive: line 61
If utils succeeds without that error, the merchant can issue production tokens — continue to config flip + deploy.
- Distinctive: line 76
Follow the PA flow (Complete application form, company/individual details).
- Distinctive: line 87
Keep a single env/config switch so sandbox ↔ production stays easy (do not hard-delete sandbox code paths).
- Very specific: line 101
Update .env (and hosting secrets).
- Distinctive: line 112
If the user hosts the storefront, deploy it.
- Very specific: line 114
If a backend grants the purchase, register a stable public HTTPS webhook URL in Publisher Account (webhooks-impl).
- Distinctive: line 164
Start a method that leaves the page (e.g.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Production / go-live
Move a working sandbox payment integration to real-money payments. The steps are the same whether the payment UI is Headless Checkout or Pay Station. Most steps are manual for the developer; the agent prepares config, checks for contract errors, and hands a test plan — it cannot complete live card or wallet payments.
Docs: Legal aspects (Licensing Agreement)
When to use
- Sandbox payments already work
- Developer wants live payments / leave sandbox
- Token or Pay Station returns Merchant contract not signed /
0002-0004/support_code00020004
Step 1 — Prove the contract gap (agent)
Mint a production payment token the same way this integration already mints
a sandbox token (omit sandbox / set sandbox: false). Then hit Pay Station
utils with that token:
GET https://secure.xsolla.com/paystation2/api/utils?access_token={TOKEN}If the licensing agreement is missing, expect an error like:
{
"errors": [
{
"message": "We're experiencing a technical issue…",
"support_code": "00020004"
}
]
}(Also reported as 0002-0004 / Merchant contract not signed.)
If utils succeeds without that error, the merchant can issue production tokens — continue to config flip + deploy.
Step 2 — Sign the licensing agreement (human)
Ask the developer to complete Agreements in Publisher Account:
https://publisher.xsolla.com/{XSOLLA_MERCHANT_ID}/agreement(XSOLLA_MERCHANT_ID from .env — see merchant-setup.)
Follow the PA flow (Complete application form, company/individual details). Xsolla reviews (often a few business days). After approval, status becomes Signed. Then complete the Tax interview (W-8 / W-9) under Agreements & taxes — required for live payouts/reporting.
Re-run Step 1 (production token → utils). The contract error must be gone.
Step 3 — Flip the integration to production mode (agent + human)
Keep a single env/config switch so sandbox ↔ production stays easy (do not hard-delete sandbox code paths). Change only the rows for the payment UI this shop uses.
Typical changes:
| Area | Sandbox | Production |
| Env | XSOLLA_SANDBOX=true (or equivalent) | false / unset per project convention |
| Token body | "sandbox": true / settings.mode: "sandbox" | omit sandbox / sandbox: false |
| Headless SDK | init({ sandbox: true, … }) | sandbox: false |
| Pay Station / return URLs | localhost / staging | public HTTPS production URLs |
| Webhook URL in PA | tunnel or staging | stable public HTTPS listener (webhooks-impl) |
Update .env (and hosting secrets). Redeploy. Confirm a production token still
passes utils (Step 1).
Step 4 — Reachable on the public internet (human)
Anything Xsolla must call, and any page the player returns to, has to be on the public internet over HTTPS. Localhost and ephemeral tunnels are not a go-live setup.
- If the user hosts the storefront, deploy it. A shop hosted on Xsolla's side does not need its own storefront deploy.
- If a backend grants the purchase, register a stable public HTTPS webhook URL
in Publisher Account (
webhooks-impl). - Return URLs are public HTTPS. For a user-hosted storefront, CORS and
CLIENT_ORIGINmatch the live domain.
Step 5 — Live testing (human only — tell the developer)
The agent cannot run real payments. Live flows need real payment accounts and real cards/wallets. The developer must test themselves after deploy.
Card (required)
Same payment UI the shop already uses, but with a real card. Prefer the lowest-priced catalog SKU.
Pass when:
- Payment reaches success in the shop UI
A transaction appears under Finance in PA:
https://publisher.xsolla.com/{XSOLLA_MERCHANT_ID}/finance- The buyer receives the good via the shop’s fulfillment path (
webhooks-impl— grant wired to the developer’s inventory)
Wallets / APMs (minimum)
Also complete (or attempt) live:
- PayPal
- Google Pay
- Apple Pay
(domain / merchant setup for wallets may already be done in sandbox —
Headless Checkout keeps it in that skill's google-pay / apple-pay
references; Pay Station shows the methods on its hosted page.)
Broader method coverage (recommended)
Open the other method types the shop offers (redirect, QR, mobile) in the live
UI even if every payment is not finished — sandbox cannot exercise most of
them. For Headless Checkout, the list is in that skill's
references/payment-methods.md.
Failed payment (required)
Start a method that leaves the page (e.g. PayPal), then cancel on the provider side. The shop should land on a failed / canceled terminal status (not success, not hung “processing”).
Agent boundaries
| Agent can | Agent cannot |
| Flip env/flags, remove sandbox from token paths, keep a toggle | Sign the licensing agreement or tax forms |
Call utils and interpret 00020004 | Charge real cards or finish wallet sheets |
| Hand the developer the PA links + checklist above | Claim “production verified” without their sign-off |
Done when the developer confirms: production token works, live card (min amount) paid, Finance shows the tx, goods granted, PayPal/Google Pay/Apple Pay exercised, and a canceled PayPal (or similar) shows failed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

