v1.5.9

​

Release overview

v1.5.9 focuses on the first few moments that matter most: sign-in, onboarding, bank connection, Money recommendations, and Growth opportunity review. Money recommendations are more specific and better qualified. The SDK can now ask for a small amount of extra context before showing recommendations that cannot be confirmed from transaction data alone, and it can surface more practical opportunities around recurring spend, idle cash, late payments, and debt costs. Onboarding and Growth have also been tightened so users see fewer ambiguous states. Public business links, mobile onboarding controls, country and sales-channel answers, and Growth impact presentation all behave more consistently. Breaking changes: None. Deprecations: None.

​

Money

Money recommendations are more specific and action-oriented. Cards are designed to focus on one clear opportunity, name the relevant counterparty or category where possible, quantify the impact when the data supports it, and give the user a practical next step. Some recommendations can now ask follow-up questions before being shown as confirmed actions. This helps recover useful recommendations when bank data suggests an opportunity but cannot confirm key context such as eligibility, software usage, or business profile details. The release adds a subscription value review flow for recurring software and service spend. When usage cannot be inferred from transactions alone, the product can ask clarifying questions and then show relevant alternatives or explain why no action is needed. Money can also surface new transaction-pattern opportunities for idle cash, late or deteriorating expected payments, and debt cost review. These recommendations are conservative by design and include caveats where timing, rates, or balances are inferred from transaction history rather than contractual records.

​

Growth

Growth recommendations are easier to compare and convert into projects. Impact formatting is clearer, metric labels are more consistent, and recommendation copy follows British spelling and sentence-case presentation more reliably. The “What you can do” section is shorter and more focused, with a clearer prompt to start a project when the user wants a full plan. Impact, cost, and timing estimates are intended to vary by opportunity instead of repeating generic defaults. Evidence quality has been tightened so recommendations are better grounded in named market signals, dated statistics, or specific sources when those are available.

​

Onboarding and first-use experience

Onboarding now preserves the public company email follow-up after the business-name step, improving the business context available to downstream product experiences. Website and social-link handling is more predictable. Public social profiles can be used as business context where supported, malformed URLs receive clearer recovery messaging, and optional skip controls behave consistently. Mobile onboarding is more usable on iPhone Safari and narrow viewports. Prompts, chips, calls to action, and input controls remain visible and tappable through the required onboarding flow. The country and sales-channel steps handle ambiguous answers more carefully. Multi-country answers and off-topic sales-channel responses can trigger clarification instead of being silently accepted or skipped. The sign-up and sign-in screens have also been polished so the first authenticated touchpoints feel more consistent with the rest of the product while preserving existing authentication behaviour.

​

Connected data and content presentation

Bank connection screens now use current Narrative branding consistently in user-visible provider flows. Visual content that uses Unsplash images now includes the required attribution and usage handling. This supports higher-volume production use while preserving graceful fallback behaviour when image data is unavailable.

​

Compatibility

This release remains compatible with existing v1.5.x integrations. No partner migration is required for standard embedded integrations. No new partner configuration is required for the improvements described above.

​

Support

Questions about this release or integration: support@narrativebanking.com SDK documentation: docs.narrativebanking.com