{"id":4906,"date":"2018-07-10T14:11:35","date_gmt":"2018-07-10T19:11:35","guid":{"rendered":"https:\/\/3dmerchant.com\/blog\/?p=4906"},"modified":"2021-12-03T03:24:39","modified_gmt":"2021-12-03T08:24:39","slug":"payment-processing-application-microsoft-dynamics-ax-365","status":"publish","type":"post","link":"https:\/\/3dmerchant.com\/blog\/erp\/payment-processing-application-microsoft-dynamics-ax-365","title":{"rendered":"Payment Processing Application for Microsoft Dynamics AX 365 ERP"},"content":{"rendered":"
Microsoft Dynamics AX credit card processing integrated for maximum profit and maximum security with Validated Point to Point Encryption (vP2PE).<\/h2>\n
<\/p>\n
\n
PCI Compliance is a moving target. We help reduce compliance burden with a PCI validated Point to Point encrypted solution. It’s important to note that only non-validated P2PE solutions have experienced data breaches in the last 12-18 months.<\/p>\n
\n
Accept credit, debit, ACH, check with guarantee, cash, wire, Paypal and more payment types. <\/strong><\/li>\n
Smart Rate Selector<\/strong> reduces credit card processing fees, including with level 3 processing. Qualifying transactions for the lowest rates is complicated and only with dynamic rules management can merchants automate processes that impact fees.<\/li>\n
Flexible processor options. You choose. Whether you want to keep your existing First Data, Chase Paymentech, Worldpay, or any other provider, or make a change, we give you options. And if you change acquirers in the future, it’s non-disruptive to operations, unlike “all-in-one” solutions.<\/li>\n
Need to reduce compliance scope for card not present transactions? Our Encrypted Virtual Keypad segregates your hardware from scope. \n<\/strong><\/li>\n
Compliance with new stored card credential rules is complicated also. We reduce compliance burden with various configurable tools.<\/li>\n<\/ul>\n
Do you have DOPS transactions currently processing credit cards?<\/strong> \nYou cannot process (authorize, capture, void, refund) any transaction through Dynamics online after Dec 31, even if that transaction occurred prior to Dec 31. After 12\/31\/2017:<\/p>\n
\n
Credit cards linked in AX \u2013 <\/strong>Will no longer work for any connector, need to be deleted and re-entered.<\/li>\n
Authorization <\/strong>\u2013 Will be lost. Either process this through your new solution or work with the payment provider to capture an existing authorization if possible.<\/li>\n
Capture<\/strong> \u2013 Will not be able to process linked refunds.<\/li>\n
Void<\/strong> \u2013 Will not be able to void a payment.<\/li>\n
Refund<\/strong> \u2013 Will not be able to refund a payment. \n<\/strong><\/li>\n<\/ul>\n
The above transaction types are very limited. For example, re-authorization, incremental authorization and authorization reversal are common types of transactions in B2B. If not managed correctly, then merchants pay higher fees and risk chargeback by both issuer or customer.<\/p>\n<\/div>\n