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
- c894ad71feb4ca576ff9b33dda90e0767a6fe1668f564cc73a37e7badcb54a6d
- request
- 6ec09dcc13c33091e4da34194b914cb40b1675883671a4004aa22d25bfd5e9f3
- transaction
- e3be4d8dbd43f8f88a37229fe852b4e56badd7307ca733e9043007a3aab210dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76787
the chainentry 76787
- sealed to the entry before
- 00b44afe5e3dfa26814403fb8edf9dca51c50c14d6c2b7225573138cd274efee
- this leaf
- ae48e7f5098e0f3cb520635816bc724e2b4d26efdba8ddb186a6dbae8de6409c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MsL2B7LdyYAQwtD3GZn0Iztqq1diukyJr5Zmti01496RlcHNN+AlndyQQ4lVJfZWjLepbkBDqwK5uEUgd/8cBw==