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
- e2db7f9352344942c649fb113169eb21fc0429137239fa9dd7112e23c83a2aa7
- request
- ed319db189f198360891fbc7469ac405bd02e49744a6f49366e0638be3205b05
- transaction
- ef3dbcf684b043acf8acdf00f5fd754a6488ea392582dcba90db025f8c5a5836computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1530
the chainentry 1530
- sealed to the entry before
- 1a3e0025a235f5c013a92fd68dfc9011a4c6a66b29093552176faf38122f0de4
- this leaf
- f8880492d8270d5b35b739d06bc4593b76a67c230ea9baf0523e00254784b907
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZN2P3ipc+ePm99/Vx/SiGXn4iwhzyf1WDO4yXmpvK81lO5YFAXOoNFA+5WMnWwFX04e4p2foIuziqD6SdYDlBQ==