Variants: Rapid vs Flex
Hosted Onboarding comes in two variants depending on your integration level.Best-fit use cases
Hosted Onboarding is the right choice when:- You want the fastest possible go-live.
- You have no engineering resources available for a custom onboarding UI.
- A standardized onboarding experience is acceptable for your merchants.
- You want Jupico to own onboarding UX, validation, and compliance updates automatically.
How it works
1
Jupico hosts the onboarding flow
Jupico provides a unique onboarding URL for your platform. The hosted flow collects business, ownership, processing, and payout information and handles all validation.
2
You share the link with merchants
Direct merchants to the hosted onboarding URL from your product, via email, SMS, or any communication channel. For Backoffice-tracked invites, use the Invites section in Backoffice to send a tracked link.
3
Merchants complete onboarding in the hosted UI
Merchants fill in their details directly in the hosted form. Jupico handles field validation and guides merchants through each section.
4
Jupico reviews the application
Once submitted, Jupico underwriting reviews the application and submerchant record. Both remain in
review status until the review is complete.5
Your platform activates the approved merchant
Monitor status through Backoffice, status API queries, or webhooks. When the merchant is approved, enable payment acceptance and payouts in your product.
Operational notes
- Jupico owns onboarding UX and validation — you do not need to maintain compliance updates.
- Flex supports branding customization (logo, colors, “Powered by Jupico”) but does not allow full UX restructuring.
- Backoffice-sent invites are trackable from the Invites page; links shared outside Backoffice are not tracked.
- Minimal ongoing maintenance is required after launch.
Tradeoffs
Pros
- Fastest implementation path — no engineering required for onboarding UI.
- Jupico handles all compliance logic and automatic updates for new requirements.
- Flex variant adds platform branding without additional development.
- Minimal ongoing maintenance burden.
Cons
- Limited control over onboarding UX and flow logic.
- Limited customization beyond branding (Flex) or no customization (Rapid).
- Cannot pre-fill merchant data from your own records (use Invites for pre-fill).
- Merchant experience is partially or fully Jupico-hosted.
What to do next
If you need more control over the onboarding experience, explore the following options:Flex & Invites
Send pre-filled invite links to merchants via Backoffice or the Invites API.
Provisioning API
Build fully embedded, API-driven onboarding with complete control over UX and flow.