If you want Api integration contact here https://signal.me/#eu/dZPptaJLdinecAyuMpa-l1-HMmbgXimaRJPgyVFEMv8Qs-7GFylEZq_Oqu19mIkZ
👍8🔥5🥰5❤4

Channel
@Btcpaymentonline
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,678subscribers
+2,091 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003741129047 |
|---|---|
| Type | Channel |
| Username | @Btcpaymentonline |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/Btcpaymentonline |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 30 September 2026 and assigned it the closest of 31 fixed categories, at 49% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:09 | 2,678 | -1,009 |
| 12 Nov 2026, 10:21 | 3,687 | -676 |
| 8 Nov 2026, 07:06 | 4,363 | -97 |
| 4 Nov 2026, 17:14 | 4,460 | -23 |
| 1 Nov 2026, 18:31 | 4,483 | -226 |
| 29 Oct 2026, 21:56 | 4,709 | -22 |
| 26 Oct 2026, 22:54 | 4,731 | -23 |
| 23 Oct 2026, 12:18 | 4,754 | -35 |
| 20 Oct 2026, 15:46 | 4,789 | -26 |
| 17 Oct 2026, 20:27 | 4,815 | -478 |
| 14 Oct 2026, 13:51 | 5,293 | +4,407 |
| 7 Oct 2026, 10:18 | 886 | -128 |
| 30 Sept 2026, 06:02 | 1,014 | +426 |
| 12 Sept 2026, 20:58 | 588 | +1 |
| 11 Sept 2026, 04:22 | 587 | no change |
| 11 Sept 2026, 03:47 | 587 | first reading |
20 posts held, back to 21 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 September 2026. An engagement rate over an empty window would be a number about nothing.
786 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 25.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 199 | 25.3% | |
| 🥰 | 199 | 25.3% | |
| ❤ | 191 | 24.3% | |
| 👍 | 180 | 22.9% | |
| 🤝 | 13 | 1.65% | |
| 🤪 | 4 | 0.509% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 786 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 August 2026 to 10 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
If you want Api integration contact here https://signal.me/#eu/dZPptaJLdinecAyuMpa-l1-HMmbgXimaRJPgyVFEMv8Qs-7GFylEZq_Oqu19mIkZ
👍8🔥5🥰5❤4
Cash app Chime pinned «If you’re currently using XXPayUS, message us for the new API integration. We’ve updated several features, including automatic payment collection through a single permanent payment link, so there’s no need to generate a new payment link for every transaction.…»
If you’re currently using XXPayUS, message us for the new API integration. We’ve updated several features, including automatic payment collection through a single permanent payment link, so there’s no need to generate a new payment link for every transaction. Pay-In: 12% | Pay-Out: 5%. Our fees may be slightly higher than some alternatives, but our focus is on fund security, reliable service, and fast payment process…
👍11❤10🥰10🔥7
Signed 比特币 付款 ㅤ
Again we sold our product sucessfully. If you want to build platform like this you can contact our business manager. @Firekirinxyz8580
👍13🥰13🔥10❤9
Signed 比特币 付款 ㅤ
Players interface: https://fluxpay.45.63.23.31.nip.io/pay/damamondamove25-8b45 Easy gateway for agents. Signup now : https://fluxpay.45.63.23.31.nip.io/dashboard
🔥13❤10👍7🥰5🤝1
Signed 比特币 付款 ㅤ
The owner provides a 12% pay-in and a 5% payout to facilitate a secure transaction. It is recommended to prioritize the security of funds over the specified percentage rates. A discussion regarding a percentage discount will be scheduled after one month by checking your cash flow at first start at 12 in / 5 out https://signal.me/#eu/dZPptaJLdinecAyuMpa-l1-HMmbgXimaRJPgyVFEMv8Qs-7GFylEZq_Oqu19mIkZ
🥰12❤8👍8🔥8🤪4
Signed 比特币 付款 ㅤ
Guys this the correct time to show humanity let's go 🇳🇵🇨🇳🤝🤝🫰
❤24🥰18🔥15👍12
Signed -
Cash app Chime pinned Deleted message
We accept US wire transfers and offer services for handling various types of funds using physical cards. We specialize in providing payment and settlement services for CashApp and Chime, focusing on e-commerce, online games, card games, and online slots. We can also integrate with online API systems.
🔥13❤12👍11🥰4
Signed 比特币 付款 ㅤ
Bind your Gmail & Google authenticator as soon as possible if you're using xxpayus. That's for your fund security.
🥰23🔥20👍19❤16🤝1
Signed 比特币 付款 ㅤ
Photo, posted without a caption
🔥23❤21🥰19👍18
Signed 比特币 付款 ㅤ
Photo, posted without a caption
🥰23🔥13❤10👍9🤝4
Signed 比特币 付款 ㅤ
Showing the 12 most recent of 20 posts we hold for @Btcpaymentonline. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 17 November 2026 — this entry's latest reading, not the date you are reading this.
“Cash app Chime” (@Btcpaymentonline), 2,678 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/Btcpaymentonline.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.