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
- a15593ac6554204055533dc91acbbe3fd70bbb164c45784dfcfd285d7ad457aa
- request
- 9b52d77a88ad1d645630a12143074758bfa9303a3390dddec49e0e1ff25093fa
- transaction
- 19f23181437d0ca82bd7b708b5eb8abc10bc682517ab9696e6620c159cd82cc1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63663
the chainentry 63663
- sealed to the entry before
- 2ee5076715061f9eebce6bbdb758f9ab7c8183c0fd747828d5864d9cb8d1a655
- this leaf
- a9c631b0bc385ef065728135051b1cc5bdc2d6452bc636e01314cf6d3550f01e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9updC5Bh/7ORrrTN75qzMDJlOuyjKn3F1b6bvpjZj96czvwdU4k0/GdHXK4S2oQQnPip95Rvgql4PkHSEn0ODQ==