Bancontact Payconiq Company (BPC) Bancontact Payconiq Payments API
PaymentsPayment ProcessingBearer Token4 EndpointsREST
For Agents
Create mobile payments with QR codes, retrieve payment status, search transaction history, and cancel pending payments for omnichannel commerce in the Benelux market.
Use for: Create a mobile payment for an online checkout flow, Generate a QR code for in-store payment at a retail terminal, Check the status of a pending payment transaction, Search for all successful payments in the last 30 days
Not supported: Does not handle refunds, chargebacks, or direct bank account management - use for payment initiation and status tracking only. Limited to EUR currency and Benelux market.
Real-time mobile payment API for creating, retrieving, and cancelling QR code-based transactions across Belgium and the Benelux region. Payconiq enables account-to-account payments through dynamic and static QR codes for in-store, online, and invoice payment scenarios. The platform handles payment authorization, status tracking, and asynchronous callbacks with JWS signature verification.
Install Jentic One Beta
Connect the Bancontact Payconiq Payments API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bancontact Payconiq Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpayconiq.com%2Fpayconiq" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpayconiq.com%2Fpayconiq" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Bancontact Payconiq Payments API.
Create dynamic QR code payments for online and in-store transactions
Generate static POS-linked QR payments for retail terminals
Retrieve real-time payment status and transaction details
Search payment history with date range and status filters
Cancel pending or identified payments before authorization
Receive asynchronous payment status callbacks with JWS signatures
Support both customer-scanned and merchant-displayed QR flows
Use Cases
Patterns agents use Bancontact Payconiq Payments API for, with concrete tasks.
★ E-Commerce Mobile Checkout
Accept mobile payments during online checkout by generating unique QR codes for each transaction. Customers scan the code with their Payconiq app and authorize payment via PIN, fingerprint, or face recognition. The API supports deep linking for app-to-app flows on mobile devices, enabling seamless payment without QR scanning. Callbacks notify your backend immediately when payment status changes from PENDING to SUCCEEDED.
Create a payment for 2500 cents (€25) with description 'Order #12345', set callback URL to receive status updates, and return the QR code URL for display on checkout page
Retail Point-of-Sale Integration
Enable contactless mobile payments at physical retail locations using dynamic or static QR codes. Dynamic QR codes are displayed on customer-facing screens or POS terminals for each transaction. Static QR stickers are printed and placed at checkout counters, with the payment amount entered at the POS terminal. Both flows support instant payment confirmation and work with existing retail systems through webhook callbacks.
Create a POS payment for 1250 cents (€12.50) linked to POS terminal ID 'STORE-01-TILL-03', retrieve the static QR code URL, and subscribe to payment status callbacks for immediate confirmation
Invoice and Billing Payments
Embed mobile payment functionality into invoices and billing systems. Generate unique QR codes for each invoice that customers can scan to pay instantly from their mobile banking app. The API tracks payment status and provides debtor IBAN details for refund processing. Bulk payment aggregation is available through Buckaroo integration for merchants processing high transaction volumes.
Create a payment for invoice INV-2024-0789 with amount 5000 cents (€50), description 'Invoice payment', merchant reference 'INV-2024-0789', and configure callback to mark invoice as paid when status reaches SUCCEEDED
Payment Status Monitoring and Reconciliation
Track payment lifecycle from creation through completion using status polling and webhook callbacks. Search payment history by date range, status, or merchant reference for reconciliation and reporting. The API provides detailed payment objects with debtor and creditor information, timestamps, and hypermedia links for related actions. Useful for financial reporting, dispute resolution, and customer support workflows.
Search all payments from the last 7 days with status SUCCEEDED, retrieve debtor IBANs for reconciliation, and generate a CSV report of completed transactions grouped by merchant reference
AI Agent Payment Orchestration
Automate payment creation, status tracking, and cancellation workflows through AI agents using Jentic. Agents can dynamically generate payment requests based on order context, monitor payment completion, handle abandoned transactions, and trigger refunds. Jentic handles credential isolation, schema discovery, and callback signature verification, enabling agents to integrate Payconiq without manual API documentation lookup.
Use Jentic to search for 'create a mobile payment', load the Payconiq payment creation schema, and execute a request for a 3500 cent (€35) transaction with automatic status polling and callback handling
Key Endpoints
4 endpoints — real-time mobile payment api for creating, retrieving, and cancelling qr code-based transactions across belgium and the benelux region.
METHOD
PATH
DESCRIPTION
POST
/payments
Create a new payment transaction
POST
/payments/pos
Create a POS-linked static QR payment
GET
/payments/{paymentId}
Retrieve payment status and details
DELETE
/payments/{paymentId}
Cancel a pending payment
POST
/payments/search
Search payments with filters and pagination
POST
/payments
Create a new payment transaction
POST
/payments/pos
Create a POS-linked static QR payment
GET
/payments/{paymentId}
Retrieve payment status and details
DELETE
/payments/{paymentId}
Cancel a pending payment
POST
/payments/search
Search payments with filters and pagination
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Payconiq by hand means handling its bearer auth, choosing the right production or external host, and driving payment initiation and status tracking yourself. Through Jentic you install once, import the Bancontact Payconiq Payments API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Payconiq puts the payment id in the URL path (/payments/{paymentId}), so a rule can pin your agent to reading one payment: it can fetch that payment's status and nothing else. You choose the operations it may call, so creating or cancelling payments is not included unless you add them.
Credential isolation
Your Payconiq API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a mobile payment' or 'check a payment status', and Jentic returns the matching Payconiq operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe offers global payment processing with card, wallet, and bank transfer support across 135+ currencies
Choose Stripe for global multi-currency payments and comprehensive payment method support. Use Payconiq for Benelux-focused mobile QR code payments with real-time bank transfers.
FAQs
Specific to using Bancontact Payconiq Payments API through Jentic.
What authentication does the Payconiq API use?
The Payconiq API uses Bearer token authentication. Include your API key in the Authorization header as 'Bearer YOUR_API_KEY'. All requests are encrypted using TLS 1.2 or 1.3. Jentic stores Payconiq API keys encrypted in the credential vault and provides scoped access tokens to agents, so raw keys never appear in agent context. Get started with Jentic One, the self-hosted execution layer.
What currencies and markets does Payconiq support?
Payconiq currently supports EUR currency only and operates primarily in the Benelux region (Belgium, Netherlands, Luxembourg). The platform is part of the European Payments Initiative working toward broader European coverage through the wero payment solution.
How do payment callbacks work in the Payconiq API?
When creating a payment, specify a callbackUrl (HTTPS endpoint) in your request. Payconiq sends asynchronous POST notifications to this URL whenever payment status changes (e.g., PENDING to SUCCEEDED). Callbacks include JWS (JSON Web Signature) headers for verification. You should validate signatures and respond with 2xx status codes to acknowledge receipt.
What are the payment amount limits in Payconiq?
The API accepts amounts from 1 to 999999 Euro cents (€0.01 to €9,999.99). For testing in the external environment, amounts up to €100 succeed normally, while amounts above €100 trigger test failure scenarios to simulate error handling.
Can I cancel a payment after it's been created?
Yes, use the DELETE /payments/{paymentId} endpoint to cancel payments in PENDING or IDENTIFIED status. Once a payment reaches AUTHORIZED or SUCCEEDED status, it cannot be cancelled through this endpoint. Refunds must be handled separately by retrieving debtor IBAN information from the payment details.
What is the difference between dynamic and static QR payments?
Dynamic QR payments (POST /payments) generate a unique QR code for each transaction with a specific amount. Static QR payments (POST /payments/pos) are linked to a physical POS terminal or sticker, allowing customers to scan the same QR code repeatedly while the merchant enters the amount at the terminal. Static QR codes are ideal for retail counters and fixed checkout locations.
How long do Payconiq payments remain valid?
Payments expire after 2 minutes (120 seconds) if not completed. After expiration, the payment status changes to EXPIRED and customers can no longer authorize it. Merchants must create a new payment for the customer to try again.
How do AI agents use the Payconiq API through Jentic?
Agents search Jentic for intents like 'create a mobile payment' or 'generate a QR code payment'. Jentic returns the relevant Payconiq API operations (e.g., POST /payments) with their input schemas. The agent calls the operation via Jentic's execution layer, which handles authentication, request formatting, and callback verification. Integration time drops from days to minutes. Get started with Jentic One, the self-hosted execution layer.
GET STARTED