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
- 857df54d8f785514280e1fc26ead81b260059a395cad6b1f541e010a5d536da3
- request
- 790b1994fc27203dda69eb28f79debc492cd72016c41e19ab2afca889640f284
- transaction
- d3dd44f490d665e32635f2dedf8fc79c3ae65a6c3b2c714932eb6da0987d9b7acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56645
the chainentry 56645
- sealed to the entry before
- a3f942b8e1381c9a6b74f30502adec1d431d5e84808bc7c09dd2fa1ce5ec614d
- this leaf
- 7cbe13ed9c409d6ed132b8eef781e65ce1501f2c458cde4d2ff627de8dcc61b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ja95FDk5gzXJt1cEUTfgtq2OPJ59BhU3yCAzkIoNV0UcaDE+3Q2toJvaViHajqh1bE3Z73ZvAS0W83d/hus7CQ==