Telegram RegisterThe public register of Telegram
Telegram profile photo for LWD PAY通知

Channel

LWD PAY通知

@lwdpay

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

16subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001178219619
TypeChannel
Username@lwdpay
DescriptionTG上最靠谱的第五方支付,Mocca Network旗下官方项目,适合发卡等使用,不接黄赌毒机场等违规,采用易支付系统,whmcs zfaka 等系统轻松对接 ***本站已稳定运行2年***
CreatedBetween 1 March 2018 and 9 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live24 August 2026
Measurements held2
On Telegramt.me/lwdpay

Growth

169 August 2026 — 16 subscribers11 August 2026 — 16 subscribers9 August 202611 August 2026
2 measurements spanning 2 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 15–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 22:3016no change
9 Aug 2026, 23:1516first reading

Engagement

20 posts held, back to 9 June 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 9 September 2022. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Links
3

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

9 Sept 2022, 01:26 UTC99 viewsread 11 August 2026

lwdpay.com 域名将在数日后到期,不再归我们管理和拥有,请各位小心防止诈骗

9 Sept 2022, 01:26 UTC99 viewsread 11 August 2026

历时2年,本站已经永久停止运营,感谢各位的关注。 全部提现已经完成,如有更多疑问可以与我们联系。

10 Feb 2022, 15:52 UTCviews —

LWD PAY通知 pinned «系统更换,已对接用户请私聊 @LWD2020 重新登记商户»

10 Feb 2022, 15:51 UTC214 viewsread 11 August 2026

系统更换,已对接用户请私聊 @LWD2020 重新登记商户

10 Feb 2022, 15:13 UTC217 viewsread 11 August 2026

因为原来使用的open系统作者不再更新,为了确保安全我们正在更换系统

10 Feb 2022, 14:30 UTC216 viewsread 11 August 2026

由于数据库过大,今天将进行清理历史订单,如有需要请进行备份留存

6 Jan 2022, 09:05 UTC261 viewsread 11 August 2026

费率: 支付宝H5 QQ 3.8% |微信 5.5% 开户费38元,D1结算,支付宝H5企业稳定接口,结算费率1%(1元起),满20自动结算 开户私聊 @moccaconnect 支付正常运行中

27 Dec 2021, 16:25 UTC258 viewsread 11 August 2026

服务器生产力环境升级中 可能造成短期服务中断 预计 1小时后恢复

11 Nov 2021, 03:11 UTC277 viewsread 11 August 2026

测试结束 ,目前接口正常使用,单笔限额120,单商户日限额500 双11商户活动: 支付接口提现手续费限免,(原1%,1起)现在提现0费用,仅需支付接口费用,活动有效期即日起至11月20日

7 Nov 2021, 14:03 UTC268 viewsread 11 August 2026

新接口测试中,禁止大额订单,流水控制在100内,2天后解除限额正常运营 费率: 支付宝 QQ 3.8% |微信 5.5%

28 Oct 2021, 02:53 UTC276 viewsread 11 August 2026

很抱歉的通知 稳定了1个月后,支付再次进入暂时维护 暂时无备用接口,我们会尽快完成维护,结算正常

28 Sept 2021, 02:58 UTC302 viewsread 11 August 2026

启动备用接口 支付宝 qq 微信均已恢复 费率 支付宝 微信 5% QQ 4%

Showing the 12 most recent of 20 posts we hold for @lwdpay. 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.

Citation-graph rank

Citation-graph rank — 1,414,784 of 1,604,161entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

Cite this entry

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“LWD PAY通知” (@lwdpay), 16 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/lwdpay.

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.