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
- f581fe6350b1ed0a46a11d3c6f9e0a04d9abdc537dd591523ecf2385d99a3d55
- request
- 317053a637742d3ab329d1d681ba5659806d50567da894e80c521757a638e7e9
- transaction
- 42dc9f9b72db34c606ea3620e3964dda0352bd9bd5e9a6161bf18f99551bce74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61930
the chainentry 61930
- sealed to the entry before
- d2ebd898a67f44de624e6bfbc129000d9fd324947165f96e1fedf32fbb03f2f1
- this leaf
- cf22752daa2d931e2179a67c84e14ea634f279a5338ec6b1b9999f17327be003
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QucECSaX/gRt/JgmoJ7VCSDuwTgCKmgWOHWbq2hT6NYhVCIp5QYaE5bYTLw23zLweDWunFuhqYfkRfk2BZTaAg==