Skip to content

Clarify the OTP flow in Sage Bank Feeds connection flow#1797

Merged
pzaichkina merged 5 commits intomainfrom
update_sage_docs_otp_flow
Apr 1, 2026
Merged

Clarify the OTP flow in Sage Bank Feeds connection flow#1797
pzaichkina merged 5 commits intomainfrom
update_sage_docs_otp_flow

Conversation

@a-diarra
Copy link
Copy Markdown
Collaborator

@a-diarra a-diarra commented Apr 1, 2026

Description

  • Include a summary of the new content you're adding or the reason for the change.
  • Include relevant context.
  • Do not link to work items.
  • Any PNG images should be compressed using Tiny PNG or equivalent.

Type of change

Please delete options that are not relevant.

  • New document(s)/updating existing
  • Fixes
  • Styling
  • Bug fix (non-breaking change which fixes an issue)

Reviews and merging

You are responsible for getting your PR merged. Address review comments promptly and make sure to merge the PR when ready.
Feel free to 'Enable automerge' - your PR will automatically merge when accepted and passing the build.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 1, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
codat-docs Ready Ready Preview, Comment Apr 1, 2026 11:06pm

Request Review


Next, make the data connection ID from step two (above) available to the SMB user by, for example, surfacing the ID in your application. They'll need to enter this ID when connecting a bank account to Sage, as described in the next procedure.

## Surface the One-Time Password (OTP) to the user
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Headings] 'Surface the One-Time Password (OTP) to the user' should use sentence-style capitalization.


Next, make the data connection ID from step two (above) available to the SMB user by, for example, surfacing the ID in your application. They'll need to enter this ID when connecting a bank account to Sage, as described in the next procedure.

## Surface the One-Time Password (OTP) to the user
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Parens] Use parentheses judiciously.


## Surface the One-Time Password (OTP) to the user

In order to authenticate the connection, your user will be asked to submit a One-Time Password.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Will] Avoid using 'will'.


## Surface the One-Time Password (OTP) to the user

In order to authenticate the connection, your user will be asked to submit a One-Time Password.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('be asked').

```
GET https://api.codat.io/companies/{{companyId}}/connections/{{dataConnectionId}}/bankFeeds/otp
```
Surface the OTP in your application in a place where your user can retrieve it later as part of the connection flow.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Google.WordList] Use 'app' instead of 'application'.

![Default Codat authentication UI - Connect your bank account to Sage](/img/integrations/bank-feeds/new_sage_UI_with_connectionID_and_OTP_field.png)

5. If the SMB user was authenticated with Codat successfully, a dialog listing the available source bank accounts (created using the `POST / bankFeedAccounts` endpoint) is displayed. For example:
4. If the SMB user was authenticated with Codat successfully, a dialog listing the available source bank accounts (created using the `POST / bankFeedAccounts` endpoint) is displayed. For example:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('was authenticated').

![Default Codat authentication UI - Connect your bank account to Sage](/img/integrations/bank-feeds/new_sage_UI_with_connectionID_and_OTP_field.png)

5. If the SMB user was authenticated with Codat successfully, a dialog listing the available source bank accounts (created using the `POST / bankFeedAccounts` endpoint) is displayed. For example:
4. If the SMB user was authenticated with Codat successfully, a dialog listing the available source bank accounts (created using the `POST / bankFeedAccounts` endpoint) is displayed. For example:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('is displayed').

5. The SMB user selects the bank account they want to connect, then clicks **OK**.

7. The SMB user is redirected to the Sage product from which they started the connection flow.
6. The SMB user is redirected to the Sage product from which they started the connection flow.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('is redirected').

@a-diarra a-diarra changed the title Update sage docs otp flow Clarify the OTP flow in Sage Bank Feeds connection flow Apr 1, 2026

Next, make the data connection ID from step two (above) available to the SMB user by, for example, surfacing the ID in your application. They'll need to enter this ID when connecting a bank account to Sage, as described in the next procedure.

## Surface the one-time password (OTP) to the user
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Parens] Use parentheses judiciously.


## Surface the one-time password (OTP) to the user

In order to authenticate the connection, your user needs to enter a one-time password in their Sage product. Call the OTP endpoint to retrieve the OTP, then display it to the user in your application.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Google.WordList] Use 'app' instead of 'application'.

Corrected spelling errors and improved clarity in the setup instructions for Sage bank feeds.
7. The SMB user selects the bank account they want to connect, then clicks **OK**.

7. The SMB user is redirected to the Sage product from which they started the connection flow.
8. The SMB user is redirected to the Sage product from which they started the connection flow.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('is redirected').

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 1, 2026

Link check results for preview deployment (https://codat-docs-git-update-sage-docs-otp-flow-codat.vercel.app):

[
  "[404] https://codat-docs-git-update-sage-docs-otp-flow-codat.vercel.app/"
]

@pzaichkina pzaichkina merged commit 9b979f5 into main Apr 1, 2026
5 of 9 checks passed
@pzaichkina pzaichkina deleted the update_sage_docs_otp_flow branch April 1, 2026 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants