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
- c44f8786182fc3807e605ce7ee507495dbf14eac97e75fad0ea81654fae27d06
- request
- 57ddcce62fef36ac74c00c0e42c6e011fefa0ec809626510d5ff3d15d642e50f
- transaction
- bc95adda0c0fdc4d9152750fca0359630c735cd6ebd70a46bc8de0cec4278312computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30491
the chainentry 30491
- sealed to the entry before
- d5a2a2d54271105a6f07329ced95e48d5506252d0269aa2247faff595f9f36c9
- this leaf
- 3ebc6114eff52ba9e6d0385ef37f12626b3904ad3da6d7b957ecbecf3f992d2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PYMg29k7O34Uoq660W+UQA4e0gOGTfoBC3a3PljTKiok2/DiPJXh5Us8SOnUXn552Z4NXUqwqLQolpc/xOIfDA==