opencashier-merchant-integration

Integrate external merchant systems with the OpenCashier Merchant API.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/aaaaaajie/OpenCashier --skill opencashier-merchant-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencashier-merchant-integration
Source: https://github.com/aaaaaajie/OpenCashier/tree/main/skills/public/opencashier-merchant-integration
Command: npx skills add https://github.com/aaaaaajie/OpenCashier --skill opencashier-merchant-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate external merchant systems with OpenCashier to enable order creation, redirect users to cashierUrl, verify notifications, query orders as a fallback, and perform refunds across diverse stacks.

Core Features & Use Cases

  • End-to-end merchant integration: create orders, obtain cashierUrl, verify PAY_SUCCESS notifications, query orders as fallback, and process refunds.
  • SDK-first guidance: Node/TypeScript projects should prefer the official @opencashier/sdk; non-Node runtimes should port the signing and verification protocol.
  • Real-world scenario: a SaaS backend needs to interact with OpenCashier without implementing a custom cashier UI.

Quick Start

Initialize the merchant client, create an order, redirect to cashierUrl, verify notifications, and optionally query and refund as needed.

Frequently Asked Questions about opencashier-merchant-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate an external merchant system with the OpenCashier API to process payments?

To integrate an external merchant system with the OpenCashier API, you create orders, redirect users to the cashierUrl, verify notifications, and optionally query or refund using the official Node/TypeScript SDK or by porting the signing protocol.

How do I verify PAY_SUCCESS webhooks and query orders for OpenCashier transactions?

You verify PAY_SUCCESS webhooks by implementing the signing and verification protocol on your notifyUrl. As a fallback, you can query the order status directly via the OpenCashier Merchant API.

Can I use the OpenCashier Merchant API with non-Node runtimes without the official SDK?

Yes, for non-Node runtimes you must port the signing and verification protocol manually. The official @opencashier/sdk is specifically recommended for Node and TypeScript integration stacks.

What credentials and parameters are required to create an order and redirect to the OpenCashier cashierUrl?

Creating an order and redirecting to the cashierUrl requires the apiBaseUrl, appId, appSecret, your system's notifyUrl, optional returnUrl, and the required allowedChannels parameter.

What is the best way to perform refunds across diverse stacks using the OpenCashier Merchant API?

The best way to perform refunds is using the official @opencashier/sdk for Node/TypeScript, while non-Node environments must manually port the API's signing and verification protocol to execute the refund transaction.

Why do I need to specify allowedChannels when creating an order via the OpenCashier Merchant API?

Specifying allowedChannels is required when creating an order to define the specific payment methods permitted for that transaction, ensuring users only see valid channels on the cashierUrl.