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
- 70e38bcb2fb0c3669cd9d1df0a630509283ab8adf5bfd327896d8533ccb710ae
- request
- 271dd410efe2fce168c777e5cb4036fe2605293ae35e76df59e2a89b8fe2f093
- transaction
- 93d06fe47381d71f2b73c370f547349006d779cdf797d1f586d402f85d0978cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14508
the chainentry 14508
- sealed to the entry before
- 1c677f41b0606856c5e0de7a0de23c049d3b45cf50a2f87ee414e46aaa8b7fd6
- this leaf
- d94d398d7f9bcc0f1891bec6e068ac4b69906862419de0c47b625d0e90770b02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ji1rTERqn/VlKn6ETEK3DYz17x7i+0ithIRsNhYWvlUVYeTAmnDrNFBKoZfKbz3VKyMfEXmjdqYH+82GVDIgBw==