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
- 14b6cf5ed4df9237c7b8995db72a6403f8a78ca50f74913fa200ed7a11b4789e
- request
- 23e0c3c1ef1a2ba1f1adb53e39c737b7fbcbd7f29730da090e50dcfe5ffd3ec4
- transaction
- be1b6fe08dade905f11eaa27e098a9fc05bb3a2703fa04af3c79f59ca7a608d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8860
the chainentry 8860
- sealed to the entry before
- 50e60079550e6507a2a0ab5d3b96ae4eaf8e2645e4dc1fea869fbb029acc0227
- this leaf
- 15108a342f8ee0e0ab8f22ba0b7a19bb8c61d32a5a41243f45d7aba6a62c2063
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ktykpl4G8jT5ZAjL7rTblue5bVQzdNHZF0JRvRY+NK82k2KI6DlWImDGWe9R4Lvdq6REAimhKW5wIw1cCG5oAA==