Billink

Introductie

API Versies

Billink Status

<p class="slate-p " >On this page you’ll find relevant updates to the Billink platform: from new features and improvements in Billink One to important bug fixes, API changes, and new PSP integrations. This way, you’ll always stay up to date on what’s changing and how it improves your checkout, integration, or customer experience.</p><p class="slate-p " ></p>

Billink Changelog

Release v2026.2 - 4 maart, 2026

Release v2026.1 - 20 januari 2026

<h3 class="slate-h3 " >Project features</h3><h4 class="slate-h4 " ><strong class="slate-bold">Billink One Optimization</strong></h4><p class="slate-p " >During the release, we test different variants via A/B testing to continuously optimize both
conversion and customer experience.</p><h4 class="slate-h4 " ><strong class="slate-bold">Features</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Billink One interface optimized with new labels and an improved form structure.</div></li><li class="slate-li " ><div style="position:relative">VAT information and payment options are presented more clearly and consistently
in Billink One.</div></li></ul><h4 class="slate-h4 " ><strong class="slate-bold">Hotfixes</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Mobile apps updated for consistent labeling and automatic selection of relevant
payment options.</div></li></ul><h4 class="slate-h4 " ><strong class="slate-bold">Bug Fixes</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Webhooks and API integrations stabilized for reliable data transfer.</div></li><li class="slate-li " ><div style="position:relative">Pop-ups and notifications trigger correctly and appear at the right time.</div></li><li class="slate-li " ><div style="position:relative">Corrections applied to calculations and page updates, including iDIN verification
and full crediting.</div></li></ul><p class="slate-p " ></p>

Release 66 - November 11, 2025

<h3 class="slate-h3 " >Project features</h3><h4 class="slate-h4 " ><strong class="slate-bold">Mobile App Improvements</strong></h4><p class="slate-p " >Previously, it was not possible for a consumer to directly pay an overdue order that had not been paid on time. From now on, this can be done directly in the app.</p><h4 class="slate-h4 " ><strong class="slate-bold">Billink One Optimization</strong></h4><p class="slate-p " >During this release, we are running several A/B tests to maintain optimal conversion rates
and continue improving the customer experience.</p><h4 class="slate-h4 " ><strong class="slate-bold">HPP Device Fingerprint v0</strong></h4><p class="slate-p " >On Billink One each device receives a unique identifier for improved fraud detection.</p><h4 class="slate-h4 " ><strong class="slate-bold">Features</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Down payment details are now shown in customer notifications.</div></li><li class="slate-li " ><div style="position:relative">General fixes and stability improvements.</div></li><li class="slate-li " ><div style="position:relative">Customers now receive emails for partial credits.</div></li><li class="slate-li " ><div style="position:relative">Developer Portal expanded with Billink One branding.</div></li><li class="slate-li " ><div style="position:relative">Ability to download PDF invoices for orders.</div></li><li class="slate-li " ><div style="position:relative">Improved reliability of settings and success notifications.</div></li><li class="slate-li " ><div style="position:relative">Invoice improvements: outstanding invoices now include pagination for better
clarity.</div></li></ul><h4 class="slate-h4 " ><strong class="slate-bold">Maintenance</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Optimizations in customer settings.</div></li><li class="slate-li " ><div style="position:relative">Extended webhook support.</div></li><li class="slate-li " ><div style="position:relative">Database performance optimizations.</div></li></ul><h4 class="slate-h4 " ><strong class="slate-bold">Bug Fixes</strong></h4><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Various improvements to login processes, translations, and interface display. </div></li><li class="slate-li " ><div style="position:relative">Improved email communication and correction of error messages in payment
flows.</div></li></ul><p class="slate-p " ></p>

Release 64 – 7 oktober, 2025

<h3 class="slate-h3 " >Project features</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">HPP – Downpayments v1: </strong>The logic around downpayments has been further refined. The option is only shown when legally and commercially appropriate.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Rebrand Mobile apps v0:</strong> Our mobile apps have been redesigned to align with Billink’s new branding. A more modern look, improved readability, simpler navigation, and a dark mode for ease of use.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Multi-email accounts (app):</strong> Users can now link multiple email addresses to a single Billink account. This allows consumers to view multiple orders if they use different email addresses.
</div></li></ul><h3 class="slate-h3 " >
Features</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Added Session Cancel status → provides merchants and customers with more clarity when a session is terminated.</div></li><li class="slate-li " ><div style="position:relative">New fields in the downpayment option → better insight into payment options and decision-making logic.</div></li><li class="slate-li " ><div style="position:relative">New payment method selector and improved Next button in Billink One → fewer clicks, faster checkout.</div></li><li class="slate-li " ><div style="position:relative">Invoice numbers added to payment descriptions.</div></li><li class="slate-li " ><div style="position:relative">Affiliate program terms linked in the system → direct visibility for merchants.</div></li><li class="slate-li " ><div style="position:relative">Webhook examples added in developer documentation → easier testing and faster integration.</div></li><li class="slate-li " ><div style="position:relative">Documentation updated with new branding → more consistent developer experience.</div></li></ul><h3 class="slate-h3 " >
Mid release deployments (Hotfixes)</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Extended documentation for webhooks (session/order info).</div></li><li class="slate-li " ><div style="position:relative">Bank option removed from iDEAL in mijn.billink.nl for a clearer payment experience for customers.</div></li></ul><h3 class="slate-h3 " >
Bug fixes</h3><p class="slate-p " >We resolved a large number of issues to improve stability and reliability. Key fixes include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Order amounts and birthdates now displayed correctly in portals.</div></li><li class="slate-li " ><div style="position:relative">Various fixes in Customer Portal (login, order overview, payroll tables).</div></li><li class="slate-li " ><div style="position:relative">Improved error handling in forms and dispute flows → fewer blockers for merchants.</div></li><li class="slate-li " ><div style="position:relative">Minor UI and UX fixes in portals (icons, translations, layouts).</div></li><li class="slate-li " ><div style="position:relative">Billink One logo added to developer portal → better recognition and consistency.</div></li></ul><h3 class="slate-h3 " >
Maintenance</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Improved dialogs and prompts in portals for clearer merchant interaction.</div></li><li class="slate-li " ><div style="position:relative">Branding and minor text changes implemented across portals and affiliate pages.</div></li></ul><p class="slate-p " ></p>

Release 62 – augustus 26, 2025

Actuele API (v2)

Partners Exclusief

Merchant Create

Betaling autoriseren

You can integrate Billink with or without a midpage. To integrate Billink with a midpage, you need to follow these steps.

Create Session

The Status API can be used to check whether an order has been paid or not. This API is optional.

Session Status

Orderbeheer

The Start Workflow API can initiate orders as soon as they are delivered. By default, an automatic start delay of 3 days is set. If you wish to use this API, you need to extend the start delay. This can easily be adjusted by yourself at app.billink.nl/settings behind the workflow.

