Onboarding Overview

Jupico provides three primary approaches to onboard merchants, each designed for different levels of control, flexibility, and speed.

This guide helps you choose the right approach based on your use case, implementation effort, and ownership of the onboarding experience.

At a Glance

Hosted Onboarding (Rapid / Flex)

What it is

A fully hosted onboarding experience managed by Jupico. You share a URL with your merchants to complete onboarding.

Variants

• Rapid → Jupico-branded onboarding experience
• Flex → Hosted onboarding with your logo and brand styling

Best-fit use cases

• Fastest possible go-live
• No engineering resources for onboarding UI
• Standardized onboarding experience is acceptable

How it works

1. Jupico hosts the onboarding flow
2. You share a link with merchants
3. Merchants complete onboarding in the hosted UI

Operational notes

• Jupico owns onboarding UX and validation
• Flex supports branding (not full UX customization)
• Minimal ongoing maintenance

Tradeoffs

* Fastest implementation
* No engineering required

* Limited control over UX
* Limited customization

➡️ Next step: Hosted Onboarding (Rapid / Flex)

Invites (Backoffice + API)

What it is

A hybrid onboarding approach where you initiate onboarding and optionally pre-fill merchant data before sending them to a hosted onboarding flow.

How it works

1. Select configuration:

   • Product (service provider context)
   • Fee template
   • Onboarding template

2. Choose invite type:

   • New Applicant
     • Creates a new applicant and sub-merchant
   • Existing Applicant
     • Adds a new sub-merchant for an existing applicant

3. Optionally pre-fill onboarding data

4. Send invite → merchant completes onboarding via hosted flow

What can be pre-filled

All onboarding fields can be pre-filled:

Applicant

• Name
• Email
• Phone
• Reference (metadata)

Business

• Legal name
• DBA name
• TIN / Tax ID
• Address
• Website
• MCC
• Expected volume
• Established date

Owners

• Name
• Email
• Phone
• Date of birth
• SSN
• Ownership percentage
• Address

Bank Accounts

• Account name
• Account type
• Routing number
• Account number

Fees (optional)

• Card processing fees
• ACH / eCheck fees
• Chargebacks
• Scheduled fees

Operational notes

• UI/UX is shared

  • You control data + initiation
  • Jupico controls onboarding experience

• Fee configuration is optional

  • Defaults to product fee template

• Can be created via:

  • Backoffice (manual workflows)
  • API (automated / embedded workflows)

• Supports embedding via the Invites API

Tradeoffs

Pros

• Pre-fill reduces friction
• Supports ops-assisted onboarding
• More control than hosted

Cons

• Still uses hosted onboarding UI
• More setup than Rapid/Flex

➡️ Next step:

• Invites Overview
• Invites API Reference

Provisioning API

What it is

A fully API-driven onboarding approach where you build and control the entire onboarding experience.

Best-fit use cases

• Fully embedded onboarding in your platform
• Complete control over UX and flow logic
• Platform or marketplace integrations

How it works

1. Build your own onboarding UI
2. Collect merchant data
3. Send data to Jupico via APIs:

• Create applicant
• Create application (applicant + owners)
• Create sub-merchant (business)
• Update entities as needed

Key capabilities

• Partial onboarding supported

  • Submit data incrementally
  • Update later via API

• Full control

  • UX
  • Validation
  • Flow logic

Operational notes

You own:

• UI/UX
• Data collection
• Validation

Jupico handles:

• Underwriting
• Provisioning
• Processing setup

Tradeoffs

Pros

• Full control over experience
• Fully embedded onboarding
• Maximum flexibility

Cons

• Highest engineering effort
• Longer time to launch
• Ongoing maintenance

➡️ Next step: Provisioning API

Decision Guide

Quick Decision Tree

• Want fastest launch with minimal effort?
  → Hosted Onboarding (Rapid / Flex)

• Want to pre-fill data or assist onboarding?
  → Invites

• Want full control and embedded onboarding?
  → Provisioning API

Decision Matrix

Next Steps

• Start with Hosted Onboarding (Rapid / Flex)
• Explore Invites (Backoffice + API)
• Build with Provisioning API