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
- 5ebad7c99388bc24e016a38db38ec1ba25aca799effaae9f6547d5c09a300325
- request
- a7559abfe399ec990e0faf54edf487bab12c873a64757037816c9311f09a5805
- transaction
- cd1b5078e8044fdaa96b64652279816799337a64ee1f4e5d9a2d6fcfa9b8bf2bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3375
the chainentry 3375
- sealed to the entry before
- 73731eb224f4f1be0f7492f71898f6e113cd5fd29aea74c75231a7807b8b376a
- this leaf
- 69939884745f62f3564d4d33274b3d5a79a0d98a35dd7ed2fbdb0affcc880bd9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2N2g2lq7JQhOoRZ0+7ZZlCEVIYdDNIsZgvijH0grZ/742a3RU1s+Bkib1krR/K7A0k3eo/fzOOZn1iPmXDtQDw==