Attention!
This API can be used 1 minute after the order is shot.

Start Workflow

With the Credit API, a product or amount can be credited on the invoice. This API is optional.

Credit

Create Tracker

Update Tracker

With the Payment API, a payment can be booked on the invoice. This API can be useful if consumers regularly transfer amounts to the webshop. This API is optional.

Payment

The On Hold API allows invoices to be put on hold for two weeks. This API is optional.

On Hold

The Resume API allows invoices to be resumed from hold. This API is optional.

Resume Order

With the Order Info API, it can be requested whether an order has been paid or not and in which step the order is located. This API is optional.

Order Info

With the Message API, messages can be posted on an order. These messages can be found in the backend of Billink by our customer service. This API is optional.

Message

<div class="slate-div"><span style="color:rgb(14, 14, 14)">The </span><span style="color:rgb(14, 14, 14)"><strong class="slate-bold">Dispute</strong></span><span style="color:rgb(14, 14, 14)"> section provides the basic functionality required to work with disputes. It allows you to retrieve the available dispute categories and to create a new dispute for a transaction when needed.</span></div><p class="slate-p " ></p><p class="slate-p " ></p>

Dispute

<p class="slate-p " >The <strong class="slate-bold">Dispute</strong> <strong class="slate-bold">Categories</strong> endpoint allows to get a list of all available dispute categories and their ids.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Dispute Categories

<p class="slate-p " >The Dispute API section allows users to create merchant disputes and manage the resolution process. With this functionality, users can handle dispute-related information, track the status of disputes, and communicate with relevant parties effectively.</p><p class="slate-p " ></p>

Dispute Create

Reconciliatie

<p class="slate-p " >Retrieves a paginated list of invoices for a given Billink client. Supports optional filtering by date range and returns invoice amounts, numbers, and related reconciliation identifiers.</p><p class="slate-p " >All available errors for this endpoint you can find in <a href="686e4450c8cadee8e237e842/686fdf404787c008b59240f4" target="_blank">errors</a> section.</p>

Invoices

<p class="slate-p " >This endpoint allows clients to download all available invoice documents as a ZIP archive. It requires a valid Billink client identifier, username, invoice year, and invoice number. </p><p class="slate-p " >On success, it returns a 200 status code with application/zip content type, triggering a ZIP file download.</p><p class="slate-p " >All available errors for this endpoint you can find in <a href="686e4450c8cadee8e237e842/6870d6a61f2cfd622c691efd" target="_blank">errors</a> section.</p>

Invoice Download

<p class="slate-p " >The <strong class="slate-bold">Webhooks section</strong> provides endpoints for configuring and managing webhook integrations. These endpoints allow users and merchants to receive real-time notifications related to sessions and order events by setting or disabling webhook URLs. This enables seamless communication between Billink and external systems, allowing for automation, event-driven workflows, and improved operational efficiency.</p><p class="slate-p " ></p>

Webhooks

<p class="slate-p " >The <strong class="slate-bold">Session Webhook</strong> notifies your system whenever a payment session changes its state.</p><p class="slate-p " >This enables your platform to react in real time — for example, when a session becomes active, fails or expires.</p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >You can also read how to set or disable the Session Webhook: <a href="68e8e4bcb98d1b6279be8a79/68e8e4bcb98d1b6279be93bf" target="">Session Webhook Set</a> | <a href="68e8e4bcb98d1b6279be8a79/68e8e4bcb98d1b6279be901f" target="">Session Webhook Disable</a></p></div></div><p class="slate-p " ></p><h3 class="slate-h3 " >When it&apos;s triggered</h3><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:246px;">Title</div><div style="width:0px;">Description</div><div style="width:400px;">Title</div></div><colgroup ><col style="width:246px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Status</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Description</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Typical Use Case</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >session_active</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The session was successfully initialized and is currently active.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The session has started and the customer interracts with payment flow.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >cancelled</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The customer cancelled the session manually or closed the checkout.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Stop tracking the session and mark it as cancelled.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >failed</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The session failed due to a technical or validation error (e.g. payment method unavailable, invalid data).</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Display a failure message or log the error for retry.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >session_expired</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The session expired automatically after a timeout (1 hour) without completing checkout.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark session as expired and cancel related pending processes.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_created</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Checkout was successfully completed and an order has been created.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Confirm the order and trigger fulfillment in your system.</p></td></div></tr></tbody></table></div></div><p class="slate-p " ></p><h3 class="slate-h3 " >Example Payloads</h3><p class="slate-p " >Each webhook uses the same payload structure. Only the status field changes to indicate the current session state.</p><p class="slate-p " ><strong class="slate-bold">Payload Parameters:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">status — current session status</div></li><li class="slate-li " ><div style="position:relative">invoiceNumber — internal invoice number</div></li><li class="slate-li " ><div style="position:relative">transactionId — unique transaction identifier</div></li><li class="slate-li " ><div style="position:relative">billinkInvoiceNumber — public invoice number, generated by <strong class="slate-bold">Billink</strong> based on invoiceNumber</div></li></ul><div class="slate-code_line"></div><h4 class="slate-h4 " >Example: session_active</h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;status&quot;: &quot;session_active&quot;,
  &quot;invoiceNumber&quot;: &quot;invoice-1234&quot;,
  &quot;transactionId&quot;: &quot;tx_001a45&quot;,
  &quot;billinkInvoiceNumber&quot;: &quot;1ABinvoice-1234&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><h4 class="slate-h4 " >Example: cancelled</h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;status&quot;: &quot;cancelled&quot;,
  &quot;invoiceNumber&quot;: &quot;invoice-1234&quot;,
  &quot;transactionId&quot;: &quot;tx_001a45&quot;,
  &quot;billinkInvoiceNumber&quot;: &quot;1ABinvoice-1234&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><h4 class="slate-h4 " >Example: failed</h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;status&quot;: &quot;failed&quot;,
  &quot;invoiceNumber&quot;: &quot;invoice-1234&quot;,
  &quot;transactionId&quot;: &quot;tx_001a45&quot;,
  &quot;billinkInvoiceNumber&quot;: &quot;1ABinvoice-1234&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><h4 class="slate-h4 " >Example: session_expired</h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;status&quot;: &quot;session_expired&quot;,
  &quot;invoiceNumber&quot;: &quot;invoice-1234&quot;,
  &quot;transactionId&quot;: &quot;tx_001a45&quot;,
  &quot;billinkInvoiceNumber&quot;: &quot;1ABinvoice-1234&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><h4 class="slate-h4 " >Example: order_created</h4><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;status&quot;: &quot;order_created&quot;,
  &quot;invoiceNumber&quot;: &quot;invoice-1234&quot;,
  &quot;transactionId&quot;: &quot;tx_001a45&quot;,
  &quot;billinkInvoiceNumber&quot;: &quot;1ABinvoice-1234&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Delivery and Retries</strong></h2><p class="slate-p " >When a webhook is triggered, Billink sends an HTTPS POST request to your configured webhook URL with the corresponding event payload.</p><p class="slate-p " >If your endpoint <strong class="slate-bold">does respond with HTTP 200-299</strong>, the system will automatically retry delivery <strong class="slate-bold">up to three times</strong>:</p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Attempt</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Delay before retry</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1st retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 5 seconds</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2nd retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 10 seconds</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >3rd retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 15 seconds</p></td></div></tr></tbody></table></div></div><p class="slate-p " >After three failed attempts, the webhook is considered <strong class="slate-bold">undeliverable</strong>, and no further retries will be made.</p><p class="slate-p " >To ensure successful delivery:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Always respond with <strong class="slate-bold">HTTP 200 OK</strong> as soon as your system receives the webhook.</div></li><li class="slate-li " ><div style="position:relative">Handle processing asynchronously to avoid timeouts.</div></li><li class="slate-li " ><div style="position:relative">Log all incoming webhook attempts for debugging and reconciliation.</div></li></ul><p class="slate-p " ></p>

