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
- 2f171297065dd6439e3e932a66683ba50be5f02ca095d920f60cd6b022b3378c
- request
- a2451f5257616ecbc546ff649fdbb15831e312208968be965909fa4ca86de82b
- transaction
- 38bf968789458445d954272932e3603e22f8a8a71cd61618f7b858086bb4f73ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66946
the chainentry 66946
- sealed to the entry before
- d6078a49dfac33690d4e63806ea82940477836fcd2058f59b2fb1c1c761f753f
- this leaf
- bfbc753e1386aeb3d1c3d75b32df5b5ab292d0a067d24931dafc556c99b914b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ebDeWXjyjcMrt9pME3yrCRzn66HTSHyYOh++Pj6UNLx4uwn6yR2r+epuHH/AXFNqm6g4BCT8uET3+a/a1MzvBw==