Nekuda Payment Executor
Run by Nekuda
How to detect Nekuda Payment Executor
Nekuda Payment Executor signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Nekuda; a copied user agent without the signature does not.
- Detection method
- SignedThe agent signs its requests, so its identity is verified cryptographically.
- Signals that identify it
- CryptographicA signed request verified cryptographically
- BehavioralHow the session clicks, types, moves and navigates, checked after the signature is verified
Every signal Verisoul checks for Nekuda Payment Executor
Nekuda Payment Executor signs its requests, so we verify who it is cryptographically, then check the rest of the session.
- Used
Cryptographic
A signed request verified cryptographically
- Not used
Network
Not needed to identify it
- Not used
Device
Not needed to identify it
- Used
Behavioral
How the session clicks, types, moves and navigates, checked after the signature is verified
How often you'll see it
Very uncommon
Rare, brand new, or not seen on Verisoul traffic yet
More from Nekuda
Questions about Nekuda Payment Executor
How do you detect Nekuda Payment Executor?
Nekuda Payment Executor signs its requests, so you detect it by verifying the cryptographic signature on each request. A valid signature proves the request came from Nekuda; a copied user agent without the signature does not.
What is Nekuda Payment Executor?
Nekuda Payment Executor is an automated service from Nekuda that signs its requests.
Does Nekuda Payment Executor identify itself?
Yes. Nekuda Payment Executor signs its requests cryptographically, which is the strongest way an agent can identify itself.
Can a bot pretend to be Nekuda Payment Executor?
Not convincingly. A bot can copy Nekuda Payment Executor's user agent, but without Nekuda signing keys its requests fail verification and it is not labeled Nekuda Payment Executor.
How common is Nekuda Payment Executor?
Very uncommon. Rare, brand new, or not seen on Verisoul traffic yet.
What does the Verisoul API return for Nekuda Payment Executor?
Every session Verisoul identifies as Nekuda Payment Executor carries an agent block with id "nekuda_payment_executor", name, provider, type "other", detection_method "signed" and the detection_signals used (cryptographic, behavioral). Build rules on the id, type and detection method.