LHV LinkPay: let customers pay directly from an invoice

Sending an invoice should also give your customer a clear next step. Aeglio now supports LHV LinkPay for EUR invoice payments: the customer opens the invoice, starts checkout and completes payment on LHV’s hosted payment page.

For teams with the integration available and configured, this brings the payment action into the invoice workflow you already use. You do not need to create and paste a separate merchant-portal link for every invoice.

If you are ready to connect it, follow our LHV LinkPay setup guide. It covers the payment fields, credentials and notification settings in five short steps.

From the invoice to checkout

The public invoice shows a payment button for its outstanding balance. Aeglio prepares the payment details when the customer starts checkout, including the amount and invoice number.

That matters for partially paid invoices too. If an invoice has a remaining balance of €23.30, the payment offered is for that balance, not automatically for the original total.

The customer completes payment on the provider’s page. Available payment methods depend on your LHV merchant configuration; connecting Aeglio does not enable every bank or card method on your behalf.

This integration is EUR-only. It does not convert an invoice from another currency or change the currency of an existing document.

No default provider to manage

You do not have to nominate a default payment provider.

• With one eligible provider, the payment button opens that provider directly.
• With multiple eligible providers, such as Stripe and LHV LinkPay, the customer chooses from the available options.
• With no eligible provider, the online-payment action is not shown.

Eligibility is checked for the particular invoice. A connected integration alone does not make drafts, fully paid invoices or unsupported currencies payable.

This keeps the setup straightforward for teams that want only LinkPay, while allowing teams already using Stripe to offer a choice.

Pay from a PDF

Invoice emails can take customers to the public invoice page, where they use the payment button. The QR code appears only on eligible invoice PDFs, labelled “Pay online”, and is also clickable.

The QR opens a small Aeglio payment screen instead of the full invoice. It checks the current balance and available payment providers before the customer continues to checkout. An older PDF therefore does not start a new payment for an outdated printed amount.

Treat invoice links and payment QR codes as private access links. Share them with the intended recipient and keep working links or codes out of public screenshots. Scanning the QR does not create a payment attempt or charge the customer; checkout starts only after they press the payment button.

A payment is recorded after verification

A successful return to the website is not enough to mark an invoice paid.

Aeglio uses payment notifications and authenticated checks with LHV to verify the transaction before recording the invoice payment. This also lets verification continue when a customer closes the checkout tab instead of returning to the invoice.

Repeated notifications must not create repeated invoice payments. If verification cannot be completed, the payment remains available for investigation rather than being treated as successful. A second genuine payment is held for review instead of automatically settling the same invoice twice.

If the provider shows a completed payment but Aeglio is still waiting, check the original transaction before asking the customer to pay again.

Invoice numbers and references keep their own roles

The checkout carries the invoice number, but it also has a separate technical order reference. That identifier connects the payment attempt to Aeglio’s verification process; it is not the invoice’s bank-payment reference.

When the invoice has a valid ISO 11649 RF reference, Aeglio sends it as the optional payment reference. An Estonian domestic 7-3-1 reference is not converted into an RF reference or sent in that field.

The invoice number and technical order reference are still provided when the optional RF reference is absent. You do not need to change an existing domestic reference just to offer LinkPay.

What setup involves

An owner or administrator connects LinkPay in the team’s integration settings. You need an LHV merchant account with LinkPay access, a reusable EUR LinkPay configuration and your API credentials.

The setup has four main parts:

1. Configure the portal link so Aeglio can supply the amount, invoice number and technical order reference, with the RF reference optional.
2. Enter the API username, API secret and LinkPay token in Aeglio.
3. Copy the notification URL from the saved connection into the e-shop’s payment settings.
4. Enable online payments on your invoices.

The settings modal stays open after saving, so you can copy the notification URL without reopening it. The online-payments toggle is inside the same modal.

The EUR processing account is selected in the merchant portal; you do not need to enter it again in Aeglio.

Separate from LHV Connect

LHV LinkPay is for collecting customer invoice payments. LHV Connect remains a separate banking integration. Connecting either one does not configure the other.

LinkPay also does not pay your Aeglio subscription or set up recurring customer charges through this integration.

For the exact payment fields and notification settings, follow the step-by-step LHV LinkPay guide.