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
- de9ee61c25e2b47f44f3b5532239eade02b60f1495d4057581e9fb484b74537d
- request
- ec75f610525a054583501a8cce6137ea0c7793ed84a2e94f1e032df761732b42
- transaction
- 9b601240926b3f5878c954c9230f32567f3146e03a60887a506125bcda96a58ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1250
the chainentry 1250
- sealed to the entry before
- 1d0eab8b9d2a16fac9529cd53521b7f94666699302956ba4089f60dcd00a6267
- this leaf
- 6c24185daffd93aa6fc2af60b86cb6f37d621e8a13183b69690224b962c5a59b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C/lZKjxwzgo2wQoQ7BuHN8N0Kdok7P2ugyESF7PQAj5SejzYruiOZD2zRw5kWlvQ3GqWL9L5kWsuywv5mD1tBw==