Skip to main content

External integrations

The Integrations screen gathers everything that links POSfix to outside services, in groups. You turn most links on once, and after that they work in the background.

A link doesn't replace the documents. The statements brought in from maib are the same statements you would have imported from a file, and electronic invoices are still issued from Sales.

Where to find it: Sidebar → Integrations

The label in the card's corner says how it gets linked:

  • Connected or Not Connected — you link it yourself; the button at the bottom takes you to the setup, and for webhooks, to their log;
  • Via the PosFix team — our technician links it. The button at the bottom — Request connection, Request installation or Request a key — opens the support window, with the request already written. Once the sensors are installed, their card turns Connected;
  • Via file — it works through the uploaded file, like the statement from other banks;
  • Coming soon — announced, with no action yet.

Payment requests from the panel and Fiscal station have no label: the button takes you straight to their page.

A card with a padlock and the Not in your subscription label is a paid integration you don't have: See what's included shows you what it does and what it costs. A few integrations sold only by contract, such as the Fiscal station, don't appear at all until you have them. If you had it and it expired, it says Access expired, and the button becomes Renew the subscription.

e-Factura​

e-Factura is the State Tax Service system through which you issue and receive electronic tax invoices. The link comes with the e-Factura module and you set it up once, from its card.

To link POSfix to e-Factura:

  1. On the e-Factura card press Set Up Connection (or Configure, if you already have saved credentials).
  2. Open the How to get the e-Factura API credentials guide and create an "API" type user in the SFS portal. You do this once.
  3. In SFS Credentials choose the Environment and type the API user's Username and Password.
  4. Press Save Settings.
  5. Press Test Connection — you get Connection Successful or Connection Failed.

The e-Factura settings, with the guide closed

1 the environment · 2 the API user · 3 its password · 4 saving · 5 the connection test

The order matters: Test Connection is grey until you have saved credentials. It doesn't test what you typed, but what stayed in POSfix, so saving comes first.

The band at the top says E-Factura Configured (green) or E-Factura Not Configured (yellow). As long as the integration isn't configured, the guide with the steps through the SFS portal opens by itself; after you have saved the credentials, you find it folded. The panel remembers whether you opened or closed it yourself.

The password is no longer shown after saving. The field stays empty and, if you leave it that way, the existing password doesn't change. The Delete Credentials button only appears when the integration is configured and asks for confirmation; documents already sent stay in POSfix.

The environment is preselected on Production

The Environment selector starts on Production, not Test. If you save without touching it, you are straight on real invoices. On Test, invoices don't reach real partners and have no tax value — choose it explicitly while you check the flow.

The responsible persons​

The screen shows you, read-only, the Administrator and the Chief accountant from the organization settings. You fill the list in under Settings → the Organization Settings tab, the Responsible Persons section; the Organization Settings link at the head of the section takes you straight there. Other positions don't appear here.

Day-to-day work with invoices isn't done here, but in Sales → the E-Factura tab and in Purchases → the E-Factura tab. The details are in e-Factura.

maib — bank statements​

The maib link brings in the statements of your bank accounts by itself, several times a day. It is free: all you need are the keys the bank gives you for API access.

What reaches POSfix is the same statement you would have imported from a file — you find it in Money → the Bank Statements tab and post it the same way. The link doesn't post anything on its own.

To turn the link on:

  1. On the maib — bank statements card press Set Up Connection.
  2. Under Bank keys type the Client ID and the Client secret.
  3. Press Save and verify with the bank. POSfix asks the bank whether the keys are good.
  4. Your maib accounts appear under Bank accounts. For each one, choose the Platform account and turn on Sync.
  5. Press Save and verify with the bank again.

The maib settings, before the keys are verified

1 Client ID · 2 Client secret · 3 creating missing partners · 4 saving and verifying with the bank

A bank account whose IBAN matches a bank account in POSfix gets linked by itself. The others stay Not linked until you choose the account. An unlinked account can't be synced: the statement needs a place to land.

