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
- 374de6e59307cf4bb25554581adf5588a8a33d99bb7a987a2fbf5e04682f0c0a
- request
- f5796ab8dd095481c82ad8c75504374740a0fd0c5977f0481e545f4829afbac2
- transaction
- df72be1adb02bcc14105de02820e3b55952a2eda5d6049d466692bb0e14a9a7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63610
the chainentry 63610
- sealed to the entry before
- 16cbc8251a87202f9584403260fa9354106ba756f5d03d3a2091b0a96df1839c
- this leaf
- 306a4864dc1e8c373901ef0b9dfb6a89af7fc6d9ce73fbc8be99fab9fb96725a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JSuPF4PWVcoxL6ebjvnWf/02ijQgSUUsIw3rg1XKD3mo50v9aubbTQSHyzLRc6JmaivbBagzbU2pTN7dGYU7CA==