Daftra integration

Connect a Daftra business from Bookkeeping → Integrations → Daftra using its API key. Import existing invoices and optionally record confirmed MakePay payments. No MakePay OAuth app is required.

Connect your business

1. In the intended Daftra business, open Settings → API → API Key. Generate a dedicated key with access to the business profile, invoices, invoice payments and treasuries needed for your chosen workflows. See Daftra's authentication guide.
2. Select Connect, enter your HTTPS business address on daftra.com or daftara.com and the key, then select Check API key. Custom domains, private servers and redirecting addresses are not supported.
3. Confirm the detected business name, ID and base currency. Use a different key and business address to choose another business.
4. For payment recording, select an active receiving treasury and a manual Bank transfer or Cash method. Check that the method is enabled in Daftra Settings → Payment Methods, then confirm it here. The API-key connection cannot retrieve the newer OAuth-only payment-method settings.
5. Enable only the workflows you want and save. Invoice import starts enabled; payment recording and notifications start disabled. The key and business address are stored together using tenant-bound encryption. The key is never returned to the browser after saving.

The receiving treasury must use the invoice's currency. Foreign-currency invoices are supported when the selected treasury uses that currency; Daftra handles its own accounting conversions. The connector never infers a crypto-to-fiat exchange rate. Payment values must be positive and have at most two decimals.

Invoice payments

Enable Accept and record MakePay invoice payments to share MakePay links from imported open invoices. Links appear in the connection panel and the main Invoices list. Only standard invoices are imported; debit notes and advance payments are excluded. Draft and fully paid invoices cannot accept new payments.

Checkout verifies the current invoice, customer, currency, balance, receiving treasury and business identity. Each issued checkout keeps its chosen method and treasury. Changing these settings pauses previous unpaid links; an already completed payment is reconciled using its original mapping. Disabling payment recording prevents new checkouts but does not discard completed settlements.

Only verified MakePay settlements can create a Daftra payment receipt. Demo or sandbox sessions, adjusted settlements, mismatched values and multiple completed checkouts wait for review. Browser redirects do not mark invoices paid.

Daftra creates new receipts as Completed and derives the customer and currency from the invoice. MakePay rereads the created receipt and verifies its completed status, invoice, currency, amount, date, treasury, method and transaction reference. Recording can affect your ledger and any rules configured for that payment method in Daftra.

Dates, sync and notifications

The connector formats payment dates using the business's numeric date format, such as DD/MM/YYYY, MM/DD/YYYY or YYYY-MM-DD. Unsupported text-month date formats prevent payment recording before a checkout is created; invoice import remains available. API receipt dates must be returned in the documented ISO/SQL date representation for verification.

Sync runs in batches about every five minutes. Invoice scans use ascending IDs, validate pagination and repeat full scans to pick up edits. The panel displays the most recent 100 imported invoices. Larger businesses need multiple batches. Sync loads another batch. Invoices with incompatible data show a connection error instead of being interpreted as a different document type or currency.

Notifications for recorded payments and sync problems are optional, in-app and deduplicated.

Recovery and connection limits

Every receipt has a stored MakePay transaction reference before its creation request is sent. If a request times out, MakePay searches that exact reference. A matching receipt is verified and recovered. An uncertain outcome without a matching receipt remains pending review; another payment is not automatically created. Check the reference in Daftra before taking manual action.

Use Replace API key to rotate credentials for the same detected business. Disconnect before choosing a different business. Disconnect pauses unpaid checkout links and requires completed payments to be reviewed first. Reconnecting the original business preserves its invoice links and history.

This connection uses Daftra's API-key /api2 endpoints. The newer /v2/api/entity endpoints require OAuth and are excluded from this connection. Existing-invoice updates require full document replacement, so MakePay shares payment links locally instead of modifying invoice notes. Wallet expense exports, supporting-file uploads and automatic invoice creation are not enabled through this connection.

Local API and recovery tests use fixtures. A live Daftra account round trip requires a merchant API key and is not implied by the fixture results.