Joining and Funding a Syndicate

Only use a Syndicate link supplied by an issuer or DeFlow. In the current private-beta environment, an on-screen raise is not an offer to invest.

Review before requesting

1. Confirm the page is the expected DeFlow host and shows the intended Syndicate ID.
2. Review the asset, currency, soft cap, hard cap, minimum ticket, deadline and status.
3. Confirm the status is Published or Funding.
4. Check the readiness indicator. Complete any required identity, AML or wallet-screening step before continuing.
5. Confirm your wallet is connected to Sepolia.

Request an allocation

1. Enter an amount at or above the minimum ticket and no greater than the displayed hard cap.
2. Select Request Allocation once.
3. Wait for the submitted or pending confirmation.
4. The issuer reviews the request and may approve a lower amount. Do not fund the originally requested amount unless it matches the approved allocation.

Deploy and fund

1. Wait until the allocation status is Approved and the protected deployment action is available.
2. Review any second-factor request and confirm you are still using Sepolia.
3. Deploy the allocation escrow. Record its address and deployment transaction hash.
4. Verify that the escrow address matches the allocation before funding.
5. Fund only with the current deployment's allowlisted TestUSDC and confirm the amount matches the approved allocation.
6. Record the funding transaction hash and wait for the allocation status to update.

Each approved investor receives a separate Escrow contract. Never send assets to another investor's escrow or to an address copied from another transaction.

Closing outcome

• If funded allocations reach the soft cap, the issuer can close the raise and settlement processing begins.
• If the soft cap is not met, closing initiates refund handling.
• Batch processing can produce individual failures. Confirm your own allocation and transaction evidence rather than relying only on the overall raise status.

If the flow differs

The allocation lifecycle has unit coverage, while the browser journey currently relies on mocked network fixtures and complete environment validation is pending. Stop after the first unexpected state, preserve the Syndicate ID, allocation ID, escrow address, transaction hash and screenshot, then use Troubleshooting.