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
- 42dba29bf46af7d9cc963428535fedc00fa9e268ab31266a54702dae605f3090
- request
- f080108b59d3c4de9ce9e0bafc1e316d331562b8689bc5a2bd604ec0a174ff33
- transaction
- 64c192c58101549127f92d499b4ddc00ebad48f17d0691f17af5313dfe7bfc65computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4472
the chainentry 4472
- sealed to the entry before
- 5164b968fb444e4d51a552171f998bd995766aa11583aea887bca68293eda588
- this leaf
- 13d772bca94d9e2e02014b184bdec60c2972fbb86eaf9218e29e2bfa0582bb9b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uqI6FfFL1pKcDdRu3EB2WUhU7W9Gk3+bHbGuCJz4bpuixrPOGjiZKPkVMRQSmW++e0IDRMuRafj6G6JsMn2RDQ==