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
- f4d43cb24d90cd4c62669bb5e84f6481025455b72758a9be99f57c1197184775
- request
- 0df905fbacb93aee0ba0a2a80d35f2d358bce1dcd11754c538c5f7aea967a81a
- transaction
- ceaecb7f20ce2671e445dfd5a80e5e5eb77916d39c4567bbd60380a4f18b3b3dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46843
the chainentry 46843
- sealed to the entry before
- 8cd0c119ab1b7f04dad01d3e6e10d1352121fdb8053ae0498cfe94e24fc003b8
- this leaf
- 2f4479db68e4dce88f2231ec0cb8a4ba80555d32522204e3955aa93dc364d8eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aHPiMHbi34rDRgKolJaBuiAtt+VEvJ9wBM0MdJZup3Ykw62qlWnJ3u4Ow2jE8ETbi4jtEyp3T83pKb14Lu5qBw==