okx-x402-payment

To redirect legacy payment aliases to a unified payment protocol, this Skill maps deprecated payment flow identifiers to the current 'okx-agent-payments-protocol', ensuring your legacy calls maintain payment process continuity without breaking existing integrations.

Legacy alias handling in payment processing resolves deprecated payment flow identifiers by redirecting them to a unified payment protocol. This mechanism ensures that older systems referencing deprecated aliases continue functioning seamlessly during protocol migrations.

You need to map deprecated payment flow identifiers when your system previously used the 'okx-x402-payment' alias and requires compatibility with the updated payment dispatcher. This ensures seamless transition from deprecated payment flows to the unified protocol.

Yes, the unified payment protocol supports legacy payment redirection by resolving deprecated alias references. It integrates with the updated payment dispatcher to ensure consistent service delivery when transitioning from deprecated payment flows.

To handle deprecated payment aliases without breaking existing integrations, load the 'okx-agent-payments-protocol' skill and follow its instructions. This redirects your legacy 'okx-x402-payment' alias calls to maintain payment process continuity.

Your legacy payment alias reference fails after a protocol update because deprecated identifiers require mapping to the unified payment protocol. Applying this redirect ensures compatibility with the updated payment dispatcher and restores functionality.