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
- 1cdf2fd40a0c50033140f5c978a3a44f08639921848627c4fdec4c288afb9daa
- request
- b24ccbcf4e7d91a5999b27b956e2fe8948b64bae4b8389aad37a61a894e2db49
- transaction
- a76b74342e0c0c758ac2234d6923339119122b0cca0efeb6a3381b613cf4b732computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62702
the chainentry 62702
- sealed to the entry before
- d738411a7a26f6dd610700ba9ed99fc8604cc05494d824f933fb678916f1bad8
- this leaf
- 1b415630ce0b32735a292d98e2ebde6d7d4eaf4755160e765178e0ac89346e28
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eW+HCaYmNGEMJPnxw0FR69wiREkS69aGK7zCptwzkf7TS5MW2UkXfGhUf6enN9mH5CkpgSv+rAB0iVysRAS9Bw==