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
- b80f4e5827cdaa23a9d25a6d8d23b4b480800b1b8faa20280a6adc85073fb674
- request
- 34bf3dc32510e063172ca5092a49c76d5559e4f74c7e38d418f6fc6e454e84de
- transaction
- 81bcfa89ac4996c934f102991ba5d133e454e03dcffeec8cac2884d0bf01dcd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22515
the chainentry 22515
- sealed to the entry before
- edeb60329c4db73cab4f5bf5217a9eb6ebefe50a25e604e1c6c0265fdd5d8370
- this leaf
- 1e9b8974ff93b97325538631099a995bc917b60b85eda5e7cdd46c07a4af0b3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R8vpzBbR3aP1PhJAK9u7Sdl6uw1XI9NPSkwtms3EEW8ZTB1+79vRa3xzaLDWJmYE3T8C9n1+05lyJVumXjyHCw==