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
- d436024fbcd81bbb39a915754e1f27bb428f318acdd2274a44027c344b61d993
- request
- 179894d44164f826299b3160d9eb8727605447ddf57ed7ffab1904b785205b3b
- transaction
- c2384b03ae23fbb06d7d3a0422355b13c3f459923a7acfffd7cc71d2867168cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20225
the chainentry 20225
- sealed to the entry before
- 3df2c84e354f81b2afeb492c72bc6a6ace6e44cd57671ecb35724767f15f1933
- this leaf
- 661cb12d83f6a55b180645366a51670e7338f9c0164881632fee7384361d9394
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GKHBl1HoEyXZ41go/vLuvXS0OVYqnzeW/v1ACtlWoVmKou/gdwEGFSns1DO5DlhRu19HKEMzYgNwPyvCIrNpCg==