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
- d60583935ec4c0866eb45b4f02d3d38e6483959579c83005fb2b6df7a0c5e49a
- request
- ce610f42c6bafcb0631f772d8808fdcb66412636ad235a5e152b458f81c3f3b7
- transaction
- f4a60035de9a98bbe7a9aec82188821a1526ad1b420b52bb8299e1724ba067f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71951
the chainentry 71951
- sealed to the entry before
- 73500f3a2f97d54439894735bf68e1980720c832a8eb70db9ddab9691813a8fb
- this leaf
- b8a91e78eac7aef65c6dca534c1500875b832fe66d71f154f3ff7171cf57ea98
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lvAflmtsC2SQ5qrde84srQw2VIrsUwI4vldvJWMshYVz4gDPIEH333ZVZd6I6vAjWQIipGRHvAr+BpVl3xylAw==