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
- 42da354a452ac0c435f4b2422cdeac20309be17d848ed89ec723945706822951
- request
- e82fc2cd953e1f50194a6bfa1020e511b6add4697189cb269b260f05a0a8d6ef
- transaction
- 7de5e1bc790238590c551b2a65a4a30d71fcd46c5aa60764f8d1aaac28d24726computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20446
the chainentry 20446
- sealed to the entry before
- b0582b09abb939abb000c74aa8c6a01f8b3f4829f1482772e2ecaab607e7af96
- this leaf
- bb95a54a0f1da5bb9da272b561a9c8ac06a8c660bed754766814504d07942b4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UUX3FEu0R1XDDEjjDHfRvzkUSP51zgFVXylJBmLbNid4fpiL6mounYMgAAweJDyHbDVOFjpT/DDa+8oZoQrmBQ==