Channel
@paymentsecuritynews
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
156subscribers
+6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001102063553 |
|---|---|
| Type | Channel |
| Username | @paymentsecuritynews |
| Created | Between 1 February 2017 and 28 February 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/paymentsecuritynews |
Technology — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 11:22 | 156 | +1 |
| 25 Sept 2026, 12:59 | 155 | +1 |
| 7 Sept 2026, 06:00 | 154 | +1 |
| 23 Aug 2026, 14:59 | 153 | +2 |
| 15 Aug 2026, 16:24 | 151 | +1 |
| 8 Aug 2026, 20:00 | 150 | no change |
| 7 Aug 2026, 22:55 | 150 | first reading |
8 posts held, back to 5 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 8 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
53 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 56.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 30 | 56.6% | |
| 🔥 | 21 | 39.6% | |
| 👍 | 2 | 3.77% |
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 8 of the 8 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 53 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 5 August 2026 to 6 August 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.
#PAYMENTSECURITY 2026 завершилась❗️ За эти два дня: ⏺Эксперты поделились своим опытом в вопросах информационной безопасности в контексте динамично развивающихся технологий. ⏺Оживлённые дискуссии позволили взглянуть по-новому на проблемы, с которыми приходится сталкиваться на практике. ⏺На Practical Security Village участники проверили себя в деле на практике - флаги найдены, устройства на мастер-классе по пайке собр…
❤10🔥4
На PCI DSS Training Сергей Шустиков рассказал про создание и развитие карточных платёжных систем, а также про предпосылки, которые привели к необходимости обеспечения безопасности карточных данных. В России оператором национальной платёжной системы МИР выступает НСПК. Она же выступает и регулятором в части соблюдения правил и требований платёжной системы. В 2026 году НСПК обновила Программу безопасности платёжной с…
❤3🔥1
Друзья, на PSV флаги подняты! Начинаем охоту 🚩
🔥7
Сергей Шустиков на сцене! Обсуждаем индустрию платёжных карт 💳
❤5👍2
Доброе утро, друзья! В ресторане Monet вас уже ждёт горячий утренний кофе! ☕️ В 11:00 в концертном зале Premio начнётся PCI DSS Training, который проведёт Сергей Шустиков, QSA-аудитор, генеральный директор Deiteriy. ⭐️ Также в 11:00 продолжаем паять, ломать и охотиться за флагами на практическом воркшопе Practical Security Village. 😵💫
❤4
День завершён, но с названием группы не поспоришь - «Ещё не вечер»! Завершаем нашу программу ярким after-party в их компании 🔥
🔥5
Завершил докладную часть Иван Алексейчук из VirtualFort. Иван рассказал про сложности, с которыми могут столкнуться ИТ и ИБ специалисты, размещая инфраструктуру у крупных облачных провайдеров. Иван подсветил, что современные облака стали сложными системами со множеством сервисов. В этой парадигме с трудом можно найти специалиста, который бы хорошо разбирался во всех сервисах облачного провайдера. В связи со сложнос…
❤3🔥2
Александр Мизерин из Yandex Cloud и Василий Пургин из Affirmative Systems рассказали, как поселить финтех в облаке, какие есть связанные с этим нюансы и как обеспечивается безопасность облачной инфраструктуры. Кроме того, докладчики рассмотрели вопрос: зачем финансовым организациям облако и какие выгоды получает организация, информационная инфраструктура которой там располагается. Например, облако может закрыть част…
❤5🔥2
Showing the 8 most recent of 8 posts we hold for @paymentsecuritynews. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“#paymentsecurity news” (@paymentsecuritynews), 156 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/paymentsecuritynews.
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.