Zynk
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Teleport - Pay-In Accounts
  • Transformer - Cross Border Transfer
    • Overview
    • Customers & Identity
      • Entities/Customers
      • About KYC/KYB
      • RFI Scenarios for Customers
      • Identity Rejection Reasons
    • Accounts & Wallets
      • External Accounts(To be deprecated soon)
      • Fetch Requirements for External Accounts V2
      • External Accounts V2
      • Funding Accounts
      • About Plaid Integration
    • Transfers
      • Counterparty Risk details
      • Addition transfer requirements
      • Transfer in Action
      • Limits and Minimums
      • Fee details
    • Miscellaneous
      • Bank Codes
      • Supported chains and currencies
      • Partner payments signature generation
      • Reserves requirements
      • Partner Payments
      • Status updates - Webhooks
  • Transporter - Automated Liquidity Manager
    • Overview
    • Visibility Protocol
    • Instant liquidity process - How it works
    • Status updates - Webhooks
  • Teleport - Pay-In Accounts
    • Overview
    • About Teleport routes
  • Warp - Pay-Outs
    • Overview
  • Continuum - Wallet Infrastructure
    • Overview
    • Authentication
    • Continuum APIs
    • Transactions on Continuum
    • Details on generating signatures
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
Getting StartedProduct GuidesAPI ReferenceFAQ'sRecipes
  1. Teleport - Pay-In Accounts

About Teleport routes

The fundamental difference between using Teleport vs Transformer is that while using Teleport, partners don't have to pre-create an execution. Partners can simply instruct users to deposit money into a funding account and the rest is handled by Zynk.
To create a Teleport route, partners can call Create Teleport API
This will enable them to link a funding account to any valid and allowed destination. This can be done individually for each entity. One entity can have multiple teleport routes also.
One funding account can only be linked to one teleport route at a time. This prevents conflicts between automated and manual transactions.
Verify both funding and external accounts exist, are active, and belong to different jurisdictions

Prerequisites and Conditions#

Your teleport route can only be created when ALL of the following conditions are met:

Funding Account Requirements#

Cannot already be linked to another teleport route (one funding account can only have one active route)
Must not have any active or pending transactions

Destination Account Requirements#

Must exist in the system
Must be a deposit, withdrawal, or deposit_and_withdrawal type account
Must be active (not deleted or disabled)

Jurisdiction Requirements#

Source and destination must be in different jurisdictions
Teleport is designed for cross-border or cross-chain transfers only
For same-jurisdiction transfers, use standard transaction APIs

Route Availability#

A transaction route must be available between your source and destination jurisdictions
The currency pair must be supported

How It Works#

Active Route
Deposit money into the funding account
Funds are automatically converted (if needed) and transferred to linked destination account
User receive the final amount minus applicable fees
Transaction history is available for review
Inactive Route
If You Disable an Active Route
New deposits will not trigger automatic transfers
Any transfers already in progress will complete successfully
Update Teleport Route endpoint updates the destination account for an existing teleport route. The funding account remains the same, but future deposits will now be transferred to the new destination. The transaction history is preserved
New deposits automatically go to the updated destination. The new destination account must meet the same requirements as when creating a route
Patners can also toggle status of teleport route using Toggle Teleport API. This enables or disables a teleport route.
Active → Inactive
New deposits will not trigger automatic transfers. Any deposits made to the funding account while inactive will be treated as regular transactions and matched with pending executions if available.
Inactive → Active
Resumes automatic transfers for new deposits
Any transfers already in progress will complete successfully even if you disable the route.

Note:#

Immediate Activation: Routes are created active by default and process deposits immediately
One Route Per Funding Account: Each funding account can only have one teleport route
Transaction History: All transfers are tracked with amounts, fees, and exchange rates
Cross-Jurisdiction Only: Source and destination must be in different jurisdictions
Route Validation: We verify a valid route exists before creating your teleport
Modified at 2025-11-14 15:12:14
Previous
Overview
Next
Overview
Built with