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
- a63f2ac7fc1d7690b68ca4020faab6451eb83017a1364c3a9f44cdb9623aa8c2
- request
- 2ec5502de88a9aeb2df30a226c469e3731e5abe6707e296193ef6ca4451224e2
- transaction
- be6d04674f8fe0f4db12dc203c779d547cad7078cb035243c78dffa1f86d1657computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22866
the chainentry 22866
- sealed to the entry before
- bbc99b936d654915df5e06f2e2d637284a9b4126c1872d70e695a24b75c9a5dc
- this leaf
- 49fb6c62b5320fda98fe5da96661fa1363a6ff40bd8459c7a5a4f867091d9491
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H46VbvhzZifaUztQUJyXNJ3zgYsKU9DC09pndXStEzw7HajQ9SJfmyc3zhY9/+Lxj257I+09umzRhhDTgkUaCQ==