DEPRECATED legacy alias — a2a-pay support has been merged into `okx-agent-payments-protocol` (see `references/a2a_charge.md`). This stub exists only so that legacy invocations referencing the old name resolve to a meaningful redirect. If you land here, immediately load `okx-agent-payments-protocol` via the Skill tool and follow it instead. Do NOT execute any payment logic from this stub. All paymentId / a2a_... / payment-link / payment-status triggers now route directly to `okx-agent-payments-pr
The okx-a2a-payment skill is a deprecated compatibility stub that exists solely to redirect legacy references to the current payment workflow implementation. It addresses the problem of older transcripts, scripts, integrations, or documentation that still reference the historical skill name. Instead of providing payment functionality itself, the skill ensures that users and systems are guided to the correct successor skill, preventing confusion and maintaining continuity as the payment architecture evolves.
Its primary capability is acting as a redirect layer to the successor skill, okx-agent-payments-protocol. The stub contains guidance for locating the consolidated payment flow documentation, including the paymentId-based workflow and the associated create, pay, and status procedures. It explicitly does not perform payment processing, execute payment logic, define payment triggers, or introduce any standalone functionality. References involving payment identifiers, a2a-related payment flows, payment links, or payment status checks are intended to be handled by the successor skill.
Typical use cases include maintaining backward compatibility for existing automation, documentation, and integrations that still reference the old skill name. The target users are developers, AI agents, workflow maintainers, and technical teams working with legacy references. When encountering this skill, users should immediately transition to the unified payment protocol skill and follow its documentation instead of attempting to execute any payment-related operations through this deprecated entry point.
You should immediately load and follow the successor skill, okx-agent-payments-protocol, as this skill only serves as a redirect.
No. This skill does not execute payment logic and should not be used for payment processing.
According to the documentation, the functionality remains unchanged; only the entry point has changed.
These requests are routed to okx-agent-payments-protocol and are not handled directly by this deprecated skill.
It exists to provide a meaningful redirect for legacy references in older transcripts, scripts, integrations, and documentation.
Quick Setup:
.claude/skills/Repository
okx/onchainos-skills