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
- 1a63e2ea012485fc1ac7b45c214691fa7d6e087cff5d6899e98e272320af29a5
- request
- 410ad000e2c419c7e5cfd90af2139867b50b410364fec1253691016421cc3345
- transaction
- 8fb012e90177dc50135fb51841fe68146930f997f06da5f18e14712b1539872dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13076
the chainentry 13076
- sealed to the entry before
- 141a353002d656f69fa3b4de2a38c997533d8a996f1e6f61f93a7a9f2ae0836a
- this leaf
- 843376caae811abe7379461eb3d7a5ad9359be34dc0be83d56f2995d8fa6fc13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZVEhdCrMOJ44olizlLxkCHsr/AlE/99WpAhvGRMXWnIAicAIozIHXPnhmqlR1vumruPFZWaCC2nbJRW5Kkk9Cg==