Skip to main content

Integrations and API

QrX supports merchants and platforms that want to automate Payment On Delivery through API and webhook integrations. Integrations can create payment-enabled orders, receive status changes, and connect QrX payment confirmation to delivery an

H
Written by Hayko

Integrations and API

QrX connects your store to payment providers and delivery networks through one shared layer. You can connect through a ready-made platform integration or build directly on the QrX API. Both bring your business into the same QrX payment and delivery flow, and you do not need to replace your existing store.

Available Integrations

The integrations directory on qrx.eu/integrations currently lists:

  • Shopify (commerce): the QrX Shopify app brings your Shopify orders, payment status and delivery information into the same workflow, and marks orders paid when the customer pays at the door. See the article "QrX for Shopify".

  • Stripe (payments): Stripe processes the payment through your own Stripe account. QrX coordinates the payment request and confirmation with the delivery journey.

  • MultiSafepay (payments): use MultiSafepay for payment processing while QrX connects the payment state to delivery.

  • UPS (delivery): QrX is the official UPS Payment on Delivery partner in Europe and can create UPS labels. See the article "UPS Payment on Delivery with QrX".

Mollie is also an integrated payment provider for QrX Payment on Delivery. Available payment methods, countries and carrier services always depend on your provider account, destination markets and QrX configuration. If your platform, PSP, carrier or locker network is not listed, request it through the integrations page or book a demo.

Building With the QrX Public API

  • Style: REST with JSON, base URL https://api.qr-x.net, OpenAPI specification available.

  • Authentication: create an API key per sales channel in PortalX under Settings, Merchant channels. Exchange it for a short-lived Bearer token with POST /api/v1/auth/token (valid for one hour).

  • Transactions: create a Payment on Delivery transaction, get its details or payment status, mark it shipped with tracking details, or cancel it.

  • Reference data: look up carriers, countries, locales, shipping methods and sender addresses.

  • Products and returns: manage your product catalog and handle return requests.

  • Warehouse stock: read stock levels, stock items and locations, book a stock correction, and receive the events stock/adjusted and stock/low. See "Stock and Warehouse API" and "Stock and Warehouse Webhooks".

  • Webhooks: subscribe to events, verify signed deliveries, inspect the delivery log, redeliver and rotate signing secrets.

  • Test mode: create transactions with testMode: true to test the full flow without real payments or payouts.

  • QrX Connect (OAuth): platforms such as apps, WMS systems or custom shops can let a merchant link a QrX channel without pasting an API key.

The full, always up-to-date reference with code samples (cURL, Node.js, C#, PHP, Python) and a ready-made Postman collection is at qrx.eu/api. Start with the article "Developer quickstart: QrX public API and webhooks".

Webhook Reliability

Webhooks are the source of truth for the final transaction state, because payment processing can complete or fail after your create request has returned. Webhook subscriptions in PortalX show a health status. If an endpoint keeps failing, QrX warns the configured recipients by email and automatically disables the subscription after roughly 24 hours of continuous failure, so it can be fixed and re-enabled. Every webhook has a delivery log showing each attempt, the request and response, and retries.

Merchant Channels

A merchant can run several sales channels in QrX. Each API key belongs to one channel, and everything created with it (transactions, labels, webhooks) stays connected to that channel. Use a separate key per channel.

Support for Developers

When contacting support about an API or webhook issue, include the request time, environment (test or live), merchant channel, order reference, transaction id, webhook delivery id, response status and a sanitized request or response body. Never send API keys, access tokens or webhook secrets in chat or email. See also "API and Webhook Troubleshooting".

Related Articles
Did this answer your question?