Hosted Payments
Hosted payment products are the fastest way to collect payments without building a custom payment UI. Jupico hosts the core payment experience and handles sensitive payment collection.
Hosted product options
| Product | Best for |
|---|---|
| Checkout | Redirect or embedded checkout for a specific purchase. |
| Payment Links | Send a payment request by link without building a checkout page. |
| Invoicing | Create, send, and track invoices. |
| Subscriptions | Ongoing recurring billing built from reusable plans. |
| Installments | Finite payment plans for a known total amount. |
Why use hosted payments
Hosted payments are useful when:
- you want to launch quickly;
- your platform does not need full control over every payment form field;
- you want to reduce payment-form maintenance;
- you want Jupico-hosted tokenization and payment collection;
- you need a payment workflow that can be sent by link or invoice.
Hosted vs custom
Choose hosted payments when the payment experience can live on a Jupico-hosted page or workflow.
Choose custom payments when your product needs native checkout, custom authorization/capture behavior, custom wallet placement, or direct Transaction API control.
Operational considerations
Even with hosted payments, your platform should track:
- merchant ID;
- customer or payer reference;
- order, invoice, subscription, or installment ID;
- payment status;
- payout status;
- metadata needed for reconciliation;
- web-hook events and retries.