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
- b639649eac96775190fb85b2d3e97b823a53f270acbb62c384cff7aff97dbb18
- request
- 2cb6edf2dbf2816af55ee0489ee1c1f6052f13ce3462669b1c510015079e77b9
- transaction
- 6c3a5822fbe1d597a810a9bb8614155ef2ff8d786160568035c66a3c82a644fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16735
the chainentry 16735
- sealed to the entry before
- 2f849d919daaeb2a9d2969acca04e162f9bf3133c91858fa131cad264e35e990
- this leaf
- 0ad5b863db6d57a304ecb21bebcc22e220ed1b0e6737356f39a3a9aa78968856
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RLTm9lD0NKJjoiuqVEKfEC+KRARtt1PcMhcSYPoEoHowRf08NmpiTgq1XJhZhb88YPF91STTE3hs2byVodNeCQ==