Fetch from says where the first fetch starts. If you leave it empty, POSfix sets it on save to the day after the account's last statement, so it doesn't duplicate what you already imported from a file. If the account has no statement at all, it starts from the beginning of the current month.

After the first save, the secret key is no longer shown. You only see its last characters, and an empty field means "keep the saved key".

When the statements arrive​

The statements arrive by themselves: every half hour during the working day and less often at night. Today stays open at the bank until the evening, so POSfix fetches it once more the next day, with everything that was added.

If you already have a statement for a day, imported from a file or entered by hand, POSfix does not make a second one. Your lines stay as they are, and the payments the bank has but your statement lacks are added to it as new lines. This happens, for example, when the file was downloaded at noon and a payment arrived in the afternoon.

Sync now, at the top of the page, fetches the statements on the spot. Under the keys you see Last success and Next, and at the bottom, under Recent syncs, how many new transactions and how many days each run brought.

Sending payments​

Once the keys are verified, the Sending payments card appears. With the Allow sending payments to the bank toggle on, payment orders can leave for maib directly from POSfix, without a file.

Turning it on asks for confirmation, turning it off doesn't. A sent instruction doesn't execute by itself: it stays in maib Business until a person with signing rights signs it. How you send an order is in Payment orders.

The maib toggles​

ToggleWhat changes when you turn it onIf you leave it off
Create partners missing from the statement (on by default)An unknown payer or beneficiary becomes a new partner, with the name and fiscal code sent by the bankThe row arrives without a partner and you choose it in the statement
Sync (on each account)The account joins the automatic fetching of statementsThe account is visible in the list, but nothing is fetched for it
Allow sending payments to the bankSend to the bank for signing appears on payment ordersThe link only brings in statements and sends nothing to the bank

A new partner is only created when the bank sends the counterparty's fiscal code; without it, the row stays without a partner. Bank fees don't create partners, even with the first toggle on.

Disconnect, from the three-dot menu at the top of the page, deletes the keys and stops fetching statements. The statements already brought in stay in POSfix.

MIA payments and payment requests from the panel​

MIA payments (instant QR) is payment at the till: the customer scans the QR code in any bank's app. Payment requests from the panel is the same thing at a distance — a link or a QR code sent to the customer from an invoice or a payment request.

You set up both on the MIA payments (instant QR) page: till payment on each till, in the Tills table, and the panel requests in their own section. Setting up the requests and what you do with them next are in Payments requested from customers.

Telegram​

The Telegram card takes you to CRM → Channels, where you link the company's Telegram bot. The steps are in Messaging channels.

Nova Post — courier delivery​

Nova Post is a paid integration, separate from the accounting subscription. With it you create shipments straight from the customer order, print the parcel label and follow the delivery to the end. The cash on delivery collected by the courier shows on the order.

You pay for the delivery itself to Nova Post, under your contract with them; the panel only creates the parcel in your Nova Post account. The integration is sold by contract, with no trial period, so until then the card stays locked.

To link the Nova Post account:​

  1. Generate the API key in my.novapost.com → Integrations → API keys, from the company account.
  2. Integrations → the Nova Post — courier delivery card.
  3. Paste the key into API key and press Save. The panel checks it with Nova Post before keeping it.

When it works, the Connection to Nova Post section shows Connected. The key is no longer displayed; you only see its last characters. To change it you paste another one, and a field left empty keeps the saved key. Check connection runs the check again at any time.

If the key belongs to a private person, an amber box appears: parcels then leave in that person's name, and the cash on delivery is paid to them. For the company, generate the key from the organisation account.

