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
- 564c1955124a851c44ef8f0afd353c197dd053993c8989556a3378c7402a1f3b
- request
- c74041e06dbcb60a6779d56120b4ca3420d9e038085f42fe331385fef82ab87e
- transaction
- 24216070b7e36479bd1499d06eac683e19b5202ffecf2d42f853e860c47ce9bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28203
the chainentry 28203
- sealed to the entry before
- dffa3f06c5b641ac57eec3c5430eb3b1f827dba62eccacdd32491e013539b74e
- this leaf
- 59b8ea9572be9e1f504c24da2742c9cea2ec4acecddb3736a286950ed5da9cd5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oU+DLzh/Z5dm/H7Y088amVGZltIy4Xr7sMJNyLCZLEESQpUiw4kuNU3/S3PDKcrsO0SGEcIVq6aeNAGVHpyoBw==