P2P Market Notifier

P2P Market Notifier is a private Telegram bot for people watching USDT and EGP peer-to-peer listings on Binance and Bybit. A user configures alert conditions in the bot, and the service checks exchange listings in the background. Matching ads become Telegram messages, with delivery timing tied to the user's plan.

The problem

P2P listings change while a trader is away from the exchange screen. Repeated polling can send the same ad many times, and a bot that sends messages directly from the polling loop can fall behind during bursts. The service separates collection, matching, duplicate control, and delivery so each part can run at its own pace.

Key features

• Exchange adapters collect P2P ads from Binance and Bybit and normalize their fields.
• Alert profiles filter listings by trade side, price, available amount, merchant information, and payment method.
• Telegram menus let users create and manage their alert settings and view account details.
• Redis keys suppress repeated notifications for the same matching ad.
• BullMQ jobs deliver alerts immediately for active PRO or trial access and delay free-plan alerts.
• Telegram Stars invoices and successful-payment handlers grant a time-limited PRO subscription.
• Arabic and English message catalogs serve the bot menus and alerts.
• An administrator can inspect bot analytics and queue broadcast messages.

Technical architecture

A Node.js process polls the exchange endpoints through Axios. Platform adapters turn each response into a common ad shape. The matcher compares ads with alert profiles stored in MongoDB through Mongoose. Redis handles duplicate keys and backs the BullMQ notification queue. A separate worker sends formatted messages through Telegraf and records delivery activity. The same process exposes a health route for database, cache, and bot state.

Engineering highlights

• Queueing keeps a burst of matching ads from blocking the market polling loop.
• The matcher combines plan delay with quiet-period delay before enqueuing an alert.
• Successful-payment handling updates the user and subscription record inside a MongoDB transaction.
• A signed deployment webhook validates incoming requests before scheduling a process reload.