Core Platform Roles
Jupico integrations involve four parties working together. Understanding each role helps you scope your integration correctly.Implementation Steps Overview
The guides in this documentation are organized around the order most teams follow when implementing Jupico.Choose Your Implementation Path
Before you start building, make two early decisions that shape the rest of your integration. 1. Integration level — how visible should Jupico be to your merchant? Choose between a deeply embedded experience where Jupico is invisible, a co-branded flow, or a fully Jupico-hosted interface. See the Integration Levels guide for a side-by-side comparison. 2. Onboarding setup — who collects merchant information, and where does the merchant complete that flow? You can use Jupico-hosted onboarding for the fastest launch, Flex onboarding for a branded hosted experience, or the Provisioning API when your platform owns the merchant onboarding UI entirely. After those decisions are made, choose your payment experience: hosted products for a faster launch, custom payments for deeper control, or in-person payments for terminal-based flows.Explore the Docs
Integration Levels
Compare integration tiers and choose how visible Jupico is to your merchants.
Accept Payments
Explore hosted products and custom card, ACH, and wallet payment flows.
Send Payouts
Configure scheduled or API-driven payout workflows for your merchants.
Go-Live Checklist
Validate credentials, webhooks, onboarding, and error handling before launch.
Recommended First Implementation
Follow these steps to build the fastest working proof of concept on Jupico.1
Request or use sandbox credentials
Use the shared public sandbox credentials to start immediately, or request platform-specific sandbox credentials from your Jupico account team.
2
Create or use a test submerchant
In sandbox, use a provided test submerchant ID to simulate a real merchant without completing full onboarding.
3
Create a browser authorization session
From your backend, call the sessions API to create a browser authorization session. The session tells the Jupico web component which submerchant, payment methods, amount, and configuration to use.
4
Render a Jupico web component
Load the Jupico web component bundle on your front end and render the component that matches your payment flow — card, bank account, Apple Pay, or Google Pay.
5
Submit the payment token to the Transaction API
After the component collects and tokenizes the payment details, send the returned token from your front end to your backend, then call the Transaction API or a hosted product to complete the charge.
6
Confirm transaction, balance, and payout behavior in sandbox
Verify the transaction appears in reporting, query its status from your backend, and confirm the expected payout mode for the test submerchant.
7
Validate with the Go-Live Checklist
When the proof of concept is stable, use the Go-Live Checklist to validate credentials, webhook endpoints, merchant onboarding, error handling, payout timing, and operational support paths before switching to production.