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
- 39d8173b0d4b61f45ae210891aca81edbdc2b4ab144fdf2b6f794eb010124b44
- request
- bfa2671bbe4e712f167df9d0890219f563bc20fe1c5240a37d4fc04823174373
- transaction
- 2f83c3b3b793e1b05569c835153d5b8d26ffd0b15ad0305127db2ebf0e9ea1cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38343
the chainentry 38343
- sealed to the entry before
- a0596bcfa1ecdcbd3538ef03de00901bf5bfb1b5e91c64b45804b918b374358d
- this leaf
- 58a794ae823ca5a1ec5dd8453819ad2aef6439263445d44811bf2422f816237a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R7EFQFkZZzGgjF+M4eep24ov7/24J7RQMkbQQ0y2Bqpbh5NyW2SEtsyfqP7pDC3Gtux3WlydYvufQEfpERz5Dg==