Session Webhook

<p class="slate-p " >This endpoint enables a merchant to configure a webhook URL for receiving real-time notifications related to user sessions. By providing the Billink username, ID, and the desired webhook URL, merchants can seamlessly integrate session updates into their systems and ensure timely, automated handling of relevant events.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Session Webhook Instellen

<p class="slate-p " >This endpoint allows a merchant to disable a previously configured session webhook. Once the Billink username and ID are provided, the associated webhook will be removed, stopping any further session-related notifications from being sent to that URL.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Session Webhook Uitschakelen

<p class="slate-p " >The <strong class="slate-bold">Order Webhook</strong> notifies your system about important events in the order lifecycle.</p><p class="slate-p " >This allows your platform to react in real time — for example, when an order is placed, partially paid, fully paid, credited, or put on hold.</p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >You can also read how to set or disable the <strong class="slate-bold">Order Webhook</strong>: <a href="68e8e4bcb98d1b6279be8a79/68e8e4bcb98d1b6279be902b" target="">Order Webhook Set</a> |<strong class="slate-bold"> </strong><a href="68e8e4bcb98d1b6279be8a79/68e8e4bcb98d1b6279be9038" target="">Order Webhook Disable</a></p></div></div><p class="slate-p " ></p><h3 class="slate-h3 " >When it’s triggered</h3><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:325px;">Title</div><div style="width:0px;">Description</div><div style="width:400px;">Title</div></div><colgroup ><col style="width:325px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Event</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Description</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Typical Use Case</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_placed</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Customer successfully placed an order.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark order as created.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_workflow_started</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The order entered internal processing workflow.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Order can be shown as started.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >partial_payment_added</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >A partial payment for the order was received.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Get the new order details to adjust the outstanding amount.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_paid</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The order has been fully paid.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark order as paused.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >partial_credit_added</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >A partial credit or refund was applied to the order.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Get the new order details to adjust the outstanding amount.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_fully_accredited</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >A full credit or refund was applied to the order.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark order as fully accredited in system.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >customer_fully_paid</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The customer has cleared all outstanding balances.</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark order as paid.</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >order_on_hold</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >The order is temporarily on hold (e.g. pending review, dispute process).</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >Mark order as paused.</p></td></div></tr></tbody></table></div></div><h3 class="slate-h3 " >Example Payloads</h3><p class="slate-p " >Each event sends a webhook payload with the same structure. Only the event parameter changes to indicate the current order state.</p><p class="slate-p " ><strong class="slate-bold">Payload Parameters:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">order_id — unique id of the <strong class="slate-bold">Billink</strong> order</div></li><li class="slate-li " ><div style="position:relative">invoice_number_clean - internal invoice number</div></li><li class="slate-li " ><div style="position:relative">invoice_number - public invoice number, generated by <strong class="slate-bold">Billink</strong> based on invoice_number_clean</div></li><li class="slate-li " ><div style="position:relative">workflow_id - unique id assigned to the order workflow</div></li><li class="slate-li " ><div style="position:relative">event - state of the order, which triggered the webhook</div></li><li class="slate-li " ><div style="position:relative">timestamp - the exact date and time when the webhook was triggered (<strong class="slate-bold">Y-m-d H:i:s</strong> format). Time zone: Amsterdam, Netherlands (GMT+2)</div></li><li class="slate-li " ><div style="position:relative">custom_invoice_id (<strong class="slate-bold">Might not be always presented</strong>) - will be shown if it&apos;s exists in Billink Session.</div></li></ul><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: order_placed</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;order_placed&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: partial_payment_added</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;partial_payment_added&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: order_paid</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;order_paid&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: partial_credit_added</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;partial_credit_added&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: order_fully_accredited</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;order_fully_accredited&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: customer_fully_paid</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;customer_fully_paid&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: order_workflow_started</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;order_workflow_started&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><p class="slate-p " ><strong class="slate-bold">Example: order_on_hold</strong></p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;order_id&quot;: &quot;123456&quot;,
  &quot;invoice_number&quot;: &quot;1ABINVOICE1234&quot;,
  &quot;invoice_number_clean&quot;: &quot;INVOICE1234&quot;,
  &quot;workflow_id&quot;: &quot;123&quot;,
  &quot;event&quot;: &quot;order_on_hold&quot;,
  &quot;timestamp&quot;: &quot;2025-10-10 09:45:00&quot;,  
  &quot;custom_invoice_id&quot;: &quot;1TST-CUSTOM-INVOICE-12345&quot; //if presented
}</div></div></code></pre></div><p class="slate-p " ></p><h2 class="slate-h2 " ><strong class="slate-bold">Delivery and Retries</strong></h2><p class="slate-p " >When a webhook is triggered, <strong class="slate-bold">Billink</strong> sends an HTTPS POST request to your configured webhook URL with the corresponding event payload.</p><p class="slate-p " >If your endpoint <strong class="slate-bold">does respond with HTTP 200-299</strong>, the system will automatically retry delivery <strong class="slate-bold">up to three times</strong>:</p><div class="published-table"><div class="table-container" style="padding-left: 0px;"><table class="slate-table" style="min-width:100%;"><div class="published-table-header" style="width:100%;min-width:100%;min-height:initial;visibility: hidden;border:initial"><div style="width:100px;">Title</div><div style="width:100px;">Description</div></div><colgroup ><col style="width:initial"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Attempt</strong></p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " ><strong class="slate-bold">Delay before retry</strong></p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >1st retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 5 seconds</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >2nd retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 10 seconds</p></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >3rd retry</p></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><p class="slate-p " >after 15 seconds</p></td></div></tr></tbody></table></div></div><p class="slate-p " >After three failed attempts, the webhook is considered <strong class="slate-bold">undeliverable</strong>, and no further retries will be made.</p><p class="slate-p " >To ensure successful delivery:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Always respond with <strong class="slate-bold">HTTP 200 OK</strong> as soon as your system receives the webhook.</div></li><li class="slate-li " ><div style="position:relative">Handle processing asynchronously to avoid timeouts.</div></li><li class="slate-li " ><div style="position:relative">Log all incoming webhook attempts for debugging and reconciliation.</div></li></ul><p class="slate-p " ></p>

