FAQ
AuthLN introduces a new paradigm in identity security. With that shift come important questions.
Below is a comprehensive FAQ organized by topic. If you need deeper technical detail or have specific requirements, please contact our team directly.
FAQs - Core Concept & “Why Now”
What is Pay Factor Authentication (PFA)?
1
Pay Factor Authentication® — a patented FIDO2 passkey + Smart Contract "paywall in front of every identity access attempt. Authorized users never pay. Attackers do. We make attackers pay real value before they can even try to log in.
Why does identity security need economic controls?
2
Every civilization learned the same lesson: free access = loss of sovereignty. Software gave cyberspace zero physical cost, so AI agents now dominate. AuthLN imposes real-world energy cost on every login, API call, and privileged action — turning cyberspace back into 3D physics where humans still win.
Is this just another MFA?
3
No. MFA is still free to attack. We are the first pre-auth economic deterrent that works with your existing MFA/IdP.
How is this different from MFA?
4
MFA is meant to verify identity but has proven to be flawed. PFA imposes economic cost before access is attempted - verifying intent before proceeding.
Is this replacing passwordless authentication?
5
No. It strengthens passwordless by adding economic enforcement.
Why hasn’t this existed before?
6
Until programmable digital value and real-time smart contracts, enforcing cost at authentication wasn’t technically feasible. With AuthLN, value is derived from Proof-of-Work—already verified at the network layer—and enforced without intermediaries, processors, or third-party fees.
FAQs - How It Works
What does the user experience?
1
Identical login flow (Okta, Microsoft, Google). QR appears → user scans QR with AuthLN App → payment is initiated → passkey refunds transaction instantly → user proceeds. Zero friction. Authorized users literally never pay.
Does the user pay personally?
2
The short answer is, No. AuthLN handles all financial mechanics on behalf of an organization. Users are essentially leveraging a FIDO2 passkey.
What happens to attackers?
3
They must send real money from their wallet. We capture it. We also log device, location, and intent data for your SOC. Every failed attempt creates signal that hardens policy.
What happens if a user makes a mistake during their access attempt?
4
The access attempt does not proceed. They can just try again, as normal.
How does value move, settle, and get governed?
4
AuthLN fully abstracts the economic layer - customers never manage wallets, liquidity, or settlement. AuthLN provisions and manages liquidity. Standard service supports thresholds.
Due to current KYC and financial regulations, captured value is not distributed to the customer. AuthLN maintains custody and accounting of economic flows in full regulatory compliance.
FAQs - Security & Compliance
7
Where does this sit in the stack?
1
We layer in front of the IdP at the application layer. No re-architecture required.
Where does AuthLN sit in the authentication flow?
2
Yes. It operates as an economic control layer within existing identity flows.
7
Is this a new factor?
3
Yes. It operates as an economic control layer within existing identity flows.AuthLN operates as an economic control layer within the authentication workflow, integrated alongside the existing IdP.
Does this introduce an authentication bottleneck?
4
No. The enforcement mechanism is designed for low-latency execution and horizontal scalability.
Credential stuffing, MFA fatigue, automated brute force, replay attempts, and AI-scale authentication abuse.
Can attackers simulate value commitments?
No. Value must be cryptographically valid and network-verified.
Is it post-quantum aware?
6
Yes. Cryptographic architecture accounts for future resilience.
Can this support Zero Trust mandates?
Yes. It strengthens Zero Trust by enforcing cost before trust decisions.
7
How does it scale under peak traffic?
5
AuthLN is stateless at the enforcement layer and scales horizontally. Value validation is deterministic and network-verified.
What threats does this mitigate?
6
Is it suitable for critical infrastructure?
6
Yes. It is designed to constrain autonomous attack traffic.
Is PFA FIDO2 compliant?
Yes. It builds on FIDO2 passkey standards.
FAQs - Integration & Deployment
Where does this sit in the stack?
1
Sits in front of any IdP (Okta, Entra, Google), ZTNA, VPN, or PAM at the application layer. No re-architecture required.
How long does deployment take?
2
Typically under one hour using guided integration.
Does this require lift-and-shift?
3
No changes to your existing identity provider are required.
Can it trigger before password entry?
4
Yes, depending on integration model.
Is this replacing passwordless authentication?
5
No. It strengthens passwordless by adding economic enforcement.
Why hasn’t this existed before?
6
Until programmable digital value and real-time smart contracts, enforcing cost at authentication wasn’t technically feasible. With AuthLN, value is derived from Proof-of-Work—already verified at the network layer—and enforced without intermediaries, processors, or third-party fees.
FAQs - AI-Agent Defense
Why do AI agents break traditional Zero Trust?
1
Because access attempts are free. AI can brute, replay workflows, or iterate at machine speed forever. Our patents force every attempt to burn attacker capital — the only resource AI cannot infinitely scale.
Will this actually slow down AI attackers?
2
Economic theory + our internal simulations show rational agents abandon or slow down when marginal cost > reward. Attackers now pay for their own telemetry.
Won't AI eventually find a way around it?
3
AI can adapt, but it cannot eliminate economic reality. Our patented model forces every attempt to burn real capital. Adaptation typically means concentrating on fewer attempts — which is exactly what we want. Fewer, more expensive probes are easier to detect, isolate, and defend.
Can this protect AI Agents from other AI Agents?
4
Absolutely. Organizations can assign controlled economic budgets or allowances to their own legitimate AI agents via FIDO2/device binding. This creates mutual deterrence: rogue, compromised, or external AI agents must still commit real value to interact with protected systems or workflows.
FAQs - Business & Economics
Who determines the invoice amount?
1
The organization sets policy-based value thresholds. AuthLN covers up to a $5 invoice with the subscription.
Is this usage-based pricing?
2
Pricing is structured around a simple SaaS model pricing.
What is the ROI?
3
It reduces breach probability and constrains automated abuse before SOC involvement.
Does this generate revenue?
4
It is a defensive control, not a profit center. As regulations evolve, so will the offering.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum id ligula porta felis euismod semper.