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
- 5bd7e66b0717678e97dd671c6829b5f43a757f69813952759f8ca2309047db24
- request
- 7a2812c12572484668543d71d50195e1d76feb35a537188bd635fe0fd8014804
- transaction
- 1fa2b061e48fc8ceba1edcf54a7e369108720738fac9bd24eb4f603f892c929fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20220
the chainentry 20220
- sealed to the entry before
- 52316c8bf8253f26fb6718b7e7f949db13e6c3a4242d1e366cd3efbf418eac56
- this leaf
- 97c6fb7185d0c9089dc6610cf92cc81e284d701e6485f9c67d0dfc0ffa7b21c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JbpHVfgLF0ax9tNVqrltjY7WUrN9X2b9wF8z/Rj0j3tnq02DiULAohWT5NwolAXUqpdWYQ1m5JDD4vT4W4yIAg==