Wallet Connection
FM Kinetic Wallet attaches to the wallets FlowMoney and Privy already manage. It creates no accounts, no wallets, and holds no credentials of its own.
Live Connection Status
Privy App ID
cmsv7ent000030cl4em40om0c
JWKS verification endpoint
Reachable · 2 key(s)
Privy app secret
Configured
Privy wallet API
Authorized
What We Need From FlowMoney
FlowMoney API base URL
The HTTPS endpoint of your existing FlowMoney application, used for account and wallet reads.
Server-side secret · FLOWMONEY_API_BASE_URL
FlowMoney integration key
A dedicated server-to-server key issued by FlowMoney for FM Kinetic Wallet, scoped to wallet read and authorize operations only.
Server-side secret · FLOWMONEY_INTEGRATION_KEY
Privy App ID
Identifies your existing Privy application so FM Kinetic Wallet attaches to customer wallets instead of creating new ones.
Configured · cmsv7ent000030cl4em40om0c
Privy App Secret
Used only by the server to read wallet metadata and prepare authorizations. It never reaches the browser.
Server-side secret · PRIVY_SECRET
FlowMoney authentication handoff
Customers stay signed in through FlowMoney’s existing Privy login. This app verifies their access token against your JWKS endpoint; the remaining piece is the redirect that delivers the token here.
JWKS · https://auth.privy.io/api/v1/apps/cmsv7ent000030cl4em40om0c/jwks.json
Allowed origin
The published FM Kinetic Wallet address, registered with FlowMoney so only this app can call the integration.
Server-side setting · configured with FlowMoney
How It Will Connect
Server-to-server read
The app reads accounts, wallets, and balances from your existing FlowMoney API using its own credentials. No customer key ever leaves the wallet.
Authorize in your wallet
Sends and shifts are confirmed inside the customer-controlled wallet through FlowMoney’s existing Privy authorization.
Nothing simulated
If the connection is not live, the dashboard shows an empty state instead of an estimate. Values only appear when they are read from the network.
Security Model
- Customer private keys stay inside the customer-controlled Privy wallet. FM Kinetic Wallet never receives, stores, or displays them.
- Every send, shift, or transfer requires explicit customer authorization in Privy before it can be broadcast.
- Balances, addresses, and history are read live from your FlowMoney and Privy infrastructure. Nothing is simulated or estimated.
- Existing addresses are never deleted or abandoned, so assets stay reachable after any address change.
- Credentials are held server-side only; no key is ever bundled into the browser.
Credentials are registered with FlowMoney and held outside this application. Once they are in place, the dashboard, Send, Receive, My Addresses, and Kinetic Shift switch from pending to live with no further rebuild.