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
- 6f966f21f4a1da72fbecb4e543e41edcfbcbb0e1e15ec00cca5a9d55251c0142
- request
- f9f345e02b2d5a8d9b17f91bc35fa38161e8484c587289aa24383b32c3b41e98
- transaction
- 43c9871876bbcc19de4aa567dce2baa56c31d7ddac5997f5cf321c62347236bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 721
the chainentry 721
- sealed to the entry before
- ec849a0b3df31ec97d8072828dd87117bcbfc96bd71ab0d2416eb66a0e922e8a
- this leaf
- f2dff5cfbbe423d2bff3203cce3c187c63e921a8484687879e76ac03c2621574
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iKy8a+51NQm89YQRGqFhiAZjzM2Cg960LwUt81SZFZyxRDg35ceexNPcFX3iBCidFcxV3SKaITT/iqUztQ6wBw==