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
- a08afe8e02b9b5a8b94153c0c73dad4290148059124d2fbdc552206b94460bb9
- request
- 168ec165c42029a7df797f1b203a193e71260099af62291e8ba76180ada48747
- transaction
- dea7342fe819c0ad8810f8a3d5de8818c73be4b3d3c9707cdccf7a62c8155b01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6065
the chainentry 6065
- sealed to the entry before
- de248123b12be1b7d0bb0f04713c98d1196f27a9f5a1e26d1e88bb94991e9e21
- this leaf
- f6634b2e18ba89c8597f6fd2df8df11036671a3558377a812bc8d3e2989bdb90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5friSKLAAUCr6jX+UOVQG6So2l9AxN5pM48Tv2qtCvcyTJIJd+vZkWT8XQKAM5L3sJwkcuNKBDtrLFkhpa3zDA==