When to use Invoicing
Use Invoicing for:- accounts-receivable workflows where you need to track open and overdue balances
- service billing sent to business customers
- B2B payment requests that require a formal invoice document
- itemized charges broken down by line item
- payments that require an invoice number or due date
- operational teams that need to monitor sent, viewed, paid, overdue, and cancelled states
Typical flow
1
Create the invoice
Create an invoice with the merchant, customer details, amount, description, and any invoice-specific fields such as invoice number, due date, and line items.
2
Send the invoice
Send the invoice to the customer directly from Jupico, or surface it from your platform.
3
Customer pays
The customer pays through the hosted invoice payment experience.
4
Jupico records the result
Jupico records the payment attempt and its outcome against the invoice record.
5
Update invoice status
Your platform updates invoice status through webhook events, query APIs, or the reporting interface.
What to configure
An invoice should include:- Merchant or submerchant — the account issuing and receiving payment for the invoice
- Customer or payer details — name, contact, and any customer reference from your platform
- Invoice number or platform reference — your identifier for the invoice
- Due date — the date by which payment is expected
- Line items or description — an itemized breakdown or summary of what is being billed
- Tax amount — applicable tax, if any
- Payment methods — which options the customer can use to pay
- Metadata — key-value pairs for reconciliation and reporting
Status model
Design your platform to handle the full invoice status lifecycle:Invoicing vs Payment Links
Use the table below to decide which approach fits your use case:Payment Links vs Invoicing — Use Payment Links for lightweight payment requests where invoice identity isn’t needed. Use Invoicing when the request requires an invoice number, due-date behavior, itemization, or accounts-receivable tracking.