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
- b666c0d9666601f520003f44621a1c9c25c49ba63d5305b28a4c881edbca345f
- request
- 50ec61ed716279d2405cd40688f8f656204ff3ad28cf919c5ffa89aeb2345186
- transaction
- 8331c43be34de4b7d32866e9aab1bc55492d19eaaa5cc4fce63ea23253911649computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55794
the chainentry 55794
- sealed to the entry before
- 3f1973301d5b6f4c584a8eccbf9c8ac1bb68577ede84bd305a8eac427816b5c0
- this leaf
- 5eef198c0550ae4646b227498332e4147a4df24f9fbfeb25853c4e636a2d9d5c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pd0umxDzXWldBLA8Fx90H4eb7tnalX5r8dXlyt+IWTMBc6tf8wbSMwCtigc220sWSf8pf9ARA3GToR7VMCL6Ag==