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
- 34bea5ce43b2a21a294ef0a3013a0c98a83ab87d19a481a741da327b43422137
- request
- 6c34b0910c4dec460f93c646dfa2684a2424d41df5e603275ece5c517a8bfbc5
- transaction
- 9653bbe4675924144b04aff337e1977970f25bb678ce4f2e4cf1de6c63b37d14computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51216
the chainentry 51216
- sealed to the entry before
- 1a1a1820928f1bb9881a8e611c658465fea95e2b74bb28aff07228d6fda828e1
- this leaf
- 81b2c57c4e815da91e72843f03e3642071b28a233c36f07955fd5f1214a9eb8e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nxb+Gf+Wt2d4Vetn67bwmTeX95Zssfs85xyeR9TWWk989aSZJPh45vjaarVR9C9b1sQ8mH0cE3ej1ryh0np5Cg==