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
- f41ed264314b013617a207f6871a7713f07a8938524c79d9a78e533f1b9cd0b9
- request
- dae84c10cfc50955a91da14ca00eda157b78159c2782090d0b278909ddbe36b8
- transaction
- 7bc6144466f06cbf40da1c8b2e09613e8bb64add9188aa93080c6b42472bdae2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11529
the chainentry 11529
- sealed to the entry before
- d59504b4ce3887b310c205c6a288136c61638bdf0701c5c365a1f7945303f213
- this leaf
- 0f1497f673336bca1e0e5f2f010e8c2c39d16e385e823a03a45143738d025ba9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m/pbD2NVJSJXAgT9MixAt2Srnkni09gNVhpWRWRQmbymjXpBe2JUJD81I6omz/Ii4lrC7sOl6/1lZTVjJMMmCg==