click-integration SKILL.md skillA

click-integration from ubranch/uzbekistan-payment-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add ubranch/uzbekistan-payment-skills/click-integration@git:20261004.f1f3b97

Pins git:20261004.f1f3b97 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
ubranch/uzbekistan-payment-skills
Path
skills/click-integration/SKILL.md
Versions recorded
2
Latest version
git:20261004.f1f3b97, committed Oct 4, 2026
First version recorded
Oct 4, 2026
Size
13,094 bytes
Repository stars
13
License
MIT

Expert-level Click payment integration skill for Uzbekistan's Click SuperApp. Use whenever user mentions Click, click.uz, SHOP API, Merchant API, Click to'lov, Click integratsiya, Click callback, prepare/complete, click_trans_id, merchant_trans_id, Click fiscalization, Click button, Click invoice, card token, Click Pass, checkout.js, createPaymentRequest, Click Telegram, mobile SDK, merchant.click.uz, my.click.uz, api.click.uz, or Click error codes (-1 to -9). Covers standard SHOP…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Click Payment Integration — Expert Guide

Use this guide to select and implement Click payment integrations in Uzbekistan. The references are practical, selective guides to official documentation, not a complete verbatim mirror. Source routes and protocol findings were last verified on 2026-10-05; unresolved upstream ambiguities are called out explicitly.

## Quick Reference

| Item | Value |
|------|-------|
| Payment page URL | `https://my.click.uz/services/pay/` |
| Merchant API endpoint | `https://api.click.uz/v2/merchant/` |
| Merchant cabinet | `https://merchant.click.uz` |
| Documentation | `https://docs.click.uz` |
| Standard SHOP API Protocol | HTTP/HTTPS POST, `application/x-www-form-urlencoded` |
| Advanced / Split Shop Protocol | Separate JSON callbacks, `application/json; charset=utf-8` |
| Merchant API Protocol | HTTPS, `application/json` (also supports `application/xml`) |
| Currency | UZS: SHOP/Merchant/checkout amounts in **so'm**; fiscalization and Telegram use **tiyin** |
| Amount format | float with 2 decimal places (e.g., `1000.00`) |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add ubranch/uzbekistan-payment-skills/click-integration@sha256:0347697aa0ee81a9

The line at the top of this page pins the label git:20261004.f1f3b97, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_h557jb4cfa6clp3p.svg)](https://markdownregistry.com/a/art_h557jb4cfa6clp3p)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, all committed on Oct 4, 2026.

versioncommittedcommitsizeaudit
git:20261004.f1f3b97 latest2026-10-04 f1f3b97 13,094 BA view · diff
git:20261004.0ff6de72026-10-04 0ff6de7 9,568 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (13094 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

ubranch/uzbekistan-payment-skills · 13 stars · license MIT · pushed 2026-10-04 · branch unknown

API

GET https://markdownregistry.com/api/v1/artifacts/art_h557jb4cfa6clp3p
GET https://markdownregistry.com/api/v1/resolve?ref=ubranch/uzbekistan-payment-skills/click-integration
GET https://markdownregistry.com/api/v1/blob/0347697aa0ee81a99245e26115caabeb61aa63854684fd6e26a7a600ab7b9899

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from ubranch/uzbekistan-payment-skills

payme-integration SKILL.md skill
ubranch/uzbekistan-payment-skills · skills/payme-integration/SKILL.md · Expert-level Payme payment system integration skill for Uzbekistan's Payme Business platform. Use this skill whenever…
git:20261004.f1f3b97 · audit A · 13 stars

Every file in ubranch/uzbekistan-payment-skills

Browse by kind, by grade A, or by owner.