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
- 45d14a6f4b561f8752f4ced14516e0c60abf40b6a16362b735eb4e2484247599
- request
- 5927e93547185126d6fc25917422b5c70bd672f1923b1e4928d10703ab72dd33
- transaction
- 47bc1701f47620e86d3d2eeb006d5c369b7d801d45824680ba8dc277bb101a8bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10447
the chainentry 10447
- sealed to the entry before
- 2db749ed4a16155e88956b15624d68ac1885987d2dfa6b7678b07c5a82dea70e
- this leaf
- 66fdf49a30d472c3e0c238cade0421f4c97bf800a37a937af8e665f058a855cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rjIapScB5plFZk1wqju/vUvaUSvC3dwl9eAG3M7cfEgRendKGUMNfrgiq2CW2oLpuglFSueDDrTNZmiCdDILDg==