Order Webhook

<p class="slate-p " >This endpoint allows a user to set or update a webhook URL for receiving real-time order-related events. By providing the Billink username, ID, and the target webhook URL, users can ensure their systems are promptly informed of order updates and can react automatically to changes in order status.</p>

Order Webhook Instellen

<p class="slate-p " >This endpoint allows a user to disable the currently configured order webhook. By providing the Billink username and ID, the system will remove the associated webhook URL if it exists. A success message will be returned upon successful removal. If no webhook is configured, the response will indicate that there is nothing to disable.</p><p class="slate-p " ></p>

Order Webhook Uitschakelen

<p class="slate-p " >In <strong class="slate-bold">Billink API</strong>, error responses follow a consistent format. All errors are returned with an <strong class="slate-bold">HTTP</strong> status code <span style="color:#00FF00">200</span>, which indicates the request was processed but there was an issue with the operation. </p><p class="slate-p " >The format of the error is as follows:</p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line"><div class="slate-code_line">{
  &quot;code&quot;: &quot;000&quot;,
  &quot;description&quot;: &quot;Error message&quot;,
  &quot;result&quot;: &quot;error&quot;
}</div></div></code></pre></div><p class="slate-p " ></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Code</strong>: A unique error code representing the specific issue.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Description:</strong> A detailed description of the error.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Result: </strong>Short informative status</div></li></ul><p class="slate-p " >These errors might indicate a variety of issues including but not limited to problems with API versioning, client authentication, missing or incorrect parameters, data format issues, and restrictions on actions (such as workflow limitations or invalid operations).</p><h3 class="slate-h3 " >Common Issues:</h3><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Client Identification</strong>: Errors related to missing or incorrect client username, client id, or API version.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Invoice and Workflow Management</strong>: Missing or incorrect invoice numbers or workflow data.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Order Management</strong>: Trying to perform actions on orders that are not allowed or are already processed.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Request Limitations</strong>: Exceeding request limits (e.g., number of invoices, action frequency).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Parameter Validation</strong>: Incorrect or unsupported parameters in requests.</div></li></ol><p class="slate-p " >This helps you to easily handle and debug issues by following the provided error code descriptions across all API endpoints.</p><p class="slate-p " >In the next subsections, you will see errors specific to each endpoint. Each of these subsections includes a list of error codes and their corresponding descriptions to help you understand and resolve issues effectively.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Fouten

<h3 class="slate-h3 " ><strong class="slate-bold">Summary of Client API Error Codes</strong></h3><p class="slate-p " >The Client API error codes mainly address issues related to client identification, parent-child client relationships, and validation of client-related data fields.</p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Unknown or invalid client username or client id.</div></li><li class="slate-li " ><div style="position:relative">Issues with parent client relationships, such as clients being their own parent or invalid parent ids.</div></li><li class="slate-li " ><div style="position:relative">Validation errors for company and personal data fields, including company name, first and last name, IBAN, BIC, contact information, and address details.</div></li><li class="slate-li " ><div style="position:relative">Errors related to uniqueness constraints, like duplicate usernames or emails.</div></li><li class="slate-li " ><div style="position:relative">Missing or invalid platform or reseller information.</div></li></ul><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:474px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:474px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >102</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >103</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Client with username “%message%” is not allowed to access api/create-client</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >104</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown parent client username</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >105</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >The client can’t be it’s own parent</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >106</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >The passed parent client id is not in a reseller clients list</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >401</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid company name. Company name must be between 2 and 100 characters long</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >402</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid first name. First name must be between 2 and 255 characters long</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >403</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid last name. Last name must be between 2 and 255 characters long</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing IBAN</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >405</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Please provide valid iban/bank account number.</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >406</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing BIC number or invalid format. See ISO 9362</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >407</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid city name. City name should contain only letters, spaces, - . and ’ signs</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >408</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid COC number. It should be 8 digits length</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >409</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing contact email or wrong contact email format</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >410</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Incorrect country code</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >411</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid contact phone. Phone number should be between 9-18 characters, it can contain only digits, spaces, ‘+’, ‘()’ and ‘-’ signs</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >412</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing email or wrong email format</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >413</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing house number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >414</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Wrong house number format</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >417</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Could not save logo image</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >418</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid phone number. Phone number should be between 9-18 characters, it can contain only digits, spaces, ‘+’, ‘()’ and ‘-’ signs</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >419</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid postcode</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >420</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid street name. Street name may contain letters, numbers, spaces, - ’ .</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >421</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Bankholder is missing</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >422</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing VAT number or wrong VAT number format</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >423</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing web site URL or invalid URL format. Example format: www.example.com</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >424</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid method. Method should be numeric</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >425</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing or invalid user name. User name must be between 4 and 50 characters long</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >426</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing country code</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >427</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Client with username “%message%” already exists</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >428</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Client with email “%message%” already exists</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >429</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Please provide platform id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >430</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Platform with such id doesn’t exist</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >431</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing parent client username</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >432</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing parent client id</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

Client

