Payconiq Bridge

This guide explains the payment flows available during the migration from Payconiq Luxembourg to Wero: Static QR, Invoice QR and e-commerce.

Static QR

Static QR codes let customers scan the same code each time they make a payment. They are typically used at physical merchant locations, for example on printed QR stickers or point-of-sale displays.

Go to Static QR documentation

Invoice QR

Add a Wero QR code to an invoice, payment request or other offline communication. Customers scan the code with a Wero-compatible wallet to complete their payment.

Go to Invoice QR documentation

Ecom

Buckaroo’s e-commerce flow remains fully compatible with the existing Payconiq v3 API. Your integration can continue to send the same API requests, which Buckaroo automatically converts into Wero payments.
No changes are required to your integration. Buckaroo will take care of migrating everything, including your API keys and webhook configuration.

Test your integration

We recommend testing your integration in the sandbox before the migration. You can use the existing v3 create-payment API to test different payment outcomes by setting the payment amount as follows:

Make sure that you are using the EXT payconiq URL for testing your integration.

Use these scenarios to check how your integration handles each payment status and its webhook notifications. Any other amount uses the Wero simulator’s default behaviour.

These amounts trigger simulated outcomes only in the sandbox. In production, they are processed as normal payment amounts.