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
- ae7a2baafffe8ec05d8bc69726790cad1cd66f4491f7121f9ecb87bdd17d3990
- request
- 02e2e2a7a81689b7c4729299ec9aa43ceb01d82667b54fa5236dff1476887fce
- transaction
- 975bf0b07585cbc61f854780facdcc4a3854701285eecedf58d1ad7ddf0d1523computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20924
the chainentry 20924
- sealed to the entry before
- 202a7ba7926c0e81757194caa5bdc43214a69ab721b3285c88f176994ac4ffcd
- this leaf
- 94ad259f89759b6b7ff22f972572681580e3465ca1093986839192e1f7bad054
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dAW/lvndpD7rAVxT8I5ptcH34qrTLKVSm4zywAlwET2EYunYNguAVNqv3Cb3Qc9XH4Mc6YMFzc1CY/asCuIxCA==