<h3 class="slate-h3 " >Summary of Session Status Error Codes</h3><p class="slate-p " >The Session Status error codes primarily address issues related to user input validation, access permissions, session existence, and unexpected server errors.</p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing required form data, such as a blank username field.</div></li><li class="slate-li " ><div style="position:relative">Access denial due to insufficient permissions.</div></li><li class="slate-li " ><div style="position:relative">Sessions that cannot be found or have expired.</div></li><li class="slate-li " ><div style="position:relative">General server errors indicating unexpected failures.</div></li></ul><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:527px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:527px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >The form contains the following errors:  1) billinkUsername: This value should not be blank.</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >403</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Access denied</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Session not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >500</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Something went wrong</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Create Session Submerchant Error Codes</h3><p class="slate-p " >The Create Session Submerchant error codes mainly cover validation issues with client data, access permissions, and general server errors.</p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing required client fields such as billinkUsername, billinkID, and workflowNumber.</div></li><li class="slate-li " ><div style="position:relative">Access denial due to insufficient permissions.</div></li><li class="slate-li " ><div style="position:relative">Client not found errors when billinkID or billinkUsername do not match any records.</div></li><li class="slate-li " ><div style="position:relative">Unexpected server errors causing failure during session creation.</div></li></ul><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:459px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:459px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >The form contains the following errors:  1) client.billinkUsername: This value should not be blank. 2) client.billinkID: This value should not be blank. 3) client.workflowNumber: This value should not be blank.</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >403</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Access denied</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No client found with such billinkID or billinkUsername</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >500</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Something went wrong</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Start Workflow API Error Codes</h3><p class="slate-p " >The <strong class="slate-bold">Start Workflow API</strong> error codes mainly focus on issues related to <strong class="slate-bold">client identification</strong>, <strong class="slate-bold">invoice validation</strong>, <strong class="slate-bold">workflow management</strong>, and <strong class="slate-bold">request limitations</strong>. </p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Unknown details</strong> such as API version, client username, or client id.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Invoice validation issues</strong>, such as missing or unknown invoice numbers.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Workflow errors</strong>, such as trying to start a workflow when it&apos;s already been started or when you&apos;re not authorized to manage the order.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Request limits</strong>, such as exceeding the maximum allowed invoices per request.</div></li></ul><p class="slate-p " >All available error codes and messages for <strong class="slate-bold">Start Workflow API</strong>:</p><p class="slate-p " ><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:434px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:434px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >102</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >103</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown action</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >603</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Redirect Billink API error</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >704</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown invoice number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >705</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No invoices provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >706</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >You are not allowed to manage this order</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >707</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Order workflow is already started</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >708</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Maximum 10 invoices per request allowed</h4></td></div></tr></tbody></table></div></p><p class="slate-p " ></p><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Credit API Error Codes</h3><p class="slate-p " >The error codes for the <strong class="slate-bold">Credit API</strong> focus on <strong class="slate-bold">workflow issues</strong>, <strong class="slate-bold">order validation</strong>, and <strong class="slate-bold">invoice management</strong>. </p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Unknown details</strong> such as API version, client username, or client id.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Workflow errors</strong> related to missing or incorrect workflow numbers.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Order errors</strong> like trying to apply credit to an order that already exists or cannot be managed at the current stage.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Invalid data</strong> for example: missing invoices.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Access control issues</strong>, such as being unable to manage an order or apply credit at a certain stage.</div></li></ul><p class="slate-p " >All available error codes and messages for <strong class="slate-bold">Credit API</strong>:</p><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:446px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:446px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >102</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >103</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown action</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >402</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Workflow with number %number% does not exist</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Order with number %number% already exists</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >603</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Redirect Billink API error</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >705</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No invoices provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >706</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >You are not allowed to manage this order</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >707</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Credit cannot be applied at this stage</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >708</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Credit cannot be applied at this stage(0)</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Payment API Error Codes</h3><p class="slate-p " >The <strong class="slate-bold">Payment API</strong> error codes mainly address issues related to <strong class="slate-bold">client identification</strong>, <strong class="slate-bold">invoice management</strong>, and <strong class="slate-bold">order status</strong>. </p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Unknown details</strong> such as API version, client username, or client id.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Invoice-related errors</strong>, such as missing or unknown invoice numbers.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Order management issues</strong>, including trying to manage an order you are not authorized to manage or attempting to pay an order that&apos;s already paid.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Description length errors</strong>, such as exceeding the character limit for payment descriptions.</div></li></ul><p class="slate-p " >All available error codes and messages for <strong class="slate-bold">Payment API</strong>:</p><p class="slate-p " ><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:initial;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:472px;">Code</div><div style="width:620px;">Message</div></div><colgroup ><col style="width:472px"><col style="width:620px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >102</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >103</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown action</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >402</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Workflow with number %number% does not exist</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >420</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing invoice numbers</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >603</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Redirect Billink API error</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >704</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown invoice number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >706</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >You are not allowed to manage this order</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >707</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Order is already paid</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >708</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Description is too long (max. 30 characters)</h4></td></div></tr></tbody></table></div></p><p class="slate-p " ></p><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of On Hold API Error Codes</h3><p class="slate-p " >The <strong class="slate-bold">On Hold API</strong> error codes mainly address issues related to <strong class="slate-bold">client identification</strong>, <strong class="slate-bold">invoice and workflow management</strong>, and <strong class="slate-bold">order hold status</strong>. </p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Unknown details</strong> such as API version, client username, or client id.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Missing or incorrect invoice or workflow numbers</strong>.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Hold period issues</strong>, such as exceeding the maximum allowed duration due to guaranteed payment restrictions.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Order management errors</strong>, such as trying to set an order on hold when it&apos;s not possible or using unsupported parameters for resuming the order.</div></li></ul><p class="slate-p " >All available error codes and messages for <strong class="slate-bold">On Hold API</strong>:</p><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:469px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:469px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >103</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown action</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >104</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unsupported param for resume</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >401</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Missing invoice number or workflow number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >402</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown invoice number or workflow number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >403</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >On hold period is too long, because of guaranteed payment (max 14 days)</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >603</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Redirect Billink API error</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >701</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Order cannot be set on hold</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Resume Order API Error Codes</h3><p class="slate-p " >The Resume Order API error codes mainly focus on data availability and order state validation.</p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing or empty data sent in the request.</div></li><li class="slate-li " ><div style="position:relative">Orders not found in the system.</div></li><li class="slate-li " ><div style="position:relative">Orders that cannot be resumed due to their current status.</div></li></ul><p class="slate-p " ></p><div class="table-container" style="width:100%;min-width:100%"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:732px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:732px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No data is send</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No order found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Order cannot be resumed!</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Order Info API Error Codes</h3><p class="slate-p " >The Order Info API error codes mainly relate to form validation, access control, session management, and server errors.</p><p class="slate-p " >Common problems include:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing required form fields like billinkUsername.</div></li><li class="slate-li " ><div style="position:relative">Access denial due to insufficient permissions.</div></li><li class="slate-li " ><div style="position:relative">Sessions that cannot be found or have expired.</div></li><li class="slate-li " ><div style="position:relative">Unexpected server errors during processing.</div></li></ul><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:432px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:432px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >The form contains the following errors:  1) billinkUsername: This value should not be blank.</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >403</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Access denied</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Session not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >500</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Something went wrong</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Message API Error Codes</h3><p class="slate-p " >The <strong class="slate-bold">Message API</strong> error codes primarily relate to authentication, resource identification, and permission issues when interacting with the messaging system.</p><p class="slate-p " ><strong class="slate-bold">Common problems include:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Invalid or unknown client username or client ID.</div></li><li class="slate-li " ><div style="position:relative">Referencing a non-existent workflow or invoice number.</div></li><li class="slate-li " ><div style="position:relative">Using an incorrect HTTP method (e.g. using GET instead of POST).</div></li><li class="slate-li " ><div style="position:relative">Attempting to perform actions (like logging a message) without proper authorization.</div></li></ul><p class="slate-p " ><strong class="slate-bold">All available error codes and messages for Message API:</strong></p><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:initial;"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:409px;">Title</div><div style="width:884px;">Description</div></div><colgroup ><col style="width:409px"><col style="width:884px"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >101</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown client username or client id</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >401</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown workflow number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >402</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Unknown invoice number</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >603</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Error request. Use method POST.</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >701</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >You are not allowed to add message to log, please contact</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p><p class="slate-p " ></p>

