Account and Binance API safety
TradeSentrix uses a restricted automation workflow designed to reject unsafe API configurations and keep withdrawal access disabled.
Encrypted credentials
Submitted Binance API credentials are encrypted by the Laravel application before storage.
No withdrawals
Withdrawal permission must remain disabled. API validation rejects configurations that do not pass the security requirements.
IP restriction
Users are instructed to restrict the API to the approved execution environment rather than allow unrestricted access.
Safety blocks
Duplicate, existing-position, symbol, balance and exchange-validation checks can prevent trade execution.
Required Binance API configuration
- Enable only the Futures trading permission required by the platform.
- Keep withdrawal permission disabled at all times.
- Apply the approved IP restriction.
- Use Binance One-Way position mode where required by the current execution system.
- Start with a small balance and conservative risk settings.
Automation risk
Exchange outages, network delay, slippage, price gaps, insufficient margin, precision restrictions and third-party service failures can affect execution. Security controls reduce risk but cannot eliminate trading or technology risk.