Custom Payments
Custom Payments are for platforms that want to own the checkout experience and transaction orchestration while using Jupico for secure tokenization, processing, and settlement.
When to use Custom Payments
Use Custom Payments when:
- checkout must remain fully inside your product;
- you need authorization and later capture;
- you need tax withholding or release behavior;
- you need dynamic fee logic;
- you need ACH/eCheck acceptance in a custom flow;
- you want to save payment methods for future use;
- your platform needs detailed control over status and error handling.
Custom payment building blocks
| Building block | Purpose |
|---|---|
| Browser authorization session | Defines the merchant and enabled payment methods for the payment page. |
| Web components | Collect card, bank, or wallet details securely. |
| Payment token | Represents the payment method without exposing sensitive data. |
| Transaction API | Executes sale, authorization, capture, void, refund, or rollback operations. |
| Metadata | Connects Jupico payments to your platform orders, customers, and reconciliation records. |
| Web-hooks / queries | Keep your platform synchronized with payment status. |
Implementation flow
- Your backend creates a browser authorization session.
- Your frontend renders one or more Jupico components.
- The customer provides payment details.
- Jupico returns a tokenization result.
- Your backend executes the correct payment operation.
- Your backend records Jupico IDs and platform references.
- Your application updates order, invoice, subscription, or installment state.
- Web-hooks and queries reconcile final status.