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
- d79e8c6a5e18ba3f0f995595103a31e3b7d1fbf076aca66deabcbb65789f6424
- request
- 0bb9b207a1a4f82f288b70e2a7217f3ebf4e89378397fddcfa178480d2bdc548
- transaction
- 404a5053566da5453da97d8816aa6a517611ae17379f31ce3e817efab66693d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10512
the chainentry 10512
- sealed to the entry before
- 07d6fc55ca7e868919612e89f2adce19ea873076375449da078edfe8af8de8d9
- this leaf
- 0aaae25ed29b76225f281fdda802aca892f0abbc2dd1b3cb8710cdd29af602bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H2qbXvXFBMLJ7Deo6NUByOZLjDAoU60TgqiyIZMGsPRAO2fSbUnnnke1cbbNHLFz+v9bGM2AHpPEdoFLyDiICA==