Frequently asked questions

Connect your accounting ledger, record your customer's payment authority, and schedule collections for agreed invoice due dates or milestones.

We support Xero, QuickBooks, Sage, Visma, Fortnox and MYOB.

You can schedule a collection for an agreed invoice due date or milestone when valid payment authority is on file and any required advance notice has been sent.

You choose. You can collect upfront, when your customer pays by link, or on the due date or milestone you agreed with them. For a debit, your customer agrees to pay on a particular date, and PaidonDue acts as your agent to collect it on your behalf. Every agreement and consent is recorded and timestamped, and every collection is subject to your customer's authority and advance notice.

They review the payment terms and provide authority on a secure hosted page. Future collections must stay within that authority and meet the required notice and eligibility checks. They can withdraw their authority.

We retry on a schedule and keep you informed. You always have full visibility of anything that didn't collect. A retry can't guarantee collection.

No. You keep creating invoices exactly as you do today, in your existing ledger.

That invoice is simply not auto-charged. You still see it and can chase it manually, exactly as before.

Where a payer has separately authorised it, you can also collect an agreed deposit or milestone payment before the due date, or set up an instalment plan across several dates — subject to the same authority and notice rules as a due-date collection.

If the retry schedule is exhausted, the invoice is flagged under Attention needed on your dashboard so you can arrange payment another way. A retry never guarantees collection.

If a payer disputes a debit as unauthorised or incorrect, refund options are handled under the applicable scheme rules by whoever processed the payment or the payer's own bank — raise it through your account.

You separately authorised a merchant to collect payment from you. The invoice reference, amount and due date shown to you are supplied by that merchant.

You'll be sent notice of the amount and date of a debit before it happens, as your authorisation and the payment scheme require — including before a retry after a failed payment.

Contact the merchant, or your own bank — those are the two routes named in the authorisation you signed. Cancelling doesn't cancel anything you already owe, and a cancellation is honoured promptly.

Yes. Every client is its own separate workspace — its own ledger connection, its own customers, its own authorisations — and you switch between them from a single login.

Per organisation. If you manage several client businesses, each one has its own subscription.

Yes — permissions are granted per person, per organisation. A staff member with no grants on a client can do nothing on that client's data.

Payment write-back works with all six supported ledgers once it is switched on for that client organisation in Settings, with the bank account to record payments against chosen. Each collected payment is then recorded against its invoice, so it reconciles in the client's ledger instead of being keyed in by hand. With write-back off, a collected payment does not appear in the client's ledger automatically.

PaidonDue is software only and never receives, holds or controls your customer's money. The merchant is the merchant of record; funds settle directly to the merchant's account.

The exact authorisation text, its version, a timestamp, IP address and device information, and the name typed as a signature — kept as evidence, never edited after the fact.

Card and bank details are entered on a secure hosted form and stored in a PCI DSS Level 1 certified vault; PaidonDue's servers never see or store the full card or account number. PaidonDue stores only the limited reference needed to identify each payment method.

Yes. A customer can withdraw their authorisation by contacting the merchant or their own bank, at any time. Cancellation requests are honoured promptly.