Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.narrativebanking.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Integration sequence

1

Load current connections

Read active integrations during account or settings bootstrap.
2

Start provider connect

Redirect the user to the provider authorisation flow from the product UI.
3

Handle provider callback completion

Confirm callback success and refresh account integration state.
4

Support safe disconnect

Require explicit user confirmation before disconnect operations.

​
What’s new in v1.5.7

v1.5.7 expands the connected-data experience and clarifies what users should expect after they connect a source.
  • Shopify provides commerce context through a guided connection and initial data load.
  • Bank connections are currently limited to one account while full multi-account handling is prepared.
  • Connection success and data availability are separate states: a provider may be connected before all related product views have refreshed.

​
Provider guides

https://mintcdn.com/narrative-b13c445c/qi6sqKB_OLTe8ty2/SVG/link-handoff.svg?fit=max&auto=format&n=qi6sqKB_OLTe8ty2&q=85&s=710c716f96a2cf04ebe7fa38257b5ea1

QuickBooks integration

Connect QuickBooks through the hosted authorisation flow and review supported data.
https://mintcdn.com/narrative-b13c445c/qi6sqKB_OLTe8ty2/SVG/link-handoff.svg?fit=max&auto=format&n=qi6sqKB_OLTe8ty2&q=85&s=710c716f96a2cf04ebe7fa38257b5ea1

Shopify integration

Set up Shopify, complete the hosted OAuth flow, and review supported commerce data.
QuickBooks follows the standard provider lifecycle, with a few accounting-specific expectations:
  • start the connect action from an authenticated product area
  • complete the hosted callback and refresh integration state immediately afterwards
  • allow time for the initial accounting data load after a successful connection
  • expect a daily scheduled refresh after the integration becomes active
Use QuickBooks integration for the connection flow, supported data, and refresh expectations. Shopify follows the same provider lifecycle, with a commerce-specific sync scope:
  • start the connect action from an authenticated product area
  • complete the hosted callback and refresh integration state immediately afterwards
  • allow time for the initial Shopify data load after a successful connection
  • distinguish between a connected store and fully available synced data
Use Shopify integration for setup, supported data, sync expectations, and current limitations.

​
Operational recommendations

  • Reconcile connection state after each connect or disconnect action.
  • Keep provider-specific copy in UI, not in shared integration assumptions.
  • Capture callback failures with trace context for support workflows.
  • If a user tries to connect an additional bank account, explain that multi-account support is coming rather than letting the user continue into an unsupported experience.

​
Error handling baseline

  • Validation errors: block and surface actionable remediation.
  • Auth failures: require user re-authentication before retry.
  • Rate limits: retry with bounded backoff.
  • Runtime failures: capture request trace and escalate if persistent.