Transfer Flows

Swype models all fund movement as a transfer between an app account and a connected stablecoin app.

Both directions (deposit and withdrawal) use the same primitives:

• A Swype user

• A connected stablecoin app

• A per-app allowance

• A Swype-hosted browser flow

• Webhook events for lifecycle updates

1. First Transfer (Deposit or Withdrawal)

This flow applies when the user has no existing allowance for the platform.

1. Platform backend creates a transfer session with destination constraints

2. Platform opens the Swype-hosted browser flow for the user

3. User authenticates to Swype (if not already authenticated)

4. Swype deep-links into the stablecoin app to create an allowance

5. User approves the allowance via native confirmation (e.g. biometrics)

6. Swype coordinates execution of the transfer

7. Swype emits a transfer.completed (or transfer.failed) webhook

The platform updates user state based on the final webhook event.

2. Repeat Transfer

This flow applies when a valid allowance already exists for the platform.

1. Platform backend creates a transfer session

2. Platform opens the Swype-hosted browser flow

3. No stablecoin app deep link is required

4. Swype coordinates execution of the transfer

5. Swype emits a transfer.completed (or transfer.failed) webhook

From the user’s perspective, this is a fast, low-friction flow.

Notes

• Stablecoin app confirmation is only required when creating or changing an allowance

• Transfer sessions are short-lived and single-use

• Platforms should treat webhook events as the source of truth for transfer state