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
- 45db8034844926186dcf2937e1e54ffaf0b48e1c63a5fdc80e951ae776524ab2
- request
- 155d0d6b8af50fe40b1e7f06a0990d5ba8b52b02ceae540edec9a0c7d475909e
- transaction
- de1845ed6b1d5bb45fc45c0b7a6f1ac4efd5db107c48f1bed293ad370de816c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49330
the chainentry 49330
- sealed to the entry before
- eb3ec95c5751b110ee6af89b0193d22059d46582dc99c79f37f5f73eab8d48b6
- this leaf
- 89218e003a259af60812bcbf3c7a9aee38ef1ed1fc891cb9b921c6ce6c7174a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ygzN2upZzY9J7DJSqNyvcx5DRTiM1SOb8OYtFcm4oDPFvKVEjR6kehJiZEuAb/7MmiGPiVdkDf0Pd1hCTiHKAw==