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
- 2c61a38d9987f6be68a0eccf51d9d12cfae100381b7e473502b2a10cb11659b6
- request
- 98c6233b8acf1e97d56cca3530d51a54606a9c76758d0d6d3db6dad1a77d26e3
- transaction
- 77c668106d962cc0f717bea6b0ebcdee1cd29a356bb0fcbdc2bc3560c129dc95computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 226
the chainentry 226
- sealed to the entry before
- 62baabbb24bc987d84d1bf7596ad6c19832216d03ce42b5df8ddd52e772327ff
- this leaf
- e8cabbe1079ee0b9ba4a5afc6675eeb178b2a5fd6a75ae45fae08500e45109c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bmhKrlUWghxj9kCrbAMD5Fa+/UjAri9RejO6eU8+U2ZNaNoh0evbKmVJhhNITK44MtUXNTFzoL0hUISCnUjtAA==