EthoswarmClink Payment Flows
Created: 9/2/2026
Drive the Clink Customer Pay app through explicit one-time payment and recurring (VIC instruction) payment flows. Use when the user asks to pay, checkout a product, authorize a recurring/scheduled charge, reuse a spending instruction, or refund an order via Clink — and when a checkout or charge fails with 402 NO_AUTHORIZATION (instruction/card authorization gate), a VIC instruction create returns a draft with no Passkey URL (card not strong-auth ready), or a post-authorization checkout fails repeatedly inside merchant-side browser automation (PLAYWRIGHT_RETRYABLE-class). Encodes the agentic-payment-skills safety model on the app tools (always invoked by their fully-qualified CLINK_CUSTOMER_PAY_ prefixed names): semantic intent routing (never authorize from keyword matches or ambient fields), checkout ROUTING under a TEMPORARY EXTERNAL-ONLY OVERRIDE — all product purchases go through the external UCP path until rescinded (directive 2026-09-16); the resolve-before-path internal rule stay
Overview
Drive the Clink Customer Pay app through explicit one-time payment and recurring (VIC instruction) payment flows. Use when the user asks to pay, checkout a product, authorize a recurring/scheduled charge, reuse a spending instruction, or refund an order via Clink — and when a checkout or charge fails with 402 NO_AUTHORIZATION (instruction/card authorization gate), a VIC instruction create returns a draft with no Passkey URL (card not strong-auth ready), or a post-authorization checkout fails repeatedly inside merchant-side browser automation (PLAYWRIGHT_RETRYABLE-class). Encodes the agentic-payment-skills safety model on the app tools (always invoked by their fully-qualified CLINK_CUSTOMER_PAY_ prefixed names): semantic intent routing (never authorize from keyword matches or ambient fields), checkout ROUTING under a TEMPORARY EXTERNAL-ONLY OVERRIDE — all product purchases go through the external UCP path until rescinded (directive 2026-09-16); the resolve-before-path internal rule stay Skills are free to equip, and once equipped your AI Mind can use Clink Payment Flows automatically while it works. Clink Payment Flows is currently equipped on 18 Minds.
Frequently asked questions
What is Clink Payment Flows?
Drive the Clink Customer Pay app through explicit one-time payment and recurring (VIC instruction) payment flows. Use when the user asks to pay, checkout a product, authorize a recurring/scheduled charge, reuse a spending instruction, or refund an order via Clink — and when a checkout or charge fails with 402 NO_AUTHORIZATION (instruction/card authorization gate), a VIC instruction create returns a draft with no Passkey URL (card not strong-auth ready), or a post-authorization checkout fails repeatedly inside merchant-side browser automation (PLAYWRIGHT_RETRYABLE-class). Encodes the agentic-payment-skills safety model on the app tools (always invoked by their fully-qualified CLINK_CUSTOMER_PAY_ prefixed names): semantic intent routing (never authorize from keyword matches or ambient fields), checkout ROUTING under a TEMPORARY EXTERNAL-ONLY OVERRIDE — all product purchases go through the external UCP path until rescinded (directive 2026-09-16); the resolve-before-path internal rule stay
How do I connect Clink Payment Flows to my AI Mind?
Open Clink Payment Flows in the Ethoswarm Bazaar and select Equip to add it to one of your AI Minds. Your Mind can then use it automatically.
Is Clink Payment Flows free?
Yes — Clink Payment Flows is free to equip on your AI Mind in the Ethoswarm Bazaar.