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
- ee7d2b8e34c9bc3251467fc38dfacbe3ebe60bfc196f155333ece3db06cb662c
- request
- b904b754dbd87875c2104500dceca6fba10b71be196a51c043c119ab4aeeabfa
- transaction
- 73e454496aab6869d07b230573a2267579a028350053b59c2bd7e04a302e88a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50645
the chainentry 50645
- sealed to the entry before
- 0a3575db50cdb3c711454c6ac84b3ce948aebf8d604125abf0c51acca50e81de
- this leaf
- 75ad700fc08deb089cb13f7092e23587f2efbe425d380b6836897eb1bbe77ef7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FaOoYgHk0ji9mGpbZlYvzGxQVe0H43T38qyF26XlS1iFntqibYaRAKQ3XKiavH5+OqMhRpyV6qvD3YnK3PxrBg==