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
- 33182202da723907d8de7f6c59e96ee5329745f78b831fbc02440090d2e0517c
- request
- 858ea06d1eb23ba28b72e4b81f4e5e6f26aeb39effc912a9e6507402a1d672cf
- transaction
- e91819c3a48275ff33da7714316b45da3351c448e0a91e5ef377e5f2f337c97bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11568
the chainentry 11568
- sealed to the entry before
- be43eb9f7a2837b4dbcbea0266a791f2667479c62aa4f3c716f2ee200c5ec68d
- this leaf
- 240dd8f4b7f7a6d5e7318fa4409371c2541ffda4fdb3ecfa801037d6a1c2f970
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Grw0k5TjL1papDG7akITR3roolFQ/1z8nJl0NzvUACT//+ByS+h7oyIkmxq+RBz/9D5RwHX+ZgKARGY2cWmaAg==