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
- 2338984ef3a33f41e732a793b19b23eb6d181b8612dc8aeaa11dc14bcd58b95b
- request
- 61d6fa5b9d45957740d29597ceea2a54d57590fb488b9c9720bd2263f8b55fe5
- transaction
- b099e2197da8b02034465dd428c1980c44c004ce096a3d7cac94b42950632005computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1018
the chainentry 1018
- sealed to the entry before
- 07751fa6ae0a12cbea31cc27c12ccd78a65f0e308ea206ca83bf774597041863
- this leaf
- a4f7609d6ea7e778b30d2794450173993a1c1803d15cd9d003463a10f2636083
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vpPXBCPiLS+b2WzFlM9cSKb+rPHjouSnRGtqeZKzrwacppufvTgDPkOZ1cqFhAZ1noSxlPMggGjsJi5803fnCg==