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
- a814dfa5e40a746cdec3ca9a3638885234d6163278af643c00e69483efa92df5
- request
- e454877dba1bbfb7a50688649679a49227431a5250622246ad3bc5e58f912be5
- transaction
- 37d780e9152ed4cf8ce19065f26c5400e86c905becbe44778a13ea8caa0723adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21875
the chainentry 21875
- sealed to the entry before
- 67bb1b2043618ebac80c85a84c6474f954fd7787ed7e2cd9829969fe75f5a7c8
- this leaf
- 22cf09d079940956b124b986038d18a09a103f4262abbeec71d3e1aae1edfdff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DK/+MA7Hx63ADzuQoAAddiOuLWyPYfGjnaSPQmGoLeGp1jq+82135wTmVPKGNdR7GQJCCMeHr4m0FgO2JtJLAA==