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
- 694545756d0bd865be1244674d15d5b428a1a38d3d657f252428993536e0d526
- request
- 7bb82ddb2ab96f8df4bc8a726ca26ee518efffa439d4ab6d305a60806f99cce9
- transaction
- ae936125fa754e4106d0e33589d366417aa508ec0a44640a3cf58d8dcf342e6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44549
the chainentry 44549
- sealed to the entry before
- 85c60b1a52e5dc8ff4730ac70b844a4a6a357081136d2cacdc0f041ae1de6b29
- this leaf
- 37be152d3219148c671178c6cad61f88b52ee3e09c9872ca2af03f9637f369ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ezu84uj8pK+POKgPxlakMwxikR20zKeal1CpWfgyaJf+3+Nk9KaNTqS5ZpCyDf7gm/7VjVJz4w1Ag9qqs4E4CQ==