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
- 68310e036cd5e50626feb97e47478c36839c0af31dbf532f9f59f7dd3a7ef145
- request
- d3d4e8674df8da983df657b7148e552a990b319ca495dee0146edce3121911bc
- transaction
- 9aab9ec92997c88a0b0fc72df7b6c51b513d267094145f2b219e85f2c22edc00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5159
the chainentry 5159
- sealed to the entry before
- d96eb59f39aa5390cd30f034fcc9d9fae8e3b19c2ce74575e5497644781a6cd2
- this leaf
- 6076bd21e0905d2ff95a3b263d0da4133677bc36478d1323dbb5e6ca1a2e2ef8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0cQ7WUtSDCyrbs78vjmphzn30/kC2c2YuLNw16nRyRN3VA7ipexEhLenrg1GhaTl8Rg4MXBEaHdORykyvdqdDQ==