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
- 3f4b4be3d7dbe4494fa6688bd2f896e6561b7ba458e0249aa3a78f1f72cfca0a
- request
- 4021f80bd109bca68cf0ebaf797945cceaa51748202d7e3a75f3670654faeef1
- transaction
- 7a007df5f22ff085667f5e65cc21173f04de9f13f4491e3584552439a431b3a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48510
the chainentry 48510
- sealed to the entry before
- 21456998c89d290ba151090875e128206da8543d9d1ceae35e4ea82b14588bff
- this leaf
- a92504094861e3fa0b988ee589a86601f108baca66be36b1600eb7b1563f4594
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c1lKNRLjLrZiVB/DQMF6l4IUMGYsHpHud9E+x0uhyW555k9RK7S1sn7P/zWOXL2Lo/PIaKBzK+E/ZdHcuCS5CQ==