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
- 149189be5edef6ca6277c4d1c3b7fa5b1330ad56a1d29a6169ba22c6afb50871
- request
- 62140464a0529ed6e70ccfb38b03b5c33e9736584f8e8f7abc892d7958ed47b6
- transaction
- e4139934b08585c698716684d1e65ecfcd38d14fde360633dcdddbb999dac407computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46137
the chainentry 46137
- sealed to the entry before
- c7f1d387da7c7a0de8169a3fe41e5e57f66dc3ab232040ea42d0deddc53145c8
- this leaf
- ffc33ff8eefcfee245db88f8c5f4ee3fca15220ca4e22c4a816d9674319ece34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TJT5K3UozFidZqBMdwMW+CgS3EdMG//ENXpT3hbhY0cKglkzgOas77JZz0ktuM5QXYN9wLYk8k3zJ2DWk0UPCA==