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
- dccea4038882e78502d852a7dfa9ef5ef7913839649d86cb8a912307fbf510aa
- request
- 9e99d421117ad465ccf8019bd5f82fa1f3a3df0bde893b854574d32d44307835
- transaction
- e9c7c7a14186f7eac7d64d40a5a46c6f65ef351683ecd69b50463b8667bcc931computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2035
the chainentry 2035
- sealed to the entry before
- 4957d0eaad1112d7159a6f952aaf982f00a58a68720ffc035be2fd79042bfd38
- this leaf
- fb845e58aec144fa27c0dcfd8527000147c995edec04c213e3f8bc940d281ebd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o8tdE6koMqQfsw6VbgvzRfIzCpmeiGbm5eYlmgbJGzdA59oVa99lpxcislJtede9qwbn1CueXZrpXjav4Ro1AQ==