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
- 68c1f03086308992ce99771cfef89774e692b0532f2c145c11224df94c017937
- request
- a315987e2a18768a9ab98f8b0de0e48c363e2160a1e7d17b6de2404b93b1b0ef
- transaction
- 426c45317313cd606ab76d65e6f09d8c7268ef7c815c55f7f6ac175610968b74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60299
the chainentry 60299
- sealed to the entry before
- 9a9a991ae3845a79d7395e94189b7d17a77552725c51de57eddaf21bcdd49379
- this leaf
- f16854d99175047af8b923640a8aa548d0dc04a714cdfefa9a52410b40ede550
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 609/N2rODbCM5LyfK9erfrKNSPnjLlFwFNCHtxgjyXNyXU+y2NVkm7t9/TfrmhbZZ0GMul3I+1+QH8ylTiJIAQ==