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
- 4759da36758878b9c6594ad4604aa527f282199b52a90580b8f6c69c011747fa
- request
- bec30cf1723906a5e3a06515dc51f30e1233d785cf4c06b67cc4a57ad54a0128
- transaction
- 9cf141e4a98814a7c38abfb7947dce3cd6213a4384ca87247232c144b719d94ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1320
the chainentry 1320
- sealed to the entry before
- 34a311186574c617fa6b7d4dca75ba35ed5335adfd74a54a31917036d490a20a
- this leaf
- f956c19c1ae0b30bef67e41fa8969f4871cf54595258e90de3af154d82f67d53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B0EoMHPtN9qpM9TfLYI1XKEc6vJYPCHEYPRemoDm4bcoqmw5YUPNa7PS//923kwHCk++dI8xfDRvaSEOwVoRCA==