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
- 99b09d4d0974aedada0ca5898162625952701d4b6dd9daa7edf61ce32234a7fa
- request
- 2f4cff6c57aa1984814de1cb4e467a5efde04a1a1f54bfbf609265924c6f5b75
- transaction
- 93d99f72d7d43fb2d05491c2ba929ae41a12c78bc761a92f69f36ceffa518214computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68674
the chainentry 68674
- sealed to the entry before
- 064999fe783ecf4a9549a7b7bc20d443ccd6d3a7e3f03218d27a5acf4610503b
- this leaf
- 1da156dbc7361670a7efa5e642d83b2e6dd641049864acfaea852a115207c520
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LN6UvJPsFtU9BAzpJ2RKy2JF8frFo/pZRcKWfCsUKHSjM5DG8hHYMb8D+khGGj0JjXoMB+Yx04QbqabM6UXzAA==