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
- ed6e3338f91cbfe2f340ee5e08174e46f8f644bd38fae1d37a38de6f5010283d
- request
- a8ec5c194975da5932e3c884144a4c92b479650d22e421615ca21ca72b0ac9c1
- transaction
- ed0c6bd6cc1b8105663d3e3a814a32e13bec037117ba1a320cf4229b76071dc8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37346
the chainentry 37346
- sealed to the entry before
- c15ce6c7170d232f8250f2bb58ebea182938e72bb29f143d7e9135aadf1f05cc
- this leaf
- 292fc2e448f5060df06c016daef5ae7aadd97ed436a02174e042dd7bf68188c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lrKttw8iUQ3ZYmk9MsqEZNccksa+RUtGU2zrWMIzYb6KQ5U44aUARgKkD6CotGhe7QNtpJmk/pv0CGnJw8fzAw==