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
- f31aa590a465f28915a8a2ebc867ca76221c0dc46609afa55386c466b6fa6d45
- request
- 796af2067b5d1e1f00271aac27b8408dcd45cc9084d6cf5f52c00cec2c776f18
- transaction
- 76c1cb1c4971b955271e48bf6fe23fddc5b77bb2ff49484029597e720d6a9034computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23954
the chainentry 23954
- sealed to the entry before
- f9b64a3f97d562f6928cdb7a8da8519eebc2330dd7a38c802e08960f968fcc9b
- this leaf
- d55c0b9ca17e4efca1f47944b6ef3c61f3ca7b4b3ced96e7a07b5b79d0c37ad1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cD8EC2YVQIS3DQPzccY/0qjoaqjgJZSbBvsd6pvlPdEUwih81KQhiVid0ExIjL/FUU7OrfhC9fE3lUDPjCaYAw==