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
- bb24691ca685b16d720b0dfcb1c72e397064d3c59c96c3613853cb968d1b0099
- request
- e0976b283ae1da8d8acca1495a729377a0290184852a04d375a0b351bd748a45
- transaction
- 88ff9065c169d441d53eb1dd7883907817aa6071b66cca093cd363bcfaede531computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31129
the chainentry 31129
- sealed to the entry before
- 86a2933589e72aa33ef8a98718fd69ae5eb29baa6f2b8e0b92a7bc06551bef1a
- this leaf
- 50c54c69528e9f83d480c4ab7e3ba96f688abfd25eb71f41768905b906da4fc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PLsNl26b+t7UPbZm7QEVK6glqvRvKdXK7LNwmS0HDopeFpr0htmjbyNm87eNbkboZe0Pqh40F8vKCQLe+fWxAQ==