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
- 2cfa649ffd00c4fd409a212dd296374b754c2abea5077e5829fbed714e1420fb
- request
- 519f59c0b8e4244bb08fbf37724da6ed74a3476f2eed5fd2b070682c77ca68f8
- transaction
- 758bf84cde6825ebb30e205f6007ef14cb0e7c873bac683bc96cf09f64a02710computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16043
the chainentry 16043
- sealed to the entry before
- e0e4bc5a1f5d3e6a77f1ea614322a1996f20fa9023092fc424fad161d49d251c
- this leaf
- abf90329a0bf5200f3ef8f9d1120ee1a6ad5944d012964e702e7e18a4e81cadb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4pszy7/qrQrlXW6/HOlqLkDaCfbXE9s1/KnvmYyocUe8RM6eZIgoJwAAh/L72yLIJMz1IhyCHQQ6YTDeuk0XAg==