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
- cd2936ce881cb030101ddfc0070137b1634aaf2560a15844515d6e2dcf0cc683
- request
- aed2440c6349bfa48831836ac80a441aeea8b2bdad8f75c0e6fff6d866e2f203
- transaction
- d07e0b1f675c2349c9eca502881efa6cd78fa8e8f78f3ff6155836808632652bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14486
the chainentry 14486
- sealed to the entry before
- c4fc103d58b5954ce0018611a351f30010f23b04b56c81ec1960b923057d2f64
- this leaf
- 5cc67006fa10e3aa82b2e4d1a2db112313d66c9b159138d42c83a888abeb2ff6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ul8iB62xhJE68Ul8S59wAoGULFVpTg+KmF7XY+Ol3Fn17Q6xNmcZC67Bnwnf9Iyq8dSYlR1H+EheM210Rnf1BA==