Give Claude Code the EPaySe Guide in Three Steps

To give Claude Code the EPaySe guide, you copy it from the EPaySe documentation, save it as a file inside your project, and open Claude Code. The assistant then reads the file while it works and follows EPaySe's rules. The whole setup takes a few minutes and needs no special tools.
- Step 1: copy the guide from the EPaySe documentation page.
- Step 2: save it as a file in your project folder.
- Step 3: open Claude Code and ask it to add EPaySe checkout.
Step 1: Where do you get the guide?
The guide lives on the Claude Code skill page of the EPaySe documentation. The page has a copy button. The same text is also available as plain text, for scripts and automated setups, at docs.epayse.com/llms-skill.txt.
Step 2: Where do you save it?
Create a folder called epayse-integration inside .claude/skills at the top level of your project, next to files such as package.json or composer.json. Inside it, create a file named SKILL.md, paste the guide into it and save. The full path is .claude/skills/epayse-integration/SKILL.md. The documentation page shows the exact command to create the folder and file.
Use the folder with SKILL.md inside, not a single loose file. In a test with a current Claude Code version, the folder form was registered as a skill and used when we asked about EPaySe, while a loose file in .claude/skills was not registered as a skill.
Step 3: How do you use it?
Open your project in Claude Code and ask for what you need, in plain words. For example: "Add EPaySe checkout to my order page, using the sandbox." The documentation explains that Claude Code reads skills stored this way as background knowledge, so it knows EPaySe's rules without searching the web.
Other tools such as Cursor or Windsurf can use the same text through their own context-file features, because it is plain Markdown.
What does the guide cover?
- How to talk to EPaySe and prove the request comes from your shop.
- How to create a payment and send the customer to the checkout page.
- How to check the confirmation messages EPaySe sends.
- How to handle refunds and look up a payment.
- A list of common mistakes to avoid, with example code in PHP, Node.js, Python and Go.
How do you keep it up to date?
The file is static. When EPaySe updates its documentation, copy the guide again, or fetch the plain-text version, and replace your file. You can also edit your copy to add your own project notes, because it is plain Markdown.
What should you still do yourself?
The guide makes the assistant much more accurate, but it does not remove your responsibility. Review the code, keep secret keys out of the chat, and test in the sandbox. See keep your EPaySe secret key away from your AI assistant and test your EPaySe integration in the sandbox.
EPaySe is an early-stage payment gateway, still in development. Read the documentation for the latest details.
Key takeaways
- Copy the guide, save it in your project, then ask the assistant for checkout.
- The guide gives the assistant EPaySe's real rules.
- Re-copy the guide when the documentation changes.
- This is general education, not legal or financial advice.
Questions? Contact the team.
FAQ
Where do I find EPaySe's guide for Claude Code?
On the Claude Code skill page of the EPaySe documentation, which has a copy button, or as plain text at the docs address under llms-skill.txt.
Where do I save the guide file?
Save it as a file named SKILL.md inside a folder called .claude/skills/epayse-integration at the top level of your project.
Does the guide update itself?
No. It is a static file, so copy the latest version again when the documentation changes.
Can I use the guide with Cursor or Windsurf?
The text is plain Markdown, so you can use it through those tools' own context-file features.
Do I still need to review the code?
Yes. The guide helps the assistant, but you should review the code and test it in the sandbox before any real payment.
Related Articles

Go-Live Checklist for a Checkout Your AI Assistant Built
Before real customers pay, read every line, re-run every test, move the live key to your server settings and start with one small order. A short checklist for AI-built checkouts.

Mark Orders Paid Only After EPaySe Confirms
The page a customer returns to is not proof of payment. Learn how EPaySe's confirmation message works, how to check it, and why AI-written code often gets this part wrong.

What to Check in Payment Code Your AI Assistant Wrote
An AI assistant can write payment code that looks right but breaks on small details. Here are the checks that catch the most common EPaySe integration mistakes, in plain words.

Keep Your EPaySe Secret Key Away From Your AI Assistant
Your secret key proves that a request comes from your shop. Learn why it must never go into a chat, where to keep it instead, and what to do if it leaks.