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
- 3238c0df06a1ed0b8321b04cf210fda663077a2ff0fe87b0e7dcdc0b943d8d3e
- request
- eb919c8610a612709d2cf88652544fa72f30fd78f3351f464f216c1d6edda5dd
- transaction
- e55b2f85bd45d0ada8738c437a029b019e49dc33762785289f21eba25766eca1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68694
the chainentry 68694
- sealed to the entry before
- 0a034b98da7eba32c5917e151b9e2e47b1261ce1908f4426f2fb035def99b0af
- this leaf
- c19a7db109d84ce676764f23038fc6417696db6b2edbbdf0388fa012addf0c0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w/A0xVlae0HpvILIvuoqxTZP+l3IpyFUC1tpiOKfFO6uGnbX8uSPMtIsCaWRSnLFE9JDZZEp8KFUpebCu4oQBg==