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
- 02fdeac5d3665cbde7cd2c7113fb0931f7e3bf002d9e2d43631ec5991142d59b
- request
- 3bc0cfd04f42430929ee2e1b27bcd0b8e5b50c99a45c94faa86afcec5ce616fa
- transaction
- ef2c46f0c4bbd7119f8c860dc19ba012ec6e85bec117aea3188eca1d599ab4e9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59271
the chainentry 59271
- sealed to the entry before
- dfb0dd8b3c64607fb83150998254abbd172808a7cfeaef5d0335a83eece5ae09
- this leaf
- 4c9637a6bce50f448f94568662ee3e927111f6792c0b3e7b7e54f400159047d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VhfBqdct02wPOPQowUr57K4ikt59zm/T/vFi9FHR80W6MLw0KZvXajUKJ1nOt5Hh6yIoyKtqi5XNCIj6NqiuAw==