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
- f992b9e159c71ecb8359fa160f4685b39d805cd17919cebd6c1817ba259416bb
- request
- f3287570360fbb3627b65c99f45e0b97c487cb82efb68be9815b7f5fb20db63d
- transaction
- bd9c37fb340fb92fc2e401364db6f1ef8b127d6e944c84872d2085235d77c57ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28902
the chainentry 28902
- sealed to the entry before
- 6acf738274e4b92171e000829035d3d2611e33895fdea06ecd168702981d9d8f
- this leaf
- 7b928966bde604b872ec18e443e2a6e36f3e83bd3906890b7be922c8d3fbea80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OhtGWf20Lrjg7N63ujUkNxxZ64lCItd45k7w9WPoizWk9orJP4wK7buhxPN53o9CB800BFOnrDmZPUCUq+71Aw==