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
- 2c4d69fe89ad313595b6262a032a79c83063bb953decd10a829a28a201b09b00
- request
- 44412e643e34d9813046644257366af106d279f98a72485165afff8442679d87
- transaction
- da03cc6b9d854cf48e8bb6a35ae7455cf59ee213a5736f1a10dae29e46b56a94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63651
the chainentry 63651
- sealed to the entry before
- 4e19bd7f77dc89df773630dae00f810242c5dd7d55c558f1ef7a329a123cee5d
- this leaf
- e4762be09a51c4d6d996d93834bc183d921910c4b158550d5171dda6fb51df19
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6kR6LgJIh3LRiYUHNLTbd+U8HMCGUy3GPmRZYbseBTYnX7ex4bwq8AHPnYjFTefyodULskqW/YDAbz0mMpyXBA==