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
- 81992291cc4218cd75106638f5d3a1c85c9c947151ffd5924cfdd94854af5a4f
- request
- f7c2e3497acc45e934a98d1b12c98eb0656df621721d198ff934457d107293aa
- transaction
- 52de15c89298bc838955a4a6ed5e31d4c2aaf4ac6038544bff42bb3a6923f51ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66223
the chainentry 66223
- sealed to the entry before
- d8765ac63dfac510386562172bb26bbf14fb4de39c053fa5fec61ea6f640403f
- this leaf
- c4db7cc2394ee2d260db5cd488d696691da26ebd9536cf7d352c1406033ebe4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vuuDKldD72Of6+2ir9EWCFmiKwv81Zo5520CvfoORawtjprRV+6rK42hOW7Yb0DiiuzwEQWR/TcTNzwF9uZiCA==