Building the future, one workflow at a time

Last month, J.P. Morgan joined Docusign onstage at its Docusign Momentum 2026 customer conference to co-present an art-of-the-possible use case our teams built together. The session, Building The Future, One Workflow at a Time, focused on an account-opening workflow powered by J.P. Morgan’s Validation Services APIs and Docusign Workflow Builder, a core part of the Docusign Intelligent Agreement Management (IAM) platform. Workflow Builder is a no-code visual workflow tool that connects Docusign and third-party applications to automate complex, multi-step agreement processes end to end. 

The session drew one of the conference’s largest breakout audiences, resulting in an over-capacity crowd. We were thrilled to be part of the event and to connect with fellow developers and technologists. You can read more about the use case we built together on the Docusign Developer Blog. 

Coming back from the event yielded multiple noticeable takeaways and prevalent themes:

Model Context Protocol (MCP) and developer workflow integration received strong interest.

MCP’s momentum is easy to understand. As teams move from experimentation to production, the challenge is no longer fragmented resources; scattered documentation, inconsistent tooling, and one-off integrations that don’t scale. MCP servers help solve that by giving developers a standard interface for exposing resources, actions, and context to AI-driven tools, reducing complexity and speeding up delivery.

When that integration works, the difference is tangible. Teams onboard faster, spend less time hunting for the right documentation, and move across systems without losing context. The result is a cleaner path from idea to production and a foundation that’s easier to maintain, govern, and build on as new tools are introduced.

In financial services, that value is even more pronounced. Institutions leverage AI-powered workflows that can work across complex systems while still meeting high standards for security, auditability, and control. MCP-based integration helps create a more governed way to connect agents to internal knowledge and operational tools making it easier to improve developer productivity without losing sight of risk and trust.

We’ve also unveiled an MCP Server on the Payments Developer Portal that provides direct, seamless access to J.P. Morgan Payments Developer Portal (PDP) documentation. This open-source solution enables developers and technologists alike to search across portal documentation, fetch specific pages in Markdown format, and discover related content all through a unified interface. The server is built for integration with AI agents and developer tools, supporting robust search, retrieval, and recommendation capabilities to streamline your workflow.

Security and fraud prevention continue to be top of mind

Security, fraud prevention, and trust are consistently top priorities for developers. Every transaction must be protected, and the systems behind it need to be reliable, secure, and built on trusted infrastructure.

For developers, security and fraud prevention are not separate requirements. They are core design considerations. The applications they build handle sensitive data, connect across multiple systems, and often support high-value transactions. That means developers need tools that help them verify identity, reduce exposure to bad actors, and maintain confidence that each step in the process is accurate, auditable, and resilient. Strong security controls also help teams move faster by reducing rework, limiting downstream risk, and creating a more dependable foundation for innovation.

This becomes especially important in financial services account opening, where institutions must balance a smooth user experience with strong controls for identity verification and fraud detection. A weak process can introduce risk at the very start of the customer relationship, while a well-designed one helps institutions onboard legitimate customers more confidently, reduce manual review, and strengthen trust from day one.

When we built our art of the possible account opening use case with Docusign, we integrated our Validation Services APIs (entity validation and account validation) and worked in tandem with the Docusign IAM platform. This enabled Workflow Builder to trigger identity & bank account verification via J.P. Morgan Payments Validation Services and generate an agreement pre-filled with verified data through Docusign's Workflow Builder. 

"We are living in a day and age where developers no longer have to choose between speed or flexibility anymore, they can have both. Our joint-session with JP Morgan sought to highlight this by connecting identity checks, bank account validation, and agreement generation in one workflow." - Niani Byrd, Docusign

There is interest in how trusted platforms can work together to simplify workflows for developers and end users

Our joint session with Docusign reinforced a clear theme: developers are looking for trusted platforms that work well together. When established providers integrate their capabilities, teams can build with more confidence, reduce implementation friction, and avoid stitching together disconnected tools on their own.

That is especially important in a use case like financial account opening, where disconnected steps can create delays, duplicate data entry, and unnecessary risk. In the example use case showcased at Momentum, applicant data is captured once, verification happens before agreement generation, and the workflow moves forward only after the required checks pass. For developers, that means a cleaner architecture and fewer manual workarounds. For end users, it means a more streamlined experience built on accuracy, trust, and speed.

A final note

Interest in MCP was strong because it points to a more practical way for developers to work across agreement data, payment APIs, and other critical systems. Instead of relying on fragmented integrations and manual handoffs, MCP creates a more consistent way to connect tools, retrieve context, and trigger actions. That simplicity matters: it helps teams reduce development overhead, accelerate implementation, and build experiences that are easier to maintain as requirements evolve.

For technology decision-makers the value is not just convenience, it’s control. Simplified workflows make it easier to standardize how teams access data and services, while strong security helps ensure those interactions remain governed, auditable, and reliable. In financial services, where workflows often involve sensitive customer information, payments, and compliance requirements, that combination is essential. The ability to simplify the developer experience without compromising trust is what turns promising technology into something institutions can confidently scale.