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
- e2243f31270a5af7a9dff33890bbc582556f75252dae2fde76d9c59f36b75095
- request
- ab56c0f29c97a867d959753abd47b18c371b8fe6396de2dfabcdbc5caeba5131
- transaction
- b76ab22bdcf1cad8b6102d0fba86507cafb16544b1dd87c58012d4f5b2e60ce9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63961
the chainentry 63961
- sealed to the entry before
- 8900785a16a149485a9e79fa667b0157d3d45260cbc9c8707fe8bd9640f7325d
- this leaf
- 09d3a69b7fbeff51d91d5519528a4ced98a96450534c9316815c227328bbe99e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D/PmWsK2N37vu3X9lHnGv/uozFZsaQJ9DReZn0vBSdFuAMiur3f0Us5PWsCAUOlS7ScT3BmieNC1ktoF1JdNBw==