.NET Monri–Dynamics 365 Connector

@amusto

Hi, I am a software engineer with 20 years' experience in software applications and integrations. I am very expert about .NET and I suggest to use the latest .Net Core 10 as .Net 6 is now deprecated as it reached the end of support in 2024. I think I can do this job. Please contact me to discuss the details. Regards, Armando

@softsolution2000

I have extensive experience in .NET development and have worked with C# programming language for many years. I am well-versed in software architecture and have a strong background in building robust and reliable applications. My experience with integrating different systems and APIs will be valuable in creating a seamless connection between Microsoft Dynamics 365 Business Central and Monri payment terminal. For the real-time handshake with Monri, I would utilize asynchronous programming in C# to ensure smooth communication and quick responses. My preferred GUI framework for this project would be WPF (Windows Presentation Foundation) as it provides a rich user interface and is easy to work with. I have previously integrated with Business Central APIs in various projects, and I am confident in my ability to create a stable and efficient connector for this specific use case. I am committed to delivering a high-quality solution with clean, well-documented code and thorough error handling. I am excited about the possibility of an ongoing partnership and look forward to discussing the project further. See the above links please.

@MSHOAIBK

Hello, I can build a reliable .NET 6+ connector that synchronizes sales and refunds between Microsoft Dynamics 365 Business Central and the Monri terminal in real time. I reviewed the supplied ECR protocol, including local TCP communication, transaction confirmation, error recovery, and daily-closing commands. I have 8+ years of experience with C#, .NET, REST APIs, Azure, SQL Server, Power Platform, and ERP/payment-related integrations. I would implement a correlation-based, idempotent workflow so every Business Central transaction is processed once and its exact approval, decline, or error response is written back for reporting and reconciliation. For the desktop interface, I recommend WPF because it is stable, lightweight, and well suited to store terminals. The architecture will separate the Business Central, Monri, UI, and persistence layers, making future payment-device integrations easier. I’m interested in supporting this connector long-term as your product line expands. I would first confirm whether the terminal will use local TCP, CloudECR, or Monri’s Remote API and review the available Business Central extension/API endpoints. Regards, Muhammad Shoaib

@a4logic

Hello, With my extensive experience and long-standing, deep skills in C# programming, I'm confident that I am the best fit for your .NET Monri-Dynamics 365 Connector project. Leveraging my 15+ years in this field, I have successfully delivered tailored solutions for businesses of all sizes and industries. Most importantly, I possess unparalleled expertise with .NET 6+, which is your stack of preference. In regards to the real-time handshake between Monri and Dynamics 365, I would use a combination of event-driven architecture and RESTful APIs. This approach will ensure smooth communication between the two platforms, guaranteeing instant data updates and seamless transactions. For the graphical interface, while I understand you prefer simplicity, rest assured that my sense of design combined with my knowledge of GUI frameworks will produce an intuitive UI that your store staff can easily navigate with no fancy storage cluttering up their workspace. Additionally, having worked on several ERP/CRM projects previously, including APIs that integrate with Business Central, I am well-versed in handling large-scale documentation as meticulously as you require. Lastly, what distinguishes me from others is my unwavering dedication to quality assurance, clean coding practices and an emphasis on maintaining good communication. I guarantee timely delivery while keeping scope for future updates open, ensuring that our partnership extends way bey Thanks!

@mak94pk

I’ll start by creating a lightweight WinForms/WPF client that connects to Monri’s REST API and subscribes to Business Central events via webhooks. The GUI will have clear fields for transaction details, a live status panel, and a day‑end report button. I’ll implement robust error handling, structured logging, and a JSON‑based config file that can be edited without recompilation. The app will be built on .NET 6+, packaged with a single‑click installer, and the source will be pushed to a Git repo. I can deliver a stable MVP in 14 days. Does Monri provide a sandbox environment and do you have existing Business Central API credentials?

@sufyanasmat38

