Jupid Embed

Partner integration docs for embedding Jupid in another product.

Jupid Embed is for banks, financial institutions, fintechs, and third-party tools that want to offer Jupid inside their own product experience.

This is a partner integration surface, not a self-serve advanced-user setup. Jupid creates partner configuration, browser origin policy, staging access, production access, and commercial terms before launch.

Start by requesting partner access. Once Jupid has configured your environment, choose the web quickstart or React Native and Expo guide, build the authenticated token endpoint, and run the launch checklist.

Partners that only need Jupid's shared public articles and tools should use Business Library for partners. That surface has no named users, workspace sessions, or financial data.

What the embed does

Jupid opens a full financial workspace inside the partner product. The partner keeps the outer relationship, navigation, and authenticated entry point. Jupid handles accounts, financial data, categorization, reports, billing-aware flows, and the workspace UI inside an iframe or top-level WebView.

The primary integration has two parts:

• a host SDK for a browser iframe or React Native WebView;
• a partner-owned server endpoint that creates short-lived signed tokens for authenticated partner users.

Some integrations also use server-to-server webhooks for partner events such as account-list changes.

For programmatic account and transaction uploads, use the Jupid API with the same partner signing configuration. It can connect users and businesses before their first embedded session.

Jupid uses the token to map each partner user to a Jupid user, create a session, and render the embedded dashboard in an iframe or top-level WebView.

What partners build

The minimum authentication integration is one partner-owned server endpoint:

GET /api/jupid/embed-token

That endpoint signs a token with the shared secret provided by Jupid. The host SDK calls the endpoint while mounting Jupid. A mobile app authenticates that request with its user's partner access token. The signing secret stays on the server; the browser or mobile app receives only a short-lived JWT.

Use the same durable partner user ID for returning sessions. Partners using the API should also keep business IDs stable so uploads and embedded sessions resolve the same business. See authentication for the claims and the API guide for business provisioning.

What Jupid configures

Jupid provides:

• the partner ID;
• separate staging and production token signing secrets;
• the staging and production Jupid app URLs;
• webhook URLs and webhook secrets, when the partner integration uses server-to-server events;
• the agreed pilot usage allowance and paid-access policy;
• the allowed local, staging, and production browser origins;
• iframe ancestor policy for those origins;
• default shell mode, chat visibility, and partner branding;
• the production app URL: https://app.jupid.com.

Start with Embed quickstart for web or the React Native and Expo guide for mobile. Then review authentication, webhooks, and testing and launch.

Contact slava@jupid.com to request partner access.