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
- cf5d70553e5878c57aac8dec14e67d82c3d11c08f046522cbca89ac495db5451
- request
- 450389420b45eb755283fa8271efbc634556d4609976ed7f8275d5a8d25a401c
- transaction
- 99c1d578b47fcfa6c599c56c82c9c289e111aeb88b39e998b45099458566d7e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34025
the chainentry 34025
- sealed to the entry before
- 6c035c9fae2cd070b6f525ea2373e11673de06480d241f2f5c6bab33ece3bf11
- this leaf
- 04c1857aeeae6bff9f8b9be8460a392f1733c9c85f7c6468f4a9b509ac88122d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q4h8mV7hUrDxv1Zn0yA2fc2QmM5xUEf0cp4AVeDxMm4ZMw1NG7/JH22yn8kZY13jL4lO8nldnEdB/pGxohnHBQ==