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
- 5491e601a8faeef19a1b1fb65e1043804e9175c40017bc7aaa3f9c610d7d4f05
- request
- a6955f9e0542f894f52ab6ed002d3b9a61f56d79c477b221ad125cf225263e27
- transaction
- 339d47797112737e6294b8c90feeab9635e5df917efdb70285ea11c30a2f076bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56284
the chainentry 56284
- sealed to the entry before
- c7dd2a6986c69a1df56d7c613b92a93847855acc93be929dc73ac72bc36fd9ef
- this leaf
- 351231ebc5d3b7c28ca1e4182be047608bd3b302be84758934f4b4a20d8c6d2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nkyyhh3NM0ek4kN6t0lEaa0jWD311BttUeJs4+tVOd8mn3Le/o7JiIJh1kgnP07emY8VIgDv8g+C9n4eMMbqAQ==