Register customer wallet
Registers a crypto wallet for a customer that belongs to the caller’s organization or a
direct child organization. Mirrors POST /ramp/wallet but scoped
to a specific customer within the caller’s org hierarchy.
If the wallet was previously soft-deleted, it is restored. Optionally claims ownership of the wallet on behalf of the customer’s organization.
Idempotent — registering an already-active wallet returns the existing record.
Authorizations
API key sent in the Authorization header.
Path Parameters
The customer (child org) ID. Must belong to the caller's organization or a direct child.
Body
Documented request body for registering a wallet — the bring-your-own
(external) shape that is generally available today. Managed-wallet
provisioning ({ "signer": … }) is not yet generally available and is intentionally
omitted from the published schema. This type describes the wire shape for the
docs; the handler deserializes the full [RegisterWalletPayload] enum.
Response
The registered wallet
Blockchain the wallet is on.
stellar, solana, base, polygon, monad Timestamp when the wallet was created.
ID of the customer who owns this wallet.
Public key / address of the wallet.
Timestamp when the wallet was last updated.
Unique identifier for the wallet.
Whether the wallet has active claimed ownership by the organization. When true
and the organization is approved, the wallet is treated as compliant without
requiring individual KYC. Only present when claimed ownership has been set.
Timestamp when the wallet was deleted (if applicable).
Display name for the wallet.
Whether KYC is marked on-chain for the wallet. Only present for Solana wallets; for other blockchains this field is omitted as on-chain KYC marking does not apply.
Current KYC verification status for the wallet. Only present for individual wallet
calls. The approved_chain_deploying status indicates the user is approved but
waiting for on-chain marking (Solana only).