opencashier-merchant-integration

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.

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.

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.

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.

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.

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.