When a Customer initiates a payment through a Zateway checkout:
- The Customer sends the full payment amount from their personal wallet.
- On EVM chains, the ZatewayRouter smart contract automatically splits the payment: 99% to the Merchant's wallet, 1% to the Zateway treasury.
- On Solana, the checkout page constructs an atomic multi-instruction transaction that performs the same split natively, without requiring a deployed program.
- The Zateway backend monitors the blockchain for the incoming transfer, verifies its finality, and updates the payment session status.
- Webhook notifications are dispatched to the Merchant's configured endpoint.
Important:At no point during this process do funds pass through Zateway's servers or any intermediary wallet controlled by Zateway. The Company has no ability to freeze, reverse, or withhold any merchant funds.
5.1 Confirmation Delays: Payments are not instantaneous. After a customer submits a transaction, it must be included in a block and receive a chain-specific number of subsequent block confirmations before Zateway marks the payment as confirmed. Typical times range from ~1 second (Solana) to ~2 minutes (Polygon). During periods of network congestion, these times may increase. See our
Risk Disclosure for details.
5.2 Direct Transfer Mode: In certain cases, payments may be processed via direct wallet-to-wallet transfer rather than the ZatewayRouter smart contract. Direct transfers rely on amount-matching heuristics and do not provide cryptographic session binding. This mode carries a higher risk of payment misattribution. Merchants should use the
senderAddress parameter to mitigate this risk.
5.3 Webhook Delivery: Zateway delivers payment event notifications via HTTPS webhooks on a
best-effort basis. If your endpoint is unreachable, returns a non-2xx status, or times out (10 seconds), Zateway retries up to 5 times with exponential backoff. After all retries are exhausted, the webhook enters a 1-hour cooldown period. Zateway does not guarantee delivery of every webhook. Merchants should implement server-side polling as a secondary verification mechanism.
5.4 Session Expiry:Payment sessions expire 15 minutes after creation. Payments received after expiry are matched on a best-effort basis and marked as "late_confirmed." Zateway does not guarantee matching of late payments.