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
- 178f0c744de32b0b0087aebef7d26716491edc1bf6fe9e44880bd0c98c032859
- request
- c441c755b0bebaf454b74c018e69a7cc693fd341fcd7b04ed79e7c070db8d6b7
- transaction
- db5539476b3169d45b78a1cd42310e8188232789b759be63d74ad0aebb73242bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2535
the chainentry 2535
- sealed to the entry before
- ac511f8946d5bdf412dcac11815db12f3fbbbacf2f7e193376f62d7fad75a512
- this leaf
- 8b495d7e7021e9988f8cd546ce6684ffa9d3bf75a937aac57afd8ad3cfe20b43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9Jr558Wfcxq7/vhuDFA08zn3Z5/Ke8s55g9eFaShHJ7Hub+K8ZR8RJsaQ66hEackddLwQ8exTN5Er3nih06LAw==