Notification banner
Show a banner that lists required actions for risk interventions and onboarding requirements.
Renders a notification banner that lists open tasks for the connected account. Tasks can involve risk interventions or outstanding requirements for account capabilities such as accepting payments and payouts. This component helps connected accounts maintain active status by notifying them of open tasks that can affect their status or capabilities. The banner renders only when the connected account must respond to risk interventions or provide currently due requirements.
Requirements collection options![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
You can control the collection of currently_
or eventually_
requirements and the inclusion of future requirements by using the collectionOptions
attribute when you integrate the notification banner component.
External account collection![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Use the external_account_collection feature to control whether the notification banner component collects external account information. This parameter is enabled by default, and only platforms responsible for collecting updated information when requirements are due or change (including Custom accounts) can disable it. When enabled, this option requires user authentication.
Create an Account Session![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
When creating an Account Session, enable notification banner by specifying notification_
in the components
parameter.
Render the notification banner component![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Configure custom banner behaviour![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
You can configure custom behaviour, such as different margins, for when the banner includes any notifications or when the notifications require any action. To do so, set a custom callback function using onNotificationsChange
.
Testing![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
To test this component in test mode, specify different test inputs for fields that fail verifications or generate requirements on the account. For example, you can use the account management component to enter address_
in line1
of an individual’s address to trigger an address mismatch. In production, it can be difficult to verify that this component is working as expected because it’s hidden when an account has no banner items. To validate your integration is working, you can:
- Set a callback using
onNotificationsChange
that verifiesresponse.
is zerototal - Confirm the component is being displayed with no content using a loader start handler