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
- abb65556a2ca6234cf0c9bca957b6015fdc77ad082955671ba256a68aeaf0c54
- request
- d1497fe675b267fe4b2e75930249a9accf33ec7531bef593fd073c83d076c19d
- transaction
- fb73f645bf9a0e756b725299f4ca3d137cb53c7f4f3c7c300710d50b979fa594computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55298
the chainentry 55298
- sealed to the entry before
- fe249fdeedde45c0a3c6f8378d5cec37083f34df0c10f45b33d7cffda0fc6384
- this leaf
- 2c5f99581aca858e829cff5f2a488991f01b5719892b7b617247764d36b044c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +S3pBKwu5q2mpPaj0AfQz6sHwYRspLDZypgQuprv/LwFxiCMSKXjTnBfOjLn2hXXpFGiQ4SaFPZTq3Ju6IKoCg==