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
- 2468a57cc0ddd30bc007c4b51a3c0fc4ce4be44e70ca33f43f1580a66ea2d64e
- request
- 00dfa1c905030f836a1f9094e292a14a18a377f053277c089e8d0f0d11b9a300
- transaction
- 7d10416eec9d9b17d4c2baecac4f5d06b8fc642f41bcc049d16ebb7ef8bda783computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40278
the chainentry 40278
- sealed to the entry before
- a16d9123bd419e6e6da81b6349e8e5f5f80177f308d4934da3f9073c75a0d667
- this leaf
- 24933c6a99e139877c6cef6300d9f7cfeba2674c1081f69980f70d3e711010fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /jia9FuadAyxeJqeRenwVcM+GpuvHRtAISv8H4HGF16JfoM+dVCeKJfmjx4yJzhnhhEHLH5TqHfboWDNni2hCg==