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
- bc5272953ca328724323c0f7b2481c6a1919d7f605b567f6b129b3b8340cbc6f
- request
- a4522bf2bf647383cb8d84fd56fe7e0850663e30a7aa4745cec9f0d4877c0f7c
- transaction
- a1794c0771ad9b9b11ab69eaabb5d955ff733ddcf99a23a3fc114384daa5386ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60103
the chainentry 60103
- sealed to the entry before
- 5ac3701d9c4e12206d7e341302393a14b6c2af39d6d1995c57d43afcb2d0d487
- this leaf
- 0f6439a507811edfd0d97c07aaa8e9038691b3244cdb61f482f3b18993d60927
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sdiexr9FnnVyZc/ZNf5Ahbncf89eejZiep9nSTzVkZPvl3pN+4VN1flRkk9o+7tPHDma7fvCrrG+HG0rY5uLCQ==