In this post, we’ll explain how to process credit card payments in Dynamics 365 Finance & Operations without using the Retail (Commerce) module. This functionality is not well documented in Microsoft’s official materials, so the goal of this guide is to clarify how it works and how it can be configured and used in real projects. First things first — you must have a payment connector developed using the Dynamics 365 Payment SDK. In this scenario, we use Stripe as an example to

During our recent tests we discovered that Adyen capture response is just an acknowledgement, not a result. That implies Adyen accepted the request to capture money, but it doesn’t guarantee the capture of funds.   It's easy to prove. We'll create a new authorization to demonstrate this. and cancel it from the Adyen portal. Once the status is displayed as "canceled," we will proceed to D365 Commerce and post an invoice. As you can see, the invoice has been posted, and the pay

If you have a legacy payment connector implemented using RetailSDK and you're unsure about how to upgrade it to CommerceSDK, this post is for you. In RetailSDK, there was a folder containing a sample connector implementation. However, when Microsoft released CommerceSDK, this particular example was not added to the GitHub repository. Let's proceed with upgrading this code to the CommerceSDK package by copying the sample connector from RetailSDK to a separate folder. Next, we'

If you have a legacy POS payment connector integration with IPaymentDevice implementation, you must update it before upgrading to MPOS V34 or moving to StoreCommerce App. In V34, Microsoft added a new parameter RequestContext in the hardware station extension. This parameter doesn't exist in the IPaymentDevice interface, which is why you must remove IPaymentDevice from hardware station extension declaration. New method parameter Make sure that Legacy.PaymentDeviceAdapter is c