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
- eaf52c9e343785b990162ced2bead37f5260be12ca649188e9791825c29aa0ee
- request
- 4f34c16ad915049752b1f4f46ab0ff27892d6a5de441d7cd5d3c4cb7fc7baeca
- transaction
- e601332ed98d714300a432f3f6f26eae4401eaac549d34cedbc6ba4db3292958computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55081
the chainentry 55081
- sealed to the entry before
- 8f7cf7d2051de1cd49f83e8a84b3924280ca414a26e239639fe36f191e54041d
- this leaf
- 4f7f725a6b4c00c8ca406c6fd57b4beced43381b8edd21b92dc8fb55783d99cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wR6iabpzK2YNX29OLHOKUKvQtAg4PPcC27jbnDagurCSBT7hrdZXfRDy19BnaD8WaWP/U4jPGZiby0tgWlmVBA==