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
- b23048f28dabb5d9f3e03361d4616d954da55bfe68dc52696d5b80c9d2b9c25b
- request
- 96626e663c3318e6912870254678b0c401bc6e55afc9728c03afa1ec5c3494fb
- transaction
- 0545678781657952f0e8038ad4747ea1db67d40c4ff42f831999b376406fbe84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34821
the chainentry 34821
- sealed to the entry before
- d527f6d19a0cd804f2dcea0a1115db5fa34cf2ffb95e9c9cba7d975a5e5c839e
- this leaf
- 488131b48a77d7d4e7cb57d0b35794492b1b08664efd1451d0bf6c31e68de24d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vnzAV9aOh+OuJpdm5P4yP424iiXzP/H212rjYBQSgUPlOYFyq0lLMIzKHCPW4mFQddlmOpPBnb5oQxtIqCY5Aw==