<h3 class="slate-h3 " ><strong class="slate-bold">Summary of Invoices endpoint Error Codes</strong></h3><p class="slate-p " >The Invoices error codes are primarily related to validation, missing parameters, client authentication, and incorrect date formatting when retrieving invoice data.</p><p class="slate-p " ><strong class="slate-bold">Common problems include:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing or empty required fields such as billinkID or billinkUsername.</div></li><li class="slate-li " ><div style="position:relative">Submitting data that is not a valid JSON array.</div></li><li class="slate-li " ><div style="position:relative">Using incorrectly formatted dates (should be dd-mm-yyyy).</div></li><li class="slate-li " ><div style="position:relative">Supplying invalid calendar dates.</div></li><li class="slate-li " ><div style="position:relative">Referencing a non-existent client or master client.</div></li></ul><p class="slate-p " ><strong class="slate-bold">All available error codes and messages for the Invoices:</strong></p><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:502px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:502px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No data is sent</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No array provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field billinkID is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field billinkUsername is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Client is not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Master client is not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field “date_from” does not match the pattern dd-mm-yyyy</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field “date_from” is not a valid date</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field “date_to” does not match the pattern dd-mm-yyyy</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field “date_to” is not a valid date</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

<h3 class="slate-h3 " >Summary of Download Endpoint Error Codes</h3><p class="slate-p " >The Download endpoint error codes are mainly related to missing or invalid input data, client or master client lookup failures, and issues generating or retrieving the required PDF or ZIP files.</p><p class="slate-p " ><strong class="slate-bold">Common problems include:</strong></p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Missing or empty required fields such as billinkID, billinkUsername, year, or number.</div></li><li class="slate-li " ><div style="position:relative">Submitting data that is not a valid JSON array.</div></li><li class="slate-li " ><div style="position:relative">Providing a billinkID or billinkUsername that does not correspond to an existing client.</div></li><li class="slate-li " ><div style="position:relative">Master client not found when using grouped invoice logic.</div></li><li class="slate-li " ><div style="position:relative">Invoice not found based on the given input.</div></li><li class="slate-li " ><div style="position:relative">Required files (PDF or HTML) are missing or cannot be generated from HTML.</div></li></ul><h3 class="slate-h3 " >All available error codes and messages for the Download endpoint:</h3><p class="slate-p " ></p><div class="table-container" style="width:60%;
  min-width:60%;"><table class="slate-table" style="min-width:100%"><div class="published-table-header" style="width:100%;min-width:100%;"><div style="width:412px;">Code</div><div style="width:0px;">Message</div></div><colgroup ><col style="width:412px"><col style="width:initial"></colgroup><tbody class="slate-TableElement-tbody"><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No data is sent</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >No array provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field billinkID is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field billinkUsername is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field year is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Field number is not provided</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >400</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Invoice is not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Client is not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Master client is not found</h4></td></div></tr><tr class="slate-tr " ><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >404</h4></td></div><div class="slate-TableCellElement-content"><td class="slate-td"><h4 class="slate-h4 " >Could not get or generate pdf file. Please, see error log file for details</h4></td></div></tr></tbody></table></div><p class="slate-p " ></p>

Legacy API (v1)

<p class="slate-p " >In <strong class="slate-bold">Billink API</strong>, error responses follow a consistent format. All errors are returned with an <strong class="slate-bold">HTTP</strong> status code <span style="color:#00FF00">200</span>, which indicates the request was processed but there was an issue with the operation. </p><p class="slate-p " >The format of the error is as follows:</p><div class="code-block-wrapper"  style="width:60%" ><div class="code-block-header">XML</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"><?xml version='1.0' encoding='UTF-8' ?>
<API>
    <RESULT>ERROR</RESULT>
    <ERROR>
        <CODE>000</CODE>
        <DESCRIPTION>Error message</DESCRIPTION>
    </ERROR>
</API> </textarea><code class="language-xml keep-markup drop-tokens"></code></pre></div><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">CODE</strong>: A unique error code representing the specific issue.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">DESCRIPTION</strong>: A detailed description of the error.</div></li></ul><p class="slate-p " >These errors might indicate a variety of issues including but not limited to problems with API versioning, client authentication, missing or incorrect parameters, data format issues, and restrictions on actions (such as workflow limitations or invalid operations).</p><h3 class="slate-h3 " >Common Issues:</h3><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Client Identification</strong>: Errors related to missing or incorrect client username, client id, or API version.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Invoice and Workflow Management</strong>: Missing or incorrect invoice numbers or workflow data.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Order Management</strong>: Trying to perform actions on orders that are not allowed or are already processed.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Request Limitations</strong>: Exceeding request limits (e.g., number of invoices, action frequency).</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Parameter Validation</strong>: Incorrect or unsupported parameters in requests.</div></li></ol><p class="slate-p " >This helps you to easily handle and debug issues by following the provided error code descriptions across all API endpoints.</p><p class="slate-p " >In the next subsections, you will see errors specific to each endpoint. Each of these subsections includes a list of error codes and their corresponding descriptions to help you understand and resolve issues effectively.</p><p class="slate-p " ></p>

Brand assets

