You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
With RetailSDK, the development VM provided local package references for Microsoft.Dynamics.Commerce.HardwareStation.CardPayment which is needed for creating a Payment Connector for pay in store with card present scenarios. RetailSDK also used to have "Payments" directory which provides Connector.Sample.Desktop and other PaymentSDK samples necessary to create a fully functional payment connector. To be able to maintain our existing payment connector and to continue to upgrade the extensions we need to know how we can reference the "CardPayment" library. I have verified that the dll is still present in the 9.51 sealed installers, but need to know how to continue to update the references for the payment connector to be upgraded. If the CardPayment library reference won't be available any more, then we need samples or assistance with how we can migrate the payment connector for CommerceSDK. There is very little to no documentation on this issue. The end-to-end payment connector documentation only addresses part of the issue. And the PaymentDevice sample is insufficient in details.
Version and Error Info
Commerce SDK Component: PaymentConnector/PaymentSDK/CardPayment/SDKManager
Component Version: 9.51
Commerce SDK Version: 9.51
Exception/Error Details: No exceptions. But need nuget library references for continuation of extension upgrades.
Reproducing the Issue
Link to GitHub repo/solution where the issue is reproducible: There is no issue to reproduce. But the payment connector cannot be upgraded without access to the necessary nuget packages.
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Run command '....'
See error
Screenshots
Please include any screenshots that would help us understand the issue.
The text was updated successfully, but these errors were encountered:
ja1m1n8hatt
changed the title
NUGET references for Microsoft.Dynamics.Commerce.HardwareStation.CardPayment.CardPaymentManager not available in CommerceSDK for PaymentConnectors
NUGET references for Microsoft.Dynamics.Commerce.HardwareStation.CardPayment not available in CommerceSDK for PaymentConnectors
Nov 16, 2024
Other Development Issue
Summary
Describe the issue
With RetailSDK, the development VM provided local package references for Microsoft.Dynamics.Commerce.HardwareStation.CardPayment which is needed for creating a Payment Connector for pay in store with card present scenarios. RetailSDK also used to have "Payments" directory which provides Connector.Sample.Desktop and other PaymentSDK samples necessary to create a fully functional payment connector. To be able to maintain our existing payment connector and to continue to upgrade the extensions we need to know how we can reference the "CardPayment" library. I have verified that the dll is still present in the 9.51 sealed installers, but need to know how to continue to update the references for the payment connector to be upgraded. If the CardPayment library reference won't be available any more, then we need samples or assistance with how we can migrate the payment connector for CommerceSDK. There is very little to no documentation on this issue. The end-to-end payment connector documentation only addresses part of the issue. And the PaymentDevice sample is insufficient in details.
Version and Error Info
Commerce SDK Component: PaymentConnector/PaymentSDK/CardPayment/SDKManager
Component Version: 9.51
Commerce SDK Version: 9.51
Exception/Error Details: No exceptions. But need nuget library references for continuation of extension upgrades.
Reproducing the Issue
Link to GitHub repo/solution where the issue is reproducible: There is no issue to reproduce. But the payment connector cannot be upgraded without access to the necessary nuget packages.
Steps to reproduce the behavior:
Screenshots
Please include any screenshots that would help us understand the issue.
The text was updated successfully, but these errors were encountered: