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
- 1a35bbb865fb3f586de14f26196781408a372750ff6cd4703575c5a76ddffe0a
- request
- 1a49b1663e2d8e8354e070c679d760502fbd1ab1b64738dcc6220d349089a2a8
- transaction
- 31f0e68337f7c9ede0ed70ee12874de622984780a9887e0c851e6fdeca0dbad8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70091
the chainentry 70091
- sealed to the entry before
- 738667faecdb5912c41cf771a397aa50d5564f698a0113ea1a2eb6e85251741d
- this leaf
- 4c2e51d48c6f6a6b7cbae5badf650d4fce4940b0c2b7291261426b9d00fefac5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ik+bJSamqfEzkwHfTY/dOCMTVYRq4Mrb0PWH/3w6OPSb1VGszPMdw90DXCT/eY0yo0iMrkrWJsiVtTYq9mXkBg==