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
- b66bc699c69b35232bce2156e02e1ccd61e862d53ef525ac2171f043014b160d
- request
- 246d8be32a7e87bb38dfd41b6595b492d8cff17c5951278b5364e24e5bfd400d
- transaction
- 06ce94adfb3ecda92605e5b8505cfa706d73613733a0f6dede5869a9f437b965computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10662
the chainentry 10662
- sealed to the entry before
- 4d1e9c86aecac8637ac896d4733a15a0871438353292d7f303ed30686fdf9d7f
- this leaf
- 0c337fa3e87a430c9de1245bf26a8cceec06b43b0a267a7274015feae5050528
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dUA9ZnAKlMoNxC2s/mOS1W6qQUQMePb52gTwZ0C0x8zo6io6M0f7yDW7J5D9Of7+6+1AaozOZM9PSU3Q3XzKAg==