Path SDK Intro

The Path SDK is a pre-built solution that simplifies building connections between our MDX specification, your application, and other third party connections using our Path framework. Path is an API framework that connects our mobile app product to the MX platform and any other data source you may rely on and translates between both of these connections, despite how disparate those systems are.

Use the Path SDK to independently build connections and interchange them within your mobile application as needed. The following guides explain the Path SDK architecture in detail and provide additional instructions to build your own accessor connections, behaviors, and facilities. It's available for download on GitHub.

Path Architecture

When you use the Path SDK, your application connects to an interface called the Path Gateway. The Gateway mirrors the MDX API protocol. The MDX protocol standardizes most common banking functions such as accounts, transfers, account origination and more. Learn more by visiting our MDX developer documentation.

To connect the Path Gateway to your selected fintech connection, Path relies on accessors, which translate between the fintech and our MDX specification. When using the SDK, you'll build your own accessors to accomodate these connections.

To create this connection, the Path SDK requires a configuration file named gateway.yml. This file provides the configuration which is modified and passed through a configurator to the Path Gateway. gateway.yml enables you to define API connections via accessors without having to change the core product associated with the Path Gateway or the MDX Interface.

The SDK also hosts facilities and behaviors. The SDK can switch between implementation of key/value storage, encryption appliances, and other services via facilities without having to reconfigure an accessor. It hosts behaviors in a similar way; caching, access control, and logging are all implemented within the SDK separate from the accessors.