Import External Wallet
Bind an existing non-custodial wallet to a customer
Enable non-custodial flows by binding an external wallet address to a specific customer. This allows the customer to receive funds directly to their personal wallet on supported networks like Ethereum, Polygon, and Optimism.
For complete API specification including request/response schemas and interactive examples, see the API Reference.
Import Wallet Endpoint
This endpoint links a public blockchain address to a customerId, allowing the system to recognize it as a valid destination for that user.
Endpoint: POST /v1/customers/{customerId}/wallets/import
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
customerId | string | Yes | The unique identifier of the customer you are binding the wallet to |
Body Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | The external public wallet address to import (e.g., 0x742...) |
chain | string | Yes | The blockchain network of the address. See Supported Rails for all networks |
Error Codes
| Status Code | Description |
|---|---|
400 | Bad Request - Invalid network specified or the wallet address has already been imported for this network |
401 | Unauthorized - Invalid or missing API key |
404 | Not Found - Customer ID does not exist |
Key Integration Notes
Non-Custodial Nature: Unlike the create-wallet flow, wallets imported via this endpoint do not generate private keys within Swipelux. You are only binding the public address for tracking and receiving purposes.
Network Validation: Ensure the address format matches the requirements of the selected chain. For example, EVM chains (Ethereum, Polygon, Base, etc.) require 0x-prefixed hexadecimal strings.