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
- 3973742cdf7752d238b1ffebe9c10142fc0913e6df69a11e11b61b2118762cf8
- request
- ea3bb6dae0e16393a699564264f690cb62467f8ae3e0b16a2b69e9bc6af63d68
- transaction
- 56fa2651157ce8ee290e703778ba9a5da15791d91f837a1e87756aa61c0a793dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72546
the chainentry 72546
- sealed to the entry before
- 168dbd58ff083bb1ca6c513681568532ad019a06ce8f45103d94011004156859
- this leaf
- 8fd5c52be63f093a0bc345d17bae8b7ed4868fa2460f8813773460768e680c01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4h0yEWmLYKrFUWwClg1hHDTTPOEl64uWvyJ53e6unut72HB6r4PqA2b9Cf3BxqkSiEJ0HG2dGW077HxLQwPjDw==