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
- bf9e2e32452f67e0700b21ed179a29f6c16816ceb505fee9aeceda280f8ed20c
- request
- 66c04b6d31332e3f4f8ec5e5bc238e8a5c84993669b76f934fa7abc1448ba5b4
- transaction
- c472b62261001724c4f9a74a91eecc9cccbf5c93f8d482b404c41a1f9532dae1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29323
the chainentry 29323
- sealed to the entry before
- bc3f86f9d0c5b98030af3f84e61e196eae79a4e6bae33d05554d5b7a28fc3940
- this leaf
- 06b9fdfc6ce0653e6941a4399543d34aa9494ff027846ff91b305f4f5d9964e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Tj3L7gSP4/hcnKV1teHJzOwT7XH0C6UkU3wJo3KNfre9FRnnaM7tOT+KbfwS5Qg1pFa7l/FsiyV1pl54zJcBg==