# Fiskil Link messaging (/data-api/guides/link-widget/messaging)

Recommendations and examples for messaging before and after Fiskil Link.



The screens around Fiskil Link help users understand why they should connect an account and what happens next. Use clear benefits, a short explanation of data sharing, and an obvious next step.

<Callout type="info">
  These are fictional application examples, not Fiskil Link screenshots. Adapt the copy to your product's data requests, sharing duration, and account-management features.
</Callout>

Before Fiskil Link [#before-fiskil-link]

Explain the benefit [#explain-the-benefit]

Lead with what the user gains from connecting, such as understanding their spending or reducing manual data entry. Keep the explanation short: a clear heading and one or two benefits are usually enough.

Set expectations [#set-expectations]

Introduce Fiskil Link before opening it. Explain what data your app will receive and why, with a link to your privacy information for more detail.

For example: “You'll use Fiskil Link to connect your bank account. We use your balances and transactions to build your spending overview.”

Make the next step clear [#make-the-next-step-clear]

Present Fiskil Link as the primary connection option, with a prominent action such as “Connect a bank account”. Use consistent branding and a polished screen so the transition feels familiar.

Build confidence [#build-confidence]

Explain that users authenticate with their institution and review the sharing request. Tell them how they can end sharing. Keep security statements specific to your integration and supported by facts.

Pre-Link messaging examples [#pre-link-messaging-examples]

Personal finance [#personal-finance]

This example leads with spending insights and explains which banking data supports them.

<LinkMessagingExample variant="finance">
  <h4>
    Make sense of your spending
  </h4>

  <p>
    Connect a bank account to build your Daylight money overview.
  </p>

  <ul>
    <li>
      See your balances in one place.
    </li>

    <li>
      Understand your spending over time.
    </li>
  </ul>

  <p>
    Daylight uses account details, balances, and transactions for your overview. Review the sharing request and duration with Fiskil Link before approving.
  </p>

  <LinkMessagingAction>
    Connect a bank account
  </LinkMessagingAction>

  <p>
    End sharing in your connected-account settings.
  </p>
</LinkMessagingExample>

Income assessment [#income-assessment]

Explain how banking data supports the application, without promising a lending outcome.

<LinkMessagingExample variant="income">
  <h4>
    Help us understand your income
  </h4>

  <p>
    Share banking data with Kin Lending to support your application.
  </p>

  <ul>
    <li>
      Use transaction history to help assess income.
    </li>

    <li>
      Reduce manual entry of income information.
    </li>
  </ul>

  <p>
    Kin Lending uses account details and transactions for your assessment. Review the sharing request and duration with Fiskil Link before approving.
  </p>

  <LinkMessagingAction appearance="income">
    Connect a bank account
  </LinkMessagingAction>

  <p>
    Connecting an account does not guarantee approval.
  </p>
</LinkMessagingExample>

Energy insights [#energy-insights]

Use the same approach for energy: explain the benefit and the data needed to provide it.

<LinkMessagingExample variant="energy">
  <h4>
    Understand your energy use
  </h4>

  <p>
    Connect your energy account to build your Evergreen overview.
  </p>

  <ul>
    <li>
      Explore your energy usage over time.
    </li>

    <li>
      Review your billing history in one place.
    </li>
  </ul>

  <p>
    Evergreen uses account details, usage, and billing data for your overview. Review the sharing request and duration with Fiskil Link before approving.
  </p>

  <LinkMessagingAction>
    Connect your energy account
  </LinkMessagingAction>

  <p>
    You choose whether to approve the sharing request.
  </p>
</LinkMessagingExample>

Follow-up messaging [#follow-up-messaging]

If a user hasn't connected an account, a reminder can bring them back to the task. Use the same branding, benefits, and clear action as your in-app messaging, and respect their notification preferences.

<LinkMessagingExample variant="email">
  <p className="border-b border-fd-border pb-5 text-xs">
    From: Daylight

    <br />

    Subject: Ready to finish your money overview?
  </p>

  <h4>
    Your money overview can wait for you
  </h4>

  <p>
    Return to Daylight to connect a bank account and start understanding your spending.
  </p>

  <p>
    We use account details, balances, and transactions for your overview. You'll review the sharing request with Fiskil Link before approving.
  </p>

  <LinkMessagingAction appearance="email">
    Return to Daylight
  </LinkMessagingAction>

  <p>
    Manage reminders in your notification preferences.
  </p>
</LinkMessagingExample>

After Fiskil Link [#after-fiskil-link]

Confirm that the account was connected and give users a clear next step. When account details are available, show a recognisable label and masked account number. Offer the option to connect another account if your app supports it.

Provide a place to view connections and manage or end sharing. See [Consents](/data-api/guides/core-concepts/consents) for how consent can end.

Consent completion does not mean all data is ready. If data is still syncing, say so; use the relevant [webhook notifications](/data-api/guides/core-concepts/webhooks) to determine when it is available.

Confirmation example [#confirmation-example]

Here, account details are available but transactions are still syncing.

<LinkMessagingExample variant="success">
  <h4>
    Your account is connected
  </h4>

  <p>
    Thanks for connecting with Fiskil Link.
  </p>

  <p className="rounded-xl border border-fd-border px-4 py-3 text-left">
    Example Bank

    <br />

    Everyday account · ending 4821
  </p>

  <p className="rounded-xl bg-fd-secondary px-4 py-3 text-left">
    Your transactions are syncing. We'll show your spending overview when they're ready.
  </p>

  <LinkMessagingAction>
    Go to my overview
  </LinkMessagingAction>

  <p>
    Review or end sharing in your connected-account settings.
  </p>
</LinkMessagingExample>

Next steps [#next-steps]

* [Integrate Fiskil Link](/data-api/guides/link-widget/integrating-the-link-sdk) to launch the flow and handle its result.
* Read the [Flow Overview](/data-api/guides/link-widget/flow-overview) to understand the consent journey.