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
- 0499111b504fa9bf37b79b07b3ae7439a7663ea35e64bcec5bd5f01caf066105
- request
- 6b39e62ae583d78bb271c61b6060eec174504a5a5a9ea13af4a93beaac5444d7
- transaction
- 7f9af90d53fd4de8e6fc85f6613b768fe33da4fb0eca74caa81c55f5194850c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42290
the chainentry 42290
- sealed to the entry before
- cae0229a7d3b26d3980c1925b57f49723d1e83b58c7b19de1be0b9f8c4344034
- this leaf
- 991c74866bcd9953493a501d320eef16c5572b6117110bf9a1173480efb77fc9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3qMdVRN7lTkGQog9kLjSArwSM+CjQ4/3yj9IFvLew/lc+p7wa+LvrJ+0/k/NjPlDLg3np5qPyEeoUPr8J2jDCQ==