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
- e3f926b5e15ff05827ade0b139c6273f92705694d3afedf95d6bbc5f9058ed6b
- request
- 50b9df1fb11233c4001de15438a18211bb2b58e2d88c6f9ce84be7f5d4796569
- transaction
- 0d719035975b8f9a531539f6f48f8f11ee16dc0610d7bf9f7767661421f5233acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42257
the chainentry 42257
- sealed to the entry before
- 9ae3f89b19316beba3b3c84dfde5a2cf65749167d12253d4b33203dba019a71c
- this leaf
- c9218f92e65aa4ffcf0b0b479468c55387ff31537bcaf7e1f07233dd2064fb37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lps2+IVtWfQVBRLnwSk/bKgIfZcXOQIdfKjqC3z872V0uvJrS8anGsTEwPx+CmIhz5XOgNsRrd3hGSe5CWJHBQ==