why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 8594d441a1c7ae6a78e5950b9e3fd89d018810fa9797d40436a56732bbac352b
- request
- fd9a4e4863ee00ab4bacf16aaac7da87932d86c6ae207e643760b51cffcfc284
- transaction
- 460b4b815468de4470716d6b5783915cce997cc158f0576fe417adfbb4ff974acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40042
the chainentry 40042
- sealed to the entry before
- f5117b2f182d8983167db55f01beda112f4c7f4f72820cb33905d788430ef1a8
- this leaf
- 61fe321d21a760eacfcec21d2d8252476f49943c4fa3a31f480c453f5c37592f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- djRLtWdEtYLAEyIVLfxBBLg2RRrmpVRWUmP1ljFDIQxvuj8W0+oYURRMEMNg3k+Lya4tRhfq89MUWfioS9pDAw==