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
- b36f76380e4ad324cc52594c41e9ffe3405270b678e31c5da68b98509024b556
- request
- f3b82e5370efb9cf4e6f9f0c31ff9631d8c8c431f8fbb2c3ab230da088512dfa
- transaction
- d8578a27961e25877061d32d1b34b8ba9c8b5126d85c95b6ebe3bec6714b67c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3060
the chainentry 3060
- sealed to the entry before
- a014d58865c15247e9026234a2b66f7cc9737490d7e131731c0a1675d65b1770
- this leaf
- a3313b3eded2e027ee7915731352ae3fb42f392be9c62f02d89d02b8e674b588
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tSCyh8lgXSVx7dXxpxi3hfExup5pigoV8ZO6TzCE9PG5vPxF21Xcejyky++U9YOJvuIvlbhr2JQcvj2HGZocDQ==