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
- d5a86bf41b01db085324af8307fb78634085a6d995bc0822a8bd225c91a84edd
- request
- 0b39cafa3a387bc857a1cd2cf54bf491346057b0feb390e554b93a4d7a6da4a4
- transaction
- 862aa221e0a0a93af39bd90beb129901415569b4449db44ad6acfb55aec77bc9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15903
the chainentry 15903
- sealed to the entry before
- 9ce7508331a06de96c57fa21e16bd45b9d3fa7a923424df627a8cfd4cab059c5
- this leaf
- df18c04024afb2d88bb2f57da233d81ead8d19cee0f5cdfbc24138a30d5a8d51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Neq1lPP+LxKwhO79V3YykBdmxZZjy90Hmkl3WfZ8w8jMo8DZCa8gL88Sr2EvQktsxqYc+b2PidTKp35UsLZvBA==