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
- cc48dee38dc4abb1e35a0397b60ba9155e6f8597900de92efd0a701c2bd45a81
- request
- 0d1f70b95ce1bf4b82892353585880ccea9f58b2004a165297dd1b170a357150
- transaction
- 12a885c0ea366497fb8befea37b209e055af938aa9d11793a8295fc060e11e2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67173
the chainentry 67173
- sealed to the entry before
- 588c5206cd252a8f172d677937ee33f4412b321ea77d5943080b92573304d944
- this leaf
- d4798c7042d158704fadc3f1722727df2ee156c6b785b3ee3e355a9dcd64a5c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qvh+2b2Zt0aObdNJSPRHWphQOUWIwhKxE46arqYVWNAYzKPTv0TsfDry6NNMPcUJQmOvOBHy8YYWZYKrDXEABQ==