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
- 21db613ba1c1fdf19238c6ebfc75c36f0e7c33bce0ec07ccee0e98efa2871354
- request
- 6e913e8e73a9604d2b10d575b3a4cd02f5955697b071968efd0c22481aef19d3
- transaction
- 6809544d402178f74b94b20eae1658a5209cf60f7f85a7f20a625a3d23fc5b18computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53915
the chainentry 53915
- sealed to the entry before
- 2e218c7fabbd74c29eea167a7642ba9caa423fcaf6edd030816fe1c9cc8f2646
- this leaf
- 909914e2a4557b46e34499d61c955039c754c9ff237fd1645c3f0171ffb0872e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v3c9piTK8mYJxi19v5sQb/2MIEujOK1VpscaycqAarO4bCTDiCRTpCWAHlrCj4mai/W9A+fQXDidyvfpmHQKDQ==