Docs

1. 1
   Signup: /pricing → pilih tier → login Telegram → isi tenant name + slug.
2. 2
   Bot: @BotFather → /newbot → copy token → di-paste ke /admin/tenant-bots. Lalu /setprivacy → Disable.
3. 3
   Invite bot ke grup VIP / channel lo. Bot otomatis DM lo chat ID begitu join.
4. 4
   Register channel di /admin/channels → pilih parser → enabled.
5. 5
   Test: kirim sample signal di grup. Cek /admin/signals — appear sebagai parsed + fanout fired ke subscribers.

kopitrade itu multi-tenant infrastructure-as-a-service buat sinyal trading. Lo (KOL) bawa tiga hal:

• Bot Telegram sendiri (dari BotFather)
• Channel / grup tempat lo post sinyal
• Subscriber base lo sendiri (lo collect fee, kita gak masuk)

Kita orchestrate:

• Webhook routing — message dari bot lo masuk ke pipeline kita
• Parser plugins — convert raw text → structured signal (pair, side, entry, TPs, SL)
• Fanout queue — 1 signal × N subscribers (BullMQ + Redis)
• Order placement — execute di exchange subscriber via stored credentials (AES-256-GCM at-rest)
• Tenant admin panel — channel management + signal feed + billing

5.1 · LIQUIDITY WAVES format

LIQUIDITY WAVES SETUP

#BTCUSDT  LONG x10
Entry: 67200 — 67400
TP1: 68100
TP2: 68900
TP3: 70200
SL: 66500

{
  "pair": "BTC",
  "side": "long",
  "entry": [67200, 67400],
  "tps": [68100, 68900, 70200],
  "sl": 66500,
  "leverage": 10
}
confidence: 0.95

5.2 · Cornix-style format

🟢 Long #ETHUSDT
Entry: 3850
TP: 3900, 3950, 4020
Stop: 3780
Leverage 5x

{
  "pair": "ETH",
  "side": "long",
  "entry": [3850, 3850],
  "tps": [3900, 3950, 4020],
  "sl": 3780,
  "leverage": 5
}
confidence: 0.92

5.3 · Bare regex format

#SOLUSDT LONG x5
Entry: 168 - 172
TP1: 178
TP2: 185
SL: 162

{
  "pair": "SOL",
  "side": "long",
  "entry": [168, 172],
  "tps": [178, 185],
  "sl": 162,
  "leverage": 5
}
confidence: 1.0

Subscriber daftar di kopitrade.id/login (Telegram deeplink), connect exchange mereka sendiri (Binance / Bybit / OKX / KuCoin / Bitget), lalu subscribe ke tenant lo dari /me/signals.

Setiap signal yang masuk ke channel lo dengan confidence ≥ floor:

1. 1
   Worker resolve siapa aja yang subscribe active ke tenant lo
2. 2
   Tiap subscriber → enqueue order.place job (default paperTrade=true)
3. 3
   Worker decrypt cred → call adapter → place order
4. 4
   JobAudit row written buat post-mortem visibility

Permission API-key (untuk subscriber)

• Enable: Trading + Read
• Disable: Withdraw (CRITICAL — jangan pernah enable)
• IP whitelist: kontak support buat dapet IP VPS kopitrade kalau exchange-nya support

Flow:

1. 1
   Tenant admin buka /t/<slug>/billing → pilih plan → Bayar
2. 2
   Kita create Payment row + redirect ke Pakasir hosted page
3. 3
   Subscriber scan QRIS, complete payment
4. 4
   Pakasir webhook ke kopitrade.id/api/payments/pakasir/webhook dengan x-webhook-secret header
5. 5
   Kita verify secret + amount + order_id, lalu activate subscription (extend period 1 bulan dari periodEnd existing atau dari now)
6. 6
   Tenant pending → active kalau ini bayar pertama

Refund policy: trial 14-hari = full refund kalau cancel sebelum trial end. Setelah bayar pertama, prorated refund untuk unused days.

9.1 · Telegram bot webhook

Endpoint: POST /api/tg/webhook/<secret>

Auth: URL path <secret> matches Tenant.webhookSecret AND X-Telegram-Bot-Api-Secret-Token header matches.

Handled updates:

['message', 'edited_message',
 'channel_post', 'edited_channel_post',
 'my_chat_member']

Response: always 200 OK (intentional — prevent Telegram retry storms; errors logged internally).

9.2 · Pakasir billing webhook

Endpoint: POST /api/payments/pakasir/webhook

Auth: X-Webhook-Secret header matches PAKASIR_WEBHOOK_SECRET env, ATAU source IP di PAKASIR_WEBHOOK_IPS allowlist.

Payload shape:

{
  "project": "kopitrade-indonesia",
  "order_id": "tenant-slug-plan-abc123",
  "amount": 1990000,
  "status": "completed",
  "payment_method": "qris"
}

Idempotency: by order_id — already-paid Payment returns {ok:true, idempotent:true}.

9.3 · Manual signal ingest (admin only)

Endpoint: POST /api/admin/signals/ingest

Auth: admin cookie (kopi_admin) required.

Request:

{
  "channelId": "cmpesysur0001m2f7lag7rjrr",
  "rawText": "#BTC LONG\nEntry: 67200\nTP1: 68100\nSL: 66500",
  "fakeMessageId": 12345
}

Use case: demo/testing pipeline tanpa bot live, atau replay/backfill missed signals.

Tenant

Lo, sebagai KOL. Tiap KOL = 1 tenant. Memiliki bot + channel + subscriber feed sendiri.

Subscriber

User end-customer yang follow signal lo + bayar lo. Connect exchange API key sendiri.

Channel (listener)

Telegram chat (grup / supergroup / channel) yang lo set sebagai sumber signal. Mapped 1-to-1 dengan ParserPlugin.

ParserPlugin

Code yang convert raw text → ParsedSignal. Built-in: regex.basic, cornix-format, liquidity-waves, ai.fallback.

SignalEvent

DB row per message yang lewat parser. Status: received → parsed → fanned-out (atau review / rejected).

Fanout

Proses 1 signal × N subscriber → N order.place job. Powered by BullMQ + Redis.

Webhook secret

Random 24-byte token di URL /api/tg/webhook/<secret>; harus match Tenant row + X-Telegram-Bot-Api-Secret-Token header. Defense-in-depth.

Paper-trade

Order simulasi — adapter returns synthetic paper:<ts>:<rand> id. Phase 2 default, safety net pra-live-trading.

JobAudit

DB mirror dari BullMQ jobs. Setiap job lifecycle (running → completed / failed) di-record. Buat post-mortem visibility.

RLS

Row Level Security — PostgreSQL policy yang scope DB query by session GUC. Memastikan user-A gak bisa baca / write row user-B walaupun app-layer bug.