Merchant API ki fees aur limits
Invoices par ek platform fee lagti hai jo aapko milne wale amount mein se jaati hai; transfers aur checks amount limits se bandhe hote hain. Neeche ke figures maujooda settings hain, contract terms nahi — agar yeh app mein dikhne wale figures se alag hon, to app hi sahi hai, aur sabse bharosemand source hamesha aapke apne paid invoices hain.
Invoice ki fee
Payer hamesha invoice ka face amount hi pay karta hai. Fee merchant ki taraf se jaati hai: aapka app balance utni amount se credit hota hai jo fee kaat kar bachta hai.
Fee invoice amount ka 3% hai, aur aapke pichhle 30 din ke payment volume ke saath yeh apne aap kam hoti jaati hai:
| 30-din ka volume | Fee |
|---|---|
| $10,000 se kam | 3% |
| $10,000 se | 2.9% |
| $25,000 se | 2.8% |
| $50,000 se | 2.7% |
| $75,000 se | 2.6% |
| $100,000 se | 2.5% |
Number se zyada do rules maayne rakhte hain:
- Fee payment ke waqt tay hoti hai aur wahin lock ho jaati hai. Rate mein baad mein hone wala koi badlaav us invoice ko kabhi nahi chhoota jo pehle hi pay ho chuka hai.
- Aapka rate aapke volume ke saath badal sakta hai. Pichhle 30 din ki window mein zyada payment volume aapko apne aap kisi neeche wale tier par le ja sakta hai. Iske liye na apply karna hota hai, na kuch configure karna hota hai.
Theek-theek kitna charge hua yeh dekhne ke liye paid invoice se fee_asset aur
fee_amount padhein — invoice_paid webhook payload se ya getInvoices se.
Aapki books ke liye wahi authoritative figure hai.
Refunds fee wapas nahi karte: refundInvoice payer ko jo bhejta hai wo aapke
balance se jaata hai, aur fee refund nahi hoti — partial refund par bhi nahi.
Subscription charges par bhi merchant-side fee lagti hai; har charge apna figure
subscription_charged webhook ke charge.fee field mein batata hai.
Transfer limits
transfer par ek per transfer minimum aur maximum lagta hai, jo per-asset
figure ke bajaay maujooda rates par US-dollar-equivalent estimate ki tarah
lagaya jaata hai. Is range se bahar ka amount saaf error ke saath reject ho
jaata hai, isliye apne integration mein amount_too_small aur amount_too_big
handle karein.
Transfer in cases mein bhi fail hota hai:
- us asset mein aapka app balance kam pad jaaye,
- recipient app ka user na ho — kisi anjaan ya galat type kiye gaye Telegram ID par payout aise wallet ko credit karne ke bajaay error deta hai jise koi kabhi kholega hi nahi,
- recipient ka account blocked ho.
Rate limits
Paisa move karne wale methods par per app rate limit hai (uske sabhi tokens mein
shared): createInvoice aur createCheck 60 per minute, refundInvoice aur
transfer 30, transferBatch 10. Read methods unlimited hain. Theek se likha integration is limit tak kabhi pahunchta hi nahi; retry loop zaroor pahunchega — isliye rate_limited milne par hammer karne ke bajaay back off karein.
Idempotency
transfer ke liye aapka banaya hua spend_id zaroori hai; createCheck
aur refundInvoice ise accept karte hain. Wahi value dobara use karne par funds
doosri baar move hone ke bajaay purana result replay ho jaata hai — isliye
timeout wali request ko usi spend_id ke saath dobara bhejna safe hai, aur
naya sirf sach mein naye payout ke liye banta hai.
Kya free hai
Merchant API mein kahin bhi network fee nahi hai — invoices, transfers aur checks sab app ke andar, off-chain settle hote hain. Sirf invoices par lagne wali platform fee hi ek charge hai.
⚠️ Fee khud kabhi calculate na karein
Koi percentage hardcode na karein, aur na hi face amount se net nikaalne ki koshish karein. Tiers aur rates badalte hain, aur purana pada constant chupchaap aapki accounting kharab kar deta hai. Har baar invoice par record ki gayi fee hi padhein.
Kya yeh article helpful tha?
Feedback ke liye shukriya.