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
- 6ccdc7d5ad1414e4a5a2525bef947a4dfe7f76ecc38b1087374a48aab020e619
- request
- 98660ceca5e6f26802524a0553d420193977d0dcf255b37e8ade253f7069598c
- transaction
- e79ae6fd33042aed36c1baecbf0604f9f512620feb16308e9570806219d846b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37861
the chainentry 37861
- sealed to the entry before
- c5f14903c6450db144e2b98e023db151ef0def168cb5fed62115135c86aa2257
- this leaf
- e7e1e0f4df3590636a790a2f57897597e2b5c9cd60d24fc12c519bb9475d397a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o8xiExW18/urGi5vudS4m+a3pgvMx2VJvpjBRhoFW+9cR0OidoIowfV8wRGFm4EbTqs35nTmPOrF8AQVt0MPBA==