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
- c008f9efac750868c0dba273940c0eabba6965b79ade3e4ede3af9036ed54273
- request
- eeffd79594ddb36ab1793d3226ef813e87b225e27572d7d6dcd38daade659a07
- transaction
- 01818a05b429d9030e1db90a263295d78977a8fb688ff018538e350400973b27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63220
the chainentry 63220
- sealed to the entry before
- 950a59e43a870f9f0ec9d0beafa8ce644001e704e845de8cbf493142a2b5a03d
- this leaf
- b9c08811be0e8c88ed94927a0370a5df48650bf54f23b272a6693b675c7bd488
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kqgPzvWeR4ZAh/1OEkemArDoxxn6xf5Oe7WWRwl/vzR6Cmo5Y0rbI8WFIvwuKMPPUGruOjOblbbOu96VA/juCA==