The short answer
The registry records Auth0 Identity & User Authentication as a possible interpretation of AUTH0* IDENTITY. This descriptor-to-company association has not passed claim-level evidence review. Compare the exact line, amount and posted status with your own receipt or account activity; the name alone cannot confirm the merchant or whether you authorized the payment.
What do the parts of AUTH0* IDENTITY mean?
- AUTH0 * IDENTITY
- Before the asterisk, "AUTH0" usually names the platform or parent company. After it, "IDENTITY" usually names the product, store or order. How descriptors work →
The notes below are unreviewed registry explanations, not confirmation of merchant identity, authorization or current policy. Claim-level source review is pending for this entry.
Why it shows up like this
Unreviewed registry note: A transaction labeled AUTH0* IDENTITY on your bank or credit card statement is an automated subscription payment billed by Auth0 by Okta, Inc. Auth0 provides Auth0 Identity & User Authentication services that allow software developers and companies to add secure login boxes, social sign-ins, and multi-factor authentication to their web or mobile applications. If your business runs an app, customer portal, or internal tool, your engineering team likely uses this platform to handle user access without building custom login systems from scratch.
Unreviewed registry note: Auth0 plans operate on a monthly recurring subscription model based on monthly active users, or MAUs. An MAU is counted whenever an individual user logs in, signs up, or refreshes an authentication token during the billing period. The service offers a free tier for up to 7,500 active users, but production applications automatically transition to paid billing once they surpass that limit. Paid self-service tiers start at $35 per month for B2C Essentials and scale upwards as your user base expands or when you enable premium features like custom domains and enterprise single sign-on connections.
Don’t recognize it? Common scenarios
Unreviewed registry note: Another frequent trigger is sudden user growth. Because Auth0 charges are tied directly to monthly active users, a marketing campaign or product launch that attracts thousands of new visitors can push a previously free account past the 7,500 user threshold, generating an unexpected monthly bill.
- Unreviewed registry note: A company web application implemented Auth0 to manage customer logins.
- Unreviewed registry note: Monthly active user volume exceeded the 7,500 MAU free tier threshold.
- Unreviewed registry note: Enterprise SSO or passwordless authentication features were enabled on the tenant.
Frequently Asked Questions
How does Auth0 count Monthly Active Users (MAUs)?
Unreviewed registry note: An MAU is counted whenever a user logs in, signs up, or refreshes an active authentication token within a given billing cycle.
Can I cap MAUs on Auth0 to avoid overages?
Unreviewed registry note: Auth0 provides alerts when reaching plan thresholds, but authentication continues unless hard tier restrictions apply.
Dispute Rights & Fraud Prevention
Unreviewed registry note: If an Auth0 charge appears on your statement and no one on your team created an account, report the unauthorized transaction to your financial institution. Under the Fair Credit Billing Act, you have sixty days from the statement date to dispute unauthorized charges on personal and business credit cards.
Independent reference — not affiliated with Auth0 by Okta, Inc.. Billing names and policies change; verify with the merchant or your bank before acting.
Sources and evidence
Sources may support different parts of this page. A company homepage does not establish a statement descriptor, refund policy or contact detail. Check the claim notes and your own receipt before acting.
- Auth0 Billing & Subscription Documentation https://auth0.com
- FTC: Disputing Credit Card Charges https://consumer.ftc.gov
Evidence review pending · pending · About UnknownCharges