<p class="slate-p " >Welcome to our brand Toolkit. Here you can find the logos that you can use in your webshop. Place the Billink logo where you also have the logos of other payment methods. The logos can be placed in the check-out, footer, and for example the productpage and the landingpages.</p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=success ><div class="callout-icon"><svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M7.77116 10.8968L5.72949 8.8551C5.60449 8.7301 5.45171 8.6676 5.27116 8.6676C5.0906 8.6676 4.93088 8.73705 4.79199 8.87594C4.6531 9.01482 4.58366 9.17455 4.58366 9.3551C4.58366 9.53566 4.6531 9.68844 4.79199 9.81344L7.33366 12.3551C7.45866 12.4801 7.60449 12.5426 7.77116 12.5426C7.93783 12.5426 8.08366 12.4801 8.20866 12.3551L13.2087 7.3551C13.3337 7.2301 13.3927 7.07732 13.3857 6.89677C13.3788 6.71621 13.3128 6.56344 13.1878 6.43844C13.0628 6.29955 12.9066 6.2301 12.7191 6.2301C12.5316 6.2301 12.3684 6.29955 12.2295 6.43844L7.77116 10.8968ZM9.00033 17.3343C7.81977 17.3343 6.72255 17.1225 5.70866 16.6989C4.69477 16.2752 3.81283 15.6884 3.06283 14.9384C2.31283 14.1884 1.72602 13.3065 1.30241 12.2926C0.878798 11.2787 0.666992 10.1815 0.666992 9.00094C0.666992 7.83427 0.878798 6.74399 1.30241 5.7301C1.72602 4.71621 2.31283 3.83427 3.06283 3.08427C3.81283 2.33427 4.69477 1.74399 5.70866 1.31344C6.72255 0.88288 7.81977 0.667603 9.00033 0.667603C10.167 0.667603 11.2573 0.88288 12.2712 1.31344C13.285 1.74399 14.167 2.33427 14.917 3.08427C15.667 3.83427 16.2573 4.71621 16.6878 5.7301C17.1184 6.74399 17.3337 7.83427 17.3337 9.00094C17.3337 10.1815 17.1184 11.2787 16.6878 12.2926C16.2573 13.3065 15.667 14.1884 14.917 14.9384C14.167 15.6884 13.285 16.2752 12.2712 16.6989C11.2573 17.1225 10.167 17.3343 9.00033 17.3343ZM9.00033 16.0843C11.0142 16.0843 12.6982 15.4072 14.0524 14.053C15.4066 12.6989 16.0837 11.0148 16.0837 9.00094C16.0837 6.98705 15.4066 5.30302 14.0524 3.94885C12.6982 2.59469 11.0142 1.9176 9.00033 1.9176C6.98644 1.9176 5.30241 2.59469 3.94824 3.94885C2.59408 5.30302 1.91699 6.98705 1.91699 9.00094C1.91699 11.0148 2.59408 12.6989 3.94824 14.053C5.30241 15.4072 6.98644 16.0843 9.00033 16.0843Z" fill="#06837A"></path></svg></div><div ><p class="slate-p " ><strong class="slate-bold">Tip:</strong> Implement the badges and logos with direct link to the source file that we make available. <a href="67b87acd710b81af8f99c95b" target="">Read more.</a> </p></div></div><p class="slate-p " ></p>

Billink merkactiva

<p class="slate-p " >The payment badges are aimed at implementation in the checkout. Below you can download the Billink badges in SVG (optimal for web implementation) and PNG format. The orange badge is our preferred badge. Below there are 2 alternative badges, white with orange and black with orange. </p><p class="slate-p " >The preferred orange badge ensures the greatest recognisability for consumers in the check-out and will be most often used by other web shops. </p><p class="slate-p " ></p><h2 class="slate-h2 " >Default badges:</h2><div class=card-group-box style="width:100%; min-width:540px;"><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Preferred orange badge</h3><div style="text-align:left"><img src="https://theneo-prod-public.s3.us-east-1.amazonaws.com/33f187fe-f57f-4bca-9386-14ff3e971084.png" style="
              width:160px;
	            height:88px;
	            aspect-ratio:160 / 88"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orange.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#ffffff">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>       https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orange.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-orange.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>      https://cdn.billink.nl/assets/paybadge/png/billink-badge-orange.png</p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Preferred wide orange badge</h3><div style="text-align:left"><img src="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orange-wide.svg" style="
              width:233px;
	            height:86px;
	            aspect-ratio:233 / 86"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orange-wide.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#FFFFFF">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>         https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orange-wide.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-orange-wide.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>        https://cdn.billink.nl/assets/paybadge/png/billink-badge-orange-wide.png</p></div></div></div><p class="slate-p " >When you have a good reason to not use the orange badge, there are two alternatives. The white with orange badge and the black with orange badge. </p><p class="slate-p " >When you want to use it, use the one with the highest contrast with the background.</p><div class=card-group-box style="width:100%; min-width:540px;"><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Alternative badge orange on white</h3><div style="text-align:left"><img src="https://cdn.billink.nl/assets/paybadge/png/billink-badge-white.png" style="
              width:142px;
	            height:78px;
	            aspect-ratio:142 / 78"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-white.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#FFFFFF">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>         https://cdn.billink.nl/assets/paybadge/svg/billink-badge-white.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-white.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>        https://cdn.billink.nl/assets/paybadge/png/billink-badge-white.png</p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Alternative wide badge orange on white</h3><div style="text-align:left"><img src="https://cdn.billink.nl/assets/paybadge/png/billink-badge-white-wide.png" style="
              width:201px;
	            height:74px;
	            aspect-ratio:201 / 74"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-white-wide.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#FFFFFF">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>         https://cdn.billink.nl/assets/paybadge/svg/billink-badge-white-wide.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-white-wide.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>        https://cdn.billink.nl/assets/paybadge/png/billink-badge-white-wide.png</p></div></div></div><div class=card-group-box style="width:100%; min-width:540px;"><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Alternative badge orange on black</h3><div style="text-align:left"><img src="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack.svg" style="
              width:156px;
	            height:86px;
	            aspect-ratio:156 / 86"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#FFFFFF">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>         https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-orangeonblack.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>        https://cdn.billink.nl/assets/paybadge/png/billink-badge-orangeonblack.png</p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Alternative wide badge orange on black</h3><div style="text-align:left"><img src="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack-wide.svg" style="
              width:240px;
	            height:88px;
	            aspect-ratio:240 / 88"
         /></div><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack-wide.svg" target="_blank"><span style="background-color:#f18d20;color:#f18d20">x</span><span style="background-color:#f18d20;color:#FFFFFF">Download SVG</span><span style="background-color:#f18d20;color:#f18d20">x</span></a>         https://cdn.billink.nl/assets/paybadge/svg/billink-badge-orangeonblack-wide.svg</p><p class="slate-p " ><a href="https://cdn.billink.nl/assets/paybadge/png/billink-badge-orangeonblack-wide.png" target="_blank"><span style="background-color:#5d6678;color:#5d6678">x</span><span style="background-color:#5d6678;color:#FFFFFF">Download PNG</span><span style="background-color:#5d6678;color:#5d6678">x</span></a>        https://cdn.billink.nl/assets/paybadge/png/billink-badge-orangeonblack-wide.png</p></div></div></div><p class="slate-p " ></p>

Betaalbadges

Logo lockups

<div class=card-group-box style="width:100%; min-width:540px;"><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Billink Primary</h3><p class="slate-p " ><span style="background-color:#ff8d29;color:#FFFFFF">#FF8D29</span></p><p class="slate-p " ><span style="background-color:#ff8d29;color:#FFFFFF">rgba(255,141,41)</span></p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Billink Primary Light</h3><p class="slate-p " ><span style="background-color:#ffedde;color:#FFFFFF">#FFEEDE</span></p><p class="slate-p " ><span style="background-color:#fcefe0;color:#FFFFFF">rgba(255, 238, 222, 1)</span></p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Billink Pastel Blue</h3><p class="slate-p " ><span style="background-color:#9abae8;color:#FFFFFF">#9ABAE8</span></p><p class="slate-p " ><span style="background-color:#9abae8;color:#FFFFFF">rgb(154, 186, 232)</span></p></div></div></div><div class=card-group-box style="width:100%; min-width:540px;"><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Billink Liliac</h3><p class="slate-p " ><span style="background-color:#9577ad;color:#FFFFFF">#9577AD</span></p><p class="slate-p " ><span style="background-color:#9577ad;color:#FFFFFF">rgb(149, 119, 173)</span></p></div></div><div class="card-box without-icon"><div ><h3 class="slate-h3 " >Billink Dark Taupe</h3><p class="slate-p " ><span style="background-color:#16120d;color:#FFFFFF">#16120D</span></p><p class="slate-p " ><span style="background-color:#16120d;color:#FFFFFF">rgba(22, 18, 13)</span></p></div></div></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Kleurcodes

<ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Refer directly to the source images that are shown above and are hosted on CDN.Billink.nl.</div></li><li class="slate-li " ><div style="position:relative">Preferably make use of the SVG files regarding scalability.</div></li></ul><p class="slate-p " >We recommend that you implement the logos with a direct link to the source image as we made available above. For this we have setup a so-called CDN (Content Delivery Network) to guarantee loading times of just a few milliseconds. The advantage of a link to the source files is that you are always guaranteed for the most current logos and badges in line with the final brand strategy of Billink.</p><p class="slate-p " ></p>

Implementatie tips

<p class="slate-p " >To clearly display Billink at checkout, it is important to mention that the customer can pay afterwards. This is central to how we communicate as a company. Always use the following text next to or behind the Billink logo:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Pay afterwards with Billink</div></li><li class="slate-li " ><div style="position:relative">Pay later with Billink</div></li><li class="slate-li " ><div style="position:relative">Pay afterwards</div></li></ul><p class="slate-p " >These formulations are clear and directly inform the customer about the possibility of paying afterwards via Billink. It is essential to always display these texts at checkout.</p><div style="text-align:left"><img src="https://cdn.billink.nl/assets/dedicated/branding/checkout_voorbeeld_1.png" style="
              width:1712px;
	            height:208px;
	            aspect-ratio:1712 / 208"
         /></div><p class="slate-p " ></p>

Billink in je checkout

<p class="slate-p " >Do you need an alternative format which is not listed on this page or do you have a different question about the deployment of logos? Send an e-mail to <a href="mailto:marketing@billink.nl" target="_blank">marketing@billink.nl</a>.</p>

Heb je een ander formaat nodig?

Aanvullende informatie

Contactgegevens

Default

Billink Documentatie

Sandbox

Production

Check

Order

Status

<p class="slate-p " >Op deze pagina vind je relevante updates aan het Billink-platform: van nieuwe features en verbeteringen in Billink One tot belangrijke bugfixes, API-wijzigingen en nieuwe PSP-integraties. Zo blijf je altijd op de hoogte van wat er verandert en hoe dit jouw checkout, integratie of klantbeleving verbetert.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Op deze pagina vind je relevante updates aan het Billink-platform: van nieuwe features en verbeteringen in Billink One tot belangrijke bugfixes, API-wijzigingen en nieuwe PSP-integraties. Zo blijf je altijd op de hoogte van wat er verandert en hoe dit jouw checkout, integratie of klantbeleving verbetert.

<h3 class="slate-h3 " >Project features</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">HPP – Aanbetalingen v1: </strong>De logica rondom aanbetalingen is nog meer verfijnd. De optie wordt alleen getoond wanneer dit wettelijk en commercieel verantwoord is.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Rebrand Mobile apps v0:</strong> Onze mobiele apps zijn voorzien van een nieuw design, afgestemd op de Billink branding. Een moderner uiterlijk, betere leesbaarheid, eenvoudigere navigatie en een dark mode voor gebruiksgemak.</div></li><li class="slate-li " ><div style="position:relative"><strong class="slate-bold">Multi-email accounts (app):</strong> Gebruikers kunnen nu meerdere e-mailadressen koppelen aan één Billink-account. Hierdoor kunnen consumenten meerdere orders inzien als zij meerdere e-mailadressen gebruiken.
</div></li></ul><h3 class="slate-h3 " >
Features</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Session Cancel status toegevoegd → geeft merchants en klanten meer duidelijkheid wanneer een sessie wordt afgebroken. </div></li><li class="slate-li " ><div style="position:relative">Nieuwe velden in aanbetalingen betaaloptie → meer inzicht in betaalopties en betere beslislogica. </div></li><li class="slate-li " ><div style="position:relative">Nieuwe betaalmethode-selector en verbeterde Next-button in Billink One → minder klikken, snellere checkout. </div></li><li class="slate-li " ><div style="position:relative">Factuurnummers toegevoegd aan betaalomschrijvingen  </div></li><li class="slate-li " ><div style="position:relative">Affiliate-programma voorwaarden gelinkt in systeem → direct inzicht voor merchants. </div></li><li class="slate-li " ><div style="position:relative">Webhook-voorbeelden toegevoegd in developer documentatie → eenvoudiger testen en sneller integreren. </div></li><li class="slate-li " ><div style="position:relative">Documentatie vernieuwd en voorzien van nieuwe branding → consistentere ervaring voor developers. </div></li></ul><h3 class="slate-h3 " >
Mid release deployments (Hotfixes)</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Uitgebreide documentatie over webhooks sessie/orderinfo toegevoegd. </div></li><li class="slate-li " ><div style="position:relative">Bankoptie verwijderd bij iDEAL in mijn.billink.nl voor een duidelijkere betaalervaring voor klanten. </div></li></ul><h3 class="slate-h3 " >
Bug fixes</h3><p class="slate-p " >We hebben een groot aantal bugs verholpen die de stabiliteit en betrouwbaarheid verbeteren. Enkele belangrijke fixes:</p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Orderbedragen en geboortedata nu correct weergegeven in portals. </div></li><li class="slate-li " ><div style="position:relative">Diverse fixes in Customer Portal (login, orderoverzicht, factorloon-tabellen). </div></li><li class="slate-li " ><div style="position:relative">Betere foutafhandeling bij formulieren en disputeflows → minder blokkades voor merchants. </div></li><li class="slate-li " ><div style="position:relative">Kleine UI- en UX-fixes in portals (icons, vertalingen, lay-outs). </div></li><li class="slate-li " ><div style="position:relative">Billink One-logo toegevoegd aan developer portal → herkenbaarheid en consistentie.</div></li></ul><h3 class="slate-h3 " >
Maintenance</h3><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">Verbeterde dialogen en prompts in portals voor een duidelijkere interactie met merchants </div></li><li class="slate-li " ><div style="position:relative">Branding en kleine tekstwijzigingen doorgevoerd op portals en affiliatepagina’s.</div></li></ul><p class="slate-p " ></p><p class="slate-p " ></p>

We hebben een groot aantal bugs verholpen die de stabiliteit en betrouwbaarheid verbeteren. Enkele belangrijke fixes:

Sections

Release 62 – augustus 26, 2025

Project features

Features

Mid release deployments (Hotfixes)

Bug fixes

Maintenance

What made this section unhelpful for you?

On this page