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
- ff2468a1d03cbae4e560b6d17ac4326e4bf746a09d3e9b9991fb15ce65c00677
- request
- ff1c18bdc1f271bd33b3fccf74a773c2804434affd7b5dc8768252ff9e26d8ab
- transaction
- 05b5937294ccf205e83e8b59d27c1a4005fdcfc9a889e335951c1008640e281ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48499
the chainentry 48499
- sealed to the entry before
- 8cadf04877ede064338e2f8809316858151c4ea3ffbe0e61a30f236376d71919
- this leaf
- 145db81646a8bb4a7ab2d046acb6a47f93c499e929ed51547b6a2935c25094d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F0FgZRe10fe3rFFnu0plwot0JYq933z75xcgIXkW3TmNEWGBZPs99SWh9cwZD8DJJo9OSDBMdVxuxjL3k4e1Aw==