Chargebee integration

Connect from Bookkeeping → Integrations → Chargebee with your Chargebee site address and a merchant-created API key. Choose the entire site or one business entity, inspect the key, and confirm that billing scope before saving. Invoice import starts enabled. Payment recording and MakePay notifications start disabled.

Create a site API key

In the intended Chargebee site, open Settings → Configure Chargebee → API Keys and Webhooks → API Keys. Create a dedicated key. Read access is needed for currencies and invoices. Checkout also reads the invoice's customer and subscriptions. Recording confirmed payments requires a key with write permission for invoice payments. See Chargebee's API key guide.

Enter the HTTPS site address, such as https://your-site.chargebee.com. The EU and Australia site domains are also supported. Choose Entire site · All business entities, or choose One business entity and copy its native entity ID from Settings → Configure Chargebee → Business Entities. API keys are site-wide; the selected scope controls which records MakePay can use. The API does not expose an entity-name list, so MakePay shows your actual site address, selected scope and native base currency for confirmation. See Chargebee's business entity settings.

Select Check API key, confirm the billing scope and save. Credentials are encrypted with your MakePay company and connection context and are never returned in summaries. A site or entity already covered by another active MakePay connection cannot be connected again. Distinct entities can connect separately. Replacing a key preserves the same scope and invoice history; changing the site or entity requires disconnecting and creating a new connection. Known Chargebee test sites and test keys support read-only import; actual MakePay payment recording requires a live site.

Invoice payments

To enable Accept and record MakePay invoice payments, choose the Chargebee billing scope and an offline payment method: Other, Bank transfer, Cash or Check. This is Chargebee's native payment classification, so choose the one appropriate for your accounting records.

Checkout requires an open invoice with a positive balance, no active dunning or scheduled retry, and automatic collection disabled for all of its billing context. A subscription's collection setting can override its customer's setting. For consolidated invoices, every subscription must have automatic collection disabled; standalone charges also require the customer setting to be off. MakePay checks the customer and all subscriptions before checkout and before recording. It does not change these vendor settings. A different payment owner requires accounting review.

After MakePay confirms a checkout, the connection records its exact amount against the original Chargebee invoice as an offline payment. It does not charge a stored payment source. The original confirmation timestamp, business entity and chosen payment method are preserved for reconciliation. Chargebee receipt emails are suppressed on this API request; independently configured webhooks and other automations still apply.

Native invoice and transaction amounts use Chargebee's published currency units, including its zero-decimal list and two-decimal UGX rule. Unknown currency definitions and conflicting published ISK definitions require review. Amounts are converted exactly without rounding. Enterprise invoice lines are paged before verifying subscriptions; incomplete, repeated or changing context stops checkout. Automatic checks are bounded to five additional line-item pages and 20 distinct subscriptions per invoice.

Sync, recovery and notifications

Invoice scans run in batches of 20 about every five minutes. Larger sites take multiple runs. Full scans repeat to refresh balances and deletions. The panel shows the most recent 100 imported records. Sync requests another batch. Deleted invoices disable unpaid MakePay links.

Before recording, MakePay stores the exact request and a unique payment reference. Recovery searches Chargebee's transactions for that reference and verifies the customer, currency, amount, method, date, entity, and allocation in both the transaction and original invoice. A paid balance alone is insufficient. Partial allocation, excess money, duplicate references or incomplete evidence remain in review.

An uncertain request is never blindly posted again, even after Chargebee's 30-minute idempotency retention expires. Later runs check the original reference again. Recovery searches up to three pages of 100 transactions and requires a complete search. Use the displayed reference and Chargebee transaction/request logs when reviewing an uncertain result.

Payment-recorded and sync-problem notifications are optional, in-app and deduplicated. Turning recording off or changing its mapping pauses unpaid MakePay links. Already-confirmed checkouts retain their original payment context for reconciliation. Disconnecting preserves local history.

This connection supports invoice import and optional confirmed checkout recording. Wallet expense export, receipt uploads, invoice creation and automatic payment-link insertion into Chargebee documents are unavailable through this connection. No live Chargebee account round trip is claimed without merchant credentials.