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
- 6f39bf51aca4cb649d592946023080401a207cb253286977d0f49b4257e78344
- request
- b6c4b6ff1cd14d1a69fc92b42f6f561f55aad605e61f4af1285ff5d408babba4
- transaction
- f0efc1374304d264ae53eef232ec4c181ad75aab42a77d945ac614289b2a30c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10163
the chainentry 10163
- sealed to the entry before
- 059235a256b48b094edc311ce6e6aa92259275f0aa3ad70dadaacc1d59262c28
- this leaf
- 468268b5c7db87c7c1f6b002b183325f93a4588d29b8a3a996514e3358eafa08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KAT+k1xkSon6Fg3NdlbGZF/MCF+56elVAN5/GYT+NWFHuC7FtrcvRbq69tOtMu5l4PqcJsDzv0hvCh+K+KoHCw==