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
- 09ef5175f84d6266ce5fb101fd4cbb7b386129f463dd0274570e0f3cc6572972
- request
- 8ca911974986ea842f60e59796a98407b3fb7bbcec85bf777c9011460de752f2
- transaction
- 213765dd1133752b52038c5d3aa72e50957a3402b07cc5211af47ac183268094computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11883
the chainentry 11883
- sealed to the entry before
- 4daea5b6df4c4d69a91af8211efdb23767662673166989cdab718b4a907b2908
- this leaf
- 5681e62876d682642449b753cbd7aa0b8146e891f01ed4b2a73ecd92819ee3ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kjwkLYpkcloentmfyEPnIXhgbV08EXjDM9eWeya6eOmSkBjOMLJ/h92GvBLkIadph2LyMjNML0DXyBptDGKrDw==