Overview

That is right. Unfortunately, receipts created via API can't have more than one payment type.

Hello! By default, the limit of the Loyverse API is set to 50. But it is possible to change the number of objects returned in the response. It can be done by passing the limit parameter. The default value is 50, and the maximum is 250. You can also try pagination. https://developer.loyverse.com/docs/#section/Pagination

Global e-invoicing is a huge, standardized ETL (Extract, Transform, Load) and API integration challenge. Viewing the 2024-2026 e-invoicing landscape as more than a tech upgrade reveals a major shift in business and government communication. From 2024 to 2026, e-invoicing shifts from a "nice-to-have" to a global mandate. The key driver is now fiscal transparency. Governments aim to close the "VAT Gap" by requiring real-time transaction reporting. 1. Trends in e-invoicing A. From post-audit to "clearance" models Traditionally, invoices were sent and reported weeks or months after transactions (post-audit). The main trend for 2024–2026 is shifting to Continuous Transaction Controls (CTC), requiring real or near real-time invoice data submission for continuous monitoring. Invoices are legally valid only after "clearance" via government platforms in real time, ensuring compliance before completion. This prevents "missing trader" fraud by giving tax authorities real-time visibility and matching data from buyers and suppliers for accuracy. B. The end of the "PDF" Standard PDFs sent by email no longer qualify as true "e-invoices" since they lack structured data needed for automation. The move away from PDFs supports more efficient, automated financial processes with less manual work. Trend: e-invoices now mean structured data in machine-readable formats like XML or JSON for automated processing. "Paperless" invoicing is outdated; the aim is "touchless" invoicing—fully automated from issue to payment without manual steps. C. Lowering of exemption thresholds E-invoicing mandates, once for large B2B firms, are expanding to include small and medium businesses (SMBs) by 2026. This broadens transparency and compliance across all business sizes. Revenue exemptions are lowered or removed, so even small merchants previously exempt must comply. D. Market growth The global e-invoicing market will grow as mandates spread across regions and industries. Growth is fueled by digital adoption, regulations, automation benefits, and fraud reduction. Market valued at about USD 15.9 billion in 2024, forecast to reach USD 68.7 billion by 2033, growing at a CAGR of 16.8% 2. What this means for SMB merchants For small merchants, this change may seem like a compliance task but brings key operational benefits. Here’s the selected table converted into HTML: Benefit Description Faster Cash Flow (DSO Reduction) Structured e-invoicing removes the "black hole" of emailed PDFs. Machine-readable invoice data allows instant approval by buyer's accounting software, reducing Days Sales Outstanding (DSO) so SMBs get paid faster. Cost Reduction Manual paper or PDF invoice processing costs more due to printing, postage, and errors. Automating saves money and time. Access to Supply Chain Finance Real-time invoice validation creates trusted data. Banks use this to offer faster, safer financing to SMBs, improving working capital. Future-Proofing As major buyers adopt standards, they’ll reject non-standard invoices. E-invoicing keeps SMBs "trade-ready." 3. How it works This section explains the technical setup behind modern e-invoicing. The "Structured Data" Standard Unlike PDFs, true e-invoices are text files in code formats like XML or JSON. UBL (Universal Business Language): A global standard. Semantic Mapping: Ensures "Total Amount" matches exactly between sender and receiver systems, regardless of software. The Four-Corner Model (Peppol Network) The common 2024-2026 framework, the Four-Corner Model, works like sending an SMS between different carriers. Corner 1 (Supplier): Sends invoice to their Access Point. Corner 2 (Sender’s Access Point): Converts data to a standard format and sends it securely. Corner 3 (Receiver’s Access Point): Receives, validates, and converts data for buyer's software. Corner 4 (Buyer): Gets clean data directly into their ERP or accounting system. This lets an SMB using "Software A" bill a client using "Software B" without custom links. API-First Connectivity Modern e-invoicing uses RESTful APIs for communication. Instead of manual entry on portals, accounting software uses APIs to send invoices directly to tax servers. Security: Encryption and digital signatures protect data during transit. 4. Real case Loyverse works with middleware like Myinvoice2u and Jomeinvoice to help SMBs meet Malaysian LHDN e-invoicing rules. They built the integration using the Loyverse API, providing a strong platform to connect services and support Malaysian merchants efficiently.

So there is no way to push a sale receipt with multiple payment types to loyverse API? So you cannot push a split payment type?

