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
- 06d483c1bf5cb8dc3a4a86b646c65bcc1ddf7e70b2aa910a6194eaadecb240a0
- request
- cbf8d142c266483f56ffef36f966f28855b8d3970752af4414870a2631677618
- transaction
- 2828b33b1a4a00c1ac95f62a26cecb83752d188f01761e6cd16d99f28f1d6ce0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30708
the chainentry 30708
- sealed to the entry before
- 16395a91b19e63182eb5ec9f5bedac7e59ee25f76d1b15f106ab7e786fa1e2be
- this leaf
- 11313ef4edd813ecc34aae44a4a93148d9f540967ef80e9039d3801636eab7d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1FhPVu2dobp1ZL0Z/9x9QOnilk54BwEyoEJdBkZJuDFznQW8gUdhkNRHJ3UqFQXF820dksMPMR4/WXtpUugPAQ==