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
- 17a0b2a8e0fad1241670f896e20ac8c5e807b99b0ee189ebb39aefd8c3b56afb
- request
- b4c6e229f3979a14092939042865697cd5b79c804ad37cbfa66ed55aed740966
- transaction
- c6223f0630387953befa7074cabcde90043e9a87e19211266427c4c2968b2d62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44074
the chainentry 44074
- sealed to the entry before
- 0e3c203c0b55b1345b79826fb88bc2c66111501de4b10886c76880147577d572
- this leaf
- 32ed32a5b9e37945b0864165087e23c0355ab0c038b79585fedd6659f5825de0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6y3c8QRqcwJuICNF0fi2CINKkTkdHQrbuWoMhn/vjfaVkRi/utBbW3sbnnKZQsjdKvhcHxrxNxM71va4F8U1Cw==