Member01
Register, log in, acknowledge risk
Users can register, log in, see subscription state, and accept the current risk version. Inactive or unacknowledged users cannot create usable rules.
Docs
Docs
These docs explain how members register, activate a subscription, and use alert workflows. Online checkout availability is shown live on the purchase page; the service provides informational spot-spread alerts for users to review and act on themselves.
Market information for human review; users make their own decisions and transactions.
ArbPingDocs
01Member onboarding
02Telegram binding
03Alert rules
04Notification logs
ArbPing docs for registration, subscription activation, Telegram binding, alert rules, notification logs, and troubleshooting.
Member
Shortest path from registration to alert
Follow these steps to move from registration to an alert-ready member state. Each result remains visible in the member portal.
Telegram02
Bind and verify a target
The main flow uses a binding code or deep link to verify a private Telegram target. Unverified targets cannot receive alerts.
Rules03
Save personalized alert conditions
All supported symbols are selected by default. Members can paste bulk lists, restrict exchanges, and set minimum estimated value, cooldown, and quiet hours.
Logs04
Confirm delivery records
After delivery processing, members can inspect notification records, delivery status, and failure reasons.
Member onboarding
Members register or log in, confirm subscription state, bind a private Telegram target, and create alert rules. Alert rules affect distribution only; they do not change the central scanning strategy.
Telegram binding
Private chat targets are supported first. A target must be verified and enabled before it can receive alerts.
Alert rules
Rules can filter by estimated value, spread, symbol, buy exchange, sell exchange, cooldown, and quiet hours. Rules do not bypass global route safety state.
Notification logs
Members can inspect delivery status, attempt counts, and failure reasons in notification records. Reprocessing the same opportunity does not create a duplicate delivery.
Troubleshooting
If no alerts arrive, check subscription status, target verification, rule thresholds, symbol or exchange filters, and the delivery status shown in notification records.