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
- 56bb90c5dccc097edc905b5cf05410c720915fbcef14399b768b53916f866c0d
- request
- 002ea92e55ce651442f919ad326fa81d0bd037fef53edddefaf63978d9bc024b
- transaction
- 6b55a9877f6c8f6bc90fe7da17c3e7aaae9b60fb37a626f2358478864b706ba3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41165
the chainentry 41165
- sealed to the entry before
- 2e67d1e2e308494a27b6814c87b1065a14f6de9963bc6e65107b94ad011637fc
- this leaf
- 16add28c85968e3decd542acb09aa44e10121f1a670aefe12191004463354f63
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UEI454ZYSfila93GSwJ23iobSYIdF2ZwEG4IMVvA2bWse62g/+RD3YoS8G2nqjZziMKuAWmuLtihdSGdScI6Ag==