tgpay cryptoAPI
crypto-paymcpaiagent

AI agent connect karein

5 minute readUpdated 9 Oct 2026

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. Manually diye gaye token ki permissions tay karti hain ki agent kya kar sakta hai.

App approve karein

  1. Agent se payments set up karne ko kahein. Woh docs padhta hai aur approval maangta hai.
  2. 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.
  3. Agent par waapas aayein taaki woh token le sake aur integration aage badhaaye. App creation ke liye eligible account chahiye; maanga jaaye to verification poori karein.

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. Har link sirf ek baar chalta 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.

Is approval flow se mila token transfers nahi kar sakta, checks nahi bana sakta aur payments refund nahi kar sakta (neeche dekhein). Manually diye gaye token ki permissions alag ho sakti hain. Jo app aapne maanga hi nahi, uska aapke account par hona hi galat hai.

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 aur subscription plans banana, aapka balance, rates aur stats padhna, aur webhook URL set karna.
  • Wo nahi kar sakta — transfers karna, checks issue karna ya payments refund karna. In operations ke liye payouts, checks ya refunds ki corresponding permission, ya full-access main token chahiye. Is flow se mile token mein inmein se koi permission nahi hoti.

Token private rakhein: iski permissions se invoices, subscription plans aur webhook URL 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.

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