AI agent connect karein · TgPay Crypto API

Remote MCP servers support karne waala AI coding agent https://app.tgpaycrypto.com/mcp se connect karein. Woh API docs padh sakta hai, merchant app ki request kar sakta hai, webhooks configure kar sakta hai aur integration likhne mein madad kar sakta hai. App creation aap bot mein approve karte hain; agent ko restricted token milta hai, jise aapko manually copy nahi karna padta. Real payments lene se pehle bani hui integration review aur test karein.

Yeh URL ek MCP server hai (Model Context Protocol — kisi service ko AI agent se jodne ka standard tareeka). Ise browser mein kholein to wo apna setup khud samjha deta hai.

Connect karein

Apne tool ke hisaab se line chunein:

Remote MCP support waala agent — yeh prompt paste karein:
```
Connect the tgpay MCP server (https://app.tgpaycrypto.com/mcp) and integrate payments via the TgPay Crypto Merchant API.
```
App mein More → Merchant API → AI agent connect karein se bhi setup prompt copy kar sakte hain.
Claude Code — claude mcp add --transport http tgpay https://app.tgpaycrypto.com/mcp
claude.ai aur Claude Desktop — Claude ki setup instructions ke mutaabik URL ko custom connector ke roop mein add karein.
ChatGPT aur doosre MCP clients — account aur workspace allow karein to URL ko custom MCP server ke roop mein add karein. ChatGPT ke liye maujooda setup instructions follow karein.

Pehle testnet par banaana ho to https://testnet.tgpaycrypto.com/mcp use karein. Approval link @tgpaycrypto_testnet_bot kholta hai aur API docs mein testnet base URL hota hai.

Pehle se API token lene ki zaroorat nahi — agent apna token agle step mein khud le leta hai. Agar aapne app manually banaya hai, to sirf agent ke kaam ki permissions wala restricted token banayein aur integration mein use karein. Main token apne server par rakhein. Agent ke paas koi bhi token ho, MCP server ke through woh sirf payments receive kar sakta hai (neeche dekhein).

Apne client ki connection settings mein MCP server add karte waqt header TgPayCrypto-API-Token: <token> (ya Authorization: Bearer <token>) dein. Is tarah token dene par approval step ki zaroorat nahi hoti. Har client mein custom headers ka field nahi hota (claude.ai aur ChatGPT connectors mein nahi hai, aur server OAuth sign-in nahi deta); wahan neeche wala approval flow use karein. Agent ek tool call mein api_token argument se bhi token de sakta hai, agar uska client aisa argument bhejne de jo tool declare nahi karta.

App approve karein

Agent se payments set up karne ko kahein. Woh docs padhta hai aur approval maangta hai.
Agent aapko t.me link deta hai. Use kholein — bot dikhaata hai ki kya request kiya gaya hai — aur ✅ App banayein aur token issue karein tap karein.
Agent par waapas aayein taaki woh token le sake aur integration aage badhaaye.

App aur agent ka token tab bante hain jab aapke tap ke baad agent request ko dobara check karta hai — aam taur par kuch hi seconds mein. Request agent ke banaane ke waqt se 10 minute tak valid rehti hai: agar agent time par check nahi karta, to kuch nahi banta, chahe bot ne aapka tap confirm kar diya ho, aur agent ko dobara shuru karna padta hai. App creation ke liye eligible account chahiye; verification zaroori ho to agent ko usi check par error milta hai — verification poori karein aur agent se usi 10 minute ke andar dobara check karwaayein, ya dobara shuru karwaayein.

Request approve karke aap us app ke liye Merchant API ki terms accept karte hain jo isse banta hai — bilkul waise hi jaise Mini App mein khud app banate waqt.

Link hamesha aapke agent se aata hai, bot apne aap kabhi nahi bhejta: jab tak aap use kholte nahi, bot ko yeh pata hi nahi hota ki agent kis account ke baare mein pooch raha hai. Jab tak aap koi button nahi dabaate, link dobara kholne par wahi request dikhti hai; ✅ App banayein aur token issue karein ya ❌ Decline dabaane ke baad, ya 10 minute beetne par, link kaam karna band kar deta hai. Agar dabane se pehle hi wo kaam karna band kar de, to agent se dobara shuru karne ko kahein — jab tak aap approve nahi karte, kuch banta hi nahi.

