# Non-SDK Integration
source: https://developer.mastercard.com/open-finance-us/documentation/connect/integrating/non-sdk/index.md

The Non-SDK integration path is designed for partners whose security requirements do not allow for external SDKs, or whose tech stack is not compatible with our SDKs. This approach provides full functionality across all of the same platforms that our SDKs support.

To implement Data Connect without an SDK, the following are required:

* Include a suitable `redirectUri` when [generating the Data Connect URL](https://developer.mastercard.com/open-finance-us/documentation/connect/generate-2-connect-url-apis/index.md), and also set `isHostedInMobileApp` as true for mobile applications.

* Handle OAuth completion via redirect, using the `redirectUri`.

In the Non-SDK model, all user interactions and session states must be tracked via Data Connect webhooks.

* You must subscribe to individual webhook events relevant to your integration.

* Webhooks provide essential insight into account linking, session completion, and error states.

See [Data Connect Webhooks](https://developer.mastercard.com/open-finance-us/documentation/webhooks/webhooks-connect/index.md) and [Data Connect Webhook Events](https://developer.mastercard.com/open-finance-us/documentation/webhooks/webhooks-connect/webhooks-events-connect/index.md) for more details.

## Web Integration (via iframe) {#web-integration-via-iframe}

Warning: Support for this integration style is not available by default. Discuss with your Customer Success Manager or Solution Engineer so that they can make the necessary changes to Data Connect behavior for your application.

If your application can't use the Mastercard Data Connect Web SDK, Data Connect can now be embedded using an iframe:

* Create and manage an iframe in your app.

* Set the Data Connect URL as the iframe `src` attribute.

* Ensure `redirectUri` is included in the Data Connect URL.

  This allows the user to return to your app once the account connection flow is complete.
* After Data Connect completes, the user will be redirected to your specified `redirectUri`, along with the following query parameters:

  * `code`: Numeric status code for session completion (for example: 200).

  * `reason`: Text explanation of the session status.

This approach gives you flexibility when SDK integration is not possible. However, it requires manual management of iframe behavior and session state.

## Mobile Integration (iOS and Android) {#mobile-integration-ios-and-android}

When embedding Data Connect within a native mobile app without using the SDK:

* Pass a `redirectUri` to regain control after the user completes the Data Connect flow.

  * Prefer Universal Links for iOS and App Links for Android.

  * Avoid using deep links as `redirectUri` values.

* Expect two redirects to the same `redirectUri`:

  * After the user completes their FI flow

  * After the user submits their connected accounts to Connect

<!-- -->

* Set `isHostedInMobileApp` as true for mobile applications.

<br />

The implementation details will depend on whether the user has their FI app installed, and whether you launch Data Connect in a Webview and the FI app in a secure container (Safari View Controller for iOS or Chrome Custom Tab for Android), or if both Data Connect and the FI authentication will be via secure containers.

See the following for further detail:

* [Non-SDK Integration Guide for iOS](https://developer.mastercard.com/open-finance-us/documentation/connect/integrating/non-sdk/non-sdk-ios/index.md)
* [Non-SDK Integration Guide for Android](https://developer.mastercard.com/open-finance-us/documentation/connect/integrating/non-sdk/non-sdk-android/index.md)