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
- f9cfd6b24bf2e0de713df8bfe6e4a446fdf44cda65928f6a216079f5dd9cf294
- request
- 62a004dc36d3b4b3354659a51fbb1ad82510ea7769815503a39aa74ff5a39e12
- transaction
- 3d94e0510fe717fa22ee975ca5bc201f4d1ab901ed401e709e2007990cf60dffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43555
the chainentry 43555
- sealed to the entry before
- f547b20b189bf1827eeabbc773b2ce81ac3d9d6577e570796a4dc48d9ead5aa2
- this leaf
- c538ba851870505f54c4b57786a0cab572a794bb8734d9bd331d609beef7d4a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 08k2qkkgjirU2NPS08bPiFQkJTLZJ3dg6S/HB7x+UiSSaXBNR+eU+KG3v0p9q1HvQVJqbIpmyggRemwK12HMCQ==