What else you fill in the settings​

  • The sender: the name, the contact person and the phone on the label. A name and phone left empty come from the Organization Settings.
  • Where parcels leave from: on each warehouse you ship from, you turn on I ship from here and choose I take them to a branch (with the branch picked from the list) or The courier picks them up (with the pickup address). Parcel lockers and partner points receive parcels but don't send them, so for drop-off you choose a branch.
  • Parcels and delivery payment: the quick sizes, with their dimensions and weight, who pays for delivery by default and the number of your contract with Nova Post. Without a contract, the delivery you pay for is paid in cash, at hand-over.
  • Cash on delivery: the lei account the cash on delivery comes into and who pays the fee. Left empty, the account is the IBAN from the Organization Settings. Cash on delivery needs a separate contract with Nova Post Moldova, and the account must be the one written in it.
  • Notifications: what you learn about parcels, with an In the panel and a By e-mail toggle on each row — delivery problems, a parcel waiting for pickup too many days (you choose the number of days), a delivered parcel.

By e-mail, delivery problems go out Right away. The waiting parcel and the delivered one come only in the Daily summary, at 19:00, so with the summary off you get no e-mail about them. E-mails go to the company's administrators, and Also send the e-mails to adds other addresses, separated by commas.

ToggleWhat changes when you turn it onIf you leave it off
We send parcels as a companyThe company shows on the parcel, with the IDNO from the Organization Settings, and the cash on delivery can come into the company accountThe parcel leaves from a private person, with no IDNO, and cash on delivery into the company account can't be sent
I ship from here (per warehouse)The choice between branch and courier appears; the warehouse's parcels leave from thereThe warehouse isn't used for shipping
Suggest cash on delivery = the order balance dueWhen shipping, Cash on delivery comes filled with what the customer still owes on the orderCash on delivery starts at 0 and you write it yourself, if needed
The customer may inspect the parcel before payingThe customer opens the parcel at pickup, before paying. It's a free Nova Post service, in Moldova onlyThe customer pays before opening the parcel
Daily summary, at 19:00In the evening you get by e-mail the parcels waiting for pickup and the delivered onesYou get no e-mail about them; delivery problems still come, if turned on

We send parcels as a company comes on for a new connection, if the company has an IDNO. Turn it off only when the Nova Post key belongs to a private person. With no IDNO in the Organization Settings, a link straight there appears under the toggle.

The last two toggles only suggest: you can change them on each shipment.

To ship an order with Nova Post:​

  1. On the customer order, in the Delivery card, choose Nova Post under How the goods leave. Fill in the recipient, the recipient's phone and the Nova Post point or the address.
  2. Confirm the order, then press Ship with Nova Post.
  3. In the Nova Post shipment window check the parcel: pick a quick size or type the dimensions and weight, then Parcel contents.
  4. Under Payment check Declared value, Cash on delivery and Who pays for delivery.
  5. When the details are complete, Nova Post calculates the Delivery cost and the estimated date. Press Create shipment.

The delivery lot goes to the courier with the parcel number. From the order you print the label and track the parcel. Parcels created directly in the Nova Post account you see in Sales → Delivery Lots → Nova Post parcels. You link a given one to the order: from the order with I have the parcel number, from the list with Link to order.

If the refusal comes from the settings — the drop-off warehouse or the cash-on-delivery account is missing —, Complete now appears under the message. You fix it right from the window, without losing the shipment.

Webhooks — Integration API​

A webhook is the address where the platform notifies your system by itself — the online shop or the ERP. It notifies it when a product, a stock level, an order or a sale (receipt, invoice, return) is created or changed. It also notifies it when a member joins the loyalty program or when their balance changes. The integrator creates webhooks through the API; in the panel you follow them.

The card comes with the Integration API module, and the Connected status means you have at least one active webhook. The integrator needs a key with the "Manage webhooks" permission. The POSfix team issues the key, once you have the module active. You ask for it from the API keys and online shops card → Request a key: the support window opens with the request already written, and you just send it.

To see what your system received:

  1. On the Webhooks — Integration API card, press Open the log.
  2. The Webhooks list shows each address, its status and its deliveries over the last 30 days.
  3. Press Log on the row, or the row itself. The delivery log opens, newest first.
  4. Filter by Delivered, Failed or In progress and, if you want, by event.
  5. The newest delivery is already expanded; press the others to open them. You see every attempt, what was sent and what your system answered.

