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
- ab6d5ecc7ced8034e9bdd733f72be11226dfdeb5cda4b785545bc2af0ecc562b
- request
- e2947b3d4c621f377c2f234d0b747cb52cc4a2172c41cab23db20b6181faa869
- transaction
- 38ddf39f12edc000e5ce53028412981dfa3d9cb33f1a30dacf8d8069b151ce26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46127
the chainentry 46127
- sealed to the entry before
- febc55fedda05250ca241254d20f087c4ffbe9053b36a6802bf1190b9aeb645b
- this leaf
- 9238b7f8655fa8d7454961310abd4fff5d4707ab6b2aef1b7a051aa835e95f87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bMpwx4mwwS9JK6MX2lhmD1U41NBR2g3SK6lzISrTP8JvuqdVBX4/Pfef8zxVrC9zCqlixYwnkufV/do2BLKFAw==