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
- 05ab87978d30cb7b587950906ba6fa65843f0fd989db1911f53050c7ab95a50c
- request
- 814541d64deb4054227be271720e681d3016f8a3af16c7ce453b707186b690f3
- transaction
- ee45b855a92f5ff6b4691dae6e602aee0541e3a8ef9c06bcd426580d8b99e823computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56152
the chainentry 56152
- sealed to the entry before
- 33caeeefcbe65b3ad700cf6d2c3ecc84230cc91a5a4088fd1f5d3b847dea3d96
- this leaf
- 134bdf39900009c632df08fc6aa4d414dfdc1aa8f5bb6ed417d3ec9875505628
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oMP8Y3FxXI/bqccVJ6+Yvpa/JUpIeIXNxJp9/tKWzKbV2oL1belEOmAAvTJ7JWINch4IyjaKvy6uzDZF4MaSDA==