Skip to main content
Before a merchant can accept payments or receive payouts through Jupico, they must be created, reviewed, and approved. Onboarding collects the business, ownership, processing, and payout information Jupico needs to underwrite the merchant and activate the right capabilities. Jupico supports a range of onboarding models so your platform can decide how much of the experience Jupico hosts and how much your product owns.

​
Two decisions to make

Merchant onboarding involves two related decisions that you make early — one about the merchant relationship model, and one about the implementation path. The integration level defines the business and user-experience model. The onboarding setup defines the implementation path. Choose both before you begin building.

​
Typical onboarding lifecycle

1

Create or invite the merchant

Start the application through Backoffice, an invite flow, a hosted onboarding link, or an API call.
2

Collect business and owner details

Gather the required information for the selected business type, including business identity, ownership, processing expectations, and payout information.
3

Submit for review

Jupico underwriting reviews the application and submerchant record. Both remain in review status until underwriting completes its checks.
4

Track account approval status

Monitor account status through Backoffice, API queries, or webhooks. Build your platform to handle merchants at every state — started, submitted, approved, and rejected.
5

Activate processing

Once approved, the merchant can accept payments and/or receive payouts according to its product configuration.

​
Account types

Jupico account types control how much of the merchant experience is hosted by Jupico versus owned by your platform.
  • Rapid is the fastest path. The merchant has a direct Jupico-branded experience and can access the Jupico Backoffice.
  • Flex keeps Jupico in the merchant relationship but adds platform branding and optional platform-controlled steps, with a “Powered by Jupico” positioning.
  • Custom lets the platform own the merchant-facing experience entirely and use APIs to submit onboarding data to Jupico.
Contact Sales to learn more about which account type fits your program.

​
Onboarding setups

The following table compares the three primary onboarding approaches side by side.

​
Quick decision guide

Choose Hosted Onboarding (Rapid / Flex) when:
  • You want to go live as quickly as possible.
  • You have no engineering resources for a custom onboarding UI.
  • A standardized onboarding experience is acceptable.
→ See Hosted Onboarding

​
Explore further

Integration Levels

Compare Rapid, Flex, and Custom to choose the right merchant experience and branding model.

Hosted Onboarding

Share a URL and let Jupico handle the entire onboarding UI and validation.

Flex & Invites

Send trackable invite links with optional pre-filled merchant data.

Provisioning API

Build fully embedded onboarding using the Applicant → Application → Submerchant sequence.

​
Account Types & Abilities Matrix

Use this matrix to compare capabilities across all three integration levels before committing to a model.
Last modified on July 15, 2026