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
- 7cae3cc52b6298ce25297c4e3dbfd766b7ec27a98320ab2014749cec29f5cbc9
- request
- 75aaeff936f8816ac73d05a9f1e8a65c8fb8c6314a122c97a7dff9a7b367c43e
- transaction
- 0fd941606fa56977599913a722582aac205382b7e757bcd5d749bc63b8465f2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44920
the chainentry 44920
- sealed to the entry before
- 3dc8cf338ee02098abf2bec2268000dcceb909d11c2b46de4baf81b7c04adc0b
- this leaf
- 4cc569385e392b6c0a852e8a41f6d8d0197549c9a26199bc2c20bca2c48c4894
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GNUDsrTLxxWI3oUbo5RnGQEkj8U9zEbXQfWwYCvPogzG08XL53U66SrkBCFcKpv+wC2wLSyrsrXjkXw7OQQEAQ==