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
- 9f2ed5032778aa9313767eccdaa996ac1fa4296656dc2bb85bc24c300a78dc23
- request
- f8f353cf98ccf95d7be448686175c35a35355bbcf24aacdbe06f36cac0e43b7d
- transaction
- 24b15876a2e16803115a41114a80ef0fb10a404fb4e0aeab975856d864cf6ec2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43742
the chainentry 43742
- sealed to the entry before
- 7bfae4b444ea36d0cde9203be8f5e690a6c6ce0c29dcc02355ec3eaf2349fe97
- this leaf
- bf1b422636ef86b60358b476939953b3133a5b575c3f82241c039bc214cecd14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PbwTfl9grrn70K4R+7CtNXdcHkRTQaOShdmiwfNtt+BdWpllyLMAXg1uCDki1kcZlkH318R07Z5bLpe6dYVVBA==