BEMXC Automated Webhooks & Non-Custodial Execution Disclaimer

Legal architecture

BEMXC is an analytical software provider. BEMXC publishes a verification protocol, a read-only settlement ledger, and a Terminal client. BEMXC is not a broker. BEMXC is not a dealing desk. BEMXC is not a liquidity provider. BEMXC is not a fund manager, PAMM operator, or commodity trading advisor. BEMXC is not a financial advisor and does not provide personalized investment advice.

Nothing on bemxc.com, in the Terminal, in 1v1 desk chats, or in group rooms is a solicitation to buy or sell any FX pair, CFD, or other instrument. A hashed signal is a structured observation in a skill ledger. It is not a recommendation sized to your circumstances. If you require advice, retain a licensed adviser in your jurisdiction. BEMXC is not that adviser.

Non-custodial webhook execution

Automated execution on BEMXC is optional. When enabled, it is a webhook you own. The Terminal can emit a signed protocol payload after you choose to follow a call. That payload is delivered to an endpoint you register: a self-hosted worker or a broker-supported trading interface. From there, user-side API keys — keys that never leave your device keychain or your worker — authenticate to your FX broker and submit orders into that broker’s order book and liquidity stack.

BEMXC does not take custody of funds at any hop. There is no BEMXC wallet, no BEMXC margin pool, and no BEMXC omnibus account. User-side keys communicate with the broker. The broker’s book decides accept, reject, partial, or fill. BEMXC sees, at most, an acknowledgement you optionally echo back for your own audit trail. That echo does not rewrite the hashed signal and does not make BEMXC the executing principal.

Data plane versus money plane

• Data plane (BEMXC): pair, side, entry, TP, SL, digest, UTC, provider Trust Score at publish.
• Money plane (you + broker): balances, margin, lot size, fills, commissions, swaps, liquidations.

The two planes meet only if you configure them to meet. A VIP signal can settle as a win on the ledger while your webhook is down and your account did nothing. Conversely, your broker can fill you at a worse price than the hashed entry because the book moved. Neither event is a protocol defect. Verification and execution are decoupled by design. Full lifecycle context is in What is BEMXC.

Credentials, if any, are stored in the OS keychain, a hardware secret store, or your worker — not on BEMXC servers as withdrawal-capable keys. BEMXC will not request, store, or transmit credentials that allow withdrawal, transfer, or beneficiary changes. Investor or read-only passwords are the maximum the architecture is designed to tolerate, and even those remain yours.

Execution risks

A verified signal is a settled historical object plus an open object with frozen levels. It is not a promised fill. The following risks are material and expected.

Network latency

Time elapses between ledger commit, your worker’s receipt, TLS handshake to the broker, and the broker’s acknowledgement. In fast FX, tens of milliseconds move pip value. A hashed entry of 1.0872 can be stale at the book by the time the order arrives. Latency is not refunded by the protocol. Faster networks reduce variance; they do not eliminate it.

Market slippage

Slippage is the difference between requested price and fill price. News spikes, thin liquidity at session rolls, and wide spreads on crosses routinely gap through advertised stops. Leveraged FX and FX CFDs can lose more than the posted SL if the market gaps over a weekend or a data release. The hashed SL is a protocol level for scoring the provider. It is not a guaranteed stop in your account.

Broker and matching-engine downtime

Brokers halt, throttle, or disconnect. Matching engines reject during maintenance windows. Your webhook can 5xx. If the path is down, the signal still settles on the BEMXC ledger. Your account may not be in the market, or may be stuck in a position you intended to close. That gap is yours. BEMXC is not a standby executing broker.

Execution variance

Partial fills, requotes, last-look liquidity, different contract specifications, and symbol mapping (EURUSD vs EUR/USD vs a broker-suffixed symbol) produce fills that will not match the ledger tick-for-tick. Variance also includes human delay if you confirm orders manually. Ranking the provider uses the hashed object. Ranking your P&L uses your fills. Do not conflate them.

• Latency between print and broker ACK.
• Slippage and gapping through SL/TP.
• Broker, API, DNS, or worker downtime.
• Partial fills, requotes, symbol mismatch.
• A verified provider entering drawdown the moment you subscribe.

User responsibility clause

By enabling a BEMXC webhook, configuring broker API keys, or sizing an order in response to a BEMXC signal, you agree that financial risk and lot sizing reside 100% with you. You are the sole authorizing party for every order. Enabling automation is an explicit instruction from you to your broker, not from BEMXC to your broker.

You — not BEMXC — are responsible for:

1. Know-your-customer and account status at your FX broker.
2. Lot sizing, leverage, margin headroom, and liquidation risk.
3. Kill switches, maximum daily loss, and hours of operation.
4. Slippage, partial fills, requotes, swaps, and weekend gaps.
5. Tax reporting on realized and unrealized results.
6. Disabling automation when you are not monitoring the account.
7. Confirming that following a BUY or SELL is lawful where you live and permitted by your broker agreement.

Desk chats and group rooms may discuss a call. Discussion is not an order. Only your webhook configuration and your broker can create an order. BEMXC does not size that order.

BEMXC provides zero profit guarantees. Automated routing of a verified signal can still lose the full risk amount, plus fees and slippage. Anyone stating that BEMXC “prints money,” “cannot lose,” or will trade your account on your behalf is contradicting this page.

If a third party tells you that BEMXC will hold your margin or lock in a monthly return, that third party is not describing BEMXC. Do not wire funds to accounts claiming to be BEMXC custody. BEMXC has no client trading accounts. Scoring rules that people confuse with “guaranteed edge” are specified in the Credibility Scoring article; they measure the provider’s ledger, not your equity curve.

FAQ