Skip to main content
Flex Onboarding uses invite flows — from Backoffice or API — to send merchants to a hosted onboarding form, optionally pre-filled with data your platform already has. This approach gives your operations team more control over the onboarding process while Jupico still hosts the form, validation, and compliance logic. It is the middle ground between a plain hosted link and fully API-driven onboarding.

​
Two invite methods

Jupico provides two ways to send onboarding invites to merchants.

​
Backoffice Invites

Use the Jupico Backoffice to send trackable invite links. You can send invites individually to merchants or generate unique links to share via your own communication tools. Invites sent through the Backoffice Invites page are tracked — you can follow each merchant’s progress from Sent through to Approved. Links generated outside this flow are not tracked in Backoffice.

​
Onboarding Invites API

Use the Onboarding Invites API (POST /v1/onboarding/invites) for automated or embedded invite workflows. The API lets you send onboarding links programmatically and pre-fill the application with existing merchant data, reducing the information merchants need to enter themselves.

​
How it works

1

Select your configuration

Choose the product (service provider context), fee template, and onboarding template for this invite.
2

Choose the invite type

Select one of two invite types:
  • New Applicant — creates a new applicant and submerchant.
  • Existing Applicant — adds a new submerchant for an applicant already in Jupico.
3

Pre-fill merchant data (optional)

Populate any known fields before sending. The merchant only needs to fill in what you have not already provided.
4

Send the invite

Dispatch the invite via Backoffice (tracked) or the Invites API (automated). The merchant receives a link to the hosted onboarding form.
5

Merchant completes onboarding

The merchant opens the link, reviews pre-filled data, completes any remaining fields, and submits the application. Jupico underwriting then reviews the submission.

​
Invite types

​
What can be pre-filled

All standard onboarding fields support pre-fill. Use the following reference when building your pre-fill payload.
Pre-filling reduces friction for the merchant and lowers the chance of data-entry errors. Fill in everything you already know about the merchant before sending the invite.

​
Operational notes

  • UI/UX is shared — you control data and invite initiation; Jupico controls the onboarding form experience.
  • Fee configuration is optional — the invite defaults to the product fee template if no fees are specified.
  • Invites can be created via Backoffice (manual, ops-assisted workflows) or the Invites API (automated, embedded workflows).
  • Backoffice invites are trackable; links generated outside Backoffice are not.

​
Tradeoffs

Pros

  • Pre-filling reduces merchant friction and data-entry errors.
  • Supports ops-assisted onboarding workflows.
  • More control over initiation and data than plain hosted onboarding.
  • Trackable invite status in Backoffice.
  • Embeddable via the Invites API for automated workflows.

Cons

  • Still uses Jupico-hosted onboarding UI — you cannot fully customize the form.
  • More setup required than Rapid or plain Flex hosted onboarding.
  • Shared communication model requires clear ownership documentation for support.
To automate invite creation and pre-fill at scale, use the Invites API Reference.
Last modified on July 15, 2026