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
- f3db58032af074d0916cfdd374395d081a0c4430e3a26888f4bae01ce630e55b
- request
- 394cdce1d28dd1c5366e1f1d044e351a7b31408c7e2dc1f844ff2234a9fdded2
- transaction
- c8493b8dc578d7966ce0b41a89c161eda65bbd92d15adbf5fee32f8e1c17fb91computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46909
the chainentry 46909
- sealed to the entry before
- 5d36e85347974b1d20b29fafd9220d12eb434f49dc39247892c073fef1b765b3
- this leaf
- d7c97d4ca4de155b0b588093cb415cc9b4157c0f0ec2b968ea6bfeb880e48e40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S1ufrFOavWGlHPiCvPiyVsm0kE5NC3L197YJlPGpDU3/mA3jabVAVoDfDNjvuxuRpqQRSlDGVVSoBcOW2++tAg==