Dynamics 365 F&O/AX Dynamics 365 CE / CRM Dynamics GP Business Central / NAV UG Dynamics SL Power Platform Fabric UG MS Copilot UG

[Archive User]

Microsoft announced the discontinuation of the Dynamics Online Payment Services effective January 1, 2018. According to the Microsoft blog post, Users processing credit card payments within Microsoft Dynamics AX and other applications must migrate to alternative solutions provided by Dynamics Independent Solution Providers to avoid a disruption in service.

——————————
Christopher Justice
CenPOS
Miami FL
——————————

[John Plut]

Having been in the AX market for many years, the name that always comes up for Credit Card Solutions is Red Maple. I have implemented their solution on a number of end users. 

——————————
John Plut
——————————
——————————————-

[Adrienne Refsgaard]

Thank You John for recommending Red Maple. We are currently working with many users that are impacted by this announcement. Please let us know if you have any questions about the news or alternatives to transition away from the discontinued Dynamic Online Payment Services.

——————————
Adrienne Refsgaard
Red Maple
BOERNE TX
——————————
——————————————-

[Lori Holmes]

In addition to Red Maple, what is everyone else using?  We are impacted by this and are interested in pros/cons seen by the community.

Thank you.

——————————
Lori Holmes
Bridgewater, NJ
LHOLMES@hamamatsu.com
732-537-3619
——————————
——————————————-

[Daniel Zook]

We use Retail Realm.

——————————
Daniel Zook
Director of IT
Lehman’s
Dalton OH
——————————
——————————————-

[Seth Derevensky]

I was actually going to suggest the same thing Daniel said. I know we (RSM) have built direct payment connectors in the past (to First Data, Chase Paymentech, Litle, etc.), but some of our customer use Retail Realm w/Shift4. 

——————————
Seth Derevensky
Consulting Director
RSM US LLP
——————————
——————————————-

[Robert Funke]

Although we are on R3 CU8 right now we are building out own from the Microsoft Dynamics Payment SDK they released for AX 2012 R2 CU7. We went through Microsoft Support to get the SDK.

Our internal development team has already used the SDK to connect AX and CyberSource for transactions coming from one of our ecommerce sites. On those sites the ecom system would call CyberSource to authorize the card and capture the token. The order information along with the token for the credit card are sent to AX and through the SDK, AX settles the transaction once shipped and delivered. For returns and exchanges done at the main office, everything goes through the SDK.

We will just do something similar for our stores before the end of the year.

——————————
Robert Funke
Manager, Global ERP
TempurSealy Inc.
Lexington KY
——————————
——————————————-

[Tony Malarz]

I was reading the whitepaper on the AX credit card feature (2009) yesterday to see if it’s something I can start using (or more like *want* to start using, I didn’t like seeing that card-on-file is saved in the database unencrypted and not out at the processor like I hoped to see.)

Score one for AXUG membership!  This is good timing for me to see this, and to Christopher, thanks for posting it.

Out of the box AX offers 2 card processor choices, “Microsoft Dynamics Payment Services” and “Authorize.net”.

To be clear:  MS is discontinuing the card processor “Microsoft Dynamics Payment Services”, but the AX credit card feature lives on?
So then Authorize.net is the only remaining out-of-the-box processor for this AX feature?  (without looking at ISV solutions like Christopher’s company?)

——————————
Tony Malarz
Sr. Database Analyst
Nortek Air Solutions
Eden Prairie MN
——————————
——————————————-

[Christine Speedy]

ISV is the only option- the notice states “customers should consider payment solutions provided by Dynamics Independent Solution Providers (ISVs)”.

AX 2012 does not offer the authorize.net option that you see in 2009, because that was rolled into single point of access through Payment Services with 2012.

UPDATE: Due to significant Visa payment processing rules changes from October 2016 and continuing through 2017, impacting card issuer, acquirer, merchant and customer experience,  all users are recommended to review applicable rules for their industry. What worked in the past is NOT compliant for the future. Reference: Visa Core Rules and Visa Product and Service Rules (PSR 384 is a good starting point)  October 2016, and subsequent bulletins.
Some items impacted include:

• Stored credential on file (token billing), including written authorization from customers
• Estimated Authorization Request
• Incremental Authorization Request
• Final Authorization & Reversal Requests
• Cancellation Policy
• Issuer initiated chargeback reason 72
• Cardholder Authentication Verification Value requirements

————————-
Christine Speedy
CenPOS
Miami FL
https://www.youtube.com/watch?v=ZZRRTB2ExH4
——————————
——————————————-