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
- 0dd255c3a537bab86755c6b3fb66691a9eb1a10806422aeeae400edbfb01fdbb
- request
- 6ba009b14770203a4bd3665705cf6a8a35d012df4420f7e1e40b933788be3f60
- transaction
- fcd3b3b9c75ccb74d6e752e70626d8998911960ae19e6284495c5e43e1164eb8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3507
the chainentry 3507
- sealed to the entry before
- bbb97828e324d46b986a1d31329f8d75cf82027d2d48d7f11fe97eb660f555da
- this leaf
- b82328bc8cdcdaaaf9fbb78fdd3ef1af7e15fcb2d67f63bed516af55ca2e5236
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PUSOzhFZg4upJizxb6tV61/soY5D0W8wxMs5d5fzgu1cV2XimBQ5fghvqMlrZCpYA4VMSxymbUMOPWX0anHIDQ==