Integration of Dynamics F&O with a payment app/portal

(0) Share

Report

Posted on by capedcrusader

Hello guys, Please I have a requirement to integrate a payment app with the ERP. the idea is to for payments to flow seemlessly once vendor payment journals have been approved and posted. upon posting, the Payment plaftorm picks up the details from the payment journals and processes the payments. The The payment API uses JSON request and response messages which can be run on any platform and in any programming language. The messages are transported via REST over HTTPS. I am essentially a functional person with a little bit of technical knowledge and have been asked to facilitate this, so I am hoping if anyone has pointers that can help

All responses (3)

Answers (0)

Martin Dráb 230,836 Most Valuable Professional on at

Like (0)

Report

Integration of Dynamics F&O with a payment app/portal

The single API just one small piece of an integration solution.
Frank Hamelly | MVP... 46,243 Super User 2025 Season 1 on at

Like (0)

Report

Integration of Dynamics F&O with a payment app/portal

Dumb question, but does the payment app API not handle the integration also?
Martin Dráb 230,836 Most Valuable Professional on at

Like (0)

Report

Integration of Dynamics F&O with a payment app/portal

It seems to me that your company significantly underestimate the complexity of integration scenarios. Collecting all the requirements and designing architecture of such solutions requires quite a lot of experience and "a little bit of technical knowledge" doesn't sound sufficient for a role of an integration architect. Therefore I strongly recommend that you don't try to do it on your own.

But let me give you a glimpse of the topics.

What is obvious is that you'll need to work on business requirements, such as what happens when payments are processed, what if they aren't and what if something changes in F&O. You'll likely also need integration of master data, e.g. to have the list of vendors synchronized across both systems and so some translation of values that aren't synchronized. This may show that the work needed is an order of magnitude bigger than what it seemed from the description. If changes may be done in both systems, you'll also need some way of dealing with update conflicts.

And there are also non-functional requirements. For example, reliability. A naive implementation may be calling the other's system service endpoint after journal posting, but what if it isn't available for some reason, e.g. because it's down for maintenance or there is a network issue? If you don't want to lose any messages, you'll likely need to use a message queue in between these systems. A possible designing may be putting business events to a service bus queue and having a cloud application (e.g. a Power Automate flow) taking messages from the queue and trying to call the target system.

Then you'll need to think about things like authorization, performance, throttling, deployment, monitoring and so on.

Integration of Dynamics F&O with a payment app/portal

Helpful resources

News and Announcements

Quick Links

Announcing Our 2025 Season 1 Super Users!

Announcing Forum Attachment Improvements!

Vahid Ghafarpour – Community Spotlight

Leaderboard

Featured topics

Product updates

Integration of Dynamics F&O with a payment app/portal

Helpful resources

News and Announcements

Quick Links

Announcing Our 2025 Season 1 Super Users!

Announcing Forum Attachment Improvements!

Vahid Ghafarpour – Community Spotlight

Subscribe to this forum!

Select categories

Leaderboard

Featured topics

Product updates