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
- 0c57e18b57cd36a678fa834a1427226b39ba8c93f6b170b40da1229e75d5a9fd
- request
- d247a8e6c8e6b20ac34955c937eff4adc7b4d26acc4fd7db1de4f0cfa644d344
- transaction
- 66bbe4666c7347532bec8815b56db4455c60459896a4a4ecb16fd6070a2e4903computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64232
the chainentry 64232
- sealed to the entry before
- fcf6dbd6b84d49591c2608d5256d68dbd0cada576a83545aec0f7b13ec9a3edc
- this leaf
- 0a8360e42c7dfd298cefadef65d5e253a24edb0e170f788098fbafe2f03801c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- swSu/soJPRwg11v+rInqaAibsM6ULr7CgsJlxYgQOtJnJU7d8va8WL5srauZ30IuE4chf1glGoQgdoXekjR/Dw==