The webhook list, with a deactivated webhook and one with a failed delivery

1 the address · 2 the status — here, a deactivated webhook · 3 the deliveries of the last 30 days · 4 Log · 5 Deactivate · 6 Activate, on the stopped webhook

The log of a webhook, with a failed delivery expanded

1 the status filter · 2 the event filter · 3 the attempts, with the code received · 4 what was sent · 5 what your system answered · 6 Resend

The log keeps deliveries for 30 days. Those still in progress aren't deleted until they finish.

Resend a failed delivery​

When your system doesn't answer, or answers with a server error, the platform tries again for a few hours, with longer and longer pauses. If it still doesn't get through, it gives up and the delivery stays Failed.

Most 4xx answers — a wrong address, a rejected signature check — close the delivery as Failed on the first attempt. Your system refused it, so the platform doesn't insist.

Once your system is fixed, open the delivery and press Resend: it goes out again within seconds. The delivery records how many times you resent it. Resend is greyed out while the webhook is deactivated — activate it first, then resend.

Stop a webhook​

Deactivate, on the webhook's row, stops sending to its address. It asks for confirmation, because queued deliveries end without going out. Use it when your system is down for a longer time and you don't want the log to fill up with failures.

Activate turns it back on, without confirmation. New events go out again; the ones that failed in the meantime you resend from the log.

A webhook deleted by the integrator stays in the list with the Deleted status. You see its history through Log, but it can't be stopped, started or resent any more.

Deactivate, Activate and Resend appear only if you have write rights on the webhooks module, in your team's permissions. Without them, the list and the log are visible, but nothing changes.

What can trip you up​

  • Test Connection is grey — you don't have saved e-Factura credentials yet. Press Save Settings first.
  • The e-Factura test fails — wrong username, password or environment. Check the details in the SFS portal, save again and repeat the test.
  • You changed the password at SFS and the transmissions fail — type the new password, press Save Settings, then Test Connection.
  • You added a responsible person and don't see them here — the section only shows the Administrator and the Chief accountant.
  • Wrong maib keys aren't saved: the bank's message appears right after you press Save and verify with the bank, and Bank accounts stays empty.
  • The Error badge next to Bank keys — a link that used to work was later refused by the bank. The reason is written underneath.
  • You can't turn on Sync on an account — choose the Platform account first. If it is missing from the list, create it in Money → the Bank Accounts tab.
  • A POSfix account can't be linked to two of the bank's accounts. Each maib account needs its own account.
  • Today's statement doesn't have all the payments yet — the day is still open at the bank. The rest comes with the next fetch.
  • Send to the bank for signing doesn't appear on the payment order — the Allow sending payments to the bank toggle is off.
  • The Webhooks list is empty — the integrator hasn't created any webhook yet. They create it through the API.
  • Resend is greyed out — the webhook is deactivated. Press Activate on its row, then resend the delivery.
  • The delivery is Failed after a single attempt, with an HTTP 4xx code — your system refused it. Resending won't help until the integrator fixes the address or the check.
  • “Cash on delivery into the company account works only if the parcel is sent as the company…” — turn on We send parcels as a company in the Nova Post settings or send the parcel without cash on delivery.
  • “Nova Post does not accept the account for the cash-on-delivery payout…” — Nova Post pays cash on delivery only into the account from the cash-on-delivery contract. Check the IBAN in the settings; if it's right, ask Nova Post to enable cash on delivery to a bank account for your company.
  • “Nova Post does not allow inspecting the parcel before payment on your account…” — the service is enabled by contract with Nova Post. Until then, turn off The customer may inspect the parcel before paying.
  • “Nova Post does not accept the recipient details…” or “…the parcel details…” — the message says which fields to check in the shipment window.
  • “It is not certain whether the shipment was created at Nova Post…” — the connection dropped right during the request. Press Check again on the order's Nova Post card and don't create it a second time.