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
- 3675c2a4ac06466a725a8b6fa9c34476ad4ede9e7c6313f1cef83fa78db12c15
- request
- c07a0d3c5b617e8fde7be92d76cc7eda754f39520ba6b1c18dfbea18f1577403
- transaction
- 304181733f9ad4da9aaa970f84a8da52f75d5f5b7d8eb9900508e41eb41f97afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32027
the chainentry 32027
- sealed to the entry before
- 4fa639cba92fdb87e7bba7bd29fe325fd87c34211dd106ee1ff5dff56e5984a1
- this leaf
- 88ca90c07022974113f380903b8b74f716a9e23cc06cf4fbf12e0f6516786ae3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dDQH7Fu+nkO//2s5FpzGm05ml5w3pZhZUEDL1/anr+BMFNa1qEnKNybQc2s9LNdyLW5xS+HfwlXbnMKN+aS7AQ==