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
- 9dd4fd477b453caa161181123b35d32e87618961e87c6079f46d8be867718be6
- request
- e45cd62b9bb69441cdf9c3eff516bfd0785cc166cf2173b73ea874d014941b14
- transaction
- e8734bad1da87190fa01f72da2912d8eb51448f04ab4b527a7c414873b3f9598computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72276
the chainentry 72276
- sealed to the entry before
- cf4d025ed37b293af85942a3c9f7ff26d98dd7f7793bd0d84af9e2b0db8efd0e
- this leaf
- 5af53bb2eabff2fa94763bdf4ca03332237c1a143e4ba687699429c439c59363
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- shli2jXhx5NmqBxvgdUUhgS5xyDN4OJA7mwYW09XnR0Jvbr/20d2ZP/jiON8bfGEU9JTEv4r3Poty7yQtWA7CQ==