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
- 84c055d8fb191e46158b0ade47f72c82c9306f016fb5002d4bf7bf181911f959
- request
- 97ca984da01139e4a1c9bdbb2bcffa65639e453898f8a6ec26452c4392748459
- transaction
- d31077d2df0b0402ac56ef28f48e827ef065b290c939102744489cdfd021116dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72175
the chainentry 72175
- sealed to the entry before
- 9d8754633e67bbc957a30ba29ade3ab993a0254d1679ee6836a82c2b9ece183c
- this leaf
- f679c20e505ac53c5f961650e535cf621cc8254fd1849f663c82bfabde3a95a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f8iPHc/uxFrsPCnpL40QHN4vll6AFheYZJ220xvqBzxPC4qIkfP79WiQAZPv3LtZKn1kk0Rnbq39SIk37tWeDw==