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
- 0b273010e73e4899bb426b1d1ec3bd76be6baf937325386e49aad11edd615d2f
- request
- bf017b4401e7c61392611038489ff2345222b7ab2ce4de0bb5e5e075bb3f79c5
- transaction
- efc3e7387b83293f4c009f925121e4bec20ee9a80fae46374651edec52ab9a21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33941
the chainentry 33941
- sealed to the entry before
- 87606986f079381992e7808602a31badb0df53514ba657c26347e13fc42057a8
- this leaf
- c30bd5b3992332a1f31d27001f9e808238098d857824530aace5b67bffb66640
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rhR1/Nj0J25ZKZ63iLaImgsooPt4iQEl7JQvvVhY52cp97UpegopG36ItJ6w+iUZiVhJ9QIh2rY2uNGzFrP7Aw==