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
- a0761db6e1cd7f6ad22a6177366ced278cd5c364d37ef270f61e01ce2a488bfa
- request
- f1a615b071b511bbda7bfa2590598a2faeecf91bad417494bb516501c69aeead
- transaction
- 37842b6232a7ca63730f9a3d7e4cd2cce48fdfcff1bf397373f9eac4855ef13fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46672
the chainentry 46672
- sealed to the entry before
- fa383b3ebc7297e4bcd76b1901bc4ac6ca8bcf861806b12e83d295cdf118dbdf
- this leaf
- 287f21fdb979959171d46053f1345618228ed1ece60a68dae9f4960f0cb57a44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +GPW//pcRc/t73CfdvZYNdM3SuTzTSHom1vu3fLxmcXZ4zVwFuNJs/z0cJNZROvlhQbC9eMFqyJWaZTEQqVSDg==