Clink Payments Suite

Apply for a FULL refund of a completed order via POST /agent/cwallet/refund/apply with body {orderId}. Only on explicit Steward request in the current exchange, supplying the original order ID (must start order_). Partial refunds are NOT supported. WRITE operation requiring explicit Steward confirmation. Returns data.refundOrderId (starts rfd_) and status.

Execute a DIRECT-MODE charge via POST /agent/order/charge with body containing paymentInstrumentId, paymentMethodType, merchantId, customAmount (JSON number UNQUOTED), and paymentCurrency. Used when no merchant payment session exists. customAmount must be EXACTLY the Steward-stated amount. WRITE operation requiring DOUBLE confirmation. Response and outcome handling identical to Clink_ChargeSession.

Execute a SESSION-MODE charge via POST /agent/order/charge. Session mode is the merchant-402-recovery path: the merchant created the payment session server-side and the session DEFINES the amount — never pass, invent, or restate an amount into this request. WRITE operation requiring explicit Steward authorization. Response: data.channelPaymentResponse and data.paySuccessInfo on success. Status 1=success, 3=declined, 4=risk-blocked, 6=other failure. flag3DS=1 means 3-D Secure required.

Generate a hosted card-binding link AND list currently bound payment methods via POST /agent/cwallet/card/bindingLink (send a literal {} JSON body — empty object, not a bodiless POST). Returns data.bindingUrl (Clink-hosted secure page; send to the Steward VERBATIM; never parse, decode, store, or reuse any token embedded in the URL; treat every returned URL as single-use and re-mint rather than reuse — whether Clink rotates the URL per call is unverified) and data.paymentMethodsVoList (bound instruments — empty array means no payment method bound yet; item fields per Clink reference code, expected paymentInstrumentId, type, brand/scheme, last4, default flag — verify against the first live response before relying on them). Triple duty: (1) card binding — Steward enters card data on Clink's hosted page, card data never transits the Mind; (2) list payment methods — the response list is the only trustworthy source; (3) binding-completion poll — after sending the link, re-call every ~60 seconds (max ~10 minutes in-turn) until the new instrument appears in paymentMethodsVoList. Success ONLY when envelope code=200. Errors: HTTP 401 envelope code 401 'Timestamp parameter is missing' (regenerate X-Timestamp, retry once — pre-execution rejection), HTTP 401 envelope code 401 'invalid.customer.api.key' (the customer_api_key sent is wrong or missing — re-read this Mind's TENET 'clink' entry and retry once; if it persists, the entry needs re-provisioning via the step 4 setup/recovery ceremony — never ask for the key in chat outside that ceremony, never echo it, never store it in LTM), CUSTOMER_VERIFY_FAILED (email/key mismatch — security block, NO retry).

Poll refund progress via GET /agent/cwallet/refund/{refundOrderId}. Returns data.status with lifecycle: pending_review, refunding, then terminal success, failed, or review_rejected. Report status verbatim; never report refunded before terminal success; on review_rejected, report it and do NOT auto-reapply.