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
- 15cd0d56a38b6ad3c4fd8af4fa40e5d590a7b6696b280949a1908b0c14a66be3
- request
- e95498d3ef95181e3cf20e32da5d9939446ed12fe2069169e8783c5aeef6d30e
- transaction
- 446efb3f141c0cb153218a2692ec585276f63c6f3bc31ad58f90568bc2ecc904computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3461
the chainentry 3461
- sealed to the entry before
- 1a8f5e614143dd449b5fb8abb31416fd794ebac3e4457ceb2f0e0f2a12e60135
- this leaf
- 6f683579698b1fefe3ed297f6690f7a5cc3d8e6219c851915f8fe6bd007eb7c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KG0Avph/ezb3mu8n1czMz2ZJgIvbX3VpMq/ecKv/05jYZDmCa0TzhJvW1JX7i/YQqwt2H+KdWeAGEKJ3OOsiDA==