opencashier-merchant-integration

Name: opencashier-merchant-integration
Availability: InStock
Author: ShijayHuo

Integrate external merchant systems with OpenCashier's Merchant API for order creation and notification verification.

Updated Mar 12, 2026

Search Tags:#integration #sdk #payments #webhooks #merchant #opencashier

Ready to run

npx skills add https://github.com/ShijayHuo/OpenCashier --skill opencashier-merchant-integration-shijayhuo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opencashier-merchant-integration
Source: https://github.com/ShijayHuo/OpenCashier/tree/main/skills/public/opencashier-merchant-integration
Command: npx skills add https://github.com/ShijayHuo/OpenCashier --skill opencashier-merchant-integration-shijayhuo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merchants and SaaS backends can seamlessly integrate with the OpenCashier Merchant API to create orders, redirect users to cashier URLs, verify merchant notifications, and perform order queries as a fallback.

Core Features & Use Cases

Create real OpenCashier orders from external systems and obtain a cashierUrl for user redirects.
Verify OpenCashier merchant notifications and reconcile with order data across multi-provider setups.
Optionally bootstrap provider config and support refunds for complete merchant integrations.

Quick Start

Initialize the merchant client, create an order to obtain a cashierUrl, and redirect the user to that URL.

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 Merchant API?▼

To integrate with the OpenCashier Merchant API, initialize the merchant client using your apiBaseUrl, appId, appSecret, notifyUrl, and allowedChannels, then create orders to obtain a cashierUrl for user redirects. It uses the official SDK on Node/TypeScript.

How does OpenCashier merchant notification verification work?▼

OpenCashier merchant notification verification works by using a signing and verification protocol to validate incoming webhooks at your single merchant notifyUrl endpoint. The system enforces idempotent writes to safely reconcile notification data with your order records.

Can I use OpenCashier merchant integration with a runtime other than Node or TypeScript?▼

Yes, you can use OpenCashier merchant integration with other runtimes by porting the signing and verification protocol. While the official SDK targets Node/TypeScript stacks, the protocol can be manually implemented for your specific environment.

What's the best way to handle OpenCashier order queries as a fallback?▼

The best way to handle OpenCashier order queries as a fallback is to query the order status directly through the Merchant API when notifications fail or require reconciliation. This ensures accurate order data across multi-provider setups.

Does the OpenCashier merchant integration support refunds?▼

Yes, the OpenCashier merchant integration optionally supports refunds for complete merchant flows. You can also optionally bootstrap provider config to manage complete merchant integrations across real-world transaction setups.

What configuration values are required to create an OpenCashier order?▼

Creating an OpenCashier order requires apiBaseUrl, appId, appSecret, a merchant notifyUrl, and a defined set of allowedChannels. An optional returnUrl can also be configured to manage user redirects after the cashier process completes.