Hi, I can build this .NET 6+ integration using clean C# architecture, with Business Central APIs connected to the Monri terminal through a reliable real-time transaction flow. I’d use a simple WPF or WinUI desktop interface for transaction details, live approval/decline status, and day-end reporting, with configurable endpoints, structured logging, retries, and error handling. I’ll also provide the installer, Git repository, documentation, and architecture designed for future payment-terminal integrations. Could you please share the Monri terminal model and API/integration documentation, along with any existing Business Central API details?

@juanpablomacf

The real challenge in this integration isn't the UI - it's building a reliable, real‑time handshake between Business Central and the Monri payment terminal. If the connector doesn't manage synchronous calls, retries, and error states correctly, you end up with mismatched transactions, incomplete refunds, and reports that can't be trusted. I've worked on .NET 6+ integrations where the priority was exactly this: stable API communication, clean logging, and predictable behavior for store staff. For your project I'd build a C# service that listens for sales/refunds from Business Central, triggers the corresponding Monri action, waits for approval/decline, and writes the result back through the BC API. The GUI would be a lightweight WPF or WinUI interface with clear fields, live status messages, and a simple day‑end report viewer. Endpoint settings, credentials, and terminal parameters would be editable without recompiling. A key early focus is the Monri handshake - handling timeouts, partial approvals, and terminal connectivity gracefully. I'd also ensure the connector logs every step so reconciliation is straightforward. If this approach fits your needs, I can outline the architecture and milestone plan. Juan Pablo

@vishal1145

Your real-time handshake with Monri will fail under network latency if you rely on synchronous HTTP calls blocking the Business Central UI thread. This creates timeout errors that corrupt transaction state and leave your staff unable to reconcile payments. Quick questions - are you running Business Central on-premises or SaaS, and does Monri expose webhooks for async confirmations or only a polling endpoint? Here is the architectural approach: - API INTEGRATION: Build an async message queue (RabbitMQ or Azure Service Bus) that decouples Business Central requests from Monri responses so network delays don't freeze your POS workflow. - .NET 6+ & C#: Implement a WPF desktop client with real-time SignalR updates for transaction status, plus a background Windows service handling retry logic and logging to SQL Lite for offline reconciliation. - BUSINESS CENTRAL: Use OAuth2 + OData v4 endpoints to POST sales invoices and PATCH payment confirmations, with idempotency keys preventing duplicate charges during retries. I've built three similar ERP-to-payment-gateway connectors for retail clients processing 2K+ daily transactions without data loss. Let's schedule a 20-minute call to map your Monri API spec and confirm the deployment model before I draft the technical design doc.

@huzaifa306

Hi, I can build the Business Central and Monri integration in C# with real time payments, refunds, logging, and reporting. Do you already have the Monri API documentation and test credentials available?

@AndrewJSMAN

I've built real-time payment integrations with .NET and Dynamics 365 before, so this is right in my wheelhouse. I'll use SignalR for the real-time handshake with Monri, WPF for the GUI, and the Business Central AL SDK for API calls. The app will poll Business Central for transactions, push them to Monri via REST, handle responses, and log everything. Configuration will be JSON-based, and I'll include a day-end report generator. The installer will use WiX, and the repo will have a README with setup notes. I can start immediately. Thanks, Andrii.

@wasifmuneer

As a seasoned Software Architect & Full Stack Developer with 16 years of experience, I can confidently say that I have a strong foundation in .NET, C# Programming, and software architecture, which will serve as the backbone of this project. From your job post, I understand that you need a robust .NET application that integrates with Microsoft Dynamics 365 Business Central and Monri payment terminals in real-time. I'm excited to build on my previous experience with Salesforce Apex triggers and .NET REST API integration, which will help me tackle the API integration aspect of this project. To ensure a straightforward graphical interface, I'll utilize a GUI framework that aligns with my expertise in .NET 6+ and C#. I'll also leverage clean, well-documented C# code to handle solid error handling, logging, and endpoint settings adjustments. To address your requirements, I'll focus on the following: 1. Establishing a real-time handshake with Monri using the .NET framework and implementing necessary error handling and logging mechanisms. 2. Designing a user-friendly GUI that meets your needs, with clear fields for transaction details, live status messages, and a day-end report area. 3. Packaging the finished app with a simple installer and source code in a Git repository. Before we proceed, I'd like to clarify a few aspects of the project: 1. Will the integration with Monri require any additional hardware or software components, such as a payment gateway or a dedicated server? 2. Are there any specific security or compliance requirements that need to be met for the integration with Dynamics 365 Business Central? I believe my expertise in .NET, C# Programming, and software architecture, combined with my experience with Dynamics 365 Business Central and Monri payment terminals, make me an ideal candidate for this project. I'm excited to discuss this further and provide a more detailed proposal. My bid amount is $1125, which I believe is competitive with the budget range of 750 - 1500 EUR. I'm committed to delivering high-quality work and look forward to the opportunity to work with you.

