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
- 67984a7aa2d8129acd9ac4840091c8178bfbf8361c2d26881a608fd89bb496b1
- request
- ceb32ac707d57b354ac84783ad60a50bc1a0deda00891ff3c936990330fa3a3f
- transaction
- 172764dce27469b525e28c694cdaa4b97099a4695247f942d8ced0929453c2c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55065
the chainentry 55065
- sealed to the entry before
- c1761997e11cf50279186e0ec5ed1848787404826e39f14f5933570b1e66c3bf
- this leaf
- e4d041b889ac94688f3a18514616cb121427b5e39378d077fa9b665ae4f7ea02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JJStNAZ0P7bjkvnJJB+R97ktrgCM8hQ9xQAYXSjOugCvfRMVSIFrklln6Uqc1AAz987pAMCWC0KZAVpcc5ojCQ==