How MakePay works with Chargebee
Chargebee can collect subscriptions automatically, while a MakePay payment is completed by the customer outside Chargebee. This connector therefore checks the full billing context before offering crypto checkout, including every subscription contributing to a consolidated invoice.
You can connect the entire site or a single business entity. Chargebee keys are site-wide; the scope you confirm in MakePay determines which invoices the connection can use. Existing invoice records remain in Chargebee.
Before you connect
- A merchant-created Chargebee API key and HTTPS site address on a supported Chargebee production domain.
- The native business entity ID if connecting one entity instead of the whole site.
- An eligible open invoice with automatic collection disabled across its customer/subscriptions, no dunning or scheduled retry, and an offline payment method selected in MakePay.
Set up Chargebee with MakePay
- 01
Prepare the site API key
Create the key under Chargebee Settings → Configure Chargebee → API Keys and Webhooks. Allow the reads needed for invoices, currencies, customers and subscriptions, plus invoice payment writes when recording is enabled.
- 02
Confirm the site or entity
Enter the site address and key in Bookkeeping → Integrations → Chargebee. Choose Entire site or One business entity and supply its native ID. Confirm the actual site, selected scope and base currency.
- 03
Review automatic collection
Before sharing a MakePay link, disable automatic collection in the original Chargebee billing context. A subscription can override its customer. All subscriptions on a consolidated invoice must satisfy the eligibility checks.
- 04
Record an offline payment
Choose Other, Bank transfer, Cash or Check as the native payment classification, then enable recording and share an eligible invoice’s MakePay link. A verified settlement records the exact amount with its original entity and confirmation time.
What happens when a customer pays
Entity-aware invoice collection
MakePay preserves the chosen billing scope for each checkout and verifies it during receipt recovery. A site or entity already covered by an active connection cannot be connected again with overlapping scope; distinct entities can connect separately.
Offline receipt without charging a stored source
The connector records an already received payment rather than invoking automatic collection. Chargebee receipt emails are suppressed on that API request. Your independently configured webhooks and other Chargebee automations still apply.
Check these connection limits
- Known test sites and keys support read-only import; actual MakePay payment recording requires a live site.
- Large consolidated invoices are subject to bounded line/subscription checks. Incomplete or changing billing context requires review.
- Wallet expenses, receipt uploads, new invoice creation and automatic payment-link insertion into Chargebee documents are unavailable.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
