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
- 82287a607e8cb8156f5db53b92ca6587435bd32ebbb4ecc67f970de11ba6a26e
- request
- 30a1deba545b383cb43215750b57bd98cb9f4a13b442452b4fa5ce62cf0a587a
- transaction
- 539f8759e55f6e82ace31377b382b3b1ef2f338095acc5d3bdda6211aa03737dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22217
the chainentry 22217
- sealed to the entry before
- 3fe7449941addaf412d153b4ea5f60c5db2817bf899bb58d004cfa309bffe113
- this leaf
- 8e12ad550a52900eb78365364394f2b8bb4a33dcb43e28c1f7c412f5ad81d434
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- meA+hC21T8tzadfRgNW7eDun3IynmH9rI6OhcUVqlYP6cHwfebAhDA+YJjD1Kj5wuD6DJ2TH5T4qt/5mLwIRDw==