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
- b2a9cc275c5ffd07885ac4966b9e1fe7a9f70be87293810e135e67800dd47d5f
- request
- 1bcc579253348caa5d58b1225d619e668e1ea98bcb9d9b31a145589f3456f170
- transaction
- a3e93a3e7445c780a1232591d6ebbef564f3dc7bb35ef39a46ad4d108c10332bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30354
the chainentry 30354
- sealed to the entry before
- 6ecb4b236a4d23f7307c65afcdf9946edc3a3739f44b3fe5325bb68295f0c068
- this leaf
- fd27cf066dd5266bf15082f672464bc0b0fea8aa7c21b895a18ca9bc98218058
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JkP1tEEh023RwzkGiN97yHCqM9Lg0ZRwcCggV8iasV4uhdfiwXq8frtU/hP0fHer/RtWplNszNe+84b53wJ6Ag==