Payment matching

In short

Orders → Payment matching watches the movements on your connected bank accounts, finds the matching order and marks it as paid. It is off by default and is turned on through a single wizard, where you also say what should happen to the order.

What you need first

1. A connected bank account under Settings → Connected apps (the account token).
2. At least one e-shop whose orders are being read.

Turning it on

On the Overview tab click Turn on matching. The dialog asks for:

Section	What it covers
What happens after a match	Mark the order as paid (on by default) and add a note.
Which e-shops	Where matching runs, which accounts the payments arrive on and, for each e-shop separately, whether the order status should change too (optional).
Notifications and documents	Whether the e-shop should send the customer an e-mail or SMS and issue a document. By default it behaves exactly as if a person made the change.
What will be set up	A summary: which automation is created, which is extended or switched on, and exactly what it will do.

The order status is required only for an e-shop whose platform cannot record payment directly — the order status then expresses it.

Once confirmed, the app creates the automation that processes a matched payment and activates it right away. You will find it in the Automations module under “Bank payment: mark order as paid” — you can edit it, extend it or switch it off there.

When a payment is matched

A payment is linked to an order only on unambiguous evidence:

• it is an incoming payment on an account that belongs to that e-shop,
• the variable symbol or the order number in the message matches the order number,
• the amount and currency match,
• exactly one order qualifies and it is not paid yet.

A matching amount alone is never enough. If two orders qualify, the payment stays unmatched and waits for you — that is by design, not a failure.

What you see

• Overview: whether matching is running, how many payments were matched, how many found no order and where something does not add up.
• History: every movement with the reason for its outcome. Filter by period, account, e-shop or result.
• Order detail: next to the payment state there is a badge with the amount, account, time and reference.

Another e-shop or another bank

Turn on another e-shop on the E-shops tab with Turn on. The same dialog as for the first setup opens and tells you what will happen:

• the e-shop joins the automation that does exactly what you chose for it (payment, optionally the order status); if there is none, a new one is created — your edits in existing ones stay,
• if an existing automation does not mark the order as paid (it was created from an older version of the template), the dialog offers to add the step “Mark the order as paid” — on by default,
• you choose the order status for each e-shop separately and it is optional,
• if the automation is not switched on, the dialog switches it on,
• if your own automation already handles the e-shop, nothing else is created for it.

When the order statuses of an e-shop cannot be loaded, the dialog says so next to the e-shop, with the reason, and offers Try again.

The automation is not tied to a particular bank or account: it covers payments from every account assigned to the e-shop. After connecting another bank, just assign its account.

When an e-shop is being matched but no active automation handles it, the overview says so and Add to automation opens the dialog for exactly that e-shop. The overview likewise flags an active automation that does not mark the order as paid after a match, and Add marking as paid opens the dialog where the step is added.

If matching ran without the automation

A payment is processed once. If matching ran for a while without the automation, those orders were found but never handled. That is why the Overview tab has Process again — it replays matched payments from the last 30 days. An order that is already paid is not marked twice by the e-shop, so nothing breaks.

Common questions

The payment arrived but the order is not paid. Check the history: each movement says whether the variable symbol was missing, the amount did not match, or two orders qualified.

The customer paid twice or sent a different amount. Such a payment is not matched and you handle it manually. The app deliberately does not guess at “close enough” matches.

Can I turn matching off? Yes, with the toggle on the Overview tab. That switches off the search for payments; the automation stays active but has nothing to process, because no matches are created. Turning matching back on continues with your edits intact. To stop the rule as well, switch it off in the Automations module.

Who can open this

The screen is visible to the administrator. It shows bank accounts and payment amounts, so it is not available to other roles by default.