Overview
How Jupid embeds inside partner products and what partners need to build.
Jupid partner integrations let another product open a full Jupid financial workspace. The primary path is iframe embedding inside the partner product. Jupid can also support redirect-based partner integrations where the partner links users into the hosted Jupid app.
Partners integrate against Jupid's hosted staging environment first. They do not need access to Jupid source code or a local Jupid app.
The iframe integration has two parts:
- a browser SDK loaded from the Jupid app URL for iframe integrations;
- a partner-owned server endpoint that creates short-lived signed tokens for authenticated partner users.
Jupid uses the token to map each partner user to a Jupid user, create a session, and render the embedded dashboard in an iframe.
Integration paths
| Path | Use when | Partner work |
|---|---|---|
| Iframe embed | Jupid should run inside the partner product workspace. | Mount the browser SDK, sign short-lived tokens, and choose optional shell/chat SDK overrides. |
| Redirect | The partner wants to link users into the hosted Jupid app instead of framing it. | Send users to the agreed Jupid or OAuth entrypoint; Jupid applies the same partner branding and shell configuration. |
Partner model
The embed is a hosted integration, not a source-code handoff. After Jupid approves a partner, Jupid creates a staging partner configuration and sends the partner the environment values needed to develop against Jupid staging.
The default pilot offer uses a Jupid-side usage-based free limit. A new user can try Jupid until the configured free usage threshold is reached, such as a number of categorized transactions or counterparties. The paywall appears after the product has shown value.
Commercial terms are agreed separately for each partner. Revenue share is one available model, and Jupid can also support other commercial structures when a pilot requires them.
What partners get
- A Jupid workspace mounted inside the partner product.
- Partner-controlled entry points and navigation.
- A lightweight SSO flow that does not expose partner secrets to the browser.
- A stable mapping between partner users and Jupid users.
- A first-run path that sends new users to account connection.
- Existing-user routing to the requested in-product path.
What partners build
Partners build one authenticated server endpoint:
GET /api/jupid/embed-tokenThat endpoint signs a token with the shared secret provided by Jupid. The browser page fetches the token, loads the SDK, and mounts Jupid into a real height container.
What Jupid configures
Jupid provides:
- the partner ID;
- separate staging and production token signing secrets;
- the staging and production Jupid app URLs;
- the Jupid-side usage-based free limit for the pilot;
- the allowed local, staging, and production origins;
- iframe ancestor policy for those origins;
- default shell mode, chat visibility, and partner branding;
- the production app URL:
https://app.jupid.com.
Contact slava@jupid.com to request partner access.