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
- a24fc5b35a18c52eac73cda4052253e2bea62fcac154643b02195f783eebe191
- request
- b4fe9551a407a039435b9914eddb220309407a45d95631539ac5573113b13499
- transaction
- 06d15fd62de229db8412612c301514b6fe25fb0d36edfb935da06003dfbb4a7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26240
the chainentry 26240
- sealed to the entry before
- 24b9cac24a2170f8ba455788a24c545cc0bc0a18ea4da6be2ebaa37469a19c76
- this leaf
- a2d5dc1f709d134d143365e111e438738f8c364d164176ea0696013d50bff317
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zzw8g3VDfxRc/HOjPkWv9MyB0u4YZUKveTx0R2HggN8e0m0xjshAslKIBeNbKlONmJ8tGx48NEafFMRJtCN3DA==