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
- 4d1884daf6e5ea7eb4bee9117c82cb48aadff595e5fc96744eadf4b24d9cb906
- request
- 31c66cc8c4bde63583dd3f19e9cab29a28331d8189f6dbe31e08835f14c034ff
- transaction
- 204633ebecd695380561ce9334f8667054642a9ac0119236b321f353549e413acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23433
the chainentry 23433
- sealed to the entry before
- bf6a62219cd68ac50399fe9f0d3a169e34860c21f7d0465ceb3456a96b61135d
- this leaf
- d7a857f007fe7a334e43ae4daca3dee16fac0634031a451f631a5293ccff2b2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 60QpGATT9uJD8FgUzAdMlcz8UeWrqXcMqZmJqwR99IjMKqm/tLaSsnctrtJeOqORTPEEBTcGV3Qbqz9I9GlpBA==