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
- 085b7b25fc941f4a6691e9ed90e72f55c3411e1fac9fbf14c364fe712bf6a785
- request
- 977ca502c1210ada05045d2f8b2db776de070e1c6327e92611997cc1dda02bb5
- transaction
- 8c4b53c0ea1843d0bba747bc3c0488d5a8436b5cbf1ab20d2500c19294bfbdc1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17611
the chainentry 17611
- sealed to the entry before
- b381a0449640872430e97c6677ff323e3ac15e36bee8da22196dc6e6936d7e2f
- this leaf
- d0e9cdb2096007796de10253cbb30dd0227d59c1f3e425226be938cdb7074fb1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QqeHVnZNMvAhBu8qlbfZBulHJdNnVL/bmaklgTtE4x9wUkNS47zFN6rJCImVk5tto2+FYe6psl/CUErPfdUfCQ==