FAQ
Frequently asked questions
Everything you need to understand how StockGate works, from deposits and trading to payouts, security, and support.
These answers are written for product, operations, and compliance stakeholders who need practical implementation detail before launch.
Each response explains not only what StockGate does, but why the behavior matters for user trust and day-to-day operational reliability.
StockGate is a configurable fintech platform and can run in simulation or admin-controlled market modes depending on deployment policy. This allows teams to provide transparent trading experiences without representing external brokerage execution by default.
Deposits can flow through crypto integrations or manual review pathways. Teams choose the balance of speed and control based on risk profile, while users receive clear status communication from initiation to settlement.
Investing and savings payouts follow configured product rules, schedule checks, and idempotent settlement references. The structure is designed so users can understand each period result and support teams can trace every payout event.
Yes. Withdrawal processing supports automated and manual paths with review safeguards, fallback behavior, and explicit failure handling. This reduces payout risk while preserving a predictable user journey.
Yes. KYC enforcement can block restricted financial actions while still allowing deposits where policy permits. This model helps teams fund accounts first and unlock higher-risk actions only after verification.
Yes. Manual deposits, withdrawals, and KYC submissions include review workflows with approve/reject controls, notes, and status visibility so operational decisions remain transparent and traceable.
StockGate uses typed wallet transactions and metadata references to represent every balance-impacting action. Deterministic state changes and consistent event logging make reconciliation and support diagnostics significantly faster.
Webhook processing uses signature validation, replay-safe handling, and idempotent update rules. This protects against duplicate mutations when providers retry events or send delayed delivery attempts.
Yes. The mailing module supports templates, segmentation, campaign orchestration, open/click tracking, and unsubscribe behavior, enabling teams to run growth communication without abandoning compliance basics.
Yes. Users can manage communication preferences in settings so marketing and account updates are aligned with consent expectations and user-level communication intent.
Most teams can launch quickly using default modules and a clear production checklist. The timeline depends on brand customization, operational policy decisions, and integration readiness for funding and withdrawal flows.
Use the Contact page and include your business context, objective, and any relevant workflow details. The team responds with practical next steps for onboarding, migration, or issue resolution.