onchain-pay-open-api

Signs and sends Binance Onchain-Pay Open API requests with RSA SHA-256.

168|13|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/npc-live/clawfirm --skill onchain-pay-open-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onchain-pay-open-api
Source: https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api
Command: npx skills add https://github.com/npc-live/clawfirm --skill onchain-pay-open-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openssl, curl, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables developers to securely invoke Binance Onchain-Pay Open API endpoints by automatically signing requests with RSA SHA-256, reducing the risk of tampered payloads and credential exposure.

Core Features & Use Cases

  • Signing and calling payment APIs (payment-method-list, trading-pairs, estimated-quote, pre-order, order, crypto-network, p2p/trading-pairs)
  • End-to-end workflow support for fiat-to-crypto purchases, transfers, cross-chain bridging, and merchant integrations
  • Detailed authentication and timestamp handling, with a ready-to-run script for deterministic calls to the external service.

Quick Start

Run the sign_and_call.sh script with your base URL, API path, credentials, PEM key, and a compact JSON payload to execute a signed request.

Frequently Asked Questions about onchain-pay-open-api

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

FAQPage Schema
How do I sign Binance Onchain-Pay API requests with RSA SHA-256?

You sign Binance Onchain-Pay API requests by applying RSA SHA-256 to your payload and timestamp using a PEM private key, preventing tampered payloads and credential exposure during endpoint calls.

What endpoints are available for fiat-to-crypto purchases using the Binance Onchain-Pay API?

Available Binance Onchain-Pay API endpoints include payment-method-list, trading-pairs, estimated-quote, pre-order, order, crypto-network, and p2p/trading-pairs for end-to-end buy and transfer workflows.

Do I need openssl and python3 to call Binance Onchain-Pay API endpoints?

Yes, you need openssl, curl, and python3 installed in your environment to run the signing scripts and execute deterministic calls to the external Binance Onchain-Pay service.

What credentials are required to execute a signed Binance Onchain-Pay API call?

Executing a signed Binance Onchain-Pay API call requires a base URL, client ID, API key, a PEM private key, and a properly structured JSON payload containing the required parameters for authentication.

How does timestamp signing work for Binance Onchain-Pay pre-orders and quotes?

Timestamp signing for Binance Onchain-Pay pre-orders and quotes works by incorporating the current timestamp into the RSA SHA-256 signature process, ensuring request validity and preventing replay attacks.

Can I use curl to test Binance Onchain-Pay API signing scripts locally?

Yes, you can use curl alongside the sign_and_call.sh script to locally test signed Binance Onchain-Pay API requests by passing your base URL, API path, credentials, and compact JSON payload.