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
- 18eacf4bafc29c6d93c4d362bbd663ba2b236286aae383eca436fb55494b72e5
- request
- 08a3fe04f5ea700f048ad68312feffd64fb76e0b6687839ee36f8bb10c9bd857
- transaction
- 461162f9574d1a333482afe31a3bd4d0b41c512e31568cc808ec231d96fb899acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 446
the chainentry 446
- sealed to the entry before
- 902d8deca3078472823146ef6e23dd83cc9cff7afd3db18298081c193161a22d
- this leaf
- c3a55e69d42a2d48d7e238225a4c8b5c09c519079d5a514854eaddc7a9b89221
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2BELbI6rOJVr6WM6YiNb33lmrhgqB1zJ1320z3zk5FnSCm6+89DnG59crUzKKk0V5G/ANUuVt/NjxjQ4rjA9Dg==