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
- 5a23d7b7c0571b03d54105867bde0c3f7abfd0ac9682e77e710a6a5ed2c76e23
- request
- 02540dc234de794ba840725dc0bbcd50ecff3494a541673aad711bc4f777ee52
- transaction
- 43967289e8f32b3c831550857dcbb751579c688056dc2ee577d2d15d5e706e7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22494
the chainentry 22494
- sealed to the entry before
- f0c6cfef2f92b1978551463d7c9792de13406f171cfbea07c15a9042235f1b30
- this leaf
- aff5af4af9795e565c4cd2a0a2da632b198a8f932c3c4239d77a4577d27c947b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QVXEUTexbDvlUjyooutNf01NsSFVnDda4FmlgcJe5xb2fyvpxxHXH3sKAxLU+1RkmYsCE7OR2RkycUDz8xqIDQ==