| Event | Who sees disclosures | What they accept |
|---|---|---|
| Account application | The applying Authorized Signer | The full stack: entity-level agreements (executed on behalf of the business), their own certification of authority, E-SIGN consent, and access terms. The applicant is identity-verified (KYC) during onboarding. |
| New user invited | The invited user, at first login | Person-level items only: E-SIGN consent, access terms, and privacy notice. No identity verification is required for ordinary users. |
| New Authorized Signer designated | The incoming signer, after bank KYC completes | Certification of authority, their own E-SIGN consent and access terms, and acknowledgment of the current versions of the entity-level agreements. The designation activates only after this stack is completed. |
| Bank updates a disclosure | Depends on update type and scope, see Disclosure updates | Existing customers are notified or re-prompted per the update’s enforcement. New customers receive the new active version in the flows above. |
Every account needs an Authorized Signer
Every active account must have at least one active Authorized Signer. The platform blocks deactivating the last Authorized Signer and directs the business to the signer-change process. An account that loses all its signers enters a restricted state until a new signer is verified and completes the acceptance stack.