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
- d4487b61a3f0d64f136704f4d3f896731cc9912204801b6a742b5147c97290af
- request
- 0c0a31cd2ffa415798f238399c3a435eb696a5174fafa010831810a6c953a683
- transaction
- 76bee30e48ff9a3ca61606e884e6021b44d0e1c998814347fc7a08e3aa42832bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37098
the chainentry 37098
- sealed to the entry before
- e431a7f22ab3273f178c6b7e67a7300cf0ce5238bac85e9847b9b15ac7d30fde
- this leaf
- 8ac7d796a0b6c47f45dcc5bb41279af54d98884af5c9f243a4e4cc8e4a90da23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XUtvDFUDMd2EBJN1d9SP1wCFJYnu0q1o5WwO36KHeOFCMmOsi6pZtyMQFixZAh3/XuoqXjU+ZCRELYbYGg99Bw==