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
- 5f9131bac6f577626dda669ae394e3bb2913b9d7ff8d0b8967aaba1c47728191
- request
- 19dc0e96caedf516128cfc2e107af9bfa7b0f242711000ef874beded6a42450e
- transaction
- c4b510d596606d7573c163a45fde6fe666a38a7334a001d346fb63afd7ef3be5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62812
the chainentry 62812
- sealed to the entry before
- 126b482c67a6933b2987e8862f315e00f19943626db21d91f5fc7c68fc55f065
- this leaf
- c2c031fcfae0e289a1bdccf975436f7915fc0fb6714b0e699baf883be9263529
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- saPdfBcqruMpUtQiHsSk/g4ucwCg1HBtnHhIZwxmCVEA4WuxaNONJpGXME0Ntm3SWGhTMssKS7fu9JvR9RFFDQ==