@longngoc2307

Hi, there. ".NET MONRI-DYNAMICS 365 BUSINESS CENTRAL CONNECTOR" - you need a reliable real-time bridge where Business Central sales/refunds reach the Monri terminal, return approval or decline, and remain traceable in transaction reports. I’d use .NET 6+ with C# and a simple WPF GUI, keeping Business Central API calls, Monri terminal communication, transaction state, and logging in separate services. The handshake would use explicit transaction states with timeouts, retries, duplicate protection, and clear handling for terminal declines or connection loss, so a failed response cannot accidentally create a second payment. Endpoint settings would stay configurable without recompilation, with installer and Git source included. Which Monri terminal/API specification and Business Central API endpoints are already available for the first connector? Looking forward to working with you.

@TechWagger2026

As an experienced full-stack developer, my 14+ years of expertise align perfectly with the requirements for this project. My proven track record and comprehensive command over various technologies—including the ones you're seeking (i.e., .NET) make me a strong fit for this role. Alongside .NET, I am well-versed in C# libraries, which would come in handy for your ERP integration. Moreover, having worked with payment gateways like Monri and other ERP systems similar to Dynamics 365 Business Central before, I'm well-aware of the critical nature of real-time transactions and can build a robust solution that ensures accurate reporting. Furthermore, my commitment to client satisfaction has often led to substantial long-term partnerships; I hope to earn just such an opportunity through this project. Consider me not just as a freelancer but as a reliable technology partner who can continuously improve your product line and adapt to new technological challenges as they arise. With me on board, you can remain confident that every aspect of this project—from the real-time handshake with Monri to the GUI framework utilized—will be tackled with expertise and precision.

@ssquare489

For the Business Central → Monri flow, I’d build the connector as a small .NET service layer that receives sale/refund requests, sends them to the terminal, validates the terminal response, and writes the final status plus transaction reference back to Business Central before reporting. I’d use C#/.NET 6+ with WPF for the GUI because it is stable, lightweight, and well suited to Windows-based store environments. My two priorities would be integrations and maintainability: terminal communication should have timeouts, retries, idempotency, structured logging, and reconciliation so a network failure never creates duplicate charges, while endpoint/device settings should live in configuration rather than compiled code. That makes future terminal or ERP upgrades much easier to support. I can handle the connector, GUI, Business Central API/OData integration, sale/refund workflows, day-end reporting, logging, installer packaging, Git repository, and technical documentation. I’ve worked on payment/POS integrations and business-system connectors, including Restaurant POS Rescue, where reliable communication between legacy operational systems and payment-related services was central. For Business Central specifically, I’d map the integration against the available API endpoints and extension requirements rather than forcing logic into the desktop client.

@jonasdedzo

Hi there, The main goal is to create a reliable real-time bridge between Dynamics 365 Business Central and your Monri payment terminal, so every sale or refund follows one clear path: Business Central sends the request, Monri processes it, and the final approval or decline is written back immediately for accurate reporting. I’d build this in .NET 6+ with a modular connector layer, configurable endpoints, structured logging, retry/error handling, and a simple GUI for transaction details, live status, and day-end reports. For the interface, I’d lean toward WPF because it provides a clean, maintainable desktop application without unnecessary complexity. I think you are planning to turn this first connector into a reusable product line, so I’d structure the payment and ERP adapters independently to make future device integrations easier. Looking forward to work with you. Thanks

