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
- ec2fe232014ab71fd2785a2a95ee7d5bd91bb3e558e9a3afdf3a269ec9550966
- request
- 5096c181c8a7e6a8dfa578cd25750c68f15114c345a5081c3e59b10355bd0951
- transaction
- e5cf9c0e09ea3e0bc011c0284d52ff200b77fc5f8f52fa1e7c489b7ac366297ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35706
the chainentry 35706
- sealed to the entry before
- 20343bad91a0aaf43384d991c23639419a8418575313a10c4a6b1c07d8abe704
- this leaf
- 3dc228a668a9a12d9e5fd8182cc23c3a0bea1af49338f4836db127b17627a1a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RoVDa85aPmm44N/C3Ew0WA8wPxMWyR/+LxQd1MZ1HrOFo3prisYP4PPMB8+qZrubPNAhNlRjYQtv7LbimLTqBQ==