This guide covers Qliro-specific configuration when connecting Qliro to Specter via Junipeer. Before reading this, make sure you have worked through the universal PSP setup guide — it covers all the foundational steps that apply to every payment provider integration:
[Connecting payment services to Junipeer →](/guides/payment-services-101)
The steps in that guide (flow selection, credentials, OSS mapping, settlement account mapping, webhook activation) all apply here. This article only documents what is specific to Qliro and Specter.
Credentials
To connect Qliro to Junipeer, you need your Qliro API credentials. Contact your Qliro account manager to obtain these if you don't already have them.
Qliro-specific settings
The following settings are available in the Qliro connector configuration and are specific to this integration. Both are optional.
Fee article number in Specter
This is the SKU used to identify a fee row in Specter when Qliro includes a fee in the transaction.
If Qliro charges a fee (e.g. a payment processing fee), Junipeer needs to know which Specter article number to use when creating the corresponding row
Leave this field empty if you have enabled Always Credit Fee or Always Capture Fee in Qliro — in those cases the fee is handled entirely on the Qliro side and does not need a Specter article
Also leave it empty if you always want to manage the fee directly in Qliro without it appearing as a line in Specter
If you are unsure whether to fill this in, check with your Qliro account manager whether fees will appear as line items in the settlement data Qliro sends to Junipeer.
Payment Reference Prefix
If set, this prefix will be added to all payment references sent from Junipeer to Specter.
For example, if your prefix is QLIRO-, a payment reference of 12345 will appear in Specter as QLIRO-12345.
This is useful when you have multiple payment providers connected to the same Specter account and want to distinguish Qliro transactions at a glance. Leave it empty if you do not need this distinction.
Refunds
Creating credit invoices (refunds) in Specter via Qliro requires Qliro API Plus credentials — standard API credentials are not sufficient for this operation.
If refunds are failing or credit invoices are not being created, the first thing to check is whether your API Plus credentials are correctly configured. In Junipeer, navigate to your Qliro connector settings and review the keys under PLUS settings.
If you do not have API Plus credentials, contact your Qliro account manager to get them enabled on your account.
Updating order status
For Junipeer to update the order status in Qliro (e.g. marking an order as shipped), Qliro must be configured as a payment method in Specter — not a generic payment type like fak (Faktura).
This is a common misconfiguration. If Qliro is not set up as its own payment method in Specter, Junipeer cannot send status updates back to Qliro's Merchant Center. The order will be processed and invoiced correctly in Specter, but Qliro will show the order as "Ej skickad" (not shipped) indefinitely — because the status update signal never reaches Qliro.
Symptom: Order is marked as "levererad och fakturerad" in Specter but remains "Ej skickad" in Qliro Merchant Center.
Cause: The payment method in Specter is set to fak or another generic value instead of Qliro.
Fix: In Specter, ensure that Qliro is configured as a dedicated payment method. Once corrected, re-trigger the status update from Junipeer.
Go-live
As with all PSP integrations, Qliro goes live through webhook activation, not the Start syncing button. Once your configuration is complete, contact your Junipeer onboarding contact to review the setup and activate the webhooks.
For troubleshooting, see the Error Codes reference or contact support@junipeer.io.