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
- 253a66fc15f0cdecd92c3df49934f6fb5932c286a3f6e67e6ac8c0ff24499c72
- request
- 57a6f8eb3b9b22447af75aa39c6e35385147992b33dd9927207ac21201ffb564
- transaction
- aaab81c4939091c5ea2da5dcffc873429d973c0805e8b5ab8131a695226141fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60005
the chainentry 60005
- sealed to the entry before
- ed63e89f0a6a24eb32a222bec59f635bf9385ef99ebd0f0d2044da523ec065c7
- this leaf
- 689f5364ad936020705a84516498504ed270188d57491cfb39925ed479db74e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HmVFhjHJ7L3cYXdmK8iyVZioY5usRAJc5x+tKcBoKFQtbE3lEtQlrgFJ2CZEo8dViFDN+EqaXYHYK+qaiO/fBQ==