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
- 3bf98181c05a437b7527841fc448fd9f47dfeb7387f3398c0731cae576ce0dc3
- request
- e00f9591a992b6652861fb5e201c7243dc1af7c4f8d1bed514969df5bbb79f99
- transaction
- 21880acf5b6421e0c3d9520020896567409b0b28c717e737ec365a95f1e734a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36518
the chainentry 36518
- sealed to the entry before
- 29258130ec3aac9155cd820c70a9b05fadf6f37eb42dc44ceb859d6fcbd84742
- this leaf
- a306152fd829b2b1c5748575fc782ab3d1f35e982a270486578a700938af8ff3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FIBn09Kuu4qVLNHPffEwOT+bVVDC4DwnaNiiGoqKwliLRCoqqzvQ4cyJDGDTDqFxUfVkw9nHhL2AJsiRbUYrCw==