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
- 0a5dab8a9eaca84951aa5bd4b9f0b039426f2d96ac90603e9560a62ee73b9f10
- request
- cd90c351f382c6428370f3f943034ef6eff096b082fb4804e163d8e50c8a1601
- transaction
- 74983e052546c64b1240cbbf4c06d2845219a0cd72713baba404e92cb4677561computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41851
the chainentry 41851
- sealed to the entry before
- ebcf848011ccbdcaf59be05b4e6869971617660d89ce66a099d7c88b68b0a20a
- this leaf
- 38d2978f7dc7c02c2ae58129e3c5c806e5dd85fc7d22a49d991bc70ba0fa3168
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DH8LgS9fnRZj3k1C7z+qTJeLCweE0+3JU0kH8OUn9NB6abw/1i+C+Mo5zT+YHmT39UarwQwKUP2i4DIjxxPwAQ==