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
- 5ada751655ae0c58fe3706640785492732839a5fd2c73fe3f5eae6044f67e6a4
- request
- 8a64ee884e63e56122b2d405ba22429822d6d3abbd4796c5b5304108a0bbaf81
- transaction
- bc64706428b978f0b4a82a43b509c475ee2c6ac3a89c6312a484bcd495bfab38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69406
the chainentry 69406
- sealed to the entry before
- d33fc9109365f7d545298869660ece28f407c00d7d2c67cf7bffaf1304ecd07e
- this leaf
- f6d844b11d16f8976aee22a300eac10d65a55b6f91feea7d59528c5f09c013c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F58s0hdEoyGzFrmNcze+lOoyc5oMj2Job3BH8Ww3DguQu/YbkLXXHNE0+G8nIqXpbEJHqPEcPL8Q5p0K02tGDA==