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
- 6f7a9c80785717095794d2bf05f98e2ef69b5a59bad4961942e2739da8cd7c1b
- request
- c0c796366b274e6b116d07fd5157dd95ced516c8ce522aff38c2004419a78f7a
- transaction
- be373bf4dc55700c57f2e33c0f9cb0413ae8e9318e27ff8d7a59f7aa3d53d792computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58819
the chainentry 58819
- sealed to the entry before
- 1967659c32c00cdea1e0222609f85c448d19a4179e6e8ac1b729d185199081a0
- this leaf
- b6e2c9f2c9ecb4f35aad66d1adde3dccc7fbebb53d489a181a2beee6b28c6ac2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RSXB3LgRgMii26bokT8s1NaqGzd4tB0FTQC2PktXoqJ1DNvk9C6ZTHnO6prwZ/H77LPykqfBIGDDLvJCTHvvAw==