FAQ
Plain-language answers to common product and integration questions.
Does TxnShield replace authorization?
No. Your app still decides who has access to a capability. TxnShield decides whether a specific sensitive transaction should proceed in its current context.
What should I protect first?
Start with actions that create irreversible risk: exporting records, reading customer PII, changing payment details, changing permissions, or approving financial actions.
Does every API request count as usage?
No. Usage is based on evaluated transactions, meaning protected runtime actions recorded as TxnShield transaction events.
Can I keep using my auth provider?
Yes. TxnShield complements your auth provider by consuming actor context, roles, resource context, and runtime signals after login.
What happens if billing fails?
The organization status can become past_due or unpaid. TxnShield preserves data and restricts premium entitlements according to plan rules until billing recovers.
How do I contact support?
Use the contact page for support, security reports, billing, docs feedback, or enterprise sales. Include organization, project, environment, operation key, and event identifiers when they are relevant.
Is TxnShield certified for compliance frameworks?
No certification is claimed in the current product surfaces. TxnShield can provide transaction decision evidence, audit logs, and rollout controls, but customers should not treat that as a compliance certification.
Next steps