Skip to main content
This is an independent documentation project for @mono.co/connect.js. It is not Mono’s official documentation.

​
Verification record

The guide was checked against the public Connect.js implementation, its README, and Mono’s official API documentation.

​
Precedence

Use this order when sources disagree:
  1. Mono’s current official documentation for production behavior and API policy.
  2. The current Connect.js source for SDK signatures and browser behavior.
  3. This guide for explanation and implementation examples.
Payment capabilities, required customer fields, and API behavior can change independently of the JavaScript package. Verify production payment and financial-data integrations in Mono’s official documentation.

​
Documentation conventions

  • PUBLIC_KEY means a Mono public key that may be used in browser code.
  • MONO_SECRET_KEY means a secret that must remain on your backend.
  • code means the short-lived value returned to onSuccess after account linking.
  • accountId means the Mono account identifier returned after the backend exchanges that code.
  • Examples use scope: "auth" explicitly for account linking.
  • Reauthorization examples pass an accountId to reauthorise(). They do not pass a reauth token.

​
Machine-readable access

Agents can discover the page index at /llms.txt, load the complete documentation from /llms-full.txt, and read the integration capability contract at /skill.md. Individual Mintlify pages are also available as Markdown by adding .md to the page URL.