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
- 4b90c67b1fd68b1091e2b258ca8c4c7e6609736947a2f9bed080e7e213617624
- request
- 36dc72776ba5666ff8fe8f7edb287478748ca4b65f59b7d5b06e96693557b85f
- transaction
- ba48fe8f028d9d2964da044184bc564793eb9a2960fdb9c9278a2e2df515571bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36293
the chainentry 36293
- sealed to the entry before
- b88136a28d06012f300fa8b51668e529c3048b86a555fda8af205004a9b72eb1
- this leaf
- 1990e87e3435b50294056e066788126316f715156f1d7d6db6a5e15d9b9a512e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jgECS6tGfFwq++JGEKYsGdp5UlabuOBGGWDnO2dg0myVArrJPTWCPteKktLmjmGhmOW/ZqebsdJu2TCkwLlGAA==