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
- d193723d5c9e72bcfcb1fbbd68aabf8994d519a6f464b603659fd37ecd0973c8
- request
- 5c48f65778e0cf91ec8eedf02d6549f155d32780ae0f510ff4cd245a6da3f0ff
- transaction
- 9d3182701c34ad705b491b043cfb48cf50eacbe6cc0dca40fc8a62893ea83ba3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13725
the chainentry 13725
- sealed to the entry before
- e904c690e5d5830657a6e1c2bd7abe4ce4aeff14d19f430d26582b392caf5ffb
- this leaf
- 236d8616260eebc784c073ccd32ed16404b5f88ed6590aec8b80b63912b3140b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c+Po31MUyeeo6loDc3GKpnFS7stT/YFwfXAOCqG7yW9E1WFMYQNuKYLWmeKY1kqy/mWNH9iEbPThPtDPSwpCAw==