Deferred Flow Guide

The deferred flow lets you create wallet metadata at sign-up and activate the account (sponsor + trustlines) later, when the app decides (e.g. after KYC or first purchase).

Sequence

1. User signs in (Google, GitHub, Email OTP, Freighter, Albedo).
2. App calls the SDK to create the wallet with fundingMode: 'deferred'.
3. Pollar API persists the wallet with pending_activation status and returns wallet_id, public address and state.
4. App continues with KYC or other internal logic.
5. When the app decides to activate, it calls activateWallet(wallet_id) (SDK or API).
6. API validates policy and state; the Relay prepares and submits the transaction (create account, sponsor reserves, set trustline).
7. Wallet becomes active and is ready for payments and invocations.

Why use it

• You control cost: you do not activate every account on sign-up.
• Fits KYC-gated or funnel-gated flows.
• The user does not need to understand reserves or trustlines.

Reference

• Funding Modes — description of immediate, deferred and manual.
• Architecture — wallet lifecycle.