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
- c1aa7adbf9a678de01f1e67b7d0063df424a00e98533dcbee1ab20e368c71995
- request
- 51391e06244146b0aeb41f3419f656a6582edd16580d85170dcae7c1cd75e1bc
- transaction
- 05008c8cec97241c984a1ac9d44fcd8ee2693d4da652e3cd798f840e1d163cd3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27920
the chainentry 27920
- sealed to the entry before
- d6fb58778b5e67f97cb5c266932427947f5851e45761388ecb8f7e57a1a7eba2
- this leaf
- 4482eaeb04d2747246ef2435c8a7c8e3f966d547b5e883e3c2dc98e46ed7406d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ANI7n1V0Fr+6GwjRjG5ZUtibnHN4IO+hurmEluHd5GltHbrH1htVDnnCNgJIblowV2sve62eJODeDh/fVH/sBQ==