Support

Payout timing follows the escrow program and session outcome you approve in wallet. Drivers commit estimated USDC on chain during the handshake, and reconciliation continues to tighten as charger cloud and OEM APIs connect. Near term you should treat earnings as routed through escrow rules visible at signing time rather than instantaneous automatic metering from legacy payment rails.

We design sessions around proof of presence. A driver must be at your location and scan the session QR you show from your dashboard before payment continuation. That lowers remote spoofing risk and binds intent to real-world presence alongside our oracle middleware for cloud API telemetry reconciliation.

When a driver arrives, your dashboard exposes a scoped QR for this listing. The driver scans inside M2M and the app verifies a listing match before the payment step. Place and charger identity therefore stay aligned instead of trusting GPS alone.

Charges follow the escrow and session ledger state you acknowledged when signing. As OEM and charger cloud integrations widen, reconciliation will lean on APIs for delivered energy readings and clearer settlement outcomes.

M2M uses the Solana wallet adapter ecosystem. Common desktop choices include Phantom, Solflare, and Binance Web3 Wallet. On mobile browsers we open deep links into the respective wallet apps so you can approve escrow steps with fewer manual copy paste flows.