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
- ab3786614b8b0fb882587816b5db9713a93109967fd8ef235ae440e0e05c797e
- request
- 0218eccf2dccf90e2ba6e4d96cfba16adf804c3287aabe7f25b4f374cf91b562
- transaction
- caa588b3bb6ec86e4c74bac9a983b399a479adadfb0c083bbc4a64a2036fdcd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74221
the chainentry 74221
- sealed to the entry before
- 58d6c9e4edfd40f740bcdd1ef20baee6b0f7d95c8834386f5a463dc4869b10b7
- this leaf
- 271160034faebb78a5ea4fc215fb42e1d839aef324d12e6a5e7d491d71a8607e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nfd00VR88CSiofKPPSYIYHFxQHugSd+1IjvjdrOirNiaupaE30L/tlbqTYlchDqHJXq/PH2HZwZS6ahTDfLsCA==