How MakePay works with Daftra
Daftra separates the business address, receiving treasury and payment method used for a receipt. MakePay keeps those settings with each checkout, so a confirmed settlement is recorded using the mapping that was selected when the customer paid.
The released connector uses Daftra’s API-key endpoints. It imports standard invoices and optionally records completed invoice-payment receipts. You keep using Daftra to create the invoice and manage its document templates.
Before you connect
- A public HTTPS business address on daftra.com or daftara.com and a dedicated API key.
- A receiving treasury in the invoice currency and an enabled manual Bank transfer or Cash payment method.
- A supported numeric business date format, such as DD/MM/YYYY, MM/DD/YYYY or YYYY-MM-DD.
Set up Daftra with MakePay
- 01
Check your hosted business
Generate the API key in Daftra Settings → API → API Key. In MakePay Bookkeeping, enter that key and the business address, then confirm the detected business identity and base currency.
- 02
Map the treasury and method
Select an active receiving treasury. Check in Daftra that your chosen Bank transfer or Cash method is enabled, then confirm it in MakePay. The API-key connector cannot read the newer OAuth-only method settings.
- 03
Share an imported invoice
Enable invoice payment recording and sync. Share the MakePay URL from the connection panel or Invoices list. Checkout verifies the current customer, invoice currency, balance and treasury before it can proceed.
- 04
Confirm the completed receipt
After settlement, MakePay creates the Daftra receipt and verifies its Completed status, original invoice, transaction reference, date, amount, treasury and method. Review the resulting entry and your own Daftra payment-method rules.
What happens when a customer pays
Treasury currency follows the invoice
Foreign-currency invoices are supported when the selected treasury uses that currency. Daftra handles its own accounting conversions. MakePay does not invent a crypto exchange rate, and checkout values must fit two decimal places exactly.
Settings remain attached to the payment
Changing a method or treasury pauses old unpaid links. A payment that already completed is reconciled using its original mapping. Receipt recovery checks the exact stored transaction reference before any manual follow-up.
Check these connection limits
- Custom domains, private addresses and redirecting business URLs are unsupported.
- Debit notes and advance payments are excluded. Draft and fully paid invoices cannot collect a new payment.
- The connector shares links locally; it does not replace existing invoice documents, export wallet expenses, upload receipts or create invoices automatically.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
