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
- abb5487be80540703c20a7148ec1768ccf22a24e5f90500bfd7496bc9920b969
- request
- bd04c4fcc19ecc9e64484ffba95b426906da73c3da355d300533519135cacefd
- transaction
- 20fe1d258ddaf6d75eec9ce435130fcac8c0bcde108093b00c09322f8a1071a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1245
the chainentry 1245
- sealed to the entry before
- 88d18f08e304c3a31b141482abd56954fdcabb22961eefcf3b1718d339ac1575
- this leaf
- 09f6e53a4a53913d854a84ff4ab5be2a6982e5bd2239e9b97a195db0f1781cee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ydx6+la2ozs7Ze51rOboyh2Rs9DmtiBlfWdTKLmBlsCsuon190HfCUBJMlpNlL99yeTfrmtG1slKlXKEdha/BA==