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
- 7b976720c7f6af9f7e9d1863361ae946ce3c016fb342fbc8651bc3b4a222642f
- request
- f736dac8cd5a213ac899b0b727d4138cc6fce037d0ed086702a46e9548154565
- transaction
- 8235168bde88d748b0413fbcdec934184aaf311af766636c427c01c54ce886a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2095
the chainentry 2095
- sealed to the entry before
- 5fbdc0b62dba7f3ac2b95e1f418062699ef213af514295cea7fd182987f7277f
- this leaf
- 0366fbfd79e7b9d17bc657b7b7be91a6cb3b3abae0aecef6306e1ca6529def6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LWk3B0iicrUy8pLSn8/oSLCHEYGFhZ5MIwDLG4/Y9J5vXmBHd3Ey/Z48BXtIlld775X1V7LJ7CREdsVWLs98DA==