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
- 0412096267b0ebcaee5943c99e04989ad5d17e7f7aac6ae6b5e769166f98b3f8
- request
- 3015017056ef95ce7b9f5c9342b032739ee649175fa6aad1da957d9bb8624b0f
- transaction
- 1497f99f20d5d550a923cd9ce40788367b4eaf3731e257823ed3fb4be35be248computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9149
the chainentry 9149
- sealed to the entry before
- 47796b78450c31815e29949297d33f0866cb2c4daad5acdfefd51e74bce0c2d6
- this leaf
- cccd04def1164969345e5ee91102cb00dc8c1ed42c9730e35e47a29b5fc3948d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZHkeFFJQIQEV2p27la3ktlksx3nKuUGSgd6SD8MUhk7Iie2z1IV3J/Y9663syN2fq19b/pctN7q3uiMhem2aAQ==