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
- b01b73612de01f7ea0b928a99ebe9b6bb667d009ca0f80324b0b2b006547e98e
- request
- 794ce3ef0949a826bc0707f47a87f9e5e9a44905aff88ddad934fe89426ae588
- transaction
- b3a9779d0a6b26bd39084b2cb55aa4272fc57b4836edce076fb9208d651142b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73268
the chainentry 73268
- sealed to the entry before
- 1d5cd1d8f2081e651e61c50eb2443cc449a0a394ff79f6f44667aa0b7432a809
- this leaf
- e10d2226432df17829f39531727b2f60eaef6af999956ce87896fca353bcb88c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q3QQjLuhBfopd+MYXkw85a7/5UAAKUvuCQLNfBA5UJ2OpNdqDRsReG5CeI70bXOMAT4Ls7ToeyXdgcttrM5MCg==