@PrateekP3003

Being a seasoned developer with more than a decade of experience in the field, I'm confident about delivering a robust, well-documented .NET application that not only connects Microsoft Dynamics 365 Business Central with Monri but also ensures absolute real-time functionality. My extensive knowledge of both .NET 6+ and the C# language, paired with my proficient API integration skills, makes me a strong fit for this project. My approach to the real-time handshake with Monri would be to ensure efficient communication between the payment terminal and Business Central by incorporating diligent error handling, logging mechanisms, and adaptable endpoint settings. While building the solution, I will consider user-experience as a priority, ensuring a straightforward graphical interface that fits your store staff's requirements perfectly. Having developed various successful API integration solutions in the past and maintaining an ongoing relationship with my clients by continuously improving their products, I'm confident that I can meet your current needs while leaving scope for upgrading the integrations as you require. To document our collaboration and make any further enhancements seamless, I will package the final application along with its installer and source in a Git repository. If you're seeking a long-lasting partnership that yields proficient results even amidst future technology changes - together, we can achieve that!

@SkillCrafts

I can build a real-time .NET connector for your Monri payment terminal and Dynamics 365 Business Central, similar to how I've integrated payment gateways with ERP systems for seamless transaction processing and reporting. My focus will be on ensuring every sale and refund in Business Central immediately reflects on the Monri terminal, captures the approval/decline status, and updates Dynamics for accurate, on-demand reporting. My technical approach will involve developing a .NET Core application leveraging the Monri payment terminal's API and the Dynamics 365 Business Central Web Services (OData). I'll implement a robust event-driven architecture to handle real-time updates. The application will feature a clean WPF or WinForms GUI for transaction input, status display, and day-end report generation, prioritizing user simplicity and clarity for store staff. To ensure the best fit, could you clarify the specific Monri terminal model and its available API documentation? Also, what are your immediate priorities for the initial rollout of this connector? I'm available for a quick call to discuss the technical details further.

@Aaleen110

The main technical risk here is the real-time synchronization of transaction events between Dynamics 365 Business Central and the Monri payment terminal, so I build this with a dedicated service that polls Business Central for new sales and refunds, and then pushes those events to Monri. I'll use C# and .NET 6 for the application, integrating with the Monri API for payment processing and the Business Central API to read sales and refunds. For the user interface, I'll use WPF for a clear, straightforward graphical display of transaction status and reports, making sure error handling and logging are built in from the start so we can track down any issues quickly. The first piece I build is the Monri API integration layer, so that once it's proven, we can confidently push data from Business Central without worrying about the payment gateway itself. I would like to know what format the Monri API returns transaction statuses in, so I can design the response handling correctly. Preferred Freelancer here, 5.0 over 10 reviews, no missed deadline and nothing over an agreed price yet. I will send back a detailed technical approach document outlining the specific API endpoints I'll use and a basic architecture diagram once I have the Monri API response format.

@ranjika08

What matters most in this connector is keeping sales and refunds synchronized in real time without leaving staff guessing whether the terminal or Business Central is the source of truth. My approach would be to isolate the transaction engine from the UI, so the app can listen for the Business Central action, send the payment/refund request to Monri, capture the response immediately, and write back a normalized result with logs for audit and troubleshooting. I’ve handled API-based integrations and operational tools where stability, traceability, and maintainability mattered more than flashy UI. For your stack, I’d keep it in clean .NET 6+ C#, document the code properly, expose environment/settings in config, and package it with a straightforward installer plus repo handoff so future connectors can branch from the same base. I’d lean toward WPF for a clearer desktop interface and cleaner scaling if this product line grows. - Do you need automatic retries on temporary communication failures, or should failed transactions always require manual user confirmation? - Should day-end reporting be generated inside the app only, or also pushed back into Business Central in a report-friendly format? - Has Monri provided technical docs for terminal communication already?