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
- 1a43c07666be3a5ba7f79f4b648b7b9d3bfd1a1aa5fbc9bc4442ed927d9d33ad
- request
- c7b7cb836d6077ab2cea25b96ef42e7602095fc1717d91b414c5d0d573966316
- transaction
- a1786285d28869a69af8b4b88f293c89e8dd2a016461fdb2a18d0c52cef1f00ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52193
the chainentry 52193
- sealed to the entry before
- 0312a5e4099ddf7d34e5898c419a801319ff0878990af157cfd4b349e5e4c35e
- this leaf
- 55896e9af860df58df2ee87e8dbfee9e9c9b5e5f2b1b87da9f3c86c6d4f3bee9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2tsEnMM4xvTtXB6GY9KC5znXN5efdBXfM5FrQwdT3JwRAzfv+RAGAYa75JrVo2z9cZCkrzfcSAvkf8ns6/6dBQ==