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
- 01df1b8d15af1504058b2b3e3a760f358dfb5db5ff84f58a36ad8643deff5d80
- request
- 34d88e498f5d86ea16fd598ba0993b678b77423f17d79e0c8cd93670f473e926
- transaction
- e55ff27a79817476e9546755771eba9a39647383789ac64a2f9b43657a2989bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60035
the chainentry 60035
- sealed to the entry before
- 4da418c0776fe980803325992cabffe4990b84f023a85bfa10b90522460dd9b0
- this leaf
- 5438f7a54e631cde466a4b0193dcd95b0ffa145fef4d780cbcb0d08ffb94cd22
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vaGs734SQs86Q2cS94wgtAvqabSe13Hd0SE65UN4S20GNbJQNmvB8NrOIUdRbTszUYLS4+zUUv/hlsSyZuHaDg==