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
- be2d50dfd081be67c64a8a2ebdc5a09b62bbb952a2f7669ac11974b7e4886928
- request
- 73c34000bee0f72370db3b823103f32614ac94a288d9414a28c7165d235e60db
- transaction
- 956c658b64a1ecfd44d7ed031b440e9bdd0d285a7733b8080f8d62275a6bb8cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29028
the chainentry 29028
- sealed to the entry before
- b919489bfd3930088133cab32707642caa9b949fc1b3df68cf238ff414483736
- this leaf
- e1838b234d429a584092236861a8570e387955510b1761477e390cbf21d4b6a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1G5+oj4n+FKMS793zFeuPCzr6SPKbLxTYgOzS2A6xOwKO4oZD70d+bj6vieaiCVKQXaER3JmJ6RvRYkVpdrMAA==