Connection checks

What evidence shows that native order protection was accepted?

Separate documented capability, requested protection and the account's actual native state. Keep missing or ambiguous evidence visibly unconfirmed.

TradeTwin · Product educationPublished October 5, 2026

THE SHORT ANSWER

Separate documented capability, requested protection and the account's actual native state. Keep missing or ambiguous evidence visibly unconfirmed.

A request containing Stop Loss and Take Profit fields states what software asked for. It does not prove the venue accepted those values, filled the intended amount or retained protection on the resulting position. A protection record should connect the exact account and operation to an authoritative native observation.

Check capability before interpreting a result

cTrader's new-order documentation distinguishes absolute and relative protection fields; absolute Stop Loss and Take Profit are unsupported for market orders in that message contract. Its position model exposes current protection, and reconciliation can return protection orders. MetaQuotes exposes allowed symbol order types, stop distance and freeze distance. These are interface capabilities whose actual account and instrument values must be verified.

Create a protection evidence worksheet

Identify the owner-approved plan version, exact broker or exchange account, environment, instrument and requested operation. Keep its original identifier together with the request hash.
Record which protection mode the exact adapter supports and the authoritative source for the instrument's units and constraints. Do not translate a price distance from another symbol by its display name.
Separate requested values from the venue's acknowledgment and from the later native order or position readback. Link authoritative IDs; a generic HTTP success is not a fill or protection receipt.
Record the actual filled amount and current native protection state with observation time. Keep partial fills, missing fields, netting changes or competing observations unconfirmed until the approved reconciliation resolves them.
Record what remains dependent on the client machine or provider. Never label a future follow-up patch as proof that an entry was protected when it was accepted.

Know where protection runs

MetaTrader's help describes ordinary Stop Loss and Take Profit as stored and executed on the broker server, while trailing stops run in the terminal. This distinction matters when a machine is offline. It is not a guarantee of execution price or every broker's order lifecycle. Current account rules, execution policy and an accepted native result still need separate verification.

When the evidence is incomplete

Use a precise state such as protection unconfirmed, naming the missing observation and its time. Keep new-entry authorization blocked under the approved policy while authorized inspection and protective management remain separate. A confident AI explanation, a saved plan or a live price cannot fill an evidence gap. Do not submit a test order from this checklist; any acceptance test needs a separately authorized environment and exact procedure.

Source check · 5 October 2026

cTrader: https://help.ctrader.com/open-api/messages/ and https://help.ctrader.com/open-api/model-messages/ . Symbol constraints: https://www.mql5.com/en/docs/constants/environment_state/marketinfoconstants . Protection location: https://www.metatrader5.com/en/terminal/help/trading/performing_deals . The worksheet is TradeTwin's evidence standard; documentation alone is not account acceptance.

Questions worth asking

Is an accepted request proof that the position is fully protected?

No. Keep acknowledgment, fill and native protection evidence distinct. Confirm the resulting amount and protection through the approved exact-account readback.

Can AI choose missing protection settings during recovery?

No. The accepted plan, saved risk and supported native contract remain authoritative. Missing evidence requires inspection and review, not invented values or broader permissions.

Primary documentation for further reading

API documentation describes the provider's interface. It does not certify your account or TradeTwin connector as ready to trade.

Check capability before interpreting a result

Create a protection evidence worksheet

Identify the owner-approved plan version, exact broker or exchange account, environment, instrument and requested operation. Keep its original identifier together with the request hash.

Record which protection mode the exact adapter supports and the authoritative source for the instrument's units and constraints. Do not translate a price distance from another symbol by its display name.

Separate requested values from the venue's acknowledgment and from the later native order or position readback. Link authoritative IDs; a generic HTTP success is not a fill or protection receipt.

Record the actual filled amount and current native protection state with observation time. Keep partial fills, missing fields, netting changes or competing observations unconfirmed until the approved reconciliation resolves them.

Record what remains dependent on the client machine or provider. Never label a future follow-up patch as proof that an entry was protected when it was accepted.