The public profile, discovery, following or direct-message workflow received a material implementation update. The billing, checkout, payout or recurring-pay workflow received a material implementation update. Request, session, browser or abuse-protection handling received a material implementation update. Sign-in, passkey or account-verification handling received a material implementation update.
What users should notice
• People can use the same Ident.ink account and public project identity without creating a separate network account. • Customers should see clearer progression through funding, onboarding and payment state instead of being sent between disconnected screens. • The change strengthens the protection boundary without changing legitimate account permissions or product access. • The affected account flow now uses the same server-side session and verification boundary as the rest of Ident.ink.
How it works
• Visibility and messaging remain subject to relationship, blocking and account-standing checks. • Sensitive payment details remain with the payment processor; Ident.ink stores only the references and operational state required for the workflow. • Security controls remain layered and server-enforced; public release notes never include rules that would help bypass them. • Authentication changes remain scoped to verified challenges, protected cookies and explicit account ownership checks.
Affected product areas
Platform services, Website and interface, Account and platform security, Billing and payments
Published on Discord by Ident.ink Bot.