# PropShield Webhook Firewall — User Guide

**Mergify Digital · Price: $19.99/month or $99/year (via Whop)**

## What it is

PropShield is a guard layer that sits between TradingView alerts and a broker-routing destination. You send your TradingView alerts to PropShield first. Before anything is forwarded, PropShield checks the alert against the guards you have configured. Alerts that pass are forwarded as broker-style JSON to your sealed (locked-in) destination. Alerts that fail a guard are blocked instead of forwarded.

Guards and protections documented in the software include:

- A re-check that your Whop membership/license is still valid
- Risk and session policy, including New York session restrictions that are aware of daylight-saving time
- An economic-news blackout guard. This guard is designed to fail closed — if fresh news data cannot be confirmed, alerts are held rather than let through
- Destination protection: only allowlisted hosts, a sealed destination URL, and optional enforcement that webhooks only come from TradingView source addresses
- Duplicate / replay protection, so the same alert is not forwarded twice
- Delivery formatting for broker-routing destinations, with an optional Discord notice

PropShield also includes an activation website with an interactive TradingView JSON builder (to help you format the alert message TradingView sends) and a free Pine Script companion that visualizes sessions on a TradingView chart.

To be clear about what it is not: PropShield is a filtering and routing utility in front of an execution service. It is not a broker, it does not hold funds, it does not create trading strategies, and it does not guarantee that any trade will be taken, filled, or profitable.

## Who it's for

- Traders who automate TradingView strategies and route alerts to a broker-routing service
- Prop-firm challenge and funded-account traders who need to avoid trading through major news releases or outside allowed sessions — the situations that commonly breach firm rules

## Requirements

- A Whop purchase/license for PropShield
- A TradingView account that can send webhook alerts
- A broker-routing destination that accepts JSON webhooks (for example, a TradersPost- or CrossTrade-style endpoint) — PropShield forwards to a destination; it does not replace one
- An internet connection and a modern web browser for activation and configuration
- The PropShield starter-kit ZIP delivered after purchase

## Getting started

1. **Check out on Whop.** Purchase PropShield Webhook Firewall from Mergify Digital on Whop ($19.99/month or $99/year). Keep your Whop account details and license information — activation checks your license against Whop.
2. **Download the starter kit.** After purchase, download the PropShield starter-kit ZIP delivered through Whop and unzip it. Read the included starting/read-me material before changing any routing settings.
3. **Activate with your license.** Open the PropShield activation page/service from the starter kit and activate using your Whop license key. PropShield re-checks membership as part of its normal operation, so the license needs to stay active for routing to work.
4. **Set your destination.** Enter and seal your broker-routing destination URL. Sealing locks that destination in, so alerts cannot quietly be redirected somewhere else. Only allowlisted hosts are accepted.
5. **Build your TradingView alert message.** Use the interactive TradingView JSON builder included with PropShield to format the message your TradingView alert will send, and copy that format into your TradingView alert's message field. Point the TradingView alert webhook URL at the tokenized PropShield route provided during activation.
6. **Configure your guards before enabling routing.** Set your session policy and news-blackout preferences first (see below).
7. **Test with routing still off, then enable it deliberately.** Trade routing is **OFF by default**. That is intentional. Send test alerts, confirm they are received, checked, and logged as you expect, and only then deliberately enable/configure routing in the settings. Do not skip the test step, and start with paper/small-size routing through your destination service until you have seen several alerts behave correctly end to end.

## Step-by-step: main features

### 1. Configure the news-blackout guard

1. Open your PropShield configuration.
2. Set the news-blackout window you want around major economic releases.
3. Leave the fail-closed behavior on. If fresh news information cannot be confirmed, PropShield is designed to hold alerts rather than pass them — that conservative behavior is the point of the guard.
4. Remember that the guard is only as good as the release information available to it. Check your settings before known high-impact days (for example, major US employment or inflation releases and central-bank decisions) rather than assuming any calendar is perfect.

### 2. Configure session / risk policy

1. Set the trading sessions (New York time, daylight-saving aware) in which alerts may be forwarded.
2. Set any risk-policy limits offered in your configuration.
3. Alerts arriving outside your allowed sessions, or breaching your policy, are blocked instead of forwarded.

### 3. Set up a TradingView alert

1. In TradingView, create or open the alert on your chart/strategy.
2. Enable the webhook option for the alert and paste the tokenized PropShield route URL provided at activation.
3. Paste the message format produced by the included JSON builder into the alert message field.
4. Save the alert, then trigger a test alert and confirm in PropShield that it was received and how each guard treated it (passed or blocked, and why, where that information is shown).

### 4. Use the Pine companion (optional)

1. Open the Pine companion script file included with PropShield in TradingView's Pine Editor.
2. Add it to your chart. It is a session-visualization aid to help you see the sessions your policy uses — it does not place or filter trades by itself.

### 5. Review blocks and deliveries

1. After any blocked alert, review which guard stopped it before changing settings — most blocks are the session or news guard doing the job you configured.
2. If you enabled the optional Discord notice, use it as an alert that something was delivered or blocked, not as proof of a broker fill. Confirm fills in your broker/routing service, not in PropShield.

## Tips

- Test the full chain — TradingView alert → PropShield guard checks → routing destination → broker — with paper trading or your smallest size before relying on it.
- Re-check your guard settings after any TradingView strategy change. A new alert with an old or wrong message format may not route the way you expect.
- Keep the tokenized route URL private. Anyone with that URL may be able to send alerts to your route.
- If you trade a prop-firm account, read your firm's current rules yourself. Configure PropShield to match them; do not assume the defaults match any particular firm.

## Troubleshooting

- **Alerts are not arriving at PropShield.** Check that the TradingView alert is active, the webhook option is on, and the webhook URL is exactly the tokenized PropShield route from activation. Re-trigger a test alert.
- **Alerts arrive but nothing is forwarded.** Routing is off by default — check whether you have deliberately enabled it. Also check whether a guard blocked the alert (outside session, news blackout, or duplicate/replay protection).
- **Everything is being blocked around news.** That is the fail-closed design when fresh news data cannot be confirmed, or your blackout window is wide. Review the window you set, and check again once release information is current.
- **Destination was rejected.** PropShield only forwards to allowlisted hosts with a sealed destination. Re-check the destination URL you entered and re-seal it if you changed routing services.
- **Activation or routing says your license is invalid.** Confirm your Whop subscription is active and that you entered the license key exactly as delivered. If the problem continues, contact support (below) with your Whop receipt information — never send your full payment-card details.

## Support

Email: **support@mergifystudios.com** (placeholder — mailbox existence unconfirmed; use the support contact shown on the Mergify Digital Whop page if this address does not respond).

Website: https://mergifydigital.mergifystudios.com

Please include: your Whop product name, the date of purchase, a short description of the problem, and any error message shown. Do not send passwords, full payment-card numbers, or broker account credentials.

## Disclaimer

PropShield Webhook Firewall is a software utility for filtering and routing webhook alerts. It is not financial, investment, or trading advice, and it is not a broker or execution service. Trading — including futures, stocks, options, and crypto — involves substantial risk of loss, and past performance does not guarantee future results. No result is guaranteed: guards can be misconfigured, data can be delayed or unavailable, and alerts can be blocked or forwarded in ways you did not intend, so test before relying on it and monitor your own accounts. You are solely responsible for your trading decisions, your configuration, and compliance with any prop-firm or broker rules that apply to you.