Cross-Chain Swap and Bridge

Let your users swap tokens within a chain and bridge assets across chains, aggregated across major liquidity venues, inside a wallet experience that handles wallet-connect, routing, and settlement.

Who this is for

Persona	Typical inbound
Wallet partner	”We need to embed swap inside our wallet — what do you offer?”
Trading interface	”Our users need cross-chain bridge as a workflow step in our app.”
Consumer fintech adding crypto	”Our users hold one stablecoin and want to move into another chain or token.”

Not a fit if you need a self-hosted swap engine with no KryptoGO-operated routing layer, central-exchange-style limit orders against an order book (this is on-chain DEX aggregation), or routing logic outside the supported aggregators today.

What you can ship today

Cross-chain swap and bridge is currently deployed inside our consumer wallet and the deployed swap application that partners can embed or link to. Capabilities include:

Capability	What it does
Multi-aggregator routing	Aggregates Jupiter for Solana, OKX for cross-EVM coverage, Uniswap for single-EVM swaps, and Tron-specific bridges, picking the route that fits the requested pair.
Multi-chain wallet connect	EVM, Solana, and Tron wallet-connect flows in a single application surface, so a user with a single wallet can swap or bridge regardless of source chain.
In-wallet swap inside the Mobile Wallet SDK	Consumer wallets built on the White-Label Crypto Wallet embed swap as a first-class action; users do not leave your branded wallet to swap.
Embeddable swap surface	Partners who do not ship the Mobile Wallet SDK can embed or link to the deployed swap application as a step inside their own flow.

Integration as a partner SDK is on the roadmap. Contact us if a published swap SDK is critical to your scenario — we will scope the productisation work alongside the partnership.

How it works


1. User picks a "from" token / chain and a "to" token / chain inside the wallet
   or embedded swap surface.
              │
              ▼
2. The router queries the aggregators that cover the requested pair:
   - Solana → Jupiter
   - Single-EVM or cross-EVM → OKX or Uniswap
   - Tron → dedicated Tron bridge adapter
              │
              ▼
3. The user sees the best route, expected output, and fees, and signs the
   transaction with the wallet they connected (EVM, Solana, or Tron).
              │
              ▼
4. The transaction is submitted on-chain through the chosen aggregator. For
   cross-chain routes, the bridge step settles on the destination chain.
              │
              ▼
5. Final balances refresh inside the wallet view. For wallets built on the
   Mobile Wallet SDK, the post-swap balance updates with no extra integration.

For a worked walkthrough that includes swap inside a consumer-fintech wallet, see Solutions: Consumer Fintech Bolt-On.

Custody model

Swap and bridge are wallet-side actions — the user’s own wallet signs and pays. The model depends on which custody track the wallet sits on:

End-user wallets built on the Mobile Wallet SDK use embedded self-custody (Shamir’s-Secret-Sharing shares split across the user’s device, your cloud, and KryptoGO’s cloud). The user signs the swap themselves.
External wallets (a user’s MetaMask, Phantom, or TronLink) sign through their wallet’s standard prompt; KryptoGO does not touch their key.

See Custody Options for the full catalogue.

Compliance posture

Swap and bridge inherit our regulated posture: Taiwan VASP registration, ISO 27001 and ISO 27701 certifications, SOC 2 Type II examined controls, Cure53 audit. Routing and settlement happen on-chain through the aggregator the user picked; we do not move user funds. See Compliance and Certifications for the full posture.

Chains and venues supported today

Chain family	Aggregators / venues
Solana	Jupiter
EVM (single-chain swap)	Uniswap
EVM (cross-chain swap)	OKX
Tron	Dedicated Tron adapter

Cross-chain routes (for example Solana to an EVM chain) settle through the bridge each aggregator supports for the requested pair. Confirm the specific pair coverage with us during scoping if the route is unusual.

Typical integration timeline

Path	Bucket
Use swap inside a wallet built on the Mobile Wallet SDK	Included with the SDK integration timeline
Link out to or embed the deployed swap surface from your app	Under one month
Partner-specific routing or fee policy	Scoped per partnership

Current scope

Aggregation across Jupiter, OKX, Uniswap, and a Tron-specific path is in production today.
EVM, Solana, and Tron wallet-connect flows are supported in a single surface.
Limit orders and dollar-cost-averaging execution are not part of this product today; analytics for these patterns are surfaced inside our trading-data product.
Currently deployed inside our consumer wallet; integration as a partner SDK is on the roadmap. Contact us if this is critical to your scenario.
Per-partner fee or revenue-share arrangements are scoped per partnership.

Talk to us

The fastest way to scope a swap or bridge integration is a 45-minute discovery call. Reach our partnerships team via the address on www.kryptogo.tw .

Where to go next

White-Label Crypto Wallet — for the wallet that embeds swap as a first-class action.
Custody Options — to see how user wallets sign swaps.
Architecture Overview — to see how swap and bridge fit into the wider platform.