❌ Decline dabane par bhi kuch nahi banta aur wo request wahin khatam ho jaati hai — mann badle to agent se nayi request maangni hogi.

⚠️ Sirf wahi request approve karein jo aapne khud shuru ki ho

Connection request ka matlab hai aapke account par ek app banane ki request. Ise sirf tab approve karein jab aapne abhi khud apne agent se payments set up karne ko kaha ho. Agar link kisi aur tareeke se aaye — kisi chat mein, kisi forward kiye gaye message mein, kisi anjaan insaan ke “support” se — to use decline kar dein.

MCP server ke through kisi bhi token se transfers, checks ya refunds nahi kiye ja sakte — is approval flow se mile token se bhi nahi (neeche dekhein). Jo app aapne maanga hi nahi, woh aapke account par nahi hona chahiye.

Agent kya kar sakta hai aur kya nahi

Upar diye gaye approval flow se agent ko ek restricted token milta hai:

Wo kar sakta hai — invoices banana aur delete karna, subscription plans banana aur archive karna, kisi subscriber ki subscription cancel karna, aapka balance, rates aur stats padhna, aur webhook URL aur app ka naam badalna.
Wo nahi kar sakta — transfers karna, checks issue karna ya payments refund karna. Uske token mein payouts, checks ya refunds ki permission nahi hai.

MCP server par ek aur rok hai: paise bhejne wale tools — transfer, transferBatch, createCheck aur refundInvoice — abhi band hain. Agent ko yeh tools dikhte nahi, aur call karne par request reject hoti hai, chahe uske paas full-access main token hi kyon na ho. Isliye agent ka token leak hone par bhi MCP ke through app se paise nahi bheje ja sakte. Agent jis text ko padhta hai, jaise payer ka comment, usmein chhupi harmful instruction bhi MCP ke through paise nahi bhejwa sakti.

Transfers, checks aur refunds seedhe API se ab bhi kiye ja sakte hain. Apne server ke code se /pay/api call karein aur operation ke hisaab se payouts, checks ya refunds permission wala token use karein. Payouts app se bhi kar sakte hain: More → Merchant API kholein, apna app chunein, phir Payouts kholein.

Token private rakhein: iski permissions se invoices, subscription plans, subscriptions, webhook URL aur app ka naam badle ja sakte hain. Jab bhi kisi agent ko token issue hota hai, aur jab bhi kisi app ka webhook URL badalta hai, aapko bot ka message aata hai.

Agent ke token ki permissions dekhne ya revoke karne ke liye More → Merchant API mein app dhoondhein, Access aur tokens kholein aur Restricted tokens dekhein — Revoke se token turant band ho jaata hai. App, uska balance aur payment history rahte hain. Token ki value dobara nahi dekh sakte. Expiry date waala token expire hone par bhi kaam karna band kar deta hai.

Webhook signatures ke liye aapka main token chahiye

Agent webhook URL aapke server par set kar sakta hai, lekin wahan aane waali deliveries verify nahi kar sakta: unke signatures app ke main token se bante hain, jo agent ko kabhi nahi milta. Agent se verification code likhne aur bharne ke liye TGPAY_WEBHOOK_TOKEN jaisa placeholder chhodne ko kahein.

Use bharne ke liye: More → Merchant API kholein, agent ka banaya hua app dhoondhein, Access aur tokens kholein, Token rotate karein dabayein aur jo dikhe use copy karein — wo sirf ek baar dikhta hai. Use apne server ke environment mein rakhein, agent ki config ya apni repository mein kabhi nahi. Rotation se agent ke restricted token par koi asar nahi padta, isliye integration chalta rehta hai. Rotation ko PIN ya Face ID se confirm karna hoga. Agent se bana app aise account par bhi ho sakta hai jismein PIN na ho. Lekin rotation ke liye active PIN chahiye: pehle Security mein PIN set karein aur uske active hone ka intezaar karein.

Rotate karte hi signatures naye token par switch ho jaati hain, isliye rotation live jaane se pehle karein, apni pehli asli payment ke baad nahi.

Aage kya

Developer ke taur par shuruaat — manual tareeka, aur app ban jaane ke baad use manage kaise karein.
API reference: webhooks — payload shapes, retries aur signature check.
Merchant API reference — har method, un methods ke saath jo is approval flow se mile token se call nahi kiye ja sakte.