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
- 6987dbc1c5a2fd269513f1472fed9e62509ee11c83090d9c0b627af7a88a559f
- request
- df3ad2332e19de5ed1a03327bb53a45617a4b5dc5f7277b79ab791c99be3259a
- transaction
- 44b55b0a211770bbd3142ec0ec594d1dcda097ef0659f95c675be00917fd7673computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46277
the chainentry 46277
- sealed to the entry before
- 8fc2fdc103cfea9191999993c66f34dab3f4fa5c4a1633e2ddc36059e3a266f4
- this leaf
- 67de479c4eff0d3a45ec4ee52e3bc6f3ee2d0688c4cd71a69138d768ba0eaf4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HTodCVCmnlWLaJQAMElA/mkUZIY8ihwng+ITTDxxgnS1hZZnHmgLiGRJlOlY+SSZV/B3fslkiOgOOr59+mGrBg==