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
- f095fb2c22905f494fe35651bbbdb5c4b3669134b5024789ccc4e5eab8b39afc
- request
- e41eca94e54d6ca590e0c360115620b67edd389e47264953d7cc37a230669b47
- transaction
- 587e6caef40bee269d2cb818b958d16e1fa39e18e036665d342c64e9f0e5e8f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30753
the chainentry 30753
- sealed to the entry before
- 3de0d760aa5985c957a2c8a8a3ddfed16b92aad8e716d11fc79958b090605f49
- this leaf
- 143e7ac18dffc25ef243340d395b476c36b6133ce4ed918018b9645d3467dac8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ToPM0L3sa+aghvDGW5b/r4iaxvnvKQ9oRGo+imMqrGwcwWHCm0+WMkOgpWyGkCeYTBuZutav/doZ3dzm3oLYAg==