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
- a671ead01622f0534e74105fbd6932d59d88a57ffc0a32af85bd1f245a0a8a42
- request
- 569f2446933e17577e639b18e55607fca469273f62bdb3fc6b7480e4fed2615e
- transaction
- c66728c0e80c4e4178179192380558ab32e47fbde05ce98c1d2a2038c1d31220computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35722
the chainentry 35722
- sealed to the entry before
- 9aaa2ef9c5ff8de7d011b0f6ee5473e2414a7bb41af4d76f6ffd209d14f63f9d
- this leaf
- 72e2ace52be8bed6a28e5407dad26e47e2a3928c663472592726e55495b9c699
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3m83snGGKEegG0jP48gJSLvUFUByvNRffwOAYyDBbA145+efAL8oPirXjapu7mgWsS09onsOGV48XrL5D5AmCA==