Overview
Jupico helps software platforms and marketplaces embed payment acceptance, merchant onboarding, and payout workflows into their own products. The guides are organized around the order most teams follow when they implement Jupico:
- Get started — learn the environments, credentials, test data, and launch requirements.
- Onboard merchants — choose how your merchants will apply, get approved, and access Jupico-powered services.
- Accept payments — choose hosted payment products or build a custom card, ACH/eCheck, or wallet flow using tokenization and our Transaction API.
- Send payouts — configure scheduled payouts or send payout instructions through API-driven workflows.
- Secure and operate — protect your integration, monitor account and transaction activity, and use support resources.
Who these guides are for
These guides are written for platform product, engineering, implementation, and operations teams. They assume your platform is integrating Jupico on behalf of merchants, sellers, service providers, or other recipients who need to accept payments, receive payouts, or both.
Core platform roles
Jupico integrations usually involve four parties:
| Role | Description |
|---|---|
| Jupico | Payment facilitator and platform infrastructure provider. |
| Platform / Service Provider | The software platform embedding Jupico into its product experience. |
| Merchant / Sub-merchant | The business, individual, or organization accepting payments and/or receiving payouts. |
| Customer / Cardholder | The end customer making a payment or saving a payment method. |
Choose your implementation path
Most platforms make two early decisions:
- Integration level: How visible should Jupico be to your merchant?
- Onboarding setup: Who collects the merchant’s onboarding information, and where does the merchant complete that flow?
After those decisions are made, you can choose the payment experience: hosted products for faster launch, custom payments for deeper control, or in-person payments for terminal-based flows.
Recommended first implementation
For the fastest proof of concept:
- Request or use sandbox credentials.
- Create or use a test sub-merchant.
- Create a browser authorization session.
- Render a Jupico web component for card, bank account, Apple Pay, or Google Pay collection.
- Submit the returned payment token to the Transaction API or to a hosted product.
- Confirm the transaction, merchant balance, and payout behavior in sandbox.
When the proof of concept is stable, use the Go-Live Checklist to validate credentials, web-hook endpoints, merchant onboarding, error handling, payout timing, and operational support paths.