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
- ffd80809799ca94c21deb2cd7fca9382b5db56867c384bb2b376503719e8841b
- request
- a34a4febe91a4f21b895078d1f37368a9c9160f2a42556479d13ac397519cde5
- transaction
- 62704c018a236c2518ecc39567d7ae3411e5b91131f6fccaa4df44fd652a0d1dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73392
the chainentry 73392
- sealed to the entry before
- 28c3484de41bda846b90ebe4713ab4a23cff4510ba6dc222237a9dbaf523e8c9
- this leaf
- ef3b1252b0a3517a3f7029fcb74389148c7d3e7046222313ba738377f6bae31a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qg0gw65Kc90XOoQqPn1wa+OBtddgyIxjyK5o6B0JCB6e2/evN0m/E30Irfz4u9dU0pBx5u6aqsKgM3kaBS2pDg==