We have identified an issue with the Loyverse Get a list of items API (https://api.loyverse.com/v1.0/items). The API consistently returns a 403 Forbidden error when the request includes more than 50 IDs in the item_ids parameter. However, the request works as expected when we reduce the number of IDs to 50 or fewer. It appears there might be a limit on the number of IDs allowed per request, or the request size is triggering a security block, even though our credentials are valid. Endpoint: GET https://api.loyverse.com/v1.0/items Trigger: Sending > 50 item_ids Result: 403 Forbidden Error loyverse_error.txt

Thank you for reporting!

Hello. Thank you for your question. Unfortunately, it is not possible to post receipt by using get request. Best regards,

I have try a lot of different way to get data from Receipts by Item with google sheet script every column of my data went fine expect "Categoty Name" and "Modifier Applied (Option Name)" here is my sample code that's function function getLoyverseData_Fixed() { const ss = SpreadsheetApp.getActiveSpreadsheet(); let sheet = ss.getSheetByName(SHEET_NAME) || ss.insertSheet(SHEET_NAME); sheet.clear(); const headers = [ "Date", "Receipt #", "Item Name", "Category Name", "Modifier Applied (Option Name)", "Modifier ID", "Status" ]; sheet.appendRow(headers); const categoriesMap = fetchCategoriesMap(); const todayStart = new Date(); todayStart.setHours(0, 0, 0, 0); const url = `https://api.loyverse.com/v1.0/receipts?created_at_min=${todayStart.toISOString()}&limit=250`; const options = { 'headers': { 'Authorization': 'Bearer ' + LOYVERSE_TOKEN }, 'muteHttpExceptions': true }; const response = UrlFetchApp.fetch(url, options); const json = JSON.parse(response.getContentText()); if (!json.receipts) { Logger.log("Failed"); return; } let rows = []; json.receipts.forEach(r => { r.line_items.forEach(item => { let catName = item.category_name || categoriesMap[item.category_id] || "No Category"; let modOptions = []; let modIds = []; if (item.modifiers) { item.modifiers.forEach(m => { modOptions.push(m.option_name || m.name); // ดึง Option Name ตามภาพ modIds.push(m.modifier_id); }); } rows.push([ r.created_at, r.receipt_number, item.item_name, catName, modOptions.join(", ") || "-", // คอลัมน์ U modIds.join(", ") || "-", // คอลัมน์ V r.receipt_type ]); }); }); if (rows.length > 0) { sheet.getRange(2, 1, rows.length, headers.length).setValues(rows); sheet.autoResizeColumns(1, headers.length); Logger.log("Done checking at" + SHEET_NAME); } } function fetchCategoriesMap() { let catMap = {}; try { const res = UrlFetchApp.fetch('https://api.loyverse.com/v1.0/categories?limit=250', { 'headers': { 'Authorization': 'Bearer ' + LOYVERSE_TOKEN } }); const json = JSON.parse(res.getContentText()); if (json.categories) { json.categories.forEach(c => { catMap[c.id] = c.name; }); } } catch(e) { Logger.log("Failed"); } return catMap; } result is Category and Modifiers return blank and I can't use this data to run around powerBI with sheet sources to visualize for my team. By far I'm not sure if I call a wrong data name or I just can't get these both data. I'm not really developer just a marketing so if anyone can help me fixed this please.

In your API reference, you have put this... The receipt object payments > The list of payments. There is a restriction that only one payment can be applied to receipt when using POST request. Does that mean a receipt can be sent with a GET request, and multiple payment IDs can be sent - to allow for a split payment?

Yes - I assumed that. But it looks like now that the urls are being returned - so either you fixed something, or there was a reason it was not returning. Either way - it looks like it's working now. Thank you

would you like to send the zip to test it?

Hello. Thank you for your questions. 1. What is the monthly fee for Loyverse Online Ordering in Japan? It depends on which third-party online ordering you choose. 2. Are there any additional charges or transaction fees? Loyverse doesn't take a transaction fee. 3. What are the differences between the free plan and the paid plans? Could you refer to this page?: https://loyverse.com/pricing 4. Does Loyverse Online Ordering integrate automatically with the Loyverse POS system? Additionally, my main purpose is to use Online Ordering with QR codes in the restaurant. Customers will scan a QR code, place orders by themselves on their smartphones, and have those orders sent directly to the POS system automatically. 5. Is this QR code self-ordering flow supported by Loyverse Online Ordering? You can try Fuudey or MyMenu, for example. Let me know if there is anything else we can assist you with. 6. When customers place orders via QR code, do the orders appear automatically in the POS without manual input? 7. Can this be used for dine-in orders inside the restaurant?

Hello. Is that the "get a single item" endpoint? The image_url will appear only when you uploaded an item picture.

Hello. Unfortunately, Loyverse POS cannot print receipt created from API automatically.

Hi, I create a plugin dat creates a receipt via API, and it appears in Receipts in the pos , so that's working, but I doesn't print automatic the receipt. is there a solution for this ? does automatic printing also works within receipt that is created via API ?

[form] => SQUARE [color] => GREY [image_url] => image_url is always just empty API says it should be a string, and I see in other posts - others have managed to get the URL path - so has this feature broken, or been removed? "form": "SQUARE", "color": "GREY", "image_url": "string",

Hello. Thank you for your post. Loyverse expects the response from your server to be JSON (starting with {). Instead, it received a response starting with <. This is the opening bracket for HTML tags. [Source: (String)"<!DOCTYPE html>... <title>Server Error</title>...: This means your web server or framework caught an error and returned a standard "500 Internal Server Error" or "404 Not Found" HTML page to Loyverse.

Hello, I am operating a restaurant in Japan and currently using Loyverse POS. I am interested in starting Loyverse Online Ordering and would like to confirm the pricing details for Japan. Could you please clarify the following points: 1. What is the monthly fee for Loyverse Online Ordering in Japan? 2. Are there any additional charges or transaction fees? 3. What are the differences between the free plan and the paid plans? 4. Does Loyverse Online Ordering integrate automatically with the Loyverse POS system? Additionally, my main purpose is to use Online Ordering with QR codes in the restaurant. Customers will scan a QR code, place orders by themselves on their smartphones, and have those orders sent directly to the POS system automatically. 5. Is this QR code self-ordering flow supported by Loyverse Online Ordering? 6. When customers place orders via QR code, do the orders appear automatically in the POS without manual input? 7. Can this be used for dine-in orders inside the restaurant? Thank you very much for your support. Best regard

Hello @Steven111 Unfortunately, we don't have API for accepting orders yet. But you can post sales receipt via API.

I've looked through the forums and seen a recurring theme of wanting to interact with orders through the api. I would guess that if it were feasible through the API only, it would've already been done. I assume you need local network access. I'm curious if an Android SDK with a limited scope could accomplish this? If so, I would be happy to help in any way. I assume most of the functionality is already in the pos app (it could emulate a pos device and work perfectly for me). Best Regards, Steven

Hello @RAGAS Thank you for your post. You can see all the available API here: https://developer.loyverse.com/docs/ There are several integrators who provide e-invoicing integrations. https://loyverse.com/marketplace#:~:text=By Teketik-,e-Invoicing,-JomeInvoice Loyverse can be connected to Quickbooks via Amaka. https://loyverse.com/marketplace/quickbooks-amaka Let me know if there is anything else we can assist you with.

I just added a webhook through the web dashboard at https://r.loyverse.com/dashboard/#/webhooks. However, when I try to test the notification from the web interface, the request returns an error like this: { "result": "Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')\n at [Source: (String)\"<!DOCTYPE html>\n<html lang=\"en\">\n <head>\n <meta charset=\"utf-8\">\n <meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\n <title>Server Error</title>\n\n <style>\n /*! normalize.css v8.0.1 | MIT License | github.com/necolas/normalize.css */html{line-height:1.15;-webkit-text-size-adjust:100%}body{margin:0}a{background-color:transparent}code{font-family:monospace,monospace;font-size:1em}[hidden]{display:none}html{font-family:system-ui,-apple-sy\"[truncated 6109 chars]; line: 1, column: 2]" } The request never reaches my application. Can anyone help me with this?

Hi everyone, I am currently using Loyverse as my point-of-sale system and would like to request guidance and technical support regarding an integration setup. My goal is to integrate Loyverse with: A local electronic invoicing provider authorized by the Ministry of Finance in El Salvador (for compliant electronic tax invoices), and an accounting ERP such as QuickBooks for automated bookkeeping, VAT tracking, and financial reporting. Below is the intended data flow: CLIENT │ ▼ LOYVERSE (Sales, services, customers, pricing) │ │ Sale data ▼ SMARTBILL (Electronic invoicing authorized by the Ministry of Finance) │ │ Authorized electronic invoice (DTE) ▼ QUICKBOOKS (Accounting, VAT, financial reports) Specifically, I would appreciate your support with: *Available APIs, webhooks, or supported integrations to export sales and customer data from Loyverse. *Best practices or recommended partners for integrating Loyverse with third-party e-invoicing platforms *Existing or supported methods to connect Loyverse with QuickBooks (directly or via middleware) Thank you in advance for your assistance. I look forward to your guidance so we can implement this integration correctly.

Out of interest… does any pos allow this level of customisation?

Hello! You can get the store name and the employee name by using the "get a single store" and the "get a single employee" endpoint, using the Store ID and the employee ID. You can also get the payment type name by "get a single payment type" with the payment ID.