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
- f1141a6b9c64cd69fe03dac0dcae35b14c3f772c21c94d3e9a79e3df7c65bd27
- request
- 71fa90a2bf8d66ca38898f82113ecc143cf32fd12971606a822e0fd0199196f2
- transaction
- 00a813564566ed2eac94286bee65b80166cacc82b140efe99eaefd2b3be8e67bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10135
the chainentry 10135
- sealed to the entry before
- 8f4d8e35123e96b5df1b963551bad3f28e0013605a0afbe1b927b866922aa4a9
- this leaf
- 70d73b5933c9cd402a94d58a8e3c334841ec5bd2147c5d5e73f5f2760c75ee94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u+Bx7vlEEuMUaItsACkIsvGMgBqryMSTZwdragpdow+otYokcKk1IsRXPQrJYgzWAbSp8wSM7nAoyCDMCs4qAQ==