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
- afe91e01c52f861ed776f139fc25d1743f96944fa009609f1d35ba995220a1a9
- request
- d38ec5bd983201a8e83e4afd9a2d3b22c2f3465ff6b117daf90382445da4ab65
- transaction
- e433e2985ef2a042c1b1435562c056daa5a6175af7c83ca3bfe52f0b11f1937ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16932
the chainentry 16932
- sealed to the entry before
- 5f5d2c78e511e25e3e682972061ec4aea169bde1debd3974e6ad4d8132e3a6fe
- this leaf
- 1460e01ee858e9d3bd49eb98d99695cf7ebd3c6faf9dfa8888704b849b2ea992
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q528p8S0NdhUcrF/blnWwxgpBf7BBjVCc3FLMMuz1Y60rt42A8cLfHF7WaRRgwMcqYxm8qUh91y0D0YE2GHKBg==