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
- 9f932e5ba766cf284cc07acee7b397bdcc7c4a03e02d89016bb3ed2740046391
- request
- 40086853f2e33de1a5a85a778abe31394575aee7c80b7e47268f5dfbec59fbdd
- transaction
- 940b293baa0d6244ab841389e5b2bbfaa47769f4e3c5027dcde0102cd78f95eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14446
the chainentry 14446
- sealed to the entry before
- 0c6c82deaa6d3879c3e2464b6ab3ad74a1896ee7cfcb7003867c5c5e65dd738f
- this leaf
- 7697ce5e04fccc6cf416e27ceb2c4e07f2a1165442f755456c19af7bc3ac7407
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7k11Jc5qYH5/8lNxxSCoXnmse5+GpFO48y6zrUiK0nYEme+oCCBVc3zW3RMhDw2OK1rIzyXE3wvrm0HlouYMCg==