Secure high-value transactions without blocking every payment
Not every transaction needs the same scrutiny. Authsignal's rules engine applies step-up authentication based on transaction amount, risk signals, and regulatory requirements. Passkeys for high-value transfers, invisible risk assessment for everyday purchases.
Step-up auth at the point of transaction, not at login
Step-up
authentication for high-value transfers across 200+ countries and a global user base of 50 Million.
Passkeys
usage planned to be extended to high-risk actions like transaction approvals, building on their ~60% passkey authentication adoption.
The right challenge at the right transaction
Dynamic linking (PSD2)
Tie authentication to the specific transaction: amount and payee are cryptographically bound to the user's approval. Required by PSD2/SCA for payment initiation and demonstrated to auditors via the audit trail.
Risk-based step-up
Define thresholds in the rules engine: transactions above a set amount, first-time payees, unusual locations, or flagged risk signals trigger step-up. Everyday transactions pass through without friction.
Real-time observability
See every transaction authentication event in real time: method used, risk signals evaluated, outcome. Stream to your fraud monitoring platform or SIEM. Investigate incidents with full context.
No-code rules engine
Fraud teams set and adjust transaction authentication rules without engineering. Respond to new fraud patterns in minutes: add a rule, test it, deploy it. No code release required.
Frequently asked questions
PSD2 requires that strong customer authentication for payment transactions is dynamically linked to the specific transaction amount and payee. Authsignal handles this by binding the authentication challenge to the transaction details, creating an audit-ready record that the user approved this specific payment.
Yes. The rules engine supports policies by transaction amount, payee type, user segment, geography, device, time of day, and risk score. High-value wire transfers can require passkey + biometric; small purchases can pass through with a risk assessment only.
Yes. Authsignal integrates via API at the point where your system initiates a transaction. Your payment processor, banking platform, or custom system calls Authsignal's API with the transaction details; Authsignal applies the configured rules and returns an allow/challenge/block decision.
The rules engine evaluates multiple signals: device trust, location, transaction pattern, user history. Trusted patterns pass through; anomalies trigger step-up. You tune the thresholds based on your fraud and conversion data. Conversion analytics show the direct impact of each rule.