How MakePay works with Mekari Jurnal
Mekari Jurnal uses company-specific HMAC credentials for this connection. MakePay signs API requests on the server, checks the company and accounting currency, and imports existing sales invoices before you choose whether to record payments.
The receiving-account choice matters in Jurnal: the native payment endpoint identifies an account by name. MakePay requires an active, unlocked Cash & Bank leaf account whose name is unique among active accounts, together with an existing payment method.
Before you connect
- Jurnal HMAC client ID and client secret for the intended company, with the subscription and scopes needed for the API actions you enable.
- An unlocked Cash & Bank receiving account in the company accounting currency, with a unique active account name.
- Approved sales invoices with a positive whole-unit balance in that accounting currency for checkout recording.
Set up Mekari Jurnal with MakePay
- 01
Obtain company HMAC credentials
Use the Mekari developer portal or your Mekari support contact to obtain the company’s Jurnal client ID and secret. Access for another company or Mekari product requires its own credential pair.
- 02
Confirm the Jurnal company
In Bookkeeping → Integrations → Mekari Jurnal, enter both credentials and select Check API key. Confirm the returned company name, identifier and accounting currency.
- 03
Choose the receipt mapping
Select the eligible Cash & Bank account and an existing payment method. Enable invoice payment recording if wanted; import is enabled separately. MakePay does not create new accounts or payment methods.
- 04
Collect an eligible invoice
Sync sales invoices and share a MakePay link for an approved whole-unit balance. After settlement, MakePay verifies the resulting receive-payment record, its custom reference and the exact invoice allocation.
What happens when a customer pays
Whole-unit invoice payments
Jurnal’s documented payment-creation amount is an integer. Fractional-balance and foreign-currency invoices remain visible for review with checkout disabled. MakePay never rounds an invoice to make it eligible.
Stable references for recovery
Each payment carries a stored custom ID. If the creation response is lost, MakePay retrieves that reference and verifies the receipt instead of posting a replacement. A changed invoice number or account name requires review before an unstarted receipt can be sent.
Check these connection limits
- Draft, void, deleted and fully paid invoices cannot accept new checkout.
- Account and payment-method changes pause unpaid links. Confirmed payments retain the mapping selected for that checkout.
- Wallet exports, supporting-file uploads, invoice creation and existing-invoice edits are unavailable.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
