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
- 889a611da5fdf973c9458f39a45c7fa346949e0226884d9cbc4482da8c762bb6
- request
- c1b844e247650a9562ce9e4a50fe42010a89d83b6786a48314b11207e7e13b31
- transaction
- 42276138cb47be565db6c90665642fa77500c6e2ac1986d2f0fbc33fca49b59dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2305
the chainentry 2305
- sealed to the entry before
- cf498a51d392a1219ea6b096b73bb4a958e3c51975b6a6a55db24de5ee8811e0
- this leaf
- 81afec8f0f295e3cd7b5bfc89815d991d15c263189022b4f88e09775e7b5049c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z1o+IgyxImd3gOS/2PpDS1se4AO7JX5fc5sjkyLe+kDNqzl4q6N5SVScW0MwKO/ZkZw8wsA6+DQcZB5sMSWGDw==