Integration Surface

Platforms integrate Swype through a small, stable surface area consisting of:

• One backend API call

• One frontend entry point

• Webhook handling

1. Backend Integration

Create a transfer session

Platforms initiate deposits and withdrawals by creating a transfer session server-to-server.

The platform backend provides:

• Destination address (app account or stablecoin app)

• Destination chain

• Accepted assets

• Optional amount constraints

• Return URLs for client handoff

Transfer sessions are:

• Short-lived

• Single-use

• Immutable once created

Platforms should treat Swype as the source of truth and avoid maintaining parallel transfer state.

Idempotency

• Session creation requests must be idempotent

• Platforms should include a unique idempotency key per logical transfer

• Replayed requests will return the same session object

This prevents duplicate transfers during retries or network failures.

2. Frontend Integration (Mobile)

Platforms expose a single entry point on the frontend.

On user interaction:

1. The app requests a transfer session from its backend

2. The app opens the returned Swype-hosted browser flow

3. Control returns to the app via deep link on completion or cancellation

The platform does not render transfer UI, wallet selection, or approval screens.

3. Webhooks

Swype communicates transfer lifecycle updates via webhooks.

Event types

• transfer.processing

• transfer.completed

• transfer.failed

Webhooks are:

• Delivered at least once

• Signed for verification

• Replay-safe