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
- 0b95866000d1250751c3609996c1d74979f7d6b8733789349c564c1caf1d05e5
- request
- 75c08d23f9a21c06c216502a102df7322746efcaa3df961508592613f138db39
- transaction
- 51caf944a7144ddecf1b4b245314ec59d707c80f25c7c1ee8f6e10d69690de17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21568
the chainentry 21568
- sealed to the entry before
- 0580f1127cb5cdd11f553ea42519f878b6b097db2b91ffedca325c00a9f0cca1
- this leaf
- 6b811cfe8ed2665154f6cb0c9ec11cf1a2aa77b723d89f557b76f19bc6110ffc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q8jAoYQTu6Ubgsf36UEQ7szcvclML6K+80WuXhu48PrncW8QIjZvSPkoHAEl3PnIlnfwLpQQnrRgZUBTeMRCBA==